This section contains the DB2 Embedded SQLJ in Java (SQLJ) messages. The messages are listed in numeric sequence.
| SQJ0001W | Customizing profile "<profile-name>". |
Explanation: This message is written to the standard output device when the precompiler begins processing. The token "<profile-name>" refers to the particular profile being customized.
Processing continues.
User Response: No action is required.
| SQJ0100E | Invalid option specified "<option>". |
Explanation: The specified option is invalid.
User Response: Check the syntax and resubmit the command with the valid option and parameter. The format is -<option>=<parameter>.
| SQJ0101E | Unknown option "<option>". |
Explanation: The option is unknown or unsupported.
User Response: Execute the command alone without specifying options for usage help. Resubmit the command with a valid option.
| SQJ0102E | No <option> specified. |
Explanation: An option is missing.
User Response: Resubmit the command specifying the required option.
| SQJ0103E | No profile specified. |
Explanation: The profile name is required but missing.
User Response: Resubmit the command with the profile name.
| SQJ0104E | Unable to load profile "<profile>". |
Explanation: The specified profile cannot be found or does not exist.
User Response: Make sure the profile exists or the profile name is correctly specified.
| SQJ0105E | Unable to customize profile "<profile>". |
Explanation: The profile cannot be customized due to system or internal error.
User Response: Contact IBM service for assistance.
| SQJ0106E | Invalid syntax "<command-syntax>". |
Explanation: The syntax of the specified option is invalid.
User Response: Resubmit the command with the correct syntax.
| SQJ0200E | An internal error has occured. |
Explanation: An unexpected internal error has occurred.
User Response: Turn trace on and retry the steps that caused the error. If the problem reoccurs, save the trace information to a file and contact IBM Support with the following information:
| SQJ0201E | An internal error has occurred during profile customization. Reason code "<reason-code>". |
Explanation: An unexpected internal error has occurred when customizing a profile.
User Response: Turn DB2 and CLI trace on and retry the steps that caused the error. If the problem reoccurs, save the trace information to a file and contact IBM Support with the following information:
| SQJ0202E | An internal error has occurred during precompilation. Reason code "<reason-code>". |
Explanation: An unexpected internal error has occurred when precompiling.
User Response: Turn trace on and retry the steps that caused the error. If the problem reoccurs, save the trace information to a file and contact IBM Support with the following information:
| SQJ0203E | An internal error has occurred when processing the command. Reason code "<reason-code>". |
Explanation: An unexpected internal error has occurred when processing the command.
User Response: Turn trace on and retry the steps that caused the error. If the problem reoccurs, save the trace information to a file and contact IBM Support with the following information:
| SQJ0204E | A FOR UPDATE clause was found from a SELECT statement. |
Explanation: A syntax error in the SQL statement was detected when the update-clause appears in a SELECT statement.
User Response: Correct the syntax error in the SELECT statement and specify the update-clause through the iterator-declaration-clause.
| SQJ4011E | Invalid SQL sub-statement in a Compound SQL statement. |
Explanation: This error is returned when an invalid sub-statement is detected in a Compound SQL statement. Valid statements are:
User Response: Resubmit the command without the invalid sub-statement.