This chapter contains the error messages which may be generated during installation and configuration of DB2 products.
db2icrt [-a AuthType]
[-p PortName]
[-s InstType] -u FencedID InstName
Cause: An invalid argument was entered for the db2icrt command. Valid arguments for this command are:
Action: For more information about this command, please refer to the manual "Quick Beginnings for UNIX". Enter the command again as follows:
db2icrt [-a AuthType] -u FencedID InstName
dlfmcrt [-p PortName] DLFMAdmin
Cause: An invalid argument was entered for the dlfmcrt command. Valid arguments for this command are:
Action: Enter the command again as follows:
dlfmcrt DLFMAdmin
db2idrop InstName
Cause: An incorrect argument was entered for the db2idrop command. Valid arguments for this command are:
Action: Enter the command again as follows:
db2idrop InstName
db2idrop [-f] InstName
Cause: An incorrect argument was entered for the db2idrop command. Valid arguments for this command are:
Action: Enter the command again as follows:
db2idrop [-f] InstName
dlfmdrop DLFMAdmin
Cause: An invalid argument was entered for the dlfmdrop command. Valid arguments for this command are:
Action: Enter the command again as follows:
dlfmdrop DLFMAdmin
db2iupdt [-h|-?] [-d] [-k] [-s]
[-a AuthType] [-u FencedID] InstName
Cause: An incorrect argument was entered for the db2iupdt command. Valid arguments for this command are:
Action: Enter the command again with the proper options and arguments.
db2iupdt [-f] -u FencedID InstName
Cause: An incorrect argument was entered for the db2iupdt command. Valid arguments for this command are:
Action: Enter the command again as follows:
db2iupdt [-f] -u FencedID InstName
dlfmupdt [-h|-?] DLFMAdmin
Cause: An invalid argument was entered for the dlfmupdt command. Valid arguments for this command are:
Action: Enter the command again as follows:
dlfmupdt [-h|-?] DLFMAdmin
db2imigr [-a AuthType] -u FencedID InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: For more information about this command, please refer to the manual "Quick Beginnings for UNIX". Enter the command again as follows:
db2imigr [-a AuthType] -u FencedID InstName
db2imigr [-f] [-a AuthType] -u FencedID InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: For more information about this command, please refer to the manual "Quick Beginnings for UNIX". Enter the command again as follows:
db2imigr [-f] [-a AuthType]
-u FencedID InstName
db2istop [-h|-?] [-d] [-f] InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: Enter the command again as follows:
db2istop [-h|-?] [-d] [-f] InstName
db2setup [-h|-?] [-d] [-r RespFile]
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: Enter the command again as follows:
db2setup [-h|-?] [-d] [-r RespFile]
db2imigrev [-h|-?] InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: Enter the command again as follows:
db2imigrev [-h|-?] InstName
db2imigrev [-h|-?] [-f] InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: Enter the command again as follows:
db2imigrev [-h|-?] [-f] InstName
db2iauto [-h|-?] -on|-off InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
Action: Enter the command again as follows:
db2iauto [-h|-?] -on|-off InstName
dasicrt DASName
Cause: An invalid argument was entered for the dasicrt command. Valid arguments for this command are:
Action: Enter the command again as follows:
dasicrt DASName
dasidrop DASName
Cause: An invalid argument was entered for the dasidrop command. Valid arguments for this command are:
Action: Enter the command again as follows:
dasidrop DASName
dasiupdt [-h|-?] DASName
Cause: An invalid argument was entered for the dasiupdt command. Valid arguments for this command are:
Action: Enter the command again as follows:
dasiupdt [-h|-?] DASName
Cause: DB2 requires certain kernel parameters to be updated.
Action:
Action: 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/lpp/db2_05_00 on AIX
and /opt/IBMdb2/V5.0 on Solaris, HP-UX.
Cause: Your current operating system is not supported or this version of the operating system is not supported. Refer to the "Quick Beginnings for UNIX".
Cause: This program can only be run under a non-root user ID.
Action: Login as an user ID other than root, and issue the command again.
Cause: This program can only be run under the root user ID. Special privileges are required to execute this program.
Action: Login as root and issue the command again.
Cause: 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 filesystem.
Action: Change the home directory to a supported file system and recreate the instance.
Cause: 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.
Action: Verify that the product option containing the message file is installed correctly. If there are verification errors, reinstall the product option.
Cause: The required locale directory, /usr/lib/locale/LANG/LC_MESSAGES, does not exist, where LANG is the name of your current locale.
Action: Verify that the specified locale has been installed correctly. Also check for the read and execute permissions are set correctly on that directory.
Cause: An incorrect name has been entered. The package either does not exist or the name has been entered incorrectly.
Action: 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. All package names should be in lower case.
Cause: An error occurred when verifying software pre-requisites. The above fileset or package must be installed before using this command.
Action: Check to see if the name of the given package has been installed on your system.
Cause: The above fileset or package must be installed before using this command.
Action: Install the fileset or package and then reissue this command.
Cause: The above PTF or patch must be installed before using this command. This PTF or patch is required to complete this command successfully.
Action: Install the required PTF or patch and and enter this command again.
Cause: An error has occurred during the execution and that has caused this program to terminate prematurely.
Action: Correct the problem and try the command again.
Cause: This program has been terminated by the user.
Action: Issue the same command to restart the program.
Cause: No compressed-tar HTML files can be found in the DB2DIR/doc/"<locale-name>"/html directory, where
DB2DIR = /usr/lpp/db2_05_00 on AIX
= /opt/IBMdb2/V5.0 on HP-UX,
Solaris,
SCO UnixWare
Action: Install the DB2 Product Library for the required locale and issue this command again.
Cause: After uncompress and un-tar, all the HTML files cannot be saved in the above directory because the filesystem is full.
Action: Increase the size of the filesystem or free up sufficient disk space in the filesystem. Issue the command again.
Cause: An unexpected error occurred during the execution of this program.
Action: If the problem persists, contact IBM Support with the following information:
Cause: db2licinst failed to add the license to the nodelock file, so DB2 will run with a Try-and-Buy license until a product license is installed.
Action: Try the command again and if it continues to fail, manually add the license key to the nodelock file. Refer to the Quick Beginnings guide for more information on licensing.
Cause: All processed and failed operations have been saved into this log file.
Action: Do not modify this file in any way. This file is for IBM Technical Support reference.
Cause: There is not enough free space available in the file system or directory.
Action: Free more disk space and retry the command.
Cause: A file or directory that is required to process this command is missing.
Action: 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.
Cause: A file or directory that the command needs to create already exists.
Action: Examine the specified file or directory. If the file or directory exists as a result of a previous successful completion of the command then no action is required. Otherwise, you will need to either rename or remove the specified file or directory before trying the command again.
Cause: An error occurred when removing the given file or directory. This may be due to an inappropriate ownership on this given file or directory.
Action: Adjust the file permissions or ownership of the specified file or directory and then issue the command again.
Cause: An error occurred when creating the given file or directory.
Action: 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.
Cause: An error occurred when attempting to relocate the given file or directory. The command could not be processed successfully.
Action: Determine why the specified file or directory could not be moved and then try the command again.
Cause: An error occurred when attempting to duplicate the given file or directory. The command could not be processed successfully.
Action: Determine why the specified file or directory could not be copied and then try the command again.
Cause: 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.
Action: Check permissions for the parent directory and restart the install process. Suggested directory permissions are u=rwx,go=rx.
Cause: There may be several reasons for this error. It is likely that one of the following situations has occurred:
Action: Check permissions for the given directory and restart the install process. Suggested directory permissions are u=rwx,go=rx.
Cause: There may be several reasons for this error. It is likely that one of the following situations has occurred:
Action: Take an appropriate corrective action and issue the command again.
Cause: An error occurred while updating the given file.
Action: Verify that all occurances of "<parameter>" are set to "<value>" in "<file-name>".
Cause: 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.
Action: Check permissions and ownership for the given directory and restart the install process. Suggested directory permissions are u=rwx,go=rx.
Cause: 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.
Action: Check ownership for the given directory and restart the install process.
Cause: 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.
Action: Check ownership for the given directory and restart the install process.
Cause: The command failed because another instance management command (eg. db2icrt, db2idrop, db2iupdt, or db2imigr) is running. The instance management commands acquire an exclusive lock to avoid conflicting simultaneous commands against the same instance.
Action: 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:
/var/db2/v5
or /var/opt/db2/v5
Cause: Instance name must be the login name of an existing user and cannot:
Action: Try the command again with a valid instance name.
Cause: The system detects that the Administration Server has already been created on your system. You can only create one Administration Server on each system.
Action: If you want to re-create the Administration Server, you have to drop the Administration Server first before re-creating it.
Cause: An attempt to drop the Administration Server failed. The system detects that the Administration Server does not exist or has been created under a different user ID.
Action: Verify that the name of the Administration Server as reported by the "dasilist" command is correct and try again.
Cause: The system detects that the DB2 File Manager Administrator has already been created on your system. You can only create one DB2 File Manager Administrator on each system.
Action: If you want to re-create the DB2 File Manager Administrator, you have to drop the DB2 File Manager Administrator first before re-creating it.
Cause: An attempt to drop the DB2 File Manager Administrator failed. The system detects that the DB2 File Manager Administrator does not exist or has been created under a different user ID.
Action: Verify that the name of the DB2 File Manager Administrator as reported by the "dlfmlist" command is correct and try again.
Cause: Some of the kernel parameters are not configured properly.
Action:
Cause: 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.
Action: 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.
Cause: The FencedID parameter which specifies the user name under which fenced User Defined Functions and fenced Stored Procedures will be run:
Action: Try the command again with a valid FencedID parameter.
Cause: 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.
Cause: The AuthType parameter which specifies the authentication type used for the instance is not valid. Valid authentication types are:
Action: Try the command again with a valid AuthType parameter.
Cause: An attempt was made to drop an instance which may still be active.
Cause: 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.
Action: Use the "dasidrop" command to remove the Administration Server.
Cause: An attempt was made to update an instance. This instance cannot be updated because:
Action: Ensure that you are using the correct version of the "db2iupdt" command. Also ensure that there are no db2 processes running at the instance. Retry the command.
Cause: 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.
Action: Use the "dasiupdt" command to update the Administration Server.
Cause: An attempt was made to migrate an instance. This instance cannot be migrated because:
Action: Ensure that instance is ready for migration and you are using the correct version of the "db2imigr" command. For more information on instance migration, please refer to the book "Quick Beginnings for UNIX".
Cause: An attempt was made to drop the DB2 File Manager Administrator using "db2idrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.
Action: Use the "dlfmdrop" command to remove the DB2 File Manager Administrator.
Cause: 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.
Action: Use the "dasidrop" command to remove the Administration Server.
Cause: 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.
Action: Use the "dasiupdt" command to update the Administration Server.
Cause: An attempt to access the given user ID failed. One of the following situations has occurred:
Action: 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.
Cause: The primary group name of the instance user ID cannot:
Action: Change the primary group of the instance user ID to a group with a valid name and then try the command again.
Cause: An existing Sync Point Manager (SPM) log directory was found. This new version of the SPM cannot process the old version of the log. You must verify that there are no indoubt transactions prior to using this new version of the SPM.
Action:
Cause: The command cannot proceed because the specified directory does not point to the required version of the database products.
Action: The command cannot be run with the specified instance.
Cause: The instance cannot be migrated because:
Action: Make sure that the instance is valid for migration and then try the command again with a valid instance name.
Cause: Possible errors on the database are:
Action: Take the following corrective action for each database from the file "<logfile-name>" :
Cause: A system error such as running out of disk space or memory has been encountered during the migration of the directory. Instance migration failed.
Action: Make sure there is sufficient disk space and memory before trying the command again.
Cause: The process of migrating local database directory is not complete because of an unexpected error occurred.
Action: An error file "db2mgdbd.err" and a local database directory backup "sqldbdir/sqldddir.bak" are created in the directory path mentioned above.
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 catalogued in the local database directory will no longer be accessible.
Cause: The process of migrating node directory is not complete because of an unexpected error occurred.
Action: Two options to recover:
Keep these two files and contact IBM service for instruction of possible ways to repair your directory. Contact IBM services to recover your node directory.
Cause: Either the node directory files are not the same or the node directory file is corrupted.
Action: Remove node directry and re-catalog node entry.
Cause: Either the primary and backup system database directory files are not the same or system database directory is corrupted.
Action: Remove system database directry and re-catalog all database entry.
Cause: Either the primary and backup database directory files are not the same or the local database directory file is corrupted.
Action: An error file "db2mgdbd.err" and a local database directory backup "sqldbdir/sqldddir.bak" are created in the directory path mentioned above.
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 catalogued in the local database directory will no longer be accessible.
Cause: One or more catalogued database entries were detected that have an authentication type that is different from the authentication type that was specified for the instance. If no action is taken then all catalogued local database entries will assume the authentication type of the instance they belong to.
Action: Check the file migration.log in the home directory of the instance for a list of the catalogued local database entries that are not the same as the authentication specified for the instance. If you want the database to maintain it's previous authentication type then 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. Before changing the authentication type of the instance, however, you should make sure that you want all the catalogued local database entries to have the new authentication type.
Cause: The database manager could not be started when attempting to check if catalogued local databases can be migrated.
Action: Resolve why the database manager could not be started and then try the command again.
Cause: There are applications that are still running that are using the specified instance. All applications using this instance must be terminated before the command can be completed successfully. You can get a list of the applications that are currently using the instance by issuing the command:
db2 list applications
Action: You can either wait for the applications to end by themselves, or you can explicitly force the applications to end. You can logon as the instance owner and run the command
db2 force application all
Note that some applications may have unexpected behaviour when terminated using the above command. After all the applications have stopped, stop the database manager using "db2istop" command.
Cause: An attempt was made to read from the given response file failed. Ensure that the response file has read access permission and the given path to the response file is correct.
Action: Correct the access permission and the location of the response file and try again.
Cause: The value specified in the response file is not valid for its corresponding keyword. Refer to the sample response file for a list of valid entries.
Action: Correct the problem in the following line of the response file and try again.
Cause: The given keyword in the response file is not valid. Refer to the sample response file for a list of valid keywords.
Action: Correct the problem in the following line of the response file and try again.
Cause: All processed and failed operations have been saved into this log file.
Action: Do not modify this file in any way. This file is for IBM Technical Support reference.
Cause: All processed and failed operations have been saved into this log file.
Action: Do not modify this file in any way. This file is for IBM Technical Support reference.
Cause: One of the filesets to be installed is not found on the installation media. If the fileset is not located on the installation media then it cannot be installed.
Action: Ensure that the fileset is located on the installation media. If the fileset is not located on the installation media de-select it and try again.
Cause: An error has been detected when processing the response file. Install cannot be continued unless the problem has been corrected.
Action: Correct the problem in the following line of the response file and try again.
Cause: A warning has been raised when processing the response file. DB2 Installer will carry on without stopping.
Action: If required, correct the problem in the following line of the response file and try again.
Cause: A notice has been issued when processing the response file. DB2 Installer will carry on without stopping.
Action: This is for your information only. No action is required.
Cause: An error occurred when attempting to initialize the database manager configuration file. A DB2 Version 5 instance could not be created or migrated.
Action: Refer to the log file for problem determination. Resolve the problem and try the command again. If the problem persists, please contact IBM Support.
Cause: An error was detected when attempting to merge two database manager configuration files. The previous database manager configuration file could not be merged with the new database manager configuration file.
Action: Check the values in the new database manager configuration file and update the parameters as required.
Cause: The SVCENAME parameter and/or the DB2COMM registry values could not be updated during instance creation.
Action: Make sure that the SVCENAME parameter is set to "<profile-name>" in the database manager configuration file and update using
db2 update dbm cfg using SVCENAME "<profile-name>"Also update the DB2COMM variable to tcpip by running
db2set DB2COMM=tcpip
Cause: An error occurred when creating the profile registry. One of the following situations occurred:
Action: Check the file permissions on the instance list profile in one of the following directories:
/var/db2/v5
or /var/opt/db2/v5
Cause: The specified instance was not found in the instance list.
Action: Verify that the list of instances as reported by the "db2ilist" command is correct. Retry the command with a valid instance name.
Cause: The instance that is being created or migrated is already in the instance list.
Action: Use a different instance name that is not part of the instance list as reported by the "db2iset -l" command.
Cause: The instance could not be added to or removed from the instance list. An error has occurred when adding or removing the instance from the instance list. One of the following situations occurred:
Action: Check the file permissions on the instance list profile in one of the following directories:
/var/db2/v5
or /var/opt/db2/v5
Cause: An error occurred when updating the instance profile registry. One of the following situations occurred:
Action: Check the file permissions on the instance list profile in one of the following directories:
/var/db2/v5
or /var/opt/db2/v5
db2set [[[variable=[value]]
[-g|-i instance[node-number]]]
[-all] [-null]
[-r instance[node-number]]
[-n DAS node[-u user[-p password]]]
[-l|-lr] [-v] [-?|-h]
Cause: The command options are:
Notes:
Cause: An invalid parameter was used.
Action: Use the -? option for the usage help message.
Cause: The variable was not set in the profile registry.
Action: No further action is required.
Cause: The tool encountered an unexpected system error.
Action: Contact your DB2 service representative.
Cause: The target machine does not have a profile registry setup.
Action: Create the registry on the target machine by installing DB2.
Cause: The instance is not defined in the target machine registry.
Action: Specify an existing instance name or create the required instance.
Cause: The instance node is not defined in the target machine registry.
Action: Create the registry by installing the required DB2 product parts.
Cause: The tool encountered an "out of memory resource" error.
Action: System is low on memory resources. Terminate non-essential applications or try again later.
Cause: The tool encountered an operating system error.
Action: A system error was encountered during registry access. Ensure that there is enough space on the file system where the registry is located, and that there is a valid LAN connection if the registry is remote.
Cause: The tool does not support the remote registry option.
Action: Consult the Command Reference on how to access the registry remotely.
Cause: The target instance is not a DB2 MPP instance.
Action: Choose an MPP instance.
Cause: A duplicate instance node already exists.
Action: Choose a different instance node.
db2inst [-f <response-file>]
Cause: An incorrect argument was entered. The command accepts an optional flag -f which is followed by the path of the "DB2 Installer" response file.
Action: Re-enter the command with a valid argument.
Cause: An error was detected while performing an internal operation.
Action: Verify that the file system on which the file resides is not damaged. If the problem persists, contact IBM Support with the following information:
Cause: An error was encountered when opening or reading from a file. One of the following errors occurred:
Action: If the file was modified by the user, verify that the data in the file is valid. If the file was not modified by the user, contact IBM Support with the following information:
Cause: An error was encountered when writing data to a file. One of the following errors occurred:
Action: Check to see if the permissions on the file's parent directory have been set correctly. If the problem persists, contact IBM Support with the following information:
Cause: An attempt to open and read from "DB2 Installer" message catalog files failed. Before DB2 Installer starts up, it looks for two resource files -- db2inst.rcx and db2inst.cat in the following locations:
Action: Set the environment variables DB2IRCX and DB2ICAT to the absolute location of db2inst.rcx and db2inst.cat respectively.
Cause: An error was detected when attempting to allocate memory.
Action: Terminate other applications running on the system that may be using large amounts of memory. If the problem persists, contact IBM Support with the following information:
Cause: An error was detected when attempting to start up the DB2 Installer. Another instance of the DB2 Installer is still running.
Action: Terminate all instances of the DB2 Installer and restart the install process. If the problem persists, remove the lock file /tmp/.db2inst.lck and restart the DB2 Installer.
Cause: An error was detected when attempting to startup a subprocess.
Action: Terminate other applications running on the system that may be using large amounts of resources. If the problem persists, contact IBM Support with the following information:
Cause: An error was detected when attempting to terminate a subprocess.
Action: Terminate other applications running on the system that may be using large amounts of resources. If the problem persists, contact IBM Support with the following information:
Cause: An error was detected when attempting to execute a command in a subprocess. One of the following problems occurred:
Action: Correct the problem and try again. If the problem persists, contact IBM Support with the following information:
Cause: Your current terminal or window size is not large enough. This program requires a minimum terminal display size of 24 lines by 80 columns.
Action: Check your terminal or window size and try again.
Cause: An error was detected when attempting to initialize your terminal display. There are two conditions where this type of error would occur:
Action: Set your environment variable TERM to a correct terminal type. If the problem persists, try to terminate other applications running on the system that may be using large amounts of memory. If the problem still occurs, contact IBM Support with the following information:
Cause: An error was detected when attempting to restore your terminal display to the original state.
Action: Set your environment variable TERM to a correct terminal type. If the problem persists, try to terminate other applications running on the system that may be using large amounts of memory. If the problem still occurs, contact IBM Support with the following information:
Cause: An error has occurred while unpacking the tar image from the distribution media. One of the following situations has occurred:
Action: Restart the install process and retry with a correct path name.
Cause: An error was detected when attempting to locate the installable images on the distribution media. One of the following errors occurred:
Action: Check the path and try the command again. Note that all file and directory names in Unix are case sensitive.
Cause: An error was detected when attempting to open or read from the status file. If the status file has not been modified manually, then one of the following errors occurred:
Action: Check the path and try the command again. Note that all file and directory names in Unix are case sensitive. If the problem persists, contact IBM Support with the following information:
Cause: An error was encountered when trying to allocate more disk space on the file system.
Action: Retry the command after enough space has been freed up for the specified operation.
Cause: One of the following situations has occurred:
Action: If this is not a disk space problem, try to re-install the product. If the problem persists, turn trace on and retry the steps to create a database through the CLP. Then, save the trace information to a file and contact IBM Support with the following information:
Cause: One of the following situations has occurred:
Action: If any of the above three situations apply, then correct the problem and retry the command. If the problem persists, contact IBM Support with the following information:
Cause: One of the following situations has occurred:
Action: If any of the above three situations apply, then correct the problem and retry the command. If the problem persists, contact IBM Support with the following information:
Cause: An error was detected when attempting to add a DB2 instance to the Administration Server group list.
Action: If you are running this command on an NIS client, try to append the group name of the DB2 instance to the secondary group of the Adminstration Server on your NIS server.
Cause: An invalid UID has been entered. One of the following situations has occurred:
Action: Retry with a different user ID.
Cause: An invalid user name has been entered. One of the following situations has occurred:
Action: Retry with a different user name.
Cause: An invalid group ID or group name has been entered. One of the following situations has occurred:
Action: Retry with a different group ID or group name.
Cause: An invalid directory has been entered. One of the following situations has occurred:
Action: Retry with the user's home directory specified on the system or a different directory.
Cause: An invalid password has been entered. One of the following situations has occurred:
Action: Retry with a different password.
Cause: An instance with the same name already exists on your system.
Action: Verify with the list of instances as reported by the "db2ilist" command. Retry with a different user name.
Cause: One of the following situations has occurred:
Action: Correct the problem and try again.
Cause: The service name or port number entered by the user conflicts with existing values in the TCP/IP services file. The service name may already be used with a different port number, or the port number may already be used with a different service name.
Action: Specify a service name and port number that does not conflict with existing entries in the services file.
Cause: No valid service name or port number for this instance can be found in the TCP/IP services file. This information is either missing or is invalid.
If you installed "DB2 Extended Enterprise Edition" product, a service name must be specified for the instance before using this command.
Action: For more information, refer to the "DB2 Extended Enterprise Edition for AIX Quick Beginnings". Specify valid service name and port number for this instance and enter this command again.
Cause: An attempt to add a service name and port number to the TCP/IP services file failed.
Action: If the user wishes to use the service name instead of the port number in the node directory entry, the node must be manually uncatalogued and then recatalogued using the service name. The services file must also be updated manually. If Network Information Services (NIS) is being used, the local services file may have been updated but the NIS server must be updated manually. In this case, the node was also catalogued using the port number.
Cause: One of the following situations has occurred:
Action: Correct the problem and try again.
Cause: The NetWare User ID and NetWare Password that you specify must already exist and is used to register the DB2 Object Name at a NetWare file server and must have supervisory or equivalent authority.
Action: Correct the problem and try again.
Cause: NIS is running on your system. A new User ID or Group ID cannot be created while you have NIS running on your system.
Action: Use a previously created User ID or Group ID and try again.
Cause: NIS is running on your system. A new service cannot be added to the /etc/services file while you have NIS running on your system.
Action: Use a previously created service name and port number from the /etc/services file and try again.
Cause: Using the default instance user ID here allows this instance to have full access permission to other instances on your system. It is highly recommended to use a different user ID for security reasons.
Action: To avoid the possibility of a security risk, use a different user ID.
Cause: You have selected a protocol that is not detected. DB2 Installer cannot update all of the protocol's required settings. However, you can provide values for this protocol's settings.
Action: No actions required.
Cause: You have not created the DB2 File Manager Administrator. Without the DB2 File Manager Administrator, you cannot administer the DB2 File Manager.
Action: No actions required.
Cause: You have not created a Administration Server. Without the Administration Server, you cannot provide services to support client tools that automate the configuration of connections to DB2 databases, and cannot administer DB2 from your server system or a remote client using the Control Center.
Action: No actions required.
Cause: You have not created a DB2 Instance. A DB2 Instance is an environment where you store data and run applications.
Action: No actions required.
Cause: The directory specified in the Home Directory field already exists. If you choose to use this directory you may run into permission problems.
Action: Choose a different directory if this may be a problem.
Cause: Using the default instance user ID here allows this instance to have full access permission to other instances on your system. It is highly recommended to use a different user ID for security reasons.
Action:
Cause: You have selected a protocol that is not detected. DB2 Installer cannot update all of the protocol's required settings. However, you can provide values for this protocol's settings.
Action:
Cause: You have not created the DB2 File Manager Administrator. Without the DB2 File Manager Administrator, you cannot administer the DB2 File Manager.
Action:
Cause: You have not created a Administration Server. Without the Administration Server, you cannot provide services to support client tools that automate the configuration of connections to DB2 databases, and cannot administer DB2 from your server system or a remote client using the Control Center.
Action:
Cause: You have not created a DB2 Instance. A DB2 Instance is an environment where you store data and run applications.
Action:
Cause: The directory specified in the Home Directory field already exists. If you choose to use this directory you may run into permission problems.
Action:
Cause: You have selected to removed the entire DB2 product. However, a DB2 Instance or Administration Server has been detected on your system. If you remove the DB2 product without dropping these instances first, your DB2 Instances may not be able to function properly later on.
Action:
Cause: You do not have the Administration Server selected. This will cause all of your Administration Server and DB2 Instance configurations to be discarded.
Action:
Cause: An error occurred when verifying software pre-requisites on the above fileset or package. Continuing may result in the product not functioning properly. Do you want to continue without installing its pre-requisites?
Action:
Cause: An error occurred when verifying software dependencies on the above fileset or package. Continuing may result in removing all of its software dependencies. Do you want to remove its software dependencies?
Action:
Cause: The English HTML documentation files are required when you select any non-English HTML documentation files for installation. This is to ensure that users will be able to search the entire DB2 documentation library.
Cause: The registry is containing a non-existing user ID. This can be caused by just removing the instance user ID without first dropping the instance. This will not affect the normal operation of DB2, but it is recommended to remove this obsolete user ID from the instance list in the registry.
Action: To remove this user ID from the registry with the command: db2iset -d "<InstName>"
Cause: A code, "<code>", is returned when attempting to change the secondary group list of the given user ID. One of the following situations has occurred:
Action: You must add the group ID, "<groupId>", to the secondary group list of the user ID, "<userId>", so that the Adminstration Server can function properly.
Cause: The registry may contain invalid instance information. This is probably due to the fact that an instance or the Administration Server is not deleted properly before removing the DB2 product. If you are re-installing the product and want to keep the existing instance information in the registry, press Cancel. Otherwise, press OK to re-create the registry. Do you want to re-create the registry?
Action:
Cause: DB2 has failed to modify the .profile file or the .login file of this user. These files may not exist, or you may not have write permission to them. Without the modification you need to set your environment manually each time when you log in as this user to use DB2.
Action: Add the following line to the .profile file or the .login file:
. sqllib/profile to the .profile file, or source sqllib/db2cshrc to the .login file
See the Quick Beginning Guide for more details on how to set the DB2 environment automatically.
Cause: DB2 has failed to comment out the DB2 environment setting line in the .profile file or the .login file of this user. The next time you log in as this user, you may get a message saying that the file db2profile (or db2cshrc) cannot be found. There can be different reasons:
Action: If you receive a message concerning missing db2profile or db2chsrc, locate your .profile or .login file and comment out the following:
. sqllib/db2profile from your .profile file source sqllib/db2cshrc from your .login file
Cause: The following DB2 File Manager specific entry is required in the /etc/vfs file:
dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none
where dlfs_num is to be set to 12, or some number between 8 and 15 if 12 is already assigned to another fs. The installation process has failed to insert this line into the /etc/vfs file. There may be different reasons:
Action: Manually edit the /etc/vfs file, and add the entry for dlfs into this file.
Cause: For DB2 File Manager to work, the following line has to be inserted into the /etc/vfs file:
dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none
A backup copy of the original /etc/vfs file has been placed in /tmp/.db2.etcvfs.backup.
Cause: The version of your current operating system is not supported to run DB2 File Manager. However, you can still install and configure the product at your own risk. The following is a list of supported operating systems for DB2 File Manager:
Cause: ODSSI utilities have not been installed. These utilities (config_search, config_view and config_help) are required to create the search index for the DB2 online documentation.
Action: Install the ODSSI utilities, then run the following commands:
/opt/IBMdb2/V5.0/doc/db2insthtml lang_locale
to create the search index for DB2 documentation in the language locale lang_locale. Note that whenever you install documentation in any language, English documentation is installed as well. So you should also run the following command to index the English files:
/opt/IBMdb2/V5.0/doc/db2insthtml en_US
Cause: DB2 runs the system utilities config_view and config_help to create or remove DB2 search index to be used with SCOHELP. However, error messages may be returned if there exists other non-DB2 indexes on the system that have not been created/removed properly.
Action:
Cause: Search index for DB2 documentation files are being created. Depending on the language(s) you have selected, this may take some time.
Cause: DB2 is unable to access the Windows NT Cluster.
Action: Ensure the Windows NT Cluster support has been correctly installed and the Cluster Service has been started.
Cause: DB2 encountered an error when attempting to grant the necessary user rights to the account specified for use with the DB2 service.
Action: Ensure a valid account has been specified and that you have the necessary privilege to grant user rights.
Cause: DB2 encountered an error when attempting to update the DB2/NT cluster service configuration.
Action: Ensure the Service Database has not been locked and is accessible. Also ensure the DB2/NT Cluster Service has been created.
Cause: DB2 encountered an error when attempting to read or update the Windows NT Cluster registry.
Action: Ensure the Windows NT Cluster support has been correctly installed and the Cluster Service has been started. Ensure that the current logon user account has sufficient authority to access the Cluster registry.
Cause: DB2 attempted to access an instance to perform cluster operations but the instance was not identified as a DB2 Cluster instance.
Action: Verify the instance was created with the Cluster options. The instance may be dropped and re-created using the Cluster option but the Node directory, Database Directory, and Database Manager Configuration file will be lost.
Cause: A system error was detected while DB2 was performing a Cluster operation.
Action: Check to make sure the Windows NT operating system is at the correct level for Cluster Support.
Also ensure the Windows NT Cluster support has been correctly installed and the Cluster Service has been started.
Cause: An error was encountered while attempting to update a node to support a DB2 Cluster instance.
Action: Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.
Cause: An error was encountered while attempting to delete a node from a DB2 Cluster instance.
Action: Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.
A workstation cannot drop cluster support from itself. The instance must be dropped to perform this task.
Cause: A error was detected while attempting to create the instance profile on a remote system to enable Cluster Support.
Action: Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.
Cause: A error was detected while attempting to delete the instance profile on a remote system to disable Cluster Support.
Action: Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.
Cause: The user specified incorrect arguments to the DB2NCRT command.
Action: Re-issue the command specifying a clustered instance and a valid workstation name for the cluster node.
Cause: The user specified incorrect arguments to the DB2NLIST command.
Action: Re-issue the command specifying a clustered instance.
Cause: The user request was successfully processed.
Action: No action required.
Cause: DB2 encountered an error when attempting to connect to the Windows NT registry on a remote machine.
Action: Ensure that the target machine is running and that the computer name specified is correct. Also ensure that the current logon user account has sufficient authority to connect to the remote machine registry.
Cause: DB2 encountered an error when attempting to connect to the Windows NT Cluster registry.
Action: Ensure that the Windows NT Cluster support has been correctly installed and the Cluster Service has been started.
Cause: The command failed for one of the following reasons:
Action: Follow the action corresponding to the cause of the problem:
Cause: The instance specified by the instance name parameter does not exist for the local machine.
Action: To find a list of valid instances, run the db2ilist command. Issue the command again using a valid instance name.
Cause: The required DB2 Profile Variable is not set at the target machine. The command can not continue.
Action: Contact your IBM service representative for assistance.
Cause: DB2 encountered an error when attempting to read or update the Windows NT registry of the target machine.
Action: Ensure that the current logon user account has sufficient authority to access the Windows NT registry of the target machine. If the problem persists, contact your IBM service representative for assistance.
Cause: DB2 encountered an error when reading or updating the TCP/IP services file.
Action: Ensure that the services file exists in the system and that the file can be accessed for read and write authority. Also, ensure that the contents of the file are valid and no duplicate of entries exist in the services file.
Cause: DB2 is unable to access the DB2 instance profile path specified because the path does not exists or write access has not been given to the current logon user account.
Action: Ensure that the path name for the DB2 instance profile points to a valid directory and that the current logon user account has write access to the directory.
Cause: The user account or the password is not valid.
Action: Issue the command again with the correct account.
Cause: The TCP/IP host name parameter is not valid or does not exist.
Action: Ensure that TCP/IP is operational on the system. If a domain name server is used, ensure that the domain name server machine is active. Issue the command again using the correct TCP/IP host name.
Cause: The db2icrt utility requires the TCP/IP port range to be specified when creating a partitioned database instance if the entries for TCP/IP port range for the instance have not been added to the services file.
Action: Choose a range of TCP/IP ports that are available for the system and issue the db2icrt command again with the -r option.
Cause: The computer name parameter is not valid
Action: Ensure that the target machine is running and that the computer name specified is correct. Also ensure that the current logon user account has sufficient authority to connect to the target machine registry.
Cause: DB2 is unable to query the service status for the DB2 service.
Action: Ensure that the DB2 service exists on the target machine. Ensure that the current logon user account has sufficient authority to query the service status on the target machine.
Cause: The account password has expired.
Action: Change your password, then retry the request using the new password.
db2iclus {add | drop | list | migrate }
[/c:Cluster name]
[/p:instance profile path]
[/u:username,password]
[/i:instance name]
Cause: Valid arguments for this command are:
Valid options for this command are:
Action: Enter the command again using valid parameters
Cause: When creating a partitioned database instance or adding a node to a partitioned database instance, you must specify the user account parameter. Under the Windows NT environment, each database manager partition (or MPP node) is required to run under a valid Windows NT account to access the network share which contains the instance directory.
Action: Issue the command again with the -u option to specify the user account name and password.
Cause: An attempt to migrate an instance into an MSCS instance failed because the the instance is already configured for MSCS support.
Action: No action required.
Cause: An attempt to add an MSCS node to the DB2 MSCS instance failed because The target machine is already part of the DB2 MSCS instance.
Action: No action is necessary.
Cause: The database partition server can not be dropped or modified because it is active.
Action: Ensure that the database partition server is stopped before attempting to drop or change it. To stop a database partition server, use the db2stop command as follow:
db2stop nodenum <node-number>
Cause: The db2ncrt command failed to add a new database partition server on a remote machine because there is an existing instance on the remote machine.
Action: If the instance on the remote machine is no longer used, remove the instance by running the db2idrop command on the remote machine.
Cause: When the db2nchg command is issued with the /m:machine option, the command will move the database partition server to a new machine. The db2nchg will fail if there is existing database(s) in the system.
Action: To move the database partition server to a new machine when there is database(s), use the db2start restart command. For more information on the db2start command, refer to the DB2 Command Reference.
db2iupdt InstName /u:username,password
[/p:instance profile path]
[/r:baseport,endport]
[/h:hostname]
Cause: An invalid argument was entered for the db2iupdt command. Valid arguments for this command are:
DB2_InstName baseport/tcp DB2_InstName_END endport/tcp
Action: Enter the command again using valid arguments.
Cause: The db2iupdt command failed to update the instance directory because of one of the following reasons:
Action: Ensure that the db2audit.cfg file exists in the \SQLLIB\CFG directory and that the current logon account has sufficient authority to create files and directories in the instance directory. The instance directory is located in \SQLLIB\InstName (where InstName is the name of the instance).
Cause: The db2iupdt command failed to update the database manager configuration file because the previous database manager configuration file is corrupted or missing. The current instance is in inconsistent state and can not be used.
Action: Copy the default database manager configuration file to the instance directory then re-submit the command. The instance directory is located in \SQLLIB\InstName. The default database manager configuration file is named db2systm and can be found in the \sqllib\cfg directory.
Cause: The db2nodes.cfg file is not updated to include the new node until all nodes are simultaneously stopped by the STOP DATABASE MANAGER (db2stop) command. Until the file is updated, the existing nodes cannot communicate with the new node.
Action: Issue db2stop to stop all the nodes. When all nodes are successfully stopped, issue db2start to start all the nodes, including the new node.
Cause: The instance that is being created or migrated is already in the instance list.
Action: Verify that the list of instances as reported by the db2ilist command is correct.
Cause: The specified instance was not found in the instance list.
Action: Verify that the list of instances as reported by the db2ilist command is correct.
Cause: The instance name is invalid. It cannot:
Action: Try the command again with a valid instance name.
Cause: An attempt was made to drop an instance which is active.
Action: Make sure all applications that are using the instance have finished executing before stopping the instance by issuing a db2stop (from that instance's user ID.)
Cause: The instance cannot be created becaused it is currently used by the DB2 Admin Server.
Action: Try the command again with a different instance name.
Cause: An incorrect argument was entered for the db2idrop command. Valid arguments for this command are:
Action: Enter the command again as follows:
db2idrop [-h] [-f] InstName
Cause: An incorrect argument was entered for the db2ilist command. The db2ilist command does not require any arguments.
Action: Enter the command again as follows:
db2ilist
Cause: The db2icrt utility creates a database instance:
db2icrt InstName [/mpp]
[/p:instance profile path]
[/u:username,password]
[/h:hostname]
[/c:Cluster name]
[/r:baseport,endport]
[/?]
The command options are:
DB2_InstName baseport/tcp DB2_InstName_END endport/tcp
Action: Enter the command again using the valid parameters.
Cause: An error occurred when adding the instance profile to the registry. The instance was not created.
Action: Contact your IBM service representative.
Cause: An error occurred when creating the required files or directories for the new instance. The instance was not created.
Action: Ensure that you have write access to the location where the instance directory is created. The instance directory is created under the path where the product is installed. You may use the DB2INSTPROF Profile Variable to specify a different location for the instance directory.
Cause: An error occurred when registering a DB2 service.
Action: Ensure you have sufficient authority to create an NT service and the Service Database is not locked, then retry the operation.
Cause: An error occurred when adding a node key for the new instance in the instance profile registry.
Action: Contact your IBM service representative.
Cause: An error occurred when adding the new node to the instance profile registry.
Action: Contact your IBM service representative.
Cause: When configuring the account for the DB2 Service, the account must be granted the user rights :
An error occurred when granting the user rights to the account for the instance.
Action: If the machine belongs to an NT domain, ensure that the primary domain controller is active and accessible over the network. Otherwise, contact your IBM service representative.
Cause: An error occurred when assigning a logon account to the DB2 service.
Action: Ensure user that the user name and the password for the logon account is valid.
Cause: The specified node was not found in the node list.
Action: Verify that the node exists by displaying the list of nodes using the DB2NLIST command.
Cause: An error occurred when removing the specified node from the instance profile registry.
Action: Contact your IBM service representative.
Cause: An error occurred when de-registering a DB2 service.
Action: Ensure that you have sufficient authority to delete an NT service.
Cause: An error occurred when changing the node configuration in the profile registry.
Action: Contact your IBM service representative.
Cause: An internal error occurred when creating a new file in the instance directory.
Action: Ensure that you have write access to the instance directory.
Cause: An internal error occurred when reading from or writing to a file in the instance directory.
Action: Contact your IBM service representative.
Cause: An error occurred when removing the instance profile from the registry.
Action: Contact your IBM service representative.
Cause: An error occurred when removing the required files or directories belonging to the specified instance.
Action: Ensure that you have write access to the location where the instance directory is located.
Cause: An error occurred when setting the DB2 service to start automatically.
Action: Reboot the machine and try the command again. If the problem persists, contact your IBM service representative.
Cause: An error occurred when setting the profile variable DB2ADMINSERVER in the profile registry.
Action: Contact your IBM service representative.
Cause: An error occurred when removing the environment variable DB2ADMINSERVER in the profile registry.
Action: Contact your IBM service representative.
Cause: The user ID that you provided during product installation could not be created in User Profile Management (UPM). This user ID is required to start the DB2 Administration Server.
Action: Manually create a user ID and password using UPM and then manually start the DB2 Administration Server. You may need to set the DB2 Administration Server to use this user ID and password combination using the "db2admin" command.