message reference, volume 2 - san diego …users.sdsc.edu/~jrowley/db2/messages v2.pdf4 message...

IBM

DB2 Universal Database

Message ReferenceVolume 2

Version 8

GC09-4841-00

Before using this information and the product it supports, be sure to read the general information under Notices.

This document contains proprietary information of IBM. It is provided under a license agreement and is protected bycopyright law. The information contained in this publication does not include any product warranties, and anystatements provided in this manual should not be interpreted as such.

You can order IBM publications online or through your local IBM representative.v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/orderv To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at

www.ibm.com/planetwide

To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU(426-4968).

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1993 - 2002. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

http://www.ibm.com/shop/publications/orderhttp://www.ibm.com/planetwide

Contents

About This Guide . . . . . . . . . . vWho Should Use This Guide . . . . . . . vHow This Guide Is Structured . . . . . . v

Conventions . . . . . . . . . . . v

Chapter 1. Introduction to Messages . . . 1Message Structure . . . . . . . . . . 1Information Available Online. . . . . . . 1

Other DB2 Messages . . . . . . . . 3Other Message Sources. . . . . . . . 4

Chapter 2. SQL Messages . . . . . . . 5SQL0000 - SQL0099 . . . . . . . . . . 5SQL0100 - SQL0199 . . . . . . . . . 14SQL0200 - SQL0299 . . . . . . . . . 31SQL0300 - SQL0399 . . . . . . . . . 55SQL0400 - SQL0499 . . . . . . . . . 72SQL0500 - SQL0599 . . . . . . . . . 98SQL0600 - SQL0699 . . . . . . . . . 119SQL0700 - SQL0799 . . . . . . . . . 132SQL0800 - SQL0899 . . . . . . . . . 140SQL0900 - SQL0999 . . . . . . . . . 149SQL1000 - SQL1099 . . . . . . . . . 168SQL1100 - SQL1199 . . . . . . . . . 189SQL1200 - SQL1299 . . . . . . . . . 207SQL1300 - SQL1399 . . . . . . . . . 227SQL1400 - SQL1499 . . . . . . . . . 241SQL1500 - SQL1599 . . . . . . . . . 254SQL1600 - SQL1699 . . . . . . . . . 260SQL1700 - SQL1799 . . . . . . . . . 267SQL1800 - SQL1899 . . . . . . . . . 274SQL1900 - SQL1999 . . . . . . . . . 279SQL2000 - SQL2099 . . . . . . . . . 280SQL2100 - SQL2199 . . . . . . . . . 291SQL2200 - SQL2299 . . . . . . . . . 293SQL2300 - SQL2399 . . . . . . . . . 297SQL2400 - SQL2499 . . . . . . . . . 299SQL2500 - SQL2599 . . . . . . . . . 304SQL2600 - SQL2699 . . . . . . . . . 317SQL2700 - SQL2799 . . . . . . . . . 319SQL2800 - SQL2899 . . . . . . . . . 326SQL3000 - SQL3099 . . . . . . . . . 330SQL3100 - SQL3199 . . . . . . . . . 345SQL3200 - SQL3299 . . . . . . . . . 361SQL3300 - SQL3399 . . . . . . . . . 369

SQL3400 - SQL3499 . . . . . . . . . 375SQL3500 - SQL3599 . . . . . . . . . 378SQL3600 - SQL3699 . . . . . . . . . 386SQL3700 - SQL3799 . . . . . . . . . 388SQL3800 - SQL3899 . . . . . . . . . 391SQL3900 - SQL3999 . . . . . . . . . 392SQL4000 - SQL4099 . . . . . . . . . 398SQL4100 - SQL4199 . . . . . . . . . 401SQL4300 - SQL4399 . . . . . . . . . 410SQL4400 - SQL4499 . . . . . . . . . 412SQL4900 - SQL4999 . . . . . . . . . 414SQL5000 - SQL5099 . . . . . . . . . 423SQL5100 - SQL5199 . . . . . . . . . 429SQL6000 - SQL6099 . . . . . . . . . 434SQL6100 - SQL6199 . . . . . . . . . 452SQL6500 - SQL6599 . . . . . . . . . 454SQL7000 - SQL7099 . . . . . . . . . 463SQL8000 - SQL8099 . . . . . . . . . 466SQL8100 - SQL8199 . . . . . . . . . 470SQL9300 - SQL9399 . . . . . . . . . 471SQL10000 - SQL10099 . . . . . . . . 472SQL20000 - SQL20099 . . . . . . . . 476SQL20100 - SQL20199 . . . . . . . . 498SQL20200 - SQL20299 . . . . . . . . 513SQL22000 - SQL22099 . . . . . . . . 517SQL22200 - SQL22299 . . . . . . . . 518SQL27900 - SQL27999 . . . . . . . . 530SQL29000 - SQL29099 . . . . . . . . 536SQL30000 - SQL30099 . . . . . . . . 538SQL30100 - SQL30199 . . . . . . . . 552

Chapter 3. SQLSTATE Messages . . . . 555Class Code 00 Unqualified SuccessfulCompletion . . . . . . . . . . . . 556Class Code 01 Warning . . . . . . . . 556Class Code 02 No Data . . . . . . . . 560Class Code 07 Dynamic SQL Error . . . . 560Class Code 08 Connection Exception . . . 561Class Code 09 Triggered Action Exception 561Class Code 0A Feature Not Supported . . . 561Class Code 0D Invalid Target TypeSpecification . . . . . . . . . . . 562Class Code 0F Invalid Token . . . . . . 562Class Code 0K Invalid RESIGNAL statement 562

Copyright IBM Corp. 1993 - 2002 iii

Class Code 20 Case Not Found for CaseStatement . . . . . . . . . . . . 562Class Code 21 Cardinality Violation. . . . 562Class Code 22 Data Exception. . . . . . 563Class Code 23 Constraint Violation . . . . 564Class Code 24 Invalid Cursor State . . . . 565Class Code 25 Invalid Transaction State . . 565Class Code 26 Invalid SQL StatementIdentifier. . . . . . . . . . . . . 566Class Code 28 Invalid AuthorizationSpecification . . . . . . . . . . . 566Class Code 2D Invalid TransactionTermination . . . . . . . . . . . . 566Class Code 2E Invalid Connection Name . . 567Class Code 34 Invalid Cursor Name . . . 567Class Code 36 Invalid Cursor Specification 567Class Code 38 External Function Exception 567Class Code 39 External Function CallException . . . . . . . . . . . . 568Class Code 3B Invalid SAVEPOINT . . . . 569Class Code 40 Transaction Rollback . . . . 569Class Code 42 Syntax Error or Access RuleViolation . . . . . . . . . . . . . 569Class Code 44 WITH CHECK OPTIONViolation . . . . . . . . . . . . . 582Class Code 46 Java DDL . . . . . . . 582Class Code 51 Invalid Application State . . 582Class Code 53 Invalid Operand orInconsistent Specification . . . . . . . 583Class Code 54 SQL or Product LimitExceeded . . . . . . . . . . . . 584Class Code 55 Object Not in PrerequisiteState . . . . . . . . . . . . . . 585Class Code 56 Miscellaneous SQL or ProductError . . . . . . . . . . . . . . 586Class Code 57 Resource Not Available orOperator Intervention . . . . . . . . 587Class Code 58 System Error . . . . . . 588

Appendix A. Communications Errors . . 591TCP/IP . . . . . . . . . . . . . 591APPC . . . . . . . . . . . . . . 595NETBIOS . . . . . . . . . . . . 596

Appendix B. DB2 Universal Databasetechnical information . . . . . . . . 599Overview of DB2 Universal Databasetechnical information . . . . . . . . 599

FixPaks for DB2 documentation . . . . 599Categories of DB2 technical information 599

Printing DB2 books from PDF files . . . . 607Ordering printed DB2 books . . . . . . 607Accessing online help . . . . . . . . 608Finding topics by accessing the DB2Information Center from a browser . . . . 609Finding product information by accessingthe DB2 Information Center from theadministration tools . . . . . . . . . 611Viewing technical documentation onlinedirectly from the DB2 HTML DocumentationCD. . . . . . . . . . . . . . . 612Updating the HTML documentation installedon your machine . . . . . . . . . . 613Copying files from the DB2 HTMLDocumentation CD to a Web server . . . . 614Troubleshooting DB2 documentation searchwith Netscape 4.x . . . . . . . . . . 615Searching the DB2 documentation . . . . 615Online DB2 troubleshooting information . . 616Accessibility . . . . . . . . . . . 617

Keyboard Input and Navigation . . . . 617Accessible Display . . . . . . . . 617Alternative Alert Cues . . . . . . . 618Compatibility with Assistive Technologies 618Accessible Documentation . . . . . . 618

DB2 tutorials . . . . . . . . . . . 618DB2 Information Center accessed from abrowser . . . . . . . . . . . . . 619

Appendix C. Notices . . . . . . . . 621Trademarks . . . . . . . . . . . . 624

Index . . . . . . . . . . . . . 627

Contacting IBM . . . . . . . . . . 629Product information . . . . . . . . . 629

iv Message Reference, Volume 2

About This Guide

The purpose of this book is to list the messages returned by variouscomponents of DB2.

Who Should Use This Guide

The Message Reference is designed to be used by anyone using DB2 andrequiring more detailed information about returned messages.

How This Guide Is Structured

This guide lists the possible error messages returned by the variouscomponents of DB2.

ConventionsThe format for date and time, and the characters used as separators for dateand time, are intended for a system configured to use the United StatesEnglish national language format. These may be different on your display,depending on the national language format used by your system.

Copyright IBM Corp. 1993 - 2002 v

vi Message Reference, Volume 2

Chapter 1. Introduction to Messages

It is assumed that you are familiar with the functions of the operating systemwhere DB2 is installed. You can use the information contained in thefollowing chapters to identify an error or problem and resolve the problem byusing the appropriate recovery action. This information can also be used tounderstand where messages are generated and logged.

Message Structure

Message identifiers consist of a three character message prefix, followed by afour or five digit message number, followed by a single letter suffix. Forexample, SQL1042C. For a list of message prefixes, see Information AvailableOnline and Other DB2 Messages on page 3. The single letter suffixdescribes the severity of the error message.

In general, message identifiers ending with a C are severe messages. Thoseending with an E are urgent messages. Message identifiers ending with an Nare error messages, those ending with a W are warning messages and an Iindicates an informational message.

For ADM messages, message identifiers ending with a C are severe messages.Those ending with an E are urgent messages. Message identifiers ending witha W are important messages and an I are indicates an informational messages.

For SQL messages, message identifiers ending with an N are error messages.Those ending with a W indicate warning or informational messages. Messageidentifiers ending with a C indicate critical system errors.

Information Available Online

The following DB2 messages are accessible from the operating systemcommand line:

Prefix Description

ASN messages generated by DB2 Replication

CCA messages generated by the Client Configuration Assistant

CLI messages generated by Call Level Interface

DBA messages generated by the Database Administration tools

DBI messages generated by installation and configuration

Copyright IBM Corp. 1993 - 2002 1

DBT messages generated by the Database tools

DB2 messages generated by the command line processor

DWC messages generated by the Data Warehouse Center

GSE messages generated by the DB2 Spatial Extender

ICC messages generated by the Information Catalog Center

SAT messages generated in a satellite environment

SPM messages generated by the sync point manager

SQL messages generated by the database manager when a warning orerror condition has been detected.

As well, the message text associated with SQLSTATE values is availableonline.

Message identifiers consist of a three character message prefix (see above list),followed by a four or five digit message number. The single digit letter at theend which describes the severity of the error message is optional.

To access help on these error messages, enter the following at the operatingsystem command prompt:

db2 ? XXXnnnnn

where XXX represents the message prefixand where nnnnn represents the message number.

Note: The message identifier accepted as a parameter of the db2 command isnot case sensitive, and the terminating letter is not required.

Therefore, the following commands will produce the same result:v db2 ? SQL0000Nv db2 ? sql0000v db2 ? SQL0000n

If the message text is too long for your screen, use the following command(on unix-based systems and others which support more):

db2 ? XXXnnnnn | more

Help can also invoked in the interactive input mode. To enter the interactiveinput mode, enter the following at the operating system command prompt:

db2

2 Message Reference, Volume 2

Once in the interactive input mode, you can enter commands at the followingcommand prompt:

db2 =>

To get DB2 message help in this mode, type the following at the commandprompt:

?

Note: If the message text exceeds the length of the screen, users withnon-graphical workstations can pipe the output to the more (onunix-based systems) program or redirect the output to a file which canthen be browsed.

The message text associated with a given SQLSTATE value can be retrievedby issuing:

db2 ? nnnnn

or

db2 ? nn

where nnnnn is a five digit SQLSTATE (alphanumeric) and nn is the two digitSQLSTATE class code (first two digits of the SQLSTATE value).

Other DB2 MessagesSome DB2 components return messages that are not available online or arenot described in this manual. Some of the message prefixes may include:

ADM messages generated by many DB2 components. These messages arewritten in the Administration Notification log file and are intended toprovide additional information to System Administrators.

Note: Although the ADM messages are available for reference, themessages are not available online.

AUD messages generated by the DB2 Audit facility.

DIA diagnostics messages generated by many DB2 components. Thesemessages are written in the diagnostics log file db2diag.log, and areintended to provide additional information for users and DB2 servicepersonnel when investigating errors.

GOV messages generated by the DB2 governor utility.

In most cases, these messages provide sufficient information to determine thecause of the warning or error. For more information on the command or

Chapter 1. Introduction To Messages 3

utility that generated the messages, please refer to the appropriate manualwhere the command or utility is documented.

Other Message SourcesWhen running other programs on the system, you may receive messages withprefixes other than those mentioned in this reference.

For information on these messages, refer to the publications that you receivedfor that program product.


Chapter 2. SQL Messages

Each message has a message identifier that consists of a prefix (SQL) and amessage number. Messages are listed in numeric sequence based upon themessage number. There are three message types: notification, warning, andcritical. Message identifiers ending with an N are error messages. Thoseending with a W indicate warning or informational messages. Messageidentifiers ending with a C indicate critical system errors.

The message number is also referred to as the SQLCODE. The SQLCODE ispassed to the application as a positive or negative number, depending on itsmessage type (N, W, or C). N and C yield negative values whereas W yields apositive value. DB2 returns the SQLCODE to the application and theapplication can get the message associated with the SQLCODE. DB2 alsoreturns an SQLSTATE value for conditions that could be the result of an SQLstatement. SQLSTATE values are listed in . Some SQLCODE values haveassociated SQLSTATE values. SQLSTATE values associated with a givenSQLCODE (if applicable) have been documented with each message in thischapter.

Variable parameters for SQL messages are shown as descriptive names.

SQL0000 - SQL0099

SQL0000W Statement processing wassuccessful.

Explanation: The SQL statement executedsuccessfully, unless a warning conditionoccurred.

User Response: Check SQLWARN0 to ensurethat it is blank. If it is blank, the statementexecuted successfully. If it is not blank, awarning condition exists. Check the otherwarning indicators to determine the particularwarning condition. For example, if SQLWARN1is 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 notcomplete successfully.

Explanation: For reasons specified in theprevious messages, the bind or precompilerequest was unsuccessful.

No package is created.

User Response: Refer to the messages in themessage file. Resubmit the command.

If installing the sample database, drop it andinstall the sample database again.

SQL0002N The bind file name is not valid.

Explanation: For reasons specified in theprevious messages, the bind file name cannot beused as specified.

Copyright IBM Corp. 1993 - 2002 5




SQL0003N The database name is not valid.

Explanation: For reasons specified in theprevious messages, the database name cannot beused as specified.



SQL0004N The password is not valid.

Explanation: The password contains charactersthat are not valid or the password is too long.


User Response: Resubmit the command with avalid password.

SQL0005N The message file name is notvalid.

Explanation: For reasons specified in theprevious messages, the message file name cannotbe used as specified.


User Response: Refer to the messages in themessage file. Check the name of the message file.Check the attributes of the message file if itexists. Resubmit the command.

SQL0006N The datetime format parameter isnot valid.

Explanation: The value of the datetime formatparameter is not in the valid range of 0 through3.


User Response: Resubmit the command with avalid format parameter.

SQL0007N The character character followingtext is not valid.

Explanation: The specified character is not avalid character in SQL statements. The text fieldindicates the 20 characters of the SQL statementthat preceded the character that is not valid.

Federated system users: some data sources donot provide the appropriate values for thecharacter and text message tokens. In these cases,character and text will have the following format::UNKNOWN, indicating that theactual values for the specified data source areunknown.

The statement cannot be processed.

User Response: Remove or replace the characterthat is not valid.

sqlcode: -7

sqlstate: 42601

SQL0008N The token token found in a hostvariable declaration is not valid.

Explanation: A host variable declaration hasinvalid syntax. The precompiler cannot identifythe host variable.

The statement cannot be processed. None of thehost variables declared in the statement (up tothe semicolon) are accepted.

User Response: Examine the syntax of the hostvariable declaration.

SQL0009W An attempt to override aprecompiler option was ignored.

Explanation: An attempt was made to overridea precompiler option.

The option is ignored.

User Response: Ensure that all precompileroptions are specified correctly.


SQL0010N The string constant beginningwith string does not have anending string delimiter.

Explanation: The statement contains a stringconstant, beginning with string, that is notterminated properly.


User Response: Examine the statement formissing apostrophes in the indicated stringconstant.

sqlcode: -10

sqlstate: 42603

SQL0011N The comment is not terminated.

Explanation: The comment is not terminatedproperly.


User Response: Examine the statement for amissing or extra comment delimiter in theindicated comment.

SQL0012W Correlation without qualificationhas occurred for the columncolumn.

Explanation: The named column occurs in aSELECT statement, is not explicitly qualified, andoccurs in a table specified in the FROM clause ofan outer select. Consequently, the reference to thecolumn in the SELECT statement has been takento be an outer reference and correlation willoccur.

The statement was processed under theassumption that correlation was intended.

User Response: Ensure that correlation wasintended. It is a good practice to explicitlyqualify intended outer references.

sqlcode: +12

sqlstate: 01545

SQL0013N An empty delimited identifier isnot valid.

Explanation: During precompilation, either acursor name, statement name, database name, orauthorization ID, specified as an empty string,was found. This is not valid. The statementcannot be processed.

User Response: Provide a valid cursor name,statement name, database name, or authorizationID.

SQL0014N The source file name is not valid.

Explanation: The source file name specified inthe call to the precompiler contains invalidcharacters or the pointer to the source file nameis invalid.

No package was created.

User Response: Ensure that the source filename is correct.

SQL0015N The host variable data type token-1is not valid. Use token-2 instead.

Explanation: If the WCHARTYPE CONVERTprecompile option is in effect then the graphichost variable must be declared with the datatype wchar_t, not sqldbchar.

If the WCHARTYPE NOCONVERT precompileoption is in effect (the default) and wchar_t isdefined as a 4-byte integer on this platform, thenthe graphic host variable must be declared withthe data type sqldbchar, not wchar_t.

User Response: Replace the current data type ofthe host variable with the data type specified inthe message.

SQL0017N A RETURN statement must bespecified and executed in an SQLfunction or method.

Explanation: The SQL function or method eitherdoes not contain a RETURN statement, or thefunction or method did not end with theexecution of a RETURN statement.

User Response: Ensure the function or method

Chapter 2. SQL Messages 7

executes a RETURN statement.

sqlcode: -17

sqlstate: 42632

SQL0020W Bind or precompile option(s)(name or value) option-name(s) arenot supported by the targetdatabase and will be ignored.

Explanation: This warning is returned in thefollowing situations:

v one or more options that were specified atprecompile/bind time are not supported bythe target DBMS

v the option value(s) of one or more options thatwere specified at precompile/bind time are notsupported by the target DBMS

The unsupported options/values will be ignored.

Note that the option names in the messagecorrespond to terms used by DB2 UWO.

Enter db2 ? bind or db2 ? prep for a list ofoptions supported by DB2 UWO.

User Response: Ensure the specification of bindor precompile option-name(s) or the associatedoption value(s) was intended while connected tothis DBMS.

SQL0021W Invalid precompiler option optionis ignored.

Explanation: The option specified in themessage is not a valid precompiler option.


User Response: Ensure that all precompileroptions are specified correctly.

SQL0022W Duplicate precompiler optionoption is ignored.

Explanation: The precompiler option option is aduplicate.


User Response: Ensure that all precompileroptions are specified only once.

SQL0023N The database name is not valid.

Explanation: The specified database name is nota valid name.

Precompilation is terminated.

User Response: Ensure that the database nameis spelled correctly and follows the rules forshort identifiers.

SQL0024N A database name was notspecified.

Explanation: No database name was providedto proceed with precompilation.


User Response: Provide a database name.

SQL0025W Binding or precompilationcompleted with warnings.

Explanation: Binding or precompilationsucceeded, but warnings were issued. A packageand/or bindfile was created as requested in thecommand.

User Response: Refer to the messages in themessage file. If necessary, correct the problemsand resubmit the command.

SQL0026N The password is not valid.

Explanation: The specified password is not avalid password.


User Response: Ensure that the passwordprovided follows the rules for valid passwords.

SQL0028C The release number of the bindfile is not valid.

Explanation: The release number of the bindfile is not compatible with the release number ofthe installed version of the database manager.


The bind file cannot be used with the currentversion of the database manager. The commandcannot be processed.

User Response: If possible, repeat theprecompile process with the current databasemanager. Otherwise, use only bind files createdwith a compatible release level of the databasemanager.

SQL0029N INTO clause required.

Explanation: Non-cursor SELECT or VALUESstatements embedded in an application programmust have an INTO clause to denote where theresults of the statement are to be placed.Dynamic SELECT statements do not permit theINTO clause.

User Response: Add the INTO clause to theSELECT or VALUES statement and precompilethe application program again.

sqlcode: -29

sqlstate: 42601

SQL0030N A source file name was notspecified.

Explanation: A source file name was notprovided to proceed with precompilation.


User Response: Specify a source file name.

SQL0031C File name could not be opened.

Explanation: The file name is required but couldnot be opened.


User Response: Ensure that the file namespecified is correct and exists in the file system,and that the file permissions are correct.

If installing the sample database, drop it andinstall the sample database again. If the errorcontinues, reinstall the database manager andthen install the sample database.

SQL0032C Unable to use file name.

Explanation: While reading or writing file name,an error was encountered.


User Response: Retry the precompilation.

SQL0033N name is not a valid bind file.

Explanation: The bind file name specified is nota bind file.

Binding is terminated.

User Response: Ensure that the correct filename was specified.

SQL0034N A bind file name was notspecified.

Explanation: No bind file name was specified toproceed 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 notbe opened.

Binding or precompilation has been terminated.

User Response: Ensure that the system canaccess the file.

SQL0036N The syntax of the file name nameis not valid.

Explanation: If the file is input to theprecompiler, it must have an extension with thecorrect extension for the language being used. Ifthe file is input to the binder, it must have anextension of .bnd. Also, a fully resolved file namewhich is over the platform maximum length willcause this error.

Precompilation or binding is terminated.

User Response: Ensure that the specified filename is correct.


SQL0037W The syntax of the message filename is not valid.

Explanation: The message file name name is notsyntactically correct for this function.

The system redirects the output to the standardoutput device.

User Response: Ensure that the specified filename is correct.

SQL0038W The bind option SQLERRORCONTINUE has been activatedsince it is required when bindingthis DB2-supplied list file toDB2/MVS, SQL/DS, or OS/400.

Explanation: The SQLERROR CONTINUE bindoption is required when binding the followingDB2-supplied list files:

v ddcsmvs.lstv ddcsvm.lstv ddcsvse.lstv ddcs400.lst

This option instructs a DRDA server to create apackage even if there are SQL statements in abind file which it considers invalid. Since not allof the DRDA servers support all of the SQLstatements contained in the DB2-supplied bindfiles, the SQLERROR CONTINUE bind optionmust be used to guarantee that packages arecreated for all of the bind files in the list file.

User Response: No response is necessary. Therequired bind option, SQLERROR CONTINUE,has been specified for you. To avoid receivingthis warning in the future specify theSQLERROR CONTINUE bind option.

SQL0039N The binder did not finishprocessing because the bind file isnot valid.

Explanation: The binder could not process thebind file. The bind file may not be valid becausethe bind file contents were altered accidentally.

The bind file is not processed.

User Response: If possible, repeat theprecompile process to create a new bind file.Otherwise, obtain a new copy of the bind file.

SQL0040N An error occurred on one or morebind files in the list name. Thefollowing files were not bound:list.

Explanation: For reasons specified in theprevious messages in the message file, one ormore bind files were not bound. The list of filesthat were not bound is composed of digits,starting from 1, that indicate the relative positionof the unbound files in the list file. name does notinclude the path specification of the list file.

Only the first 20 bind files in error are listed inthe message. If there were more than 20 bindfiles in error, ellipses (...) are inserted after thelast bind file name in the list.

One or more packages were not created.

User Response: Refer to the messages in themessage file. Check the list file to verify that itcontains valid names. Resubmit the command.

SQL0041N No attempt was made to bind thefiles following file numbernumber in list name because a fatalerror occurred which terminatedprocessing.

Explanation: Some errors encountered duringthe binding process are considered fatal (i.e.system errors, memory errors). If one of theseerrors occurs while processing a file in a list file,processing terminates. No attempt is made tobind the remaining files in the list file.

Such an error occurred while binding thespecified bind file in the list. Note that the digitused to identify the bind file indicates therelative position of the file in the list file.

User Response: Refer to the other messageswhich accompanied this one to resolve the errorswhich occurred. Resubmit the command.


SQL0051N The space required to hold allSQL statements for a singleprogram has exceeded its allowedmaximum.

Explanation: The space required by all SQLstatements in the program cannot fit into thecolumn SECT_INFO in SYSIBM.SYSPLAN.


User Response: Either simplify the program, orsplit the program into smaller, separateprograms, or do both.

SQL0053W No SQL statements were found inthe program.

Explanation: The specified source file containsno SQL statements.

If binding, an empty package is created.

User Response: Ensure that you areprecompiling or binding the correct program.

SQL0055N Source input file is empty.

Explanation: The program source input filecontained no data.


User Response: Ensure that the correct inputfile was specified.

SQL0056N An SQLSTATE or SQLCODEvariable declaration is in a nestedcompound statement.

Explanation: An SQLSTATE or SQLCODEvariable declaration is in a nested compoundstatement instead of the outermost compoundstatement in the SQL routine.


User Response: Declare the SQLSTATE andSQLCODE variables only in the outermostcompound statement of the SQL routine.

sqlcode: -56

sqlstate: 42630

SQL0057N A RETURN statement in an SQLfunction or method must includea return value.

Explanation: A RETURN statement is specifiedin the SQL function or method withoutspecifying a value to return.


User Response: Specify a value on the RETURNstatement.

sqlcode: -57

sqlstate: 42631

SQL0058N The data type of the RETURNstatement value in an SQLprocedure must be INTEGER.

Explanation: A RETURN statement is specifiedin the SQL procedure with a value or expressionthat is not of the INTEGER data type.


User Response: Specify a value on the RETURNstatement that has a data type of INTEGER.

sqlcode: -58

sqlstate: 428F2

SQL0060W The name precompiler is inprogress.

Explanation: This message is written to thestandard output device when the precompilerbegins processing. The token name refers to theparticular language precompiler which wasinvoked.

Processing continues.

User Response: No action is required.

SQL0061W The binder is in progress.

Explanation: This message is written to thestandard output device when the binder beginsprocessing.

Processing continues.



SQL0062W Starting INCLUDE of file name.

Explanation: An INCLUDE statement has beenencountered. The precompiler is now processingthe INCLUDE file.


SQL0063W Completed INCLUDE of file name.

Explanation: The precompiler has completedprocessing the INCLUDE file. It will resumeprocessing the file which contained theINCLUDE statement.


SQL0064N File name directly or indirectlyINCLUDEs itself.

Explanation: A cyclic INCLUDE has beenencountered. A precompiler input file cannotINCLUDE itself, nor be INCLUDEd by a file itINCLUDEs.

The specified file is not INCLUDEd.

User Response: Check the nesting of theINCLUDE files, and remove any cycles.

SQL0065N An unexpected end-of-line wasencountered in a host variabledeclaration.

Explanation: A host variable declaration has aninvalid syntax. An end-of-line was encounteredbefore the declaration was complete.


User Response: Examine the syntax of the hostvariable declaration.

SQL0078N Parameter names must bespecified for routine routine-name.

Explanation: The routine routine-name does nothave parameter names specified for allparameters. When the routine is defined withLANGUAGE SQL or SQLMACRO a parameter

name is required for each parameter defined.


User Response: Ensure that each definedparameter includes a parameter name.

sqlcode: -78

sqlstate: 42629

SQL0079N The Schema name for thedeclared global temporary table orindex name must be SESSION, notschema-name.

Explanation: The schema name name for adeclared temporary table or an index on adeclared global temporary table must beSESSION. The statement is specifying an explicitschema-name of schema-name for the declaredglobal temporary table or index on a declaredglobal temporary table. This is not allowed.


User Response: Change the statement in one ofthe following ways:

v Change the schema name to SESSION.v Remove the schema name and let DB2 use the

default value, SESSION.

sqlcode: -79

sqlstate: 428EK

SQL0081N SQLCODE sqlcode returned duringprecompilation/bind.

Explanation: While precompiling or binding theprogram, an unexpected SQLCODE sqlcode wasreturned from the database manager.


User Response: Inspect the SQLCODE todetermine the problem and take the appropriateaction.


SQL0082C An error has occurred which hasterminated processing.

Explanation: A previous, non-SQL error hascaused processing to terminate.

Precompile/bind/rebind is terminated. Nopackage was created.

User Response: Correct the situation thatcaused the previous error and retry theoperation.

SQL0083C A memory allocation error hasoccurred.

Explanation: During processing, there was notenough memory to continue processing.

User Response: Possible solutions include:

v Ensure that your system has sufficient real andvirtual memory.

v Remove background processes.

If you continue to receive this message afterattempting the suggested solutions, contact IBMCustomer Support.

SQL0084N An EXECUTE IMMEDIATEstatement contains a SELECT orVALUES statement.

Explanation: A SELECT or VALUES statementwas used in an EXECUTE IMMEDIATEstatement.


User Response: The implied function is notsupported. Prepare the SELECT or VALUESstatement. Then use OPEN, FETCH, and CLOSE.

sqlcode: -84

sqlstate: 42612

SQL0085N The statement name name isalready defined.

Explanation: A previous DECLARE statementalready used the statement name specified in thecurrent DECLARE statement.

The current DECLARE statement is notprocessed. The previous DECLARE statementretains use of the statement name.

User Response: Use a different name for thestatement.

SQL0086C A memory allocation error hasoccurred.

Explanation: During processing, there was notenough memory to continue processing.

User Response: Possible solutions include:

v Verify that your system has the requiredmemory.

v Remove background processes.

SQL0087N Host variable name is a structureused where structure referencesare not permitted.

Explanation: When a structure reference is usedin an SQL statement, it is treated as if acomma-separated list of its component fields hadbeen used instead. Since a list of host variables isnot permitted in SQL statements such asPREPARE, neither is a reference to a structurewith multiple fields.

User Response: Replace the structure referencewith an atomic host variable, or with a fullyqualified structure field name.

SQL0088N Host variable name is ambiguous.

Explanation: Host variable name cannot beuniquely identified. More than one host variablewith the same qualification can be found.


User Response: Qualify the host variablefurther, or rename it if it is already fullyqualified.

SQL0089N Processing ended after 100 errorswere found.

Explanation: The precompiler or binder quitsprocessing after 100 errors were found.


User Response: Fix the errors indicated in themessage log and resubmit the command.

SQL0091W Precompilation or binding wasended with number-1 errors andnumber-2 warnings.

Explanation: The precompilation or binding hasterminated with the stated number of warningsand errors.

Precompilation or binding is terminated.

User Response: If warnings or errors occurred,correct the program, if necessary, and retry theprecompilation or binding.

SQL0092N No package was created becauseof previous errors.

Explanation: Because of previous errors, nopackage was created.

User Response: Correct the errors and retry theprecompilation or bind.

SQL0093N The end-of-input was encounteredbefore the statement terminatorfor EXEC SQL.

Explanation: While processing an SQLstatement, the end of source was encounteredbefore the statement terminated.


User Response: Ensure that the SQL statementterminates properly.

SQL0094N Binding was ended because ofuser interrupt request.

Explanation: Binding was terminated becausethe user may have pressed the interrupt keysequence.

Processing is terminated. No package is created.

User Response: Resubmit the bind, if needed.


SQL0095N No bind file was created becauseof previous errors.

Explanation: Because of previous errors, nobind file was created.

No bind file is created.

User Response: Correct the errors and retry theprecompilation.

SQL0097N Variables or parameters of LONGVARCHAR or LONGVARGRAPHIC data types are notsupported in SQL routines.

Explanation: SQL routines (procedures,functions or methods) do not support variablesor parameters of LONG VARCHAR or LONGVARGRAPHIC data types.

User Response: Do not use variables orparameters of LONG VARCHAR or LONGVARGRAPHIC data types in SQL routines. ForLONG VARCHAR, use VARCHAR with anexplicit length. For LONG VARGRAPHIC, useVARGRAPHIC with an explicit length.

sqlcode: -97

sqlstate: 42601

SQL0100 - SQL0199


SQL0100W No row was found for FETCH,UPDATE or DELETE; or the resultof a query is an empty table.

Explanation: One of the following conditions istrue:

v No row was found that meets the searchconditions specified in an UPDATE orDELETE statement.

v The result of a SELECT statement was anempty table.

v A FETCH statement was executed when thecursor was positioned after the last row of theresult table.

v The result of the SELECT used in an INSERTstatement is empty.

No data was retrieved, updated, or deleted.

User Response: No action is required.Processing can continue.

sqlcode: +100

sqlstate: 02000

SQL0101N The statement is too long or toocomplex.

Explanation: The statement could not beprocessed because it exceeds a system limit foreither length or complexity, or because too manyconstraints or triggers are involved.

If the statement is one that creates or modifies apacked description, the new packed descriptionmay be too large for its corresponding column inthe system catalogs.

Federated system users should also check to seeif the statement:

v Exceeds either a federated server system limitor a data source system limit for length orcomplexity.

v Violates some other data source specific limit.


Note: Where character data conversions areperformed for applications and databases

running under different codepages, theresult of the conversion is exceeding thelength limit.

User Response: Either:

v Break the statement up into shorter or lesscomplex SQL statements.

v Increase the size of the statement heap(stmtheap) in the database configuration file.

v Reduce the number of check or referentialconstraints involved in the statement or reducethe number of indexes on foreign keys.

v Reduce the number of triggers involved in thestatement.

v Federated system users: determine which datasource is failing the statement (see the problemdetermination guide for procedures to followto identify the failing data source) anddetermine the cause of the rejection. If therejection is coming from the federated server,increase the size of the statement heap(stmtheap) in the database configuration file.

sqlcode: -101

sqlstate: 54001

SQL0102N The string constant beginningwith string is too long.

Explanation: One of the following has occurred:

v The comment in the COMMENT ONstatement is greater than 254 bytes.

v The application server name specified in theSQL CONNECT statement is greater than 18characters.

v The string constant beginning with string has alength greater than 32672 bytes. Characterstrings with lengths greater than 32672 bytesor graphic strings with lengths greater than16336 characters can be specified only throughassignment from host variables. Note thatother servers in the DB2 family of productsmay specify a different size limit for characterstrings. Consult the documentation for theappropriate DB2 product for details.

v Federated system users: the datasource-specific limits must not be exceeded in


a pass-through session. For example, acharacter literal larger than 254 bytes includedin a statement sent to DB2 for OS/390 in apass-through session would cause this error.

It may be that data conversion is occurring andthe resultant string is too long. For connectionsbetween applications and databases runningunder different codepages, string constants areconverted from the application codepage to thedatabase codepage. In certain situations, graphicstring constants may be further converted fromthe database codepage to a UCS-2 (UNICODE)encoding, for example when the database hasbeen created with an EUC codepage. This meansthat it is possible to have a resultant string whichis longer than the input string.


User Response: For Comment on Table orComment on Column, reduce the size of thecomment. For the SQL CONNECT statement,reduce the length of the application server name.For other string constants, the requested functionis not available interactively. For an erroroccurring in the context of a non-CONNECTSQL statement embedded in an applicationprogram, assign the long string to a host variableand substitute that variable for the string literalin the SQL statement.

Federated system users: for a pass-throughsession, determine what data source is causingthe error (see the problem determination guidefor the failing data sources). Examine the SQLdialect for that data source to determine whichspecific limit has been exceeded, and adjust thefailing statement as needed.

sqlcode: -102

sqlstate: 54002

SQL0103N The numeric literal literal is notvalid.

Explanation: The indicated literal begins with adigit but is not a valid integer, decimal, orfloating point literal.

Federated system users: a data source-specific

literal representation error has occurred in apass-through session.


User Response: Correct the invalid numericliteral. Federated system users, if the erroroccurred in a pass-through session, determinewhat data source is causing the error (see theproblem determination guide for the failing datasources). Examine the SQL dialect for that datasource to determine which literal representationrule has been violated, and adjust the failingstatement as needed.

sqlcode: -103

sqlstate: 42604

SQL0104N An unexpected token token wasfound following text. Expectedtokens may include: token-list.

Explanation: A syntax error in the SQLstatement was detected at the specified tokenfollowing the text text. The text field indicates the20 characters of the SQL statement that precededthe token that is not valid.

As an aid to the programmer, a partial list ofvalid tokens is provided in the SQLERRM fieldof the SQLCA as token-list. This list assumes thestatement is correct to that point.


User Response: Examine and correct thestatement in the area of the specified token.

sqlcode: -104

sqlstate: 42601

SQL0105N The string constant beginningwith string is not valid.

Explanation: The statement contains a stringconstant beginning with string that is not valid.


User Response: Specify the correct format ofthe string constant. Check for graphic string,paired delimiters, and an even number of byteswithin the string.


Federated system users, see the problemdetermination guide to determine which datasource is causing the error.

sqlcode: -105

sqlstate: 42604

SQL0106N SQL statement begins properlybut is incomplete.

Explanation: The SQL statement was correct upto the point where no more input was found.This may be caused by failure to properly end aliteral. String literals need a final quote mark.

Processing of this SQL statement has ended.

User Response: Check that the statement has allthe necessary parts to complete the desiredfunction and that all clauses are complete.

For PL/I: Check that the SQL statement iscomplete before the semicolon. For Assembler:Check that the continuation rules are properlyfollowed. (A nonblank character must be incolumn 72, and continued lines must start incolumn 16 or beyond.)

For COBOL: Check that the SQL statement iscomplete before END-EXEC.

sqlcode: -106

sqlstate: 42601, 42603

SQL0107N The name name is too long. Themaximum length is length.

Explanation: The name returned as name is toolong. The maximum length permitted for namesof that type is indicated by length.

The names for indexes and constraints can be amaximum length of 18 bytes. The names forcolumns can be a maximum length of 30 bytes.The names for savepoints, tables, views andaliases can be a maximum length of 128 bytes.(This does not include any escape characters, ifpresent.)

SQL variable names, condition names and labelsin SQL routines must not exceed 64 bytes inlength.

A maximum of 30 bytes is permitted for aschema name (object qualifier), with theexception of user-defined types, which allow amaximum of 8 bytes for a schema name.

Host variable names must not exceed 255 bytesin length.

For the SQL CONNECT statement, anapplication server name of up to 18 characters inlength will be accepted at precompilation time.However, at runtime, an application server namewhich is greater than 8 characters in length willcause an error.

Also, a password of up to 18 characters in lengthand an authorization ID of up to 8 characters inlength will be accepted in the SQL CONNECTstatement.

A package version identifier must not exceed 64bytes in length.

Federated system users: if in a pass-throughsession, a data source-specific limit might havebeen exceeded.


Note: Where character data conversions areperformed for applications and databasesrunning under different codepages, theresult of the conversion is exceeding thelength limit.

User Response: Choose a shorter name orcorrect the spelling of the object name.

Federated system users: for a pass-throughsession, determine what data source is causingthe error (see the problem determination guidefor the failing data sources). Examine the SQLdialect for that data source to determine whichspecific limit has been exceeded, and adjust thefailing statement as needed.

sqlcode: -107

sqlstate: 42622

SQL0108N The name name has the wrongnumber of qualifiers.

Explanation: The name name is improperlyqualified.


The object given the name name can only haveone qualifier.

A column name is qualified with a table name,which is either qualified or unqualified, or acorrelation name. In some contexts, a columnname requires a table name qualifier.


User Response: Ensure that the name for theobject is qualified correctly.

sqlcode: -108

sqlstate: 42601

SQL0109N The clause clause is not allowed.

Explanation: The indicated clause is notallowed in the context where it appears in theSQL statement.

A subquery, an INSERT statement, or a CREATEVIEW statement cannot have INTO, ORDER BY,or FOR UPDATE clauses. An embedded SELECTstatement cannot have ORDER BY or FORUPDATE clauses. An embedded SELECTstatement cannot contain a set operator except ina subquery. SELECT or VALUES statements usedin cursor declarations cannot have an INTOclause. A RAISE_ERROR function can only beused as a select list item if it is cast to some datatype using the CAST specification.

Federated system users: In a pass-throughsession, a data source-specific restriction mighthave been violated.


User Response: Correct the SQL statement byremoving the clause.

Federated system users: For a pass-throughsession, determine what data source is causingthe error (see the problem determination guidefor the failing data sources). Examine the SQLdialect for that data source to determine whichspecific restriction has been violated, and adjustthe failing statement as needed.

sqlcode: -109

sqlstate: 42601

SQL0110N string is an invalid hexadecimalconstant.

Explanation: The hexadecimal constant string isinvalid. The problem is one of the following:

v An invalid hexadecimal digit was specified.Only 0 to 9, A to F, and a to f are allowed.

v An uneven number of hexadecimal digits wasspecified.

v More than 8000 hexadecimal digits werespecified.

User Response: Correct the constant andresubmit the statement.

sqlcode: -110

sqlstate: 42606

SQL0111N The column function name doesnot include a column name.

Explanation: The specification of the columnfunction name (AVG, MIN, MAX, SUM, orCOUNT(DISTINCT)) was not specified correctlybecause such functions must include a columnname in the operand.


User Response: Specify a column name in theexpression that is the operand to the columnfunction.

NOTE: This error is only applicable to releases ofDB2 prior to Version 2.

sqlcode: -111

sqlstate: 42901

SQL0112N The operand of the columnfunction name includes a columnfunction, a scalar fullselect, or asubquery.

Explanation: The operand of a column functioncannot include a:

v column functionv scalar fullselectv subquery.


In a SELECT list, the operand of an arithmeticoperator cannot be a column function thatincludes the DISTINCT keyword.


User Response: Correct the use of the columnfunction to eliminate the invalid expression andtry again.

sqlcode: -112

sqlstate: 42607

SQL0113N identifier contains a character thatis not allowed or does not containany characters.

Explanation: An SQL-variable-name,parameter-name or condition-name identifiercontains an invalid character. Only charactersthat are valid for an SQL ordinary identifier areallowed. Note that because the identifier isdelimited, folding is not performed anduppercase and lowercase letters are treated asdistinct from each other.

User Response: Correct the identifier andresubmit the statement.

sqlcode: -113

sqlstate: 42601

SQL0117N The number of values assigned isnot the same as the number ofspecified or implied columns.

Explanation:

v The number of insert values in the value list ofthe INSERT statement is not the same as thenumber of columns specified or implied. If nocolumn list is specified, a column list thatincludes all columns of the table or view isimplied.

v The number of values on the right hand sideof an assignment in a SET transition-variablestatement or SET clause of an UPDATEstatement does not match the number ofcolumns on the left hand side.


User Response: Correct the statement to specifyone value for each of the specified or impliedcolumns.

sqlcode: -117

sqlstate: 42802

SQL0118N The table or view that is thetarget of the INSERT, DELETE, orUPDATE statement is alsospecified in a FROM clause.

Explanation: The table or view specified as thetarget of an INSERT, DELETE, or UPDATEstatement also appears in the FROM clause of asubquery within the statement.

The table or view that is the target of an INSERT,UPDATE, or DELETE cannot also be used tosupply the values to be inserted or to qualify therows to be inserted, updated, or deleted.


This message is only applicable to Version 1.2servers and earlier, and hosts accessed throughDB2 Connect.

User Response: The implied function is notsupported. To attempt to obtain the desiredresult, create a temporary copy of the object tableor view and address the subselect to that copy.

sqlcode: -118

sqlstate: 42902

SQL0119N An expression starting withexpression-start specified in aSELECT clause, HAVING clause,or ORDER BY clause is notspecified in the GROUP BYclause or it is in a SELECT clause,HAVING clause, or ORDER BYclause with a column functionand no GROUP BY clause isspecified.

Explanation: The SELECT statement has one ofthe following errors:

v The identified expression and a columnfunction are contained in the SELECT clause,


HAVING clause, or ORDER BY clause butthere is no GROUP BY clause

v The identified expression is contained in theSELECT clause, HAVING CLAUSE, or ORDERBY clause but is not in the GROUP BY clause.

The identified expression is an expression thatstarts with expression-start. The expression maybe a single column name.

If the NODENUMBER or PARTITION functionsare specified in the HAVING clause, then allpartitioning key columns of the underlying tableare considered to be in the HAVING clause.


User Response: Correct the statement byincluding the expression in the GROUP BYclause that are in the SELECT clause, HAVINGclause, or ORDER BY clause or by removing thecolumn function from the SELECT statement.

sqlcode: -119

sqlstate: 42803

SQL0120N A WHERE clause, GROUP BYclause, SET clause, or SETtransition-variable statementcontains a column function.

Explanation: A WHERE clause can contain acolumn function only if that clause appearswithin a subquery of a HAVING clause and theargument of the column function is a correlatedreference to a group. A GROUP BY clause cancontain a column function only if the argumentof the column function is a correlated referenceto a column in a different subselect than the onecontaining the GROUP BY clause. A SET clauseof an UPDATE statement or a SETtransition-variable statement can only include acolumn function within a fullselect on the righthand side of an assignment.


User Response: Change the statement so thatthe column function is not used or used onlywhere it is supported.

sqlcode: -120

sqlstate: 42903

SQL0121N The column name is specifiedmore than once in the INSERT,UPDATE or SETtransition-variable statement.

Explanation: The same column name is specifiedmore than once in the list of columns of anINSERT statement, the left hand side ofassignments in the SET clause of an UPDATEstatement, or the left hand side of assignments inthe SET transition-variable statement. Note thatthis error may occur when updating or insertinginto a view where more than one column of theview is based on the same column of a basetable.


User Response: Correct the syntax of thestatement so each column name is specified onlyonce.

sqlcode: -121

sqlstate: 42701

SQL0122N A SELECT statement with noGROUP BY clause contains acolumn name and a columnfunction in the SELECT clause, ora column name is contained in theSELECT clause but not in theGROUP BY clause.

Explanation: The SELECT statement has one ofthe following errors:

v A column name and a column function arecontained in the SELECT clause but there is noGROUP BY clause.

v A column name is contained in the SELECTclause but not in the GROUP BY clause.

The column may be contained in a scalarfunction.

If the NODENUMBER or PARTITION functionsare specified in the SELECT clause, then all


partitioning key columns of the underlying tableare considered to be in the SELECT clause.


User Response: Correct the statement byincluding the columns in the GROUP BY clausethat are in the SELECT clause or by removingthe columns from the SELECT clause.

sqlcode: -122

sqlstate: 42803

SQL0123N The parameter in position n in thefunction name must be a constantor a keyword.

Explanation: The parameter in position n in thefunction name is not a constant when it isrequired to be a constant or a keyword when it isrequired to be a keyword.

User Response: Ensure that each argument ofthe function conforms to the definition of thecorresponding parameter.

sqlcode: -123

sqlstate: 42601

SQL0125N The column number in theORDER BY clause is either lessthan one or greater than thenumber of columns in the resulttable.

Explanation: The ORDER BY clause in thestatement contains a column number that iseither less than 1 or greater than the number ofcolumns in the result table (the number of itemsin the SELECT clause).


User Response: Correct the syntax of theORDER BY clause so each column identifierproperly identifies a column of the result table.

sqlcode: -125

sqlstate: 42805

SQL0127N DISTINCT is specified more thanonce.

Explanation: The DISTINCT qualifier cannot beused:

v In both the SELECT clause and a columnfunction

v In two or more column functions in the sameSELECT statement.


User Response: This error is only applicable toreleases of DB2 prior to DB2 Version 2 and hostsaccessed through DB2 Connect.

sqlcode: -127

sqlstate: 42905

SQL0129N The statement contains too manytable names (the maximum is 15).

Explanation: The SQL statement contains toomany table names. A single SQL statement canreference up to 15 tables. Each table in any viewreferenced is included in this limit.


User Response: Break the SQL statement intotwo or more simple statements with 15 or fewertable references.

This message is only applicable to Version 1.2servers and earlier, and hosts accessed throughDB2 Connect.

sqlcode: -129

sqlstate: 54004

SQL0130N The ESCAPE clause is not a singlecharacter, or the pattern stringcontains an invalid occurrence ofthe escape character.

Explanation: The escape character must be asingle character no more than two bytes inlength. It can only appear in the pattern string ifit is followed by itself, a percent sign, or anunderscore. For more information about the


ESCAPE clause on the LIKE predicate, refer tothe SQL Reference.

User Response: Correct the pattern string or theescape character accordingly.

sqlcode: -130

sqlstate: 22019, 22025

SQL0131N The operands of a LIKE predicatehave incompatible data types.

Explanation: If the expression to the left of aLIKE or NOT LIKE is of type character, theexpression to the right must be of type character.

If the expression to the left is of type graphic, theexpression to the right must be of type graphic.

If the expression to the left is of type BLOB, theexpression to the right must be of type BLOB.


User Response: Correct the expressions of theLIKE predicate to be the same data type.

sqlcode: -131

sqlstate: 42818

SQL0132N A LIKE predicate or POSSTRscalar function is not validbecause the first operand is not astring expression or the secondoperand is not a string.

Explanation: A LIKE predicate or POSSTRscalar function appearing in the statement is notvalid because either the first operand is not astring expression or the second operand is not astring.

The operand appearing to the left of a LIKE orNOT LIKE predicate or the first operand ofPOSSTR must be a string expression. The valueappearing to the right of the predicate or thesecond operand of POSSTR can be one of:

v a constantv a special registerv a host variable

v a scalar function whose operands are any ofthe above

v an expression concatenating any of the above

with the restrictions that:

v no element in the expression can be of typeLONG VARCHAR, CLOB, LONGVARGRAPHIC, or DBCLOB. In addition itcannot be a BLOB file reference variable.

v the actual length of the expression cannot bemore than 4000 bytes.

A LIKE predicate or POSSTR scalar functioncannot be used with DATE, TIME, orTIMESTAMP.


User Response: Check and correct the syntax ofLIKE and POSSTR

sqlcode: -132

sqlstate: 42824

SQL0134N Improper use of a string column,host variable, constant, orfunction name.

Explanation: The use of the string name is notpermitted.

An expression resulting in a string data typewith a maximum length greater than 255 bytes isnot permitted in:

v A SELECT DISTINCT statementv A GROUP BY clausev An ORDER BY clausev A column function with DISTINCTv A SELECT or VALUES statement of a set

operator other than UNION ALL.

An expression resulting in a LONG VARCHARor LONG VARGRAPHIC data type is notpermitted in:

v A predicate other than EXISTS or NULLv A column functionv The SELECT clause of a subquery of a

predicate other than EXISTS or NULL


v The SELECT clause of a subselect in anINSERT statement

v The value expression of a SET clause in anUPDATE statement unless the expression is aLONG VARCHAR or LONG VARGRAPHIChost variable

v A SELECT statement of a set operator (exceptUNION ALL)

v VARGRAPHIC scalar function.

Federated system users: in a pass-throughsession, a data source-specific restriction cancause this error. See the SQL Referencedocumentation for the failing data sources.


User Response: The requested operation on thestring is not supported.

Note: If it is unclear as to how the 255 byte limitis being exceeded, consider that codepageconversion operations may be required toevaluate the string expression. Dependingon the source and target codepages, thetarget may have a greater length attributethan the source. For more information,refer to the SQL Reference for discussionson string restrictions and stringconversions.

sqlcode: -134

sqlstate: 42907

SQL0135N The input for a long stringcolumn in an INSERT statementor UPDATE statement must befrom a host variable or be thekeyword NULL.

Explanation: The UPDATE or INSERT is usingconstants, column names, or subqueries where itshould be using NULL or a host variable.

A long string column is either a LONGVARCHAR, LONG VARGRAPHIC,VARCHAR(n) where n is greater than 254 butless than or equal to 32767, or VARGRAPHIC(n)

where n is greater than 127 but less than or equalto 16383.

User Response: Refer to the DB2 for VMApplication Programming manual forinformation on the use of long strings. Correctthe statement. Try again.

sqlcode: -135

sqlstate: 56033

SQL0137N The length resulting fromoperation is greater thanmaximum-value.

Explanation: The result of concatenating thegiven operands was longer than what issupported by the result type.

Character string results are limited to 32,700bytes unless one of the operands is a CLOB andthen the limit is 2 gigabytes.

Graphic string results are limited to 16,350characters unless one of the operands is aDBCLOB and then the limit is 1,073,741,823 (1less than 1 gigabyte) double byte characters.

Binary string results (operands are BLOB) arelimited to 2 gigabytes.

User Response: Ensure that the sum of thelengths of the operands does not exceed thesupported maximum and try the operation again.

sqlcode: -137

sqlstate: 54006

SQL0138N The second or third argument ofthe SUBSTR function is out ofrange.

Explanation: One of the following conditionsoccurred:

v The second argument of the SUBSTR functionis less than 1 or greater than M.

v The third argument of the SUBSTR function isan expression with a value less than 0 orgreater than MN+1.


M is the length of the first argument if it is fixedlength or the maximum length of the firstargument if it is varying length. N is the value ofthe second argument.


User Response: Ensure that the second andthird arguments of the SUBSTR function havevalues that conform to the above rules.

sqlcode: -138

sqlstate: 22011

SQL0139W A redundant clause appears in thespecification for column column.

Explanation: The clause in the columnspecification is redundant.

The statement was processed successfully, butthe redundant clause was ignored.

User Response: Correct the columnspecification.

sqlcode: +139

sqlstate: 01589

SQL0142N The SQL statement is notsupported.

Explanation: An embedded SQL statement thatmay be valid for other IBM relational databaseproducts is not supported by the databasemanager.

Federated system users: check to see if an SQLstatement was directed at a data source that doesnot support the SQL statement.


User Response: Change the syntax of the SQLstatement or remove the statement from theprogram.

Federated system users: if the reason isunknown, isolate the problem to the data sourcefailing the request (see the problemdetermination guide for procedures to follow toidentify the failing data source) and examine theSQL dialect for that data source.

SQL0143W The SQL statement is notsupported; invalid syntax isignored.

Explanation: An embedded SQL statement thatmay be valid for other IBM relational databaseproducts is understood but is not supported bythe database manager.

The statement may produce inconsistent orunwanted results.

User Response: Change the syntax of the SQLstatement or remove the statement from theprogram.

SQL0150N The view, typed table,materialized query table, orstaging table in the INSERT,DELETE, or UPDATE statement isa view, typed table, materializedquery table, or staging table forwhich the requested operation isnot permitted.

Explanation: The view, typed table, materializedquery table, or staging table named in theINSERT, UPDATE, or DELETE statement isdefined so that the requested insert, update, ordelete operation cannot be performed.

A view is read only if the SELECT statementcontains any of the following:

v A DISTINCT keywordv A column function in the select listv A GROUP BY or HAVING clausev A FROM clause that identifies one of the

following:

More than one table or view

A read-only view (READONLY column ofSYSCAT.SYSVIEWS is set to Y)

A table or view that is also identified in theFROM clause of a subquery of the SELECTstatement. (NOTE: This only applies toreleases prior to DB2 Version 2.)

v A set operator (other then UNION ALL).v Federated system users: a data source specific

limitation that causes the column not to beupdatable


Note that these conditions do not apply tosubqueries of the SELECT statement.

You cannot insert rows directly into a typed tabledefined on a not instantiable structured type.Subtables of this table may allow inserts.

In general, system maintained materialized querytables and staging tables do not allow the insert,update or delete operations.


User Response: The requested function cannotbe performed on the view, system maintainedmaterialized query table, or staging table.

Federated system users: if the reason isunknown, isolate the problem to the data sourcefailing the request (see the problemdetermination guide for procedures to follow toidentify the failing data source) and examine theobject definition and the update restrictions forthat data source.

sqlcode: -150

sqlstate: 42807

SQL0151N The column name cannot beupdated.

Explanation: The specified column cannot beupdated because one of the following wasattempted.

v the object table is a view, and the specifiedcolumn is derived from a scalar function,expression, keyword, constant, or column of aview where that column cannot be updated.

v the specified column is a non-updatablecolumn of a system catalog, or a columnexplicitly marked as READ ONLY.

Federated system users should check to see ifsome other data source specific limitationprevents the column from being updated.


User Response: If the specified column isderived from a scalar function, expression,

keyword, or non updatable column, omit thecolumn from the set clause of the update or thecolumn of the insert. For a list of updatablecatalogs (and the updatable columns) see theSQL Reference.

Federated system users: if the reason isunknown, isolate the problem to the data sourcefailing the request (see the problemdetermination guide) and examine the objectdefinition and the update restrictions for thatdata source.

sqlcode: -151

sqlstate: 42808

SQL0152N Constraint constraint-name is aactual-constraint-type constraintinstead of a expected-constraint-typeconstraint.

Explanation: An attempt was made to alter ordrop constraint constraint-name, but it is definedas a expected-constraint-type constraint, not as thespecified actual-constraint-type constraint.

User Response: Verify the name and type ofconstraint to be altered or dropped.

sqlcode: -152

sqlstate: 42809

SQL0153N The CREATE VIEW statement orcommon table expression does notinclude a column list.

Explanation: A column list must be specified ina CREATE VIEW statement or a common tableexpression when:

v any element of the SELECT list in the fullselectis other than a column name and is not namedusing the AS clause

v any two elements are the same column namethat were not renamed using the AS clause.

The statement cannot be processed. For aCREATE VIEW statement, the view was notcreated.

User Response: Provide a column name list inthe CREATE VIEW statement or common table


expression or name the columns in the SELECTlist of the fullselect using the AS clause.

sqlcode: -153

sqlstate: 42908

SQL0155N A trigger transition table cannotbe modified.

Explanation: The trigger includes aREFERENCING clause with an OLD_TABLE orNEW_TABLE identified. A DELETE, INSERT orUPDATE triggered SQL statement has used thename specified as the OLD_TABLE orNEW_TABLE as the table to modify.

User Response: Remove the DELETE, INSERTor UPDATE triggered SQL statement from thetriggered action or change the name of thetransition table so that it does not conflict withthe table you are attempting to modify.

sqlcode: -155

sqlstate: 42807

SQL0156N The name used for this operationis not a table.

Explanation: The SQL statements ALTERTABLE, DROP TABLE, SET CONSTRAINTS,CREATE TRIGGER, CREATE INDEX, LOCKTABLE, and RENAME TABLE are applicableonly to tables, not to views. The RUNSTATS andLOAD utilities are also applicable only to tables,not to views.

Federated system users: Some utilities andstatements are not supported in a federatedenvironment. See the Administration Guide formore information.

The statement or utility cannot be processed.

User Response: Verify that the correct tablename is specified in the statement. If an aliasname was supplied, ensure that the alias resolvesto a table.

Federated system users: Verify that the object isnot a nickname.

sqlcode: -156

sqlstate: 42809

SQL0157N name is not allowed in aFOREIGN KEY clause because itdoes not identify a base table.

Explanation: The object name was identified in aFOREIGN KEY clause of a CREATE or ALTERTABLE statement. A FOREIGN KEY clause mustidentify a base table.

The statement cannot be processed. The specifiedtable is not created or altered.

User Response: Correct the statement to specifya base table name in the FOREIGN KEY clause.

If an alias name was supplied, ensure that thealias resolves to a base table.

sqlcode: -157

sqlstate: 42810

SQL0158N The number of columns specifiedfor name is not the same as thenumber of columns in the resulttable.

Explanation: The identifier name could identify:

v a view named in a CREATE VIEW statementv a table name of a common table expressionv a correlation name of a nested table expressionv a materialized query table named in a

CREATE TABLE or ALTER TABLE statement

v a function named in a CREATE FUNCTIONstatement

v a method named in a CREATE METHODstatement.

v a staging table name in a CREATE STAGINGTABLE statement

The number of column names specified must beequal to the number of columns in the resulttable of the associated fullselect. If name is astaging table and the associated materializedquery table has group by clause, the number ofcolumn names specified must be 2 more than thenumber of columns in the materialized querytable for which the staging table is being defined.


If the associated materialized query table has nogroup by clause, the number of column namesspecified must be 3 more than the number ofcolumns in the materialized query table.


User Response: Correct the syntax so that thelist of column names defined for name specify aname for each column of the result table.

sqlcode: -158

sqlstate: 42811

SQL0159N The statement references objectwhich identifies a(n) object-typerather than a(n) expected-object-type.

Explanation: The object object specified as partof the statement or command refers to an objectof type object-type instead of the expected typeexpected-object-type.

The type of the object provided with thestatement or command must match the typeidentified by expected-object-type. For example, ifthe statement is DROP ALIAS PBIRD.T1, thenPBIRD.T1 must be an alias name.

User Response: Change the statement orcommand to properly match the type of objectidentified by expected-object-type.

sqlcode: -159

sqlstate: 42809

SQL0160N The WITH CHECK OPTIONclause is not valid for thespecified view.

Explanation: The WITH CHECK OPTIONclause cannot be used in a view definition if:

v The view is defined as read only. The view isread only if the SELECT statement containsany of the following. (Note that theseconditions do not apply to subqueries of theSELECT statement.)

A DISTINCT keyword

A column function in the selected list

A GROUP BY or HAVING clause

A FROM clause that identifies either:

- More than one table or view

- A read-only view

A set operator (other than UNION ALL).

v The SELECT statement in the CREATE VIEWstatement includes a subquery (except forspecific statistic columns of some catalogtables).

v A view on which the specified view definitionis dependent has an INSTEAD OF triggerdefined.

v A view on which the specified view definitionis dependent contains a text search function.

Federated system users: the WITH CHECKoption is not supported on views that referenceupdatable nicknames.

The statement cannot be processed. The specifiedview was not created.

User Response: Remove the WITH CHECKOPTION clause or change the view definition soit conforms to the rules above.

sqlcode: -160

sqlstate: 42813

SQL0161N The resulting row of the INSERTor UPDATE does not conform tothe view definition.

Explanation: The WITH CHECK OPTIONclause was specified in the view definition that isthe object of the INSERT or UPDATE statement.Consequently, all attempts to insert or updaterows in that view are checked to ensure that theresults conform to the view definition.

The statement cannot be processed. No inserts orupdates are performed, and the contents of theview and underlying base table remainunchanged.

User Response: Examine the view definition todetermine why the requested INSERT orUPDATE was rejected. Note that this may be adata-dependent condition.

Requested INSERT or UPDATE may be trying to


put out of range value(s) in the target column(s).For system catalog updates, see the SQL Referencefor valid ranges of values in various updatablecolumns of catalogs.

Federated system users, if the reason isunknown, isolate the problem to the data sourcefailing the request (see the problemdetermination guide) and examine the objectdefinition and the view definition for that datasource.

sqlcode: -161

sqlstate: 44000

SQL0170N The number of arguments forfunction name is incorrect.

Explanation: The specified scalar function namehas either too few or too many arguments.


User Response: Ensure that the correct numberof arguments is specified for the scalar function.

sqlcode: -170

sqlstate: 42605

SQL0171N The data type, length or value ofargument n of routine name isincorrect.

Explanation: The data type, length or value ofargument n of routine name is incorrect.


User Response: Ensure the arguments of theroutine conform to the rules of the routine.

sqlcode: -171

sqlstate: 42815

SQL0172N name is not a valid function name.

Explanation: The SQL statement includes anunknown scalar function.


User Response: Ensure that you correctly spellthe function name.

sqlcode: -172

sqlstate: 42601

SQL0176N The second, third or fourthargument of the TRANSLATEscalar function is incorrect.

Explanation: The statement is not correct forone or more of the following reasons:

v The translate scalar function does not allowreplacement of a character by anothercharacter which is encoded using a differentnumber of bytes. For example, a single-bytecharacter cannot be replaced with adouble-byte character nor can a double-bytecharacter be replaced with a single-bytecharacter.

v The second and third arguments of thetranslate scalar function must end withcorrectly formed characters.

v The fourth argument of the translate scalarfunction must be a correctly formedsingle-byte character if the first argument isCHAR or VARCHAR.

v The fourth argument of the translate scalarfunction must be a correctly formeddouble-byte character if the first argument isGRAPHIC or VARGRAPHIC.


User Response: Ensure that the second, third,and fourth arguments of the translate scalarfunction have correct values.

sqlcode: -176

sqlstate: 42815

SQL0180N The syntax of the stringrepresentation of a datetime valueis incorrect.

Explanation: The string representation of a date,time, or timestamp value does not conform tothe syntax for the specified or implied data type.


User Response: Ensure that the syntax of thedate, time, or timestamp value conforms to the


syntax for its data type. If the string is notintended to be a date, time, or timestamp value,ensure that when used, it does not imply thatdata type.

Federated system users: the problem might bedue to a date/time representation problem at thedata source. If the reason is unknown, isolate theproblem to the data source failing the requestTroubleshooting Guide and examine thedate/time representation restrictions for that datasource.

sqlcode: -180

sqlstate: 22007

SQL0181N The string representation of adatetime value is out of range.

Explanation: The string representation of a date,time or timestamp value contains a value that isout of range.

This error could be caused by accessing adatetime value from an application using aterritory code whose datetime format is differentthan the one used by the application that createdit. For example, a string datetime value stored inthe format dd/mm/yyyy will not be valid whenread by an application expecting its format to bemm/dd/yyyy.

The correct ranges for date, time, or timestampvalues are as follows:

v 0001 to 9999 for years.v 1 to 12 for months.v 1 to 31 for days when the month is 1, 3, 5, 7, 8,

10, and 12.

v 1 to 30 for days when the month is 4, 6, 9, 11.v 1 to 28 for days when the month is 2 in a

non-leap year.

v 1 to 29 for days when the month is 2 in a leapyear.

v 0 to 24 for hours. If the hour is 24, the otherparts of the time are 0. If the format is USA,the hour cannot be greater than 12.

v 0 to 59 for minutes.v 0 to 59 for seconds.v 0 to 999999 for microseconds.

v 001 to 365 for the day portion of a Juliancalendar date when the year is not a leap year.

v 001 to 366 for the day portion of a Juliancalendar date when the year is a leap year.

Federated system users: the problem might bedue to a date/time representation problem at thedata source. Refer to the data sourcesdocumentation for the ranges for date and timevalues at the data source. If the reason isunknown, isolate the problem to the data sourcefailing the request (see the TroubleshootingGuide) and examine the date/time representationrestrictions for that data source.


User Response: Ensure that the value is withinthe valid range, and the applications datetimeformat is the same as the string value.

sqlcode: -181

sqlstate: 22007

SQL0182N An expression with a datetimevalue or a labeled duration is notvalid.

Explanation: The specified expression containsan improperly used date, time, or timestampvalue or labeled duration.


User Response: Examine the SQL statement todetermine the cause of the problem and correctthe statement.

sqlcode: -182

sqlstate: 42816

SQL0183N A datetime arithmetic operation ordatetime scalar function has aresult that is not within the validrange of dates.

Explanation: The result of an arithmeticoperation is a date or timestamp duration whichis outside the range 0001-01-01 through9999-12-31.


The statement cannot be executed.

User Response: Examine the SQL statement todetermine the cause of the problem. If theproblem is data-dependent, examine the dataprocessed when the error occurred.

sqlcode: -183

sqlstate: 22008

SQL0187N A reference to a current date/timespecial register is invalid.

Explanation: An error indication from theoperating system was detected while retrievingdate/time information.

User Response: Ensure that the system TODclock and timezone settings are correct.

sqlcode: -187

sqlstate: 22506

SQL0190N ALTER TABLE table-namespecified attributes for columncolumn-name that are notcompatible with the existingcolumn.

Explanation: The attributes specified in theALTER COLUMN clause for the columncolumn-name of the table table-name in an ALTERTABLE statement are not compatible with theattributes of the existing column. The error wasreturned for one of the following reasons.

v If a SET DATA TYPE clause is specified, theexisting column:

is not of data type VARCHAR or

has a length that is greater than the lengthspecified in the clause.

v If a SET EXPRESSION clause is specified, theexisting column is not defined as generatedusing an expression.


User Response: Make the attributes specifiedcompatible with the existing column, remove theattribute specification, or specify a differentcolumn name.

sqlcode: -190

sqlstate: 42837

SQL0191N Error occurred because of afragmented MBCS character.

Explanation: Possible causes:

1. User data contained an improperly formedmulti-byte character. For example, the firstbyte of a DBCS character was found, but thesecond character was not.

2. A scalar function, such as SUBSTR orPOSSTR has truncated a multi-bytes stringincorrectly. For these functions, start andlength values must be correct in terms ofbytes, in the context of the database codepage. For a Unicode database, a commoncause of this could be that the start or lengthfor a UTF-8 string are incorrect.

3. A scalar function such as TRANSLATE hasmay have changed the multi-byte string.

Federated syst

message reference, volume 2 - san diego …users.sdsc.edu/~jrowley/db2/messages v2.pdf4 message...

Documents