Messages Reference

SQL10000 - SQL10099

SQL10002N The password supplied is too long.

Cause: The length of the password is expected to be 18 characters or less. However, if the password is to be verified for an APPC conversation, it must be 8 characters or less.

Action: Ensure that the password is not longer than the limit allowed.

sqlcode: -10002

sqlstate: 28000

SQL10003C There are not enough system resources to process the request.

The request cannot be processed.

Cause: The database manager could not process the request due to insufficient system resources. The resources that can cause this error include:

The amount of memory in the system
The number of message queue identifiers available in the system.

Action: Stop the application. Possible solutions include:

Remove background processes.
Terminate other applications using the above resources.
If you are using Remote Data Services, increase the Remote Data Services heap size (rsheapsz) in the server and client configuration because at least one block is used per application.
NOTE: This is applicable only for releases of DB2 prior to Version 2.
Decrease the values of the configuration parameters that define allocation of memory, including udf_mem_sz if UDFs are involved in the failing statement.

sqlcode: -10003

sqlstate: 57011

SQL10004C An I/O error occurred while accessing the database directory.

Cause: Either the system database directory or the local database directory cannot be accessed. This error may occur not only when the system is cataloging or uncataloging a database but also when the system is accessing a database that is cataloged in the directory.

The command cannot be processed.

Action: Possible solutions include:

If the local database directory is damaged, restore the databases that were cataloged there from backup versions and catalog them.

If installing the sample database, drop it and install the sample database again.

sqlcode: -10004

sqlstate: 58031

SQL10005N The mode parameter "<parameter>" in the CONNECT TO statement is not valid. It must be SHARE for shared access, EXCLUSIVE for exclusive use or EXCLUSIVE MODE ON SINGLE NODE for exclusive use on single node. For DDCS connections, only SHARE mode is supported. EXCLUSIVE MODE ON SINGLE NODE is only supported in MPP configuration.

Cause: The mode parameter of the CONNECT TO statement must be SHARE for shared, EXCLUSIVE for exclusive use or EXCLUSIVE MODE ON SINGLE NODE for exclusive use on single node. If connecting to a database using Distributed Database Connection Services (DDCS), only shared access is allowed. EXCLUSIVE MODE ON SINGLE NODE is only supported in MPP configuration.

The command cannot be processed.

Action: Resubmit the command with a valid mode parameter.

SQL10007N Message "<msgno>" could not be retrieved. Reason code: "<code>".

Cause: The requested message <msgno> could not be retrieved from the message file. Reason code <code> is one of the following:

The environment variable "DB2INSTANCE" is either not set, or is set to an invalid instance. Correct it and try again.
The message file was found, but the file could not be opened because of permissions. Check the file permissions of the files under the message directory.
The message file could not be found. Either the file does not exist, or the directory the message file should be in does not exist. Check that a either a 'prime' directory (the default) or a directory with the same name as the 'LANG' environment variable exists under the message directory.
The requested message does not exist in the message file. Either the message file is outdated, or it is the wrong one.
LC_CTYPE is set to a locale which the database does not support. Correct it and try again.
An unexpected system error occurred. Try execution again. If problem persists, contact your IBM representative.
Not enough memory. An attempt to get private memory failed. Try again.

Action: Reissue the command after verifying the following:

ensure that the DB2INSTANCE environment variable is set to the correct literal string for the username attempting this command
ensure that correct home directory is specified for the username attempting this command (i.e. in the /etc/passwd file)
ensure that the LANG environment variable is set to the correct value for the installed language, or is set to 'C' (defaults to whatever is in the 'prime' directory), on the username attempting this command

If all of the above are correct and the error still occurs, reinstall DB2.

SQL10009N The codeset "<codeset>" and/or territory "<territory>" that has been specified is not valid.

Cause: This version of the database manager does not support the active codeset or territory or both, as specified by the Create Database command.

The command cannot be processed.

Action: Refer to the Create Database command in the Administration Guide for details of valid codeset and territory pairs supported by the database manager.

SQL10010N The specified library, "<name>", was loaded, but the function "<function>" could not be executed.

Cause: The function routine within the library cannot be found.

The command cannot be processed.

Action:

If it is a DARI library, ensure the DARI library is built correctly. Make sure that the function routine is exported through the 'export file'.
For other libraries, user may have to reinstall the database manager instance or the database manager product.

sqlcode: -10010

sqlstate: 42724

SQL10011N An interrupt was received while loading the specified DARI library "<name>".

Cause: When loading the DARI library, the command was interrupted, perhaps by the interrupt key (usually Ctrl+Break or Ctrl+C).

Processing is stopped.

Action: Resubmit the command.

sqlcode: -10011

sqlstate: 42724

SQL10012N An unexpected operating system error was received while loading the specified library "<name>".

Cause: An unexpected error occurred when trying to load the library module specified in the program name field.

Action: Resubmit the current command. If the error continues, stop the database manager and start it again. If the error continues, reinstall the database manager.

If reinstallation does not correct the error, record the message number (SQLCODE) and all information in the SQLCA if possible.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Refer to the Independent Trace Facility in the Troubleshooting Guide for information on how to use this facility. Then contact IBM as specified in this guide.

sqlcode: -10012

sqlstate: 42724

SQL10013N The specified library "<name>" could not be loaded.

Cause: The library module could not be found.

DataJoiner users: the specified library module could be one of the following:

a DataJoiner system library
a DARI library
a DataJoiner data access module

Action: For DARI users, ensure that the specified library is available.

If the client application uses a fully qualified path name to specify the DARI library, the DARI library must be stored in the given directory path. If the client application does not use the path name, the DARI library must be stored in the default directory (<InstanceHomeDir>/sqllib/function). Where <InstanceHomeDir> is the home directory of the database manager instance.
If the error message occurs during database manager start time then the user will have to reinstall the DB2 instance or the database manager product.

DataJoiner users: if the error message occurs as a result of issuing db2start on the DataJoiner system and the "<name>" is "from DJXCOMM" then DataJoiner experienced a problem loading one of the data access modules identified by the DJXCOMM environment variable. The DJXCOMM environment variable must be updated to contain only valid data access modules.

If the error message occurs as a result of issuing db2start on the DataJoiner system and the "<name>" is not "from DJXCOMM", the user must re-install the DataJoiner instance or the DataJoiner product.

If the library identifies a data access module, that module must be installed, link-edited (as required), and available in the correct directory. Refer to the IBM DataJoiner Planning, Installation, and Configuration Guide for more information about configuring data access modules.

sqlcode: -10013

sqlstate: 42724

SQL10014N The invoking DARI program name "<name>" specified is not valid.

Cause: The DARI library module or the DARI program name syntax is not correct.

Action: Ensure that the DARI library or program name is specified correctly.

sqlcode: -10014

sqlstate: 42724

SQL10015N There are not enough system resources to load the specified library "<name>".

Cause: There is not enough memory to load the library module.

Action: Stop the application. Possible solutions are:

Remove background processes.
Decrease the values of the configuration parameters that define the allocation of memory.
Install more memory.

sqlcode: -10015

sqlstate: 42724

SQL10017N The SQL CONNECT RESET statement is not allowed in a Database Application Remote Interface (DARI) procedure.

Cause: The remote procedure contains an SQL CONNECT RESET statement.

Action: Remove the SQL CONNECT RESET statement and retry the remote procedure.

sqlcode: -10017

sqlstate: 42987

SQL10018N The disk is full. Processing was ended.

Cause: The disk is full. During the export to a PC/IXF file, either the PC/IXF data file is on a fixed disk, or the PC/IXF data file and the database are on the same file system , or the PC/IXF data file and the message file are on the same file system.

The EXPORT utility stops processing. The exported data is not complete.

Action: Provide more space on the disk or specify that the data file be located on a different file system than the database or the message file and resubmit the command.

SQL10019N The database cannot be accessed in the specified path.

Cause: The database cannot be accessed for one of the following reasons:

The path does not contain a database image.
Permissions on the path are incorrect.

Action: Ensure that the path references a valid database and that the permissions are correct.

sqlcode: -10019

sqlstate: 58031

SQL10021N The file permissions do not allow write access to the database.

Cause: A write operation was attempted to a database residing on a file system which does not allow write access.

The statement cannot be processed.

Action: Verify that the file permissions for the file system on which the database resides allow write access.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]