DBA0000-0999

DBA Message ID	Message	Explanation	User Response
DBA0000I	The function completed successfully.	This message is for your information only.	No action is required.
DBA0001E	An internal error occurred when allocating memory.	An internal error occurred when allocating memory. The application is terminated.	Try closing some applications to release memory. If the problem persists, contact IBM Service.
DBA0002E	An internal error occurred. Unexpected input was received from the request.	An unexpected input value was received from the request. The application is terminated.	Contact IBM Service.
DBA0003E	An inconsistency in the table definition was detected when processing the alter request.	When processing an alter table request, an inconsistency was detected between the last known table definition and the table definition fetched from the database. The table definition might have changed outside of the context of the administration tool. The table cannot be altered. The request is terminated.	Select the "Refresh" action on the "Tables" pop-up menu to get an updated list of tables from the database. Try altering the table again.
DBA0004E	An error occurred when validating a connection to a database.	An invalid connection was detected. A problem can occur if the server is brought down, the currently held connections are no longer valid, and a new connection cannot be obtained. The request is terminated.	Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again. If the action fails again, ensure that your network is operating for the target system and that the database is up and running on that system. If the network is operational, a system internal error might have occurred. Contact IBM Service.
DBA0005E	An error occurred when validating an attach to an instance.	An invalid connection was detected. The database might have stopped or the connection might no longer exist. The request is terminated.	Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again. If the action fails again, ensure that your network is operating for the target system and that the database is up and running on that system. If the network is operational, a system internal error might have occurred. Contact IBM Service.
DBA0006E	An error occurred when validating a handle for a persistent database connection or instance attach.	An invalid connection was detected. The database might have stopped or the connection might no longer exist. The request is terminated.	Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again. If the action fails again, ensure your network is operating for the target system and that the database is up and running on that system. If the network is operational, a system internal error might have occurred. Contact IBM Service.
DBA0007E	An internal error occurred when setting the context type for connections.	An error occurred when setting the context type for connections established by the application. The application is terminated.	Contact IBM Service.
DBA0008E	An internal error occurred. An unexpected list type was requested.	The type of object to be listed was not recognized as a valid type by the application. The application is terminated.	Contact IBM Service.
DBA0009E	An internal error occurred. An unexpected request type was received.	The type of request to be performed was not recognized as a valid type by the application. The application is terminated.	Contact IBM Service.
DBA0010E	An internal error occurred. An unexpected object type was detected.	The type of object to be processed was not recognized as a valid type by the application. The application is terminated.	Contact IBM Service.
DBA0011E	There are too many open connections.	The maximum number of open database connections was reached. The request is terminated.	Either: Disconnect from other databases and connect to the database you want. Select the "Disconnect" action in the pop-up menu of the databases from which you want to disconnect. Select the "Connect" action in the pop-up menu of the database to which you want to connect. Update the configuration parameter to increase the number of connections allowed.
DBA0012E	Unable to allocate a connection handle.	An error occurred when attempting to allocate a connection handle. The application is terminated.	Contact IBM Service.
DBA0013W	The maximum number of objects that can be listed was reached.	The maximum number of objects that can be listed by the application was reached. The maximum number is 20,000.	None
DBA0014E	An internal error occurred. An unexpected drop type was requested.	The type of object to be dropped was not recognized as a valid type by the application. The application is terminated.	Contact IBM Service.
DBA0015E	An internal error occurred. A latch request failed.	A latch request failed. The application is terminated.	Contact IBM Service.
DBA0016E	An internal error occurred. An unlatch request failed.	An unlatch request failed. The application is terminated.	Contact IBM Service.
DBA0017E	No error information is available. See the administration tools log.	No error information can be displayed.	See the administration tools log for error information.
DBA0018E	The Administration Server is not started. Start the Administration Server and try the action again.	The Administration Server is not started.	Start the Administration Server using the DB2ADMIN START command on the target system and try the action again.
DBA0019E	The object `object-name` is in use. Try the action again at a later time.	The object on which the action was requested or a related object is already being used in another action. Modifications to the object or a related object might be in progress. The requested action cannot be performed at the same time as the current action. Examples: If a table is being altered, a request to rename the same table will not be allowed until the interaction with the Alter window is complete. However, a request to sample the contents of that table is allowed. A request to drop an object (such as a table) will not be allowed if any other actions are pending on related objects (such as the database, views, or triggers). The action is not performed.	Try the action again at a later time when the object is available.
DBA0020E	An error occurred opening the administration tools trace file.	An error occurred opening the administration tools trace file.	Contact IBM Service.
DBA0021E	An error occurred writing to the administration tools trace file.	An error occurred writing to the administration tools trace file.	Contact IBM Service.
DBA0022W	An error occurred closing the administration tools trace file.	An error occurred when attempting to close the administration tools trace file. Processing continues.	Ensure that the administration tools log file was specified correctly.
DBA0023W	An error occurred opening the administration tools log file.	An error occurred when attempting to open the administration tools log file. Processing continues.	Ensure that the administration tools log file was specified correctly.
DBA0024W	An error occurred writing to the administration tools log file.	An error occurred when attempting to write to the administration tools log file. Processing continues.	Ensure that the administration tools log file was specified correctly and can be written to.
DBA0025W	An error occurred closing the administration tools log file.	An error occurred when attempting to close the administration tools log file. Processing continues.	Ensure that the administration tools log file was specified correctly.
DBA0026E	An internal administration tools error occurred.	An unrecoverable error occurred.	Contact IBM Service.
DBA0027E	An internal error occurred. A lock contention in the administration tools was detected.	Lock contention in the administration tools was detected.	Contact IBM Service.
DBA0028I	The current administration tools session will be terminated due to an unrecoverable error.	A severe internal error occurred.	Contact IBM Service.
DBA0029C	The application programming interface `program` did not complete successfully for object `name` with reason code `name`. Try again or contact your local support.	An application programming interface call did not complete.	Try the operation again or contact your system administrator.
DBA0030E	An error occurred while attempting to connect to database `name`.	The requested operation could not complete because it requires a connection to database `name`. The connection was not successful.	Make sure the database is accessible. Try explicitly connecting to the database using the connect action on the database pop-up menu. A common error on connection is an invalid userid and password. Make sure you have supplied the proper userid and password. Try the operation again or contact your system administrator.
DBA0031E	An error occurred while attempting to attach to instance `name`.	The requested operation could not complete because it requires an attachment to the instance `name`. The attachment was not successful.	Make sure the instance is accessible. Try explicitly connecting to the instance using the connect action on the instance pop-up menu. A common error on connection is an invalid userid and password. Make sure you have supplied the proper userid and password. Try the operation again or contact your system administrator.
DBA0032C	An error occurred while attempting to load DLL `name`.	Either the dynamic link library `name` was not found or an error occurred while reading the file.	Verify that the DLL is installed and undamaged, and its location is part of the LIBPATH parameter in the CONFIG.SYS file.
DBA0033C	`name` cannot be dropped because it is currently in use by the administration tools. Close some windows and retry the command.	Either the object `name` you selected to drop, or an item that is owned by the object you selected to drop, is still being used by another administration tool. For example, you might have and ALTER table window open for a database that you are trying to drop. In this case, you cannot drop the database until you close its ALTER table window.	Close all the windows using the object you selected, or close all the windows using items owned by that object, and then retry the command.
DBA0034C	`name` cannot be removed because it is currently in use by the administration tools. Close some windows and retry the command.	Either the object `name` you selected to remove, or an item that is owned by the object you selected to remove, is still being used by another administration tool. For example, you might have and ALTER table window open for a database that you are trying to remove. In this case, you cannot remove the database until you close its ALTER table window.	Close all the windows using the object you selected, or close all the windows using items owned by that object, and then retry the command.
DBA0035C	The `operation` operation cannot be performed because the object `name` is currently in use by the administration tools. Close some windows and retry the command.	This operation `operation` requires `name` to be in a `name` state.	Make sure all other pending operations on the selected object are complete, and then retry the command.
DBA0036I	The database configuration was successfully updated. All applications must disconnect from database `name` before the changes come into effect. If a backup has already been taken it is recommended to take another backup of the database in order to pick up the new configuration values.	The database configuration was successfully updated, but the active database configuration cannot be changed until all applications are disconnected from the database. Once all applications are disconnected, the changes will come into effect with the first connection to the database.	Ensure that all applications are disconnected from the database, and then reconnect to the database.
DBA0037I	The instance configuration was successfully updated. The instance `name` must be stopped before most changes come into effect.	The instance configuration was successfully updated. Changes to the configuration parameter "dftdbpath" take effect immediately. For the remaining configuration parameters, the changes do not take effect until all applications have disconnected from the database, and the instance is successfully stopped and started again.	To make all changes take effect, ensure that all applications have disconnected from the database, stop the instance, and then start it again. You can stop the instance by issuing the db2stop command. You can then start the instance by issuing the db2start command.
DBA0039W	There are currently database objects locked or database connections in use. Continue shutdown?	The database objects in the Control Center are locked when actions, such as Alter Table, are taken against them. Other actions will maintain connections to the database that are required to complete the task.	If you choose to continue with the shutdown, then all locks and connections are forced and the tools will shut down. It can be dangerous to do so, however, because forcing some actions (like Restore Database) halfway through the task can leave the database in a corrupted state. It is safest to first go back to the DB2 tools and make sure there are no database operations outstanding.
DBA0040W	Shutting down will stop the Snapshot monitor. Continue shutdown?	Snapshot monitoring has been started on one or more database objects and to continue the monitoring, you must have the DB2 tools running.	Choose to continue the shutdown only if you no longer require the Snapshot monitor.
DBA0041I	The requested operation could not be performed because the DB2 Administration Tools is an untrusted applet.	Applets loaded over the network are usually considered to be untrusted. Different Web browsers and applet viewers may impose different restrictions on untrusted applets including most local system operations (For example, read files, write files, and print files).	Consult your system administrator and see if these restrictions can be relaxed or customized.
DBA0042I	Do you want to clear the setting for the userid and password that was used to connect to this database.	If you choose to clear this setting, you will prevent unauthorized access to this database from this workstation. However, you will be prompted to enter the correct userid and password the next time you connect to this database.	Click on Yes to clear the userid and password setting. Click on No to save the userid and password setting until you exit the Control Center.
DBA0043I	The command has not been executed.	The operation did not occur and has been aborted.	Resubmit the command.
DBA0044N	The Java Virtual Machine heap size is not large enough to handle your request.	If your request is accessing a large amount of data, this is probably an expected occurrence. Note that if your request is not accessing a large amount of data, this occurrence may indicate a memory problem.	Increase the size of the Java Virtual Machine heap and restart the application. To increase the Java Virtual Machine heap size include the -Xmx<size> option when invoking the application, where <size> is the maximum size in bytes. Optionally specify a different unit of measurement by appending the letter k or K to indicate kilobytes, or m or M to indicate megabytes. For example, to start the Control Center with a Java Virtual Machine heap size of 128 megabytes, enter: db2cc -Xmx128m.
DBA0045N	At least one required field in the Register XSR dialog is incomplete.	All required fields must be filled in before the XSR object registration process can be completed by the Register XSR dialog.	Verify that all required fields have been completed in the Register XSR dialog and try again.
DBA0046N	A file required for XSR object registration cannot be found.	When you add XSR objects through the Register XSR dialog, the files you reference must be available during the registration process. At least one file cannot be found.	Verify that all files you reference during the XSR object registration process are available and try again.
DBA0047N	The requested native XML data store functionality is not available on this database.	This message is expected behavior when you attempt to use the XML functionality supported by a native XML data store administration tool against a database which does not support native XML data store. Note that XML Extender is not part of the native XML data store.	If the DB2 instance does not support native XML data store functionality, no user response is necessary. You cannot use the XML functionality supported by your native XML data store administration tool against this database. For further information on how to use the supported native XML data store functionality, visit the DB2 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9index.jsp and search for "native XML data store" and "overview".
DBA0048N	Automatic storage cannot be added to this database.	An attempt has been made to access the 'Add Automatic Storage' window for a non-automatic storage database.	To add storage for a non-automatic storage database, select a table space listed in the Table Spaces folder. Right click on the table space name and select "Alter..." . The Alter Table Space notebook opens. Select the Containers tab to add storage for your database.
DBA0049N	Registration with the XML schema repository (XSR) failed because there was an error reading or processing the selected file.	The Register XSR notebook only supports certain file extensions when you are adding objects to the XSR. If you are using a supported extension, then the error occurred during the processing of the file.	The supported extensions are .dtd (XML DTDs), .mod (XML DTD Modules), .ent (External Entities), and .xsd (XML Schemas). If you are using a supported extension, try validating the file contents using an XML editor. If there are no errors, try the registering the object again. If registration still fails, contact IBM Service for additional help.
DBA0099N	The Java Virtual Machine heap size is not large enough to service your request.	If your request is accessing a large amount of data, this is probably a normal response. However, if your request is not accessing a large amount of data, this may indicate a memory problem.	Modify the maximum size of the Java Virtual Machine heap with the -Xmx<size> option when invoking the program. Specify the maximum size, in bytes. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. For example, db2cc -Xmx128m If the problem persists, contact IBM Service.
DBA0100I	Control Center is updating node directory information for instance - `instance`. Incorrect information is being corrected. The current request cannot be performed.	The Control Center detected that the nodetype changed at the instance and is recataloging the instance based on the new information. Depending on the nodetype value for the instance, actions from the Control Center may be different.	If available, try the request again.
DBA0101W	Entries specified in the exception list will not be used. Do you want to continue?	The Nodes Contain Exceptions check box is deselected, but exception containers are specified in the List Exception dialog.	Click on Yes to clear the exception containers list, or click on No or Cancel to reselect the Nodes Contain Exceptions check box.
DBA0102W	Unable to detect nodetype for instance - `instance`. Reason Code: `reason-code`.	Nodetype is a database manager configuration parameter that identifies whether the instance consists of a single or multiple database partition servers. Discovery tries to resolve the nodetype value for you. This distinction between instances is required because actions in the Control Center can be different between single and multiple database partition servers environments. If the reason code is -1, discovery could not map the catalogued instance to a valid DB2 instance. All other reason codes map to a valid SQL message. Check the help for the corresponding SQL message.	Discovery has the following requirements: DB2 Administration Server must be set up and running at the remote instance you want to catalog or access. Ensure the instance is listed in the registry. Issue db2set -l from the host you are cataloging. The following global DB2 Registry values must be set: DB2SYSTEM DB2ADMINSERVER The following instance DB2 Registry values must be set: DB2COMM The following administration server configuration parameters must be set: DISCOVER = KNOWN and DISCOVER_COMM = null or DISCOVER = SEARCH and DISCOVER_COMM = protocol (for example, TCPIP ) Verify the setting of these registry values by entering db2set -all.
DBA0103W	Changes made to the configuration parameter values will not be used. Do you want to continue?	Another database partition was selected, but the changes to the configuration parameters apply to the previously selected database partition.	Click on Yes to obtain the configuration parameter values for the next database partition and discard the changes that were specified for the previously selected database partition.
DBA0113E	Exception containers are specified, but not all nodes in the database partition group are included. No containers are specified for the following nodes: `node-list`.	The specified exception containers have no common container. Because no common container is specified, the exception container must be defined at every node in the database partition group.	Click on OK to add containers to the specified nodes.
DBA0114W	Control Center detected incorrect node directory information for instance - `instance`. Incorrect information is being corrected. Please exit and restart the Control Center. The current request cannot be performed.	The Control Center detected that the nodetype changed at the instance.	Exit the Control Center and restart it.
DBA0115I	Node directory information has been corrected for this instance. Instance `instance` should be refreshed.	Because the cataloged information for the instance is updated, the displayed objects and actions may not be correct.	Select the "Refresh" action from the instance pop-up menu to update the Control Center, then try the request again.
DBA0116I	The operation cannot be performed by the JDBC server at this time. Retry this operation later.	The JDBC server is currently busy with an existing operation and cannot perform the user operation.	Wait until the JDBC server completes the existing operation and retry the operation.
DBA0117W	Database partition information could not be retrieved. Reason code = `reason-code`, object = `object`.	Function which relies on successful retrieval of database partition information will be disabled or removed. This may include menu items as well as actual dialog function.	Make sure that the DAS is started at the server where the object exists. If the DAS is started, then treat the return code as a DAS error and continue troubleshooting.
DBA0200E	An attempt to open or read from file `filename` failed. Error code = `error-code`.	An attempt was made to either open or read from a file using the Database Administration Server (DAS). The attempt failed.	Verify that the DAS is running, and that the file exists and has read permission for the userid associated with the DAS. If the problem persists, contact your IBM service representative with the corresponding file name and error code.
DBA0201E	An attempt to open or write to file `filename` failed. Error code = `error-code`.	An attempt was made to either open or write to a file using the Database Administration Server (DAS). The attempt failed.	Verify that the DAS is running, and that the file system is not full and has write permission for the userid associated with the DAS. If the problem persists, contact your IBM service representative with the corresponding file name and error code.
DBA0202E	An attempt to open or read from file `filename` failed. Error code = `error-code`.	An attempt was made to either open or read from a file. The attempt failed.	Verify that the file exists and has appropriate read permission. If the problem persists, contact your IBM service representative with the corresponding file name and error code.
DBA0203N	An attempt to open or write to file `filename` failed. Error code = `error-code`.	An attempt was made to either open or write to a file. The attempt failed.	Verify that the file system is not full and that it has appropriate write permission. If the problem persists, contact your IBM service representative with the corresponding file name and error code.
DBA0900N	The path `path-name` already exists.	The path `path-name` was specified in the context of a non-existing path, but this path already exists.	Specify a path that does not exist.
DBA0901N	The path `path-name` does not exist.	The path `path-name` was specified in the context of a existing path, but this path either does not exist or it is not accessible.	Specify a existing path which is accessible.
DBA0902E	The file or directory specified by path `path-name` is read-only.	An attempt was made to modify the file or directory specified by path `path-name`, which is currently read-only.	Specify a file or directory which is not read-only.
DBA0903E	The file or directory specified by path `path-name` is currently in use by another application.	An attempt was made to modify or delete the file or directory specified by `path-name`, which is currently in use by another application.	Close all applications accessing the file or directory and retry the operation.
DBA0904E	The file or directory specified by `path-name` is not accessible.	The file or directory specified by `path-name` is not accessible to the current user.	Verify the permissions set on the file or directory allow access to the current user and retry the operation.
DBA0905E	The path or device `name` is not available.	The path or device `name` is not available at this time.	Verify the path or device is still available and retry the operation.
DBA0906E	The directory `directory-name` is not empty.	The directory `directory-name` was specified in the context of an empty directory, but this directory is not empty.	Verify the directory is empty and retry the operation.
DBA0907E	The path `path-name` does not refer to a directory.	The path `path-name` was specified in the context of a directory, but this path does not refer to a directory.	Verify the path specifies a valid directory and retry the operation.
DBA0908E	The path `path-name` is not valid.	The path `path-name` does not refer to a valid path.	Specify a valid path and retry the operation.
DBA0909E	The path `path-name` is too long.	The length of the path `path-name` exceeds the maximum value permitted by the operating system.	Specify a path whose length is within the maximum value allowed by the operating system and retry the operation.
DBA0910E	There is no more space available on the file-system.	There is no more space available on the file-system to permit the operation to complete successfully.	Make sure there is enough space on the file-system to complete the operation and then retry the operation.
DBA0911E	The maximum number of files that can be open has been reached.	The maximum number of files that is permitted to be open by the operating system has been reached.	Close one or more open files and retry the operation.
DBA0912E	The end of the file `file-name` has been reached.	An attempt was made to read or seek beyond the end of the file `file-name`.	Verify the operation is not attempting to read or seek beyond the end of the file and retry the operation.
DBA0913E	A physical I/O error occurred.	An undetermined physical I/O error while accessing the file-system.	Retry the operation. If the problem persists, contact IBM Service.