DBI1000 - DBI1249

DBI Message ID	Message	Explanation	User Response
DBI1001I	An invalid argument was entered for the db2icrt command.	You can create a database manager instance, including a DB2 pureScale instance by using the db2icrt command. You can also create an initial DB2 member and cluster caching facility (CF) as part of the creation of the DB2 pureScale instance by using the db2icrt command. This message is returned when the db2icrt command is invoked with incorrect or missing parameters.	Enter the command again using valid parameters.
DBI1002I	Usage: db2uit [-d] [-Q] [-D] [-q <field>] [-i <id>] [-a <action>] [-r <runlevels>] [-p <process>]	An invalid argument was entered for the db2uit command. Valid arguments for this command are: -d turn debug mode on -q query a field given the search parameters. Without -q, this becomes an update (if -i ID is already present) or insert. Valid fields: i, r, a, p -i ID of the entry -r run levels -a action to perform -p process to launch -Q Quiet: no output -D Delete record FileName file to modify RETURN CODES: -q If no field matches, non-zero, zero otherwise update/insert If file could not be updated, non-zero, zero otherwise	Rerun the command with valid arguments.
DBI1003I	Usage: dlfmcrt [-b BackupDir] -p PortName -g DLFMGid DLFMAdmin	An invalid argument was entered for the dlfmcrt command. Valid arguments for this command are: -h\|-? display the usage information. -p PortName is the port name or port number to be used by this instance. -b BackupDir is the directory to be used to create the backup of the dlfm database in. -g DLFMGid is the DLFM Admin group (this group must be a secondary group of DLFMAdmin) DLFMAdmin is the name of the DB2 Data Links Manager Administrator.	Enter the command again as follows: dlfmcrt -p PortNum -g DLFMGid DLFMAdmin
DBI1004W	`libdb2-link` detected. This DB2 copy may encounter problems loading its libraries.	The db2ln command was run from another DB2 copy which creates symlinks in /usr/lib. These symlinks interfere with multiple DB2 copies running on the same system, whether those copies are the same version at different fixpacks, or different versions.	From the installation path where the db2ln command was run, run the db2rmln command to remove these links.
DBI1006I	An invalid argument was entered for the db2idrop command.	The syntax for the db2idrop command is: `db2idrop [-h\|-?] [-d] [-g] [-f] InstName` Valid arguments for this command are: -h\|-? Display the usage information. -d Turn debug mode on. -g This parameter is required when `db2idrop` is used with a DB2 pureScale instance. Specifies that you want to drop the DB2 pureScale instance on all hosts. This parameter requires all DB2 members and all cluster caching facilities (CFs) are stopped on all the hosts in the DB2 pureScale instance. -f This parameter is deprecated. This parameter flags applications. If this flag is specified all applications using the instance will be forced to terminate. This parameter is not supported on a DB2 pureScale environment. InstName Specifies the name of the instance.	Enter the command again using valid parameters.
DBI1007I	Usage: dlfmdrop DLFMAdmin	An invalid argument was entered for the dlfmdrop command. Valid arguments for this command are: -h\|-? display the usage information. DLFMAdmin is the name of the DB2 data Links Manager Administrator.	Enter the command again as follows: dlfmdrop DLFMAdmin
DBI1008E	Install media and AIX version mismatch.	Installing DB2 64-bit on AIX requires different CDs for AIX version 4 and AIX version 5. db2setup has detected that your system is running AIX version 5, but you are installing from the DB2 for AIX version 4 CD.	Insert the DB2 for AIX version 5 CD and try the installation again.
DBI1009E	Install media and AIX version mismatch.	Installing DB2 64-bit on AIX requires different CDs for AIX version 4 and AIX version 5. db2setup has detected that your system is running AIX version 4, but you are installing from the DB2 for AIX version 5 CD.	Insert the DB2 for AIX version 4 CD and try the installation again.
DBI1010E	The host `host-name` is not offline. Command: `command-name`	The host is still active in the GPFS cluster. Prior to updating the GPFS level, the host must be offline.	Shutdown the GPFS cluster on the specified host by executing the specified command. For example, /usr/lpp/mmfs/bin/mmshutdown
DBI1011I	An invalid argument was entered for the db2iupdt command.	You can use the db2iupdt command to update a database manager instance to a higher level within a release, convert a database manager instance to a DB2 pureScale instance, or manage DB2 members or cluster caching facilities (CFs) of a DB2 pureScale instance. This message is returned when the db2iupdt command is invoked with incorrect or missing parameters.	Enter the command again using valid parameters.
DBI1013I	Usage: dlfmupdt [-h\|-?] DLFMAdmin	An invalid argument was entered for the dlfmupdt command. Valid arguments for this command are: -h\|-? display the usage information. DLFMAdmin is the name of the DB2 Data Links Manager Administrator.	Enter the command again as follows: dlfmupdt [-h\|-?] DLFMAdmin
DBI1014E	Instance upgrade to 32-bit is not supported.	Upgrading from 64-bit to 32-bit is not supported in this version.	No actions required.
DBI1015E	The db2iupgrade command failed because an invalid argument was specified.	You can upgrade a database manager instance to a new release by using the db2iupgrade command. This message is returned when the db2iupgrade command is called and invalid parameters or arguments are specified.	Run the command again, specifying only valid parameters and arguments.
DBI1016I	Program `program-name` is performing uninstallation. Please wait.
DBI1017I	installFixPack is updating the database products installed in location `location`.
DBI1019E	DB2 Administration Server `DAS` cannot be updated.	An attempt to update the DB2 Administration Server `DAS` has failed because: This version of the dasupdt command cannot be used to update the DB2 Administration Server. To use this level of code for the DB2 Administration Server, an upgrade is required (instead of an update).	To move the DB2 Administration Server up to this code level, issue the dasmigr command from the <current database product installation path>/instance directory to upgrade the DB2 Administration Server.
DBI1020I	An invalid argument was entered for the db2setup command.	The syntax for the db2setup command is: `db2setup [-h\|-?] [-t <TrcFile>] [-r <RspFile>] [-c] [-l <LogFile>] [-i <Lang>] [-f <nobackup>]` Valid arguments for this command are: -h\|-? Displays help information. -t Turns on the debug mode. The debug information is written to the file name specified. -r Performs a response file install using the file name specified. This parameter is mandatory when -c is specified. -c Validates the contents of the response file specified in the -r parameter. When specified, you must also specify the -r parameter. -l Writes the log to the file name specified. For root installations, the default log file is /tmp/db2setup.log. For non-root installations, the default log file is /tmp/db2setup_<userID>.log, where <userID> represents the user ID that owns the non-root installation. If the IBM Tivoli System Automation for Multiplatforms (SA MP) is being installed with db2setup, the install log file for the SA MP will be located in the same directory as database log files. -i Displays the db2setup utility in the language specified. -f This applies to the non-root upgrade only. Force db2setup to not backup installation files when the components are updated. If you choose not to backup the files, the space requirement of the installation directory is reduced. However, choosing not to backup the files also means that if any errors occur, the database product installer will not be able to perform a rollback operation. In this case, you will need to manually clean up the files and reinstall the product.	Enter the command again using valid parameters.
DBI1021I	Usage: db2imigrev [-h\|-?] [-m Version] InstName	An incorrect argument was entered. Valid arguments for this command are: -h\|-? display the usage information. -d turn debug mode on. -m specify DB2 version. Version is the version the instance will be migrated backward to. InstName is the name of the instance which will be migrated backward from version 8 to the previous version of DB2.	Enter the command again as follows: db2imigrev [-h\|-?] InstName
DBI1022I	Usage: db2imigrev [-h\|-?] [-f] InstName	An incorrect argument was entered. Valid arguments for this command are: -h\|-? display the usage information -d turn debug mode on. -f is the force applications flag. If this flag is specified then all applications using the instance will be forced to terminate. InstName is the name of the instance which will be migrated backward from version 8 to a previous version of DB2.	Enter the command again as follows: db2imigrev [-h\|-?] [-f] InstName
DBI1023I	Usage: db2ginfo [-h\|-?] [-y] [-c InstName [-a AuthType] [-u FencedID]] OutputDir	An invalid argument was entered for the db2ginfo command. Valid arguments for this command are: -h\|-? display usage information. -y executes script (only shows warning otherwise). -c InstName specify instance to test. -a AuthType specify authentication type (SERVER, CLIENT, or SERVER_ENCRYPT). -u FencedID specify fenced user ID. OutputDir is the directory where the output file, dbginfo.txt, will go.	Enter the command again as follows: db2ginfo [-h\|-?] [-y] [-c InstName [-a AuthType] [-u FencedID]] OutputDir
DBI1024I	Usage: db2iauto [-h\|-?] -on\|-off InstName	An incorrect argument was entered. Valid arguments for this command are: -h\|-? display the usage information -on\|-off enables or disables autostarting of an instance. InstName is the name of the instance.	Enter the command again as follows: db2iauto [-h\|-?] -on\|-off InstName
DBI1025I	Usage: dascrt [-d] -u ASUser	An invalid argument was entered for the dascrt command. Valid arguments for this command are: -d enters debug mode, for use with DB2 Service -u ASUser is the user the DAS will run under	Enter the command again as follows: dascrt -u ASUser Confirm that user IDs and group names used to create the database manager instance are valid.
DBI1026I	Usage: dlfmfsmd [-h\|-?] [-j] dlfsMntPt	An invalid argument was entered for the dlfmfsmd command. Valid arguments for this command are: -h\|-? display the usage information. -j modify the named file system from dlfs to jfs on AIX. dlfsMntPt Mount Point for Data Links Manager Filter file system (including the slash: /).	Enter the command again as follows: dlfmfsmd dlfsMntPt
DBI1027I	Usage: `command-name` [-d]	An invalid argument was entered for the command. Valid arguments for this command are: -d enters debug mode, for use with DB2 Service	Review the command syntax and enter the command again.
DBI1028I	Usage: dasupdt [-d] [-D] [-h\|-?]	An invalid argument was entered for the dasupdt command. Valid arguments for this command are: -d enters debug mode, for use with DB2 Service -D Moves the DAS from a higher code level on one path to a lower code level installed on another path. -h\|-? Displays usage information.	Enter the command again as follows: dasupdt
DBI1029I	Usage: db2nqadm [start\|stop]	An invalid argument was entered for the db2nqadm command. Valid arguments for this command are: start start all NetQ services and daemon stop stop all NetQ services and daemon You must specify one of the arguments.	Enter the command again with the proper argument.
DBI1030E	Kernel parameter `name` must be set to `value`.	DB2 requires certain kernel parameters to be updated.	Update all necessary kernel parameters. Reboot the system Try this command again
DBI1031E	The installation operation failed because the selected product requires the database server to be installed first.	There are multiple methods for installing database software, including the DB2 Setup wizard and the db2_install command. This message is returned when a component or Feature is selected to be installed, but the selected component or Feature cannot be installed until after the database server is installed.	Install the database server.
DBI1032E	The product you selected can not be installed on AIX with a version less than 4.3	The database product you selected requires an AIX version that is 4.3 or greater.
DBI1033E	The installation operation failed because the selected product requires the database server to be installed first.	There are multiple methods for installing database software, including the DB2 Setup wizard and the db2_install command. This message is returned when a component or Feature is selected to be installed, but the selected component or Feature cannot be installed until after the database server is installed.	Install the database server.
DBI1034W	Missing prerequisite package.	One of the following packages has been selected for installation: "<pkg-name>" Either the installed "<pkg-name>" file set level is below "<name>" or it cannot be detected.	Ensure the "<pkg-name>" file set is version "<name>" or higher. Your "<pkg-name>" level will not affect the installation of DB2.
DBI1035E	Failed to mount file system `File-System`.	An attempt to mount the specified file system has failed.	Verify that the file system is defined. Correct any errors from the mount command and try again.
DBI1036E	Failed to unmount file system `File-System`.	An attempt to unmount the specified file system has failed.	Correct any errors from the umount command and try again.
DBI1037E	File system `File-System` does not exist.	The file system specified is not defined on this workstation.	Define the file system on the workstation and try again.
DBI1038E	File system `File-System` cannot be modified.		Ensure that you have write permission to the system file that contains file system definition, and try again.
DBI1039W	Missing prerequsite package.	One of the following packages has been selected for installation: "<name>" However, the installed "<name>" file set level is below "<name>"	Install the "<name>" file set version "<name>" which is provided on the CD.
DBI1040I	The translated version of following message is not available on this system.		The translated version of following message is not available on this system. Please refer to the "Installation.Notes" file in the PRODDIR/Readme/LOCALE directory, where PRODDIR is the product directory and LOCALE is the locale name. For example, the product directory is: /usr/opt/db2_08_xx, where xx is 01 or FPn, where n is the FixPak number or /opt/IBM/db2/V8.x, where x is 1 or FPn, where n is the FixPak number
DBI1041E	File system `inputMntPt` cannot be converted to dlfs.	The File-systems "/", "/var", "/usr", and "/tmp" cannot be converted to a dlfs File-system. This has been done to avoid booting problems that may arise by making these dlfs File-systems.	Run the command again specifying a different File-system.
DBI1042E	Base File-system `BaseFS` cannot be changed to dlfs.	On Aix, a File-system can be changed to dlfs only if its vfs is fsm or jfs. Dlfs is not supported for any other vfs.	Run the command again on a jfs or fsm file system.
DBI1043E	The product you selected requires DB2 Administration Client installed first.		Install DB2 Administration Client. Try to install the product again.
DBI1044E	The installation of the national language package cannot begin because there is no prerequisite database product installed at this install location: `install-path`.	The national language package can only be used to add national language support to installed database products that include:
DBI1045E	An invalid argument was entered for the db2_install command.	On UNIX operating systems, you can install all features of a database product to a specified path by calling the db2_install command. This message is returned when the db2_install command is called with invalid parameters or syntax.	Call the db2_install command again, specifying valid parameters and syntax.
DBI1046I	Usage: doce_install [-b <installpath>] [-p <db2producttobeinstalled>] [-c <imagelocation>] [-l <logfile>] [-t <trcFile>] [-n] [-L <language>] [-h\|-?]	-b Specifies the path where the database product will be installed. Mandatory when -n is specified. The length of the path is limited to 128 characters and is a full path name. -p Specifies the database product to be installed. Mandatory when -n is specified. -c Specifies the location of the related national language pack (NLPACK). This parameter is mandatory when -n is specified. The NLPACK locations needs to be provided explicitly if the all of the following conditions are all met: The -n option is specified The current installation requires needs to install National Language (non-English) language supports The NLPACK is neither on the installation media nor in the same subdirectory as the database product being installed -l Specifies the log file. The default log file is /tmp/doce_install.log$$, where $$ is the process id. -t Turns on the debug mode. The debug information is written to the file name specified. -n Specifies non-interactive mode. When specified, you must also specify -b, -p, and -c. -L Specifies national language support. To install multiple languages at the same time, this parameter can be specified multiple times. For example, to install both English and German, specify -L EN -L DE. -h\|-? Displays help information.	Reenter the command.
DBI1047I	An invalid argument was entered for the db2_deinstall command.	The syntax for the db2_deinstall command is: `db2_deinstall -F <featureName> \| -a \| -r <RspFile> [-l <logFile>] [-b <installPath>] [-t <trcFile>] [-s GPFS] [-s TSAMP] [-f sqllib] [-h\|-?]` For details about the parameters of the db2_install command, refer to the documentation for Linux, UNIX, and Windows.	Enter the command again using valid parameters.
DBI1048I	Usage: doce_deinstall -a [-l <logFile>] [-b <installPath>] [-t <trcFile>] [-r <response_file>] [-h\|-?]	-a Removes all installed database products in the current location. -b <installPath> This option is valid if the command is run from the installation media. It specifies the absolute path where the database product was installed and will be uninstalled. The command will prompt for the path if the option is not specified. -l <logFile> Specifies the log file. The default log file is /tmp/doce_deinstall.log$$, where $$ is the process id. -t <trcFile> Turns on the debug mode. The debug information is written to the file name specified. -r <response_file> Removes the Information Center using a response file. For example, doce_deinstall -r db2un.rsp. Cannot be combined with the -a parameter. -h\|-? Displays help information.	Reenter the command.
DBI1049I	Usage: db2ls [-q] [-b <baseInstallpathOfDB2>] [-c] [-f <feature rsp file ID>] [-l <logfile>] [-p] [-a]	-q Specifies that this is a query of the local components. By default, only the visible components (features) are displayed unless -a is also specified. Mandatory when -p is specified. -b <installpath> When using the global db2ls command, you need to specify which directory you are querying. The global db2ls command will simply call the db2ls from that install path and pass in the rest of the parameters. -c Prints the output as a colon-separated list of entries rather than column-based. Allows you to use shell scripts to accurately work with this information. For example: #FEATURE:NAME:VRMF:FIXPACK: SPECIALINSTALL:PREREQS. -f <feature response file ID> Queries to check if the specific feature is installed. If the feature is installed, the return code is zero. If the feature is not installed, the return code is non-zero. -l <logfile> Specifies the log file name. -p Lists the database products installed. Cannot be combined with -f or -a. Must include -q. -a Lists all hidden components and visible features. The default is to only list visible features.	Reenter the command.
DBI1050E	Unsupported operating system - `OS-name`, version `OS-ver`.	Your current operating system is not supported or this version of the operating system is not supported.
DBI1051E	You cannot execute this program as root.	This program can only be run under a non-root user ID.	Login as an user ID other than root, and issue the command again.
DBI1052E	The command failed because the current user does not have system root user authority.	Special privileges are required to execute some DB2 database commands. This message is returned when a non-root user ID issues a database command that requires root user authority.	Login as root and then issue the command again.
DBI1053E	File system of type `fsys-type` is not supported.	Creating the instance's home directory on this type of file system is not supported. Instance's home directory must exist either on a local file system or on a NFS mounted file system.	Change the home directory to a supported file system and recreate the instance.
DBI1054I	The installFixPack command failed because an invalid argument was specified.	You can update the installed database products in a given location, on all UNIX and Linux platforms by using the installFixPack command. This message is returned when an invalid parameter argument is specified with the installFixPack command.	Enter the command again using valid parameters.
DBI1055E	The message file `file-name` cannot be found.	The message file required by the instance commands is missing from the system; it may have been deleted or the database products may not be installed properly.	Verify that the product option containing the message file is installed correctly. If there are verification errors, reinstall the product option.
DBI1056I	Usage: db2chgpath [-d] [-f <relativePath/FileName>]	-d Turns debug mode on. -f Specifies a specific file name to update the runtime path. The specified file name should have the path name relative to the base of the current database product install location. Root authority is required, and this command must be run directly from DB2DIR/install directory.	Reenter the command.
DBI1057E	Required locale `locale` is not available.	The required locale directory, /usr/lib/locale/LANG/LC_MESSAGES, does not exist, where LANG is the name of your current locale.	Verify that the specified locale has been installed correctly. Also check for the read and execute permissions are set correctly on that directory.
DBI1058E	gunzip command not found.	The gunzip utility must be available on your system to install or update database products.	Ensure the gunzip utility is installed in the PATH environment variable. Reenter the command.
DBI1059E	The deinstallation process halted and cannot continue because there still exist database manager instances related to the current installation directory where files are going to be completely uninstalled.		If the deinstallation is for moving up level or down level, use installFixPack in the images of the desired level to perform the update. If the purpose is to uninstall then reinstall the database product in the same location, use installFixpack with the -f option. If the purpose is to just uninstall the database product in the current location, drop the database manager instances related to the installation directory if they are not needed any more. Or update the database manager instances to another installation location for the same version of the database product and then restart db2_deinstall.
DBI1060E	Invalid package name `pkg-name`.	An incorrect name has been entered. The package either does not exist or the name has been entered incorrectly.	Check to see if the name of the given package exists on the distribution media. If so, examine the name to see if it has been misspelled.
DBI1061E	A file set or package name `pkg-name` is missing.	An error occurred when verifying software pre-requisites. The indicated file set or package must be installed before using this command.	Check to see if the name of the given package has been installed on your system.
DBI1062E	A file set or package name `pkg-name` is missing.	The indicated file set or package must be installed before using this command.	Install the file set or package and then reissue this command.
DBI1063E	PTF or patch `patch-name` is missing.	The indicated PTF or patch must be installed before using this command. This PTF or patch is required to complete this command successfully.	Install the required PTF or patch and enter this command again.
DBI1064E	The user `user` is being used by the database manager instance and thus can not be used to create the DB2 Administration Server.	The user that is being used to create the DB2 Administration Server is being used by the database manager instance. You should not create the DB2 Administration Server with this user.	Use a different user name that is not being used by the database manager instance to create the DB2 Administration Server.
DBI1065E	Program `program-name` terminated prematurely.	An error has occurred during the execution and that has caused this program to terminate prematurely.	Correct the problem and try the command again.
DBI1066E	Program `program-name` terminated by request.	This program has been terminated by the user.	Issue the same command to restart the program.
DBI1067E	The library for locale `locale-name` is not installed.	No compressed-tar HTML files can be found in the DB2DIR/doc/"<locale-name>"/html directory, where DB2DIR = /usr/opt/db2_08_xx, where xx is 01 or FPn, where n is the FixPak number or /opt/IBM/db2/V8.x, where x is 1 or FPn, where n is the FixPak number	Install the library for the required locale and issue this command again.
DBI1068E	There is not enough space to uncompress and un-tar all the HTML file in the directory `dir-name`.	After uncompress and un-tar, all the HTML files cannot be saved in the indicated directory because the file system is full.	Increase the size of the file system or free up sufficient disk space in the file system. Issue the command again.
DBI1069E	Unexpected error. Function = `fname`, Return code = `return-code`.	An unexpected error occurred during the execution of this program.	If the problem persists, contact IBM Support with the following information: Message number Function name Return code Problem description
DBI1070I	Program `program-name` completed successfully.
DBI1072I	The db2licm command failed to update the license. Refer to the log file `log-name` for more information.	Because the db2licm command failed to add the license, the database product will run with a Try-and-Buy license until a product license is installed.	Issue the command again. If the problem persists, contact IBM software support.
DBI1073E	The parameter `parameter_name` is missing. This parameter is required for the `installer_name` command.
DBI1074E	Administration server does not exist.	An attempt was made to update or upgrade an administration server. An administration server does not exist.	Create an administration server using the dascrt command.
DBI1075E	Administration server cannot be migrated.	The administration server cannot me migrated. The administration server is running at a level which is not a supported DB2 migration level.	If the administration server is running the same version as DB2, use dasupdt to update the administration server. If the administration server is running an unsupported migration level, drop the administration server using the dasdrop command, and re-create the administration server using the dascrt command at the current DB2 level.
DBI1076E	The installation of DB2 pureScale failed because no supported RDMA capable network adapters were found.	The DB2 pureScale Feature requires the use of Remote Direct Memory Access (RDMA) capable network adapters to provide a low latency cluster interconnect. A supported RDMA adapter was not found.	Consult the documentation about installing DB2 pureScale for information on network considerations in the installation prerequisites.
DBI1077E	The user `user` is being used by the DB2 Administration Server and thus can not be used to create the database manager instance.	The user that is being used to create the database manager instance has been used by the DB2 Administration Server. You should not create the instance with this user.	Use a different user name that is not being used by the DB2 Administration Server to create the database manager instance.
DBI1078E	Updating the IBM Tivoli System Automation for Multiplatforms (SA MP) failed. See the log file `log-file-name` for details. (TSAMP_RC=`TSAMP_RC`).	The database product installer uses the installSAM utility to update the SA MP. The installSAM utility returned errors. The installSAM log file contains more complete information. TSAMP_RC is the return code from the installSAM utility. Note that you must have root authority to use the database product installer to update SA MP. SA MP was not updated.	See the mentioned log file for details. To update SA MP manually, use the installSAM command. For more information about the installSAM command, see the SA MP Base Component documentation.
DBI1079I	Output is saved in the log file `log-name`.	All processed and failed operations have been saved into this log file.	Do not modify this file in any way. This file is for IBM Technical Support reference.
DBI1080E	Disk full. Minimum space required in `dir-name` is `KB` KB, whereas only `KB` KB space is available.	There is not enough free space available in the file system or directory.	Free more disk space and retry the command.
DBI1081E	The file or directory `file-name` is missing.	A file or directory that is required to process this command is missing.	If the file belongs to one of the database products then verify that the product is installed correctly and reinstall the product if necessary. If the file belongs to an instance then the instance may have already been removed or it may be corrupted. Check to see if the name of the given directory exists on your file system. If so, examine the name to see if it has been misspelled. Note that all file and directory names are case-sensitive on Unix.
DBI1082E	The file or directory `file-name` already exists.	A file or directory that the command needs to create already exists.	Examine the specified file or directory. If the file or directory exists as a result of a previous successful completion of the command, no action is required. Otherwise, you need to either rename or remove the specified file or directory before trying the command again.
DBI1083E	An attempt to remove `file-name` failed.	An error occurred when removing the given file or directory. This may be due to an inappropriate ownership on this given file or directory.	Adjust the file permissions or ownership of the specified file or directory and then issue the command again.
DBI1084E	An attempt to create `file-name` failed.	An error occurred when creating the given file or directory.	Check that there is enough space in the file system and that you have write permission for the required directory. Suggested directory permissions are u=rwx,go=rx.
DBI1085E	An attempt to move the file or directory `file-name` to `file-name` failed.	An error occurred when attempting to relocate the given file or directory. The command could not be processed successfully.	Determine why the specified file or directory could not be moved and then try the command again.
DBI1086E	An attempt to copy the file or directory `file-name` to `file-name` failed.	An error occurred when attempting to duplicate the given file or directory. The command could not be processed successfully.	Determine why the specified file or directory could not be copied and then try the command again.
DBI1087E	An attempt to create the link `filename` failed.	The given link cannot be created. It could be that the write permission on its parent directory has been turned off, or that a file or directory with the same name already exists.	Check permissions for the parent directory and restart the install process. Suggested directory permissions are u=rwx,go=rx.
DBI1088E	Invalid access permission detected for directory `directory`.	This message can be returned for multiple reasons, including the following reasons: The given name is not a directory, or the directory does not have read and execute permission. The given directory can be created but cannot be accessed. The permissions on any of the parent directories of the given directory do not meet requirements for DB2 database instance and database directories. If the home directory of the database manager instance is located on a mounted drive, this message can be returned if the DB2 database install utility fails to validate the permissions of the mount point.	Check permissions for the given directory and restart the install process. Suggested directory permissions are u=rwx,go=rx. If the home directory of the database manager instance is located on a mounted drive, perform the following troubleshooting steps: Verify the access permissions of the home directory of the instance owner by using the command "su". Example: `/usr/bin/su <instance_owner> -c /bin/pwd` If the permissions do not include "r" and "x", unmount the drive, change the permissions, and remount the drive. Example: `unmount /<directory> chown <instance_owner> /<directory> chmod 755 /<directory> mount /<directory>`
DBI1089E	Error in saving current instance related information in the `backup-dir` directory.	There may be several reasons for this error. It is likely that one of the following situations has occurred: The given directory does not have sufficient permissions or does not have the write permission. There is no space left on the file system.	Take an appropriate corrective action and issue the command again.
DBI1090E	An attempt to update `parameter` in `file-name` failed.	An error occurred while updating the given file.	Verify that all occurences of "<parameter>" are set to "<value>" in "<file-name>".
DBI1091E	An attempt to change permissions for `directory` failed.	An error occurred when changing permissions on the given file or directory. This may be due to an inappropriate ownership on this file or directory.	Check permissions and ownership for the given directory and restart the install process. Suggested directory permissions are u=rwx,go=rx.
DBI1092E	An attempt to change ownership for `directory` failed.	An error occurred when changing ownership on the given file or directory. This may be due to an inappropriate ownership on this given file or directory.	Check ownership for the given directory and restart the install process.
DBI1093E	An attempt to change group ownership for `directory` failed.	An error occurred when changing group ownership on the given file or directory. This may be due to an inappropriate ownership on this file or directory.	Check ownership for the given directory and restart the install process.
DBI1094E	Directory access error.	The tool encountered an access error during an I/O operation with the directory server.	Ensure the directory server is on-line and accessible over the LAN.
DBI1095W	The file or directory `name` cannot be found.		Verify that the file set/package providing the file/directory has been installed.
DBI1096E	The file or directory `file-name` already exists.	A file or directory that the command needs to create already exists.	Examine the specified file or directory. If you no longer need this file or directory, remove it and then run the command again. Otherwise, you will need to either rename or remove the specified file or directory before trying the command again.
DBI1097E	The command failed because a file or directory does not exist or is invalid. File or directory name: `file-or-dir-name`.	This message can be returned when a file or directory that the command requires does not exist. This message can also be returned when the DB2WORKDIR environment variable is set to an invalid value: A directory that does not exist The /tmp directory	If the file or directory does not exist, you might have to install the software that provides the file or directory. If the file or directory does exist, ensure that the required directory is in the PATH environment variable. If this message is returned because DB2WORKDIR is set to a directory that does not exist, set the DB2WORKDIR to an existing directory. If this message is returned because DB2WORKDIR is set to /tmp, either set DB2WORKDIR to a directory other than /tmp, or use the environment variable DB2_SKIP_CHK_TMP to enable setting DB2WORKDIR to /tmp.
DBI1098I	Usage: db2cptsa [-h\|-?] [-c] [-f] [-r]	Valid arguments for this command are: -h\|-? Displays help information. -c Verifies that the DB2 High Availability (HA) scripts exist in /usr/sbin/rsct/sapolicies/db2, and that they are at the proper level. -f Forces a reinstall of the DB2 HA scripts in /usr/sbin/rcst/sapolicies/db2. Without this argument, if the version of the DB2 HA scripts that are already installed is the same as or higher than the version of the scripts being installed, then the installed scripts are not overwritten. -r Removes the directory /usr/sbin/rsct/sapolicies/db2. This dicrectory is where the DB2 HA scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) are located. These scripts and this directory will only be removed if the SA MP is not installed. This utility installs or updates the DB2 HA scripts in /usr/sbin/rsct/sapolicies/db2. You need these DB2 HA scripts to use the IBM Tivoli System Automation for Multiplatforms (SA MP) with the DB2 HA feature. By default, this utility installs the DB2 HA scripts in /usr/sbin/rsct/sapolicies/db2 if they aren't already installed there, or if the version of the scripts already installed is older than the version of the scripts being installed. This utility installs or updates the DB2 HA scripts if and only if the SA MP is already installed. This command must be run with root authority. This command can be found on the database product install media in the directory: db2/<plat>/tsamp where <plat> is: aix for DB2 for AIX linux for DB2 for Linux on 32-bit AMD and Intel systems (x86) linuxamd64 for DB2 for Linux on AMD64 and Intel EM64T systems (x86-64) linuxppc for DB2 for Linux on POWER (iSeries(TM) and pSeries) systems linux390 for DB2 for Linux on System z9 and zSeries The command is also available at <DB2DIR>/install/tsamp directory where <DB2DIR> is the installation path of DB2 database.	Reenter the command.
DBI1099I	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) were successfully installed in /usr/sbin/rsct/sapolicies/db2.	You need DB2 HA scripts to use the IBM Tivoli System Automation for Multiplatforms with the DB2 HA feature. These DB2 HA scripts are located at /usr/sbin/rsct/sapolicies/db2. The database product installer detects whether these DB2 HA scripts need to be installed or updated. The database product installer successfully installed the DB2 HA scripts.	No action is required.
DBI1100E	An instance lock is found. Another instance management command is running.	The command failed because another instance management command (eg. db2icrt, db2idrop, or db2iupdt) is running. The instance management commands acquire an exclusive lock to avoid conflicting simultaneous commands against the same instance.	Wait for all other occurrences of the instance commands to finish executing before trying the command again. If no other instance commands are running then delete the file "instance.lock" in one of the following directories: /usr/opt/db2_08_xx, where xx is 01 or FPn, where n is the FixPak number or /opt/IBM/db2/V8.x, where x is 1 or FPn, where n is the FixPak number
DBI1101E	The user name `user-name` is invalid.	The given user name must be the login name of an existing user and cannot: be more than 8 characters long. start with "sql", "ibm" or "sys". start with a numeral or contain characters other than a-z, _, or 0-9.	Please check the "User, user ID and group naming rules" in DB2 Administration Guide for details. Try the command again with a valid user name.
DBI1102E	The DAS name is invalid.	The DAS name must be the login name of an existing user and cannot be more than 8 characters long, start with "sql", "ibm", or "sys", or start with a numeral or contain characters other than a-z, $, #, @, _, or 0-9.	Issue the command with a valid DAS name.
DBI1103E	The Administration Server already exists.	The system detects that the Administration Server has already been created on your system. You can only create one Administration Server on each system.	If you want to re-create the Administration Server, you have to drop the Administration Server first before re-creating it.
DBI1104E	The Administration Server cannot be dropped.	An attempt to drop the Administration Server failed. The system detects that the Administration Server does not exist.	No action required.
DBI1105E	The DB2 Data Links Manager Administrator already exists.	The system detects that the DB2 Data Links Manager Administrator has already been created on your system. You can only create one DB2 Data Links Manager Administrator on each system.	If you want to re-create the DB2 Data Links Manager Administrator, you have to drop the DB2 Data Links Manager Administrator first before re-creating it.
DBI1106E	The DB2 Data Links Manager Administrator cannot be dropped.	An attempt to drop the DB2 Data Links Manager Administrator failed. The system detects that the DB2 Data Links Manager Administrator does not exist or has been created under a different user ID.	Verify that the name of the DB2 Data Links Manager Administrator as reported by the "dlfmlist" command is correct and try again.
DBI1108E	Valid group name or number `group-name` not specified for the DLFM user `user`.	While creating a dlfm instance,or migrating a dlfm instance from DB2 V7 or earlier, the -g DLFMGid must be specified. DLFMGid can be a numeric group id or a group name. The named group must be in the secondary group list of the named DLFM user. If migrating a V8 or later dlfm instance, if -g DLFMGid is specified which is not the same as the DLFMGid already set up for the instance, the specified parameter will be ignored and the old Gid will be used.	Set the group in the list of secondary groups for the DLFM user and reissue the command.
DBI1109E	The kernel parameters must be updated before using this command.	Some of the kernel parameters are not configured properly.	Update all necessary kernel parameters. Reboot the system Try this command again
DBI1110I	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) were successfully updated in /usr/sbin/rsct/sapolicies/db2.	You need DB2 HA scripts to use SA MP with the DB2 HA feature. These DB2 HA scripts are located at /usr/sbin/rsct/sapolicies/db2. The database product installer detects whether these DB2 HA scripts need to be installed or updated. The database product installer successfully updated the DB2 HA scripts.	No action is required.
DBI1111E	The FencedID parameter must be specified using -u flag with this command.	The FencedID parameter must be specified with this command. The FencedID parameter is set to the name of the user under which fenced User Defined Functions (UDFs) and fenced Stored Procedures will be run.	Enter the command again adding the arguments “-u FencedID” where FencedID is the name of the user that you want your fenced UDFs or fenced Stored Procedures to run under. For security reasons it is recommended that you do not use the instance name as the FencedID. However, if you are not planning to use fenced User Defined Functions (UDFs) or fenced Stored Procedures then setting the FencedID to the instance name may save you the step of having to create another user for the FencedID.
DBI1112E	The FencedID parameter `fenced-id` is not valid.	The FencedID parameter which specifies the user name under which fenced User Defined Functions and fenced Stored Procedures will be run: Must be the login name of an existing user. Cannot be set to the root or the bin user.	Try the command again with a valid FencedID parameter.
DBI1113W	Previous value of FencedID parameter `old-value` is different. New value `new-value` is ignored.	The FencedID parameter entered on the command line is different from the one used before for this userid. New value for this parameter is ignored.
DBI1114W	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) were not found in /usr/sbin/rsct/sapolicies/db2.	You need DB2 HA scripts to use SA MP with the DB2 HA feature. The db2cptsa utility expects to find these scripts, as well as a file named "spec", in /usr/sbin/rsct/sapolicies/db2. The database product installer could not find the DB2 HA scripts, or the spec file.	Run the db2cptsa utility with root authority to manually install the DB2 HA scripts.
DBI1115E	Invalid AuthType parameter `auth-type` specified with -a flag.	The AuthType parameter which specifies the authentication type used for the instance is not valid. Valid authentication types are: SERVER CLIENT SERVER_ENCRYPT	Try the command again with a valid AuthType parameter.
DBI1116W	The version of the high availability scripts found in /usr/sbin/rsct/sapolicies/db2 is a lower version than the version of the same scripts on the current install media.	The high availability feature being installed requires scripts with a version the same as or higher than the version of the scripts on the install media. This message is returned when the version of the scripts currently installed is lower than the version of the scripts on the install media.	Run the db2cptsa utility with root authority to manually update the scripts.
DBI1117I	The version of the high availability scripts found in /usr/sbin/rsct/sapolicies/db2 is a higher version than the version of the same scripts on the install media.	The high availability feature being installed from the install media requires scripts with a version the same as or higher than the version of the scripts on the install media. This message is returned when the version of the scripts currently installed is higher than the version of the scripts on the install media.	No action is required.
DBI1118W	The database manager has created a .profile file under the home directory of user `name` (instance owner or DAS) that contains the entries to set up a default environment (instance or DAS).	The user ID for the instance or DAS `name` is using the Korn Shell but does not have a .profile file under its home directory. The database product installation script has created the .profile file for the user ID and has populated the file with entries necessary for setting the default instance or DAS environment. This is done so that when the user logs in, the user will automatically acquire the instance or DAS environment.	If you are using the Korn Shell and want to manually set up the environment of the instance or DAS `name`, you can remove the .profile created by the DB2 script and manually set up the instance or DAS environment.
DBI1119I	The version of the high availability scripts found in /usr/sbin/rsct/sapolicies/db2 is the same version as the version of the scripts on the install media.	The high availability feature being installed from the install media requires scripts with a version the same as or higher than the version of the scripts on the install media. This message is returned when the version of the scripts currently installed is the same as the version of the scripts on the install media.	No action is required.
DBI1120E	Instance `inst-name` cannot be dropped.	An attempt was made to drop an instance which may still be active.
DBI1121E	Cannot drop the Administration Server using "db2idrop".	An attempt was made to drop the Administration Server using "db2idrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.	Use the "dasidrop" command to remove the Administration Server.
DBI1122E	Instance `inst-name` cannot be updated or upgraded.	An attempt was made to either update or upgrade an instance. This instance cannot be updated or upgraded because: One of the following commands cannot be used to either update or upgrade this instance: db2iupdt, db2iupgrade, or db2nrupdt. The instance is still active.	Ensure that you are using the correct version of one of the following commands: db2iupdt, db2iupgrade, or db2nrupdt. Also, ensure that there are no database manager processes running at the instance. Retry the command.
DBI1123E	Cannot update the Administration Server using "db2iupdt".	An attempt was made to update the Administration Server using "db2iupdt". This operation is not allowed since it will cause the registry to be in an inconsistent state.	Use the "dasiupdt" command to update the Administration Server.
DBI1124E	Instance upgrade failed. Instance name: `inst-name`.	This message is returned when upgrading an instance fails for one of several reasons: The instance is still active and the -prepare parameter was not specified. Upgrading this instance is not supported. This version of the db2iupgrade command cannot be used to upgrade this instance. The version of the currently installed product is the same as the version to which the upgrade was being attempted.	Ensure that the instance is ready for upgrading and you are using the correct version of the db2iupgrade command.
DBI1125E	Cannot drop the DB2 Data Links Manager Administrator using "db2idrop".	An attempt was made to drop the DB2 Data Links Manager Administrator using "db2idrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.	Use the "dlfmdrop" command to remove the DB2 Data Links Manager Administrator.
DBI1126W	Instance upgrade failed because one or more views defined in the database might impact database upgrade.	The db2iupgrade command calls the db2ckupgrade command. The instance upgrade fails if the db2ckupgrade command returns any errors. The db2ckupgrade command has identified one or more views that are dependent on database entities that have changed. This might cause the UPGRADE DATABASE command to fail. The identified views are listed in the db2ckupgrade log file.	Resolve the issue with the identified views or drop the views and then re-issue the re-issue the db2iupgrade command. After database upgrade, re-create the views that you dropped. Alternatively, you can upgrade a test database that contains the identified views in a testing environment to determine if the UPGRADE DATABASE command will fail. If the database upgrade is successful, re-issue the db2iupgrade command with the -F parameter to force the upgrade.
DBI1127E	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) found in /usr/sbin/rsct/sapolicies/db2 were not removed because the SA MP was still installed.	You need DB2 HA scripts to use the SA MP with the DB2 HA feature. You cannot uninstall these scripts while the SA MP is still installed. This is to prevent unexpected behavior resulting from using the SA MP with the DB2 HA feature without the scripts being installed. The DB2 HA scripts were not uninstalled.	If you intend to manually uninstall the SA MP as well as the DB2 HA scripts, uninstall the SA MP first using the uninstallSAM utility. Alternatively, use db2_deinstall with the -a and -F TSAMP arguments to uninstall the SA MP and the DB2 HA scripts, because db2_deinstall will uninstall these in the correct order.
DBI1128E	Cannot drop the Administration Server using "dlfmdrop".	An attempt was made to drop the Administration Server using "dlfmdrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.	Use the "dasidrop" command to remove the Administration Server.
DBI1129E	Cannot update the Administration Server using "dlfmupdt".	An attempt was made to update the Administration Server using "dlfmupdt". This operation is not allowed since it will cause the registry to be in an inconsistent state.	Use the "dasiupdt" command to update the Administration Server.
DBI1130E	The IBM Tivoli System Automation for Multiplatforms (SA MP) could not be installed or updated because system prerequisites were not met. See the log file `log-file-name` for details.	There are system prerequisites for installing or updating SA MP. These prerequisites have not been met. The mentioned log file has the details for the unsatisfied prerequisites. To find out more about the system prerequisites for the SA MP Base Component, see the SA MP Base Component documentation's Installation and Configuration Guide. SA MP cannot be installed or updated.	Modify your system to meet the prerequisites; and use the installSAM utility to manually install SA MP.
DBI1131E	The user ID `user-id` is invalid.	An attempt to access the given user ID failed. One of the following situations has occurred: This user ID does not exist on the system. The home directory of this user does not exist or is not set up properly. One of the user attributes needed by the database manager is unset. The UID of this user is 0	Make sure a valid user ID with valid home directory, shell, primary group and secondary group has been used. Create a new user if necessary.
DBI1132E	The database product installer could not find the correct license to install or update the IBM Tivoli System Automation for Multiplatforms (SA MP). The database product installer expected the license file to be found at `directory-name` on the database product install media.	The regular license for SA MP is named sam31.lic, and the try-and-buy license is named sam31tb.lic. One, but not both, of these files must exist in the specified directory on the database product install media for the database product installer to install or update SA MP. SA MP cannot be installed without the proper license.	Ensure the appropriate license file is in the specified directory and reissue the command.
DBI1133E	Command failed. The current host is part of a GPFS cluster.	The current host is part of an IBM General Parallel File System (GPFS) cluster. You cannot remove the GPFS cluster from the host on which the command was run. Also, the uninstallGPFS command is not a supported command.	To remove the GPFS file system and cluster on the remaining host, run the db2cluster command.
DBI1134W	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) were not installed because the SA MP was not installed.	You need DB2 HA scripts to use the SA MP with the DB2 HA feature. You do not need these scripts if you are not using the SA MP. The DB2 HA scripts were not installed.	No action is required.
DBI1135E	The primary group `users` of user ID `test-user` is invalid.	The primary group name of the instance user ID: Cannot be one of "guests", "admins", "users" or "local". Cannot start with "sql" or "ibm". Cannot start with a numeral number. Can contain only lowercase letters (a-z), numbers (0-9), and the underscore character ( _ ).	Ask a user with root privilege to change the primary group of the instance user ID to a valid group as described in this message's Explanation and then try the command again.
DBI1137W	Server Product not installed.	The instance you are upgrading is a Server instance. A database server product has not been detected. The instance will be upgraded only if the -F parameter is specified.	If the db2iupgrade command fails, reissue this command with the -F parameter to force the upgrade. The instance will not have the database server functionality . To re-enable database server functionality in the instance, install a database server product and issue the db2iupdt command to update the instance.
DBI1139E	Data-Links File Manager is not installed.	The instance you are upgrading has Data-Links functionality. Data-Links File Manager is not supported in the version of the database product you are upgrading to.
DBI1140W	Command is being Forced. You have specified the -F flag to force the issued command past the point of failures mentioned in the previous warnings.
DBI1141E	Visual Warehouse 3.1 instance detected. Visual Warehouse 3.1 instance migration to V8 is not supported. Only Visual Warehouse 5.2 and above can be migrated to V8.
DBI1142W	Visual Warehouse 5.2 instance detected. Instance will be migrated but warehouse metadata will not be migrated.
DBI1143W	Relational Connect is not installed.	Relational Connect was not detected in the version you are migrating to, but a setting file was detected for the instance you are migrating. This configuration will be migrated but Relational Connect has to be installed to make use of these configuration parameters.	Install Relational Connect to make use of the configuration parameters.
DBI1144E	Relational Connect is not installed.	Relational Connect was not detected in the version you are migrating to but environment variables have been found that indicate that you have non-DB2 data sources. This instance cannot be migrated if Relational Connect is not installed.	Please install Relational Connect and try the command again.
DBI1146E	The instance Setup wizard is not installed.	The db2isetup script can perform configuration and database manager instance setup tasks using a response file, or it can launch the instance Setup wizard to perform these tasks using a graphical user interface. Currently, only the response file support mode is installed. To use the graphical mode, the instance Setup wizard feature must be installed.	Install the instance Setup wizard by launching the DB2 Setup wizard from the CD (not available as part of the Runtime Client). Create a response file and reissue the command as db2isetup -r <responsefile>.
DBI1147E	db2iupdt failed to update the user ID `userid`.	The user ID specified is not a database manager instance.
DBI1148E	dasupdt failed to update the user ID `userid`.	The user ID specified is not an Administration Server.
DBI1149E	To execute this program, you must be the owner of the installation copy.	The current DB2 copy was not installed by the user who is running the program.	Log in as the user who installed the current copy of the database product and rerun the command.
DBI1150W	db2iupdt has updated this instance to a 64-bit non-server instance.	You cannot create or upgrade to a 64-bit Express server instance. If you want to run a 64-bit server instance, you must have the database server installed.	If you do not require a server instance, you can continue to use the created or upgraded instance. If you want to use a 64-bit server instance, you should install a database server, and run the following command: `db2iupdt -w 64 <instance-name>`
DBI1151E	The db2icrt command or the db2iupgrade command has created a 64-bit non-server instance.	You cannot create or upgrade to a 64-bit Express server instance. If you want to run a 64-bit server instance, you must have the database server installed.	If you do not require a server instance, you can continue to use the created or upgraded instance. If you want to use a 64-bit server instance, you should install the database server, and run the following command: `db2iupdt -w 64 <instance-name>`
DBI1152E	To run this program, you can not be root user.	`tool-name` can not be run by users with root authority.	Rerun the command as a non-root user.
DBI1153E	AIO is not enabled.	AIO needs to be enabled on the system to run DB2.	Ask a user with root privileges to enable AIO and try the command again.
DBI1154E	`instance-name` is an instance that belongs to a DB2 copy installed by a non-root user. The instance cannot be updated from a DB2 copy installed by a root user. If you want to update the instance, run db2nrupdt from the DB2 copy installed by the non-root user.
DBI1155E	The command failed for the non-root instance `instance-name`.	The command failed because you tried one of the following actions, which are not supported: Update the non-root instance to become a root instance Upgrade the non-root instance to become a root instance Drop the non-root instance by running the db2idrop command from a root installation location	To update the non-root instance, run the db2nrupdt command in the $HOME/sqllib/instance/ directory, where $HOME is the home directory of the user ID that installed the non-root instance. Upgrading to a root instance is not supported for non-root instances. To drop the non-root instance, uninstall the non-root installation by running the db2_deinstall command in the command $HOME/sqllib/install/ directory, where $HOME is the home directory of the user ID that installed the database product.
DBI1156I	System prerequisites cannot be checked completely when installing as a non-root user.	A complete system check cannot be performed because root authority is required.	A non-root user must check system prerequisites from the documentation. A system administrator must make sure the system meets all the requirements to install and use the current DB2 level.
DBI1157E	Invalid value.	The `parameter-or-value` passed to the installer command `cmd` is not valid.	Correct the error and run the command again.
DBI1158I	The database product will be installed to `installpath`.
DBI1159E	db2iupdt can not update an instance from using a non-root installation to using a root installation or vise versa.
DBI1160I	Non-root install is being performed.
DBI1161I	Usage: db2rfe [-h\|-?] [-d] [-l logfile_name] [-q] -f <db2rfe_configuration_file>	-h\|-? displays the usage information. -d turns debug mode on. -l logfile_name is a user specified log file. -q query which installed root features are enabled or not enabled or which configured service ports are reserved or not reserved. The -q option should not be used with the -f option. -f is mandatory option. db2rfe_configuration_file is the full path name of db2rfe's configuration file. Note: This command must be run from the $DB2DIR/instance directory. If the db2rfe command detects any root features enabled or any port numbers reserved and used by the database manager instance, a summary report shows the following information: The installed root features that have been or have not been enabled The service ports used by the instance that have been or have not been reserved in the system's services file.
DBI1162I	Usage:	You can configure non-root installations by using the db2nrcfg utility. Syntax: `db2nrcfg [-h\|-?] [-d] [-a AuthType] [-p PortName] [-s InstType]`	Call the db2nrcfg command, specifying valid parameters.
DBI1163I	An invalid argument was entered for the db2nrupdt command.	The syntax for the db2nrupdt command is: `db2nrupdt [-a AuthType] [-d] [-k ] [-j "TEXT_SEARCH" \| -j "TEXT_SEARCH,portnumber"] [-h\|-?]` For details about the parameters of the db2nrupdt command, refer to the documentation for Linux, UNIX, and Windows. This command must be run from the $HOME/sqllib/instance directory where the $HOME is the home directory of the non-root database manager instance ID. This command can be run only as the non-root instance who owns the non-root database product installation at $HOME/sqllib.	Enter the command again using valid parameters or run the command from the correct directory.
DBI1164E	A value is needed for `entry-name`.	To enable the remote connection, please provide a value for `entry-name` in the configuration file.
DBI1165E	Instance `instance-name` is not accessible on the following database partitions: `database-partitions-list`	Your db2nodes.cfg file is referring to nodes that cannot be accessed from this node. Furthermore, the remote node might also not be sharing the sqllib with this node. With DPF, all nodes must have the same sqllib mounted.	You must either fix your db2nodes.cfg file or ensure that the same sqllib is mounted on all nodes, or both.
DBI1166E	The version string for the file set contains invalid characters. Version string: `version`. File set: `fileset`.	The file name of the specified file set has been modified or corrupted.	Download the fix pack installation package again and re-run the command.
DBI1167I	An invalid argument was entered for the db2ckgpfs command.	The syntax for the db2ckgpfs command is: `db2ckgpfs [-d] [-l <logFile>] [-v install \| media] [-s install \| media] [-c] [-n <cluster-name>] [-h\|-?]`	Enter the command again using valid parameters.
DBI1168W	While attempting to create or update a 64-bit instance, it was detected that the installed level of bos.rte.libc is lower than the minimum requirement for 64-bit instances.	The installed level of bos.rte.libc is lower than 5.1.0.28, the minimum required level for supporting 64-bit instances.	Before proceeding, download APAR IY32466 and update your system. Information on downloading APARs is available from http://www.ibm.com/aix. You can reissue the command with a -F parameter to force execution past the point of warning.
DBI1169E	The DB2 HTML Documentation is not installed.	The DB2 HTML Documentation is not installed or it cannot be found. To update the DB2 HTML Documentation to this FixPak, the DB2 HTML Documentation must be installed.	Install the DB2 HTML Documentation and try the command again.
DBI1170I	An invalid argument was entered for the db2cktsa command.	The syntax for the db2cktsa command is: `db2cktsa [-d] [-l <logFile>] [-v install \| media] [-i install \| media] [-c] [-n <cluster-name>] [-h\|-?]`	Enter the command again using valid parameters.
DBI1171E	DB2 64-bit support is not installed.	64-bit instances are not supported or implicit on this platform.	For Linux IA64, reissue the command without the -w option to create a 64-bit instance. For other platforms, reissue the command without the -w 64 option to create a 32-bit instance.
DBI1172W	While attempting to create or update a 64-bit instance, it was detected that the installed level of one or both of bos.rte.libc and bos.adt.prof is lower than the minimum requirement for 64-bit instances.	The installed level of one or both of bos.rte.libc and bos.adt.prof is lower than 4.3.3.50, the minimum required level for supporting 64-bit instances.	Before proceeding, download one or both of the following PTFs and update your system. For bos.rte.libc, the PTF is U473728.bff For bos.adt.prof, the PTF is U473581.bff Information on downloading PTFs is available from http://www.ibm.com/aix. You can reissue the command with a -F parameter to force execution past the point of warning.
DBI1173W	db2iupdt has updated this instance to a 64-bit non-server instance.	You can only update a 32-bit Workgroup server instance to a 64-bit server instance if you have a database server installed.	If you do not wish to update to a server instance, you can continue to use the updated instance. If you wish to change this instance back to a 32-bit Workgroup server instance, run the following command: `db2iupdt -w 32 <instance-name>` If you wish to use a 64-bit server instance, install the database server and run the following command: `db2iupdt -w 64 <instance-name>`
DBI1174E	The GPFS version installed is too low. Installed version: `installed-version`. Media version: `media-version`.	The IBM General Parallel File System (GPFS) version level installed on your system is lower than the GPFS version level on the installation media. GPFS cannot be automatically upgraded. Also, the installGPFS command is not a supported command.	Manually remove the GPFS file system and cluster, uninstall GPFS, then install the fix pack with the installFixPack command.
DBI1175W	While attempting to create or update a 64-bit instance, it was detected that the installed level of the Solaris Operating Environment is lower than the minimum requirement for 64-bit.	The installed level of the Solaris Operating Environment is lower than 5.7, the minimum required level for supporting 64-bit instances.	Before proceeding, update your system to the minimum required level of the Solaris Operating Environment. You can reissue the command with a -F parameter to force execution past the point of warning.
DBI1176I	Usage: installAltFixPak [-h] [-s] [-y]	-h display the usage information -s install the exact same file sets/packages to the alternate path (for supported products) as those installed in /usr/opt/db2_08_01 or /opt/IBM/db2/V8.1. If installAltFixPak detects that the database product is not installed in /usr/opt/db2_08_01 or /opt/IBM/db2/V8.1, the -s option will not be used. In that case, it will call the db2_install utility. -y You have reviewed and accepted the license terms and conditions located in the db2/license directory for all the DB2 Version 8 products on your system. Please confirm that you have reviewed the license terms and conditions located in the db2/license directory for the installed products. If you accept these license terms and conditions, restart the FixPak installation and specify the '-y' option. By specifying the '-y' option, you indicate your agreement to the license terms and conditions provided with this product.
DBI1177W	Updating an instance to a code level that is lower than the current level used by the instance.	An attempt has been made to update an instance to a code level that is lower than the one being used by the instance currently.	To update an instance to a code level that is lower than the current level, issue the db2iupdt command with the -f level option as follows: `db2iupdt -f level <instance-name>`
DBI1178W	Updating a DAS to a code level that is lower than the current level used by the DAS.	An attempt has been made to update a DAS to a code level that is lower than the one being used by the DAS currently.	To update a DAS to a code level that is lower than the current level, issue the dasupdt command with the -D option as follows: dasupdt -D
DBI1179E	Client instances cannot be created using the db2icrt command when the PortName parameter is specified.	The PortName parameter is used for inbound TCP/IP connections and is not applicable to client instances.	Reissue the db2icrt command without specifying the PortName parameter.
DBI1180E	32-bit server instances are not supported.	The current platform does not support 32-bit server instances.	You cannot specify the bit size for the instance when you create or upgrade an instance. The bit size for new instances is determined by the operating system where DB2 database is installed.
DBI1181E	DB2 64-bit support is not installed.	64-bit instances are not supported on this platform.	Before proceeding, either update your system to the minimum required level to run 64-bit DB2, and reissue the command again, or drop the instance you are upgrading or updating, and re-create it as a 32-bit instance.
DBI1182W	Either DB2 Warehouse Manager, or DB2 Warehouse Manager Connectors, or both are not supported for upgrade in this release.	The instance you are trying to upgrade has Warehouse Manager or Warehouse Manager Connectors functionality. Warehouse Manager and Warehouse Manager Connectors are not supported in the product release to which you are trying to upgrade. A successful upgrade means that the upgraded instance will not have these capabilities. If this is the expected outcome, you can re-issue the db2iupgrade command.	Re-issue the db2iupgrade command to force the upgrade. Either the Warehouse Manager, or the Warehouse Manager Connectors, or both will not be available once the upgrade is completed.
DBI1183W	Spatial Extender not installed.	The instance you are upgrading has Spatial Extender functionality. Spatial Extender was not detected in the installed database product.	If the db2iupgrade command fails, reissue the command to force the upgrade. The instance will not have the Spatial Extender functionality . To re-enable Spatial Extender functionality in the instance, install Spatial Extender and issue the db2iupdt command to update the instance.
DBI1184W	Life Sciences Data Connect not installed.	The instance you are migrating has Life Sciences Data Connect functionality. Life Sciences Data Connect was not detected in the installed database product.	Rerun the db2iupgrade command to force migration. Life Sciences Data Connect will not be present. You must install Life Sciences Data Connect and manually run db2iupdt on the instance you are migrating in order to re-enable Life Sciences Data Connect functionality.
DBI1185I	Server protocol `protocol` is no longer supported. It has been removed from DB2COMM.
DBI1186I	Usage: db2cdbcr [-d] -n CDBName	An incorrect argument was entered for the db2cdbcr command. Valid arguments for this command are: -h\|-? display the usage information -d turn debug mode on. -n CDBName CDBName is the name of the Warehouse Control Database you want to create.	Enter the command again as follows: db2cdbcr -n CDBName
DBI1187E	Unable to complete DB2 Warehouse Control Database setup.	An attempt to create the DB2 Warehouse Control Database has failed.	A database partition groups (created on database partition 0) and a table space (both called FLG32K) needs to be created as well. See DB2 DataWarehouse documentation for details.
DBI1188E	Migration failed. The group `group-name` is not in the secondary group list of the DLFM user `user-name`.		Set the group `group-name` in the list of secondary groups for the DLFM user `user-name` and reissue the command.
DBI1189E	There has been an attempt to use db2_deinstall on an image for a platform that does not match the current platform `platform` on which it is being run.	Possible causes include: This database product install image is not valid for the current platform. The current platform is not supported by DB2	Install the database product using the install image that corresponds with the current platform `platform`
DBI1190I	db2setup is preparing the DB2 Setup wizard which will guide you through the program setup process. Please wait.
DBI1191I	db2setup is installing and configuring DB2 according to the response file provided. Please wait.
DBI1192I	The database product installation completed successfully. The install logs db2setup.log and db2setup.err are location in `location`.
DBI1193W	The database product installation completed with warnings. A minor error occurred while installing this computer. Some features may not function correctly. The install logs db2setup.log and db2setup.err are located in `location`.
DBI1194E	An error occurred while installing DB2 on this computer. The installation cannot continue. The install logs db2setup.log and db2setup.err are located in `location`.
DBI1195E	db2nrupdt failed to update user `user-name`.	The instance can not be updated because it is still active.	Make sure that the instance is stopped. Then rerun the command.
DBI1196E	The database product installer cannot detect the operating system on host `host-name`. System command used: `system-command`.	The database product installer cannot continue. Either the system command was run on an unsupported operating system, or, there is a problem with the specified system command.	Ensure you are running on a supported operating system. If you are running the specified command on a supported operating system, ensure the command is functioning correctly. Contact your system administrator.
DBI1197E	An error occurred acquiring the processor type information on host `host-name`. System command used: `system-command`.	The database product installer cannot continue. Either the system command was run on an unsupported processor type, or, there is a problem with the specified system command.	Ensure you are running on a supported processor type. If you are running the specified command on a supported operating system, ensure the command is functioning correctly. Contact your system administrator.
DBI1198E	An error occurred acquiring the Linux distribution on host `host-name`.	The database product installer could not determine the Linux distribution on the specified host. This can happen if there is a problem with the Linux release files.	Ensure that either the /etc/issue/release files, or the /etc/*release files, or both, are installed correctly.
DBI1199I	DB2IDROP completed successfully. The DB2INSTDEF registry variable was set to the dropped instance; it has been cleared. This registry variable should be explicitly set to another valid instance name.
DBI1200E	The directory `directory-name` is not a version `version-number` instance.	The command cannot proceed because the specified directory does not point to the required version of the database products.	The command cannot be run with the specified instance.
DBI1201E	The specified hosts are not running on the same type of operating systems. Host: `host-name1`. Operating system: `operating-system1`. Installation-initiating host: `host-name2`. Operating system: `operating_system2`.	All hosts in the same cluster must be running on the same type of operating system.	Ensure all hosts are created on the same operating system.
DBI1202E	Upgrading of instance `inst-name` is not supported.	The instance cannot be upgraded because: Upgrading from this version of the instance is not supported. The instance is already using the current version of the product and upgrade is not required.	The db2level command shows the current version and service level of the installed database product. The db2ls command lists where database products are installed on your system and list the database product level. Make sure that the instance is valid for upgrading and try the command again with a valid instance name.
DBI1203I	The DB2 High Availability (HA) scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) were successfully uninstalled.	You need DB2 HA scripts to use SA MP with the DB2 HA feature. These scripts have been removed.	No action is required.
DBI1204E	The keyword `keyword` has an invalid value. Sample configuration file name: `file_name`	The sample configuration file has examples of valid values for this keyword.	Correct the error and rerun the command.
DBI1205E	One or more local databases cannot be upgraded to the version from which you are running this command. Check the log file `logfile-name` for the list of errors.	The following list provides the reasons why a database cannot be upgraded and the corrective action to take: Database is in Backup pending state. Perform backup of the database. Database is in Roll-forward pending state. Perform a roll-forward database to end of logs and stop. Database is in Restore pending state. Perform restore of the database. Database is inconsistent. Restart database to return it to a consistent state. Database has one or more table space not in normal state. Perform a roll-forward database. Database contains database objects that have a schema name of SYSCAT, SYSFUN, SYSIBM, SYSPUBLIC, or SYSSTAT. Drop the object and re-create the object with a correct schema name (qualifier). If the object is a table you should first export its data, drop the table, re-create the table with a correct schema name, and then import or load the data to the new table. Database contains database objects that have a dependency on the SYSFUN.DIFFERENCES function. Possible violated objects and the associated action to correct the violation are: constraint - alter table to drop the constraint function - drop the function trigger - drop the trigger view - drop the view Database contains user-defined data types that are reserved in the new version. Rename the data types. Database contains orphan rows in system catalog tables. Contact IBM technical service representative. Cataloged database does not exist. Create cataloged database. Database does not allow successful connection as an HADR primary database. Stop HADR on primary database. A database has HADR standby role. Stop HADR on the standby database and drop the standby database. Upgrade the HADR primary database. Reinitialize the standby database from the copy of upgraded primary database via restore or db2inidb.	Determine the reason why the database cannot be upgraded and take the corresponding action specified in the explanation.
DBI1206E	Enablement of root feature `feature-name` failed. See log file `log-file-name` for details.
DBI1207E	Reserving the service for `feature-name` failed.	Can not reserve the service in the services file. Possible reasons are: The service name and port number are used in services file. The service name or port number are not valid values.	Correct the error and rerun the command.
DBI1208E	Reserving the service for `feature-name` failed.
DBI1209E	`keyword` is missing in the configuration file.	`keyword` is needed in the configuration file to enable the root feature `feature-name`.	Provide a valid value for `keyword` and rerun the command.
DBI1210E	Unknown system error.
DBI1211E	Upgrading of the `directory-name` failed.	A system error such as running out of disk space or memory has been encountered during the directory upgrade. Instance upgrade failed.	Make sure there is sufficient disk space and memory before you reissue this command again.
DBI1212W	Upgrade of the local database directory on `path` failed.	The upgrade process of the local database directory is not complete because of an unexpected error occurred. Without the local database directory, databases that are cataloged in the local database directory will no longer be accessible.	Perform one of the following actions: Remove the local database directory and re-catalog the databases. Keep the db2mgdbd.err error file and the sqldbdir/sqldddir.bak local database directory backup file that are created in the `path` directory and contact IBM service for instruction of possible ways to repair your directory.
DBI1213I	Root feature `feature-name` has been enabled successfully.
DBI1214I	Service for `feature-name` is succussfully reserved.
DBI1215I	Service for `feature-name` has been reserved successfully.
DBI1216E	Uninstalling the IBM Tivoli System Automation for Multiplatforms (SA MP) failed because the command uninstallSAM was not found in the expected directory: `directory`.	db2_deinstall uses the uninstallSAM utility to uninstall the SA MP. db2_deinstall expects to find the uninstallSAM utility in the specified directory, but did not find it there in this case. This might be because the current version of the SA MP is earlier than version 2.2. The option to uninstall the SA MP with the db2_deinstall command is only supported for SA MP Version 2.2 or higher. The SA MP was not uninstalled.	To uninstall the SA MP manually, use the uninstallSAM command. For more information about the uninstallSAM command, see the SA MP Base Component documentation.
DBI1217E	Valid installation identifier not detected.	All valid identifiers from the image have been removed. The installer cannot determine which valid product(s) are available on the image and cannot display the installation choices.	The product image has been modified and does not have a valid identifier for the installer to display the available options. Install using the original database product image.
DBI1218I	The license certificate `license-certificate-file-name` for the IBM Tivoli System Automation for Multiplatforms (SA MP) was successfully installed.	SA MP requires a valid license certificate to work with the DB2 High Availability (HA) feature. This license certificate was successfully installed or updated.	No response is required.
DBI1219E	The license certificate `license-certificate-file-name` for the IBM Tivoli System Automation for Multiplatforms (SA MP) was not successfully installed.	SA MP requires a valid license certificate to work with the DB2 High Availability (HA) feature. This license certificate was not successfully installed or updated. If you used the database product installer to install or update this license certificate, you can find more detailed information about why the install or update failed in the database product install log file.	To manually install or update this license certificate for the SA MP Base Component, issue the command: samlicm -i license-certificate-file-name For more information about the samlicm command, see the SA MP Base Component documentation.
DBI1220W	The upgrade of the node directory on `path` failed.	The process of upgrading a node directory did not complete because an unexpected error occurred.	Perform one of the following actions: Remove the node directory and re-catalog the node entries. Keep the db2ugndd.err error file and the sqlnodir/sqlnddir.bak node directory backup file that are created in the path directory and contact IBM service for instruction of possible ways to repair your directory.
DBI1221W	The node directory is corrupted and cannot be upgraded.	Either the node directory files are not the same or the node directory file is corrupted.	Remove node directory and re-catalog node entry.
DBI1222W	The system database directory is corrupted and cannot be upgraded.	Either the primary and backup system database directory files are not the same or system database directory is corrupted.	Remove system database directory and recatalog all database entries.
DBI1223W	The local database directory is corrupted and cannot be upgraded.	Either the primary and backup database directory files are not the same or the local database directory file is corrupted.	An error file db2mgdbd.err and a local database directory backup sqldbdir/sqldddir.bak are created in the indicated directory path. Keep these two files and contact IBM service for instruction of possible ways to repair your directory. Without the local database directory, databases that are cataloged in the local database directory will no longer be accessible.
DBI1224E	The target host is not running on the same processor type as the source host. Source host: `source-host`, processor type: `source-processor-type`. Target host: `target-host`, processor type: `target-processor-type`.	The source host and target host must run on the same processor type.	Ensure all hosts have the same processor type.
DBI1225W	The authentication type of one or more cataloged local databases have been changed.	One or more cataloged database entries were detected with an authentication type different than the authentication type for the instance that owns these databases. If no action is taken, all cataloged local database entries will inherit the authentication type from the instance.	Check the log file for the db2ckupgrade command for a list of the cataloged local database entries that do not have the same authentication type as the instance. If you want the database to maintain its previous authentication type, you can either change the authentication type of the instance, or, you can move the database to another instance that has the desired authentication type. However, before changing the authentication type of the instance, you should make sure that you want all the cataloged local database entries to have the new authentication type.
DBI1226E	The target host is not running on the same Linux distribution as the source host. Source host: `source-host`, distribution: `source-host-distribution`. Target host: `target-host`, distribution: `target-host-distribution`.	The hosts must be running on the same Linux distribution. The target host must have the same Linux distribution as the source host.	Ensure all hosts are created on the same Linux distribution.
DBI1227E	`product-name` is not a supported database product for non-root installation.
DBI1228E	The instance `inst-name` is not a server instance.	Some configuration tasks can be performed against database server instances only. Such configuration tasks include remote connection and DB2 text search.	If the specified instance is a client instance and a database server product is installed, run db2iupdt or db2nrupdt to update the client instance to a server instance. Then try the configuration task again.
DBI1229E	DB2 copy upgrade on Windows is not supported for the IBM Data Server Runtime Client, DB2 Thin Client, or IBM Data Server Driver Package installed at the location `installation-location`.	One of the following conditions is true: The selected DB2 copy for upgrade is an installation of previous releases of DB2 Run-Time, DB2 Run-Time Client Lite, DB2 Runtime Client, or Data Server Runtime Client. The database product being installed is IBM Data Server Runtime or IBM Data Server Driver Package. The DB2 copy upgrade is not supported from previous releases of DB2 Run-Time, DB2 Run-Time Client Lite, DB2 Runtime Client, or Data Server Runtime Client. Also, DB2 copy upgrade is not supported to IBM Data Server Runtime or IBM Data Server Driver Package.	Choose "Install New" to install the IBM Data Server Runtime Client, or IBM Data Server Driver Package in a new location. For IBM Data Server Runtime Client, upgrade the existing client instances to the new DB2 copy with the db2iupgrade command.
DBI1230E	DB2 copy upgrade is not supported for the selected DB2 copy installed at `installation-location`.	DB2 copy upgrade is not supported for the selected DB2 copy due to one or both of the following reasons: One or more database manager instances have an instance type that is not supported by the database product that you want to install. On Windows operating systems, upgrading to an instance type of a lower level is not supported. The DB2 DAS is related to the installation location from which the DB2 copy upgrade was requested, but the database product to be installed does not support the DB2 DAS.	Choose the database product which supports all the instances or DAS related to the DB2 copy to be upgraded.
DBI1231E	Upgrading a database manager instance is not supported for the instance `instance-name`. (The original instance type is `original-instance-type`. The instance type to be upgraded is `upgraded-instance-type`.)	The specified database manager instance cannot be upgraded to the current DB2 copy. On Windows operating systems, upgrading to an instance type of a lower level is not supported.	Install the database product which supports the instance type and rerun the db2iupgrade command.
DBI1232E	Cannot continue with the uninstallation.	Possible reasons: The database manager for the instance `inst-name` is still active. The DB2 Text Search instance service is still active.	Stop the database manager and the DB2 Text Search instance service then rerun the command.
DBI1233E	Instance `inst-name` cannot be dropped.	An instance cannot be dropped if the DB2 Text Search instance service is active.	Stop the DB2 Text Search instance service then rerun the command.
DBI1234E	The database manager instance update is not supported for the instance `instance-name`. (The original instance type is `original-instance-type`. The instance type to be updated is `updated-instance-type`.)	The specified database manager instance cannot be updated. Downgrading the instance type is not supported.	Install the database product which supports the instance type and rerun the db2iupdt command.
DBI1235E	Only one product can be installed at a time.	The database product installer only supports the installation of one product at a time.	Specify only one product and rerun the command.
DBI1236E	The multi-partition instance `instance-name` cannot be upgraded or updated to a non multi-partition instance.	The instance being upgraded or updated is a multi-partition instance. The current DB2 copy to which the instance is being upgraded to or updated does not support multi-partition instances.	If the database manager instance does not have any partitioned local databases and you want to use non multi-partition instance, update the current db2nodes.cfg to include only one partition and rerun the command. If a partitioned local database with a instance exists, you should upgrade or update it to a DB2 copy that supports multi-partition instances. DB2 Enterprise Server Edition supports multi-partition instances.
DBI1237E	The specified components cannot be uninstalled because the database manager has not been stopped on all the instances related to the current installation. Specified components: `component-name`.	The database manager has to be stopped on all the instances related to the current installation before the specified components can be dropped.	Stop the database manager on all of the instances related to the current installation and then rerun the command.
DBI1238E	The db2cluster_prepare command failed because the following invalid parameter was specified: `invalid-parameter`.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. This message is returned when the db2cluster_prepare command is called with an invalid parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying only valid parameters.
DBI1239I	The DB2 Information Center is listening for requests on port `port-number`
DBI1240E	The database manager could not be started.	The database manager could not be started when attempting to check if cataloged local databases can be upgraded.	Resolve why the database manager could not be started and try the command again.
DBI1241I	The Information Center daemon is already active.	The command to start the DB2 Information Center is already processed. The command cannot be processed.	The application is already listening.
DBI1242I	The STOP command to stop the DB2 Information Center completed successfully.
DBI1243I	The START command to start the DB2 Information Center completed successfully.
DBI1244I	Directory for non-root installation of DB2 - `directory`
DBI1245E	One or more space characters were found in the specified database product installation path `install-path`, which is not supported.	The specified installation path of DB2 contains one or more space characters, which is not supported for database product installation on the Unix and Linux platforms.	Specify an installation path without space characters and rerun the command.
DBI1246I	The db2_deinstall command can only be run from a database product installation directory.	Starting from DB2 9, the db2_deinstall command can only be run from a database product installation path. It can be found under DB2DIR/install, where DB2DIR represents the directory where the database product is installed.	Reenter the command from DB2DIR/install directory.
DBI1247W	Root feature `feature-name` can not be enabled because the feature does not exist in the current installation.
DBI1248E	You can only use this version of the db2_deinstall command to uninstall a DB2 version `version` product.	To uninstall a database product, you must use the db2_deinstall command that is at the same version level.	Find the appropriate DB2 media and rerun the command or run the db2_deinstall command from the <DB2DIR>/install directory, where <DB2DIR> represents the installation path of the database product you want to remove.
DBI1249E	You can only use this version of the doce_deinstall command to uninstall the DB2 Information Center version `version`.	To uninstall the DB2 Information Center, you must use the doce_deinstall command that is at the same version level.	Find the appropriate DB2 Information Center media and rerun the command or run the doce_deinstall command from the <DB2DIR>/install directory, where <DB2DIR> represents the installation path of the DB2 Information Center you want to remove.