Cause: The authentication type supplied is not one of the supported types.
The command can not be processed.
Action: The user should reissue the command with a valid parameter value.
See API Reference for a list of supported authentication types.
Cause: The user is attempting to connect to a remote database which is cataloged on the local node with a different authentication type from the remote node.
DataJoiner users: this message can also appear when:
Action: The command can not be processed.
The user should recatalog the database alias on the client node with the same authentication type as the remote database. Resubmit the command.
DataJoiner users:
sqlcode: -1401
sqlstate: 08001
Cause: Call your system administrator. On unix-based systems, the file db2ckpw may not have the correct permission bits set, or the system may have run out of swap/paging space. On Windows NT, the DB2 security service may not have been started.
The command can not be processed.
DataJoiner users: this situation can be detected by DataJoiner or by the data source.
Action: On unix-based systems, have the system administrator ensure the correct access permissions are set for db2ckpw, and that there is enough swap/paging space allocated. On Windows NT, have the system administrator verify that the DB2 security service is installed and started.
Cause: The username and/or password supplied is incorrect or not a valid username/password combination or the database to which you are attempting to connect to has an authentication type of SERVER and no username and password was supplied on the CONNECT TO statement.
If DB2 Connect is being used, the problem may be that the DCS directory entry for the host connection could not be found.
If a connection is being made from an OS/2 client to a UNIX-based server with authentication server, and the userid and password are being picked up from UPM, then the userid on the server must be defined in lowercase and have an uppercase password.
The command can not be processed.
DataJoiner users: this situation can be detected by DataJoiner or by the data source.
Action: Supply the correct username and password combination.
DataJoiner users: ensure that the entry in SYSCAT.REMOTEUSERS contains the correct username and password for the data source being accessed.
sqlcode: -1403
sqlstate: 08004
Cause: Your password has expired.
Action: Change your password, then retry the request using the new password. You can use the DB2 Client Configuration Assistant, or Command Line Processor CONNECT and ATTACH commands to change your password.
sqlcode: -1404
sqlstate: 08004
Cause: The application failed to authenticate due to an error while communicating to the local DB2 authentication server.
Action: Ensure that the DB2 authentication server is started by entering the following command from an OS/2 window:
detach db2upm
Cause: The statement was processed through parts of the system to collect diagnostic information using service features. The necessary steps to allow further processing of the statement have not been completed.
Action: This error is returned to prevent further processing by the system of statements prepared using service features and is expected.
Cause: The database manager has reached an internal limit while evaluating an expression, of long or large object string result type, that contains concatenation operators.
Action: Reduce the number of concatenations in the expression and try again.
sqlcode: -1420
sqlstate: 54001
Cause: A C/C++ application with embedded SQL statements was precompiled with the WCHARTYPE CONVERT option. At runtime, the application received an error which occurred during conversion in either wcstombs(), for input host variables, or mbstowcs(), for output host variables. The host variable or sqlvar number indicates which data item experienced the problem. Valid reason codes are:
Action: If application data is already in MBCS format, re-precompile the application with WCHARTYPE NOCONVERT and re-build. If application data is intended to be in wchar_t format, then input data failing in wcstombs() may be corrupt. Correct the data and re-execute the application.
sqlcode: -1421
sqlstate: 22504
Cause: One of the containers to be used in a database managed table space is either too large or too small. A container must be at least extentsize + 1 pages in length. The maximum size of a container is operating system dependent. The most common system limit is 2 gigabytes (524288 4K pages).
Action: Check the diagnostic log for details. Then correct the SQL statement.
sqlcode: -1422
sqlstate: 54039
Cause: The query includes a column with a data type of BLOB, CLOB or DBCLOB. In general, such data types cannot be handled from clients available prior to Version 2.1.
The error occurred for a condition that corresponds to warning SQLCODE +238. See this message for details that explain the condition. The client level receiving this message cannot process BLOB data types. It may be able to handle CLOB and DBCLOB data types by using the SUBSTR function or by setting the data type in the SQLDA to one of the character data types available in Version 1 if the LOB column is not larger than the supported length of the character data type.
Action: Change the query to exclude any column that has a data type of BLOB, CLOB or DBCLOB. This is the only possible action if the query includes a column of type BLOB. If the column (say C1) is a CLOB, you could use CAST(C1 AS LONG VARCHAR) to get the first 32700 characters. Similarly for DBCLOB column (DC1) use CAST(DC1 AS LONG VARGRAPHIC) to get the first 16350 characters. If the application code can be changed, code can be added to change the SQLDA to use LONG VARCHAR or LONG VARGRAPHIC for CLOB and DBCLOB.
sqlcode: -1423
sqlstate: 56093
Cause: The trigger includes a REFERENCING clause that identifies one or more transition tables and transition variables. The triggered action of the trigger contains references to transition table columns or transition variables with one of the following conditions identified by the reason code:
Action: Reduce the number of references to transition variables and transition table columns in the trigger action of the trigger so that the length is reduced or the total number of such references is less than the maximum number of columns in a table.
sqlcode: -1424
sqlstate: 54040
Cause: Any command/API that accepts a userid and password will not accept a password without a userid.
Action: Resubmit the command/API and supply a userid if you are also supplying a password.
Cause: If an explicit 'attach to instance' has not been performed, instance commands try to form an implicit attachment to a default instance. The default instance is determined from the DB2INSTDFT and DB2INSTANCE environment variables. If neither of these are set, then no implicit attachment can be formed.
Action: Set one of these environment variables to a valid instance name and resubmit the command.
Cause: The application is not attached to an instance. The attempted command/API cannot be executed unless there is an existing instance attachment.
Action: If the error occurred when detaching from an instance, continue processing. If the error occurred during the execution of any other command, attach to an instance and reissue the failed command.
Cause: In order to successfully process the command, an attachment to a node other than that which currently exists is required. The application must either: 1) have no attachment when the command is issued, or 2) already be attached to the node required by the command.
Action: Ensure that the application has no attachment before issuing the command or that the attachment that exists is to the correct node.
Cause: The CATALOG NODE command or API does not allow an entry whose nodename matches the value of the DB2INSTANCE environment variable.
Action: Choose another node name for the node being cataloged and try again.
Cause: When specific database names are provided to the database monitor, those databases must reside either at the node to which you are currently attached or at the local node.
Action: Make sure the databases listed in the request all reside at the node to which you are attached or at the local node. Reissue the request.
Cause: When the application is remote from the server, relative paths are not allowed.
Action: Specify a fully qualified path that is valid at the server and reissue the command.
Cause: This error is caused by sending a DB2 request to a server which does not understand the database protocol being used to transmit the request. This situation will occur most frequently when sending a DB2 ATTACH request to a server listed in your node directory which is not a DB2 Version 2 or greater server. This error will also arise if you send an attach request to DB2 for AS/400, DB2 for MVS, or DB2 for VM and VSE servers.
Action: Do not attempt to attach to any of the servers listed above.
Cause: In order to successfully process the command, a connection to a database other than that which currently exists is required. The application must either: 1) have no connection when the command is issued, or 2) already be connected to the database required by the command.
Action: Ensure that the application has no connection before issuing the command or that the connection that exists is to the correct database.
Cause: The WITH GRANT OPTION is not applicable when granting database authorities or privileges on packages or indexes. The WITH GRANT OPTION does not apply to CONTROL privilege on tables, views, indexes, or packages.
All valid requested privileges were granted.
Action: When granting database authorities, package privileges or index privileges do not include the WITH GRANT OPTION clause. When granting CONTROL, use a separate grant statement for the CONTROL privilege without specifying the WITH GRANT OPTION clause.
sqlcode: +1440
sqlstate: 01516
Cause: The following is a list of valid reason codes:
Action: Ensure that the application context pointer has been properly initialized and that any options used are valid and try again.
Cause: The call failed because:
Action: For a detach call, ensure that the context is the one in use by the current thread, and that a corresponding attach was done.
For a get current context call, ensure that the thread is currently using a context.
Cause: The user attempted to attach a context to a thread, and the thread is already using a context.
Action: Detach from the previous context before attaching to a new one.
Cause: The user attempted to destroy an application context while it is still in use. Either there is a thread attached to the context, or the context has a CONNECT or ATTACH associated with it. A CONNECT RESET or DETACH must be done (if a CONNECT or ATTACH has been done), and all threads must detach from the context before it can be destroyed.
Action: Ensure that all calls to attach to a context have a corresponding detach, all CONNECTS have a corresponding CONNECT RESET, and all ATTACHES have a corresponding DETACH.
Cause: A context type of SQL_CTX_MULTI_MANUAL is in effect, but the current thread or process has not been attached to a context.
Action: Make sure the current thread or process is attached to a context before making any database calls.
Cause: An invalid registration information pointer was passed to the register/deregister DB2 server command/API.
Action: Verify that a valid pointer was passed to the register/ deregister DB2 server command/API.
Cause: Register/deregister DB2 server was issued from an invalid node.
Action: Reissue the register/deregister DB2 server command/API from a server node.
Cause: An invalid registration location was passed to the register/deregister DB2 server command/API.
Action: Verify that a valid registration location was passed to the register/deregister DB2 server command/API.
Cause: The file server name specified in the configuration command/API or in the database manager configuration file is missing or invalid.
Action: Verify that a file server name was specified, that the name does not contain invalid characters, and is not longer than 48 characters in length. Update the file server name in the database manager configuration file and resubmit the command/API.
Cause: The object name specified in the configuration command/API or in the database manager configuration file is missing or invalid.
Action: Verify that an object name was specified, that the name does not contain invalid characters, and is not longer than 48 characters in length. Update the object name in the database manager configuration file and resubmit the command/API.
Cause: The IPX socket number specified in the configuration command/API or in the database manager configuration file is missing or invalid.
Action: Verify that an IPX socket number was specified, that the number does not contain invalid characters, and is not longer than 4 characters in length. Update the IPX socket number in the database manager configuration file and resubmit the command/API.
Cause: A duplicate object name was found when trying to register the DB2 server object name on the NetWare file server.
Action: The object name specified in the database manager configuration file is already in use. Change the object name and then re-register the DB2 server.
Cause: A bindery login using NWLoginToFileServer cannot be performed if a NetWare directory services connection is already established to the specified file server.
Action: Sever the directory services connection by logging out and detaching from Directory Services, and then reissue register/deregister.
Cause: Issuing register/deregister is not necessary since the database manager configuration file has been configured for IPX/SPX direct addressing. ie. Fileserver and objectname have been specified as '*'.
Action: Note that since the DB2 server has been configured for direct addressing only, IPX/SPX clients using fileserver addressing will not be able to connect to this server. For the server to support both types of IPX/SPX client addressing, specify a fileserver and objectname in the database manager configuration file.
Cause: The SOCKS environment variable SOCKS_NS or SOCKS_SERVER is not defined. SOCKS protocol support requires that both these environment variables be defined.
Action: Define the missing environment variable and resubmit the command.
Cause: The SECURITY option for a TCP/IP node has a value other than 'SOCKS'. This option is used to enable the TCP/IP node being cataloged to use SOCKS protocol support to traverse a firewall. No value other than 'SOCKS' is permitted.
Action: Verify that SOCKS protocol support is required. If so, re-catalog the node with SECURITY SOCKS. If not, re-catalog the node, but omit the SECURITY option.
Cause: A request was attempted which is only valid for a syncpoint manager connection, but the syncpoint manager instance is not connected to.
Action: Connect to the syncpoint manager instance and reissue the request.
Cause: The SET CLIENT command or api or the environment variable DB2NODE was used to set the node for CONNECT or ATTACH to "<node-num2>". In order to CONNECT or ATTACH to this node, the Database Manager TCP/IP listener must be configured and running on the server instance "<instance>" (node "<node-num1>").
| Note: | This message may be returned by an implicit CONNECT or ATTACH. |
Action: Either:
or
sqlcode: -1468
sqlstate: 08004
Cause: The SET CLIENT command or api or the environment variable DB2NODE was used to set the node for CONNECT or ATTACH to "<node-num2>". Subsequent CONNECT or ATTACH processing was unable to locate this node in the db2nodes.cfg file on the instance "<instance-name>" (node "<node-num1>").
| Note: | This message may be returned by an implicit CONNECT or ATTACH. |
Action: Ensure that the node number specified by the SET CLIENT command or api or the DB2NODE environment variable exists in the db2nodes.cfg file of the intermediate instance "<instance-name>", node "<node-num1>".
sqlcode: -1469
sqlstate: 08004
Cause: The DB2NODE environment variable indicates the node the application will attempt to connect to. If DB2NODE is unset or is blank, the application will attempt to connect to the default node. Otherwise, DB2NODE must be set to the node number of one of the nodes defined on the same host as the application.
Action: Set the DB2NODE environment variable to one of the following values:
sqlcode: -1470
sqlstate: 08001
Cause: The end-of-log information on this node does not match the corresponding record on the catalog node. This can be caused by restoring the database on various nodes with backups taken from different times.
Action: If the database is restored without rolling forward on one node, ensure that the database is restored from consistent offline backups on all nodes without rolling forward.
sqlcode: -1471
sqlstate: 08004
Cause: The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.
Action: Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.
If the above does not fix the problem, see the Administration Guide for possible causes and actions.
sqlcode: -1472
sqlstate: 08004
Cause: The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.
If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.
Action: Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.
sqlcode: -1473
sqlstate: 40504
Cause: The system time difference for the machines in the configuration (listed in the db2nodes.cfg file) is greater than the max_time_diff database manager configuration parameter.
This warning message is returned to read-only transactions because they are not affected by this condition. However, other transactions would be rolled back. This message is to inform the user about this condition so that action can be taken at the earliest possible time.
If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.
Action: Synchronize the system times on all machines, and ensure that the max_time_diff parameter is configured to allow for normal communication delays among the database machines.
sqlcode: 1474
sqlstate: 01607
Cause: The CONNECT RESET was successful but a system error such as a node failure or a communications error may have occurred.
Action: Check the db2diag.log file for details. The database at this node may need to be restarted.
sqlcode: 1475
sqlstate: 01622
Cause: A table was being created with the NOT LOGGED INITIALLY option. During the same unit of work, an error occurred. This unit of work is rolled back, and any table that was created in it is dropped.
The "<sqlcode>" reported is the SQLCODE of the original error.
Action: Correct the problem, then run the transaction again.
sqlcode: -1476
sqlstate: 40506
Cause: An attempt was made to access a table that is not accessible. The table is not accessible because the Rollforward utility found a log record indicating one of the following:
After successful roll-forward recovery, access to this table is not allowed because its integrity cannot be guaranteed.
Action: Drop the table. If this table is required, re-create it.
sqlcode: -1477
sqlstate: 55019
Cause: Only one small buffer pool with no extended storage has been activated. This is because of one of the following reasons:
Action: Check the db2diag.log file for the correct source of the problem. Possible solutions will be:
sqlcode: +1478
sqlstate: 01626
Cause: The requested rowset overlapped the start of the result set and, depending on the fetch orientation specified:
Action: No action needed.
Cause: Valid values for the DISCOVER parameter in the database manager configuration file are: DISABLE, KNOWN, or SEARCH.
Action: Update the DISCOVER database manager configuration parameter with a type of DISABLE, KNOWN, or SEARCH.
Cause: Valid values for the DISCOVER_COMM parameter in the database manager configuration file are any combination of NETBIOS, and TCPIP, separated by commas.
Action: Update the DISCOVER_COMM database manager configuration parameter with any combination of NETBIOS, and TCPIP, separated by commas.
Cause: This is a warning that the BUFFPAGE database configuration parameter will be ignored if none of the database's buffer pools is defined with a size of -1. -1 indicates that the buffer pool is to use the BUFFPAGE parameter as the number of buffer pool pages.
Action: You can select from the SYSCAT.BUFFERPOOLS to review the buffer pool definitions. If none of the buffer pools are defined with size -1 (NPAGES), then setting the BUFFPAGE parameter will not change the size of the buffer pools for the database.
Cause: Database has already been explicitly started (activated) on one or more nodes.
Action: Refer to the diagnostic log to see which node returns the warning.
Cause: The database cannot be deactivated if there are any applications connected to the specified database.
Action: Ensure that all applications have done a CONNECT RESET, then try again.
Cause: The database cannot be deactivated because the specified database was not active.
Action: No action is required.
Cause: The ACTIVATE DATABASE and DEACTIVATED DATABASE commands cannot proceed because the application is already connected to a database.
Action: Disconnect from the database then re-submit the command.
Cause: There is already database connection on one or more nodes.
Action: Refer to the diagnostic log to see which node returns this warning.
Cause: There is still database connection to one or more nodes.
Action: Refer to the diagnostic log to see which node returns this warning.
Cause: Database was not explicitly started on one or more nodes when deactivate database was executed.
Action: Refer to the diagnostic log to see which node returns this warning.
Cause: Activate/Deactivate database is successful at least on the catalog node and coordinator node, however, on some other node(s) an error has occurred.
Action: Refer to the diagnostic log to find out what error has occurred on which node, fix the problem if possible and then reissue the activate/deactivate database command.