DBI1250 - DBI1499

DBI Message ID	Message	Explanation	User Response
DBI1250E	Applications are still using instance `instance-name`.	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`	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 behavior when terminated using the indicated command. After all the applications have stopped, stop the database manager using "db2stop" command.
DBI1251N	An error occurred while creating the cluster resource for this instance.	The db2iupgrade command is unable to initialize the clustering service or is unable to find the existing DB2 resource to upgrade.	Ensure that the current logon user account has sufficient authority to access the clustering service. Also ensure that the cluster service is active on the system, and that any resources that the DB2 resource you are upgrading depends on are online on the current node. If the problem persists, contact your IBM service representative for assistance.
DBI1252N	An error occurred while registering the database server resource type in the clustering service.	DB2 requires a resource type to be available in the clustering service but the command to register the resource type failed.	Ensure that the current logon user account has sufficient authority to access the clustering service. Register the resource type manually using the utility "db2wolfi.exe i". If the problem persists, contact your IBM service representative for assistance.
DBI1253N	An error occurred while creating the cluster resource for this instance. The system cannot revert to its original settings.	An error occurred while creating the cluster resource required for this instance. The existing cluster resource for this instance was removed and could not be restored.	Ensure that the current logon user account has sufficient authority to access the clustering service. Also ensure that that cluster service is active on the system, and that any resources that the DB2 resource you are upgrading depends on are online on the current node. Recreate the resource for the instance using the "Cluster Administrator" available under the administrative tools control panel applet. If the problem persists, contact your IBM service representative for assistance.
DBI1254N	An error occurred while upgrading the cluster resource for this instance because the existing resource cannot be removed.	In order to upgrade the instance, the cluster resource must be removed and a new cluster resource must be created using the database server type. The command was not able to remove the existing cluster resource and therefore cannot upgrade this instance.	Ensure that the current logon user account has sufficient authority to access the clustering service. Also ensure that the cluster service is active on the system, and that any resources that the DB2 resource you are upgrading depends on are online on the current node. If the problem persists, contact your IBM service representative for assistance.
DBI1255E	The configuration file `filename` needed to create the specified instance type cannot be found.	The required configuration file to create the specified instance type can not be found.	Specify the instance type supported by the current installation and then rerun the command.
DBI1256E	The db2cluster_prepare command failed because the -instance_shared_dev parameter was not specified.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. You must specify the absolute path to the shared device on which the GPFS file system will be created using the required -instance_shared_dev parameter. This message is returned when the db2cluster_prepare command is called without the -instance_shared_dev parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a valid value for the -instance_shared_dev parameter.
DBI1257I	The DB2 Information Center is not listening for requests.
DBI1258E	Unable to start DB2 Information Center.	The command to start the DB2 Information Center was unsuccessful.	The messages are written in the log file doc/eclipse/workspace/.metadata/.log from the DB2 Information Center install path.
DBI1259I	Enabled root feature:
DBI1260E	Cannot read from response file.	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.	Correct the access permission and the location of the response file and try again.
DBI1261E	The value is not valid for the keyword.	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.	Correct the problem in the following line of the response file and try again.
DBI1262E	Unknown keyword detected in the response file.	The given keyword in the response file is not valid. Refer to the sample response file for a list of valid keywords.	Correct the problem in the following line of the response file and try again.
DBI1263I	Not enabled root feature:
DBI1264E	This program failed. Errors encountered during execution were written to the installation log file. Program name: `program-name`. Log file name: `log-name`.	This message is returned when some processes and operations have failed. Detailed information about the error was written to the log file.	Contact IBM support to get assistance in resolving this issue. Keep the log file intact as this file is an important reference for IBM support.
DBI1265I	Reserved service entry:
DBI1266I	Refer to the log file `log-name` for more information.	All processed and failed operations have been saved into this log file.	Do not modify this file in any way. This file is for IBM Technical Support reference.
DBI1267I	Not reserved service entry:
DBI1268E	The file set `fileset` is not available on the installation media.	One of the file sets to be installed is not found on the installation media. If the file set is not located on the installation media then it cannot be installed.	Ensure that the file set is located on the installation media. If the file set is not located on the installation media de-select it and try again.
DBI1269I	Summary:
DBI1270E	Error detected in the response file.	An error has been detected when processing the response file. Install cannot be continued unless the problem has been corrected.	Correct the problem in the following line of the response file and try again.
DBI1271E	The configuration file `configuration-file` is invalid.
DBI1272I	To start using the database manager instance `instance-name`, you must set up the instance environment by sourcing db2profile or db2cshrc in the sqllib directory, or you can open a new login window of the instance user.	The database manager instance cannot be used before db2profile (for Bourne or Korn shell users) or db2cshrc (for C shell users) is sourced.	To set up the database manager instance environment, you can open a new login window under the ID that owns the instance, or source the instance environment by running the appropriate following command under the ID that owns the instance: . $HOME/sqllib/db2profile source $HOME/sqllib/db2cshrc where $HOME represents the home directory of the user ID that owns the instance.
DBI1273W	The DB2 Text Search instance service could not be configured for the instance. Reason code: `reason-code`.	An attempt to configure the instance for DB2 Text Search failed. Possible reasons are: 1 DB2 Text Search is not installed. Install DB2 Text Search from the installation media then try again. 2 The service name or port number specified is not valid. A valid service name must not exceed 14 characters in length, and a valid port number must be in the range 1024-65535. 3 The port number specified is being used by another application. Choose a port number that is available on the system. 4 The specified service name or port number conflict with existing values in the TCP/IP services file. Provide a service name and a port number that is available on the system. 5 The TCP/IP services file could not be accessed. Check that you have permission to read and write to the services file. Also, ensure that the content of the file is valid and no duplicate entries exist. 6 The default service name is reserved to a port number that is different from the one provided. Provide a service name and port number that do not conflict with existing entries in the TCP/IP services file. 7 The default service name is reserved to a port number that is being used by another application. Choose a service name and port number that is available on the system. 8 The service name provided is reserved to a port number that is being used by another application. Choose a service name and port number that is available on the system. 9 An attempt to create or copy DB2 Text Search directories or files in the instance directory failed. 10 An attempt to read or write to DB2 Text Search configuration files in the instance directory failed. 11 An attempt to create the DB2 Text Search instance service Windows service failed. 12 An unexpected internal error occurred.	Contact your IBM service representative if the suggested action associated with the reason code did not solve the problem.
DBI1274N	The DB2 Text Search instance service for the instance could not be stopped.	An attempt to stop the DB2 Text Search instance service failed. The Windows service could not be stopped.	Stop the DB2 Text Search server for the instance and try your command again.
DBI1275E	The DB2 Text Search instance service for the instance could not be stopped.	An attempt to stop the DB2 Text Search instance service failed.	Stop the DB2 Text Search instance service for the instance and try your command again.
DBI1276E	The database product installation at `install-path` must be updated while logged in under the user ID that performed the installation.	You can only update the database product installation by running the installFixPack command under the user ID that performed the database product installation. You have to run the installFixPack command as a user with root privilege to update a Db2® root installation.	Rerun the command with an appropriate user ID.
DBI1277E	Install path and runtime path do not match	When setting up the runtime path with db2chgpath, a path was given that does not match the current path that the database manager is running from.	Perform one of the following actions: Move the install path to match the runtime path. Rerun db2chgpath with the correct runtime path, to match the current install path.
DBI1278W	Warning issued from the response file.	A warning has been raised when processing the response file. The database product installer will carry on without stopping.	If required, correct the problem in the following line of the response file and try again.
DBI1279I	Notice issued from the response file.	A notice has been issued when processing the response file. The database product installer will carry on without stopping.	This is for your information only. No action is required.
DBI1280E	The db2cluster_prepare command failed because one or more parameters were specified multiple times.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. This message is returned when the db2cluster_prepare command is called with a duplicate parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying each parameter only once.
DBI1281E	The database manager configuration file could not be initialized.	An error occurred when attempting to initialize the database manager configuration file. A database manager instance could not be created or upgraded.	Refer to the log file for troubleshooting. Resolve the problem and try the command again. If the problem persists, contact your IBM service representative.
DBI1282W	The database manager configuration files could not be merged. The original configuration file was saved as `dbm-cfg-file-name`. (The original instance type is `original-instance-type`. The instance type to be upgraded or updated is `instance-type-upgraded`.)	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. This error could happen if the instance is being upgraded or updated from a higher instance type to a lower instance type. If the instance update or upgrade was successful, a new instance is created using the default configuration settings for the instance-type-upgrade. This error could happen if the instance is being upgraded or updated from a higher instance type to a lower instance type. The new instance uses the default configuration settings for the new instance type if update or upgrade was successful.	Check the values in the new database manager configuration file and update the parameters as required using the dbm-cfg-file-name original configuration file.
DBI1283E	Unable to update the communication information for `instance`.	The SVCENAME parameter and/or the DB2COMM registry values could not be updated during instance creation.	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
DBI1284I	`feature-name` has been set successfully.
DBI1285E	Setting `feature-name` failed. See log file `log-file-name` for details.
DBI1286E	The utility `utility-name` was not found.	The utility must be available on your system to install or update database products.	Ensure that the utility is installed and its location is in the PATH environment variable. Re-enter the command.
DBI1287E	There has been an attempt to use db2_deinstall on an image for a platform that does not match the current platform `platform` on which it is being run.	Possible causes include: This database product install image is not valid for the current platform. The current platform is not supported by the database product.	Remove the database product using the install image that corresponds with the current platform `platform` or directly run the command db2_deinstall from the directory 'DB2DIR/install', where DB2DIR is the database product installation path.
DBI1288E	The execution of the program `program-name` failed. This program failed because you do not have write permission on the directory or file `directory-or-file-name`.	Reasons for this error include: The given directory or file is on a local file system of the current machine, but the user id running the program does not have write permission for that directory or file. The given directory or file is on an NFS mounted file system mounted on the current machine, but the current user id does not have write permission for that directory or file. The current user id does not have write permission for the given directory or file located at the target partition. This can happen when the current machine's operating system is IBM AIX Version 6.1 or later and a Workload Partition root user id is attempting to write to a Global Partition.	There are several ways to respond to this message: Run the program with a user id that has write permission for the given directory or file. Modify the permissions of the directory or file to allow the user id to write to that directory or file, and rerun the program. Modify the authority of the user id to allow that user id to write to the given directory or file, and rerun the program.
DBI1289W	The database product install or instance utility `utility-name` failed to configure file permission and ownership properties for files related to DB2 Advanced Copy Services (ACS). See the log file `log-file-name` for more information.	The database product install or instance utility attempted to configure permission and ownership for DB2 ACS files that are located in the sqllib/acs directory under the DB2 instance home directory. The given log file contains information about why the database product install or instance utility failed. DB2 ACS might not be usable because the database product install or instance utility failed to configure permission and ownership for these files.	If you will not be using DB2 ACS, you do not need to reinstall IBM Data Server, or recreate the database manager instance. If you will be using DB2 ACS, perform the following steps: See the given log file for more information about the failures. Correct the cause of the failures and take the action recommended in the log file.
DBI1290E	An attempt to create the profile registry `profile-name` failed.	An error occurred when creating the profile registry. One of the following situations occurred: Incorrect access permission on the top directory of the current database product installation. There is not enough space on your file system.	Check the directory permissions for the top directory of the current database product installation.
DBI1291E	The instance `instance-name` was not found in the instance list.	The specified instance was not found in the instance list.	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.	The instance that is being created or upgraded is already in the instance list.	Use a different instance name that is not part of the instance list as reported by the db2ilist command.
DBI1294W	The database product install or instance utility `utility-name` failed to start DB2 Advanced Copy Services (ACS.) See the log file `log-file-name` for more information.	Before you can use DB2 ACS, the services must be started. The database product install or instance utility attempted to start the services, but failed. You can use the database manager instance, but you cannot use DB2 ACS until the services are started.	To start DB2 ACS, perform the following steps: See the given log file for more information about the failures. Correct the cause of the failures. Start DB2 ACS manually.
DBI1295E	The instance list could not be updated.	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: Incorrect access permission on the registry profile. Profile registry is not set up properly. There is not enough space on your file system.	Check the file permissions on the instance list profile under the top directory of the current database product installation.
DBI1296E	The database product install or instance utility `utility-name` failed to stop DB2 Advanced Copy Services (ACS.) See the log file `log-file-name` for more information.	Before you can update or upgrade a database manager instance, DB2 ACS must be stopped. The database product install or instance utility attempted to stop the services, but failed. You cannot update or upgrade the instance until DB2 ACS is stopped.	To stop DB2 ACS, perform the following steps: See the given log file for more information about the failures. Correct the cause of the failures. Stop DB2 ACS manually.
DBI1297E	The instance profile `profile-name` could not be updated.	An error occurred when updating the instance profile registry. One of the following situations occurred: Incorrect access permissions on the instance profile registry. Profile registry is not set up properly. There is not enough space on your file system.	Check the file permissions on the instance list profile under the top directory of the current database product installation.
DBI1298E	The database product install or instance utility `utility-name` failed to disable DB2 Advanced Copy Services (ACS.) See the log file `log-file-name` for more information.	Before you can drop a database manager instance, or remove a non-root install of IBM Data Server, DB2 ACS must be stopped. The database product install or instance utility attempted to disable the services, but failed. You cannot drop an instance, or remove a non-root install of IBM Data Server until DB2 ACS is disabled.	To disable DB2 ACS, perform the following steps: See the given log file for more information about the failures. Correct the cause of the failures. Disable DB2 ACS manually.
DBI1299E	DB2 profile registry variable `variable-name` was not nulled because it is a member of an aggregate set.	Several DB2 profile registry variables can be grouped together and set as one aggregate DB2 profile registry variable. When you configure an aggregate DB2 profile registry variable, the DB2 profile registry variables that are members of that set are automatically configured to their predefined values. DB2 profile registry variables that are members of an aggregate set, can not be nulled using the following db2set command syntax: db2set `variable-name`= The variable was not nulled.	To null a DB2 profile registry variable that is a member of an aggregate set, use the following db2set command syntax to set the variable to NULL: db2set -null `variable-name`
DBI1300N	db2set displays, sets, or removes DB2 profile variables. db2set [variable=[value]] [-g\|-i instance [member-number]] [-all] [-null] [-r [instance] [member-number]] [-im\|-immediate] [-info] [-n DAS node[-u user[-p password]]] [-l\|-lr] [-v] [-ul\|-ur] [-?\|-h]	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. -ul Access the user profile variables -ur Refreshes user profile variables -p Specifies the password to use for the admin server attachment. -r Resets the profile registry for the given instance. The default/current instance will be used if none is provided. -im \| -immediate Specifies that the update takes effect the next time an SQL statement is compiled for registry variables that support this feature. -info Returns the properties of the specified variable. The properties state whether an immediate change is supported by the variable and whether the change is immediate by default -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 user level registry, denoted by [u] 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 -ur refreshes the current user profile. db2set <variable> -ul displays defined <variables> at the user level. db2set -all displays all defined variables in all registry levels.
DBI1301E	The registry variable was not updated because an invalid value was specified.	You can configure many aspects of DB2 database functionality by setting DB2 profile registry variables. You can set DB2 profile registry variables by using the db2set command. This message is returned when an attempt is made to use the db2set command to set a DB2 profile registry variable to a value that is invalid.	Determine the range of valid values for the registry variable. Call the db2set command again, specifying a valid value for the specified registry variable.
DBI1302E	Invalid parameter detected.	An invalid parameter was used.	Use the -? option for the usage help message.
DBI1303W	Variable not set.	The variable was not set in the profile registry.	No further action is required.
DBI1304E	Unexpected error.	The tool encountered an unexpected system error.	Contact your DB2 service representative.
DBI1305E	The profile registry was not found.	The target machine does not have a profile registry setup.	Create the registry on the target machine by installing DB2.
DBI1306N	The instance profile is not defined.	The instance is not defined in the target machine registry.	Specify an existing instance name or create the required instance.
DBI1307N	The instance node profile is not defined.	The instance node is not defined in the target machine registry.	Create the registry by installing the required database product parts.
DBI1308E	Out of memory condition encountered.	The tool encountered an "out of memory resource" error.	System is low on memory resources. Terminate non-essential applications or try again later.
DBI1309E	System error.	The tool encountered an operating system error.	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.	The tool does not support the remote registry option.	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...
DBI1315E	The specified variable is not an aggregate type registry variable.	To display the group definition, the registry variable must be an aggregate type registry variable.	Do not specify the -gd option or specify a valid aggregate variable name when using the -gd option.
DBI1316E	Instance is not MPP.	The target instance is not a DB2 MPP instance.	Choose an MPP instance.
DBI1317E	Instance node already exists.	A duplicate instance node already exists.	Choose a different instance node.
DBI1318E	The value specified for the registry variable is too long.	The value specified for the registry variable exceeds the maximum limit. The maximum length for a registry variable value is 255 bytes.	Specify a shorter value for the registry variable.
DBI1319W	The variable `variable-name` has been explicitly set and will not be affected by the configuration of the aggregate variable `aggregate-var-name`.	An aggregate registry variable has been configured to a value whose group definition contains settings for a variable which has been explicitly configured. The explicitly configured value will be retained.	If desired, explicitly configure the variable.
DBI1320W	WARNING:	This script is used to gather information useful to IBM Support to debug the problems you may be experiencing. This information may be of a sensitive nature. You may wish to edit the output file, db2ginfo.txt, before sending it to IBM Support.	To signal your awareness and acceptance of the warning, run this script with the -y flag specified.
DBI1321W	The ulimit setting for the database manager instance `instance-name` does not comply with the recommended values for DB2 on the current platform.	The ulimit setting for the current non-root database manager instance has values for 'data' and 'nofiles' smaller than the values recommended by DB2 on the current platform. Set the 'data' to 'unlimited' and 'nofiles' to '65536' or the maximum value allowed on the system. If setting 'data' to 'unlimited' cannot be done, the following formula can be used as reference to decide the estimate value in kilobytes of 'data' required by DB2 for the current platform: default_data_ulimit + ( ( 20 * max_concurrent_active_databases ) + estimated_max_connections ) * max_querydegree * 8192 where: default_data_ulimit is the default value of 'data' of ulimit for a user on the system. For example, the default value is 262144 on IBM AIX system. max_concurrent_active_databases is the maximum number of concurrent active databases for the instance. estimated_max_connections is the estimated maximum number of database connections for the instance. max_querydegree is the value of the parameter "MAX_QUERYDEGREE" for database manager configuration when the INTRA_PARALLEL is enabled in the database manager configuration. If INTRA_PARALLEL is not enabled, the max_querydegree's value is 1.	Ask the system administrator with root privilege to update the ulimit setting for the current instance.
DBI1322I	An incorrect argument was entered for the db2iprune command.	Syntax: `db2iprune -r input_file_path -o destination_dir_path \| -c [-t trace_file] [-l log_filename] [-h\|-?]`	Enter the command again using the valid parameters.
DBI1323I	Usage: db2rspgn -d output_directory [-i instance] [-t trace-file] [-h\|-?]	An incorrect argument was entered for the db2rspgn command. Valid arguments for this command are: -d Specifies the full path to the output directory for generated files. If the output directory specified is an existing directory, the directory must be empty and writable. If the output directory specified does not exist, the new directory is created if the location is writable. This parameter is mandatory. -i instance Generates the specified instance configuration and saves this information in the generated response file and instance configuration profile. This parameter is optional. By default, all instances are selected. To specify multiple instances, specify this parameter multiple times. For example, -i db2inst1 -i db2inst3. -t trace-file Linux and UNIX operating systems only. Turns on the debug mode. The debug information is written to the file name specified as trace-file. -h\|-? Displays help information.	Enter the command again using the valid parameters.
DBI1324W	Support of the `command-name` command is deprecated.
DBI1325E	The `command-name` command has failed.	At least one instance is still running the DB2 Text Search instance service.	Stop the DB2 text search instance service and re-run the command.
DBI1326W	The Text Search instance services failed to restart.	Before running the database manager instance command, the Text Search instance service was not stopped. The database manager process stopped the Text Search instance service. However, the database manager process is unable to restart the Text Search instance service.	Manually restart the Text Search instance service.
DBI1327E	The db2icrt command failed because the home directory of the instance owner is a subdirectory under the directory in which the database product is installed.	The home directory of the instance owner cannot be a subdirectory under the directory in which the database product is installed. For example, if the database product is installed in the directory named /opt/db2v97, the home directory of the user who will be the instance owner cannot be in any directory under /opt/db2v97. This message is returned in the following scenario: On Linux and UNIX operating systems: the home directory of the instance owner is a subdirectory under the directory in which the database product is installed. The database manager instance was not created.	Configure that the user environment and directory structure so that the home directory of the instance owner is not a subdirectory of the directory in which the database product is installed. Run the db2icrt command again.
DBI1328E	The db2cluster_prepare command failed because no value was specified for the -instance_shared_dev parameter.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. You must specify the absolute path to the shared device on which the GPFS file system will be created using the required -instance_shared_dev parameter. The db2cluster_prepare utility will create the GPFS file system in the specified location. This message is returned when the db2cluster_prepare command is called without a value specified for the -instance_shared_dev parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a value for the -instance_shared_dev parameter.
DBI1329I	Usage: db2val [-h\|-?] [-o] [-i inst_name1] \| [-a] [-b db_name] [-t trace_file] [-d] [-s] [-l log_file]	An invalid argument was entered for the db2val command. Valid arguments for this command are: -o Specifies that only the installation files will be validated; validation of the instance, database, and extended security will not be performed. If this parameter is specified, the -i, -a, -b, and -s parameters are ignored. -i inst_name Specifies that the name of the instance to validate. To specify validation of multiple instances, specify this parameter multiple times. For example, -i inst1 -i inst2. On Windows operating systems, if this parameter is not specified, the current instance will be used as the default value. On Linux and UNIX operating systems, this parameter can only be used by root users in a root installation of a DB2 copy. -a Validates all instances in the DB2 copy. On Linux and UNIX operating systems, this parameter can only be used by root users in a root installation of a DB2 copy. This option overrides the -i option. -b db_name Validates the local database creation and connection with the given database name. This parameter is ignored in the following scenarios: the instance to be validated is a client instance -a and -i are not specified when db2val is run by root users (on Linux and UNIX only). -t trace_file Specifies the full path and name of trace file specified by trace_file. -d This parameter is deprecated and might be removed in a future release. Use the -t parameter instead. Valid only on Linux and UNIX operating systems. Use this parameter only when instructed by DB2 Support. Turns the debug mode on. -s Starts the database manager for the specified instance that is part of a partitioned database environment. This parameter overrides parameter -i. -l log_file Writes the log to the file name specified. Unless the -l parameter is specified, the default log path is: On Linux and Unix, /tmp/db2valxx.log On Windows, My Documents\DB2LOG\db2valxx.log where xx is a generated value. -h\|-? Displays the usage information.	Enter the command again using the valid parameters.
DBI1330W	The action might affect other instances.	The file IWH.environment contains global information for all instances. Updating this file might affect all instances. Do you wish to continue?
DBI1331E	Installation file validation for the DB2 copy `copy_name` failed.	Some features or components have missing files or are the wrong size.	To repair the database product installation, from the Add or Remove Programs tool, select Change for the DB2 copy, and select the Repair option. Rerun the db2val command.
DBI1332E	Missing template file for IWH.environment.	The template file for IWH.environment is needed.
DBI1333I	Installation file validation for the DB2 copy `copy_name` was successful.
DBI1334E	Installation file validation failed for the DB2 copy installed at `installation-location`. Reason code = `reason-code`.	You can verify the basic functions of a DB2 copy, checking the state of installation files, instance setup, and local database connections, by using the db2val utility. This message is returned when the db2val utility detected problems with the DB2 copy that is installed at the given location. The reason code indicates more specifically what the problem is: 1 Some features or components have missing files or files with the wrong size. 2 The installation image inside the install path has missing files. 3 The embedded runtime path for some DB2 library or executable files is not set properly. 4 The installation path is not accessible to the database manager. 5 The /etc/services file is not accessible to the database manager.	Respond to this message according to the reason code: 1 Respond to reason code 1 in one of the following ways: If your DB2 copy has the DB2 pureScale Feature installed: Reinstall the DB2 copy to a new path by running the installFixPack command from the installation media, specifying the -p <new-path> option and the -f nobackup option. Update the instance to the new copy using the db2iupdt command. Run the db2val command. If your DB2 copy does not have DB2 pureScale installed: Reinstall the DB2 copy to the same path by running the installFixPack command, specifying the "-f nobackup" option. Run the db2val command. 2 Copy the installation image into <DB2-installation-path>/sd directory. 3 Set the embedded runtime path by using one of the following methods: For root installations, run <DB2-installation-path>/install/db2chgpath as root. For non-root installations, run <DB2-installation-path>/install/db2chgpath as the copy owner. Then run the db2val command. 4 Modify the access permissions for the installation path so that the database manager can access the installation path. 5 Modify the access permissions for the /etc/services file so that the database manager can access that file.
DBI1335I	Installation file validation for the DB2 copy installed at `installation_location` was successful.
DBI1336E	The partitioned database environment validation for the instance `instance_name` failed. Reason code = `reason_code`.	The format of the DB2 node configuration file (db2nodes.cfg) is incorrect. The other database partition servers are not accessible. The start and end ports for Fast Communication Manager (FCM) are not reserved properly on all database partition servers. The instance profile directory is not accessible from all database partition servers. The instance service is running under a non-domain account. This will prevent the database manager instance from starting. The installation directory for the instance is not accessible from all database partition servers. The code level on each database partition server is not consistent. On Windows operating systems, if the db2val command is run to validate a multiple partition instance, domain user account authority is required. An unexpected internal error occurred.	Ensure the format of db2nodes.cfg follows the DB2 standard. Check the .rhosts file is configured on all the partitions. If the DB2RSHCMD registry variable is set to ssh, ensure the ssh remote shell utility is available. Ensure the start and end ports for FCM are free and reserved on each computer participating in the partitioned database environment. The start port should be the same on each participating computer. Ensure the instance profile directory on the instance-owning machine is shared among all the database partition servers. The instance profile directory should be in the UNC format. Use a domain account for the instance service on all database partition servers. Ensure the installation directory is accessible from all database partition servers. Ensure the same code level is installed on all computers participating in the partitioned database environment. Log on as a user with the domain user account authority and retry the command. Rerun the db2val command. If this error persists, contact your IBM service representative.
DBI1337I	The partitioned database environment validation for the instance `instance_name` was successful.
DBI1338E	The validation of instance `instance_name` failed. Reason code=`reason_code`.	The default instance is not set. Some files in the instance directory are damaged. The symbolic links of the files are not pointing to the current DB2 copy installation path, and the file permission and ownership might have been changed. The DB2 Extended Security setup does not allow the current user to start an instance. If Extended Security is enabled, the user needs to be in the DB2ADMNS group. To start the instance, read permission is required to the /etc/services file. The appropriate authority is required to validate this instance. The partitioned database environment setting is not correct. The instance failed to start because of system errors. An unexpected internal error occurred.	Set the DB2INSTDEF profile registry variable to an instance in the DB2 copy. Run the db2iupdt or db2nrupdt command with the -k option for the instance. Add the current user to the DB2ADMNS group and rerun the command. Ensure you have read permission to the /etc/services file. Log on as a user with the appropriate authority, and retry the command. Check the partitioned database environment validation log file for details. Check the log file for details. Rerun the db2val command. If this error persists, contact your IBM service representative.
DBI1339I	The instance validation for the instance `instance_name` was successful.
DBI1340I	Database validation for instance `instance_name` was successful.
DBI1341E	`ID` does not have the authority to perform the requested command.	The appropriate authority is required to run the command.	Log on as a user with the appropriate authority, and retry the command.
DBI1342E	Instance `instance_name` does not exist in the current DB2 copy.	The specified instance does not exist in the current DB2 copy and will not be validated.	Rerun the db2val command with an instance that is listed by the db2ilist command for the current DB2 copy.
DBI1343I	The db2val command completed successfully. For details, see the log file `log_path`.
DBI1344E	The validation tasks of the db2val command failed. For details, see the log file `log_path`.
DBI1345W	Read permission to the /etc/services file is not granted to every user. This lack of permission can cause the instance creation to fail.	Creating an instance requires the users who manage the instance to have read permission to the /etc/services file.	Ensure users have read permission to the /etc/services file.
DBI1346W	Path `path` defined in the DFTDBPATH database manager configuration variable is not accessible on the current database partition server. This can cause the database creation to fail.
DBI1347W	The db2val command completed with warnings. For details, see the log file `log_path`.
DBI1348W	Read and execute permissions to the installation directory are not granted to everyone. This lack of permission might cause problems when using your database product.
DBI1349W	Installation file validation completed with warnings for the DB2 copy installed at `installation_location`. For details, see the log file `log_path`.
DBI1350E	The database validation failed for the instance `instance_name`. Reason code=`reason_code`.	Database validation failed because of one of the following reasons: Database creation failed because of system errors. Database connection failed because of system errors. An unexpected internal error occurred.	Check the log file for details, or rerun the db2val command. If this error persists, contact your IBM service representative.
DBI1354E	The instance `instance-name` is not an DB2 Query Patroller Server instance.		Use dqplist to find out the proper server instance name and re-run the command again.
DBI1356I	Usage: dqplist [-h\|-?]	An incorrect argument was entered. Valid arguments for this command are: -h\|-? display the usage information	Re-enter the command with the proper syntax.
DBI1362W	IWM schema objects have been detected.	The database manager has detected IWM schema objects, possibly from a previous install of IWM.	If you wish to keep the existing IWM schema objects, there is nothing to do. If you wish to remove them and re-create new ones, re-issue the dqpsetup command with the -o flag.
DBI1363E	Failed to create IWM schema objects.	An attempt to create the IWM schema objects has failed.	Verify that the files db2_qp_schema and iwm_schema.sql are both in the directory /usr/opt/db2_08_xx/bin, where xx is 01 or FPn, where n is the FixPak number. If both files exist, then the output of the IWM schema creation procedure can be found in /tmp/iwmschcr.log. Correct any error and re-run the dqpsetup command again.
DBI1365E	Node number is not defined.	The node number is not defined in the db2nodes.cfg.	Examine the db2nodes.cfg file and make sure the entry you want is there. Enter the command again using the correct node number exactly as recorded in the db2nodes.cfg file.
DBI1366E	The container `sms-path` is already in use.	The directory named as a container for the table space already exists.	Run the command again using a different path for the container for the table space.
DBI1367E	Failed to bind the files listed in `bind-list`.	There was a problem binding the bind files listed in named file(s).	Perform the binding manually.
DBI1368E	Failed to connect to DQP database `db2dbdft`.	The database likely does not exist.	Specify that you would like to setup a new DQP instance using all the required parameters to dqpsetup. This instance cannot be upgraded.
DBI1369W	The partitioned database environment validation for the instance `instance_name` completed with warnings.
DBI1370W	Unable to modify the .profile or the .login file of user `inst-name`.	The database manager 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 Query Patroller.	Set up the application development environment.
DBI1374W	The validation of instance `instance_name` completed with warnings.
DBI1377N	db2isetup was unable to locate a suitable Java Runtime Environment on your computer. If a Java Runtime Environment `jre-version` is present, set your JAVA_HOME environment variable and run the command again. Otherwise, refer to the database product installation requirements for information on the recommended Java environment for your operating system. If you need to use your own JRE, set DB2USELOCALJRE=true.
DBI1378N	db2setup was unable to locate a suitable Java Runtime Environment on your computer. If a Java Runtime Environment `jre-version` is present, set your JAVA_HOME environment variable and run the command again. Otherwise, refer to the database product installation notes for information on the recommended Java environment for your operating system. If you are unable to obtain a suitable Java Runtime Environment you can install this product from the command using the doc_install script. Run this script without any parameters for information on how to use it. If you need to use your own JRE, set DB2USELOCALJRE=true.
DBI1379I	The db2val command is running. This can take several minutes.
DBI1380W	The database `db_name` cannot be removed.	The database might be in use by other applications.	To manually drop the database, run the following command: db2 drop db `db_name`
DBI1381W	Database validation for instance `instance_name` completed with warnings.
DBI1382W	The database manager of the instance `instance_name` cannot be stopped.	The database might still be in use.	To stop the database manager, run the db2stop command.
DBI1383I	You must update the DB2 registry for the current instance manually using the db2iset command, including the full path of the db2iset command. For example: /opt/ibm/db2/<release>/instance/db2iset -d `instance-name`.
DBI1384E	The instance `instance-name` cannot be created.	DB2 Text Search configuration can only be performed on server instances.	Configure the DB2 Text Search feature on a server instance.
DBI1385W	Partitioned instances are not supported with the DB2 Text Search feature.	The DB2 Text Search feature cannot be configured for this instance.	Configure a single-partition instance to use the DB2 Text Search feature
DBI1386N	The account `user-name` is locked.	The user's account is locked by the operating system.	Contact the system administrator to unlock this user's account.
DBI1387I	An invalid argument was entered for the db2isetup command.	The syntax for the db2isetup command is: `db2isetup [-h\|-?] [-i <language_code>] [-r <response_file>] [-t <trace_file>] [-l <log_file>]`	Enter the command again using valid parameters.
DBI1388E	The db2nrupgrade command failed because an invalid parameter was specified.	You can upgrade a non-root database manager instance to a new database product version by issuing the db2nrupgrade command. This message is returned when the db2nrupgrade command is issued and an unsupported parameter is specified with the command.	Enter the command again specifying supported parameters.
DBI1389I	Usage: db2ckupgrade ( <database_name> \| -e ) -l <logfile> [-u <userid> -p <password>] [-h\|?]	database_name Specifies the name of a database to be scanned. -e Specifies that all local cataloged databases are to be scanned. -l logfile Mandatory parameter. Specifies a log file to keep a list of errors and warnings generated for the scanned database. -u userid Specifies the user ID of the instance owner. -p password Specifies the password of the instance owner. -h\|? Displays the usage information.	Reenter the command with the proper syntax.
DBI1390E	The current instance cannot be upgraded.	An attempt was made to upgrade the instance. This instance cannot be upgraded because either: The DB2 version running the db2nrupgrade command is not a supported version to upgrade the current instance. The instance is still active	Also ensure that there are no database manager processes running at the instance. Fix the error, and to upgrade the instance to the new DB2 Copy version, rerun the db2nrupgrade command.
DBI1391E	`directory-name` is not a valid path.	The directory cannot be accessed.	Enter a valid path and rerun the command.
DBI1392W	The `deprecated-command-name` command is deprecated. The deprecated command is replaced by new command `new-command-name`.	The deprecated command will be removed from a future release.	Replace the deprecated command with the new command in any scripts or applications.
DBI1393W	The -j "TEXT_SEARCH" option is supported only on server instances ese, wse and standalone.	The current instance is of type client or DB2 pureScale. The command completed, but the -j "TEXT_SEARCH" option was ignored.	To use DB2 Text Search specify a server instance.
DBI1394E	The db2cluster_prepare command failed because the db2cluster_prepare utility cannot write to the following trace file path: `trace-file-path`.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. You can cause the db2cluster_prepare utility to generate a trace file by specifying an absolute path for the trace file using the -t parameter. The db2cluster_prepare utility will create the trace file in the specified location. You can use this trace file to investigate any errors that occur while the GPFS cluster is being created. This message is returned when the db2cluster_prepare command is called with a trace file location specified with the -t parameter and the db2cluster_prepare utility cannot access the specified trace path. The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that the user who runs the db2cluster_prepare command must have access to the path specified with the parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a trace file path that you can access.
DBI1395E	The db2cluster_prepare command failed because the db2cluster_prepare utility cannot write to the following log file path: `log-file-path`.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. The db2cluster_prepare utility generates a log file that you can use to investigate any errors that occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path for the log file using the -log_file_path parameter. The db2cluster_prepare utility will create the log file in the specified location. This message is returned when the db2cluster_prepare command is called with a log file location specified with the -log_file_path parameter and the db2cluster_prepare utility cannot access the specified log path. The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that the user who runs the db2cluster_prepare command must have access to the path specified with the -log_file_path parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a log file path that you can access.
DBI1396E	The db2cluster_prepare command failed because the utility was unable to create necessary temporary files in the following path: `path`.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. The db2cluster_prepare utility generates some temporary files for internal use. This message is returned when the db2cluster_prepare command is unable to create these internal, temporary files. The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that to run the db2cluster_prepare command, you must have access to the named path. A GPFS file system was not created.	Ensure you have permission to access the named path. Ensure that there is enough disk space available to create the temporary files. Run the db2cluster_prepare command again.
DBI1397W	The db2set command failed to set the database manager configuration parameter DB2_ATS_ENABLE value to YES.	The Administrative Task Scheduler (ATS) could not be enabled. Enabling ATS is a prerequisite for using DB2 Text Search.	To use DB2 Text Search, you must enable the Administrative Task Scheduler.
DBI1398E	The db2cluster_prepare command failed because the db2cluster_prepare utility was unable to access the following directory: /tmp.	You can create a IBM General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. The db2cluster_prepare utility generates a log file that you can use to investigate any errors that occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path with the -log_file_path parameter. If you do not use the -log_file_path parameter, the db2cluster_prepare utility will attempt to create a log file named db2prepare_cluster.log in the default directory location /tmp. This message is returned when the db2cluster_prepare command is called without a log file location being specified with the -log_file_path parameter the db2cluster_prepare utility cannot access the directory named /tmp. The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that you must be able to access the directory named /tmp to be able to call the db2cluster_prepare command without specifying the -log_file_path parameter. A GPFS file system was not created.	Respond to this error in one of the following ways: Run the db2cluster_prepare command again, specifying a log file path with the -log_file_path parameter that you can access. Allow the db2cluster_prepare utility to create the log file in the default location by performing the following two steps: Configure the /tmp directory permissions so that you have access to that directory. Run the db2cluster_prepare command again without using the -log_file_path parameter.
DBI1399I	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility.	In a DB2 pureScale environment, all data and logs must be on a General Parallel File System. Existing data and logs that are not on GPFS must be moved to GPFS before upgrading to a DB2 pureScale environment. You can set up a DB2 managed GPFS cluster and file system, so that the data and logs can be moved to it in preparation for the upgrade to a DB2 pureScale environment using the db2cluster_prepare utility.	No response is necessary. This message is for your information only.
DBI1400N	The syntax of the db2licm command is incorrect.	The db2licm tool performs basic license functions. It adds, removes, lists, and modifies licenses installed on the local system. Execute db2licm tool with -l parameter to find out the product identifier for your product: db2licm [-a filename] [-e product-identifier HARD \| SOFT] [-p product-identifier REGISTERED \| CONCURRENT \| OFF] [-r product-identifier] [-u product-identifier num-users] [-c product-identifier num-connectors] [-l] [-v] [-?] The command options are: -a Adds a license for a product. Specify a file name containing valid license information. This can be obtained from your licensed product CD or contact your IBM representative or authorized dealer. -e Updates the enforcement policy on the system. Valid values are: HARD and SOFT. HARD specifies that unlicensed requests will not be allowed. SOFT specifies that unlicensed requests will be logged but not restricted. -p Updates the license policy type to use on the system. The keywords CONCURRENT, REGISTERED, or CONCURRENT REGISTERED can be specified. Specify OFF to turn off all policies. -r Removes the license for a product. After the license is removed, the product functions in "Try & Buy" mode. To get the password for a specific product, invoke the command with the -l option. -u Updates the number of user entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of users. -c Updates the number of connector entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of connectors. -l Lists all the products with available license information, including the product identifier. -v Displays version information. -? Displays help information. When this option is specified, all other options are ignored, and only the help information is displayed.	Enter the command again using the valid parameters.
DBI1401I	Command line DB2 License Manager.	The db2licm tool performs basic license functions. It adds, removes, lists, and modifies licenses installed on the local system. To determine the product identifier for your product issue the db2licm -l command. db2licm [-a filename] [-e product-identifier HARD \| SOFT] [-p product-identifier REGISTERED \| CONCURRENT \| OFF] [-r product-identifier] [-u product-identifier num-users] [-c product-identifier num-connectors] [-l] [-v] [-?] The command options are: -a Adds a license for a product. Specify a file name containing valid license information. This can be obtained from your licensed product CD or contact your IBM representative or authorized dealer. -e Updates the enforcement policy on the system. Valid values are: HARD and SOFT. HARD specifies that unlicensed requests will not be allowed. SOFT specifies that unlicensed requests will be logged but not restricted. -p Updates the license policy type to use on the system. The keywords CONCURRENT, REGISTERED, or CONCURRENT REGISTERED can be specified. Specify OFF to turn off all policies. -r Removes the license for a product. After the license is removed, the product functions in "Try & Buy" mode. -u Updates the number of user entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of users. -c Updates the number of connector entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of connectors. -l Lists all the products with available license information, including the product identifier. -v Displays version information. -? Displays help information. When this option is specified, all other options are ignored, and only the help information is displayed.
DBI1402I	License added successfully.
DBI1403I	License removed successfully.
DBI1404N	Product identifier not found.	The given identifier is invalid, or a license for this product was not found.	Verify the license keys and product identifiers by listing licenses using the db2licm command with the -l parameter.
DBI1405I	License policy type updated successfully.
DBI1406N	Invalid license policy type.	The license policy type that was entered was not valid for the product specified.	Please enter a valid license policy. Options are: CONCURRENT REGISTERED CONCURRENT REGISTERED OFF
DBI1407N	Invalid license certificate file.	License certificate file is not in the correct format.	Enter the name of a file with the correct license certificate format.
DBI1408N	The file `file-name` could not be opened.	The file is not found or access to the file is denied.	Enter the name of a file that exists and can be opened and try the command again.
DBI1409N	Invalid enforcement policy type.	The enforcement policy type specified is not valid for this product.	Please enter a valid enforcement policy type that is supported by the specified product.
DBI1410I	Concurrent entitlements updated successfully.
DBI1411I	Enforcement policy type updated successfully.
DBI1412W	A hard stop enforcement policy stops the use of the product by unlicensed users when licensing infractions have been exceeded.
DBI1413W	A soft stop enforcement policy logs license infractions, but allows unlicensed users to still use the product.
DBI1414I	The db2ls command is preparing and checking the installed DB2 copies on the system.
DBI1415I	Checking active database manager instances on AIX system workload partitions (WPARs) `workload-partition-list` for the related DB2 copy.
DBI1416N	The license could not be added automatically. Return code: `return-code`.	You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command.	Add the license manually by using the db2licm command.
DBI1417N	The specified license could not be removed. Return code: `return-code`.	You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command. This message is returned when a license cannot be removed.	Verify that the license for this product exists by using the db2licm command.
DBI1418I	The number of licensed processors on this system has been updated successfully.
DBI1419N	There was an error updating the number of licensed processors.	The return code is "<return-code>".
DBI1420N	This product does not support this type of license policy.	The license policy specified does not apply to this product or is not supported.	Please enter a valid license policy.
DBI1421N	This product specified is not installed on this system.	You can not configure a license policy for a product until the product is installed.	Install the product before running this command or specify the correct product identifier. To list the products install on the system issue db2licm -l command.
DBI1422N	The number of concurrent entitlements was not updated.	The return code is "<return-code>".	Please ensure the concurrent policy is enabled for this product.
DBI1423N	This option requires the creation of an instance.	Features that are required to perform this action are only accessible once an instance has been created.	Please create an instance and issue this command again.
DBI1424N	An unexpected error occurred while accessing processor information.	The return code is "<return-code>".	None.
DBI1425E	The license for the OLAP server cannot be updated because the OLAP processes are currently active.	The database manager cannot update the license for the OLAP server while the OLAP server is running.	To update your OLAP license, stop all OLAP processes and reinstall this license.
DBI1426I	This product is now licensed for use as specified in the License Acceptance and License Information documents pertaining to the licensed copy of this product. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE ACCEPTANCE AND LICENSE INFORMATION DOCUMENTS, LOCATED IN THE FOLLOWING DIRECTORY: `dir-name`
DBI1427I	This product is now licensed for use as specified in the License Acceptance and License Information documents pertaining to the evaluation ("Try and Buy") copy of this product. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE ACCEPTANCE AND LICENSE INFORMATION DOCUMENTS, LOCATED IN THE FOLLOWING DIRECTORY: `dir-name`
DBI1428N	There was an error updating the number of licensed processors.	The number of licensed processors entered exceeds the number of maximum licensed processors allowed for this product.	Please enter number of licensed processors that does not exceed the defined maximum. If the number of processors on your system exceeds the maximum number of processors allowed for this product, please contact your IBM representative or authorized dealer.
DBI1429N	This product does not support this combination of license policies.		Please enter a valid combination of license policies. For example, you can specify "CONCURRENT REGISTERED" as a valid combination.
DBI1430N	The license could not be added because the license date is greater than operating system date.	You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command. This message is returned when a license could not be added because the date in the certificate file is later than the current operating system date.	Verify that the license start date in the certificate file precedes the current date on the operating system.
DBI1431N	This user does not have sufficient authority to perform the specified action.	This program can be run only under the root user ID or a user ID with SYSADM authority.	Login with a user ID that has permission to run this command.
DBI1432N	The license could not be added because this product has used the maximum number of evaluation licenses: `num-licenses`.	This product has used the maximum number of evaluation licenses.	Run this command again with a permanent license key.
DBI1433N	The number of license entitlements was not updated.	The specified number of license entitlements is not in the valid range.	Run this command again using a valid number of license entitlements.
DBI1434N	The license entry was added, however this license entry is not active.	The installer failed to activate this license entry, therefore the database product will run with the previous license configuration until this license is activated.	Issue the command again. If the operation continues to fail, contact IBM software support.
DBI1435E	Error Opening DB2 First Steps. Cannot find supported Web browser.	DB2 First Steps requires a supported Web browser.	Install one of the following Web browsers: Internet Explorer 6.0 and up Mozilla 1.7 and up Firefox 2.0 and up When using Windows operating systems, set the default browser to your choice from the previous list.
DBI1437E	The db2cluster_prepare command failed because no value was specified for the -t parameter.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. You can cause the db2cluster_prepare utility to generate a trace file by specifying an absolute path for the trace file using the -t parameter. The db2cluster_prepare utility will create the trace file in the specified location. You can use this trace file to investigate any errors that occur while the GPFS cluster is being created. This message is returned when the db2cluster_prepare command is called without a value specified for the -t parameter. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a value for the -t parameter.
DBI1438E	The db2cluster_prepare command failed because no value was specified for the parameter named -l.	You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility. The db2cluster_prepare utility generates a log file that you can use to investigate any errors that might occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path with the parameter named -l. If you use the parameter named -l, the db2cluster_prepare utility will create the log file in the specified location. This message is returned when the db2cluster_prepare command is called without a value specified for the parameter named -l. A GPFS file system was not created.	Run the db2cluster_prepare command again, specifying a value for the parameter named -l.
DBI1439W	The option -immediate was used when running db2set, but the variable specified cannot be updated immediately	The registry was successfully updated with the new value, however, it is never possible for the change to the variable specified by the db2set -immediate call to take effect immediately. The -immediate option has been ignored.	Do not supply the -immediate option when updating this specific variable.
DBI1440W	A db2set -immediate call was made, the offline registry was successfully updated, but db2set could not attach to the instance	Although the offline registry was updated successfully, the value cannot be applied immediately by one or more members because db2set could not attach to the instance.	Try attaching to the instance explicitly and re-run the command and verify that all members of the instance are healthy.
DBI1441W	A db2set -immediate call was made but the dynamic update failed on one or more hosts or members	The offline registry was successfully updated, and the registry update has been made immediately on all of the hosts or members db2set could access. On the hosts or members that db2set could not access, however, the setting for the variable specified could not be applied immediately.	Make sure that all members can be accessed from the host where the command was issued and re-run the command or try attaching to each host or member explicitly and re-run the command. Alternatively, all members will see the changes the next time they restart.
DBI1442W	Some variables governed by the aggregate variable `aggregate_name` were updated dynamically, although some variables it governs do not support an immediate change.	The aggregate registry variable was successfully updated immediately. Some of the variables governed by the aggregate variable were changed dynamically, but other variables governed by the aggregate variable require the instance to be restarted to take effect.	Restart the instance for all of the variables governed by this aggregate registry variable to take effect.
DBI1443W	One or more registry variables meant to take effect for the whole instance have different values on different hosts.	On the Windows operating system, registry variables are stored within the operating system registry of each host. Currently at least one registry variable has been set to a number of different values across hosts. It is highly recommended to keep each registry variable set consistently on all hosts.	Make sure that all DB2 registry variable settings are consistent on all hosts and re-run the command.
DBI1444E	The db2ls command cannot be found in the expected directory `directory-name`.	The database product installation path passed to the db2ls command with the -b option must be the location of a copy with DB2 Version 9 or later installed.	Specify a database product installation path of a copy with DB2 Version 9 or later installed.
DBI1445E	The -b install-path option is mandatory when the -q option is specified. For a list of database product installation locations to query, run the db2ls command without the -b and -q options.
DBI1446I	The `%1` command is running.
DBI1447E	A Java Runtime Environment is needed to run the program `program-name`.	The execution of the command requires a Java Runtime Environment (JRE). If IBM Software Development Kit (SDK) for Java is installed with the related DB2 copy, the JRE is found in <DB2DIR>/java/jdk64/jre/bin for 64-bit Linux systems, or <DB2DIR>/java/jdk32/jre/bin for 32-bit Linux systems, where <DB2DIR> represents the installation path of the related DB2 copy. If a JRE is not found in either path, the program looks for a JRE in either: the current user's ${JAVA_HOME}/jre/bin, or, the default PATH environment. In this case, the JRE must meet the current DB2 version requirements.	Install the IBM Software Development Kit (SDK) for Java and rerun the program.
DBI1448E	An error occurred during the creation or removal of an entry on the main menu. Log file: `log-file-name`.	On Linux operating systems, main menu entries for database tools can be created and removed manually or automatically. Main menu entries for database tools, such as db2fs, can be created manually by running the db2addicons command, or created automatically when some commands are run. These main menu entries can be removed manually by running the db2rmicons command, or removed automatically when some commands are run. Errors occurred during either the creation or removal of these main menu entries.	Check the error log file for details and rerun the program.
DBI1449I	Usage: db2addicons [-h]	The db2addicons command creates main menu entries for the database tools, such as db2fs, for the current user. The main menu entries for the database manager tools are created by manually running the db2addicons command, or are created automatically when some commands are run. The only argument for this command is: -h displays the usage information.	Enter the db2addicons command again without any argument.
DBI1450I	Usage: db2rmicons [-h]	The db2rmicons command removes main menu entries for the database tools, such as db2fs, for the current user. The main menu entries for the database tools are removed by manually running the db2rmicons command, or are removed automatically when some commands are run. The only argument for this command is: -h displays the usage information.	Enter the db2rmicons command again without any argument.
DBI1451E	A database manager instance environment is not set to run the program `program-name`.	On Linux operating systems, the database manager instance environment needs to be set for the current user before the command can be run. An instance environment can be setup with: <Instance_HOME>/sqllib/db2profile (for Bourne shell and Korn shell users), or <Instance_HOME>/sqllib/db2chsrc (for C shell users) where <Instance_HOME> is the instance owner's home directory.	Set up the database manager instance environment and rerun the program.
DBI1452E	You do not have the authority to install the network version of the DB2 Information Center. Installing the product named `product-name` requires root authority. You can find the workstation version of the DB2 Information Center in the subdirectory called "workstation" of the folder located at `folder-location`, at IBM Passport Advantage, or at the following URL: www.ibm.com/support/docview.wss?rs=71&uid=swg27009474. You do not need to have root authority to install the workstation version of the DB2 Information Center.
DBI1453E	Invalid component name `component-name`	Specified component name is either incorrect or misspelled. If the component name is correct, this component name might not be valid on this operating system or platform.	Check to see if the component name is a valid DB2 component for the current operating system or platform.
DBI1454E	`instance-name` is a DB2 pureScale instance. Validation on this type of instance is not supported in the current DB2 release.	The db2val command does not support validation on a DB2 pureScale instance.	No action required.
DBI1455W	The information on instance `instance_name` will not be added to the generated response file.	The specified instance is a DB2 pureScale instance. When the db2rspgn command is run against a DB2 pureScale instance the information on the specified instance is not added to the generated response file and the instance profile is not created.	No action required
DBI1456W	The `command-name` command failed because it was executed on a member that is not the coordinating member of the instance `instance-name`.	The command is only supported on the coordinating member of the instance.	Run the command on the coordinating member of the instance.
DBI1457E	The database product or feature could not be uninstalled. To uninstall, the following list of instances must be dropped: `instance-list`.	The product or feature must not be associated with any instances when it is uninstalled. The db2ilist command is used to list installed instances.	Drop the offending instances using the db2idrop command and re-run the db2_deinstall command.
DBI1458E	The db2iupdt or db2iupgrade commands are not supported on a non instance-owning member.	The db2iupdt command can be used to update an instance to a higher level within a release. The db2iupgrade command upgrades an instance to a DB2 copy of the current release from a DB2 copy of a previous release. The instance update and upgrade are only supported on the instance-owning member.	Run the db2iupdt or db2iupgrade command on the instance-owning member.
DBI1459E	The db2_deinstall command failed because some DB2 database files are in use.	You can uninstall database products, features, or languages using the db2_deinstall command. Before you can uninstall any part of a non-root installed database manager instance, all operating system processes and resources for that instance must be release. This message is returned when an attempt is made to uninstall a non-root installed instance while some DB2 database-related system resources have not been freed. For example, this message can be returned for the following reasons: DB2 database-related operating system processes are still running DB2 database-related libraries are still loaded in memory	Stop the database manager using the db2stop force command Run the db2_deinstall command again
DBI1460E	Command parameter combination is invalid.	When using the db2setup command, if the -c parameter is specified to validate the contents of a response file, the -r parameter indicating the response file must also be specified.	Rerun the db2setup command specifying both the -c and -r parameters.
DBI1461E	The distributed fix pack installation failed because the -H parameter was specified with the installFixPack command, but the installer detected no DB2 pureScale components in the base copy of the database product.	You can update the installed database products to the same level by using the installFixPack command. In DB2 pureScale environments only, you can update multiple hosts in a DB2 cluster by specifying the -H parameter with the installFixPack command. This message is returned when the -H parameter is specified with the installFixPack command in an environment that is not a DB2 pureScale environment.	Rerun the installFixPack command without the -H parameter.
DBI1462I	The db2setup command is validating the response file provided. This can take several minutes.	Validation process in progress.	No action required.
DBI1463E	The response file validation failed. Log file: `path_to_logfile`	Invalid entries were detected in the response file. For more details, refer to the log file.	Correct the response file errors and rerun the command.
DBI1464E	Conflicting installFixPack command parameters specified. Parameters: `conflicting-parameter-list`.	There are specific parameters related to specific actions in the installFixPack command. Some parameters cannot be specified for some actions. This message is returned when two parameters of the installFixPack command cannot be specified together because the syntax does not support such usage.	Review the syntax of the installFixPack command and re-issue the command with the correct parameters.
DBI1465E	An error occurred in the host list file. Host file: `host-file-name`.	An error was detected in the specified host list file. The error can occur for any of the following reasons: the file does not exist, the file is not readable, the file is empty or contains an invalid character, the path name is not specified, or the HOST keyword is not valid.	Check the contents of the specified host list file, and rerun the command.
DBI1466E	Instance validation failed. Instance name: `instance_name`. Reason code: `reason_code`. Current host name: `host_name`.	The specified reason code indicates one of the following errors occurred: 1 The IBM Reliable Scalable Cluster Technology (RSCT) peer domain is not online 2 The IBM General Parallel File System (GPFS) cluster is not online 3 At least one db2 cluster services alert is indicated	Depending on the specified reason code, take the appropriate action: 1 Bring the RSCT peer domain online by entering the following command: db2cluster -cm -start -domain domain_name 2 Start the GPFS cluster by entering the following command: db2cluster -cfs -start -host host_name 3 Clear all alerts by running the following command: db2cluster -list -alert
DBI1467N	The db2ndrop command was not able to drop the multiple partition instance member 0.	The db2ndrop command is used to drop a database partition server from an instance that has no databases. The db2ndrop command cannot drop the instance owning database partition server (0). To drop a database partition server that is assigned to the logical port 0 from a machine that is running multiple logical database partition servers, all other database partition servers assigned to the other logical ports must be dropped first. Each database partition server must have a database partition server assigned to logical port 0.	Use the db2idrop command to drop the multiple partition instance member 0, after the rest of members have been dropped using the db2ndrop command.
DBI1468E	Instance validation failed. Instance: `instance_name`. Log file: `path_to_logfile`. Hosts: `host_name`.	The validation failed on the specified hosts.	Check the log file for more details.
DBI1469W	The DB2 copies of the hosts participating in the instance do not have the same code level or install path. Instance: `instance_name`.	The instance might be in the rolling update stage.	Update your instance to the same level and the same path on all participating hosts in the instance using the db2iupdt command.
DBI1470E	The instance validation failed on host `host_name`. Reason code = `reason_code`.	The specified reason code indicates one of the following errors occurred: 1 Validation on the specified host did not finish before time-out. 2 The instance is configured to use passwordless SSH and passwordless SSH communication between the specified host and other hosts failed. 3 Instance shared directory cannot be accessed from the given host or is not shared between the given host and the local host. 4 Some files in the instance directory are damaged. The symbolic links of the files are not pointing to the instance shared directory. 5 The specified host is offline in the RSCT peer domain. 6 The specified host is stopped in the GPFS cluster. 7 Installation file validation failed for the DB2 copy on the specified host.	Depending on the specified reason code, take the appropriate action: 1 Rerun the db2val command on the specified remote host. 2 To use passwordless SSH, configure passwordless SSH access for the instance owner on the host machines. 3 The instance shared directory must be accessible from the specified host. The directory path must be accessible from all the hosts, and must have read/write permission. 4 To fix the symbolic links, run db2iupdt <instance_name> as root. 5 Bring the host online by running the following command: db2cluster -cm -start -host <host-name> 6 Bring the host online by running the following command: db2cluster -cfs -start -host <host-name> 7 Check the log file for more details.
DBI1471I	db2setup validated the response file successfully. Log file: `path_to_logfile`.	The validation process completed successfully.	Check the log file for details.
DBI1472W	The db2val -d parameter is deprecated. The deprecated parameter is replaced by the -t `trace_file` parameter.	The deprecated parameter will be removed from a future release.	Replace the deprecated parameter with the new parameter in any scripts or applications.
DBI1473W	Parameter `deprecated-parm-name` is deprecated. The deprecated parameter is replaced by new parameter `new-parm-name`. Command: `command-name`.	The deprecated parameter might be removed from a future release.	Replace the deprecated parameter with the new parameter in any scripts or applications.
DBI1474E	The instance shared mount point path is invalid. Command: `command-name`.	In the specified command, the path specified for the instance shared mount point must be a new path and must not be a sub-directory of an existing GPFS file system.	Rerun the command specifying a new path for the instance shared mount point.
DBI1475E	The installation failed because only the root user is permitted to install DB2 pureScale.	To install the DB2 pureScale Feature you must be logged in as the root user. Installation is restricted to the root user because components required by DB2 pureScale affect shared resources on the system.	Review the prerequisites for DB2 pureScale before attempting another installation.
DBI1476E	The db2_install command failed because the option "-f PURESCALE" was specified and the following option that is not supported with the "-f PURESCALE" option was specified: `option`.	This message is returned when the db2_install command is issued with the "-f PURESCALE" option and another option is also specified that is not supported with the "-f PURESCALE" option.	Respond to this message in one of the following ways: To include DB2 pureScale in the installation, rerun the db2_install command without specifying the option that is not supported with the "-f PURESCALE" option. If you do not want to install DB2 pureScale, rerun the db2_install command without specifying the "-f PURESCALE" option.
DBI1477E	The db2cluster_prepare command failed because of a syntax error. Reason code: `reason-number`.	The syntax entered was invalid. See the corresponding reason code for an explanation of the cause of the error. The -cfs_takeover and -instance_shared_dev option are mutually exclusive, when specifying one option for db2cluster_prepare the other cannot be used. The db2cluster_prepare command failed because one or more parameters were specified multiple times. The db2cluster_prepare command failed because no value was specified for the -instance_shared_dev parameter. The db2cluster_prepare command failed because no value was specified for the -t parameter. The db2cluster_prepare command failed because no value was specified for the parameter named -l. The db2cluster_prepare command failed because no value was specified for the -instance_shared_dev parameter.	Rerun the db2cluster_prepare command with the correct syntax. For the correct syntax, see the command reference or run the command with the "-?" option, by typing "db2cluster_prepare -?".
DBI1478E	The GPFS binary update failed. Installation detected one or more GPFS efixs that were not originally installed by the database product. Installation cannot proceed until these efixes are manually removed. efixes: `efix_list`	The GPFS efixes detected by the installer were not installed by the database product. The installer can only remove efixes installed as part of a database product installation. The specified efixes must be removed manually.	Manually remove the efixes, and rerun the command.
DBI1479N	The syntax of the DB2NDROP command is incorrect.	The DB2NDROP utility drops a node from a partitioned system. `DB2NDROP /n:node [/i:instance]` The command options are: /i Specify the instance if different from the default/current instance	Issue the DB2NDROP command with one of the valid command options.
DBI1480N	Node `node` not found for instance `instance`.	DB2NDROP failed because the node does not exist.	Ensure the node number is correct and reissue the command.
DBI1481W	Node `node` for instance `instance` has been deleted.	The DB2NDROP processing has completed successfully.	No further action is required.
DBI1482E	Syntax error, the db2_deinstall command options to skip the removal and remove the same feature are mutually exclusive.	The '-s' option skips the removal of a feature, and the '-F feature-name' option specifies that feature feature-name, should be removed. These two options must not contain the same feature identifier.	If you want to remove the feature, rerun the command without the '-s feature-id' option. If you want to skip the removal of the feature, rerun the command without the '-F feature-id' option.
DBI1483E	Syntax error, the '-F GPFS' option is not valid.	The GPFS feature cannot be removed with '-F GPFS' option of the db2_deinstall command. By default, the GPFS feature will be removed with the 'db2_deinstall -a' command when you remove the last DB2 copy and GPFS is not still in use, if GPFS was installed by the database product installer.	Rerun the db2_deinstall command without the '-F GPFS' option. See the uninstall documentation for more information.
DBI1493W	A Reliable Scalable Cluster Technology (RSCT) peer domain was detected, IBM Tivoli System Automation for Multiplatforms (SA MP) cannot be removed by the DB2 uninstall process.	If an RSCT peer domain is present, the Tivoli SA MP component is not uninstalled with the DB2 copy to prevent adverse behavior of other copies or applications, which might depend on the peer domain or Tivoli SA MP.	If there are no other DB2 copies or applications dependant on Tivoli SA MP component and the component is no longer required, remove it.