DBA3000-3999

DBA Message ID	Message	Explanation	User Response
DBA3007W	Are you sure you want to delete the explained statement?	You are about to delete the explained statement. This will delete the rows in the explain tables.	Ensure that you want to delete the explained statement.
DBA3008W	Are you sure you want to delete the explained statements?	You are about to delete the explained statements. This will delete the rows in the explain tables.	Ensure that you want to delete the explained statements.
DBA3009E	A system error occurred. The Visual Explain tool could not continue processing.	An unexpected error occurred causing the operation to stop.	Possible solutions include: Verify that your system has sufficient memory. Where appropriate, stop other programs using the system. If the problem persists, contact your system administrator.
DBA3010E	The explain snapshot has been deleted. Your request cannot be completed.	The explain snapshot that is requested has been deleted from the explain tables.	Regenerate the snapshot.
DBA3011E	This explain snapshot was created using a different version of the database manager from the Visual Explain Tool. Your request cannot be completed.	The explain snapshot was created using a newer version or an older version of the database manager from the Visual Explain Tool. The access plan graph cannot be constructed by the Tool.	Use the same version of the database manager as the Visual Explain Tool to graph the explain snapshot.
DBA3012I	String not found.	The search string is not found in the text being displayed.	None.
DBA3013E	Text is missing. You must specify the text string to be found.	You did not specify a search string.	Specify a search string.
DBA3014E	No selection is made in the list. You must select at least one entry in the list.	You did not make a selection in the list.	Select at least one entry in the list.
DBA3015I	There are no referenced columns associated with this access plan.	There were no columns referenced in the query for the referenced table.	None.
DBA3016I	There are no page fetch pairs statistics associated with this index.	There are no page fetch pairs statistics stored in the catalog table for this index. Refer to the System Catalog Statistics section in the Administration Guide for more details.	None.
DBA3017I	There are no referenced functions associated with this access plan.	This access plan did not require the use of any functions.	None.
DBA3018I	There are no column distribution statistics associated with this column.	There are no column distribution statistics stored in the catalog table for this column. Refer to the System Catalog Statistics section in the Administration Guide for more details.	None.
DBA3019I	There are no indexes associated with this table.	There were no indexes defined on the referenced table at the time of explain and there are no indexes currently defined in the table.	None.
DBA3020E	An error occurred while a COMMIT against the database was being attempted and no SQLCODE can be returned.	An unexpected error occurred.	Contact your system administrator.
DBA3021E	An error occurred while a ROLLBACK against the database was being attempted and no SQLCODE can be returned.	An unexpected error occurred.	Contact your system administrator.
DBA3022E	The Get Database Manager Configuration API passed back a non-zero return code.	An unexpected error occurred causing the operation to stop.	Contact your system administrator.
DBA3023E	The Get Database Configuration API passed back a non-zero return code.	An unexpected error occurred causing the operation to stop.	Contact your system administrator.
DBA3024E	An error occurred while saving to the file `file`.	Possible problems include: The file cannot be opened for write. The file name does not conform to the file system convention.	Possible solutions include: Change the file attribute to read write. Specify the correct file name.
DBA3025E	An error occurred while retrieving from the file `file`.	Possible problems include: The file is not readable. The file does not exist.	Specify the correct file name.
DBA3026E	No printers are installed.	There are no printers installed on your machine.	Install a printer on your machine.
DBA3033I	There are no referenced table spaces associated with this access plan.	This access plan did not reference any database objects contained in a table space.	None.
DBA3034W	The snapshot was created using code page `codepage` but is not converted to the code page of the window running the Visual Explain Tool.	The snapshot of the access plan graph displayed was created on a code page different from the code page of the window running the Visual Explain Tool. Code page conversion is not successful because the snapshot is too large. The access plan graph is displayed without code page conversion. You may not be able to display the current statistics when you open the statistics windows.	Change the code page of the window running the Visual Explain Tool to the same one used to create the snapshot and display the access plan graph again.
DBA3035W	The snapshot was created using code page `codepage` but is not converted to the code page of the window running the Visual Explain Tool. The value of the database manager configuration parameter ASLHEAPSZ is too small.	The snapshot of the access plan graph displayed was created on a code page different from the code page of the window running the Visual Explain Tool. Code page conversion is not successful because the user defined function used to convert between the code pages do not have enough memory to run. The access plan graph is displayed without code page conversion. You may not be able to display the current statistics when you open the statistics windows.	Possible solutions include: Change the database manager configuration parameter ASLHEAPSZ of your server to 512 and display the access plan graph again. Note that the configuration parameter may not take effect until the next time you do a db2start on your server. Change the code page of the window running the Visual Explain Tool to the same one used to create the snapshot and display the access plan graph again.
DBA3036I	Explain tables have been created to process your dynamic explain request.	One or more explain tables have been created under the current user ID. These tables will be used to store the information needed by your dynamic explain request.	None.
DBA3037E	The explain snapshot has been corrupted. Your request cannot be completed.	The explain snapshot that is requested has been corrupted in the explain tables.	Regenerate the snapshot.
DBA3038I	There are no referenced buffer pools associated with this access plan.	This access plan did not reference any database objects contained in a buffer pool.	None.
DBA3039E	Explain tables cannot be found.	Explain tables do not exist.	Create explain tables using one of the following methods: Run the EXPLAIN.DDL sample command file. This file is located in the sqllib\misc directory. To run the command file, go to this directory and issue the db2 -tf EXPLAIN.DDL command. Call the SYSPROC.SYSINSTALLOBJECTS procedure.
DBA3040E	The command is specified incorrectly.	The command has invalid syntax.	Issue the command with the -h option to see the correct syntax.
DBA3041E	The name of the database must be between 1 and `maximum` characters long.	The specified database name is either empty or too long.	Reissue the command with a valid database name.
DBA3042E	The explainable statement text must be between 1 and `maximum` characters long.	The specified explainable statement text is either empty or too long.	Reissue the command with valid explainable statement text.
DBA3043E	The query tag cannot have more than `maximum` characters.	The specified query tag is too long.	Reissue the command with a valid query tag.
DBA3044E	The user ID cannot have more than `maximum` characters.	The specified userid is too long.	Reissue the command with a valid userid.
DBA3045E	The valid range for query number is from 0 to `maximum`.	The specified query number is either too small or too large.	Reissue the command with a valid query number.
DBA3046E	The valid values for optimization class are 0, 1, 2, 3, 5, 7 and 9.	The specified optimization class is not one of the valid values.	Reissue the command with a valid optimization class.
DBA3047E	The database `name` cannot be found.	The database name specified in the command does not exist in the system database directory.	Reissue the command with an existing database name or catalog the database in the system database directory.
DBA3059I	There is no details information associated with the selected operator `operator`.	The details information of the selected operator is not available for the current release of the DB2 Administration Tools.	None.
DBA3060I	There is no help information associated with the selected operator `operator`.	The help information of the selected operator is not available for the current release of the DB2 Administration Tools.	None.
DBA3061I	There are no column groups associated with this table.	There were no column groups defined on the referenced table at the time of explain and there are no column groups currently defined in the table.	No response required.
DBA3062N	Generate DDL cannot be performed on system tables.	Tables with schema SYSIBM, SYSCAT, or SYSSTAT are system tables.	Perform generate DDL on non-system tables.
DBA3063N	One or more system tables have been selected for Generating DDL. DDL will be generate for selected user tables only. Do you want to continue?		Tables with schema SYSIBM, SYSCAT, and SYSSTAT are system tables.
DBA3064N	Only the first `number` tables will be processed by db2look.	The db2look -t option will only process `number` tables.	Move the list of selected tables to the list of available tables.
DBA3065E	Snapshot cannot be processed due to a CLI error.	A CLI error has occurred during snapshot processing. An access plan cannot be displayed.	Check the CLI configuration by issuing the following command: db2 get cli cfg for section <db-name> If LONGDATACOMPAT is set to 1, try cataloging the database with a different alias: catalog db <db-name> as <db-alias-name> Set LONGDATACOMPAT=0 for the database alias: db2 update cli cfg for section <db-alias-name> using longdatacompat 0 Submit the query for EXPLAIN in the alias database. If LONGDATACOMPAT is not set to 1, or the parameter is not being set in the CLI configuration, contact IBM Service.
DBA3066E	Statement text for a snapshot contains an empty string.	The statement text of an explain record contains an empty string. Explained statement history cannot be retrieved successfully.	Check the CLI configuration by issuing the following command: db2 get cli cfg for section <db-name> If LONGDATACOMPAT is set to 1, try cataloging the database with a different alias: catalog db <db-name> as <db-alias-name> Set LONGDATACOMPAT=0 for the database alias: db2 update cli cfg for section <db-alias-name> using longdatacompat 0 Submit the query for EXPLAIN in the alias database. If LONGDATACOMPAT is not set to 1, or the parameter is not being set in the CLI configuration, contact IBM Service.