SQL1800N An invalid pointer to structure sqle_request_info was passed to the catalog admin command/api.
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.
SQL1801N Invalid request type.
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:
SQL1802N No entry belongs to the request type.
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.
SQL1820N Action on the LOB value failed. Reason code = "<reason-code>".
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
SQL1821W The LOB value retrieved may have changed.
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.
sqlcode: +1821
sqlstate: 01621
SQL1822N Unexpected error code "<error code>" received from data source "<data source name>". Associated text and tokens are "<tokens>".
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.
SQL1823N No data type mapping exists for data type "<data type name>" from server "<server name>".
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
SQL1824W Some base tables in the operands of this UNION ALL may be the same table.
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
SQL1825N This SQL statement cannot be handled in DataJoiner.
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
SQL1826N An invalid value "<value>" was specified for column "<column-name>" in a system catalog object "<object-name>".
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
SQL1827N No user mapping is defined from local authorization ID "<auth-ID>" to server "<server-name>".
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
SQL1828N No server option "<option-name>" is defined for remote server "<server-name>" or for a group of remote servers: server type "<server-type>", version "<server-version>", and protocol "<server-protocol>".
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