Transcription

IBM DB2 Universal Database Message ReferenceVolume 2Version 8GC09-4841-00

IBM DB2 Universal Database Message ReferenceVolume 2Version 8GC09-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 atwww.ibm.com/planetwideTo 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.

ContentsAbout This Guide . . . .Who Should Use This Guide .How This Guide Is StructuredConventions . . . . .vvvvChapter 1. Introduction to Messages . . . 1Message Structure . . . . . . . . . . 1Information Available Online. . . . . . . 1Other DB2 Messages . . . . . . . . 3Other Message Sources. . . . . . . . 4Chapter 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 Copyright IBM Corp. 1993 - 2002SQL3400 - SQL3499 .SQL3500 - SQL3599 .SQL3600 - SQL3699 .SQL3700 - SQL3799 .SQL3800 - SQL3899 .SQL3900 - SQL3999 .SQL4000 - SQL4099 .SQL4100 - SQL4199 .SQL4300 - SQL4399 .SQL4400 - SQL4499 .SQL4900 - SQL4999 .SQL5000 - SQL5099 .SQL5100 - SQL5199 .SQL6000 - SQL6099 .SQL6100 - SQL6199 .SQL6500 - SQL6599 .SQL7000 - SQL7099 .SQL8000 - SQL8099 .SQL8100 - SQL8199 .SQL9300 - SQL9399 .SQL10000 - SQL10099SQL20000 - SQL20099SQL20100 - SQL20199SQL20200 - SQL20299SQL22000 - SQL22099SQL22200 - SQL22299SQL27900 - SQL27999SQL29000 - SQL29099SQL30000 - SQL30099SQL30100 - hapter 3. SQLSTATE Messages . . . .Class Code 00 Unqualified SuccessfulCompletion . . . . . . . . . . . .Class Code 01 Warning . . . . . . . .Class Code 02 No Data . . . . . . . .Class Code 07 Dynamic SQL Error . . . .Class Code 08 Connection Exception . . .Class Code 09 Triggered Action ExceptionClass Code 0A Feature Not Supported . . .Class Code 0D Invalid Target TypeSpecification . . . . . . . . . . .Class Code 0F Invalid Token . . . . . .Class Code 0K Invalid RESIGNAL statement555556556560560561561561562562562iii

Class Code 20 Case Not Found for CaseStatement . . . . . . . . . . . .Class Code 21 Cardinality Violation . . . .Class Code 22 Data Exception. . . . . .Class Code 23 Constraint Violation . . . .Class Code 24 Invalid Cursor State . . . .Class Code 25 Invalid Transaction State . .Class Code 26 Invalid SQL StatementIdentifier. . . . . . . . . . . . .Class Code 28 Invalid AuthorizationSpecification . . . . . . . . . . .Class Code 2D Invalid TransactionTermination . . . . . . . . . . . .Class Code 2E Invalid Connection Name . .Class Code 34 Invalid Cursor Name . . .Class Code 36 Invalid Cursor SpecificationClass Code 38 External Function ExceptionClass Code 39 External Function CallException . . . . . . . . . . . .Class Code 3B Invalid SAVEPOINT . . . .Class Code 40 Transaction Rollback . . . .Class Code 42 Syntax Error or Access RuleViolation . . . . . . . . . . . . .Class Code 44 WITH CHECK OPTIONViolation . . . . . . . . . . . . .Class Code 46 Java DDL . . . . . . .Class Code 51 Invalid Application State . .Class Code 53 Invalid Operand orInconsistent Specification . . . . . . .Class Code 54 SQL or Product LimitExceeded . . . . . . . . . . . .Class Code 55 Object Not in PrerequisiteState . . . . . . . . . . . . . .Class Code 56 Miscellaneous SQL or ProductError . . . . . . . . . . . . . .Class Code 57 Resource Not Available orOperator Intervention . . . . . . . .Class Code 58 System Error . . . . . 69582582582583584585Appendix B. DB2 Universal Databasetechnical information . . . . . . . . 599Overview of DB2 Universal Databasetechnical information . . . . . . . . 599FixPaks for DB2 documentation . . . . 599Categories of DB2 technical information599Printing 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 . . . . . . . . . . . 617Keyboard Input and Navigation . . . . 617Accessible Display . . . . . . . . 617Alternative Alert Cues . . . . . . . 618Compatibility with Assistive Technologies 618Accessible Documentation . . . . . . 618DB2 tutorials . . . . . . . . . . . 618DB2 Information Center accessed from abrowser . . . . . . . . . . . . . 619586587588Appendix C. Notices . . . . . . . . 621Trademarks . . . . . . . . . . . . 624IndexAppendix A. Communications Errors . . 591TCP/IP . . . . . . . . . . . . . 591APPC . . . . . . . . . . . . . . 595NETBIOS . . . . . . . . . . . . 596ivMessage Reference, Volume 2. 627Contacting IBM . . . . . . . . . . 629Product information . . . . . . . . . 629

About This GuideThe purpose of this book is to list the messages returned by variouscomponents of DB2.Who Should Use This GuideThe Message Reference is designed to be used by anyone using DB2 andrequiring more detailed information about returned messages.How This Guide Is StructuredThis 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 - 2002v

viMessage Reference, Volume 2

Chapter 1. Introduction to MessagesIt 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 StructureMessage 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 OnlineThe following DB2 messages are accessible from the operating systemcommand line:Prefix DescriptionASNmessages generated by DB2 ReplicationCCAmessages generated by the Client Configuration AssistantCLImessages generated by Call Level InterfaceDBAmessages generated by the Database Administration toolsDBImessages generated by installation and configuration Copyright IBM Corp. 1993 - 20021

DBTmessages generated by the Database toolsDB2messages generated by the command line processorDWCmessages generated by the Data Warehouse CenterGSEmessages generated by the DB2 Spatial ExtenderICCmessages generated by the Information Catalog CenterSATmessages generated in a satellite environmentSPMmessages generated by the sync point managerSQLmessages 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 “? SQL0000N”v db2 “? sql0000”v 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” moreHelp can also invoked in the interactive input mode. To enter the interactiveinput mode, enter the following at the operating system command prompt:db22Message 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”ordb2 “? 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.AUDmessages generated by the DB2 Audit facility.DIAdiagnostics 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.GOVmessages 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 orChapter 1. Introduction To Messages3

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.4Message Reference, Volume 2

Chapter 2. SQL MessagesEach 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 - SQL0099SQL0000WStatement processing wassuccessful.SQL0001NBinding or precompilation did notcomplete successfully.Explanation: The SQL statement executedsuccessfully, unless a warning conditionoccurred.Explanation: For reasons specified in theprevious messages, the bind or precompilerequest was unsuccessful.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.No package is created.Refer to the Application Development Guide.SQL0002Nsqlcode: 0Explanation: For reasons specified in theprevious messages, the bind file name cannot beused as specified.sqlstate: 00000, 01003, 01004, 01503, 01504, 01506,1509, 01517 Copyright IBM Corp. 1993 - 2002User Response: Refer to the messages in themessage file. Resubmit the command.If installing the sample database, drop it andinstall the sample database again.The bind file name is not valid.5

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.SQL0003NThe database name is not valid.Explanation: For reasons specified in theprevious messages, the database name cannot beused as specified.No package is created.User Response: Refer to the messages in themessage file. Resubmit the command.SQL0004NThe password is not valid.Explanation: The password contains charactersthat are not valid or the password is too long.SQL0007NThe 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:“ data source :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: -7sqlstate: 42601No package is created.User Response: Resubmit the command with avalid password.SQL0005NThe message file name is notvalid.SQL0008NThe token token found in a hostvariable declaration is not valid.Explanation: A host variable declaration hasinvalid syntax. The precompiler cannot identifythe host variable.Explanation: For reasons specified in theprevious messages, the message file name cannotbe used as specified.The statement cannot be processed. None of thehost variables declared in the statement (up tothe semicolon) are accepted.No package is created.User Response: Examine the syntax of the hostvariable declaration.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.SQL0006NThe datetime format parameter isnot valid.Explanation: The value of the datetime formatparameter is not in the valid range of 0 through3.No package is created.User Response: Resubmit the command with avalid format parameter.6Message Reference, Volume 2SQL0009WAn 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.

SQL0010NThe string constant beginningwith string does not have anending string delimiter.Explanation: The statement contains a stringconstant, beginning with string, that is notterminated properly.The statement cannot be processed.User Response: Examine the statement formissing apostrophes in the indicated stringconstant.sqlcode: -10The comment is not terminated.Explanation: The comment is not terminatedproperly.The statement cannot be processed.User Response: Examine the statement for amissing or extra comment delimiter in theindicated comment.SQL0012WCorrelation 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: 12sqlstate: 01545An 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 nam