SQL0000W Statement processing was successful.
Explanation: The SQL statement executed successfully, unless a warning condition occurred.
User Response: Check SQLWARN0 to ensure that it is blank. If it is blank, the statement executed successfully. If it is not blank, a warning condition exists. Check the other warning indicators to determine the particular warning condition. For example, if SQLWARN1 is not blank, a string was truncated.
Refer to the Application Development Guide.
sqlcode: 0
sqlstate: 00000, 01003, 01004, 01503, 01504, 01506, 1509, 01517
SQL0001N Binding or precompilation did not complete successfully.
Explanation: For reasons specified in the previous messages, the bind or precompile request was unsuccessful.
No package is created.
User Response: Refer to the messages in the message file. Resubmit the command.
If installing the sample database, drop it and install the sample database again.
SQL0002N The bind file name is not valid.
Explanation: For reasons specified in the previous messages, the bind file name cannot be used as specified.
No package is created.
User Response: Refer to the messages in the message file. Resubmit the command.
If installing the sample database, drop it and install the sample database again.
SQL0003N The database name is not valid.
Explanation: For reasons specified in the previous messages, the database name cannot be used as specified.
No package is created.
User Response: Refer to the messages in the message file. Resubmit the command.
SQL0004N The password is not valid.
Explanation: The password contains characters that are not valid or the password is too long.
No package is created.
User Response: Resubmit the command with a valid password.
SQL0005N The message file name is not valid.
Explanation: For reasons specified in the previous messages, the message file name cannot be used as specified.
No package is created.
User Response: Refer to the messages in the message file. Check the name of the message file. Check the attributes of the message file if it exists. Resubmit the command.
SQL0006N The datetime format parameter is not valid.
Explanation: The value of the datetime format parameter is not in the valid range of 0 through 3.
No package is created.
User Response: Resubmit the command with a valid format parameter.
SQL0007N The character "<character>" following "<text>" is not valid.
Explanation: The specified "<character>" is not a valid character in SQL statements. The "<text>" field indicates the 20 characters of the SQL statement that preceded the character that is not valid.
Federated system users: some data sources do not provide the appropriate values for the "<character>" and "<text>" message tokens. In these cases, "<character>" and "<text>" will have the following format: "<data source>:UNKNOWN", indicating that the actual values for the specified data source are unknown.
The statement cannot be processed.
User Response: Remove or replace the character that is not valid.
sqlcode: -7
sqlstate: 42601
SQL0008N The token "<token>" found in a host variable declaration is not valid.
Explanation: A host variable declaration has invalid syntax. The precompiler cannot identify the host variable.
The statement cannot be processed. None of the host variables declared in the statement (up to the semicolon) are accepted.
User Response: Examine the syntax of the host variable declaration.
SQL0009W An attempt to override a precompiler option was ignored.
Explanation: An attempt was made to override a precompiler option.
The option is ignored.
User Response: Ensure that all precompiler options are specified correctly.
SQL0010N The string constant beginning with "<string>" does not have an ending string delimiter.
Explanation: The statement contains a string constant, beginning with "<string>", that is not terminated properly.
The statement cannot be processed.
User Response: Examine the statement for missing apostrophes in the indicated string constant.
sqlcode: -10
sqlstate: 42603
SQL0011N The comment is not terminated.
Explanation: The comment is not terminated properly.
The statement cannot be processed.
User Response: Examine the statement for a missing or extra comment delimiter in the indicated comment.
SQL0012W Correlation without qualification has occurred for the column "<column>".
Explanation: The named column occurs in a SELECT statement, is not explicitly qualified, and occurs in a table specified in the FROM clause of an outer select. Consequently, the reference to the column in the SELECT statement has been taken to be an outer reference and correlation will occur.
The statement was processed under the assumption that correlation was intended.
User Response: Ensure that correlation was intended. It is a good practice to explicitly qualify intended outer references.
sqlcode: +12
sqlstate: 01545
SQL0013N An empty delimited identifier is not valid.
Explanation: During precompilation, either a cursor name, statement name, database name, or authorization ID, specified as an empty string, was found. This is not valid. The statement cannot be processed.
User Response: Provide a valid cursor name, statement name, database name, or authorization ID.
SQL0014N The source file name is not valid.
Explanation: The source file name specified in the call to the precompiler contains invalid characters or the pointer to the source file name is invalid.
No package was created.
User Response: Ensure that the source file name is correct.
SQL0015N The host variable data type "<token_1>" is not valid. Use "<token_2>" instead.
Explanation: If the WCHARTYPE CONVERT precompile option is in effect then the graphic host variable must be declared with the data type 'wchar_t', not 'sqldbchar'.
If the WCHARTYPE NOCONVERT precompile option is in effect (the default) and 'wchar_t' is defined as a 4-byte integer on this platform, then the graphic host variable must be declared with the data type 'sqldbchar', not 'wchar_t'.
User Response: Replace the current data type of the host variable with the data type specified in the message.
SQL0020W Bind or precompile option(s) "<option-name(s)/option-number(s)>" are not supported by the target database and will be ignored.
Explanation: This warning is returned in the following situations:
The unsupported options/values will be ignored. The most probable cause is that an option or option value which is only supported while connected to a DRDA application server has been specified while connected to a non-DRDA server.
Enter "db2 ? bind" or "db2 ? prep" for a list of which options are supported only by a DRDA application server.
Possible option numbers and their corresponding option names include:
User Response: Ensure the specification of bind or precompile "<option-name(s)/option-number(s)>" was intended while connected to this DBMS.
SQL0021W Invalid precompiler option "<option>" is ignored.
Explanation: The option specified in the message is not a valid precompiler option.
The option is ignored.
User Response: Ensure that all precompiler options are specified correctly.
SQL0022W Duplicate precompiler option "<option>" is ignored.
Explanation: The precompiler option "<option>" is a duplicate.
The option is ignored.
User Response: Ensure that all precompiler options are specified only once.
SQL0023N The database name is not valid.
Explanation: The specified database name is not a valid name.
Precompilation is terminated.
User Response: Ensure that the database name is spelled correctly and follows the rules for short identifiers.
SQL0024N A database name was not specified.
Explanation: No database name was provided to proceed with precompilation.
Precompilation is terminated.
User Response: Provide a database name.
SQL0025W Binding or precompilation completed with warnings.
Explanation: Binding or precompilation succeeded, but warnings were issued. A package and/or bindfile was created as requested in the command.
User Response: Refer to the messages in the message file. If necessary, correct the problems and resubmit the command.
SQL0026N The password is not valid.
Explanation: The specified password is not a valid password.
Precompilation is terminated.
User Response: Ensure that the password provided follows the rules for valid passwords.
SQL0028C The release number of the bind file is not valid.
Explanation: The release number of the bind file is not compatible with the release number of the installed version of the database manager.
The bind file cannot be used with the current version of the database manager. The command cannot be processed.
User Response: If possible, repeat the precompile process with the current database manager. Otherwise, use only bind files created with a compatible release level of the database manager.
SQL0029N INTO clause required.
Explanation: Non-cursor SELECT or VALUES statements embedded in an application program must have an INTO clause to denote where the results of the statement are to be placed. Dynamic SELECT statements do not permit the INTO clause.
User Response: Add the INTO clause to the SELECT or VALUES statement and precompile the application program again.
sqlcode: -29
sqlstate: 42601
SQL0030N A source file name was not specified.
Explanation: A source file name was not provided to proceed with precompilation.
Precompilation is terminated.
User Response: Specify a source file name.
SQL0031C File "<name>" could not be opened.
Explanation: The file "<name>" is required but could not be opened.
Precompilation is terminated.
User Response: Ensure that the file name specified is correct and exists in the file system, and that the file permissions are correct.
If installing the sample database, drop it and install the sample database again. If the error continues, reinstall the database manager and then install the sample database.
SQL0032C Unable to use file "<name>".
Explanation: While reading or writing file "<name>", an error was encountered.
Precompilation is terminated.
User Response: Retry the precompilation.
SQL0033N "<name>" is not a valid bind file.
Explanation: The bind file "<name>" specified is not a bind file.
Binding is terminated.
User Response: Ensure that the correct file name was specified.
SQL0034N A bind file name was not specified.
Explanation: No bind file name was specified to proceed with binding.
Binding is terminated.
User Response: Provide a bind file name.
SQL0035N The file "<name>" cannot be opened.
Explanation: The message file "<name>" could not be opened.
Binding or precompilation has been terminated.
User Response: Ensure that the system can access the file.
SQL0036N The syntax of the file name "<name>" is not valid.
Explanation: If the file is input to the precompiler, it must have an extension with the correct extension for the language being used. If the file is input to the binder, it must have an extension of .bnd. Also, a fully resolved file name which is over the platform maximum length will cause this error.
Precompilation or binding is terminated.
User Response: Ensure that the specified file name is correct.
SQL0037W The syntax of the message file "<name>" is not valid.
Explanation: The message file name "<name>" is not syntactically correct for this function.
The system redirects the output to the standard output device.
User Response: Ensure that the specified file name is correct.
SQL0038W The bind option SQLERROR CONTINUE has been activated since it is required when binding this DB2-supplied list file to DB2/MVS, SQL/DS, or OS/400.
Explanation: The SQLERROR CONTINUE bind option is required when binding the following DB2-supplied list files:
This option instructs a DRDA server to create a package even if there are SQL statements in a bind file which it considers invalid. Since not all of the DRDA servers support all of the SQL statements contained in the DB2-supplied bind files, the SQLERROR CONTINUE bind option must be used to guarantee that packages are created for all of the bind files in the list file.
User Response: No response is necessary. The required bind option, SQLERROR CONTINUE, has been specified for you. To avoid receiving this warning in the future specify the SQLERROR CONTINUE bind option.
SQL0039N The binder did not finish processing because the bind file is not valid.
Explanation: The binder could not process the bind file. The bind file may not be valid because the bind file contents were altered accidentally.
The bind file is not processed.
User Response: If possible, repeat the precompile process to create a new bind file. Otherwise, obtain a new copy of the bind file.
SQL0040N An error occurred on one or more bind files in the list "<name>". The following files were not bound: "<list>".
Explanation: For reasons specified in the previous messages in the message file, one or more bind files were not bound. The list of files that were not bound is composed of digits, starting from 1, that indicate the relative position of the unbound files in the list file. "<name>" does not include the path specification of the list file.
Only the first 20 bind files in error are listed in the message. If there were more than 20 bind files in error, ellipses (...) are inserted after the last bind file name in the list.
One or more packages were not created.
User Response: Refer to the messages in the message file. Check the list file to verify that it contains valid names. Resubmit the command.
SQL0041N No attempt was made to bind the files following file number "<number>" in list "<name>" because a fatal error occurred which terminated processing.
Explanation: Some errors encountered during the binding process are considered fatal (i.e. system errors, memory errors). If one of these errors occurs while processing a file in a list file, processing terminates. No attempt is made to bind the remaining files in the list file.
Such an error occurred while binding the specified bind file in the list. Note that the digit used to identify the bind file indicates the relative position of the file in the list file.
User Response: Refer to the other messages which accompanied this one to resolve the errors which occurred. Resubmit the command.
SQL0051N The maximum number of SQL statements was exceeded in the program.
Explanation: Too many SQL statements are in the program to fit into one package in the database.
Precompilation is terminated.
User Response: Either simplify the program, or split the program into smaller, separate programs, or do both.
SQL0053W No SQL statements were found in the program.
Explanation: The specified source file contains no SQL statements.
If binding, an empty package is created.
User Response: Ensure that you are precompiling or binding the correct program.
SQL0055N Source input file is empty.
Explanation: The program source input file contained no data.
Precompilation is terminated.
User Response: Ensure that the correct input file was specified.
SQL0060W The "<name>" precompiler is in progress.
Explanation: This message is written to the standard output device when the precompiler begins processing. The token "<name>" refers to the particular language precompiler which was invoked.
Processing continues.
User Response: No action is required.
SQL0061W The binder is in progress.
Explanation: This message is written to the standard output device when the binder begins processing.
Processing continues.
User Response: No action is required.
SQL0062W Starting INCLUDE of file "<name>".
Explanation: An INCLUDE statement has been encountered. The precompiler is now processing the INCLUDE file.
User Response: No action is required.
SQL0063W Completed INCLUDE of file "<name>".
Explanation: The precompiler has completed processing the INCLUDE file. It will resume processing the file which contained the INCLUDE statement.
User Response: No action is required.
SQL0064N File "<name>" directly or indirectly INCLUDEs itself.
Explanation: A cyclic INCLUDE has been encountered. A precompiler input file cannot INCLUDE itself, nor be INCLUDEd by a file it INCLUDEs.
The specified file is not INCLUDEd.
User Response: Check the nesting of the INCLUDE files, and remove any cycles.
SQL0065N An unexpected end-of-line was encountered in a host variable declaration.
Explanation: A host variable declaration has an invalid syntax. An end-of-line was encountered before the declaration was complete.
The statement cannot be processed.
User Response: Examine the syntax of the host variable declaration.
SQL0081N SQLCODE "<sqlcode>" returned during precompilation/bind.
Explanation: While precompiling or binding the program, an unexpected SQLCODE "<sqlcode>" was returned from the database manager.
The statement cannot be processed.
User Response: Inspect the SQLCODE to determine the problem and take the appropriate action.
SQL0082C An error has occurred which has terminated processing.
Explanation: A previous, non-SQL error has caused processing to terminate.
Precompile/bind/rebind is terminated. No package was created.
User Response: Correct the situation that caused the previous error and retry the operation.
SQL0083C A memory allocation error has occurred.
Explanation: During processing, there was not enough memory to continue processing.
User Response: Possible solutions include:
SQL0084N An EXECUTE IMMEDIATE statement contains a SELECT or VALUES statement.
Explanation: A SELECT or VALUES statement was used in an EXECUTE IMMEDIATE statement.
The statement cannot be processed.
User Response: The implied function is not supported. Prepare the SELECT or VALUES statement. Then use OPEN, FETCH, and CLOSE.
sqlcode: -84
sqlstate: 42612
SQL0085N The statement name "<name>" is already defined.
Explanation: A previous DECLARE statement already used the statement name specified in the current DECLARE statement.
The current DECLARE statement is not processed. The previous DECLARE statement retains use of the statement name.
User Response: Use a different name for the statement.
SQL0086C A memory allocation error has occurred.
Explanation: During processing, there was not enough memory to continue processing.
User Response: Possible solutions include:
SQL0087N Host variable "<name>" is a structure used where structure references are not permitted.
Explanation: When a structure reference is used in an SQL statement, it is treated as if a comma-separated list of its component fields had been used instead. Since a list of host variables is not permitted in SQL statements such as PREPARE, neither is a reference to a structure with multiple fields.
User Response: Replace the structure reference with an atomic host variable, or with a fully qualified structure field name.
SQL0088N Host variable "<name>" is ambiguous.
Explanation: Host variable "<name>" cannot be uniquely identified. More than one host variable with the same qualification can be found.
The statement cannot be processed.
User Response: Qualify the host variable further, or rename it if it is already fully qualified.
SQL0089N Processing ended after 100 errors were found.
Explanation: The precompiler or binder quits processing after 100 errors were found.
User Response: Fix the errors indicated in the message log and resubmit the command.
SQL0091W Precompilation or binding was ended with "<number-1>" errors and "<number-2>" warnings.
Explanation: The precompilation or binding has terminated with the stated number of warnings and errors.
Precompilation or binding is terminated.
User Response: If warnings or errors occurred, correct the program, if necessary, and retry the precompilation or binding.
SQL0092N No package was created because of previous errors.
Explanation: Because of previous errors, no package was created.
User Response: Correct the errors and retry the precompilation or bind.
SQL0093N The end-of-input was encountered before the statement terminator for EXEC SQL.
Explanation: While processing an SQL statement, the end of source was encountered before the statement terminated.
Precompilation is terminated.
User Response: Ensure that the SQL statement terminates properly.
SQL0094N Binding was ended because of user interrupt request.
Explanation: Binding was terminated because the user may have pressed the interrupt key sequence.
Processing is terminated. No package is created.
User Response: Resubmit the bind, if needed.
If installing the sample database, drop it and install the sample database again.
SQL0095N No bind file was created because of previous errors.
Explanation: Because of previous errors, no bind file was created.
No bind file is created.
User Response: Correct the errors and retry the precompilation.