This chapter contains the error messages which may be generated during installation and configuration of DB2 products.
DBI1001I
Usage:
db2icrt [-a AuthType] -u FencedID InstName
Cause: An invalid argument was entered for the db2icrt command. Valid arguments for this command are:
-h|-? display the usage information.
-d turn debug mode on.
-a AuthType is the authentication type
(SERVER, CLIENT, or DCS) for
the instance.
-u FencedID is the name of the user under
which fenced UDFs and fenced
Stored Procedures will be run.
This flag is not required if only
DB2 CAE product is installed.
InstName is the name of the instance.
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
DBI1005I
Usage:
db2idrop InstName
Cause: An incorrect argument was entered for the db2idrop command. Valid arguments for this command are:
-h|-? display the usage information -d turn debug mode on. InstName is the name of the instance
Action: Enter the command again as follows:
db2idrop InstName
DBI1006I
Usage:
db2idrop [-f] InstName
Cause: An incorrect argument was entered for the db2idrop command. 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.
Action: Enter the command again as follows:
db2idrop [-f] InstName
DBI1011I
Usage:
db2iupdt -u FencedID InstName
Cause: An incorrect argument was entered for the db2iupdt command. Valid arguments for this command are:
-h|-? display the usage information
-d turn debug mode on.
-u FencedID is the name of the user under
which fenced UDFs and fenced
Stored Procedures will be run.
This flag is not required if only
DB2 CAE product is installed.
InstName is the name of the instance.
Action: Enter the command again as follows:
db2iupdt -u FencedID InstName
DBI1012I
Usage:
db2iupdt [-f] -u FencedID InstName
Cause: An incorrect argument was entered for the db2iupdt command. 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.
-u FencedID is the name of the user under
which fenced UDFs and fenced
Stored Procedures will be run.
This flag is not required if only
DB2 CAE product is installed.
InstName is the name of the instance.
Action: Enter the command again as follows:
db2iupdt [-f] -u FencedID InstName
DBI1015I
Usage:
db2imigr [-a AuthType] -u FencedID InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
-h|-? display the usage information
-d turn debug mode on.
-a AuthType is the authentication type
(SERVER, CLIENT, or DCS) for
the instance.
-u FencedID is the name of the user under
which fenced UDFs and fenced
Stored Procedures will be run.
This flag is not required if only
DB2 CAE product is installed.
InstName is the name of the instance.
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
DBI1016I
Usage:
db2imigr [-f] [-a AuthType] -u FencedID InstName
Cause: 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 appli-
cations using the instance
will be forced to terminate.
-a AuthType is the authentication type
(SERVER, CLIENT, or DCS) for
the instance.
-u FencedID is the name of the user under
which fenced UDFs and fenced
Stored Procedures will be run.
This flag is not required if only
DB2 CAE product is installed.
InstName is the name of the instance.
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
DBI1018I
Usage:
db2istop [-h|-?] [-d] [-f] InstName
Cause: 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 appli-
cations using the instance
will be forced to terminate.
InstName is the name of the instance.
Action: Enter the command again as follows:
db2istop [-h|-?] [-d] [-f] InstName
DBI1021I
Usage:
db2imigrev [-h|-?] InstName
Cause: An incorrect argument was entered. Valid arguments for this command are:
-h|-? display the usage information.
-d turn debug mode on.
InstName is the name of the instance
which will be migrated
backward from version 5 to
the previous version of DB2.
Action: Enter the command again as follows:
db2imigrev [-h|-?] InstName
DBI1022I
Usage:
db2imigrev [-h|-?] [-f] InstName
Cause: 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 5 to a previous
version of DB2.
Action: Enter the command again as follows:
db2imigrev [-h|-?] [-f] InstName
DBI1025I
Usage:
dasicrt DASName
Cause: An invalid argument was entered for the dasicrt command. Valid arguments for this command are:
-h|-? display the usage information.
DASName is the name of the DB2
Administration Server.
Action: Enter the command again as follows:
dasicrt DASName
DBI1027I
Usage:
dasidrop DASName
Cause: An invalid argument was entered for the dasidrop command. Valid arguments for this command are:
-h|-? display the usage information.
DASName is the name of the DB2
Administration Server.
Action: Enter the command again as follows:
dasidrop DASName
DBI1030E Kernel parameter "<name>" must be set to "<value>".
Cause: DB2 requires certain kernel parameters to be updated.
Action:
DBI1040I The translated version of following message is not available on this system.
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.
DBI1050E Unsupported operating system - "<OS-name>", version "<OS-ver>".
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".
DBI1051E You cannot execute this program as root.
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.
DBI1052E You must be root to execute this program.
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.
DBI1053E File system of type "<fsys-type>" is not supported.
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.
DBI1055E The message file "<file-name>" cannot be found.
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.
DBI1057E Required locale "<locale>" is not available.
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.
DBI1060E Invalid package name "<pkg-name>".
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.
DBI1061E A fileset or package name "<pkg-name>" is missing.
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.
DBI1062E A fileset or package name "<pkg-name>" is missing.
Cause: The above fileset or package must be installed before using this command.
Action: Install the fileset or package and then reissue this command.
DBI1063E PTF or patch "<patch-name>" is missing.
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.
DBI1065E Program "<program-name>" terminated prematurely.
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.
DBI1066E Program "<program-name>" terminated by request.
Cause: This program has been terminated by the user.
Action: Issue the same command to restart the program.
DBI1067E DB2 Product Library for locale "<locale-name>" is not installed.
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
Action: Install the DB2 Product 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>".
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.
DBI1069E Unexpected error. Function = "<fname>", Return code = "<return-code>".
Cause: An unexpected error occurred during the execution of this program.
Action: If the problem persists, contact IBM Support with the following information:
DBI1070I Program "<program-name>" completed successfully.
DBI1079I Output is saved in the log file "<log-name>".
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.
DBI1080E Disk full. Minimum space required in "<dir-name>" is "<KB>" KB, whereas only "<KB>" KB space is available.
Cause: There is not enough free space available in the file system or directory.
Action: Free more disk space and retry the command.
DBI1081E The file or directory "<file-name>" is missing.
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.
DBI1082E The file or directory "<file-name>" already exists.
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.
DBI1083E An attempt to remove "<file-name>" failed.
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.
DBI1084E An attempt to create "<file-name>" failed.
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.
DBI1085E An attempt to move the file or directory "<file-name>" to "<file-name>" failed.
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.
DBI1086E An attempt to copy the file or directory "<file-name>" to "<file-name>" failed.
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.
DBI1087E An attempt to create the link "<filename>" failed.
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.
DBI1088E Invalid access permission detected for directory "<directory>".
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.
DBI1089E Error in saving current instance related information in the "<backup-dir>" directory.
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.
DBI1091E An attempt to change permissions for "<directory>" failed.
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.
DBI1092E An attempt to change ownership for "<directory>" failed.
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.
DBI1093E An attempt to change group ownership for "<directory>" failed.
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.
DBI1095W
The file or directory "<name>" not found.
DBI1100E An instance lock is found. Another instance management command is running.
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
DBI1101E The instance name "<instance-name>" is invalid.
Cause: Instance name must be the login name of an existing user and cannot:
Action: Try the command again with a valid instance name.
DBI1103E The Administration Server already exists.
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.
DBI1104E The Administration Server cannot be dropped.
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 "db2iset -g DB2ADMINSERVER" command is correct and try again.
DBI1109E The kernel parameters must be updated before using this command.
Cause: Some of the kernel parameters are not configured properly.
Action:
DBI1111E The FencedID parameter must be specified using -u flag with this command.
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.
DBI1112E The FencedID parameter "<fenced-id>" is not valid.
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.
DBI1113W Previous value of FencedID parameter "<old-value>" is different. New value "<new-value>" is ignored.
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.
DBI1115E Invalid AuthType parameter "<auth-type>" specified with -a flag.
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.
DBI1120E Instance "<inst-name>" cannot be dropped.
Cause: An attempt was made to drop an instance which may still be active.
DBI1122E Instance "<inst-name>" cannot be updated.
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 and the instance is inactive. Retry the command.
DBI1124E Instance "<inst-name>" cannot be migrated.
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".
DBI1131E The user ID "<user-id>" is invalid.
Cause: An attempt to access the given user ID failed. One of the following situations has occurred:
Action: Make sure a valid user ID has been used. Create a new user if necessary.
DBI1135E The primary group "<group-name>" of user ID "<user-id>" is invalid.
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.
DBI1200E The directory "<directory-name>" is not a version "<version-number>" instance.
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.
DBI1202E Migration of instance "<inst-name>" is not supported.
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.
DBI1205E One or more local databases have been detected that cannot be migrated to the newest version. Check the logfile "<logfile-name>" for the list of errors.
Cause: Possible errors on the database are:
Action: Take the following corrective action for each database from the file "<logfile-name>" :
DBI1211E Migration of the "<directory-name>" failed.
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.
DBI1212W Migration of the local database directory on "<path>" failed.
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.
DBI1220W Migration of the node directory on "<path>" failed.
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.
DBI1221W The node directory is corrupted and cannot be migrated.
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.
DBI1222W The system database directory is corrupted and cannot be migrated.
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.
DBI1223W The local database directory is corrupted and cannot be migrated.
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.
DBI1225W The authentication type of a catalogued local database has been changed.
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.
DBI1240E The database manager could not be started.
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.
DBI1250E Applications are still using instance "<instance-name>".
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.
DBI1281E The database manager configuration file could not be initialized.
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.
DBI1282E The database manager configuration files could not be merged.
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.
DBI1290E An attempt to create the profile registry "<profile-name>" failed.
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
DBI1291E The instance "<instance-name>" was not found in the instance list.
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.
DBI1292E The instance "<instance-name>" is already in the instance list.
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.
DBI1295E The instance list could not be updated.
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
DBI1297E The instance profile "<profile-name>" could not be updated.
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
DBI1300N
db2set displays, sets, or removes DB2 profile variables.
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:
-g Access the global profile variables.
-i Specifies the instance profile to
use instead of the current or default.
-n Specifies the remote DB2 Administration
Server node name.
-u Specifies the user ID to use for the
Administration Server attachment.
-p Specifies the password to use for the
admin server attachment.
-r Resets the profile registry for the
given instance
-l Lists all instance profiles.
-lr Lists all supported registry variables.
-v Verbose mode.
-? Displays the command help message.
-h Same as -? option.
-all Displays all occurrences of the local
environment variables as defined in:
The environment, denoted by [e]
The node level registry,
denoted by [n]
The instance level registry,
denoted by [i] and
The global level registry,
denoted by [g]
-null Sets the variables value to null at
the specified registry level to prevent
looking up the value in the next registry
level as defined in the variable value
search order.
Notes:
db2set with no variable name displays all
defined variables.
db2set <variable> displays <variable>'s
value.
db2set <variable>= (nothing) deletes
the <variable>.
db2set <variable>=<value> modifies
the <variable>'s value.
db2set <variable> -null sets
<variable>'s value to NULL.
db2set <variable> -all displays all
defined <variable>'s values.
db2set -all displays all defined
variables in all registry levels
DBI1302E Invalid parameter detected.
Cause: An invalid parameter was used.
Action: Use the -? option for the usage help message.
DBI1303W Variable not set.
Cause: The variable was not set in the profile registry.
Action: No further action is required.
DBI1304E Unexpected error.
Cause: The tool encountered an unexpected system error.
Action: Contact your DB2 service representative.
DBI1305E The profile registry was not found.
Cause: The target machine does not have a profile registry setup.
Action: Create the registry on the target machine by installing DB2.
DBI1306N The instance profile is not defined.
Cause: The instance is not defined in the target machine registry.
Action: Specify an existing instance name or create the required instance.
DBI1307N The instance node profile is not defined.
Cause: The instance node is not defined in the target machine registry.
Action: Create the registry by installing the required DB2 product parts.
DBI1308E Out of memory condition encountered.
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.
DBI1309E System error.
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.
DBI1310E Remote registry access is not supported.
Cause: The tool does not support the remote registry option.
Action: Consult the Command Reference on how to access the registry remotely.
DBI1311I Listing registry instance profiles...
DBI1312I Listing defined global variables...
DBI1313I Listing defined instance variables...
DBI1314I Listing all supported registry variables...
DBI1315W Unknown message!
DBI1316E Instance is not MPP.
Cause: The target instance is not a DB2 MPP instance.
Action: Choose an MPP instance.
DBI1317E Instance node already exists.
Cause: A duplicate instance node already exists.
Action: Choose a different instance node.
DBI1500I
Usage:
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.
DBI1501E An internal error was encountered.
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:
DBI1502E An error was encountered when opening or reading from file, "<file-name>".
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:
DBI1503E An error was encountered when opening or writing to file, "<file-name>".
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:
DBI1504E An error occurred opening message files.
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.
DBI1505E An attempt to allocate memory failed.
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:
DBI1507E An instance of the DB2 Installer is already started.
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.
DBI1515E An attempt to allocate resource for a subprocess failed.
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:
DBI1516E An attempt to terminate a subprocess failed.
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:
DBI1517E An attempt to execute a command in a subprocess failed.
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:
DBI1520E Minimum terminal display size is 24 x 80.
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.
DBI1521E An attempt to read in the terminal capability information failed.
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:
DBI1522E An attempt to restore the terminal capability information failed.
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:
DBI1530E Cannot unpack image file.
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.
DBI1540E An invalid distribution media path is specified.
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.
DBI1541E An attempt to open or read from the given status file failed.
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:
DBI1550E There is not enough disk space on the file system.
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.
DBI1631E An error was encountered while creating a sample database.
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:
DBI1632E An error was encountered while configuring to "auto-start" instance.
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:
DBI1633E An error was encountered while removing the configuration to "auto-start" instance.
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:
DBI1635E An error was encountered while adding to the Administration Server group list.
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.
DBI1651E The specified UID is invalid.
Cause: An invalid UID has been entered. One of the following situations has occurred:
Action: Retry with a different user ID.
DBI1652E The specified user name is invalid.
Cause: An invalid user name has been entered. One of the following situations has occurred:
Action: Retry with a different user name.
DBI1653E The specified group is invalid.
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.
DBI1655E The specified password is invalid.
Cause: An invalid password has been entered. One of the following situations has occurred:
Action: Retry with a different password.
DBI1657E Instance name already in use.
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.
DBI1701E One or more of the TCP/IP parameters specified is invalid.
Cause: One of the following situations has occurred:
Action: Correct the problem and try again.
DBI1702E The specified service name or port number conflicts with existing values in the TCP/IP services file.
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.
DBI1703E No valid service name or port number found.
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.
DBI1709E An error was encountered when updating the TCP/IP services file.
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.
DBI1711E One or more of the IPX/SPX parameters specified is invalid.
Cause: One of the following situations has occurred:
Action: Correct the problem and try again.
DBI1715E NetWare User ID or NetWare Password is invalid.
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.
DBI1750W Security Risk.
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:
DBI1751W Protocol not detected.
Cause: You have selected a protocol that is not detected. DB2 Installer cannot update all of the protocol's required settings. However, you can to provide values for this protocol's settings.
Action:
DBI1755W The Administration Server is not created.
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:
DBI1756W DB2 Instance is not created.
Cause: You have not created a DB2 Instance. A DB2 Instance is an environment where you store data and run applications.
Action:
DBI1758W DB2 Instance or Administration Server detected.
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:
DBI1759W DB2 Instance or Administration Server configurations detected.
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:
DBI1761W Software pre-requisites violated on fileset or package "<pkg-name>".
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:
DBI1762W Software dependencies violated on fileset or package "<pkg-name>".
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:
DBI1900N The Windows NT Cluster support is not accessible.
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.
DBI1901N An error occurred when attempting to update the user rights for the DB2/NT cluster service.
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.
DBI1902N An error occurred when attempting to update the DB2/NT cluster service configuration.
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.
DBI1903N An error occurred when attempting to update the Cluster registry.
Cause: DB2 encountered an error when attempting to update the Windows NT Cluster registry.
Action: Ensure the Windows NT Cluster support has been correctly installed and the Cluster Service has been started. Use the Registry Editor to verify that the DB2 Key in the Resource Parameters Key has not been deleted.
DBI1904N The DB2 instance is not Clustered.
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.
DBI1905N A System Error occurred during a DB2 Cluster operation.
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.
DBI1906N A error occurred while attempting to add a node to a DB2 Cluster instance.
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.
DBI1907N A error occurred while attempting to delete a node from a DB2 Cluster instance.
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.
DBI1908N A error occurred while attempting create the instance profile on a remote system.
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.
DBI1909N A error occurred while attempting delete the instance profile on a 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.
DBI1910N Usage : DB2NCRT -I:<Instance Name> -C:<cluster node>
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.
DBI1911N Usage : DB2NLIST -I:<Instance Name>
Cause: The user specified incorrect arguments to the DB2NLIST command.
Action: Re-issue the command specifying a clustered instance.
DBI1912I The DB2 Cluster command was successful.
Cause: The user request was successfully processed.
Action: No action required.
DBI1950W The instance "<instance-name>" is already in the instance list.
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.
DBI1951W The instance "<instance-name>" was not found in the instance list.
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.
DBI1952E The instance name "<instance-name>" is invalid.
Cause: The instance name is invalid. It cannot:
Action: Try the command again with a valid instance name.
DBI1953E The instance is active.
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.)
DBI1954E The instance name is currently used by the DB2 Admin Server.
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.
DBI1955E Usage: db2idrop [-h] [-f] InstName
Cause: An incorrect argument was entered for the db2idrop command. Valid arguments for this command are:
-h display the usage information
-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
Action: Enter the command again as follows:
db2idrop [-h] [-f] InstName
DBI1956E Usage: db2ilist
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
DBI1957E Incorrect number of arguments for the db2icrt command.
Cause: The db2icrt command accepts the argument InstName.
Action: Enter the command again as follows:
db2icrt InstName
DBI1958N The instance profile cannot be added to the registry.
Cause: An error occurred when adding the instance profile to the registry. The instance was not created.
Action: Contact your IBM service representative.
DBI1959N The instance directory cannot be created.
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.
DBI1960N The DB2 service cannot be created.
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.
DBI1961N The node key for the new instance cannot be added to the registry.
Cause: An error occurred when adding a node key for the new instance in the instance profile registry.
Action: Contact your IBM service representative.
DBI1962N The new node can not be added to the registry.
Cause: An error occurred when adding the new node to the instance profile registry.
Action: Contact your IBM service representative.
DBI1963N An error occurred when granting the user rights to the account for the instance.
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.
DBI1964N The logon account cannot be assigned to the DB2 service.
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.
DBI1965N The node "<node-number>" was not found in the node list.
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.
DBI1966N The node cannot be deleted from the registry.
Cause: An error occurred when removing the specified node from the instance profile registry.
Action: Contact your IBM service representative.
DBI1967N The DB2 service cannot be de-registered.
Cause: An error occurred when de-registering a DB2 service.
Action: Ensure that you have sufficient authority to delete an NT service.
DBI1968N An error occurred when changing the node configuration in the profile registry.
Cause: An error occurred when changing the node configuration in the profile registry.
Action: Contact your IBM service representative.
DBI1969N An error occurred when creating a new file in the instance directory.
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.
DBI1970N An error occurred when reading from or writing to a file in 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.
DBI1971N The instance profile cannot be removed from the registry.
Cause: An error occurred when removing the instance profile from the registry.
Action: Contact your IBM service representative.
DBI1972N The instance directory cannot be removed.
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.
DBI1973N An attempt to configure the DB2 service to start automatically failed.
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.
DBI1974N The profile variable DB2ADMINSERVER cannot be set in the profile registry.
Cause: An error occurred when setting the profile variable DB2ADMINSERVER in the profile registry.
Action: Contact your IBM service representative.
DBI1975N The environment variable DB2ADMINSERVER cannot be removed from the profile registry.
Cause: An error occurred when removing the environment variable DB2ADMINSERVER in the profile registry.
Action: Contact your IBM service representative.
DBI1980W Unable to create user ID "<userID>" in UPM.
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.