Cause: The pointer to structure sqle_request_info passed as a parameter to the catalog admin command/api was invalid. For Client Configuration Assistance request this pointer must not be NULL.
Action: Specify a valid pointer to sqle_request_info and re-submit the command.
Cause: The specified request type is not supported for this command.
Action: Ensure that the request type is one of the following supported request types:
Cause: There is no entry in the node directory that is catalogued by the given request type.
Action: Catalog an entry with the same request type and re-submit the command.
Cause: The database manager is currently operating in "No Package Lock" mode. This mode has been activated by setting the DB2_NO_PKG_LOCK registry environment variable to "ON".
In this mode, the following classes of operations are prevented from being executed because of their impact on packages:
Since the requested operation would affect the package "<package-name>" in one of these ways, the operation is disallowed.
Action: Do not attempt disallowed operations in "No Package Lock" mode. In order to execute the requested operation, "No Package Lock" mode must be exited. This is accomplished by unsetting the DB2_NO_PKG_LOCK environment registry variable. In order for the variable change to take effect, that database manager must be stopped and restarted.
sqlcode: -1803
sqlstate: 57056
Cause: The possible reasons codes are:
Action: Reduce the size of the LOB or replace the function which is being applied on the LOB datatype. As a last resort, remove the LOB datatype from the statement.
sqlcode: -1820
sqlstate: 560A0
Cause: The LOB value was evaluated on a deferred retrieval basis. The LOB value may have changed between the time it was first accessed and when it was actually retrieved.
Action: Set the "deferred_lob_retrieval" to "N" in SYSSERVEROPTIONS, resubmit your query, or ignore the warning. See the IBM DataJoiner Application Programming and SQL Reference Supplement for information on setting the value used for the "deferred_lob_retrieval" setting.
sqlcode: +1821
sqlstate: 01621
Cause: While referencing a data source, DataJoiner received an unexpected error code from the data source that does not map to a DB2 equivalent.
Action: Identify and correct the root cause of the problem by locating the appropriate message text and corrective action for the specified error at the data source.
Cause: An attempt was made to create a nickname for an object. One or more columns of that object are of a type currently unknown to DataJoiner. The name of (one of) the unknown type(s) is listed in the message.
Action: Create a mapping for the specified type name on the specified server using the CREATE TYPE MAPPING statement.
sqlcode: -1823
sqlstate: 428C5
Cause: A nickname can refer to a remote base table, a remote view, a remote alias/synonym, or a remote nickname. If two operands of a UNION ALL view refer to different nicknames, they may potentially be pointing to the same table (if not both of them are known to be remote base tables). This message is issued to warn the user that potentially one remote base table can get updated/deleted twice via updates/deletes through two operands.
Action: Verify if all operands point to different remote tables. If two operands point to the same remote base table, consider issuing a rollback to reverse the update/delete operation.
sqlcode: +1824
sqlstate: 01620
Cause: Due to some limitation, the current SQL statement cannot be handled in DataJoiner. Possible limitations include:
Action: Based on the cause:
sqlcode: -1825
sqlstate: 429A9
Cause: An invalid value "<value>" was specified for a column "<column-name>" in a system catalog object "<object-name>".
The statement cannot be processed.
Action: Refer to the IBM DataJoiner Application Programming and SQL Reference Supplement for valid values for the specified column in the specified system catalog object. Correct the statement and reissue it.
sqlcode: -1826
sqlstate: 23521
Cause: An attempt was made to drop or alter a user mapping that is not defined.
Action: If it is an ALTER USER MAPPING statement, first create a user mapping using the CREATE USER MAPPING statement. Then, alter the user mapping. If it is a DROP USER MAPPING statement, no extra action is needed because the user mapping does not exist.
sqlcode: -1827
sqlstate: 42704
Cause: An attempt was made to drop or alter a server option that is not defined.
Action: If it is an ALTER SERVER OPTION statement, first create a server option using the CREATE SERVER OPTION statement. Then, alter the server option. If it is a DROP SERVER OPTION statement, no extra action is needed because the server option for the servers does not exist.
sqlcode: -1828
sqlstate: 42704
Cause: The RETURNS clause is not specified before the AS PREDICATE WHEN clause that includes the EXPRESSION AS clause. The RETURNS clause may have been included after the predicate specification or may be missing.
The statement cannot be processed.
Action: Specify the CREATE FUNCTION statement with the RESULTS clause prior to the AS PREDICATE WHEN clause.
sqlcode: -1830
sqlstate: 42627
Cause: The statement attempts to update the statistics values of NPAGES, FPAGES, or OVERFLOW, for table "<subtable-name>", that is defined as a subtable. For typed tables, these statistics can only be updated using the root table of the table hierarchy.
The statement cannot be processed.
Action: Update the catalog statistics for the root table of the table hierarchy instead of the subtable.
sqlcode: -1831
sqlstate: 428DY
Cause: The data filter function "<function-name>" in the user defined predicate specification can not be defined with LANGUAGE SQL.
The statement cannot be processed.
Action: Specify a function that is not defined with LANGUAGE SQL.
sqlcode: -1832
sqlstate: 429B4