Message Reference, Volume 2

IBM®

DB2 Universal Database™

Message ReferenceVolume 2

Version 8

GC09-4841-00

��

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/order

v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts atwww.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/order

http://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 “? 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” | 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.





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:“<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: -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.lst

v ddcsvm.lst

v ddcsvse.lst

v 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.




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 thedefault 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.


v Verify that your system has the requiredmemory.


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 function

v scalar fullselect

v 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 constant

v a special register

v 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 statement

v A GROUP BY clause

v An ORDER BY clause

v A column function with DISTINCT

v A SELECT or VALUES statement of a setoperator 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 NULL

v A column function

v The SELECT clause of a subquery of apredicate 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 M−N+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 keyword

v A column function in the select list

v A GROUP BY or HAVING clause

v A FROM clause that identifies one of thefollowing:

– 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 specificlimitation 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 statement

v a table name of a common table expression

v a correlation name of a nested table expression

v a materialized query table named in aCREATE 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 anon-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 source’sdocumentation 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 application’s 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 system users: this situation can also bedetected by the data source.

User Response:

1. Correct the input data and try again.

2. Change the start and length values such thatwhen characters are converted to thedatabase code page, the multi-byte charactersare not truncated incorrectly.

3. Correct the TRANSLATE in error.

Federated system users: if the data is correct,isolate the problem to the data source failing therequest (see the Troubleshooting Guide) andexamine the DBCS restrictions of that datasource. If the data appears to be correct, contactIBM service for assistance.

sqlcode: -191

sqlstate: 22504


SQL0193N In an ALTER TABLE statement,the column column-name has beenspecified as NOT NULL andeither the DEFAULT clause wasnot specified or was specified asDEFAULT NULL.

Explanation: When new columns are added to atable that already exists, a value must beassigned to that new column for all existingrows. By default, the null value is assigned.However, since the column has been defined asNOT NULL, a default value other than null mustbe defined.

User Response: Either remove the NOT NULLrestriction on the column or provide a defaultvalue other than null for the column.

sqlcode: -193

sqlstate: 42601

SQL0197N A qualified column name is notallowed in the ORDER BY clause.

Explanation: The ORDER BY clause of afullselect that includes a set operator (UNION,EXCEPT, INTERSECT) cannot have qualifiedcolumn names.

User Response: Ensure that all column namesin the ORDER BY clause are unqualified.

sqlcode: -197

sqlstate: 42877

SQL0198N The statement string of thePREPARE or EXECUTEIMMEDIATE statement is blankor empty.

Explanation: The host variable that was theobject of the PREPARE or EXECUTEIMMEDIATE statement either contained allblanks or was an empty string.

The PREPARE or EXECUTE IMMEDIATE couldnot be completed.

User Response: Correct the logic of theprogram to ensure that a valid SQL statement isprovided in the operand of the PREPARE orEXECUTE IMMEDIATE statement before it isexecuted.

sqlcode: -198

sqlstate: 42617

SQL0199N The use of reserved word keywordfollowing text is not valid.Expected tokens may include:token-list.

Explanation: A syntax error in the SQLstatement was detected at the point in thestatement when the reserved word keywordappears following text. The text field indicatesthe 20 characters of the SQL statement thatpreceded the reserved word. Clauses in thestatement may be in the wrong order.

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 the statement in thekeyword area. Add a colon or SQL delimiter, ifmissing. Verify that the clauses are in the correctorder. If the reserved word identified in themessages is listed as a reserved word, make theword a delimited identifier.

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

sqlcode: -199

sqlstate: 42601

SQL0200 - SQL0299


SQL0203N A reference to column name isambiguous.

Explanation: The column name is used in thestatement and there is more than one possiblecolumn to which it could refer. This could be theresult of:

v two tables specified in a FROM clause thathave columns with the same name

v the ORDER BY clause refers to a name thatapplies to more than one column in the selectlist

v a reference to a column from the subject tablein a CREATE TRIGGER statement does notuse the correlation name to indicate if it refersto the old or new transition variable.

The column name needs further information toestablish which of the possible table columns itis.


User Response: Add a qualifier to the columnname. The qualifier is the table name orcorrelation name. A column may need to berenamed in the select list.

sqlcode: -203

sqlstate: 42702

SQL0204N name is an undefined name.

Explanation: This error is caused by one of thefollowing:

v The object identified by name is not defined inthe database.

v A data type is being used. This error can occurfor the following reasons:

– If name is qualified, then a data type withthis name does not exist in the database.

– If name is unqualified, then the user’sfunction path does not contain the schemato which the desired data type belongs.

– The data type does not exist in the databasewith a create timestamp earlier than thetime the package was bound (applies tostatic statements).

– If the data type is in the UNDER clause of aCREATE TYPE statement, the type namemay be the same as the type being defined,which is not valid.

v A function is being referenced in one of:

– a DROP FUNCTION statement

– a COMMENT ON FUNCTION statement

– the SOURCE clause of a CREATEFUNCTION statement

If name is qualified, then the function doesnot exist. If name is unqualified, then afunction of this name does not exist in anyschema of the current function path. Notethat a function cannot be sourced on theCOALESCE, NULLIF, or VALUE built-infunctions.

This return code can be generated for any typeof database object.

Federated system users: the object identified byname is not defined in the database or name isnot a nickname in a DROP NICKNAMEstatement.

Some data sources do not provide theappropriate values for name. In these cases, themessage token will have the following format:“OBJECT:<data source> TABLE/VIEW”,indicating that the actual value for the specifieddata source is unknown.


User Response: Ensure that the object name(including any required qualifiers) is correctlyspecified in the SQL statement and it exists. Formissing data type or function in SOURCE clause,it may be that the object does not exist, OR itmay be that the object does exist in someschema, but the schema is not present in yourfunction path.

Federated system users: if the statement is DROPNICKNAME, make sure the object is actually anickname. The object might not exist in thefederated database or at the data source. Verifythe existence of the federated database objects (ifany) and the data source objects (if any).


sqlcode: -204

sqlstate: 42704

SQL0205N Column or attribute name is notdefined in object-name.

Explanation: If object-name is a table or view,then name is a column that is not defined inobject-name. If object-name is a structured type,then name is an attribute that is not defined inobject-name.

Federated system users: object-name could refer toa nickname.


User Response: If object-name is a table or view,verify that the column and table or view names(including any required qualifiers) are specifiedcorrectly in the SQL statement. If object-name is astructured type, verify that the attribute and typenames (including any required qualifiers) arespecified correctly in the SQL statement.

Also, if you receive this error during a REORGor an IMPORT, the column names in the indexmay violate the database manager naming rulesas defined in the Administration Guide.

sqlcode: -205

sqlstate: 42703

SQL0206N name is not valid in the contextwhere it is used.

Explanation: This error can occur in thefollowing cases:

v For an INSERT or UPDATE statement, thespecified column is not a column of the table,or view that was specified as the object of theinsert or update.

v For a SELECT or DELETE statement, thespecified column is not a column of any of thetables or views identified in a FROM clause inthe statement.

v For an ORDER BY clause, the specified columnis a correlated column reference in a subselect,which is not allowed.

v For a CREATE TRIGGER, CREATE METHODor CREATE FUNCTION statement:

– The reference name does not resolve to thename of a column, local variable ortransition variable.

– The condition name name specified in theSIGNAL statement has not been declared.

v For a CREATE TRIGGER statement:

– A reference is made to a column of thesubject table without using an OLD orNEW correlation name.

– The left hand side of an assignment in theSET transition-variable statement in thetriggered action specifies an old transitionvariable where only a new transitionvariable is supported.

v For a CREATE FUNCTION statement with aPREDICATES clause:

– The RETURN statement of the SQL functionreferences a variable that is not a parameteror other variable that is in the scope of theRETURN statement.

– The FILTER USING clause references avariable that is not a parameter name or anexpression name in the WHEN clause.

– The search target in an index exploitationrule does not match some parameter nameof the function that is being created.

– A search argument in an index exploitationrule does not match either an expressionname in the EXPRESSION AS clause or aparameter name of the function beingcreated.

v For a CREATE INDEX EXTENSION statement,the RANGE THROUGH clause or the FILTERUSING clause references a variable that is nota parameter name that can be used in theclause.


User Response: Verify that the names arespecified correctly in the SQL statement. For aSELECT statement, ensure that all the requiredtables are named in the FROM clause. For asubselect in an ORDER BY clause, ensure thatthere are no correlated column references. If acorrelation name is used for a table, verify that


subsequent references use the correlation nameand not the table name.

For a CREATE TRIGGER statement, ensure thatonly new transition variables are specified on theleft hand side of assignments in the SETtransition-variable statement and that anyreference to columns of the subject table have acorrelation name specified.

sqlcode: -206

sqlstate: 42703

SQL0207N A column name is not allowed inthe ORDER BY clause of aSELECT statement used with a setoperator.

Explanation: A SELECT statement with a setoperator contains an ORDER BY clause, whichspecifies column names. In this case, the list ofcolumns in the ORDER BY clause must containonly integers.


User Response: Specify only integers in the listof columns in the ORDER BY clause.

NOTE: This error is only applicable to releases ofDB2 prior to Version 2 and hosts accessedthrough DB2 Connect.

sqlcode: -207

sqlstate: 42706

SQL0208N The ORDER BY clause is notvalid because column name is notpart of the result table.

Explanation: The statement is not valid becausea column name specified in the ORDER BY list isnot specified in the SELECT list and is not in theresult table. Only columns in the result table canbe used to order that result when the fullselect ofthe select-statement is not a subselect.


User Response: To correct the syntax of thestatement, either add the specified column to theresult table or delete it from the ORDER BYclause.

sqlcode: -208

sqlstate: 42707

SQL0212N name is a duplicate tabledesignator or is specified morethan once in the REFERENCINGclause of a trigger definition.

Explanation: The exposed table, view, alias, orcorrelation name specified by name is identical toanother exposed table, view, alias, or correlationname in the same FROM clause.

If the statement is a CREATE TRIGGER, theREFERENCING clause may have specified thesame name as the subject table or may have thesame name for more than one of the OLD orNEW correlation names or the NEW_TABLE orOLD_TABLE identifiers.


User Response: Rewrite the FROM clause of theSELECT statement. Associate correlation nameswith table, view, or alias names so no exposedtable, view, alias, or correlation name is identicalto any other exposed table, view, alias, orcorrelation name in the FROM clause.

For a CREATE TRIGGER statement, change thenames in the REFERENCING clause so that thereare no duplicates.

sqlcode: -212

sqlstate: 42712

SQL0214N An expression in the ORDER BYclause in the following position,or starting withexpression-start-or-order-by-positionin the clause-type clause is notvalid. Reason code = reason-code.

Explanation: The expression identified by thefirst part of the expression expression-start-or-order-by-position in the clause-type clause is notvalid for the reason specified by the reason-codeas follows:

1 The fullselect of the select-statement isnot a subselect. Expressions are notallowed in the ORDER BY clause for


this type of select-statement. This reasoncode occurs only when clause-type isORDER BY.

2 DISTINCT is specified in the selectclause and the expression cannot bematched exactly with an expression inthe select list. This reason code occursonly when clause-type is ORDER BY.

3 Grouping is caused by the presence of acolumn function in the ORDER BYclause. This reason code occurs onlywhen clause-type is ORDER BY.

4 Expression in a GROUP BY clausecannot be a scalar-fullselect. This reasoncode occurs only when clause-type isGROUP BY.

5 The left side of a dereference operator ina GROUP BY clause cannot be a variantfunction. This reason code occurs onlywhen clause-type is GROUP BY.


User Response: Modify the select-statementbased on the reason specified by the reason-codeas follows:

1 Remove the expression from the ORDERBY clause. If attempting to reference acolumn of the result, change the sortkey to the simple-integer orsimple-column-name form.

2 Remove DISTINCT from the selectclause or change the sort key to thesimple-integer or simple-column-nameform.

3 Add a GROUP BY clause or remove thecolumn function from the ORDER BYclause.

4 Remove any scalar-fullselect from theGROUP BY clause. If grouping isdesired on a column of the result that isbased on a scalar-fullselect use a nestedtable expression or a common tableexpression to first provide a result tablewith the expression as a column of theresult.

5 Remove any variant function from theleft side of the dereference operators inthe GROUP BY clause.

sqlcode: -214

sqlstate: 42822

SQL0216N The number of elements on eachside of a predicate operator doesnot match. Predicate operator ispredicate-operator.

Explanation: A predicate includes a list ofelements on the right or left side (or both sides)of the predicate operator. The number ofelements must be the same on both sides. Theseelements may appear in a list of expressionsenclosed in parentheses or as elements of a selectlist in a fullselect.


User Response: Correct the predicate withmismatched number of elements on each side ofthe predicate operator.

sqlcode: -216

sqlstate: 428C4

SQL0217W The statement was not executed asonly Explain information requestsare being processed.

Explanation: The current value of one of theExplain special registers has been set toEXPLAIN. This value allows dynamic SQLstatements to be prepared and explained butprevents any dynamic statement from beingexecuted.

User Response: Change the value of theappropriate Explain special register to a settingother than EXPLAIN by issuing the appropriateSET statement from the interface or applicationthat is encountering this condition.

sqlcode: +217

sqlstate: 01604


SQL0219N The required Explain table namedoes not exist.

Explanation: The Explain facility has beeninvoked but was unable to find the requiredExplain table name. The Explain tables must becreated prior to invoking Explain.

User Response: Create the required Explaintables. The SQL Data Definition Languagestatements needed to create the Explain tablesare available in the file called EXPLAIN.DDL inthe misc directory under sqllib.

sqlcode: -219

sqlstate: 42704

SQL0220N The Explain table name, columnname2 does not have the properdefinition or is missing.

Explanation: The Explain facility has beeninvoked but the Explain table name did not havethe expected definition. The definition could beincorrect due to:

v Incorrect number of columns defined (if name2is numeric)

v Incorrect data type assigned to columns (ifname2 is a column name).

User Response: Correct the definitions of thespecified Explain table. The SQL Data DefinitionLanguage statements needed to create theExplain tables are available in the file calledEXPLAIN.DDL in the misc directory undersqllib.

sqlcode: -220

sqlstate: 55002

SQL0222N Operation was attempted againsta hole using cursor cursor-name.

Explanation: If the SQLSTATE is 24510, then anerror occurred. A positioned update or deletewas attempted with cursor cursor-name, which isdefined as SENSITIVE STATIC, and the currentrow has been identified as either a delete hole orupdate hole. A hole occurred when DB2 tried toupdate or delete a row in the database

corresponding to the current row of the resulttable for cursor cursor-name and thecorresponding row of the underlying table nolonger exists.

If the SQLSTATE is 02502, then this is a warning.A delete hole or update hole has been detectedwhile processing a fetch for cursor cursor-name. Ahole occurred when DB2 tried to refetch a rowfrom the database corresponding to the currentrow of the result table for cursor cursor-name andthe corresponding row of the underlying table nolonger exists. No data is returned.

A delete hole occurs when the correspondingrow of the underlying table has been deleted.

An update hole occurs when the correspondingrow of the underlying table has been updated inthe underlying table such that the updated rowno longer satisfies the search condition specifiedin the SELECT statement of the cursor.

The statement cannot be processed. The cursorremains positioned on the hole.

User Response: Issue a FETCH statement toposition the cursor on a row that is not a hole.

sqlcode: -222

sqlstate: 02502,24510

SQL0224N The result table does not agreewith the base table using cursorcursor-name.

Explanation: A positioned UPDATE or DELETEwas attempted using cursor cursor-name, definedas SENSITIVE STATIC, on a row where thecolumn values in the result table do not matchthe current values in the base table row. Therows do not match because the row of the basetable was updated between the time it wasfetched into the result table and the time thepositioned UPDATE or DELETE was processed.

The statement cannot be processed. The cursorposition is unchanged.

User Response: Change isolation levels so thatthe base table row cannot be updated againduring the cursor operation, or change theapplication to do a FETCH INSENSITIVE and try


the positioned UPDATE or DELETE again.

sqlcode: -224

sqlstate: 24512

SQL0225N FETCH statement for cursorcursor-name is not valid becausethe cursor is not defined asSCROLL.

Explanation: A FETCH statement fornon-scrollable cursor cursor-name been specifiedwith one of the following scrollable cursorkeywords: PRIOR, FIRST, LAST, BEFORE,AFTER, CURRENT, ABSOLUTE or RELATIVE.Only NEXT can be specified for non-scrollablecursors. No data is fetched.


User Response: Change the FETCH statementto remove the current fetch orientation keyword,such as PRIOR or FIRST, and replace it withNEXT. Alternatively, change the definition of thecursor to be scrollable.

sqlcode: -225

sqlstate: 42872

SQL0227N FETCH NEXT, PRIOR, CURRENTor RELATIVE is not allowedbecause cursor cursor-name has anunknown position (sqlcode,sqlstate).

Explanation: The cursor position for cursor-nameis unknown. A previous multiple row FETCH forcursor cursor-name resulted in an error(SQLCODE sqlcode, SQLSTATE sqlstate) in themiddle of processing multiple retrieved rows.One or more of the requested rows could not bereturned to the program following the error,leaving the position of the cursor unknown.

If an indicator structure had been provided onthe previous multiple row FETCH, a positiveSQLCODE would have been returned and all ofthe retrieved rows could have been returned tothe application program.


User Response: Close and reopen the cursor toreset the position. For scrollable cursors, you canchange the FETCH statement to specify one ofthe other fetch orientations, such as FIRST, LAST,BEFORE, AFTER or ABSOLUTE, to establish avalid cursor position and fetch a row of data.

sqlcode: -227

sqlstate: 24513

SQL0228N FOR UPDATE clause specified forread-only cursor cursor-name.

Explanation: Cursor cursor-name is defined asINSENSITIVE SCROLL, but the correspondingSELECT statement contains a FOR UPDATEclause.


User Response: To define a read-only cursor,specify INSENSITIVE on DECLARE CURSOR,but do not specify the FOR UPDATE clause aspart of the SELECT statement of the cursor.

sqlcode: -228

sqlstate: 42620

SQL0231W Current position of cursorcursor-name is not valid for FETCHof the current row.

Explanation: A FETCH CURRENT or FETCHRELATIVE 0 statement was issued for scrollablecursor cursor-name. The operation is not valid,because the cursor is not positioned on a row ofthe result table. A FETCH of the current row isnot allowed following a FETCH BEFORE orFETCH AFTER statement, or following a FETCHstatement that resulted in SQLCODE +100.


User Response: Ensure that the cursor ispositioned on a row of the result table beforeattempting to fetch the current row.

sqlcode: +231


sqlstate: 02000

SQL0236W SQLDA has only provided integer1SQLVAR entries. integer2 SQLVARentries are required for integer3columns. No SQLVAR entrieshave been set.

Explanation: The value of the SQLN field of theSQLDA should be at least as large as the numberof columns in the result set.

The database manager has not set any SQLVARentries (and the SQLDOUBLED flag has been setto ″off″ (i.e. to the space character)).

User Response: Increase the value of the SQLNfield in the SQLDA to the value indicated in themessage (making sure the SQLDA is largeenough to support that amount) and resubmitthe statement.

sqlcode: +236

sqlstate: 01005

SQL0237W SQLDA has only provided integer1SQLVAR entries. Since at leastone of the columns beingdescribed is a distinct type,integer2 SQLVAR entries shouldhave been specified. None of theSecondary SQLVAR entries havebeen set.

Explanation: Since at least one of the columnsin the result set is a distinct type, space shouldbe provided for twice as many SQLVAR entriesas the number of columns in the result set. Thedatabase manager has only set the Base SQLVARentries (and the SQLDOUBLED flag has been setoff (i.e. to the space character).

User Response: If there is no need for theadditional information about the distinct type(s)in the result set, then no action is required. If thedistinct type information is needed, the value ofthe SQLN field in the SQLDA should beincreased to the value indicated in the message(after making sure that the SQLDA is largeenough to support that amount) and thestatement should be resubmitted.

sqlcode: +237

sqlstate: 01594

SQL0238W SQLDA has only provided integer1SQLVAR entries. Since at leastone of the columns beingdescribed is a LOB or structuredtype, integer2 SQLVAR entries arerequired for integer3 columns. NoSQLVAR entries have been set.

Explanation: Since at least one of the columnsin the result set is a LOB or structured type,space must be provided for twice as manySQLVAR entries as the number of columns in theresult set. Note also that one or more of thecolumns in the result set may be a distinct type.

The database manager has not set any SQLVARentries (and the SQLDOUBLED flag has been setoff (i.e. to the space character).

User Response: Increase the value of the SQLNfield in the SQLDA to the value indicated in themessage (after making sure that the SQLDA islarge enough to support that amount) andresubmit the statement.

sqlcode: +238

sqlstate: 01005

SQL0239W SQLDA has only provided integer1SQLVAR entries. Since at leastone of the columns beingdescribed is a distinct type orreference type, integer2 SQLVARentries are required for integer3columns. No SQLVAR entrieshave been set.

Explanation: If any of the columns in the resultset is a distinct type or reference type, then spaceshould be provided for twice as many SQLVARentries as the number of columns in the resultset.

The database manager has not set any SQLVARentries (and the SQLDOUBLED flag has been setoff (i.e. to the space character).

User Response: If the distinct type or reference


type information is needed, the value of theSQLN field in the SQLDA should be increased tothe value indicated in the message (after makingsure the SQLDA is large enough to support thatamount) and the statement should beresubmitted. If there is no need for the additionalinformation about the distinct type(s) orreference type(s) in the result set, then it ispossible to resubmit the statement onlyproviding enough SQLVAR entries toaccommodate the number of columns in theresult set.

sqlcode: +239

sqlstate: 01005

SQL0242N The object named object-name oftype object-type was specified morethan once in the list of objects.

Explanation: In a list of object names of typeobject-type, the object named object-name wasspecified more than once. The operation of thestatement cannot be performed on the objectmore than once.

User Response: Correct the duplicated object inthe list removing duplicate occurrences.

sqlcode: -242

sqlstate: 42713

SQL0243N SENSITIVE cursor cursor-namecannot be defined for thespecified SELECT statement.

Explanation: Cursor cursor-name is defined asSENSITIVE, but the content of the SELECTstatement requires DB2 to build a temporaryresult table of the cursor, and DB2 cannotguarantee that changes made outside this cursorwill be visible. This situation occurs when thecontent of the query makes the result tableread-only. For example, if the query includes ajoin, the result table is read-only. In this case, thecursor must be defined as INSENSITIVE orASENSITIVE.


User Response: Either change the content of the

query to yield a result table that is not read-only,or change the type of the cursor to INSENSITIVEor ASENSITIVE.

sqlcode: -243

sqlstate: 36001

SQL0244N SENSITIVITY sensitivity specifiedon FETCH is not valid for cursorcursor-name.

Explanation: The sensitivity option sensitivityspecified on FETCH conflicts with the sensitivityoption in effect for cursor cursor-name. Thefollowing list shows what can be specified onFETCH:

DECLARE CURSORFETCH StatementINSENSITIVE INSENSITIVESENSITIVE STATIC SENSITIVE

or INSENSITIVESENSITIVE DYNAMIC SENSITIVESENSITIVE SENSITIVEASENSITIVE INSENSITIVE

or SENSITIVE(depending on theeffectivesensitivity of thecursor)

In the case of a non-scrollable cursor, asensitivity option cannot be specified.


User Response: Change or remove thesensitivity option specified on FETCH.

sqlcode: -244

sqlstate: 428F4

SQL0257N Raw DEVICE containers arecurrently not supported on thisplatform.

Explanation: An attempt was made to useDEVICE containers. These are not currentlysupported on this platform.

User Response: Use FILE containers or


system-managed table spaces instead.

sqlcode: -257

sqlstate: 42994

SQL0258N Containers cannot be added whilea rebalance of the table space ispending or in progress.


1. An ALTER TABLESPACE statement involvingcontainer operations has previously beenissued by this application or another and hasyet to be committed.

2. An ALTER TABLESPACE statement involvingcontainer operations has been issued andcommitted and the table space is currentlybeing rebalanced.

User Response:

1. If possible, roll back the uncommitted unit ofwork and issue a single ALTER TABLESPACEstatement to perform all of the containeroperations. Otherwise, wait until therebalance has completed and then try theoperation again. Note that pages cannot bothbe added to and removed from a table spacein the same ALTER TABLESPACE statement.

2. Wait until the rebalance has completed andthen try the operation again.

sqlcode: -258

sqlstate: 55041

SQL0259N Container map for table space istoo complicated.

Explanation: The map structure keeps a recordof how the table space address space is mappedto the various containers. If this gets toocomplicated, it does not fit in the table space file.

User Response: The table space may need to berebalanced to more evenly distribute the dataamong the containers. This may simplify themapping.

If this does not work, try making as many

containers as possible the same size. Existingcontainer sizes can be changed by backing up thetable space and then using the databaseadministration utility to change the containers.Restore the table space to the new containers.

sqlcode: -259

sqlstate: 54037

SQL0260N Column column-name cannotbelong to the partitioning keybecause it is either a LONGcolumn, DATALINK column, orstructured type column.

Explanation: A partitioning key cannot have aLONG-type column, DATALINK column, orstructured type column.


User Response: Do not use LONG columns,DATALINK columns, or structured type columnsfor the partitioning key.

If the table only has LONG columns, DATALINKcolumns, or structured type columns, either adda column that can be used for the partitioningkey to the table, or define the table without apartitioning key in a single-node nodegroup.

sqlcode: -260

sqlstate: 42962

SQL0262N Table table-name cannot be createdin the database partition groupgroup-name because no columnexists that can be used as thepartitioning key.

Explanation: The table table-name cannot becreated in a database partition group. The tablemust have at least one column that can be usedas the partitioning key. Columns of the followingdata types cannot be used in a partitioning key:

v LONG VARCHAR, LONG VARGRAPHIC,BLOB, CLOB, DBCLOB

v DATALINK

v Structured type


v A user-defined data type based on any of theabove data types


User Response: Either create the table with oneor more columns that can be used in apartitioning key, or create the table in a singledatabase partition group.

sqlcode: -262

sqlstate: 428A2

SQL0263N Node range from node-number-1 tonode-number-2 is not valid. Secondnode number must be greaterthan or equal to first nodenumber.

Explanation: The specified node range is notvalid.


User Response: Correct the node range in thestatement, then try the request again.

sqlcode: -263

sqlstate: 428A9

SQL0264N Partitioning key cannot be addedor dropped because table residesin a table space defined on themulti-node nodegroup name.

Explanation: You can only add or drop apartitioning key on a table in a single-nodenodegroup.


User Response: Do one of the following and trythe request again:

v Define an identical table with a partitioningkey.

v Redistribute the nodegroup to a single-nodenodegroup.

sqlcode: -264

sqlstate: 55037

SQL0265N Node node-number is a duplicatenode.

Explanation: For the CREATE NODEGROUPstatement, a node can only appear once in theON NODES clause.

For the CREATE TABLESPACE and ALTERTABLESPACE statement, a node can appear onlyonce and in only one ON NODES clause.

For the ALTER NODEGROUP statement orREDISTRIBUTE NODEGROUP command, one ofthe following occurred:

v The node appeared more than once in theADD NODES or the DROP NODES clause.

v The node appeared in both the ADD NODESand the DROP NODES clause.

v The node to be added is already a member ofthe nodegroup.


User Response: Ensure that the node names ornode numbers in the ON NODES, ADD NODES,or DROP NODES clause are unique. For theCREATE TABLESPACE and ALTERTABLESPACE statements, ensure that a nodeappears in no more than one ON NODES clause.

In addition, for the ALTER NODEGROUPstatement or REDISTRIBUTE NODEGROUPcommand:

v Do not specify a node in both the ADDNODES and the DROP NODES clause.

v Remove the node from the ADD NODESclause if the node is already defined in thenodegroup.

sqlcode: -265

sqlstate: 42728

SQL0266N Node node-number is not defined.

Explanation: The node node-number is not validfor one of the following reasons:

v the node number is not in the valid range of 0to 999

v the node is not in the node configuration file


v the node is not part of the nodegroup,therefore the requested operation cannot beprocessed.


User Response: Depending on the condition:

v issue the statement, command or API withnode numbers in the valid range.

v follow the procedure to add a node to thesystem.

v remove the node from the specified nodes inthe statement, command or API.

sqlcode: -266

sqlstate: 42729

SQL0268N operation cannot be performedwhile nodegroup is beingredistributed.

Explanation: One of the following:

v The nodegroup is being redistributed. Itcannot be altered, dropped or redistributedagain until the current operation is complete.

v The partitioning key of a table cannot bedropped while the nodegroup of the table isbeing redistributed.


User Response: Wait until the redistribution iscomplete, then try the request again.

sqlcode: -268

sqlstate: 55038

SQL0269N Database contains maximumnumber of partitioning maps.

Explanation: Because the database contains themaximum number of partitioning maps (32,768),you cannot create a new nodegroup, alter anodegroup, or redistribute an existing one.


User Response: Drop one or more nodegroupsin the database.

Note: Dropping a nodegroup drops all databaseobjects such as table spaces, tables and viewsthat reside in the nodegroup.

sqlcode: -269

sqlstate: 54033

SQL0270N Function not supported (Reasoncode = reason-code).

Explanation: The statement cannot be processedbecause it violates a restriction as indicated bythe following reason code:

1 The primary key, each uniqueconstraint, and each unique index mustcontain all partitioning columns of thetable (columns may appear in anyorder).

2 Update of the partitioning key columnvalue is not supported.

3 A foreign key cannot include anynullable partitioning key columns whendefined with ON DELETE SET NULL.This is a special case of reason code 2since defining such a constraint wouldresult in attempting to update apartitioning key column.

4 A table defined using a multipartitionnodegroup or a single-partitionnodegroup on other than the catalogpartition does not support DATACAPTURE CHANGES.

5 View created with the WITH CHECKOPTION clause should not usefunctions (or reference views that usefunctions ) that:

v are non-deterministic

v have side effects

v are related to the placement of data(for example nodenumber or partitionfunctions).

These functions must also not bepresent within referenced views if thenew view is created with theCASCADED check option.


6 A transform cannot be defined for auser-defined distinct type.

7 Long fields can only be defined using atable space with a page size that is 4K.A LARGE TABLESPACE can only becreated using a 4K page size.

8 Structured types are not supported ascolumns of a table or structured typeattribute data types prior to DB2 Version7.1.

9 Triggers are not supported on typedtables.

10 A single default table space cannot beselected since the table has one or moreLOB columns which must be placed in atable space with a 4K page size and therowsize or number of columns in thetable requires a table space with an 8Kpage size.

11 A typed table or typed view cannot becreated using a structured type that hasno attributes.

12 The type of a source key parametermust be a user-defined structured typeor a distinct type that is not sourced onLOB, DATALINK, LONG VARCHAR, orLONG VARGRAPHIC.

13 Check constraints cannot be defined ona typed table or the WITH CHECKOPTION clause cannot be specified on atyped view.

14 Referential constraints cannot be definedon a typed table or to a parent table thatis a typed table.

15 A default value cannot be defined forreference type columns.

16 A reference data type or structured datatype cannot be used as a parameter datatype or a returns data type of a userdefined function prior to DB2 Version7.1. Otherwise, a scoped reference datatype cannot be used as a parameter datatype or returns data type of a routine. A

structured type cannot be used as areturn column of a table or rowfunction.

17 The SET CONSTRAINTS statementcannot be used for a typed table.

18 Column level UPDATE andREFERENCES privileges cannot begranted on a typed table or typed view.

19 A specific default value must bespecified when defining a default for acolumn of a typed table.

20 ALTER TABLE is not supported for amaterialized query table.

21 Column length cannot be altered on atable which is a base table for amaterialized query table.

22 Materialized query tables cannot bedefined in a CREATE SCHEMAstatement.

23 REPLICATED can only be specified fora materialized query table defined withREFRESH DEFERRED.

24 The triggered-action in a BEFOREtrigger cannot reference a materializedquery table defined with REFRESHIMMEDIATE.

25 Only one materialized query table canbe specified for a SET CONSTRAINTSstatement.

26 The nodegroup being redistributedcontains at least one replicatedmaterialized query table.

27 Replicated materialized query tablescannot be defined on a table that doesnot have a unique index existing on oneor more columns that make up thereplicated materialized query table.

28 A typed table or materialized querytable cannot be renamed.

29 FOR EXCEPTION clause cannot bespecified with a materialized query tablein the SET CONSTRAINTS statement.


30 Typed tables and typed views cannot bedefined in a CREATE SCHEMAstatement.

31 A partitioning key cannot be definedwith more than 500 columns.

32 A table defined using a multipartitionnodegroup or a single-partitionnodegroup on other than the catalogpartition does not support DATALINKcolumns defined with FILE LINKCONTROL.

33 An underlying table of a materializedquery table defined with REFRESHIMMEDIATE cannot be the child of areferential constraint with cascadingeffect (i.e. with option ON DELETECASCADE or ON DELETE SET NULL).

34 The underlying object relational featureis not supported in the current release.

35 A sequence or an identity columncannot be created in a multi-nodedatabase environment.

36 Database activation of a multi-nodedatabase is not allowed if sequences oridentity columns exist.

38 An index using an index extension isnot supported in a multiple partitionnodegroup.

39 Nicknames or OLE DB table functionscannot be referenced directly orindirectly in the body of an SQLfunction or SQL method.

40 The function IDENTITY_VAL_LOCALcannot be used in a trigger or SQLfunction.

41 An SQL variable statement assigns toboth a local variable and a transitionvariable. This is not supported.

42 The execution of a trigger, method orfunction using SQL control statementsand the execution of a dynamiccompound statement in a multi-nodedatabase is not allowed.

43 One or more of the options you haverequested is currently not supported.

44 The following EXPLAIN MODES arenot supported in MPP, SMP, and DataJoiner:

v COUNT CARDINALITIES

v COMPARE CARDINALITIES

v ESTIMATE CARDINALITIES

45 APPEND mode is not supported formulti-dimensionally clustered (MDC)tables.

46 INPLACE table reorganization is notsupported for multi-dimensionallyclustered (MDC) tables.

47 Index extensions are not supported formulti-dimensionally clustered (MDC)tables.

48 Changes to the dimension specificationof a multi-dimensionally clustered(MDC) table are not supported.

49 Clustering Indexes are not supported formulti-dimensionally clustered (MDC)tables.

50 A user defined temporary table cannotbe a multi-dimensionally clustered(MDC) table.

51 CREATE PROCEDURE withLANGUAGE SQL from a non-catalogdatabase partition is not supported.

52 The expression of a generated columncannot be modified if that column wasused in the DIMENSIONS clause.

53 A column with a LONG VARCHAR,LONG VARGRAPHIC, DATALINK,LOB type, distinct type on any of thesetypes, or structured type cannot bespecified in the select-list of a scrollablecursor.

54 INPLACE table reorganization is notsupported for the specified SystemCatalog table.


55 Federated database system support andconcentrator feature cannot be active atthe same time.

56 Online index reorganization is notsupported for spatial indexes inALLOW WRITE mode.

57 Online index reorganization is notsupported on multi-dimensionallyclustered (MDC) tables in ALLOWWRITE mode.

58 The XML data type can only be used asa transient data type and cannot bestored in the database nor returned toan application.

59 A function or method that contains SQLstatements cannot be used in a parallelenvironment.

60 The ALTER TABLE ALTER COLUMNSET INLINE LENGTH statement is notallowed because there is an object oftype VIEW, either typed or untyped,that depends on the typed table.

61 Text search function cannot be used inthe expression for check constraints orgenerated columns.

62 The WITH CHECK OPTION clausecannot be used with views whichreference text search functions directlyor depend on other views referencingtext search functions.

63 A column with a LOB type, distinct typeon a LOB type, or structured typecannot be specified in the select-list ofan insensitive scrollable cursor.

64 Federated processing is not supportedon this platform.

65 Altering the nickname local type fromthe current type to the specified type isnot allowed.

User Response: The action corresponding to thereason code is:

1 Correct the CREATE TABLE, ALTERTABLE or CREATE UNIQUE INDEXstatement.

2 Do not attempt to update thepartitioning key columns for amultipartition table or consider deletingand then inserting the row with the newvalues in the partitioning columns.

3 Make the partitioning key column notnullable, specify a different ON DELETEaction, or change the partitioning key ofthe table so that the foreign does notinclude any columns of the partitioningkey.

4 Either specify DATA CAPTURE NONEor ensure that the table is placed in atable space on a single-partitionnodegroup that specifies the catalogpartition.

5 Do not use the WITH CHECK OPTIONclause or remove the function or viewfrom the view definition.

6 Transforms are automatic foruser-defined distinct types. Use theCREATE TRANSFORM statement foruser-defined structured types only.

7 Use a table space with 4K page size forany table that includes long fields. Ifusing DMS table spaces, long fields canbe placed in a table space with 4K pagesize with other table or index data intable spaces with a different page size.When defining a LARGE TABLESPACE,use PAGESIZE 4K.

8 For servers prior to DB2 Version 7.1,ensure that no column data types arestructured types in the CREATE TABLEstatement or ALTER TYPE ADDCOLUMN statement. Ensure that noattribute data types are structured typesin the CREATE TYPE statement orALTER TYPE ADD ATTRIBUTEstatement.

9 Do not define triggers on typed tables.

10 Either reduce the row size or number ofcolumns in the table or specify 2 tablespaces such that the long data is in a


table space with a 4K page size and thebase data is in a table space with an 8Kpage size.

11 When creating a typed table or typedview, specify a structured type that hasat least one attribute defined.

12 For the type of a source key parameter,use only a user-defined structured typeor a distinct type that is not sourced onLOB, DATALINK, LONG VARCHAR, orLONG VARGRAPHIC.

13 In a CREATE TABLE or ALTER TABLEstatement for a typed table, do notspecify check constraints. In a CREATEVIEW statement of a typed view, do notspecify the WITH CHECK OPTIONclause.

14 Do not specify referential constraintsinvolving typed tables in a CREATETABLE or ALTER TABLE statement.

15 Do not specify a DEFAULT clause for acolumn with a reference data type in aCREATE TABLE or ALTER TABLEstatement.

16 For servers prior to DB2 Version 7.1, donot specify a structured type parameteror returns type when creating a userdefined function. Otherwise, do notspecify a scoped reference type as aparameter or returns type. Do notspecify a structured type as a returncolumn of a table or row function.

17 Do not specify a typed table in the SETCONSTRAINTS statement.

18 Do not include specific column nameswhen granting REFERENCES orUPDATE privileges on a typed table ortyped view.

19 Include a specific value when specifyingthe DEFAULT clause on a column of atyped table.

20 Drop the materialized query table andrecreate it with the desired attributes.

21 Drop the materialized query table(s),

alter the column length of the base tableand then recreate the materialized querytable(s).

22 Issue the CREATE SUMMARY TABLEstatement outside of the CREATESCHEMA statement.

23 Either remove the REPLICATEDspecification or ensure that REFRESHDEFERRED is specified for thematerialized query table definition.

24 Remove the reference to thematerialized query table in thetriggered-action in the BEFORE trigger.

25 Issue separate SET CONSTRAINTSIMMEDIATE CHECKED statements foreach materialized query table.

26 Drop all replicated materialized querytables in the nodegroup and then issuethe REDISTRIBUTE NODEGROUPcommand again. Recreate the replicatedmaterialized query table(s).

27 Ensure that a subset of the columnsdefined for the materialized query tablealso are the set of columns that make upa unique index on the base table.

28 A typed table or materialized querytable name can only be changed bydropping the table and creating it againwith the new name. Dropping the tablemay have implications on other objectsthat depend on the table and theprivileges on the table are lost.

29 Remove the FOR EXCEPTION clausefrom the SET CONSTRAINTS statement.

30 Issue the CREATE statement for thetyped view or typed table outside of theCREATE SCHEMA statement.

31 Reduce the number of columns in thepartitioning key.

32 Either specify NO LINK CONTROL forthe DATALINK column or ensure thatthe table is placed in a table space on asingle-partition nodegroup that specifiesthe catalog partition. If redistributing to


a multiple-partition nodegroup, thetable needs to be dropped to continuewith the redistribute.

33

v Do not define a referential constraintwith cascading effect (i.e. with optionON DELETE CASCADE or ONDELETE SET NULL) with anunderlying table of a materializedquery table defined with REFRESHIMMEDIATE as the child, or

v do not define a REFRESHIMMEDIATE materialized query tablewhose underlying table is the child ofa referential constraint with cascadingeffect (i.e. with option ON DELETECASCADE or ON DELETE SETNULL).

34 The error can be corrected by removingthe use of any unsupported objectrelational features.

35 Remove the “GENERATED [ALWAYS |BY DEFAULT] AS IDENTITY ...”attribute from the column or do notattempt to create the sequence.

36 Drop the new node or nodes to go backto a single node configuration. If morenodes are required, then the sequencesor tables with identity columns must bedropped before new nodes are added.

38 An index using an index extensioncannot be created on a table in amultiple partition nodegroup. Anodegroup cannot become a multiplepartition nodegroup while an indexusing an index extension exists on atable in the nodegroup. Either drop anysuch indexes and add the partition tothe nodegroup, in which case theindexes cannot be re-created, or leavethe nodegroup unchanged.

39 Remove the reference to a nickname orOLE DB table function or remove thereference to the object that indirectlyreferences one of these.

40 Remove the invocation of the

IDENTITY_VAL_LOCAL function fromthe trigger definition or the SQLfunction definition.

41 Split the assignment into two separatestatements. One statement must onlyassign values to SQL variables, whilethe other statement must assign valuesonly to transition variables.

42 Drop the new node or nodes to returnto a single node configuration. If morenodes are required, then the triggers,functions or methods containing controlstatements must be dropped.

43 Please reissue the runstats commandand set the unsupported option off.

44 These EXPLAIN modes cannot be usedin SMP, MPP, and Data Joiner. Ifpossible, try to run the query in serialmode. Otherwise, setting the EXPLAINmode to YES or EXPLAIN will providethe same information except for theactual cardinalities.

45 Do not specify the APPEND clause inan ALTER TABLE statement formulti-dimensionally clustered (MDC)tables.

46 Reissue the REORG command withoutspecifying the INPLACE option.

47 Do not specify the EXTENSION clausein a CREATE INDEX statement formulti-dimensionally clustered (MDC)tables.

48 Drop the multi-dimensionally clustered(MDC) table and recreate it with themodified dimension specification.

49 Do not specify the CLUSTER clause in aCREATE INDEX statement formulti-dimensionally clustered (MDC)tables.

50 Do not specify the DIMENSION clausein a CREATE TABLE statement fordeclared global temporary tables.


51 Issue the CREATE PROCEDURE withLANGUAGE SQL from the catalogdatabase partition.

52 Do not modify the expression. Tochange the composition of theDIMENSIONS clause or the generatingexpression of any of its members thatare generated columns, the table mustbe dropped and created again, thenrepopulated.

53 Modify the select-list of the scrollablecursor to not include a column withthese types.

54 Reissue the REORG command withoutspecifying the INPLACE option.

55 Either turn off concentrator or federateddatabase system support. Turn offconcentrator by setting the databasemanager parameterMAX_CONNECTIONS to be less thanor equal to MAX_COORDAGENTS.Turn off federated database systemsupport by setting the FEDERATEDparameter in the database managerconfiguration to NO.

56 Reissue the REORG INDEXES commandand specify ALLOW NONE or ALLOWREAD.

57 Reissue the REORG INDEXES commandand specify ALLOW NONE or ALLOWREAD.

58 Input the XML data to one of thefunctions that accept XML input andstore the output of the function in thedatabase or return it to the application.

59 In a parallel environment, only usefunctions and methods defined with theNO SQL option.

60 Drop the views that depend on thetyped table. Reissue the ALTER TABLEALTER COLUMN SET INLINELENGTH statement on the typed tableand recreate the views that weredropped.

61 Do not use the text search function in

the expression for check constraints orgenerated columns. Use the LIKEfunction instead of CONTAINS, ifpossible.

62 Do no specify the WITH CHECKOPTION clause on this view.

63 Modify the select-list of the scrollablecursor to not include a column withthese types.

64 Do not attempt federated processing onthis platform.

65 Do not attempt to alter the nicknamelocal type from the current type to thespecified type.

sqlcode: -270

sqlstate: 42997

SQL0271N Index file for table with fid fid iseither missing, or is not valid.

Explanation: The index file for the table withfid fid is required during processing. The file iseither missing, or it is not valid.

The statement cannot be processed, and theapplication is still connected to the database. Thiscondition does not affect other statements that donot use the index on this table.

User Response: Ensure that all users aredisconnected from the database, then issue theRESTART DATABASE command on all nodes.Then try the request again.

The index (or indexes) is re-created when thedatabase is restarted.

sqlcode: -271

sqlstate: 58004

SQL0276N Connection to database namecannot be made because it is inthe restore pending state.

Explanation: The database must be restoredbefore a connection can be done.


No connection was made.

User Response: Restore the database, then issuethe CONNECT statement again.

sqlcode: -276

sqlstate: 08004

SQL0279N The database connection has beenterminated during COMMITprocessing. The transaction couldbe in doubt. Reason code =reason-code.

Explanation: Commit processing encounteredan error. The transaction has been put in thecommit state, but the commit processing may nothave completed. The application’s databaseconnection has been terminated.

The cause of the error is indicated by thereason-code:

1 A node involved in the transaction hasfailed.

2 Commit was rejected on one for thenodes. Check the administrationnotification log for details.

User Response: Determine the cause of theerror. It may be necessary to contact the systemadministrator for assistance since the mostcommon cause of the error is node failure orconnection failure. The RESTART DATABASEcommand will complete the commit processingfor this transaction.

sqlcode: -279

sqlstate: 08007

SQL0280W View, trigger or materializedquery table name has replaced anexisting inoperative view, triggeror materialized query table.

Explanation: An existing inoperative view,trigger or materialized query table name wasreplaced by:

v the new view definition as a result of aCREATE VIEW statement

v the new trigger definition as a result of aCREATE TRIGGER statement

v the new materialized query table definition asa result of a CREATE SUMMARY TABLEstatement.

User Response: None required.

sqlcode: +280

sqlstate: 01595

SQL0281N Table space tablespace-name cannotbe altered with additionalcontainers because it is a systemmanaged table space.

Explanation: Additional containers cannot beadded to a system managed table space. Theexception to this is when a nodegroup wasmodified to add a node without table spaces,then containers can be added once on the newnode using the ALTER TABLESPACE command.In general, the table space must be managed bythe database in order to add additionalcontainers.


User Response: To add more containers to asystem managed table space, drop and recreatethe table space with more containers, ensuringthat each container is of the same size and lessthan the container size limit, or change to a DMStable space.

sqlcode: -281

sqlstate: 42921

SQL0282N Table space tablespace-name cannotbe dropped because at least oneof the tables in it, table-name, hasone or more of its parts in anothertable space.

Explanation: A table in the specified table spacedoes not contain all of its parts in that tablespace. If more than one table spaces arespecified, then a table in one of the specifiedtable spaces does not contain all of its parts inthe list. The base table, indexes, or long data maybe in another table space, so dropping the table


space(s) will not completely drop the table. Thiswould leave the table in an inconsistent state andtherefore the table space(s) cannot be dropped.

User Response: Ensure that all objectscontained in table space tablespace-name containall their parts in this table space beforeattempting to drop it, or include those tablespaces containing the parts in the list to bedropped.

This may require dropping the table table-namebefore dropping the table space.

sqlcode: -282

sqlstate: 55024

SQL0283N System temporary table spacetablespace-name cannot be droppedbecause it is the only systemtemporary table space with apage-size page size in the database.

Explanation: A database must contain at leastone system temporary table space with the samepage size as the page size of the catalogtablespace. Dropping table space tablespace-namewould remove the last system temporarytablespace with a page-size page size from thedatabase.

User Response: Ensure there will be anothersystem temporary table space with a page-sizepage size in the database before attempting todrop this table space.

sqlcode: -283

sqlstate: 55026

SQL0284N The table was not created becausethe table space tablespace-namefollowing the clause clause is atablespace-type table space.

Explanation: The CREATE TABLE or DECLAREGLOBAL TEMPORARY TABLE statementspecified a table space named tablespace-namefollowing the clause clause that is not a validtype of table space for this clause.

This can occur in the following situations:

v for regular tables, tablespace-name was specifiedon the IN clause and the table space is not aREGULAR table space.

v for declared temporary tables, tablespace-namewas specified on the IN clause and the tablespace is not a USER TEMPORARY table space.

v tablespace-name was specified on the LONG INclause and the table space is not a LARGE,managed by database table space.

v tablespace-name was specified on the INDEX INclause and the table space is not a REGULARor LARGE, managed by database, table space.

User Response: Correct the CREATE TABLEstatement to specify a table space with thecorrect type for the clause clause.

sqlcode: -284

sqlstate: 42838

SQL0285N The indexes and/or long columnsfor table table-name cannot beassigned to separate table spacesbecause the primary table spacetablespace-name is a systemmanaged table space.

Explanation: If the primary table space is asystem managed table space, all table parts mustbe contained in that table space. A table can haveparts in separate table spaces only if the primarytable space, index table space and long tablespace are database managed table spaces.

User Response: Either specify a databasemanaged table space for the primary table space,or do not assign the table parts to another tablespace.

sqlcode: -285

sqlstate: 42839

SQL0286N A default table space could not befound with a pagesize of at leastpagesize that authorization IDuser-name is authorized to use.

Explanation: The CREATE TABLE or DECLAREGLOBAL TEMPORARY TABLE statement didnot specify a table space, and a table space of the


right type (USER TEMPORARY for declaredtemporary table) with sufficient page size (atleast pagesize), over which authorization IDuser-name has USE privilege, could not be found.

Sufficient page size for a table is determined byeither the byte count of the row or the number ofcolumns.

User Response: Ensure the existence of a tablespace of the correct type (REGULAR or USERTEMPORARY) with a page size of at leastpagesize and that authorization ID user-name hasUSE privilege on this table space.

sqlcode: -286

sqlstate: 42727

SQL0287N SYSCATSPACE cannot be usedfor user objects.

Explanation: The CREATE TABLE or GRANTUSE OF TABLESPACE statement specified atable space named SYSCATSPACE which isreserved for catalog tables.

User Response: Specify a different table spacename.

sqlcode: -287

sqlstate: 42838

SQL0288N A large table space cannot bedefined using MANAGED BYSYSTEM.

Explanation: The table space being defined isfor use with large objects and long strings. Thesecan only be stored in table spaces that aredefined in database managed space. Thus a largetable space cannot be defined to use systemmanaged space.

User Response: Remove the keyword LARGEor change to MANAGED BY DATABASE in theCREATE TABLESPACE statement.

sqlcode: -288

sqlstate: 42613

SQL0289N Unable to allocate new pages intable space tablespace-name.


1. One of the containers assigned to this SMStable space has reached the maximum filesize. This is the likely cause of the error.

2. All the containers assigned to this DMS tablespace are full. This is the likely cause of theerror.

3. The table space object table for this DMStable space is full.

4. A rebalance is in progress, but has notprogressed far enough to enable the newlyadded space to be used.

5. A redirected restore is being done tocontainers that are too small.

6. A rollforward is being done following aredirected restore and all the containersassigned to this tablespace are full.

7. A rollforward skipping add containers isbeing done and all the containers assigned tothis tablespace are full.

8. An attempt was made to create a table spacewith less than 5 usable extents.

User Response: Perform the actioncorresponding to the cause of the error:

1. either switch to a DMS TABLESPACE orrecreate the SMS TABLESPACE with moredirectories (PATHs) such that: (number ofdirectories) >= (max tablesize / maxfilesize).Note that maximum file size is operatingsystem dependent.

2. add new container(s) to the DMS table spaceand try the operation again, after therebalancer has made the new pages availablefor use.

3. drop unnecessary tables from this DMS tablespace.

4. wait for the rebalancer to make moreprogress.

5. perform the redirected restore again to largercontainers.

6. perform the redirected restore again to largercontainers.


7. perform the rollforward again allowing addcontainers, or perform a redirected restore tolarger containers.

8. resubmit the CREATE TABLESPACEstatement, ensuring that the table space has atleast 5 usable extents.

sqlcode: -289

sqlstate: 57011

SQL0290N Table space access is not allowed.

Explanation: A process attempted to access atable space which is in an invalid state for whichthe intended access is not allowed.

v If the table space is in a quiesced state, onlyprocesses which also hold the table space in aquiesced state are allowed access to the tablespace.

v If the table space is in any other state, only theprocess which is performing the actionspecified is allowed access to the table space.

v A system or user temporary table space cannotbe dropped which contains active system ordeclared temporary tables.

v The SET CONTAINER api cannot be used toset the container list unless the table space isin a ″restore pending″ state.

User Response: Possible actions include:

v If the table space is in a quiesced state,attempt to acquire a quiesced share orquiesced update state on the table space. Or,attempt to quiesce reset the table space.

v If the table space is in any other state, waituntil the table space has returned to normalstate before attempting to access the tablespace.

Refer to the Administration Guide for furtherinformation about the table space states.

sqlcode: -290

sqlstate: 55039

SQL0291N State transition not allowed ontable space.

Explanation: An attempt was made to changethe state of a table space. Either the new state isnot compatible with the current state of the tablespace, or an attempt was made to turn off aparticular state and the table space was not inthat state.

User Response: Table space states change whena backup is taken, the load completes, therollforward completes, etc., depending on thecurrent state of the table spaces. Refer to thesystems administration guide for furtherinformation about the table space states.

sqlcode: -291

sqlstate: 55039

SQL0292N An internal database file couldnot be created.

Explanation: An internal database file could notbe created.

User Response: Check that the directorycontaining the file is accessible (e.g. mounted)and writeable by the database instance owner.

sqlcode: -292

sqlstate: 57047

SQL0293N Error accessing a table spacecontainer.

Explanation: This error may be caused by oneof the following conditions:

v A container (directory, file or raw device) wasnot found.

v A container is not tagged as being owned bythe proper table space.

v A container tag is corrupt.

This error can be returned during databasestartup and during the processing of the ALTERTABLESPACE SQL statement.

User Response: Try the following actions:


1. Check that the directory, file, or device existsand that the file system is mounted (if it is ona separate file system). Containers must bereadable and writable by the databaseinstance owner.

2. If you have a recent backup, try restoring thetable space or database. If that fails becauseof the bad container and the container is nota DEVICE type, try manually removing thecontainer first.

If the error was returned from the processing ofan ALTER TABLESPACE SQL statement with theSWITCH ONLINE option, then re-issue thestatement after correcting the problem asdescribed above.

If the error persists, call your IBM servicerepresentative.

sqlcode: -293

sqlstate: 57048

SQL0294N The container is already in use.

Explanation: Table space containers may not beshared. The possible causes of this error includethe following.

v A CREATE TABLESPACE or ALTERTABLESPACE statement included a containerthat is already in use by another table space.

v A CREATE TABLESPACE or ALTERTABLESPACE statement included a containerfrom a table space that has been dropped butthe drop statement has not been committed.

v An ALTER NODEGROUP statement used toadd a node used the containers of a LIKEnode that is on the same physical node. Thesecontainers would therefore already be in use.

v A CREATE TABLESPACE or ALTERTABLESPACE statement is attempting to usethe same container on more than one logicalnode on a single physical node. The samecontainers cannot be used for more than onenode on the same physical node.

v An ADD NODE command or API used thecontainers from the system temporary table

spaces of a LIKE node that is on the samephysical node. These containers wouldtherefore already be in use.

v A CREATE TABLESPACE or ALTERTABLESPACE statement included a DMScontainer from another database that no longerexists but was not dropped properly. Thecontainer is not actually in use but it is taggedas being in use. Therefore, DB2 will not allowit to be used until it is untagged. However, itis very important to verify that the container isnot in use by the same database or anotherdatabase when untagging it. If the container isin use when you untag it, the database(s)involved will be corrupted.

User Response: Ensure the containers areunique.

v For the CREATE or ALTER TABLESPACEstatement, specify a different container for thetable space.

v For the CREATE or ALTER TABLESPACEstatement including a container from adropped table space, try again after the dropstatement is committed or specify a differentcontainer.

v For the ALTER NODEGROUP statement,reissue the statement using the WITHOUTTABLESPACES clause, and then use theALTER TABLESPACE statement to createunique containers for the new node.

v For CREATE or ALTER TABLESPACEstatements where the environment includesmore than one logical node on a physicalnode, ensure that the same containers are notspecified for such logical nodes.

v For an ADD NODE command or API, reissuethe statement using the WITHOUTTABLESPACES clause, and then use theALTER TABLESPACE statement to createunique containers at the new node for thesystem temporary table spaces.

v If you are trying to use a DMS container thatbelonged to a database that no longer existsbut was not dropped properly, then thedb2untag utility can be used to remove theDB2 container tag from it. When this tag isremoved DB2 considers the container to befree and the container can be used in a


CREATE TABLESPACE or ALTERTABLESPACE statement.

NOTE: Use extreme caution with db2untag. Ifyou issue a db2untag command against acontainer that is still in use by a database, thenboth the database that originally used thecontainer and the database that is now usingthe container will be corrupted.

sqlcode: -294

sqlstate: 42730

SQL0295N The combined length for allcontainer names for the tablespace is too long.

Explanation: The total space required to storethe list of containers exceeds the space allottedfor this table space in the table space file.

User Response: Try one or more of thefollowing:

v Use symbolic links, mounted file systems, etc.to shorten the new container names.

v Back up the table space and then use thedatabase administration utility to reduce thenumber and/or name lengths of thecontainers. Restore the table space to the newcontainers.

sqlcode: -295

sqlstate: 54034

SQL0296N Table space limit exceeded.

Explanation: This database contains themaximum number of table spaces. No more canbe created.

User Response: Delete table spaces that are notbeing used any more. Combine small tablespaces by moving all data into one of them anddeleting the other.

sqlcode: -296

sqlstate: 54035

SQL0297N Pathname for container is toolong.

Explanation: The full path specifying thecontainer name exceeds the maximum lengthallowed. If the container was specified as a pathrelative to the database directory, theconcatenation of these two values must notexceed the maximum length.

Details can be found in the administrationnotification log.

User Response: Shorten the path length.

sqlcode: -297

sqlstate: 54036

SQL0298N Bad container path.

Explanation: The container path violates one ofthe following requirements:

v Container paths must be valid fully-qualifiedabsolute paths or valid relative paths. Thelatter are interpreted relative to the databasedirectory.

v For EXTEND, REDUCE, RESIZE and DROPoperations, the specified container path mustexist.

v The path must be read/write accessible to theinstance id (check file permissions onUNIX-based systems).

v Containers must be of the type specified in thecommand (directory, file or device).

v Containers (directories) in system managedtable spaces must be empty when designatedas containers and must not be nestedunderneath other containers.

v The containers for one database must not belocated underneath the directory of anotherdatabase, and they may not be underneath anydirectory that appears to be for anotherdatabase. This rules out any directory of theform SQLnnnnn, where ’n’ is any digit.

v The container must be within the file size limitfor the operating system.

v Containers (files) for dropped databasemanaged table spaces can only be reused as


containers (directories) for system managedtable spaces after all agents terminate and viceversa.

v During a redirected restore, an SMS containerwas specified for a DMS table space or a DMScontainer was specified for an SMS tablespace.

v The specified type of the container for anEXTEND, REDUCE, RESIZE, or DROPoperation does not match the type of thecontainer (FILE or DEVICE) that was specifiedwhen the container was created.

This message will also be returned if any otherunexpected error occurred which prevents DB2from accessing the container.

User Response: Specify another containerlocation or change the container to make it

acceptable to DB2 (such as changing filepermissions) and try again.

sqlcode: -298

sqlstate: 428B2

SQL0299N Container is already assigned tothe table space.

Explanation: The container that you areattempting to add has already been assigned tothe table space.

User Response: Choose another container andtry again.

sqlcode: -299

sqlstate: 42731

SQL0300 - SQL0399

SQL0301N The value of input host variableor parameter number numbercannot be used because of its datatype.

Explanation: A host variable or parameter inposition number could not be used as specified inthe statement because its data type isincompatible with the intended use of its value.

This error can occur as a result of specifying anincorrect host variable or an incorrect SQLTYPEvalue in a SQLDA on an EXECUTE or OPENstatement. In the case of a user-definedstructured type, the associated built-in type ofthe host variable or SQLTYPE might not becompatible with the parameter of the TO SQLtransform function defined in the transformgroup for the statement. In the case ofperforming an implicit or explicit cast betweencharacter and graphic data types, this errorindicates that such a cast was attempted with anon-Unicode character or graphic string.


User Response: Verify that the data types of allhost variables in the statement are compatiblewith the manner in which they are used.

sqlcode: -301

sqlstate: 07006

SQL0302N The value of a host variable in theEXECUTE or OPEN statement istoo large for its correspondinguse.

Explanation: The value of an input hostvariable was found to be too large for its use inthe SELECT, VALUES, or prepared statement.One of the following occurred:

v The corresponding host variable or parametermarker used in the SQL statement is definedas string, but the input host variable contains astring that is too long.

v The corresponding host variable or parametermarker used in the SQL statement is definedas numeric, but the input host variablecontains a numeric value that is too large.

v The terminating NUL character is missingfrom the C language NUL-terminatedcharacter string host variable.

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


This error occurs as a result of specifying eitheran incorrect host variable or an incorrectSQLLEN value in an SQLDA on an EXECUTE orOPEN statement.


User Response: Ensure that the input hostvariable value is the correct type and length. Ifthe input host variables supply values toparameter markers, match values with theimplied data type and length of the parametermarker.

Federated system users: for a pass-throughsession, determine what data source is causingthe error (see the problem determination guidefor procedures to follow to identify the failingdata source). Examine the SQL dialect for thatdata source to determine which specificrestriction has been violated, and adjust thefailing statement as needed.

sqlcode: -302

sqlstate: 22001, 22003

SQL0303N A value cannot be assigned to ahost variable in the SELECT,VALUES, or FETCH statementbecause the data types are notcompatible.

Explanation: An imbedded SELECT or VALUESstatement selects into a host variable, but thedata type of the variable is not compatible withthe data type of the corresponding SELECT-listor VALUES-list element. Both must be numeric,character, or graphic. For a user-defined datatype, the host variable might be defined with anassociated built-in data type that is notcompatible with the result type of the FROMSQL transform function defined in the transformgroup for the statement. For example, if the datatype of the column is date or time, the data typeof the variable must be character with anappropriate minimum length.


User Response: Verify that the table definitionsare current and that the host variable has thecorrect data type. For a user-defined data type,

verify that the associated built-in type of the hostvariable is compatible with the result type of theFROM SQL transform function defined in thetransform group for the statement.

sqlcode: -303

sqlstate: 42806

SQL0304N A value cannot be assigned to ahost variable because the value isnot within the range of the hostvariable’s data type.

Explanation: A FETCH, VALUES, or SELECTinto a host variable list failed because the hostvariable was not large enough to hold theretrieved value.

The statement cannot be processed. No data wasretrieved.

User Response: Verify that table definitions arecurrent and that the host variable has the correctdata type. For the ranges of SQL data types, referto the SQL Reference.

Federated system users: for the ranges of datatypes that are returned from a data source, referto the documentation for that data source.

sqlcode: -304

sqlstate: 22001, 22003

SQL0305N The NULL value cannot beassigned to a host variable in theSELECT or FETCH statementbecause no indicator variable isspecified.

Explanation: A FETCH or embedded SELECTor VALUES operation resulted in the retrieval ofa NULL value to be inserted into a host variablefor which no indicator variable was provided. Anindicator variable must be supplied if a columncan return a NULL value.

The statement cannot be processed. No data wasretrieved.

User Response: Examine the definition of theFETCH or SELECT object table or the elementsof the VALUES list. Correct the program to


provide indicator variables for all host variableswhere NULL values from those columns can beretrieved.

sqlcode: -305

sqlstate: 22002

SQL0306N The host variable name isundefined.

Explanation: The host variable name is notdeclared in any DECLARE SECTION.


User Response: Ensure that the host variable isdeclared and the name spelled correctly.

SQL0307N The host variable name is alreadydefined.

Explanation: The host variable name has alreadybeen declared in a DECLARE SECTION.

The definition is ignored. The previous definitionis used.

User Response: Ensure that the host variablename is spelled correctly and the name isdefined only once for each program.

SQL0308N The limit on the number of hostvariables has been reached.

Explanation: The limit on the number of hostvariables is dependent on how many will fit inthe HOST_VARS column of SYSPLAN. This limithas been reached.

The remaining variable declarations are ignored.

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

SQL0309N The value of a host variable in theOPEN statement is NULL, but itscorresponding use cannot beNULL.

Explanation: The value of an input hostvariable was found to be NULL but the

corresponding use in the SELECT, VALUES, orprepared statement did not specify an indicatorvariable.


User Response: Ensure you need a USINGclause. Otherwise, ensure an indicator variable isspecified only if required.

sqlcode: -309

sqlstate: 07002

SQL0310N SQL statement contains too manyhost variables.

Explanation: The maximum number of hostvariables was exceeded in the statement.


User Response: Ensure the statement has fewerhost variables or is less complex.

SQL0311N The length of string host variablenumber var-number is negative orgreater than the maximum.

Explanation: When evaluated, the lengthspecification for the string host variable, whoseentry in the SQLDA is indicated by<var-number> (based at 1), was negative orgreater than the maximum defined for that hostvariable.


User Response: Correct the program to ensurethat the lengths of all string host variables arenot negative or that they are not greater than themaximum allowed length.

sqlcode: -311

sqlstate: 22501

SQL0312N The host variable host-name isused in a dynamic SQL statement,a view definition, or a triggerdefinition.

Explanation: The host variable host-nameappears in the SQL statement, but host variables


are not allowed in dynamic SQL statements, inthe SELECT statement of a view definition, or inthe triggered action of a trigger definition.


User Response: Use parameter markers (?)instead of host variables for dynamic SQLstatements. Do not use host variables andparameter markers in view or trigger definitions.

sqlcode: -312

sqlstate: 42618

SQL0313N The number of host variables inthe EXECUTE or OPEN statementis not equal to the number ofvalues required.

Explanation: The number of host variablesspecified in the EXECUTE or OPEN statementdoes not equal the number of host variablesrequired for the parameter markers (?) appearingin the SQL statement.

User Response: Correct the application programso the number of host variables specified in theEXECUTE or OPEN statement is correct for theparameter markers in the SQL statement.

sqlcode: -313

sqlstate: 07001, 07004

SQL0314N The host variable name isincorrectly declared.

Explanation: The host variable name is notdeclared correctly for one of the followingreasons:

v The type specified is not one that is supported.

v The length specification is 0, negative, or toolarge.

v An initializer is used.

v An incorrect syntax is specified.

The variable remains undefined.

User Response: Ensure that you correctlyspecify only the declarations the databasemanager supports.

SQL0315N The host variable is incorrectlydeclared.

Explanation: The host variable is not declaredcorrectly for one of the following reasons:

v The type specified is not one that is supported.

v The length specification is 0, negative or toolarge.

v An incorrect syntax is specified.

The variable remains undefined.

User Response: Ensure that you correctlyspecify only the declarations the databasemanager supports.

SQL0317N No END DECLARE SECTIONwas found after a BEGINDECLARE SECTION.

Explanation: The end of input was reachedduring processing of a DECLARE SECTION.


User Response: Add an END DECLARESECTION statement to end a DECLARESECTION.

SQL0318N An END DECLARE SECTIONwas found without a previousBEGIN DECLARE SECTION.

Explanation: An END DECLARE SECTIONstatement was found, but there was no previousBEGIN DECLARE SECTION.


User Response: Enter a BEGIN DECLARESECTION before an END DECLARE SECTION.

SQL0324N The usage variable name is thewrong type.

Explanation: Either the INDICATOR variablename is not a small integer or the STATEMENTvariable name is not a character data type.


User Response: Ensure that the variable is the


correct type and is specified correctly.

SQL0332N There is no available conversionfor the source code page code-pageto the target code page code-page.Reason code reason-code.

Explanation: No conversion of data issupported from the source code page to thetarget code page. This error can occur under thefollowing conditions:

v An error has occurred executing an SQLstatement. The data cannot be processed bythe database manager.

v An error has occurred when trying to importor export a WSF or an IXF file. The import orexport will fail.

v Federated system users: the data source doesnot support the specified code pageconversion.

v DB2 Connect users: both ″source code page″and ″target code page″ may refer to a CCSIDon the host or AS/400 system.

v An error has occurred during conversion fromthe code page stored with the encrypted datato the target code page.

The reason codes are as follows:

1 source and target code pagecombination is not supported by thedatabase manager.

2 source and target code pagecombination is either not supported bythe database manager or by theoperating system character conversionutility on the client node.

3 source and target code pagecombination is either not supported bythe database manager or by theoperating system character conversionutility on the server node.


v Verify that data conversion between the sourceand target code page is supported by thedatabase manager. For database manager codepage support, check the Quick Beginnings. If

DB2 Connect is being used, check the DB2Connect Quick Beginnings.

v Data conversion for some code pagecombinations may be supported throughdatabase manager install options, dependingon the language group of the source or targetcode page. Ensure that the appropriate onesare installed and accessible to the databasemanager and the client application, asindicated by the reason code returned. For alist of install options, consult the QuickBeginnings or the DB2 Connect QuickBeginnings.

v Data conversion for some code pagecombinations may be supported by thedatabase manager through an operatingsystem-provided character conversion utility,depending on the language group of thesource or target code page. Check youroperating system documentation for a list ofsupported conversions and ensure that theappropriate ones are installed and accessible tothe database manager and the clientapplication, as indicated by the reason codereturned. For a list of operating systemconversion utilities used, consult the QuickBeginnings or the DB2 Connect QuickBeginnings.

v Change the unsupported code page(s) to oneof the documented pairs.

AS/400 users should be aware that AS/400CCSID 65535 is not supported. AS/400 dataencoded using CCSID 65535 must be convertedto a supported CCSID before it can be accessedusing DB2 Connect.

Federated system users: for data source codepage support, see the Federated Systems Guide.

sqlcode: -332

sqlstate: 57017


SQL0334N Overflow occurred whileperforming conversion fromcodepage source to codepage target.The maximum size of the targetarea was max-len. The sourcestring length was source-len and itshexadecimal representation wasstring.

Explanation: During the execution of the SQLstatement, a code page conversion operation hasresulted in a string that is longer than themaximum size of the target object.

User Response: Modify the data to avoid theoverflow condition, depending on thecircumstances, by:

v decreasing the length of the source string orincreasing the size of the target object (pleaserefer to the note below),

v altering the operation,

v casting the encrypted data value to aVARCHAR string with a larger number ofbytes before using it in a decryption function,or

v ensuring that the application codepage and thedatabase codepage are the same. Thiseliminates the need for codepage conversionsfor most connections.

Note: Automatic promotion of character orgraphic string data types will not occur aspart of character conversion. If theresultant string length exceeds themaximum length of the data type of thesource string then an overflow hasoccurred. To correct this situation eitherchange the data type of the source stringor use data type casting to allow for anincrease in the string length due toconversion.

sqlcode: -334

sqlstate: 22524

SQL0336N The scale of the decimal numbermust be zero.

Explanation: The decimal number is used in acontext where the scale must be zero. This canoccur when a decimal number is specified in aCREATE or ALTER SEQUENCE statement forSTART WITH, INCREMENT, MINVALUE,MAXVALUE or RESTART WITH.


User Response: Change the decimal number toremove any non-zero digits from the right side ofthe decimal delimiter.

sqlcode: -336

sqlstate: 428FA

SQL0338N An ON clause associated with aJOIN operator is not valid.

Explanation: An ON clause associated with aJOIN operator is not valid for one of thefollowing reasons.

v The join condition cannot include anysubqueries.

v Column references in an ON clause must onlyreference columns of tables that are in thescope of the ON clause (included in the samejoined-table clause as the ON clause).

v Scalar fullselects are not allowed in theexpressions of an ON clause.

v A function referenced in an ON clause of a fullouter join must be deterministic and have noexternal action.

v A dereference operation (->) cannot be used.

v A SQL function or SQL method cannot beused.


User Response: Correct the ON clause toreference appropriate columns or delete anysubqueries or scalar fullselects. Remove anydereference operations, SQL functions, or SQLmethods from the ON clause.

If using full outer join ensure that all functions in


the ON clause are deterministic and have noexternal action.

sqlcode: -338

sqlstate: 42972

SQL0340N The common table expressionname has the same identifier asanother occurrence of a commontable expression definition withinthe same statement.

Explanation: The common table expressionname name is used in the definition of more thanone common table expressions in the statement.The name used to describe a common tableexpression must be unique within the samestatement.


User Response: Change the name of one of thecommon table expressions.

sqlcode: -340

sqlstate: 42726

SQL0341N A cyclic reference exists betweenthe common table expressionsname1 and name2.

Explanation: The common table expressionname1 refers to name2 in a FROM clause withinits fullselect and name2 refers to name1 in aFROM clause within its fullselects. Such forms ofcyclic references are not allowed.


User Response: Remove the cyclic referencefrom one of the common table expressions.

sqlcode: -341

sqlstate: 42835

SQL0342N The common table expressionname cannot use SELECTDISTINCT and must use UNIONALL because it is recursive.

Explanation: There are two possibleexplanations:

v A fullselect within the common tableexpression name cannot start with SELECTDISTINCT because the common tableexpression is recursive.

v A fullselect within the common tableexpression name specified UNION instead ofUNION ALL as required for recursivecommon table expressions.


User Response: Remove the keywordDISTINCT from the common table expression,add the keyword ALL following UNION, orremove the recursive reference within thecommon table expression.

sqlcode: -342

sqlstate: 42925

SQL0343N The column names are requiredfor the recursive common tableexpression name.

Explanation: The recursive common tableexpression name must include the specification ofthe column names following the identifier of thecommon table expression.


User Response: Add column names followingthe identifier of the common table expression.

sqlcode: -343

sqlstate: 42908

SQL0344N The recursive common tableexpression name has mismatcheddata types, lengths or code pagesfor column column-name.

Explanation: The recursive common tableexpression name has a column column-name that


is referred to in the iterative fullselect of thecommon table expression. The data type, lengthand code page are set based on the initializationfullselect for this column. The result of theexpression for the column column-name in theiterative fullselect has a different data type,length or code page that may result in failure toassign the value for the column.


User Response: Correct the column used in thefullselects of the recursive common tableexpression so that the initialization columnmatches the iterative columns.

sqlcode: -344

sqlstate: 42825

SQL0345N The fullselect of the recursivecommon table expression namemust be the UNION of two ormore fullselects and cannotinclude column functions,GROUP BY clause, HAVINGclause, ORDER BY clause, or anexplicit join including an ONclause.

Explanation: The common table expressionname includes a reference to itself and therefore:

v must be the union of two or more fullselects

v cannot include a GROUP BY clause

v cannot have column functions

v cannot include a HAVING clause

v cannot include an ORDER BY clause on theiterative fullselect

v and cannot include an explicit join with an ONclause.


User Response: Change the common tableexpression by:

v making it a union of two or more fullselects

v removing any column functions, GROUP BYclause, HAVING clause, ORDER BY clause, orexplicit JOIN including an ON clause.

v removing the recursive reference.

sqlcode: -345

sqlstate: 42836

SQL0346N An invalid reference to commontable expression name occurs inthe first fullselect, as a secondoccurrence in the same FROMclause, or in the FROM clause ofa subquery.

Explanation: The common table expressionname includes an invalid reference to itself asdescribed by one of the following.

v A recursive reference in the first fullselectbefore the UNION ALL set operator. The firstfullselect must be an initialization and cannotinclude a recursive reference.

v More than one reference to the same commontable expression in the same FROM clause.Such references are not permitted in recursivecommon table expression.

v A recursive reference in the FROM clause of asubquery. A recursion cycle cannot be definedusing a subquery.


User Response: Change one of the following:

v the fullselect prior to the union operator sothat it does not include a recursive reference

v the FROM clause containing more than onereference to the same common table expressionto just one reference

v the FROM clause of the subquery so that itdoes not reference the common tableexpression.

sqlcode: -346

sqlstate: 42836

SQL0347W The recursive common tableexpression name may contain aninfinite loop.

Explanation: The recursive common tableexpression called name may not complete. This


warning is based on not finding specific syntaxas part of the iterative portion of the recursivecommon table expression. The expected syntaxincludes:

v incrementing an INTEGER column in theiterative select list by 1.

v a predicate in the where clause of the iterativeportion of the form ″counter_col < constant″ or″counter_col < :hostvar″.

The absence of this syntax in the recursivecommon table expression may result in aninfinite loop. The data or some othercharacteristic of the recursive common tableexpression may allow the successful completionof the statement anyway.

User Response: To prevent an infinite loop,include the expected syntax as described.

sqlcode: +347

sqlstate: 01605

SQL0348N sequence-expression cannot bespecified in this context.

Explanation: The statement contains aNEXTVAL expression or PREVVAL expression inan invalid context. NEXTVAL expressions andPREVVAL expressions cannot be specified in thefollowing contexts:

v join condition of a full outer join

v DEFAULT value for a column in a CREATETABLE or ALTER TABLE statement

v generated column definition in a CREATETABLE or ALTER TABLE statement

v condition of a CHECK constraint

v CREATE TRIGGER statement (a NEXTVALexpression may be specified, but a PREVVALexpression cannot be specified)

v CREATE VIEW statement, CREATE METHODstatement or CREATE FUNCTION statement

NEXTVAL expressions cannot be specified in thefollowing contexts:

v CASE expression

v parameter list of an aggregate function

v subquery except in the fullselect of an INSERT,UPDATE or VALUES INTO statement

v SELECT statement for which the outerSELECT contains a DISTINCT operator

v SELECT statement for which the outerSELECT contains a GROUP BY clause

v join condition of a join

v SELECT statement for which the outerSELECT is combined with another SELECTstatement using the UNION, INTERSECT orEXCEPT set operator

v nested table expression

v parameter list of a table function

v WHERE clause of the outer-most SELECTstatement, DELETE or UPDATE statement

v ORDER BY clause of the outer-most SELECTstatement

v select-cause of the fullselect of an expression,in the SET clause of an UPDATE statement

v IF, WHILE, DO...UNTIL, or CASE statement inan SQL routine


User Response: Remove the reference to thesequence expression and resubmit the statement.

sqlcode: -348

sqlstate: 428F9

SQL0349N The specification of theNEXTVAL expression for thecolumn in position column-positionmust match the specification of allother expressions for the samecolumn for all rows.

Explanation: The expression specified for thecolumn in position column-position of a VALUESclause of a multiple row INSERT statement orVALUES expression included a NEXTVALexpression. When an expression containing aNEXTVAL expression is used to specify the valueof a column in one of these contexts, then thatsame expression must be specified for thatcolumn for all rows. For example, the followingINSERT statement succeeds:


INSERT INTO T1VALUES(

NEXTVAL FOR sequence1 + 5, ’a’),(NEXTVAL FOR sequence1 + 5, ’b’),(NEXTVAL FOR sequence1 + 5, ’c’)

However, the following INSERT statement fails:

INSERT INTO T1VALUES(

NEXTVAL FOR sequence1 + 5, ’a’),(NEXTVAL FOR sequence1 + 5, ’b’),(NEXTVAL FOR sequence1 + 4, ’c’)

User Response: Correct the syntax and resubmitthe statement.

sqlcode: -349

sqlstate: 560B7

SQL0350N LOB, DATALINK, or structuredtype column column-name cannotbe used in an index, a key, aunique constraint, a generatedcolumn, or a declared temporarytable.

Explanation: Even in cases where it would notviolate the maximum size of an index, key, orunique constraint, a LOB column, DATALINKcolumn, or structured type column cannot beused in an index, key or unique constraint. Thesedata types are also not supported as columntypes of a generated column or a declaredtemporary table. This restriction includes the useof distinct type column based on a LOB orDATALINK.


User Response: Remove the LOB, DATALINKor structured type column from the specificationof the index, key, unique constraint, generatedcolumn, or declared temporary table. An index

defined on a structured type column may bedefined using an index extension.

sqlcode: -350

sqlstate: 42962

SQL0351N An unsupported SQLTYPE wasencountered in positionposition-number of the outputSQLDA (select list).

Explanation: The element of the SQLDA atposition position-number is for a data type thateither the application requestor or the applicationserver does not support. If the application is notusing the SQLDA directly, position-number couldrepresent the position of an element in the selectlist or a parameter of a CALL statement.


User Response: Change the statement toexclude the unsupported data type. For a selectstatement, remove the names of any columns inthe select-list with the unsupported data type oruse a cast in the query to cast the column to asupported data type.

sqlcode: -351

sqlstate: 56084

SQL0352N An unsupported SQLTYPE wasencountered in positionposition-number of the input list(SQLDA).

Explanation: The element of the SQLDA atposition position-number is for a data type thateither the application requestor or the applicationserver does not support. If the application is notusing the SQLDA directly, position-number couldrepresent the position of an input host variable,parameter marker, or a parameter of a CALLstatement.


User Response: Change the statement toexclude the unsupported data type.

sqlcode: -352

sqlstate: 56084


SQL0355N The column column-name, asdefined, is too large to be logged.

Explanation: Large Object data types (BLOB,CLOB, and DBCLOB) may be created in sizes upto 2 gigabytes (2147483647 bytes). Logging ofdata values is allowed only upon objects whichare less than or equal to than 1 gigabyte(1073741823 bytes) in size. Therefore, largeobjects greater than 1 gigabyte in size can not belogged.

User Response: Either explicitly indicatelogging of data is not required, by using theNOT LOGGED phrase during column creation,or reduce the maximum size of the column to 1gigabyte or below.

sqlcode: -355

sqlstate: 42993

SQL0357N The DB2 Data Links Managername is not currently available.Reason code = reason-code.

Explanation:

The statement requires processing on the DB2Data Links Manager name. The DB2 Data LinksManager is not currently available as indicatedby the reason code.

01 The DB2 Data Links Manager is notavailable.

02 The database server, instance, ordatabase from which the operation wasattempted is not registered with theappropriate DB2 Data Links Manager.

03 Either access to the DB2 Data LinksManager is currently disallowed, or DB2is unable to connect to the DB2 DataLinks Manager.

04 The DB2 Data Links Manager is anunknown server.

05 An error occurred while communicatingwith the DB2 Data Links Manager.

06 The installation type of the DB2 DataLinks Manager is not compatible withthat registered to the database.


User Response: The action depends on thereason code as follows.

01 The DB2 Data Links Manager or acommunication link may be down. Waita while and try again, or check with theDB2 Data Links Manager administrator.If the problem persists, disconnect theapplication from the database, and retryafter connecting again.

02 Register the database server, instance, ordatabase with the DB2 Data LinksManager.

03 Access to the DB2 Data Links Manageris disallowed until DB2 can ensure thatit is in a consistent state. Wait until DB2does this asynchronously. It is possiblethat DB2 is unable to do this because ofconditions in other reason codes. So, ifthe problem persists, check thedb2diag.log file of the instance to findout the condition and correct thatcondition. For more information, refer tothe Administration Guide forinformation on crash recovery for DB2Data Links Managers. Also check all thehost settings for connections to this DB2Data Links Manager.

04 Ensure that the DB2 Data LinksManager is available on the network.

05 Check that the DB2 Data Links Managerand the communication link are up. Ifthe problem persists, disconnect theapplication from the database, and retryafter connecting again.

06 If the DB2 Data Links Manager wasinstalled for DFS, then it must added asa CELL to the database. If it wasinstalled for native file systems, then itmust be added as a NODE. Refer to theCommand Reference for details on ADDDATALINKS MANAGER command.

sqlcode: -357

sqlstate: 57050


SQL0358N Unable to access file referencedby a DATALINK value. Reasoncode = reason-code.

Explanation: A DATALINK value could not beassigned. The possible reason codes are asfollows:

21 DATALINK value data location formatis not valid.

22 DATALINK value DB2 Data Linksmanager is not registered with thedatabase.

23 DATALINK linktype value is not valid.

24 DATALINK value referenced file cannotbe found by a DB2 Data Links Manager.

25 DATALINK value referenced file isalready linked to a database.

26 DATALINK value referenced file cannotbe accessed for linking. It may be adirectory, a symbolic link or a file withpermission bit for set user ID (SUID) onor set group ID (SGID) on, or a filelocated in a file system not defined as aDLFS (Data Links File System).

27 DATALINK value data location orcomment is too long.

28 Existing registry on the DB2 Data LinksManager does not allow this file to belinked (No matching prefix on DLFM).

29 The DB2 Data Links Manager does notauthorize the DB2 user to link this file.

30 A link is already in progress for the fileby another application.

31 File copy by the DB2 Data LinksManager is not complete for the file tobe unlinked. The statement cannot beprocessed.

32 DATALINK value does not contain avalid write token.

33 DATALINK value constructed by theDLPREVIOUSCOPY scalar function canbe assigned only to a DATALINK

column defined with WRITEPERMISSION ADMIN and RECOVERYYES.

34 DATALINK value constructed by theDLNEWCOPY or DLPREVIOUSCOPYscalar function does not match the valueas already exists in the column.

35 DATALINK value constructed by theDLNEWCOPY or DLPREVIOUSCOPYscalar function cannot be used in anINSERT statement to assign a newvalue.

36 The write token embedded inDATALINK value data location does notmatch the token used to open theDATALINK value referenced file.

37 DATALINK value reference file is in theupdate-in-progress state.

38 DATALINK value with scheme DFScannot be assigned to a DATALINKcolumn defined with WRITEPERMISSION ADMIN.

39 DATALINK value constructed by theDLNEWCOPY scalar function cannot beassigned to a DATALINK columndefined with WRITE PERMISSIONBLOCKED.

40 The previous archive copy ofDATALINK reference file cannot belocated from the archive server.

41 The same DATALINK value constructedby the DLNEWCOPY orDLPREVIOUSCOPY scalar functioncannot be assigned multiple timeswithin the same transaction or the samedatalink value cannot be unlinked whilethe assignment of the same datalinkvalue constructed by DLNEWCOPY orDLPREVIOUSCOPY is not yetcommitted.

42 DATALINK value constructed by theDLREPLACECONTENT scalar functioncan be assigned to a DATALINK columndefined with NO LINK CONTROL only


if the second argument (replacement filelocation) is a zero-length string or anull.

43 The unlink operation of the replacementfile specified in theDLREPLACECONTENT scalar functionhas not committed.

44 The replacement file specified in theDLREPLACECONTENT scalar functionis already used in another replacementprocess.

45 DATALINK referenced file is alreadyspecified as the replacement file inanother operation.

46 The format of the replacement filespecified in the DLREPLACECONTENTscalar function is not valid.

47 The format of the replacement filespecified in the DLREPLACECONTENTscalar function cannot be a directory ora symbolic link.

48 The replacement file specified in theDLREPLACECONTENT scalar functionis already linked to a database.

49 The replacement file specified in theDLREPLACECONTENT scalar functioncannot be found by a Data Links FileManager.

50 DATALINK values that have a writetoken in the data location, asconstructed by the DLNEWCOPY scalarfunction, can only be assigned toDATALINK columns defined withWRITE PERMISSION ADMIN.

User Response: The action is based on thereason code as follows.

21 Correct the data location format.

22 Ensure that the correct DB2 Data LinksManager is specified and if so have itregistered to the database. RegisteredDB2 Data Links Managers are ignoredunless the database managerconfiguration parameter Datalinks is setto YES.

23 Correct the linktype value.

24 Check that the correct file is specifiedand that the file exists.

25 Either unlink the existing reference tothe file or do not specify the file in thisstatement.

26 Linking of directories is not allowed.Use the actual file name, not a symboliclink. If SUID or SGID is on, or if the fileis located in a non-DLFS file system,this file cannot be linked using aDATALINK type.

27 Reduce the length of the data locationvalue or the comment.

28 Contact the DB2 Data Links Mangeradministrator to add the registrationnecessary to link this file.

29 Contact the DB2 Data Links Manageradministrator to get the necessaryauthorization.

30 Do not link this file or retry later.

31 Allow some time for the file copy tocomplete and retry later.

32 Provide the data location value with avalid write token. A write token isgenerated as part of the returned valuefrom either theDLURLCOMPLETEWRITE orDLURLPATHWRITE scalar function in aSELECT statement on a DATALINKcolumn defined with WRITEPERMISSION ADMIN.

33 Use DLVALUE scalar function instead.

34 Correct the data location to match theone as exists in the row.

35 If assigning a new DATALINK value,use DLVALUE scalar function instead.

36 Provide the data location embeddedwith the write token which is used toopen and modify the file. If the token islost, there is a set of Data Links Filemanager (DLFM) commands availableto retrieve the write token. Refer to the


Data Links Manager AdministrationGuide and Reference for details aboutthe DLM commands.

37 DATALINK value referenced file isbeing updated. First, issue a SQLUPDATE with the DLNEWCOPY orDLPREVIOUSCOPY scalar function onthe DATALINK column to commit orbackout the file changes. Then retry thesame statement again.

38 It is a restriction that DATALINK valuewith DFS scheme cannot be assigned toa DATALINK column defined withWRITE PERMISSION ADMIN. Movethe file to another type of file systemand assign the DATALINK value with adifferent scheme.

39 Use DLVALUE scalar function instead.

40 Check whether the archive server is upand running. Then retry it again.

41 Retry the UPDATE operation again in aseparate transaction.

42 Use either a zero-length string or a nullas the replacement file location.

43 Commit the current transaction. Theretry it again.

44 Use another name for the replacementfile or retry it later.

45 Do not link this file or retry it later.

46 Correct the string format of thereplacement file location.

47 Make sure a file is specified. Use theactual file name, not the symbolic linkfor the replacement file.

48 Unlink the file.

49 Check that the correct file is specifiedand that the file exists.

50 Remove the token from the datalocation value.

sqlcode: -358

sqlstate: 428D1

SQL0359N The range of values for theidentity column or sequence isexhausted.

Explanation: DB2 attempted to generate a valuefor an identity column or sequence object,however all allowable values have already beenassigned.


User Response: For an identity column,redefine the table with a larger range of valuesfor the identity column. If a MAXVALUE orMINVALUE specification has been made thatlimits the range of values to be less than therange for the data type of the column, then thecolumn can be altered to expand the range ofvalid values. Otherwise, the identity columnmust be recreated which requires that the tablebe recreated. First drop the existing table, andthen recreate the table with a different data typefor the identity column, specifying a data typethat has a larger range of values than the currentdata type for the identity column.

For a sequence object, redefine the sequence witha larger range of values. If a MAXVALUE orMINVALUE clause limits the range of values toless than the range for the data type of thesequence object, then alter the sequence toexpand the range of valid values. Otherwise,drop the sequence object and reissue theCREATE SEQUENCE statement specifying a datatype that allows a larger range of values.

sqlcode: -359

sqlstate: 23522

SQL0360W DATALINK values may not bevalid because the table table-nameis in Datalink Reconcile Pending(DRP) or Datalink Reconcile NotPossible (DRNP) state.

Explanation: DATALINK values in tabletable-name may not be valid because the table iseither in Datalink Reconcile Pending (DRP) orDatalink Reconcile Not Possible (DRNP) state.


While in either of these states, control of the fileson the DB2 Data Links Manager is notguaranteed.

Statement processing continues.

User Response: Refer to the AdministrationGuide for information on Datalink ReconcilePending (DRP) and Datalink Reconcile NotPossible (DRNP) states to take appropriateaction.

sqlcode: +360

sqlstate: 01627

SQL0368N The DB2 Data Links Managerdlm-name is not registered to thedatabase.

Explanation: The DB2 Data Links Managerdlm-name is not registered to the database.Registered DB2 Data Links Managers are ignoredif the database manager configuration parameterDATALINKS is set to NO. The DB2 Data LinksManager may have been dropped using theDROP DATALINKS MANAGER command. It ispossible that a new incarnation of the DB2 DataLinks Manager with the same name is currentlyregistered; in that case, the error pertains to oneor more previously dropped incarnations of thatDB2 Data Links Manager.


User Response: Ensure that the databasemanager configuration parameter DATALINKS isset to YES. DATALINK values that are links topreviously dropped DB2 Data Links Managersshould be removed using the reconcile utility.For additional details, see the usage notes for theDROP DATALINKS MANAGER command in theCommand Reference.

sqlcode: -368

sqlstate: 55022

SQL0370N The parameter in position n mustbe named in the CREATEFUNCTION statement forLANGUAGE SQL function name.

Explanation: All parameters for functionsdefined with LANGUAGE SQL must have aparameter-name for each parameter.


User Response: Include a parameter name foreach parameter of the function.

sqlcode: -370

sqlstate: 42601

SQL0372N Only one IDENTITY or ROWIDcolumn is allowed in a table.

Explanation: An attempt was made to do oneof the following:

v Create a table with more than one IDENTITYcolumn.

v Add an IDENTITY column to a table whichalready has one.

v Create a table with more than one ROWIDcolumn.

v Add a ROWID column to a table whichalready has one.


User Response: For a CREATE TABLEstatement, select only one column to have theROWID data type or the IDENTITY attribute. Foran ALTER TABLE statement, a ROWID columnor IDENTITY column already exists for the table.Do not attempt to add another column with datatype ROWID or with the IDENTITY attribute tothe table.

sqlcode: -372

sqlstate: 428C1


SQL0373N The DEFAULT clause cannot bespecified for GENERATEDcolumn column-name.

Explanation: A DEFAULT clause may not bespecified for a column which has been identifiedas a GENERATED column.


User Response: Remove the DEFAULT clauseand resubmit the statement.

sqlcode: -373

sqlstate: 42623

SQL0374N The clause clause has not beenspecified in the CREATEFUNCTION statement forLANGUAGE SQL functionfunction-name but an examinationof the function body reveals thatit should be specified.

Explanation: The following situations may bethe cause of this error.

NOT DETERMINISTIC must be specified ifeither of the following conditions apply withinthe body of the function:

v a function that has the NOT DETERMINISTICproperty is called,

v a special register is accessed.

READS SQL DATA must be specified if the bodyof the function defined with LANGUAGE SQLcontains a subselect or if it calls a function thatcan read sql data.

EXTERNAL ACTION must be specified if thebody of the function defined with LANGUAGESQL calls a function that has the EXTERNALACTION property.


User Response: Either specify the clause orchange the function body.

sqlcode: -374

sqlstate: 428C2

SQL0385W Assignment to an SQLSTATE orSQLCODE variable in an SQLroutine may be over-written anddoes not activate any handler.

Explanation: The SQL routine includes at leastone statement that assigns a value to theSQLSTATE or SQLCODE special variables. Thesevariables are assigned values by processing ofSQL statements in the SQL routine. The valueassigned may therefore be over-written as aresult of the SQL statement processing.Furthermore, the assignment of a value to theSQLSTATE special variable does not activate anyhandlers.

The routine definition was processedsuccessfully.

User Response: None required. Remove anyassignments to the SQLSTATE or SQLCODEspecial variable to prevent the warning.

sqlcode: +385

sqlstate: 01643

SQL0388N In a CREATE CAST statement forfunction function-name, either thesource source-data-type-name andtarget target-data-type-name are bothbuilt-in types or they are the sametype.

Explanation: One of the data types must be auser-defined type. The source type and the targettype cannot be the same data type.


User Response: Change the data type of eitherthe source or the target.

sqlcode: -388

sqlstate: 428DF


SQL0389N The specific function instancespecific-name identified in aCREATE CAST statement eitherhas more than one parameter, hasa parameter that does not matchthe source data type, or returns adata type that does not match thetarget.

Explanation: A cast function must

v have exactly one parameter,

v the data type of the parameter must be thesame as the source data type,

v the result data type must be the same as thetarget data type.


User Response: Either chose a different functioninstance, change the source data type, or changethe target data type.

sqlcode: -389

sqlstate: 428DG

SQL0390N The function function-nameresolved to specific functionspecific-name that is not valid inthe context where it is used.

Explanation: A function resolved to a specificfunction that is not valid in the context where itis used. If specific-name is an empty string, thenthe function resolved to the built-in functionidentified by function-name. Some of the possiblesituations include:

v the specific function is a table function whereonly a scalar, column, or row function isexpected (such as creating a sourced scalarfunction).

v the specific function is a scalar, column, or rowfunction where only a table function isexpected (such as in the FROM clause of aquery).

v the specific function is a row function whereonly a scalar or column function is expected.


User Response: Ensure that the correct functionname and arguments are specified and that thecurrent path includes the schema where thecorrect function is defined. You may need tochange the function name, the current path(using SET CURRENT FUNCTION PATH or theFUNCPATH bind option), or change the contextin which the function is used.

sqlcode: -390

sqlstate: 42887

SQL0391N Invalid use of the row basedfunction function-name.

Explanation: The statement uses a row basedfunction function_name that cannot be used forone of the following reasons:

v The function is used in a GROUP BY or aHAVING clause but is not also included in theselect list.

v The function cannot be used in this contextbecause of the recursive nature of thestatement.

v The function cannot be used in a checkconstraint.

v The function cannot be used in a generatedcolumn.

v The function cannot be used in a viewdefinition where the WITH CHECK OPTIONclause is specified or any view dependent onsuch a view having the WITH CHECKOPTION clause specified.

v The function has an argument that does notresolve to a row of a base table. This wouldinclude the situation involving a result columnof an outer join where NULL producing rowsare possible.

v The function cannot be used on rows from areplicated materialized query table.


User Response: Remove function-name from thecontext where it is not allowed.

sqlcode: -391

sqlstate: 42881


SQL0392N SQLDA provided for cursor cursorhas been changed from theprevious fetch.

Explanation: The application is running withDB2 rules, and has requested that LOB data bereturned as a LOB in one FETCH statement, andas a locator in another FETCH statement. This isnot permitted.

User Response: The statement cannot beexecuted.

Either do not use DB2 rules, or change theapplication to not change the data type codefrom LOB to locator (or the reverse) in theSQLDA between successive fetches.

sqlcode: -392

sqlstate: 42855

SQL0396N Object-type object-name (specificname specific-name) attempted toexecute an SQL statement duringfinal call processing.

Explanation: A routine object-name (specificname specific-name) attempted to execute an SQLstatement (other than CLOSE cursor) duringFINAL CALL (call-type = 255) processing. This isnot allowed.

User Response: Change the routine to not issueSQL statements during FINAL CALL (call-type =255) processing.

sqlcode: -396

sqlstate: 38505

SQL0400 - SQL0499

SQL0401N The data types of the operands forthe operation operator are notcompatible.

Explanation: The operation operator appearingwithin the SQL statement has a mixture ofnumeric and nonnumeric operands, or theoperation operands are not compatible.

Federated system users: this data type violationcan be at the data source or at the federatedserver.

Some data sources do not provide theappropriate values for operator. In these cases themessage token will have the following format:“<data source>:UNKNOWN”, indicating that theactual value for the specified data source isunknown.


User Response: Check all operand data types toensure that they are comparable and compatiblewith the statement usage.

If all the SQL statement operands are correct andaccessing a view, check the data types of all theview operands.

Federated system users: if the reason is

unknown, isolate the problem to the data sourcefailing the request (see the Problem DeterminationGuide for procedures to follow to identify thefailing data source) and examine the data typerestrictions for that data source.

sqlcode: -401

sqlstate: 42818

SQL0402N The data type of an operand of anarithmetic function or operationoperator is not numeric.

Explanation: A nonnumeric operand is specifiedfor the arithmetic function or operator operator.


User Response: Correct the SQL statementsyntax so all specified function or operatoroperands are numeric.

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 theoperators applied to that data source.

sqlcode: -402


sqlstate: 42819

SQL0403W The newly defined alias nameresolved to the object name2which is currently undefined.

Explanation: The alias <name> has beendefined upon:

v a table or view which currently is not definedin the database

v another alias which resolves to a table or viewwhich is not defined in the database.

The object <name2> is the undefined object. Thisobject must exist before any SQL statement(other than CREATE ALIAS) can successfully usethe newly created alias. The specified alias<name> is created.

An inoperative view is considered to beundefined for the purposes of creating an alias.

User Response: Ensure that the undefinedobject <name2> is defined prior to using thenewly created alias in an SQL statement (otherthan CREATE ALIAS).

sqlcode: +403

sqlstate: 01522

SQL0404N A string in the UPDATE orINSERT statement is too long forcolumn name.

Explanation: An INSERT or UPDATE statementspecifies a value that is longer than themaximum-length string that can be stored in thecolumn indicated.


Note: name may or may not be returned inSQLCA, depending on the INSERT orUPDATE statement syntax.

User Response: Check the length of the objectcolumn and correct the program or SQLstatement so the insert or update string does notexceed the maximum length.

sqlcode: -404

sqlstate: 22001

SQL0405N The numeric literal literal is notvalid because its value is out ofrange.

Explanation: The specified numeric literal is notin the acceptable range.

The proper ranges for SQL values are as follows:

v For FLOAT values:

– 0

– In the positive range of +2.225E-307 to+1.79769E+308

– In the negative range of -1.79769E+308 to-2.225E-307.

v -9999999999999999999999999999999. to9999999999999999999999999999999. forDECIMAL values

v -2147483647 to 2147483647 for INTEGERvalues

v -32768 to +32767 for small integer(SMALLINT) values.

In certain contexts the literal may have furtherrestrictions that result in this error. For moreinformation, look up the statement or clause inthe SQL Reference.

Federated system users: this range violation canbe at the data source or at the federated server.The proper ranges for SQL values located in datasource tables depend on the data source. Todetermine the correct range, see the appropriatedocumentation for the data source. Some datasources do not provide the appropriate values forliteral. In these cases the message token will havethe following format: “<datasource>:UNKNOWN”, indicating that the actualvalue for the specified data source is unknown.


User Response: Reduce the literal value to theappropriate size.

Federated system users: if the reason isunknown, isolate the problem to the data sourcefailing the request (see the problem


determination guide for procedures to follow toidentify the failing data source) and examine thedata range restrictions for that data source.

sqlcode: -405

sqlstate: 42820

SQL0406N A numeric value in the UPDATEor INSERT statement is notwithin the range of its targetcolumn.

Explanation: The value of a host variable or anumeric value calculated during processing ofthe UPDATE or INSERT SQL statement isoutside the target column range. This problemmay be caused by the values occurring in theobject column, the SQL operation beingperformed on those values, or both.


User Response: See the explanation of messageSQL0405 for ranges allowed for numeric datatypes.

NOTE: For system catalog updates, see the SQLReference for valid ranges in various columns ofupdatable catalogs.

sqlcode: -406

sqlstate: 22003

SQL0407N Assignment of a NULL value to aNOT NULL column name is notallowed.

Explanation: One of the following occurred:

v The update or insert value was NULL, but theobject column was declared as NOT NULL inthe table definition. Consequently:

– NULL values cannot be inserted into thatcolumn.

– An update cannot set values in that columnto NULL.

– A SET transition-variable statement in atrigger cannot set values in that column toNULL.

v The update or insert value was DEFAULT, butthe object column was declared as NOT NULL

without WITH DEFAULT in the tabledefinition. Consequently:

– A default value of NULL cannot be insertedinto that column.

– An update cannot set default values ofNULL in that column.

– A SET transition-variable statement in atrigger cannot set default values of NULL inthat column.

v The column name list for the INSERTstatement omits a column declared NOTNULL and without WITH DEFAULT in thetable definition.

v The view for the INSERT statement omits acolumn declared NOT NULL and withoutWITH DEFAULT in the base table definition.

If the value for name is of the form“TBSPACEID=n1, TABLEID=n2, COLNO=n3”,then the column name from the SQL statementwas not available when the error was issued. Thevalues provided identify the tablespace, table,and column number of the base table that doesnot allow NULL value.

Federated system users: this situation can bedetected by the federated server or by the datasource. Some data sources do not provide theappropriate values for name. In these cases themessage token will have the following format:“<data source>:UNKNOWN”, indicating that theactual value for the specified data source isunknown.


Note: Under some circumstances, the token namemay not be filled in (sqlerrmc field of theSQLCA not filled in).

User Response: Correct the SQL statement afterexamining the object table definition todetermine which columns of the table have theNOT NULL attribute and do not have the WITHDEFAULT attribute.

If the value for name is of the form“TBSPACEID=n1, TABLEID=n2, COLNO=n3”,you can determine the table name and column


name using the following query:

SELECT C.TABSCHEMA, C.TABNAME,C.COLNAME

FROM SYSCAT.TABLES AS T,SYSCAT.COLUMNS AS C

WHERE T.TBSPACEID = n1AND T.TABLEID = n2AND C.COLNO = n3AND C.TABSCHEMA = T.TABSCHEMAAND C.TABNAME = T.TABNAME

The table and column identified by this querymay be the base table of a view for which theSQL statement failed.

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 for that data source. Rememberthat the defaults (NULL and NOT NULL) are notnecessarily the same between data sources.

sqlcode: -407

sqlstate: 23502

SQL0408N A value is not compatible withthe data type of its assignmenttarget. Target name is name.

Explanation: The data type of the value to beassigned to the column, parameter, SQL variable,or transition variable by the SQL statement isincompatible with the declared data type of theassignment target. Both must be:

v Numeric

v Character

v Graphic

v Dates or character

v Times or character

v Timestamps or character

v Datalinks

v The same distinct types

v Reference types where the target type of thevalue is a subtype of the target type of thecolumn.

v The same user-defined structured types. Or,the static type of the value must be a subtypeof the static type (declared type) of the target.If a host variable is involved, the associatedbuilt-in type of the host variable must becompatible with the parameter of the TO SQLtransform function defined in the transformgroup for the statement.


User Response: Examine the statement andpossibly the target table or view to determine thetarget data type. Ensure the variable, expression,or literal value assigned has the proper data typefor the assignment target. For a user-definedstructured type, also consider the parameter ofthe TO SQL transform function defined in thetransform group for the statement as anassignment target.

sqlcode: -408

sqlstate: 42821

SQL0409N The operand of a COUNTfunction is not valid.

Explanation: As specified in the SQL statement,the operand of the COUNT function does notconform to the rules of SQL syntax. OnlyCOUNT(*) and COUNT(DISTINCT column) areallowed.


User Response: Specify COUNT(*) orCOUNT(DISTINCT column).

NOTE: This message is only applicable toversions of DB2 prior to Version 2.

sqlcode: -409

sqlstate: 42607

SQL0410N The floating point literal literalcontains more than 30 characters.

Explanation: The specified floating point literalis more than 30 characters in length, excludingleading zeros. A floating point literal has amaximum length of 30 characters.



User Response: Shorten the specified literal.

sqlcode: -410

sqlstate: 42820

SQL0412N Multiple columns are returnedfrom a subquery that is allowedonly one column.

Explanation: In the context of the SQLstatement, a fullselect is specified that can haveonly one column as a result.


User Response: Specify only one column whenonly a scalar fullselect is allowed.

sqlcode: -412

sqlstate: 42823

SQL0413N Overflow occurred duringnumeric data type conversion.

Explanation: During processing of the SQLstatement, an overflow condition arose whenconverting from one numeric type to another.Numeric conversion is performed according tothe standard rules of SQL.

Federated system users: numeric conversion canoccur at the federated server, at data sources, orboth.

The statement cannot be processed. No data wasretrieved, updated, or deleted.

User Response: Examine the syntax of the SQLstatement to determine the cause of the error. Ifthe problem is data-dependent, it may benecessary to examine the data processed at thetime of the error.

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 thedata range restrictions for that data source.

sqlcode: -413

sqlstate: 22003

SQL0415N The data types of correspondingcolumns are not compatible in afullselect that includes a setoperator or in the multiple rowsof a VALUES clause of anINSERT or fullselect.

Explanation: There are various statementswhere this error may occur.

v It may occur within a SELECT or VALUESstatement that includes set operations(UNION, INTERSECT, or EXCEPT). Thecorresponding columns of the subselects orfullselects that make up the SELECT orVALUES statements are not compatible.

v It may occur within an INSERT statement thatis inserting multiple rows. In this case, thecorresponding columns of the rows specifiedin the VALUES clause are not compatible.

v It may occur within a SELECT or VALUESstatement where the VALUES clause is usedwith multiple rows. In this case, thecorresponding columns of the rows specifiedin the VALUES clause are not compatible.

The columns are incompatible for one of thefollowing reasons:

v Both columns are not characters

v Both columns are not numbers

v Both columns are not dates

v Both columns are not times

v Both columns are not timestamps

v Both columns are not graphic

v Both columns are not the same user-defineddistinct type.

If the data type of a column is character, date,time, or timestamp the corresponding columnmay be a character string constant.


User Response: Correct the column names usedin the SELECT statements or the expressions inthe VALUES clause so that all correspondingcolumns are compatible types.


sqlcode: -415

sqlstate: 42825

SQL0416N You cannot specify a resultcolumn longer than 254 bytes inthe SELECT or VALUESstatements connected by a setoperator other than UNION ALL.

Explanation: One of the SELECT or VALUESstatements connected by a set operator specifiesa result column that is longer than 254 bytes.VARCHAR or VARGRAPHIC result columnslonger than 254 bytes can be used only with theUNION ALL set operator.


User Response: Either use the UNION ALLoperator instead of UNION, or remove the resultcolumns longer than 254 bytes from the SELECTor VALUES statements.

sqlcode: -416

sqlstate: 42907

SQL0417N A statement string to be preparedcontains parameter markers as theoperands of the same operator.

Explanation: The statement string specified asthe object of a PREPARE or EXECUTEIMMEDIATE contains a predicate or expressionin which parameter markers have been used asoperands of the same operator without a CASTspecification. For example:

? > ?


User Response: This syntax is not supported.Use a CAST specification to give at least one ofthe parameter markers a data type.

sqlcode: -417

sqlstate: 42609

SQL0418N A statement contains a use of aparameter marker that is notvalid.

Explanation: Untyped parameter markerscannot be used:

v in a SELECT list

v as the sole argument of a datetime arithmeticoperation

v in some cases as the sole argument of a scalarfunction

v as a sort key in an ORDER BY clause

Parameter markers can never be used:

v in a statement that is not a prepared statement

v in the fullselect of a CREATE VIEW statement

v in the triggered action of a CREATE TRIGGERstatement

v in a query captured by DB2 Query Patroller


User Response: Correct the syntax of thestatement. If untyped parameter markers are notallowed, use the CAST specification to give theparameter marker a data type.

sqlcode: -418

sqlstate: 42610

SQL0419N A decimal divide operation is notvalid because the result wouldhave a negative scale.

Explanation: A specified decimal division is notvalid because it will result in a negative scale.

The formula used internally to calculate the scaleof the result for decimal division is:

Scale of result = 31 - np + ns - ds

where np is the precision of the numerator, ns isthe scale of the numerator, and ds is the scale ofthe denominator.

Federated system users: Decimal division canoccur at the federated server, at data sources, or


both. The specified decimal division results in aninvalid scale for that data source.


User Response: Examine and ensure theprecision and scale of all columns that mayparticipate in a decimal division. Note that aninteger or small integer value may be convertedto a decimal for this calculation.

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 thedata range restrictions for that data source.

sqlcode: -419

sqlstate: 42911

SQL0420N Invalid character found in acharacter string argument of thefunction function-name.

Explanation: The function function-name has acharacter string argument that contains acharacter that is not valid in a numeric SQLconstant. The function may have been called as aresult of using the CAST specification withfunction-name as the target data type. Thefunction or data type used in the SQL statementmay be a synonym for function-name.

If a decimal character is specified in theDECIMAL function then that is the character thatmust be used in place of the default decimalcharacter.

User Response: Ensure that the characterstrings that are being converted to numeric typescontain only characters that are valid in numericSQL constants, using the decimal character, ifspecified.

sqlcode: -420

sqlstate: 22018

SQL0421N The operands of a set operator ora VALUES clause do not have thesame number of columns.

Explanation: The operands of a set operatorsuch as UNION, EXCEPT, or INTERSECT musthave the same number of columns. The rows in aVALUES clause must have the same number ofcolumns.


User Response: Change the SQL statement soeach operand, or each row of a VALUES clause,has exactly the same number of columns.

sqlcode: -421

sqlstate: 42826

SQL0423N Locator variable variable-positiondoes not currently represent anyvalue.

Explanation: A locator variable is in error.Either it has not had a valid result set locator orLOB locator variable value assigned to it, thelocator associated with the variable has beenfreed, or the result set cursor has been closed.

If variable-position is provided, it gives the ordinalposition of the variable in error in the set ofvariables specified. Depending on when the erroris detected, the database manager may not beable to determine variable-position.

Instead of an ordinal position, variable-positionmay have the value ″function-name RETURNS″,which means that the locator value returnedfrom the user-defined function identified byfunction-name is in error.

User Response: Correct the program so that thelocator variables used in the SQL statement havevalid values before the statement is executed. ALOB value can be assigned to a locator variableby means of a SELECT INTO statement, aVALUES INTO statement, or a FETCH statement.Result set locator values are returned by theASSOCIATE LOCATORS statements. Result setlocator values are only valid as long as theunderlying SQL cursor is open. If a commit orrollback operation closes an SQL cursor, the


result set locator associated with the cursor is nolonger valid.

If this was a WITH RETURN cursor, ensure thecursor is opened before attempting to allocate it.

sqlcode: -423

sqlstate: 0F001

SQL0426N Dynamic commit invalid forapplication executionenvironment.

Explanation: An application executing in aCONNECT TYPE 2 environment or DistributedTransaction Processing (DTP) environment suchas CICS has attempted to execute an SQLdynamic COMMIT statement. The SQL dynamicCOMMIT statement cannot be executed in thisenvironment.

Federated system users: SQL dynamic COMMITstatements cannot be executed during apass-through session.

User Response:

v Use the commit statement provided by theDTP environment to perform the commit. Forexample, in a CICS environment this would bethe CICS SYNCPOINT command.

v If this statement was executed within a storedprocedure, remove the statement entirely.

Federated system users: Either comment out theCOMMIT statement or code it as a staticstatement. Then resubmit your program.

sqlcode: -426

sqlstate: 2D528

SQL0427N Dynamic rollback invalid forapplication executionenvironment.

Explanation: An application executing in aCONNECT TYPE 2 environment or DistributedTransaction Processing (DTP) environment suchas CICS has attempted to execute an SQLdynamic ROLLBACK statement. The SQL

dynamic ROLLBACK statement cannot beexecuted in this environment.

Federated system users: SQL dynamicROLLBACK statements cannot be executedduring a pass-through session.

User Response:

v Use the rollback statement provided by theDTP environment to perform the rollback. Forexample, in a CICS environment this would bethe CICS SYNCPOINT ROLLBACK command.

v If this statement was executed within a storedprocedure, remove the statement entirely.

Federated system users: Either comment out theROLLBACK statement or code it as a staticstatement. Then resubmit your program.

sqlcode: -427

sqlstate: 2D529

SQL0428N The SQL statement is onlyallowed as the first statement in aunit of work.

Explanation: The SQL statement that wasissued is required to execute before any otherSQL statement that initiates a unit of work.Following are possible situations:

v The SQL statement must be first in the unit ofwork and SQL has been issued against theconnection within the unit of work.

v The SQL statement must be first in the unit ofwork and a WITH HOLD cursor is currentlyopen for the connection.

Note that when the statement is DISCONNECTALL, it causes the DISCONNECT to be directedagainst all connections, so the request will fail ifany of the connections violate the aboverestrictions.

User Response: Issue a COMMIT orROLLBACK prior to processing the SQLstatement. If there are any WITH HOLD cursors,these will need to be closed. If the statement isSET INTEGRITY, remove the COMMITTHRESHOLD clause.


sqlcode: -428

sqlstate: 25001

SQL0429N The maximum number ofconcurrent LOB locators has beenexceeded.

Explanation: A maximum of 32,000 concurrentLOB locators per unit of work, is supported byDB2.

User Response: Modify the program so that itrequires fewer concurrent LOB locators and tryagain.

sqlcode: -429

sqlstate: 54028

SQL0430N User defined functionfunction-name (specific namespecific-name) has abnormallyterminated.

Explanation: An abnormal termination hasoccurred while the named UDF was in control.

User Response: The UDF needs to be fixed.Contact the author of the UDF or your databaseadministrator. Until it is fixed, the UDF shouldnot be used.

sqlcode: -430

sqlstate: 38503

SQL0431N User defined functionfunction-name (specific namespecific-name) has been interruptedby the user.

Explanation: A user/client interrupt hasoccurred while the named UDF was in control.

User Response: This could indicate someproblem in the UDF, such as an infinite loop orwait. If the problem persists, (i.e. the need tointerrupt results in the same error condition),then contact the author of the UDF or yourdatabase administrator. Until the problem isfixed, the UDF should not be used.

sqlcode: -431

sqlstate: 38504

SQL0432N A parameter marker cannot havethe user defined type name orreference target type nameudt-name.

Explanation: A parameter marker in thestatement has been determined as having theuser-defined type udt-name or a reference typewith the target type udt-name based on thecontext in which it is used. A parameter markercannot have a user-defined type or reference typeas its data type unless it is part of an assignment(VALUES clause of INSERT or SET clause ofUPDATE) or it is being explicitly cast to auser-defined distinct data type or reference datatype using the CAST specification.


User Response: Use an explicit cast to theuser-defined distinct data type or reference datatype for the parameter marker. An alternative isto cast the columns that are user-defined distinctdata types to their corresponding source datatype or columns that are reference data types totheir corresponding representation type.

sqlcode: -432

sqlstate: 42841

SQL0433N Value value is too long.

Explanation: The value value requiredtruncation by a system (built-in) cast oradjustment function, which was called totransform the value in some way. The truncationis not allowed where this value is used.

The value being transformed is one of thefollowing:

v an argument to a user defined function (UDF)

v an input to the SET clause of an UPDATEstatement

v a value being INSERTed into a table

v an input to a cast or adjustment function insome other context.

v a recursively referenced column whose datatype and length is determined by the


initialization part of recursion and may growin the iterative part of the recursion.

The statement has failed.

User Response: If value is a literal string in theSQL statement, it is too long for its intended use.

If value is not a literal string, examine the SQLstatement to determine where the transformationis taking place. Either the input to thetransformation is too long, or the target is tooshort.

Correct the problem and rerun the statement.

sqlcode: -433

sqlstate: 22001

SQL0434W An unsupported value for clauseclause has been replaced by thevalue value.

Explanation: The value that was specified forclause clause is not supported and has beenreplaced with the identified supported valuevalue.

User Response: No change is required if theselected value is acceptable. Otherwise, specify avalue that is valid for clause.

sqlcode: +434

sqlstate: 01608

SQL0435N An invalid SQLSTATE sqlstate isspecified in the functionRAISE_ERROR.

Explanation: The SQLSTATE specified in theRAISE_ERROR function does not conform to therules for an application defined SQLSTATE.

User Response: Correct the SQLSTATE specifiedin the function RAISE_ERROR. The SQLSTATEmust be a character string containing exactly 5characters. It must be of type CHAR definedwith a length of 5, or type VARCHAR definedwith a length of 5 or greater. The SQLSTATEvalue must follow the rules forapplication-defined SQLSTATEs as follows:

v Each character must be from the set of digits(’0’ through ’9’) or non-accented upper caseletters (’A’ through ’Z’)

v The SQLSTATE class (first two characters)cannot be ’00’, ’01’, or ’02’ since these are noterror classes.

v If the SQLSTATE class (first two characters)starts with the character ’0’ through ’6’ or ’A’through ’H’, then the subclass (last threecharacters) must start with a character in therange ’I’ through ’Z’

v If the SQLSTATE class (first two characters)starts with the character ’7’, ’8’, ’9’ or ’I’though ’Z’, then the subclass (last threecharacters) can be any of ’0’ through ’9’ or ’A’through ’Z’.

sqlcode: -435

sqlstate: 428B3

SQL0436N The terminating NULL characteris missing from the C languageNULL-terminated character stringhost variable.

Explanation: The value of an input hostvariable code in the C programming languagerequires a NULL-terminator character at the endof the string.


User Response: Ensure that the value of theinput host variable is terminated by theNULL-terminator character.

sqlcode: -436

sqlstate: 22024

SQL0437W Performance of this complexquery may be sub-optimal.Reason code: reason-code.

Explanation: The statement may achievesub-optimal performance since the complexity ofthe query requires resources that are notavailable or optimization boundary conditionswere encountered. The following is a list ofreason codes:


1 The join enumeration method wasaltered due to memory constraints

2 The join enumeration method wasaltered due to query complexity

3 Optimizer cost underflow

4 Optimizer cost overflow

5 Query optimization class was too low

6 Optimizer ignored an invalid statistic

The statement will be processed.

User Response: One or more of the following:

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

v Break the statement up into less complex SQLstatements. (Reason codes 1,2,3,4)

v Ensure predicates do not over-specify theanswer set (Reason code 3)

v Change the current query optimization class toa lower value (Reason codes 1,2,4)

v Issue Runstats for the tables involved in thequery (Reason codes 3,4)

v Change the current query optimization class toa higher value (Reason code 5)

v Reissue RUNSTATS for both the tablesinvolved in the query and their correspondingindexes, i.e. use the AND INDEXES ALLclause so that table and index statistics areconsistent (Reason code 6)

sqlcode: +437

sqlstate: 01602

SQL0438N Application raised error withdiagnostic text: text.

Explanation: This error or warning occurred asa result of execution of the RAISE_ERRORfunction or the SIGNAL SQLSTATE statement ina trigger. An SQLSTATE value that starts with’01’ or ’02’ indicates a warning.

User Response: See application documentation.

sqlcode: -438, +438

sqlstate: application-defined

SQL0439N User defined functionfunction-name is indirectlyimplemented by functionsource-function which resulted inerror sqlcode.

Explanation: The function function-name wasreferenced in the user’s statement. However,because the SOURCE clause was used in thedefinition of this function, it has turned out thatfunction source-function actually implements thefunction. (It may be a direct or an indirectdefinition path from function-name tosource-function.) At compile time, theencapsulator (DB2 code which acts on behalf of afunction) for source-function has returned theerror identified by sqlcode.

User Response: The actual error situation needsto be understood better before corrective actioncan be taken. Look up the explanation for sqlcode.If source-function is a built-in function, the sqlcodeshould indicate the problem, as in the case wherea built-in function is directly referenced in theuser’s statement. If source-function is a userdefined function, the message most likelyindicates a problem with one of the arguments orwith the result from the function.

Correct the problem and try again.

sqlcode: -439

sqlstate: 428A0

SQL0440N No authorized routine namedroutine-name of type routine-typehaving compatible arguments wasfound.

Explanation: This occurs in a reference toroutine routine-name, when the database managercannot find a routine it can use to implement thereference. There are several reasons why thiscould occur:

v routine-name was either incorrectly specified ordoes not exist in the database.

v A qualified reference was made, and thequalifier was incorrectly specified.


v The user’s SQL path does not contain theschema to which the desired function ormethod belongs, and an unqualified referencewas used.

v The wrong number of arguments wereincluded.

v The right number of arguments were includedin the function or method reference, but thedata types of one or more of the arguments isincorrect.

v The routine does not exist in the database withthe same function id that was used when thepackage was bound (applies to staticstatements).

v The mutator method corresponding to anattribute assignment used in an UPDATEstatement could not be found. The data type ofthe new value for the attribute is not a datatype that is the same or promotable to the datatype of the attribute.

v The routine invoker is not authorized toexecute the routine.

User Response: Fix the problem and retry. Thiscould involve catalog access, a change to thestatement, a grant of the execute privilege to theroutine invoker, the addition of new functions,and/or a change to the SQL path.

sqlcode: -440

sqlstate: 42884

SQL0441N Invalid use of keywordDISTINCT or ALL with functionfunction-name.

Explanation: There are several possible causes.

v The keyword DISTINCT or ALL was detectedwithin the parentheses in a reference tofunction function-name, and the function hasbeen resolved as a scalar function. Use of thekeyword DISTINCT or ALL with a scalarfunction is invalid.

v The keyword DISTINCT is used in a columnfunction for which it is not supported. Thesefunctions include COVARIANCE,CORRELATION and the linear regressionfunctions (those that start with REGR).

v The function was expected to be a columnfunction supporting the keyword ALL orDISTINCT but the function it resolved to wasnot a column function.

User Response:

v If a scalar function is being used, then removethe keyword DISTINCT or ALL. It is invalidfor a scalar function.

v If the function is a column function that doesnot support the DISTINCT or ALL keywords,then remove the keywords.

v If a column function is being used, then thereis a problem with function resolution. Checkyour function path to see if the desiredfunction is in one of the schemas, and alsocheck the SYSFUNCTIONS catalog for thespelling of the function name and the numberand types of parameters.

Correct the error and try again.

sqlcode: -441

sqlstate: 42601

SQL0442N Error in referring to routineroutine-name. The maximumnumber of allowable arguments(90) has been exceeded.

Explanation: Too many arguments werespecified in the reference to routine routine-name.The maximum allowable is 90.

User Response: Correct the statement byensuring that the correct number of argumentshas been used and try again.

sqlcode: -442

sqlstate: 54023

SQL0443N Routine routine-name (specificname specific-name) has returnedan error SQLSTATE withdiagnostic text text.

Explanation: An SQLSTATE was returned toDB2 by routine routine-name (specific namespecific-name), along with message text text. The


routine could be a user-defined function or auser-defined method.

User Response: The user will need tounderstand the meaning of the error. See yourDatabase Administrator, or the author of theroutine.

Errors that are detected by the IBM suppliedfunctions in the SYSFUN schema all return theSQLSTATE 38552. The message text portion ofthe message is of the form:

SYSFUN:nn

where nn is a reason code meaning:

01 Numeric value out of range

02 Division by zero

03 Arithmetic overflow or underflow

04 Invalid date format

05 Invalid time format

06 Invalid timestamp format

07 Invalid character representation of atimestamp duration

08 Invalid interval type (must be one of 1,2, 4, 8, 16, 32, 64, 128, 256)

09 String too long

10 Length or position in string function outof range

11 Invalid character representation of afloating point number

12 Out of memory

13 Unexpected error

Errors that are detected by the IBM suppliedroutines in the SYSIBM or SYSPROC schemasand IBM supplied procedures in the SYSFUNschema all return the SQLSTATE 38553. Themessage text portion of the message contains amessage number that may be an SQLCODE, (forexample, SQL0572N), a DBA error message (forexample, DBA4747), or some other indicationfrom the routine as to what error wasencountered. Note that if the message for the

message number would normally contain tokens,these token values are only available in thedb2diag.log file.

sqlcode: -443

sqlstate: 38553

SQL0444N Routine routine-name (specificname specific-name) isimplemented with code in libraryor path library-or-path, functionfunction-code-id which cannot beaccessed. Reason code: code.

Explanation: The DBMS is trying to access thebody of the code that implements routineroutine-name (specific name specific-name), andcannot access it for the reason given by reasoncode code (the codes are listed below). The fileimplementing the routine is identified bylibrary-or-path, and the function byfunction-code-id.

(Note that these last two tokens may betruncated, due to limitations in the total tokenlength which can be provided. If this happens,then the definition of the routine in the catalogsmay need to be accessed in order to determinethe full library or path and function code id thatwere defined for the routine.)

User Response: Given for each reason code:

1 Path name library-or-path is longer thanthe maximum (255 bytes). Either theroutine definition needs to be changedto specify a shorter path, or the DB2instance path name is too long. Look atthe catalog definition to determinewhich is the case. It may be necessary tomove the function body to a directorywith a shorter path name.

2 The DB2 instance path name could notbe retrieved from DB2. See your systemadministrator.

3 The path library-or-path could not befound. See the routine creator or yourdatabase administrator. The routine


definition or the location of the routineitself will need to be corrected.

4 The file in library-or-path could not befound. See the routine creator or yourdatabase administrator. The routinedefinition or the location of the routinemay need to be corrected, or the routinemay need to be re-linked.

In OS/2 this reason code can arise if theUDF DLL name is longer than format(8.3). For example a name of″abcdefgh99.dll″ has format (10.3) andwould result in this message withreason code 4. The solution is to changethe name to an acceptable form, forexample ″abcdef99.dll″.

In addition to the above, this reasoncode can result if the routine requires ashared library or DLL, and the sharedlibrary cannot be located (using theconcatenation of directories specified inthe LIBPATH environment variable inUNIX-based systems, the PATHenvironment variable in INTELsystems). There can be multiple levels ofthis indirection involved, leading to thisreason code. For example, routine bodyX can be found, and it needs sharedlibrary Y which can also be found. But Yneeds Z, and Z cannot be located, andthis will result in SQL0444N reason code4.

5 There was insufficient memory to loadthe library containing the function orone or more symbols could not beresolved. Contact the routine creator oryour database administrator to makesure that the library was correctlylinked. All required libraries to resolvereferenced symbols such as externalfunctions must be available. If a lack ofmemory is determined then the systemconfiguration may need to be changedto make more memory available to DB2.

6 The function function-code-id could notbe found in the module named. See theroutine creator or your database

administrator. The routine definition orthe function itself will need to becorrected.

7 The symbol given as the function name(function-code-id) is not the name of avalid function in the named library. Seethe routine creator or your databaseadministrator. The routine definition orthe function itself will need to becorrected.

8 The ″load″ system function has failed,for other than the reasons given above.It may be that the module was notlinked at all, or not linked correctly.

9 There was insufficient memory toresolve the function namefunction-code-id in the library identifiedin library-or-path. Contact the routinecreator or your database administratorto make sure the library containing thefunction was correctly linked. Thesystem configuration may need to bechanged to make more memoryavailable to DB2 Server.

10 The loadquery system call has failed.This can only happen on unix-basedsystems, and is a symptom that thedatabase manager itself has not beeninstalled correctly. Contact your systemadministrator.

11 The agent process is searching for aparticular database manager functionthat should be in the libdb2.a library,and it cannot find it. This can onlyhappen on unix-based systems, and is asymptom that the database manager isnot correctly installed. Contact yoursystem administrator.

15 Access has been denied. This canhappen in Windows NT environments ifthe EXTERNAL NAME specification inthe routine definition statement does notspecify a full path, or the function doesnot exist in the <db2 installationpath>\function directory, necessitating asearch using the PATH environmentvariable. For example, If the PATH


contains a LAN drive prior to thedirectory containing your function andthe DB2 instance is running under theSYSTEM account, this reason code canresult. Verify that the EXTERNALNAME specification in the routinedefinition statement contains the fullpath, or the function exists in the <db2installation path>\function directory. Ifeither of the above is correct and theerror occurs due to DB2 instancerunning under an account which cannotaccess a LAN drive prior to thedirectory containing your function inthe PATH environment variable, youneed to reconfigure the DB2 service torun under a user account that has accessto all the network paths that are in thePATH environment variable. Whenassigning a user account to the DB2service, make sure that the account isgranted all the required advanced userrights as documented in the QuickBeginnings book.

other: An unidentified system failure hasoccurred. Note the code, and see yoursystem administrator.

If unable to diagnose the error using theinformation in this message, it may be necessaryto contact your system administrator forassistance.

Federated system users: if this user definedfunction is a function template (and thus no codeis required to reside on the federated server), youmay want to consider modifying the SQLstatement or statistics to enable this function tobe evaluated on the remote data source.

sqlcode: -444

sqlstate: 42724

SQL0445W Value value has been truncated.

Explanation: The value value was truncated bya system (built-in) cast or adjustment function,which was called to transform the value in some

way. This is a warning situation.

The value being transformed is the output of aroutine (user-defined function (UDF) or method),and is being transformed because of a CASTFROM specification in the routine definition, orbecause the UDF is sourced on another functionand the result needed to be transformed.

User Response: Ensure that the output is asexpected and that the truncation has not causedany unexpected consequences.

sqlcode: +445

sqlstate: 01004

SQL0447W The statement contains redundantspecifications involving the clauseclause.

Explanation: The clause keyword was includedmore than once in the statement. This is awarning condition.

User Response: If the redundancy wasintentional, or if it is determined that no harmhas resulted, then no response is necessary. Thetype of ″harm″ alluded to could include, forexample, the omission of some other desiredkeyword.

sqlcode: +447

sqlstate: 01589

SQL0448N Error in defining routineroutine-name. The maximumnumber of allowable parameters(90 for user defined functions andmethods, 32767 for storedprocedures) has been exceeded.

Explanation: Too many parameters werespecified when defining routine routine-name. Theroutine definition statement may be a CREATEFUNCTION, CREATE PROCEDURE, CREATETYPE (method definition), or ALTER TYPE(method definition).

User Response: Change the statement toinclude fewer parameters.

sqlcode: -448


sqlstate: 54023

SQL0449N The statement defining routineroutine-name contains an invalidlyformatted library/functionidentification in the EXTERNALNAME clause.

Explanation: An error was found in theEXTERNAL NAME clause of the CREATEstatement for user defined function (UDF),user-defined method, or stored procedureroutine-name. The rules for the library/functionidentification are as follows:

The name takes the form ’<a>!<b>’ or ’<a>’. Noblanks are permitted within the single quotes.<a> is one of the following:

v the full-path identification of a file (forexample, (on AIX) /u/slick/udfs/math or (onOS/2) d:\myfunc\math)

v a file name (for example, math) assumed to bein ’function’ directory in the sqllib directory.

If <b> is omitted, the default is the entry pointdefined when the named file was linked. If <b>is present, it identifies the entry point (function)within <a> that will be invoked as the body ofthe routine.

User Response: Correct the problem and tryagain. A possible cause is the inclusion of ablank, or having the ’!’ at the beginning or endof the name.

sqlcode: -449

sqlstate: 42878

SQL0450N Routine routine-name (specificname specific-name) has generateda result value, SQLSTATE value,message text, or scratchpad whichis too long.

Explanation: Upon return from routineroutine-name (specific name specific-name), DB2has detected that more bytes were returned thanwere allocated for one of the following:

v the result value (based upon the routinedefinition). There are several possible causes:

– Too many bytes were moved to the resultbuffer.

– The data type is one where the data valuemust be delimited by a null, such asVARCHAR(n), and the delimiting null wasnot within the range of the defined size.

– DB2 is expecting a two- or four- byte lengthvalue preceding the value, and this lengthexceeds the defined size of the result.

– A LOB locator is returned by the routine,and the length of the LOB value associatedwith this locator exceeds the defined size ofthe result.

The definition of the result argument in theRoutine must conform to the requirement forthe data type. Refer to the ApplicationDevelopment Guide for more information.

v the SQLSTATE value (6 bytes including thenull terminator)

v the message text (71 bytes including the nullterminator).

v the scratchpad content (length declared onCREATE FUNCTION).

This is not permitted.

This error will also be returned if the length fieldof the scratchpad is altered by the routine.

User Response: See your DatabaseAdministrator, or the author of the routine.

sqlcode: -450

sqlstate: 39501

SQL0451N The data-item definition, in thestatement that defines routineroutine-name, contains a data typetype that is not appropriate for anon-sourced routine written in thegiven language.

Explanation: An error was made in thedata-item part of the statement defining routineroutine-name. The user’s statement contained theinvalid type type, or it contained a user definedtype (UDT) which is based on the invalid typetype. The routine definition may be a CREATE


FUNCTION, CREATE PROCEDURE, CREATETYPE (method definition), or ALTER TYPE(method definition).

data-item is a token that identifies the area of theproblem in the statement. For example,″PARAMETER 2″ or ″RETURNS″ or ″CASTFROM″.

User Response: Determine which situation hasoccurred, and take corrective action. Possiblecorrective actions include:

v Changing the routine definition to a supportedtype; for example, from DECIMAL to FLOAT.This may involve a change in the routine bodyitself, and may also involve use of castfunctions upon use of the routine.

v Creating a new (suitably based) user definedtype, or changing the definition of an existingUDT.

sqlcode: -451

sqlstate: 42815

SQL0452N Unable to access the filereferenced by host variablevariable-position. Reason code:reason-code.

Explanation: An error was encounteredattempting to access or while accessing the filereferenced by the ″nth″ host variable, where n =variable-position, for the reason given byreason-code. <variable-position> is set to 0 if thehost variable position could not be determined.The possible reason codes are as follows:

v 01 - The file name length is invalid or the filename and/or the path has an invalid format.

v 02 - The file option is invalid. It must have oneof the following values:

SQL_FILE_READ-read from an existing file

SQL_FILE_CREATE-create a new file for write

SQL_FILE_OVERWRITE-overwrite an existing file.If the file does not exist,create the file.

SQL_FILE_APPEND

-append to an existing file.If the file does not exist,create the file.

v 03 - The file cannot be found.

v 04 - The SQL_FILE_CREATE option wasspecified for a file with the same name as anexisting file.

v 05 - Access to the file was denied. The userdoes not have permission to open the file.

v 06 - Access to the file was denied. The file is inuse with incompatible modes. Files to bewritten to are opened in exclusive mode.

v 07 - Disk full was encountered while writingto the file.

v 08 - Unexpected end of file encountered whilereading from the file.

v 09 - A media error was encountered whileaccessing the file.

v 10 - An incomplete or invalid multibytecharacter was encountered while reading fromthe file.

v 11 - An error was encountered whileconverting data from the file code page to theapplication’s graphic character code page.

User Response:

For reason code 01, correct the file name length,file name and/or path.

For reason code 02, specify a valid file option.

For reason code 03, ensure that the file specifiedexists before attempting to access the file.

For reason code 04, either delete the file if it isno longer required or specify a file name thatdoes not currently exist.

For reason code 05, ensure that the user hasaccess (correct file permissions) to the file.

For reason code 06, either use a different file or,if the file must be accessed, modify theapplication to ensure that the file is not accessedconcurrently.

For reason code 07, delete unnecessary files tofree up disk space or specify a file that resides onanother drive/file system with sufficient diskspace. Also, ensure that no operating system oruser file size limits were reached. If your


application code page uses a multibyte encodingscheme it is possible that only part of the lastcharacter was written, ensure that the filecontains only fully formed characters.

For reason code 08, if a file is to be used forinput, ensure that the file is not modified beforethe entire file has been read.

For reason code 09, correct all errors on themedia where the file resides.

For reason code 10, ensure that the file containsvalid multibyte characters based on the codepage of the application or submit the requestwhile running under the same code page as thecontents of the file.

For reason code 11, ensure that characterconversion support between the code page of thefile, for example Japanese EUC, and the graphiccode page of the application, for example UCS-2,is installed.

sqlcode: -452

sqlstate: 428A1

SQL0453N A problem has been identifiedwith the RETURNS clause in thestatement that defines the routineroutine-name.

Explanation: A problem casting the result ofroutine routine-name has been identified. TheCAST FROM data type is not castable to theRETURNS data type, and it should be. See theSQL Reference for details on casting between datatypes.

User Response: Change the RETURNS or CASTFROM clause so that the CAST FROM data typeis castable to the RETURNS data type.

sqlcode: -453

sqlstate: 42880

SQL0454N The signature provided in thedefinition for routine routine-namematches the signature of someother routine that already exists inthe schema or for the type.

Explanation: The signature of a functionconsists of the function name, the number ofparameters defined for the function, and anordered list of the types of the parameters(without regard to any parameters of the types).

The signature of a method consists of the methodname, the subject type of the method, thenumber of parameters defined for the method,and an ordered list of the types of theparameters (without regard to any parameters ofthe types).

The signature of a procedure consists of theprocedure name and the number of parametersdefined for the procedure (data types are notconsidered).

In this case, either:

v there is a function or procedure (routine-name)already in the schema having the samesignature as the function or procedure beingcreated

v there is a method (routine-name) for the subjecttype having the same signature as the methodspecification being added or the method bodybeing created


User Response: Determine if the existingroutine already provides the functionalitydesired. If not, then the signature of the routinewill have to be changed; for example, bychanging the routine name.

sqlcode: -454

sqlstate: 42723


SQL0455N In routine routine-name, theschema name schema-name1provided for the SPECIFIC namedoes not match the schema nameschema-name2 of the routine.

Explanation: If the SPECIFIC name is specifiedas a two part name, the schema-name1 portionmust be the same as the schema-name2 portion ofthe routine-name. Note that the schema-name2portion of routine-name may have been specifieddirectly or it may have defaulted to theauthorization ID of the statement. If the routineis a method, schema-name refers to the schemaname of the subject type of the method.

User Response: Correct the statement and tryagain.

sqlcode: -455

sqlstate: 42882

SQL0456N In the definition of routineroutine-name, the SPECIFIC namespecific-name already exists in theschema.

Explanation: The user has supplied an explicitSPECIFIC name specific-name in the definition ofroutine routine-name, but this name already existsas the SPECIFIC name for a function, method, orprocedure in the schema.

User Response: Choose a new SPECIFIC nameand try again.

sqlcode: -456

sqlstate: 42710

SQL0457N A function, method, user-defineddata type, or structured data typeattribute cannot be called namesince it is reserved for system use.

Explanation: The user-defined function,method, user-defined data type, or structureddata type cannot be created because a specifiedname is reserved for use by the system. Namesthat cannot be used for function names, distincttype names, structured type names, or attributenames include:

"=","<",">",">=","<=","&=","&>",,"&<","!=","!>","!<","<>",SOME, ANY, ALL, NOT, AND, OR,BETWEEN, NULL, LIKE, EXISTS, IN,UNIQUE, OVERLAPS, SIMILAR, and MATCH.

User Response: Select a name for the function,method, user-defined data type, or structureddata type attribute that is not reserved for systemuse.

sqlcode: -457

sqlstate: 42939

SQL0458N In a reference to routineroutine-name by signature, amatching routine could not befound.

Explanation: In a reference to function, method,or stored procedure routine-name by signature, nomatching function, method, or stored procedurecould be found.

If a data type is used that can accept aparameter, then the type parameter is optional.For example, for CHAR(12), you can eitherspecify the parameter (CHAR(12) or omit it(CHAR()). If you specify the parameter, then theDBMS will only accept an exact match on thedata type AND the data type parameter. If youomit the parameter, then the DBMS will accept amatch on data type only. The CHAR() syntaxprovides a way to tell the DBMS to ignore datatype parameters when finding a matchingfunction.

Note also that in the DROPFUNCTION/PROCEDURE and COMMENT ONFUNCTION/PROCEDURE statements, anunqualified reference is qualified with thestatement authorization ID, and this is theschema where the problem can be found. In theSOURCE clause of a CREATE function, thequalification comes from the current functionpath. In this case, there is no matching functionin the entire path.

A function cannot be sourced on the COALESCE,NULLIF, NODENUMBER, PARTITION,RAISE_ERROR, TYPE_ID, TYPE_NAME,


TYPE_SCHEMA, or VALUE built-in functions.


User Response: Possible responses include:

v Changing the function path to include thecorrect schema.

v Removing parameters from the specificationsof data types.

v Using a SPECIFIC name to refer to thefunction or procedure instead of a signature.

sqlcode: -458

sqlstate: 42883

SQL0461N A value with data typesource-data-type cannot be CAST totype target-data-type.

Explanation: The statement contains a CASTwith the first operand having a data type ofsource-data-type to be cast to the data typetarget-data-type. This cast is not supported.

User Response: Change the data type of eitherthe source or target so that the cast is supported.For predefined data types these are documentedin the SQL Reference. For a cast involving auser-defined distinct type, the cast can bebetween the base data type and the user-defineddistinct type or from a data type that ispromotable to the base data type to theuser-defined distinct type.

sqlcode: -461

sqlstate: 42846

SQL0462W Routine routine-name (specificname specific-name) has returned awarning SQLSTATE, withdiagnostic text text.

Explanation: An SQLSTATE of the form 01Hxxwas returned to DB2 by routine routine-name(with specific name specific-name), along withmessage text text.

User Response: The user will need tounderstand the meaning of the warning. See

your database administrator, or the author of theroutine.

sqlcode: +462

sqlstate: 01Hxx

SQL0463N Routine routine-name (specificname specific-name) has returnedan invalid SQLSTATE state, withdiagnostic text text.

Explanation: The valid SQLSTATEs that aroutine can return are 38xxx (error), 38502 (error)and 01Hxx (warning). This routine routine-name(specific name specific-name) returned an invalidSQLSTATE state, along with message text text.The routine is in error.

User Response: The routine will need to becorrected. See your database administrator, or theauthor of the routine. The applicationsignificance of the bad SQLSTATE can also belearned from the routine author.

sqlcode: -463

sqlstate: 39001

SQL0464W Procedure procedure-name returnedgenerated-nbr-results query resultsets, which exceeds the definedlimit max-nbr-results.

Explanation: The stored procedure named byprocedure-name completed normally. However, thestored procedure exceeded the defined limit onthe number of query result sets the procedurecan return.

generated-nbr-resultsidentifies the number of query resultsets returned by the stored procedure.

max-nbr-resultsidentifies the defined limit on thenumber of query result sets for thestored procedure.

Only the first max-nbr-results query result sets arereturned to the SQL program that issued the SQLCALL statement.


The possible causes are as follows: The storedprocedure is unable to return generated-nbr-resultsresult sets due to the DRDA limitations imposedby the client. The DRDA client establishes thislimit with the MAXRSLCNT DDM code point.

User Response: The SQL statement issuccessful. The SQLWARN9 field is set to ’Z’.

sqlcode: +464

sqlstate: 0100E

SQL0465N Unable to start, initialize, orcommunicate with fenced modeprocess. Reason code code.

Explanation: There is a system related probleminvolved with the running of a fenced moderoutine (user-defined function or method). Theexact nature of the problem is indicated by code.This is NOT a user problem. Possible reasoncodes are:

Routine process errors

21: Failure to initialize internal data orapplication data.

22: Failure to register signal handlers.

23: Failure to grant agent process the accesspermission for the REQUEST QUEUE.

24: Failure to connect to the routine processShared Memory.

25: Failure to open the REPLY QUEUE.

26: Failure to write to the REPLY QUEUE.

27: Failure to create the REQUEST QUEUE.

28: Failure to read from the REQUESTQUEUE.

29: Routine process dies.

30: Routine process catches an USERINTERRUPT signal.

31: Failure to unload routine module.

32: Failure to allocate storage for controlblocks used in moduleloading/unloading.

33: Failure to send SIGINT from agentprocess to routine process.

34: Failure to initialize OLE library.

35: Failure to initialize OLE DBInitialization Service Component.

40: Internal error occurred in routineprocess.

Agent process errors

41: Failure to spawn routine process.

42: Failure to create the REPLY QUEUE.

43: Failure to read from the REPLY QUEUE.

44: Failure to open the REQUEST QUEUE.

45: Failure to write to the REQUESTQUEUE.

47: Failure to grant the routine process theaccess permission to the UDFP sharedmemory set.

48: Failure to grant the routine process theaccess permission to the REPLY QUEUE.

49: Failure to allocate storage for controlblocks used in moduleloading/unloading.

50: Agent process died while runningroutine code or agent code.

51: Agent process catches USERINTERRUPT while running un-fencedroutine code.

60: Internal error occurred in routineprocess.

User Response: Contact your Database orSystem administrator.

sqlcode: -465

sqlstate: 58032

SQL0466W The procedure procedure-namereturns number-results result setsfrom the stored procedure.

Explanation: This message is returned as aresult of issuing a CALL SQL statement. It


indicates that the stored procedure procedure-namehas number-results result sets associated with it.

The statement completed successfully.


sqlcode: +466

sqlstate: 0100C

SQL0467W The procedure procedure-nameincludes another result set. Thereare a total of max-nbr-results resultsets.

Explanation: This message is returned as aresult of closing a cursor. It indicates that anotherresult set exists for stored procedureprocedure-name and the cursor was re-opened onthe next result set. There are a total ofmax-nbr-results result sets from the storedprocedure.

The statement completed successfully.

User Response: None required. Fetches canproceed on to the next result set.

sqlcode: +467

sqlstate: 0100D

SQL0469N The parameter mode (IN, OUT, orINOUT) is not valid for aparameter in procedureprocedure-name with specific namespecific-name (parameter numbernumber, name parameter-name).

Explanation: One of the following errorsoccurred:

v a parameter in an SQL procedure is declaredas OUT and is used as input in the procedurebody

v a parameter in an SQL procedure is declaredas IN and is modified in the procedure body.

User Response: Change the attribute of theparameter to INOUT, or change the use of theparameter within the procedure.

sqlcode: -469

sqlstate: 42886

SQL0470N The user defined routineroutine-name (specific namespecific-name) has a null value forargument argument that could notbe passed.

Explanation: A routine has an input argumentwith a null value but was defined with aparameter style that does not pass nullindicators, or the datatype of this parameter doesnot support null values.

User Response: If the routine is to be calledwith null values, ensure the parameter style andinput types are capable of accepting a null value.For functions, the function could also be createdwith ″RETURNS NULL ON NULL INPUT″.

sqlcode: -470

sqlstate: 39004

SQL0471N Invocation of routine name faileddue to reason reason-code.

Explanation: A routine name was invoked on aDB2 Universal Database for OS/390 server. Theroutine invocation failed because of the conditiondescribed by DB2 reason code reason-code.

The statement cannot be executed. A DSNX9xxmessage describing the error might be displayedon the MVS system console.

User Response: Consult the documentation forthe DB2 Universal Database for OS/390 serverand correct the condition described by the DB2reason code.

sqlcode: -471

sqlstate: 55023

SQL0472N One or more cursors were leftopen by function or methodroutine-name (specific namespecific-name).

Explanation: The function or methodroutine-name (specific name specific-name) did notclose all its open cursors before the invoking


statement completed. Functions and methodsmust close all cursors before the invokingstatement completes.

User Response: Consult with the developer ofthe function or method. The function or methodmust be rewritten to ensure that all cursors areclosed before the invoking statement completes.

sqlcode: -472

sqlstate: 24517

SQL0473N A user defined data type havingthe same name as a systempredefined type cannot be created.

Explanation: The name of a data type to becreated has an unqualified name that is the sameas a system-predefined data type or isBOOLEAN. This is not allowed. Addingdelimiters does not make the name valid.

The statement could not be processed.

User Response: Correct the statement to useanother identifier.

sqlcode: -473

sqlstate: 42918

SQL0475N The result type type-1 of theSOURCE function cannot be castto the RETURNS type type-2 ofthe user defined functionfunction-name.

Explanation: In order for the CREATE of asourced user defined function (UDF) to be valid,the result type (type-1) of the source functionmust be castable to the RETURNS type (type-2)of the function being created. There is nosupported cast between these data types. See theSQL Reference for details on casting between datatypes.

User Response: Change the RETURNS datatype or the SOURCE function identification sothat the result type of the SOURCE function iscastable to the RETURNS data type.

sqlcode: -475

sqlstate: 42866

SQL0476N Reference to routine function-namewas made without a signature,but the routine is not unique inits schema.

Explanation: References to a function or storedprocedure without a signature is permitted, butthe named function or store procedurefunction-name must be unique in its schema andis not. If the routine is a method, a referencewithout a signature is permitted but this namedmethod must be unique for the data type.

Note that in the DROPFUNCTION/PROCEDURE and COMMENT ONFUNCTION/PROCEDURE statements, anunqualified reference is qualified with thestatement authorization ID, and this is theschema where the problem can be found. In theSOURCE clause of a CREATE FUNCTION, thequalification comes from the current functionpath. In this case, the first schema in the pathcontaining a function with this name had otherfunctions by the same name.

Federated system users: For a pass-throughsession, if the statement is a CREATEFUNCTION MAPPING statement, this errorindicates that an attempt was made to create afunction mapping from one remote function tomore than one local function.

User Response: Correct the reference by one ofthe following:

v completing the signature

v using the SPECIFIC name of the desiredroutine

v changing the SQL path

and try again.

sqlcode: -476

sqlstate: 42725


SQL0478N DROP or REVOKE on object typeobject-type1 cannot be processedbecause there is an objectobject-name, of type object-type2,which depends on it.

Explanation: The requested DROP or REVOKEcannot be processed because a dependency existson this object-type1 There is a restrict dependencydefined with objects of type object-type2 (of whichobject object-name is an example).

It may be that the dependency is indirect. Thatis, the named object is dependent on anotherobject which is dependent on the object beingdropped or affected by the REVOKE.

For example:

v function F1 is sourced on function F2

v view V1 is defined using F1

v an attempt to drop F2 will fail due to thedirect dependency of F1 on F2 and the indirectdependency of V1 on F2

User Response: Remove the dependencies onthis object and then reissue the request.

sqlcode: -478

sqlstate: 42893

SQL0480N The procedure procedure-name hasnot yet been called.

Explanation: Either the procedure identified inan ASSOCIATE LOCATORS statement has notyet been called within the application process, orthe procedure has been called, but an explicit orimplicit commit occurred before the statement.

User Response: Correct the statements so thatthe exact syntax used to specify the procedurename on the CALL statement is the same as thaton the ASSOCIATE LOCATORS statement. If anunqualified name is used to CALL the procedure,the one-part name must also be used in the otherstatements. Reissue the statements.

sqlcode: -0480

sqlstate: 51030

SQL0481N The GROUP BY clause containselement-1 nested within element-2.

Explanation: The following types of nesting arenot allowed within a GROUP BY clause:

v CUBE within CUBE, ROLLUP, or GEL

v ROLLUP within CUBE, ROLLUP, or GEL

v () within CUBE, ROLLUP, or GEL

v GROUPING SET within GROUPING SET,CUBE, ROLLUP, or GEL

where GEL represents the element shown asgrouping-expression-list in the syntax diagram ofthe GROUP BY clause.

In some instances the value “---” will be shownfor element 2. In this case “---” represents one ofCUBE, ROLLUP, GROUPING SET, or GEL.


User Response: Modify the GROUP BY clauseto remove the nesting.

sqlcode: -481

sqlstate: 428B0

SQL0483N In the CREATE for user definedfunction function-name statement,the number of parameters doesnot match the number ofparameters of the SOURCEfunction.

Explanation: An attempt is being made toCREATE a user defined function function-namewhich is sourced on another function. One of thefollowing situations has been identified:

v The SOURCE clause uses a function-name(input parameter list) to identify the sourcefunction, and the number of types in the list isdifferent from the number of parameters of thefunction being created.

v The SOURCE clause uses different syntax toidentify the source function, and the numberof types of that function is different from thenumber of parameters of the function beingcreated.


User Response: The number of parameters forthe SOURCE function and for the function beingcreated must be the same. The identification ofthe SOURCE function needs to be changed, to

v fix the input parameter list

v correct the function name or function specificname to identify the proper function.

It is also possible that the function path needs tobe corrected in order for correct functionresolution to occur.

sqlcode: -483

sqlstate: 42885

SQL0486N The BOOLEAN data type iscurrently only supportedinternally.

Explanation: One or more of the data types inthe statement is BOOLEAN. This is notsupported in the current version of DB2.

User Response: Change the data type(s) thenresubmit the statement.

sqlcode: -486

sqlstate: 42991

SQL0487N Routine routine-name (specificname specific-name) attempted toexecute an SQL statement.

Explanation: The program used to implementthe body of a routine is not allowed to executeSQL statements. This routine routine-name(specific name specific-name) contains SQLstatements.

User Response: Remove any SQL statementsthen recompile the program. Investigate the levelof SQL allowed as specified on the statementdefining the routine.

sqlcode: -487

sqlstate: 38001

SQL0489N The function function-name in aSELECT or VALUES list item hasproduced a BOOLEAN result.

Explanation: The function function-name isdefined for use as a predicate, returning aboolean result. Such a result is not valid in aselect list.


User Response: Correct the function name orremove the use of the function.

sqlcode: -489

sqlstate: 42844

SQL0490N Number number directly specifiedin an SQL statement is outsidethe range of allowable values inthis context (minval,maxval)

Explanation: A number (number) was specifiedthat is not valid in the context in which it wasspecified. The minimum allowed value in thiscontext is minval. The maximum allowed value inthis context is maxval. n must be within the rangespecified by minval and maxval (minval =< n =>maxval).

User Response: Change the value n to a validvalue in the statement.

sqlcode: -490

sqlstate: 428B7

SQL0491N The definition of routineroutine-name must have aRETURNS clause, and one of: theEXTERNAL clause (with otherrequired keywords); the RETURNstatement; or the SOURCE clause.

Explanation: A required clause is missing in thedefinition of routine routine-name. If EXTERNALwas specified, one of the following clauses mustalso be specified: LANGUAGE, PARAMETERSTYLE, DETERMINISTIC or NOTDETERMINISTIC, and EXTERNAL ACTION orNO EXTERNAL ACTION.


User Response: Add the missing clause, thentry again.

sqlcode: -491

sqlstate: 42601

SQL0492N There is a problem in theCREATE for user defined functionfunction-name, with parameternumber number. It may involve amismatch with a SOURCEfunction.

Explanation: The parameter in position numberof function function-name is in error and theCREATE cannot be performed. The parameter inposition number of the source function is notcastable to the corresponding parameter of thefunction being created.

User Response: Possible corrections include:

v Identify a different source function.

v Change the data type of the parameter of thefunction being created so that the data type ofthe source function can be cast to this datatype.

sqlcode: -492

sqlstate: 42879

SQL0493N Routine routine-name (specificname specific-name) has returned adate, time or timestamp valuewhich is syntactically ornumerically invalid.

Explanation: The body of user defined function(UDF) or method routine-name (specific namespecific-name) has returned an invalid date, timeor timestamp value.

An example of a syntactically invalid date valueis ’1994-12*25’: the ’*’ should be a ’-’. An exampleof a numerically invalid time value is ’11.71.22’:there is no 71st minute in the hour.

User Response: The routine needs fixing. Seeyour DBA, or the author of the routine.

sqlcode: -493

sqlstate: 22007

SQL0495N Estimated processor cost ofestimate-amount1 processor seconds(estimate-amount2 service units) incost category cost-category exceedsa resource limit error threshold oflimit-amount service units.

Explanation:

The prepare of a dynamic INSERT, UPDATE,DELETE, or SELECT SQL statement resulted in acost estimate that exceeded the error thresholdvalue specified in the resource limit specificationtable (RLST).

This error is also issued if DB2’s cost categoryvalue was ″B″, and the default action specified inthe RLF_CATEGORY_B column in the RLST is toissue an error.

estimate_amount1The cost estimate (in processor seconds)if the prepared INSERT, UPDATE,DELETE or SELECT statement were tobe executed.

estimate_amount2The cost estimate (in service units) if theprepared INSERT, UPDATE, DELETE orSELECT statement were to be executed.

cost-categoryDB2’s cost-category for this SQLstatement. The possible values are A orB.

limit-amountThe error threshold (in service units)specified in the RLFASUERR column ofthe RLST.

The prepare of the dynamic INSERT, UPDATE,DELETE, or SELECT statement was unsuccessful.

User Response: If this SQLCODE was returnedbecause the cost category value is ″B″, it mightbe that the statement is using parameter markersor that some statistics are not available for thereferenced tables and columns. Make sure theadministrator has run the utility RUNSTATS onthe referenced tables. It might also be that UDFs


will be invoked when the statement is executed,or for INSERT, UPDATE, or DELETE statementsthat triggers are defined on the changed table.Check the DSN_STATEMNT_TABLE or theIFCID 22 record for this statement to find thereasons this SQL statement has been put in costcategory ″B″. If the program cannot be changed,or if statistics cannot be obtained, ask theadministrator to change the value in theRLF_CATEGORY_B column in the RLST to ″Y″which allows the statement to execute or ″W″which returns a warning instead of an error.

If the warning is caused by an SQL statementthat is consuming too much processor resource,attempt to rewrite the statement to perform moreefficiently. Another option is to ask theadministrator to increase the error thresholdvalue in the RLST.

sqlcode: -495

sqlstate: 57051

SQL0499N Cursor cursor-name has alreadybeen assigned to this or anotherresult set from procedureprocedure-name.

Explanation: An attempt was made to assign acursor to a result set but multiple cursors havebeen allocated for procedure procedure-name.

User Response: Determine if the target resultset was previously assigned to a cursor. Ifmultiple cursors have been allocated forprocedure procedure-name ensure that only onecursor is used to process the result sets of astored procedure.

sqlcode: -499

sqlstate: 24516

SQL0500 - SQL0599

SQL0501N The cursor specified in a FETCHor CLOSE statement is not open.

Explanation: The program attempted to either:(1) FETCH using a cursor, or (2) CLOSE a cursorat a time when the specified cursor was notopen.


User Response: Check for a previous message(SQLCODE) that may have closed the cursor.Note that after the cursor is closed, any fetchesor close cursor statements receive SQLCODE-501.

If no previous SQLCODEs have been issued,correct the application program to ensure thatthe cursor is open when the FETCH or CLOSEstatement is executed.

sqlcode: -501

sqlstate: 24501

SQL0502N The cursor specified in an OPENstatement is already open.

Explanation: The program attempted to executean OPEN statement for an open cursor.

The statement cannot be processed. The cursorwas unchanged.

User Response: Correct the application programto ensure it does not attempt to execute anOPEN statement for a cursor already open.

sqlcode: -502

sqlstate: 24502

SQL0503N A column cannot be updatedbecause it is not identified in theFOR UPDATE clause of theSELECT statement of the cursor.

Explanation: Using a cursor, the programattempted to update a value in a table columnthat was not identified in the FOR UPDATEclause in the cursor declaration or the preparedSELECT statement.

Any column to be updated must be identified inthe FOR UPDATE clause of the cursordeclaration.


User Response: Correct the applicationprogram. If the column requires updating, add


its name to the FOR UPDATE clause of thecursor declaration.

sqlcode: -503

sqlstate: 42912

SQL0504N The cursor name is not defined.

Explanation: An UPDATE or DELETE WHERECURRENT OF name was specified, but the cursorname was not declared in the applicationprogram.


User Response: Ensure the completeness of theapplication program and correct spelling errorsin the cursor names.

sqlcode: -504

sqlstate: 34000

SQL0505N The cursor name is alreadydefined.

Explanation: The cursor name specified in theDECLARE statement has already been declared.


User Response: Ensure the name is spelledcorrectly.

SQL0507N The cursor specified in theUPDATE or DELETE statement isnot open.

Explanation: The program attempted to executean UPDATE or DELETE WHERE CURRENT OFcursor statement when the specified cursor wasnot open.

The statement cannot be processed. No update ordelete was performed.

User Response: Check for a previous message(SQLCODE) that may have closed the cursor.Note that after the cursor is closed, any fetchesor close cursor statements receive SQLCODE -501and any updates or deletes receive SQLCODE-507. Correct the logic of the application programto ensure that the specified cursor is open at the

time the UPDATE or DELETE statement isexecuted.

sqlcode: -507

sqlstate: 24501

SQL0508N The cursor specified in theUPDATE or DELETE statement isnot positioned on a row.

Explanation: The program attempted to executean UPDATE or DELETE WHERE CURRENT OFcursor statement when the specified cursor wasnot positioned on an object table row. The cursormust be positioned on the row to be updated ordeleted.

The cursor is no longer positioned on a row ifthe row is deleted. This includes any use ofcursors within a savepoint when a ROLLBACKTO SAVEPOINT is performed.

Federated system users: the record in a remotedata source has been updated and/or deleted byanother application (or a different cursor withinthis application) and the record no longer exists.

The statement cannot be processed. No data isupdated or deleted.

User Response: Correct the logic of theapplication program to ensure that the cursor iscorrectly positioned on the intended row of theobject table before the UPDATE or DELETEstatement is executed. Note that the cursor is notpositioned on a row if FETCH returned messageSQL0100W (SQLCODE = 100).

sqlcode: -508

sqlstate: 24504

SQL0509N The table specified in theUPDATE or DELETE statement isnot the same table specified in theSELECT for the cursor.

Explanation: The program attempted to executean UPDATE or DELETE WHERE CURRENT OFcursor statement where the table named did notmatch the name of the table specified in theSELECT statement that declared the cursor.



User Response: Correct the application programto ensure that the table identified in the UPDATEor DELETE statement is the same table identifiedin the cursor declaration.

sqlcode: -509

sqlstate: 42827

SQL0510N UPDATE or DELETE is notallowed against the specifiedcursor.

Explanation: The program attempted to executean UPDATE or DELETE WHERE CURRENT OFcursor statement against a table or viewdefinition that does not permit the requestedupdate or delete operation. For example, thiserror can occur in a delete from a read-only viewor in an update where the cursor was notdefined with the FOR UPDATE clause.

On the database manager the view is read-only ifthe SELECT statement includes :

v The DISTINCT keyword

v A column function in the SELECT list

v A GROUP BY or HAVING clause



– 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 is a restriction onlyin releases of DB2 prior to Version 2).

v A set operator (other than UNION ALL).


The cursor is declared with a FOR FETCH ONLYor ORDER BY clause.

The cursor is ambiguous and the BLOCKINGALL bind option was specified.

The cursor references a view that has anINSTEAD OF UPDATE (or DELETE) trigger.


User Response: If the database manager isfailing the statement and the cursor is based on aread-only SELECT or VALUES statement, do notissue any update or delete statements against it.

If the database manager is failing the statementand the cursor is not based on a read-onlySELECT or VALUES statement and is definedwith a FOR FETCH ONLY or ORDER BY clause,either remove this clause from the cursordefinition or do not issue any update or deletestatements.

If the database manager is failing the statementand the cursor cannot be determined to be eitherfetch only or updatable from its definition orcontext, rebind the program with either theBLOCKING NO or BLOCKING UNAMBIG bindoption.

If the database manager is failing the statementand the cursor is based on a view with anINSTEAD OF UPDATE (or DELETE) trigger, usea searched UPDATE (or DELETE) statement.

Federated system users: isolate the problem tothe data source failing the request (see theproblem determination guide for procedures tofollow to identify the failing data source). If adata source is failing the request, examine therestrictions for that data source to determine thecause of the problem and its solution. If therestriction exists on a data source, see the SQLreference manual for that data source todetermine why the object is not updatable.

sqlcode: -510

sqlstate: 42828

SQL0511N The FOR UPDATE clause is notallowed because the tablespecified by the cursor cannot bemodified.

Explanation: The result table of the SELECT orVALUES statement cannot be updated.

On the database manager, the result table is


read-only if the cursor is based on a VALUESstatement or the SELECT statement contains anyof the following:

v The DISTINCT keyword

v A column function in the SELECT list

v A GROUP BY, HAVING, or ORDER BY clause



– A read-only view

– An OUTER clause with a typed table ortyped view

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

v A set operator (other than UNION ALL).



User Response: Do not perform updates on theresult table as specified.

Federated system users: isolate the problem tothe data source failing the request (see theproblem determination guide for procedures tofollow to identify the failing data source). If adata source is failing the request, examine therestrictions for that data source to determine thecause of the problem and its solution. If therestriction exists on a data source, see the SQLreference manual for that data source todetermine why the object is not updatable.

sqlcode: -511

sqlstate: 42829

SQL0513W The SQL statement will modifyan entire table or view.

Explanation: The UPDATE or DELETEstatement does not contain a WHERE clause soall rows of the table or view are modified if thisstatement is executed.

The statement is accepted.

Federated system users: not all data sourcesreport this warning condition. The federatedserver attempts to issue this warning wheneverthe condition exists, but there is no guaranteethat the federated server can always detect thiscondition. Do not rely on this warning topreclude UPDATE/DELETE operations fromaffecting an entire table or view.

User Response: Ensure that you intend tomodify the entire table or view.

SQL0514N The cursor name is not in aprepared state.

Explanation: The application program tried touse a cursor name that is not in a prepared state.The cursor is associated with a statement thateither (1) was never prepared, (2) was made notvalid by a ROLLBACK, or (3) was made notvalid by either an explicit or implicit rebind ofthe package.


User Response: For case (1), prepare thestatement named in the DECLARE CURSORstatement for name before you try to open thecursor. For case (2), do not issue a ROLLBACKuntil after you finish using the cursor. For case(3), the prepare for the cursor must be reissued.

sqlcode: -514

sqlstate: 26501

SQL0516N The DESCRIBE statement doesnot specify a prepared statement.

Explanation: The statement name in theDESCRIBE statement must specify a statementthat was prepared in the same databasetransaction.


User Response: Verify that the statement namespecifies a statement that has been prepared.

sqlcode: -516

sqlstate: 26501


SQL0517N The cursor name identifies aprepared statement that is not aSELECT or VALUES statement.

Explanation: The cursor name could not be usedas specified because the prepared statementnamed in the cursor declaration was not aSELECT or VALUES statement.


User Response: Verify that the statement nameis specified correctly in the PREPARE and theDECLARE CURSOR for cursor name statements.Or correct the program to ensure that onlyprepared SELECT or VALUES statements areused in association with cursor declarations.

sqlcode: -517

sqlstate: 07005

SQL0518N The statement named in theEXECUTE statement is not in aprepared state or is a SELECT orVALUES statement.

Explanation: The application program tried toEXECUTE a statement that (1) was neverprepared, (2) was made not valid by aROLLBACK, (3) is a SELECT or VALUESstatement, or (4) was made not valid by eitheran explicit or implicit rebind of the package.


User Response: For case (1), prepare thestatement before attempting the EXECUTE. Forcase (2), either do not issue a ROLLBACK untilafter you finish using the prepared statement, orprepare the statement again after theROLLBACK. For case (3), ensure that thestatement is not a SELECT or VALUES statement.For case (4), the prepare for the cursor must bereissued.

sqlcode: -518

sqlstate: 07003

SQL0519N The PREPARE statementidentifies the SELECT or VALUESstatement of the open cursor name.

Explanation: The application programattempted to prepare the SELECT or VALUESstatement for the specified cursor when thatcursor is already open.

The statement cannot be prepared. The cursorwas not affected.

User Response: Correct the application programso it does not attempt to prepare the SELECT orVALUES statement for a cursor that is open.

sqlcode: -519

sqlstate: 24506

SQL0525N The SQL statement cannot beexecuted because it was in error atbind time for section =section-number package =pkgschema.pkgname consistencytoken = 0Xcontoken.


v The statement was in error when the packagewas bound, but the error was ignored thenbecause the option SQLERROR (CONTINUE)was used. Since the statement contains anerror, it cannot be executed.

v The statement might not be an executablestatement at this location, or might only beexecutable by a DB2 application requester

Note that contoken is given in hexadecimal.


User Response: If the SQL statement is notsupposed to execute at the indicated location,then correct the program so that the statement inerror does not execute at that location.Precompile, compile, and bind replace thepackage. If the SQL statement is supposed toexecute at the indicated location, correct theproblem found and reissue PREP or BIND usingACTION(REPLACE). If multiple versions of thepackage have been bound, issue the followingSELECT statement to determine which version


has the error: SELECT PKGVERSION FROMSYSCAT.PACKAGES wherePKGSCHEMA=’pkgschema’ AND PKGNAME =’pkgname’ and HEX(UNIQUE_ID) = ’contoken’

sqlcode: -525

sqlstate: 51015

SQL0526N The requested function does notapply to declared temporarytables.

Explanation: The SQL statement being executedrefers to a declared temporary table. A declaredtemporary table cannot be used in the givencontext.


User Response: Modify the SQL statement toensure that the object references are not todeclared temporary tables.

sqlcode: -526

sqlstate: 42995

SQL0528N The table tablename already has aunique constraint that is aduplicate of constraint name.

Explanation: A UNIQUE clause uses the samecolumn list as the PRIMARY KEY clause, anotherUNIQUE clause or the PRIMARY KEY or aUNIQUE constraint that already exists for thetable tablename. Duplicate unique constraints arenot allowed.

name is the constraint name, if one was specifiedor exists. If a constraint name is not specified,name is the first column name specified in thecolumn list of the UNIQUE clause followed bythree periods.


User Response: Remove the duplicate UNIQUEclause or change the column list to a set ofcolumns that is not already part of a uniqueconstraint.

sqlcode: -528

sqlstate: 42891

SQL0530N The insert or update value of theFOREIGN KEY constraint-name isnot equal to any value of theparent key of the parent table.

Explanation: A value in a foreign key of theobject table is being set, but this value is notequal to any value of the parent key of theparent table.

When a row is inserted into a dependent table,the insert value of a foreign key must be equal tosome value of the parent key of any row of theparent table of the associated relationship.

Similarly, when the value of a foreign key isupdated, the update value of a foreign key mustbe equal to the value of the parent key of anyrow of the parent table of the associatedrelationship at the completion of the statement.

Federated system users: the constraint can existon the data source (if the child and parent tablesexist on the data source).

Some data sources do not provide theappropriate values for constraint name. In thesecases the message token will have the followingformat: “<data source>:UNKNOWN”, indicatingthat the actual value for the specified data sourceis unknown.

The statement could not be executed. Thecontents of the object table are unchanged.

User Response: Examine the insert or updatevalue of the foreign key first, and then compareit with each of the parent key values of theparent table to determine and correct theproblem.

sqlcode: -530

sqlstate: 23503

SQL0531N The parent key in a parent row ofrelationship constraint-name cannotbe updated.

Explanation: An operation attempted to updatea parent key in the row of the parent table butthe parent key in the specified row hasdependent rows in the dependent table


associated with it in the constraint-nameconstraint.

When the update rule of constraintconstraint-name is NO ACTION, the value of aparent key in a parent row cannot be updated ifthe parent row has any dependent rows at thecompletion of the statement.

When the update rule of constraintconstraint-name is RESTRICT, the value of aparent key in a parent row cannot be updated ifthe parent row has any dependent rows at thetime the update of the parent key is attempted.


Some data sources do not provide theappropriate values for constraint name. In thesecases the message token will have the followingformat: “<data source>:UNKNOWN”, indicatingthat the actual value for the specified data sourceis unknown.

The statement could not be executed. Thecontents of the parent table are unchanged.

User Response: Examine the parent key of theobject table and the foreign key of the dependenttable to determine if the value of the specifiedrow of the parent key should be changed. If thisdoes not show the problem, examine the contentsof the object table and the dependent table todetermine and correct the problem.

sqlcode: -531

sqlstate: 23001, 23504

SQL0532N A parent row cannot be deletedbecause the relationshipconstraint-name restricts thedeletion.

Explanation: An operation attempted to delete aspecified row of the parent table but the parentkey in the specified row has dependent rows inthe referential constraint constraint-name and thedelete rule of NO ACTION or RESTRICT isspecified for the relationship.

When the delete rule of constraint constraint-name

is NO ACTION, a row of the parent table cannotbe deleted if the dependent rows are stilldependent on the parent key at the completionof the statement.

When the delete rule of constraint constraint-nameis RESTRICT, a row of the parent table cannot bedeleted if the parent row has any dependentrows at the time of the delete.

Note that a delete can cascade to delete otherrows in dependent tables that have a delete ruleof NO ACTION or RESTRICT. Thus theconstraint constraint-name may be on a differenttable than the original delete operation.


Some data sources do not provide theappropriate values for constraint name. In thesecases the appropriate fields contain values (suchas “unknown”) that indicate that the actual valueis unknown.

The statement could not be executed. Thecontents of the table are unchanged.

User Response: Examine the delete rule for alldescendent tables to determine and correct theproblem. The specific tables involved can bedetermined from the relationship constraint-name.

sqlcode: -532

sqlstate: 23001, 23504

SQL0533N The INSERT statement is notvalid because a relationshiprestricts the result of the fullselectto one row.

Explanation: An INSERT operation with afullselect attempted to insert multiple rows into atable that is a parent and a dependent in thesame relationship of a referential constraint.

The fullselect of the INSERT operation shouldreturn no more than one row of data.

The INSERT statement could not be executed.The contents of the object table are unchanged.

Federated system users: the constraint can exist


on the data source (if the child and parent tablesexist on the data source).

User Response: Examine the search condition ofthe fullselect to ensure selection of no more thanone row of data.

sqlcode: -533

sqlstate: 21501

SQL0534N Invalid multiple-row update.

Explanation: An UPDATE operation attemptedto perform a multiple-row update of a columnincluded in a primary key or unique index.

Multiple-row updates of columns of a primarykey or unique index are not supported.

The UPDATE statement could not be executed.The contents of the table are unchanged.

Federated system users: the constraint can existon federated server (if the child and parent tablesexist as tables on federated server), or it can existon the data source (if the child and parent tablesexist on the data source).

User Response: Ensure the search condition ofthe UPDATE statement selects only one objecttable row to update.

sqlcode: -534

sqlstate: 21502

SQL0535N The DELETE statement is notvalid because a self-referencingrelationship restricts the deletionto one row.

Explanation: A DELETE operation with aWHERE clause attempted to delete multiplerows from a table which is a parent and adependent in the same relationship of areferential constraint with a RESTRICT or SETNULL delete rule.

The WHERE clause of the DELETE operationshould select no more than one row of data.

The DELETE statement could not be executed.The contents of the object table are unchanged.


User Response: Examine the WHERE clausesearch condition to ensure no more than one rowof data is selected.

NOTE: This is only a restriction in releases ofDB2 prior to Version 2.

sqlcode: -535

sqlstate: 21504

SQL0536N The DELETE statement is notvalid because table name can beaffected by the operation.

Explanation: A DELETE operation wasattempted with the indicated table referenced ina subquery.

The indicated table referenced in a subquery ofthe DELETE statement can be affected because itis either:

v A dependent of the DELETE object table in arelationship with a CASCADE or SET NULLdelete rule.

v A dependent of another table in a relationshipwith a CASCADE or SET NULL delete ruleand deletions from the DELETE object tablecan cascade to that table.


Some data sources do not provide theappropriate values for name. In these cases theappropriate fields contain values (such as“unknown”) that indicate that the actual value isunknown.


User Response: Do not reference a table in aDELETE statement subquery when the table canbe affected by the DELETE statement.

NOTE: This error is only applicable to releases of


DB2 prior to Version 2 and hosts accessedthrough DB2 Connect.

sqlcode: -536

sqlstate: 42914

SQL0537N The PRIMARY KEY clause, aFOREIGN KEY clause, a UNIQUEclause, or a PARTITIONING KEYclause identifies column namemore than once.

Explanation: The column name appears morethan once in a PRIMARY KEY clause, FOREIGNKEY clause, UNIQUE clause or PARTITIONINGKEY clause of a CREATE or ALTER statement.




User Response: Specify unique names for eachcolumn.

sqlcode: -537

sqlstate: 42709

SQL0538N FOREIGN KEY name does notconform to the description of theparent key of table table-name.

Explanation: The definition of the indicatedforeign key does not conform to the parent keydescription of the table table-name.

Possible errors are:

v The number of columns in the foreign keycolumn list does not match the number ofcolumns in the parent key column list.

v The number of columns in the foreign keycolumn list does not match the number ofcolumns in the primary key of the parent table(a parent key column list is not specified).

v The descriptions of the corresponding columnsare not compatible. Column descriptions arecompatible if corresponding columns havecompatible data types (both columns arenumeric, character strings, graphic, date/time,or have the same distinct type).

name is the constraint name if specified in theFOREIGN KEY clause. If a constraint name wasnot specified, name is the first column namespecified in the clause followed by three periods.

Federated system users: some data sources donot provide the appropriate values for name andtable-name. In these cases the appropriate fieldscontain values (such as “unknown”) that indicatethat the actual value is unknown.

The constraint can exist the data source (if thechild and parent tables exist on the data source).


User Response: Correct the statement so theforeign key description conforms to the parentkey description.

sqlcode: -538

sqlstate: 42830

SQL0539N Table name does not have akey-type key.


v The table name was specified as a parent in aFOREIGN KEY clause but the table is notdefined as a parent because it does not have aprimary key.

v The ALTER TABLE statement attempted todrop the primary key for the table name butthe table does not have a primary key.

v The ALTER TABLE statement attempted todrop the partitioning key for the table namebut the table does not have a partitioning key.



Some data sources do not provide theappropriate values for name and key-type. In thesecases the appropriate fields contain values (suchas “unknown”) that indicate that the actual valueis unknown.

The statement cannot be processed. A systemcatalog cannot be defined as a parent in areferential constraint.

User Response: When creating a referentialconstraint, specify the primary key beforespecifying any foreign keys (constraints).

sqlcode: -539

sqlstate: 42888

SQL0540N The definition of table table-nameis incomplete because it lacks aprimary index or a requiredunique index.

Explanation: The table named was defined witha PRIMARY KEY clause or a UNIQUE clause. Itsdefinition is incomplete, and it cannot be useduntil a unique index is defined for the primarykey (the primary index) and for each set ofcolumns in any UNIQUE clause (the requiredunique indexes). An attempt was made to usethe table in a FOREIGN KEY clause or in an SQLmanipulative statement.


User Response: Define a primary index or arequired unique index on the table beforereferencing it.

sqlcode: -540

sqlstate: 57001

SQL0541W The referential, primary key, orunique constraint name is ignoredbecause it is a duplicateconstraint.

Explanation: If name refers to a referentialconstraint, then a FOREIGN KEY clause uses thesame foreign key and parent table as anotherFOREIGN KEY clause.

If name refers to a primary key or unique

constraint, then one of the following situationsexists.

v A PRIMARY KEY clause uses the same set ofcolumns as a UNIQUE clause in the statement.

v A UNIQUE clause uses the same set ofcolumns as the PRIMARY KEY clause oranother UNIQUE clause in the statement.

v A PRIMARY KEY or a UNIQUE constraint onthe same set of columns already exists for thetable tablename.

name is the constraint name, if specified. If aconstraint name was not specified, name is thefirst column name specified in the column list ofthe FOREIGN KEY or UNIQUE clause followedby three periods.



The indicated referential constraint or uniqueconstraint was not created. The statement wasprocessed successfully.

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

sqlcode: +541

sqlstate: 01543

SQL0542N name cannot be a column of aprimary key or unique keybecause it can contain null values.

Explanation: The column name identified in aPRIMARY KEY clause or UNIQUE clause isdefined to allow null values.

Federated system users: some data sources donot provide the appropriate values for name. Inthese cases the appropriate fields contain values(such as “unknown”) that indicate that the actualvalue is unknown.



User Response: Correct the column, primarykey or unique key definition.

sqlcode: -542

sqlstate: 42831

SQL0543N A row in a parent table cannot bedeleted because the checkconstraint constraint-name restrictsthe deletion.

Explanation: The delete operation cannot beexecuted because the target table is a parent tableand is connected with a referential constraint to adependent table with a delete rule of SET NULL.However, a check constraint defined on thedependent table restricts the column fromcontaining a null value.


User Response: Examine the foreign key and itsdelete rule in the dependent table and theconflicting check constraint. Change either thedelete rule or the check constraint so that theydo not conflict with each other.

sqlcode: -543

sqlstate: 23511

SQL0544N The check constraintconstraint-name cannot be addedbecause the table contains a rowthat violates the constraint.

Explanation: At least one existing row in thetable violates the check constraint that is beadded in the ALTER TABLE statement.


User Response: Examine the check constraintdefinition that was specified in the ALTERTABLE statement and the data in the table todetermine why there is a violation of theconstraint. Change either the check constraint orthe data so that the constraint is not violated.

sqlcode: -544

sqlstate: 23512

SQL0545N The requested operation is notallowed because a row does notsatisfy the check constraintconstraint-name.

Explanation: Check constraint violations canoccur on either INSERT or UPDATE operations.The resulting row violated the check constraintdefinition on that table.


User Response: Examine the data and the checkconstraint definition in the catalog viewSYSCAT.CHECKS to determine why the INSERTor UPDATE statement failed. Change the data sothat the constraint is not violated.

sqlcode: -545

sqlstate: 23513

SQL0546N The check constraintconstraint-name is invalid.

Explanation: A check constraint in the CREATETABLE or ALTER TABLE statement is invalid forone or more of the following reasons:

v the constraint definition contains a subquery

v the constraint definition contains a columnfunction

v the constraint definition contains a hostvariable

v the constraint definition contains a parametermarker

v the constraint definition contains a specialregister

v the constraint definition contains a variantuser defined function

v the constraint definition contains a userdefined function with external action

v the constraint definition contains a userdefined function with the scratchpad option

v the check constraint is part of a columndefinition, and its check-condition contains areference to a column name other than thecolumn being defined.

v the constraint definition contains a dereferenceoperation or a DEREF function where the


scoped reference argument is other than theobject identifier (OID) column.

v the constraint definition uses a TYPEpredicate.

v the constraint definition includes a CASTspecification with a SCOPE clause.


User Response: The user response is one of thefollowing, depending on the cause of the error:

v change the check constraint so that it does notinclude the listed item.

v move the check constraint definition outsidethe column definition, so that it becomes atable level constraint definition.

sqlcode: -546

sqlstate: 42621

SQL0548N A check constraint or generatedcolumn that is defined withcheck-condition-element is invalid.

Explanation: A check constraint in the CREATETABLE or ALTER TABLE statement is invalid forone or more of the following reasons:

v the constraint definition contains a subquery

v the constraint definition contains a columnfunction

v the constraint definition contains a hostvariable

v the constraint definition contains a parametermarker

v the constraint definition contains a specialregister

v the constraint definition contains a functionthat is not deterministic

v the constraint definition contains a userdefined function with external action

v the constraint definition contains a userdefined function with the scratchpad option

v the definition contains a user defined functionwith the CONTAINS SQL or READS SQLDATA option

v the definition contains a reference to agenerated column which is based on anexpression

v the check constraint is part of a columndefinition, and its check-condition contains areference to a column name other than thecolumn being defined

v the generated column definition contains areference to itself

v the constraint definition contains a dereferenceoperation or a DEREF function where thescoped reference argument is other than theobject identifier (OID) column.

v the constraint definition uses a TYPEpredicate.

v the constraint definition includes a CASTspecification with a SCOPE clause.

v The constraint or generated column definitioncontains a text search function.

The token within the text of the error messagelists the invalid item.


User Response: The user response is one of thefollowing, depending on the cause of the error:

v change the check constraint or generatedcolumn so that it does not include the listeditem.

v move the check constraint definition outsidethe column definition, so that it becomes atable level constraint definition.

sqlcode: -548

sqlstate: 42621.

SQL0549N The statement statement is notallowed for object-type1object-name1 because the bindoption DYNAMICRULES RUN isnot in effect for the object-type2.

Explanation: A program attempted to issue theindicated SQL statement that is one of severalSQL statements that can be dynamicallyprepared only in a package exhibiting run


behavior. Those SQL statements are:

v Dynamic GRANT statement

v Dynamic REVOKE statement

v Dynamic ALTER statement

v Dynamic CREATE statement

v Dynamic DROP statement

v Dynamic COMMENT ON statement

v Dynamic RENAME statement

v Dynamic SET INTEGRITY statement

v Dynamic SET EVENT MONITOR STATEstatement

statementThe SQL statement in error

object-type1PACKAGE or DBRM. DBRM is validonly in a DRDA connection.

object-name1If object-type1 is PACKAGE, object-name1is the name of the package in the format’location-id.collection-id.package-id’. Ifobject-type1 is DBRM, object-name1 is thename of the DBRM in the format’plan-name DBRM-name’.

object-type2PACKAGE or PLAN. PLAN is validonly in a DRDA connection. Ifobject-type1 is PACKAGE, object-type2 canbe either PACKAGE or PLAN(whichever is bound withDYNAMICRULES(BIND)). If object-type1is DBRM, object-type2 is PLAN.

The SQL statement cannot be executed.

User Response: Do one of the following tocorrect the error:

v If the SQL statement is embedded, remove it,precompile and compile the applicationprogram again, and reissue the BINDcommand.

v If appropriate, use the SQL statement with apackage or plan that is bound withDYNAMICRULES(RUN).

v Issue the REBIND command with theDYNAMICRULES(RUN) option for the plan orpackage to which the SQL statement is bound.

sqlcode: -549

sqlstate: 42509

SQL0551N authorization-ID does not have theprivilege to perform operationoperation on object name.

Explanation: Authorization ID authorization-IDattempted to perform the specified operation onname without the proper authorization.

If creating or altering a table with referentialconstraints, this message (SQLCODE) canindicate that the user does not have theREFERENCES privilege to create or drop aFOREIGN KEY. In this case the operation is“REFERENCES” and the name is the object theconstraint references.

If attempting to run a DB2 utility or CLIapplication, the DB2 utility programs may needto be rebound to the database because the useridwho created the database no longer exists or nolonger has the required privileges.

If this error occurs during invocation of aroutine, then authorization ID authorization-IDdoes not have the EXECUTE privilege on anycandidate routine in the SQL path. name is thename of a candidate routine in the SQL path.

Federated system users: if this message isreturned when the user is changing theremote_pw column of theSYSCAT.USEROPTIONS view, the user is notauthorized to change a password for anotheruser. The user performing the alter operationmust have either SYSADM authority or anauthorization ID (the value in the USER specialregister) that matches the value of the authidcolumn in the rows being updated. Some datasources do not provide the appropriate values forauthid, <operation>, and <name>. In these casesthe message tokens will have the followingformat: “<data source> AUTHID:UNKNOWN”,“UNKNOWN”, and “<datasource>:TABLE/VIEW”, indicating that the


actual values for the authid, operation, and nameat the specified data source are not known.


User Response: Ensure that authorization-ID hasthe authorization necessary to perform theoperation.

Federated system users: this authorization can beat the federated server, the data source, or both.

If the DB2 utility programs need to be reboundto the database, the database administrator canaccomplish this by issuing one of the followingCLP command from the bnd subdirectory of theinstance, while connected to the database:

v ″DB2 bind @db2ubind.lst blocking all grantpublic″ for the DB2 utilities.

v ″DB2 bind @db2cli.lst blocking all grantpublic″ for CLI.

sqlcode: -551

sqlstate: 42501

SQL0552N authorization-ID does not have theprivilege to perform operationoperation.

Explanation: Authorization ID authorization-IDattempted to perform the specified operationwithout the proper authorization.

Federated system users: some data sources donot provide the appropriate values forauthorization-ID and <operation>. In these casesthe message tokens will have the followingformat: “<data source> AUTHID:UNKNOWN”,and “UNKNOWN” indicating that the actualvalues for authid and operation at the specifieddata source are not known.


User Response: Ensure that authorization-ID hasthe authorization to perform the operation.

Federated system users: this authorization can beat the federated server, the data source, or both.

sqlcode: -552

sqlstate: 42502

SQL0553N An object cannot be created withthe schema name schema-name.

Explanation: The reason the schema nameschema-name is invalid depends on the type ofobject that is being created.

v Objects of types that existed in releases priorto DB2 Version 2 (tables, views, indexes andpackages) cannot be created with the schemaname SYSCAT, SYSFUN, SYSSTAT or SYSIBM.It is strongly advised that schema namesshould not start with SYS since additionalschemas starting with these letters may bereserved for exclusive use of DB2 in the future.

v Objects of types that are being introducedstarting with DB2 Version 2 (user definedfunctions, distinct types, triggers, schemata,and aliases) cannot be created with anyschema name that starts with the letters SYS.


User Response: Use a valid schema name orremove the explicit schema name and rerun thestatement.

sqlcode: -553

sqlstate: 42939

SQL0554N An authorization ID cannot granta privilege to itself.

Explanation: An authorization ID attempted toexecute a GRANT statement where theauthorization ID itself appears as one of theentries in the authorization ID list to whichprivileges are to be granted.


User Response: Remove the authorization IDfrom the list.

sqlcode: -554

sqlstate: 42502

SQL0555N An authorization ID cannotrevoke a privilege from itself.

Explanation: An authorization ID attempted toexecute a REVOKE statement where the


authorization ID itself appears as one of theentries in the authorization ID list from whichprivileges are to be revoked.


User Response: Remove the authorization IDfrom the list.

sqlcode: -555

sqlstate: 42502

SQL0556N An attempt to revoke a privilegefrom authorization-ID was deniedbecause authorization-ID does nothold this privilege.

Explanation: The privilege cannot be revokedbecause authorization-ID does not hold theprivilege.


User Response: Change the REVOKE statementto conform to the REVOKE rules and resubmitthe statement. Ensure that when a REVOKEstatement lists several privileges to be revokedand a list of authorization IDs that eachauthorization ID possesses at least one of thespecified privileges.

sqlcode: -556

sqlstate: 42504

SQL0557N The specified combination ofprivileges cannot be granted orrevoked.


v The GRANT or REVOKE statement contains acombination of privileges that are of differentclasses. The privileges must all be of one class.Examples are DATABASE, PLAN, or TABLE.

v The GRANT statement attempted to grant aprivilege for a view that is not allowed.ALTER, INDEX and REFERENCES cannot begranted for a view.


User Response: Correct and resubmit thestatement.

sqlcode: -557

sqlstate: 42852

SQL0558N An attempt to revoke a privilegefrom authorization-ID was deniedbecause authorization-ID wouldstill hold control authority.

Explanation: authorization-ID holds the controlprivilege. The privilege to be revoked is implicitin the control privilege, so it cannot be revokedunless the control privilege is also revoked.

The valid values for control are the following:

v DBADM

v CONTROL

v CREATE NOT FENCED ROUTINE

The statement cannot be executed. No privilegesare revoked.

User Response: Revoke the control privilege, ifdesired.

sqlcode: -558

sqlstate: 42504

SQL0562N The specified database privilegescannot be granted to PUBLIC(public).

Explanation: The GRANT statement attemptedto grant a database privilege to the reservedauthorization ID PUBLIC (public). DBADMauthority cannot be granted to PUBLIC (public).


User Response: The implied function is notsupported.

sqlcode: -562

sqlstate: 42508


SQL0567N authorization-ID is not a validauthorization ID.

Explanation: The authorization ID specified byauthorization-ID is not valid for one of thefollowing reasons:

v It begins with ″SYS″, ″sys″, ″IBM″, ″ibm″,″SQL″, or ″sql″.

v It contains characters other than a through z,A through Z, 0 through 9, and the threespecial characters (#,@.$).

v It is delimited and contains lower case letters.

v It is GUESTS, ADMINS, USERS, or LOCAL.

v It is PUBLIC preceded by the keyword USERor GROUP in a GRANT or REVOKEstatement.


User Response: Correct the invalidauthorization ID.

sqlcode: -567

sqlstate: 42602

SQL0569N The GRANT/REVOKE statementfailed because authorization-namemay identify both a user and agroup in the system.

Explanation: The GRANT or REVOKEstatement specified an authorization name thatmay identify both a user and a group in thesecurity namespace, and did not explicitlyspecify the USER or GROUP keyword in thestatement. The statement is therefore ambiguous.Note that when using DCE security, the USER orGROUP keyword is always required.

User Response: Change the statement toexplicitly specify the USER or GROUP keywordto uniquely identify the required authorizationid.

sqlcode: -569

sqlstate: 56092

SQL0570W Not all requested privileges onobject object-name of typeobject-type were granted.

Explanation: A GRANT operation wasattempted on object object-name of typeobject-type, but some or all of the privileges werenot granted. The authorization ID that issued thestatement does not have all of the privileges tobe granted with grant option or does not haveDBADM authority.

All valid requested privileges were granted.

User Response: Obtain the required authorityand try the the operation again.

sqlcode: +570

sqlstate: 01007

SQL0572N Package pkgname is inoperative.

Explanation: The package pkgname is marked asinoperative and must be explicitly rebound(without specifying RESOLVE CONSERVATIVE)before it can be used. This package cannot beused because one or more user-defined functionsthat it depends upon have been dropped.

User Response: Explicitly rebind the namedpackage using either the REBIND (withoutspecifying RESOLVE CONSERVATIVE) or theBIND command.

sqlcode: -572

sqlstate: 51028

SQL0573N A column list specified in thereferences clause of constraintname does not identify a uniqueconstraint of the parent tabletable-name.

Explanation: A list of column names wasspecified in the references clause for theconstraint identified by name that does not matchthe column names of the primary key or anyunique key of the referenced table table-name.

name is the constraint name, if specified. If aconstraint name was not specified, name is thefirst column name specified in the column list of


the FOREIGN KEY clause followed by threeperiods.


User Response: Correct the column list in thereferences clause or add the unique constraint tothe referenced table.

sqlcode: -573

sqlstate: 42890

SQL0574N DEFAULT value or IDENTITYattribute value is not valid forcolumn column-name in tabletable-name. Reason code:reason-code.

Explanation: The DEFAULT value or IDENTITYattribute value for column column-name in tabletable-name is not valid. The possible reason codesare as follows:

1 The value is not assignable to thecolumn because the constant does notconform to the format for a constant ofthat data type, the value has anincorrect length or precision, or thefunction returns an incorrect data type.

2 A floating-point constant is specifiedand the column is not a floating pointdata type

3 A decimal constant is specified andnon-zero digits would be truncatedwhen assigned to the column

4 The value is more than 254 bytes,including quotes for strings, introducercharacters such as the X for a hexconstant, fully qualified function names,and parentheses. Non-significant blanksin the value are ignored. In an unequalcode page environment, the value maybe more than 254 bytes due toexpansion of the string in the databasecode page.

5 The USER special register is specifiedand the length attribute of the characterstring data type is less than 8.

6 A datetime special register (CURRENT

DATE, CURRENT TIME, or CURRENTTIMESTAMP) is specified and does notmatch the data type of the column.

7 A function was specified that is notsupported. The specified function mustbe system-generated cast function orone of the built-in functions BLOB,DATE, TIME, or TIMESTAMP.

8 The argument to a datetime functionwas not a string constant or thecorresponding datetime special register.

9 A system-generated cast function wasspecified and the column is not definedwith a user-defined distinct type.

10 A value with non-zero scale wasspecified for the START WITH orINCREMENT BY option of an identitycolumn.

11 The CURRENT SCHEMA specialregister is specified and the lengthattribute of the character string datatype is less than 128.

<0 Any reason code that is less than zero isan SQLCODE. The error in theDEFAULT value specification can bedetermined by checking the errormessage corresponding to thisSQLCODE.


User Response: Correct the DEFAULT value orIDENTITY attribute value based on the reasoncode that was returned.

sqlcode: -574

sqlstate: 42894

SQL0575N View or materialized query tablename cannot be used because ithas been marked inoperative.

Explanation: The view or materialized querytable name has been marked inoperative becausea table, view, alias, or privilege upon which it isdependent has been removed. The view cannot


be used by any SQL statement other than one ofthe following:

v COMMENT ON

v DROP VIEW or DROP TABLE

v CREATE ALIAS

v CREATE VIEW or CREATE TABLE


User Response: If name is a view, recreate theview by issuing a CREATE VIEW statementusing the same view definition as the inoperativeview. If name is a materialized query table,recreate the materialized query table by issuingthe CREATE TABLE statement using the samematerialized query table definition as in theinoperative materialized query table.

sqlcode: -575

sqlstate: 51024

SQL0576N Alias name cannot be created forname2 as it would result in arepetitive alias chain.

Explanation: The alias definition of name onname2 would have resulted in a repetitive aliaschain which could never be resolved. Forexample, ″alias A refers to alias B which refers toalias A″ is a repetitive alias chain which couldnever be resolved.


User Response: Change the alias definition forname or revise the definition of one of the otheralias definitions in the alias chain to avoid arepetitive chain.

sqlcode: -576

sqlstate: 42916

SQL0577N User defined routine routine-name(specific name specific-name)attempted to modify data but wasnot defined as MODIFIES SQLDATA.

Explanation: The program used to implementthe body of a routine is not allowed to modifySQL data.

User Response: Remove any SQL statementsthat modify data then recompile the program.Investigate the level of SQL allowed as specifiedwhen defining the routine.

sqlcode: -577

sqlstate: 38002

sqlstate: 42985

SQL0579N Routine routine-name (specificname specific-name) attempted toread data but was not defined asREADS SQL DATA or MODIFIESSQL DATA.

Explanation: The program used to implementthe body of a routine is not allowed to read SQLdata.

User Response: Remove any SQL statementsthat read data then recompile the program.Investigate the level of SQL allowed as specifiedwhen defining the routine.

sqlcode: -579

sqlstate: 38004

sqlstate: 42985

SQL0580N The result-expressions of a CASEexpression cannot all be NULL.

Explanation: There is a CASE expression in thestatement that has all the result-expressions(expressions following THEN and ELSEkeywords) coded with the keyword NULL.


User Response: Change the CASE expression toinclude at least one result-expression that is otherthan the keyword NULL.


sqlcode: -580

sqlstate: 42625

SQL0581N The data types of theresult-expressions of a CASEexpression are not compatible.

Explanation: There is a CASE expression in thestatement that has result-expressions (expressionsfollowing THEN and ELSE keywords) that arenot compatible.

The data type of a CASE expression isdetermined using the ″Rules for Result DataTypes″ on the result-expressions. The data typesof the result-expressions may be incompatible forone of the following reasons:

v they are not all character data types

v they are not all numeric data types

v They are not all date data types

v They are not all time data types

v They are not all timestamp data types

v They are not all the same user-defined distinctdata types


User Response: Correct the result-expressionsso that they are compatible.

sqlcode: -581

sqlstate: 42804

SQL0582N A CASE expression in a VALUESclause, IN predicate, GROUP BYclause, or ORDER BY clausecannot include a quantifiedpredicate, an IN predicate using afullselect, or an EXISTS predicate.

Explanation: A search condition of a CASEexpression is:

v a quantified predicate (one using SOME, ANY,or ALL),

v an IN predicate using a fullselect or

v an EXISTS predicate

and the CASE expression is part of:

v a VALUES clause

v an IN predicate

v a GROUP BY clause or

v an ORDER BY clause.

Such CASE expressions are not supported. TheCASE expression may be part of a functionwritten in SQL.


User Response: Remove the use of thequantified predicate, IN predicate, or EXISTSpredicate from the CASE expression. If the CASEexpression is part of a function, the query mayneed to be written without the function thatcauses the error.

sqlcode: -582

sqlstate: 42625

SQL0583N The use of routine routine-name isinvalid because it is notdeterministic or has an externalaction.

Explanation: The routine (function or method)routine-name is defined as a non-deterministicroutine or a routine with an external action. Thistype of routine is not supported in the context inwhich it is used. The contexts in which these arenot valid are:

v as the first operand of a BETWEEN predicate

v in the expression prior to the first WHENkeyword in a simple-case-expression.

v in an expression of a GROUP BY clause

v in an expression of an ORDER BY clause(external action only)

v in a FILTER clause of a user-defined predicatespecification or an index extension definition


User Response: If the use of a non-deterministicor external action routine was not intended,substitute a routine without these characteristics.If the behavior associated with thenon-deterministic or external action routine is


intentional, use the alternate form of thestatements that make that intent explicit.

v Instead of the BETWEEN predicate, use thecorresponding statement using the equivalentcombination of comparison predicates (a>=band a<=c instead of a between b and c).

v Instead of a simple-when-clause, use thecorresponding searched-when-clause where theroutine would get specified in eachsearch-condition.

v Remove the non-deterministic or externalaction routine from the GROUP BY clause. Ifgrouping is desired on a column of the resultthat is based on a non-deterministic or externalaction routine use a nested table expression ora common table expression to first provide aresult table with the expression as a column ofthe result.

v Remove the external action routine from theORDER BY clause. If the column is part of theresult set of the query, change the expressionin the ORDER BY clause to the simple-integeror simple-column-name form of the sort key.

v Remove the non-deterministic or externalaction routine from the FILTER clause.

sqlcode: -583

sqlstate: 42845

SQL0584N Invalid use of NULL orDEFAULT.

Explanation: DEFAULT can only be used in aVALUES clause that is part of an INSERTstatement.

A VALUES clause that is not part of an INSERTstatement must have a value other than NULL inat least one row for each column.

If DEFAULT is used as a column-name in aWHERE or HAVING clause, it must becapitalized and enclosed in double quotes.

Federated system users: DEFAULT can not beused in a VALUES clause of an INSERTstatement where the object is a nickname.

User Response: Substitute a value other than

NULL or DEFAULT in the VALUES clause. IfDEFAULT is used as a column-name, capitalize itand enclose it in double quotes.

sqlcode: -584

sqlstate: 42608

SQL0585N The schema name schema-name cannot appear more than once in thefunction path.

Explanation: The function path includesschema-name more than once. The function pathcan only include one occurrence of each schemaname.


User Response: Remove duplicate occurrencesof schema-name from the function path.

sqlcode: -585

sqlstate: 42732

SQL0586N The total length of the CURRENTFUNCTION PATH special registercannot exceed 254 characters.

Explanation: The CURRENT FUNCTION PATHspecial register is defined as a VARCHAR(254).The content of the string includes each schemaname delimited with double quotes andseparated from the next schema name by acomma. The total length of the string of allschema names in the CURRENT FUNCTIONPATH cannot exceed 254 characters. The SETCURRENT FUNCTION PATH statement or theFUNCPATH option of the PREP or BINDcommand causing this message would exceedthis limit.

The statement or command cannot be processed.

User Response: Remove schema names toreduce the total length to fit the 254 charactermaximum length. If all the schema names arerequired, it may be necessary to consolidatesome user-defined functions so that less schemanames are required on the CURRENTFUNCTION PATH.

sqlcode: -586


sqlstate: 42907

SQL0590N Name name specified in contextcontext-tag is not unique.

Explanation: Name name is specified as aparameter, SQL variable, cursor, label, orcondition in a context defined by context-tag. Thename is not unique.

If context-tag is “BEGIN...END”, then the contextof the error is a dynamic SQL compoundstatement. Otherwise, the context of the error is atrigger or routine and context-tag is the triggername or routine name containing the compoundstatement.

v If name is a parameter name, then it must beunique within the parameter list and theEXPRESSION AS clause of a routine.

v If name is an SQL variable name, cursor nameor condition, then it must be unique within acompound statement .

v A label must be unique within a compoundstatement and different from the labels of thestatements in which it is nested.

User Response: Change the name so that it isunique.

sqlcode: -590

sqlstate: 42734

SQL0595W Isolation level requested-level hasbeen escalated to escalated-level.

Explanation: The isolation level specified is notsupported by DB2. It has been escalated to thenext higher level of isolation supported by DB2.

User Response: To avoid this warning, specifyan isolation level which is supported by DB2.DB2 supports isolation levels Repeatable Read(RR), Read Stability (RS), Cursor Stability (CS),and Uncommitted Read (UR).

sqlcode: +595

sqlstate: 01526

SQL0597N Unable to retrieve a DATALINKvalue. Reason code = reason-code.

Explanation: A DATALINK value could not beretrieved. The possible reason codes are asfollows:

01 The DB2 Data Links Manager does notauthorize the DB2 user to retrieve aDATALINK value embedded with awrite token for modifying theDATALINK value referenced file.


01 Contact the DB2 Data Links Manageradministrator to grant the write accessprivilege to this file.

sqlcode: -0597

sqlstate: 42511

SQL0598W Existing index name is used as theindex for the primary key or aunique key.

Explanation: An index was required for anALTER TABLE operation that defined a primarykey or a unique key, and the indicated indexmatches the required index.

When creating a primary key or unique keyindex, an index description matches if itidentifies the same set of columns (in any order)as the primary or unique key without regard toascending or descending specifications, and isspecified as unique.

The statement is processed successfully.


sqlcode: +598

sqlstate: 01550


SQL0599W Comparison functions are notcreated for a distinct type basedon a long string data type.

Explanation: Comparison functions are notcreated for a distinct type based on a long stringdata type (BLOB, CLOB, DBCLOB, LONGVARCHAR, or LONG VARGRAPHIC) since thecorresponding functions are not available forthese built-in data types.

This is a warning situation. The statement isprocessed successfully.


sqlcode: +599

sqlstate: 01596

SQL0600 - SQL0699

SQL0600N A routine routine-name could notbe generated because of aduplicate signature or because itwould override an existingroutine.

Explanation: During the CREATE or ALTERoperation, a system-generated cast function,observer method, mutator method, or constructorfunction could not be created because anotherfunction or method with the same name andsignature already exists in the schema, orbecause the method or function would overridean existing method.

User Response: Choose another name for theuser-defined type, attribute, or cast function thatcauses the conflict, or drop the function ormethod with the same name as the function ormethod that could not be generated.

sqlcode: -600

sqlstate: 42710

SQL0601N The name of the object to becreated is identical to the existingname name of type type.

Explanation: The CREATE or ALTER statementtried to create or add an object name when anobject of type type already exists with that nameon the application server or in the samestatement.

If type is FOREIGN KEY, PRIMARY KEY,UNIQUE, or CHECK CONSTRAINT, the name isthe constraint name specified in the CREATE or

ALTER TABLE statement or generated by thesystem.

Federated system users: some data sources donot provide the appropriate values for the nameand type message tokens. In these cases, nameand type will have the following format:“OBJECT:<data source> TABLE/VIEW”, and“UNKNOWN” indicating that the actual valuesat the specified data source are not known.

The statement cannot be processed. No newobject is created, and the existing object is notaltered or modified.

User Response: Either drop the existing objector choose another name for the new object.

Federated system users: if the statement is aCREATE FUNCTION MAPPING or a CREATETYPE MAPPING statement, the user can alsoconsider not supplying a type mapping nameand the system will automatically generate aunique name for this mapping.

sqlcode: -601

sqlstate: 42710

SQL0602N The CREATE INDEX or CREATEINDEX EXTENSION statementspecifies too many columns (16 isthe maximum).

Explanation: The number of columns for theindex that would be generated by the CREATEINDEX statement exceeds the maximum of 16columns for the database manager. If the index isdefined on a typed table, there is additional


overhead that reduces the maximum number ofspecified columns to 15.

For a CREATE INDEX EXTENSION statement,the GENERATE KEY function returns a numberof columns that exceeds the maximum of 16columns allowed in an index.

Federated system users: the limit for other datasources is different. That limit could have beenexceeded. This problem may be detected on thefederated server, or it may be detected on thedata source.


User Response: Change the index definition toconform to the column limit of 16. For aCREATE INDEX EXTENSION statement, specifya different GENERATE KEY function, or redefinethe function to return fewer columns.

Federated system users: change the indexdefinition to conform to the column limit for thedata source.

sqlcode: -602

sqlstate: 54008

SQL0603N A unique index cannot be createdbecause the table contains rowswhich are duplicates with respectto the values of the identifiedcolumns.

Explanation: The index defined in the CREATEINDEX statement could not be created as unique,because the specified table already contains rowsthat duplicate the values of the identifiedcolumns.

Federated system users: this situation may alsobe detected by the data source.

The statement cannot be processed. The specifiedindex is not created.

User Response: Examine the data to determineif the duplicate data is permitted. Alternatively,consider creating a non-UNIQUE index.

sqlcode: -603

sqlstate: 23515

SQL0604N The length, precision, or scaleattribute for column, distinct type,structured type, attribute ofstructured type, function, or typemapping data-item is not valid.

Explanation: There is an error in the data typespecification in a CREATE or ALTER statement,or a CAST specification. An invalid length,precision or scale attribute may have beenspecified, or it may be that the data type itself isincorrect or not permitted in this context. Thelocation of the error is given by data-item asfollows:

v for a CREATE or ALTER TABLE statement,data-item gives the name of the columncontaining the error or the data typecontaining an error. If the column data type isa structured type, then the explicit or implicitINLINE LENGTH value must be at least 292and cannot exceed 32677.

v for a CREATE FUNCTION statement, data-itemis a token that identifies the area of theproblem in the statement. For example,″PARAMETER 2″ or ″RETURNS″ or ″CASTFROM″. In some cases, it may also be the datatype containing the error.

v for a CREATE DISTINCT TYPE statement,data-item gives the name of the type beingdefined or the source data type containing theerror.

v for a CREATE or ALTER TYPE statement,data-item gives the type of the attributecontaining the error or the name of thestructured type having an incorrect inlinelength value. The inline length cannot besmaller than 292 and the size returned by theconstructor function for the structured type.

v for CAST( expression AS data-type ), data-itemis ″CAST″ or the data type containing theerror.

Federated system users: if the statement is aCREATE TYPE MAPPING statement, an attemptwas made to create a type mapping where a typeattribute for either the local data type or theremote data type is not valid. Possible reasonsinclude:


v The local length/precision is set to 0 or anegative value.

v The length/precision attribute is specified fordata types such as date/time/timestamp, float,or integer.

v The scale attribute is specified for data typessuch as character, date/time/timestamp, float,or integer.

v The FOR BIT DATA clause is specified for anon-character type.

v The remote precision is set to 0 for remotetypes other than Informix datetime.

v An invalid field qualifier is being used in atype mapping for an Informix datetime type.

v An ending value is lower than the startingvalue in a precision/scale range.


User Response: Correct the syntax and tryagain.

sqlcode: -604

sqlstate: 42611

SQL0605W The index was not createdbecause the index name alreadyexists with the requireddescription.

Explanation: A CREATE INDEX operationattempted to create a new index and theindicated index matches the required index.

For CREATE INDEX, two index descriptionsmatch if they identify the same columns in thesame order with the same ascending ordescending specifications, and are both specifiedas unique or the new index is specified asnon-unique. Also, two index descriptions matchif they identify the same columns in the sameorder with the same or reverse ascending ordescending specifications, and at least onedescription includes the ALLOW REVERSESCANS parameter.

The new index was not created.

User Response: No action is required unless theexisting index name is not a suitable index. For

example, the existing index name is not a suitableindex if it does not allow reverse scans, and therequired one does (or vice versa). In this case,the index name must be dropped before therequired index can be created.

sqlcode: +605

sqlstate: 01550

SQL0606N The COMMENT ON or LABELON statement failed because thespecified table or column is notowned by owner.

Explanation: An attempt was made to commentor label on a table or column which does notexist or is not owned by the owner specified inthe message text.

Processing of the SQL statement has ended.

User Response: Correct the statement. Tryagain.

sqlcode: -606

sqlstate: 42505

SQL0607N operation is not defined for systemobjects.

Explanation: The operation specified in the SQLstatement cannot be performed on systemobjects. One of the following was attempted:

v DROP or ALTER a system owned object suchas a system catalog table, built-in function orbuilt-in data type

v COMMENT ON a system owned built-infunction.

v INSERT or DELETE on a system catalog table.

v UPDATE directly on a system catalog table.Some columns of a subset of system catalogtables are updatable. For UPDATE operationon these catalog tables, updatable views inSYSSTAT schema should be used. For adescription of updatable catalog views(SYSSTAT views), see the SQL Reference.

v CREATE or DROP of an index on a systemtable

v CREATE of a trigger on a system table


v A non-updatable system table was identifiedin the FROM clause of a SELECT statementcontaining a FOR UPDATE clause. For a list ofupdatable system catalogs see the SQLReference.

v DROP or ALTER of a system table space.

v DROP or ALTER of a system nodegroup.

v REDISTRIBUTE of the IBMCATGROUP orIBMTEMPGROUP nodegroups.


User Response: Do not attempt to modify anysystem objects except for those columns of thesystem catalog tables which are updatablethrough updatable SYSSTAT views. See the SQLReference for more information.

sqlcode: -607

sqlstate: 42832

SQL0612N name is a duplicate name.

Explanation: A statement was issued with thesame name appearing more than once whereduplicates are not allowed. Where these namesappear varies depending on the type ofstatement.

v CREATE TABLE statements cannot have thesame column name defined for two columns.

v CREATE VIEW statements or common tableexpression definitions cannot have the samecolumn name in the column name list. If nocolumn name list is specified, then the columnnames of the columns in the select list of theview must be unique.

v ALTER TABLE statement cannot add a columnto a table using the name of a column thatalready exists or is the same as anothercolumn being added. Furthermore, a columnname can only be referenced in one ADD orALTER COLUMN clause in a single ALTERTABLE statement.

v CREATE INDEX cannot have a column namespecified more than once as part of the indexkey or the INCLUDE columns of the index.

v CREATE TRIGGER cannot have a columnname specified more than once in the list ofcolumns that cause an update trigger to beactivated.

v CREATE TABLE OF statements cannot havethe same name defined for the REF IS columnand any attribute of the structured type.

v CREATE TYPE statements cannot have thesame name defined for two attributes.Attribute names must be unique with the typeand all supertypes.

v ALTER TYPE statements cannot add anattribute to a structured type using the nameof an attribute that already exists in the typeor any of its subtypes or is the same asanother attribute being added. Also, the nameof the attribute may not be the same as theREF IS column in any table created from thestructured type. Furthermore, an attributename can only be referenced in one ADD orDROP ATTRIBUTE clause in a single ALTERTYPE statement.

v CREATE INDEX EXTENSION statementscannot have the same name defined for twoparameters.


User Response: Specify unique names asappropriate for the type of statement.

sqlcode: -612

sqlstate: 42711

SQL0613N The primary key or a unique keyidentified by name is too long orhas too many columns.

Explanation: The sum of the internal lengths ofcolumns in the PRIMARY KEY clause or aUNIQUE clause identified by name exceeds 1024or the number of columns exceeds the maximumof 16. Also, a primary key or a unique keycannot be defined using a LONG VARCHARcolumn. If the primary key or unique constraintis defined on a typed table, there is additionalindex overhead that reduces the maximumnumber of specified columns to 15 and limits thelength to 1020.


name is the constraint name, if specified, of theprimary key or unique constraint. If a constraintname was not specified, name is the first columnname specified in the primary key or uniqueconstraint clause followed by three periods.


User Response: Modify the primary key or aunique key definition by eliminating one or morekey columns to conform to the column limit of16 and the key length limit.

sqlcode: -613

sqlstate: 54008

SQL0614N The index or index extensionindex-name cannot be created oraltered because the combinedlength of the specified columns istoo long.

Explanation: The index could not be created oraltered because the sum of the key columninternal lengths would exceed 1024. Also, anindex cannot be created using a LONGVARCHAR, LONG VARGRAPHIC, or LOBcolumn. If the index is defined on a typed table,there is additional index overhead that reducesthe maximum length by 4 bytes. The index maybe altered by an ALTER TABLE statement thatalters the data type of one or more columns.

An index extension could not be created becausethe sum of the columns returned by theGENERATE KEY function would exceed 1024.

The statement cannot be processed. The specifiedindex or index extension was not created or thetable could not be altered.

User Response: To modify the index definitionor alter column, eliminate one or more keycolumns and reduce the key length to thepermitted maximum. For an index extensiondefinition, specify a different GENERATE KEYfunction, or redefine the function to reduce thelength of the returned row.

sqlcode: -614

sqlstate: 54008

SQL0615N The object object-name of typeobject-type cannot be droppedbecause it is currently in use bythe same application process.

Explanation: A DROP statement of an objectcannot be issued when it is in use.

The statement cannot be processed. The object isnot dropped.

User Response: Close any cursors that dependeither directly or indirectly on the objectobject-name and resubmit the statement.

sqlcode: -615

sqlstate: 55006

SQL0620N The CREATE TABLE statementfailed because user-id has noprivate, recoverable dbspaces withless than 255 tables.

Explanation: The dbspace name was notspecified in the CREATE TABLE statement, sothe database manager tried to find a privatedbspace owned by user-id. This message willappear under one of the following conditions:

1. There were no private dbspaces found in theDB2 for VM database for the user-id.

2. There were one or more private dbspacesfound for the user-id, but each contained 255tables.

3. The private dbspaces were located innonrecoverable storage pools. Only privatedbspaces that exist in recoverable storagepools will be available when the CREATETABLE statement does not specify thedbspace name.


User Response: Suggestions for the threeconditions above are:

1. Acquire a private dbspace in a recoverablestorage pool. You may require a databaseadministrator’s assistance.

2. Drop a table in a private dbspace residing ina recoverable storage pool to free up an entry,or take the action indicated in (1) above.


3. If you want to create the table in a dbspaceexisting in a non-recoverable storage pool,then specify the dbspace name on theCREATE TABLE command. Otherwise, takethe action indicated in (1) above.

Then rerun the CREATE TABLE statement.

If appropriate, acquire a private dbspace for theuser.

sqlcode: -620

sqlstate: 57022

SQL0622N The clause clause is invalid forthis database.

Explanation: The clause indicated is invalidbecause it is incompatible with the definedcharacteristics for this database.

Possible reasons:

v CCSID ASCII cannot be specified whenconnected to a database created using aUNICODE code page.

v CCSID UNICODE cannot be specified whenconnected to a database created using anon-UNICODE code page.

v FOR SBCS DATA can only be specified whenconnected to a database created using a singlebyte code page.

v FOR MIXED DATA can only be specifiedwhen connected to a database created using adouble byte or UNICODE code page.

v The IN database-name.table-space-name or INDATABASE database-name clause was specifiedusing a database name that does not match thename of the database to which the applicationis currently connected.


User Response: Change or remove the clauseand re-issue the SQL statement.

sqlcode: -622

sqlstate: 56031

SQL0623N A clustering index already existson table name.

Explanation: The CREATE INDEX statementwould create a second clustering index on thespecified table. A given table can have only oneclustering index.


User Response: Check to determine the identityand validity of the existing clustering index ontable name. Consider creating the index withoutthe CLUSTER attribute.

sqlcode: -623

sqlstate: 55012

SQL0624N Table name already has a key-typekey.

Explanation: A primary key or partitioning keycannot be defined in an ALTER TABLE statementbecause the indicated table already has a key ofthis type.


User Response: A table cannot have more thanone primary key or partitioning key.

sqlcode: -624

sqlstate: 42889

SQL0628N Multiple or conflicting keywordsinvolving the clause-type clause arepresent.

Explanation: There are several possible reasonswhy this condition might have been diagnosedfor the statement. Exactly which one happened isindicated by the value of clause-type. Thepossibilities to consider are:

v The keyword may not be specified in the samestatement as some other keyword.

v The keyword may be part of a sequence ofkeywords where the order in which they arespecified is not enforced. A keyword in such asequence may have been specified with thecontradicting keyword also specified.


v The keyword may appear more than once withdifferent associated values.

v The keyword may require the specifying ofother particular keywords in the samestatement which were not specified.

v When ALTERING an object, a keyword wasspecified that conflicts with an existingproperty of the object.

User Response: Check that the statementconforms to the syntax and rules defined for thestatement. Correct any invalid occurrences ofduplicate or conflicting keywords.

sqlcode: -628

sqlstate: 42613

SQL0629N SET NULL cannot be specifiedbecause FOREIGN KEY namecannot contain null values.

Explanation: The SET NULL option of theindicated FOREIGN KEY clause is not validbecause no column of the key allows null values.

name is the constraint name, if specified, in theFOREIGN KEY clause. If a constraint name wasnot specified, name is the first column namespecified in the column list of the FOREIGN KEYclause followed by three periods.


User Response: Change either a column of thekey to allow null values or change the deleterule.

sqlcode: -629

sqlstate: 42834

SQL0631N FOREIGN KEY name is too longor has too many columns.

Explanation: The sum of the column internallengths identified in the FOREIGN KEY clause ina CREATE TABLE statement exceeds 1024, or thenumber of columns identified exceeds 16. Also, aforeign key cannot be defined using a LONGVARCHAR column.

name is the constraint name, if specified, in theFOREIGN KEY clause. If a constraint name was

not specified, name is the first column namespecified in the column list of the FOREIGN KEYclause followed by three periods.


User Response: To modify the foreign keydefinition, eliminate one or more key columnsand conform to the 16 column limit and the keylength limit.

sqlcode: -631

sqlstate: 54008

SQL0632N FOREIGN KEY name is not validbecause the table cannot bedefined as a dependent of tabletable-name because of delete rulerestrictions (reason code =reason-code).

Explanation: A referential constraint cannot bedefined because the object table of the CREATETABLE or ALTER TABLE statement cannot bedefined as a dependent of table table-name forone of the following reason codes:

v (01) The relationship is self-referencing and aself-referencing relationship already exists withthe SET NULL delete rule.

v (02) The relationship forms a cycle of two ormore tables that cause the table to bedelete-connected to itself (all other delete rulesin the cycle would be CASCADE).

v (03) The relationship causes the table to bedelete-connected to the indicated table throughmultiple relationships and the delete rule ofthe existing relationship is SET NULL.

The delete rules of the existing relationshipscause an error, not the delete rule specified in theFOREIGN KEY clause of the CREATE TABLE orALTER TABLE statement.




User Response: If possible, eliminate theparticular FOREIGN KEY clause from theCREATE TABLE or ALTER TABLE statement.

sqlcode: -632

sqlstate: 42915

SQL0633N The delete rule of FOREIGN KEYname must be delete-rule (reasoncode = reason-code).

Explanation: The delete rule specified in aFOREIGN KEY clause of the CREATE TABLE orALTER TABLE statement is not valid. Theindicated delete rule is required for one of thefollowing reason codes:

v (01) The referential constraint isself-referencing and an existing self-referencingconstraint has the indicated delete rule (NOACTION, RESTRICT or CASCADE).

v (02) The referential constraint isself-referencing and the table is dependent in arelationship with a delete rule of CASCADE.

v (03) The relationship would cause the table tobe delete-connected to the same table throughmultiple relationships and such relationshipsmust have the same delete rule (NO ACTION,RESTRICT or CASCADE).



User Response: If possible, change the deleterule.

sqlcode: -633

sqlstate: 42915

SQL0634N The delete rule of FOREIGN KEYname must not be CASCADE(reason-code = reason-code).

Explanation: The CASCADE delete rulespecified in the FOREIGN KEY clause of the

CREATE TABLE or ALTER TABLE statement isnot valid for one of the following reason codes:

v (01) A self-referencing constraint exists with adelete rule of SET NULL, NO ACTION orRESTRICT.

v (02) The relationship would form a cycle thatwould cause a table to be delete-connected toitself. One of the existing delete rules in thecycle is not CASCADE, so this relationshipmay be definable if the delete rule is notCASCADE.

v (03) The relationship would cause anothertable to be delete-connected to the same tablethrough multiple paths with different deleterules or with delete rule equal to SET NULL.

name is the constraint name, if specified, in theFOREIGN KEY clause. If a constraint namewas not specified, name is the first columnname specified in the column list of theFOREIGN KEY clause followed by threeperiods.


User Response: If possible, change the deleterule.

sqlcode: -634

sqlstate: 42915

SQL0637N Keyword keyword is not valid asused.

Explanation: The SQL statement contains aduplicate or conflicting specification for a clausewith the indicated keyword. For example:

v DEFAULT, UNIQUE, and PRIMARY can onlybe specified once in a column definition

v UNIQUE and PRIMARY cannot both bespecified for the same column definition

v PRIMARY can only be specified once in aCREATE TABLE statement

v the attribute-string specified for the PREPAREstatement cannot specify an option more thanonce, or there are conflicting options


User Response: Correct the statement to


specification of duplicate or conflicting clauses.

sqlcode: -637

sqlstate: 42614

SQL0638N Table name cannot be createdbecause no column definitionswere specified.

Explanation: The CREATE TABLE statementdoes not contain any column definitions.


User Response: Add one or more columndefinitions to the statement.

sqlcode: -638

sqlstate: 42601

SQL0644N Invalid value specified forkeyword keyword in statementstatement-type.

Explanation: The keyword keyword is followedby an invalid value as allowed by the descriptionof statement-type. For numeric values, the valuemay be outside a defined range. For other types,the value is not in the defined set of valid values.

User Response: Determine from referencedocumentation for the statement-type what arevalid values and make the appropriate change.

sqlcode: -644

sqlstate: 42615

SQL0647N Bufferpool bufferpool-name iscurrently not active.

Explanation: The bufferpool bufferpool-name isnot active in the current database environment.An attempt was made to find another bufferpoolwith the same page size but there are no suchbufferpools active in the current databaseenvironment. The bufferpool bufferpool-name wasrecently defined but has not yet been activated.


User Response: The database must be stopped

and started again to activate the requiredbufferpool.

sqlcode: -647

sqlstate: 57003

SQL0648N The foreign key cannot bedefined because it will cause tableowner1.table-name1 to bedelete-connected to tableowner2.table-name2 throughmultiple paths. Reason Code =reason-code.

Explanation: The foreign key cannot be definedbecause one of the following reason codes =reason-code:

01 The relationship will cause tableowner1.table-name1 to bedelete-connected to tableowner2.table-name2 through multiplepaths with the same delete rule of SETNULL.

02 The relationship will cause tableowner1.table-name1 to bedelete-connected to tableowner2.table-name2 through multiplepaths with different delete rules.


User Response: Correct the statement. Tryagain.

sqlcode: -648

sqlstate: 42915

SQL0658N The object name cannot beexplicitly dropped or altered.

Explanation: The identifier name identifies oneof the following:

v a cast function or comparison function thatcannot be dropped using the DROP statementbecause it was created by the system for usewith a distinct type

v a method that cannot be dropped using theALTER TYPE method because it was createdby the system for use with a structured type


v a package that cannot be dropped using theDROP statement because it was created by thesystem for use with a SQL procedure. Theconsistency token (or unique_id) is given inhexadecimal as part of the package name inthe form of “pkgschema.pkgname0Xcontoken”.

v a routine that cannot be altered because it isdefined with LANGUAGE SQL


User Response:

v The function name can only be dropped bydropping the distinct type or structured typethat caused the function to be defined. Thedistinct type name corresponds to either thename of the function or the type of theparameters to the function.

v The method name can only be dropped bydropping the structured type that caused themethod to be defined. The method namecorresponds to the name of an attribute for thestructured type.

v The package name can only be dropped bydropping the SQL procedure that caused thepackage to be defined. The specific name ofthe SQL procedure can be found by retrievingthe DSCHEMA and DNAME from theSYSIBM.SYSDEPENDENCIES catalog tablewhere the BSCHEMA, BNAME, andBUNIQUE_ID match the relevant parts ofname, BTYPE is ’K’ and DTYPE is ’L’. Theconsistency token (or unique_id) is needed todistinguish between package versions thatshare the same schema and name.

v The routine name can only be changed bydropping the routine and then redefining it.

sqlcode: -658

sqlstate: 42917

SQL0659N Maximum size of a table objecthas been exceeded.

Explanation: One or more of the objects whichmake up a table has reached its maximum size.The storage objects that make up a table are:

v Data: This is where basic column data is stored

v Index: This is where all indexes on the tableare stored

v Long Data: This is where LONG VARCHARand LONG VARGRAPHIC column data isstored

v Lob/Lob Allocation: This is where BLOB,CLOB, and DBCLOB column data and controlinformation are stored

Once a storage object has grown to its maximumsize, it cannot be extended further.

User Response: To make existing space withinthe object available to store new data, thefollowing actions may be taken:

v Reorganize the table

v Delete unnecessary rows from the table

v Drop an index from the table

v Update rows to reduce the amount of data (areorg may be required after this action inorder to reclaim unused storage)

sqlcode: -659

sqlstate: 54032

SQL0667N The FOREIGN KEY name cannotbe created because the tablecontains rows with foreign keyvalues that cannot be found in theparent key of the parent table.

Explanation: The definition of the indicatedforeign key failed because the table being alteredcontains at least one row where the foreign keydoes not match the parent key value in theparent table.

name is the constraint name, if specified. If aconstraint name was not specified, name is thefirst column name specified in the column list ofthe FOREIGN KEY clause followed by threeperiods.

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

User Response: Remove the erroneous tablerows and define the foreign key.


sqlcode: -667

sqlstate: 23520

SQL0668N Operation not allowed for reasoncode reason-code on tabletable-name.

Explanation: Access to table table-name isrestricted. The cause is based on the followingreason codes reason-code:

1 The table is in Check Pending state. Theintegrity of the table is not enforced andthe content of the table may be invalid.An operation on a parent table or anunderlying table that is not in a checkpending state may also receive this errorif a dependent table is in a checkpending state.

2 The table is in No Data Movement state.When in this state, operations that causedata movement are disallowed. Datamovement operations includeREDISTRIBUTE, update of partitioningkey, update of multi-dimensionalclustering key and REORG TABLE.

3 The table is in Load Pending state. Aprevious LOAD attempt on this tableresulted in failure. No access to the tableis allowed until the LOAD operation isrestarted or terminated.

4 The table is Read Only state. This statecan occur during on-line LOADprocessing (LOAD INSERT with theREAD ACCESS option), or after anon-line LOAD operation, but before allconstraints have been validated in thenewly appended portion of the tableusing the SET INTEGRITY statement.No update activity is allowed on thistable.

5 The table is in Load In Progress state.The LOAD utility is currently operatingon this table, no access is allowed untilthe LOAD is finished.

User Response:

1 Execute the SET INTEGRITY statement

with the IMMEDIATE CHECKEDoption on table table-name to bring thetable out of the Check Pending state.

2 Execute REFRESH TABLE statement onthe dependent immediate materializedquery tables and staging tables of tabletable-name. The contents of thesedependent immediate materializedquery tables and staging tables can beincrementally maintained from theappended data of table-name throughprevious LOAD INSERT operations.

3 Restart or terminate the previouslyfailed LOAD operation on this table byissuing LOAD with the RESTART orTERMINATE option respectively.

4 Issue the LOAD QUERY command tocheck whether the table is in the processof being loaded. If yes, wait until theLOAD utility has completed, or ifnecessary, restart or terminatepreviously failed LOAD operation. IfLOAD is currently not in progress, issuethe SET INTEGRITY command with theIMMEDIATE CHECKED option, tovalidate constraints in the newly loadedportion of the table.

5 Wait until the current LOAD operationhas finished. You can use the LOADQUERY command to monitor theprogress of load.

sqlcode: -668

sqlstate: 57016

SQL0669N A system required index cannotbe dropped explicitly.

Explanation: The DROP INDEX statementattempted to drop an index required to:

v enforce the primary key constraint on a table

v enforce a unique constraint on a table

v enforce the uniqueness of the object identifier(OID) column of a typed table hierarchy

v maintain a replicated materialized query table.


A system required index cannot be droppedusing the DROP INDEX statement.

The statement cannot be processed. The specifiedindex is not dropped.

User Response: If you do not want to keep theprimary or unique constraint, use the DROPPRIMARY KEY clause or the DROPCONSTRAINT clause of the ALTER TABLEstatement to remove the primary key or uniqueconstraint. If the index was created only forenforcing the primary or unique key, then theindex will be dropped. If not, the DROP INDEXstatement could then be processed.

The index for an OID column can only bedropped by dropping the table.

The index required to maintain a replicatedmaterialized query table can only be dropped byfirst dropping the replicated materialized querytable.

sqlcode: -669

sqlstate: 42917

SQL0670N The row length of the tableexceeded a limit of length bytes.(Table space tablespace-name.)

Explanation: The row length of a table in thedatabase manager cannot exceed:

v 4005 bytes in a table space with a 4K page size

v 8101 bytes in a table space with an 8K pagesize



The length is calculated by adding the internallengths of the columns. Details of internalcolumn lengths can be found under CREATETABLE in the SQL Reference.

One of the following conditions can occur:

v The row length for the table defined in theCREATE TABLE or ALTER TABLE statementexceeds the limit for the page size of the table

space. The regular table space nametablespace-name identifies the table space fromwhich the page size was used to determine thelimit on the row length.

v The row length for the table defined in theDECLARE GLOBAL TEMPORARY TABLEstatement exceeds the limit for the page size ofthe table space. The user temporary tablespace name tablespace-name identifies the tablespace from which the page size was used todetermine the limit on the row length.


User Response: Depending on the cause, doone of the following.

v In the case of CREATE TABLE, ALTER TABLE,or DECLARE GLOBAL TEMPORARY TABLE,specify a table space with a larger pagesize, ifpossible.

v Otherwise, reduce the row length byeliminating one or more columns or reducingthe lengths of one or more columns.

sqlcode: -670

sqlstate: 54010

SQL0672N Operation DROP not allowed ontable table-name.

Explanation: The DROP operation failed for oneof the following reasons:

v The table being dropped has the RESTRICTON DROP attribute.

v The table space or nodegroup being droppedcontains the specified table, which has theRESTRICT ON DROP attribute.

The DROP statement cannot be executed.

User Response: If the problem occurred duringa DROP TABLE statement, issue an ALTERTABLE statement using the DROP RESTRICTON DROP clause. Then re-issue the DROPTABLE statement.

If the problem occurred during a DROPTABLESPACE or DROP NODEGROUPstatement, ensure that there are no other tables


within the table space or nodegroup with theRESTRICT ON DROP attribute. The followingselect statement can help identify the tables:

SELECT TB.TABNAME, TB.TABSCHEMA,TS.TBSPACE, TS.NGNAME

FROM SYSCAT.TABLES TB,SYSCAT.TABLESPACES TS

WHERE TYPE = ’T’AND DROPRULE = ’R’AND TB.TBSPACEID = TS.TBSPACEIDORDER BY TS.NGNAME, TS.TBSPACE,

TB.TABSCHEMA, TB.TABNAME;

After identifying tables with the RESTRICT ONDROP attribute, issue an ALTER TABLEstatement using the DROP RESTRICT ON DROPclause for each table with the RESTRICT ONDROP attribute. Then re-issue the DROPTABLESPACE or DROP NODEGROUPstatement.

sqlcode: -672

sqlstate: 55035

SQL0673N A primary or unique key indexcannot be created because thetable contains rows which areduplicates with respect to thevalues of the identified primaryor unique key columns ofconstraint name.

Explanation: The primary or unique keydefinition of the constraint identified by namefailed because the table being altered alreadycontains rows with duplicate values for thePRIMARY KEY or UNIQUE clause columns.

name is the constraint name, if specified. If aconstraint name was not specified, name is thefirst column name specified in the primary keyor unique constraint clause followed by threeperiods.

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

User Response: Remove the erroneous rowsfrom the table before attempting to define theprimary or unique key.

sqlcode: -673

sqlstate: 23515

SQL0680N Too many columns are specifiedfor a table, view, or table function.

Explanation: The maximum number of columnspermitted for each table is based on the page sizeof the table space and the data types of thecolumns. The limits for tables are:

v 4K page size allows a maximum of 500columns

v 8K, 16K, and 32K page sizes allow a maximumof 1012 columns.

The actual number of columns for a table isdetermined by the following formula: TotalColumns * 8 + Number of LOB Columns * 12 +Number of Datalink Columns * 28 <= row sizelimits for page size.

The maximum number of columns permitted foreach view is 5000.

The maximum number of columns permitted fora table function is 255.

Federated system users: other data sources mayhave a different maximum column limit. Thislimit has been exceeded.


User Response: Ensure that the number of tableor view columns does not exceed the limit. Ifcreating a table where a larger page size wouldallow the number of columns, specify a tablespace with the larger page size. Create separatetables or views, as required, to hold additionalinformation beyond the limit.

Federated system users: limit the number of tablecolumns to the maximum supported by the datasource. Create separate tables or views, asrequired, to hold additional information beyondthe maximum number of columns supported bythe data source.

sqlcode: -680


sqlstate: 54011

SQL0683N The specification for column,attribute, user-defined type orfunction data-item containsincompatible clauses.

Explanation: There is an error in a data itemspecification in a CREATE or ALTER.Incompatible specifications are present, such as:″INTEGER and FOR BIT DATA″. The location ofthe error is given by data-item as follows:

v for a CREATE or ALTER TABLE statement,data-item gives the name of the columncontaining the error.

v for a CREATE FUNCTION statement, data-itemis a token that identifies the area of theproblem in the statement. For example,″PARAMETER 3″ or ″RETURNS″ or ″CASTFROM″.

v for a CREATE DISTINCT TYPE statement,data-item gives the name of the type beingdefined.

v for a CREATE or ALTER TYPE statement,data-item identifies the clause containing theerror or gives the name of the attributecontaining the error.


User Response: Remove the incompatibility andtry the statement again.

sqlcode: -683

sqlstate: 42842

SQL0696N The definition of triggertrigger-name includes an invaliduse of correlation name ortransition table name name.Reason code=reason-code.

Explanation: The trigger definition included aninvalid use of name. The value of reason-code

indicates the specific problem as follows.

1 NEW correlation name andNEW_TABLE name are not allowed in aDELETE trigger.

2 OLD correlation name and OLD_TABLEname are not allowed in an INSERTtrigger.

3 OLD_TABLE name and NEW_TABLEname are not allowed in a BEFOREtrigger.


User Response: Remove the invalid correlationname or transition table name along with thepreceding keyword.

sqlcode: -696

sqlstate: 42898

SQL0697N OLD or NEW correlation namesare not allowed in a triggerdefined with the FOR EACHSTATEMENT clause.

Explanation: The trigger, as defined, includes aREFERENCING clause with OLD or NEWcorrelation names specified (or both) and theFOR EACH STATEMENT clause. These cannotbe specified together.


User Response: Remove any OLD or NEWcorrelation names from the REFERENCINGclause or replace FOR EACH STATEMENT withFOR EACH ROW.

sqlcode: -697

sqlstate: 42899

SQL0700 - SQL0799


SQL0707N The name name cannot be usedbecause the specified identifier isreserved for system use.

Explanation: The following lists reservednames:

v a table space name cannot start with ’SYS’

v a database partition group name cannot startwith ’SYS’ or ’IBM’

v a savepoint name cannot start with ’SYS’

User Response: Select a name that is notreserved.

sqlcode: -707

sqlstate: 42939

SQL0713N The replacement value forspecial-register is invalid.

Explanation: Either the value specified in theSET <special-register> statement is not a validvalue of the indicated special register, or thevalue specified is NULL as a result of anindicator variable.


User Response: Correct the replacement valueand/or any indicator variables. See the SQLReference for an explanation of the valid values ofeach special register.

sqlcode: -713

sqlstate: 42815

SQL0719N Bind error for user auth-id.Package package-name alreadyexists.

Explanation: An attempt is made, using theACTION ADD option of PRECOMPILE or BINDto add a package that already exists. Thecombination of ’pkgschema.pgkname.pkgversion’must be unique in the SYSCAT.PACKAGEScatalog view.

auth-id Authorization ID of the invoker of theBIND or PREP

package-nameName of the package in the form’pkgschema.pkgname.pkgversion’. If thepackage version is the empty string,then ’.pkgversion’ is omitted from thename.

The package is not created.

User Response: Possible ways to ensure thatthere is no attempt to add a duplicate entryinclude:

v Check the SYSCAT.PACKAGES catalog viewfor names of existing application packages.Re-invoke the PRECOMPILE or BIND with a’pkgschema.pkgname.pkgversion’ that is not inuse.

v Reissue the PREP or BIND statement withoutthe ACTION ADD option. This will replace theexisting package.

sqlcode: -719

sqlstate: 42710

SQL0720N Attempting to replace packagepkgschema.pkgname WITHVERSION pkgversion, where thisversion already exists.

Explanation: An attempt is made to create aversion of a package that already exists using theACTION REPLACE REPLVER option. Theversion specified in the REPLVER keyword isdifferent from the version specified in theVERSION precompile option. The versionspecified in the VERSION precompile optionalready exists in the catalog. The combination of’pkgschema.pkgname.version’ must be unique inthe SYSCAT.PACKAGES catalog view.

A common mistake is that the user may believethat the version that is being created is the onespecified in the REPLVER keyword. This is notthe case. The version specified in the REPLVERkeyword is the name of the version beingreplaced. The version that will be created is theversion that is given to the program in theVERSION option.



User Response: Ensure that the version beingcreated does not already exist.

There are two approaches to solve this problem:

v Precompile the program again with a newversion name and reissue the original PREP orBIND command.

v The other approach is to reissue the PREP orBIND command specifying the ACTIONREPLACE clause without the REPLVERspecification. In this case, the REPLACE willreplace the version that matches the versionspecified in the VERSION option.

sqlcode: -720

sqlstate: 42710

SQL0721N Package pkgschema.pkgname withconsistency token = 0Xcontokencannot be created since it is notunique.

Explanation: An attempt is made to add orreplace a package with a consistency token thatis not unique for that package. The combinationof ’pkgschema.pkgname.contoken’ already exists.This is most likely caused by using the LEVELoption of the PRECOMPILE to specify theconsistency token.


User Response: Check the SYSCAT.PACKAGEScatalog table for names of existing applicationpackages with the indicated consistency token.Reissue the PREP or BIND command such thatthe ’pkgschema.pkgname.contoken’ is uniquewithin the catalog. The following SQL statementcan be used to query the catalog:

SELECT PKGSCHEMA,PKGNAMEFROM SYSCAT.PACKAGESWHERE HEX(UNIQUE_ID) = ’contoken’;

If the LEVEL option on the precompile was used,reissuing the precompile and specifying adifferent LEVEL value would change theconsistency token. It is recommended that theLEVEL option is not used; not specifying the

LEVEL option of the precompile would ensurethat the consistency token is a current timestampvalue.

SQL0722N Error performing bind-command foruser auth-id. Package package-namedoes not exist.

Explanation: Bind or rebind was issued againsta package that does not exist. The error wouldoccur if ACTION REPLACE was specified andthe REPLVER option specified a version thatdoesn’t exist.

bind-commandType of bind command (BIND |REBIND) issued. Note that the value’BIND’ will be used for a precompile aswell.

auth-idAuthorization ID that issued the bind orrebind.

package-nameName of the package in the form’pkgschema.pkgname.pkgversion’. If thepackage version is the empty string,then ’.pkgversion’ is omitted from thename.

The package was not bound or rebound.

Explanation: Check the SYSCAT.PACKAGEScatalog view for the correct’pkgschema.pkgname.pkgversion’ to specify inthe REPLVER option.

sqlcode: -722

sqlstate: 42704

SQL0723N An error occurred in a triggeredSQL statement in triggertrigger-name. Information returnedfor the error includes SQLCODEsqlcode, SQLSTATE sqlstate andmessage tokens token-list

Explanation: An SQL statement in the triggertrigger-name has failed during execution of thetrigger. The sqlcode, sqlstate and message tokenlist (each token is separated by the vertical bar


character) are provided. The message tokens maybe truncated. See the corresponding message forthe sqlcode for further explanation of the error.

The trigger and the original SQL statement thatcaused the trigger to execute cannot beprocessed.

User Response: Check the message associatedwith the SQLCODE of the SQL statement thatfailed. Follow the action suggested by thatmessage.

sqlcode: -723

sqlstate: 09000

SQL0724N The activation of object-name oftype object-type would exceed themaximum level of indirect SQLcascading.

Explanation: Cascading of indirect SQL occurswhen a trigger activates another trigger (possiblythrough referential constraint delete rules) or aroutine, containing SQL, invokes another routine.The depth of this cascading is limited to 16.

Note that recursive situations where a triggerincludes a triggered SQL statement that directlyor indirectly causes the same trigger to beactivated, or where a routine directly orindirectly invokes itself, is a form of cascadingthat is very likely to cause this error if there areno conditions to prevent cascading fromexceeding the limit.

The object-type is one of TRIGGER, FUNCTION,METHOD, or PROCEDURE.

The object-name specified is one of the objects thatwould have been activated at the seventeenthlevel of cascading.

User Response: Start with the objects that areactivated or invoked by the statement thatreceived this error. If any of these objects arerecursive, ensure that there is some conditionthat prevents the object from being activated orinvoked more than the limit allows. If this is notthe cause of the problem, follow the chain ofobjects that are activated or invoked to determinethe chain that exceeds the cascading limit.

sqlcode: -724

sqlstate: 54038

SQL0727N An error occurred during implicitsystem action type action-type.Information returned for the errorincludes SQLCODE sqlcode,SQLSTATE sqlstate and messagetokens token-list.

Explanation: The processing of a statement orcommand has caused the database manager toimplicitly perform additional processing. Duringthis processing an error was encountered. Theaction attempted is shown by the action-type:

1 implicit rebind of a package

2 implicit prepare of a cached dynamicSQL statement

3 implicit regeneration of a view

4 This return code is reserved for use byDB2.

5 incremental bind of a static SQLstatement, not bound during packagebind time

The sqlcode, sqlstate and message token list(each token is separated by the vertical barcharacter) are provided. The message tokens maybe truncated. See the corresponding message forthe sqlcode for further explanation of the error.

The original SQL statement or command thatcaused the action-type cannot be processed andthe implicit system action was not successful.

Federated system users: You may have receivedthis message because you dynamically preparedan SQL statement in a pass-through session andthen tried to execute the statement after thesession was closed.

User Response: Check the message associatedwith the SQLCODE of the SQL statement thatfailed. Follow the action suggested by thatmessage.

For an invalid package, the REBIND command


can be used to recreate the error or to explicitlyvalidate the package once the cause of the errorhas been resolved.

For a failure while regenerating a view, the nameof the view that failed is recorded in theadministration notification log. The failing viewcan be dropped or a change made to thestatement or command that caused the viewregeneration.

Federated system users: If the statement thatfailed was dynamically prepared in apass-through session, open another pass-throughsession, write and prepare the statement again,and execute it while the session is still open.

sqlcode: -727

sqlstate: 56098

SQL0740N Routine routine-name (specificname specific-name) is defined withthe MODIFIES SQL DATAoption, which is not valid in thecontext where the routine isinvoked.

Explanation: The routine routine-name (specificname specific-name) is defined with MODIFIESSQL DATA and is therefore not allowed in:

v a BEFORE trigger

v a correlated subquery

v a search-condition (such as a WHERE clauseor check constraint)

User Response: Ensure that routine resolutionresolved to the desired routine. Remove theroutine from the failing statement or redefine theroutine with an SQL access indicator other thanMODIFIES SQL DATA.

sqlcode: -740

sqlstate: 51034

SQL0746N Routine routine-name (specificname specific-name) violated nestedSQL statement rules whenattempting to perform operationoperation on table table-name.

Explanation: The routine routine-name (specificname specific-name) attempted to perform theoperation operation on table table-name. Thisoperation conflicts with other uses of the table byeither the application, or a routine invokeddirectly or indirectly from that application.

If the operation is “READ”, then the tabletable-name is currently being written to by eitherthe application or another routine.

If the operation is “MODIFY”, then the tabletable-name is already being read from or writtento by the application or another routine.

If table-name references an explain table and thestatement that receives this error message iseither a PREPARE statement or an EXECUTEIMMEDIATE statement, then a conflict occurredwhen inserting explain information into theexplain table.

User Response: The operation may besuccessful if retried. Redesign either theapplication or the routine to avoid the conflict.

If the conflict occurred when inserting explaininformation for a dynamic statement, thendisable explain for dynamic statements and trythe PREPARE statement or EXECUTEIMMEDIATE statement again.

sqlcode: -746

sqlstate: 57053

SQL0750N The source table cannot berenamed because it is referencedin a view, materialized querytable, trigger, SQL function, SQLmethod, check constraint, orreferential constraint.

Explanation: The source table in a RENAMEstatement cannot be renamed for one or more ofthe following reasons.


v The table is referenced in one or more existingviews.

v The table is referenced in one or more existingmaterialized query tables.

v The table is referenced in one or more existingtriggers. This includes triggers on the table orreferences in triggered SQL statements.

v The table is referenced in one or more existingSQL functions or SQL methods.

v The table has check constraints defined.

v The table is involved in one or more referentialconstraints as a parent or dependent table.


User Response: Drop the views, materializedquery table, triggers, SQL functions, SQLmethods, check constraints, or referentialconstraints on the table before issuing theRENAME statement. For views or materializedquery tables dependent on the table, querySYSCAT.VIEWDEP where the table matchesBSCHEMA and BNAME columns. For triggersdependent on the table, query SYSCAT.TRIGDEPwhere the table matches BSCHEMA and BNAMEcolumns. For SQL functions or SQL methods,query SYSCAT.FUNCDEP where the tablematches BSCHEMA and BNAME columns. Forcheck constraints on the table, querySYSCAT.CHECKS where the table matchesTABSCHEMA and TABBNAME columns. Forreferential constraints dependent on the table,query SYSCAT.REFERENCES where the tablematches TABSCHEMA and TABNAME columnsor REFTABSCHEMA and REFTABNAMEcolumns.

sqlcode: -750

sqlstate: 42986

SQL0751N Routine routine-name (specificname specific-name) attempted toexecute a statement that is notallowed.

Explanation: The program used to implementthe body of a routine is not allowed to issue anyconnection statements. If the routine is a functionor method, COMMIT and ROLLBACK (without

the SAVEPOINT option) are also not allowed.

User Response: Remove the statement that isnot allowed, then recompile the program.

sqlcode: -751

sqlstate: 38003

sqlstate: 42985

SQL0752N Connecting to a database is notpermitted within a logical unit ofwork when the CONNECT type 1connection setting is in use.

Explanation: An attempt was made to connectto either another database or the same databasebefore issuing a COMMIT or ROLLBACKstatement. The request cannot be processedwithin a CONNECT type 1 environment.

User Response:

v Submit a COMMIT or ROLLBACK statementbefore requesting a connection to anotherdatabase.

v If multiple databases need to be updatedwithin a unit of work, change the connectionsettings to SYNCPOINT TWOPHASE andCONNECT 2 by re-precompiling or by issuingthe SET CLIENT API from within theapplication.

sqlcode: -752

sqlstate: 0A001

SQL0773N Case not found for CASEstatement.

Explanation: A CASE statement without anELSE clause was found in the routine body of anSQL routine. None of the conditions specified inthe CASE statement were met.

User Response: Change the CASE statement tohandle all conditions that can occur.

sqlcode: -773

sqlstate: 20000


SQL0774N The statement cannot be executedwithin an ATOMIC compoundSQL statement.

Explanation: A COMMIT or ROLLBACKstatement was encountered within the context ofan ATOMIC compound SQL statement. Thesestatements are not allowed in this context.

User Response: Remove the COMMIT orROLLBACK statement or change the context sothat it is not an ATOMIC compound statement.

sqlcode: -774

sqlstate: 2D522

SQL0776N Use of cursor cursor-name is notvalid.

Explanation: Cursor cursor-name is specified asthe cursor name on a FOR statement in an SQLprocedure. The cursor cannot be specified on aCLOSE, FETCH, or OPEN statement within theFOR statement.

User Response: Remove the CLOSE, FETCH, orOPEN statement.

sqlcode: -776

sqlstate: 428D4

SQL0777N Nested compound statements arenot allowed.

Explanation: Atomic compound statements inthe routine body of an SQL procedure cannot benested.

User Response: Ensure that the SQL proceduredoes not contain nested atomic compoundstatements.

sqlcode: -777

sqlstate: 42919

SQL0778N End label label is not the same asthe begin label.

Explanation: Label label specified at the end of aFOR, IF, LOOP, REPEAT, WHILE or compoundstatement is not the same as the label at the

beginning of the statement. You cannot specifyan end label if a begin label is not specified.

User Response: Ensure that the end label is thesame as the begin label for FOR, IF, LOOP,REPEAT, WHILE, and compound statements.

sqlcode: -778

sqlstate: 428D5

SQL0779N Label label specified on a GOTO,ITERATE, or LEAVE statement isnot valid.

Explanation: Label label is specified on a GOTO,ITERATE or LEAVE statement. The label is notdefined or is not a valid label for the statement.

The label on an ITERATE statement must be thelabel for a FOR, LOOP, REPEAT, or WHILEstatement.

The label on a LEAVE statement must be thelabel for a FOR, LOOP, REPEAT, WHILE, orcompound statement.

The label on a GOTO must be defined within ascope that the GOTO statement can reach.

v If the GOTO statement is defined in a FORstatement, label must be defined inside thesame FOR statement, excluding a nested FORstatement or nested compound statement.

v If the GOTO statement is defined in acompound statement, label must be definedinside the same compound statement,excluding a nested FOR statement or nestedcompound statement.

v If the GOTO statement is defined in a handler,label must be defined in the same handler,following the other scope rules.

v If the GOTO statement is defined outside of ahandler, label must not be defined within ahandler.

User Response: Specify a valid label on theGOTO, ITERATE, or LEAVE statement.

sqlcode: -779

sqlstate: 42736


SQL0780N UNDO is specified for a handlerwhen ATOMIC is not specifiedfor the compound statement.

Explanation: UNDO is specified for a handlerin a compound statement in an SQL procedure.UNDO cannot be specified unless the compoundstatement is ATOMIC.

User Response: Either specify that thecompound statement is ATOMIC or specify EXITor CONTINUE on the handler.

sqlcode: -780

sqlstate: 428D6

SQL0781N Condition condition specified in ahandler is not defined.

Explanation: Condition condition specified in ahandler in an SQL procedure is not defined.

User Response: Define the condition using theDECLARE CONDITION statement or remove thecondition from the handler.

sqlcode: -781

sqlstate: 42737

SQL0782N A condition or SQLSTATE valuespecified in a handler is not valid.

Explanation: A condition or SQLSTATE valuespecified in a handler in an SQL is not valid forone of the following reasons:

v The condition or SQLSTATE value has alreadybeen specified by another handler in the samescope.

v The condition or SQLSTATE value wasspecified in the same handler asSQLEXCEPTION, SQLWARNING, or NOTFOUND.

User Response: Remove the condition orSQLSTATE value from the handler.

sqlcode: -782

sqlstate: 428D7

SQL0783N A duplicate column name orunnamed column was specified ina DECLARE CURSOR statementof a FOR statement.

Explanation: The select list in the FORstatement must contain unique column names.The select list specified contains either duplicatecolumn names or unnamed expressions.

User Response: Specify unique column namesin the select list specified in the FOR statement.

sqlcode: -783

sqlstate: 42738

SQL0785N The declaration or use of theSQLSTATE or SQLCODE variableis not valid.

Explanation: SQLSTATE or SQLCODE was usedas a variable in the routine body of an SQLroutine, but is not valid for one of the followingreasons:

v SQLSTATE is not declared as CHAR(5)

v SQLCODE is not declared as INTEGER

v The variable is assigned the NULL value.


User Response: Declare the SQLSTATE variableas CHAR(5) and the SQLCODE variable asINTEGER. Set the variable to a valid value.

sqlcode: -785

sqlstate: 428D8

SQL0787N RESIGNAL statement not withina handler.

Explanation: The RESIGNAL statement canonly be used inside condition handlers.

User Response: Remove the RESIGNALstatement or use a SIGNAL statement instead.

sqlcode: -787

sqlstate: 0K000


SQL0789N The data type for parameter orvariable name is not supported inthe SQL routine.

Explanation: The SQL routine (function,method, or procedure) does not supportvariables or parameters of DATALINK,REFERENCE, DISTINCT, STRUCTURED, or LOBdata types.

User Response: Do not use SQL variables orparameters of DATALINK, REFERENCE,DISTINCT, STRUCTURED, or LOB data types inthe SQL routine definition. Specify a differentdata type for the parameter or variable name.

sqlcode: -789

sqlstate: 429BB

SQL0797N The trigger trigger-name is definedwith an unsupported triggeredSQL statement.

Explanation: The trigger must be defined with atriggered SQL statement that can only includestatements from the following list.

v A trigger can include the following controlstatements:

– dynamic compound statement

– FOR statement

– GET DIAGNOSTICS statement

– IF statement

– ITERATE statement

– LEAVE statement

– SIGNAL statement

– WHILE statement

v A BEFORE trigger can also include thefollowing triggered SQL statements:

– a fullselect

– an assignment statement

v An AFTER trigger can also include thefollowing triggered SQL statements:

– an INSERT statement

– a searched UPDATE statement

– a searched DELETE statement

– a fullselect

– an assignment statement (excludingassignment of transition variables)

v An INSTEAD OF trigger can also include thefollowing triggered SQL statements:

– an INSERT statement

– a searched UPDATE statement

– a searched DELETE statement

– a fullselect

– an assignment statement (excludingassignment of transition variables)

In some cases the trigger-name is not available foruse in the message.

User Response: Check the triggered SQLstatements in the trigger for any statement thatdoes not match the above list and remove it.

sqlcode: -797

sqlstate: 42987

SQL0798N A value cannot be specified forcolumn column-name which isdefined as GENERATEDALWAYS.

Explanation: When inserting or updating a rowin a table, a value was specified for theGENERATED ALWAYS column column-name.GENERATED ALWAYS columns should not bespecified in the column-list for an INSERT or inthe SET clause for an update unless the keywordDEFAULT is specified.

The INSERT or UPDATE is not performed.

User Response: Remove the GENERATEDALWAYS column from the column-list or SETclause, or specify DEFAULT as the column value.

sqlcode: -798

sqlstate: 428C9

SQL0800 - SQL0899


SQL0801N Division by zero was attempted.

Explanation: The processing of a columnfunction or arithmetic expression resulted indivision by zero.

The statement cannot be processed. For theINSERT, UPDATE, or DELETE statements, noinserts or updates are performed.

User Response: Examine the SQL statement todetermine the cause of the problem. If theproblem is data dependent, it is necessary toexamine the data processed when the erroroccurred. Refer to the SQL Reference to see thevalid ranges for the data types.

Federated system users: examine the SQLstatement to determine the cause of the problem.If the problem is data dependent, examine thedata being processed at the data sources whenthe error occurred.

sqlcode: -801

sqlstate: 22012

SQL0802N Arithmetic overflow or otherarithmetic exception occurred.

Explanation: The processing of a columnfunction or arithmetic expression has resulted inan arithmetic overflow.

The statement cannot be processed. For theINSERT, UPDATE, or DELETE statements, noinserts or updates are performed.


This error may also be returned when columnfunctions cannot handle the value that isreturned by the SQL statement. For example,issuing a SELECT COUNT statement against atable that has more rows than defined by theMAX_LONGINT_INT SQL limit will cause anarithmetic overflow error. Consider using theCOUNT_BIG column function for tables withmore than 2 147 483 647 rows.

Federated system users: examine the SQLstatement to determine the cause of the problem.If the problem is data dependent, examine thedata being processed at the data sources whenthe error occurred. Refer to the correspondingSQL Reference for the data source to determinethe valid ranges for the data types.

sqlcode: -802

sqlstate: 22003

SQL0803N One or more values in theINSERT statement, UPDATEstatement, or foreign key updatecaused by a DELETE statementare not valid because the primarykey, unique constraint or uniqueindex identified by index-idconstrains table table-name fromhaving duplicate rows for thosecolumns.

Explanation: The INSERT or UPDATE objecttable table-name is constrained by one or moreUNIQUE indexes to have unique values incertain columns or groups of columns.Alternatively, a DELETE statement on a parenttable caused the update of a foreign key in adependent table table-name that is constrained byone or more UNIQUE indexes. Unique indexesmight support primary keys or uniqueconstraints defined on a table. The statementcannot be processed because completing therequested INSERT, UPDATE or DELETEstatement would result in duplicate columnvalues.

Alternatively, if a view is the object of theINSERT or UPDATE statement, it is the tabletable-name on which the view is defined that isconstrained.

If index-id is an integer value, the index name canbe obtained from SYSCAT.INDEXES by issuingthe following query:

SELECT INDNAME, INDSCHEMAFROM SYSCAT.INDEXESWHERE IID = <index-id>AND TABSCHEMA = ’schema’AND TABNAME = ’table’


where schema represents the schema portion oftable-name and table represents the table nameportion of table-name.

The statement cannot be processed. The tableremains unchanged.

User Response: Examine the definition for theindex identified by index-id.

For an UPDATE statement, ensure that thespecified operation is not itself inconsistent withthe uniqueness constraint. If this does not showthe error, examine the object table content todetermine the cause of the problem.

For an INSERT statement, examine the objecttable content to determine which of the values inthe specified value list violates the uniquenessconstraint. Alternatively, if the INSERT statementcontains a subquery, the object table contentsaddressed by that subquery must be matchedagainst the object table contents to determine thecause of the problem.

For a DELETE statement, examine the identifieddependent table for unique constraints on foreignkeys that are defined with the rule ON DELETESET NULL. This table has a foreign key columnincluded in the identified unique index thatcannot be set to null since there is already a nullin the column for that table.

Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)and examine the index definitions and data forthe conditions listed previously.

sqlcode: -803

sqlstate: 23505

SQL0804N The application programparameters for the current requestare not valid. Reason codereason-code. If a host variable orSQLVAR in the SQLDA is invalidthen: host variable/SQLVARnumber = var-number, SQLTYPE =sqltype, SQLLEN = sqllen, hostvariable/SQLVAR type =input-or-output.

Explanation: An error occurred whileprocessing the current request.

v The call parameter list, which is created by theprecompiler, may not be correct if theapplication programmer has modified theoutput of the precompiler or over-written thecall parameter list in another way.

v The SQLDA or host variable(s) in the SQLstatement are invalid.

v The request being made is not supported or isout of context.

Reason codes are interpreted as follows:

100 The request being made is notsupported or is out of context.

101 SQLDA.SQLN is less thanSQLDA.SQLD

102 SQLVAR.SQLTYPE is invalid.

Federated system users: A data type thatyou specified is not supported by eitherthe federated server or the data sourcethat you want to access.

103 The length specified inSQLVAR.SQLLEN orSQLVAR2.SQLLONGLEN is incorrectfor the SQL type given inSQLVAR.SQLTYPE.

104 Doubling of the SQLVARs is expected,but the SQLDOUBLED field ofSQLDA.SQLDAID is not set to ’2’. Thismay be required because of a largeobject type or a structured type.

105 A double-byte character Large Objecthas an odd value indicated by the


SQLVAR2.SQLDATALEN pointer, whichis always in terms of bytes, even forDBCLOBs.

106 The SQLDATA pointer is invalid orpoints to insufficient storage.

107 The SQLIND pointer is invalid or pointsto insufficient storage.

108 The SQLDATALEN pointer is invalid orpoints to insufficient storage.

109 A specific number of hostvariables/SQLVARS is expected for thecurrent SQL statement.

110 The LOB locator is not associated with aLOB of a compatible type.

111 A LOB is indicated by the SQLTYPE ofthe SQLVAR, but the second SQLVAR isnull.

112 The SQLDATATYPE NAME field is notvalid. It does not conform to the formatfor identifying an existing user-definedtype in the database. The format foridentifying an existing user-defined typeis as follows: 8 bytes, followed by aperiod, followed by 18 bytes.

113 The SQLFLAG4 field is not valid. If astructured type is specified the valuemust be X’12’. If a reference type isspecified the value must be X’01’.Otherwise the value must be X’00’.

In SQL statements with host variables, use thehost variable number to count in from thebeginning of the statement (or substatement, inthe case of compound SQL) to locate the invalidhost variable. For statements using an SQLDA,the SQLVAR number is used to locate the invalidSQLVAR. For an input SQLDA, count only inputhost variables or SQLVARs; similarly for output.Note that this number is based at 1.


User Response: Examine the applicationprogram for any errors noted. Note that theprogrammer should not attempt to modify theprecompiler output.

Federated system users: If you received reasoncode 102, specify a supported data type andresubmit the program.

sqlcode: -804

sqlstate: 07002

SQL0805N Package package-name was notfound.

Explanation: The statement cannot completebecause the necessary package was not found inthe catalog.

The package-name is either in the form:

v ’pkgschema.pkgname 0Xcontoken’, where theconsistency token is given in hexadecimal.

v pkgschema.pkgname.pkgversion’, if thepackage version is the empty string then’.pkgversion’ is omitted from the name.

Possible causes for this message (SQLCODE) are:

v The package was not bound or it wasdropped.

v If attempting to run a DB2 utility or CLIapplication, the DB2 utilities may need to berebound to the database.

Note that when version-ids are in use for thegiven package-schema.package-name, there maybe packages defined with the same packageschema and package name, but the correctpackage is not found since the existing packagesdo not match the requested version orconsistency token. A package must match allthree parts of the package-name. When multipleversions are being used, additional causes forthis messages are:

v the version of the application being executedwas precompiled, compiled, and linked, butwas not bound, or it was bound but thatversion of package was subsequently dropped.

v the application was precompiled and bound,but not compiled and/or linked, so theapplication being executed is not up to date.

v the package was bound from a bind filegenerated by a different precompile of thesource file than the precompile that produced


the modified source file that was compiled andlinked into the application executable.

v a new application was bound with the samename (and version) of an existing package,thus replacing the existing package. If theapplication associated with the replacedpackage is run, this error would result.

In all these cases, the consistency token of therequest does not match the consistency token ofthe existing version and thus the package isconsidered to be not found.


User Response: Specify the correct packagename or bind the program. If the applicationbeing run is not bound to the database, contactthe database administrator to do the necessarybinding. Ensure that the application or objectmodule being executed is the compiled andlinked modified source code associated with theprecompile and bind that generated the package.

The following SQL statements can be used toquery the catalog to determine if there aredifferent versions of the package.

SELECT PKGSCHEMA, PKGNAME,PKGVERSION, UNIQUE_ID

FROM SYSCAT.PACKAGESWHERE PKGSCHEMA = ’pkgschema’

and PKGNAME=’pkgname’.

Note that the UNIQUE_ID column correspondsto the consistency token.

If the DB2 utility programs need to be reboundto the database, the database administrator canaccomplish this by issuing one of the followingCLP command from the bnd subdirectory of theinstance, while connected to the database:

v ″DB2 bind @db2ubind.lst blocking all grantpublic″ for the DB2 utilities.

v ″DB2 bind @db2cli.lst blocking all grantpublic″ for CLI.

Federated system users: ensure that the packagesrequired for the federated server are bound atthe applicable data sources. Refer to the

Federated Systems Guide for more informationabout binding packages to data sources.

sqlcode: -805

sqlstate: 51002

SQL0808N The CONNECT statementsemantics are not consistent withthose of other existingconnections.

Explanation: The CONNECT statementoriginates from a source file which wasprecompiled having different connection options(SQLRULES, CONNECT type, SYNCPOINT, orRELEASE type) than that of a source file forwhich a connection exists.

User Response: Ensure that all source files areprecompiled using the same CONNECT options,or if this is not possible, call the SET CLIENT apito set the desired options for the applicationprocess before issuing the first CONNECTstatement.

sqlcode: -808

sqlstate: 08001

SQL0811N The result of a scalar fullselect,SELECT INTO statement, orVALUES INTO statement is morethan one row.

Explanation: One of the following caused theerror:

v Execution of an embedded SELECT INTO orVALUES INTO statement resulted in a resulttable of more than one row.

v Execution of a scalar fullselect resulted in aresult table of more than one row.

Federated system users: this situation can bedetected by federated server or by the datasource.


User Response: Ensure that the statementcontains the proper condition specifications. If it


does, there may be a data problem that iscausing more than one row to be returned whenonly one is expected.

Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)and examine the selection criteria and data forthat object.

sqlcode: -811

sqlstate: 21000

SQL0817N The SQL statement cannot beexecuted because the statementwill result in a prohibited updateoperation.

Explanation: The application attempted toexecute an SQL statement that would result inupdates to user data or to the subsystem catalog.This is prohibited for one of the followingreasons:

v The application is running as an IMSinquiry-only transaction.

v The application is an IMS or CICS applicationthat is attempting to update data at a remoteDBMS that does not support two-phasecommit.

v The application is attempting to update data atmultiple locations and one of the locationsdoes not support two-phase commit.

These SQL statements include INSERT, UPDATE,DELETE, CREATE, ALTER, DROP, GRANT, andREVOKE.


User Response: If the application is running asan IMS inquiry-only transaction, see your IMSsystem programmer about changing theinquiry-only status of the transaction underwhich your application is running.

If the IMS or CICS application is attempting aremote update, either the application must bechanged to run as a local application on theserver DBMS, or the server DBMS must be

upgraded to support two-phase commit.

If the application is attempting to update data atmultiple locations, either the application must bechanged, or all DBMSs involved must beupgraded to support two-phase commit.

sqlcode: -817

sqlstate: 25000

SQL0818N A timestamp conflict occurred.

Explanation: The timestamp generated by theprecompiler at precompile time is not the sameas the timestamp stored with the package at bindtime.

This problem can be caused by the following:

v The application was precompiled, compiled,and linked, but was not bound.

v The application was precompiled and bound,but not compiled and/or linked, so theapplication being executed is not up to date.

v The package was bound from a bind filegenerated by a different precompile of thesource file than the precompile that producedthe modified source file that was compiled andlinked into the application executable.

v A new application was bound of the samename and existing package, thus replacing theexisting package. If the application associatedwith the replaced package is run, this errorwould result.

Federated system users: in addition to the causeslisted previously, the problem can also be due tonot binding the required packages at allapplicable data sources.


User Response: Bind the application again,using the bind file for the program that matchesthe object module. Or, execute the program thatcorresponds to the package stored in thedatabase.

If installing the sample database, record thenumber and text of this message and thencontact your technical service representative.


Federated system users: in addition to thepreviously listed actions, ensure that thepackages required for the federated server arebound at the applicable data sources. Refer to theFederated Systems Guide for more informationon binding packages to data sources.

sqlcode: -818

sqlstate: 51003

SQL0822N The SQLDA contains a dataaddress or indicator variableaddress which is not valid.

Explanation: The application program placed anaddress that is not valid in the SQLDA.


User Response: Correct the application programso that valid addresses are placed in SQLDA.

sqlcode: -822

sqlstate: 51004

SQL0840N Too many items were returned ina SELECT list.

Explanation: The number of items returned inthe SELECT list exceeds the allowable maximum.The maximum for SELECT lists (other than oncommon table expressions) is 1012. Themaximum for SELECT lists in common tableexpressions is 5000.


User Response: Determine whether all theinformation is actually needed. (Note that thenumber of items returned by the SELECT list * inthe SQL statement SELECT * from A, B, C is thesum of the number of columns in all threetables.) If possible, rewrite the SQL statement soonly the necessary items of information arereturned. If all the information is necessary, breakthe SQL statement into two or more statements.

sqlcode: -840

sqlstate: 54004

SQL0842N A connection to server server-namealready exists.

Explanation: SQLRULES(STD) is in effect and aCONNECT statement identifies an existing SQLconnection.

User Response: The correction depends on theerror:

v If the server name is not the intended name,correct it.

v If SQLRULES(STD) is in effect and theCONNECT statement identifies an existingSQL connection, replace the CONNECT withSET CONNECTION or change the option toSQLRULES(DB2).

Correct the error in the application and try again.

sqlcode: -842

sqlstate: 08002

SQL0843N The server name does not specifyan existing connection.

Explanation: A statement, command, or APIspecified a server name that does not identify anexisting SQL connection of the applicationprocess.

This may have occurred using:

v a SET CONNECTION statement

v a RELEASE statement

v a DISCONNECT statement

v SET or QUERY CLIENT INFORMATION

User Response: The correction depends on theerror:

v If the server name is not the intended name,correct it.

v Ensure that a connection to the server hasbeen established and is in a current ordormant state before issuing the request forthat connection.

Correct the error in the application and try again.

sqlcode: -843


sqlstate: 08003

SQL0845N A PREVVAL expression cannot beused before the NEXTVALexpression generates a value inthe current session for sequencesequence-name.

Explanation: A PREVVAL expression specifiedsequence sequence-name, but a value has not yetbeen generated for this sequence. A NEXTVALexpression must be issued in this session togenerate a value for this sequence before aPREVVAL expression for the sequence can beissued.

User Response: Issue at least one NEXTVALexpression for a sequence before issuing anyPREVVAL expression for the same sequence in asession.

sqlcode: -845

sqlstate: 51035

SQL0846N Invalid specification of identitycolumn or sequence objectobject-type object-name. Reason code= reason-code.

Explanation: For an identity column orsequence object, the specification of an attributein a CREATE or ALTER statement may beinvalid for one of the following reasons:

1. The underlying data type of the identitycolumn or sequence object is not supported.Identity columns and sequence objectssupport the following data types: SMALLINT,INTEGER, BIGINT and DECIMAL (orNUMERIC) with a scale of zero.

2. The value for START WITH, INCREMENTBY, MINVALUE or MAXVALUE is outside ofthe range for the data type of the identitycolumn or sequence object.

3. MINVALUE must be less than or equal toMAXVALUE.

4. An invalid value was specified for CACHE.The value must be an INTEGER with aminimum value of 2.

User Response: Correct the syntax and resubmitthe statement.

sqlcode: -846

sqlstate: 42815

SQL0859N Access to the Transaction ManagerDatabase failed with SQLCODESQLCODE.

Explanation: The application was precompiledwith SYNCPOINT(TWOPHASE) and requires aTransaction Manager Database to coordinate thetwo phase commit. Reasons why the TransactionManager Database is not available might includethe following:

v It was not created.

v The tm_database field of the database managerconfiguration file has not been updated andactivated with the name of the database.

v The database exists, but communication to thedatabase failed.

User Response: Possible actions:

v Refer to the SQLCODE that was returned withthis message, and follow the appropriateaction for that SQLCODE.

v Verify that the tm_database exists; if not, createa new database or select a database thatcurrently exists for use as the TM database. Itis recommended to create a separate databaseif there are no serious constraints on diskstorage.

v Update the database manager configurationfor the TM database using the field tm_databaseif that has not already been done.

v Verify that a connection to the tm_database canbe made. For example, attempt the connectionusing the Command Line Processor.

v Ensure that the tm_database chosen is not adatabase accessed through DB2 Connect.

sqlcode: -859

sqlstate: 08502


SQL0863W A successful connection wasmade, but only single bytecharacters should be used.

Explanation: The server database and clientapplication are using codepages for differentlanguage types and any characters outside the7-bit ASCII range cannot be guaranteed (only thecharacters in the 7-bit ASCII range exist in allcodepages). For example, the connection mightbe between a Japanese and a Latin-1 codepage,but none of the Japanese characters will beavailable in the Latin-1 codepage, so all of thesecharacters should be avoided (English charactersare fine though).

Federated system users: possible causes are:

v The federated database supports single-byteand double-byte characters but the databaseclient system supports only single-bytecharacters.

v The data source supports single-byte anddouble-byte characters but the federatedsystem supports only single-byte characters.

User Response: Do not submit SQL statementsor commands that use characters which are notcommon between the application and databasecodepages.

Federated system users: do not submit SQLstatements or commands that use characterswhich are not common between the clientsystem, the federated system, and the datasource.

sqlcode: +863

sqlstate: 01539

SQL0865N Invalid tm_database value.

Explanation: The database chosen as thetm_database in the database managerconfiguration is not valid. The database must beat level DB2 V2.1 or later, and cannot be adatabase accessed through DRDA protocol (ie.through DB2 Connect).


User Response:

1. Update the database manager configurationto specify a valid database for the tm_databaseparameter.

2. Issue db2stop and db2start to ensure that thechange takes effect.

sqlcode: -865

sqlstate: 08001

SQL0866N Connection redirection failed.Reason code: reason-code

Explanation: Directory cataloging for a databasecaused a connection to be redirected in a mannerwhich is not supported.

Possible reason codes are:

01 A database connection involved morethan one redirection from a server toanother server; only one connectionredirection is supported.

02 A connection was attempted whichinvolved both a current version of DB2client or server and a version 1 client orserver. This attempt failed becauseredirection is not supported withversion 1 clients or servers.

User Response: By the reason code, the actionsare:

01 Recatalog the database so that there isno more than one server redirecting theconnection to another server in the pathof the connection.

02 Recatalog the database so that there isno intermediary server redirecting theconnection.

sqlcode: -866

sqlstate: 08001


SQL0868N A CONNECT using aUSER/USING clause wasattempted to a server for which aconnection already exists.

Explanation: A current or dormant connectionto a server exists, and an attempt to CONNECTto this server using the USER/USING clause isinvalid.


v Use the SET CONNECTION statement tomake the connection to the DORMANTconnection current.

v Use the CONNECT statement withoutUSER/USING if SQLRULES(DB2) are beingused by the application.

v Complete the existing unit of work,disconnect, and then reconnect usingUSER/USING.

sqlcode: -868

sqlstate: 51022

SQL0880N SAVEPOINT savepoint-name doesnot exist or is invalid in thiscontext.

Explanation: An error occurred issuing aRELEASE or ROLLBACK TO SAVEPOINTsavepoint-name statement. Either a savepoint withthat name does not exist, or it was establishedoutside the current atomic execution context.


User Response: Correct the name of thesavepoint in the statement and reissue thestatement.

sqlcode: -880

sqlstate: 3B001

SQL0881N A SAVEPOINT with namesavepoint-name already exists, butthis savepoint name cannot bereused.

Explanation: The name savepoint-name hasalready been used in a SAVEPOINT statement.The savepoint name cannot be reused because atleast one of the SAVEPOINT statements thatused this name also specified the UNIQUEkeyword, which asserts that the name must beunique.

The statement cannot be processed. The newsavepoint is not set. The old savepoint with thesame name still exists.

User Response: Choose another name for thissavepoint and reissue the SAVEPOINT statement.If this existing savepoint name must be reused,issue the RELEASE SAVEPOINT statement tofree the existing savepoint. However, be awarethat the RELEASE SAVEPOINT statement alsoreleases any savepoints that were established inthe transaction since the specified savepoint wasestablished. For more information, refer to theSQL Reference.

sqlcode: -881

sqlstate: 3B501

SQL0882N Savepoint does not exist.

Explanation: An error occurred issuing aROLLBACK TO SAVEPOINT statement. Issuinga ROLLBACK TO SAVEPOINT withoutspecifying a specific savepoint name is notallowed when there are no existing savepoints.


User Response: Issue a different statement, ortry rolling back the entire transaction with theROLLBACK statement.

sqlcode: -882

sqlstate: 3B502

SQL0900 - SQL0999


SQL0900N The application state is in error. Adatabase connection does notexist.

Explanation: A connection to a database doesnot exist. This may be due to one of thefollowing reasons:

v A serious error in the application state hascaused the database connection to be lost.

v The application may have disconnected from adatabase and not established a new currentconnection before executing the next SQLstatement.

User Response: Reestablish a currentconnection be either switching to an existingdormant connection (using CONNECT TO orSET CONNECTION) or by establishing a newconnection (using CONNECT).

sqlcode: -900

sqlstate: 08003

SQL0901N The SQL statement failed becauseof a non-severe system error.Subsequent SQL statements canbe processed. (Reason reason.)

Explanation: An error has occurred which isdue to a system error. Processing of the SQLstatement has ended for reason reason (this is inEnglish only and is useful only to IBM supportpersonnel).

User Response: Record the message number(SQLCODE) and reason reason.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Then contact your technical servicerepresentative with the following information:

v Problem description

v SQLCODE

v reason reason

v SQLCA contents if possible

v Trace file if possible.

Federated system users: isolate the problem tothe data source failing the request (refer to the

Troubleshooting Guide to determine which datasource is failing to process the SQL statement)and take the necessary diagnostic steps for thatdata source. The problem determinationprocedures for data sources vary, so refer to theapplicable data source manuals.

sqlcode: -901

sqlstate: 58004

SQL0902C A system error (reason code =reason-code) occurred. SubsequentSQL statements cannot beprocessed.

Explanation: A system error occurred.

User Response: Record the message number(SQLCODE) and reason code in the message.



v SQLCODE and embedded reason code



Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)and take the necessary diagnostic steps for thatdata source. The problem determinationprocedures for data sources vary, so refer to theapplicable data source manuals.

sqlcode: -902

sqlstate: 58005

SQL0903N COMMIT statement failed,transaction rolled back. Reasoncode: reason-code

Explanation: One or more of the serversparticipating in the current unit of work was


unable to prepare the database to be committed.The COMMIT statement has failed and thetransaction has been rolled back.


01 A connection to one of the databasesparticipating in the unit of work waslost.

Federated system users: if the databaseyou connected to is a federated serverdatabase where nicknames are used, aconnection to one of the data sourcesrequired for a nickname within thedatabase was lost.

02 One of the databases or nodesparticipating in the unit of work wasaccessed, but unable to prepare tocommit.

Federated system users: if the databaseyou connected to is a federated serverdatabase where nicknames are used, oneof the data sources required for anickname is unable to prepare tocommit.

03 A DB2 Data Links Managerparticipating in the unit of work wasunable to prepare to commit.

04 One or more declared temporary tablesare in an inconsistent state.

05 An unexpected error occurred. Checkthe administration notification log fordetails.

User Response: If a connection to a databasewas lost, reestablish the connection. If the failurewas not connection related, reference the errordiagnostic logs on the remote system todetermine the nature of the failure and whataction might be required. Rerun the application.

sqlcode: -903

sqlstate: 40504

SQL0904N Unsuccessful execution caused byan unavailable resource. Reasoncode: reason-code, type of resource:resource-type, and resource name:resource-name.

Explanation: The SQL statement could not beexecuted because resource resource-name of typeresource-type was not available at the time for thereason indicated by reason-code. Refer to theProblem Determination documentation of DB2for MVS for an explanation of resource typecodes.

User Response: Verify the identity of theresource that was not available. To determinewhy the resource was unavailable, refer to thespecified reason-code.

sqlcode: -904

sqlstate: 57011

SQL0905N Unsuccessful execution due toresource limit being exceeded.Resource name = resource-name,limit = limit-amount1 CPU seconds(limit-amount2 service units)derived from limit-source.

Explanation: The execution of the SQLstatement was terminated because a resourcelimit was exceeded.

The name of the resource whose limit wasexceeded is resource-name. It is also the name ofthe column in the resource limit specificationtable from which the limit was derived. The limitthat was exceeded in CPU seconds islimit-amount1 and in service units it islimit-amount2. The resource-name may beASUTIME, which is the number of CPU secondspermitted for each SQL statement. The maximumnumber of CPU seconds permitted islimit-amount1. The maximum number in serviceunits is limit-amount2.

The source used to derive the limit-amount islimit-source and is either the name of a resourcelimit specification table or a ’system parameter’.If the source is a system parameter, the resourcelimit specification table did not contain an


applicable entry or an error occurred whileaccessing the table. In either case, the limit isobtained from an install (system) parameter.

User Response: Determine why this SQLstatement took so long and take appropriateaction. Consider simplifying the SQL statement,restructuring tables and indexes, or contactingthe installation group responsible for maintainingthe resource limit specification tables.

An application program that receives this returncode can execute additional SQL statements.

sqlcode: -905

sqlstate: 57014

SQL0906N The SQL statement cannot beexecuted because this function isdisabled due to a prior error.

Explanation: Execution of the SQL statementfailed because the requested function had beendisabled by a prior error. This situation can ariseif the application program has intercepted anabend (for instance, by an ON ERROR conditionin a PL/I program) and continued to executeSQL statements. This situation may also arise if aDB2 CICS transaction encountered a createthread error yet continued to issue SQL requestswithout issuing a SYNCPOINT ROLLBACK first.

User Response: In general, an applicationprogram should terminate upon receipt of thisreturn code. All subsequent attempts by theapplication to execute other SQL statements willalso fail with the same return code. In the case ofa DB2 CICS transaction, if the SQLERRP field inthe SQLCA contains the module nameDSNCEXT1, the transaction may issue aSYNCPOINT ROLLBACK and continueprocessing. If the transactions chooses toROLLBACK and continue processing, it must becapable of correcting the situation that causedthe create thread error to occur originally.

sqlcode: -906

sqlstate: 24514, 51005, 58023

SQL0908N bind-type error using auth-idauthority BIND, REBIND, orAUTO_REBIND operation is notallowed.

Explanation: For BIND and REBIND, theindicated authorization ID is not allowed toperform the indicated bind-type against a plan orpackage. An entry in the resource limitspecification table (RLST) prohibits binding andrebinding by this authorization ID, or allauthorization IDs. For AUTO-REBIND, thesystem parameter controlling AUTO-REBINDoperations is set to disallow AUTO-REBIND.

bind-typeType of bind operation (BIND, REBINDor AUTO-REBIND).

auth-id Authorization ID of the invoker of theBIND subcommand or primaryauthorization ID of the invoker of theplan for AUTO-REBIND operations.

User Response: If the indicated authorization idshould be allowed to bind, change the entry inthe active RLST table. If AUTO-REBINDoperations are disabled, rebind the packagebefore reexecuting the package.

sqlcode: -908

sqlstate: 23510

SQL0909N The object has been deleted.

Explanation: The application program haseither (1) dropped a table and then attempted toaccess it, or (2) dropped an index and then triedto access its object table using that index.

User Response: The logic of the applicationprogram must be corrected such that it does notattempt to access or use an object after it hasbeen dropped.

Dropping indexes within an application programis especially hazardous, because there is no wayof determining whether or not the plan that hasbeen generated for the application (by BIND orREBIND) actually uses a particular index foraccess to its object table.

sqlcode: -909


sqlstate: 57007

SQL0910N The SQL statement cannot accessan object on which a modificationis pending.

Explanation: The application programattempted to access an object within the sameunit of work in which either:

v The application program issued a DROPagainst the object or a related object (e.g. anindex for a table)

v The application program issued a statementagainst the object that added or dropped aconstraint.

v The application program issued a DROPTRIGGER or CREATE TRIGGER statementthat affected the object, either directly orindirectly.

v The application program issued a ROLLBACKTO SAVEPOINT statement, which placed theobject in the modification pending state.

v The application program issued a statementthat caused all rows of a NOT LOGGEDdeclared temporary table to be deleted.

Federated system users: in addition to thepreviously listed causes, other data sourcespecific restrictions may exist that prevent accessto the object.

The SQL statement cannot be processed.

User Response: Modify the application programso there is no attempt to access an object withinthe same unit of work in which the modificationwas made. In general, it is better to isolate DataDefinition Language (DDL) statements in adifferent unit of work than Data ManipulationLanguage (DML) statements that access the sameobjects.

The unit of work must be committed or rolledback before the statement that failed can beprocessed successfully. If the committedmodification caused an object to be dropped,then the object may have to be recreated in orderfor the failing SQL statement to be processedsuccessfully.

If the object is modified within a SAVEPOINT,modify the application program so that it doesnot attempt to access the object after theapplication issues a ROLLBACK TO SAVEPOINTstatement. Any cursor that accesses the modifiedobject and is open at the time of the ROLLBACKTO SAVEPOINT will not be accessible. Modifythe application so that it closes the cursor.

If an insert, delete or update statement involvinga NOT LOGGED declared temporary table fails,then all rows in that table are deleted. Anycursor that is open against that declaredtemporary table at the time of the failure will notbe accessible and should be closed by theapplication.

Federated system users: if the previous actiondoes not solve the problem, isolate the request(refer to the Troubleshooting Guide to determinewhich data source is failing to process the SQLstatement) and determine what additionalconstraints exist on the data source that arepreventing access to the object. Ensure that theapplication is not violating any of thoseconstraints.

sqlcode: -910

sqlstate: 57007

SQL0911N The current transaction has beenrolled back because of a deadlockor timeout. Reason codereason-code.

Explanation: The current unit of work wasinvolved in an unresolved contention for use ofan object and had to be rolled back.


2 transaction rolled back due to deadlock.

68 transaction rolled back due to locktimeout.

72 transaction rolled back due to an errorconcerning a DB2 Data Links Managerinvolved in the transaction.

Note: The changes associated with the unit ofwork must be entered again.


The application is rolled back to the previousCOMMIT.

User Response: To help avoid deadlock or locktimeout, issue frequent COMMIT operations, ifpossible, for a long-running application, or for anapplication likely to encounter a deadlock.

Federated system users: the deadlock can occurat the federated server or at the data source.There is no mechanism to detect deadlocks thatspan data sources and potentially the federatedsystem. It is possible to identify the data sourcefailing the request (refer to the problemdetermination guide to determine which datasource is failing to process the SQL statement).

Deadlocks are often normal or expected whileprocessing certain combinations of SQLstatements. It is recommended that you designapplications to avoid deadlocks to the extentpossible.

sqlcode: -911

sqlstate: 40001

SQL0912N The maximum number of lockrequests has been reached for thedatabase.

Explanation: The maximum number of locks forthe database was reached because insufficientmemory was allocated to the lock list.


User Response: The application should submita COMMIT or ROLLBACK statement beforesubmitting other SQL statements. Considerincreasing the database configuration parameter (locklist) to allow more lock list space.

sqlcode: -912

sqlstate: 57011

SQL0913N Unsuccessful execution caused bydeadlock or timeout. Reason codereason-code.

Explanation: The request issued was involvedin an unresolved contention for use of an objectand the execution failed.


2 transaction branch failed due todeadlock.

68 transaction branch failed due to locktimeout.

72 transaction rolled back due to an errorconcerning a DB2 Data Links Managerinvolved in the transaction.

80 statement failed due to timeout.

User Response:

v For reason code 80, you can retry the failedstatement without terminating the application.If the application accesses multiple remotedatabases, it may be better to rollback thetransaction to avoid the possibility of a globaldeadlock.

v For other reason codes, issue a request torollback the transaction. The transaction cannotbe committed due to the failure of the currenttransaction branch.

v To help avoid deadlock or lock timeout, issuefrequent COMMIT operations, if possible,within long-running applications orapplications requiring data with highconcurrent access.

sqlcode: -913

sqlstate: 57033

SQL0917N Remote bind from a DRDAapplication requester failed.

Explanation: An error has occurred during aremote bind from a DRDA application requester.This error can be issued during bind or commitprocessing.

User Response: This problem is usually causedby an SQL statement which did not get boundbecause of an error. The user should consult thediagnostics facility at the DRDA applicationrequester to determine which statement iscausing the error and correct it.

sqlcode: -917

sqlstate: 42969


SQL0918N Application must execute arollback.

Explanation: The unit of work has already beenrolled back in the database but other resourcemanagers involved in this unit of work mightnot. To ensure integrity of this application, allSQL requests will be rejected until theapplication issues a rollback.

User Response: All SQL requests will berejected until the application issues a rollback.For example, in a CICS environment, this wouldbe a CICS SYNCPOINT ROLLBACK command.

sqlcode: -918

sqlstate: 51021

SQL0920N Data on a database client systemcannot be accessed from otherdatabase client systems.

Explanation: The workstation has beenconfigured as a client or a server with localclients. Any databases created on this systemcannot be shared by other workstations.

The function cannot be processed.

User Response: Request data only from serverworkstations.

sqlcode: -920

sqlstate: 57019

SQL0925N SQL COMMIT invalid forapplication executionenvironment.

Explanation: COMMIT is disallowed in thefollowing cases:

v In a Distributed Transaction Processingenvironment such as CICS, a static SQLCOMMIT statement was attempted, but acommit statement specific to the environmentis required. For example, in a CICSenvironment this would be the CICSSYNCPOINT command.

v A DB2 application precompiled or set to useCONNECT 2 in a non-TP Monitor

environment has issued a dynamic SQLCOMMIT statement, whereas only static SQLCOMMITs are allowed.

v When issued from a stored procedure, SQLCOMMIT is also not allowed if the callingprogram is executing in a distributed unit ofwork or Distributed Transaction Processingenvironment.

User Response: Correct the problem by doingone of the following:

v Remove the statement issuing the COMMITand replace it with a statement which does thevalid equivalent for the environment

v In the case of a connect type 2 in a non-TPMonitor environment, use only staticCOMMIT.

v In the case of a stored procedure, remove theCOMMIT

sqlcode: -925

sqlstate: 2D521

SQL0926N SQL ROLLBACK invalid forapplication executionenvironment.

Explanation: ROLLBACK is disallowed in thefollowing cases:

1. In a Distributed Transaction Processingenvironment such as CICS, a static SQLROLLBACK statement was attempted, but arollback statement specific to the environmentis required. For example, in a CICSenvironment this would be the CICSSYNCPOINT ROLLBACK command.

2. A DB2 application precompiled or set to useCONNECT 2 has issued a dynamic SQLROLLBACK statement, whereas only staticSQL ROLLBACKs are allowed.

3. When issued from a stored procedure, SQLROLLBACK is also restricted if the callingprogram is executing in a distributed unit ofwork (CONNECT type 2) or DistributedTransaction Processing environment.

User Response:


1. Remove the statement issuing theROLLBACK and replace it with a statementwhich does the valid equivalent for theenvironment.

2. In the case of a connect type 2, use only staticCOMMIT.

3. In the case of a stored procedure, remove itentirely.

sqlcode: -926

sqlstate: 2D521

SQL0930N There is not enough storageavailable to process the statement.

Explanation: A request was made to thedatabase that required another memory page butno more pages are available to the databasemanager.



v Verify that your system has sufficient real andvirtual memory.


v If the error occurs during DUOWresynchronization, increase the maxagents andreduce the resync_interval database managerconfiguration parameter values.

v If the error occurs on a statement whichreferenced a routine (UDF, stored procedure ormethod), it may be that the storage required tocontain the arguments and return values wasmore than the memory available in the system.This might occur if the routine is defined withBLOB, CLOB, DBCLOB parameters or returnvalues, having a large size (2GB for example).

If the possible solutions listed above do not solvethe problem, it may be necessary to considerchanging the definition of the routine.

sqlcode: -930

sqlstate: 57011

SQL0931C Operating system file tableoverflow occurred. SubsequentSQL statements cannot beprocessed.

Explanation: An Operating system limit hasbeen reached. The application program is notpermitted to issue additional SQL statements.The database is marked as needing recovery andall applications using the database are preventedfrom accessing the database.

User Response: Terminate all the applicationsusing the database. Restart the database.

To help prevent the problem from recurring:

v Change the MAXFILOP database configurationparameter to a smaller value (this will reduceDB2’s use of the operating system file table),and/or

v Terminate other applications that are usingfiles, if appropriate, and/or,

v Refer to the operating system documentationfor increasing the operating system file tablelimit. In most UNIX environments this can beaccomplished by updating the kernelconfiguration with a larger value. (On AIX,this may only be possible by increasing theamount of memory in your machine).

sqlcode: -931

sqlstate: 58005

SQL0950N The table or index cannot bedropped because it is currently inuse.

Explanation: A DROP TABLE or DROP INDEXstatement cannot be issued when an open cursoris currently using the table or index.

The statement cannot be processed. The table orindex is not dropped.

User Response: Close any cursors required andresubmit the statement.

sqlcode: -950

sqlstate: 55006


SQL0951N The object object-name of typeobject-type cannot be alteredbecause it is currently in use bythe same application process.

Explanation: An ALTER statement or SETINTEGRITY statement for an object cannot beissued when it is either locked or in use.

The statement cannot be processed. The object isnot altered.

User Response: Close any cursors that dependeither directly or indirectly on the objectobject-name and resubmit the statement.

sqlcode: -951

sqlstate: 55007

SQL0952N Processing was cancelled due toan interrupt.

Explanation: The user may have pressed theinterrupt key sequence.

The statement processing is terminated. Somechanges may have been applied to the database,but not committed, before termination occurred.


User Response: Continue the application.


sqlcode: -952

sqlstate: 57014

SQL0954C Not enough storage is available inthe application heap to processthe statement.

Explanation: All available memory for theapplication has been used.


User Response: Terminate the application onreceipt of this message. Increase the databaseconfiguration parameter ( applheapsz) to allow alarger application heap.

sqlcode: -954

sqlstate: 57011

SQL0955C Sort memory cannot be allocatedto process the statement. Reasoncode = reason-code.

Explanation: Insufficient virtual memory isavailable to the database agent for sortprocessing, as indicated by the reason code:

1 Insufficient private process memory.

2 Insufficient shared memory in thedatabase-wide shared memory areadesignated for sort processing.

The statement cannot be processed but otherSQL statements may be processed.


v Decrease the value of the sort heap parameter( sortheap) in the corresponding databaseconfiguration file.

v For reason code 1, increase the private virtualmemory available, if possible. For example, onUNIX systems you can use the ulimitcommand to increase the maximum size of thedata area for a process.

v For reason code 2, increase the size of thedatabase-wide shared memory area designatedfor sort processing. To increase the size of thisarea without affecting the sortheap thresholdfor private sorts, increase the value of theSHEAPTHRES_SHR database configurationparameter.

To increase both the size of the database-wideshared memory area designated for sortprocessing as well as the sortheap thresholdfor private sorting, increase the value of theSHEAPTHRES database managerconfiguration parameter and setSHEAPTHRES_SHR to 0

sqlcode: -955

sqlstate: 57011


SQL0956C Not enough storage is available inthe database heap to process thestatement.

Explanation: All available memory for thedatabase has been used.


User Response: Terminate the application onreceipt of this message. Increase the databaseconfiguration parameter ( dbheap) to allow alarger database heap. If the number of I/Oservers is near the high limit, reducing thisnumber may also help.

To change dbheap, enter a command similar tothe following, which sets dbheap to size 2400 fordatabase sample:

db2 UPDATE DB CFG FOR sampleUSING DBHEAP 2400

Disconnect from the database to have the changetake effect.

sqlcode: -956

sqlstate: 57011

SQL0958C The maximum number of openfiles has been reached.

Explanation: The maximum number of filehandles available to the database has beenreached.


User Response: Increase any parameter thataffects the maximum number of open filesallowed at the location of the database. Thisincludes increasing the configuration parameter (maxfilop) to allow more file handles for theinstance and terminating other sessions to reducethe number of file handles being used.

sqlcode: -958

sqlstate: 57009

SQL0959C Not enough storage is available inthe communication heap of theserver to process the statement.

Explanation: All available memory in the servercommunication heap has been used.

The command or statement cannot be processed.

User Response: Terminate the application onreceipt of this message. Increase the size of thecommunication heap ( comheapsz) parameter inthe server workstation database managerconfiguration file.

NOTE: This message is applicable only forreleases of DB2 prior to Version 2.

sqlcode: -959

sqlstate: 57011

SQL0960C The maximum number of fileshas been reached in the database.

Explanation: The maximum number of databasefiles has been reached.


User Response: Terminate the application onreceipt of this message. Have all activeapplications disconnect from the database andthen have them reconnect to the database. If theerror continues, drop either tables, indexes, orboth from the database, or split the database.


sqlcode: -960

sqlstate: 57011

SQL0964C The transaction log for thedatabase is full.

Explanation: All space in the transaction log isbeing used.

If a circular log with secondary log files is beingused, an attempt has been made to allocate anduse them. When the file system has no morespace, secondary logs cannot be used.


If an archive log is used, then the file system hasnot provided space to contain a new log file.


User Response: Execute a COMMIT orROLLBACK on receipt of this message(SQLCODE) or retry the operation.

If the database is being updated by concurrentapplications, retry the operation. Log space maybe freed up when another application finishes atransaction.

Issue more frequent commit operations. If yourtransactions are not committed, log space may befreed up when the transactions are committed.When designing an application, consider when tocommit the update transactions to prevent a logfull condition.

If deadlocks are occurring, check for them morefrequently. This can be done by decreasing thedatabase configuration parameter DLCHKTIME.This will cause deadlocks to be detected andresolved sooner (by ROLLBACK) which will thenfree log space.

If the condition occurs often, increase thedatabase configuration parameter to allow alarger log file. A larger log file requires morespace but reduces the need for applications toretry the operation.


sqlcode: -964

sqlstate: 57011

SQL0965W There is no message textcorresponding to SQL warningSQLCODE in the message file onthis workstation. The warningwas returned from module namewith original tokens token-list.

Explanation: Database server returned codeSQLCODE to your application. The warning codedoes not correspond to a message in the DB2message file on this workstation.

User Response: Refer to the documentation for

your database server to determine the cause forspecified SQLCODE.

SQL0966N The error mapping file namespecified in the DatabaseConnection Services directorycannot be found or cannot beopened.


v The error mapping file does not exist.

v The error mapping file is currently opened byanother application.

v The error mapping file is not located in theexpected path.

v The error mapping file is damaged.

The error mapping data could not be retrieved.

User Response: Release the file from theapplication in which it is open or reinstall orrestore the original file.

sqlcode: -966

sqlstate: 57013

SQL0967N The format of the error mappingfile name specified in theDatabase Connection Servicesdirectory is not valid.

Explanation: An error occurred while theprogram was reading the error mapping file.

The error mapping data could not be retrieved.

User Response: Correct all syntactic errors inthe error mapping file.

sqlcode: -967

sqlstate: 55031

SQL0968C The file system is full.

Explanation: One of the file systems containingthe database is full. This file system may containthe database directory, the database log files, or atable space container.



User Response: Free system space by erasingunwanted files. Do not erase database files. Ifadditional space is required, it may be necessaryto drop tables and indexes identified as notrequired.

On unix-based systems, this disk full conditionmay be due to exceeding the maximum file sizeallowed for the current userid. Use the chusercommand to update fsize. A reboot may benecessary.

sqlcode: -968

sqlstate: 57011

SQL0969N There is no message textcorresponding to SQL error errorin the message file on thisworkstation. The error wasreturned from module name withoriginal tokens token-list.

Explanation: The Database server returnedSQLCODE error to your application. The errorcode does not correspond to a message in theDB2 message file on this workstation.

User Response: Refer to the documentation foryour database server to determine the cause forthe specified SQLCODE. Take action specified inthe documentation for the database server to fixthis problem.

Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement).Find the error in the applicable manual at thedata source. If the problem is data dependent, itmay be necessary to examine the data beingprocessed at the data source at the time the erroroccurred.

SQL0970N The system attempted to write toa read-only file.

Explanation: A file used by the database ismarked read-only or does not exist. The databaserequires write access to this file.


User Response: Terminate the application onreceipt of this message (SQLCODE). Ensure thatall database files are allowed both read and writeaccess. Check for unnecessary blank spaceswithin the specified filename.

sqlcode: -970

sqlstate: 55009

SQL0972N The database drive does notcontain the correct diskette.

Explanation: The diskette in the drive is not thedatabase diskette.


User Response: Place the required diskette intothe drive. Do not remove a diskette if theapplication starts using a database that resides init.

sqlcode: -972

sqlstate: 57019

SQL0973N Not enough storage is available inthe heap-name heap to process thestatement.

Explanation: All available memory for this heaphas been used. The statement cannot beprocessed.

User Response: Terminate the application onreceipt of this message (SQLCODE). Increase theconfiguration parameter for heap-name to increasethe heap size by issuing the following command:

db2 update db cfgfor db-nameusing heap-name heap-size

For APPGROUP_SHARE_HEAP, the followingthree database configuration parameters controlits size and usage: APPGROUP_MEM_SZ,GROUPHEAP_RATIO, and APP_CTL_HEAP_SZ.The number of applications in one applicationgroup is calculated by: APPGROUP_MEM_SZ /APP_CTL_HEAP_SZ. The application group


shared heap size is calculated by:APPGROUP_MEM_SZ * GROUPHEAP_RATIO /100.

sqlcode: -973

sqlstate: 57011

SQL0974N The drive containing the databaseis locked.

Explanation: The system reported that the drivecontaining the database is locked.


User Response: Ensure no other processing (forexample, CHKDSK) that can lock the drive isoccurring on the system. Retry the operation.


sqlcode: -974

sqlstate: 57020

SQL0975N A new transaction could not bestarted because database orinstance name is quiesced by userusername. Quiesce type: type.

Explanation: Another user has quiesced theinstance or database that you are attempting touse, and no new transactions are allowed untilthe instance or database is no longer in thequiesced state.

Quiesce type type refers to the instance ordatabase already quiesced and is a ’1’ for aninstance and a ’2’ for a database.

User Response: Contact the user who currentlyhas the instance or database quiesced todetermine when DB2 will no longer be quiesced,and retry the request at that time.

sqlcode: -975

sqlstate: 57046

SQL0976N The diskette drive door is open.

Explanation: The drive door for the database isopen.


User Response: Close the drive door and retrythe operation.

sqlcode: -976

sqlstate: 57021

SQL0977N COMMIT state unknown.

Explanation: The tm_database has becomeunavailable during COMMIT processing, andthis has caused the result of the COMMIT to beunknown. Resynchronization of the databaseswill occur when the tm_database becomesavailable. Note that the transaction may be rolledback during resynchronization. Further executionof SQL statements can safely occur, howeverlocks might be held until the resynchronizationprocess is complete.

User Response: Verify that the connection to thetm_database can be made, for example by usingCLP. If it cannot be made, follow the necessaryactions for the SQLCODE returned to ensure thata connection can be established.

sqlcode: -977

sqlstate: 40003

SQL0978N The diskette is write-protected.

Explanation: A write operation was attemptedto the database but the database diskette is writeprotected.


User Response: Verify that you are using thecorrect diskette. Remove protection from thediskette, if necessary.

sqlcode: -978

sqlstate: 55009


SQL0979N COMMIT has failed against numdatabases for an applicationprocess running withSYNCPOINT of NONE. Thefailures include the followingdatabase alias and SQLSTATEpairs (a maximum of four can bereturned): alias/SQLSTATE1,alias/SQLSTATE2, alias/SQLSTATE3,alias/SQLSTATE4.

Explanation: An application was connected tomultiple databases, and a COMMIT was issuedwhich failed for one or more of theseconnections.

Federated system users: if one of the failedconnections is a federated server database wherenicknames are used, then a commit against oneof the data sources required for a nickname hasfailed.

User Response: Depending upon the nature ofthe application and the data being updated, theuser might wish to discontinue the processingbeing done, log the failure, and issue theappropriate SQL to ensure that the changesintended by the application are consistentlyreflected across all databases involved.

If a full list of databases affected by COMMITerrors could not be returned please refer to thediagnostic log for a full list.

sqlcode: -979

sqlstate: 40003

SQL0980C A disk error occurred. SubsequentSQL statements cannot beprocessed.

Explanation: A disk error occurred thatprevented successful execution of the current andsubsequent SQL statements. The applicationprogram is not permitted to issue additional SQLstatements. For example, a recovery routineassociated with the application program cannotissue additional SQL statements. The database ismarked as needing recovery and all applicationsusing the database are prevented from accessingthe database.


User Response: Record all error informationfrom the SQLCA, if possible. Terminate allapplications using the database. Determine if theerror is a hardware error. Restart the database. Ifrecovery is not possible, restore the databasefrom a backup copy.


sqlcode: -980

sqlstate: 58005

SQL0982N A disk error occurred. However,subsequent SQL statements canbe processed.

Explanation: A disk error occurred duringprocessing of a temporary system file thatprevented successful execution of the currentSQL statement. However, subsequent SQLstatements can be processed.


User Response: Terminate the application onreceipt of this message (SQLCODE).

sqlcode: -982

sqlstate: 58004

SQL0983N The transaction log does notbelong to the current database.

Explanation: The signature stored in the log filedoes not match the database dependentsignature. This error usually occurs when theuser specified that the log file be stored in adirectory different from where the database isstored. File redirection can be involved.


User Response: Resubmit the command withthe proper access to the log file.

sqlcode: -983

sqlstate: 57036


SQL0984C COMMIT or ROLLBACK was notsuccessful. Subsequent SQLstatements cannot be processed.

Explanation: A commit or rollback operationcould not be processed successfully because of asystem error. The application program is notpermitted to issue additional SQL statements. Forexample, a recovery routine associated with theapplication program may not issue additionalSQL statements. The database is marked asneeding recovery and all applications using thedatabase are prevented from accessing thedatabase.


User Response: Record the message number(SQLCODE) and all SQLCA error information, ifpossible. Terminate all applications using thedatabase. Restart the database. If installing thesample database, drop it and install the sampledatabase again.

If recovery is not possible, restore the databasefrom a backup copy.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Contact your technical servicerepresentative with the following information:

Information required:


v SQLCODE



Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)and take the necessary diagnostic steps anddatabase recovery procedures for that datasource. The problem determination proceduresand database recovery procedures for datasources vary, so refer to the applicable datasource manuals.

sqlcode: -984

sqlstate: 58005

SQL0985C A file error occurred whileprocessing the database catalogs.The database is not usable.

Explanation: The system is unable to recoverfrom an I/O error on a catalog file.

The system cannot process any statements usingthe database.

User Response: Restore the database from abackup copy.


sqlcode: -985

sqlstate: 58005

SQL0986N A file error occurred whileprocessing a user table. The tableis not usable.

Explanation: The data in the table is no longervalid.

The system cannot process any statements usingthe table.

User Response: Restore the database from abackup version if the database is inconsistent.


sqlcode: -986

sqlstate: 58004

SQL0987C The application control sharedmemory set cannot be allocated.

Explanation: The application control sharedmemory set cannot be allocated. This error iscaused by insufficient memory resources foreither the database manager or the environmentin which its operations are being attempted.Memory resources that can cause this errorinclude:

v The number of shared memory identifiersallocated in the system.


v The amount of paging or swapping spaceavailable in the system.

v The amount of physical memory available inthe system.


v Ensure that sufficient memory resources areavailable to satisfy the database managerrequirements and those of the other programsrunning on the system.

v Reduce the database manager memoryrequirement for this memory set by reducingthe database configuration parameter,app_ctl_heap_sz, which affects it.

v Reduce one or more of the databaseconfiguration parameters dbheap,util_heap_sz, and buffpage. Refer to theAdministration Guide for the parametersaffecting the amount of database globalmemory allocated.

v Reduce the database manager configurationparameter, sheapthres, if intra_parallel is set toyes, or set intra_parallel to no.

v Where appropriate, stop other programs usingthe system.

sqlcode: -987

sqlstate: 57011

SQL0990C An index error occurred.Reorganize the table.

Explanation: An index has had considerableactivity that used all the free space for indexes.



User Response: Commit your work and retrythe command. If the error continues, roll backyour work. If errors still persist, reorganize thetable, if possible.

Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)

and follow the index re-creation procedures forthat data source.

SQL0992C The release number of theprecompiled program is not valid.

Explanation: The release number of theprecompiled program (package) is notcompatible with the release number of theinstalled version of the database manager.

The precompiled program (package) cannot beused with the current version of the databasemanager. The command cannot be processed.

User Response: Use only programs that areprecompiled with a compatible release level ofthe database manager.

sqlcode: -992

sqlstate: 51008

SQL0993W The new path to the log(newlogpath) in the databaseconfiguration file is not valid.

Explanation: The path to the log file is not validfor one of the following reasons:

v The path does not exist.

v A file with the correct name was found in thespecified path, but it is not a log file for thisdatabase.

v The database manager instance id does nothave permission to access the path or a logfile.

The requested change is not made.

User Response: To change the path to the logfile, submit a database configuration commandwith a valid value.

sqlcode: +993

sqlstate: 01562

SQL0994N Invalid usage of the applicationsavepoint.

Explanation: The application savepoint functionhas been used inconsistently. The program


attempted to perform one of the following:

v Request more than one active savepoint.

v Issue an end savepoint call without an activesavepoint.

v Issue a rollback savepoint call without anactive savepoint.


User Response: Correct the savepoint usage inthe program.

SQL0995W The current path to the log file(logpath) is not valid. The log filepath is reset to the default.

Explanation: The path to the log file is not validfor one of the following reasons:

v The path does not exist.

v A file with the correct name was found in thespecified path, but it is not a log file for thisdatabase.

v The database manager instance id does nothave permission to access the path or log file.

For circular logging, the log file is created in thedefault log path. For archive logging, the nextlog file is created in the default log path. Therequested change is not made.

User Response: To change the path to the logfile, submit a configuration command with avalid value.

sqlcode: +995

sqlstate: 01563

SQL0996N Cannot free pages for an object ina table space.

Explanation: There are corrupted internaldatabase pages or internal logic errors in a tablespace.

User Response: Discontinue use of the object ortable space. Contact IBM service to inspect theobject and the table space.

sqlcode: -996

sqlstate: 58035

SQL0997W General informational messagefor transaction processing. ReasonCode = XA-reason-code.

Explanation: The SQLCODE 997 is only passedbetween components of the database managerand will not be returned to an application. It isused to carry XA return codes for non-errorsituations. The possible reason codes are:

v XA_RDONLY (3) - the transaction branch wasread-only and has been committed.

v 64 - TM database indicates transaction to becommitted on DUOW resynchronization

v 65 - TM database indicates transaction to berolled back on DUOW resynchronization

User Response: No action required.

SQL0998N Error occurred during transactionor heuristic processing. ReasonCode = reason-code Subcode =subcode.

Explanation: An error is detected whenprocessing a distributed transaction. Thetransaction is:

v Running under a Distributed TransactionProcessing environment (such as those fromCICS or other transaction managers).

v Performing heuristic operations.

v Updating multiple nicknames within afederated database, where each updatednickname represents a different data source. Inthis case, one of the data sources has failedduring transaction processing. The reason codereturned in this case is the reason for thefailure at the data source, not the federateddatabase.

The possible reason codes (correspondingX/Open XA reason codes are shown inparenthesis) are:

v 01 - (XAER_ASYNC) asynchronous operationalready outstanding.

v 02 - (XAER_RMERR) a resource manager erroroccurred in the transaction branch.


v 03 - (XAER_NOTA) the XID is not valid.

v 04 - (XAER_INVAL) invalid arguments weregiven. Possible subcodes are:

– 01 - xa_info pointer is invalid, eg. theXAOpen string is null.

– 02 - database name exceeds maximumlength.

– 03 - username exceeds maximum length.

– 04 - password exceeds maximum length.

– 05 - username specified but not a password.

– 06 - password specified but not a username.

– 07 - too many parameters in the xa_infostring.

– 08 - multiple xa_opens generate differentRM ids for the same database name.

– 09 - database name not specified.

– 10 - invalide exe_type.

v 05 - (XAER_PROTO) routine invoked inimproper context.

v 06 - (XAER_RMFAIL) resource managerunavailable.

v 07 - (XAER_DUPID) the XID already exits.

v 08 - (XAER_OUTSIDE) RM doing workoutside global transaction.

v 09 - registration (ax_reg) with the transactionmanager failed. Possible subcodes are:

– 01 - Joining XID not found

– 02 - dynamic library specified in thetp_mon_name configuration parametercould not be loaded.

v 10 - attempted to start a different transactionwhile suspended.

v 12 - unregistering (ax_unreg) with thetransaction manager failed.

v 13 - ax interface failure: ax_reg() andax_unreg() not found.

v 14 - The enlistment for DB2 with the MicrosoftDistributed Transaction Coordinator has failed.MSDTC service may be down. You mustterminate the current transaction.

v 35 - Heuristic operations are invalid fornon-XA database.

v 36 - The XID is not known by the databasemanager.

v 37 - The transaction has already beenheuristically committed.

v 38 - The transaction has already beenheuristically rolled back.

v 39 - The transaction is not an indoubttransaction.

v 40 - Only rollbacks are allowed for thistransaction.

v 41 - Transaction is not heuristically committedon some MPP subordinator nodes because ofnode failure.

v 42 - DB2 Connect XA support is only availableto outbound connections that were establishedusing TCPIP.

v 69 - Database log ID mismatch during DUOWresynchronization.

v 85 - As a result of heuristic processing, thetransaction has partially committed and rolledback.

v 210 - Only heuristic commits are allowed forthis transaction. Some nodes are already incommit state.

v 221 - The version of DBMS on the hostrequires that all applications that participate inthe same XA transaction use the same user IDto connect to the database.

v 222 - The version of DBMS on the hostrequires that all applications that participatethe same XA transaction have the sameCCSID.

v 223 - DB2 Connect XA support is onlyavailable to local clients or remote clients thatuse TCPIP to establish the inbound connection.

v 224 - DB2 Connect XA support is onlyavailable to clients that are at least version 7.1.

v 225 - Operation Invalid in an XA LooselyCoupled Transaction. Possible subcodes are:

– 01 - DDL statements are not allowed.

– 02 - updates and deletes specifying WHERECURRENT OF clause are not allowed.

– 03 - buffered insert operations are notallowed.

v 226 - The transaction has already been rolledback.


v 227 - Heuristic commit should be run on thecoordinator node.

User Response: For reason codes 1 through 8,an entry will be made in the system log becausesometimes the SQLCA cannot be returned to thecaller.

If the error is due to a failed data sourceassociated with a nickname, the location of thefailed data source will always appear infederated server’s system log.

For reason code 4, verify the content of the xaopen string and make necessary corrections.

For reason code 9, subcode 02, ensure that thetp_mon_name configuration parameter containsthe name of the dynamic library in the externalproduct which has the ax_reg() function used fordynamic registration of transactions.

For reason code 14, ensure that the MSDTCservice is active.

For reason code 35, you attempted to perform aheuristic operation against a database that onlyparticipates as a read-only resource manager in aglobal transaction. Examples are any DRDAdatabases such as DB2 on MVS. These type ofnon-XA databases would not have any XAindoubt transactions.

For reason codes 36, 37, and 38, you attemptedto perform an invalid heuristic operation on anindoubt transaction. Either you specified thewrong XID, or a heuristic or resync operationhad taken place since you recorded this XID.Perform a Heuristic Query request to get thecurrent list of indoubt transactions to verify ifyou still need to perform your heuristicoperation.

For reason code 39, the XID specified is for atransaction that has ended and is waiting for thetwo-phase commit process to begin. You can onlyperform heuristic operations on transactions thathave entered the two-phase commit process andbecome indoubt transactions.

For reason code 40, an SQL statement wasattempted under a transaction which has failed.An example of this is to attempt an SQLstatement in a transaction thread that has

successfully registered after a tightly coupledthread participating in the same transaction hasabnormally terminated.

For reason code 41, you can find moreinformation about the problem in theadministration notification log. You need torestart DB2 on the failed nodes. It may benecessary to contact the system administrator forassistance.

For reason code 42, an outbound connection canbe established by modifying the gatewaycatalogs to use TCPIP communication protocol.

For reason code 69, either the transactionmanager (TM) database or the resource manager(RM) database or both are different from theones when the indoubt transaction wasgenerated. In other words, the TM database orRM database names could be referencingdifferent database instances. The log IDmismatch may be caused by the followingreasons:

v The database directory for the TM database atthe RM instance is incorrect.

v The configuration may have been changedafter the indoubt transaction was generated.

v The database may have been dropped andrecreated. In that case, you can only commit orrollback the indoubt transaction heuristically.

For reason code 85, you are updating multipledata sources, and some of the data sources havebeen heuristically rolled back or committed,resulting in the transaction having partiallycommitted and rolled back. With this reasoncode data is now in an inconsistent state, youmust manually check every data source updatedby the transaction to correct the data.

For reason code 210, some of the nodes arealready in commit state. You have to performheuristic commit to resolve the indoubttransaction.

For reason code 221, ensure all applications thatparticipate in the same XA transaction use thesame user ID to connect to the database.


For reason code 222, ensure all applications thatparticipate in the same XA transaction have thesame CCSID.

For reason code 223, modify the application andclient set-up to use local clients, or for remoteclients use TCPIP as the communication protocolto connect to the gateway.

For reason code 224, update the client to version7.1 or later.

For reason code 225, ensure the application didnot contain any of the invalid operations in anXA Loosely Coupled Transaction. Commonapplication server environments where XALoosely Coupled Transaction can be used areIBM Encina Transaction Server, IBM WebSphereApplication Server, Microsoft Transaction Server,and BEA Tuxedo. If you encounter this reasoncode, then you must review your application andensure none of the above actions are performed.

For reason code 226, the transaction has reacheda rollback state, and is now rolled back on thisnode.

For reason code 227, heuristic commit should berun on the coordinator node, see db2diag.log forthe coordinator node number.

General information collection procedure:

If you cannot resolve the problem identified bythe reason codes, record the message number(SQLCODE), reason code, and the optionalsubcode in the message or the SQLCA in thesystem log.

If the failure is from a federated database, youshould also record the location of the failed datasource found in the federated server’s systemlog.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Then, contact your technical servicerepresentative with the following information:


v SQLCODE, embedded reason code, andsubcode

v SQLCA contents (if possible)

v Trace file (if possible)

v Location of the failed data source if the failureis from a federated server.

There might be additional information in theconsole or message logs of the transactionmanager and the database manager.

sqlcode: -998

sqlstate: 58005

SQL1000 - SQL1099

SQL1000N alias is not a valid database aliasname.

Explanation: The alias specified in thecommand or api is not valid. The alias mustcontain 1 to 8 characters (bytes in MBCScountries) and all the characters must be fromthe database manager base character set.

The command cannot be processed.

User Response: Resubmit the command withthe correct alias.

SQL1001N name is not a valid database name.

Explanation: The syntax of the database namespecified in the command is not valid. Thedatabase name must contain 1 to 8 charactersand all the characters must be from the databasemanager base character set.


User Response: Resubmit the command withthe correct database name.

sqlcode: -1001

sqlstate: 2E000


SQL1002N drive is not a valid drive.

Explanation: The drive specified in thecommand is not valid. The drive is a singlecharacter (A to Z) indicating the diskette drive orfixed-disk partition where the database ordatabase directory is located.


User Response: Resubmit the command withthe correct drive.

SQL1003N The password is not valid becausethe syntax is not correct or thepassword does not match thepassword of the specifieddatabase.

Explanation: The length of the password isexpected to be 18 characters or less. However, ifthe password is to be verified for an APPCconversation, it must be 8 characters or less.

User Response: Ensure that the password is notlonger than the limit allowed.

sqlcode: -1003

sqlstate: 28000

SQL1004C There is not enough storage onthe file system to process thecommand.

Explanation: There is not enough storage on thespecified file system to process the command.

In a partitioned database environment onWindows environments, each node in thepartitioned database group must have the exactsame physical hard drive specification (letter)available and useable (must contain useablespace) for the CREATE DATABASE command tosucceed. The physical hard drive letter isspecified in the database manager configuration.If DFTDBPATH is left blank the default will bethe hard drive where DB2 is installed on theinstance owning machine (db2 installation path).


User Response: Choose a different file systemor erase some non-database files from the

specified file system to make space for thedatabase manager functions.

In a partitioned database environment on OS/2and Windows environments, follow thefollowing steps:

v Determine which hard drive specification(letter) is required. The drive letter is specifiedin the error message.

v Determine which node/s of the databasepartition are experiencing the problem. Youcan usually find this information in thedb2diag.log file of the instance owning node.

v Correct the drive problem on the individualnode that is experiencing the problem orchange the drive specification in the databasemanager configuration so that the same driveis available (and has sufficient space) on eachand every node of the partitioned databasegroup.

v re-issue the command.

SQL1005N The database alias name alreadyexists in either the local databasedirectory or the system databasedirectory.

Explanation: The alias name specified hasalready been used. If no alias is specified in thecatalog database command, the database name isused as the alias. When a database is created, thealias name is the same as the database name.

This error may occur on the catalog databasecommand when the alias already exists in thesystem database directory.

On the create database command this error mayoccur in one of the following situations:

v The alias already exists in the system databasedirectory and local database directory.

v The alias already exists in the system databasedirectory but not in the local databasedirectory.

v The alias already exists in the local databasedirectory but not in the system databasedirectory.

User Response: For the catalog databasecommand, uncatalog the alias from the system


database directory and resubmit your originalcommand or catalog the database with adifferent alias name.

For the create database command, do thefollowing operations with respect to the above 3situations:

v Drop the database using the alias name.Resubmit your original command.

v Uncatalog the alias. Resubmit your originalcommand.

v Catalog the alias into the system databasedirectory. Drop the database using the samealias. Resubmit your original command.

SQL1006N The code page code-page of theapplication does not match thecode page code-page of thedatabase.

Explanation: The application could not connectto the database because the active codepage isdifferent from the one that was active when thedatabase was created.


User Response: Exit the current applicationprogram and return to the operating system.Change the code page for the process and restartthe application program.

SQL1007N Error in finding pages for anobject in a table space.

Explanation: There are corrupted internaldatabase pages or internal logic error for a tablespace.

User Response: Discontinue use of the object ortable space. Contact IBM service to inspect theobject and the table space.

sqlcode: -1007

sqlstate: 58034

SQL1008N Invalid table space ID.

Explanation: The table space ID specified doesnot exist. It is either larger than the current

maximum table space ID, or the table space hasbeen dropped.

User Response: Discontinue use of thedatabase. Save the diagnostic information in theerror log and contact IBM service.

sqlcode: -1008

sqlstate: 58036

SQL1009N The command is not valid.

Explanation: The command is not supportedwhen issued on a client-only workstation oragainst remote databases. An example of such acommand is cataloging a local database.



v Issue the specified command from a nonclient-only workstation or from theworkstation where the database resides.

v Verify that the database is cataloged correctly.

v Issue a different command.

SQL1010N type is not a valid type parameter.

Explanation: The type specified in the DatabaseEnvironment command is not valid. It must be’0’ for an indirect database or ’1’ for a remotedatabase.

In addition, on the Unix, OS/2, Windows NT,and Windows 95 platforms, the type can be ’3’for a database that has a DCE global name.


User Response: Resubmit the command with avalid type.

SQL1011N No path was specified in theCATALOG DATABASE commandfor an indirect entry.

Explanation: A CATALOG DATABASEcommand was issued for an indirect entry but nopath was specified. Indirect entries must specifythe path where the database resides.



User Response: Resubmit the command withthe required path or change the type.

SQL1012N No node name was specified inthe CATALOG DATABASEcommand for a remote entry.

Explanation: There was no nodename parameterspecified in the CATALOG DATABASEcommand for a remote entry. Remote entriesmust specify the node name of the database.


User Response: Resubmit the command withthe nodename parameter or a different type.

SQL1013N The database alias name ordatabase name name could not befound.

Explanation: The database name or aliasspecified in the command is not an existingdatabase or the database could not be found inthe (client or server) database directories.

User Response: Ensure that the specifieddatabase name exists in the system databasedirectory. If the database name does not exist inthe system database directory, then the databaseeither does not exist or the database name hasnot been cataloged.

If the database name appears in the systemdatabase directory and the entry type isINDIRECT, ensure that the database exists in thespecified local database directory. If the entrytype is REMOTE, then ensure that the databaseexists and is cataloged on the databasedirectories of the server node.

For CREATE DATABASE with the AT NODEclause, ensure that the database name is in thesystem database directory with an entry type ofINDIRECT and with a catalog node number thatdoes not equal -1.

Federated system users: in addition to the above,verify that the database names specified inSYSCAT.SERVERS are all valid. Correct anySYSCAT.SERVERS entry for which the databasespecified in that entry does not exist.

sqlcode: -1013

sqlstate: 42705

SQL1014W There are no more entries in thedirectory, file, or list beingscanned.

Explanation: The scan of the directory, file, orlist is finished.


SQL1015N The database must be restartedbecause the previous session didnot conclude normally.

Explanation: The database must be restartedbecause of an abnormal termination of theprevious session (for example, a power failure).


User Response: On receipt of this message(SQLCODE), an application can post a messagewarning the user that it takes time to recover thedatabase. To restart the database, issue theRESTART DATABASE command. In a partitioneddatabase server environment, the command mustbe issued on all nodes.

sqlcode: -1015

sqlstate: 55025

SQL1016N The local_lu alias name specifiedin the CATALOG NODEcommand is not valid.

Explanation: The local logical unit ( local_lu)alias specified in the CATALOG NODEcommand is not permitted. The local logical unitalias is the local SNA logical unit alias and mustbe 1 to 8 characters and cannot contain blankcharacters.


User Response: Verify that the alias is apermitted logical unit name. Verify the charactersused in the name. Resubmit the command with avalid logical unit name.


SQL1017N The mode parameter modespecified in the CATALOG NODEcommand is not valid.

Explanation: The mode specified in theCATALOG NODE command is not permitted.

The mode parameter identifies thecommunications profile the CommunicationsManager uses to set up a session. The modemust be 1 to 8 characters. Valid characters areuppercase or lowercase A through Z, 0 through9, #, @, and $. The first character must bealphabetic. The system changes lowercasecharacters to uppercase.


User Response: Verify that the name is apermitted mode name. Verify the characters usedin the name. Resubmit the command with acorrect mode.

SQL1018N The node name name specified inthe CATALOG NODE commandalready exists.

Explanation: The node name specified in thenodename parameter of the CATALOG NODEcommand is already cataloged in the nodedirectory on this file system.


User Response: If the nodename parameter istyped correctly, continue processing.

Uncatalog the cataloged node in the nodedirectory if the node cataloged information is nolonger valid and resubmit the command. If thenode cataloged information is valid, define anew node name and resubmit the commandusing the new node name.

SQL1019N The node name name specified inthe command is not valid.

Explanation: The node name specified in thecommand is not valid. The node name may be 1to 8 characters and all of the characters must befrom the database manager base character set.The specified node name cannot be the same asthe local instance name.


User Response: Ensure the node name is notthe same as the local instance name bydisplaying the value of the DB2INSTANCEenvironment variable. On UNIX operatingsystems, display the DB2INSTANCEenvironment variable by entering the followingcommand:

echo $DB2INSTANCE

On Windows and OS/2 operating systems,display the DB2INSTANCE environment variableby entering the following command:

echo %DB2INSTANCE%

Resubmit the command with the correct nodename.

SQL1020C The node directory is full.

Explanation: The node directory cannot holdany more entries.


User Response: Uncatalog any unnecessaryentries in the node directory.

SQL1021N The node name name specified inthe UNCATALOG NODEcommand was not found.

Explanation: The nodename specified in thecommand could not be found in the nodedirectory.


User Response: If the nodename parameter iscorrect, the node may already have beenuncataloged, and processing can continue.Otherwise, resubmit the command with thecorrect node name.

SQL1022C There is not enough memoryavailable to process the command.

Explanation: Not enough random accessmemory (RAM) is available to process thecommand.


If a remote procedure was invoked, the remoteprocedure may use a local variable space that islarger than the allowable maximum (4K).

If the statement involves a user-defined function(UDF), the memory set controlled by theudf_mem_sz database manager configurationparameter may be larger than the memoryavailable.


User Response: Stop the application. Possiblesolutions include:

v Change the MEMMAN NO SWAP, NO MOVEoption in the CONFIG.SYS file to SWAP,MOVE.


v Decrease the values of the configurationparameters that define allocation of memory,including udf_mem_sz if UDFs are involved inthe failing statement.

v Install more random access memory (RAM).

v If a remote procedure was invoked, ensurethat the remote procedure uses a local variablespace that is less than or equal to 4K.

v If you are using Remote Data Services,increase the Remote Data Services heap size(rsheapsz) in the server and clientconfiguration because at least one block isused per application.

v On OS/2 systems, change PROTECT toNOPROTECT in the MEMMAN statement ofthe CONFIG.SYS file. This will make morememory space available to applications, butdisables certain protection features of OS/2.Refer to the OS/2 documentation for moreinformation and to determine if this will beappropriate for your environment.

v On OS/2 systems, increase the value of themin_priv_mem database manager configurationparameter. This will cause the databasemanager to reserve more private memoryspace at db2start time.

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

sqlcode: -1022

sqlstate: 57011

SQL1023C The communications conversationfailed.

Explanation: An error occurred in thecommunications conversation.


User Response: Retry the original command. Ifthe error persists, contact your communicationsadministrator.


sqlcode: -1023

sqlstate: 08001

SQL1024N A database connection does notexist.

Explanation: There is no connection to adatabase. Other SQL statements cannot beprocessed unless an SQL CONNECT waspreviously executed.


User Response: If the error occurred whendisconnecting from the database, continueprocessing. If the error occurred on another SQLstatement, issue an SQL CONNECT statementand resubmit the command or statement.

sqlcode: -1024

sqlstate: 08003

SQL1025N The database manager was notstopped because databases arestill active.

Explanation: The stop database managercommand cannot be processed if there are anyapplications connected to databases undercontrol of the database manager, or if anydatabases have been activated.

No action is taken.

User Response: Usually no action is required.To stop the database manager, all active


applications must disconnect from all thedatabases they are using. Alternatively, the usercan use the FORCE command to forceapplications to disconnect, and the DEACTIVATEcommand to deactivate the database.

SQL1026N The database manager is alreadyactive.

Explanation: A start database managercommand is already processed.


User Response: Because the command isalready processed, the application may continueprocessing.

SQL1027N The node directory cannot befound.

Explanation: The list node directory commandcannot be processed because the node directorycould not be found.


User Response: Issue a CATALOG NODEcommand with the appropriate parameters andresubmit the current command.

SQL1029N The partner_lu alias namespecified in the CATALOG NODEcommand is not valid.

Explanation: The partner_lu alias specified inthe CATALOG NODE command was notspecified or contains characters that are notvalid. The partner_lu alias is the partner SNAlogical unit alias and must be 1 to 8 charactersand must not contain blank characters.


User Response: Examine the partner_lu for atyping error. Verify that the alias is a permittedlogical unit name. Verify the characters used inthe alias. Resubmit the command with a correctpartner_lu.

SQL1030C The database directory is full.

Explanation: Either the system databasedirectory or the local database directory cannothold any more entries.


User Response: Uncatalog any unnecessaryentries in the directory. Create new databases onanother file system if the local database directoryis full.

SQL1031N The database directory cannot befound on the indicated filesystem.

Explanation: The system database directory orlocal database directory could not be found. Adatabase has not been created or it was notcataloged correctly.


User Response: Verify that the database iscreated with the correct path specification. TheCatalog Database command has a pathparameter which specifies the directory wherethe database resides.

sqlcode: -1031

sqlstate: 58031

SQL1032N No start database managercommand was issued.

Explanation: The start database managercommand has not been processed. It must beprocessed before a stop database manager, anySQL statement, or utility can be issued.


User Response: Issue a start database managercommand and resubmit the current command.

If using multiple logical nodes, ensure theDB2NODE environment variable is set correctly.The DB2NODE environment variable indicatesthe node the application will attempt to connectto. DB2NODE must be set to the node number ofone of the nodes defined on the same host as theapplication.


sqlcode: -1032

sqlstate: 57019

SQL1033N The database directory cannot beaccessed because it is being used.

Explanation: The database directory cannot beaccessed if it is currently being updated. Also,the directory cannot be accessed for update if itis already being accessed for any reason. Thissituation could exist with either the systemdatabase directory or the local database directory.


User Response: Wait until the access hascompleted, then resubmit the command.

sqlcode: -1033

sqlstate: 57019

SQL1034C The database is damaged. Theapplication has been disconnectedfrom the database. Allapplications processing thedatabase have been stopped.

Explanation: Damage has occurred to thedatabase. It cannot be used until it is recovered.All applications connected to the database havebeen disconnected and all processes runningapplications on the database have been stopped.


User Response: Issue a RESTART DATABASEcommand to recover the database. If theRESTART command consistently fails, you maywant to restore the database from a backup. In apartitioned database server environment, checkthe syslog to find out if the RESTART commandfails because of node or communication failuresbefore restoring the database from a backup. Ifso, ensure the database manager is up andrunning and communication is available amongall the nodes, then resubmit the restartcommand.

If you encountered this error during roll-forwardprocessing, you must restore the database from abackup and perform roll-forward again.

Note that in a partitioned database environment,the RESTART database command is run on aper-node basis. To ensure that the database isrestarted on all nodes, use the command:

db2_all db2 restart database<database_name>

This command may have to be run several timesto ensure that all in-doubt transactions have beenresolved.

If you are installing the sample database, drop itand install the sample database again.

sqlcode: -1034

sqlstate: 58031

SQL1035N The database is currently in use.

Explanation: One of the following conditionsexists:

v Exclusive use was requested, but the databaseis already in use as a shared database byanother user (in the same process).

v Exclusive use was requested, but the databaseis already in use as an exclusive database.(Two different processes are trying to accessthe same database.)

v The maximum number of connections to thedatabase has been reached.

v The database is being used by another user onanother system.

v Activate/Deactivate database is in progress.



v Resubmit the command later when thedatabase is not in use.

v Change the authorization to match the currentuser or wait until the database is not in use.

v Wait until the database is not in exclusive use.

v Wait until other users on another system havedisconnected from the database.

sqlcode: -1035


sqlstate: 57019

SQL1036C An I/O error occurred whileaccessing the database.

Explanation: At least one database file has anI/O error:

v The system cannot open, read from, or write toa database file.

v The system cannot create the database becausean error occurred while the system wascreating a database file or a directory for thedatabase.

v The system cannot drop the database becausean error occurred while the system wasdeleting a database file or a directory for thedatabase.

v The system cannot create the database becausean interrupt was received while the systemwas creating or deleting a database file or adirectory for the database.

v The system cannot locate the databasesubdirectory or database configuration fileduring connect.

The database cannot be used.

User Response: If the error occurred during theprocessing of a database, resubmit the command.If the error continues, restore the database from abackup version.

If the error occurred during CREATE DATABASEor DROP DATABASE, a subsequent CREATEDATABASE or DROP DATABASE commandattempts to erase files and directories left fromthe unsuccessful CREATE DATABASE or DROPDATABASE command.


If the error occurred while trying to connect to adatabase, get a trace and call IBM support for thepossibility of recovering the database.

sqlcode: -1036

sqlstate: 58030

SQL1037W The Node directory is empty.

Explanation: An attempt was made to read thecontents of the node directory, but no entriesexisted.


sqlcode: +1037

sqlstate: 01606

SQL1038C An I/O error occurred whileaccessing the node directory.

Explanation: The node directory could not beaccessed because of an I/O error.


User Response: Resubmit the command. If theerror continues, remove the node directory(sqlnodir under the sqllib directory) andrecatalog the node names on the network.

sqlcode: -1038

sqlstate: 58031

SQL1039C An I/O error occurred whileaccessing the database directory.

Explanation: Either the system databasedirectory or the local database directory cannotbe accessed. This error may occur not only whenthe system is cataloging or uncataloging adatabase but also when the system is accessing adatabase that is cataloged in the directory.



v If the error occurred on a diskette system,verify that the correct diskette is in the driveand ready to use. Verify that it is notwrite-protected.

v If the database directory is damaged, restorethe databases that were cataloged there frombackup versions and catalog them.



sqlcode: -1039

sqlstate: 58031

SQL1040N The maximum number ofapplications is already connectedto the database.

Explanation: The number of applicationsconnected to the database is equal to themaximum value defined in the configuration filefor the database.


User Response: Wait for other applications todisconnect from the database. If moreapplications are required to run concurrently,increase the value for maxappls. After allapplications disconnect from the database andthe database is restarted, the new value takeseffect.

sqlcode: -1040

sqlstate: 57030

SQL1041N The maximum number ofconcurrent databases have alreadybeen started.

Explanation: The application attempted to startan inactive database but the number of activedatabases already equals the maximum valuedefined in the system configuration file.


User Response: Wait for one of the databases tobecome inactive. If more databases are requiredto be active at the same time, increase the valuefor numdb. The new value takes effect after thenext successful database manager start.

sqlcode: -1041

sqlstate: 57032

SQL1042C An unexpected system erroroccurred.

Explanation: A system error occurred. Onepossible reason for this error is that the database

manager is not installed correctly or theenvironment is not set up correctly.

On OS/2, while trying to start the databasemanager, a very common reason for this error isa corrupted NET.ACC file.


User Response: If the error occurred on OS/2while trying to start the database manager, andthe NET.ACC file is suspected, replace theNET.ACC files on the system with those ondiskette 1 of the DB2 for OS/2 installationdiskettes.

If the error occurred while trying to connect to adatabase, get a trace (instructions below) and callIBM support.

If the problem falls outside of the abovesuggestions, ensure that the system time anddate is correctly set, and make sure your systemhas enough memory and swapping/pagingspace available.

Resubmit the current command.

If the error continues, stop the database managerand restart it.

If the error still continues, reinstall the databasemanager.


Required information:


v SQLCODE or message number



Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the problem determination guide forprocedures to follow to identify the failing datasource). If the problem is with a data sourcefollow the problem determination procedures forthat data source.


sqlcode: -1042

sqlstate: 58004

SQL1043C The database manager could notinitialize the system catalogs.Error error was returned.

Explanation: The CREATE DATABASEcommand failed while initializing the systemcatalogs.

User Response: Record the message number(SQLCODE) and error in this message.


v Environment: Application

v Required information:

– Problem description

– SQLCODE or message number and erroridentifier

– SQLCA contents if possible

– Trace file if possible.

SQL1044N Processing was cancelled due toan interrupt.

Explanation: The user may have pressed theinterrupt key sequence.

Processing is stopped.


User Response: Continue processing to handlethe interrupt.


If starting the database manager, issue a db2stopbefore issuing any db2 commands.

sqlcode: -1044

sqlstate: 57014

SQL1045N The database was not foundbecause it was not catalogedcorrectly.

Explanation: An indirect entry in the databasedirectory points to another non-HOME entry.


User Response: Verify the entries in all theassociated database directories with the directoryscan commands.

sqlcode: -1045

sqlstate: 58031

SQL1046N The authorization ID is not valid.

Explanation: The authorization specified atlogon is not valid for either the data source orthe database manager. One of the followingoccurred:

v The authorization contains more than 30characters for Windows platforms or 8characters for other platforms.

v The authorization contains characters not validfor an authorization. Valid characters are Athrough Z, a through z, 0 through 9, #, @ and$.

v The authorization is PUBLIC or public.

v The authorization begins with SYS, sys, IBM,ibm, SQL or sql.

v The authorization violates some datasource-specific naming convention.


User Response: Log on with a validauthorization ID.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) and usean authorization ID valid for that data source.

sqlcode: -1046

sqlstate: 28000


SQL1047N The application is alreadyconnected to another database.

Explanation: An application cannot create adatabase while connected to another database.

Binding a bind file to one database while alreadyconnected to another database is not permitted.


User Response: Disconnect from the activedatabase and resubmit the command.

SQL1048N The use parameter parameter in theSTART USING DATABASE orCONNECT TO command is notvalid. it must be an S for sharedaccess, an X for exclusive use oran N for exclusive use at singlenode. For DB2 Connectconnections, only S is supported.N is only supported in MPPconfiguration.

Explanation: The use parameter in the STARTUSING DATABASE or CONNECT TO commandmust be either an S for shared or an X forexclusive use. If connecting to a database usingDB2 Connect, only shared access is allowed.Mnemonic equates for these values are providedin the SQLENV.H file.


User Response: Resubmit the command with avalid use parameter (preferably from themnemonic equates).

SQL1049C The application state is in error.The database connection has beenlost.

Explanation: The connection to the database hasbeen lost.


User Response: Issue a CONNECT RESETstatement.

SQL1050N The database cannot beuncataloged because it is a homedatabase.

Explanation: The database specified in theUNCATALOG DATABASE command is a homedatabase. Home databases cannot be uncatalogedbecause their directory entries are deleted whenthe database is dropped.


User Response: Continue processing if thedatabase name was specified correctly.

SQL1051N The path path for the databasedirectory does not exist.

Explanation: The path specified in the databasedirectory parameter of the command or in thedatabase directory entry is not valid. There is nofile system with that name.


User Response: Resubmit the command withthe correct path for the database directory.

sqlcode: -1051

sqlstate: 57019

SQL1052N The database path path does notexist.

Explanation: The path specified in the pathparameter of the command is not valid. There isno path with that name.

In a partitioned database environment onWindows environments, each node in thepartitioned database group must have the exactsame physical hard drive specification (letter)available and useable (must contain useablespace) for the CREATE DATABASE command tosucceed. The physical hard drive letter isspecified in the database manager configuration.If DFTDBPATH is left blank the default will bethe hard drive where DB2 is installed on theinstance owning machine (db2 installation path).


User Response: Resubmit the command with


the correct database path.






SQL1053N An interrupt is already beingprocessed.

Explanation: The system is currently processingan interrupt so another interrupt is not honored.

The interrupt request is ignored.

User Response: Wait until the current interruptprocessing finishes and resubmit the command.

SQL1054N A COMMIT is in progress andcannot be interrupted.

Explanation: The system is currently processinga COMMIT. The user entered an interrupt keysequence.



User Response: Wait until COMMIT is finishedand resubmit the request.

SQL1055N A ROLLBACK is in progress andcannot be interrupted.

Explanation: The system is currently processinga ROLLBACK. The user entered an interrupt keysequence.



User Response: Wait until ROLLBACK isfinished and resubmit the request.

SQL1056N There are already eight databasedirectory scans open.

Explanation: Eight database directory scans inthis process are already open. No more thaneight open scans are allowed.


User Response: Issue one or more CLOSEDIRECTORY SCAN commands and resubmit thecommand.

sqlcode: -1056

sqlstate: 54029

SQL1057W The system database directory isempty.

Explanation: An attempt was made to read thecontents of the system database directory, but noentries existed.


sqlcode: +1057

sqlstate: 01606

SQL1058N The handle parameter in theDirectory Scan command is notvalid.

Explanation: The handle parameter specified inthe Directory Scan command is not valid. Thehandle must be the one returned from the OPENDIRECTORY SCAN or the OPEN NODEDIRECTORY SCAN command.



User Response: Resubmit the command with avalid handle parameter.

SQL1059N A Get Next command cannot beprocessed because no Open Scancommand was issued.

Explanation: A directory scan command wasissued before the scan was opened.


User Response: Issue an OPEN DIRECTORYSCAN or OPEN NODE DIRECTORY SCANcommand and resubmit the current command.

SQL1060N User authorization-ID does not havethe CONNECT privilege.

Explanation: The specified authorization doesnot have the CONNECT privilege to access thedatabase. The CONNECT privilege must begranted before the user can connect to adatabase.

Federated system users: this situation can also bedetected by the data source


User Response: Contact the systemadministrator or database administrator for thedatabase and request a GRANT CONNECT forthe authorization ID. Resubmit the command.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andensure that correct privileges have been grantedfor that data source.

sqlcode: -1060

sqlstate: 08004

SQL1061W RESTART completed successfully,but indoubt transactions existagainst the database.

Explanation: A RESTART was successfullycompleted, except indoubt transactions were

discovered. The database is usable, but if theindoubt transactions are not resolved before thelast connection to the database is dropped, thenthe database will again require a RESTARTbefore it can be used.

User Response: Either resolve the indoubttransactions, or be prepared to RESTART thedatabase whenever you wish to use it. If thetransaction manager (TM) that was using thedatabase (in an XA/DTP environment) isavailable, then the administrator should instructthe TM to resolve the indoubt transactions.Alternatively, with great caution, theadministrator can use the CLP to heuristicallycomplete the transactions.

Note that in a partitioned database serverenvironment, the RESTART database command isrun on a per-node basis. In order to ensure thatthe database is restarted on all nodes, use thefollowing command:

db2_all db2 restart database<database_name>

Issuing the above command will resolve anyin-doubt transactions if all nodes are operational.

This command may have to be run several timesto ensure that all in-doubt transactions have beenresolved.

SQL1062N The database path path was notfound.

Explanation: The database path parameterspecified in the command does not exist. If thepath is not specified, the default path defined inthe system configuration file is used, and it doesnot exist.

In a partitioned database environment onWindows environments, each node in thepartitioned database group must have the exactsame physical hard drive specification (letter)available and useable (must contain useablespace) for the CREATE DATABASE command tosucceed. The physical hard drive letter isspecified in the database manager configuration.If DFTDB is left blank the default will be thehard drive where DB2 is installed on the instance


owning machine (db2 installation path).


User Response: Verify the path or the defaultpath and make sure they exist in the system.Resubmit the command.






SQL1063N The start database managerprocessing was successful.

Explanation: The command to start thedatabase manager completed successfully.

SQL1064N The stop database managerprocessing was successful.

Explanation: The command to stop the databasemanager completed successfully.

SQL1065W The database was created, but anerror occurred on one or morebind files in list list-name. Thefollowing files were not bound:list.

Explanation: One or more utilities were notbound to the database. The list file list-namecontains a list of the bind files. The numbers inlist indicate the relative positions of the unboundfiles in the list file.

The listed utility bind files are not bound to thenewly created database.

User Response: The user may bind theindicated utilities to the database. The formatoption must not be used on the binder call.

SQL1066N DB2START processing wassuccessful. IPX/SPX protocolsupport was not successfullystarted.

Explanation: The IPX/SPX protocol supportwas not successfully started. Remote clientscannot use IPX/SPX to connect to the server.Possible causes are:

v The workstation is not logged in to theNetWare file server.

v The workstation does not have authority tocreate an object in the NetWare file serverbindery.

v Another database manager on the network isusing the same object name specified in thedatabase manager configuration file.

User Response: Ensure that the workstation islogged in to the NetWare file server, and hassufficient authority to create an object in thebindery at the file server. The user must belogged in as SUPERVISOR or equivalent. Alsoensure that the object name specified in thedatabase manager configuration file is unique forall database managers in the network. Make anycorrections, run DB2STOP, and then runDB2START again.

If the problem continues, at the operating systemcommand prompt type DB2TRC ON -L0X100000. Run DB2START again, then at thecommand prompt, type DB2TRC DUMPfilename to save the trace information. To turntrace off, type DB2TRC OFF. Contact your servicecoordinator with the trace information.


SQL1067N DB2STOP processing was notsuccessful. IPX/SPX protocolsupport was not successfullystopped.

Explanation: The IPX/SPX protocol supportwas not successfully stopped. Possible causesare:

v The workstation is not logged in to theNetWare file server.

v The workstation does not have authority todelete an object in the NetWare file serverbindery.

User Response: Ensure that the workstation islogged in to the NetWare file server, and hassufficient authority to delete an object in thebindery at the file server. The user must belogged in as SUPERVISOR or equivalent. Makeany corrections, and run DB2STOP again.

If the problem continues, at the operating systemcommand prompt type DB2TRC ON -L0X100000. Run DB2STOP again, then at thecommand prompt, type DB2TRC DUMPfilename to save the trace information. To turntrace off, type DB2TRC OFF. Contact your servicecoordinator with the trace information.

SQL1068N The domain that owns the user IDuser-ID for the CONNECT orATTACH statement is not definedin the DB2DOMAINLISTenvironment variable.

Explanation: A user ID in a CONNECT TO orATTACH TO statement does not belong to adomain defined in the DB2DOMAINLISTenvironment variable.

User Response: Specify the name of the domainwhich owns the user ID in theDB2DOMAINLIST environment variable byusing the DB2SET command.

sqlcode: -1068

sqlstate: 08004

SQL1069N The database name is not a homedatabase.

Explanation: The database is not a localdatabase. A local database is cataloged as indirectin the system database directory and this entryreferences a home entry in the local databasedirectory on the same node. Remote databasescannot be dropped.


User Response: If the specified database namewas incorrect, resubmit the command with thecorrect database name. If the specified databasename was correct and the intent is to remove thedatabase name from the database directory, usethe UNCATALOG DATABASE command.

SQL1070N The address of the database nameparameter is not valid.

Explanation: The application program used anaddress that is not valid for the database nameparameter. Either the address points to anunallocated buffer or the character string in thebuffer does not have a null terminator.


User Response: Correct the application programso a correct address is used and the input stringis null terminated.

SQL1071N The address of the database aliasname parameter is not valid.

Explanation: The application program used anaddress that is not valid for this parameter.Either the address points to an unallocated bufferor the character string in the buffer does nothave a null terminator.


User Response: Ensure that a valid address isused in the application program and the inputstring is null terminated.


SQL1072C The database manager resourcesare in an inconsistent state. thedatabase manager may have beenincorrectly terminated, or anotherapplication may be using systemresources in a way which conflictswith the way the databasemanager uses system resources.System resource cleanup may berequired.

Explanation: The request failed because thedatabase manager resources are in aninconsistent state. This can occur if:

v DB2 was incorrectly terminated (onUNIX-based systems, for example, this mayoccur if the processes were terminated withthe ″kill″ command, rather than the stopdatabase manager command).

v Another application or user may haveremoved the database manager resources (onUNIX-based systems, for example, a user withsufficient privilege may have accidentallyremoved an Interprocess Communication (IPC)resource owned by the database manager,using the ″ipcrm″ command).

v Another application’s use of system resourcesconflicts with the database manager’s use ofsystem resources (on UNIX-based systems, forexample, another application may be using thesame keys that the database manager uses forcreating IPC resources).

v Another instance of the database manager maybe using the same resources. This could occuron UNIX-based systems if the two instancesare on different file systems and the sqllibdirectories happen to have the same i-node(i-nodes are used to get the IPC keys).

User Response: Resource cleanup may berequired:

v Remove all the database manager processesrunning under the instance id (on UNIX-basedsystems, you can use ″ps -eaf -u <instance id>| grep db2″ to list all the database managerprocesses running under the instance id, andthe ″kill -9 <process id>″ command to removethem).

v Ensure that no other application is runningunder the instance id, and then remove allresources owned by the instance id (onUNIX-based systems, you can use the ″ipcs |grep <instance id>″ command to list all IPCresources owned by the instance id, and the″ipcrm -[q|m|s] <id>″ command to removethem).

v If there is another instance of the databasemanager running, there may be an inodeconflict. This is probably the case if you findthat two instances cannot be active at the sametime, but can be started individually. It isnecessary to change the inode being used togenerate IPC keys for one of the instances.

For single-node instances, perform thefollowing as the instance owner from the sqllibdirectory:

– delete the .ftok file

rm .ftok

– create a new .ftok file

touch .ftok

For multi-node instances, perform thefollowing as the instance owner:

– create another directory at the same level assqllib

– move everything from under sqllib to thenew directory

– delete sqllib

– rename the new directory to sqllib

v Restart the database manager instance.

SQL1073N The node directory releasenumber is not correct.

Explanation: The node directory release numberdoes not match the product expected releasenumber. The node directory could be from aprevious release.

User Response: Re-catalog all the node entriesand try the command again.


SQL1074N The address of the passwordparameter is not valid.




SQL1075N The address of the databasecomment parameter is not valid.




SQL1076N The address of the countparameter is not valid.

Explanation: The application program used anaddress that is not valid for the count parameter.


User Response: Ensure that a valid address isused in the application program.

SQL1077N The address of the handleparameter is not valid.

Explanation: The application program used anaddress that is not valid for the handle parameter.



SQL1078N The address of the bufferparameter is not valid.

Explanation: The application program used anaddress that is not valid for the buffer parameter.



SQL1079N The address of the nodenameparameter is not valid.

Explanation: The application program used anname parameter address that is invalid. Eitherthe address points to an unallocated buffer or thecharacter string in the buffer does not have anull terminator.



SQL1080N The address of the local_lu nameparameter is not valid.

Explanation: The application program used anaddress that is not valid for the local_lu nameparameter. Either the address points to anunallocated buffer or the character string in thebuffer does not have a null terminator.



SQL1081N The address of the partner_luparameter is not valid.

Explanation: The application program has usedan address that is not valid for the partner_luparameter. Either the address points to anunallocated buffer or the character string in thebuffer does not have a null terminator.


User Response: Ensure that a valid address is


used in the application program and the inputstring is null terminated.

SQL1082N The address of the modeparameter is not valid.

Explanation: The application program has usedan address that is not valid for the modeparameter. Either the address points to anunallocated buffer or the character string in thebuffer does not have a null terminator.



SQL1083N The database description blockcannot be processed, reasoncode=reason-code.

Explanation: The application issued a CREATEDATABASE command, but the databasedescriptor block (DBDB) could not be processedfor one of the following reason codes:

v The address of the DBDB is not valid (reasoncode 01).

v The value of the SQLDBDID field of the DBDBis not valid (reason code 02). It should be setto the value SQLDBDB1.

v The value of the SQLDBCSS field of the DBDBis not valid (reason code 04).


User Response: Correct the error and resubmitthe command.

SQL1084C Shared memory segments cannotbe allocated.

Explanation: The database manager could notallocate segments while processing a DatabaseEnvironment command or an SQL CONNECTstatement.

The dbheap parameter may be too small.

User Response: Record the message number(SQLCODE). The cause of this error may be

insufficient memory resources either for thedatabase manager or the environment whereoperation of the database manager is beingattempted. Validate that sufficient memoryresources are available to satisfy the databasemanager requirements. You may also close anybackground processes that do not need to beactive.

If sufficient memory resources exist and theproblem continues, invoke the Independent TraceFacility at the operating system commandprompt. Contact your technical servicerepresentative with the following information:






sqlcode: -1084

sqlstate: 57019

SQL1085N The application heap cannot beallocated.

Explanation: The application could not connectto the database because the database managercould not allocate the number of applicationheap 4K pages specified in the databaseconfiguration file. The system is out of 4K pages.The command cannot be processed.

User Response: Possible solutions are:

v Lower the size of the application heap(applheapsz) in the database configuration file.

v Reduce the maximum number of applicationsin the database configuration file.


v Install more memory.

sqlcode: -1085

sqlstate: 57019


SQL1086C An operating system error erroroccurred.

Explanation: The command received an errorfrom the operating system that prevents furtherprocessing.


User Response: Refer to the operating systemuser publications to determine the nature of theerror.

SQL1087W The database was created, but anerror occurred while opening thelist file name. The utilities are notbound to the database.

Explanation: CREATE DATABASE could notopen the list file containing the list of utility bindfiles. The list file should be located in the bndsubdirectory of the sqllib subdirectory.

The utility bind files are not bound to the newlycreated database.

User Response: Bind the utilities to thedatabase. Do not use the format option on thebinder call.

SQL1088W The database was created, but anerror occurred while binding theutilities. The utilities are notbound to the database.

Explanation: CREATE DATABASE or MIGRATEDATABASE could not bind the utility bind filesto the database.

The utility bind files are not bound to the newlycreated or migrated database.


SQL1089W The database was created, but thebinding of the utilities wasinterrupted. The utilities are notbound to the database.

Explanation: CREATE DATABASE wasinterrupted while binding the utilities to the

database. The interrupt key sequence may havebeen pressed.

The utility bind files are not bound to the newlycreated database.


SQL1090C The release number of theprecompiled application programor utility is not valid.

Explanation: The release number of theprecompiled application program or utility is notcompatible with the release number of theinstalled version of the database manager.

The error will also occur if the applicationprogram is using down-level database managerlibraries or DLLs while accessing the installedversion of the database manager configurationfile.


User Response: Verify that there is no olderversion of the database manager libraries orDLLs that will be picked up for your applicationprocessing.

If the problem persists, repeat the precompileprocess with the current database manager. Useonly application programs precompiled with acompatible release level of the database manager.

SQL1091C The release number of thedatabase is not valid.

Explanation: The release number of thedatabase is not compatible with the releasenumber of the installed version of the databasemanager. This can be the release number whenthe database was created, the release numberwhen the database was last migrated, or thehighest version, release, modification, and fixpaklevel defined in the catalog.

The command cannot be processed. If the erroroccurred during a Migrate or Restore, you areattempting to migrate or restore an incompatiblerelease of database. If the error occurred on the


first connection after removing a fixpak, you areattempting to connect to a database that isdefined to use a higher level of databasemanager code.

User Response: Use only databases createdwith a compatible release of database manager. Ifthe error occurred during a Migrate or Restore,you must first migrate the database to a releasewhich can be migrated by the current release ofthe database manager. If the error occurred onthe first connection after removing a fixpak, thedatabase should be restored from a backup priorto using the utility to update the database to thefixpak level.

sqlcode: -1091

sqlstate: 08004

SQL1092N authorization-ID does not have theauthority to perform the requestedcommand.

Explanation: The user attempted to execute acommand or operation without having theproper authority for that command or operation.



User Response: Log on as a user with thecorrect authority and retry the failed commandor operation. Correct authorities may includeSYSADM, SYSCTRL, SYSMAINT, and DBADM.DBADM is granted on databases and all otherauthorities are determined by membership in thegroups defined in the database managerconfiguration (eg. if sysctrl_group in the databasemanager configuration file is defined as ’beatles’,then you must belong to the group ’beatles’ tohave SYSCTRL authority). Refer to the CommandReference or the SQL Reference for the listing ofrequired authorities for the attempted commandor operation.

If you are using Kerberos authentication in aWindows environment, ensure that you log on tothe machine using a domain account. Onlydomain users can use Kerberos authentication ina Windows 2000 environment.

If you are using LDAP support, ensure that youor the DB2 Connect gateway has the authority toperform the CATALOG DATABASE, NODE andDCS DATABASE commands. Invoke thecommand ″UPDATE DBM CFG USINGCATALOG_NOAUTH YES″ at the client or thegateway to correct the problem.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andensure that the authorization id specified has theproper authority on that data source.

Contact the System Administrator for authorityrequest assistance. Do not attempt to execute thecommand without appropriate authorization.

SQL1093N The user is not logged on.

Explanation: A user must be logged on beforeany command requiring authorization can beprocessed. Possible causes for this error include:

v Unable to get a user ID.

v An unexpected operating system erroroccurred when attempting to log on.

v The application is running in a backgroundprocess.

v The user cancelled an attempted logon.


User Response: Log on with a valid user IDand resubmit the command. If several concurrentprocesses are attempting to log on, wait a fewseconds and retry the logon procedure.

sqlcode: -1093

sqlstate: 51017

SQL1094N The node directory cannot beaccessed because it is beingupdated.

Explanation: The node directory cannot bescanned or used while it is being updated. Also,the directory cannot be accessed for update if itis already being accessed for any reason.



User Response: Resubmit the command afterthe update is finished.

sqlcode: -1094

sqlstate: 57009

SQL1095N There are already eight nodedirectory scans open.

Explanation: Eight node directory scans arealready open in this process and no more thaneight are allowed.


User Response: Issue one or more CLOSENODE DIRECTORY SCAN commands. Resubmitthe command.

sqlcode: -1095

sqlstate: 54029

SQL1096N The command is not valid for thisnode type.

Explanation: A command was issued on a nodethat does not support the command, or thesystem environment was found to be set upincorrectly for this node type. For example, adatabase was cataloged as LOCAL on a clientnode.


User Response: Verify that the command andparameters are correct for the node type. Alsoverify that the environment where the commandis to be processed is correct. Resubmit thecommand.

SQL1097N The node name was not found inthe node directory.

Explanation: Either the node name listed in thedatabase directory for a remote database or thenode name specified on an attach command wasnot cataloged in the node directory.



User Response: Verify that the node name listedin the database directory or as the object of theattach command is cataloged in the nodedirectory. If the node is not listed in the nodedirectory, submit a CATALOG NODE command.

Federated system users: in addition to the actionslisted above, also verify that the node nameslisted in all the SYSCAT.SERVERS entries arecorrect. If the node is not listed in the nodedirectory and the server is a member of the DB2family, issue a CATALOG NODE command forthat node.

sqlcode: -1097

sqlstate: 42720

SQL1098N The application is alreadyconnected to this database.

Explanation: A connection to a database wasrequested but the application is alreadyconnected to the specified database.


User Response: No action is necessary.

sqlcode: -1098

sqlstate: 53056

SQL1099N The diskette is write-protected.

Explanation: A write operation was attemptedto a database residing on a write-protecteddiskette.


User Response: Verify you are using the correctdiskette. Remove protection from the diskette, ifnecessary.

SQL1100 - SQL1199


SQL1100W The node name name specified inthe Catalog Database commandhas not been cataloged in theNode Directory.

Explanation: The Catalog Database commandspecified node name name but that is notcataloged in the node directory. The node namemust be cataloged before the remote databasecan be used.

The CATALOG DATABASE command completedsuccessfully.

User Response: Issue a CATALOG NODEcommand.

SQL1101N Remote database name on nodenode-name could not be accessedwith the specified authorizationid and password.

Explanation: A connection to the remotedatabase name on node node-name was requested,and the remote node does not accept theauthorization ID and password combinationspecified for this node (either in the remoteauthorization tables or at runtime).

The request cannot be processed.

User Response: Resubmit the request with avalid authorization ID and passwordcombination for the remote system.

SQL1102N A database name was notspecified.

Explanation: No database name was providedto proceed with migration.


User Response: Specify a database name formigration.

SQL1103W The Migrate Database commandprocessing was successful.

Explanation: The Migrate command completedsuccessfully.

Note that this message will also be returned if

the database was already at the current level anddid not need to be migrated.



SQL1104N The address of the program nameparameter is not valid.

Explanation: The application program has usedan address for the program name that is notvalid.


User Response: Use a correct address in theapplication program.

SQL1105N The SQL CONNECT RESETstatement is not allowed in aRemote Application InterfaceProcedure.

Explanation: The remote application procedurecontains an SQL CONNECT RESET statement.

The remote procedure is not allowed to continue.

User Response: Remove the SQL CONNECTRESET statement and retry the remote procedure.

sqlcode: -1105

sqlstate: 38003

SQL1106N The specified DLL name modulewas loaded, but the functionfunction could not be executed.

Explanation: The function within the DLL(dynamic link library) cannot be found.


User Response: Ensure that the DLL module isbuilt correctly. Reference the module in thedefinition file.

sqlcode: -1106

sqlstate: 42724


SQL1107N An interrupt was received whileloading the specified DLL name.

Explanation: When loading the DLL (dynamiclink library) module, the command wasinterrupted, perhaps by Ctrl+Break.


User Response: Resubmit the command.

sqlcode: -1107

sqlstate: 42724

SQL1108N An unexpected I/O error oroperating system error wasreceived while loading thespecified DLL name.

Explanation: An unexpected error occurredwhen trying to load the DLL (dynamic linklibrary) module specified in the program namefield.


User Response: Resubmit the current command.If the error continues, reinstall the databasemanager.

If reinstallation does not correct the error, recordthe message number (SQLCODE) and allinformation in the SQLCA if possible.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Then contact your technical servicerepresentative.

sqlcode: -1108

sqlstate: 42724

SQL1109N The specified DLL name could notbe loaded.

Explanation: The DLL (dynamic link library)module specified could not be found.


User Response: Ensure that the specified file isin a subdirectory identified in the systemLIBPATH.

sqlcode: -1109

sqlstate: 42724

SQL1110N A supplied data area was invalidand could not be used.

Explanation: The data area is not initializedcorrectly.


User Response: Ensure that the user-suppliedinput SQLDA or output SQLDA fields areinitialized correctly.

SQL1111N The program name name specifiedwas not valid.

Explanation: The DLL (dynamic link library)module or program name syntax is not correct.


User Response: Ensure that the DLL orprogram name is specified correctly.

sqlcode: -1111

sqlstate: 42724

SQL1112N There are not enough systemresources to load the specifiedDLL name.

Explanation: There is not enough randomaccess memory (RAM) to load the specified DLL(dynamic link library) module.


User Response: Stop the application. Possiblesolutions are:

v Change the MEMMAN NO SWAP, NO MOVEoption in the CONFIG.SYS file to SWAP,MOVE.


v Decrease the values of the configurationparameters that define the allocation ofmemory.

v Install more random access memory (RAM).

sqlcode: -1112


sqlstate: 42724

SQL1113N The data type for sqlvar n in theoutput SQLDA was changed fromtype-1 to type-2.

Explanation: The remote stored procedurechanged the data type of the nth sqlvar in theoutput SQLDA; n is the sequence number of thefirst mismatched sqlvar.

The stored procedure does not return any data.

User Response: Correct the remote storedprocedure so the data type information in theoutput SQLDA is not changed.

sqlcode: -1113

sqlstate: 39502

SQL1114N The data length for the sqlvar n inthe output SQLDA was changedfrom length-1 to length-2.

Explanation: The remote stored procedurechanged the data length of the nth sqlvar in theoutput SQLDA; n is the sequence number of thefirst mismatched sqlvar.


User Response: Correct the remote storedprocedure so the data length information in theoutput SQLDA is not changed.

sqlcode: -1114

sqlstate: 39502

SQL1115N The number of sqlvars in theoutput SQLDA was changed fromcount-1 to count-2.

Explanation: The remote procedure changed thesqld field in the output SQLDA; sqld is thenumber of used sqlvars in the SQLDA.


User Response: Correct the remote storedprocedure so the sqld field in the output SQLDAis not changed.

sqlcode: -1115

sqlstate: 39502

SQL1116N A connection to or activation fordatabase name cannot be madebecause of BACKUP PENDING.

Explanation: The specified database requires abackup to be taken to provide a starting pointfor roll-forward recovery.


User Response: Back up the database by callingthe BACKUP routine or, if roll-recovery is notrequired, set the log retain and user exit databaseconfiguration parameters off.

sqlcode: -1116

sqlstate: 57019

SQL1117N A connection to or activation fordatabase name cannot be madebecause of ROLL-FORWARDPENDING.

Explanation: The specified database is enabledfor roll-forward recovery and it has been restoredbut not rolled forward.



User Response: Roll forward the database orindicate that you do not wish to roll forward byusing the ROLLFORWARD command. Note thatif you do not roll forward the database, therecords written since the last backup of thedatabase will not be applied to the database.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andtake recovery action appropriate to that datasource to bring the data source to a point ofconsistency.

sqlcode: -1117

sqlstate: 57019


SQL1118N A connection to or activation ofdatabase name cannot be madebecause a previous backup isincomplete.

Explanation: The database is in an inconsistentstate because a system error occurred during abackup function.



User Response: Issue the BACKUP commandand then try the command again.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andissue the BACKUP command against that datasource prior to trying the command again.

sqlcode: -1118

sqlstate: 57019

SQL1119N A connection to or activation ofdatabase name cannot be madebecause a previous restore isincomplete.

Explanation: The database is in an inconsistentstate because a system error occurred during arestore function.


Federated system users: this situation can bedetected by the data source.

User Response: Issue the RESTORE commandand then try the command again.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andissue the RESTORE command against that datasource prior to trying the command again.

sqlcode: -1119

sqlstate: 57019

SQL1120N A connection to or activation ofdatabase name cannot be madebecause a previous backup orrestore is incomplete.

Explanation: The database is in an inconsistentstate because a system error occurred during abackup or restore function. It cannot bedetermined if backup or restore was beingprocessed.



User Response: Issue the BACKUP orRESTORE command, and then try the commandagain.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andissue the BACKUP or RESTORE commandagainst that data source prior to trying thecommand again.

sqlcode: -1120

sqlstate: 57019

SQL1121N The address of the node structureparameter is not valid.

Explanation: The application used an addressfor the node structure parameter that is notvalid. Either the address points to an unallocatedbuffer or the buffer is not large enough tocontain the required input.


User Response: Verify that the programallocates the required buffer area and resubmitthe command.

SQL1122N The address of the protocolstructure parameter is not valid.

Explanation: The application used an addressfor the protocol structure parameter that is notvalid. Either the address points to an unallocated


buffer or the address points to the incorrectprotocol buffer.


User Response: Verify that the programallocates the required buffer area based on theprotocol field in the node structure and resubmitthe command.

SQL1123N The protocol type is not valid.

Explanation: The protocol type specified in thenode structure for the Catalog command doesnot represent a recognized value. The validprotocol types are defined in the sqlenv headerfiles.


User Response: Verify the protocol type in thenode structure and resubmit the command.

SQL1124N The remote workstation namename is not valid.

Explanation: The remote workstation namespecified in the NETBIOS protocol structure forthe Catalog command is not specified or containscharacters that are not valid. The workstationname must be 1 to 8 characters. Valid charactersare A through Z, a through z, 0 through 9, #, @,and $. The first character must be alphabetic or aspecial character: #, @, or $. Lowercase charactersare changed to uppercase by the system.


User Response: Verify the characters specifiedin the remote workstation name. Resubmit thecommand with a valid workstation name.

SQL1125N The adapter number number is notvalid.

Explanation: The adapter number specified inthe NETBIOS protocol structure for the Catalogcommand is not valid.


User Response: Verify that the adapter numberis valid and resubmit the command.

SQL1126N The network ID ID is not valid.

Explanation: The network ID specified in theAPPN protocol structure for the Catalogcommand is not valid. The network ID identifiesthe SNA network where the remote logical unit(LU) resides. The network ID must be 1 to 8characters. Valid characters are A through Z, athrough z, 0 through 9, #, @, and $. The firstcharacter must be alphabetic or a specialcharacter: #, @, or $. Lowercase characters arechanged to uppercase by the system.


User Response: Verify the characters specifiedin the network ID. Resubmit the command witha valid network ID.

SQL1127N The remote LU name name is notvalid.

Explanation: The remote logical unit (LU) namespecified in the APPN protocol structure for theCatalog command is not valid. The remote LUname is the remote SNA logical unit name andmust be 1 to 8 characters. Valid characters are Athrough Z, a through z, 0 through 9, #, @, and $.The first character must be alphabetic or aspecial character: #, @, or $. Lowercase charactersare changed to uppercase by the system.


User Response: Verify the characters specifiedin the remote LU name. Resubmit the commandwith a remote LU name.

SQL1128W SAVECOUNT is ignored.

Explanation: Consistency points are notsupported when loading into MDC tables.



SQL1129N New DARI (Stored Procedure)process could not be startedbecause there are insufficientresources for a new process to becreated.

Explanation: New DARI (Stored Procedure)process could not be started because there areinsufficient resources for a new process to becreated.

User Response: Do one of the following:

v Reduce the number of users using DB2

v Increase the system process limit.

sqlcode: -1129

sqlstate: 42724

SQL1130N New DARI (Stored Procedure)process could not be startedbecause the maximum number ofDARI processes allowed to bepresent at the server at the sametime has been reached.

Explanation: New DARI (Stored Procedure)process could not be started because themaximum number of DARI processes allowed tobe present at the server at the same time hasbeen reached.

User Response: Increase the maximum numberof DARI processes, maxdari, configurationparameter. See the database configurationparameter maxdari for more details.

sqlcode: -1130

sqlstate: 42724

SQL1131N DARI (Stored Procedure) processhas been terminated abnormally.

Explanation: The cause of this error may be:

v There was a coding error (e.g. segmentationviolation) within the DARI routine.

v The DARI process has been terminated byanother process through the use of a signal.

User Response: Reinitiate the DARI request

after doing the following :

v Ensure that the DARI procedure is free fromprogramming errors.

v Make sure that no user is sending atermination signal to the DARI process.

sqlcode: -1131

sqlstate: 38503

SQL1132N The command is not allowed toexecute within a DARI (StoredProcedure).

Explanation: An illegal command has beenmade within the scope of DARI (StoredProcedure).

The DARI procedure is not allowed to continue.

User Response: Remove the illegal command inthe DARI procedure and retry.

sqlcode: -1132

sqlstate: 38003

SQL1133N A pointer address inside an sqlvar( index = n ) of the outputSQLDA was modified within theDARI (Stored Procedure)function.

Explanation: The “sqlind” or the “sqldata”pointer within the sqlvar of the output SQLDAhas been altered within the user prepared DARIfunction.


User Response: Correct the usage of theindicated sqlvar within the output SQLDA sothat pointer addresses are not changed withinthe DARI (Stored Procedure) function routine.

sqlcode: -1133

sqlstate: 39502


SQL1134N For database authentication typeCLIENT, the command is notallowed within the scope of DARI(Stored Procedure).

Explanation: All SYSADM commands are notallowed to execute within DARI (StoredProcedure) when the database authenticationtype is CLIENT.


The DARI procedure is not allowed to continue.

User Response: Remove the illegal command inthe DARI procedure and retry.

sqlcode: -1134

sqlstate: 38003

SQL1135N An invalid value was specified forthe number of segments whencreating a database.

Explanation: The value that was specified forthe number of segments was out of range. Thevalid range is from 1 to 256.

User Response: Respecify the number ofsegments and try to create the database again.

SQL1136N An invalid value was specified forthe default table space extent size(dft_extentsize) when creating adatabase.

Explanation: The value that was specified forthe default table space extent size (dft_extentsize)is out of range. The valid range is from 2 to 256.

User Response: Correct the table space extentsize and try again.

SQL1137W The database manager was unableto remove the database path orsome of the containers whendropping database dbalias.Cleanup is required.

Explanation: Either the list of containers couldnot be accessed or some failure occurred while

attempting to remove them or the databasedirectory.

User Response: System managed containers(directories) and database managed filecontainers may be manually removed usingoperating system commands. To release devicecontainers, please call your IBM servicerepresentative for assistance.

If the log directory has been changed via theNew Log Path configuration parameter, thenmanually unmount the log directory file systemand remove the log and database directories.

SQL1138W The unique index name wasmigrated to support deferreduniqueness checking. A newindex was not created.

Explanation: A CREATE INDEX operation wasattempted on an existing index. Since the indexhad not yet been migrated to support deferreduniqueness checking, this migration wasperformed.

The migrated format of the unique index willallow multiple row updates to check theuniqueness of the columns of the index at theend of the update statement instead of wheneach row is updated.


sqlcode: +1138

sqlstate: 01550

SQL1139N The total size of the table space istoo big.

Explanation: The size of the current table spaceis too big. The size of a REGULAR or USERTEMPORARY table space is limited to 0xFFFFFF(16777215) pages while the size of a SYSTEMTEMPORARY or LONG table space is limited to2 terabytes (2 TB).

User Response: Check the administrationnotification log for details. Reduce the size of thetable space and correct the SQL statement.

sqlcode: -1139


sqlstate: 54047

SQL1140W Estimated processor cost ofestimate-amount1 processor seconds(estimate-amount2 service units) incost category cost-category exceedsa resource limit warning thresholdof limit-amount service units.

Explanation: The prepare of a dynamic INSERT,UPDATE, DELETE, or SELECT SQL statementresulted in a cost estimate that exceeded thewarning threshold value specified in the resourcelimit specification table (RLST).

This warning is also issued if DB2’s cost categoryvalue was ″B″, and the default action specified inthe RLF_CATEGORY_B column in the RLST is toissue a warning.

estimate_amount1The cost estimate (in processor seconds)if the prepared INSERT, UPDATE,DELETE or SELECT statement were tobe executed.

estimate_amount2The cost estimate (in service units) if theprepared INSERT, UPDATE, DELETE orSELECT statement were to be executed.

cost-categoryDB2’s cost-category for this SQLstatement. The possible values are A orB.

limit-amountThe warning threshold (in service units)specified in the RLFASUWARN columnof the RLST.

The prepare of the dynamic INSERT, UPDATE,DELETE, or SELECT statement was successful.An SQLCODE -905 might be issued if theexecution of the prepared statement exceeds theASUTIME value specified in the RLST.

User Response: Ensure that there is applicationlogic to handle the warning to either allow thestatement to execute or to stop the statementfrom being executed. If this SQLCODE wasreturned because the cost category value is ″B″, itmight be that the statement is using parameter

markers or that some statistics are not availablefor the referenced tables and columns. Make surethe administrator has run the utility RUNSTATSon the referenced tables. It might also be thatUDFs will be invoked when the statement isexecuted, or for INSERT, UPDATE, or DELETEstatements that triggers are defined on thechanged table. Check theDSN_STATEMNT_TABLE or the IFCID 22 recordfor this statement to find the reasons this SQLstatement has been put in cost category ″B″.

If the warning is caused by an SQL statementthat is consuming too much processor resource,attempt to rewrite the statement to perform moreefficiently. Another option is to ask theadministrator to increase the warning thresholdvalue in the RLST.

sqlcode: +1140

sqlstate: 01616

SQL1141N The operation completed witherrors or warnings. The details arelocated in the result file file-namethat needs to be formatted withthe db2inspf utility.

Explanation: In a partitioned databaseenvironment, the file extension corresponds tothe database partition node number. The files arelocated in the directory specified by theDIAGPATH database manager configurationparameter.

User Response: Use the db2inspf utility toformat the inspection data result file file-name.

SQL1142N The operation cannot completebecause the file file-name isalready in use.

Explanation: There is an existing file using thefile name specified in the INSPECT command.


User Response: Resubmit the command using adifferent file name that is not already in use. Orremove the existing file file-name and resubmitthe command.


In a partitioned database environment, the fileextension corresponds to the database partitionnode number. The files are located in thedirectory specified by the DIAGPATH databasemanager configuration parameter.

SQL1143N The operation cannot completebecause a file error occurred forthe file file-name.

Explanation: The file could not be accessedbecause of an I/O error. The system cannot open,read from, or write to the file. The file may beincomplete or the disk may be full.

The utility stops processing.

User Response: If possible, record all errorinformation from the SQLCA. Look in thediagnostics log file for additional information.

In a database partitioned environment, the fileextension corresponds to the database partitionnode number. The files are located in thedirectory specified by the DIAGPATH databasemanager configuration parameter.

SQL1144N The current transaction was rolledback as a result of a failurecreating an index, sqlcode =sqlcode.

Explanation: In the same transaction, the lastremaining index on a table was dropped andthen a new index was created on the same table.The index creation either failed with an error,sqlcode, or was rolled back by a ROLLBACK TOSAVEPOINT statement (sqlcode=0). A rollback ofthe index creation cannot be successfullycompleted when a drop index of the lastremaining index on a table has not yet beencommitted. The entire transaction is rolled backfor either of these cases. Note that indexes arealso created or dropped by adding or droppingunique or primary key constraints in an ALTERTABLE statement.

User Response: Where possible, commit thedrop of an index before creating a new index onthe same table in order to avoid rolling back theentire transaction. If the sqlcode is not 0, thenrefer to the message for the sqlcode for corrective

action. All statements in the rolled backtransaction need to be issued again. If the sqlcodeis zero and the index is dropped within thesavepoint scope, the statements may need to bere-ordered to create the new index beforedropping the old index on the same table. If thedrop and add unique or primary key constraintsare in the same ALTER TABLE statement, thismay need to be done in two statements,performing the ADD in the first statement andthe drop in the second statement.

sqlcode: -1144

sqlstate: 40507

SQL1145N PREPARE statement is notsupported when using a gatewayconcentrator. Reason code:reason-code.

Explanation: The statement failed for one of thefollowing reasons, based on reason-code.

1 When gateway concentrator feature isON, dynamically prepared statementsfrom embedded SQL are not supported.In this configuration, dynamicallyprepared statements are only supportedif the client is a CLI application.

2 When the gateway concentrator featureis ON, dynamically prepared SETstatements are not supported.

User Response: Based on the reason code,perform the following actions:

1 Change the application to use CLI fordynamic SQL statements, or change theapplication to use static SQL.

2 Use EXECUTE IMMEDIATE for SETstatements.

sqlcode: -1145

sqlstate: 560AF


SQL1146N There are no indexes on tabletable-name.

Explanation: The table-name specified for indexreorganization has no indexes.

User Response: Resubmit the command with avalid table name.

SQL1147W TOTALFREESPACE is ignored forMDC tables.

Explanation: Because the table free space is wellmanaged for MDC tables, theTOTALFREESPACE file type modifier isunnecessary and will be ignored.


SQL1150N The address of the user idparameter is not valid.




SQL1160N The DOS network-protocol TSR hasnot been loaded.

Explanation: The Terminate and Stay Resident(TSR) network driver for the specifiedcommunications protocol has not been loaded.The TSR must be loaded before attempting touse network communications.

User Response: Ensure that the TSR for thespecified communications protocol has beensuccessfully loaded, then run your applicationagain.

SQL1161W Reconcile processing failed.DataLink column(s) not definedon DB2 DataLinks Manager(s).Check the administrationnotification log for details.

Explanation: Metadata information about one ofmore DataLink columns of the table are missingon DB2 DataLinks Managers. Reconcileprocessing has failed. Table is placed in DataLinkReconcile Not Possible (DRNP) state.

User Response: To take the table out ofDataLink Reconcile Not Possible state, follow theprocedure mentioned under “Removing a tablefrom the DataLink Reconcile Not Possible state”in the Administration Guide.

SQL1162W Reconcile processing failed. DB2DataLinks Manager(s) becameunavailable during exceptionprocessing.

Explanation: One of more DB2 DataLinksManagers referred to by the table data becameunavailable during reconcile exceptionprocessing. Reconcile processing has failed. Tableis placed in DataLink Reconcile Pending (DRP)state.

User Response: Run reconcile again.

SQL1163N The table cannot be enabled fordata capture as the identifiername ident-name of type ident-typeis too long.

Explanation: Data capture is not supportedwith certain identifier types exceeding specificlengths. In processing the attempted change, itwas found that the identifier ident-name of typeident-type is too long. The identifier types and themaximum lengths allowed for data captureenablement are as follows:

1. column. Column names cannot be longerthan 18 bytes for data capture to be enabled.

2. table. Table names cannot be longer than 18bytes for data capture to be enabled.

3. schema. Schema names cannot be longer than18 bytes for data capture to be enabled.


User Response: If data capture is to be enabledfor this table than ensure that the identifiers inquestion do not exceed the maximum sizesstated above. Otherwise disable data capture forthe table in order to use longer identifier names.

sqlcode: -1163

sqlstate: 42997

SQL1164N The SQLDA or host variables, oftype type, used in the SQLstatement are not valid. Reasoncode reason-code, hostvariable/SQLVAR numbervar-number.

Explanation: An error occurred whileprocessing the SQLDA or host variable(s) in theSQL statement.

The call parameter list, which is created by theprecompiler, may not be correct if the applicationprogrammer has modified the output of theprecompiler, used a variable name beginningwith SQL in the application program, orover-written the call parameter list in anotherway.

Also, if an SQLDA is passed directly by theapplication, it may not be initialized correctly.

Host variable/SQLDA types:

1 input host variable(s) or SQLDA

2 output host variable(s) or SQLDA

In SQL statements with host variables, use thehost variable number to count in from thebeginning of the statement (or substatement, inthe case of compound SQL) to locate the invalidhost variable. For statements using an SQLDA,the SQLVAR number is used to locate the invalidSQLVAR. For an input SQLDA, count only inputhost variables or SQLVARs; similarly for output.Note that this number is based at 1, and may notbe applicable to all reason codes. Reason codesare interpreted as follows:

1 SQLDA.SQLN is less thanSQLDA.SQLD

2 SQLVAR.SQLTYPE is invalid.

3 The length specified inSQLVAR.SQLLEN orSQLVAR2.SQLLONGLEN is incorrectfor the SQL type given inSQLVAR.SQLTYPE.

4 A Large Object SQLVAR is present, butthe SQLDOUBLED field ofSQLDA.SQLDAID is not set to ’2’.

5 An input varchar is supplied whosecurrent length (from the length field ofthe varchar itself) is greater than themaximum length. The maximum lengthis determined by the declaration (in thecase of a host variable) or by the settingof SQLVAR.SQLLEN (in the case of auser-defined SQLDA).

6 An input Large Object is passed inwhose current length (either in thelength field of the LOB itself, or asindicated by theSQLVAR2.SQLDATALEN pointer) isgreater than the maximum length. Themaximum length is determined by thedeclaration (in the case of a hostvariable) or by the setting ofSQLVAR2.SQLLONGLEN (in the case ofa user-defined SQLDA).

7 A double-byte character Large Objecthas an odd value indicated by theSQLVAR2.SQLDATALEN pointer, whichis always in terms of bytes, even forDBCLOBs.

8 The SQLDATA pointer is invalid orpoints to insufficient storage.

9 The SQLIND pointer is invalid or pointsto insufficient storage.

10 The SQLDATALEN pointer is invalid orpoints to insufficient storage.

11 A specific number of input hostvariables/SQLVARS is expected for thecurrent SQL statement.


User Response: Examine the applicationprogram for any errors noted. Note that the


programmer should not attempt to modify theprecompiler output.

sqlcode: -1164

sqlstate: 07002

SQL1165W A value cannot be assigned to ahost variable because the value isnot within the range of the hostvariable’s data type.

Explanation: A FETCH, VALUES, or SELECTinto a host variable list failed because the hostvariable was not large enough to hold theretrieved value.

The statement processing continued returning anull indicator of -2.

User Response: Verify that table definitions arecurrent and that the host variable has the correctdata type. For the ranges of SQL data types, referto the SQL Reference.

sqlcode: +1165

sqlstate: 01515

SQL1166W Division by zero was attempted.

Explanation: The processing of an arithmeticexpression resulted in division by zero. Thiswarning may be returned with a row other thanthe row which caused the warning. For example,this occurs with arithmetic expressions inpredicates or when the query is processed usingsystem temporary tables. The warning may beissued again since it is also returned whenever anull indicator variable is set to -2.

The statement processing continued, using nullas the result of the division expression andpossibly returning a null indicator of -2.

User Response: Examine the SQL statement todetermine the cause of the problem. If theproblem is data dependent, it is necessary toexamine the data processed when the erroroccurred.

sqlcode: +1166

sqlstate: 01564

SQL1167W Arithmetic overflow or otherarithmetic exception occurred.

Explanation: The processing of an arithmeticexpression has resulted in an arithmetic overflow,underflow or other arithmetic exception. Thiswarning may be returned with a row other thanthe row which caused the warning. For example,this occurs with arithmetic expressions inpredicates or when the query is processed usingsystem temporary tables. The warning may beissued again since it is also returned whenever anull indicator variable is set to -2.

The statement processing continued, using nullas the result of the arithmetic expression andpossibly returning a null indicator of -2.


sqlcode: +1167

sqlstate: 01519

SQL1178N The federated object-type calledobject-name does not reference afederated database object.

Explanation: The object of type object-typeidentified by object-name is defined using thekeyword FEDERATED but the fullselect in thestatement does not reference a federateddatabase object.


User Response: Remove the keywordFEDERATED from the statement.

sqlcode: -1178

sqlstate: 429BA


SQL1179W The object-type called object-namemay require the invoker to havenecessary privileges on datasource objects.

Explanation: The object identified by object-namereferences a federated object (such as an OLE DBtable function, federated routine, federated view,or a nickname), where the actual data exists at adata source. When the data source data isaccessed, the user mapping and authorizationchecking is based on the user that initiated theoperation.

If the object-type is SUMMARY TABLE, then theoperation is refreshing the data for thematerialized query table. The user that invokedthe REFRESH TABLE or SET INTEGRITYstatement that causes the refresh may be requiredto have the necessary privileges to access theunderlying data source object at the data source.

If the object-type is VIEW, then any user of theview may be required to have the necessaryprivileges to access the underlying data sourceobject at the data source.

If the object-type is PROCEDURE, FUNCTION, orMETHOD then the invoker of the routine may berequired to have the necessary privileges toaccess the underlying data source object at thedata source for any SQL statements in theroutine.

In any case, an authorization error may occurwhen the attempt is made to access the datasource object.

User Response: Granting privileges to theobject may not be sufficient to supportoperations that access the data from the datasource. User access may need to be granted atthe data source for the underlying data sourceobjects.

sqlcode: +1179

sqlstate: 01639

SQL1180N Routine routine-name (specificname specific-name) has caused anOLE error. HRESULT=hresult.Diagnostic text: message-text.

Explanation: DB2 received an OLE error codewhile trying to communicate with the OLEautomation server of user defined function(UDF) or stored procedure routine-name (specificname specific-name). HRESULT hresult is thereturned OLE error code, and message text is theretrieved error message.

The following shows a partial list of errormessages, HRESULTS, and possible causes. Theerror message text may be changed by OLE, andnew error codes may be added by OLE.

Unknown interface (0x80020001):The specified OLE object does notsupport the IDispatch interface.

Type mismatch (0x80020005):One or more of the SQL data types donot match the data types of the methodarguments.

Unknown name (0x80020006):The specified method name was notfound for the specified OLE object.

Invalid number of parameters (0x8002000E):The number of arguments passed to themethod is different from the number ofarguments accepted by the method.

Invalid class string (0x800401F3):The specified ProgID or CLSID isinvalid.

Class not registered (0x80040154):CLSID is not properly registered.

Application not found (0x800401F5):Local server EXE not found.

DLL for class not found (0x800401F8):In-process DLL not found.

Server execution failed (0x80080005):Creation of the OLE object failed.

User Response: Consult the OLE Programmer’sReference Guide for a complete documentation,including the meaning of the special terminology.


sqlcode: -1180

sqlstate: 42724

SQL1181N Routine routine-name (specificname specific-name) has raised anexception with descriptionmessage-text.

Explanation: The user defined function (UDF)or stored procedure routine-name (specific namespecific-name) has raised an exception. Themessage text shows the textual description of theexception returned by the routine.

User Response: The user will need tounderstand the meaning of the exception. See theauthor of the routine.

sqlcode: -1181

sqlstate: 38501

SQL1182N User defined functionfunction-name could not initializedata source object of specifiedOLE DB provider.HRESULT=hresult. Diagnostic text:message-text.

Explanation: The OLE DB data source object ofthe specified OLE DB provider could not beinstantiated or initialized. hresult is the returnedOLE DB error code, and message-text is theretrieved error message.

The following shows a partial list of HRESULTSand possible causes.

0x80040154Class (OLE DB provider) not registered.

0x80040E73The initialization string specified doesnot conform to specification.

0x80004005Unspecified error (during initialization).

User Response: Verify proper registration of theOLE DB provider and correct initialization of theparameters in the connection string. ConsultMicrosoft OLE DB Programmer’s Reference andData Access SDK for a complete documentation

of HRESULT codes and Data Link APIconnection string syntax in OLE DB CoreComponents.

sqlcode: -1182

sqlstate: 38506

SQL1183N User defined functionfunction-name received an OLE DBerror from specified OLE DBprovider. HRESULT=hresult.Diagnostic text: message-text.

Explanation: The specified OLE DB providerreturned an OLE DB error code. hresult is thereturned OLE DB error code, and message-text isthe retrieved error message.

The following shows a partial list of HRESULTSand possible causes.

0x80040E14The command contained one or moreerrors, e.g. syntax error in pass-throughcommand text.

0x80040E21Errors occurred, e.g. the suppliedcolumnID was invalid(DB_INVALIDCOLUMN).

0x80040E37The specified table does not exist.

User Response: Consult Microsoft OLE DBProgrammer’s Reference and Data Access SDKfor a complete documentation of HRESULTcodes.

sqlcode: -1183

sqlstate: 38506

SQL1184N One or more EXPLAIN tableswere not created using the currentversion of DB2.

Explanation: EXPLAIN will not be able to insertinto these tables until they are migrated usingDB2EXMIG, or dropped and created with theEXPLAIN.DDL CLP script for the current versionof DB2.

User Response: Either migrate the tables using


DB2EXMIG, or drop and re-create them with theEXPLAIN.DDL CLP script for the current versionof DB2. Re-issue the command.

sqlcode: -1184

sqlstate: 55002

SQL1185N FEDERATED value is incorrectlyused in binding the package.

Explanation: If value is NO, then at least onestatic SQL statement in the package includes areference to either a nickname or OLE DB tablefunction or OLE DB procedure. In this case, youmust specify FEDERATED YES to bind thepackage.

If value is YES, then no static SQL statement inthe package includes a reference to either anickname or OLE DB table function or OLE DBprocedure. In this case, you must specifyFEDERATED NO to bind the package.


User Response: Specify the correctFEDERATED option.

SQL1186N The object object-type namedobject-name is either being alteredto become a federated object, orbeing created as a federatedobject, without specifying theFEDERATED clause.

Explanation: The object identified by object-namereferences a federated object (such as an OLE DBtable function, federated routine, federated view,or a nickname) where the actual data exists at adata source.

If a non-federated view is being altered and thefullselect now refers to a federated databaseobject, either directly or indirectly, thenFEDERATED must be specified.

If a federated view is being altered and thefullselect still refers to a federated databaseobject, either directly or indirectly, then NOTFEDERATED must not be specified.

If a materialized query table is being created andthe fullselect refers to a federated database

object, either directly or indirectly, then NOTFEDERATED must not be specified.

If an SQL routine is being created and theroutine refers to a federated database object,either directly or indirectly, then NOTFEDERATED must not be specified.

User Response: To alter a non-federated view tobecome a federated view, specify theFEDERATED clause.

To alter a federated view that continues to be afederated view, do not specify the NOTFEDERATED clause.

To create a materialized query table in which thefullselect refers to a federated database object,either directly or indirectly, do not specify theNOT FEDERATED clause.

To create an SQL routine which refers to afederated database object, either directly orindirectly, do not specify the NOT FEDERATEDclause.

sqlcode: -1186

sqlstate: 429BA

SQL1187W The database was createdsuccessfully, but an error occurredwhile creating the detaileddeadlocks event monitorevent-monitor-name. The detaileddeadlocks event monitor is notcreated.

Explanation: CREATE DATABASE could notcreate a detailed deadlocks event monitor for thenewly created database.

User Response: Create a detailed deadlocksevent monitor if desired.


SQL1188N Column src-col-num of theSELECT or VALUES statement isnot compatible with table columntgt-col-num. The source columnhas sqltype src-sqltype, and thetarget column has sqltypetgt-sqltype.

Explanation: The source and target columns arenot compatible. This may be a result of anincorrect ordering of the columns in the SELECTor VALUES statement, or of an incorrect orderingof the METHOD P or METHOD N specification.

User Response: Correct the command so thatthe source and target columns are compatible,and then resubmit the command.

SQL1189N The LOAD METHOD specified isinvalid for the specified file type.

Explanation: An invalid METHOD wasspecified for the specified file type.

User Response: Resubmit the command with adifferent METHOD.

SQL1190N The LOAD utility encounteredSQLCODE sqlcode, SQLSTATEsqlstate, and message tokenstoken-list.

Explanation: The LOAD utility encountered anerror with the SQLCODE sqlcode and has stoppedprocessing.

User Response: Look up the SQLCODE sqlcodein the Message Reference. Take the requiredcorrective actions, and then resubmit thecommand.

SQL1191N Column col-spec specified in theMETHOD parameter does notexist.

Explanation: Column col-spec does not exist inthe result of the query.

User Response: Correct the invalid columnspecification and resubmit the command.

SQL1192W Too many input sources werespecified for the current filetype.The maximum number allowed ismax-input-sources.

Explanation: The filetype specified does notallow more than max-input-sources input sourcesto be specified for a single load.

User Response: Resubmit the command with anumber of input sources that does not exceedmax-input-sources.

SQL1193I The utility is beginning to loaddata from the SQL statementstatement.

Explanation: This is an informational messageindicating that a load from an SQL statement hasbegun.


SQL1194W The value in row row-numcorresponding to target columnnumber col-num is not valid. Therow has been rejected.

Explanation: Row number row-num has beenrejected because the value corresponding totarget column col-num is not a valid value forthat column.

Possible reasons are :

v A numeric value is not within the minimum ormaximum range of its target column.

v A character value is too long for its targetcolumn.

User Response: Examine the input value. Ifnecessary, define a new table replacing targetcolumn col-num with a more appropriatelydefined column and repeat the process.

SQL1195N The Tools Catalog Databasedatabase-name creation orinitialization failed at server-name.SQLCODE = SQLCODE.

Explanation: The Tools Catalog Databasedatabase-name creation or initialization failed at


server-name. SQLCODE = SQLCODE.

User Response: Refer to the user response forthe SQLCODE returned from the operation.

SQL1196W Backup completed successfully.However, one or more Data LinksFile Managers could not becontacted. The timestamp for thisbackup image isbackup-image-timestamp.

Explanation: Backup completed successfully.One or more Data Links File Managers were notavailable during backup processing. Additionalverification are needed from the Data Links FileManagers when they are available.

User Response: Bring up the Data Links FileManagers that were unavailable during backupprocessing. Once all the Data Links FileManagers can be contacted, DB2 willautomatically complete the final verification forthis backup image.

SQL1197N Invalid value specified forkeyword keyword in commandcommand.

Explanation: The keyword value specified for thecommand is invalid. For numeric values, the valuemay be outside a defined range. For other types,the value specified is not in the defined set ofvalid values.

User Response: Determine from referencedocumentation for the command what are validvalues and make the appropriate change. If thiserror has been returned by an API, determinefrom the reference documentation for thecommand API what are valid values for thecorresponding API option and make theappropriate change.

SQL1198N This command is not supported inthe current downlevelclient-server configuration.Reason code = reason-code.

Explanation: The command you have entered isnot supported in your current configuration

involving either a pre-V8 client or server. Thepossible reason codes are as follows:

1 Scrollable cursors are not supportedfrom a pre-V8 client through a V8 orlater gateway to a DB2 UDB server.

2 Utility commands are not supportedfrom a pre-V8 client through a V8 orlater gateway to any DB2 server.

3 Access to a pre-V8 server through a V8or later gateway is not supported.

4 Utility commands are not supported toa pre-V8 server from a V8 or later client.

98 Operation not supported to a pre-V8server from a V8 or later client.

99 Operation not supported from a pre-V8client to a V8 or later server.

User Response: The action is based on thereason code as follows:

1 Do not use scrollable cursors from adownlevel client through a gateway. Usea direct client-server connection orupgrade your client to a compatiblerelease.

2 Do not issue utility commands from adownlevel client through a gateway. Usea direct client-server connection orupgrade your client to a compatiblerelease.

3 Use a compatible level of gateway orconfigure a direct connection(non-gateway) to the server.

4 Use a compatible client level to issue V8utility commands.

98 Use a compatible level of client to issuethis command or consider upgradingyour server’s level of code.

99 Use a compatible level of server to issuethis command or consider upgradingyour client’s level of code.


SQL1200 - SQL1299

SQL1200N The object parameter is not valid.

Explanation: The value specified for the objectparameter in the COLLECT DATABASE STATUSfunction call is not valid. Valid values are:

SQLE_DATABASEStatus is to be collected for a singledatabase.

SQLE_DRIVEStatus is to be collected for all LOCALdatabases on a single path.

SQLE_LOCALStatus is to be collected for all LOCALdatabases.


User Response: Correct the object parameterand resubmit the COLLECT DATABASE STATUSfunction call.

SQL1201N The status parameter is not valid.

Explanation: The value specified for the statusparameter in the COLLECT DATABASE STATUSfunction call is not valid. Valid values are:

SQLE_SYSTEMSystem status is to be collected.

SQLE_DATABASESystem status and database status is tobe collected.

SQLE_ALLSystem status, database status and userstatus is to be collected.


User Response: Correct the status parameterand resubmit the COLLECT DATABASE STATUSfunction call.

SQL1202N Status has not been collected.

Explanation: The value specified for the handleparameter in the GET NEXT DATABASE

STATUS BLOCK or the FREE DATABASESTATUS RESOURCES function calls is not valid.The handle must be the one returned as thepositive function value from the COLLECTDATABASE STATUS function call.

This is the second COLLECT DATABASESTATUS call made from the process. The firstCOLLECT DATABASE STATUS call terminatesand its handle can no longer be used.


User Response: Correct the handle parameterand resubmit the COLLECT DATABASE STATUSfunction call.

SQL1203N The database has no usersconnected.

Explanation: A request was made for userstatus on a database, but the database has nousers connected.


User Response: Verify the database name andthe connection status. Resubmit the commandwith a database currently being used.

SQL1204N The code page code-page and/orterritory code territory-code is notsupported by the installed versionof the database manager.

Explanation: This version of the databasemanager does not support the active code pageor territory code or both.


Choose an active code page and territory codesupported by this version of the databasemanager.

Federated system users: if necessary isolate theproblem to the data source rejecting the request(see the Troubleshooting Guide for procedures tofollow to identify the failing data source) andchoose an active code page and territory codesupported by both the federated server and thedata source.


User Response: Exit the current program andreturn to the operating system.

sqlcode: -1204

sqlstate: 22522

SQL1205N The code page code-page and/orterritory code territory that hasbeen specified is not valid.

Explanation: This version of DB2 does notsupport the active code page or territory code orboth, as specified by the Create Databasecommand.


User Response: Refer to the Create Databasecommand in the Command Reference for details ofvalid code page and territory code pairssupported by DB2/2.

SQL1206N PRUNE LOGFILE is notsupported in this databaseconfiguration.

Explanation: The PRUNE LOGFILE request isnot supported if:

1. both LOGRETAIN and USEREXIT are set toNO, or

2. the active logfile path is set to a raw device.

User Response: Do not issue the PRUNELOGFILE command for this database.

SQL1207N Communication Managerconfiguration file name cannot befound.

Explanation: The Communication Managerconfiguration file name specified on theCATALOG NODE command was not foundeither in the path specified or in the CMLIBdirectory on the default drive.


User Response: Resubmit the command withthe correct configuration file name and path.

SQL1209W The partner_lu name namespecified in the CATALOG NODEfunction does not exist. One wascreated.

Explanation: The logical partner unit namespecified in the CATALOG NODE function doesnot exist in the Communications Managerconfiguration file located in the CMLIB directoryon the default drive.

A logical unit profile of the specified name wascreated.


SQL1210W Default values were returned forone or more DOSRequester/WINDOWS Requesterconfiguration file parameters.

Explanation: One or more of the DOSRequester/WINDOWS Requester configurationvalues returned was defaulted. The parametermay not be defined in the DOSRequester/WINDOWS Requester configurationfile or the configuration file could not be openedor an error occurred reading the file.

User Response: Ensure that the DOSRequester/WINDOWS Requester configurationfile exists in the appropriate path and that theparameters are explicitly defined.

SQL1211N The computer name name is notvalid.

Explanation: The computer name specified inthe NPIPE protocol structure for the Catalogcommand is not valid. The size of the computername must be 15 characters or less.


User Response: Verify that the computer nameis valid and resubmit the command.

SQL1212N The instance name name is notvalid.

Explanation: The instance name specified forthe Catalog command is not valid. The size of


the instance name must be 8 characters or less.


User Response: Verify that the instance name isvalid and resubmit the command.

SQL1213N The change password LU namename is not valid.

Explanation: The change password logical unit(LU) name specified in the APPN protocolstructure for the CATALOG command is notvalid.

The change password LU name is the remoteSNA LU name and must be 1 to 8 characters.Valid characters are A through Z, a through z, 0through 9, #, @, and $. The first character mustbe alphabetic or a special character: #, @, or $.Lowercase characters are changed to uppercaseby the system.


User Response: Verify the characters specifiedin the change password LU name.

Resubmit the command with a valid changepassword LU name.

SQL1214N The transaction program namename is not valid.

Explanation: The transaction program (TP)name specified in the APPN protocol structurefor the CATALOG command is not valid.

The TP name is the remote SNA Application TPname and must be 1 to 64 characters. Validcharacters are A through Z, a through z, 0through 9, #, @, and $. The first character mustbe alphabetic or a special character: #, @, or $.


User Response: Verify the characters specifiedin the TP name.

Resubmit the command with a TP name.

SQL1215N The LAN adapter address addressis not valid.

Explanation: The LAN adapter addressspecified in the APPN protocol structure for theCATALOG command is not valid.

The LAN adapter address is the remote SNALAN adapter address and must be a12-hexadecimal number.


User Response: Verify the LAN adapteraddress.

Resubmit the command with a valid LANadapter address.

SQL1216N Graphic data and graphicfunctions are not supported forthis database.

Explanation: The code page of the databasedoes not support graphic data. The data typesGRAPHIC, VARGRAPHIC, and LONGVARGRAPHIC are not valid for this database.The GRAPHIC literal and the VARGRAPHICscalar functions are not valid for this database.



User Response: Resubmit the command withvalid data types.

sqlcode: -1216

sqlstate: 56031

SQL1217N The REAL data type is notsupported by the target database.

Explanation: An SQL operation is using a datatype of REAL (single-precision floating pointnumber) as an input or output variable. TheREAL data type is not supported on the targetdatabase for this request.

The statement is not processed.

User Response: Replace the declaration of anyhost variable that corresponds to the SQL data


type of REAL with a declaration thatcorresponds to an SQL data type of DOUBLE inyour application.

sqlcode: -1217

sqlstate: 56099

SQL1218N There are no pages currentlyavailable in bufferpoolbuffpool-num.

Explanation: All of the pages in the bufferpoolare currently being used. A request to useanother page failed.


User Response: The bufferpool is not largeenough to provide pages to all databaseprocesses or threads at this time. The bufferpoolis too small or there are too many activeprocesses or threads.

The statement may be successful if executedagain. If this error occurs frequently, some or allof the following actions may prevent furtherfailures:

1. increase the bufferpool size

2. decrease the maximum number of databaseagents and/or connections

3. decrease the maximum degree of parallelism

4. decrease the prefetch size for table spaces thatare in this bufferpool

5. move some table spaces into otherbufferpools.

sqlcode: -1218

sqlstate: 57011

SQL1219N The request failed because privatevirtual memory could not beallocated.

Explanation: The instance was unable toallocate enough private virtual memory toprocess the request. This may be a result ofshared memory allocations made in other(unrelated) processes.

User Response: The problem may be correctedby:v On OS/2, increasing the min_priv_mem

configuration parameter. This will result inmore private virtual memory being reservedwhen the instance is started.

v Stopping other applications running on themachine, especially those that use largeamounts of shared memory.

sqlcode: -1219

sqlstate: 57011

SQL1220N The database manager sharedmemory set cannot be allocated.

Explanation: The database manager could notallocate its shared memory set. The cause of thiserror may be insufficient memory resourceseither for the database manager or theenvironment in which its operation is beingattempted. Memory resources that can cause thiserror include:

v The number of shared memory identifiersallocated in the system

v The amount of paging or swapping spaceavailable in the system

v The amount of physical memory available inthe system


v Validate that sufficient memory resources areavailable to satisfy the database manager’srequirements, and those of the other programsrunning on the system.

v Reduce database manager’s memoryrequirement for this memory set by reducingthe database manager configurationparameters which affect it. These are:maxagents, maxdari and, numdb.



SQL1221N The Application Support Layerheap cannot be allocated.

Explanation: The Application Support Layerheap could not be allocated. The cause of thiserror may be insufficient memory resourceseither for the database manager or theenvironment in which its operations are beingattempted. Memory resources that can cause thiserror include:

v The number of shared memory identifiersallocated in the system

v The amount of paging or swapping spaceavailable in the system

v The amount of physical memory available inthe system


v Validate that sufficient memory resources areavailable to satisfy the database manager’srequirements, and those of the other programsrunning on the system.

v Reduce the aslheapsz configuration parameter.


sqlcode: -1221

sqlstate: 57011

SQL1222N Not enough storage is available inthe Application Support Layerheap to process the request.

Explanation: All available memory in theApplication Support Layer heap has been used.

User Response: Increase the aslheapszconfiguration parameter.

sqlcode: -1222

sqlstate: 57011

SQL1223N An agent could not be started toservice this request.

Explanation: The request failed because themaxagents configuration parameter limit wouldbe exceeded.

User Response: Increase the maxagentsconfiguration parameter, and/or reduce thenumber of users using the database.

sqlcode: -1223

sqlstate: 57019

SQL1224N A database agent could not bestarted to service a request, or wasterminated as a result of adatabase system shutdown or aforce command.

Explanation: The message may be attributed toany of the following cases.

v The database manager has not been started onthe database server

v The database manager was stopped

v The database manager has already allocatedthe maximum number of agents

v The database agent was forced off by thesystem administrator

v The database agent was terminated due to anabnormal termination of a key databasemanager process

v The application is using multiple contexts withlocal protocol. In this case the number ofconnections is limited by the number of sharedmemory segments to which a single processcan be attached. For example, on AIX, the limitis ten shared memory segments per process.

v A user with SYSADM authority issued aFORCE QUIESCE command while you wereconnected. Because your user ID does not haveCONNECT QUIESCE authority for thedatabase/instance or belong to a group thathas CONNECT QUIESCE authority, you weredisconnected from the database/instance.

Additional federated server cases are:

v The maximum number of processes per user(maxuproc on AIX) at the operating systemlevel has been exceeded.

v In the client/server environment using theTCP/IP protocol, the port number assigned tothe TCP/IP service name on the client is notthe same as the port number on the server.


This situation can be detected by federatedserver or by the data source.

User Response:

v Reissue the database request. If a connectioncannot be established, then ensure that thedatabase manager has been startedsuccessfully. Additionally, ensure that themaxagents database manager configurationparameter is appropriately configured.

v Have the SYSADM unquiesce thedatabase/instance or add the user to thequiesced group.

Federated system users, should also:

v Isolate the problem to the data source rejectingthe request (see the Troubleshooting Guide forprocedures to follow to identify the failingdata source) and ensure that thecommunication subsystem is active and thatthe database manager and requiredcommunication protocol server processes havebeen started on the database server.

v For AIX operating systems, check the setting ofmaxuproc and change it if needed. maxuprocrestricts the number of processes that can rununder a given federated server. The defaultsetting is 40.

You can check the current setting of maxuprocwith the command:

.lsattr -E -l sys0

To view the number of processes currentlyrunning under a given federated server, usethe command:

ps -ef | grep instdj1 | wc -l

where “instdj1” is the instance name of thefederated server.

To change maxuproc, use the command:

chdev -l sys0 -a maxuproc=’nn’

where nn is the new integer value ofmaxuproc.

If the application is using multiple contexts withlocal protocol, then either reduce the number ofconnections in the application, or switch toanother protocol (for example, TCP/IP). Forusers on AIX version 4.2.1 or newer, theenvironment variable EXTSHM can be set to ONto increase the number of shared memorysegments to which a single process can beattached.

sqlcode: -1224

sqlstate: 55032

SQL1225N The request failed because anoperating system process, thread,or swap space limit was reached.

Explanation: An operating system process,thread, or swap space limit was reached. You canfind more information about the problem in theadministration notification log. On AIX systems,the maxuproc value might be too low. OnOS/2-based systems, the THREADSCONFIG.SYS value might be too low.

User Response: Check the administrationnotification log to determine which limit wasreached and increase that limit.

sqlcode: -1225

sqlstate: 57049

SQL1226N The maximum number of clientconnections are already started.

Explanation: The number of client connectionsis already equal to the maximum value definedin the system configuration file.

The operation cannot be processed.

User Response: Wait for other applications todisconnect from the database. If one or moreapplications are required to run concurrently,increase the value for max_connections. The newvalue takes effect after the next successfuldatabase manager start. If the value formax_connections is larger than the value formax_coordagents, the concentrator feature isturned on.


sqlcode: -1226

sqlstate: 57030

SQL1227N The catalog statistic value forcolumn column is out of range forits target column, has an invalidformat, or is inconsistent inrelation to some other statistic.Reason Code = code

Explanation: The value or format of a statisticprovided for an updatable catalog is eitherinvalid, out of range, or inconsistent. The mostcommon checks for value, range and format are(corresponding to code):

1 Numeric statistics must be -1 or >= 0.

2 Numeric statistics representingpercentages (eg. CLUSTERRATIO) mustbe between 0 and 100.

3 HIGH2KEY, LOW2KEY related rules :

v The datatype of any HIGH2KEY,LOW2KEY value must be the same asthe datatype of the correspondinguser column.

v The length of HIGH2KEY, LOW2KEYvalue must be the smaller of 33 or thetarget column’s datatype’s maximumlength.

v HIGH2KEY must be > LOW2KEYwhenever there are 3 or more distinctvalues in the corresponding column.In the case of less than 3 distinctvalues in the column, HIGH2KEY canbe equal to LOW2KEY.

4 PAGE_FETCH_PAIRS related rules :

v Individual values in thePAGE_FETCH_PAIRS statistic mustbe separated by a series of blankdelimiters.

v Individual values inPAGE_FETCH_PAIRS statistics mustnot be longer than 10 digits and mustbe less than the maximum integervalue (MAXINT = 2147483647).

v There must always be a validPAGE_FETCH_PAIRS value if theCLUSTERFACTOR is > 0.

v There must be exactly 11 pairs in asingle PAGE_FETCH_PAIR statistic

v buffer size entries ofPAGE_FETCH_PAIRS must beascending in value. Also, any buffersize value in a PAGE_FETCH_PAIRSentry cannot be greater than MIN(NPAGES, 524287) where NPAGES isthe number of pages in thecorresponding table.

v ″fetches″ entries ofPAGE_FETCH_PAIRS must bedescending in value, with noindividual fetches entry being lessthan NPAGES. Also, any ″fetch″ sizevalue in a PAGE_FETCH_PAIRS entrymust not be greater than CARD(cardinality) statistic of thecorresponding table.

v If buffer size value is the same in twoconsecutive pairs, then page fetchvalue must also be the same in boththe pairs.

5 CLUSTERRATIO andCLUSTERFACTOR related rules :

v Valid values for CLUSTERRATIO are-1 or between 0 and 100

v Valid values for CLUSTERFACTORare -1 or between 0 and 1

v Either CLUSTERRATIO orCLUSTERFACTOR must be -1 at alltimes.

v If CLUSTERFACTOR is a positivevalue, it must be accompanied by avalid PAGE_FETCH_PAIR statistic.

6 The cardinality of a column (COLCARDstatistic in SYSCOLUMNS) or columngroup (COLGROUPCARD inSYSCOLGROUPS) cannot be greaterthan the cardinality of its correspondingtable (CARD statistic in SYSTABLES).

7 No statistics are supported for columnswith the following data types: LONG


VARCHAR, LONG VARGRAPHIC,BLOB, CLOB, DBCLOB, or user-definedstructured types.

8 A statistic is inconsistent with otherrelated statistics for this entity or isinvalid in this context.

User Response: Make sure the new catalogstatistic satisfies the above range/length/formatchecks.

Make sure that any updates to statistics areconsistent in their inter-relationships (eg.cardinality).

sqlcode: -1227

sqlstate: 23521

SQL1228W DROP DATABASE has completedbut the database alias name ordatabase name name could not befound on num nodes.

Explanation: The drop database command hascompleted successfully, however, there are somenodes where the database alias or database namewas not found. It is possible that DROPDATABASE AT NODE was already performedon these nodes.

User Response: This is a warning message only.No response is necessary.

SQL1229N The current transaction has beenrolled back because of a systemerror.

Explanation: One of the following has occurred:

1. A system error, such as node failure orconnection failure, has occurred. Theapplication is rolled back to the previousCOMMIT.

Note that in the case of DB2 utility functions,the behavior is described below:

Import The application is rolled back. If theCOMMITCOUNT parameter wasused, the operation is rolled back toa previous committed point.

Reorg The operation is aborted and mustbe resubmitted.

RedistributeThe operation is aborted, however,some of the operation may havebeen successful. Issuing the requestagain with the ″continue″ option willrestart the operation from the pointof failure.

RollforwardThe operation is aborted and thedatabase is still in rollforwardpending state. The command mustbe resubmitted.

Backup/RestoreThe operation is aborted and mustbe resubmitted.

2. The service port numbers assigned for FCM(Fast Communication Manager)communications are not the same on allnodes in the DB2 instance. Check the servicesfile being used on all nodes to ensure that theports are the same. The ports are definedusing the format:

DB2_<instance> xxxx/tcpDB2_<instance>_END xxxx/tcp

where <instance> is the DB2 instance nameand xxxx is the port number Ensure thatthese port numbers are not being used forDB2 remote client support.

User Response:

1. Try the request again. If the error persists,you can find more information about theproblem in the administration notificationlog. It may be necessary to contact the systemadministrator for assistance since the mostcommon reason for this error is that a nodehas failed.

Note that in an SP environment where thehigh speed switch is used, this error can be asymptom of a failure in the high speedswitch.

2. Update the service ports to be the same on allnodes and try the request again.


The sixth sqlerrd field of the SQLCA willindicate the node number that detected the nodefailure. On the node that detected the failure amessage will be placed in the db2diag.log thatidentifies the failed node.

sqlcode: -1229

sqlstate: 40504

SQL1230W At least one agent id specifiedcould not be forced.

Explanation: At least one agent id specified onthe Force command could not be forced. Causesof this warning may be:

v A nonexistent or invalid agent id wasspecified.

v The agent disconnected from the databasemanager between the time that the agent idswere collected and the Force command wasissued.

v The agent id specified was for a parallel agentwhich cannot be forced.

User Response: If a nonexistent or invalid agentid was specified, retry the command using thevalid agent id.

SQL1231N Invalid Force count specified.

Explanation: The value specified for the countparameter of the Force command is not valid.The value specified must either be a positiveinteger or SQL_ALL_USERS. A value of 0 willresult in an error.

User Response: Correct the value of count andresubmit the command.

SQL1232N Invalid Force mode specified.

Explanation: The value specified for the modeparameter of the Force command is not valid.Only asynchronous mode is supported for theForce command. The parameter must be set tothe value SQL_ASYNCH.

User Response: Set the mode to SQL_ASYNCHand resubmit the command.

SQL1233N The use of this clause or scalarfunction is supported only forgraphic data that is UCS-2.

Explanation: UCS-2 is not supported for thisdatabase. The support of UCS-2 is required forthe following:

v Specifying a graphic string expression as thefirst argument of the VARCHAR scalarfunction

v Specifying a character string expression as thefirst argument of the VARGRAPHIC scalarfunction when a second argument is specified

v Specifying a UCS-2 hexadecimal constantusing the format UX’hex-digits’


User Response: Resubmit the command withvalid data types.

sqlcode: -1233

sqlstate: 560AA

SQL1240N The maximum number ofquiescers has been reached.

Explanation: An attempt was made to acquire aquiesce state on a table space which has alreadybeen quiesced by 5 processes.

User Response: Wait for one of the processes torelease its quiesce state and try again.

SQL1241N An invalid value was specified forthe tbs-name table space definitionwhen creating a database.Attribute is string.

Explanation: The value for a table spaceattribute was out of range. See the DataStructures section of Application DevelopmentGuide for the format of the sqletsdesc structureused for the create database api. The identifiedattribute is the field name of this structure.

User Response: Correct the create databaserequest.


SQL1244W Disconnect for transactionmanager database server-name willoccur at next COMMIT.

Explanation: A disconnect has been issuedagainst a database which is acting as the TMdatabase. The disconnect cannot be completeduntil the next COMMIT is processed.

User Response: If it is necessary that thedatabase which is acting as the TM database bedisconnected immediately, issue a COMMITstatement before execution continues.

sqlcode: +1244

sqlstate: 01002

SQL1245N Connection limit has beenreached. No more connections areallowed from this client.

Explanation: The maximum number ofconcurrent database connections has beenreached for an environment where the number ofconnections is restricted or must be predefined.The primary example of where this would occuris when the NETBIOS protocol is being used.


v Use the SET CLIENT command or API to setthe MAX NETBIOS CONNECTIONS field tothe maximum number of concurrentconnections required. This must be donebefore any connections are made.

sqlcode: -1245

sqlstate: 08001

SQL1246N Connection settings cannot bechanged while connections exist.


v An attempt was made to change theconnection settings for an application usingthe SET CLIENT API. This was rejectedbecause one or more connections exist.

v The application contains both DB2 Call LevelInterface API calls and calls to functions

containing embedded SQL, and the connectionmanagement was not invoked using the CLIAPIs.


v Ensure that the application disconnects fromall servers before attempting to issue the SETCLIENT API (sqlesetc or sqlgsetc) or CLPcommand.

v Ensure that all connection managementrequests are issued via the DB2 Call LevelInterface APIs if CLI is being used by theapplication.

SQL1247N Applications running in an XAtransaction processingenvironment must use theSYNCPOINT TWOPHASEconnection setting.

Explanation: The application was precompiledwith the option SYNCPOINT ONEPHASE orSYNCPOINT NONE, or the SYNCPOINTconnection setting was changed to one of thesevalues using the SET CLIENT API. These settingsare invalid for applications which causetransaction processing syncpoint commands (forexample CICS SYNCPOINT) to be executed.Note that SYNCPOINT ONEPHASE is thedefault precompiler option.


v Re-precompile the application using theprecompiler option SYNCPOINT TWOPHASE.

v Modify the program such that the SETCLIENT API is called to set the connectionoption to SYNCPOINT TWOPHASE prior toany other processing.

sqlcode: -1247

sqlstate: 51025

SQL1248N Database database-alias not definedwith the transaction manager.

Explanation: You attempted to access adatabase that had not been opened by thetransaction manager. A database must be definedto the transaction manager in order to participate


in the two-phase commit process.

User Response: Define the database as aresource manager to the transaction manager ofyour Distributed Transaction Processingenvironment. For example, in a CICSenvironment this requires adding the database tothe XAD file and provides the database aliasname in the XAOpen string of the XAD entry.

sqlcode: -1248

sqlstate: 42705

SQL1251W No data returned for heuristicquery.

Explanation: There are no in-doubt transactionsin the database, nor any transactions that haveended and are waiting to enter the syncpointprocess.


SQL1259N The ARCHIVE LOG commandfailed for database db-name ondatabase partition partition-list dueto SQLCODE SQLCODE.

Explanation: An SQL error occurred whileattempting to issue the ARCHIVE LOGcommand for database db-name on databasepartition partition-list.

User Response: Refer to the SQLCODE in theMessage Reference for the user response andresubmit the ARCHIVE LOG command.

SQL1260N Database name is not configuredfor roll-forward recovery onnode(s) node-list.

Explanation: The specified database is notconfigured for roll-forward recovery on thespecified node(s). If ″,...″ is displayed at the endof the node list, see the administrationnotification log for the complete list of nodes.

The database is not rolled forward on thespecified node(s).

(Note : if you are using a partitioned databaseserver, the node number(s) indicate which

node(s) the error occurred on. Otherwise, it isnot pertinent and should be ignored.)

User Response: Ensure that recovery is requiredon the specified node(s), then restore the mostrecent backup version of the database on thesenodes.

SQL1261N Database name is not inrollforward pending state onnode(s) node-list, so it does notneed to be rolled forward onthese nodes.

Explanation: The specified database is not inroll-forward pending state on the specifiednode(s). This may be because the database hasnot been restored, or was restored with theWITHOUT ROLLING FORWARD option, orroll-forward recovery is complete on these nodes.

If ″,...″ is displayed at the end of the node list,see the administration notification log for thecomplete list of nodes.

The database is not rolled forward.

(Note : if you are using a partitioned databaseserver, the node number(s) indicate whichnode(s) the error occurred on. Otherwise, it isnot pertinent and should be ignored.)

User Response: Do the following:

1. Ensure that recovery is required on thespecified node(s).

2. Restore a backup version of the database onthese nodes.

3. Issue the ROLLFORWARD DATABASEcommand.

SQL1262N The point-in-time specified forrolling forward database name isnot valid.

Explanation: The timestamp parameterspecified for the point-in-time stopping value isnot valid. The timestamp must be entered in ISOformat (YYYY-MM-DD-hh.mm.ss.<ssssss> whereYYYY represents year, MM represents month,DD represents day, hh represents hours, mmrepresents minutes, ss represents seconds, and


ssssss represents optional microseconds).


User Response: Ensure that the timestamp isentered in the correct format.

When you issue a ROLLFORWARD DATABASEcommand, ensure that you are not specifying ayear greater than 2105.

SQL1263N The archive file name is not avalid log file for database name onnode node-number.

Explanation: The specified archive log file existsin the database log directory or the overflow logdirectory on the specified node, but the file is notvalid.

Roll-forward recovery processing stops.

(Note : if you are using a partitioned databaseserver, the node number indicates which nodethe error occurred on. Otherwise, it is notpertinent and should be ignored.)

User Response: To determine the correctarchive log file, issue the ROLLFORWARDDATABASE command with the QUERY STATUSoption. Move the correct archive log file into thedatabase log directory or, if the database is in aconsistent state, change the log path to point tothe correct archive file, and issue theROLLFORWARD DATABASE command again.Alternatively, resubmit the command with theoverflow log path pointing to the correct archivefile.

SQL1264N The archive file name does notbelong to database database-nameon node node-number.

Explanation: The archive log file specified wasfound in the log directory or the overflow logdirectory but does not belong to the specifieddatabase.



User Response: To determine the correctarchive log file, issue the ROLLFORWARDDATABASE command with the QUERY STATUSoption. Move the correct archive log file into thedatabase log directory or, if the database is in aconsistent state, change the log path to point tothe correct archive file and issue theROLLFORWARD DATABASE command again.Alternatively, resubmit the command with theoverflow log path pointing to the correct archivefile.

SQL1265N The archive log file name is notassociated with the current logsequence for database name onnode node-number.

Explanation: For roll-forward recovery, the logfiles need to be processed in correct sequence.The log file sequence is determined by thedatabase that has been restored or the log filesthat have been processed. In addition to this, fortable space level roll-forward recovery, the logfiles must be processed in the sequence throughwhich the current state of the database has beenreached. The specified archive log file was foundin the log directory or the overflow log path forthe database on the specified node but the logfile is not in the correct log sequence.



User Response: To determine the correctarchive log file, issue the ROLLFORWARDDATABASE command with the QUERY STATUSoption. Move the correct archive log file into thedatabase log directory or, if the database is in aconsistent state, change the log path to point tothe correct archive file and issue theROLLFORWARD DATABASE command again.Alternatively, resubmit the command with theoverflow log path pointing to the correct archivefile.


SQL1266N Database name has been rolledforward to timestamp, which ispast the specified point-in-time.

Explanation: Roll-forward is requested to stopat a timestamp that is before the current point intime in the specified database log file. This canhappen when rolling forward either the databaseor a subset of table spaces to a point in time.

Database roll-forward processing stops.

User Response: Specify the correct point in timeor restore the database or table space subset froma backup version and resubmit theROLLFORWARD command.

SQL1267N The system could not finddb2uexit in the current PATHenvironment variable.

Explanation: The user-supplied file db2uexitcannot be found, either because it is not in thecurrent PATH environment variable or it doesnot exist.


User Response: Update the current PATHenvironment variable to include the path todb2uexit or create a db2uexit file and update thecurrent PATH environment variable if necessary.

SQL1268N Roll-forward recovery stoppeddue to error error while retrievinglog file logfile for database name onnode node-number.

Explanation: Roll-forward processing invokesdb2uext2 to retrieve the log file. The error mayhave occurred in db2uext2.

Roll-forward processing stopped. The databaseor table space is still in a roll forward pendingstate.


User Response: See the user exit documentationin the Administration Guide for a description of

the error and resume or terminate roll-forwardrecovery.

SQL1269N Table space level roll-forwardrecovery is already running.

Explanation: An attempt has been made to usetable space level roll-forward recovery but it isalready running. Only one agent can beexecuting roll-forward recovery at any giventime.

User Response: Wait until table space levelroll-forward recovery is complete. If more tablespaces need recovery, initiate table space levelroll-forward recovery again.

SQL1270C The LANG environmentalvariable is set to string. Thislanguage is not supported.

Explanation: The LANG environmental variableis set to a language that is not supported by thedatabase manager. Processing cannot continue.

User Response: Set the LANG environmentalvariable to a language that is supported. Formore information please refer to “NationalLanguage Support” appendix in theAdministration Guide.

Federated system users: see the Federated SystemsGuide for NLS information.

SQL1271W Database name is recovered butone or more table spaces areoff-line on node(s) node-list.

Explanation: This message can occur after crashrecovery, database level roll-forward recovery, ortable space level roll-forward recovery. Fordatabase level roll-forward recovery, the databaseis available for use if the STOP option wasspecified. One or more table spaces on thespecified node(s) are not available. This couldhappen if:

v the STOP option is not specified for a tablespace level roll-forward recovery to a point intime.

v one or more table spaces receive errors duringrecovery.


v additional table spaces are restored while atable space level roll-forward recovery isalready in progress.

v the database is rolled forward past a previouspoint-in-time table space roll-forward, causingall table spaces involved to be placed inrestore pending state.

The table spaces that are off-line can beidentified on the specified node(s) by the LISTTABLESPACES command or the db2dart utility.The administration notification log will providemore information on specific table spaces.



User Response: Repair or restore the tablespaces if necessary and run roll-forwardrecovery. If the same error occurs, try runningtable space level roll-forward recovery offline.

SQL1272N Table space level roll-forwardrecovery for database name hasstopped before completion onnode(s) node-list.

Explanation: Table space level roll-forwardrecovery has stopped on the specified node(s)before all qualifying table spaces could be rolledforward. This can be cause by one of thefollowing:

v The transaction table is full.

v All table spaces being rolled forward receivedI/O errors.

v Point-in-time table space level roll-forwardencountered an I/O error on one of the tablespaces being rolled forward.

v Point-in-time table space level roll-forwardencountered an active transaction that madechanges to one of the table spaces being rolledforward. This transaction could be an indoubttransaction.

v The table space level roll-forward wasinterrupted and, before it was resumed, alltable spaces that were being rolled forward arerestored again.



User Response: Check the administrationnotification log for the cause. Do one of thefollowing depending on the cause:

v Use the LIST TABLESPACES command todetermine if the table spaces received I/Oerrors. If so, repair them.

v If the transaction table became full, include theMAXAPPLS database configuration parameteror try running table space level roll-forwardrecovery offline.

v If the cause is an active or indoubt transaction,complete the transaction.

v If the table spaces were restored after aprevious table space level roll forward wasinterrupted, the previous table space levelroll-forward is now canceled. The next tablespace level roll-forward command will checkfor table spaces in rollforward pending state.

Run table space level roll-forward recoveryagain.

SQL1273N Roll-forward recovery on databasename cannot reach the specifiedstop point (end-of-log orpoint-in-time) because of missinglog file name on node node-number.

Explanation: The Rollforward Database utilitycannot find the specified archive log file in thedatabase log directory or the overflow logdirectory on the specified node.

Roll-forward recovery has stopped.

(Note : if you are using a partitioned database


server, the node number indicates which nodethe error occurred on. Otherwise, it is notpertinent and should be ignored.)


v Move the specified archive log file into thedatabase log directory or, if the database is ina consistent state, change the log path to pointto the correct archive file, and issue theROLLFORWARD DATABASE command again.Alternatively, resubmit the command with theoverflow log path pointing to the correctarchive file.

v If you cannot find the missing log files, restorethe database/table space on all nodes, then dopoint-in-time recovery using a timestamp thatis earlier than that of the missing log file.

SQL1274N The database name requiresroll-forward recovery and thepoint-in-time must be to the endof logs.

Explanation: The database needs to be rolledforward. For database level roll-forward recovery,the point-in-time must be to the end of logsbecause a database level roll-forward to end oflogs is already in progress. To continue the rollforward, the same stoptime must be specified.

For table space level roll-forward recovery, thepoint-in-time must be to the end of logs for oneof the following reasons:

v The system catalogs require roll-forwardrecovery. System catalogs must always berolled forward to the end of logs to remainconsistent with all other table spaces.

v A table space level roll-forward to the end oflogs is already in progress. To continue the rollforward, the same stoptime must be specified.


User Response: Resubmit the ROLLFORWARDcommand specifying ROLLFORWARD TO ENDOF LOGS.

SQL1275N The stoptime passed toroll-forward must be greater thanor equal to timestamp, becausedatabase name on node(s) node-listcontains information later thanthe specified time.

Explanation: The database or at least one of thetable spaces to be rolled forward were backed uponline. An advanced virtual timestamp is in thedatabase or table space backup. The stoptimepassed to roll-forward must be greater than orequal to the time the online backup ended on thespecified node.




v Resubmit the command with a stoptimegreater than or equal to timestamp. Time mustbe specified in CUT (Coordinated UniversalTime).

v Restore an earlier backup on node(s), thenissue the ROLLFORWARD DATABASEcommand again.

SQL1276N Database name cannot be broughtout of rollforward pending stateuntil roll-forward has passed apoint in time greater than orequal to timestamp, because nodenode-number contains informationlater than the specified time.

Explanation: A request was made to bring thedatabase or subset of table spaces out ofrollforward pending state by specifying calleraction SQLUM_ROLLFWD_STOP, SQLUM_STOP,SQLUM_ROLLFWD_COMPLETE, orSQLUM_COMPLETE. However, the database orat least one of the table spaces to be rolledforward was backed up online. The requestcannot be granted until the database or all tablespaces have been rolled forward to the end of


the online backup timestamp on the specifiednode.

This error can also occur if not all the log filesare provided to perform the requested recovery.


User Response: If the stoptime specified on theROLLFORWARD command is smaller thentimestamp, resubmit the command with astoptime greater than or equal to timestamp.

Verify that all the log files were provided. theROLLFORWARD QUERY STATUS commandshows which log file is to be processed next.Some of the reasons for missing log files include:

v the log path has changed. The file can befound in the old log path.

v the userexit program is not able to retrieve thelog file, because it may have been archived toa different location.

If the missing log file is found, copy it to the logpath and resubmit the command.

SQL1277N Restore has detected that one ormore table space containers areinaccessible, or has set their stateto ″storage must be defined″.

Explanation: Restore validates that thecontainers needed by each table space beingrestored are currently accessible on the system.Where possible, restore will create the containersif they do not exist. If they cannot be created, orare currently in use by another table space, or areinaccessible for any other reason, then the list ofcontainers needed must be corrected before therestore can continue.

If this is a redirected restore, the state of eachcontainer of the table spaces being restored is setto ″storage must be defined″. This makes itpossible to use the SET TABLESPACECONTAINERS api or command against thecontainers to redefine their storage.

User Response: To determine the list of

containers for each table space being restored,use the TABLESPACE CONTAINER QUERY apior the LIST TABLESPACE CONTAINERScommand. To specify an updated list for eachtable space, use the SET TABLESPACECONTAINERS api or command. This api orcommand lets you specify whether this shouldbe the initial list of containers (i.e. a subsequentrollforward will redo any ″add container″operations described in the database log) or thefinal list (rollforward will not redo ″addcontainer″ operations).

It is also possible that the container(s) areread-only, in which case the only action requiredbefore continuing with the restore is to giveread/write access to the container.

SQL1278W Roll-forward operation hascompleted successfully. Active orindoubt transactions requiredrollback on node(s) node-list.

Explanation: The roll-forward of a table spacesubset to a point in time was completedsuccessfully, however one or both of thefollowing situations occurred:

1. There was one or more active transactions atthe point in time specified. Each transactionwas rolled back from the table spaces in thetable space subset.

2. There was one or more indoubt transactionsat the point in time specified. Each indoubttransaction was rolled back from the tablespaces in the table space subset.

Transactions that were rolled back from the tablespaces in the table space subset may still becommitted in other table spaces not involved inthe roll-forward.




User Response: The administration notificationlog will contain details on the transactions thatwere rolled back by roll-forward recovery.

SQL1279W Some indexes may not have beenrecreated.

Explanation: An error occurred during indexrecreation while performing a database restart orfollowing a table reorganization which preventedsome of the indexes from being recreatedsuccessfully. Details can be found inadministration notification log.

Database restart or Reorg table was successful.

User Response: Examine the administrationnotification log to determine why the index(es)could not be recreated and correct the problem.The invalid indexes for a table will be recreatedwhen the table is first accessed.

SQL1280N The stoptime passed toroll-forward must be less than orequal to timestamp for databasename because at least one of thetable spaces was already rolledforward to this point in time.

Explanation: At least one of the table spacesspecified by the roll-forward to point in time hasalready been rolled forward to an earlier point intime. It cannot be rolled forward any further.


v Resubmit the command with stoptimetimestamp.

v Restore all table spaces again, and resubmitthe command with a stoptime less thantimestamp.

v Restore the table space backup(s) takenfollowing the earlier table space roll-forwardto point in time and resubmit the commandwith the same stoptime.

Time must be specified in CUT (CoordinatedUniversal Time).

SQL1281N The connection to databasedatabase-alias has been severedbecause the pipe pipe-name hasbeen broken.

Explanation: The connection was lost becausethe DB2 server broke the pipe. The currenttransaction has been rolled back.

User Response: Resubmit the current command.If the error continues, contact your technicalservice representative.





v SQLCA contents, if possible

v Trace file, if possible.

sqlcode: -1281

sqlstate: 40504

SQL1282N The attempt to connect todatabase database-alias failedbecause all the pipe instances onpipe-name are busy.

Explanation: Attempts to connect to the namedpipe failed because the connection was refusedby DB2. There is a limit to the number ofconnections that are allowed on the named pipe.

User Response: Increase the connection limit onthe DB2 server, or terminate some of theapplications using named pipe to free upconnection resources.

sqlcode: -1282

sqlstate: 08001


SQL1283N The attempt to connect todatabase database-alias failedbecause the pipe pipe-name is inuse by another process.

Explanation: The name of the named pipe isalready in used by another process. Named pipesupport did not start.

User Response: Choose a different name bysetting the environment variable DB2PIPENAME,or have the other programs which use namedpipe use a different pipe name.

SQL1284N The attempt to connect todatabase database-alias failedbecause the pipe pipe-name cannotbe found.

Explanation: The server has not started itsnamed pipe support, or the server is using adifferent name for the named pipe.

User Response: Start the database manager andensure the named pipe support starts. If thenamed pipe support has been started, thenensure the name of the named pipe is the samebetween the client and server by setting theenvironment variable DB2PIPENAME to thesame value.

sqlcode: -1284

sqlstate: 08001

SQL1285N The attempt to connect todatabase database-alias failedbecause the pipe pipe-name isinvalid.

Explanation: The alternate pipe name set by theenvironment variable DB2PIPENAME is invalid.

User Response: The value of the environmentvariable DB2PIPENAME must be a valid pipename. The pipe name must be no longer thaneight characters, and has the same syntacticalrestrictions as a normal file name.

sqlcode: -1285

sqlstate: 08001

SQL1286N The connection to databasedatabase-alias has been severedbecause the operating system ranout of resources for pipepipe-name.

Explanation: Named pipe failed because theoperating system ran out of resources (swappingspace, disk space, file handles). The currenttransaction has been rolled back.

User Response: Free up the system resourcesand try again.

sqlcode: -1286

sqlstate: 40504

SQL1287N ATTACH to instance instancefailed because the named pipepipe cannot be found.

Explanation: The server has not started itsnamed pipe support, or the instance name isincorrect.

User Response: Ensure that the databasemanager is started at the server and that thenamed pipe support is started. Ensure that theinstance name is correct.

SQL1288N The remote server does notsupport this operation.

Explanation: The remote server is running on a64-bit platform that does not support non-SQLrequests from Version 7 (or earlier) 32-bit clients.

User Response: Perform this operation from asupported client.

SQL1290N The value of either theDFT_CLIENT_COMM databasemanager configuration parameteror the DB2CLIENTCOMMenvironment variable is not valid.

Explanation: Either an incorrect value wasspecified or the protocol(s) specified are notsupported by the target database. The acceptablevalues are:

v Unix platforms: TCPIP and APPC


v OS/2: TCPIP, APPC, IPXSPX, and NETBIOS

v Windows: TCPIP, APPC (Windows 32-bitonly), NETBIOS, and NPIPE

If more than one value is specified, then theymust be delimited by a comma.

Note that this message may be returned from anintermediate node involved in your connection.For example, if you are trying to connect to aDRDA server via a DB2 Connect gateway andyour client workstation does not use globaldirectory services, this message may be returnedfrom the DB2 Connect gateway.

User Response: Correct the value and try again.

sqlcode: -1290

sqlstate: 08001

SQL1291N A directory services error hasbeen detected. Service:directory-services-type, API: API,function: function, error code: rc.

Explanation: An error has been detected by thedirectory services subsystem. Refer to the tokenvalues for details. The following is theexplanation of the token values:

directory-services-typeThe type of the directory services beingused. Valid tokens include:

v DCE

API The application programming interfaceused to access the above directoryservices. Valid tokens include:

v XDS/XOM

function The name of the directory servicessubsystem function that returned theerror code.

rc The error code returned from the abovefunction. The meaning of the value isspecific to the API being used.

For XDS functions such as ds_read, thereturn code values can be found in theDCE include file xds.h.

For XOM functions such as om_get, thereturn code values can be found in theDCE include file xom.h.


User Response: Ensure that:

v The product providing the directory services isproperly installed and operational.

v You are logged in to the directory serviceswith the appropriate authorization to accessthe directory entries, if login is required by thedirectory services provider, for example, DCE.

If the problem persists, consult with your systemadministrator and/or database administrator todetermine the cause of the problem using the setof tokens provided.

sqlcode: -1291

sqlstate: 08001

SQL1292N The global name of the databaseor database manager instance isinvalid.

Explanation: The global name of the databaseor database manager instance cannot be NULLand cannot be longer than 255 characters. It muststart with either ″/.../″ or ″/.:/″.


User Response: Correct the global name and tryagain.


SQL1293N An error was found in a globaldirectory entry. Error code:error-code.

Explanation: An error has been detected in oneof the global database directory entries used.Refer to the following error codes for details:

1 The database object does not containauthentication information

2 Both the database object and thedatabase locator object do not containcommunication protocol information

10 Entry not a database object

11 Native database name in the databaseobject is either not found or too long

12 Database protocol in the database objectis either not found or too long

13 Invalid authentication value found inthe database object

14 Insufficient or invalid communicationprotocol information in the databaseobject

15 Database locator object name not foundin the database object

16 Database locator object name in thedatabase object invalid

20 Entry not a database locator object

22 Insufficient or invalid communicationprotocol information in the databaselocator object

30 Entry not a routing information object

31 Target database information not foundin the routing information object

32 Insufficient information for the targetdatabase in the routing informationobject

33 No appropriate gateway found in therouting information object

34 Invalid flag for authentication atgateway

35 Database locator object name for thegateway invalid

36 Database name in the target databaseinformation attribute of the routinginformation object is either not found ortoo long

37 Database protocol in the target databaseinformation attribute of the routinginformation object is either not found ortoo long

Note that you may also see this message if theDCE subsystem is not operational, or if you donot have sufficient privilege to read the DCEdirectory entry.


User Response: Make sure the DCE subsystemis operational and that you have the appropriateprivilege to read the directory entry. If theproblem persists, inform the databaseadministrator to correct the error in the directoryentry. Refer to the Administration Guide for theformat of these directory objects.

sqlcode: -1293

sqlstate: 08001

SQL1294N The directory path name beingused for global directory access isnot specified or not valid.

Explanation: In order to use global directoryservices, a directory path name must be specifiedeither in the dir_path_name database managerconfiguration parameter, or in theDB2DIRPATHNAME environment variable. You


either did not specify it, or the name youspecified is not valid.


User Response: Consult your databaseadministrator for the correct name to use, specifyit, and try again.

sqlcode: -1294

sqlstate: 08001

SQL1295N The routing information objectname being used for globaldirectory access is not specified ornot valid.

Explanation: In order to use global directoryservices to access a remote database with adatabase protocol that is not native to this client,the name of a routing information object must bespecified either in the route_obj_name databasemanager configuration parameter, or in theDB2ROUTE environment variable. You either didnot specify it, or the name you specified is notvalid.


User Response: Consult with your databaseadministrator for the correct object name to use,specify it and try again.

sqlcode: -1295

sqlstate: 08001

SQL1296N Valid values must be specified forthe DIR_PATH_NAME andDIR_OBJ_NAME databasemanager configuration parametersif the DIR_TYPE parameter has avalue other than NONE.

Explanation: These three parameters areinterrelated. If the DIR_TYPE value is NONE,then the other two are ignored. If the DIR_TYPEvalue is not NONE, then the other two mustboth contain valid values. The following rulesapply when the DIR_TYPE value is not NONE:

1. The DIR_PATH_NAME and DIR_OBJ_NAMEvalues cannot be NULL (or blanks).

2. If the DIR_TYPE value is DCE, then theDIR_PATH_NAME value must start witheither of the special DCE strings enclosed inthe following quotes: ″/.../″ or ″/.:/″.

User Response: If you want to change theDIR_TYPE value, make sure theDIR_PATH_NAME and DIR_OBJ_NAMEparameters have been specified with the validvalues first. If you want to blank out either theDIR_PATH_NAME or the DIR_OBJ_NAMEparameter, make sure you set DIR_TYPE toNONE first.

SQL1297N This command is currently notsupported on this platform.

Explanation: The function requested using thiscommand is not supported on this platform.

User Response: Do not use this command.

SQL1300 - SQL1399

SQL1300N Invalid DCE principal name incatalog statement.

Explanation: The DCE principal name in thecatalog database operation was invalid. DCE

principal names are subject to the followingconditions:

v If AUTHENTICATION is specified as DCE, aprincipal name must be included in thecatalog statement.


v If AUTHENTICATION is not specified asDCE, a principal name can not be included inthe catalog statement.

v The maximum length of the principal name is1024 bytes.

User Response: Ensure that the principal nameconforms to the conditions above, and resubmitthe catalog command.

SQL1301N An error occurred when accessingthe server’s DCE keytab file.

Explanation: An error occurred when accessingthe server’s DCE keytab file. For a keytab file tobe valid, the following conditions must besatisfied:

v The server’s keytab file exists, has the namekeytab.db2, and is in the sqllib/securitydirectory.

v There is only a single entry in the keytab file.

User Response: Make sure that DCE is started.Next, check that the keytab file exists, andcontains a single entry (with rgy_edit). Retry theoperation.

SQL1302N DCE principal to DB2authorization id mapping error.Reason code: reason-code.

Explanation: An error occurred when mappinga DCE principal to a DB2 authorization id. Referto the reason code below.

v 1. Missing or invalid DCE user to DB2authorization id mapping

v 2. Missing or invalid DCE group to DB2authorization id mapping

User Response: The DCE principal must havean ERA mapping to a DB2 authorization id. Addthe missing entry to the DCE registry, and retrythe operation.

sqlcode: -1302

sqlstate: 08001

SQL1303N Security daemon could not berestarted.

Explanation: An attempt to restart the securitydaemon has failed after communication betweenthe agents and the security daemon was severedor the security daemon terminated abnormally.All new connections to the database managerwill be rejected, as authentication is not possible.

User Response: Stop the database manager andstart it again. If the db2start command fails,follow the user response for that sqlcode.

sqlcode: -1303

sqlstate: 58004

SQL1304N The TCP/IP security type SOCKSis not valid.

Explanation: The TCP/IP security type SOCKSin the TCP/IP protocol structure of the CatalogNode command is invalid with authenticationtype DCE.

User Response: Make sure you do not use thecombination of TCP/IP protocol with securitytype SOCKS and authentication type DCE.

sqlcode: -1304

sqlstate: 08001

SQL1305N An internal DCE error occurred.

Explanation: DB2 processing failed due to aninternal DCE error.

User Response: Make sure DCE is started. Ifthe problem persists, contact a servicerepresentative for assistance.

sqlcode: -1305

sqlstate: 58004

SQL1306N An invalid parameter wasspecified during invocation of thesecurity audit facility. ReasonCode: reason-code.

Explanation: One of the parameters of thesecurity audit API is incorrect. Reasons:


1 An invalid audit option was specified.

2 Invalid pointer to Configure/Describesqleaucfg structure.

3 Invalid Configure/Describe parametertoken.

4 Invalid Configure/Describe parametervalue. The value is incorrect or outsidethe valid range for the parameter.

5 Invalid count specification forConfigure/Describe parameter.

6 Insufficient length allocated forConfigure/Describe parameter.

7 Invalid pointer to Extract sqleauextractstructure.

8 Invalid Extract parameter token.

9 Invalid Extract parameter value. Thevalue is incorrect or outside the validrange.

10 Invalid count specification for Extractparameter.

11 Invalid length for Extract parameter.

User Response: The system administratorshould take specific actions for each of thereasons.

1 Provide the right option value for theaudit API call by looking at the sqlutil.hinclude file.

2 Check to see if a valid pointer has beenprovided to a Configure/Describestructure.

3 The correct parameter should bespecified by looking up the audit facilityreference section for the sqleaucfgparameter tokens.

4 Correct the parameter value by lookingup the valid values in the audit facilityreference.

5 Specify the correct count andallocate/initialize the appropriate lengthfor variable length parameters.

6 Correct the length allocated for

Configure/Describe parameter based onthe error token that is returned in theSQLCA.

7 Check to see if a valid pointer has beenprovided to a Extract structure.

8 The correct parameter should bespecified by looking up the audit facilityreference section for the sqleauextractparameter tokens.

9 Correct the parameter value by lookingup the valid values in the audit facilityreference.

10 Specify the correct count andallocate/initialize the appropriate lengthfor variable length parameters.

11 Correct the length allocated for Extractparameter based on the error token thatis returned in the SQLCA.

SQL1307N An error occurred duringinvocation of the security auditfacility. Reason Code: reason-code.

Explanation: The invocation of the securityaudit API caused an error to occur. Reasons:

1. Audit is already started.

2. Audit is already stopped.

3. Invalid checksum for audit configuration file.

4. The default or user-provided audit pathnameis too long.

5. Could not update the audit configuration file.Either the filesystem is full or the permissionsdo not allow write.

6. Configuration File not found. Either the fileor the directory which contains the file doesnot exist.

7. The extract file is not found.

8. Invalid format of audit records duringextract. The file is corrupted.

User Response: The system administratorshould take specific actions for each of thereasons.

1. No action required.



3. Restore the configuration file from backup orissue ’audit reset’ command.

4. Choose a different audit pathname which iswithin the filename length limit.

5. If the file permissions are incorrect,set thepermissions to allow write by owner. If thefilesystem is full, create free space beforeproceeding.

6. If the audit configuration file is missing, thenrestore it from a backup or issue the ’reset’command to initialize the file to defaults. Ifthe directory is missing, restore from abackup or recreate the database managerinstance.

7. Verify that file exists in the specified path. Iffile missing, restore from backup if available.

8. The audit log file is most likely corrupted. Ifproblem persists for other audit log files,notify DB2 service.

SQL1308W The audit Extract Facilitycompleted Processing. num-recordsrecords were extracted.

Explanation: The security audit extract facilitycompleted its processing succesfully andextracted the specified number of records.

User Response: If zero records were extracted,the user should verify that the extract pathnamecontains extract files and the extract parametersare correct.

SQL1309N Invalid server principal name.

Explanation: The server principal namespecified in the database catalog statement doesnot exist in the DCE registry. Because of this aDCE ticket could not be obtained for the DB2server.

User Response: Make sure that the principalname in the database catalog entry correspondsto the DCE principal being used by the DB2server. It may be necessary to fully qualify theprincipal name.

sqlcode: -1309

sqlstate: 08001

SQL1310N The Database Connection Servicesdirectory service failed whileattempting to access the DatabaseConnection Services directory.

Explanation: The Database Connection ServicesDirectory Service failed because of file errorswhile trying to access the Database ConnectionServices directory file.


User Response: Rerun the function after doingone of the following:

v If you are adding an entry to the DatabaseConnection Services directory, ensure thatthere is sufficient space for the directory file tobecome larger.

v Ensure that no other concurrently runningprogram is trying to access the file.

v Verify that the directory file has not beendamaged. If it is unrecoverable, you musterase it and recreate it or restore it from abacked-up version.

SQL1311N The Database Connection Servicesdirectory cannot be found.

Explanation: The directory cannot be found.The directory may have been deleted.


User Response: Use the CATALOG DCSDATABASE command to add an entry to theDatabase Connection Services directory, orrestore the directory from a backed-up version.

SQL1312W The Database Connection Servicesdirectory is empty.

Explanation: An attempt was made to read thecontents of the Database Connection Servicesdirectory, but no entries existed.

Processing continues, but subsequent commandsexpecting entries to be available cannot beprocessed.

User Response: Use the Catalog DCS Databasecommand to add entries to the directory orrestore a backed-up version that contains entries.


SQL1313N The Database Connection Servicesdirectory is full.

Explanation: The entry cannot be added to theDatabase Connection Services directory becausethe directory has already reached its maximumsize.


User Response: Delete an entry or entries fromthe directory before adding any more entries.

SQL1314N The address of the DatabaseConnection Services directoryentry parameter is not valid.

Explanation: The application program has usedan address for this parameter that is not valid.Either the address points to an unallocated bufferor the buffer is not large enough to contain therequired input.


User Response: Ensure that the applicationprogram has allocated the required buffer areaand resubmit the command.

SQL1315N The local database name is notvalid.

Explanation: A local database name wasspecified that contains characters that are notvalid. All characters must be from the databasemanager base character set.


User Response: Ensure that the characters usedin the local database name are from the databasemanager base character set and resubmit thecommand.

SQL1316N No entry was found in theDatabase Connection Servicesdirectory for the specified localdatabase name.

Explanation: The Database Connection Servicesdirectory service failed because no entry could befound in the Database Connection Services

directory that corresponds to the input localdatabase name.


User Response: Ensure that the local databasename is correct and resubmit the command.

SQL1317N The local database name alreadyexists in the Database ConnectionServices directory.

Explanation: The entry could not be added tothe directory because an entry for that localdatabase name already exists in the directory.


User Response: Specify a unique local databasename or delete the existing entry and add thenew entry.

SQL1318N The length of element name in theinput structure for parameter 1 isnot valid.

Explanation: The length values in the DatabaseConnection Services directory entry structureshould not be less than zero nor greater than themaximum length for the element it represents.


User Response: If an element of the directoryentry structure is specified, the associated lengthvalue should represent the number of bytes inthe element. Otherwise, the length value shouldbe zero. Ensure that all the directory entrystructure elements have the requiredspecifications and lengths for the command andresubmit the command.

SQL1319N The Database Connection Servicesdirectory entries have not beencollected.

Explanation: A request to copy all the directoryentries was received, but either a prior request tocollect the entries was not received or the priorrequest to collect the entries failed.


User Response: Issue a request to open the


directory and collect the entries. Then resubmitthis command.

SQL1320N The Database Connection Servicesdirectory cannot be accessed atthis time.

Explanation: A request to access the DatabaseConnection Services directory failed. Access tothe Database Connection Services directory isdependent on the type of access requested andthe current activity in the directory. If the requestis for the intention of updating the directory,then the directory must not be active. If therequest is to read the directory, then access isallowed if the directory is not being updated.


User Response: Wait for the current activity tocomplete and resubmit the command.

SQL1321N The structure ID specified in thedirectory entry structure is notvalid.

Explanation: The structure ID received in thedirectory entry structure does not represent arecognized value.


User Response: Verify the structure ID passedin the directory entry structure is a valid valueand resubmit the command.

SQL1322N An error occurred when writing tothe audit log file.

Explanation: The DB2 audit facility encounteredan error when invoked to record an audit eventto the trail. There is no space on the file systemthe audit log resides on. Free up space on thisfile system or prune the audit log to reduce itssize.

When more space is available, use db2audit toflush out any data in memory, and to reset theauditor to a ready state. Ensure that appropriateextracts have occurred, or a copy of the log hasbeen made prior to pruning the log, as deletedrecords are not recoverable.

User Response: The system administratorshould take the suggested corrective action sothat the audit facility can resume logging.

sqlcode: -1322

sqlstate: 58030

SQL1323N An error occurred when accessingthe audit configuration file.

Explanation: db2audit.cfg could not be opened,or was invalid. Possible reasons:

v The db2audit.cfg file either does not exist, orhas been damaged. Take one of the followingactions:

– Restore from a saved version of the file.

– Reset the audit facility configuration file byissuing the reset command from thedb2audit executable.

User Response: The system administratorshould take the suggested action to resolve theproblem.

sqlcode: -1323

sqlstate: 57019

SQL1325N The remote database environmentdoes not support the command orone of the command options.

Explanation: An attempt has been made toissue a DB2 workstation database specificcommand or command option against a hostdatabase through DB2 Connect or federatedserver. The following commands generate thiserror when issued against a DB2 for MVS*, DB2for OS/400* or SQL/DS* database:

v OPSTAT (Collect Operational Status)

v DARI (Database Application Remote Interface)

v GETAA (Get Administrative Authorizations)

v GETTA (Get Table Authorizations)

v PREREORG (Prepare to Reorganize Table)

v REORG (Call Reorganize Function)

v RQSVPT/ENSVPT/RLBSVPT (SubtransactionRequests)

v RUNSTATS (Run Statistics).


v COMPOUND SQL ATOMIC STATIC (AtomicCompound SQL)

v ACTIVATE DATABASE

v DEACTIVATE DATABASE

As well, the following commands generate thiserror with incorrect options:

v IMPORT (Import table) The filetype must beIXF, commitcount must be 0, and the firstword in the Action String (e.g. ″REPLACE into...″) must be INSERT.

v EXPORT (Export table) The filetype must beIXF.


User Response: Do not attempt to issue thiscommand against a host database through DB2Connect or federated server.

SQL1326N The file or directory name cannotbe accessed.

Explanation: The file or directory name cannotbe accessed because either the file permissionsare incorrect, the file path is incorrect, or there isinsufficient space in the directory or path.

User Response: Verify that any path or filenamespecified in the command is valid, you have theproper permissions to access the path orfilename, and there is sufficient space to containthe file. Correct the problem and resubmit thecommand. If the problem persists, contact yourSystem Administrator.

SQL1327N An implicit connection attemptfailed. database-name is not a validdatabase name.

Explanation: An attempt to perform an implicitconnection failed. The syntax of the databasealias name specified by the DB2DBDFTenvironment variable is not valid. The databasename must contain 1 to 8 bytes and all thecharacters must be from the database managerbase character set.


User Response: Correct the database alias name

specified by the DB2DBDFT environmentvariable and resubmit your command. If usingthe command line processor, then a ″db2terminate″ should be issued prior to resubmittingthe command. If you do not want an implicitconnection to be performed, remove theDB2DBDFT environment variable.

sqlcode: -1327

sqlstate: 2E000

SQL1328N An implicit connection attemptfailed. The database alias name ordatabase name name was notfound in the local databasedirectory.

Explanation: An attempt to perform an implicitconnection failed. The database name specifiedby the DB2DBDFT environment variable doesnot name an existing database. The databasecould not be found in the database directory.


Note that a CONNECT RESET request issuedwithin a distributed unit of work will attempt animplicit connect to the default database. Thismay be the reason for this error.

User Response:

v Correct the database alias name specified bythe DB2DBDFT environment variable andresubmit the command.

v If the intended action is to remove aconnection while operating in a distributedunit of work environment, consider replacingthe CONNECT RESET statement with aDISCONNECT or RELEASE statement.

v If using the command line processor, then a″db2 terminate″ should be issued prior toresubmitting the command.

v If you do not want an implicit connection tobe performed, remove the DB2DBDFTenvironment variable.

sqlcode: -1328

sqlstate: 42705


SQL1329N The resolved path specified onthe command is too long.

Explanation: The resolved path specified on thecommand exceeds the maximum lengthsupported by the database manager. Theresolved path must be no longer than 215characters in length. During a Create Database,Catalog Database, Open Database Directory forscan, and change database comment commands,the database manager instance name is appendedto the end of the specified path.

User Response: Check that the fully resolvedabsolute or relative path name, including thedatabase manager instance name, does notexceed 215 characters in length. Correct the pathand resubmit the command.

SQL1330N The symbolic destination namename is not valid.

Explanation: The symbolic destination name inthe CPIC protocol structure of the Catalog Nodecommand is either not specified or longer thanthe allowable length. The name must be 1 to 8bytes in length.

User Response: Verify that the symbolicdestination name is specified and that it is notlonger than 8 bytes in length. Resubmit thecommand with a valid symbolic destinationname.

SQL1331N The CPIC security type type is notvalid.

Explanation: The CPIC security type specifiedin the CPIC protocol structure of the CatalogNode command is invalid. The security typespecifies the security information that will beincluded when a database client allocates aconversation with a partner LU, as specified bythe LU 6.2 architecture. Correct values forsecurity type are:

v SQL_CPIC_SECURITY_NONE

– No access security information will beincluded.

Note: This is not supported when usingfederated server. When DB2 Connectis used, it is only supported whenauthentication type is DCE,KERBEROS, or SERVER_ENCRYPT.

v SQL_CPIC_SECURITY_SAME

– A userid will be included together with anindicator specifying that the userid isalready verified. This is not supportedwhen authentication type SERVER is usedwith DB2 Connect or federated server, orwhen authentication type is DCE,KERBEROS, or SERVER_ENCRYPT.

v SQL_CPIC_SECURITY_PROGRAM

– Both a userid and a password will beincluded. This is not supported whenauthentication type CLIENT is used withDB2 Connect or when authentication type isDCE, KERBEROS,or SERVER_ENCRYPT.

User Response: Set the security type to one ofthe above and resubmit the command.

sqlcode: -1331

sqlstate: 08001

SQL1332N The Host Name name is not valid.

Explanation: The host name in the TCP/IPprotocol structure of the Catalog Node commandis either not specified or longer than theallowable length. The name must be 1 to 255characters in length and cannot be all blanks.

User Response: Verify that the host name isspecified and that it is not longer than 255characters in length. Resubmit the commandwith a valid host name.

SQL1333N The Service Name name is notvalid.

Explanation: The service name is the TCP/IPprotocol structure of the Catalog Node commandis either not specified or longer than theallowable length. The name must be 1 to 14characters in length and cannot be all blanks.

User Response: Verify that the service name isspecified and that it is not longer than 14


characters in length. Resubmit the commandwith a valid service name.

SQL1334N The database server cannot beused to route a remote request toa second database server in thisconfiguration.

Explanation: An attempt was made to route arequest through a database server node using anunsupported combination of client and targetdatabase server. Either a client or target databaseprior to release version 2 was used or an attemptwas made to route the request from a DRDAclient to a DRDA target database. The requestmust be routed directly from the client to thenode on which the target database is running.

User Response: Uncatalog the database at theclient machine and then catalog the databasespecifying the node on which the databaseactually resides. Ensure that the node is alsocataloged.

SQL1335N The application requestor name isnot valid

Explanation: An application requestor namewas specified that contains characters that arenot valid. All characters must be from thedatabase manager base character set.

User Response: Ensure that the characters usedin the application requestor name are from thedatabase manager base character set andresubmit the command.

SQL1336N The remote host hostname was notfound.

Explanation: The system cannot resolve theaddress of the remote host. Possible causes are:

v An incorrect hostname value was specifiedwhen the TCP/IP node was cataloged.

v The correct hostname was specified, but wasnot defined in any TCP/IP name serveraccessible to your client node, nor in theclient’s hosts file.

v The TCP/IP name server where the hostnamewas defined was not available at the time youtried to connect.

v TCP/IP is not running.

User Response: Make sure that TCP/IP isrunning and that the hostname specified whencataloging the TCP/IP node is a correct name,and that it is defined in an accessible nameserver or in the local hosts file.

Federated system users: verify that the remotehost is cataloged correctly in theSYSCAT.SERVERS view.

SQL1337N The service service-name was notfound.

Explanation: The system cannot resolve the portnumber associated with the service-name.Possible causes are:

v An incorrect service-name value was specifiedwhen the TCP/IP node was cataloged.

v The correct service-name was specified, butwas not defined in the client’s services file.


User Response: Make sure that theservice-name specified when cataloging theTCP/IP node is a correct name, and that it isdefined in the local services file.

Federated system users must also ensure that thename is defined in the services file at the datasource.

SQL1338N The symbolic destination namesymbolic-destination-name was notfound.

Explanation: The system cannot find the SideInformation associated with thesymbolic-destination-name you specified.Possible causes are:

v An incorrect symbolic-destination-name valuewas specified when the CPIC NODE wascataloged.


v The symbolic destination name and itsassociated side information have not beendefined to the SNA communicationssubsystem.

v The SNA communication subsystem has notbeen started.

User Response: Make sure that thesymbolic-destination-name specified whencataloging the CPIC node is a correct name, andthat it has been defined to the local SNAcommunication subsystem.

Start the SNA communication subsystem if it hasnot been started.

SQL1339N n SQL error(s) were detected inthe execution of a Not AtomicCompound SQL statement, andhave the following identification:error1 error2 error3 error4 error5error6 error7.

Explanation: One or more SQL substatementswithin a Compound SQL statement resulted inSQL errors (negative return codes).

The error tokens will not be returned forCLI/ODBC applications. CLI/ODBC applicationscan use SQLGetDiagRec, SQLGetDiagField, orSQLError APIs to get more information abouteach error.

User Response: Examine the error identificationinformation provided. There will be <n><errorX> tokens filled in, up to a maximum of 7.Each <errorX> represents an SQL statement error.These errors are listed in the order that theywere encountered. If the message text has notbeen formatted, this information can be found inthe second and subsequent tokens of theSQLERRMC field (tokens are separated by a onebyte hexadecimal value 0xFF).

Each <errorX> is of the format PPPSSSSS where:

PPP PPP represents the position of thestatement that caused the error withinthe Compound SQL block, and isleft-justified. For example, if the firststatement failed, this field wouldcontain the number one (″1 ″).

SSSSS SQLSTATE of the statement that failed.

More information can be found by examining theSQLCA itself. The third SQLERRD field containsthe number of rows affected by the compoundSQL statement, the fourth SQLERRD fieldcontains the position of the last statement thatsucceeded, the 5th SQLERRD field contains thenumber of rows affected by referential integritywhen DB2 Client/Server and SQL/DS databasesare accessed, and the 6th SQLERRD fieldcontains the number of statements that failed(returned negative SQLCODES).

sqlcode: -1339

sqlstate: 56091

SQL1340N The file server fileserver was notfound.

Explanation: The system cannot find thespecified file server on the network. Possiblecauses are:

v An incorrect fileserver name was specifiedwhen the IPX/SPX node was cataloged.

v The correct fileserver name was specified, butthe file server was not available at the time theconnect was tried.

User Response: Make sure that the fileservername specified when cataloging the IPX/SPXnode is correct, and that the file server isavailable on the network.

SQL1341N A workstation name must bespecified in the client databasemanager configuration file.

Explanation: A workstation name has not beenspecified in the client database managerconfiguration file. A workstation name must bespecified when using NetBIOS to communicatewith the server.

User Response: Specify a workstation name inthe client database manager configuration file.


SQL1342N The File Server name name ismissing or invalid.

Explanation: The File Server name specified inthe command/API is missing or invalid.

User Response: Verify that a File Server namewas specified, that the name does not containinvalid characters, and is not longer than 48characters in length. Resubmit thecommand/API with a valid File Server name.

SQL1343N The Object Name name is missingor invalid.

Explanation: The Object Name specified in thecommand/API is missing or invalid.

User Response: Verify that the Object Namewas specified, that the name does not containinvalid characters, and is not longer then 48characters in length. Resubmit thecommand/API with a valid Object Name.

SQL1350N The application is not in thecorrect state to process thisrequest. Reason code=rc.

Explanation: Corresponding to rc:

01 The application is currently processingSQL and cannot process the utilitycommand requested.

02 A Backup request is in progress. Awarning was received from the initialutility call indicating that furtherrequests are required before Backup cancomplete.

03 A Restore request is in progress. Awarning was received from the initialutility call indicating that furtherrequests are required before Restore cancomplete.

04 A Rollforward request is in progress. Awarning was received from the initialutility call indicating that furtherrequests are required before Rollforwardcan complete.

05 A Load request is in progress. A

warning was received from the initialutility call indicating that furtherrequests are required before Load cancomplete.

07 Federated system users: the applicationcannot process this command afterexecuting SQL statements.

User Response: Corresponding to rc:

01 Complete the unit of work (using eitherCOMMIT or ROLLBACK) beforereissuing this command.

02-05 Issue the required call(s) to complete theutility in progress, then reissue thiscommand.

07 Federated system users: the applicationmust issue the commands afterestablishing a connection to the databasemanager but prior to any other SQLstatements.

SQL1360N Current processing cannot beinterrupted.

Explanation: The user attempted to interrupt aprocess which is not interruptible.

User Response: Do not interrupt the currentprocess.

SQL1361W Execution time has exceededtimeout value. Do you wish tointerrupt it?

Explanation: If a command takes longer than apre-defined timeout period, a dialog box pops upasking if the (Windows client) user wants tointerrupt it or not.

Note that this message is applicable in Windowsenvironments only, and will only be seen in adialog pop up box.

User Response: There are three choices: YES -interrupt now; NO - continue, don’t prompt me;CANCEL - continue, same timeout.


SQL1362W One or more of the parameterssubmitted for immediatemodification were not changeddynamically. Client changes willnot be effective until the nexttime the application is started orthe TERMINATE command hasbeen issued. Server changes willnot be effective until the nextDB2START command.

Explanation: Some changes to the databasemanager configuration could not be appliedimmediately. For these parameters, the changesbecome effective only after DB2 is started. Thistypically occurs after a DB2START on a serverand after the application restarts on a client.

User Response: To see which parameterchanges took effect dynamically and which onesdid not, retrieve the database managerconfiguration parameters and display theparameter details using the following command:

DB2 GET DBM CFG SHOW DETAIL

Changes to database manager configurationparameters can only take effect dynamically ifyou are attached to the instance. Not allconfiguration parameters support dynamicupdate. To see which parameters can be changeddynamically, refer to the Administration Guide.

If several parameters were submitted in a group,submit the parameters individually. In thosecases where a configuration parameter could notchange dynamically, do one or more of thefollowing:

v for user applications: stop and start theapplication

v for CLP: TERMINATE and reconnect

v for a server: issue DB2STOP and DB2START

SQL1363W One or more of the parameterssubmitted for immediatemodification were not changeddynamically. For theseconfiguration parameters, allapplications must disconnect fromthis database before the changesbecome effective.

Explanation: The database configurationcommand has been successfully processed.However, not all changes were processed rightaway. After the applications disconnect from thedatabase, the first connection to the database willcause the changes to become effective.

User Response: To see which parameterchanges took effect dynamically and which onesdid not, retrieve the database configurationparameters and display the parameter detailsusing the following command:

DB2 GET DB CFG FOR<database-alias> SHOW DETAIL

Changes to database configuration parameterscan only take effect dynamically if you areconnected to the database. Not all configurationparameters support dynamic update. To seewhich parameters can be changed dynamically,refer to the Administration Guide.

If several parameters were submitted in a group,submit the parameters individually. In thosecases where a configuration parameter could notchange dynamically, do one or more of thefollowing:

v Ensure that all applications disconnect fromthe database and issue a db2 connect tocommand.

v Rebind your packages after the newconfiguration parameters take effect so that thenew values will be used during the bind.

v Use the FLUSH PACKAGE CACHE commandto invalidate dynamic statements in the SQLcache.


SQL1364W One or more of the configurationparameters were set toAUTOMATIC in a case where theparameter does not supportAUTOMATIC.

Explanation: One or more of the configurationparameters were set to AUTOMATIC in a casewhere the parameter does not supportAUTOMATIC.

User Response: If the parameter changes weresubmitted as a group, resubmit the changesindividually to see which parameter changeswere successful.

If only one parameter was submitted then thismessage indicates that the value AUTOMATIC isnot supported for this parameter.

To find out which configuration parameterssupport the AUTOMATIC value, refer to theAdministration Guide.

SQL1370N An attempt to quiesce instance ordatabase name1 failed becauseinstance or database name2 isalready quiesced by user username.Quiesce type: type.

Explanation: An attempt was made to quiescean instance or database which would havecaused an overlapping quiesce, such as quiescingan instance while a database is already quiescedby another user.

Quiesce type type refers to the instance ordatabase already quiesced and is a ’1’ for aninstance and a ’2’ for a database.

User Response: Contact the user who currentlyhas the instance or database quiesced todetermine when DB2 will no longer be quiesced,and retry the request at that time.

SQL1371W Instance or database name isalready quiesced. Quiesce type:quiesce-type.

Explanation: An attempt was made to quiescean instance or database which is alreadyquiesced.


SQL1372N Cannot perform a quiesce whilein a transaction.

Explanation: An attempt was made to quiesce adatabase or instance while the user issuing thequiesce has uncompleted units of work. Quiescecannot be issued while in this state.

User Response: Complete the unit of work(COMMIT or ROLLBACK) and retry the request.

SQL1373W Cannot unquiesce instance ordatabase name, because it is notquiesced.

Explanation: Unquiesce failed because theinstance or database is not quiesced.

User Response: Ensure that the unquiesce isbeing issued for the correct instance or database.

SQL1374N Cannot QUIESCE RESET instanceor database name, because it hasbeen quiesced by another userusername.

Explanation: The instance or database isquiesced, but you are not the quiescer.

User Response: Ensure that the quiesce reset isbeing issued for the correct instance or database.

SQL1375N An invalid parameter was passedto the api. Parameter parm-code isin error.

Explanation: parm-code indicates the parameterin error:

1 scope

2 options

The value may be out of range or invalid.

User Response: Check the syntax of the api,correct the parameter and try again.


SQL1380N An unexpected Kerberos securityerror has occurred.

Explanation: An unexpected Kerberos securityerror occurred during authentication.


SQL1381N The Security Support ProviderInterface is not available.

Explanation: Authentication failed because theSecurity Support Provider Interface (SSPI) wasnot available.

User Response: When running under Windowsoperating system, ensure that the file security.dllexists under the system directory. Also ensurethat SSPI is supported for the operating systemthat is being used.

SQL1382N Kerberos support is not available.

Explanation: Authentication failed becauseKerberos support is not installed.

User Response: Ensure that Kerberos support isinstalled and operational, then retry theconnection.

SQL1383N The target principal name is notvalid.

Explanation: The target principal name that wasspecified in the CATALOG DATABASEcommand is not valid.

User Response: Remove the database entry thathas the invalid target principal name by usingthe UNCATALOG DATABASE command.Re-catalog the database entry with a valid targetprincipal name using the CATALOG DATABASEcommand and retry the connection.

When running in a Windows operating systemenvironment, the target principal name is thelogon account name of the DB2 service in theformat of <domain name>\<user ID>.

SQL1384N Unable to complete mutualauthentication.

Explanation: The connection failed becauseeither the client or server was unable to completemutual authentication.

User Response: If the target principal name wasspecified in the CATALOG DATABASEcommand, ensure that the target principal nameis valid for the server to which the client isattempting to connect or attach.

When running in a Windows operating systemenvironment, the target principal name is thelogon account name of the DB2 service in theformat of <domain name>\<user ID>.

If the target principal name appears to beinvalid, then contact IBM service for assistance.

SQL1390C The environment variableDB2INSTANCE is not defined oris invalid.

Explanation: The environment variableDB2INSTANCE is not defined or is not set to avalid instance owner.

User Response: Set the DB2INSTANCEenvironment variable to the name of the instanceto use. If you do not know the name of theinstance to use or how to set the DB2INSTANCEenvironment variable to the instance name, referto the Administration Guide.

Federated system users: refer to the FederatedSystems Guide for DB2INSTANCE information.

Ensure your PATH environment variablecontains the sqllib/adm path in the homedirectory of the instance you want to use (forexample, /u/instance/sqllib/adm, where/u/instance is the home directory of the instanceowner on a UNIX system).

SQL1391N The database is already in use byanother instance.

Explanation: The request failed because thedatabase is in use by another instance of thedatabase manager (a database may only be usedby one instance.) This may be caused by


attempting to access a database located on amounted file system accessible to anotherinstance located on another machine.

This can also occur if you have an openconnection (via SNA) to a database and thedatabase manager was brought downabnormally.

User Response:

v Validate that you are using the correctdatabase and ensure no other instance usesthis database.

v If the database manager was brought downabnormally, and you have a command lineprocessor connection to it, perform a db2terminate to close the offending openconnection before attempting to connect again.

sqlcode: -1391

sqlstate: 51023

SQL1392N Multiple instances of applicationsusing prep,-bind,-import,-export isnot supported.

Explanation: Only 1 instance of prep, bind,import, or export can be running at any one timewithin WINDOWS.

User Response: Within WINDOWS, do notattempt to start more than 1 application that usesprep, bind, import, or export.

SQL1393C The environment variableDB2PATH is not defined or isinvalid.

Explanation: The environment variableDB2PATH is not defined or is not set to a validdirectory path.

User Response: Set the DB2PATH environmentvariable to the directory where the databasemanager is installed.

SQL1394N The instance is not defined.

Explanation: The new instance can not be setfor the application because the instance is notdefined.

User Response: Ensure that the specifiedinstance exists. Use the db2ilist command todisplay the list of instances:

db2ilist

SQL1395N Unable to switch to anotherinstance because the application isusing multiple contexts.

Explanation: The request to switch to anotherinstance failed because the application is usingmultiple contexts.

User Response: Ensure that the application isnot using multiple contexts before switching toanother instance.

SQL1396N Unable to switch to anotherinstance because the application isconnected to a database orattached to an instance.

Explanation: Request to switch to anotherinstance failed because the application isconnected to a database or attached to aninstance.

User Response: Ensure that the application isnot connected to any database or attached to anyinstance before switching to another instance.

SQL1397N The DB2 service failed to logon.

Explanation: DB2 service did not start due to alogon failure.

User Response: If you are starting the DB2Administration Server, then use the DB2ADMINSETID command to set a new logon account. Ifyou are starting a DB2 server on Windows NT,you can set the logon account for a DB2 serviceby using the Services dialog box from theControl Panel.

SQL1400 - SQL1499


SQL1400N Authentication is not supported.

Explanation: The authentication type suppliedis not one of the supported types.

The command can not be processed.

User Response: The user should reissue thecommand with a valid parameter value.

See Application Development Guide for a list ofsupported authentication types.

SQL1401N Authentication types do notmatch.

Explanation: The user is attempting to connectto a remote database which is cataloged on thelocal node with a different authentication typefrom the remote node.

Federated system users: this message can alsoappear when:

v A data source is identified inSYSCAT.SERVEROPTIONS with SETTING=’N’for OPTION =’PASSWORD’ and the datasource is not running in trusted client mode(that is, the data source expects a password)

v The data source is identified inSYSCAT.SERVEROPTIONS with SETTING=’Y’for OPTION =’PASSWORD’ and the datasource is running in trusted client mode (thatis, the data source does not expect a password)

v There is no server option specified forOPTION=’PASSWORD’ inSYSCAT.SERVEROPTIONS and the systemdefault value for PASSWORD violates the datasource password requirement.

User Response: The command can not beprocessed.

The user should recatalog the database alias onthe client node with the same authentication typeas the remote database. Resubmit the command.

Federated system users:

v If the problem is that the data source requiresa password but SYSCAT.SERVEROPTIONScontains SETTING=’N’ forOPTION=’PASSWORD’ for that server, alterSYSCAT.SERVEROPTIONS to reflect the true

data source password requirement using theALTER SERVER SQL statement.

v If the problem is that the data source does notrequire a password butSYSCAT.SERVEROPTIONS containsSETTING=’Y’ for OPTION=’PASSWORD’ forthat server, alter SYSCAT.SERVEROPTIONS toreflect the true data source passwordrequirement using the ALTER SERVER SQLstatement.

v If the server option for OPTION=’PASSWORD’is not set in SYSCAT.SERVEROPTIONS, createan entry using the CREATE SERVER SQLstatement to reflect the true data sourcepassword requirement.

sqlcode: -1401

sqlstate: 08001

SQL1402N Unable to authenticate user due tounexpected system error.

Explanation: Call your system administrator.On unix-based systems, the file db2ckpw may nothave the correct permission bits set, or thesystem may have run out of swap/paging space.On Windows NT, the DB2 security service maynot have been started or the account may belocked.



User Response: On unix-based systems, havethe system administrator ensure the correctaccess permissions are set for db2ckpw, and thatthere is enough swap/paging space allocated. OnWindows NT, have the system administratorverify that the DB2 security service is installedand started. If the service is running then ensurethat the account is not locked.

SQL1403N The username and/or passwordsupplied is incorrect.

Explanation: The username and/or passwordsupplied is incorrect or not a validusername/password combination or the database


to which you are attempting to connect to has anauthentication type of SERVER and no usernameand password was supplied on the CONNECTTO statement.

If DB2 Connect is being used, the problem maybe that the DCS directory entry for the hostconnection could not be found.

If a connection is being made from an OS/2client to a UNIX-based server with authenticationserver, and the userid and password are beingpicked up from UPM, then the userid on theserver must be defined in lowercase and have anuppercase password.



User Response: Supply the correct usernameand password combination.

Federated system users: ensure that the entry inSYSCAT.USEROPTIONS contains the correctusername and password for the data sourcebeing accessed.

sqlcode: -1403

sqlstate: 08004

SQL1404N Password expired.

Explanation: Your password has expired.

User Response: Change your password, thenretry the request using the new password. Youcan use the DB2 Client Configuration Assistant,or Command Line Processor CONNECT andATTACH commands to change your password.

sqlcode: -1404

sqlstate: 08004

SQL1405N Unable to communicate with localDB2 authentication server.

Explanation: The application failed toauthenticate due to an error whilecommunicating to the local DB2 authenticationserver.

User Response: Ensure that the DB2authentication server is started by entering thefollowing command from an OS/2 window:

detach db2upm

SQL1415N The statement was compiled fordiagnostic purposes only and hasnot been executed.

Explanation: The statement was processedthrough parts of the system to collect diagnosticinformation using service features. The necessarysteps to allow further processing of the statementhave not been completed.

User Response: This error is returned toprevent further processing by the system ofstatements prepared using service features and isexpected.

SQL1420N Too many concatenation operators.

Explanation: The database manager has reachedan internal limit while evaluating an expression,of long or large object string result type, thatcontains concatenation operators.

User Response: Reduce the number ofconcatenations in the expression and try again.

sqlcode: -1420

sqlstate: 54001

SQL1421N MBCS conversion error occurredwhen converting host variable orsqlvar number to or from wchar_tformat. Reason code rc.

Explanation: A C/C++ application withembedded SQL statements was precompiled withthe WCHARTYPE CONVERT option. At runtime,the application received an error which occurredduring conversion in either wcstombs(), for inputhost variables, or mbstowcs(), for output hostvariables. The host variable or sqlvar numberindicates which data item experienced theproblem. Valid reason codes are:

1 the problem occurred with input data

2 the problem occurred with output data


User Response: If application data is already inMBCS format, re-precompile the application withWCHARTYPE NOCONVERT and re-build. Ifapplication data is intended to be in wchar_tformat, then input data failing in wcstombs()may be corrupt. Correct the data and re-executethe application.

sqlcode: -1421

sqlstate: 22504

SQL1422N The size of the container isinvalid.

Explanation: One of the containers to be usedin a database managed table space is either toolarge or too small. A container must be at least 2* extentsize pages in length. The maximum sizeof a container is operating system dependent.The most common system limit is 2 gigabytes(524288 4K pages).

User Response: Check the administrationnotification log for details. Then correct the SQLstatement.

sqlcode: -1422

sqlstate: 54039

SQL1423N The query includes a column witha large object data type.

Explanation: The query includes a column witha data type of BLOB, CLOB or DBCLOB. Ingeneral, such data types cannot be handled fromclients available prior to Version 2.1.

The error occurred for a condition thatcorresponds to warning SQLCODE +238. See thismessage for details that explain the condition.The client level receiving this message cannotprocess BLOB data types. It may be able tohandle CLOB and DBCLOB data types by usingthe SUBSTR function or by setting the data typein the SQLDA to one of the character data typesavailable in Version 1 if the LOB column is notlarger than the supported length of the characterdata type.

User Response: Change the query to excludeany column that has a data type of BLOB, CLOB

or DBCLOB. This is the only possible action ifthe query includes a column of type BLOB. If thecolumn (say C1) is a CLOB, you could useCAST(C1 AS LONG VARCHAR) to get the first32700 characters. Similarly for DBCLOB column(DC1) use CAST(DC1 AS LONG VARGRAPHIC)to get the first 16350 characters. If the applicationcode can be changed, code can be added tochange the SQLDA to use LONG VARCHAR orLONG VARGRAPHIC for CLOB and DBCLOB.

sqlcode: -1423

sqlstate: 56093

SQL1424N Too many references to transitionvariables and transition tablecolumns or the row length forthese references is too long.Reason code=rc.

Explanation: The trigger includes aREFERENCING clause that identifies one ormore transition tables and transition variables.The triggered action of the trigger containsreferences to transition table columns ortransition variables with one of the followingconditions identified by the reason code:

1 references total more than the limit ofthe number of columns in a table

2 sum of the lengths of the referencesexceeds the maximum length of a rowin a table.

User Response: Reduce the number ofreferences to transition variables and transitiontable columns in the trigger action of the triggerso that the length is reduced or the total numberof such references is less than the maximumnumber of columns in a table.

sqlcode: -1424

sqlstate: 54040

SQL1425N A password has been suppliedwithout a userid.

Explanation: Any command/API that accepts auserid and password will not accept a passwordwithout a userid.


User Response: Resubmit the command/APIand supply a userid if you are also supplying apassword.

SQL1426N A default instance cannot bedetermined.

Explanation: If an explicit ’attach to instance’has not been performed, instance commands tryto form an implicit attachment to a defaultinstance. The default instance is determined fromthe DB2INSTDFT and DB2INSTANCEenvironment variables. If neither of these are set,then no implicit attachment can be formed.

User Response: Set one of these environmentvariables to a valid instance name and resubmitthe command.

SQL1427N An instance attachment does notexist.

Explanation: The application is not attached toan instance. The attempted command/APIcannot be executed unless there is an existinginstance attachment.

User Response: If the error occurred whendetaching from an instance, continue processing.If the error occurred during the execution of anyother command, attach to an instance and reissuethe failed command.

SQL1428N The application is alreadyattached to nodename1 while thecommand issued requires anattachment to nodename2 forsuccessful execution.

Explanation: In order to successfully process thecommand, an attachment to a node other thanthat which currently exists is required. Theapplication must either: 1) have no attachmentwhen the command is issued, or 2) already beattached to the node required by the command.

User Response: Ensure that the application hasno attachment before issuing the command orthat the attachment that exists is to the correctnode.

SQL1429N A node directory entry cannot becreated in which the node namematches the value of theDB2INSTANCE environmentvariable.

Explanation: The CATALOG NODE commandor API does not allow an entry whose nodenamematches the value of the DB2INSTANCEenvironment variable.

User Response: Choose another node name forthe node being cataloged and try again.

SQL1430N The database name database cannotbe found in the system databasedirectory on node nodename.

Explanation: When specific database names areprovided to the database monitor, thosedatabases must reside either at the node towhich you are currently attached or at the localnode.

User Response: Make sure the databases listedin the request all reside at the node to which youare attached or at the local node. Reissue therequest.

SQL1431N The relative path path is notallowed when executing remotely.

Explanation: When the application is remotefrom the server, relative paths are not allowed.

User Response: Specify a fully qualified paththat is valid at the server and reissue thecommand.

SQL1432N A request has been sent to aserver using a database protocolwhich the server does notrecognize.

Explanation: This error is caused by sending aDB2 request to a server which does notunderstand the database protocol being used totransmit the request. This situation will occurmost frequently when sending a DB2 ATTACHrequest to a server listed in your node directorywhich is not a DB2 Version 2 or greater server.


This error will also arise if you send an attachrequest to DB2 for AS/400, DB2 for MVS, or DB2for VM and VSE servers.

User Response: Do not attempt to attach to anyof the servers listed above.

SQL1433N The application is alreadyconnected to database1 while thecommand issued requires aconnection to database2 forsuccessful execution.

Explanation: In order to successfully process thecommand, a connection to a database other thanthat which currently exists is required. Theapplication must either: 1) have no connectionwhen the command is issued, or 2) already beconnected to the database required by thecommand.

User Response: Ensure that the application hasno connection before issuing the command orthat the connection that exists is to the correctdatabase.

SQL1434N A CONNECT or ATTACHstatement failed because of aclient/server incompatibilitybetween 32 bit and 64 bitplatforms.

Explanation:

1. Version 7 does not support client/serverconnections between 32 bit and 64 bitplatforms.

2. Version 8 Windows 64-bit database serverdoes not support client/server connectionsfrom Version 7 64-bit clients.

User Response: For scenario 1 listed above, youcan issue a CONNECT or ATTACH statement inthe following scenarios:

v from a 32 bit client to a 32 bit server

v from a 64 bit client to a 64 bit server

For scenario 2 listed above, reissue the statementfrom a supported client.

sqlcode: -1434

sqlstate: 08004

SQL1440W The WITH GRANT OPTION hasbeen ignored on the GRANT(Database Authorities) statement,GRANT (Index Privileges)statement, or when grantingCONTROL privilege on a table orview.

Explanation: The WITH GRANT OPTION isnot applicable when granting databaseauthorities or privileges or privileges on indexes.The WITH GRANT OPTION does not apply toCONTROL privilege on tables, views, indexes, orpackages.

All valid requested privileges were granted.

User Response: When granting databaseauthorities or index privileges do not include theWITH GRANT OPTION clause. When grantingCONTROL, use a separate grant statement forthe CONTROL privilege without specifying theWITH GRANT OPTION clause.

sqlcode: +1440

sqlstate: 01516

SQL1441N Invalid parameter. Reason codecode.

Explanation: The following is a list of validreason codes:

1 A NULL was passed in for the contextpointer.

3 The context pointer has been initialized,but not to a valid context area.

4. Invalid option

5 reserved parameter was not NULL

User Response: Ensure that the applicationcontext pointer has been properly initialized andthat any options used are valid and try again.


SQL1442N The context is not in use or is notin use by the current thread.Reason code code.

Explanation: The call failed because:

1 The context is not in use by any thread(no attach was done)

2 The context is not in use by the currentthread.

3 The current thread is not using acontext.

User Response: For a detach call, ensure thatthe context is the one in use by the currentthread, and that a corresponding attach wasdone.

For a get current context call, ensure that thethread is currently using a context.

SQL1443N Thread is already attached to acontext.

Explanation: The user attempted to attach acontext to a thread, and the thread is alreadyusing a context.

User Response: Detach from the previouscontext before attaching to a new one.

SQL1444N The application context cannot bedestroyed because it is in use.

Explanation: The user attempted to destroy anapplication context while it is still in use. Eitherthere is a thread attached to the context, or thecontext has a CONNECT or ATTACH associatedwith it. A CONNECT RESET or DETACH mustbe done (if a CONNECT or ATTACH has beendone), and all threads must detach from thecontext before it can be destroyed.

User Response: Ensure that all calls to attach toa context have a corresponding detach, allCONNECTS have a corresponding CONNECTRESET, and all ATTACHES have a correspondingDETACH.

SQL1445N Thread or process does not have acontext to use.

Explanation: A context type ofSQL_CTX_MULTI_MANUAL is in effect, but thecurrent thread or process has not been attachedto a context.

User Response: Make sure the current thread orprocess is attached to a context before makingany database calls.

SQL1450N Invalid registration informationpointer.

Explanation: An invalid registration informationpointer was passed to the register/deregisterDB2 server command/API.

User Response: Verify that a valid pointer waspassed to the register/ deregister DB2 servercommand/API.

SQL1451N Register/deregister DB2 servermust be issued from a servernode.

Explanation: Register/deregister DB2 serverwas issued from an invalid node.

User Response: Reissue the register/deregisterDB2 server command/API from a server node.

SQL1452N An invalid registration locationwas specified.

Explanation: An invalid registration locationwas passed to the register/deregister DB2 servercommand/API.

User Response: Verify that a valid registrationlocation was passed to the register/deregisterDB2 server command/API.

SQL1453N The entry in the databasemanager configuration file for fileserver name is missing or invalid.

Explanation: The file server name specified inthe configuration command/API or in thedatabase manager configuration file is missing orinvalid.


User Response: Verify that a file server namewas specified, that the name does not containinvalid characters, and is not longer than 48characters in length. Update the file server namein the database manager configuration file andresubmit the command/API.

SQL1454N The entry in the databasemanager configuration file forobject name is missing or invalid.

Explanation: The object name specified in theconfiguration command/API or in the databasemanager configuration file is missing or invalid.

User Response: Verify that an object name wasspecified, that the name does not contain invalidcharacters, and is not longer than 48 charactersin length. Update the object name in thedatabase manager configuration file andresubmit the command/API.

SQL1455N The entry in the databasemanager configuration file for IPXsocket number is missing orinvalid.

Explanation: The IPX socket number specifiedin the configuration command/API or in thedatabase manager configuration file is missing orinvalid.

User Response: Verify that an IPX socketnumber was specified, that the number does notcontain invalid characters, and is not longer than4 characters in length. Update the IPX socketnumber in the database manager configurationfile and resubmit the command/API.

SQL1456N The object name specified in thedatabase manager configurationfile already exists on the NetWarefile server.

Explanation: A duplicate object name wasfound when trying to register the DB2 serverobject name on the NetWare file server.

User Response: The object name specified inthe database manager configuration file isalready in use. Change the object name and then

re-register the DB2 server.

SQL1457N Register/deregister failed to loginto the NetWare file serverspecified because a NetWaredirectory services connection isalready established to that fileserver.

Explanation: A bindery login usingNWLoginToFileServer cannot be performed if aNetWare directory services connection is alreadyestablished to the specified file server.

User Response: Sever the directory servicesconnection by logging out and detaching fromDirectory Services, and then reissueregister/deregister.

SQL1458N IPX/SPX has been configured inthe database managerconfiguration file for directaddressing. It is not necessary toregister/deregister the DB2 serverat/from a NetWare file server.

Explanation: Issuing register/deregister is notnecessary since the database managerconfiguration file has been configured forIPX/SPX direct addressing. ie. Fileserver andobjectname have been specified as ’*’.

User Response: Note that since the DB2 serverhas been configured for direct addressing only,IPX/SPX clients using fileserver addressing willnot be able to connect to this server. For theserver to support both types of IPX/SPX clientaddressing, specify a fileserver and objectnamein the database manager configuration file.

SQL1460N The environment variable variablerequired for SOCKS server nameresolution is not defined or notvalid.

Explanation: The SOCKS environment variableSOCKS_NS or SOCKS_SERVER is not defined.SOCKS protocol support requires that both theseenvironment variables be defined.


SOCKS_NSThis is the IP address of the domainname server where the SOCKS server isdefined.

SOCKS_SERVERThis is the hostname of the SOCKSserver.

User Response: Define the missing environmentvariable and resubmit the command.

SQL1461N The security option security is notvalid.

Explanation: The SECURITY option for aTCP/IP node has a value other than ’SOCKS’.This option is used to enable the TCP/IP nodebeing cataloged to use SOCKS protocol supportto traverse a firewall. No value other than’SOCKS’ is permitted.

User Response: Verify that SOCKS protocolsupport is required. If so, re-catalog the nodewith SECURITY SOCKS. If not, re-catalog thenode, but omit the SECURITY option.

SQL1462N Request is only valid for asyncpoint manager connection.

Explanation: A request was attempted which isonly valid for a syncpoint manager connection,but the syncpoint manager instance is notconnected to.

User Response: Connect to the syncpointmanager instance and reissue the request.

SQL1468N The database manager TCP/IPlistener must be configured andrunning on the server instanceinstance (nodenum node-num1)before attempting to CONNECTor ATTACH to node node-num2.

Explanation: The SET CLIENT command or apior the environment variable DB2NODE was usedto set the node for CONNECT or ATTACH tonode-num2. In order to CONNECT or ATTACH tothis node, the Database Manager TCP/IP listenermust be configured and running on the serverinstance instance (node node-num1).

Note: This message may be returned by animplicit CONNECT or ATTACH.

User Response: Either:

v Ensure that svcename has been specified in thedatabase manager configuration on theinstance instance, node node-num1, theDB2COMM environment variable has been setto use TCP/IP, and that TCP/IP listener wassuccessfully started at DB2START time.

or

v Explicitly catalog the node and database.

sqlcode: -1468

sqlstate: 08004

SQL1469N Instance instance-name (nodenumnode-num1) does not have nodenode-num2 specified in itsdb2nodes.cfg file.

Explanation: The SET CLIENT command or apior the environment variable DB2NODE was usedto set the node for CONNECT or ATTACH tonode-num2. Subsequent CONNECT or ATTACHprocessing was unable to locate this node in thedb2nodes.cfg file on the instance instance-name(node node-num1).

Note: This message may be returned by animplicit CONNECT or ATTACH.

User Response: Ensure that the node numberspecified by the SET CLIENT command or api orthe DB2NODE environment variable exists in thedb2nodes.cfg file of the intermediate instanceinstance-name, node node-num1.

sqlcode: -1469

sqlstate: 08004

SQL1470N Value of DB2NODE environmentvariable is not valid.

Explanation: The DB2NODE environmentvariable indicates the node the application willattempt to connect to. If DB2NODE is unset or isblank, the application will attempt to connect tothe default node. Otherwise, DB2NODE must be


set to the node number of one of the nodesdefined on the same host as the application.

User Response: Set the DB2NODE environmentvariable to one of the following values:

unset causes the application to connect to thedefault node.

blank causes the application to connect to thedefault node.

A numbercauses the application to connect to thenode with that node number. The nodemust be running on the same host asthe application.

sqlcode: -1470

sqlstate: 08001

SQL1471N Cannot connect to databasedatabase-name on node node-numberbecause the database on this nodeis not synchronized with catalognode.

Explanation: The end-of-log information on thisnode does not match the corresponding recordon the catalog node. This can be caused byrestoring the database on various nodes withbackups taken from different times.

User Response: If the database is restoredwithout rolling forward on one node, ensure thatthe database is restored from consistent offlinebackups on all nodes without rolling forward.

sqlcode: -1471

sqlstate: 08004

SQL1472N Cannot connect to databasedatabase-name on node node-numberbecause the difference betweenthe system time on the catalognode and the virtual timestampon this node is greater than themax_time_diff database managerconfiguration parameter.

Explanation: The system time difference for themachines in the configuration (listed in thedb2nodes.cfg file) is greater than themax_time_diff database manager configurationparameter.

User Response: Synchronize the system timeson all machines, and ensure that themax_time_diff parameter is configured to allowfor normal communication delays among thedatabase machines.

If the above does not fix the problem, see theAdministration Guide for possible causes andactions.

sqlcode: -1472

sqlstate: 08004

SQL1473N Cannot commit the transactionbecause the time differencebetween the system time on thelocal node and the virtualtimestamps of node(s) node-list isgreater than the max_time_diffdatabase manager configurationparameter. The transaction isrolled back.


If ″,...″ is displayed at the end of the node list,see the syslog file for the complete list of nodes.



sqlcode: -1473

sqlstate: 40504

SQL1474W The transaction completedsuccessfully, but the timedifference between the systemtime on the local node and thevirtual timestamps of node(s)node-list is greater than themax_time_diff database managerconfiguration parameter.


This warning message is returned to read-onlytransactions because they are not affected by thiscondition. However, other transactions would berolled back. This message is to inform the userabout this condition so that action can be takenat the earliest possible time.



sqlcode: 1474

sqlstate: 01607

SQL1475W A system error occurred duringCONNECT RESET processing.

Explanation: The CONNECT RESET wassuccessful but a system error such as a nodefailure or a communications error may haveoccurred.

User Response: Check the administrationnotification log for details. The database at thisnode may need to be restarted.

sqlcode: 1475

sqlstate: 01622

SQL1476N The current transaction was rolledback because of error sqlcode.

Explanation: The transaction was rolled backbecause:

1. An implicit or explicit CLOSE CURSORfailed, or

2. A table was being created with the NOTLOGGED INITIALLY option, or NOTLOGGED INITIALLY was activated for anexisting table. During the same unit of work,either an error occurred, or a ROLLBACK TOSAVEPOINT statement was issued. This unitof work is rolled back, with the followingeffects:

v any table that was created in this unit ofwork is dropped.

v any NOT LOGGED INITIALLY tables thatwere activated in the transaction aremarked inaccessible, and can only bedropped.

v the sqlcode will be 0 if a ROLLBACK TOSAVEPOINT was issued in the transaction.

3. A rollback to savepoint failed.

The sqlcode reported is the SQLCODE of theoriginal error.

User Response: Correct the problem asindicated by the error sqlcode, then run thetransaction again. Remove any ROLLBACK TOSAVEPOINT statement that is used in the sametransaction in which a NOT LOGGEDINITIALLY table is created or activated.

sqlcode: -1476

sqlstate: 40506

SQL1477N Table table-name cannot beaccessed.

Explanation: An attempt was made to access atable that is not accessible. The table may not beaccessible because of one of the followingreasons:

v The table had NOT LOGGED INITIALLYactivated when the unit of work was rolledback.


v The table is a partitioned declared temporarytable and one or more partitions failed sincethe temporary table was declared (all declaredtemporary tables have the schema nameSESSION).

v ROLLFORWARD encountered the activation ofNOT LOGGED INITIALLY on this table or aNONRECOVERABLE load on this table.

Access to this table is not allowed because itsintegrity cannot be guaranteed.

User Response: One of the following actionscan be taken.

v If the table had NOT LOGGED INITIALLYactivated, drop the table. If this table isrequired, re-create it.

v If the table is a declared temporary table, dropthe table. If this table is required, declare itagain.

v Otherwise, restore from a tablespace ordatabase backup. The backup image musthave been taken subsequent to the commitpoint following the completion of thenon-recoverable operation (NOT LOGGEDINITIALLY operation, or NONRECOVERABLEload).

sqlcode: -1477

sqlstate: 55019

SQL1478W The defined buffer pools couldnot be started. Instead, one smallbuffer pool for each page sizesupported by DB2 has beenstarted.

Explanation: The defined buffer pools could notbe started. Instead, one small buffer pool for eachpage size supported by DB2 has been started,and extended storage has been disabled. Thedefined buffer pools could not be started for oneor more of the following reasons:

v Not enough memory could be allocated for thetotal size of the buffer pools and the extendedstorage specified for this database.

v The buffer pool files in the database directoryare missing or corrupt.

User Response: Check the administrationnotification log for the correct source of theproblem. A possible solution includes:

v Drop or alter the size of one or more of thebuffer pools to allow the database to startproperly. If there is extended storage specifiedfor the database, adjust the configurationvalues of num_estore_segs and estore_seg_szfor less memory consumption.

After making the changes, disconnect from thedatabase and start the database again.

sqlcode: +1478

sqlstate: 01626

SQL1479W Attempt to fetch before the resultset returned the first rowset.

Explanation: The requested rowset overlappedthe start of the result set and, depending on thefetch orientation specified:

SQL_FETCH_PRIORone of the following situations:

v the current position was beyond thefirst row, and the number of thecurrent row is less than or equal tothe rowset size.

v the current position was beyond theend of the result set, and the rowsetsize was greater than the result setsize.

SQL_FETCH_RELATIVEthe absolute value of the fetch offsetwas less than or equal to the currentrowset size.

SQL_FETCH_ABSOLUTEthe fetch offset was negative, and theabsolute value of the fetch offset wasgreater than the result set size but lessthan or equal to the current rowset size.

User Response: No action needed.


SQL1480N The discover type specified in theDISCOVER database managerconfiguration parameter isinvalid.

Explanation: Valid values for the DISCOVERparameter in the database manager configurationfile are: DISABLE, KNOWN, or SEARCH.

User Response: Update the DISCOVERdatabase manager configuration parameter witha type of DISABLE, KNOWN, or SEARCH.

SQL1481N One or more of thecommunications protocolsspecified in theDISCOVER_COMM parameter isinvalid.

Explanation: Valid values for theDISCOVER_COMM parameter in the databasemanager configuration file are any combinationof NETBIOS, and TCPIP, separated by commas.

User Response: Update the DISCOVER_COMMdatabase manager configuration parameter withany combination of NETBIOS, and TCPIP,separated by commas.

SQL1482W The BUFFPAGE parameter willonly be used if one of the bufferpools is defined with a size of -1.

Explanation: This is a warning that theBUFFPAGE database configuration parameterwill be ignored if none of the database’s bufferpools is defined with a size of -1. -1 indicatesthat the buffer pool is to use the BUFFPAGEparameter as the number of buffer pool pages.

User Response: You can select from theSYSCAT.BUFFERPOOLS to review the bufferpool definitions. If none of the buffer pools aredefined with size -1 (NPAGES), then setting theBUFFPAGE parameter will not change the size ofthe buffer pools for the database.

SQL1490W Activate database is successful,however, the database has alreadybeen activated on one or morenodes.

Explanation: Database has already beenexplicitly started (activated) on one or morenodes.


SQL1491N The database name was notdeactivated because the databaseis still being used.

Explanation: The database cannot bedeactivated if there are any applicationsconnected to the specified database.

User Response: Ensure that all applicationshave done a CONNECT RESET, then try again.

SQL1492N The database name was notdeactivated because it was notactivated.

Explanation: The database cannot bedeactivated because the specified database wasnot active.


SQL1493N The application is alreadyconnected to an active database.

Explanation: The ACTIVATE DATABASE andDEACTIVATED DATABASE commands cannotproceed because the application is alreadyconnected to a database.

User Response: Disconnect from the databasethen re-submit the command.

SQL1494W Activate database is successful,however, there is already aconnection to the database.

Explanation: There is already databaseconnection on one or more nodes.



SQL1495W Deactivate database is successful,however, there is still aconnection to the database.

Explanation: There is still database connectionto one or more nodes.


SQL1496W Deactivate database is successful,but the database was notactivated.

Explanation: Database was not explicitly startedon one or more nodes when deactivate databasewas executed.


SQL1497W Activate/Deactivate database wassuccessful, however, an erroroccurred on some nodes.

Explanation: Activate/Deactivate database issuccessful at least on the catalog node andcoordinator node, however, on some othernode(s) an error has occurred.

User Response: Refer to the diagnostic log tofind out what error has occurred on which node,fix the problem if possible and then reissue theactivate/deactivate database command.

SQL1500 - SQL1599

SQL1512N ddcstrc could not write to thespecified file.

Explanation: ddcstrc was not able to write thetrace information to the filename that it has beeninstructed to write to.

User Response: Ensure that the filenamespecified is valid for your file system. If afilename is not specified, ensure that you havethe necessary permission to write to the defaultfile ddcstrc.tmp.

SQL1513W ddcstrc has not been turned off.

Explanation: Because of an error conditionddcstrc has not been turned off. This was done toensure that the trace information will not be lostbefore being safely placed in a file.

User Response: Correct the ddcstrc errorcondition reported prior to this error and attemptto turn off the trace again.

SQL1520N Buffersize must be a numericvalue greater than or equal to65536.

Explanation: The user specified an invalidbuffersize for the ddcstrc command.

User Response: Ensure that the buffersize usedis numeric and greater than or equal to 65536

(64K). Note that the memory to be used will be amultiple of 64K. ddcstrc rounds down thebuffersize specified to the nearest multiple of64K.

SQL1525N An error occurred when startingthe DB2 security daemon.

Explanation: An unexpected error occurredwhen starting the DB2 security daemon.

User Response: Retry the DB2START command.If the problem persists, contact IBM Service.

SQL1526N db2start failed because DB2VIAsupport was not started. Reasoncode reason-code.

Explanation: DB2VIA support was not startedsuccessfully at db2start time. The reason codeindicates the error:

1. The VIPL library specified in DB2_VI_VIPLregistry variable could not be loaded.

2. The Device name specified inDB2_VI_DEVICE registry variable could notbe opened.

3. DB2 does not support the VIAimplementation installed.

User Response:


1. Make sure the DB2 registry DB2_VI_VIPL isproperly set and the name specified inDB2_VI_VIPL is in the %PATH% environmentvariable.

2. Make sure the DB2 registry DB2_VI_DEVICEis properly set.

3. DB2 only supports a VIA implementation thatsupports at least Reliable Delivery reliabilitylevel. It is also required that the VIAimplementation complies with Intel VirtualInterface Architecture Implementation Guideand passes the conformance Suite. Make surethe VIA implementation you chose satisfiesthese requirements.

SQL1530W The specified degree ofparallelism will be ignoredbecause the system is not enabledfor intra-partition parallelism.

Explanation: Either the DEGREE bind optionwas specified with a value greater than 1 or theSET CURRENT DEGREE statement was executedwith a value greater than 1, but the databasemanager was not enabled for intra-partitionparallelism.

The database manager must be started with theintra_parallel configuration parameter set to ONin order for the instance to be enabled forintra-partition parallelism.

The statement or command completedsuccessfully, but the degree specification wasignored.

User Response: If you want to useintra-partition parallelism restart the databasemanager with the intra_parallel configurationparameter set to ON.

Otherwise use a value of 1 or ANY for thedegree specification.

sqlcode: +1530

sqlstate: 01623

SQL1550N The SET WRITE SUSPENDcommand failed. Reason code =reason-code.

Explanation: You cannot issue the SET WRITESUSPEND command until the conditionindicated by reason-code is resolved:

1 Database is not activated.

2 A backup database operation iscurrently in progress for the targetdatabase. You cannot suspend writeoperations until DB2 completes thebackup.

3 A restore database operation is currentlyin progress for the target database. Youcannot suspend write operations for thisdatabase until DB2 completes the restoreoperation.

4 Write operations have already beensuspended for this database.

5 The current state of one or more tablespaces does not permit write suspend.

User Response:

1 Activate the database by issuing theACTIVATE DATABASE command, thenre-issue the SET WRITE SUSPENDcommand.

2 Wait until the BACKUP procedurefinishes, then re-issue the SET WRITESUSPEND command.

3 Wait until the RESTORE procedurefinishes, then re-issue the SET WRITESUSPEND command.

4 The database is already in suspendedstate. To resume write operations forthis database, issue the SET WRITERESUME command.

5 To view the table space states, issue theLIST TABLESPACES command. Forthose table spaces that are in a pendingstate, issue the appropriate command tobring them out of the pending statebefore reissuing the SET WRITESUSPEND command. If one or more


table spaces involve an operation inprogress, wait until the operation iscomplete before reissuing the SETWRITE SUSPEND command.

sqlcode: -1550

SQL1551N The SET WRITE RESUMEcommand failed because thedatabase is not currently inWRITE SUSPEND state.

Explanation: The database is not currently inWRITE SUSPEND state. You can only resumewrite operations for a database for which writeoperations have been suspended.

User Response: No action is required, becausewrite operations are enabled for this database. Tosuspend write operations for the database, issuethe SET WRITE SUSPEND command.

sqlcode: -1551

SQL1552N The command failed because thedatabase is currently in WRITESUSPEND state.

Explanation: This command is not allowedwhen write operations are suspended for thedatabase. The database is in WRITE SUSPENDstate.

User Response: If the command that failed wasRESTART DATABASE, re-issue the RESTARTDATABASE command using the WRITERESUME option. In a multi-node databaseenvironment, re-issue the command concurrentlyon all nodes.

If the command that failed was a BACKUP orRESTORE command, issue a SET WRITERESUME FOR DATABASE command to resumewrite operations for the database. Then re-issuethe BACKUP or RESTORE command.

sqlcode: -1552

SQL1553N DB2 cannot be stopped becauseone or more databases are inWRITE SUSPEND state.

Explanation: You cannot shut down a databasefor which write operations are suspended. Thedatabase is in WRITE SUSPEND state.

User Response: Issue the SET WRITE RESUMEcommand to resume write operations for thedatabase, then re-issue the db2stop command.

sqlcode: -1553

SQL1560N Statistics profile does not exist fortable table-name.

Explanation: A statistics profile needs to bedefined before use.

User Response: Register a statistics profile forthe table using the SET PROFILE option of theRUNSTATS command and then reissue theoperation.

SQL1561N Statistics option not compatiblewith the database server level.

Explanation: One or more of the optionsspecified are not compatible with the databaseserver level. This database server version doesnot supprort all of the statistics options availableusing the db2runstats API.

User Response: Use the sqlustat API to collectthe statistics or use the db2runstats API andspecify only those options that are availableusing the sqlustat API.

SQL1562N Statistics node option is notcompatible with the existing tableand/or index statistics for thetable table-name.

Explanation: The statistics node option isdifferent from the existing table and/or indexstatistics of the table.

User Response: Use consistent node option tocollect the statistics for a table.


SQL1580W Trailing blanks were truncatedwhile performing conversion fromcodepage source-code-page tocodepage target-code-page. Themaximum size of the target areawas max-len. The source stringlength was source-len and itshexadecimal representation wasstring.

Explanation: During the execution of the SQLstatement, a code page conversion operation hasresulted in a string that is longer than themaximum size of the target object. Processingcontinued because only blank characters weretruncated.

User Response: Ensure that the output is asexpected and that the truncation has not causedany unexpected consequences.

sqlcode: +1580

sqlstate: 01004

SQL1581N The table table-name cannot be inappend mode and have aclustering index.

Explanation: There are two situations wherethis error is issued.

v A clustered index exists for a table and ALTERTABLE is used to attempt to place the table inappend mode.

v A table is in append mode and CREATEINDEX is used to attempt to create aclustering index.

User Response: If a clustering index isnecessary then alter the table to set append modeoff. If append mode is desired, drop the existingclustering index on the table.

sqlcode: -1581

sqlstate: 428CA

SQL1582N The PAGESIZE of the table spacetbspace-name does not match thePAGESIZE of the bufferpoolbufferpool-name associated with thetable space.

Explanation: The PAGESIZE value specified inthe CREATE TABLESPACE statement does notmatch the page size of the bufferpool specifiedfor use with the table space. These values mustmatch.


User Response: Change the value specified forPAGESIZE to match the page size of thebufferpool or change the bufferpool to one thathas a page size that matches.

sqlcode: -1582

sqlstate: 428CB

SQL1583N PAGESIZE value pagesize is notsupported.

Explanation: The PAGESIZE that is specified inthe CREATE BUFFERPOOL or CREATETABLESPACE statement is not a supported pagesize. The supported page sizes for Version 5 are4K, 8K, 16K, and 32K.


User Response: Specify one of the supportedpage sizes.

sqlcode: -1583

sqlstate: 428DE

SQL1584N System temporary tablespace withpage size of at least pagesize couldnot be found.

Explanation: A system temporary table spacewas required to process the statement. There wasno system temporary table space available thathad a page size of pagesize or larger.


User Response: Create a system temporarytable space with a page size of at least pagesize.


sqlcode: -1584

sqlstate: 57055

SQL1585N A system temporary table spacewith sufficient page size does notexist.

Explanation: One of the following conditionscould have occurred:

1. The row length of the system temporary tableexceeded the limit that can be accommodatedin the largest system temporary table space inthe database.

2. The number of columns required in a systemtemporary table exceeded the limit that canbe accommodated in the largest systemtemporary table space in the database.

The system temporary table space limits dependon its page size. These values are:

Max Max Page size ofRecord Cols temporaryLength table space----------- ---- ------------1957 bytes 244 2K4005 bytes 500 4K8101 bytes 1012 8K16293 bytes 1012 16K32677 bytes 1012 32K

User Response: Create a system temporarytable space of a larger page size supported, ifone does not already exist. If such a table spacealready exists, eliminate one or more columnsfrom the system temporary table. Create separatetables or views, as required, to hold additionalinformation beyond the limit.

sqlcode: -1585

sqlstate: 54048

SQL1590N LONG VARCHAR and LONGVARGRAPHIC fields are notpermitted in TABLESPACEswhich are built on DEVICEs.

Explanation: Devices (raw i/o) on HP requirei/o to be aligned on 1024 byte boundaries.LONG VARCHAR and LONG VARGRAPHICfields are handled in 512 byte pieces, and thus

can only be used in SYSTEM MANAGEDTABLESPACEs or in DATABASE MANAGEDTABLESPACEs with only FILE containers.

User Response: Alternatives:

v Choose one of the LOB columns types(BLOB,CLOB,DBCLOB) instead of LONG.

v Use a table space with the correct attributes.

sqlcode: 1590

sqlstate: 56097

SQL1591N The ON option of the SETINTEGRITY statement is notvalid since the table table-name isnot in the correct state.

Explanation: The ON option can only bespecified on a table that is in the check pendingstate and the first (for foreign key constraints),second (for check constraints) and fifth (formaterialized query tables) fields in theCONST_CHECKED column of SYSCAT.TABLEScatalog must be either ’Y’ or ’U’.

User Response: If the table is not in checkpending, do not specify the ON option. If thetable is in check pending, perform integritychecking on the table (or refresh the table if it isa materialized query table) before executing theSET INTEGRITY statement with the ON option.

sqlcode: -1591

sqlstate: 55019

SQL1592N The INCREMENTAL option is notvalid with reason code reason-codesince the table table-name cannotbe incrementally processed.

Explanation: The cause is based on thereason-code:

32 The table is not a REFRESHIMMEDIATE materialized query table,nor a REFRESH DEFERREDmaterialized query table with asupporting staging table, nor aPROPAGATE IMMEDIATE stagingtable.


33 A Load Replace or Load Insert hasoccurred to the table if it is amaterialized query table or stagingtable.

34 A Load Replace has occurred to thetable after the last integrity check.

35 One of the following:

v The materialized query or stagingtable was newly created. Fullprocessing is required for the firsttime the table is checked for integrityafter it has been created.

v New constraint has been added to thetable itself or its parents (or itsunderlying table if it is a materializedquery table or staging table) while incheck pending.

v If it is a materialized query table orstaging table, a Load Replace hasoccured to any underlying table ofthe table after the last refresh.

v If it is a materialized query table, atleast on underlying table was forcedto full access (using the FULLACCESS option) before thematerialized query table wasrefreshed.

v If it is a staging table, at least oneunderlying table was forced to fullaccess (USING the FULL ACCESSoption) before the staging table waspropagated.

v If it is a deferred materialized querytable and its corresponding stagingtable is in incomplete state.

v Some of its parents (or underlyingtable if it is a materialized query tableor staging table) have beennon-incrementally checked forintegrity.

v The table was in the check pendingstate before migration. Full processingis required for the first time the tableis checked for integrity aftermigration.

v The table was placed in the checkpending state during a point in timeroll-forward operation.

User Response: Do not specify theINCREMENTAL option. The system will checkthe entire table for constraint violations (or if it isa materialized query table, recompute thematerialized query table definition query).

sqlcode: -1592

sqlstate: 55019

SQL1593N The REMAIN PENDING optionis not valid since the tabletable-name is not in check pendingstate.

Explanation: The table must be in checkpending state if the REMAIN PENDING optionis to be specified.

User Response: Do not specify the REMAINPENDING option.

sqlcode: -1593

sqlstate: 55019

SQL1594W Integrity of non-incremental dataremains unverified by thedatabase manager.

Explanation: The table was previouslyunchecked. When the option NOTINCREMENTAL is not specified, incrementalprocessing of the table is done. The previouslyunchecked portion of the table remainsunchecked and the corresponding values in theCONST_CHECKED column remains marked as’U’.

User Response: No action is required. To verifythe integrity of previously unchecked data andhave the system maintain the integrity of thedata in the table, issue the SET INTEGRITY...OFFstatement to place the table in the check pendingstate and then re-execute the SETINTEGRITY...IMMEDIATE CHECKED statementwith the NOT INCREMENTAL option.

sqlcode: +1594


sqlstate: 01636

SQL1595N The integrity for table table-namecannot be checked because eithera parent table in a referentialconstraint has not been checkedor an underlying table of thematerialized query or stagingtable has not been checked.

Explanation: To avoid propagating this tablewith data that might violate integrity checks, allparents must not be in check pending in order tocheck integrity for this table. If this is amaterialized query table, all underlying tablesmust have been validated in order to refresh thistable. If this is a staging table, all underlyingtables must not be in check pending in order topropagate this table. A table is validated whenthe first (for foreign key constraints), the second(for check constraints), the fifth (for materializedtables), and the seventh (for staging tables) fieldsin the CONST_CHECKED column ofSYSCAT.TABLES are either ’Y’ or ’U’.

User Response: Check integrity for all its parenttables (or underlying tables if it is a materializedquery table or a staging table) and re-execute thisstatement.

sqlcode: -1595

sqlstate: 55019

SQL1596N WITH EMPTY TABLE cannot bespecified for table-name.

Explanation: The WITH EMPTY TABLE clausecannot be specified for table table-name becausethe table:

v is a materialized query table

v has a dependent refresh immediatematerialized query table, or

v is the parent in a referential constraint.

The WITH EMPTY TABLE clause cannot bespecified when altering such a table toACTIVATE NOT LOGGED INITIALLY.


User Response: Remove the WITH EMPTYTABLE clause from the ALTER TABLE statement.

sqlcode: -1596

sqlstate: 42928

SQL1600 - SQL1699

SQL1601N The Database System Monitorinput parameter parameter is a nullpointer.

Explanation: The user called one of theDatabase System Monitor APIs and provided anull pointer instead of a required parameter.



SQL1602N An object type supplied in theinput data structure (sqlma) is notsupported.

Explanation: An object type specified in thevariable data area of the input data structure

(sqlma) for Database System Monitor SnapshotAPI is not supported.


User Response: Reissue the command using avalid object type. Refer to the Administrative APIReference and Application Development Guide forfurther information about valid object types.

SQL1603N The parameter parameter is notspecified in the input datastructure (sqlma).

Explanation: A required parameter is notspecified in the input data structure (sqlma) ofthe Database System Monitor Snapshot orEstimate Buffer Size API.



User Response: The user should reissue thecommand specifying a valid parameter value.

SQL1604N The parameter parameter is notnull terminated.

Explanation: A null character is expected at theend of the character string parameter.


User Response: Add a null character at the endof the character string parameter and reissue thecommand.

SQL1605W The database db-alias is not active.

Explanation: The Database System MonitorReset API was called for a specific database, butthe database was not active.

The command completed successfully but noaction was taken.

User Response: Verify that the database alias iscorrect and the database has been started.

SQL1606W The Database System Monitoroutput buffer is full.

Explanation: The Database System Monitoroutput buffer area is not large enough toaccommodate the returned data. Likely causesare intense system activity when the call wasmade, or in the case of a Database Monitor APIcall within a user application, the user allocateda buffer too small to contain the returned data.

The command completed successfully and datacollected prior to the buffer overflow is returnedin the user’s buffer.

User Response: The user should reissue thecommand, or in the case of a Database MonitorAPI call within a user application, allocate alarger buffer or reduce the amount ofinformation requested.

SQL1607N There is not enough workingmemory to execute the requestedDatabase System Monitorfunction.

Explanation: The database manager is out ofworking memory to process the Database SystemMonitor command.


User Response: Reduce the buffer size in theinput parameter and reissue the command.

SQL1608W Two or more database aliasesspecified on input refer to thesame database.

Explanation: A Database System MonitorSnapshot or Estimate Buffer Size API call wasissued specifying the same request for two ormore database aliases in the sqlma input datastructure, and they point to the same database.

Database System Monitor executes successfully,but returns only one copy of the information inthe output buffer.

User Response: No action is required. However,the user should verify that the database aliasesspecified on input are correct if information ondifferent databases was expected.

SQL1609N The database db-alias is a remotedatabase and cannot bemonitored.

Explanation: A Database System Monitor APIcall was issued specifying the database alias of aremote database. Database System Monitor doesnot support monitoring of remote databases.


User Response: The user should verify that thedatabase alias specified on input is correct, andreissue the command with the correct databasealias.


SQL1610N The Database System Monitorinput parameter parameter isinvalid.

Explanation: The user called one of theDatabase System Monitor APIs and specified aninvalid value for the specified parameter.



SQL1611W No data was returned by DatabaseSystem Monitor.

Explanation: None of the monitoringinformation requested by the users was availableat the time the Database System Monitor API callwas issued. This can occur when a requesteddatabase or application is inactive, or when amonitoring group such as the Table group isturned OFF, and Table information is requested.

User Response: The command completedsuccessfully, but no data is returned to the user.

The user should make sure that the databases orapplications for which monitoring is desired areactive at the time the Database System MonitorAPI is called, or that the desired monitoringgroups are active.

SQL1612N The specified event monitor targetpath is invalid.

Explanation: The target path specified in theCREATE EVENT MONITOR statement is not avalid path name. The command could not beprocessed.

User Response: Resubmit the statement withthe correct event monitor target path.

sqlcode: -1612

sqlstate: 428A3

SQL1613N The specified event monitoroption is invalid.

Explanation: The option specified in theCREATE EVENT MONITOR statement is not

valid. Possible causes include:

v The specified MAXFILES, MAXFILESIZE, orBUFFERSIZE is too low.

v MAXFILESIZE is smaller than BUFFERSIZE.

v MAXFILESIZE NONE was specified withMAXFILES not equal to 1.

The command could not be processed.

User Response: Resubmit the statement withthe corrected event monitor options.

sqlcode: -1613

sqlstate: 428A4

SQL1614N An I/O error occurred whenactivating an event monitor.Reason code = reason-code.

Explanation: An I/O error was detected whenan event monitor was activated. <reason-code> isone of the following:

1 Encountered an unknown event monitortarget type.

2 The Event monitor target path was notfound.

3 Access to event monitor target path wasdenied.

4 Event monitor target path is not thename of a pipe.

5 No process has opened the eventmonitor target pipe for reading.

6 Encountered an unexpected I/O error.

7 The target pipe was not opened inmessage mode. (This reason code isapplicable on OS/2 only.)

8 The target pipe buffer is too small. Theinbound pipe buffer must be at least4096 bytes in size. (This reason code isapplicable on OS/2 only.)

User Response: Where possible, fix the problemdescribed by the reason code, and resubmit theSET EVENT MONITOR statement.

sqlcode: -1614


sqlstate: 58030

SQL1615W The specified event monitor isalready in the requested state.

Explanation: An attempt was made to eitheractivate an already active event monitor, ordeactivate an already inactive event monitor. TheSET EVENT MONITOR statement was ignored.

User Response: No user response is required.

sqlcode: +1615

sqlstate: 01598

SQL1616N The limit on the maximumnumber of active event monitorshas already been reached.

Explanation: A maximum of 32 event monitorscan be active simultaneously per database. Thislimit has already been reached. The specifiedevent monitor cannot be activated.

User Response: If possible, deactivate one ofthe active event monitors and resubmit the SETEVENT MONITOR statement.

sqlcode: -1616

sqlstate: 54030

SQL1617N The specified event monitor hasalready reached its MAXFILESand MAXFILESIZE limit.

Explanation: The specified event monitor wascreated with a limit on the amount of data thatwould be allowed in the event monitor targetdirectory. This limit has already been reached.The specified event monitor cannot be activated.

User Response: If possible, delete some of theevent monitor data files from the target directory,and resubmit the SET EVENT MONITORstatement.

sqlcode: -1617

sqlstate: 54031

SQL1618N The target path of the specifiedevent monitor is in use by anotherevent monitor.

Explanation: The specified event monitor wascreated with the same target path as anotherevent monitor. This other event monitor wasactivated at least once, and has left .evt and/or.ctl files in the target path. These files may be inuse by application(s) that are reading the eventinformation they contain.

User Response: If the other event monitor iscurrently active, deactivate it. After ensuring noapplication(s) are using the files it created in thetarget path, remove the files. Then resubmit theSET EVENT MONITOR statement.

Alternatively, recreate the required eventmonitor, specifying a different target path, andresubmit the SET EVENT MONITOR statement.

sqlcode: -1618

sqlstate: 51026

SQL1619N Cannot DROP an active eventmonitor.

Explanation: The specified event monitor iscurrently active, and therefore cannot bedropped.

User Response: Deactivate the event monitorand resubmit the DROP EVENT MONITORstatement.

sqlcode: -1619

sqlstate: 55034

SQL1620N Unable to flush event monitor.Reason code rc.

Explanation: The event monitor could not beflushed. Possible reasons are:

1. The event monitor is not started.

2. The event monitor is running at a pre-version6 level of output, for which flush is notavailable.

User Response: Ensure that the event monitoris started. If the event monitor is running at a


pre-version 6 level of output, do not attempt toflush it.

sqlcode: -1620

sqlstate: 55034

SQL1621N The transaction in which thespecified event monitor wascreated has not yet beencommitted. The event monitorcannot be activated.

Explanation: An event monitor cannot beactivated until the transaction in which it wascreated has been committed.

User Response: Commit the transaction inwhich the event monitor was created and thenreissue the SET EVENT MONITOR statement.

sqlcode: -1621

sqlstate: 55033

SQL1622N The STATE value specified in theSET EVENT MONITOR STATEstatement is invalid.

Explanation: The STATE value specified in theSET EVENT MONITOR STATE statement is notwithin the range of valid values, or the value isNULL as a result of an indicator variable.

Valid values for the Event Monitor State include:

0 to deactivate the event monitor

1 to activate the event monitor


User Response: Correct the event monitor statevalue and/or any indicator variable and reissuethe statement.

sqlcode: -1622

sqlstate: 42815

SQL1623N The sqlmonsz or sqlmonss APIwas called with too many objectsspecified in the sqlma inputstructure.

Explanation: The limit imposed on the numberof objects that are permitted in the sqlma inputstructure has been exceeded.

User Response: Reduce the number of objectsin the sqlma parameter and try the call again.

SQL1624N All databases referenced by thesqlmonsz or sqlmonss API mustbe located at the same node.

Explanation: The sqlma parameter containedreferences to databases that reside on differentnodes.

User Response: Modify the sqlma parameter sothat all database objects reference the same nodeand then try the call again.

SQL1625W The monitor is not able to convertfrom the code page source to thecode page target. This conversionwas attempted for data pertainingto type type.

Explanation: Possible types are as follows:

1. statement text

2. dcs application

3. application

4. table

5. locks

6. table space

Conversion of data from the source code page tothe target code page is not supported. Thiscondition can occur under the followingconditions:

1. source and target code page combination isnot supported by the database manager.

2. source and target code page combination isnot supported by the operating systemcharacter conversion utility on the servernode.


This situation can occur when the monitor triesto convert data pertaining to a database whosecode page is incompatible to that of the monitorapplication.

User Response: Check your operating systemdocumentation for a list of supportedconversions and ensure that the appropriate onesare installed and accessible to the databasemanager.

If possible ensure that the database beingmonitored and the monitoring application are inthe same codepage.

SQL1626W Overflow occurred whileperforming conversion fromcodepage source to codepage target.The size of the target area wasmax-len ,the data pertained to typetype and the first eight charactersare data.

Explanation: Possible types are as follows:

1. statement text

2. dcs application

3. application

4. table

5. locks

6. table space

The monitor is unable to convert the data due tospace constraints. The data is retained in itsoriginal form.

User Response: If possible ensure that thedatabase being monitored and the monitoringapplication are in the same codepage.

SQL1627W A snapshot api request was madeat the self-describing datastreamlevel, but the server was only ableto return a snapshot of the fixedsize structure format.

Explanation: Although the application issuingthe snapshot request made it at theSQLM_DBMON_VERSION6 or later level, theserver returning the snapshot returned adownlevel view of the data.

User Response: In the self describing dataformat for snapshot (DB2 version 6 and later),collected information, including the server level,is returned as part of the snapshot datastream. Inthe pre-version 6 levels of DB2, the snapshotcollected information is returned in ansqlm_collected structure. You must use thesqlm_collected structure, and the old data streamprocessing method to parse this snapshotdatastream.

SQL1628W A remote get switches operationreturned partial results becausethe output buffer is full. Toretrieve the full results, use aminimum buffer size of size bytes.

Explanation: The output buffer provided wasnot large enough to return all the switch dataavailable. The monitor returned as much data aspossible using the given output buffer.

User Response: Allocate a larger data bufferand re-issue the switch request.

SQL1629W A remote snapshot operationfailed on node or nodes node-list,with reason code or codesreason-list.

Explanation: Some type of failure occurredduring an operation on a remote node for reason<reason-code>, which is one of the following:

1 FCM was unable to communicate withthe target node, due to a node failure orcommunications error.

2 The snapshot operation failed tocomplete on the target node. Please seethe administration notification log forthe specific sqlca.

User Response: If the cause of the error was anode failure, or communication error, you willneed to resolve the communication error, orrestart the node that failed to correct the error.

If the error was due to a snapshot operationfailure on a remote node, see the administrationnotification log for the sqlca from the failedoperation, and refer to the instructions for that


code to correct the problem.

SQL1650N The function invoked is no longersupported.

Explanation: The user has attempted to call anAPI that is no longer supported in this version ofthe database manager.

User Response: The function required may besupported by a different API call. Check in theAdministrative API Reference and ApplicationDevelopment Guide to determine if the function issupported through a different API call.

SQL1651N The request cannot be executedbecause the DB2 server versiondoes not support thisfunctionality.

Explanation: Some new functionality is notsupported against older DB2 server versions.Another possible cause of this error could be therequest referenced objects with qualifiers oflength that exceeds the support of the serverversion.

User Response: Execute the request against aDB2 server where the latest DB2 server versionhas been installed, or upgrade the server to thelatest DB2 server version.

SQL1652N File I/O error occurred.

Explanation: Error occurred either opening,reading, writing, or closing a file.

User Response: Check the db2diag.log fordetails. Also, check for disk full conditions, filepermissions, and operating system errors.

SQL1653N An invalid profile path wasspecified.

Explanation: A full path to a file where serverinformation should be generated must bespecified.

User Response: Ensure that the profile pathspecified is correct and not null.

SQL1654N An instance path error wasencountered.

Explanation: The instance path could not bereturned.

User Response: Check that the DB2INSTANCEpath was specified correctly. Check that thecomplete path length specified is notapproaching the maximum supported by theoperating system.

SQL1660N The Generator at the server,which is used by Discovery togather server information, hasfailed.

Explanation: A server system failure hasoccurred.

User Response: Report the failure to your DB2server administrator. More details of the failurecan be found in the server’s db2diag.log file.

SQL1670N The discover type specified in theDISCOVER database managerconfiguration parameter indicatesdiscovery is disabled.

Explanation: DISCOVER = DISABLE isconfigured in the database managerconfiguration file.

User Response: If DISCOVER functionality isrequired, change the discover type to KNOWNor SEARCH.

SQL1671N The search discovery requestfailed. Check the administrationnotification log for further details.

Explanation: The search discovery requestfailed for one of the following reasons:

1. Initialization failed(sqleCommonInitializationForAPIs)

2. Failed to retrieve the client instance path(sqloinstancepath)

3. Failed to open the output file (sqlofopn)

4. Failed to write to output file (sqlofprt)

5. Failed to get memory (sqlogmblk)


6. Failed to retrieve database managerconfiguration (sqlfcsys)

7. NetBIOS call failed

8. DB2 internal system function failed (sqlogpid,sqlogmt)

Check the db2diag.log for details.

User Response:

1. If initialization fails, try re-booting themachine or re-installing the product.

2. If there was an instance path failure, checkthe DB2INSTANCE value to ensure it iscorrectly set.

3. If the open or write to file failed, check thatyou have access to open and write a file tothe <sqllib path>\<instance>\tmp directoryon Intel machines, or the <instancepath>/sqllib/tmp directory on UNIXmachines.

4. If get memory failed, check the availablememory on your machine.

5. If retrieving the DBM configuration failed, tryre-booting the machine or re-installing theproduct.

6. If a NetBIOS call failed:

v If Add Name failed with a return code of13, check that the nname configured in theDBM configuration was not used toconfigure another DB2 client/server on thenetwork.

v Check that NetBIOS was installed andconfigured properly, and is functioningcorrectly.

v Check your network for problems.

7. If a DB2 internal system function failed,check that the operating system functions onyour machine are functioning correctly.

DB2 Service can provide details about the errorcodes returned by the above functions andwritten to the db2diag.log.

SQL1673N The address list specified as inputto the discover interface isinvalid.

Explanation: The application program used aninvalid input address list pointer. The address listpoints to nothing.

User Response: Ensure that a valid inputaddress list pointer is specified in the applicationprogram, and that it is not null.

SQL1674N The server address specified asinput to the discover interface isinvalid.

Explanation: The application program used aninvalid input server address pointer. The serveraddress points to nothing.

User Response: Ensure that a valid input serveraddress is specified in the application program,and that it is not null.

SQL1675N Discovery is only allowed againstDB2 administration servers. Thecommunications informationprovided does not access anadministration server.

Explanation: A KNOWN discovery request wasissued against a DB2 server that is not a DB2administration server. The communicationsinformation specified is not correct.

User Response: Verify that DB2ADMINSERVERis set on the DB2 server instance you areaccessing. This indicates that the server instanceis a DB2 administration server. Retry theKNOWN discovery request with the correctcommunications information.

SQL1700 - SQL1799


SQL1700N The reserved schema name namewas found in the database duringdatabase migration.

Explanation: The database contains one or moredatabase objects which use the schema namename that is reserved by the current DatabaseManager.


User Response: Ensure that all the databaseobjects that use the reserved schema name aredropped and recreate the objects using a differentschema name. This correction must be made inthe release of Database Manager where thedatabase was originally created. Ensure that noreserved schema names are in use beforeattempting the migration again. Then, resubmitthe database migration command under thecurrent release of Database Manager.

SQL1701N The database cannot be migratedbecause the last session wasabnormally terminated.

Explanation: The last database operation wasabnormally terminated (for example, a powerfailure) under the previous database manager.Database migration cannot be done until thedatabase has been restarted.


User Response: The database must be restarted.You must issue the RESTART DATABASEcommand using the release of Database Managerwhere the database was last accessed. Then,resubmit the database migration command underthe current release of Database Manager.

SQL1702W The protocol connection managershave started successfully.


SQL1703W The db2event directory could notbe created during databasemigration.

Explanation: The database was migratedsuccessfully but the db2event directory could notbe created.

This is a warning only.

User Response: The db2event directory must becreated if the event monitor is to be used. Thedb2event directory must be created in thedatabase directory where the migrated databaseresides. The database directory of the migrateddatabase can be determined by invoking LISTDATABASE DIRECTORY.

SQL1704N Database migration failed. Reasoncode reason-code.

Explanation: Database migration failed. Thereason codes are as follows:

1 an invalid schema name was found.

2 database is not migrateable. Thedatabase could be in one of thefollowing states:

v backup pending state

v roll-forward pending state

v transaction inconsistent state.

3 database logs are full.

4 insufficient disk space.

5 cannot update database configurationfile.

6 failed to relocate database.

7 failed to access the databasesubdirectory or one of the database files.

8 failed to update database container tag.

9 table space access is not allowed.

10 an invalid type name was found.

11 Specific name of procedure conflictswith specific name of function.

12 Datajoiner abstract datatype found.


13 Datajoiner extended index found.

17 Failure to allocate new page from theDMS system catalog table space.

18 Duplicate functions encountered forunicode database migration.

For a unicode database, the followingare considered equivalent string types:

CHAR and GRAPHICVARCHAR and VARGRAPHICLONG VARCHAR and LONG VARGRAPHICCLOB and DBCLOB

Function signatures that are onlydifferent in equivalent string types areconsidered “duplicates” and cannotco-exist in the database. For example,func1(CHAR, GRAPHIC, VARCHAR)and func1(GRAPHIC, GRAPHIC, VARGRAPHIC) are duplicates.

19 Duplicate specificname encountered.

SYSIBM.SYSFUNCTIONS andSYSIBM.SYSPROCEDURES are mergedinto SYSIBM.SYSROUTINES catalog inthe database migration. However, thespecificname must be unique within theSYSIBM.SYSROUTINES.

20 ADT data type encountered.

One or more abstract data types wasfound in the database. Migration failed.All abstract data types must be droppedprior to database migration to thecurrent release.

21 Database migration is complete on thecatalog node and other nodes, but noton all nodes. There are some nodesreporting node failure. As a result,migration has not been performed onthese nodes.

22 Database migration failed because thecatalog node is reporting node failure.

23 Database migration failed. Federateddatabase migration to a 64-bit instanceis not supported.

User Response: Possible solutions based on thereason code are:

1 The reserved schema names are:SYSIBM, SYSCAT, SYSSTAT, andSYSFUN. Ensure that all the databaseobjects that use one or more of theseschema names are dropped and recreatethe objects using a different schemaname. This correction must be made inthe release of database manager in useprior to the current release. Resubmitthe database migration command underthe current release.

2 Correct the database state by going backto release of database manager in useprior to the current release and performany necessary corrective action to thedatabase. Resubmit the databasemigration command under the currentrelease.

3 Increase the database configurationparameters logfilsiz or logprimary to alarger value. Resubmit the databasemigration command.

4 Ensure that there is sufficient disk spaceand resubmit the database migrationcommand.

5 There was a problem in updating thedatabase configuration file. Ensure thatthe database configuration file is notbeing held exclusively by any users andis updatable. Resubmit the databasemigration command. If the problempersists, inform your IBM servicerepresentatives.

6 Restore the database from the databasebackup.

7 Restore the database from the databasebackup.

8 Resubmit the database migrationcommand. If the problem persists,contact your IBM service representative.

9 Correct the table space by going back tothe release of the database manager inuse prior to the current release. Refer to


message SQL0290N for the suggestedactions to take to correct the table space.

10 The type name is reserved by thesystem. Ensure that the type anddatabase objects that use the type aredropped and recreated using anon-reserved type name. This correctionmust be made in the release of databasemanager in use prior to the currentrelease. Resubmit the databasemigration command under the currentrelease.

11 Ensure that the procedure is droppedand recreate procedure using a differentspecific name. This correction must bemade in the release of database managerin use prior to the current release.Resubmit the database migrationcommand under the current release.

12 Ensure that the abstract datatype isdropped. This correction must be madein the release of database manager inuse prior to the current release.Resubmit the database migrationcommand under the current release.

13 Ensure that the extended index isdropped. This correction must be madein the release of database manager inuse prior to the current release.Resubmit the database migrationcommand under the current release.

17 Restore database backup onto itsprevious database manager system. Addmore containers to the table space. Youshould allocate 70% free space fordatabase migration. Move back to thecurrent release and migrate thedatabase.

18 Restore the database backup onto itsprevious database manager system.Drop one of the duplicate functions. Ifnecessary, recreate the function with adifferent signature. Move back to thecurrent release of the database managersystem. Resubmit the databasemigration command. Please refer to theQuick Beginnings book and follow the

instructions on how to verify that thedatabase is ready for migration beforemoving to the current release of DB2.

19 Restore the database backup onto itsprevious database manager system.Drop either the function or procedure. Ifnecessary, recreate it under a differentspecificname. Move back to the currentrelease of the database manager system.Resubmit the database migrationcommand. Please refer to the QuickBeginnings book and follow theinstructions on how to verify that thedatabase is ready for migration beforemoving to the current release of DB2.

20 Restore the database backup onto itsprevious database manager system.Drop all the abstract data types. Moveback to the current release of thedatabase manager system. Resubmit thedatabase migration command. Pleaserefer to the Quick Beginnings book andfollow the instructions on how to verifythat the database is ready for migrationbefore moving to the current release ofDB2.

21 Check the administration notificationlog to determine the nodes that arereporting node failure. Correct the nodefailure situation and resubmit thedatabase migration command. Asmigration only takes place on nodes thatrequire migration, you can submit thecommand from any node.

22 Correct the node failure situation on thecatalog node. Resubmit the migrationcommand.

23 Migrate the Federated database to a32-bit instance.

SQL1705W Unable to update a databasedirectory entry to the currentrelease level.

Explanation: One or more database aliasescould not be updated in the database directory


for a database which has just been migrated froma previous release.

User Response: Uncatalog the database alias(es)for the migrated database and re-catalog thedatabase alias using the same information.

SQL1706W At least one non local databasewas detected in the node directoryfor this instance during word sizeinstance migration.

Explanation: While performing word sizeinstance migration, at least one database notcreated under this instance was encountered.Such databases must have the same word size asthis instance for migration to completesuccessfully.

User Response: Ensure that all databasescataloged at the instance have the same wordsize.

SQL1707N Unable to migrate the instanceword size.

Explanation: There was an error whileattempting to migrate the word size of theinstance. Please contact your IBM servicerepresentative.

User Response: Contact your IBM servicerepresentative.

SQL1708W Database migration completedwith the following warning code:warning-code.

Explanation: Database migration completedwith a warning. The warning codes are asfollows:

1 One or more nodes failed to migrate.

User Response: Possible solution based on thewarning codes:

1 Re-issue the database migrationcommand on that node.

SQL1749N The NOT LOGGED INITIALLYattribute cannot be activated fortable table-name since it was notcreated with NOT LOGGEDINITIALLY.

Explanation: The table table-name was notcreated with the NOT LOGGED INITIALLYattribute specified and therefore this attributecannot be activated using ALTER TABLE.


User Response: Remove the NOT LOGGEDINITIALLY clause from the ALTER TABLEstatement.

sqlcode: -1749

sqlstate: 429AA

SQL1750N Foreign keys cannot reference aparent key table table-name thatwas created with the NOTLOGGED INITIALLY clause.

Explanation: A table that was created with theNOT LOGGED INITIALLY clause cannot bereferenced by a foreign key.

User Response: Remove the foreign keyreference to table-name in the ALTER or CREATETABLE statement.

sqlcode: -1750

sqlstate: 429A0

SQL1751N The resulting nodegroup wouldnot contain any nodes that can beused in a partition map.

Explanation: A nodegroup must contain at leastone node that can be used in a partition map. Ifa node is added to a nodegroup WITHOUTTABLESPACES, it cannot be included in thepartition map because there are no containers forthe table spaces defined on the nodegroup. If anode is added LIKE another node and the othernode does not have containers for all tablespaces on the nodegroup then neither node canbe included in the partition map.

User Response: Do not drop all the nodes in


the nodegroup without adding at least one node.If tablespaces are already defined on thenodegroup but there are no tables, ensure that atleast one node has containers for all the tablespaces.

sqlcode: -1751

sqlstate: 428C0

SQL1752N The table space cannot be createdin the nodegroup ngname.

Explanation: The nodegroup IBMTEMPGROUPcan be specified if and only if the table space is asystem temporary table space.

User Response: For system temporary tablespaces, specify nodegroup IBMTEMPGROUP. Forother table space types, specify a nodegroupother than IBMTEMPGROUP.

sqlcode: -1752

sqlstate: 429A1

SQL1753N Node node-number does not havecontainers for all the systemtemporary table spaces defined inthe nodegroup IBMTEMPGROUP.

Explanation: A node must have containersdefined for all the system temporary table spacesdefined in the nodegroup IBMTEMPGROUP forthis database before it can be included in anodegroup.

User Response: Issue the ALTER TABLESPACEstatement to add containers on every node forevery system temporary table space in thedatabase.

sqlcode: -1753

sqlstate: 57052

SQL1754N The index table space or longtable space is not in the samenodegroup as the primary tablespace.

Explanation: All the table spaces specified inthe CREATE TABLE statement must belong tothe same nodegroup.

User Response: Make sure all the table spacesspecified in the CREATE TABLE statementbelong to the same nodegroup.

sqlcode: -1754

sqlstate: 42838

SQL1755N Node node-number does not havecontainers for all the table spacesdefined in the nodegroup ngname.

Explanation: A node must have containersdefined for all the table spaces defined in anodegroup before that node can be included in aredistribution operation of a nodegroup.

User Response: Issue the ALTER TABLESPACEstatement to add containers on the node for allthe table spaces defined in the nodegroup.

SQL1756N More than one clause specifiescontainers without the ONNODES clause.

Explanation: For the CREATE TABLESPACE,the USING clause without the ON NODESclause can only be specified once.

For the ALTER TABLESPACE, the ADD clausewithout the ON NODES clause can only bespecified once.

The statement was not processed.

User Response: Correct the statement andreissue it.

sqlcode: -1756

sqlstate: 428B1

SQL1757N A USING clause without an ONNODES clause is missing.

Explanation: In CREATE TABLESPACEstatement, every USING clause specifies the ONNODES clause. However not all the nodes in thenodegroup are included, and therefore not allnodes in the nodegroup have containers.

The statement is not processed.

User Response: Ensure that the USING clause


without the ON NODES clause is specified orthat each node in the nodegroup is includedonce in an ON NODES clause.

sqlcode: -1757

sqlstate: 428B1

SQL1758W The containers not designated forspecific nodes are not used by thetable space on any node.

Explanation: The ALTER TABLESPACE andCREATE TABLESPACE statement includescontainer specification for all the nodes in thenodegroup. The specification of the containersthat is not followed by an ON NODES clause isredundant and has been ignored.

The statement has been processed.

User Response: If the containers are needed onsome of the nodes, issue an ALTERTABLESPACE statement to add the necessarycontainers.

sqlcode: -1758

sqlstate: 01589

SQL1759W Redistribute nodegroup isrequired to change datapartitioning for objects innodegroup nodegroup-name toinclude some added nodes orexclude some dropped nodes.

Explanation: This warning indicates that achange being made using the ALTERNODEGROUP or ALTER TABLESPACEstatements has not caused the partitioning mapfor the nodegroup to be changed. Thepartitioning map for a nodegroup is onlychanged immediately by these statements if thereare no tables defined using any table spacedefined in the nodegroup or the node beingdropped is not in the partitioning map.

This warning is issued in the following cases:

v One or more nodes are added using ALTERNODEGROUP ADD NODE

v One or more nodes are dropped using ALTERNODEGROUP DROP NODE

v Containers are added for table space and nofurther containers are required for a node tobe used.

For all of these cases, a table is already definedusing a table space in the nodegroup.

User Response: If you want the node includedor excluded for data partitioning then issue theREDISTRIBUTE NODEGROUP command or API.Another alternative is to drop all tables that usetable spaces in the nodegroup.

sqlcode: +1759

sqlstate: 01618

SQL1760N The CREATE statement for storedprocedure procedure-name musthave a valid LANGUAGE clause,EXTERNAL clause andPARAMETER STYLE clause.

Explanation: A required clause is missing in theCREATE for procedure procedure-name.LANGUAGE, EXTERNAL and PARAMETERSTYLE must be specified.

User Response: Add the missing clause, thentry again.

sqlcode: -1760

sqlstate: 42601

SQL1761N The nodegroup ngname is notdefined for the buffer poolbpname.

Explanation: The nodegroup for the table spacehas not been defined for the buffer pool. Thetable space cannot be created or altered to usethis combination of nodegroup and buffer pool.


User Response: The possible actions are:

v specify a buffer pool that has defined thenodegroup for the table space

v alter the buffer pool to add the nodegroup ofthe table space

v If CREATE TABLESPACE, specify a nodegroupthat is defined for the buffer pool.


sqlcode: -1761

sqlstate: 42735

SQL1762N Unable to connect to databasebecause there is not enough spaceto allocate active log files.

Explanation: There is not enough disk space toallocate active log files. Possible reasons include:

v There is insufficient space available on thedevice used to store the recovery logs.

v If userexits are enabled, the userexit programmay be failing due to an incorrect path,incorrect install directory, sharing violation, orother problem.

User Response: Based on the cause:

v Ensure that there is sufficient space on thedevice for the primary logs, as DB2 mayrequire extra space to allocate new logs so thatthe database will start with at leastLOGPRIMARY log files. Do NOT deleterecovery logs to free space, even if they appearinactive.

v Ensure the userexit program is operatingcorrectly by manually invoking it. Review theinstructions provided in the sample userexitsource code for compiling and installing theuserexit program. Ensure that the archivedestination path exists.

As a last resort, try reducing the values forLOGPRIMARY and/or LOGFILSIZ databaseconfiguration parameters so that a smaller set ofactive log files are used. This will reduce therequirement for disk space.

Reissue the connect statement after determiningand correcting the problem.

SQL1763N There are multiple conflictingcontainer operations in theALTER TABLESPACE statement.

Explanation: The specified container operationsare conflicting. The BEGIN NEW STRIPE SET

container operation cannot be used with any ofthe other container operations (ADD, DROP,EXTEND, REDUCE, or RESIZE) in the sameALTER TABLESPACE statement for the samenode. Pages cannot both be added to (usingADD, EXTEND, or RESIZE) and removed from(using DROP, REDUCE, or RESIZE) a table spacein the same ALTER TABLESPACE statement forthe same node.

User Response: If using the BEGIN NEWSTRIPE SET container operation and otheroperations in the same statement, move theBEGIN NEW STRIPE SET operation into its ownALTER TABLESPACE statement. If both addingpages to and removing pages from a table space,use two ALTER TABLESPACE statements.

sqlcode: -1763

sqlstate: 429BC

SQL1764N Specified size for a RESIZE actionin an ALTER TABLESPACEstatement is smaller than thecurrent size of the table spacecontainer.

Explanation: The size specified in an ALTERTABLESPACE statement using the RESIZE actionis smaller than the current size of the table spacecontainer. You can only increase the size of acontainer.

User Response: Specify a size that is larger thanthe current size value of the table spacecontainer.

sqlcode: -1764

sqlstate: 560B0

SQL1800 - SQL1899


SQL1800N An invalid pointer to structuresqle_request_info was passed tothe catalog admin command/api.

Explanation: The pointer to structuresqle_request_info passed as a parameter to thecatalog admin command/api was invalid. ForClient Configuration Assistance request thispointer must not be NULL.

User Response: Specify a valid pointer tosqle_request_info and re-submit the command.

SQL1801N Invalid request type.

Explanation: The specified request type is notsupported for this command.

User Response: Ensure that the request type isone of the following supported request types:

1. SQLE_CCA_REQUEST - CCA catalog noderequest for catalog and open scan command

2. SQLE_DAS_REQUEST - DAS catalog noderequest for catalog and open scan command

3. SQLE_CND_REQUEST - Open scancommand for CCA and DAS catalog entries

SQL1802N No entry belongs to the requesttype.

Explanation: There is no entry in the nodedirectory that is catalogued by the given requesttype.

User Response: Catalog an entry with the samerequest type and re-submit the command.

SQL1803N The requested operation cannotbe executed in ″No Package Lock″mode. An affected package ispkgschema.pkgname 0Xcontoken.

Explanation: The database manager is currentlyoperating in ″No Package Lock″ mode. Thismode has been activated by setting theDB2_APM_PERFORMANCE registryenvironment variable to ″ON″.

In this mode, the following classes of operationsare prevented from being executed because oftheir impact on packages:

v An operation that invalidates packages.

v An operation that makes a packageinoperative.

v Binding, rebinding (explicitly or implicitly) ordropping a package.

Since the requested operation would affect thepackage pkgschema.pkgname 0Xcontoken in one ofthese ways, the operation is disallowed.

User Response: Do not attempt disallowedoperations in ″No Package Lock″ mode. In orderto execute the requested operation, ″No PackageLock″ mode must be exited. This is accomplishedby unsetting the DB2_APM_PERFORMANCEenvironment registry variable. In order for thevariable change to take effect, that databasemanager must be stopped and restarted.

sqlcode: -1803

sqlstate: 57056

SQL1816N Wrapper wrapper-name cannot beused to access the type-or-version ofdata source (server-typeserver-version) that you are tryingto define to the federateddatabase.

Explanation: The wrapper that you specifieddoes not support the type or version of datasource that you want to define.

User Response: Consult the documentation tofind out which wrapper supports the type andversion of data source that you want to define.Make sure that the wrapper has been registeredto the federated database by the CREATEWRAPPER statement. Then recode the CREATESERVER statement so that it specifies thiswrapper, and run the CREATE SERVERstatement again.

sqlcode: -1816

sqlstate: 560AC


SQL1817N The CREATE SERVER statementdoes not identify thetype-or-version of data source thatyou want defined to the federateddatabase.

Explanation: When a CREATE SERVERstatement references the wrapper that youspecified, it must also identify the type-or-versionof data source that is to be defined to thefederated database.

User Response: In the CREATE SERVERstatement, code the type-or-version option so thatit designates the type-or-version of data sourcebeing defined. Then run the CREATE SERVERstatement again.

sqlcode: -1817

sqlstate: 428EU

SQL1818N The ALTER SERVER statementthat you submitted could not beprocessed.

Explanation: The ALTER SERVER statement ispreceded in a unit of work by a SELECTstatement that references a nickname for a tableor view within the data source (or category ofdata sources) that the ALTER SERVER statementreferences.

User Response: Let the unit of work finish; thenresubmit the ALTER SERVER statement.

sqlcode: -1818

sqlstate: 55007

SQL1819N The DROP SERVER statementthat you submitted could not beprocessed.

Explanation: The DROP SERVER statement ispreceded in a unit of work by a SELECTstatement that references a nickname for a tableor view within the data source (or category ofdata sources) that the DROP SERVER statementreferences.

User Response: Let the unit of work finish; thenresubmit the DROP SERVER statement.

sqlcode: -1819

sqlstate: 55006

SQL1820N Action on the LOB value failed.Reason code = reason-code.

Explanation: The possible reasons codes are:

1. Not enough buffer space to store the LOBvalue.

2. The remote data source does not support thecurrent action on LOB datatype.

3. Some internal programming limitationexceeded.

User Response: Reduce the size of the LOB orreplace the function which is being applied onthe LOB datatype. As a last resort, remove theLOB datatype from the statement.

sqlcode: -1820

sqlstate: 560A0

SQL1821W The LOB value retrieved mayhave changed.

Explanation: The LOB value was evaluated on adeferred retrieval basis. The LOB value may havechanged between the time it was first accessedand when it was actually retrieved.

User Response: Set the ″deferred_lob_retrieval″to ″N″ in SYSSERVEROPTIONS, resubmit yourquery, or ignore the warning.

sqlcode: +1821

sqlstate: 01621

SQL1822N Unexpected error code error-codereceived from data sourcedata-source-name. Associated textand tokens are tokens.

Explanation: While referencing a data source,the federated server received an unexpectederror code from the data source that does notmap to a DB2 equivalent.

Possible error codes include:

v 4901 Trying to open more than 15 cursors


v 4902 Row size exceeds 32K limit

This error might also be returned if the datasource is not available.

User Response: Ensure the data source isavailable, then identify and correct the root causeof the problem by locating the appropriatemessage text and corrective action for thespecified error at the data source.

sqlcode: -1822

sqlstate: 560BD

SQL1823N No data type mapping exists fordata type data-type-name fromserver server-name.

Explanation: An attempt was made to create anickname for an object. One or more columns ofthat object are of a type currently unknown tothe federated server. The name of (one of) theunknown type(s) is listed in the message.

User Response: Create a mapping for thespecified type name on the specified server usingthe CREATE TYPE MAPPING statement.

sqlcode: -1823

sqlstate: 428C5

SQL1824W Some base tables in the operandsof this UNION ALL may be thesame table.

Explanation: A nickname can refer to a remotebase table, a remote view, a remotealias/synonym, or a remote nickname. If twooperands of a UNION ALL view refer todifferent nicknames, they may potentially bepointing to the same table (if not both of themare known to be remote base tables). Thismessage is issued to warn the user thatpotentially one remote base table can getupdated/deleted twice via updates/deletesthrough two operands.

User Response: Verify if all operands point todifferent remote tables. If two operands point tothe same remote base table, consider issuing arollback to reverse the update/delete operation.

sqlcode: +1824

sqlstate: 01620

SQL1825N This SQL statement cannot behandled in a federatedenvironment.

Explanation: Due to some limitation, thecurrent SQL statement cannot be handled in afederated environment. Possible limitationsinclude:

v A cursor update/delete statement involves arefetch of a column into the federated serverthat is not being fetched in the cursor selectstatement.

v Some internal programming limitation isexceeded.

User Response: Based on the cause:

v If this is the cursor update/delete statementthat involves refetch of a column not beingfetched in the cursor select statement, modifythe cursor select statement so that the neededcolumn is fetched.

v If some internal programming limitation isexceeded, try to simplify or rewrite the part ofthe statement that seems complex, e.g.expression.

sqlcode: -1825

sqlstate: 429A9

SQL1826N An invalid value value wasspecified for column column-namein a system catalog objectobject-name.

Explanation: An invalid value value wasspecified for a column column-name in a systemcatalog object object-name.


User Response: Refer to the SQL Reference forvalid values for the specified column in thespecified system catalog object. Correct thestatement and reissue it.

sqlcode: -1826


sqlstate: 23521

SQL1827N No user mapping is defined fromlocal authorization ID auth-ID toserver server-name.

Explanation: An attempt was made to drop oralter a user mapping that is not defined.

User Response: If it is an ALTER USERMAPPING statement, first create a user mappingusing the CREATE USER MAPPING statement.Then, alter the user mapping. If it is a DROPUSER MAPPING statement, no extra action isneeded because the user mapping does not exist.

sqlcode: -1827

sqlstate: 42704

SQL1828N No server option option-name isdefined for remote serverserver-name or for a group ofremote servers: server typeserver-type, version server-version,and protocol server-protocol.

Explanation: An attempt was made to drop oralter a server option that is not defined.

User Response: If it is an ALTER SERVERstatement, first create a server option using theCREATE SERVER statement. Then, alter theserver option. If it is a DROP SERVER statement,no extra action is needed because the serveroption for the servers does not exist.

sqlcode: -1828

sqlstate: 42704

SQL1830N RETURNS clause must bespecified prior to a predicatespecification using theEXPRESSION AS clause.

Explanation: The RETURNS clause is notspecified before the PREDICATE clause thatincludes the EXPRESSION AS clause. TheRETURNS clause may have been included afterthe predicate specification or may be missing.


User Response: Specify the CREATEFUNCTION statement with the RESULTS clauseprior to the PREDICATE clause.

sqlcode: -1830

sqlstate: 42627

SQL1831N Table statistics for a subtablesubtable-name cannot be updated.

Explanation: The statement attempts to updatethe statistics values of NPAGES, FPAGES, orOVERFLOW, for table subtable-name, that isdefined as a subtable. For typed tables, thesestatistics can only be updated using the roottable of the table hierarchy.


User Response: Update the catalog statistics forthe root table of the table hierarchy instead of thesubtable.

sqlcode: -1831

sqlstate: 428DY

SQL1832N The routine routine-name cannot beused to define a filter because itis defined as an SQL function.

Explanation: The routine (function or method)routine-name is specified in a FILTER clause for auser defined predicate specification or an indexextension definition. The routine can not bedefined with LANGUAGE SQL.


User Response: Specify a routine that is notdefined with LANGUAGE SQL.

sqlcode: -1832

sqlstate: 429B4

SQL1881N option-name is not a validoption-type option for object-name.

Explanation: The specified option might notexist, or it might not be valid for the particulardata source, data source type, or database objectthat you’re working with.


User Response: Consult the SQL Reference toverify the option that you want. Then revise andresubmit the statement that you want to run.

sqlcode: -1881

sqlstate: 428EE

SQL1882N The option-type option option-namecannot be set to option-value forobject-name.

Explanation: The value that you specified eitherlacks the proper delimiters or is invalid.

User Response: Consult the SQL Reference toverify the value that you want. Then revise andresubmit the statement that you want to run. Besure to delimit the value in single quotes.

sqlcode: -1882

sqlstate: 428EF

SQL1883N option-name is a requiredoption-type option for object-name.

Explanation: You did not specify an option thatDB2 requires in order to process the statementthat you submitted.

User Response: Consult the documentation tofind out the options that are required for thestatement that you want to run. Then revise andresubmit this statement.

sqlcode: -1883

sqlstate: 428EG

SQL1884N You specified option-name (aoption-type option) more than once.

Explanation: You entered a statement thatreferences the same option multiple times.

User Response: Recode the statement so that itreferences the option that you want only once.Then resubmit the statement.

sqlcode: -1884

sqlstate: 42853

SQL1885N The option-type option option-nameis already defined.

Explanation: You entered a value for an optionthat already has a value.

User Response: Query the appropriate catalogview to determine what value the option iscurrently set to. If this value differs from the onethat you want, recode the statement so that theSET keyword follows the OPTIONS keyword. Tofind out what catalog view contains the valuesfor this option, consult the SQL Reference.

sqlcode: -1885

sqlstate: 428EH

SQL1886N The operation-type operation is notvalid because the option-typeoption option-name has not beendefined.

Explanation: You tried to change or delete avalue for an option that has not been defined forthe data source, data source type, or databaseobject that you’re working with.

User Response: If you specified SET in thestatement that you want to run, recode thestatement, either omitting SET or replacing itwith ADD (ADD is the default). Then resubmitthe statement. If you specified DROP, do nothing.

sqlcode: -1886

sqlstate: 428EJ

SQL1887N SPECIFICATION ONLY clauserequired.

Explanation: A CREATE INDEX statement for anickname must have a SPECIFICATION ONLYclause.

User Response: Add the SPECIFICATIONONLY clause and then resubmit the statement.

sqlcode: -1887

sqlstate: 42601

SQL1900 - SQL1999


SQL1900N The command completedsuccessfully.

Explanation: The command line utilitysuccessfully completed the command.


SQL1901N The syntax of the command is notcorrect.

Explanation: The command line utility couldnot process the command.

User Response: Correct and resubmit thecommand.

SQL2000 - SQL2099

SQL2000N The drive specified in the utilitycommand is not a valid diskettedrive or fixed disk.

Explanation: The input or output drivespecified in the utility command does not exist.


User Response: Resubmit the utility commandwith the correct drive specifier.

SQL2001N The utility was interrupted. Theoutput data may be incomplete.

Explanation: The user may have pressed theinterrupt key sequence, or had called the utilitywith a terminate caller action.

This message can also be returned during abackup or restore operation on a database nodewhen the database catalog node is down.


User Response: Restart the application orreissue the command, if needed. The output datafrom the interrupted command may beincomplete, and should not be used.

SQL2002N The specified database utilitycommand is not valid for remotedatabases. The database specifiedin the command must reside onyour local workstation.

Explanation: The database utility command isonly valid for local databases.


User Response: Run the utility locally.

SQL2003C A system error occurred.

Explanation: An operating system erroroccurred. The return code can be found in theSQLERRD[0] field of the SQLCA.


User Response: Look at the error return code inthe SQLERRD[0] field of the SQLCA. Correct theerror, if possible, and resubmit the command.

SQL2004N An SQL error sqlcode occurredduring processing.

Explanation: The utility was using an SQLstatement when an error occurred.


User Response: Look at the SQLCODE(message number) in the message for moreinformation. Make changes and resubmit thecommand.


SQL2005C An I/O error occurred during aread operation. The data may beincomplete.

Explanation: Incomplete data was read duringan I/O operation.


User Response: Determine if the I/O error canbe corrected and resubmit the command.

SQL2006C An I/O error occurred during awrite operation. The data may beincomplete.

Explanation: Incomplete data was writtenduring an I/O operation.


User Response: Determine if the I/O error canbe corrected and resubmit the command.

SQL2007N Specified buffersize of buffersize4K buffers is too small for pagesizepage size object.

Explanation: To backup a pagesize page sizedatabase object one needs a buffer larger thanthe page size. When backing up a database thedata is first copied to an internal buffer. Data isthen written from this buffer to the backupmedia when the buffer is full. The buffersize ofbuffersize 4K buffers that was specified isinadequate.

User Response: Use a larger buffersize.

SQL2008N The callerac parameter is notwithin valid range or therequested action is out ofsequence.

Explanation: Either the callerac parameter valueis not one of the acceptable values or therequested action is out of sequence.


User Response: Each utility has its own list ofvalid callerac values. Check the ApplicationDevelopment Guide for the valid values for the

callerac for the utility in use. Resubmit thecommand with a valid callerac parameter.

SQL2009C There is not enough memoryavailable to run the utility.

Explanation: More memory is needed to runthe specified utility.


User Response: Possible actions include:

v Increase the UTIL_HEAP_SZ databaseconfiguration parameter. For backup andrestore, this value must be at least as high asthe number of buffers * buffer size. For moreinformation on backup and restore buffers,refer to the Command Reference.



v Increase the DBHEAP database configurationparameter.

SQL2010N The utility encountered an errorerror while connecting to thedatabase.

Explanation: The utility could not connect tothe database.


User Response: Look at the error number in themessage for more information. Make changesand resubmit the command.

SQL2011N The utility encountered an errorerror while disconnecting from thedatabase.

Explanation: The utility could not disconnectfrom the database.




SQL2012N Interrupt handling could not beenabled.

Explanation: The utility could not enableinterrupt handling. The actual return code can befound in the SQLERRD[0] field of the SQLCA.



SQL2013N The utility could not access thedatabase directory. Error error wasreturned.

Explanation: An error occurred while the utilitywas accessing the database directory.


User Response: If the path in the databaseparameter is not the database directory path,resubmit the command with the correct path.Otherwise, look at the error number in themessage for more information. Make changesand resubmit the command.

SQL2014N A database environment erroroccurred.

Explanation: The utility received an error froma database environment command. The databasemanager configuration file and the databaseconfiguration file may contain incompatiblevalues.


User Response: Check the database managerconfiguration file and the database configurationfile for inconsistent values. Resubmit thecommand.

SQL2015N The database parameter is notvalid. The database name is toolong, it was not specified, or theaddress of the name is not valid.

Explanation: The database name is required. Itmust contain 1 to 8 characters and the charactersmust be chosen from the database manager base

character set. The name must be located at avalid address for the application.


User Response: Resubmit the command with avalid database name.

SQL2016C The PATH command does notcontain a path to program-name.

Explanation: The utility could not find therequired program using the operating systemSelect Path.


User Response: Update the PATH command toinclude the path to the indicated program name.

SQL2017N Too many sessions are alreadystarted or OS/2 Start Session didnot complete successfully.

Explanation: The BACKUP or RESTORE utilitycould not start the new session because:

v The maximum number of sessions is alreadystarted.

v The OS/2 Start Session program returned anerror.


User Response: Wait until some of the currentsessions stop processing and resubmit thecommand. Or, see the SQLERRD[0] field in theSQLCA for more information and resubmit thecommand.

SQL2018N The utility encountered an errorerror while attempting to verifythe user’s authorization ID ordatabase authorizations.

Explanation: The user attempted to execute autility and one of the following has occurred:

v The user authorization ID is not valid.

v An error occurred attempting to access theuser’s authorizations for the database.




SQL2019N An error occurred while bindingthe utilities to the database.

Explanation: Because the current level of theutility being executed was not bound to thedatabase, the system attempted to bind allutilities to the database and this binding processfailed. Possible causes for the error include:

v The system may have run out of disk space.

v A system resource problem such as too manyfiles opened.

v A missing or invalid list of utility programs tobe bound (db2ubind.lst).

v A missing or invalid bind file for one of theutilities (db2uxxxx.bnd).

v The user does not have the requiredauthorization for binding utilities. Therequired privileges are:

– BIND privilege for the utility programs

– SELECT privilege for the system catalogs.

For the RESTORE utility, the database is restored,but at least one utility is not bound to thedatabase. The other utilities stop processing.

User Response: Complete all activities that maybe competing for system resources and resubmitthe utility command. If the error continues,perform one of the following actions:

v Have a user with SYSADM or DBADMauthority retry the command.

v Reinstall the database manager or reapply anyrecent updates or do both.

v Bind the utility programs (db2uxxxx.bnd files)individually to the database (with no formatoption) to isolate the problem and, possiblyenable some utilities to operate successfully.

SQL2020N The utility is not bound to thedatabase correctly.

Explanation: All the utilities were rebound tothe database because the utility was not boundto the database or the package of the utility that

was bound to the database was not compatiblewith the installed version of the databasemanager, but there is still a timestamp conflictbetween the installed version of the databasemanager and the package so the utility and bindfile are not compatible.


User Response: Reinstall the database manageror reapply any recent updates or do both.Resubmit the utility command.

SQL2021N The correct diskette is not in thedrive.

Explanation: The diskette to be used for BackupDatabase or for Restore Database is not in thedrive or is not valid.


User Response: Verify that the correct disketteis in the drive or insert a new diskette.

SQL2023N The utility encountered an I/Oerror code while accessing the logcontrol file.

Explanation: The read or write operationagainst the log control file failed.


User Response: Record the error return codevalue. Determine whether the I/O error can becorrected.

SQL2024N The utility encountered an I/Oerror code while accessing the filetype file-type.

Explanation: An I/O error occurred whileaccessing the specified file.

A file with the extension “.BRG” is used todetermine whether a RESTORE operation hasterminated abnormally. The file resides in thelocal database directory of the database forwhich the RESTORE operation was attempted.

A file with the extension “.BRI” storesinformation about the progress of an incrementalRESTORE operation. The file resides in the local


database directory of the database for which theRESTORE INCREMENTAL operation wasattempted.

The file name consists of the database tokenconcatenated with the file type extension. Forexample, if the database “SAMPLE” is assignedthe database token “SQL00001”, the BRI file willhave the name“instance/NODE0000/sqldbdir/SQL00001.BRI”.


User Response: Record the error return code.Determine whether the I/O error can becorrected.

SQL2025N An I/O error code occurred onmedia dir/devices.

Explanation: An I/O error occurred whileaccessing a file on the specified media.


User Response: Record the error return code.Determine whether the I/O error can becorrected.

SQL2026N An error sqlcode occurred whiletrying to internally disconnectfrom the database.

Explanation: The internal disconnect commandfailed. The SQLCODE is returned in the message.



SQL2027N An error sqlcode occurred whiletrying to internally connect to thedatabase.

Explanation: The internal connection failed. TheSQLCODE is returned in the message. Thedatabase manager configuration file and thedatabase configuration file may containincompatible values.


User Response: Look at the SQLCODE(message number) in the message for moreinformation. Make changes and resubmit thecommand. Check that the database managerconfiguration file values and the backup image’sdatabase configuration file values are compatible.

SQL2028N Error sqlcode occurred whileinstalling the interrupt handler.

Explanation: The utility could not enable theinterrupt handler. The SQLCODE is returned inthe message.



SQL2029N An error error occurred whilecommand-file-name was processing.

Explanation: An error was returned from eitherthe specified command file, or from theoperating system.

User Response: The user has either requested a“Backup changes only” of a database enabled forROLLFORWARD recovery, or has requested a“Backup changes only” while requesting the useof the user exit.

SQL2030N The name drive is full. At leastnumber free bytes are needed onthis drive.

Explanation: The specified drive does not haveenough space for creating an internalsubdirectory and information file.


User Response: Free the indicated space on thespecified drive and resubmit the command.

SQL2031W Warning! Please mount the targetor source media on device device.

Explanation: A database utility process eitherwrites data to or reads data from the media on


the specified device. The utility returns so thatthe user may mount the correct media for theoperation.

The utility waits for a response to continue.

User Response: Mount the media and return tothe utility with the callerac parameter indicatingif processing continues or ends.

SQL2032N The parameter parameter is notvalid.

Explanation: The parameter is incorrectlyspecified. Either the value is out of range or isincorrect.

User Response: Resubmit the command with acorrect value for the parameter.

SQL2033N The TSM error error occurred.

Explanation: During the processing of adatabase utility, TSM was called and encounteredan error.

User Response: Consult the TSMdocumentation for a description of the error, takecorrective actions and resubmit the command.

SQL2034N The address of the parm parameteris not valid.



SQL2035N The warning condition warn wasencountered while executing theutility in non-interrupt mode.

Explanation: The calling application invokedthe utility with no interrupt mode. During theoperation a warning condition was encountered.

User Response: Resubmit the operation withoutspecifying the no interrupt condition in the

callerac parameter or take actions to prevent thewarning and resubmit the operation.

SQL2036N The path for the file or devicepath/device is not valid.

Explanation: The application calling the utilityhas supplied a source or target path that is notvalid. The path or device specified may not existor is incorrectly specified.

User Response: Reissue the utility commandwith a path that represents a correct path ordevice.

SQL2037N TSM could not be loaded.

Explanation: A call to a database utilityspecified TSM as the target or source of thebackup. An attempt was made to load the TSMclient. Either the TSM client is not available onthe system or an error was encountered in theload procedure.

User Response: Ensure that the system hasTSM available. Resubmit the command afterTSM is made available, or resubmit thecommand without utilizing TSM.

SQL2038N A database system error errcodeoccurred during processing.

Explanation: A database system error wasencountered during the processing of one of theutilities.

User Response: Examine the error code in themessage for more information. Take correctiveaction and resubmit the command.

SQL2039N The application calling the utilityhas terminated.

Explanation: The application calling the utilityhas terminated. The application side of the utilityis in the same process as the calling applicationand terminates with the application. The agentside of the utility terminates as a result.

User Response: Reissue the command afterdetermining why the application terminated.


SQL2040N The database alias parameterdbalias is not valid or notspecified.

Explanation: The application calling the Backupor Restore utility has supplied a database aliasparameter that is not valid. The alias must be 1to 8 bytes and the characters must be chosenfrom the database manager base character set.

User Response: Reissue the Backup or Restorecommand with a valid database alias.

SQL2041N The buffer size parameterspecified is not valid. The buffersize must be specified as 0 or bebetween 8 and 16384 inclusive.

Explanation: The application calling the utilityhas supplied a buffer size parameter that is notvalid. The buffer size is used to determine theinternal buffer size. The value is the number of4K pages that are obtained for this buffer. Thevalue must be specified as 0 or be between 16and 16384 inclusive.

When running the backup or restore utility, if 0is specified, the default buffer size defined in thedatabase manager configuration is used.

If the target media is a diskette, the buffer sizemust be smaller than the diskette size.

SQL2042W Warning! I/O error error accessingdevice device. Additionalinformation (if available):additional-information. Please ensuremedia is mounted and positionedcorrectly.

Explanation: The application calling the utilityhas encountered an I/O error while trying toread or write to the tape device. The utilityreturns so that the user may correctly mount andposition the tape.

The message may contain additional informationto help diagnose the problem.


User Response: Correctly mount and positionthe tape and return to the utility indicating if

processing continues or ends.

The error, device and the additional information(if present) can be used to diagnose and correctthe problem.

SQL2043N Unable to start a child process orthread.

Explanation: Unable to start up the childprocesses or threads required during theprocessing of a database utility. There may not beenough available memory to create the newprocess or thread. On AIX-based systems, themaxuproc value set by the chdev command maybe too low. On OS/2-based systems, theTHREADS value set in CONFIG.SYS may be toolow. The utility stops processing.

User Response: Ensure the system limit fornumber of processes or threads has not beenreached (either increase the limit or reduce thenumber of processes or threads already running).Ensure that there is sufficient memory for thenew process or thread. Resubmit the utilitycommand.

SQL2044N An error occurred while accessinga message queue. Reason code:reason-code

Explanation: An unexpected error or badmessage was received on one of the messagequeues during the processing of a databaseutility. The following is a list of reason codes:

1 Unable to create a message queue. Thenumber of message queues allowed mayhave been exceeded.

2 An error was encountered while readingfrom a message queue.

3 An error was encountered while writingto a message queue.

4 An invalid message was received from amessage queue.

5 An error was encountered whileopening a message queue.

6 An error was encountered while closinga message queue.


7 An error was encountered whilequerying a message queue.

8 An error was encountered whiledeleting a message queue.


User Response: Ensure the number of messagequeues allowed is not reached. Reduce thenumber of message queues in use if necessaryand resubmit the utility command.

SQL2045W Warning! Error error occurredwhile writing to media media.

Explanation: A database utility processencountered error error returned by the operatingsystem while writing to the media media. Theutility returns so that the user may attempt to fixthe problem or cancel the operation.


User Response: Consult the problemdetermination documentation for your operatingsystem and correct the error condition. Return tothe utility with the correct caller actionparameter to indicate if processing shouldcontinue or terminate.

SQL2048N An error occurred while accessingobject object. Reason code:reason-code.

Explanation: An error occurred while accessingan object during the processing of a databaseutility. The following is a list of reason codes:

1 An invalid object type is encountered.

2 A lock object operation failed. The lockwait may have reached the lock timeoutlimit specified in the databaseconfiguration.

3 An unlock object operation failed duringthe processing of a database utility.

4 Access to an object failed.

5 An object in the database is corrupted.

6 The object being accessed is a table

space and either the table space is insuch a state that the operation is notallowed or one or more containers ofthe table space is not available. (LISTTABLESPACES will list the current tablespace state.)

7 A delete object operation failed.

8 Trying to load/quiesce into a table thatis not defined on this partition.


User Response: If a lock object operation failed,ensure the lock timeout limit in the databaseconfiguration is adequate and resubmit theutility command. You may also consider usingthe QUIESCE command to bring the database toa quiesced state to ensure access.

If the error was encountered during backup, takecorrective action to recover the database andresubmit the utility command.

If the error was encountered during restore orload recovery, ensure the backup or copy imageis correct and resubmit the utility command.

If the object is a table space and the error wasencountered during a restore, the set table spacecontainer api may be used to modify the tablespace before resubmitting the utility command.

SQL2054N The backup or copy image iscorrupted.

Explanation: The backup or copy image in useis corrupted


User Response: Discard the image as it is not avalid image. Resubmit the utility command witha valid image.

SQL2055N Unable to access memory frommemory set memory-heap.

Explanation: A database utility was unable toaccess memory during processing.



User Response: Stop the database manager,then restart it and resubmit the utility command.

SQL2056N An invalid media type wasencountered on media media.

Explanation: An invalid media type wasencountered during the processing of a databaseutility.


User Response: Ensure the media used isamong of the types supported by the utility.Resubmit the command with a valid media list.

SQL2057N The media media is alreadyopened by another process.

Explanation: The source or target mediaspecified during the processing of a databaseutility is already open by another process. Theutility does not allow shared access for theoperation.


User Response: Ensure the media used is not inuse currently. Resubmit the command with avalid media list.

SQL2058W An end-of-media warning wasencountered on media media.

Explanation: An end-of-media warning wasencountered during the processing of a databaseutility. This error can also occur if an invalid tapedevice block size was specified.

The utility is waiting for a response to continue.

User Response: Correct the end-of-mediacondition and return to the utility with thecorrect caller action parameter to indicate ifprocessing should continue or terminate.

The tape device block size (or blocking factor)used at restore time must be the same as thatused during the backup. If a variable block sizeis used, then the buffer size used must be lessthan or equal to the maximum block size of thetape device.

SQL2059W A device full warning wasencountered on device device.

Explanation: An device full warning wasencountered during the processing of a databaseutility.

The utility is waiting for a response to continue.

User Response: Correct the device fullcondition and return to the utility with thecorrect caller action parameter to indicate ifprocessing should continue or terminate.

SQL2060W The device device is empty.

Explanation: An empty device was encounteredduring the processing of a database utility. Theutility is waiting for a response to continue.

User Response: Mount the media and return tothe utility with the caller action parameter toindicate if processing should continue orterminate.

SQL2061N An attempt to access media mediais denied.

Explanation: An attempt to access a device, file,TSM or the vendor shared library is deniedduring the processing of a database utility. Theutility stops processing.

User Response: Ensure the device, file, TSM orvendor shared library used by the utility allowsthe access requested and resubmit the utilitycommand.

SQL2062N An error occurred while accessingmedia media. Reason code:reason-code

Explanation: An unexpected error occurredwhile accessing a device, file, TSM or the vendorshared library during the processing of adatabase utility. The following is a list of reasoncodes:

1 An attempt to initialize a device, file,TSM or the vendor shared library failed.

2 An attempt to terminate a device, file,TSM or the vendor shared library failed.


other If you are using TSM, this is an errorcode returned by TSM.


User Response: Ensure the device, file, TSM orvendor shared library used by the utility isavailable and resubmit the utility command. Ifthe command is still unsuccessful, contact yourtechnical service representative.

SQL2065W Caller action caller-action specifiedis not allowed when the mediamedia specified is the only one leftconnected to the utility.

Explanation: The caller action specified is notallowed because there is only one device leftconnected to the database utility.

User Response: Return to the utility with thecorrect caller action parameter to indicate ifprocessing should continue or terminate.

SQL2066N Table space name name specifieddoes not exist in the database orcannot be used for the utilityoperation.

Explanation: The table space name specified issyntactically correct, but it does not exist in thedatabase or cannot be used in an utilityoperation. If the utility in use is a backupoperation, the table space may be disallowedbecause it is a system or user temporary tablespace or is in an inconsistent state.

User Response: Check the table space nameand resubmit the utility command with thecorrect table space name.

SQL2068N An invalid image wasencountered on media media.There was no media header.

Explanation: An invalid image was encounteredduring the processing of a database utility. Theutility was not able to locate a valid mediaheader. The utility stops processing.

User Response: Resubmit the command withcorrect backup or copy images.

SQL2069N An invalid image wasencountered on media media. Theimage was created for databasealias dbalias.

Explanation: An invalid image was encounteredduring the processing of a database utility. Theimage provided was from a different databasealias. The utility stops processing.


SQL2070N An invalid image wasencountered on media media. Theimage contained timestamptimestamp.

Explanation: An invalid image was encounteredduring the processing of a database utility. Theimage provided was from a backup or copy witha different timestamp. The utility stopsprocessing.


SQL2071N An error occurred while accessingthe shared library shr-lib-name.Reason code: reason-code

Explanation: An unexpected error occurredwhile accessing a vendor shared library duringthe processing of a database utility. Thefollowing is a list of reason codes:

1 An invalid shared library path wasencountered.

2 An attempt to load the backup sharedlibrary failed.

3 An error was encountered whileunloading the shared library.


User Response: Ensure the shared libraryprovided is valid and resubmit the utilitycommand or use another supported media.


SQL2072N Unable to bind the shared libraryshr-lib-name. Reason code:reason-code.

Explanation: An error was encountered whilebinding the shared library during the processingof a database utility. The utility stops processing.

User Response: Note the reason code returnedfrom the vendor utility in the message and takecorrective action if possible. Resubmit thecommand with a valid shared library or usinganother supported media.

SQL2073N DATALINK processing failedbecause of internal problems atthe database server or DB2 DataLinks Manager.

Explanation: An unexpected error occurredwhile processing DATALINK values.

User Response: Resubmit the command. If theproblem still exists, resubmit the command aftershutdown and restart of DB2 and the DB2 DataLinks Managers.

The Restore utility can avoid DATALINKprocessing by specifying WITHOUT DATALINK.

SQL2074N DATALINK processing failedbecause of internal problems atthe database server.


User Response: Resubmit the command. If theproblem still exists, resubmit the command aftershutdown and restart of DB2.


SQL2075N DATALINK processing failedbecause of internal problems atthe DB2 Data Links Manager.


User Response: Resubmit the command. If theproblem still exists, resubmit the command after

shutdown and restart of the DB2 Data LinksManagers.


SQL2076W The DB2 Data Links Managerserver-name was not registered tothe database.

Explanation: The DB2 Data Links Managerserver-name was not registered to the databasewith the ADD DATALINKS MANAGERcommand.

User Response: For details on why the ADDDATALINKS MANAGER command failed, checkthe administration notification log.

SQL2077W Reconcile processing completedsuccessfully on Data LinksManagers that were available.Reconcile processing is pendingon Data Links Managers that werenot available. Examine theadministration notification log formore information.

Explanation: Some or all of the Data LinksManagers referred to in the table data were notavailable during reconcile processing. Reconcileprocessing completed successfully on Data LinksManagers that were available. The table is placedin DataLink Reconcile Pending (DRP) state,because reconcile processing is pending on DataLinks Managers that were not available.

User Response: The table will be taken out ofDataLink Reconcile Pending state when reconcileis completed successfully on all Data LinksManagers referred to in the table data. Bring upthe Data Links Managers that were not availableand run reconcile again.

SQL2078N The DB2 Data Links Managercould not be added or droppedsuccessfully. Reason code =reason-code.

Explanation: The DB2 Data Links Managercould not be added or dropped, as indicated by


the one of the following reason codes:

01 The DB2 Data Links Manager beingadded is already registered to thedatabase.

02 The DB2 Data Links Manager beingdropped is not registered to thedatabase.

03 The database manager configurationparameter DATALINKS is set to NO.

04 The database already has the maximumallowed number of DB2 Data LinksManagers registered to it.

User Response: The action depends on thereason code as follows:

01 Do not attempt to add the DB2 DataLinks Manager more than once.

02 Do not attempt to drop a DB2 DataLinks Manager which is not registered.

03 Set the database manager configurationparameter DATALINKS to YES usingthe UPDATE DATABASE MANAGERCONFIGURATION command andattempt the operation again.

04 Do not attempt to add more than themaximum allowed number of DB2 DataLinks Managers.

SQL2079N An error was reported by theshared library shr-lib-name. Returncode: return-code.

Explanation: An error was reported from avendor shared library during the processing of a

database utility. The return code displayedcorresponds to one of the valid vendor APIreturn codes. The utility stops processing.

Possible API return codes are:

3 The DB2 and vendor products areincompatible.

4 An invalid action was requested.

8 An invalid userid was specified.

9 An invalid password was provided.

10 Invalid options were specified.

12 An invalid device handle was provided.

13 An invalid buffer size was specified.

30 A severe error was experienced insidethe vendor product.

other A specific severe error returned by thevendor product.

User Response: Ensure the shared libraryprovided is valid. Attempt to make the necessarycorrective actions based on the vendor APIreturn code and the corresponding db2diag entryand resubmit the utility command.

SQL2100 - SQL2199

SQL2150W The table spaces contained in thebackup image were restored.Depending on the request of thecaller, one or more of these tablespaces might have been skipped.

Explanation: A RESTORE DATABASEcommand was issued. The user might haveindicated that only a subset of the table spaces in

the backup image were to be recovered.



SQL2154N The RESTORE was not successful.The backup used to restore thetable space(s) is not associatedwith the current log sequence forthe database.

Explanation: For table space restore, the backupmust have been taken during the current logsequence of the database. The log file sequence isdetermined by the database that has beenrestored previously or the log files that havebeen processed. In addition, the backup musthave been taken after the last time the databasewas enabled for roll forward recovery.

Table space restore has stopped.

User Response: Resubmit the command with acorrect backup image.

SQL2155W Changes have been made to therecovery history file since theopen scan was issued.

Explanation: Changes have been made to therecovery history file since the file was open for ascan. The data read may not be consistent.

User Response: If it is essential to haveconsistent data from the scan, close the recoveryhistory file and resubmit the command.

SQL2157N There are already eight recoveryhistory file scans open.

Explanation: Eight recovery history file scans inthis process are already open. No more thaneight open scans are allowed.


User Response: Issue one or more CLOSERECOVERY HISTORY FILE SCAN commandsand resubmit the command.

SQL2160W A damaged recovery history filehas been replaced. Processingcontinued.

Explanation: An error was encountered duringan access to the recovery history file. The utilityis able to recover the file from an alternate copy.

The utility continues processing.

User Response: The utility continues processingsuccessfully. The user should take appropriateprecautions to ensure the recovery history file isnot damaged again.

SQL2161N A damaged recovery history filecould not be fixed. The specifiedaction failed.

Explanation: An error was encountered duringan access to the recovery history file. The utilityis not able to recover the file. The utility stopsprocessing.

User Response: To continue processing, the usermay remove the recovery history file andresubmit the command. The utility willregenerate a new file. Any data from thecorrupted file are lost. The user may look at thecorrupted file to see if any information can besaved. The user should take appropriateprecautions to ensure the recovery history file isnot damaged again.

SQL2162N Rollforward operation failedbecause DB2 does not havepermission to access log filelog-file-number for databasedatabase-name on node node-number.

Explanation: DB2 cannot access the specifiedlog file because of the file permission settings.Rollforward cannot continue.

User Response: Check the file system where thelog files are stored. Make sure sufficientpermission is given to the instance owner toaccess these log files.

SQL2165W The SQLUHINFO structure didnot provide enough TABLESPACEentries.

Explanation: The SQLUHINFO structure wasnot large enough to hold the entry that was to bereturned (including all of its TABLESPACES).The value of the SQLN field of the SQLUHINFOstructure should be at least as large as the SQLDfield returned.



User Response: Increase the value of the SQLNfield in the SQLUHINFO structure to the valueindicated by the SQLD field (making sure theSQLUHINFO structure is large enough tosupport that amount) and resubmit thecommand.

SQL2170N The utility encountered entrieswith the same identifier in therecovery history file. Write fails.

Explanation: The utility has encountered anentry with the same identifier (timestamp to thesecond) in the recovery history file while writingto it. The write to the recovery history fileterminates. Database manager ensures theuniqueness of the recovery history file identifiersand makes provisions for it even if there aremore than one request per second. However,there may be cases where it will fail if numerousrequests come in within a few seconds.

User Response: If the applications are runningutilities (such as backup, quiesce, load) thatgenerate numerous entries to the history file, tryto pace the utility requests to prevent theproblem.

SQL2171N The update of the recovery historyfile failed because the specifiedobject part does not exist in thefile.

Explanation: The entry specified to be updatedin the recovery history file does not exist in thefile. The utility stops processing.

User Response: Resubmit the command with avalid entry.

SQL2172W The utility has completed but it isnot able to log the event in therecovery history file due to errorerror.

Explanation: The utility has encountered anerror writing to the recovery history file. Thiswarning does not affect processing.

User Response: Correct the error condition toprevent future warnings.

SQL2180N Incorrect syntax or incorrectpassword key used in filteringspecification.

Explanation: The filtering specification provideduses one or both of incorrect syntax or anincorrect password key.

User Response: Save the diagnosticinformation. Contact IBM service.

SQL2181N An internal error occurred duringfiltered recovery.

Explanation: An internal error occurred duringfiltered recovery. Recovery is terminated.

User Response: If the error was on an attemptto change the state for a table, try filtering outthe full tablespace. Save the diagnosticinformation. Contact IBM service.

SQL2200 - SQL2299

SQL2200N The qualifier for the table orindex name is too long.

Explanation: The authid must be 1 to 30characters (bytes in MBCS environment).


User Response: Resubmit the command withthe correct qualifier.

SQL2203N The tablename parameter is notvalid. Either the table name is toolong, only an authorization IDwas specified, the table name wasnot specified, or the address ofthe name is not valid.

Explanation: The table name is required and itmust be 1 to 128 characters in length (bytes inMBCS environments). The table name must be


located at a valid application address.


User Response: Resubmit the command withthe correct table name.

SQL2204N The iname parameter is not valid.The name of the index is too long,only an authorization ID wasspecified, or the address of theindex is not valid.

Explanation: If an index is specified, the namemust be 1 to 18 characters (bytes in MBCSenvironments). The index must be located at avalid application address.


User Response: Resubmit the command with avalid index name.

SQL2205N The specified index is not valid.Reason code: reason-code.

Explanation: The specified index parameter isnot valid for the requested operation. Followingis a list of reason codes:

1 The specified index does not exist forthe specified schema.table-name orschema.index-name.

2 The specified index is an extendedindex. The Reorganize Table utility doesnot support indexes based on indexextensions.

3 All indexes defined on the table must bepseudo delete enabled for the followingoperations: Inplace Table REORG,Online LOAD in incremental mode,REORG INDEXES with the CLEANUPONLY option.

4 An index other than the clustering indexwas specified on the REORG command.

5 Inplace table REORG is not allowed ifany spatial indexes exist on the table.

6 An index cannot be specified for aREORG of a table that has one or more

dimensions using the ORGANIZE BYclause of the CREATE TABLE command.


The utility or operation stops processing.

User Response: Resubmit the command with avalid index or without an index.

SQL2207N The filepath specified by thedatafile parameter is not valid.

Explanation: The datafile parameter is not anyof the values that indicate the default filepath.Also the datafile parameter is not a validnon-default value. One of the following mayapply:

v The pointer is not valid.

v The pointer points to a string that is too longfor a filepath designation.

v The specified path value is not valid (on theserver machine).

v The file path does not end with an appropriateseparator for the server machine.


User Response: Resubmit the command with avalid datafile parameter.

SQL2208N The table space specified by thetable space parameter is not valid.

Explanation: The table space parameter doesnot contain a valid value. One of the followingconditions may exist:

v The pointer is not valid

v The pointer points to a string that is too longfor a table space name

v The specified table space does not exist.


User Response: Resubmit the command with avalid table space parameter or do not use thetable space name parameter. In the latter case,the Reorganize Table utility will use the table


space(s) in which the table itself resides.

SQL2211N The specified table does not exist.

Explanation: The table does not exist in thedatabase. Either the table name or theauthorization ID is incorrect.



SQL2212N The specified table is a view. TheReorganize Table utility cannot berun against a view.

Explanation: The Reorganize Table utilitycannot be run against a view.



SQL2213N The specified table space is not asystem temporary table space.

Explanation: The REORG utility requires thatany table space specified is a system temporarytable space. The table space name provided isnot a table space defined to hold systemtemporary tables.


User Response: Resubmit the command withthe name of a system temporary table space ordo not use the table space name parameter. Inthe latter case, the REORG utility will use thetable space(s) in which the table itself resides.

SQL2214N The user does not have theauthority to run the REORGutility on table name.

Explanation: The user attempted to reorganizethe specified table or its indexes without theappropriate authorization (either SYSADM orDBADM authority or the CONTROL privilege onthe table).


User Response: Logon as a user with theappropriate authority or privilege and resubmitthe REORG utility command.

SQL2215N SQL error sqlcode occurred whilecommitting previous work for thedatabase.

Explanation: The user was already connected tothe database specified in the Reorganize Tablecommand. An error occurred while committingthe previous work in progress for the database.

The utility stops processing with no attempt toroll back the work or break the databaseconnection.


SQL2216N SQL error sqlcode occurred whilereorganizing a database table orits indexes.

Explanation: An error occurred during thereorganization of a database table or its indexes.



SQL2217N The page size of the systemtemporary table space used by theREORG utility must match thepage size of the table space(s) inwhich the table data resides(including the LONG and/or LOBcolumn data).

Explanation: If the system temporary table wasexplicitly specified to the REORG utility then thepage size of the system temporary table spaceused by the REORG utility must match the pagesize of the table space or table spaces in whichthe table data, including LONG and/or LOBcolumn data, resides. One of the following hasviolated this restriction:


v The table’s data resides in a table space thathas a different page size than that of thespecified system temporary table space.

v The table contains LONG and/or LOBcolumns whose data resides in a table spacewith a page size that is different than that ofthe system temporary table space and thetable’s regular data.

If the system temporary table space was notspecified to the REORG utility then the utilitywas looking internally for a system temporarytable space. A system temporary table space thatuses the same page size as the table data eitherdid not exist in the database or was not availableat the time.

User Response: If the table being reorganizedresides in a table space with a page size which isdifferent than that of the table space in which theLONG and/or LOB data of the table resides,then a system temporary table space cannot beprovided to the REORG utility. Reissue theREORG request without specifying a systemtemporary table space.

If a system temporary table space that uses thesame page size as the table data does not exist inthe database, please create a system temporarytable space using a page size that matches thepage size of the table data.

If a system temporary table space that uses thesame page size as the table data exists in thedatabase but was not available at the time ofyour command, please reissue the commandwhen the system temporary table space isavailable.

SQL2218N One or more parameters specifiedon the reorg command isincompatible.

SQL2219N The specified INPLACE tablereorganization action on tabletable-name is not allowed on oneor more nodes. Reason code:reason-code.

Explanation: The statement cannot be processedbecause it violates a restriction as indicated by

the following reason code:

1 Table reorganization cannot RESUME asthe original data or index object haschanged.

2 There is no reorganization to RESUMEfor the specified table.

3 An index cannot be specified toRESUME a non-clustering tablereorganization.

4 Table reorganization cannot RESUME asthe original index specified to STARTthe reorganization has been dropped.

5 The index specified on RESUME is notthe same index that was specified whenthe table reorganization was paused.

6 Unable to RESUME table reorganizationas the Status File is corrupted ormissing.

7 An I/O error occurred when attemptingto access the Status File.

8 INPLACE table reorganization is alreadyin progress for the specified table.

9 START is not allowed as a prior pausedtable reorganization has not beenstopped.

10 PAUSE or STOP has already beenissued. The specified action isasynchronous and may not be effectiveimmediately.

11 There is no table reorganization toPAUSE or STOP.

12 INPLACE table reorganization is notallowed for tables in append mode.

User Response:

1 Issue a STOP then a START.

2 There is no outstanding tablereorganization to RESUME. Issue theSTART action to reorganize the specifiedtable.

3 The original table reorganization did notuse an index and therefore an index


cannot be specified on RESUME. Eithercontinue the reorganization withoutusing an index or STOP the existingreorganization and issue a START withan index name.

4 STOP the existing paused tablereorganization and issue a START.

5 Resubmit the RESUME command withthe correct index. If no index is specifiedon RESUME the original index will beused by default.

6 Confirm whether the Status File“<tablespaceID><objectID>.OLR” existsunder the database directory and isaccessible then resubmit the command.If the file is damaged STOP then STARTthe table reorganization.

7 Ensure the Status File

“<tablespaceID><objectID>.OLR” isaccessible and resubmit the command.

8 START or RESUME is not allowed astable reorganization is already inprogress.

9 A reorg on the table has been paused.Either RESUME the paused reorg orSTOP then START the reorg.

10 Wait for the original STOP or PAUSE tocomplete.

11 Ensure reorganization is running for thespecified table.

12 Either ALTER the table to turn APPENDmode OFF or reorganize the tableoffline.

SQL2300 - SQL2399

SQL2300N The identifier for the table nameis too long or it was not specifiedas part of the table name.

Explanation: The table name must be fullyqualified. The format is authid.tablename whereauthid contains 1 to 30 characters and tablenamecontains 1 to 128 characters (bytes in MBCSenvironments).


User Response: Resubmit the command withthe fully qualified table name, including thecorrect qualifier.

SQL2301N The tablename parameter is notvalid. Either it is too long, only anauthorization ID was specified, orthe address of the name is notvalid.

Explanation: The table name must be fullyqualified and in the format authid.name whereauthid contains 1 to 30 characters and namecontains 1 to 128 characters (bytes in MBCSenvironments) and must be located at a validapplication address.


User Response: Resubmit the command withthe correct table name.

SQL2302N The index list is not valid. Eitherthe address for the list is notvalid, the number of entries in thelist is less than the number ofindexes specified, or the addressfor an index in the list is notvalid.

Explanation: The address for the list is notvalid, the number of entries in the list is lessthan the number of indexes specified, or theaddress for an index in the list is not valid.


User Response: Resubmit the command with avalid index list.

SQL2303N The statsopt parameter is notvalid.

Explanation: The statsopt parameter in the RunStatistics command must be one of the following:


v T for basic table only

v I for basic indexes only

v B for both basic table and indexes

v D for table and distribution

v E for table and distribution and basic indexes

v X for extended indexes only

v Y for extended indexes and basic table

v A for all


User Response: Resubmit the command with avalid statsopt parameter.

SQL2304N The sharelev parameter is notvalid. It must be ’R’ for referenceor ’C’ for change.

Explanation: The sharelev parameter in the RUNSTATISTICS command must be R for reference orC for change.


User Response: Resubmit the command with avalid sharelev parameter.

SQL2305N The table specified is a view. Theutility cannot be run against aview.

Explanation: The tname parameter specified aview rather than a table.


User Response: Resubmit the command with avalid tname parameter.

SQL2306N The table or index name does notexist.

Explanation: The table or index identified byname does not exist in the database, or the indexidentified by name is not defined on the specifiedtable. The qualifier for the table or one of theindexes may be incorrect.


User Response: Resubmit the command with

valid table names and indexes.

SQL2307N The table specified is a systemtable. The Runstats utility cannotbe run against a system table.

Explanation: The Run Statistics utility commandmay not be run against a system table.



SQL2308N The qualifier for the index namename is too long, or it was notspecified as part of the indexname.

Explanation: The index name must be a fullyqualified name. The format is authid.name whereauthid contains 1 to 30 characters and namecontains 1 to 18 characters (bytes in MBCSenvironments).


User Response: Resubmit the command with afully qualified name, including the correctqualifier.

SQL2309N The index name name is not valid.It is too long or only a qualifierwas specified.

Explanation: The index name must be a fullyqualified name. The format is authid.name whereauthid contains 1 to 30 characters and namecontains 1 to 18 characters (bytes in MBCSenvironments).


User Response: Resubmit the command with avalid index.

SQL2310N The utility could not generatestatistics. Error sqlcode wasreturned.

Explanation: An error occurred while the utilitywas gathering statistics.



User Response: Look at the message errornumber for more information. Make changes andresubmit the command.

SQL2311N The user does not have theauthority to run the Run Statisticsutility on table name.

Explanation: The user attempted to runstatistics on the specified table without theappropriate authorization (either the SYSADM orDBADM authority or the CONTROL privilege onthe table). If the table specified in RUNSTATS isthe root table of a table hierarchy, then the tablename returned in the message may be a subtableof the specified root table.


User Response: Do not attempt to call the RunStatistics utility command without appropriateauthorization.

SQL2312N Statistics heap size is too small tocarry out the operation. Suggestedheap size is num pages.

Explanation: The setting of the databaseconfiguration parameter stat_heap_sz is not bigenough to collect non-uniform distributionstatistics on the table.

User Response: Update the databaseconfiguration parameter stat_heap_sz to thesuggested value and try again.

SQL2313W All available memory in thestatistics heap has been used.Statistics were collected on thefirst n1 rows out of a total of n2rows.

Explanation: The setting of the databaseconfiguration parameter stat_heap_sz is not big

enough to collect non-uniform distributionstatistics on the table. Only <n1> of <n2> rowscould be processed.

User Response: Update the databaseconfiguration parameter stat_heap_sz by 20percent and try again.

SQL2314W Some statistics are in aninconsistent state. The newlycollected object1 statistics areinconsistent with the existingobject2 statistics.

Explanation: Issuing RUNSTATS on the tableonly may result in a situation where the tablelevel statistics are inconsistent with the alreadyexisting index level statistics. For example, ifindex level statistics are collected on a particulartable and later a significant number of rows isdeleted from this table, issuing RUNSTATS onthe table only may end up with the tablecardinality less than FIRSTKEYCARD which isan inconsistent state. Likewise, issuingRUNSTATS for indexes only or collectingstatistics during index creation may leave thealready existing table level statistics in aninconsistent state. For example, if table levelstatistics are collected on a particular table andlater a significant number of rows is deletedfrom this table, issuing RUNSTATS for theindexes only or collecting statistics during indexcreation may end up with some columns havinga COLCARD greater than the table cardinality.

User Response: If a RUNSTATS was issued onthe table only, issue a RUNSTATS for the indexesas well so that table level and index levelstatistics are consistent. Likewise, if a RUNSTATSwas issued for indexes only or statistics werecollected during index creation, issue aRUNSTATS on the table as well.

sqlcode: 2314

sqlstate: 01650

SQL2400 - SQL2499


SQL2400N The type specified in theBACKUP command is not valid. Itmust be either 0 to back up theentire database or 1 to back uponly the current changes.

Explanation: The type must be either 0 forbacking up the whole database or 1 for backingup changes only.


User Response: Resubmit the utility commandwith the correct type.

SQL2401N “Backup changes only” cannot beperformed until a backup of theentire database has been done.The type must be 0.

Explanation: A backup of changes only hasbeen requested without requesting a backup ofthe entire database first, or an internal file hasbeen damaged such that the BACKUP utilitycannot determine whether a full backup hadbeen taken. The backup of changes only cannotbe used until after a backup of the entiredatabase.


User Response: Resubmit the utility commandwith the correct type.

SQL2403N The user does not have theauthority to run the utility againstthe database.

Explanation: The user attempted to execute adatabase utility without either SYSADM orDBADM authority.


User Response: Do not attempt to call theutility command without appropriateauthorization.

SQL2404N The backup target media is full.At least number free bytes areneeded on the target media.

Explanation: The backup target media does nothave enough space for creating an internalsubdirectory and information file.


User Response: Prepare a backup media thathas at least the specified number of bytes of freespace and then resubmit the command.

SQL2405N The BACKUP cannot beperformed because there is apreviously incomplete RESTORE.

Explanation: The database is in an inconsistentstate due to a system crash during a restoreoperation or due to an abnormally terminatedRESTORE.


User Response: Resubmit the RESTOREcommand.

SQL2406N The BACKUP cannot beperformed because the databaseneeds to be rolled forward.

Explanation: The backup failed because thedatabase is in an inconsistent state.


User Response: Use the ROLLFORWARDcommand to make the database usable. Thenresubmit the BACKUP command.

SQL2407N An I/O error occurred reading thefile name. The BACKUP cannot beperformed because it cannotdetermine if a RESTORE wascompleted.

Explanation: The indicated file cannot be readdue to the I/O error. Since the file exists, aBACKUP or RESTORE command must have notcompleted. Upon successful completion of theprocess this file is deleted.



User Response: Determine which process wasexecuted previously. Delete the indicated file andresubmit the previous command.

SQL2408W The database was backed up, butan I/O error error occurred whiledeleting the file name.

Explanation: The BACKUP command ransuccessfully. The indicated file was not deleteddue to an I/O error.

The utility completed processing.

User Response: Try to delete the file indicatedin the message.

SQL2409N When doing a BACKUP ofchanges only, the most recentbackup image must be used.

Explanation: The user has attempted to performa changes only backup but the backup imagespecified is not the most current backup or theprevious backup of changes only failed.


User Response: Locate the most recent backupimage and resubmit the command. If the mostrecent backup image cannot be located or if theprevious backup of changes only failed, resubmitthe command requesting a backup of the entiredatabase rather that a changes only backup.

SQL2410N “Backup changes only” cannot beperformed if the database isenabled for ROLLFORWARD or ifthe BACKUP is being donethrough a user exit.

Explanation: The user requested a changes onlybackup of a database with roll-forward enabled,or has requested a changes only backup throughthe user exit program.


v If the database is roll-forward enabled,resubmit the BACKUP utility commandrequesting a backup of the entire database.

v Disable roll-forward by turning of theSQL_ENABLE_LOG_RETAIN flag andSQL_ENABLE_USER_EXIT flag in thedatabase configuration file. Then resubmit theBACKUP utility command requesting achanges only backup.

v If the backup was requested through the userexit program, resubmit the BACKUP utilitycommand to do a changes only backup notusing the user exit program.

v If the backup was requested through the userexit program to a standard device, resubmitthe BACKUP utility command to do a changesonly backup not using the user exit program.

SQL2411C An I/O error occurred whilerunning a utility. Either the diskcould not be physically written toor has been filled.

Explanation: An operating system erroroccurred when the utility was writing to the diskor diskette. The actual return code can be foundin the SQLERRD[0]field of the SQLCA.


SQL2412C A corrupted database page wasencountered while running adatabase utility.

Explanation: During the utility operation acorrupted database page was encountered. Thedatabase is in an unpredictable state and theutility cannot continue.

User Response: Record the message number(SQLCODE).




v SQLCA if possible



SQL2413N Online backup is not allowedbecause either logretain oruserexit for roll-forward is notactivated, or a backup pendingcondition is in effect for thedatabase.

Explanation: Online backup cannot beperformed while the database is not logging forforward recovery as forward recovery will berequired at restore time. Forward recovery isplaced into effect by setting either the databaseconfiguration logretain parameter or the userexitparameter, and then performing an offlinebackup of the database.

User Response: Execute an offline backup orreconfigure the database for roll-forwardrecovery and issue an offline backup so thatsubsequent online backups will be allowed.

SQL2414W Warning! Insufficient space ondevice device to contain backupcontrol information. This mediawill not contain backupinformation.

Explanation: During the Backup operation anew media was mounted and positioned afterone or more media became full. There is notenough space on this media to contain theBackup Control Information and the mediashould not be included during the Restoreoperation.

User Response: Mount a new media, orreposition the current media to provide enoughspace for this header, then return to the utilitywith the callerac parameter indicating ifprocessing continues.

SQL2416W Warning! Device device is full.Please mount new media.

Explanation: The tape which the utility is usinghas become full.

User Response: Mount another tape andcontinue the operation with the calleracparameter indicating if processing continues.

SQL2417N Archive log is not allowed onnon-recoverable databases.

Explanation: The archive log command canonly be used on databases that are in recoverablemode. A database is in recoverable mode if eitherLOGRETAIN or USEREXIT are enabled.

User Response: Ensure that the specifieddatabase is in recoverable mode and reissue thecommand.

SQL2418N The database specified for Backupdoes not exist.

Explanation: The database specified in the dbaseparameter of the Database Backup commandcould not be found.

User Response: Ensure that the correct databasealias was specified for the Backup Databaseutility and that the database exists for this alias.Resubmit the command with the correct alias.

SQL2419N The target disk disk has becomefull.

Explanation: During the processing of adatabase utility, the target disk became full. Theutility has stopped and the target is deleted.

User Response: Ensure enough disk space isavailable for the utility or direct the target toother media, such as tape.

On unix-based systems, this disk full conditionmay be due to exceeding the maximum file sizeallowed for the current userid. Use the chusercommand to update fsize. A reboot may benecessary.

On non unix-based systems, this disk fullcondition may be due to exceeding themaximum file size allowed for the operatingsystem. Direct the target to other media, such astape, or use multiple targets.


SQL2420N Insufficient space on device deviceto contain initial backup controlinformation.

Explanation: During the Backup operation aninitial backup header needs to be created at thestart of the backup image. This header must fiton one tape when backing up to tape. There isinsufficient space on the tape to contain thisheader.

User Response: Resubmit the Backup operationand either direct the output to a new tape, orreposition the current tape to provide enoughspace for this header.

SQL2421N Table space level backup is notallowed because roll-forwardrecovery is not enabled.

Explanation: Table space level backup cannot beperformed while the database is not logging forforward recovery as forward recovery will berequired at restore time. Forward recovery isplaced into effect by setting either the databaseconfiguration logretain parameter or the userexitparameter, and then performing an offlinebackup of the database.

User Response: Execute a full database backupor reconfigure the database for roll-forwardrecovery and issue an offline backup so thatsubsequent table space level backups will beallowed.

SQL2422N The database cannot be backed upwith a back-level backup API dueto incompatible table spacelocations.

Explanation: This database contains tablespace(s) which have been defined in a locationother than the database subdirectory. This is notcompatible with the API being used.

User Response: Use the current backup API tobackup the database.

SQL2423N The database cannot be backed upbecause some index files aremissing.

Explanation: Some of the index files requiredby the backup are missing. These index filesmust be recreated prior to backing up thedatabase.

User Response: Run the ’db2recri’ program torecreate the missing index files and thenresubmit the backup command.

SQL2424N The backup could not succeedbecause asynchronous copyoperations at DB2 Data LinksManagers are not complete.

Explanation: The TSM or vendor suppliedarchive server might not be in operational state.

User Response: Ensure TSM or the vendorsupplied archive server is in an operational stateand resubmit the backup command.

SQL2425W The log file for the online backupwas not truncated.

Explanation: During an online backup, allbuffered log records are forced to disk and thelast active log file is truncated. During thecurrent backup, truncation of the last active logfile has failed. As a result, new log records willcontinue to be written into the last log file usedduring the backup.

User Response: No user action is required. Thelast active log file used during the backup willeventually become inactive when it becomes full.

SQL2426N The database has not beenconfigured to allow theincremental backup operation.Reason code = reason-code.

Explanation: Incremental backups are notenabled for a table space until after modificationtracking has been activated for the database anda non-incremental backup has been performedon the table space.

Possible reason codes:


1. The configuration parameter TRACKMODhas not been set for the database.

2. The TRACKMOD configuration parameterhas been set but at least one table space hasnot had a non-incremental backup taken sincethe TRACKMOD parameter was set.

User Response: The action is based on thereason code as follows:

1. Activate modification tracking for thedatabase by setting the TRACKMODdatabase configuration parameter to on, thenperform a full database backup.

2. Perform a full backup of the table space.

SQL2500 - SQL2599

SQL2501C The database was restored but thedata in the restored database wasunusable.

Explanation: The RESTORE utility either couldnot read data from the restored database or onlya portion of the database was restored. Bothcases indicate that the restored database is notusable.

The database is unusable and the RESTOREutility stops processing.

User Response: Resubmit the RESTOREcommand.

SQL2502C An error occurred while readingthe backup files. Either the diskcould not physically be read orthe specified disk did not containa valid backup.

Explanation: An operating system erroroccurred when the RESTORE utility was readingthe diskette or disk, or the diskette or disk doesnot contain a backup of the database directory ordoes not contain the results of any previousbackup.


User Response: If the input drive specified is adiskette drive, check the diskette being used. Ifthe input drive is a hard file, verify that it is thecorrect hard file. Resubmit the command withthe correct input drive and the correct diskettes,if applicable.

SQL2503N The RESTORE was not successful.The backup used to restore thedatabase contained the wrongdatabase.

Explanation: The name of the databasecontained on the backup disk does not match thedatabase name specified on the RESTOREcommand. The RESTORE utility cannotdetermine the name until after the database hasbeen restored because a previous release backupimage was restored.


User Response: If the wrong database namewas used in the command, resubmit thecommand with the correct database name. If theinput drive specified is a diskette drive, checkthe diskette being used. If the input drive is ahard file, verify that it is the correct hard file.Resubmit the command with the correct inputdrive and the correct diskettes, if applicable.

SQL2504W Insert the first backup disketteinto drive drive.

Explanation: The RESTORE utility reads thefirst backup diskette to determine the path of thedatabase directory that was backed up. If thebackup media is a diskette and the diskette isnot found in the specified input drive, the utilityreturns to the caller with this prompt. The callingprogram is expected to query the user and returnto the utility with the user response.

The utility waits for a response from the caller.

User Response: Prompt the user for the disketteand return to the utility with the callerac


parameter, indicating if processing continues orends.

SQL2505W Warning! Database name resides atdrive. The files for this databasewill be deleted.

Explanation: If the database being restoredalready exists, its files will be deleted before therestore process starts. The utility returns to thecaller with this warning. The caller is expected toquery the user and return to the utility with theuser response. Once the database is dropped, itcannot be accessed again.

The utility waits for response from the caller.

User Response: Warn the user that the databasefiles will be deleted and return to the utility withthe callerac parameter indicating if processingcontinues or ends.

SQL2506W The database was restored, butthere may be extra files in thedatabase.

Explanation: If changes-only backups wereperformed and database files were deletedbetween backups, the RESTORE utility addsthese deleted files back into the database. Therestore process could not delete the extra fileseither because of an I/O error or by the failure ofan internal connection to an internally stoppeddatabase.

The utility ends successfully.

User Response: Either use the database as it isor attempt to restore it again. Ensure that theDB2 configuration is compatible with therestored database configuration before rerunningthe RESTORE utility.

SQL2507W The RESTORE utility is notbound to the database correctly.

Explanation: Because the RESTORE utility wasnot bound to the database or the package of theutility that was bound to the database is notcompatible with the installed version of DB2, allthe utilities have been rebound to the database.But there is a timestamp conflict between the

installed version of DB2 and the package so theutility and bind file are not compatible.

The database is restored, but the utility is notcorrectly bound.

User Response: Reinstall DB2 or reapply recentupdates and resubmit the utility command.

SQL2508N The Database Restore timestampparameter timestamp is not valid.

Explanation: The timestamp parameter mustcontain either NULL or a portion of a validtimestamp, the portion consisting of completecomponents of a timestamp.

User Response: Resubmit the Restore operationwith a valid timestamp value.

SQL2509N The database drive parameter isnot valid.

Explanation: The drive specified does not exist,or the database does not exist on this drive or isnot cataloged on this drive. RESTORE should usethe db2uexit command to perform the databaserestore.


User Response: Resubmit the utility commandwith a valid drive.

SQL2510N An operating system semaphoreerror occurred.

Explanation: An error occurred in the wait orpost semaphore.


User Response: Stop the database manager,then restart it and resubmit the utility command.

SQL2511N The utility encountered an errorerror while dropping the database.

Explanation: The utility could not drop thedatabase.


User Response: Look at the error number in the


message for more information. Make changesand resubmit the command.

SQL2512N The utility encountered an errorerror while creating the database.

Explanation: The utility could not create thedatabase.



SQL2513N The utility encountered an errorerror renaming the database.

Explanation: The utility could not rename thedatabase.



SQL2514N The RESTORE was not successful.The backup used to restore thedatabase contained a databasewith a release number that is notcompatible with the installedversion of the database manager.

Explanation: The release number of the restoreddatabase is not compatible with the releasenumber of the installed version of the databasemanager.


User Response: Resubmit the command with abackup that is compatible with the release levelof the database manager.

SQL2515N The user does not have theauthority to run the RESTOREutility against the database.

Explanation: The user attempted to execute theRESTORE utility without SYSADM authority.


User Response: Do not attempt to call theRESTORE utility command without appropriateauthorization.

SQL2516N The RESTORE utility cannotcomplete because at least onedatabase on the workstation is inuse.

Explanation: In some situations, the RESTOREutility can attempt to move a database to adirectory by renaming the directory associatedwith the database. This cannot be done if anydatabases are in use in any process on theworkstation.


User Response: Wait until no databases on theworkstation are in use and resubmit thecommand.

SQL2517W The restored database wasmigrated to the current release.

Explanation: The database being restored wasbacked up using a previous release of DB2. TheRESTORE utility migrated it to the format of thecurrent release.

The user who submitted the RESTORE commandis given DBADM authority for the database. Ifthere are other users, the database administratorwith DBADM authority must grant authorizationprivileges to the specific database users.

The RESTORE utility completes successfully.


SQL2518N The RESTORE was not successful.An I/O error occurred whiletrying to restore the databaseconfiguration file.

Explanation: The database configuration filecould not be restored due to an I/O error.


User Response: Determine whether the I/Oerror can be corrected. Resubmit the command.


SQL2519N The database was restored, butthe restored database was notmigrated to the current release.Error sqlcode with tokens tokens isreturned.

Explanation: The backup image contains aprevious release of the database. After thedatabase files were restored, an attempt wasmade to migrate the database to the currentrelease. The migration failed.

The utility finishes processing but the databasewas not migrated.

User Response: Look at the SQLCODE(message number) in the message for moreinformation. Make changes and submit theMigrate command before using the database.

SQL2520W The database was restored. Thebackup version of theconfiguration file was used.

Explanation: When a database is restored, thecurrent database configuration file is not alwaysreplaced with the backup version. The currentdatabase configuration file was not usable. It hasbeen replaced by the backup version.

The utility completed successfully.

User Response: Some values in the databaseconfiguration file may be different after therestore process. Check that the configurationparameters are set to the desired values.

SQL2521W The database was restored, but anI/O error code occurred whiledeleting file type file-type.

Explanation: The restore process ransuccessfully. The specified file was not deleteddue to an I/O error.

A file with the extension “.BRG” is used todetermine whether a RESTORE operation hasterminated abnormally. The file resides in thelocal database directory of the database forwhich the RESTORE operation was attempted.

A file with the extension “.BRI” storesinformation about the progress of an incremental

RESTORE operation. The file resides in the localdatabase directory of the database for which theRESTORE INCREMENTAL operation wasattempted.

The file name consists of the database tokenconcatenated with the file type extension. Forexample, if the database “SAMPLE” is assignedthe database token “SQL00001”, the BRI file willhave the name“instance/NODE0000/sqldbdir/SQL00001.BRI”.

The utility completed successfully.

User Response: Delete the .BRG or .BRI filemanually. If the file cannot be deleted, contactyour technical service representative.

SQL2522N More than one backup filematches the timestamp valueprovided for the backed updatabase image.

Explanation: The backup image file filenameconsists of a database alias and a timestampcomponent. A filename is constructed from thesource database alias and timestamp parametersprovided in the Database Restore call. A portionof a timestamp may have been specified so that amatch with more than one backup imagefilename was found.

User Response: Resubmit the operation byspecifying a timestamp with sufficient timestampcomponents to result in a match to a uniquebackup file.

SQL2523W Warning! Restoring to an existingdatabase that is different from thedatabase on the backup image,but have matching names. Thetarget database will beoverwritten by the backupversion. The Roll-forwardrecovery logs associated with thetarget database will be deleted.

Explanation: The database alias and name ofthe target database are the same as the backupimage database alias and name. The databaseseeds are not the same indicating that thedatabases are not the same. The target database


will be overwritten by the backup version. TheRoll-forward recovery logs associated with thetarget database will be deleted. The currentconfiguration file will be overwritten with thebackup version.

User Response: Return to the utility with thecallerac parameter indicating processing tocontinue or end.

SQL2524W Warning! Restoring to an existingdatabase which appears to be thesame but the alias dbase of theexisting database does not matchthe alias dbase of the backupimage. The target database will beoverwritten by the backupversion.

Explanation: The database seeds of the targetdatabase and the database image are the same,indicating these are the same databases, thedatabase names are the same, but the databasealiases are not the same. The target database willbe overwritten by the backup version.


SQL2525W Warning! Restoring to an existingdatabase that is different from thedatabase on the backup image,and the alias dbase of the existingdatabase does not match the aliasdbase of the backup image, but thedatabase names are the same. Thetarget database will beoverwritten by the backupversion. The Roll-forwardrecovery logs associated with thetarget database will be deleted.

Explanation: The database aliases of the targetdatabase and database image are not the same,the database names are the same, and thedatabase seeds are not the same, indicating theseare different databases. The target database willbe overwritten by the backup version. TheRoll-forward recovery logs associated with thetarget database will be deleted. The current

configuration file will be overwritten with thebackup version.


SQL2526W Warning! Restoring to an existingdatabase that is the same as thebackup image database, and thealias names are the same, but thedatabase name dbname of theexisting database does not matchthe database name dbname of thebackup image. The targetdatabase will be overwritten bythe backup version.

Explanation: The database aliases of the targetdatabase and database image are the same, andthe database seeds are the same, however thedatabase names are different. These are the samedatabases. The target database will beoverwritten by the backup version.


SQL2527W Warning! Restoring to an existingdatabase that is different from thebackup image database, and thedatabase name dbname of theexisting database does not matchthe database name dbname of thebackup image, but the aliasnames are the same. The targetdatabase will be overwritten bythe backup version. TheRoll-forward recovery logsassociated with the targetdatabase will be deleted.

Explanation: The database aliases of the targetdatabase and database image are the same, thedatabase names are not the same, and thedatabase seeds are not the same, indicating theseare different databases. The target database willbe overwritten by the backup version. TheRoll-forward recovery logs associated with thetarget database will be deleted. The current


configuration file will be overwritten with thebackup version.


SQL2528W Warning! Restoring to an existingdatabase that is the same as thebackup image database, but thealias name dbase of the existingdatabase does not match the aliasdbase of backup image, and thedatabase name dbname of theexisting database does not matchthe database name dbname of thebackup image. The targetdatabase will be overwritten bythe backup version.

Explanation: The database aliases of the targetdatabase and database image are not the same,the database names are not the same, and thedatabase seeds are the same, indicating these arethe same databases. The current database will beoverwritten by the backup version.


SQL2529W Warning! Restoring to an existingdatabase that is different from thebackup image database, and thealias name dbase of the existingdatabase does not match the aliasname dbase of the backup image,and the database name dbname ofthe existing database does notmatch the database name dbnameof the backup image. The targetdatabase will be overwritten bythe backup version. TheRoll-forward recovery logsassociated with the targetdatabase will be deleted.

Explanation: The database aliases of the targetand database image are not the same, thedatabase names are not the same, and thedatabase seeds are not the same, indicating these

are different databases. The current database willbe overwritten by the backup version. TheRoll-forward recovery logs associated with thetarget database will be deleted. The currentconfiguration file will be overwritten with thebackup version.


SQL2530N The backup image is corrupted.Restore of database from thisbackup image is not possible.

Explanation: The backup image being restoredis corrupted making the database imagenon-restorable.

User Response: Discard the backup image as itis unusable. Restore from a previous backup ifpossible.

SQL2531N The backup image selected forrestore is not a valid databasebackup image.

Explanation: The file selected for restore is nota valid backup image. Either the file selected hasbecome corrupted or a backup tape is not at thecorrect position.

User Response: Determine the location of thecorrect backup image file, and resubmit theRestore command.

SQL2532N The backup file contains thebackup image of database dbaliastaken at timestamp timestamp. Thisis not the backup imagerequested.

Explanation: The file selected for restore doesnot contain the requested backup image. Theimage is for a different database than thatrequested.

User Response: If using tape, ensure that thecorrect tape is mounted. If a restore or load isbeing done from disk, then the file must havebeen renamed. Rename the file to the correctfilename with a match on database name and


timestamp. Resubmit the command after takingthe appropriate action.

SQL2533W Warning! The backup file ondevice device contains the image ofdatabase database taken attimestamp timestamp. This is notthe backup image requested.

Explanation: The backup image read from thetape position contains a media header that doesnot match the header of the image of the first fileof the backup file sequence.

User Response: Ensure that the tape ispositioned at the correct backup, then return tothe utility with the callerac parameter indicatingif processing continues.

SQL2534W Warning! The media on devicedevice is not positioned at a validbackup media header.

Explanation: The data read from the tapeposition does not contain a valid backup mediaheader.

User Response: Ensure that the tape ispositioned at the correct position, then return tothe utility with the callerac parameter indicatingif processing continues.

SQL2535W Warning! End of media on devicedevice has been reached. Pleasemount the next source media.

Explanation: The end of tape has been reachedand there is still more data to be processed. Theremainder of the backup or load source exists onanother tape or on several more tapes.

User Response: Mount the next tape insequence that contains the source image andresubmit the Restore or Load command with thecallerac parameter set to continue or end.

SQL2536W Warning! The backup image ondevice device contains an incorrectsequence number. Sequencenumber number is expected.

Explanation: The tape is positioned on abackup image file that is out of sequence. Thetape containing the backup image must bepositioned to the file of sequence numbersequence of the backup image.

User Response: Position the tape containing thebackup image to the correct file and resubmit theRestore command with the callerac parameter setto continue or end.

SQL2537N Roll-forward is requiredfollowing the Restore.

Explanation: SQLUD_NOROLLFWD wasspecified for the rst_type parameter of theDatabase Restore utility, indicating that aroll-forward is not required to make the restoreddatabase usable. The database to be restored wasbacked up in online mode and a roll-forwardoperation is necessary to make the databaseusable.

User Response: Resubmit the Database Restorecommand without specifyingSQLUD_NOROLLFWD for the rst_typeparameter.

SQL2538N Unexpected End of File of BackupImage reached on media media.

Explanation: While reading and restoring fromthe Backup Image file, an end of file conditionwas reached unexpectedly. The backup image isunusable and the restore operation terminates.

User Response: Resubmit the Database Restorecommand with a usable backup image file.

SQL2539W Warning! Restoring to an existingdatabase that is the same as thebackup image database. Thedatabase files will be deleted.

Explanation: The database aliases, names andseeds of the target database and database image


are the same, indicating these are the samedatabases. The current database will beoverwritten by the backup version.


SQL2540W Restore is successful, however awarning warn was encounteredduring Database Restore whileprocessing in No Interrupt mode.

Explanation: The Database Restore utility wasinvoked in No Interrupt mode, i.e.SQLUB_NO_INTERRUPT orSQLUD_NO_INTERRUPT was specified. Duringthe processing a warning was encountered butnot returned at the time it was encountered. TheRestore has completed successfully and thewarning message found is shown at thecompletion in this message.

User Response: Ensure that the action thatcaused this warning to be generated has notresulted in a condition not wanted.

SQL2541W The utility was successful,however the file containing thebackup image could not beclosed.

Explanation: The utility was successful, but thefile containing the backup image could not beclosed.

User Response: Attempt to close the filecontaining the backup image.

SQL2542N No match for a database imagefile was found based on thesource database alias database-aliasand timestamp timestampprovided.

Explanation: The backup image file filenameconsists of a database alias and a timestampcomponent. A filename is constructed from thesource database alias and timestamp parametersprovided in the Database Restore call. Nofilename existed in the source directory that

matched based on the source database alias andtimestamp provided. If this error was receivedfrom an automatic incremental restore then arequired image was not found based on thetimestamp and location in the database history.

User Response: Ensure that the databasebackup image resides on the media source.Resubmit the operation by specifying a correcttimestamp to result in a match.

If this error was received from an automaticincremental restore, check the database historyfor the corresponding backup entry and verifythat the location listed matches the actuallocation of the backup image. Either update thedatabase history and retry the operation to resultin a match or issue a RESTORE INCREMENTALABORT command to cleanup any resources thatmay have been created during processing.

SQL2543N The target directory specified forthe database is not valid.

Explanation: The application calling the Restoreutility has supplied a target directory for the newdatabase to be created. Either this directory doesnot exist, or is not a valid directory for databasecreation. An invalid directory for databasecreation would be a directory of greater than 255characters in length.

User Response: Reissue the Backup or Restorecommand with a valid target directory.

SQL2544N The directory where the databaseis being restored has become full.

Explanation: While the database was beingrestored the directory to which it was beingrestored had become full. The database beingrestored is unusable. The Restore terminates andif the database being restored is a new database,then it is deleted.

User Response: Free up sufficient space on thedirectory for the database, and reissue theRestore, or if restoring to a new database supplya directory with sufficient space to contain thedatabase.


SQL2545W Warning! The backup image onthe TSM server is currently storedon mountable media. The timerequired to make it available isunknown.

Explanation: The backup image is notimmediately accessible by the TSM server. Therestore process can continue and make therequest to the server to retrieve the data. Thetime required is unknown.


SQL2546N The image on media media is notthe first in sequence from thebackup or copy.

Explanation: During restore or load recovery,the first image from the backup or copy must beprocessed first. The image found on the media isnot the first in sequence.


User Response: Mount the media with thecorrect backup or copy image and return to theutility with the correct caller action parameter toindicate if processing should continue orterminate.

SQL2547N The database was not restoredbecause the backup image is froma previous release and requiresrollforward recovery.

Explanation: The physical log file formats havechanged between these releases, makingrollforward impossible.

User Response: Restore the database using theversion of DB2 used to create the database androllforward to the end of logs. Take an off-linefull database backup at this time. This newbackup image will be restorable on the newrelease of DB2.

SQL2548N Database code page indicatedwithin the backup image code-pageis invalid or not supported. Therestore operation has failed.

Explanation:

1. The backup image you are restoring mayhave been created on a server with a newerFixPak level than the FixPak level that hasbeen applied to this server. In this case, it ispossible that the image contains a newer codepage that is unsupported.

2. The backup image is corrupt and containsinvalid code page information.

User Response: If attempting to restore animage from a server with a newer FixPak level toa server with a lesser FixPak level, then ensurethat the code page is supported by both servers.Alternatively, consider applying the newerFixPak to the server you are restoring to.

SQL2549N The database was not restoredbecause either all of the tablespaces in the backup image areinaccessible, or one or more tablespace names in list of table spacenames to restore are invalid.

Explanation: The containers which were usedby the table spaces in the backup image are notavailable, are already in use, or one or more tablespace names specified in the list on the restorecommand do not exist in the backup image.

User Response: Use redirected restore toredefine the containers for the table spaces in thisbackup image, or specify a list of valid tablespace names to restore.

SQL2550N Database backed up on nodenode1 cannot be restored to nodenode2.

Explanation: The backup image used for therestore is a backup of a database from a differentnode. You can only restore a backup to the samenode.

User Response: Ensure that you have the


correct backup image for the node then issue therequest again.

SQL2551N Database with catalog node node1cannot be restored to a databasewith catalog node node2.

Explanation: The catalog node can exist on onlyone node and there is a discrepancy between thebackup image and the node being restored to.This can occur in the following cases:

1. The backup image specified catalog nodenode1 and the restore was attempted to anexisting database whose catalog node is nodenode2

2. The restore was attempted to a new databaseand the catalog node has not been restoredfirst.

User Response: Verify that the correct backupimage is being restored.

If you are restoring to an existing database andwant to change the catalog node to node2, theexisting database must be dropped first.

If you are restoring to a new database, restorethe catalog node node1 first.

SQL2552N Invalid report file name specifiedin the restore command.

Explanation: The length of the report file nameexceeded the allowed limit of 255.

User Response: Specify a report file namewhose length is within the allowed limit andresubmit the restore command.

SQL2553I The RECONCILE utilitycompleted successfully.

Explanation: The utility completed successfully.

User Response: No action necessary.

SQL2554N The RECONCILE utility failedwith reason code reason-code.Possible problem with component.

Explanation: Possible Reason codes:

1 Unknown connection to a DB2 DataLinks Manager.

2 Table/DATALINK column not definedon the DB2 Data Links Manager.

3 DB2 Data Links Manager may be down.

4 I/O problems.

5 The exception table contains datalinkcolumns that are defined with file linkcontrol.

6 Table is in “Datalink Reconcile NotPossible” state.

7 Exception table not allowed for reconcileon typed tables.

8 ALTER TABLE failed to put the tableinto “Datalink Reconcile Pending” or“Datalink Reconcile Not Possible” state,or failed to take the table out of“Datalink Reconcile Pending” or“Datalink Reconcile Not Possible” state.

9 Data Links support is not turned on.

10 Table is in check pending state.

11 A required DB2 Data Links Managerwas not available during exceptionhandling. Table is placed in DataLinkReconcile Pending state.

12 Reconcile processing could not completeon the DB2 Data Links Manager(s) inthe allotted time period. Check theadministration notification log fordetails.

User Response: Possible Solutions:

1 Make sure that the DB2 Data LinksManager is up and running, and that ithas been registered with the databaseusing the ADD DATALINKSMANAGER command. Try connectingto the database and make a sure acorresponding connection has beenestablished on the DB2 Data LinksManager.

2 The table does not seem to exist on theDB2 Data Links Manager. Nothing toreconcile.


3 DB2 Data Links Manager may be down.Try starting the DB2 Data LinksManager.

4 Ensure you have file permissions andenough space for the report file. A fullyqualified path is required for theDLREPORT parameter. Ensure that thetable being reconciled is not damaged.

5 Redefine all datalink columns in theexception table as “NO LINKCONTROL”.

6 Take the table out of “DatalinkReconcile Not Possible” state using theSET INTEGRITY command. Repeat thereconcile command.

7 Do not specify an exception table.

8 Try issuing a SET INTEGRITY commandto put the table into “Datalink ReconcilePending” state or to reset the “DatalinkReconcile Pending” or “DatalinkReconcile Not Possible” state.

9 The value of the database managerconfiguration parameter DATALINKS isset to NO. To use RECONCILE, youmust set the value of the parameterDATALINKS to YES.

10 To run reconcile on a table, the tablecannot be in check pending state. Toremove the check pending state, use theSET INTEGRITY command.

11 Run reconcile again.

12 The reconcile command has timed outwaiting for verification from the DB2Data Links Manager(s). Try the reconcilecommand again.

SQL2560N The target database is notidentical to the source databasefor a restore from a table spacelevel backup.

Explanation: For a restore from a table spacelevel backup, the target database must be eitherthe original database from which the backup istaken or a new database.

User Response: Specify the correct targetdatabase and resubmit the utility command.

SQL2561W Warning! Restoring from a tablespace level backup to a databasewhich does not exist. A databasewith the same attributes in thebackup will be created.

Explanation: For a restore from a table spacelevel backup, the target database must have thesame attributes (database name, alias and seed)as the source database. If the database does notalready exist, it will be created.


SQL2562N Table space level restore from afull database backup is notallowed.

Explanation: For a restore from a full databaselevel backup, the restore type cannot be tablespace level.

User Response: Specify a correct restore type oruse a correct backup image and resubmit theutility command.

SQL2563W The restore process has completedsuccessfully, but one or moretable spaces from the backupwere not restored.

Explanation: The restore process has completedsuccessfully. One or more table spaces that are inthe backup were not restored for one of thefollowing reasons:

v an error was encountered while accessing thecontainers of the table spaces. If the tablespaces have been dropped since the backupwas taken, no further action is necessary.

v the restore command was invoked with a listof table spaces so that only a subset of thetable spaces in the backup were restored. Nofurther action is necessary.

User Response: If this message is not due to asubset restore, use the query table space function


to check the states of the table spaces. If a tablespace is in the ″storage definition pending″ state,the storage definition for the table space must becorrected for restore to complete successfully. Seethe Administration Guide for details aboutrecovering the table space.

SQL2564N The pagesize of one or more tablespaces in the backup image donot match that of thecorresponding destination tablespaces.

Explanation: The target table space pagesizemust match that of the table space pagesize inthe backup image. Restoring to a table space of adifferent pagesize is not supported. The defaultpagesize is 4K.

User Response: Ensure that the table spacebeing restored into has the same pagesize as thetable space in the backup image.

SQL2565N The option specified forRESTORE is not allowed with thebackup image provided.

Explanation: The database contained in thebackup image is an existing database and doesnot match the database to be restored. Theoption you have specified for restore requiresthat the database being restored to is new or thesame as in the backup image.


User Response: Resubmit the command withthe correct database name.

SQL2566W The restore process has completedsuccessfully, but one or moretable spaces have their tables putin DRP/DRNP state. Check thedb2diag.log file for details.

Explanation: One or more table spaces havetables in DATALINK Reconcile Pending (DRP) orDATALINK Reconcile Not Possible (DRNP)because of one of the following reasons:

v Restoring to a database that has a differentdatabase name, alias, hostname, or instance

than the backup image. If no rollforwardfollows the restore, any tables withDATALINK columns are placed in DRNPstate.

v Restore is done specifying the WITHOUTDATALINK option and no rollforward followsthe restore. Any tables with DATALINKcolumns are placed in DRP state.

v Restoring from a backup image that hasbecome unusable. If no rollforward follows therestore, any tables with DATALINK columnsare placed in DRNP state.

v DATALINK column information does not existat the DB2 Data Links Manager(s). Affectedtables are placed in DRNP state.

v Restore involving fast reconciliation failedwhile trying to relink files at the DB2 DataLinks Manager(s). Affected tables are placed inDRNP state.

User Response: Look in the administrationnotification log to find out what tables are put inDRP/DRNP state. See the Administration Guidefor information on reconciling tables that are inDRP/DRNP state.

SQL2570N A database cannot be restored ona platform that does not match theplatform on which the backupimage was created.

Explanation: You created the backup image onone type of platform and are trying to restore iton a different platform. However, backup imagesmust be restored on a system whose machinetype and operating system match the system onwhich the backup image was created.

User Response: To use this particular backupimage, restore it on a system that corresponds tothe system on which the backup was taken.

To move a database from one type of platform toanother, use the db2move utility described in theData Movement Utilities Guide and Reference.


SQL2571N Automatic incremental restore isunable to proceed. Reason code:reason-code.

Explanation: An error was encountered duringthe automatic incremental restore process. Theutility was unable to complete as intended. Theutility stops processing. This error is returnedafter the initial definitions have been restoredand the processing of the required incrementalrestore set cannot be completed successfully,corresponding to the following reason codes:

1 The backup image corresponding to thespecified timestamp could not be foundin the database history.

2 An error occurred trying to determinewhich table spaces to restore.

3 A required backup image could not befound in the database history.

User Response: Issue a RESTOREINCREMENTAL ABORT command to cleanupany resources that may have been created duringprocessing. Perform a manual incremental restoreto restore the database from this backup image.

SQL2572N Attempted an incremental restoreof an out of order image. Therestore of tablespacetablespace-name encountered anerror because the backup imagewith timestamp timestamp-valuemust be restored before the imagethat was just attempted.

Explanation: When restoring images producedwith an incremental backup strategy, restore theimages in the following order:

1. Restore the final image first to indicate toDB2 the increment to which you want torestore the database.

2. Restore the full database or tablespace imagewhich precedes the set of incremental images.

3. Restore the set of incremental and deltaimages in the chronological order in whichthey were produced.

4. Restore the final image for a second time.

Each tablespace in the backup image is aware ofthe backup image that must be restored beforethe backup image that failed can be successfullyrestored. You must restore the image with thetimestamp reported in this message before youcan successfully restore the image that invokedthis message. There might be additional imagesto restore before the indicated image, but thiswas the first tablespace to encounter an error.

User Response: Ensure the order of the set ofincremental backup images is correct andcontinue the incremental restore process.

SQL2573N An incremental backup imagemust be restored as part of anincremental RESTORE operation.

Explanation: A RESTORE operation wasattempted using an incremental backup image.An incremental backup cannot be restored on itsown; it can be restored only as part of anincremental RESTORE operation.


User Response: To restore this backup image,reissue the RESTORE command using theINCREMENTAL modifier. To perform anon-incremental RESTORE operation, specify anon-incremental backup image.

SQL2574N A backup image restored as partof an incremental RESTOREoperation cannot be newer thanthe target image.

Explanation: The target image is the first imageto be restored as part of an incrementalRESTORE operation. This image contains thetablespace definitions and other controlstructures for the database that is being restored.The RESTORE utility cannot restore an imagethat is newer than the target image during anincremental RESTORE operation, because itcould corrupt the database.

The incremental RESTORE operation failedbecause it attempted to restore a backup imagewith a timestamp that is more recent than thetimestamp of the target image.



User Response: Reissue the command,specifying a backup image with a timestamp thatis older than the timestamp of the target image.

SQL2575N The timestamp of the specifiedincremental backup image is olderthan the timestamp of the lastimage that was restored fortablespace tablespace-number. Thelast backup image has atimestamp of timestamp.

Explanation: To perform an incrementalRESTORE operation, the backup images must berestored in chronological order of oldest tonewest for each tablespace. An incrementalRESTORE operation specified a backup imagewith a timestamp older than the timestamp ofthe previous image that was restored for thespecified tablespace.


User Response: Reissue the command,specifying a backup image with a timestamp thatis newer than the timestamp of the last imagethat was restored for the tablespace.

SQL2576N Tablespace tablespace-name is beingrestored as part of an incrementalRESTORE operation, but theRESTORE command did notspecify the INCREMENTALclause.

Explanation: To incrementally restore atablespace, each RESTORE command mustspecify the INCREMENTAL clause.


User Response: Reissue the RESTOREcommand and include the INCREMENTALclause.

SQL2600 - SQL2699

SQL2600W The input parameter pointer tothe authorization block is invalidor the block’s size is incorrect.

Explanation: The pointer to the authorizationstructure parameter is NULL, the pointer to theauthorization structure points to an area that issmaller than the length indicated in the structurelength field, or the authorization structure lengthfield is not set to the correct value.


User Response: Correct the value of the inputparameter and resubmit the command.

SQL2650N An invalid parameterparameter_name was passed to theAPI-name read log API. ReasonCode = reason-code.

Explanation: An invalid parameter was passedto a read log API. The possible reason codes areas follows:

01 Invalid action specified.

02 The starting log sequence number isgreater than the current database activelog sequence number.

03 The log sequence number rangebounded by the starting and ending logsequence numbers is not large enoughto span a log record.

04 The starting log sequence number doesnot represent the start of an actual logrecord.

05 The starting log sequence number’slocation could not be determined.

06 The ending log sequence number is lessthan or equal to the starting logsequence number.

07 The buffer is not valid for the indicatedsize.

08 The buffer is not of sufficient size tostore a log record.

09 A pointer is not valid.


10 The filter option is not valid.

11 The logfile path is not valid.

12 The overflow logfile path is not valid.

13 The retrieve logs option is not valid.

14 The specified number of bytes formemory allocation is too small.

User Response: For reason code 01, ensure thatthe action is either DB2READLOG_QUERY,DB2READLOG_READ,DB2READLOG_READ_SINGLE.

For reason code 02, reduce the value of thestarting log sequence number.

For reason code 03, ensure that the ending logsequence number is sufficiently larger than thestarting log sequence number.

For reason code 04, ensure that the starting logsequence number is either the initial logsequence number or the next start log sequencenumber returned in the read log informationstructure.

For reason code 05, ensure that the starting logsequence number resides in a log extent in thedatabase log file path.

For reason code 06, ensure that the ending logsequence number is greater than the starting logsequence number.

For reason code 07, ensure that the buffer hasbeen allocated and is of the size indicated by thelog buffer size parameter.

For reason code 08, increase the size of theallocated buffer.

For reason code 09, ensure that memory has beencorrectly allocated and the pointers properlyinitialized.

For reason code 10, ensure that the filter optionis either DB2READLOG_FILTER_OFF orDB2READLOG_FILTER_ON.

For reason code 11, ensure that the logfile pathfield is defined and points to a valid directory.

For reason code 12, ensure that the overflow

logfile path field is defined and points to a validdirectory.

For reason code 13, ensure that the retrieveoption is eitherDB2READLOGNOCONN_RETRIEVE_OFF,DB2READLOGNOCONN_RETRIEVE_LOGPATH,orDB2READLOGNOCONNRETRIEVE_OVERFLOW.

For reason code 14, increase the amount of bytesthat may be allocated internally.

SQL2651N The log records associated withthe database can not beasynchronously read.

Explanation: The asynchronous read log APIwas used against a connected database whichdoes not have LOG RETAIN or USER EXITS ON.Only databases which are forward recoverablemay have their associated logs read.

User Response: Update the databaseconfiguration for the database, identified to theasynchronous read log API, turning LOGRETAIN and/or USER EXITS ON.

SQL2652N Insufficient memory to run theasynchronous log reader.

Explanation: The allocation of the internalbuffers used by the asynchronous read log APIhas failed.

User Response: Increase the amount ofavailable memory available to the process(increase real or virtual memory or removeunnecessary background processes) or decreasethe log sequence number range provided to theasynchronous read log API.

SQL2653W A Restore, Forward or CrashRecovery may have reused logsequence number ranges. Reasoncode reason-code.

Explanation: A Restore, Forward or CrashRecovery may have reused log sequence numberranges. The possible reason codes are as follows:

v 01 - Restore has taken place.


v 02 - Forward Recovery (ROLLFORWARD) hastaken place.

v 03 - Crash Recovery has taken place.


SQL2654W The database log has beenasynchronously read to the end ofthe current active log.

Explanation: All log records in the databaseactive log have been read by the asynchronouslog reader.


SQL2655N The Asynchronous Log Readerencountered log file name which isnot associated with the databasebeing asynchronously read.

Explanation: The Asynchronous Log Readerattempted to read log records from the specifiedlog file. The specified log file is not associatedwith the database being asynchronously read.

User Response: Remove this log file from thedatabase log directory. Move the correct log fileinto the database log directory and resubmit thecall to the Asynchronous Read Log API.

SQL2656N The Asynchronous Log Readerhas encountered log file namewhich cannot be read.

Explanation: The Asynchronous Log Readerattempted to read log records from the specified

log file. The specified log file has been corruptedand cannot be read.

User Response: Increase the start read logsequence and resubmit the call to theAsynchronous Read Log API to start readingafter the specified log file.

SQL2657N The Asynchronous Log Readerrequires log file name which doesnot currently reside in thedatabase log directory.

Explanation: The Asynchronous Log Readerrequires log records from the specified log file.The specified log file does not currently reside inthe database log directory.

User Response: Move the specified log file intothe database log directory of the database beingasynchronously read. If the database log pathwas changed, the log file might be found in theold log path. Resubmit the call to theAsynchronous Read Log API.

SQL2700 - SQL2799

SQL2701N Invalid command line option forprogname. Reason code: reason-code

Explanation: Command line option for the datasplitting utility is not valid. Valid options are:

v -c ″Configuration file name″

v -d ″Distribution file name″

v -i ″Input file name″

v -o ″Output file prefix″

v -h Usage message


1 There is an option not started with ’-’sign.

2 Each option except ’h’ (or ’H’) must befollowed by an argument.

3 There is an invalid option.

4 The argument of an option is too long(maximum 80 characters).


SQL2702N Failed to open the configurationfile config-file.

Explanation: The utility cannot read theconfiguration file config-file.

User Response: Please ensure the configurationfile exists and is readable.

SQL2703N Failed to open the log file log-file.

Explanation: The utility cannot open the log filelog-file for writing or appending.

User Response: Please ensure the log file existsand is writable.

SQL2704N Failed to open the input data fileinput-data-file.

Explanation: The utility cannot read the inputdata file input-data-file.

User Response: Please ensure the input data fileexists and is readable.

SQL2705N Failed to open the inputpartitioning map file in-map-file.

Explanation: The utility cannot read the inputpartitioning map file in-map-file.

User Response: Please ensure the inputpartitioning map file exists and is readable.

SQL2706N Failed to open the outputpartitioning map file out-map-file.

Explanation: The utility cannot open the outputpartitioning map file out-map-file for writing.

User Response: Please ensure the outputpartitioning map file is writable.

SQL2707N Failed to open the distributionfile dist-file.

Explanation: The utility cannot open thedistribution file dist-file for writing.

User Response: Please ensure the distributionfile is writable.

SQL2708N Failed to open the output data fileout-data-file.

Explanation: The utility cannot open the outputdata file out-data-file for writing.

User Response: Please ensure the output datafile is writable.

SQL2709N Syntax error at line line of theconfiguration file.

Explanation: There is a syntax error in thespecification of a keyword and its argument.

User Response: A keyword and its argumentmust be delimited by an ’=’ sign.

SQL2710N Invalid keyword at line line of theconfiguration file.

Explanation: There is an undefined keyword inthe configuration file.

User Response: Valid keywords (caseinsensitive) are:

v DESCRIPTION, CDELIMITER, SDELIMITER,NODES, TRACE, MSG_LEVEL, RUNTYPE,OUTPUTNODES, NODES, OUTPUTNODES,OUTPUTTYPE, PARTITION, MAPFILI,INFILE, MAPFILO, OUTFILE, DISTFILE,LOGFILE, NEWLINE, HEADER, FILETYPE

SQL2711N Invalid column delimiter(CDELIMITER) at line line of theconfiguration file.

Explanation: The column delimiter(CDELIMITER) specified in the configuration fileis not valid.

User Response: Make sure the column delimiter(CDELIMITER) is a single byte character.

SQL2712N Invalid string delimiter(SDELIMITER) at line line of theconfiguration file.

Explanation: The string delimiter(SDELIMITER) specified in the configuration fileis not valid.


User Response: The string delimiter(SDELIMITER) cannot be a period.

SQL2713N Invalid run type (RUNTYPE) atline line of the configuration file.

Explanation: The value for run type(RUNTYPE) specified in the configuration file isnot valid.

User Response: Valid run type (RUNTYPE) canbe either PARTITION or ANALYZE (caseinsensitive).

SQL2714N Invalid message level(MSG_LEVEL) at line line of theconfiguration file.

Explanation: The value for message level(MSG_LEVEL) specified in the configuration fileis not valid.

User Response: Valid message level(MSG_LEVEL) can be either CHECK orNOCHECK (case insensitive).

SQL2715N Invalid check level(CHECK_LEVEL) at line line ofthe configuration file.

Explanation: The value for check level(CHECK_LEVEL) specified in the configurationfile is not valid.

User Response: Valid check level(CHECK_LEVEL) can be either CHECK orNOCHECK (case insensitive).

SQL2716N Invalid record length (RECLEN)reclen at line line of theconfiguration file.

Explanation: The value for record length(RECLEN) reclen specified in the configurationfile is not valid.

User Response: The record length (RECLEN)must be between 1 and 32767.

SQL2717N Invalid node specification(NODES) at line line of theconfiguration file. Reason codereason-code.

Explanation: The node specification (NODES) inthe configuration file is not valid.


1 NODES has already been defined.

2 The format is not valid. A validexample: NODES=(0,30,2,3,10-15,57)

3 Each entry must be numeric databetween 0 and 999.

4 Range specification must be from alower number to a higher number.

SQL2718N Invalid output node specification(OUTPUTNODES) at line line ofthe configuration file. Reasoncode reason-code.

Explanation: The output node specification(OUTPUTNODES) in the configuration file is notvalid.


1 OUTPUTNODES has already beendefined.

2 The format is not valid. A validexample: OUTPUTNODES=(0,30,2,3,10-15,57)

3 Each entry must be numeric databetween 0 and 999.

4 Range specification must be from alower number to a higher number.

SQL2719N Invalid output type(OUTPUTTYPE) at line line of theconfiguration file.

Explanation: The output type (OUTPUTTYPE)in the configuration file is not valid.

User Response: Valid output types(OUTPUTTYPE) are W (write) or S (stdin), caseinsensitive.


SQL2720N Number of partition keysexceeded the maximum ″256″.This error was detected at line lineof the configuration file.

Explanation: The number of partitioning keysdefined cannot exceed the maximum limit: 256.

User Response: Remove one or morepartitioning keys defined in the configurationfile.

SQL2721N Invalid partitioning keyspecification (PARTITION) at lineline of the configuration file.Reason code reason-code.

Explanation: A partitioning key specification(PARTITION) in the configuration file is notvalid. Valid format:

PARTITION=<key name>,<position>,<offset>,<len>,<nullable>,<datatype>

If a delimited-data file, <position> must bedefined; otherwise, <offset> and <len> must bedefined.


1 Fields must be delimited by the ’,’character.

2 <position>, <offset> and <len> must bepositive integers.

3 <nullable> must take a value from{N,NN,NNWD}.

4 Valid <data type> includes: SMALLINT,INTEGER, CHARACTER, VARCHAR,FOR_BIT_CHAR, FOR_BIT_VARCHAR,FLOAT (for binary numerics only),DOUBLE (for binary numerics only),DATE, TIME, TIMESTAMP,DECIMAL(x,y).

5 For DECIMAL data type, precision (x)and scale (y) must be specified and theymust be positive integers.

6 For CHARACTER or VARCHAR datatype, <len> must be specified.

SQL2722N Invalid log file specification(LOGFILE) at line line of theconfiguration file.

Explanation: The log file specification(LOGFILE) in the configuration file is not valid.

User Response: The log file specification(LOGFILE) must be in one of the following twoformats:

v LOGFILE=<log file name>,<log type>

v LOGFILE=<log file name>

<log type> can only be W (write) or A (append),case insensitive.

SQL2723N Invalid trace specification(TRACE) at line line of theconfiguration file.

Explanation: The trace specification (TRACE) inthe configuration file is not valid.

User Response: The trace specification (TRACE)must be a positive integer between 0 and 65536(exclusive).

SQL2724N Invalid node list specification.

Explanation: The node list specification is notvalid.

User Response: One and only one of the twoparameters: NODES and MAPFILI (inputpartition map) must be specified in theconfiguration file.

SQL2725N Filename for output partition mapwas not specified.

Explanation: If run type is ANALYZE, afilename for the output partition map must bedefined.

User Response: Specify a filename for theoutput partition map.


SQL2726N There is no partitioning keydefined.

Explanation: At least one partitioning key mustbe defined.

User Response: Specify one or morepartitioning keys.

SQL2727N Partition key key-name exceeds therecord length reclen.

Explanation: For non-delimited data, startingposition for a key must be less than the recordlength.

User Response: Make sure starting position fora key is less than the record length.

SQL2728N Output node out-node is notdefined in the node list.

Explanation: Output node list must be a subsetof the node list, which is derived from NODESor the input partition map file.

User Response: Make sure all output nodes aredefined in the node list.

SQL2729N Invalid input partition map.

Explanation: There is at least one error in theinput partition map file.

User Response: The input partition map mustcontain no less than 4096 data entries, and eachdata entry must be a number between 0 and 999.

SQL2730N Error while writing header tooutput data file out-data-file.

Explanation: An I/O error occurred whilewriting the header to an output data file.

User Response: Check your operating systemdocumentation for file I/O errors and ensure thatthere is sufficient space on the output device.

SQL2731N Error while reading from inputdata file filename.

Explanation: An I/O error occurred whilereading from input data file.

User Response: Check your operating systemdocumentation for file I/O errors.

SQL2732N Line line of the input data filecontains binary data.

Explanation: Binary data is not permitted onthe host versions of this utility program.

User Response: Check your input data file.

SQL2733N Run type (RUNTYPE) was notdefined in the configuration file.

Explanation: The run type (RUNTYPE) must bedefined as either PARTITION or ANALYZE.

User Response: Please specify run type(RUNTYPE) in the configuration file.

SQL2734N Invalid specification for parameter32KLIMIT at line line of theconfiguration file.

Explanation: The specification for parameter32KLIMIT in the configuration file is not valid.

User Response: Parameter 32KLIMIT can beeither YES or NO, case insensitive.

SQL2735W The record rec-no of the input datafile was discarded because it wasan empty record.

Explanation: The record rec-no of the input datais discarded because it contains nothing butspaces.

User Response: Check record rec-no in the inputdata file.


SQL2736N sqlugrpi_api returned an errorwhen processing record at line lineof the input data file.

Explanation: Partitioning key fields containinvalid data.

User Response: Check the input data file at lineline.

SQL2737N Failed to write output data file foroutput node out-node whenprocessing record at line line ofinput data file.

Explanation: An I/O error occurred whilewriting a record to the output data file for nodeout-node.

User Response: Check your operating systemdocumentation for file I/O errors and ensure thatthere is sufficient space on the output device.

SQL2738W Record at line line of input datafile has been truncated whenwriting to the output data file fornode out-node. Expected writinglength is reclen while actualwriting length is real-len.

Explanation: Expected writing length (RECLEN)does not match the actual writing length.

User Response: Adjust record length valuedefined in the configuration file.

SQL2739N The record length was notspecified for a binary numericaldata file.

Explanation: If a binary numerical input datafile, the record length has to be defined.

User Response: Please specify the record lengthin your configuration file.

SQL2740N Float data type is not allowed in anon-binary input data file.

Explanation: Float data type is only supportedwhen the file type is BIN (binary).

User Response: Make sure data types and thetype of input data file match.

SQL2741N Invalid file type specification atline line of the configuration file.

Explanation: The file type specification(FILETYPE) in the configuration file is not valid.

User Response: Valid values for the file typeparameter are as follows:

v ASC (positional ascii data file)

v DEL (delimited ascii data file)

v BIN (ASC file with all numeric data in binaryformat)

v PACK (ASC file with all decimal data inpacked decimal format)

v IMPLIEDDECIMAL (DEL file with decimaldata in implied decimal format).

All the values are case insensitive.

SQL2742N The length of partition keypartition-key does not match itsprecision.

Explanation: In a binary input data file, thelength of a partition key with decimal data typemust conform to the equation:LENGTH=(PRECISION+2)/2 (integer division),because it is a packed decimal.

User Response: Match the length of adecimal-typed partition key with its precision ifthe input data file is a binary data file.

SQL2743N The length of partition keypartition-key does not match itsdata type.

Explanation: In a binary input data file, thelength of a partition key with integer, smallinteger, float, and double data type must be apredefined constant, i.e. 4 for integer, 2 for smallinteger, 4 for float, and 8 for double.

User Response: Check partition key definitionsin the configuration file.


SQL2744N Illegal file name specification forfile at line line of the configurationfile.

Explanation: The maximum length for a filename is 80 bytes.

User Response: Check the configuration file.

SQL2745N Invalid NEWLINE flag at line lineof the configuration file.

Explanation: The NEWLINE flag must be eitherYES or NO, and if not given, it is NO.

User Response: Check the specification ofNEWLINE flag in the configuration file.

SQL2746N An incomplete record was foundwhile reading record record-numberfrom the input data file.

Explanation: If a fixed-length positional ASCfile or a binary numerical data file, each recordhas to be exactly the same length as the value ofthe RECLEN parameter in the configuration file.

User Response: Make sure the input data file iscomplete.

SQL2747N A record was too long whilereading record rec-no from theinput data file.

Explanation: For a positional ASC input datafile or a delimited data file with parameter32KLIMIT on, the maximum record length cannot exceed the 32k (bytes) limit.

User Response: Check your input data file andmake sure the record length is less than 32kbytes.

SQL2748N Record record-number has a lengthof length bytes, which is too shortto hold the partitioning key key.

Explanation: For a positional ASC input datafile or a binary numerical data file, each recordhas to be long enough to hold all partitioningkeys.

User Response: Check the record length of yourinput data file.

SQL2749N Partitioning key key-no of recordrec-no was not in the first 32kbytes of the record.

Explanation: If a record is greater than 32kbytes long in a delimited data file, allpartitioning keys of each record have to bewithin the first 32k bytes of the record.


SQL2750N The length of line line-number inthe configuration was more than255 bytes.

Explanation: The maximum length of a line inthe configuration file must be less than 255 bytes.

User Response: Check your configuration fileand make sure all lines are less than 255 bytes.

SQL2751N The actual length actual-reclen ofrecord rec-no did not match theexpected length exp-reclen.

Explanation: If new line checking is requiredfor a fixed length ASC data file (NEWLINEparameter is YES and RECLEN parameter is notzero), the actual length of each record has tomatch the expected record.


SQL2752N Invalid codepage specificationcodepage at line line of theconfiguration file.

Explanation: The codepage specification is notvalid. It must be a positive integer.

User Response: Correct the codepagespecification in the configuration file.


SQL2753N Failed to get the territory codeand codepage for the application.Return code from functionfunction-name is rc.

Explanation: The program failed to get theterritory code and codepage of its environment.

User Response: Check with your databasesystem administrator.

SQL2754N Codepage source-cp cannot beconverted to codepage target-cp.

Explanation: The database does not supportcodepage conversion between those twocodepages.

User Response: Please ensure your data is in aconvertible codepage.

SQL2755N Decimal data can not be in bothIMPLIEDDECIMAL andPACKEDDECIMAL format.

Explanation: Valid format of decimal data isSQL_PACKEDDECIMAL_FORMAT,SQL_CHARSTRING_FORMAT, orSQL_IMPLIEDDECIMAL_FORMAT, mutuallyexclusive.

User Response: Verify the format of yourdecimal data, correct the format value, andresubmit the command.

SQL2761N Only one of table name ornodegroup can be specified.

Explanation: Specify either the table name orthe nodegroup name, but not both.

User Response: Check your command lineoptions.

SQL2762N The utility failed to find thedatabase installation path.

Explanation: The utility needs to know wherethe database manager is installed, then it canfind its bind file.

User Response: Make sure your databasemanager is properly installed.

SQL2763N The table tbl-name was not found.

Explanation: The table tbl-name cannot belocated in sysibm.systables.

User Response: Make sure the table exists inthe database.

SQL2764N The nodegroup nodegroup was notfound.

Explanation: The nodegroup nodegroup cannotbe located in sysibm.sysnodegroupdef.

User Response: Make sure the nodegroup existsin the database.

SQL2765W The utility failed to open outputpartition map file out-map-file.

Explanation: The utility cannot open the outputpartition map file for writing. It will write theoutput to stdout.

User Response: Check your file accesspermissions.

SQL2766N The partition map is not of thecorrect size map-size.

Explanation: The size of the partition map isnot correct. Data is corrupted in the database.

User Response: Contact the DatabaseAdministrator to resolve the problem.

SQL2767N A command line option is notvalid.

Explanation: There is an invalid command lineoption.

User Response: Make sure to specify the correctcommand line options.

SQL2800 - SQL2899


SQL2800N CREATE, DROP, or CHANGENODE failed. Reason codereason-code.

Explanation: The utility failed to add, drop, orchange the node because the input parametersspecified are invalid as indicated by thefollowing reason codes:

v (1) The node number is not specified

v (2) The TCP/IP host name is not specified

v (3) The computer name is not specified

v (4) The node number is invalid.

v (5) The port number is invalid.

v (6) The TCP/IP host name is invalid.

v (7) The port value is not defined for yourinstance in the services file.

v (8) The port value is not in the valid rangedefined for your instance in the services file.

v (9) The node number is not unique.

v (10) The host name/port couple is not unique.

v (11) The host name value has nocorresponding port 0.


v (1) Ensure that the node number is specified

v (2) Ensure that the TCP/IP host name isspecified

v (3) Ensure that the computer name is specified

v (4) Ensure that the node number is between 0and 999.

v (5) Ensure that the port number is between 0and 999.

v (6) Ensure that the host name specified is bothdefined on the system and is operational

v (7) Ensure that the TCP/IP services on yoursystem contains an entry for your instance

v (8) Ensure that you only use port values thatare specified in the services file on yoursystem

v (9) Ensure that the node number specified isunique.

v (10) Ensure that the new host name/port isnot already defined in the db2nodes.cfg file.

v (11) Ensure that the port value 0 has beendefined for host name specified.

SQL2801N The syntax of the DB2NCRTcommand is incorrect.

Explanation: The DB2NCRT utility creates anew node in a partitioned database system.

DB2NCRT /n:node/u:username,password[/i:instance][/h:host][/m:machine][/p:port][/o:instance owning

machine][/g:netname]

The command arguments are:

v /n Specify the node number

v /u to specify the account name and passwordfor the DB2 service.

The command options are:

v /i Specify the instance if different from thedefault/current instance

v /h Specify the TCP/IP host name if the hostname is not the machine default TCP/IP hostname

v /m Specify the workstation name if the nodeis created on a remote machine

v /p Specify the logical port number if this isnot the first node on the machine

v /o Specify the computer name of the instanceowning machine when creating the first nodeon a machine.

v /g Specify the network name or IP Address.

User Response: Enter the command again usingvalid parameters.

SQL2802N The syntax of the DB2NCHGcommand is incorrect.

Explanation: The DB2NCHG utility changes orupdates node configuration for a given node in apartitioned database system.


DB2NCHG /n:node[/h:host][/m:machine][/p:port][/i:instance][/u:username,

password][/g:netname]


v /h Change the TCP/IP host name

v /m Change the workstation name

v /p Change the logical port number


v /u Change the Logon Account name andpassword

v /g Specify the network name or IP Address

User Response: Issue the DB2NCHG commandwith one of the valid command options.

SQL2803N The syntax of the DB2NDROPcommand is incorrect.

Explanation: The DB2NDROP utility drops anode from a partitioned system.

DB2NDROP /n:node[/i:instance]



User Response: Issue the DB2NDROPcommand with one of the valid commandoptions.

SQL2804N The syntax of the DB2NLISTcommand is incorrect.

Explanation: The DB2NLIST utility list allnodes in a partitioned system.

DB2NLIST [/i:instance][/s]



v /s Display node status

User Response: Issue the DB2NLIST commandwith one of the valid command options.

SQL2805N A service error has occurred.Reason code reason-code.

Explanation: A service error has occurredduring CREATE, DROP or ADD NODEprocessing as indicated by the following reasoncodes:

v (1) Unable to register the service

v (2) Unable to set the required User RightsPolicy

v (3) Unable to set the Logon Account for theservice

v (4) Unable to delete the service


v (1) If the workstation name is specified duringDB2NCRT, ensure that the workstation nameis correct.

v (2) Ensure that the user name specified isvalid.

v (3) Ensure that the user name and thepassword specified are valid.

v (4) If the node resides on another machine,ensure that the machine is running.

If the problem persists, contact IBM Service.

SQL2806N Node node not found for instanceinstance.

Explanation: DB2NDROP failed because thenode does not exist.

User Response: Ensure the node number iscorrect and reissue the command.

SQL2807N Node node already exists forinstance instance.

Explanation: DB2NCRT failed because the nodealready exists.

User Response: Ensure the node number is


correct and reissue the command.

SQL2808W Node node for instance instance hasbeen deleted.

Explanation: The DB2NDROP processing hascompleted successfully.

User Response: No further action is required.

SQL2809W Node: node added to instance:instance {Host: host-name Machine:machine-name Port: port-num}

Explanation: The DB2NCRT processing hascompleted successfully.


SQL2810W Node: node changed in instance:instance {Host: host-name Machine:machine-name Port: port-num}

Explanation: The DB2NCHG processing hascompleted successfully.


SQL2811N The command is invalid becausethe instance is not a partitioneddatabase instance.

Explanation: The command is only valid if theinstance is a partitioned database instance.

User Response: Ensure that the specifiedinstance name is valid. If the instance name isnot specified on the command line, ensure thatthe DB2INSTANCE environment is set to a validpartitioned database instance.

SQL2812N An invalid argument was enteredfor the db2drvmp command.

Explanation: Usage:

db2drvmp add node_numberfrom_drive to_drive

drop node_numberfrom_drive

query [node_number]

[from_drive]reconcile [node_number]

[from_drive]

Valid arguments for this command are:

add assign a new database drive map.

drop remove an existing database drive map.

query query a database map.

reconcilerepair a database map drive when theregistry contents are damaged.

node_numberthe node number. The parameter isrequired for add and drop operations.

from_drivethe drive letter to map from. Thisparameter is required for add and dropoperations.

to_driveto drive letter to map to. This parameteris required only for add operation. It isnot applicable for any other operations.

User Response: Enter the command again usingvalid arguments.

SQL2813I The drive mapping from drivedrive-1 to drive drive-2 was addedfor node node.

Explanation: The drive mapping was addedsuccessfully.


SQL2814I The drive mapping from drivedrive was deleted for node node.

Explanation: The drive mapping was deletedsuccessfully.



SQL2815I The drive mapping for node nodeis: drive-1 - drive-2.

Explanation: Informational message.

User Response: No action necessary

SQL3000 - SQL3099

SQL3001C An I/O error (reason = reason)occurred while opening theoutput file.

Explanation: A system I/O error occurred whileopening the output file.

The command cannot be processed. No data isprocessed.

User Response: For IMPORT/LOAD, verifythat the output file exists. For EXPORT, verifythat the output media has enough free space.Resubmit the command with a valid output filename, including the correct path. Look in themessage file for additional information.

SQL3002C An I/O error occurred whilewriting to the output data file.

Explanation: A system I/O error occurred whilewriting to the output data file. The output maybe incomplete or the disk may be full.


User Response: If the output data file isincomplete, erase it and resubmit the command.

SQL3003C An I/O error occurred whileclosing the output data file.

Explanation: A system I/O error occurred whileclosing the output data file.

The file is not closed.

User Response: If the output data file isincomplete, erase it and resubmit the command.

SQL3004N The filetype parameter is notvalid.

Explanation: The filetype parameter must beDEL, ASC, IXF, WSF, or DB2CS for thecommand.

The filetype parameter must be DEL, IXF, or WSFfor the EXPORT command.

The filetype parameter must be ASC, DEL, IXF, orDB2CS for the LOAD command.

IXF files can not be used to load into a tabledefined on a multinode nodegroup.


User Response: Resubmit the command with avalid filetype parameter.

SQL3005N Processing was interrupted.

Explanation: An interrupt was received duringprocessing. The user may have pressed theinterrupt key sequence.

The utility stops processing. Any databaseupdates not committed are rolled back.

User Response: Resubmit the command. Ifdoing an import, see Command Reference forinformation on how to use commitcount andrestartcount parameters. If doing a load, seeCommand Reference for information on how torestart the load.

SQL3006C An I/O error occurred whileopening the message file.

Explanation: A system I/O error occurred whileopening the message file. This error can refer toa problem on either the client or the server.



User Response: Resubmit the command with avalid message file name, including the correctpath.

SQL3007C An I/O error occurred whilewriting to the message file.

Explanation: A system I/O error occurred whilewriting to the message file.

Processing may not have finished.

User Response: If the message file isincomplete, erase it and resubmit the command.

SQL3008N The utility encountered an errorerror while connecting to thedatabase.

Explanation: The IMPORT or EXPORT utilitycould not connect to the database.

No data is imported or exported.


SQL3009N The Action String parameter isnot valid.

Explanation: The Action String (e.g. ″REPLACEinto ...″) parameter in the command is not valid.The Action String pointer may be incorrect. Thestructure that the Action String points to may beincorrect. The Action String structure may containcharacters that are not valid.


User Response: Verify the Action String pointerand the structure it points to. Resubmit thecommand with a valid Action String.

SQL3010N The METHOD parameter is notvalid.

Explanation: The METHOD parameter in thecommand is not valid. The METHOD pointermay be incorrect. The structure that theMETHOD points to may be incorrect. TheMETHOD structure may contain characters thatare not valid.


User Response: Examine the METHOD pointerand the structure it points to. Resubmit thiscommand with a valid METHOD.

SQL3011C There is not enough storage toprocess the command.

Explanation: A memory allocation erroroccurred. Not enough memory is available toprocess the command, or there was an errorfreeing storage.





v Increase the util_heap_sz for the database.

v Decrease the size of buffers to use for theLOAD.

v The util_heap_sz is shared by the LOAD,BACKUP and RESTORE utilities, so havefewer concurrent instances of these utilitiesrunning.

SQL3012C A system error occurred.

Explanation: An operating system erroroccurred.


User Response: Check your message file,correct the problem and resubmit the command.

SQL3013N The length of the filetmod is outof the acceptable range. It shouldbe greater than or equal to zeroand less than or equal to 8000.

Explanation: The filetmod specified is outsidethe acceptable range (greater than or equal tozero and less than or equal to 8000).


User Response: Examine the filetmod pointerand the structure it points to. Resubmit the


command with a valid filetmod.

SQL3014C An I/O error occurred whileclosing the message file.

Explanation: A system I/O error occurred whileclosing the message file.

The message file is not closed.

User Response: If the message file isincomplete, resubmit the command.

SQL3015N An SQL error sqlcode occurredduring processing.

Explanation: An SQL error occurred during theutility call.



SQL3016N An unexpected keyword keywordwas found in the filetmodparameter for the filetype.

Explanation: A keyword that does not apply tothe filetype for the utility was found in thefiletype modifier (the filetmod parameter or thephrase following MODIFIED BY in a CLPcommand).


User Response: Remove the filetype modifier orspecify at least one valid keyword in the filetypemodifier. See the Command Reference for moreinformation on filetype modifiers.

SQL3017N A delimiter is not valid or is usedmore than once.

Explanation: For Delimited ASCII (DEL) files,one of two errors occurred:

v The character specified for either the columndelimiter, character string delimiter, or decimalpoint character is not valid.

v The same character is specified for more thanone of the preceding items.


User Response: Examine the specifieddelimiters for validity and uniqueness. Resubmitthe command with valid delimiter overrides.

SQL3018N The period was specified as acharacter string delimiter.

Explanation: For Delimited ASCII (DEL), theperiod cannot be specified as the character stringdelimiter.


User Response: Resubmit the command withvalid delimiter overrides.

SQL3019N No Action String parameter wasspecified in the command.

Explanation: No Action String (e.g. ″REPLACEinto ...″) parameter is specified for this utilitycall. This parameter is required.


User Response: Resubmit the command with anAction String parameter.

SQL3020N The user does not have theauthority to run the specifiedExport command.

Explanation: The user attempted to export datawithout the appropriate authorization (either theSYSADM or DBADM authority), or theCONTROL or SELECT privilege for each tableinvolved in the export.

The export action is not performed.

User Response: Request appropriateauthorization before exporting data from thetables.


SQL3021N The user does not have theauthority to run the specifiedImport command on table name.

Explanation: The user attempted to import datawithout the appropriate authorization for thespecified option and table.

Import using the INSERT option requires one ofthe following:

v SYSADM or DBADM authority

v CONTROL privilege on the table, view, orentire hierarchy

v INSERT and SELECT privilege on the table,view, or entire hierarchy.

Note: entire hierarchy refers to all subtables orobject views in the hierarchy.

Import to an existing table or view using theINSERT_UPDATE, REPLACE, or theREPLACE_CREATE option, requires one of thefollowing:


v CONTROL privilege on the table, view, orentire hierarchy.

Note: entire hierarchy refers to all subtables orobject views in the hierarchy.

Import to a table that does not exist, using theCREATE or REPLACE_CREATE option, requiresone of the following:


v CREATETAB authority on the database andone of:

– IMPLICIT_SCHEMA authority on thedatabase, if the schema name of the tabledoes not exist

– CREATEIN privilege on the schema, if theschema of the table exists

The import operation is not performed.

User Response: Ensure that the user has theauthorization to perform the import operation.

SQL3022N An SQL error sqlcode occurredwhile processing the SELECTstring in the Action Stringparameter.

Explanation: In IMPORT or EXPORT, duringprocessing of the SELECT string from the ActionString (e.g. ″REPLACE into ...″) structure, an SQLerror occurred.



SQL3023N The database name parameter isnot valid.

Explanation: The database name parameter isnot valid. See the SQLERRD[0] field in theSQLCA for more information.

The database name must contain 1 to 8characters and the characters must be from thedatabase manager base character set.


User Response: Resubmit the statement with avalid database name parameter.

SQL3024N An I/O error occurred whileopening the format file.

Explanation: A system I/O error occurred whileopening the format file. This error can refer to aproblem on either the client or the server.

A possible cause may be that the format file is inuse by another application.


User Response: Ensure that the format file isvalid, including the path, and that it is notcurrently in use by another application.

Resubmit the command. Look in the diagnosticslog file for additional information.


SQL3025N A parameter specifying a filenameor path is not valid.

Explanation: The parameter contains a path,directory, or file name that is not valid.

For IMPORT and EXPORT, verify the datafileparameter.

For LOAD, verify that each entry in theparameters of type sqlu_media_list: datafile shouldcontain valid filenames; lobpaths copytarget, andworkdirectory should contain valid paths on theserver including the final separator and a nullterminator.

The pointer to lobpaths, copytarget andworkdirectory must be valid or null.

The pointer to the targets in these structuresmust be valid.

Check that sessions and media_type are specifiedcorrectly.

Also, if the lobpaths parameter is specified, checkthat the media_type is the same as that specifiedfor the datafile structure.

If the filetype is IXF, the length of the file namemay be too long.


User Response: Resubmit the statement with avalid parameter.

SQL3026N The msgfile or tempfiles pathparameter is not valid.

Explanation: For IMPORT or EXPORT, themsgfile parameter contains a path, directory, orfile name that is not valid.

For LOAD, either the msgfile parameter containsa path, directory, or file name that is not valid onthe client, or the tempfiles path is not valid onthe server.

If the database to which the application isconnected is a remote database, the msgfile mustbe fully qualified. For a local database the utilitywill attempt to fully qualify the msgfile if it isnot already fully qualified. Also verify that thepointer to the msgfile is valid.


User Response: Resubmit the statement with avalid msgfile and/or tempfiles path parameter.

SQL3027N An I/O error occurred whilereading from the format file.

Explanation: A system I/O error occurred whilereading from the format file. This error can referto a problem on either the client or the server.


User Response: Verify that the format file isreadable.

SQL3028N The export method indicator isnot valid. It must be either ’N’ or’D’.

Explanation: The export method indicator mustbe either N for Names or D for Default.


User Response: Resubmit the statement with avalid method indicator.

SQL3029N No filetype parameter wasspecified.

Explanation: The filetype parameter was eithernot specified or null. The system does not knowwhich format to use for the data file.


User Response: Resubmit the statement with avalid filetype.

SQL3030C An I/O error (reason = reason)occurred while opening the inputfile.

Explanation: A system I/O error occurred whileopening the input file. This error can refer to aproblem on either the client or the server.

A possible cause may be that the input file is inuse by another application.



User Response: Ensure that the input file isvalid, including the path, and that it is notcurrently in use by another application.

Resubmit the command.

SQL3031C An I/O error occurred whilereading from the input file.

Explanation: A system I/O error occurred whilereading from the input file. This error can referto a problem on either the client or the server.


User Response: Verify that the input file isreadable.

SQL3032N The LOAD/IMPORT methodindicator is not valid for thespecified filetype. It must beeither ’N’, ’P’, or ’default’.

Explanation: For the IXF and WSF filetypes, theLOAD/IMPORT method indicator must be eitherN for Names, P for Positional, or D for Default.


User Response: Resubmit the command with avalid method indicator.

SQL3033N A keyword such as INSERT,REPLACE, CREATE,INSERT_UPDATE, orREPLACE_CREATE is missingfrom the target specification or itis misspelled.

Explanation: For IMPORT, the Action String (e.g.″REPLACE into ...″) parameter does not containthe keyword INSERT, REPLACE, CREATE,INSERT_UPDATE, or REPLACE_CREATE. ForLOAD, the Action String parameter does notcontain the keyword INSERT, REPLACE, orRESTART. The keyword must be followed by atleast one blank.


User Response: Resubmit the command with avalid Action String parameter.

SQL3034N The keyword INTO is missingfrom the target specification or itis misspelled.

Explanation: The INTO keyword is missing orspelled incorrectly. INTO must be followed by atleast one blank.


User Response: Resubmit the command with avalid Action String (e.g. ″REPLACE into ...″)parameter.

SQL3035N The tablename parameter in thetarget specification is not valid.

Explanation: For IMPORT, the tablename in theAction String (e.g. ″REPLACE into ...″) is notvalid. For LOAD, the tablename or the exceptiontablename in the Action String is not valid.


User Response: Resubmit the command with avalid tablename. Also ensure that all commandkeywords and parameters are entered in thecorrect order.

SQL3036N The tcolumn-list in the targetspecification does not have aclosed parenthesis.

Explanation: The tcolumn-list must be delimitedby parentheses. The list was not terminated bythe closed parenthesis.


User Response: Resubmit the statement with avalid, complete column list in the Action String(e.g. ″REPLACE into ...″) parameter.

SQL3037N An SQL error sqlcode occurredduring Import processing.

Explanation: An SQL error occurred duringprocessing of the Action String (e.g. ″REPLACEinto ...″) parameter.


User Response: Look at the SQLCODE(message number) in the message for more


information. Make changes and resubmit thecommand.

SQL3038N The Action String parametercontains unexpected characters.

Explanation: For IMPORT, there are charactersother than blanks after the closing parenthesis ofthe column list in the Action String (e.g.″REPLACE into ...″) parameter. For LOAD, thereare characters other than blanks after the closingparenthesis of the column list and/or theexception tablename in the Action Stringparameter.


User Response: Resubmit the command with avalid Action String parameter.

SQL3039W The memory available to LOADfor DATA BUFFER prohibits fullLOAD parallelism. Loadparallelism of value will be used.

Explanation: The LOAD utility attempted todetermine the optimal level of CPU parallelismfor SMP exploitation based on the systemconfiguration, or the user specified a value forLOAD parallelism when invoking the utility.However, one of the following limitation wasencountered:

1. The amount of free memory in the utilityheap prohibits this degree of parallelism.

2. The DATA BUFFER parameter was specifiedwith a value too small to allow for thespecified or available parallelism.

A lesser degree of parallelism, requiring lessmemory, will be used.

User Response:

1. Ignore this message, and the LOAD willcomplete normally using the smaller valuefor LOAD parallelism. However, Loadperformance may be less than optimal.

2. Specify a smaller value for LOAD parallelismwhen invoking the utility.

3. Increase the size of the utility heap.

4. Increase the size of the data buffer parameter,or leave the parameter blank and let theLOAD utility determine a default based onthe freespace in the utility heap.

SQL3040N Unable to use the lobpath/lobfileparameters as specified. Reasoncode: reason-code.

Explanation: The utility is unable to use thelobpath or lobfile parameters as specified for thereason given by reason-code. The codes are listedbelow.


1 The lobpath is not a validsqlu_media_list or the values providedare not valid. The media_type must beSQLU_LOCAL_MEDIA and allpathnames must be terminated with avalid path separator.

2 The lobfile is not a valid sqlu_media_listor the values provided are not valid.The media_type must beSQLU_LOCAL_MEDIA.

3 There are not enough lobpath namesprovided. For export, there is notenough space on the paths provided tohold all the lobs.

4 There are not enough lobfile namesprovided. For export, there are morelobs than the number of lobfile namesprovided multiplied bySQLU_MAX_SESSIONS.

5 The combination of a lobpath name andlobfile name would exceed themaximum size of a lobfile name (255bytes).

6 An error occurred while trying to accessthe file.

SQL3041N The date value specified is notsupported in Sybase.

Explanation: Sybase does not support datevalues prior to 1753.

User Response: Please give a valid date value


and issue the command again.

SQL3042N The LINKTYPE specified for aDATALINK column is invalid.

Explanation: The value specified for LINKTYPEfor a DATALINK column is invalid.

User Response: Check the LINKTYPE specified.Correct the value and resubmit the command.

SQL3043N The DATALINK SPECIFICATIONfor DATALINK column(s) isinvalid.

Explanation: The DATALINK SPECIFICATIONfor DATALINK column(s) is invalid for one ofthe following reasons:

v No value is specified forDL_URL_REPLACE_PREFIX.

v No value is specified forDL_URL_DEFAULT_PREFIX.

v No value is specified for DL_URL_SUFFIX.

v Contains keywords other thanDL_URL_REPLACE_PREFIX orDL_URL_DEFAULT_PREFIX orDL_URL_SUFFIX.

User Response: Correct the specification andresubmit the command.

SQL3044N The DATALINK SPECIFICATIONfor a DATALINK column hasduplicate prefix specification.

Explanation: The DATALINK SPECIFICATIONfor a DATALINK column has duplicatespecifications for DL_URL_REPLACE_PREFIX orDL_URL_DEFAULT_PREFIX.

User Response: Remove the duplicatespecification and resubmit the command.

SQL3045N A dcolumn position in theMETHOD parameter is less thanone or greater than the maximumnumber of columns (1024) in aDelimited ASCII file.

Explanation: The dcolumn position is less than 1or greater than the maximum number ofcolumns (1024) in a delimited file.


User Response: Resubmit the command withvalid dcolumn positions.

SQL3046N The number of columns in theMETHOD parameter is less thanone.

Explanation: For METHOD methods other thanDefault, the number of columns specified mustbe a positive number (greater than 0).


User Response: Resubmit the command with avalid number of columns in the METHODparameter.

SQL3047N The LOAD/IMPORT methodspecified in METHOD is notvalid for Delimited ASCII files. Itmust be either ’P’ or ’default’.

Explanation: The only valid LOAD/IMPORTmethods for Delimited ASCII files are P forPositions or D for Default.


User Response: Resubmit the command with avalid import method.

SQL3048N There are fewer columns specifiedfrom the input file than databasecolumns, but one of the databasecolumns is not nullable.

Explanation: When fewer columns are specifiedin the METHOD list than are specified for thetarget table, the values for the missing inputcolumns are loaded as nulls. Because thecolumns in the target table that correspond to


one or more of these input columns are notnullable, null cannot be inserted.

The file cannot be loaded.

User Response: Define a new table that has thesame number of columns as the input file or thathas nullable columns. Resubmit the command.

SQL3049N The data type type of the databasecolumn name is not compatiblewith this format file, but thedatabase column is not nullable.

Explanation: The database column type is notvalid for this format file. The database column isnot nullable so the utility is ended.

The utility stops processing. No data is loaded.

User Response: Redefine the database table sothe columns are compatible with the columnsloaded from the file.

SQL3050W Conversions on the data will bemade between the IXF file codepage and the application codepage.

Explanation: If an IMPORT of an IXF data filehas been issued and the code page of thecharacter data in the IXF file is different from thecode page of the application invoking the importoperation, a conversion will be made from thecode page of the data file to the code page of theapplication and the operation will continue.

If a LOAD of an IXF data file has been issuedand the code page of the character data in theIXF file is different from the database code page,a conversion will be made from the code page ofthe data file to the code page of the database andthe operation will continue.

User Response: If you do not want aconversion to be performed, invoke the utilityusing the FORCEIN option; otherwise no actionis required.

SQL3051W The data to be loaded intocolumn-name has been loaded, butconversion from the IXF file codepage to the application code pagehas not been performed.

Explanation: The data that was loaded into theCLOB or DBCLOB column is stored in a separatefile and no conversions have been performed onit.

To properly load the data, call the utility from anapplication that has the same code page as theIXF file.

User Response: This is a warning only.

SQL3053N There are more than 8191 rows tobe exported to a worksheetformatted file.

Explanation: The maximum number of rowsthat can be placed in a worksheet format file(WSF) is 8191.

The EXPORT utility stops processing afterplacing 8191 rows in the file.

User Response: To prevent this error, use aSELECT statement that results in fewer rows toexport, and resubmit the command.

SQL3054N The input file is not a validPC/IXF file. The file is too shortto contain a valid H record.

Explanation: The end of the file was reachedbefore the expected end of the first record. Thefile may not be a PC/IXF file.

The LOAD/IMPORT utility stops processing. Nodata is imported.

User Response: Verify that the input file iscorrect.

SQL3055N The input file is not a validPC/IXF file. The length field inthe first record cannot beconverted to a numeric value.

Explanation: The value in the length field of thefirst record is not the ASCII representation of a


number. The file may not be a PC/IXF file.



SQL3056N The input file is not a validPC/IXF file. The value in thelength field of the H record is toosmall.

Explanation: The value in the length field of theH record is not large enough for a valid Hrecord. The file may not be a PC/IXF file.



SQL3057N The input file is not a validPC/IXF file. The type field in thefirst record is not H.

Explanation: The type field in the first record isnot H. The first record is not a valid H record.The file may not be a PC/IXF file.



SQL3058N The identifier field in the Hrecord is not IXF.

Explanation: The identifier field in the H recorddoes not identify the file as a PC/IXF file.


User Response: Examine the identifier field inthe H record.

SQL3059N The version field in the H recordis not valid.

Explanation: The version field in the H recordcontains a value that is not valid.


User Response: Examine the version field in theH record.

SQL3060N The HCNT field in the H recordcannot be converted to a numericvalue or the value is out of range.

Explanation: The Heading-record-count field inthe H record is not an ASCII representation of anumber or is a number that is not valid for thisfield.


User Response: Examine the HCNT field in theH record.

SQL3061N The single-byte and/ordouble-byte code page field in theH record cannot be converted to anumeric value or the value is outof range.

Explanation: The single-byte and/ordouble-byte code page field in the H record isnot an ASCII representation of a number or is anumber that is not valid for this field.


User Response: Examine the single-byte anddouble-byte code page field in the H record,change them to appropriate values as specified inthe Application Development Guide and resubmitthe command.

SQL3062N The double-byte code page fieldin the H record cannot beconverted to a numeric value orthe value is out of range.

Explanation: The double-byte code page field inthe H record is not an ASCII representation of anumber or is a number that is not valid for thisfield.


User Response: Examine the double-byte codepage field in the H record, change it to anappropriate value as specified in the ApplicationDevelopment Guide and resubmit the command.


SQL3063N The single-byte code page valuevalue-1 in the H record is notcompatible with the single-bytecode page value value-2 for theapplication. The FORCEIN optionwas not specified.

Explanation: The single-byte code page value inthe H record is not compatible with theapplication code page value. When the FORCEINoption is not used, the data cannot be loadedunless conversion from value 1 to value 2 issupported.


User Response: To load this data, resubmit thecommand with the FORCEIN option.

SQL3064N The double-byte code page valuevalue-1 in the H record is notcompatible with the double-bytecode page value value-2 for theapplication. The FORCEIN optionwas not specified.

Explanation: The double-byte code page valuein the H record is not compatible with theapplication code page value. When the FORCEINoption is not used, the data cannot be loadedunless value 1 and value 2 are the same.


User Response: To load data where thedouble-byte code page values do not match,resubmit the command with the FORCEINoption.

SQL3065C The value for the application codepage cannot be determined.

Explanation: The system encountered an errorwhile determining the code page of theapplication.

The utility stops processing. No data is loaded orunloaded.

User Response: Contact your technical servicerepresentative.

SQL3066N While reading or looking for theT record, the end of the file wasreached.

Explanation: The end of the file was reachedwhile the system was looking for the T record orwhile it was reading the T record.


User Response: Examine the T record of theinput file. If the PC/IXF file was copied from onemedium to another, compare the copy with theoriginal or repeat the copy process.

SQL3067N The length field in the T recordcannot be converted to a numericvalue.

Explanation: The length field in the T record isnot an ASCII representation of a number.


User Response: Examine the length field in theT record.

SQL3068N The value in the length field ofthe T record is too small.

Explanation: The value in the length field of theT record is not large enough so the T record isnot valid.


User Response: Examine the length field in theT record.

SQL3069N The first non-A record followingthe H record is not a T record.

Explanation: After the H record, the first recordnot an A record is also not a T record. The Hrecord must be immediately followed by a Trecord but A records may exist before the Trecord.


User Response: Examine the records followingthe H record.


SQL3070N The length field in an A record isout of range.

Explanation: The length field in an A record is anumber that is not valid for this field.


User Response: Examine the length field in theA records.

SQL3071N The data-convention field in the Trecord is not C.

Explanation: The data-convention field in the Trecord is a value other than C.


User Response: Examine the data-conventionfield in the T record.

SQL3072N The data-format field in the Trecord is not M.

Explanation: The data-format field in the Trecord is a value other than M.


User Response: Examine the data-format fieldin the T record.

SQL3073N The machine format field in the Trecord is not PCbbb (where b =blank).

Explanation: The machine format field in the Trecord is a value other than PC bbb, where each bis a blank.


User Response: Examine the machine formatfield in the T record.

SQL3074N The data-location field in the Trecord is not I.

Explanation: The data-location field in the Trecord is a value other than I.


User Response: Examine the data-location fieldin the T record.

SQL3075N The CCNT in the T record cannotbe converted to a numeric valueor the value is out of range.

Explanation: The C-record count field in the Trecord is not an ASCII representation of anumber or is a number that is not valid for thisfield.


User Response: Examine the CCNT field in theT record.

SQL3076N The name length field in the Trecord cannot be converted to anumeric value or the value is outof range.

Explanation: The name length field in the Trecord is not an ASCII representation of anumber or is a number that is not valid for thisfield.


User Response: Examine the name length fieldin the T record.

SQL3077N The number of C recordsspecified in the CCNT field in theT record value exceeds themaximum allowed maximum.

Explanation: The value in the CCNT field of theT record is larger than the maximum allowed forthe indicated release.


User Response: Examine the CCNT field in theT record.

SQL3078N The length field in an A recordcannot be converted to a numericvalue.

Explanation: The length field in an A record isnot an ASCII representation of a number.



User Response: Examine the length fields in theA records.

SQL3079N The length field in a C recordcannot be converted to a numericvalue.

Explanation: The length field in a C record isnot an ASCII representation of a number.


User Response: Examine the length field in theC records.

SQL3080N The value in the length field ofthe C record is too small.

Explanation: The value in the length field of aC record is not large enough so the C record isnot valid.


User Response: Examine the length field in theC records.

SQL3081N Not enough C records werefound.

Explanation: The number of C records found(in the correct position) is less than the numberexpected from the C-record-count (CCNT) in theT record.


User Response: Examine the T and C records.

SQL3082N While reading or looking for a Crecord, the end of the file wasreached.

Explanation: The end of the file was reachedwhile the system was looking for a C record orwhile it was still reading a C record.


User Response: Examine the C records in theinput file. If the PC/IXF file was copied from onemedium to another, compare the copy with the

original or repeat the copy process.

SQL3083N The D-record-id field in the Crecord for column name cannot beconverted to a numeric value.

Explanation: The D-record-id field in the Crecord for the indicated column is not an ASCIIrepresentation of a number.


User Response: Examine the D-record-id fieldin the C record.

SQL3084N The D-record-position field in theC record for column name cannotbe converted to a numeric value.

Explanation: The D-record-position field in theC record for the indicated column is not anASCII representation of a number.


User Response: Examine the D-record-positionfield in the C record.

SQL3085N The D-record-id andD-record-position fields in the Crecord for column name are out ofrange or inconsistent with theprevious C record.

Explanation: The D-record-id or theD-record-position fields in the C record for theindicated column contain a value that is eitherout of the value range or is not correct relative tothe previous C record.


User Response: Examine the D-record-id andD-record-position fields in the C record.


SQL3086N There was no source columnspecified to be loaded intodatabase column name or thespecified source column does notexist, but the database column isnot nullable.

Explanation: Either there was not a PC/IXFcolumn specified to be exported into theindicated column or the specified PC/IXF sourcecolumn does not exist. Nulls cannot be insertedbecause the database column is not nullable.


User Response: Check the METHOD parameterfor erroneous names or positions or for fewerentries in the METHOD parameter than theAction String (e.g. ″REPLACE into ...″) parameterstates or implies.

SQL3087N The source column specified to beloaded into database column nameis not valid, but the databasecolumn is not nullable.

Explanation: The PC/IXF column cannot beloaded into the indicated database column andthe reason was given in a previous message inthe message log. Nulls cannot be insertedbecause the database column is not nullable.


User Response: Read the previous messages tounderstand why the column is not valid.

SQL3088N The source column specified to beloaded into database column nameis not compatible with thedatabase column, but the databasecolumn is not nullable.

Explanation: The source PC/IXF column is notcompatible with the target database column. Thecolumn types or lengths may be incompatible.Nulls cannot be inserted because the databasecolumn is not nullable.


User Response: Compare the columns in the

source PC/IXF file with the columns in thedatabase.

SQL3089N A non-D record was found wherea D record was expected.

Explanation: Some record other than a D recordwas found where a D record was expected.


User Response: Examine the D records in thefile.

SQL3090N The length field in a D recordcannot be converted to a numericvalue.

Explanation: The length field in a D record isnot an ASCII representation of a number.


User Response: Examine the length field in theD records.

SQL3091N The length field in a D record isout of range.

Explanation: The length field in a D record is anumber that is not valid for this field.


User Response: Examine the length field in theD records.

SQL3092N The identifier field in a D recorddoes not contain the expectedvalue.

Explanation: The identifier field in a D record isnot valid. One or more D records may have beenwritten out of sequence.


User Response: Examine the identifier field inthe D records.


SQL3093N The input file is not a valid WSFfile.

Explanation: The first record in the worksheetformat (WSF) file was not a beginning-of-file(BOF) record, or the version of the WSF file isnot supported.

The IMPORT utility stops processing. No data isimported.

User Response: Verify that the file is a validWSF file and that the name was enteredcorrectly.

SQL3094N The input column name was notfound, but the correspondingdatabase column is not nullable.

Explanation: The specified column was not inthe input file. Because the correspondingdatabase column is not nullable, data cannot beloaded into the column.

The utility stops processing. No data is loaded.The column names processed before the erroroccurred are in the database

User Response: Verify that the input filecontains the specified column names.

SQL3095N The specified column positionposition is not in the valid range of1 to 256.

Explanation: A column position was specifiedthat was not within the range of 1 to 256.

The utility stops processing. No data is loaded.The column names processed before the erroroccurred are in the database.

User Response: Verify that the specified columnposition is within the range 1 to 256.

SQL3096N The data type type of the databasecolumn name is not compatiblewith any WSF column type, butthe database column is notnullable.

Explanation: There is not any worksheet format(WSF) column type that is compatible with the

indicated database column. The database columnis not nullable so the IMPORT utility stopsprocessing.

No data is imported.

User Response: Redefine the database table sothe columns are compatible with the columnsbeing imported from the WSF file. Resubmit thecommand.

SQL3097N The record length field in theWSF record is not valid for itsrecord type.

Explanation: The worksheet format (WSF)records have an expected fixed length or avariable-length range. The record does notcontain the fixed length, or the variable length isout of range. Some damage occurred to the WSFfile, or it was generated incorrectly, possibly witha level of the Lotus product not supported by thedatabase manager.

The IMPORT utility stops processing.

User Response: Regenerate the WSF file with asupported level of the Lotus product.

SQL3098N The row number from the inputfile is not in the valid range of 1to 8192.

Explanation: The maximum number of rowsthat a worksheet format (WSF) spreadsheet cancontain is 8192. The cell coordinate contains avalue outside the valid range. Some damageoccurred to the WSF file, or it was generatedincorrectly, possibly with a level of the Lotusproduct not supported by the database manager.



SQL3099N The column number from theinput file is not in the valid rangeof 1 to 256.

Explanation: The maximum number of columnsthat a worksheet format (WSF) spreadsheet cancontain is 256. The cell coordinate contains a


value outside the valid range. Some damage hasoccurred to the WSF file, or it was generatedincorrectly, possibly with a level of the Lotusproduct that is not supported by the databasemanager.



SQL3100 - SQL3199

SQL3100W Column number column-number(identified as name) in the outputDEL format file is longer than 254bytes.

Explanation: The length or maximum length ofthe specified output column is greater than 254bytes. Columns larger than 254 are not supportedby some other products.

The entire field is exported without truncation.

User Response: If the output file cannot beprocessed by another product, export only asubstring of the incorrect column, redefine thetable, or manually truncate the data in the DELcolumn.

SQL3101W There is a character stringdelimiter in column column-numberin row row-number.

Explanation: The system puts character stringdelimiters around the character strings beingexported but it found a character string thatalready has the delimiter in the character string.

Delimiters will be placed around the characterstring. Future use of that string leads to anappearance of truncation. Processing cancontinue.

User Response: Review the data for the givencolumn and row in the output table or file. Toavoid loss of data, change the character delimiterto some character that is not in the data.

SQL3102W The number of columns in theMETHOD parameter is greaterthan the number of columns inthe Action String (e.g. ″REPLACEinto ...″) parameter.

Explanation: The number of columns takenfrom the input file or table is greater than thenumber to be put in the output table or file.

Only data for the columns indicated in theoutput table or file will be processed. Data in theexcess input columns is not processed.

User Response: Review the data in the outputtable or file.

SQL3103W The number of columns in theMETHOD parameter is less thanthe number of columns in theAction String (e.g. ″REPLACE into...″) parameter.

Explanation: The number of columns takenfrom the input file or table is less than thenumber to be put in the output table or file.

Only data for the columns indicated in the inputtable or file will be processed. Data in the excessoutput columns is not processed.

User Response: Review the data in the outputtable or file.

SQL3104N The Export utility is beginning toexport data to file name.

Explanation: This is the normal beginningmessage.



SQL3105N The Export utility has finishedexporting number rows.

Explanation: This is the summary message forthe export utility which is printed at the end ofthe message file. This message will state howmany rows resulting from the SELECT statementwere processed before the export utilityterminated.

User Response: If an sqlcode of 0 was returnedfrom the utility, then no response is required. Ifan sqlcode of 3107 was returned, check themessage file for warnings that occurred duringthe export and resubmit the command if desired.If a negative sqlcode was returned, an erroroccurred during the export and the data file maynot contain all the data requested. The commandshould be resubmitted with the error corrected.

SQL3106N An error occurred whileformatting a message for themessage file.

Explanation: The error message may beincomplete or formatted incorrectly.


SQL3107W There is at least one warningmessage in the message file.

Explanation: At least one warning was receivedduring processing.

This warning does not affect processing.

User Response: Review the message filewarning.

SQL3108W Unable to access file referencedby a DATALINK value in rowrow-number and columncolumn-number. Reason code =reason-code.

Explanation: The possible causes of thismessage depend on the value of reason-code:

1 DATALINK value data location formatis not valid.

2 DATALINK value DB2 Data LinksManager is not registered with thedatabase.

3 DATALINK linktype value is not valid.

4 DATALINK value referenced file cannotbe found by the DB2 Data LinksManager.

5 DATALINK value referenced file isalready linked to the database.

6 DATALINK value referenced file cannotbe accessed for linking. It may be asymbolic link or a file with permissionbit for set user ID (SUID) on or setgroup ID (SGID) on.

7 DATALINK value URL or comment istoo long.

8 DATALINK value referenced file cannotbe linked to the database. The DB2 DataLinks Manager does not authorize theDB2 user to link this file.

User Response: The action is based on thereason-code as follows:

1 Correct the data location format. Ifhostname is not specified, DB2 can usethe local hostname as default only ifsupport for FILE LINK CONTROL isenabled. Refer to the AdministrationGuide for information on enabling thissupport.

2 Ensure that the correct DB2 Data LinksManager is specified and if so have itregistered to the database. RegisteredDB2 Data Links Managers are ignoredunless support for FILE LINKCONTROL is enabled. Refer to theAdministration Guide for informationon enabling this support.

3 Correct the linktype value.

4 Check that the correct file is specifiedand that the file exists

5 Either unlink the existing reference tothe file or do not specify the file in thisstatement.


6 Linking of directories is not allowed.Use the actual file name, not thesymbolic link. If SUID or SGID is on,this file cannot be linked using aDATALINK type.

7 Reduce the length of the data locationvalue or the comment.

8 Contact the DB2 Data Links Manageradministrator to get the necessaryauthorization

SQL3109N The utility is beginning to loaddata from file name.

Explanation: This is the normal beginningmessage. The message may indicate the name ofa temporary file created on the server instead ofthe source file.


SQL3110N The utility has completedprocessing. number rows were readfrom the input file.

Explanation: This is the normal endingmessage.


SQL3111C An I/O error occurred whileclosing the input data file.

Explanation: A system I/O error occurred whileclosing the input data file. This error can refer toa problem on either the client or the server.

The file is not closed.

User Response: Examine the input file for anI/O error.

SQL3112W There are fewer input filecolumns specified than databasecolumns.

Explanation: There are fewer columns specifiedin the input file than in the output table. Becausethe extra columns in the table are defined asnullable, the values in those columns are filledwith nulls.


SQL3113W The data type type of the databasecolumn name is not compatiblewith this format file. Null valuesare inserted for the column.

Explanation: The database column type is notvalid for this file. Because the column is nullable,nulls are inserted.

Null values are loaded for the indicated column.

User Response: If nulls are not acceptable forthe column, do one of the following:

v Edit the data in the table.

v If possible, use another compatible column inthe database table as the target column andresubmit the command.

v Redefine the database table so the columns arecompatible with the columns being loaded andresubmit the command.

SQL3114W Some data following text in rowrow-number and columncolumn-number was not loaded.

Explanation: Some data in the specified rowand column is not loaded, probably because thecolumn contains data as follows:

v A closed string delimiter

v An isolated carriage return or line feed controlcharacter

v A non-delimited string value.

The text that was loaded is shown in the texttoken.

The contents of the field may be incomplete.

User Response: Compare the value in theoutput table with the input file. If necessary,correct the input file and resubmit the command,or edit the data in the table.


SQL3115W The field value beginning text inrow row-number and columncolumn-number is longer than thelongest allowable table column.The value was truncated.

Explanation: The field value is longer than32700 bytes.

The value was truncated after 32700 bytes.

User Response: Compare the value in theoutput table with the input file. If necessary,correct the input file and resubmit the commandor edit the data in the table. Check forunmatched character string delimiters.

SQL3116W The field value in row row-numberand column column-number ismissing, but the target column isnot nullable.

Explanation: A null field value was encounteredin the input file. Because the target column in thetable is not nullable, it cannot be loaded.

For files other than ASCII files, the value of thecolumn number specifies the field within the rowof the missing data. For ASCII files, the value ofthe column number specifies the byte positionwithin the row of the missing data.

The row is not loaded.

User Response: If necessary, correct the inputfile and resubmit the command or edit the datain the table.

SQL3117W The field value in row row-numberand column column-number cannotbe converted to a SMALLINTvalue. A null was loaded.

Explanation: The value in the specified fieldcannot be converted to a SMALLINT value.There may be a data type mismatch. The valuemay be larger than a 2-byte integer.

For delimited ASCII (DEL) files, the value of thecolumn number specifies the field within the rowthat contains the value in question. For ASCIIfiles, the value of the column number specifies

the byte location within the row where the valuein question begins.

A null value is loaded.

User Response: Examine the input value. Ifnecessary, correct the input file and resubmit thecommand or edit the data in the table.

SQL3118W The field value in row row-numberand column column-number cannotbe converted to a SMALLINTvalue, but the target column is notnullable. The row was not loaded.

Explanation: The value in the specified fieldcannot be converted to a SMALLINT value.There may be a data type mismatch. The valuemay be larger than a 2-byte integer. A nullcannot be loaded because the output column inthe table is not nullable.

For delimited ASCII (DEL) files, the value of thecolumn number specifies the field within the rowthat contains the value in question. For ASCIIfiles, the value of the column number specifiesthe byte location within the row where the valuein question begins.


User Response: Correct the input file andresubmit the command or edit the data in thetable.

SQL3119W The field value in row row-numberand column column-number cannotbe converted to an INTEGERvalue. A null was loaded.

Explanation: There may be a data typemismatch because the value in the specified fieldcannot be converted to an INTEGER value.



User Response: Examine the input value. If


necessary, correct the input file and resubmit thecommand or edit the data in the table.

SQL3120W The field value in row row-numberand column column-number cannotbe converted to an INTEGERvalue, but the target column is notnullable. The row was not loaded.

Explanation: There may be a data typemismatch because the value in the specified fieldcannot be converted to an INTEGER value. Anull cannot be loaded because the output columnin the table is not nullable.




SQL3121W The field value in row row-numberand column column-number cannotbe converted to a FLOAT value. Anull was loaded.

Explanation: The value in the specified fieldcannot be converted to a FLOAT value. Theremay be a data type mismatch.




SQL3122W The field value in row row-numberand column column-number cannotbe converted to a FLOAT value,but the target column is notnullable. The row was not loaded.

Explanation: The value in the specified fieldcannot be converted to a FLOAT value. Theremay be a data type mismatch. A null cannot beloaded because the output column in the table isnot nullable.




SQL3123W The field value in row row-numberand column column-number cannotbe converted to a PACKEDDECIMAL value. A null wasloaded.

Explanation: The value in the specified fieldcannot be converted to a PACKED DECIMALvalue. There may be a data type mismatch.





SQL3124W The field value in row row-numberand column column-number cannotbe converted to a PACKEDDECIMAL value, but the targetcolumn is not nullable. The rowwas not loaded.

Explanation: The value in the specified fieldcannot be converted to a PACKED DECIMALvalue. There may be a data type mismatch. Anull cannot be loaded because the output columnin the table is not nullable.




SQL3125W The character data in rowrow-number and columncolumn-number was truncatedbecause the data is longer thanthe target database column.

Explanation: The length of the field data in theinput file was longer than the length of thedatabase field where it is being loaded.

The character data was truncated.

User Response: Compare the value in theoutput table with the input file. If necessary,correct the input file and resubmit the commandor edit the data in the table. The width of thedatabase column cannot be increased. Ifnecessary, define a new table with widercolumns and repeat the process.

SQL3128W The field containing data in rowrow-number and columncolumn-number. was truncated intoa DATE field because the data islonger than the database column.

Explanation: The date value in the specifiedfield is longer than the length of the stringrepresentation of a date.

The date value is truncated to fit into the table.

User Response: Compare the value in theoutput table with the input file. If necessary,correct the input file and resubmit the commandor edit the data in the table.

SQL3129W The date, time, or timestamp fieldcontaining text in row row-numberand column column-number waspadded with blanks.

Explanation: The field data in the input file wasshorter than the database column.

The data on the right is padded with blanks.


SQL3130W The field containing text in rowrow-number and columncolumn-number was truncated intoa TIME field because the data islonger than the database column.

Explanation: The time value in the specifiedfield is longer than the length of the stringrepresentation of a time.

The time value is truncated to fit into the table.



SQL3131W The field containing text in rowrow-number and columncolumn-number was truncated intoa TIMESTAMP field because thedata is longer than the databasecolumn.

Explanation: The timestamp value in thespecified field is longer than the length of thestring representation of a timestamp.

The timestamp value is truncated to fit into thetable.


SQL3132W The character data in columncolumn will be truncated to sizesize.

Explanation: The character data column has adefined size that is longer than the longestdefault character column which can be exported;each value will be truncated to the specified size.

For example, by default, only the firstSQL_LONGMAX bytes of a LOB column will beexported. If the entire LOB column is desired, theLOBSINFILE keyword must be specified in thefiletype modifier and each LOB column will bestored into a separate file.

User Response: This is a warning only. Noaction is required.

SQL3133W The field in row row-number andcolumn column-number containsinvalid DATALINK value. A nullwas loaded.

Explanation: The DATALINK value in thespecified field is invalid. For delimited ASCII(DEL) files, the value of the column numberspecifies the field within the row that containsthe value in question. For ASCII files, the valueof the column number specifies the byte locationwithin the row where the value in questionbegins.



SQL3134W The field in row row-number andcolumn column-number containsinvalid DATALINK value, but thetarget column is not nullable. Therow was not loaded.

Explanation: The DATALINK value in thespecified field is invalid. For delimited ASCII(DEL) files, the value of the column numberspecifies the field within the row that containsthe value in question. For ASCII files, the valueof the column number specifies the byte locationwithin the row where the value in questionbegins.

User Response: Examine the input value. Ifnecessary, correct the input file and resubmit thecommand.

SQL3135N The number of columns in theMETHOD parameter is greaterthan the number of columns inthe target table.

Explanation: The number of data columns inthe METHOD parameter must be less than orequal to the number of data columns in theactual table.

User Response: Specify the correct number ofinput columns in the METHOD parameter andresubmit the command.

SQL3137W Row row-number is too short. Atleast one input value beingloaded to a non-nullable databasecolumn is missing. The row wasnot loaded.

Explanation: If loading from a delimited ASCIIfile, the row contains too few fields. If loadingfrom a non-delimited ASCII file, the row containstoo few bytes of data. There is no input value forat least one non-nullable target column.



User Response: Examine the input file and thecontents of the target table. Correct the input fileand resubmit the command, or edit the data inthe table.

SQL3138W The ending character stringdelimiter was not found beforethe end of the input data file wasreached.

Explanation: The end of the input data file wasreached before the terminating character stringdelimiter was found.

A closing character string delimiter is assumed atthe end of the data.


SQL3139W An error error occurred while theutility was disconnecting from thedatabase.

Explanation: The IMPORT or EXPORT utilitycould not disconnect from the database.

The output data may be incomplete.

User Response: Use the error number in themessage to determine the exact error.

SQL3142W The column heading for columncolumn-number is being truncatedto 240 bytes.

Explanation: The LOTUS 1-2-3** andSymphony** programs have a limit of 240 bytesfor label records. If a column heading greaterthan 240 bytes is specified for export, it is betruncated to 240 bytes.

The column heading is truncated. Processingcontinues.

User Response: Verify that the column headingsare 240 bytes or less. Check for a possible errorin specifying the names for the columns in theoutput worksheet format (WSF) file.

SQL3143W A maximum length of variablelength column column-numberexceeds the limitation of 240bytes. Data from the column maybe truncated.

Explanation: The LOTUS 1-2-3** andSymphony** programs have a limit of 240 bytesfor label records. Whenever a character fieldlonger than 240 bytes is written to a worksheetformat (WSF) file, the data will be truncated to240 bytes.

Continue processing. Subsequent data entries forthe column may be truncated.

User Response: Verify the output. If significantdata from the column is lost because oftruncation, investigate selecting the data from thecolumn in several fields by substringing, orredesign the database.

SQL3144W The length of fixed length columncolumn-number exceeds the240-byte limitation. Data from thecolumn may be truncated.

Explanation: The Lotus 1-2-3** and Symphony**programs have a limit of 240 bytes for labelrecords. Whenever a character field longer than240 bytes is written to a worksheet format (WSF)file, the data will be truncated to 240 bytes.

All data entries for the column are truncatedwith no additional messages written to themessage log.

Continue processing.

User Response: Verify output. If significant datafrom the column is lost because of truncation,investigate selecting the data from the column inseveral fields by substringing, or redesign thedatabase.

SQL3145W The data for row row-number,column column-number is beingtruncated to 240 bytes.

Explanation: The Lotus 1-2-3** and Symphony**programs have a limit of 240 bytes for labelrecords. Whenever a character field longer than


240 bytes is written to a worksheet format (WSF)file, the data is truncated to 240 bytes. Thismessage is preceded by message SQL3143associated with the column.

Processing continues. The data is truncated.

User Response: Verify the output. If significantdata from the column is lost because oftruncation, investigate selecting the data from thecolumn in several fields by substringing, orredesign the database.

SQL3146N The DATE or TIMESTAMP valuefor row row-number and columncolumn-number is out of range.

Explanation: The value for a date or timestampis not valid. A date value from 01-01-1900 to12-31-2099 is valid for worksheet format (WSF)files.

The cell record is not created.

User Response: Compare the value in theoutput file with the input table. If necessary,correct the input value and resubmit thecommand or edit the data in the table.

SQL3147W More than 2048 rows wereexported into a worksheetformatted file.

Explanation: The number of rows exportedexceeds 2048. The first generation productscannot support more than 2048 rows.


User Response: The rows beyond 2048 can beread only by second and third generationproducts.

SQL3148W A row from the input file was notinserted into the table. SQLCODEsqlcode was returned.

Explanation: The database operation to insert arow of data read from the input file failed. Oneor more of the fields in the input file is notcompatible with the database field where thefield is being inserted.

Processing continues with the next row of inputdata.

User Response: See the next message in themessage file for the row number not inserted.Examine the input file and the database contents.If desired, modify the database or modify theinput file and rerun the operation.

SQL3149N number-1 rows were processedfrom the input file. number-2 rowswere successfully inserted into thetable. number-3 rows wererejected.

Explanation: This summary message tells howmany rows of data were read from the input file,how many rows were successfully inserted intothe database table, and how many rows wererejected. If using the INSERT_UPDATE option,the number of rows updated is the number ofrows processed minus the number inserted andrejected.

User Response: None, because this is asummary message. The detail messages maysuggest corrective action.

SQL3150N The H record in the PC/IXF filehas product product, date date, andtime time.

Explanation: Information is given about theproduct that created the PC/IXF file and when itwas created.


SQL3151N No data conversion will be donefrom the single-byte code pagevalue code-page in the H record tothe application single-byte codepage value code-page because theFORCEIN option was specified.

Explanation: No data conversion will beperformed from the IXF code page to theapplication code page because the FORCEINoption was specified.

User Response: No action is required. If theconversion from the IXF file code page to the


application code page is supported by thedatabase manager, the operation can beresubmitted without the FORCEIN option andthe data will be converted.

SQL3152N The double-byte code page valuevalue in the H record is notcompatible with the double-bytecode page value value for theapplication. Data will be insertedbecause the FORCEIN option wasspecified.

Explanation: The double-byte code page valuesin the record and the application are notcompatible. Because the FORCEIN option wasused, the data is inserted.


SQL3153N The T record in the PC/IXF filehas name name, qualifier qualifier,and source source.

Explanation: Optional information is givenabout the name of the table where data wasextracted, the product that created the table, andthe original source of the data.


SQL3154W The HCNT value in the H recordand the CCNT value in the Trecord are not compatible. TheCCNT value in the T record willbe used.

Explanation: The HCNT value in the H recordand the CCNT value in the T record do notagree.

The CCNT value in the T record is used.

User Response: Verify that the CCNT value iscorrect. If not, make the necessary changes to theHCNT or CCNT values and resubmit thecommand.

SQL3155W The name length field in the Crecord for column name is notvalid. Data from the column willnot be loaded.

Explanation: The value in the name length fieldin the C record for the indicated column is notvalid.

Data from the indicated column is not loaded.

User Response: Change the name length fieldin the C record and resubmit the command.

SQL3156W The null field in the C record forcolumn name is not valid. Datafrom the column will not beloaded.

Explanation: The null field in the C record forthe indicated column is not valid.


User Response: Change the null field in the Crecord and resubmit the command.

SQL3157W The type field in the C record forcolumn name is not valid. Datafrom the column will not beloaded.

Explanation: The type field in the C record forthe indicated column is not valid. The code pagevalues may not be compatible with the columntype.


User Response: Change the type field in the Crecord and resubmit the command.

SQL3158W The single-byte code page field inthe C record for column name isnot valid. Data from the columnwill not be loaded.

Explanation: The single-byte code page field inthe C record for the indicated column is notvalid.


User Response: Change the single-byte code


page field in the C record and resubmit thecommand.

SQL3159W The double-byte code page fieldin the C record for column name isnot valid. Data from the columnwill not be loaded.

Explanation: The double-byte code page field inthe C record for the indicated column is notvalid.


User Response: Change the double-byte codepage field in the C record and resubmit thecommand.

SQL3160W The column length field in the Crecord for column name is notvalid. Data from the column willnot be loaded.

Explanation: The column length field in the Crecord for the indicated column is not valid.


User Response: Change the column length fieldin the C record and resubmit the command.

SQL3161W The precision field in the Crecord for column name is notvalid. Data from the column willnot be loaded.

Explanation: The precision field in the C recordfor the indicated column is not valid.


User Response: Change the precision field inthe C record and resubmit the command.

SQL3162W The scale field in the C record forcolumn name is not valid. Datafrom the column will not beloaded.

Explanation: The scale field in the C record forthe indicated column is not valid.


User Response: Change the scale field in the Crecord and resubmit the command.

SQL3163W The column length field in the Crecord for floating point columnname is blank. A value of 00008will be used.

Explanation: The column length field in the Crecord for the indicated column is blank.

A column length of 00008 is used.


SQL3164W The column length field in the Crecord for floating point columnname is not valid. Data from thecolumn will not be loaded.

Explanation: The column length field in the Crecord for the indicated column is not valid. Theindicated column is a floating point column.


User Response: Change the column length fieldin the C record and resubmit the command.

SQL3165W The column type field type in theC record for column name is notvalid. Data from the column willnot be loaded.

Explanation: The column type in the C recordfor the indicated column is not valid.


User Response: Change the column type fieldin the C record and resubmit the command.

SQL3166W No PC/IXF column was specifiedto be loaded into database columnname, or the specified PC/IXFcolumn does not exist. Nulls willbe inserted.

Explanation: Either there was not a PC/IXFcolumn specified to be loaded into the indicatedcolumn, or the specified PC/IXF source columndoes not exist.



User Response: No action is required. If nullsare not acceptable for this column, check theMETHOD parameter for erroneous names orpositions or for fewer entries in the METHODparameter than columns stated in or implied bythe Action String (e.g. ″REPLACE into ...″)parameter.

SQL3167W The PC/IXF column specified tobe loaded into database columnname is not valid. Nulls will beinserted.

Explanation: Values in the PC/IXF columncannot be loaded into the indicated databasecolumn and the reason is given in a previousmessage in the log.


User Response: Read the previous messages tounderstand why the column is not valid.

SQL3168W The PC/IXF column specified tobe loaded into database columnname is not compatible with thedatabase column. Nulls will beinserted.

Explanation: The source PC/IXF and the targetdatabase column types or lengths may not becompatible.


User Response: Compare the columns in thesource PC/IXF file and the database.

SQL3169N The FORCEIN option may beused to make the PC/IXF columnname acceptable for loading intodatabase column name.

Explanation: This is for information only aboutthe optional use of the FORCEIN option.


SQL3170W The end of the file was reachedwithin a row of data. The partialrow of data was not loaded.

Explanation: The end of the file was reachedbefore the end of the current row of data. Thefile may contain only part of the expected data.

The partial row of data is not loaded.

User Response: If the PC/IXF file was copiedfrom one medium to another, compare the copywith the original or repeat the copy process.

SQL3171W A non-label record was found inthe column header row. Therecord was not processed.

Explanation: The IMPORT utility expects onlylabel records in the column header row (rowone) of the worksheet format (WSF) file.

The system does not process the record andcontinues to the next record.

User Response: Remove all data andinformation except the column headers from thefirst row of the spreadsheet file. Resubmit thecommand.

SQL3172W The specified input column namewas not found. The correspondingdatabase column will contain nullvalues.

Explanation: The specified input column wasnot found in the input spreadsheet file. Thedatabase column is nullable and contains nullvalues.

User Response: Verify the specified inputcolumn name.

SQL3173N The inserted data for column namewill always contain fewercharacters than the column width.

Explanation: The database column width islarger than the maximum worksheet format(WSF) label record.




SQL3174W The data type type of the databasecolumn name is not compatiblewith any WSF column type. Nullvalues will be inserted for thiscolumn.

Explanation: The database column type is notvalid for a worksheet format (WSF) file. Becausethe column is nullable, nulls are imported for thecolumn.

User Response: If nulls are not acceptable forthe column, do one of the following:

v Edit the data in the table.

v If possible, use another compatible column inthe database table as the target column andresubmit the command.

v Redefine the database table so that thecolumns are compatible with the columnsimported from the WSF file, and resubmit thecommand.

SQL3175W The input record for database rowrow, column column is not valid.

Explanation: The record in the spreadsheet fileis not compatible with the data type of thedatabase column. If the database column is agraphic data type, the input data may contain anodd number of bytes.

If the column is nullable, a null is inserted. If thecolumn is not nullable, the row is not imported.

User Response: Either edit the data in the tableor verify that the data in the spreadsheet file isvalid for importing into a database managerdatabase and resubmit the command.

SQL3176W The value for row row, columncolumn in the WSF file is out ofrange for a date value.

Explanation: The record in the spreadsheet filecontains a value that is too large or too small torepresent a valid worksheet format (WSF) date.A valid WSF date is between 1 and 73050,inclusive.


User Response: Either edit the data in the tableor verify that the data in the spreadsheet file isvalid for import into a database managerdatabase and resubmit the command.

SQL3177W The value in the WSF file for rowrow, column column is out of rangefor a time value.

Explanation: The record in the spreadsheet filecontains a value that is either too large or toosmall to represent a valid worksheet format(WSF) time. A WSF time is a value equal to orgreater than zero, but less than one.


User Response: Either edit the data in the tableor verify that the value to be imported is a timevalue in the input spreadsheet file and resubmitthe command.

SQL3178W The type of record in the WSF filefor database row row-number,column column-number is not validfor representing a time value.

Explanation: The input value is an integervalue. A time value must be represented by afloating point number or a fraction of a day in aworksheet format (WSF) spreadsheet file.


User Response: Either edit the data in the tableor verify that the value to be imported is a timevalue in the input spreadsheet file and resubmitthe command.

SQL3179W Row row in the input file ismissing data for inserting into anon-nullable column in thedatabase. The row was notinserted.

Explanation: The row of data from the inputfile has missing or not valid data for a


non-nullable column. The values in theremaining database columns in that row are notinserted.

Processing continues with the next row. The rowis not inserted.

User Response: Either edit the data in the tableor verify that the data in the spreadsheet file isvalid for inserting into a database managerdatabase.

SQL3180W Insert diskette number into drivedrive.

Explanation: This is a request for theapplication to prompt the user to place thespecified diskette in the specified drive.

The utility is waiting to be called again after theuser puts the diskette in the drive.

User Response: Prompt the user for the disketteand then return to the utility with the calleracparameter indicating whether processingcontinues or ends.

SQL3181W The end of the file was reachedbefore the expected ending recordwas found.

Explanation: During the load of a PC/IXF filecreated by the database manager, the A record ofsubtype E that is expected as the last A recordwas not found.

The input file probably is damaged.


User Response: Check for data that was notloaded. If data is missing, edit the table orchange the input file and resubmit the command.If the PC/IXF file was copied from one mediumto another, compare the copy with the original orrepeat the copy process.

SQL3182W Insert diskette number into drivedrive. The diskette that iscurrently inserted is not the rightdiskette or the continuationdiskette is not valid.

Explanation: During the load of a PC/IXF filethat is contained on more than one diskette, arequest to insert a diskette was sent to theapplication, a confirmation that the diskette is inthe drive was returned but the continuation fileis not there or is not valid. This action does notapply to the first diskette.

The utility waits for a response from theapplication to either continue processing or stopprocessing.

User Response: Have the user verify that thecorrect diskette is in the drive. If the correctdiskette is in the drive, call the utility again withthe callerac parameter set to stop processing.

SQL3183W Multiple delimiter overrides inthe filetmod parameter are notseparated by blanks.

Explanation: At least one COLDEL, CHARDELor DECPT keyword in the filetmod parameter isnot at the beginning of the filetmod parameterand does not follow a blank (space). Thiscondition may arise during the LOAD/IMPORTor export of delimited ASCII (DEL) files.

The utility stops processing. The erroneousdelimiter overrides are ignored.

User Response: Resubmit the command with acorrect filetmod parameter.

SQL3185W The previous error occurred whileprocessing data from rowrow-number of the input file.

Explanation: This message provides theidentification of the row where the erroroccurred for the previous message listed in themessage file (for example, SQL3306).



SQL3186W Data was not loaded into thedatabase, because the log was full.SQLCODE sqlcode was returned. Acommit will be attempted and theoperation will continue if thecommit is successful.

Explanation: The utility could not insert a rowof data into the database because the databasetransaction log is full.

The completed database transactions arecommitted and the insert is tried again. If therepeated insert continues to indicate that the logis full, the utility stops processing.

User Response: Be aware that a subsequentfailure of the utility causes the database to rollback to the state after the last commit, not to thestate before the utility was initially called.

SQL3187W An error occurred while creatingan index. SQLCODE sqlcode wasreturned.

Explanation: The IMPORT utility was creatingan index when an error occurred. An index mayalready exist for some table.

This error occurs only during the import of aPC/IXF file.

The utility continues processing. The file wasimported, but the index was not created on thetable.

Federated system users: in addition to thepreviously listed cause, this error can occur whena CREATE NICKNAME statement was issued atfederated server and the table at the data sourcehad an index or indexes with too many columns,or the total index row size could not berepresented in the federated server catalog. Thesqlcode in the message provides furtherinformation about the problem encountered.

User Response: Read the next message in themessage log (SQL3189) for the name of the indexthat was not created. Create the index with theCREATE INDEX command.

Federated system users: select from the datasource catalog and the federated server catalog to

determine which index or indexes were notcreated in the federated server catalog. Either:

v Create the indexes using the CREATE INDEXcommand. Remember to truncate columns asappropriate in order to not violate limitswhich caused the index to not be created inthe first place.

v Do nothing and allow federated server tofunction without knowledge about the index.

Both of the previously listed options havepotential performance implications.

SQL3188N An error occurred while erasingthe contents of the table.

Explanation: When running LOAD/IMPORTwith the REPLACE option, the specified databasetable is truncated before inserting the data backinto the table. An error occurred during thetruncation processing.

The utility ends with an error.


SQL3189N The previous message refers toindex name with columnscolumn-list.

Explanation: This message always followsmessage SQL3187 when an error occurs whilecreating an index. name is the name of the indexwhere the create failed. column list is a string ofindex column names. Each column name in thestring is preceded by a plus (+) or a minus (−)sign indicating ascending or descending order.


User Response: Manually create the index withthe CREATE INDEX command.

SQL3190N The indexixf option is not validfor this Import operation.

Explanation: If INDEXIXF is used in the filetmodparameter of the IMPORT command, each of thefollowing is also required:

v The IMPORT must be replacing the contents ofa table.


v The METHOD parameter must be null.

v Each IXF column must be targeted to adatabase column with the same name.

The utility stops processing. No data is imported.

User Response: Resubmit the command eitherwithout the INDEXIXF option or with the otherparameters that are valid with the INDEXIXFoption.

SQL3191N The field in row row-number,column column-number whichbegins with string does not matchthe user specified DATEFORMAT,TIMEFORMAT, orTIMESTAMPFORMAT. The rowwill be rejected.

Explanation: The data does not match the userspecified format. This may be caused by missingfields, mismatched column separators, or a valueout of range.

User Response: Examine the input value.Correct the input file or specify aDATEFORMAT, TIMEFORMAT, orTIMESTAMPFORMAT that matches the data andresubmit the command.

SQL3192N In the filetmod a user specifiedformat keyword beginning with thestring string is not valid.

Explanation: The user specified format is notvalid because it may be specified more thanonce, or it may contain an invalid character.

The formats must be enclosed in double-quotes.

Valid DATEFORMAT specifiers include “YYYY”and the “M”, and “D” characters.

Valid TIMEFORMAT specifiers include “AM”,“PM”, “TT”, and the “H”, “M”, and “D”characters.

Valid TIMESTAMPFORMAT specifiers include allof the specifiers for DATEFORMAT andTIMEFORMAT, as well as “UUUUUU”.However, “M” cannot be next to both a dateformat specifier and a time format specifier.

A field separator is necessary if thecorresponding value in the data file can have avariable length.


User Response: Examine the format specifier.Correct the format, and resubmit the command.

SQL3193N The specified view ormaterialized query table cannotbe updated. You cannotLOAD/IMPORT into this view orLOAD into this materializedquery table.

Explanation: The LOAD/IMPORT utility can berun against a view only if the view can beupdated. The specified view is defined such thatdata in it may not be changed.

The LOAD utility can be run against amaterialized query table only if the materializedquery table is not replicated. The specified tableis a replicated materialized query table.

The IMPORT utility can be run against amaterialized query table only if the materializedquery table is a user maintained materializedquery table. The specified table is a systemmaintained materialized query table.

The LOAD/IMPORT utility stops processing. Nodata is inserted.

User Response: Resubmit the command withthe name of a table or a view that can beupdated.

SQL3194N The specified table is a systemtable. You cannot load a systemtable.

Explanation: The utility cannot be run against asystem table.




SQL3195W The diskette number in drive drivecannot be used for the output file.Insert a formatted diskette withwritable free space.

Explanation: The EXPORT utility cannot use thecurrent diskette for exporting to a PC/IXF file forone of the following reasons:

v The output file cannot be opened on thediskette. The diskette may be unformatted.

v Not enough free space is available on thediskette.

This warning code is a request for theapplication to prompt the user to place anotherdiskette in the specified drive.

The utility is waiting to be called again after theuser puts the diskette in the drive.

User Response: Prompt the user for the disketteand then return to the utility with the calleracparameter indicating whether processingcontinues or ends.

SQL3196N The input file was not found.

Explanation: The source file to be loaded into adatabase could not be found in the pathindicated by the datafile parameter.


User Response: Verify that the input file doesexist and that the path to it is correct.

SQL3197N An attempt was made to executemultiple copies of import orexport.

Explanation: An attempt was made to executemore than one instance of the import or exportutility on a system where this is not supported.


User Response: Resubmit the second operationwhen no other processes are attempting toexecute the same utility.

SQL3200 - SQL3299

SQL3201N The specified table cannot bereplaced because another table isdependent on it.

Explanation: A table that is a parent in arelationship with another table cannot bereplaced.


User Response: Select a different option, suchas INSERT, or select a different target for theutility operation.

SQL3203N The INSERT_UPDATE option isnot permitted for the specifiedtarget because it has no primarykey or all columns are in theprimary key.

Explanation: The INSERT_UPDATE option isonly valid when the target table has a primarykey and the target columns include all columnsof the primary key. In addition, the target table

should contain at least one column that is notpart of the primary key.


User Response: Select a different option such asINSERT, or choose a different target for theutility operation.

SQL3204N The INSERT_UPDATE optionmay not be applied to a view.

Explanation: The INSERT_UPDATE option isnot valid for views and a view has been selectedas the target of the utility operation.




SQL3205N The specified view cannot bereplaced because the base tablehas a dependent.

Explanation: A view whose base table is aparent table in a referential relationship with anytable (including itself) cannot be replaced.



SQL3206N The specified view cannot bereplaced because its definitioninvolves a subquery.

Explanation: A view whose definition involvesa subquery cannot be replaced. If the viewdefinition depends on the definition of otherviews, the other views cannot containsubqueries. The use of a subquery anywhere inthe definition of any view on which the targetview is based prohibits the REPLACE option.


User Response: Select a different option, suchas INSERT, or choose a different target for theutility operation.

SQL3207N Invalid table-list provided.Reason code reason-code.

Explanation: The traversal-order-list/subtable-list provided is invalid. The explanation for thereason code is:

1. Tables specified in the traversal-order-list arenot in PRE-ORDER fashion.

2. Tables specified in the traversal-order-list arenot connected.

3. Mismatch of schema name found intraversal-order-list/subtable-list.

4. With REPLACE option, some subtables aremissing in the traversal-order-list.

5. Subtable-list is not equal to or a subset of thetraversal-order-list.

User Response: The user action, based on thereason code, is:

1. Make sure the traversal-order-list is inPRE-ORDER fashion.

2. Make sure all tables in the traversal-order-listare connected.

3. Make sure schema names are consistent.

4. When REPLACE option is used, make sureall subtables in the hierarchy are included.

5. Make sure subtable-list is equal to or is asubset of the traversal-order-list.

SQL3208W Importing data from typed tablesinto regular table.

Explanation: User specified to import data fromtyped tables into regular table. Please note,object_id column will not be cast whileimporting.

User Response: Please make sure suchoperation is intentional.

SQL3209N Import with CREATE option doesnot allow renaming subtablename nor attribute names.

Explanation: When CREATE option is used,neither subtable name nor attribute names can berenamed.

User Response: Please check your IMPORTcommand and make sure no subtable-list isspecified.

SQL3210N Option option is not compatiblewith hierarchy in command-name.

Explanation: option is not compatible withhierarchy in EXPORT, IMPORT, or LOAD.

User Response: Please check the commandsyntax for hierarchical support.

SQL3211N LOAD does not support typedtables.

Explanation: LOAD does not support typedtables. Please consider IMPORT instead.

User Response: Please use IMPORT to bringhierarchical data into the database.


SQL3212N The TERMINATE option of theLOAD command is not currentlysupported for tables withDATALINK column(s), or tablespaces in delete pending state.

Explanation: An attempt was made to terminatea crashed, interrupted, or forced LOADoperation against a table which containsDATALINK column(s), or a table which residesin table space(s) in delete pending state. Theseare not currently supported.

User Response: Use the RESTART option of theLOAD command to recover a crashed,interrupted, or forced LOAD operation.

SQL3213I The indexing mode is mode.

Explanation: The indexing mode values are afollows:

REBUILDindexes will be completely rebuilt

INCREMENTALindexes will be extended

DEFERREDindexes will not be updated, but will bemarked as requiring refresh prior tonext access.


SQL3214N The LOAD utility does notsupport deferred indexing fortables with unique indexes.

Explanation: An indexing mode of DEFERREDwas specified for a table that has unique indexes.This is not valid.

User Response: Specify an indexing mode ofAUTOSELECT, REBUILD or INCREMENTAL,and reissue the command.

SQL3215W The Load utility currently doesnot support INCREMENTALindexing when loading into aDMS table space on tables wherethe table’s index object resides inthe same table space as any of theother target table’s objects, andthe COPY option is also specified.The REBUILD indexing modewill be used instead.

Explanation: INCREMENTAL indexing mode isnot supported for this operation. REBUILDindexing mode is used instead.

User Response: The user can avoid thiswarning by defining the index in a table spacethat is not shared by other objects in the table tobe loaded. Alternatively, avoid use of the COPYoption. Please refer to the DB2 documentation fora full list of alternatives to the COPY option.

SQL3216W The table’s index object was notconsistent at the time the loadutility began. INCREMENTALindexing cannot be performedduring this load utility operation.The REBUILD indexing modewill be used instead.

Explanation: INCREMENTAL indexing can onlybe used on tables that have a consistent indexobject at the time the load utility begins. Loadingwith indexing mode REBUILD causes the tableindex to be rebuilt in a consistent manner.


SQL3217W The INCREMENTAL indexingmode is supported only whenusing LOAD to append data usingthe INSERT INTO action. Thecurrent LOAD action is action. Theutility will use indexing mode ofmode instead.

Explanation: INCREMENTAL indexing can onlybe used when appending data to a table usingthe load INSERT action. This feature is notsupported with when loading with REPLACE,RESTART, or TERMINATE actions.



SQL3218C The LOAD utility cannot proceedbecause it has encountered one ormore damaged index files. Restartthe database and resubmit theLOAD command.

Explanation: The LOAD utility cannot proceedbecause one or more index on disk datastructures for the target table are in aninconsistent state.

User Response: Terminate all applications andissue the RESTART DATABASE command for theaffected database to rebuild the damaged indexor indexes. Then resubmit the LOAD command.

SQL3219N LOAD utility failed to disableconstraint checking for the targettable.

Explanation: The LOAD utility encounteredproblems during its attempt to disable constraintchecking for the target table.

User Response:

v Issue the SET INTEGRITY OFF command onthe target table prior to running the LOADutility.

v If attempting a LOAD in the REPLACE modeafter a previously failed LOAD operation, usethe LOAD TERMINATE command to put thetablespace into an accessible state prior toissuing a LOAD REPLACE command.

SQL3220W Volume volume-name was notfound in the directory-namedirectory. Copy the volume intothis directory and continue theLOAD/IMPORT.

Explanation: An attempt to LOAD/IMPORT amultiple IXF file was made, but one of the files ismissing from the directory specified.LOAD/IMPORT tries to find the parts in thesame directory as the first part.

The import will terminate.

User Response:

v Find the part and put it in the same directoryas the first part. Then call LOAD/IMPORTagain with callerac of SQLU_CONTINUE. TheLOAD/IMPORT will continue processing thefile.

v Terminate the LOAD/IMPORT by callingLOAD/IMPORT with a callerac ofSQLU_TERMINATE.

SQL3221W ...Begin COMMIT WORK. InputRecord Count = count

Explanation: The import is about to attempt aCOMMIT of the work performed.

User Response: If the SQL3222W message isnot printed immediately after this message, thenthe COMMIT failed and you will need to checkyour table or view to see which records havebeen imported. You can then start the importagain with a RESTARTCOUNT set to the numberof records successfully imported to skip thoserows and import the rest of the file. (If you hadbeen doing a CREATE or REPLACE_CREATE orREPLACE, call the second import with INSERToption.)

SQL3222W ...COMMIT of any databasechanges was successful.

Explanation: The COMMIT was successful.

User Response: None necessary if you get thismessage.

SQL3223N The parameter of type pointer toparameter is not specified properly.

Explanation: The parameter of type<parameter> is not specified properly. The typesare one of ″struct sqluimpt_in″, ″structsqluimpt_out″, ″struct sqluexpt_out″, ″structsqluload_in″, ″struct sqluload_out″, ″structsqluunld_in″, or ″struct sqluunld_out″. Thepointer should be either a NULL pointer orshould point to the appropriate structure and itssizeOfStruct field should be initialized to one ofSQLUIMPT_IN_SIZE for struct sqluimpt_in,SQLUIMPT_OUT_SIZE for struct sqluimpt_out,SQLUEXPT_OUT_SIZE for struct sqluexpt_out,SQLULOAD_IN_SIZE for struct sqluload_in,


SQLULOAD_OUT_SIZE for struct sqluload_out,SQLUUNLD_IN_SIZE for struct sqluunld_in orSQLUUNLD_OUT_SIZE for struct sqluunld_out.


User Response: Call the utility again with aproper parameter.

SQL3225N The RESTARTCOUNT value isgreater than the number of rowsin the file. No rows were loaded.

Explanation: The utility was called with aRESTARTCOUNT value which was greater thanthe number of rows in the input file resulting inno rows being loaded into the table/view.

User Response: Ensure that theRESTARTCOUNT value is correct or call theutility again with the REPLACE or INSERToption and a correct RESTARTCOUNT value.

SQL3227W Record token token1 refers to userrecord number token2.

Explanation: An error or warning wasencountered during LOAD, IMPORT or EXPORTof a table. CPU parallelism was greater than 1 atthe time the problem was encountered, and anSQL message was written which identified theuser record with a special unique token. Thismessage serves to map the unique record tokento the record number of the source user data.

User Response: Refer to the original SQLmessage returned for appropriate action.

SQL3228N DEFERRED INDEXING is notsupported for tables withDATALINK columns.

Explanation: The “indexing mode” option forthe load utility was specified as “deferred”. Thisoption is not supported with tables havingDATALINK columns.

User Response: Reissue the load commandspecifying a different indexing mode.

SQL3250N COMPOUND=value is an invalidvalue or is not allowed inconjunction with other importparameters.

Explanation: The COMPOUND=x option wasspecified for the import utility and cannot beprocessed due to one of the following reasons:

v It is invalid when the INSERT_UPDATEoption is used.

v The database being imported to is accessedthrough a server or gateway of a previousrelease.

v The value is not within the allowed range of 1to 100. (On DOS or Windows, the maximumvalue is 7).

User Response: Change the filetmod option tocorrect the usage of COMPOUND=x.

SQL3251N ″number″ more errors occurredduring the import.

Explanation: The utility encountered moreerrors than can be relayed in the sqlca(maximum number is 7) while using theCOMPOUND option. Messages for these errorswill not be printed to the message file.


User Response: If you desire all the errormessages for each row inserted during animport, do not use the COMPOUND option oruse a COMPOUND value less than or equal to 7.

SQL3260N An unexpected error occurredwhen accessing the LDAPdirectory. Error code = error-code.

Explanation: An unexpected error occurredwhen accessing the LDAP directory. Thecommand can not be processed.

User Response: Record the message number(SQLCODE) and the error code. Use theIndependent Trace Facility to obtain the DB2trace. Then contact your IBM servicerepresentative.


SQL3261N The REGISTER LDAP commanddid not complete successfullybecause a required inputparameter was not specified.Reason code = reason-code.

Explanation: The REGISTER LDAP commanddid not complete successfully because a requiredinput parameter was not specified as indicatedby the following reason codes:

1 The Network Id parameter was notspecified.

2 The Partner LU parameter was notspecified.

3 The Transaction Program (TP) nameparameter was not specified.

4 The Mode parameter was not specified.

5 The Netbios NNAME parameter wasnot specified.

6 The TCP/IP hostname parameter wasnot specified.

7 The TCP/IP service name parameterwas not specified.

8 The IPX Address was not specified.

9 The computer name was not specified.

10 The instance name was not specified.

User Response: Re-submit the command withthe required input parameter

SQL3262N The TCP/IP service name name isnot valid.

Explanation: The TCP/IP service namespecified is not valid.

User Response: Ensure that the TCP/IP servicename is configured and reserved in the localetc/services file, then re-submit the command.Alternatively, specify the port number that isassigned to the TCP/IP service name.

SQL3263N The protocol type is notsupported.

Explanation: The protocol type specified is notsupported for the command.

User Response: Re-submit the command usinga supported protocol type.

SQL3264N The DB2 server has not beenregistered in LDAP.

Explanation: The command did not completesuccessfully because the DB2 server had not beenregistered in LDAP.

User Response: Register the DB2 server inLDAP using the REGISTER LDAP command.Then re-submit the command.

SQL3265N An unexpected error occurredduring LDAP authentication.

Explanation: Unable to authenticate the LDAPuser due to unexpected LDAP system error.

User Response: Use the Independent TraceFacility to obtain the DB2 trace. Then contactyour IBM service representative.

SQL3266N The LDAP user password isincorrect.

Explanation: The specified password is not acorrect password for the specified userDistinguished Name (DN).

User Response: Re-submit the command usingthe correct password.

SQL3267N authid does not have sufficientauthority to perform the requestedcommand.

Explanation: The command did not completesuccessfully because the LDAP user did not havesufficient authority to perform the required task.

User Response: Ensure that the LDAP user hasthe authorization to perform the operation.


SQL3268N The LDAP schema is notcompatible with the currentrelease of DB2.

Explanation: The LDAP schema defined at theserver does not contain the definition for the DB2object classes and/or attributes used in thecurrent release of DB2.

User Response: Refer to the AdministrationGuide on how to extend the LDAP schema withDB2 object classes and attributes.

SQL3269N The LDAP server is not available.

Explanation: DB2 was not able to accessinformation in the LDAP directory because theLDAP server was not available.

User Response: Perform the following actions:

1. Ensure that the LDAP server is active.

2. Verify that TCP/IP is configured correctly onyour machine

3. Verify that the DB2LDAPHOST registryvariable is set to the TCP/IP hostname andport number of the LDAP server by runningthe ″db2set DB2LDAPHOST″ command. Ifthe DB2LDAPHOST is not set, you can set itby using the ″db2set DB2LDAPHOST=<host-name>:<port-number>″ command, where<host-name> is the TCP/IP hostname of theLDAP server and <port-number> is theTCP/IP port number of the LDAP server. Thedefault port number is 389.

SQL3270N The LDAP user’s DistinguishedName (DN) is not valid.

Explanation: The LDAP user’s DistinguishedName (DN) is not valid.

User Response: Re-submit the command usinga valid LDAP user’s DN.

SQL3271N The LDAP user’s DistinguishedName (DN) and/or password isnot defined for the current logonuser.

Explanation: When setting user preferencessuch as CLI configuration or DB2 registryvariable, the LDAP user’s DN and passwordmust be defined for the current logon user.

User Response: Refer to the IBM eNetworkLDAP documentation on how to configure theLDAP user’s DN and password for the currentlogon user.

SQL3272N The node node-name was notfound in the LDAP directory.

Explanation: The command did not completesuccessfully because the node node-name was notfound in the LDAP directory.

User Response: Ensure the node name is correctand re-submit the command.

SQL3273N The database database-alias was notfound in the LDAP directory.

Explanation: The command did not completesuccessfully because the database database-aliaswas not found in the LDAP directory.

User Response: Ensure the database name iscorrect and re-submit the command.

SQL3274W The database was createdsuccessfully. However, thedatabase was not cataloged in theLDAP directory. SQLCODE =sqlcode.

Explanation: The database was createdsuccessfully. However, the database could not becataloged in the LDAP directory because therewas an error occurred during the operation.

User Response: Correct the error as indicated inthe SQLCODE. Then catalog the database in theLDAP directory using the CATALOG LDAPDATABASE command.


SQL3275W The database was droppedsuccessfully. However, thedatabase was not uncataloged inthe LDAP directory. SQLCODE =sqlcode.

Explanation: The database was droppedsuccessfully. However, the database could not beuncataloged in the LDAP directory because therewas an error occurred during the operation.

User Response: Correct the error as indicated inthe SQLCODE. Then uncatalog the database inthe LDAP directory using the UNCATALOGLDAP DATABASE command.

SQL3276N Unable to obtain the LDAPnaming context.

Explanation: Unable to query for the LDAPnaming context for the LDAP server.

User Response: Contact your LDAP directoryadministrator to obtain the LDAP namingcontext for the LDAP server that you are using.If you are using IBM eNetwork Directory V2.1,this is the name of the LDAP suffix. Then set thenaming context for the current machine using the″db2set DB2LDAP_BASEDN=<naming-context>″command.

SQL3277N The database database-alias alreadyexists in the LDAP directory.

Explanation: The command did not completesuccessfully because another database of thesame name already exists in the LDAP directory.

User Response: Re-submit the command usinga different alias name.

SQL3278N The node node already exists inthe LDAP directory.

Explanation: The command did not completesuccessfully because another node of the samename already exists in the LDAP directory.

User Response: Re-submit the command usinga different alias name.

SQL3279N The command did not completesuccessfully because LDAP isdisabled.

Explanation: The command did not completesuccessfully because the LDAP support isdisabled on the current machine.

User Response: If the LDAP support isinstalled, enable the LDAP support by runningthe command: ″db2setDB2_ENABLE_LDAP=YES″.

If the LDAP support is not installed, you need torun the setup program and select to install theLDAP support.

SQL3280N The attempt to connect to aDRDA server failed.

Explanation: The attempt to connect to a DRDAserver failed because DB2 Connect is notinstalled on this DB2 client and thegateway-node was not specified when catalogingthis LDAP database.

User Response: Either install DB2 Connect onthis DB2 client or recatalog this LDAP databasewith a valid gateway-node.

SQL3281N The OSTYPE parameter is notvalid.

Explanation: The database server was notregistered in LDAP because the OSTYPEparameter specified was not valid. The OSTYPEparameter describes the operating system type ofthe server.

User Response: Resubmit the commandspecifying an operating system type (OSTYPE)that is supported by DB2.

SQL3282N The supplied credentials are notvalid.

Explanation: Either or both the distinguishedname (DN) of the user and the password thatwere specified were not valid.

User Response: Resubmit the command usingvalid values for both the distinguished name


(DN) of the user and the password.

SQL3283W The database managerconfiguration was updatedsuccessfully. However, theprotocol information was notupdated in the LDAP directory.SQLCODE = sqlcode-value.

Explanation: The database managerconfiguration was updated successfully.However, the protocol information could not beupdated in the LDAP directory because an erroroccurred during the LDAP operation.

User Response: Correct the error as indicated in

the SQLCODE. Then update the protocolinformation in the LDAP directory using theUPDATE LDAP NODE command.

SQL3284N The nodetype parameter is notvalid.

Explanation: The database server was notregistered in LDAP because the nodetypeparameter specified was not valid.

User Response: Use a valid nodetype whenregistering the database server in LDAP. Validvalues for the nodetype parameter are: SERVER,MPP, and DCS.

SQL3300 - SQL3399

SQL3300N The records in the input file arenot in the correct sequence.

Explanation: The records in the worksheetformat (WSF) file are expected to be in ascendingorder (row 1, col 1 ... row 1, col 256; row 2, col 1... row 2, col 256, and so on). Some damage hasoccurred to the WSF file or it was generatedincorrectly, possibly with a level of the Lotusproduct not supported by the database manager.



SQL3301N A BOF record was found in themiddle of the input file.

Explanation: A beginning-of-file (BOF) recordmust be the first record of a worksheet format(WSF) file. It cannot occur at any other locationin the file. Some damage has occurred to theWSF file or it was generated incorrectly, possiblywith a level of the Lotus product not supportedby the database manager.



SQL3302N An EOF record was found beforeany data was imported.

Explanation: The input file is valid, but it didnot contain any usable data to be imported. Thefirst worksheet row is reserved for titleinformation. The second worksheet row is usedfor column labels. Data begins in the third row.


User Response: Regenerate the worksheetformat (WSF) file with valid data in the rowsthat the database manager uses for data.

SQL3303N The file type must be IXF whenusing the CREATE orREPLACE_CREATE keywords inthe Action String parameter.

Explanation: File types other than IXF are notallowed with the CREATE orREPLACE_CREATE keywords in the ActionString (e.g. ″REPLACE into ...″) parameter.


User Response: Change the file type to IXF, oruse INSERT, INSERT_UPDATE or REPLACE.


SQL3304N The table does not exist.

Explanation: The parameters specified on thecommand require that the table exists.



v Resubmit the command with a table name ofan existing table.

v If the input file is a PC/IXF file, resubmit thecommand with the CREATE option.

SQL3305N The table cannot be createdbecause it already exists.

Explanation: The CREATE keyword indicatesthat a new table must be created but a table withthe specified name already exists.


User Response: Either erase the existing tableor use a keyword other than CREATE andresubmit the command.

SQL3306N An SQL error sqlcode occurredwhile inserting a row into thetable.

Explanation: An SQL error occurred whileinserting a row into the table.

If the SQL error is not severe the row will berejected and the utility continues processing;otherwise the utility stops processing.

User Response: Examine other messages in themessage file for details about the actual errorand resubmit the command, if necessary.

SQL3307N The number of columns in theMETHOD parameter does notmatch the number of entries inthe Action String parameter, or acolumn specified in the METHODparameter does not exist.

Explanation: The CREATE orREPLACE_CREATE option was specified on theIMPORT command. Either:

v If the NAMES or POSITIONS methodindicator was specified in the METHODparameter, the number of columns explicitlyspecified in METHOD is not equal to thenumber of columns explicitly specified in theAction String (e.g. ″REPLACE into ...″)parameter.

v If the DEFAULT method indicator wasspecified in the METHOD parameter, thenumber of columns in the PC/IXF file is lessthan the number of columns specified in theAction String parameter.

v One column specified in the METHODparameter does not exist in the PC/IXF file.

The IMPORT utility stops processing. No table iscreated.

User Response: Either correct the columnsspecified in the METHOD and Action Stringparameters or correct the columns specified inthe METHOD parameter.

SQL3308N The code page values of thePC/IXF column name are notcompatible with the code pagevalues for the application. TheFORCEIN parameter was notspecified.

Explanation: The code page values for thecolumn and the application are not compatible.When the FORCEIN parameter is not specified,the data cannot be loaded if the conversion fromthe IXF file code pate to the application codepage is not supported.


User Response: To load data with these codepages, resubmit the command with theFORCEIN option.

SQL3309N Column name in the PC/IXF file isdefined as a graphic column. TheFORCEIN parameter was notspecified.

Explanation: During the load of a PC/IXF file, agraphic data column was encountered. Because


the FORCEIN parameter was not used, the datacannot be loaded.


User Response: If you want to load the datawith the graphic data, resubmit the commandwith the FORCEIN parameter.

SQL3310N Column name in the PC/IXF file isnot valid.

Explanation: The CREATE orREPLACE_CREATE option was specified on theIMPORT command. A column with an invalid Crecord was found while importing the PC/IXFfile.

The IMPORT utility stops processing. The table isnot created.

User Response: Verify the column definitioninformation in the input file.

SQL3313N The disk is full. Processing wasended.

Explanation: The disk or diskette is full. Duringthe export to a PC/IXF file, either the PC/IXFdata file is on a fixed disk, or the PC/IXF datafile and the database are on the same drive, orthe PC/IXF data file and the message file are onthe same drive.

The EXPORT utility stops processing. Theexported data is not complete.

User Response: Provide more space on the diskor diskette or specify that the data file be locatedon a different drive than the database or themessage file and resubmit the command.

SQL3314N The date and time fields in an Arecord do not match the date andtime fields in the H record.

Explanation: During the load of a PC/IXF file,an A record was found in the PC/IXF file, thatcontained run identification information (in thedate and time fields) that differs from the runidentification information in the header (H)record. This action does not apply to an A recordat the start of a continuation file.

The input file has probably been damaged.


User Response: Re-create the damaged file, orrepair the damaged file to recover as much dataas possible. Resubmit the command.

SQL3315N The volume fields in an A recordof subtype C are not valid.

Explanation: During the load of a PC/IXF filethat was created by Database Services, an Arecord was found in the PC/IXF file, thatcontained volume information (in the volumefields) that is not valid.

The input file has probably been damaged.


User Response: Re-create the damaged file, orrepair the damaged file to recover as much dataas possible. Resubmit the command.

SQL3316N An I/O error occurred whileclosing part of the input file.

Explanation: During the load of a multiple partPC/IXF file, an I/O error occurred while thesystem was closing one of the files that make upthe input PC/IXF file. This action does not applyto the last file in the group of files that make upthe PC/IXF file.



SQL3317N The string pointed to by thefiletmod parameter containsconflicting information.

Explanation: The filetmod string defines thegeneration and product family for the outputWSF file. More than one generation or productfamily was defined in the string.

The utility stops processing. The output file isnot created.

User Response: Change the filetmod string todefine only one generation and product family.Resubmit the command.


SQL3318N There are duplicate keywords inthe filetmod parameter.

Explanation: A COLDEL, CHARDEL, orDECPT keyword appears more than once in thefiletmod parameter. This condition may arisewhile using delimited ASCII (DEL) files.

The utility stops processing. No data is loaded orexported.


SQL3319N An SQL error sqlcode occurredwhile creating the table.

Explanation: An SQL error occurred whilecreating the table.

The IMPORT utility stops processing. The tablewas not created. No data was imported.


SQL3320N There is no delimiter or decimalpoint character after a keyword inthe filetmod parameter.

Explanation: A COLDEL, CHARDEL, orDECPT keyword is located at the very end of thefiletmod parameter. There is no delimiter ordecimal point character following the keyword.This condition may arise while using delimitedASCII (DEL) files.

The utility stops processing. No data is loaded orexported.


SQL3321C Data was not imported into thedatabase because the log was full.Recovery was not successful.SQLCODE sqlcode was returned.

Explanation: The IMPORT utility could notinsert a row of data into the database becausethe database transaction log was full. All work

was committed, but the utility could not insertthe row, because the database transaction logremains full.

The utility stops processing. All previous changeswere committed, but the current row was notimported.

User Response: Check the amount of spaceremaining on the filesystem containing yourdatabase files. Consider increasing the maximumlog size in the database configuration file.

SQL3322N An operating system semaphoreerror occurred.

Explanation: An error occurred in the wait/postsemaphores.

The utility stops processing. For the EXPORTutility, data may be incomplete on the media. Forthe IMPORT utility, data not already committedis rolled back.

User Response: Stop and restart DB2 andresubmit the utility.

SQL3324N Column name has a type of typewhich is not recognized.

Explanation: A column of data returned by theSQL statement is not supported.

Federated system users: The data type of thedata that you want is not supported by either thefederated server or the data source that you wantto access.

User Response: Correct the error and retry thecommand.

Federated system users: Specify a supported datatype and resubmit the program.

SQL3325W All the columns in rowrow-number have NULL values; therow will not be included in theWSF data file.

Explanation: When you are doing an export ofa WSF file and the SELECT statement results in arow of all NULL values, the row will not beadded to the WSF file. The total number of rows


specified in message SQL3105N is the number ofrows resulting from the SELECT statement andnot the number of rows in the WSF file.

The command continues processing.

User Response: No action required. This is aninformational message.

SQL3326N The column list following thetable name in the Action Stringparameter is invalid.

Explanation: When you call IMPORT or LOADwith an Action String (e.g. ″REPLACE into ...″)parameter which contains a column list after thetable name, this message will result if it isinvalid. For example, the following Action Stringparameters will fail:

insert into tablea()no columns within the parenthesis

insert into tablea(two words)invalid column name

insert into tablea(grant.col1)column name should not be qualified

insert into tablea(x1234567890123456789)column name too long

insert into tablea(,col1,col2)missing column name

The command cannot continue.

User Response: Change the Action Stringparameter with a valid column list and call theutility again.

SQL3327N A system error occurred (reasoncode1 = “ reason-code-1 and reasoncode2 = reason-code-2).

Explanation: A system error occurred duringprocessing.


User Response: Record all error informationfrom the SQLCA, if possible. Retain the messagefile. Terminate all applications using thedatabase. Reboot the system. Restart the

database. Try the command again.

If sufficient memory resources exist and theproblem continues, invoke the Independent TraceFacility at the operating system commandprompt.

SQL3330W In row row-number a characterfield has an odd length but itstarget database column is agraphic column. The row was notloaded.

Explanation: Only even length character fieldscan be loaded into graphic database columns.


User Response: Either load the data to a newtable using the CREATE option in the IMPORTcommand or do not load this column into thistable.

SQL3331C The permission setting of a file(or directory) does not allow thespecified access.

Explanation: This may accompany another errormessage. It indicates an attempt was made to getaccess to a file or directory in a way that isincompatible with the attributes of the file. Oneof the following may be the source of thedifficulty:

v Opening a file for writing on a read-onlydevice

v Opening a file for writing on a read-only file

v Opening a directory instead of a file

v Encountering a locking or sharing violation.


User Response: Retry the utility when the file isnot in use, or retry the utility directing theoutput to a path and file that allows writing.

SQL3332C The maximum number of openfiles has been reached.

Explanation: This message may accompanyanother error message. It indicates that the


maximum number of open files has beenreached.


User Response: Terminate other applications toreduce the number of files open and retry theutility.

SQL3333C The file or directory does notexist.

Explanation: This message may accompanyanother error message. It indicates that a file ordirectory to be accessed does not exist or cannotbe found.


User Response: Resubmit the command withthe correct file name, including a valid path.

SQL3334C There is not enough storageavailable.

Explanation: This message may accompanyanother error message. It indicates there is notenough storage available to open the file.





SQL3335C The file system is full.

Explanation: This message may accompanyanother error message. It indicates there is noavailable space for writing on the device.


User Response: To make space available on thedevice, delete unneeded files or direct the outputdata to a device with space available.

SQL3337N An I/O error occurred whilewriting data to the server.

Explanation: An I/O error has occurred whileattempting to write data to a temporary file onthe server (temporary files are created in the tmpdirectory under the sqllib directory for theinstance of the database manager). The filesystem on the server may be full.

The utility stops processing. The database isunchanged.

User Response: Contact the SystemAdministrator for the server to make spaceavailable on the server, and resubmit thecommand.

SQL3338N An I/O error occurred reading atemporary message file on theserver.

Explanation: A system I/O error has occurredwhile attempting to read the temporary messagefile on the server.

The IMPORT operation is complete; however, themessage file on the database client system maybe empty or incomplete.

User Response: Query the remote database todetermine if the utility operation was successful.

SQL3340N Unable to perform a load withconcurrent read access to thetable. Reason code = reason-code.

Explanation: The ALLOW READ ACCESSoption of the load command is not supported inthe following cases as specified in the reason-code:

1. When using LOAD REPLACE.

2. When using INDEXING MODE DEFERRED.

3. When the target table is in the CHECKPENDING state and is not in the READACCESS ONLY state.

4. When the indexes are marked invalid.

5. When using LOAD TERMINATE or LOADRESTART on a load that did not use theALLOW READ ACCESS option.

User Response: Resubmit the command using


the ALLOW NO ACCESS option.

SQL3341N Invalid table space name providedwith the USE option. Reason code= reason-code.

Explanation: Only system temporary tablespaces can be used for rebuilding the indexes ina table space other than the index table space.The page size of the system temporary tablespace must match the page size of the indextable space.

User Response: Resubmit the command with atable space name referring to a system temporarytable space with the correct page size. Thereason-code describes the failure as follows:

1. Table space name in USE clause not found.

2. Table space must be a system temporary tablespace.

3. Page size in system temporary table spacemust match page size in index table space.

SQL3346W USE TablespaceName optionignored. Reason code = reason-code.

Explanation: USE TablespaceName is only validfor ALLOW READ ACCESS loads withINDEXING MODE REBUILD. If INDEXINGMODE AUTOSELECT is specified, load will usethe alternate table space only if it chooses torebuild the indexes.

User Response: Refer to the reason code for anexplanation.

1. Indexing mode incompatible with USETablespaceName option.

2. Table has no indexes.

3. LOAD TERMINATE does not need to use aseparate table space.

4. USE TablespaceName is only supported forALLOW READ ACCESS loads.

SQL3400 - SQL3499

SQL3400N The method specified inMETHOD is not valid forNon-Delimited ASCII files. Itmust be ’L’ for locations.

Explanation: When loading from anon-delimited ASCII file, columns must beselected by locations in the file.


User Response: Resubmit the command with avalid set of locations for the columns in thesource file.

SQL3401N The method specified inMETHOD is not valid for anyfiletype.

Explanation: The method for selecting columnsin the file is not a value allowed for any filetype.Choose one of the following method indicators:

v P for positions

v N for names

v L for locations

v D for default

Further restrictions are based on filetype.


User Response: Resubmit the command with avalid method indicator.

SQL3402N A beginning-ending location pairwith both values zero wasspecified for non-nullable columnname.

Explanation: A location pair with both thebeginning and the ending location set to zerowas specified for the indicated column, but thecolumn is not nullable.




SQL3403N The beginning-ending locationpair for inserting into columnname is not valid.

Explanation: The field specification for locatingthe input data for the indicated database columnwithin the input non-delimited ASCII file is notvalid. The field specification has one of thefollowing errors:

v The beginning location is less than zero.

v The ending location is less than zero.

v The ending location is less than the beginninglocation.



SQL3404N The beginning-ending locationpair for inserting into columnname is not valid for a number.

Explanation: The field specification for locatingthe data for the indicated database columnwithin the input non-delimited ASCII file is notvalid. The location pair defines a field longerthan 50 bytes.



SQL3405N The beginning-ending locationpair for inserting into columnname is not valid for a date.

Explanation: The field specification for locatingdata for the indicated database column withinthe non-delimited ASCII file is not valid. Thelocation pair defines a field length that is notvalid for an external representation of a date.



SQL3406N The beginning-ending locationpair for inserting into columnname is not valid for a time.

Explanation: The field specification for locatingthe data in the indicated database column withinthe input non-delimited ASCII file is not valid.The location pair defines a field length that is notvalid for an external representation of a time.



SQL3407N The beginning-ending locationpair for inserting into columnname is not valid for a timestamp.

Explanation: The field specification for locatingthe data for the indicated database columnwithin the input non-delimited ASCII file is notvalid. The location pair defines a field length thatis not valid for an external representation of atimestamp.


User Response: Resubmit the command with avalid set of locations for the columns in the file.

SQL3408W The beginning-ending locationpair for inserting into columnname defines a field larger thanthe target column. Data may betruncated.

Explanation: The field specification forobtaining data from the input non-delimitedASCII file defines a field larger than the size (ormaximum size) of the target database column.

The utility continues processing. Truncationoccurs when necessary.



SQL3409W The beginning-ending locationpair for inserting into columnname defines a field shorter thanthe target fixed-length column.Data will be padded.

Explanation: The indicated database column isa fixed-length column. The field specification forobtaining data from the input non-delimitedASCII file defines a field smaller than the size ofthe target database column.

The utility continues processing. Values input tothe indicated database column are padded withspaces as necessary, on the right.


SQL3410N The beginning-ending locationpair for inserting into columnname is not valid for a graphiccolumn.

Explanation: The field specification for locatingthe input data in the ASCII file that is to beinserted into the indicated database columndefines a field with an odd number of bytes.



SQL3411W The field value in row row-numberand column column-number is notvalid for a graphic column. A nullwas inserted.

Explanation: The value in the field indicated isnot an acceptable graphic column value. Thevalue may contain an odd number of bytes. ForDEL files, the value of the column numberspecifies a field in the indicated row. For ASCIIfiles, the value of the column number specifiesthe byte location within the row where the valuebegins.

The row is not inserted.

User Response: If a null is not acceptable,correct the input file and resubmit the command,or edit the data in the table.

SQL3412W The field value in row row-numberand column column-number is notvalid for a graphic column but thetarget column is not nullable. Therow was not inserted.

Explanation: The value in the field indicated isnot an acceptable graphic column value. Thevalue may contain an odd number of bytes. Anull cannot be inserted because the targetcolumn is not nullable. For DEL files, the valueof the column number specifies a field in theindicated row. For ASCII files, the value of thecolumn number specifies the byte location withinthe row where the value begins.

The row is not inserted.

User Response: No action is required. If therow is necessary, correct the input file andresubmit the command, or edit the data in thetable.

SQL3413W The field value in row row-numberand column column-number is tooshort for the target column. A nullwas inserted.

Explanation: The value in the specified field isnot acceptable because it is too short for thetarget column. The value of the column numberspecifies the byte location within the row wherethe field begins.

A null value is inserted.

User Response: No action is required. If a nullis not acceptable, correct the inner field andresubmit the command, or edit the data in thetable.

SQL3414N The temporary file filename couldnot be found.

Explanation: At the end of the load phase atemporary file is created with informationnecessary to restart the load. If the load isinterrupted before this point, this file is notcreated.

This message indicates that this file could not befound during load restart.


The utility stops.

User Response: Depending on where theinterrupt occurred, it may be possible to restartthe load at the build phase.

SQL3415W Failed to convert the field valuein row row-number and columncolumn-number from the codepageof the input data file to thecodepage of the database. A nullvalue was loaded.

Explanation: The value in the field indicatedcannot be converted from the codepage of theinput data file to the codepage of the database.

User Response: If a null value is not acceptable,correct the input data file and resubmit the

command, or edit the data in the table.

SQL3416W Failed to convert the field valuein row row-number and columncolumn-number from the codepageof the input data file to thecodepage of the database. Therow was not loaded.

Explanation: The value in the field indicatedcannot be converted from the codepage of theinput data file to the codepage of the database.

User Response: No action is required. If therow is necessary, correct the input data file andresubmit the command, or edit the data in thetable.

SQL3500 - SQL3599

SQL3500W The utility is beginning the phasephase at time timestamp.

Explanation: This is an informational messageindicating that a phase is about to begin and thatthe previous phase has ended. The phases are (inorder of appearance):

v LOAD

v BUILD

v DELETE

During the LOAD phase, data is loaded intoyour table. If there are any indexes to be built,BUILD phase will follow the LOAD phase. Ifthere were any duplicate keys found for a uniqueindex, the DELETE phase will follow the BUILDphase.

If the LOAD is terminated before the end of theLOAD, you need to know the phase at whichyou should restart the LOAD.


SQL3501W The table space(s) in which thetable resides will not be placed inbackup pending state sinceforward recovery is disabled forthe database.

Explanation: COPY NO was specified on theinvocation of LOAD which results in the tablespace(s) in which the table resides being placedinto backup pending state unless forwardrecovery is disabled for the database.

The utility continues.


SQL3502N The utility has encounterednumber warnings which exceedsthe total number of warningsallowed.

Explanation: The number of warnings issuedduring the command has exceeded the totalnumber of warnings that the user specified atinvocation of the utility.

The utility terminates.

User Response: Ensure that the correct data isbeing loaded with the appropriate options or


increase the number of warnings allowed.Resubmit the command.

SQL3503W The utility has loaded numberrows which equals the total countspecified by the user.

Explanation: The number of rows loaded hasequaled the total number of rows that the userspecified at invocation of the utility.

The utility has successfully completed.

User Response: No response required.

SQL3504W A consistency point is beingestablished.

Explanation: Consistency points will beestablished at times other than the regularinterval specified in the SAVECOUNT parameterat invocation when:

v the threshold for the amount of meta-data keptin memory or in temporary files has beenreached.

v A device error occurred for the copy imageand the load must terminate.

User Response: If the LOAD continues afterthis message, no action is required. If the LOADterminates, it can be restarted after all errors arecorrected (such as activating a device ordecreasing the interval at which consistencypoints are to be established).

SQL3505N The length specified in thefiletmod for the RECLEN optionis not in the valid range of 1 to32767.

Explanation: In the filetmod parameter, theRECLEN option was specified for an ASC file.The length specified is not valid.

User Response: Correct the length specified andresubmit the command.

SQL3506W The value specified in the nullindicator in row row-number andcolumn column-number is notvalid. A value of ’N’ will beassumed.

Explanation: For ASC files, a null indicatorcolumn can be specified for each data columnand should contain either a ’Y’ or a ’N’. A ’Y’indicates that the column is a null value and a’N’ indicates that the column contains data. Ifneither of these values are in the null indicatorcolumn, it is assumed to be a ’N’ and data willbe loaded into the column.

User Response: If the data or the null indicatorare incorrect, correct the input file and resubmitthe command.

SQL3507N The column number specified fora null indicator is not in the validrange of 0 to 32767 or the nullindicator parameter is not valid.

Explanation: In the null_ind parameter, columnsfor null indicators were specified for an ASC filebut one of the columns is not valid or the pointerpassed in for the null indicators is not valid.

User Response: Correct the parameter andresubmit the command.

SQL3508N Error in accessing a file or path oftype file-type during load or loadquery. Reason code: reason-code.Path: path/file.

Explanation: An error occurred while trying toaccess a file during load or load queryprocessing. The utility stops processing.

User Response: If doing a load and the tablespace is not in load pending state, correct theproblem and invoke the load utility again. If thetable space is in load pending state, then invokethe load utility in RESTART or REPLACE mode,or restore a backup of the table space(s). Thestate of the table space can be determined usingthe LIST TABLESPACES command.

The following is a list of reason codes:


1 Unable to open the file.

This could be caused by an incorrect filename or insufficient authority to accessthe file/directory. Correct the problemand either restart or rerun the load.

2 Unable to read/scan the file.

This could be the result of a hardwareerror. If the error is a hardware error,take the appropriate action and restartor rerun the load.

3 Unable to write to or change size of thefile.

This could be the result of a disk fullcondition or a hardware error. Refer tothe file type list below and either ensurethere is enough space to run the load orspecify a different location to be used.Restart or rerun the load. If the error isa hardware error, take the appropriateaction an restart or rerun the load.

4 The file contains invalid data.

A file required by the load containsincorrect data. See the action describedfor TEMPFILES_PATH.

5 Unable to close the file.

If the load cannot be restarted or rerun,contact your IBM service representative.

6 Unable to delete the file.

If the load cannot be restarted or rerun,contact your IBM service representative.

7 Parameter specified incorrectly. Refer tothe list of file types to determine theparameter in error and rerun the loadwith a valid parameter.

The following is a list of file types:

SORTDIRECTORYEnsure that the workdirectory parameteris specified properly. There must beenough combined space in all thedirectories to hold twice the size of theindex keys for the loaded data. For loadinsert and load restart there must also

be room for twice the size of the indexkeys of the existing data in the table.

MSGFILEEnsure that the messagefile parameter isspecified properly. There must beenough disk space to write out themessages that occur during the load.

If this is a load query, ensure that thelocal message file parameter is NOT thesame as the messagefile parameter usedfor the load whose status is beingqueried.

TEMPFILES_PATHEnsure that the tempfiles pathparameter is specified properly. See theData Movement Utilities Guide andReference for more details on thisparameter.

SQL3509W The utility has deleted numberrows from the table.

Explanation: When a table with a unique indexis loaded, rows causing violation of uniquenessof an index will be deleted from the table duringthe delete phase. This message providesinformation on how many rows have beendeleted.


SQL3510N The working directory for the sortphase cannot be accessed.

Explanation: One or more of the specifiedworking directories for the sort phase either doesnot exist or has no read/write permission.

User Response: Ensure that the specifiedworking directories exist and the read/writepermission is setup correctly and resubmit thecommand.


SQL3511W The file named in row row-numberand column column-number cannotbe found. A null was loaded.

Explanation: The filename in the specified fieldcannot be found. There may be a data typemismatch.




SQL3512W The file named in row row-numberand column column-number cannotbe found, but the target column isnot nullable. The row was notloaded.

Explanation: The filename in the specified fieldcannot be found. A null cannot be loadedbecause the output column in the table is notnullable.




SQL3513N The codepage of the file does notmatch the codepage of thedatabase. The file cannot beloaded.

Explanation: DB2CS files cannot be loaded intoa database with a codepage that differs from theoriginal database.

User Response: Change the codepage of thedatabase and resubmit the command or useanother filetype (such as PC/IXF) to move yourdata from the original database to the newdatabase.

SQL3514N A utility system error occurred.Function code: function. Reasoncode: reason-code. Error code:error-code.

Explanation: A system error occurred duringdatabase utility processing.

User Response: Different actions are requireddepending on the value of function.

The possible function codes are:

v 1 - An error occurred while Load was sorting.

Try to restart the load. If the error persists,provide the function, reason code and errorcode to your technical service representative.

v 2 - An error occurred using the vendor sortutility.

Try the load again using the DB2Client/Server sort utility instead of the vendorsort. To do this, reset the Profile Registry valueat the server to blank. You may have to restartthe Database Manager in order to pick up thenew Profile Registry value. If the errorpersists, provide the function, reason code anderror code to your vendor sort technicalservice representative.

SQL3515W The utility has finished the phasephase at time timestamp.

Explanation: This is an informational messageindicating that a phase has finished. The phasesare (in order of appearance):

v LOAD

v BUILD

v DELETE



SQL3516N The utility could not restart theload as specified.

Explanation: The Load Utility detecteddiscrepancies in the last consistency pointperformed by Load before failure occurred. Thiscondition might be caused either by a systemerror or an invalid log file.

User Response: Restart the Load at the Buildphase, to bring the table to a consistent state andcreate indexes (if applicable), or perform Loadwith the REPLACE option.

SQL3517N An unexpected record was readfrom the input source.

Explanation: The utility has encountered arecord that is in a format that is not valid. Thesource may have been corrupted when copiedfrom the original source.

Processing terminates.

User Response: Copy the record from theoriginal source in binary and restart the LOAD.

SQL3518N The data in the source is notcompatible to the table to beloaded.

Explanation: The source cannot be used to loadthis table because one of the following reasons:

v the table definition does not match the tabledefinition of the source.

v the source was created on a different platformthan the table that is being loaded.

v the source was created from a table that had adifferent codepage from the table that is beingloaded.

User Response: Ensure that both the table andsource are correctly specified. If you want to loaddata from a table with a different definition orfrom a different platform or codepage, useanother filetype such as IXF or DEL.

SQL3519W Begin Load Consistency Point.Input record count = count.

Explanation: The Load Utility is about toattempt to perform a Consistency Point tocommit the table data that has already beenloaded.

User Response: If message SQL3520W is notprinted immediately after this message, then theConsistency Point failed. The Load will have tobe restarted at the Build phase, to ensure that thetable is brought back to a consistent state and allindexes (if any) created. It will then be possibleto check which records have been loaded. Startthe Load again with a RESTARTCOUNT set tothe number of records successfully loaded to skipthose rows and load the rest of the file.

If this message is followed by messagesSQL3520W, then this message is informationalonly and no response is required.

SQL3520W Load Consistency Point wassuccessful.

Explanation: The Consistency Point performedby Load was successful.

User Response: This is an informationalmessage only. No response is required.

SQL3521N The input source file sequence-numwas not provided.

Explanation: A load was invoked with multipleinput files but not all the files were provided. Forthe DB2CS filetype, all the input source files thatwere created originally must be provided. Forthe IXF filetype, all the input source files must beprovided in the correct order.

The utility terminates.

User Response: Restart the utility providing allthe input source files and setting theRESTARTCOUNT appropriately for the data thatwas already loaded.


SQL3522N A copy target cannot be providedwhen both log retain and userexits are disabled.

Explanation: A copy target has been specifiedon invocation of load for a database that hasboth log retain and user exits disabled. Copytargets are not valid for such databases.


User Response: Verify that the database shouldhave log retain and user exits disabled andinvoke the load without specifying a copy target.

SQL3523W There are no messages to beretrieved from the message file.Reason code: rc.

Explanation: No messages are returned from aquery of the LOAD temporary message file. Thepossible return codes are:

1 No LOAD temporary message fileexists.

2 There are no messages in the LOADtemporary message file.

User Response: Ensure that a valid table namehas been specified. If the table name is specifiedcorrectly and messages are expected, check thedatabase monitor to verify that the utility isactive and it is not waiting for resources such aslocks. Note that the LOAD temporary messagefile will not be created until the LOAD utility isin progress and it will be deleted after thecompletion of the LOAD utility.

SQL3524N Option option has an invalid valueof value.

Explanation: The value provided must be aninteger value. Its range for each option is asfollows:

1. TOTALFREESPACE: the value must be in therange of 0 to 100, and is interpreted as apercentage of the total pages in the table thatare to be appended to the end of the table asfree space.

2. PAGEFREESPACE: the value must be in therange of 0 to 100, and is interpreted as apercentage of each data page that is to be leftas free space.

3. INDEXFREESPACE: the value must be in therange of 0 to 99, and is interpreted as apercentage of each index page that is to beleft as free space when loading indexes.


User Response: Correct the value and resubmitthe command.

SQL3525N The option-1 option isincompatible with the option-2option.

Explanation: Incompatible options have beenprovided to the utility.

User Response: Remove or modify one of theoptions and resubmit the command. See theCommand Reference for more information onvalid options.

SQL3526N The modifier clause clause isinconsistent with the current loadoptions. Reason code: reason-code.

Explanation: The load file type mode (modifier)indicated, is incompatible with yourload/import/export command. This is because ofone of the following reasons:

1. The current option requires you to specify theRECLEN and NOEOFCHAR file typemodifiers. One or more of these options aremissing from your command.

2. The indicated option, such as DEL or ASC, isinconsistent with the format of the input oroutput data file.

3. Generated or identity related file typemodifiers have been specified but the targettable contains no such columns.

4. When a pre-Version 8 client is used, it is notpossible to load a table having a non-identitygenerated column in a unique index, unlessthe column is specified in the INCLUDEclause of the CREATE INDEX statement or


the GENERATEDOVERRIDE file typemodifier is used. For pre-Version 8 clients, itis also necessary to specify theGENERATEDOVERRIDE file type modifierwhen loading a table that has a non-identitygenerated column in its ORGANIZE BYclause.

5. The IDENTITYOVERRIDE file type modifiercannot be used when loading a table with aGENERATED BY DEFAULT identity column.

6. The LOBSINFILE file type modifier cannot bespecified in a partitioned database load whena generated column, that is part of thepartitioning key, is defined in terms of a longfield or LOB column.

7. Use of the GENERATEDMISSING orIDENTITYMISSING modifier in the currentload or import command would result in allcolumns in the table being excluded from theload operation.

User Response: Check the requirements of theoption you are using. Reissue the commandusing modifier clauses (file type modes) andutility options that are consistent.

SQL3527N The number specified in theFILETMOD parameter for theCODEPAGE option is not valid.

Explanation: In the FILETMOD parameter, theCODEPAGE option was invalid.

User Response: Correct the codepage numberand resubmit the command.

SQL3528W The delimiter (column delimiter,string delimiter, or decimal point)specified in the CLP commandmay get translated from theapplication codepage to thedatabase codepage.

Explanation: When a CLP command is sentfrom the client to the server, it may gettranslated from the codepage of client to thecodepage of server, if they are different.

User Response: To ensure that delimiters arenot converted, they should be specified in hexformat.

SQL3529N The operation-name operationencountered the unsupported datatype data-type in columncolumn-number.

Explanation: The operation-name operation doesnot support data type data-type found in columncolumn-number.

User Response: Please check your tabledefinition and the Data Movement Guide forsupported data types.

SQL3530I The Load Query utility ismonitoring agenttype progress onpartition partitionnumber.

Explanation: The Load Query utility wasinvoked in an MPP environment.


SQL3531I A LOAD RESTART has occurred.

Explanation: The RESTART option was givenfor the Load currently being queried.


SQL3532I The Load utility is currently inthe phase phase.

Explanation: This is an informational messageindicating the phase of the Load currently beingqueried.


SQL3533I The Load utility is currentlybuilding index number of number.

Explanation: This is an informational messagereturned if the Load currently being queried is inthe BUILD phase.



SQL3534I The Load DELETE phase isapproximately number percentcomplete.

Explanation: This is an informational messagereturned if the Load currently being queried is inthe DELETE phase.


SQL3535W The LOAD command parameterparameter-name is no longersupported; its value will beignored by the LOAD utility.

Explanation: Your LOAD command contains aparameter that is no longer supported.

User Response: Please refer to the DB2documentation for information on temporary sortspace for LOAD and suggestions related toLOAD performance tuning.

SQL3536N System temporary table spacetable-space-name is full.

Explanation: The LOAD utility has encountereda table space full condition while sorting indexkeys.

User Response: Ensure that there is enoughspace allocated to the system temporary tablespace table-space-name, at least two times the totalsize of the indexes being built. Restart the LOADutility.

SQL3537N Sort memory could not beallocated during the execution ofthe LOAD utility.

Explanation: Insufficient process virtualmemory is available to the LOAD utility for sortprocessing.

User Response: Terminate the application onreceipt of this message. Ensure there is enoughvirtual memory available for sort processing.

Possible solutions include:

v Disconnect all applications from the databaseand decrease the size of the sort heap

parameter (sortheap) in the correspondingdatabase configuration file.

v Remove background processes and/orterminate other currently executingapplications.

v Increase the amount of virtual memoryavailable.

SQL3538N The LOAD QUERY utility failedbecause multiple LOADs areusing the same temporary filespath.

Explanation: At least one other LOAD wasinvoked using the same TEMPFILES PATH asthe queried LOAD and is still in progress. TheLOAD QUERY utility cannot uniquely determinewhich LOAD to query.

User Response: Use the TABLE parameter ofLOAD QUERY instead.

SQL3539N LOAD RESTART cannot proceedbecause LOAD TERMINATE hasbeen attempted at least once.

Explanation: LOAD TERMINATE can only befollowed by LOAD TERMINATE.

User Response: User can proceed with LOADTERMINATE only.

SQL3550W The field value in row row-numberand column column-number is notNULL, but the target column hasbeen defined as GENERATEDALWAYS.

Explanation: A non NULL field value wasencountered in the input file. Because the targetcolumn is of type GENERATED ALWAYS, thevalue cannot be loaded. The column numberspecifies the field within the row of the missingdata.

User Response: For LOAD, an explicit, nonNULL field value can be loaded into aGENERATED ALWAYS identity column only ifthe identityoverride file type modifier is used.For non-identity GENERATED ALWAYScolumns, the generatedoverride file type modifier


can be used to load explicit, non NULL valuesinto a row. If using these modifiers is notappropriate, the field value must be replacedwith a NULL if LOAD is to accept the row.

For IMPORT there is no way to override aGENERATED ALWAYS column. The field valuemust be removed and replaced with a NULL ifthe utility is to accept the row.

SQL3551W The table contains at least oneGENERATED ALWAYS columnthat the utility will override.

Explanation: An “override” file type modifier(for example, IDENTITYOVERRIDE or

GENERATEDOVERRIDE) has been specified.

For IDENTITYOVERRIDE, this may violate theuniqueness property of an identity columndefined as GENERATED ALWAYS.

For GENERATEDOVERRIDE, this may result ina non-identity GENERATED ALWAYS columncontaining a value that does not correspond toits column definition.


SQL3600 - SQL3699

SQL3600N The IMMEDIATE CHECKEDoption of the SET INTEGRITYstatement is not valid since thetable table-name is a usermaintained materialized querytable or not in the check pendingstate.

Explanation: The data is checked for constraintviolations only if the table has been placed in thecheck pending state, is not a user maintainedmaterialized query table, or if one of its ancestorsthat has been placed into the check pending stateusing the CASCADE DEFERRED option is alsoin the invocation list and all intermediateancestors are also in the list.

User Response:

1. Use the SET INTEGRITY statement with theOFF option to place a table in the checkpending state.

2. Use the IMMEDIATE UNCHECKED optionfor a user maintained materialized querytable.

3. Include an ancestor of the table to the list oftables to be checked. The ancestor must be inthe check pending state and all intermediateancestors must also be in the list.

4. If the table is in the no data movement mode,specify the SET INTEGRITY...FULL ACCESSstatement to force the table into the full

access mode. Note that all dependentimmediate materialized query tables thatremain in the check pending state are alsoforced to be fully recomputed in subsequentREFRESH statement, and all dependentimmediate staging tables that remain in thecheck pending state can no longer be used torefresh their dependent materialized querytables.

sqlcode: -3600

sqlstate: 51027

SQL3601W The statement caused one or moretables to automatically be placedin the check pending state.

Explanation: Dependent tables, descendenttables, descendent refresh immediatematerialized query tables or staging tables wereput in the check pending state. This is done toenforce referential integrity constraints or toenforce the data relationship between the basetable, the dependent materialized query tables,and the staging tables.

User Response: To validate the integrity for allthe dependent tables, descendent tables,descendent refresh immediate materialized querytables, or staging tables, execute the SETINTEGRITY...IMMEDIATE CHECKED statement


for these tables. To determine which tables are inthe check pending state, issue the followingquery:

SELECT TABSCHEMA, TABNAME, STATUSFROM SYSCAT.TABLESWHERE STATUS = ’C’

sqlcode: +3601

sqlstate: 01586

SQL3602W Check data processing foundconstraint violations and movedthem to exception tables.

Explanation: There are rows that violateconstraints that were specified to be checked bythe SET INTEGRITY statement execution. Thesewere moved to exceptions tables.

User Response: Check the exception tables forrows that violate constraints. The rows have beendeleted from the original table but can becorrected and transferred back from theexception tables.

sqlcode: +3602

sqlstate: 01603

SQL3603N Check data processing throughthe SET INTEGRITY statementhas found integrity violationinvolving a constraint with namename.

Explanation: A row has been found to violate aconstraint defined on a table specified to bechecked by the SET INTEGRITY statement. Thename name is either a constraint name or thename of a generated column.

User Response: The row has not been deletedfrom the table since the FOR EXCEPTION optionwas not used.

It is advisable to execute the SET INTEGRITYstatement using the FOR EXCEPTION optionwhen checking the data. The data may becorrected with the information from theexception table(s).

sqlcode: -3603

sqlstate: 23514

SQL3604N Exception table excp-table-namecorresponding to table table-namein the SET INTEGRITY statementor LOAD utility does not have theproper structure, has been definedwith unique indexes, constraints,generated columns, or triggers, oris in the check pending stateitself.

Explanation: The exception table correspondingto a table must have its definition similar to thatof the original table. Optional columns for theutility are as specified in the relevant section ofthe documentation describing the exceptiontables. There may not be any generated columnsin the exception table. There must not be anyconstraints or triggers defined on the exceptiontable. The exception table itself should not be inthe check pending state.

User Response: Create the exception table asindicated in the relevant section of thedocumentation and re-run the statement orutility.

sqlcode: -3604

sqlstate: 428A5

SQL3605N Table table-name named in the SETINTEGRITY statement is eithernot listed to be checked or is anexception table specified morethan once.

Explanation: When the FOR EXCEPTIONclause is specified in the SET INTEGRITYstatement, this error could be caused by one ofthe following :

v The table is missing from the list of tables tobe checked

v The table to be checked is the same as anexception table

v The exception table is specified for more thanone table to be checked


User Response: Correct the table names andexecute the command again.

sqlcode: -3605

sqlstate: 428A6

SQL3606N There is a mismatch in thenumber of tables being checkedand in the number of exceptiontables specified in the SETINTEGRITY statement.

Explanation: There must be a one-to-onecorrespondence between the exception tables andthe tables that are not materialized query tablesor staging tables provided in the invocation list.The tables in the invocation list that arematerialized query tables or staging tables mustnot have corresponding exception tables.

User Response: Create the missing exceptiontable for the table that is not a materializedquery table or staging table if it does not alreadyexist and specify it in the invocation list in orderto execute the command again. Do not specifyexception tables for materialized query tablesand staging tables.

sqlcode: -3606

sqlstate: 428A7

SQL3608N Cannot check a dependent tabledependent-table-name using the SETINTEGRITY statement while theparent table or underlying tableparent-table-name is in the checkpending state or if it will be putinto the check pending state bythe SET INTEGRITY statement.

Explanation: The parent table or underlyingtable must not be in the check pending state

either before or after the SET INTEGRITYstatement, or it must be included in theinvocation list in order to check a dependenttable.

User Response: Ensure that the parent table isnot in the check pending state by executing theSET INTEGRITY statement to check the parenttable. If the dependent table is a materializedquery table or staging table, ensure that theunderlying table is not in the check pending stateby executing the SET INTEGRITY statement tocheck the underlying table.

If the dependent table is not a materialized querytable or staging table, it is recommended tocheck the parent table first. It is also possible tocheck the dependent table and include the parenttable in the invocation list. In this case, thestatement could still fail if there are rows in theparent table which violate the constraint andthese rows are not deleted and put into anexception table. This can happen if the FOREXCEPTION option is not used.

If the dependent table is a materialized querytable or staging table, it is recommended tocheck the underlying table first. It is also possibleto refresh the dependent materialized query tableand include the underlying table in theinvocation list. In this case, the statement couldstill fail if there are rows in the parent tablewhich violate the constraint and these rows arenot deleted and put into an exception table. Thiscan happen if the FOR EXCEPTION option is notused.

In the case of a referential cycle, all tables mustbe included in the invocation list.

sqlcode: -3608

sqlstate: 428A8

SQL3700 - SQL3799


SQL3700W Device device is full. There areactive-devices other active devices.Please mount new media or takeappropriate action.

Explanation: The media on the specified deviceis full. This device is one of the active-devices + 1target devices to which unloaded data is beingdirected.

User Response: Take ONE of the followingactions:

v Mount a new target media on the specifieddevice and continue unloading by invokingunload with caller action 1(SQLU_CONTINUE).

OR

v If active-devices is not zero, continue the unloadwithout this device by invoking the UNLOADutility with the caller action 4(SQLU_DEVICE_TERMINATE).

OR

v Cancel the unload by invoking the UNLOADutility with caller action 2(SQLU_TERMINATE).

SQL3701W The lobpaths parameter wasspecified, but the table does notcontain any LOB or Long data.This parameter will be ignored.

Explanation: The lobpaths parameter specifies aseparate target for LOB and Long data. The tabledoes not contain any LOB or Long data, so thetargets specified by the lobpaths parameter willnot be used.


SQL3702W Warning. SQLCODE sqlcode wasreceived for device device. Unloadwill attempt to continue withoutthis device.

Explanation: SQLCODE sqlcode was detected forthe specified device which is one of the targetsfor the unload. Unload will continue but willignore this device.

User Response: The media loaded on the

specified device will not contain any unloadeddata and should not be included with the mediasupplied to the LOAD utility when the unloadeddata is being loaded. In order to fix the problemwith the device, look up the returned SQLCODEin the Message Reference.

SQL3703W xxx of yyy number of type typepages have been unloaded andsent to be written out to the targetmedia.

Explanation: The table being unloaded consistsof yyy pages of the specified type of data. xxx ofthese have been processed by the UNLOADutility and have been sent to a media writerwhich will write the data to the target media.

type is one of:

v 0 for regular data

v 2 for Long data and allocation information

v 3 for LOB data

v 4 for LOB allocation information

Note that for Long and LOB data, xxx may beless than yyy when unload is complete, becauseunused space is not unloaded, but will berecreated when the data is reloaded.

Even for regular data, a final message where xxx= yyy may not be issued. Instead message 3105 isused to indicate that the unload completedsuccessfully.

User Response: This is an informationalmessage. No action is required.

SQL3704N The num_buffers parameterspecified is invalid.

Explanation: The num_buffers parameterdetermines the number of buffers that the utilitywill use. The minimum is 2 if the lobpathsparameter is not specified and 3 if the lobpathsparameter is specified. This is the minimumrequired to allow the utility to work. There is,however, an optimal number of buffers that theutility will use if this parameter is not specified.This optimal number is based on the number ofinternal processes that the utility will have


running and whether or not the lobpathsparameter was specified. If the number of buffersspecified is less than the optimal number, someprocesses will be waiting for buffers to use.Therefore, it is recommended to specify 0 for thisparameter and let the utility choose the numberof buffers. Only specify this parameter if, due tothe size of the utility storage heap, it is necessaryto limit the amount of memory that the utilityuses.

User Response: Resubmit the command using avalid num_buffers parameter.

SQL3705N The buffer size parameterspecified is not valid. The buffersize must be specified as 0 or bebetween 8 and 16384 inclusive.For multiple buffers, the totalbuffer size must not exceed 16384.

Explanation: The application calling the utilityhas supplied a buffer size parameter that is notvalid. The buffer size is used to determine theinternal buffer size. The value is the number of4K pages that are obtained for this buffer. Thevalue must be specified as 0 or be between 8 and16384 inclusive. If there are multiple buffers, thenumber of buffers multiplied by the buffer sizemust not exceed 16384.

When 0 is specified:

v for a table whose regular data is in a databasemanaged storage table space, the defaultbuffer size chosen is the extent size for thetable space or 8, whichever is larger.

v for a table whose regular data is in a systemmanaged storage table space, the defaultbuffer size chosen is 8.

User Response: Reissue the command with avalid buffer size.

SQL3706N A disk full error was encounteredon path/file.

Explanation: A disk full error was encounteredduring the processing of a database utility. Theutility stops.

User Response: Ensure enough disk space is

available for the utility or direct the output toother media such as tape.

SQL3707N The sort memory size parameterspecified size1 is not valid. Theminimum size required is size2.

Explanation: The sort memory size is not largeenough for sorting the keys of the index(es).

User Response: Reissue the command with avalid sort memory size.

To ensure that only the minimum amount ofstorage is used, specify a value of 0 (to let itdefault). However, using more than theminimum should improve the performance ofthe sort.

SQL3783N An error was encountered whileopening the copy location file.Open file error code is errcode.

Explanation: During load recovery, an error wasencountered while opening the copy location file.The operating system file open return code isreturned.

User Response: Look at the error code in themessage for more information. Correct the error,if possible, and resubmit the command.

SQL3784W Invalid data was encounteredwhile reading from the copylocation file. Failure occurred atline line-no with error type errtype

Explanation: During load recovery, invalid datawas encountered while reading from the copylocation file. The line number and error type arereturned. The utility waits for a response tocontinue.

User Response: Correct the data in the copylocation file and return to the utility with thecorrect caller action parameter to indicate ifprocessing should continue or terminate.


SQL3785N Load recovery for tableschema.tablename at time timestampon node node-number failed due toerror sqlcode with additionalinformation additional-info.

Explanation: A severe error occurred duringload recovery. The utility stops processing.


User Response: Examine the error code in themessage for more information. Take correctiveaction and resubmit the command.

SQL3798W An invalid value was used forparameter parameter to invoke theroll-forward recovery API tocontinue load recovery.

Explanation: Load recovery is in progress andone of the parameters passed in is not valid forthe current state of load recovery.

User Response: Correct the value in error andreturn to the utility with the correct caller actionparameter to indicate if processing shouldcontinue or terminate.

SQL3799W Load recovery for tableschema.tablename at time timestampon node node-number is pendingdue to warning sqlcode withadditional informationadditional-info.

Explanation: A warning condition isencountered during load recovery. The utilitywaits for a response to continue.


User Response: Examine the error code in themessage for more information. Take correctiveaction and return to the utility with the correctcaller action parameter to indicate if processingshould continue or terminate.

SQL3800 - SQL3899

SQL3802N An invalid quiesce modequiesce-mode was encountered.

Explanation: An invalid quiesce mode waspassed to the quiesce API.

User Response: Resubmit the command withthe correct parameters.

SQL3804N The index is invalid.

Explanation: An invalid index was encounteredduring the processing of a utility command.

User Response: Check in the AdministrationGuide to determine the appropriate way torevalidate the index and resubmit the commandafter the condition is corrected.

SQL3805N The state of the application or ofone or more table spaces for thetable specified prohibits theloadapi action or quiescemodeaction. Reason code = reason-code.

Explanation: The loadapi action (eitherquiescemode or callerac) passed to the load APIis in conflict with either the state of theapplication or the state of one or more tablespaces for the table.

The possible reason codes are as follows:

01 the state of one of the table spaces forthe table specified prohibits the loadapiaction or quiescemode.

02 the application is not at the start of itslogical unit of work. This conditionprohibits the load action specified.

03 the state of the application prohibits theload action specified.


04 one or more of the table spaces for thetable is already quiesced by themaximum number of quiescers.

05 system catalog table space cannot bequiesced.

06 load copy not allowed when table spaceis in backup pending state.

07 Attempt to restart a load at an incorrectphase

User Response: Corresponding to each of theabove reasons:

01 Resubmit the command with the correctloadapi action or quiescemode, orcorrect the state of the table spaces forthe table.

02 Resubmit the command with the correctload action or complete the currentlogical unit of work by issuing either aCOMMIT or ROLLBACK.

03 Resubmit the command with the correctload action.

04 Determine which table spaces for thetable have reached the maximumnumber of quiescers. QUIESCE RESETthese table spaces.

05 Resubmit the command with a tablewhich is not in the system catalog tablespace.

06 Resubmit the command omitting thecopy parameter

07 Determine at which phase the loadshould be restarted and resubmit thecommand with the correct phase.

SQL3806N Not all table constraints are offfor the table to be loaded.

Explanation: One or more constraints for thetable to be loaded are still on when the load APIis invoked.

User Response: Resubmit the command after alltable constraints are turned off.

SQL3807N Instance or database name quiesceis pending.

Explanation: Another user has submitted thequiesce command and it has not yet completed.

User Response: Wait for the quiesce tocomplete.

SQL3808N Instance or database nameunquiesce is pending.

Explanation: Another user has submitted theunquiesce command and it has not yetcompleted.

User Response: Wait for the unquiesce tocomplete.

SQL3900 - SQL3999

SQL3901N A non-severe system erroroccurred. Reason code reason-code.

Explanation: Processing ended because of anon-severe system error.

User Response: If trace was active, invoke theIndependent Trace Facility at the operatingsystem command prompt. Then contact yourtechnical service representative with thefollowing information:





SQL3902C A system error occurred. Furtherprocessing is not possible. Reasoncode = reason-code.

Explanation: A system error occurred.

User Response: If trace was active, invoke theIndependent Trace Facility at the operating


system command prompt. Then contact yourtechnical service representative with thefollowing information:





SQL3910I Synchronization sessioncompleted successfully.

Explanation:

User Response:

SQL3911I Test synchronization sessioncompleted successfully.

Explanation:

User Response:

SQL3912I STOP completed successfully.

Explanation:

User Response:

SQL3913I STOP issued, but nosynchronization session iscurrently active.

Explanation:

User Response:

SQL3914I A user interrupt was issued. Thesynchronization session stoppedsuccessfully.

Explanation:

User Response:

SQL3915I A user interrupt was issuedbefore the results were uploadedto the satellite control server. Theresults will be uploaded duringthe next synchronization session.

Explanation:

User Response:

SQL3916I A STOP request was received.Synchronization session stoppedsuccessfully.

Explanation:

User Response:

SQL3917I A STOP request was receivedbefore the results were uploadedto the satellite control server. Theresults will be uploaded duringthe next synchronization session.

Explanation:

User Response:

SQL3918I Synchronization progressinformation was obtainedsuccessfully.

Explanation:

User Response:

SQL3919I A STOP request was receivedbefore the satellite could contactthe satellite control server.Synchronization stoppedsuccessfully.

Explanation:

User Response:


SQL3920I The application version on thissatellite does not match one thatis available for the group of thissatellite. Synchronization cannotoccur.

Explanation: The application version reportedby the satellite does not exist at the satellitecontrol server.

User Response: Contact the help desk or yoursystem administrator.

SQL3921I This satellite is disabled at thesatellite control server.Synchronization cannot occur.

Explanation: When disabled, the satellite cannotsynchronize.


SQL3930W There are no synchronizationscripts to execute.

Explanation: No synchronization scripts weredownloaded to the satellite for execution.

User Response: Contact the help desk or yoursystem administrator to ensure thatsynchronization scripts are available on thesatellite control database for this satellite.

SQL3931W The test synchronization sessioncompleted successfully. Thesatellite ID, however, could not befound in the satellite controldatabase.

Explanation: Either the satellite ID is notdefined correctly on the satellite or this satellitehas not been defined in the satellite controldatabase.

User Response: If you use theDB2SATELLITEID registry variable, ensure that itis set to the unique ID for the satellite. If you areusing the operating system logon ID as thesatellite ID, ensure you log on using it.

SQL3932W The test synchronization sessioncompleted successfully. Thesatellite’s application version,however, is not set locally, or doesnot exist for this satellite’s groupat the satellite control server.

Explanation: The application version on thesatellite is different from any that are availablefor this satellite’s group.

User Response: Ensure that the applicationversion on the satellite is set to the correct value.

SQL3933W The test synchronization sessioncompleted successfully. Therelease level of the satellite,however, is not supported by therelease level of the satellitecontrol server.

Explanation: The release level of the satellitemust be within the range of one level above totwo levels below that of the satellite controlserver.


SQL3934W The test synchronization sessioncompleted successfully. Thissatellite, however, is disabled atthe satellite control server.

Explanation: The satellite has been placed in thedisabled state at the satellite control server.


SQL3935W The test synchronization sessioncompleted successfully. Thissatellite, however, is in the failedstate at the satellite control server.

Explanation: The satellite is in the failed state atthe control server.



SQL3936W No progress information isavailable.

Explanation: The synchronization session hasnot reached a stage where the progressinformation has been logged, or there is noactive synchronization session for this satellite.

User Response: Ensure the synchronizationsession is active, or try querying for progressinformation later.

SQL3937W The application version for thissatellite does not match one thatis available for this satellite’sgroup.

Explanation: A satellite can only synchronizewith a particular application version for itsgroup. The application version for this satellite isnot available for the satellite’s group at thecontrol server.

User Response: Ensure that the applicationversion on the satellite is set to the correct value.

SQL3938W An interrupt was issued duringscript execution. Thesynchronization session wasstopped, but the satellite may bein an inconsistent state.

Explanation: An interrupt was issued while thescript execution phase of the synchronizationprocess was being performed. Thesynchronization session was stopped but thesatellite may be in an inconsistent state because ascript may have been halted at an inappropriateplace.


SQL3942I Synchronization session identifierwas set successfully for thesatellite.

Explanation: The session identifier was setsuccessfully for the satellite.


SQL3943N Synchronization session identifierexceeds the maximum length oflength characters.

Explanation: The specified synchronizationsession identifier is longer than the allowedlength of length characters.

User Response: Ensure that the identifier is nomore than nnn characters.

SQL3944I Synchronization session identifierwas reset successfully for thesatellite.

Explanation: The session identifier was resetsuccessfully for the satellite.


SQL3945I Synchronization session identifierfor the satellite was retrievedsuccessfully.

Explanation: The session identifier for thissatellite was found and returned successfully.


SQL3946N Synchronization session identifieroperation failed.

Explanation: The synchronization sessionidentifier operation has failed for an unknownreason.

User Response: Ensure that the product isinstalled correctly. If the failure persists, contactDB2 service.

SQL3950N A synchronization session isactive. Only one synchronizationsession can be active.

Explanation: Only one synchronization sessioncan be active at a time.

User Response: Wait until the currentsynchronization session completes successfullybefore initiating another session.


SQL3951N The satellite ID cannot be foundlocally.

Explanation: Either the operating system logonwas bypassed or the DB2SATELLITEID registryvariable was not set.

User Response: If you are using the operatingsystem logon ID as the satellite ID, log on to theoperating system. If you use theDB2SATELLITEID registry variable, ensure that itis set to the unique ID for the satellite.

SQL3952N The satellite ID could not befound at the satellite controlserver.

Explanation: Either the satellite ID is notdefined correctly on this satellite or this satellitehas not been defined at the satellite controlserver.

User Response: If you use theDB2SATELLITEID registry variable, ensure that itis set to the unique ID for the satellite. If you areusing the operating system logon ID as thesatellite ID, ensure you log on using it.Otherwise, contact the help desk or your systemadministrator.

SQL3953N This satellite has been disabled atthe satellite control server.

Explanation: The satellite ID has been disabledat the satellite control server.


SQL3954N This satellite is in the failed stateat the satellite control server.

Explanation: The satellite is in the failed statebecause a previous synchronization sessionfailed.


SQL3955N The satellite control databasename or its alias could not befound.

Explanation: The satellite control database isnot cataloged correctly.

User Response: Contact the help desk or yousystem administrator.

SQL3956N The application version for thissatellite is not defined locally.

Explanation: The application version is notdefined locally on this satellite or is not definedcorrectly.

User Response: Ensure that the applicationversion is set to the correct value.

SQL3957N Cannot connect to the satellitecontrol server because of acommunication failure:SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.

Explanation: An error has been detected by thecommunication subsystem. Refer to sqlcode formore details.


SQL3958N Error occurred duringsynchronization session:SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.

Explanation: An unknown error has beendetected by the communication subsystem. Referto sqlcode for more details.



SQL3959N Synchronization session cannotstart because of a communicationfailure: SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.



SQL3960N Cannot upload results to thesatellite control server because ofa communication failure:SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.



SQL3961N Cannot authenticate with thesatellite control server.

Explanation: An authentication error wasdetected while trying to connect to the satellitecontrol database.

User Response: Either the remoteadministrative user ID or the password requiredto connect to the satellite control database wasnot correct, or both. Either provide the correctuser ID and password, or contact the help deskor your system administrator.

SQL3962N Synchronization could not bestarted because of a databaseerror: SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.

Explanation: An error preventingsynchronization occurred at the satellite controlserver.

User Response: Attempt to synchronize again.

If failure persists, contact the help desk or yoursystem administrator.

SQL3963N Results cannot be uploadedbecause of a database error:SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.

Explanation: An error occurred while uploadingresults to the satellite control server.


SQL3964N Synchronization failed becausethe release level of the satellite isnot supported by the satellitecontrol server.

Explanation: The release level of the satellitemust be within the range of one level above totwo levels below that of the satellite controlserver.


SQL3965N Cannot download thesynchronization scripts because ofa satellite control server failure:SQLCODE=sqlcodeSQLSTATE=sqlstate, tokens=token1,token2, token3.

Explanation: The satellite cannot download thescripts that are required to synchronize thesatellite. One possible reason for this failure isthat the control server cannot instantiateparameterized scripts with the attributes of thesatellite. Another reason is that the satellitecontrol server was temporarily unable tocomplete the request because of resourceconstraints.

User Response: Try the request again. If thefailure persists, contact the help desk or yoursystem administrator.


SQL3966N Synchronization session failed.Reason code reason-code.

Explanation: The synchronization session failedto complete for one of the following reasons:

v (01) Missing authentication information.

v (02) Some scripts required for synchronizationare missing.

v (03) System files are corrupted or missing.

v (04) A system error prevented scripts fromexecuting.

User Response: Try the request again. If failurepersists, contact the help desk or your systemadministrator.

SQL3967N Progress information cannot beretrieved.

Explanation: Progress on this satellite’ssynchronization session cannot be retrieved.Either the data is corrupt, or it does not exist.

User Response: If a synchronization session isactive and no progress information is available,contact the help desk or your systemadministrator.

SQL3968N Synchronization failed tocomplete successfully because of ascript failure. The results of theexecution, however, were sent tothe satellite control server.

Explanation: One of the synchronization scriptsfailed during execution. Either a return code was

not in the defined success code set, or the scriptfailed to execute.


SQL3969N Synchronization failed because aninterrupt was received duringscript execution.

Explanation: Script execution fails when aninterrupt is received. An abnormal termination ofthis type will cause the synchronization sessionto fail because the system may be in aninconsistent state.


SQL3970N Synchronization session failedwith, SQLCODE sqlcodeSQLSTATE sqlatate The error wasdetected at location location.

Explanation: Script execution failed because ofan unknown error.


SQL4000 - SQL4099

SQL4001N The character character in columncolumn on line line is not valid.

Explanation: The specified character is not avalid character in SQL statements.


User Response: Remove or replace the characterthat is invalid.

SQL4002N token-1 and token-2 are undeclaredhost variables that cannot both beused as descriptor names in asingle SQL statement.

Explanation: The specified identifiers have notbeen declared as host variables. Descriptornames are not declared before using. Becausemore than one descriptor name in a singlestatement is not valid, at least one of the hostvariables is not valid.



User Response: Correct the use of descriptornames or undeclared host variables in thestatement. Note that the statement can containadditional undeclared host variables.

SQL4003N The SQL statement on line line isnot supported by this version ofthe precompiler.

Explanation: The release numbers of theprecompiler and the installed version of thedatabase manager are not compatible. Thespecified statement is supported by the databasemanager but not the precompiler.


User Response: Repeat the precompile processwith the current version of the precompiler.

SQL4004N The package name is not valid.

Explanation: The package name containscharacters that are not valid. Either the name istoo long or no name was specified with thePACKAGE option.


User Response: Resubmit the command with avalid package name or without the PACKAGEoption.

SQL4005N An invalid token token was foundstarting in position position on lineline.

Explanation: A syntax error in the SQLstatement was detected at the specified tokentoken.


User Response: Examine the statement,especially around the specified token. Correct thesyntax.

SQL4006N The structures are nested toodeeply.

Explanation: The number of nested structuresexceeded the maximum of 25.


User Response: Reduce the number of nestedstructures.

SQL4007N The host structure host-structurehas no fields.

Explanation: No field can be found within thehost structure host-structure.


User Response: Add a field to the hoststructure.

SQL4008N The host variable name cannot beuniquely referenced even withfull qualification.

Explanation: The host variable name matcheswith at least one other unqualified or partiallyqualified host variable even with fullqualification.


User Response: Rename the host variable.

SQL4009N The expression for data length isinvalid.

Explanation: The expression for data length hassyntax errors or is too complex.


User Response: Check the syntax of the sizeexpression.

SQL4010N Illegal nesting of Compound SQLstatements.

Explanation: This error is returned when aBEGIN COMPOUND clause is detected as asub-statement of a Compound SQL statement.

User Response: Resubmit the precompilation


without the nested BEGIN COMPOUND.

SQL4011N Invalid SQL sub-statement in aCompound SQL statement.

Explanation: This error is returned when aninvalid sub-statement is detected in a CompoundSQL statement. Valid statements are:

v ALTER TABLE

v COMMENT ON

v CREATE INDEX

v CREATE TABLE

v CREATE VIEW

v Positioned DELETE

v Searched DELETE

v DROP

v GRANT

v INSERT

v LOCK TABLE

v REVOKE

v SELECT INTO

v Positioned UPDATE

v Searched UPDATE

v COMMIT; only when specified as the lastsub-statement.

v RELEASE TO SAVEPOINT; only fornon-atomic Compound SQL

v ROLLBACK TO SAVEPOINT; only fornon-atomic Compound SQL

v SAVEPOINT; only for non-atomic CompoundSQL

User Response: Resubmit the precompilationwithout the invalid sub-statement.

sqlcode: -4011

sqlstate: 42910

SQL4012N Invalid use of COMMIT in aCompound SQL statement.

Explanation: This error is returned when asub-statement is detected after a COMMIT hasbeen found in a COMPOUND SQL statement.

User Response: Make the COMMIT

sub-statement the last sub-statement, andresubmit the precompilation.

SQL4013N An END COMPOUND statementwas found without a previousBEGIN COMPOUND statement.

Explanation: This error is returned when anEND COMPOUND statement has been foundwithout a preceding BEGIN COMPOUND.

User Response: Either remove the ENDCOMPOUND, or add a BEGIN COMPOUND,and resubmit the precompilation.

SQL4014N Invalid Compound SQL syntax.

Explanation: This error is returned when aCompound SQL statement contains a syntaxerror. Possible causes include:

v END COMPOUND is missing

v one of the substatements is empty (zero lengthor blank).

User Response: Fix the syntax error andre-precompile.

SQL4015N An error has occurred duringpreprocessing.

Explanation: The external preprocessor hasterminated with one or more errors.


User Response: Please refer to the “.err” file forthe corresponding source file for more details.

SQL4016N The preprocessor specified cannotbe found.

Explanation: The preprocessor specifiedthrough the PREPROCESSOR option cannot befound.


User Response: Ensure that the preprocessorcan be executed from the current directory, andalso check the syntax of the PREPROCESSORoption.


SQL4017W Preprocessing has completedsuccessfully.

Explanation: Preprocessing of the input file hascompleted successfully using the externalcommand specified through thePREPROCESSOR option.


SQL4018W Starting to process thepreprocessed file preprocessed-file.

Explanation: The precompiler is now processingthe preprocessed file.


SQL4019W Completed processing thepreprocessed file preprocessed-file.

Explanation: The precompiler has completedprocessing the preprocessed file.


SQL4020N The ’long’ host variable token-1 isnot valid. Use ’sqlint32’ instead.

Explanation: If the LONGERROR YESprecompile option is in effect or the precompileoption LONGERROR has not been specified andthe platform has 8-byte ’long’s, then theINTEGER host variable must be declared withthe data type ’sqlint32’, not ’long’.

On 64 bit platforms with 8-byte ’long’ types theprecompile option LONGERROR NO can beused to specify that ’long’ host variables are tobe used for BIGINT data types. For maximumportability the use of ’sqlint32’ and ’sqlint64’ arerecommended for INTEGER and BIGINT datatypes respectively.

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

SQL4100 - SQL4199

SQL4100I The sqlflag-type SQL languagesyntax is used for syntax checkingby the flagger.

Explanation: The SQL statements that havepassed the precompiler checking will be subjectto checking against the specified syntax by theflagger. Warning message will be issued againstthe statement when there is a syntax deviation.


User Response: None. This is an informationalmessage only.

SQL4102W An SQL syntax deviation hasoccurred at the token starting withthe text text.

Explanation: The flagger has detected adeviation from the SQL language syntaxspecified in the SQLFLAG precompiler option.


User Response: Correct the SQL statement.

SQL4103W A data definition statement is notwithin a CREATE SCHEMAstatement.

Explanation: The FIPS standard requires that alldata definition statements are contained within aCREATE SCHEMA statement.



SQL4104W There is a non-standardembedded comment.

Explanation: A comment embedded in an SQLstatement does not meet the requirements of thestandard being flagged. The comment does notbegin with at least two consecutive hyphens




SQL4105W An SQL syntax deviation hasoccurred. The statement is notcomplete.

Explanation: The SQL statement has terminatedbefore all required elements have been found.



SQL4106W The identifier identifier is morethan 18 characters.

Explanation: Authorization identifier, tableidentifier, column name, correlation name,module name, cursor name, procedure name, orparameter name has a length of more than 18characters.



SQL4107W Column column has an invalidlength, precision, or scaleattribute.

Explanation: One of the following conditionshas not been met:

v Length value should be greater than zero.

v Precision value should be greater than zero.

v Scale value should not be greater thanprecision.



SQL4108W An indicator variable has datatype other than exact numeric, orhas a non-zero scale.

Explanation: Data type of an indicator variableshould be exact numeric with a scale of zero.



SQL4109W The SET FUNCTIONSPECIFICATION referencescolumn column.


v The COLUMN REFERENCE of a DISTINCTSET FUNCTION cannot reference a columnderived from a SET FUNCTIONSPECIFICATION.

v COLUMN REFERENCEs in the VALUEEXPRESSION of an ALL SET FUNCTIONcannot reference a column derived from a SETFUNCTION SPECIFICATION.



SQL4110W A VALUE EXPRESSIONcontaining column cannot includeoperators.

Explanation: A VALUE EXPRESSION cannotinclude operators in an OUTER REFERENCECOLUMN REFERENCE.



SQL4111W The COLUMN REFERENCE ismissing or is invalid for the ALLcolumn function function.

Explanation: The VALUE EXPRESSION of anALL SET FUNCTION SPECIFICATION shouldinclude a COLUMN REFERENCE.



SQL4112W Column column is not unique andrequires qualification.

Explanation: The specified column is notunique within the current scope. Qualificationmust be given to uniquely identify the requiredcolumn.




SQL4113W A VALUE EXPRESSION may notcontain a SET FUNCTIONSPECIFICATION.

Explanation: The VALUE EXPRESSION of anALL SET FUNCTION may not contain SETFUNCTION SPECIFICATION.



SQL4114W Column column does not identifya column of a table within thecurrent scope.


v The table or correlation name used as aqualifier does not exist.

v The column name does not exist within thecurrent scope or the scope of the qualifier.



SQL4115W A column function that containsthe OUTER REFERENCE columncolumn is not in the subquery of aHAVING clause.

Explanation: A column function must becontained in a subquery of a HAVING clause if itcontains an OUTER REFERENCE COLUMNREFERENCE.



SQL4116W The result of a SUM or AVGfunction cannot be a characterstring.

Explanation: Character string is not valid forthe result of a SUM or AVG SET FUNCTIONSPECIFICATION.



SQL4117W Operator operator is invalid in thiscontext.


v A VALUE EXPRESSION containing aDISTINCT SET FUNCTION cannot includedyadic operators.

v First character following a monadic operatorcannot be a plus or minus sign.

v VALUE EXPRESSION should not containoperators if PRIMARY is of type characterstring.



SQL4118W The exptype EXPRESSION iscomparing incompatible datatypes.

Explanation: The data types of one of thefollowing (identified by exptype) do not match:

v exptype = COMPARISON - Comparisonoperators must match

v exptype = BETWEEN - The three VALUEEXPRESSIONs must match

v exptype = IN - VALUE EXPRESSION,subquery and all VALUE SPECIFICATIONsmust match

v exptype = QUANTIFIED - VALUEEXPRESSION and subquery must match



SQL4119W The operand in the LIKEpredicate is not a character string.


v Data type of the column in a LIKE predicate isnot a character string.


v Data type of the pattern in a LIKE predicate isnot a character string.



SQL4120W The ESCAPE character must be aone-byte character string.

Explanation: Escape character in a LIKEpredicate must have the data type of characterstring with a length of 1.



SQL4121W The WHERE clause, GROUP BYclause, or HAVING clause isinvalid for the grouped viewschema-name.view.

Explanation: If the table identified in the FROMclause is a grouped view, then the TABLEEXPRESSION must not contain a WHERE clause,GROUP BY clause, or HAVING clause.



SQL4122W schema-name.name occurs more thanonce in a FROM clause.


v Table name occurs more than once in a FROMclause.

v Correlation name is identical to a table nameor to another correlation name in a FROMclause.



SQL4123W Only one table reference isallowed in the FROM clause for aGROUPed view.

Explanation: If the table identified by tablename is a GROUPed view, then the FROM clausemust contain exactly one table reference.



SQL4124W A reference to column columnderived from a column function isinvalid in a WHERE clause.

Explanation: A VALUE EXPRESSION directlycontained in the SEARCH CONDITION of aWHERE clause must not include a reference to acolumn derived from a column function.



SQL4125W A HAVING clause must containthe WHERE clause when theWHERE clause has a columnfunction.

Explanation: If a VALUE EXPRESSION directlycontained in the SEARCH CONDITION is acolumn function, then the WHERE clause mustbe contained in a HAVING clause.



SQL4126W The COLUMN REFERENCE forcolumn must be an OUTERREFERENCE.

Explanation: If a VALUE EXPRESSION directlycontained in the SEARCH CONDITION is afunction, then the COLUMN REFERENCE in thecolumn function expression must be an OUTERREFERENCE.




SQL4127W Column column is duplicatedwithin the current scope.

Explanation: The specified column is duplicatedwithin the current scope.



SQL4128W The COLUMN REFERENCE forcolumn-name should be a groupingcolumn or should be specifiedwithin a column function.

Explanation: Each COLUMN REFERENCEcontained in a subquery in the SEARCHCONDITION of a HAVING clause mustreference a grouping column or be specifiedwithin a column function.



SQL4129W DEGREE of table schema-name.tableshould be 1 when using aSELECT LIST of *.

Explanation: The DEGREE of the TABLEEXPRESSION must be 1 if a SELECT LIST of * isspecified in a subquery of any predicate otherthan an EXISTS predicate.



SQL4130W The column function is not validfor the TABLE EXPRESSIONbeginning with tableschema-name.table.


v If the TABLE EXPRESSION is a grouped view,the SELECT LIST of a subquery cannot containa SET FUNCTION SPECIFICATION.

v If the TABLE EXPRESSION is a grouped view,the SELECT LIST of a QUERYSPECIFICATION cannot contain a columnfunction.



SQL4131W The COLUMN REFERENCE forcolumn is invalid.


v For a GROUPed table, the COLUMNREFERENCE must reference a GROUPingcolumn or be specified within a SETFUNCTION SPECIFICATION.

v If not a GROUPed table and VALUEEXPRESSION includes a SET FUNCTIONSPECIFICATION, then each COLUMNREFERENCE must be specified within a SETFUNCTION SPECIFICATION.



SQL4132W DISTINCT is specified more thanonce.


v DISTINCT must not be specified more thanonce in a QUERY SPECIFICATION, excludingany subquery of that QUERYSPECIFICATION.

v DISTINCT must not be specified more thanonce in a subquery, excluding any subquerycontained in that subquery.



SQL4133W The COMPARISON PREDICATEsubquery cannot contain aGROUP BY or HAVING clause.

Explanation: If a subquery is specified in aCOMPARISON PREDICATE, then the TABLEEXPRESSION whose FROM clause identifies thenamed table must not contain a GROUP BYclause or a HAVING clause.




SQL4134W The COMPARISON PREDICATEsubquery cannot identify aGROUPed view.

Explanation: If a subquery is specified in aCOMPARISON PREDICATE, then the TABLEEXPRESSION whose FROM clause identifies thenamed table must not identify a GROUPed view.



SQL4135W There is an invalidAUTHORIZATION IDENTIFIERauthid.

Explanation: The AUTHORIZATIONIDENTIFIER prefixed to the table name isinvalid.



SQL4136W Table or view schema-name.namealready exists.

Explanation: The table name or view namespecified already exists in the catalog.



SQL4137W The COLUMN DEFINITION ismissing.

Explanation: At least one COLUMNDEFINITION should be specified for a CREATETABLE.



SQL4138W The data type type1 of the target isnot compatible with the data typetype2 of the source.

Explanation: Data types should match:

v In a FETCH statement, between source andtarget.

v In a SELECT statement, between source andtarget.



SQL4139I You must specify a VIEWCOLUMN LIST forschema-name.table.

Explanation: If any two columns in the tablespecified by the QUERY SPECIFICATION havethe same column name, or if any column of thattable is an unnamed column, then a VIEWCOLUMN LIST must be specified.



SQL4140W An error has occurred causing theflagger to stop. Module name =module-name. Internal error code =error-code.

Explanation: The flagger has encountered aninternal error. If the syntax, bindfile or packageoption is also specified, processing continues butflagger operation is discontinued. Otherwise,processing is terminated.

User Response: Record this message number(SQLCODE), module name and error code in themessage. Contact your technical servicerepresentative with the information.

SQL4141W An error has occurred whenattempting to produce messagemessage-number in modulemodule-name.

Explanation: The FLAGGER has attempted toproduce an undefined message.




SQL4142W There is not enough memory forflagger operation. Internal errorcode = error-code.

Explanation: There is not enough memory forthe flagger to operate. If the syntax, bindfile orpackage option is also specified, processingcontinues but flagger operation is discontinued.Otherwise, processing is terminated.

User Response: Ensure that your system hassufficient real and virtual memory, and removeany unnecessary background processes.

SQL4143W An error has occurred whenreleasing flagger memory. Internalerror code = error-code.

Explanation: The flagger cannot releaseallocated memory. If the syntax, bindfile orpackage option is also specified, processingcontinues but flagger operation is discontinued.Otherwise, processing is terminated.

User Response: Restart precompilation ifflagging is required.

SQL4144W Internal error on call to theFLAGGER found in modulemodule-name. Internal error code =error-code.

Explanation: The FLAGGER encountered aninternal error.

Preprocessing continues but FLAGGER operationis discontinued.


SQL4145W Error during FLAGGER access tothe system catalog. Flaggingcontinues to check syntax only.SQLCODE = nnn SQLERRP =modname SQLERRD = nnnCreator = creatorname Table =tablename

Explanation: An internal error has occurredduring FLAGGER access to the system catalog.

Processing continues but with flagger syntaxchecking only.


SQL4146W Internal error occurred causing thesemantics processing to stop.Module name = module-name.Internal error code = error-code.

Explanation: The FLAGGER has encountered asevere internal error in a semantics analysisroutine.

Processing continues but with flagger syntaxchecking only.


SQL4147W Invalid flagger version number.

Explanation: An invalid flagger version numberis passed to the Precompiler Services COMPILESQL STATEMENT API. If the syntax, bindfile orpackage option is also specified, processingcontinues but flagger operation is discontinued.Otherwise, processing is terminated.

User Response: Provide a valid flagger versionnumber. Refer to the Command Reference manual.


SQL4170W You must declare column columnas NOT NULL.

Explanation: All columns identified as UNIQUEmust be defined with the NOT NULL option.



SQL4171W The viewed table schema-name.tablemust be updatable.

Explanation: When the WITH CHECK OPTIONclause is specified then the viewed table must beupdatable.



SQL4172W Invalid number of column names.

Explanation: The number of column names inthe VIEW COLUMN LIST should be the same asthe DEGREE of the table specified by the QUERYSPECIFICATION.



SQL4173W You must declare cursor cursorbefore using it.

Explanation: The cursor specified has not beendeclared in a DECLARE CURSOR statement.



SQL4174W Cursor cursor is already declared.

Explanation: Cursor specified has already beendeclared in a DECLARE CURSOR statement.



SQL4175W Only * or column names are validin this context.

Explanation: When UNION is specified, theSELECT LIST for the specification of the twoTABLE EXPRESSIONs identified by the QUERYEXPRESSION and QUERY TERM should consistof * or COLUMN REFERENCE(s).



SQL4176W The descriptions of tablesidentified by the QUERYEXPRESSION beginning withschema-name1.table1 and theQUERY TERM beginning withschema-name2.table2 should beidentical.

Explanation: When UNION is specified, thedescriptions of the two tables should be identical,except for the column names.



SQL4177W The SORT SPECIFICATIONnumber is outside the DEGREE ofcursor cursor.

Explanation: If the SORT SPECIFICATIONcontains an unsigned integer, it should be greaterthan 0 and not greater than the number ofcolumns in the table.



SQL4178W Table schema-name.table is aread-only table.

Explanation: A DELETE, an INSERT, or anUPDATE was specified on a read-only table.




SQL4179W Table schema-name.table must notbe identified in a FROM clause ofany subquery contained in aSEARCH CONDITION.

Explanation: A table specified in a DELETE oran UPDATE cannot be used in a FROM clause ofany subquery contained in its SEARCHCONDITION.



SQL4180W Table schema-name1.table1 is not thefirst table schema-name2.table2specified in the DECLARECURSOR statement.

Explanation: Table specified in a DELETE or anUPDATE statement should be the first tablespecified in the FROM clause of the DECLARECURSOR statement.



SQL4181W The number of TARGETSPECIFICATIONs does not matchthe DEGREE of cursor cursor.

Explanation: The number of TARGETSPECIFICATIONs in the FETCH statement doesnot match the DEGREE of the table specified.



SQL4182W Target table schema-name.table ofthe INSERT statement is also inthe FROM clause or in thesubquery.

Explanation: The named table must not beidentified in a FROM clause of a QUERYSPECIFICATION or of any subquery containedin the QUERY SPECIFICATION.



SQL4183W The number of columns specifieddoes not match the number ofvalues specified.

Explanation: In an INSERT statement, thenumber of columns specified does not match thenumber of values specified.



SQL4184W The number of columns specifieddoes not match the DEGREE ofthe QUERY SPECIFICATIONbeginning with tableschema-name.table.

Explanation: In an INSERT statement, thenumber of columns specified does not match theDEGREE of the table specified in the QUERYSPECIFICATION



SQL4185W There is a data type or lengthmismatch between column columnand the INSERT or UPDATE item.


v If the data type of the column name ischaracter string, then the corresponding itemin the INSERT or UPDATE statement shouldbe character string of length equal to or lessthan the length of the column name.

v If the data type of the column name is exactnumeric, then the corresponding item in theINSERT or UPDATE statement should be exactnumeric.

v If the data type of the column name isapproximate numeric, then the correspondingitem in the INSERT or UPDATE statementshould be approximate numeric or exactnumeric.




SQL4186W You cannot use a GROUP BY orHAVING clause or identify aGROUPed view in this context.

Explanation: The table identified in the FROMclause of the TABLE EXPRESSION in a SELECTstatement should not include a GROUP BY orHAVING clause and should not identify aGROUPed view.



SQL4187W The number of elements specifiedin the SELECT LIST should matchthe number in the SELECTTARGET LIST.

Explanation: In the SELECT statement, thenumber of elements specified in the SELECTLIST should match the number of elements inthe SELECT TARGET LIST.



SQL4188W A column function is not allowedin a SET clause of an UPDATEstatement.

Explanation: A VALUE EXPRESSION in a SETclause of an UPDATE statement should notinclude a column function.



SQL4189W You cannot specify NULL forNOT NULL column column.

Explanation: If NULL is specified in the SETclause of the UPDATE statement, then the

corresponding column should allow nulls.



SQL4190W A host variable of anunrecognized data type isreferenced. Host variable positionis position.

Explanation: The host variable reference atposition position is of a data type not recognizedby the standard.



SQL4191W The data type of columncolumn-name is not recognized.

Explanation: The data type of the column is notrecognized by the standard.



SQL4192W Table schema-name.table is notfound in the catalog.

Explanation: The named table or view does notexist in the system catalog.

SQL4300 - SQL4399


SQL4300N Java support is not installed orproperly configured on thisplatform.

Explanation: Support for Java stored proceduresand user-defined functions is not installed andconfigured on this server.

User Response: Ensure that a compatible JavaRuntime Environment or Java Development Kitfor the server is installed. Ensure that the″JDK_PATH″ configuration parameter is correctlyset.

sqlcode: -4300

sqlstate: 42724

SQL4301N Java interpreter startup orcommunication failed, reasoncode reason-code.

Explanation: An error occurred whileattempting to start or communicate with a Javainterpreter. The reason codes are:

1 Java environment variables or Javadatabase configuration parameters areinvalid.

2 A Java Native Interface call to the Javainterpreter failed.

3 The ″db2java.zip″ file may be corrupt ormissing.

4 The Java interpreter has terminateditself and cannot be restarted.

User Response: Ensure that the Java databaseconfiguration parameters (jdk_path andjava_heap_sz) are correctly set. Ensure that asupported Java runtime environment is installed.Ensure that internal DB2 classes (COM.ibm.db2)are not overridden by user classes.

sqlcode: -4301

sqlstate: 58004

SQL4302N Java stored procedure oruser-defined function name,specific name spec-name abortedwith an exception string.

Explanation: The Java stored procedure oruser-defined function aborted with a Javaexception. The administration notification logcontains a Java stack traceback for the abortedmethod.

User Response: Debug the Java method toeliminate the exception.

sqlcode: -4302

sqlstate: 38501

SQL4303N Java stored procedure oruser-defined function name,specific name spec-name could notbe identified from external namestring.

Explanation: The CREATE PROCEDURE orCREATE FUNCTION statement that declaredthis stored procedure or user-defined functionhad a badly formatted EXTERNAL NAMEclause. The external name must be formatted asfollows: ″package.subpackage.class!method″.

User Response: Submit a corrected CREATEPROCEDURE or CREATE FUNCTION statement.

sqlcode: -4303

sqlstate: 42724

SQL4304N Java stored procedure oruser-defined function name,specific name spec-name could notload Java class class, reason codereason-code.

Explanation: The Java class given by theEXTERNAL NAME clause of a CREATEPROCEDURE or CREATE FUNCTION statementcould not be loaded. The reason codes are:

1 The class was not found on theCLASSPATH.

2 The class did not implement therequired interface


(“COM.ibm.db2.app.StoredProc” or“COM.ibm.db2.app.UDF”) or lacked theJava “public” access flag.

3 The default constructor failed or wasunavailable.

4 Could not load driver for“jdbc:default:connection”.

5 Could not establish default context.

User Response: Ensure that the compiled″.class″ file is installed in the CLASSPATH, forexample under ″sqllib/function″. Ensure itimplements the required Java interfaces and is″public″.

sqlcode: -4304

sqlstate: 42724

SQL4306N Java stored procedure oruser-defined function name,specific name spec-name could notcall Java method method, signaturestring.

Explanation: The Java method given by theEXTERNAL NAME clause of a CREATE

PROCEDURE or CREATE FUNCTION statementcould not be found. Its declared argument listmay not match what the database expects, or itmay not be a ″public″ instance method.

User Response: Ensure that a Java instancemethod exists with the ″public″ flag and theexpected argument list for this call.

sqlcode: -4306

sqlstate: 42724

SQL4400 - SQL4499

SQL4400N authorization-ID does not have theauthority to perform theadministration task at the DB2Administration Server.

Explanation: The user does not have thenecessary authority at the DB2 AdministrationServer to perform the attempted administrativeaction.

User Response: Submit the request to the DB2Administration Server using a user ID withDASADM authority. DASADM authority isrequired to perform any administrative actionsagainst the DB2 Administration Server. TheDASADM group is a DB2 Administration Serverconfiguration parameter. Verify the currentsetting of the DASADM group by viewing theDB2 Administration Server configurationparameters using the GET ADMINCONFIGURATION command. To modify the

value of any configuration parameter, use theUPDATE ADMIN CONFIGURATION command.

SQL4401C The DB2 Administration Serverencountered an error duringstartup.

Explanation: An error was encountered duringstartup of the DB2 Administration Server.

User Response: Refer to the DB2Administration Server’s First Failure DataCapture Log for additional information. Take theappropriate action as necessary and attempt torestart the DB2 Administration Server.

If the problem persists contact your technicalservice representative.


SQL4402W The DB2ADMIN command wassuccessful.

Explanation: All processing completednormally.


SQL4403N The syntax of the command isinvalid.

Explanation: The command was entered usinginvalid arguments or an invalid number ofparameters.

User Response: Re-submit the command withvalid argument(s).

SQL4404N The DB2 Administration Serverdoes not exist.

Explanation: The DB2 Administration Serverwas not found on the machine.

User Response: Create the DB2 AdministrationServer on the machine.

v On Windows operating systems, issue thefollowing command:

db2admin create

v On UNIX platforms, ensure that you have rootauthority, and issue the following commandfrom the DB2DIR/instance directory, whereDB2DIR is the installation path of DB2.<ASName> represents the name of theAdministration Server:

dascrt <ASName>

SQL4405W The DB2 Administration Serveralready exists.

Explanation: The DB2 Administration Serveralready exists on the machine


SQL4406W The DB2 Administration Serverwas started successfully.



SQL4407W The DB2 Administration Serverwas stopped successfully.



SQL4408N The DB2 Administration Serverwas not dropped because it isactive.

Explanation: The DB2 Administration Servermust be stopped before it can be dropped.

User Response: To stop the DB2 AdministrationServer, enter the following command:

DB2ADMIN STOP

SQL4409W The DB2 Administration Server isalready active.

Explanation: The DB2ADMIN START commandcannot be processed because the DB2Administration Server is already active.


SQL4410W The DB2 Administration Server isnot active.

Explanation: The DB2ADMIN STOP commandcannot be processed because the DB2Administration Server is not active.


SQL4411N The requested operation is notallowed because the serverinstance is not the DB2Administration Server.

Explanation: The requested operation is onlyvalid when issued against the DB2Administration Server.

User Response: The DB2 Administration Servershould be set up using the DB2ADMINcommand. Refer to the Quick Beginnings for


further information about the DB2ADMINcommand.

SQL4412N The logon user account for theDB2 Administration Server isinvalid.

Explanation: To perform the requested task, theDB2 Administration Server must be runningunder a valid logon user account. This error iseither caused by the account not being setup, orthe logon user account does not contain a validDB2 user ID.

User Response: If a logon user account hasbeen set up, then ensure that the account uses avalid DB2 user ID.

You can set up the logon user account for theDB2 Administration Server by using thefollowing command:

DB2ADMIN SETID <userid><password>

SQL4413W Usage: DB2ADMIN creates, drops,starts, or stops the DB2Administration Server.

Explanation: The DB2ADMIN command syntaxis:

DB2ADMIN CREATE [/USER:<username>/PASSWORD:<password>]

DROPSTARTSTOP [/FORCE]SETID <username>

<password>SETSCHEDID <username> <password>/h


CREATEcreate the DB2 Administration Server

DROP delete the DB2 Administration Server

START start the DB2 Administration Server

STOP stop the DB2 Administration Server

SETID set the logon account for the DB2Administration Server

SETSCHEDIDset the logon account used by thescheduler to connect to the tools catalogdatabase. Only required if the scheduleris enabled and the tools catalogdatabase is remote to the DB2Administration Server.

/USER specify the logon account name duringDB2ADMIN CREATE

/PASSWORDspecify the logon account passwordduring DB2ADMIN CREATE

/FORCEstop the DB2 Administration Serverduring DB2ADMIN STOP regardless ofwhether or not it is in the process ofservicing any requests

/h display the usage information

User Response: Issue the DB2ADMINcommand with one of the valid commandoptions.

SQL4414N The DB2 Administration Server isnot active.

Explanation: The request cannot be processedunless the DB2 Administration Server is active.

User Response: Start the DB2 AdministrationServer by issuing the command DB2ADMINSTART, and reissue the request.

SQL4900 - SQL4999


SQL4901N Precompiler Services requiresreinitialization because of aprevious error.

Explanation: On a previous function call, anerror occurred. The requested function callcannot be processed until Precompiler Services isreinitialized.

The function cannot be completed.

User Response: Call the sqlainit function toreinitialize Precompiler Services

SQL4902N At least one of the characters inparameter n of function function isnot valid.

Explanation: The specified parameter in thespecified function contains at least one characterthat is not valid.


User Response: Correct the specified parameterand call the function again.

SQL4903N The length of parameter n offunction name is not valid.

Explanation: The length of the specifiedparameter in the specified function is not valid.



SQL4904N The pointer to parameter n offunction function is not valid.

Explanation: The pointer to the specifiedparameter in the specified function is not valid.



SQL4905N The value of parameter n offunction function is not within thevalid range.

Explanation: The value of the specifiedparameter in the specified function is outside thevalid range for that parameter. If the specifiedparameter is a structure, it may contain valuesthat are within the valid range but are not validwhen considered together. Some structurescontain headers that specify the allocated sizeand how much of that size is being used. It isnot valid for the allocated size to be less than theused size.



SQL4906N The list of table space namesspecified is an incomplete set forthe rollforward operation.

Explanation: The list of table space names isincomplete for one of the following reasons:

v For point-in-time table space recovery, a tablespace list must be specified.

v For point-in-time table space recovery, aself-contained list of table space names mustbe specified. The table spaces in the list mustcontain all objects of every table included inthe table spaces.

v Point-in-time table space recovery is notallowed for the system catalogs.

v End-of-logs table space recovery is allowed forthe system catalogs but it can be the only tablespace name in the list.

v The CANCEL option for rollforward musthave a table space list if there are no tablespaces in ″rollforward-in-progress″ state.

User Response: Check the table space list andresubmit the rollforward command with thecomplete table space list.


SQL4907W Database name is recovered butone or more of the tables in thetable space list included for therollforward operation are placedin check pending states.

Explanation: One or more of the tables involvedin the point-in-time tablespace recovery havereferential constraints with tables outside of thetable space list used for recovery. All these tablesare placed in check pending state. Rollforwardoperation is otherwise completed successfully.

User Response: Check the state for the tables inthe table spaces and take appropriate actions ifnecessary.

SQL4908N The table space list specified forroll-forward recovery on databasename is invalid on node(s)node-list.

Explanation: If starting a new table spacerollforward, one or more of the table spacesspecified in the list to be rolled forward is not inrollforward pending state on the specified nodes.If continuing a table space rollforward that isalready in progress, one or more of the tablespaces specified in the list to be rolled forward isnot in rollforward in progress state on thespecified nodes.


Roll-forward recovery stops.


User Response: Use the LIST TABLESPACESSHOW DETAIL command on the nodes specifiedto find out which table spaces are not ready tobe rolled forward. Use the QUERY STATUSoption of the rollforward command to determinethe status of the table space rollforward. If therollforward status is ″TBS pending″, a new tablespace rollforward can be started. If therollforward status is ″TBS working″, a table space

rollforward is already in progress.

If starting a new table space rollforward, put thetablespaces into rollforward pending state byrestoring them.

If continuing a table space rollforward and oneor more of the table spaces involved have beenrestored and put into rollforward pending state,the table space rollforward in progress must becanceled. Submit the rollforward command againwith the CANCEL option and the same tablespace list. When the rollforward in progress iscanceled, the table spaces will have been put intorestore pending state. Restore the table spacesand submit the original rollforward commandagain.

SQL4909W Roll forward recovery hascompleted successfully but one ormore table spaces have theirtables put in DRP/DRNP state.Check the administrationnotification log for details onnode(s) node-list.

Explanation: One or more table spaces havetables in DATALINK Reconcile Pending (DRP)state or DATALINK Reconcile Not Possible(DRNP) state for one of the following reasons:

v Restore is done specifying the WITHOUTDATALINK option and rollforward to apoint-in-time follows the restore. Any tableswith DATALINK columns are placed in DRPstate.

v Restoring from a backup image with adifferent database name, alias, hostname, orinstance and rollforward follows the restore.Any tables with DATALINK columns areplaced in DRNP state.

v Restoring from a backup image that hasbecome unusable and rollforward follows therestore. Any tables with DATALINK columnsare placed in DRNP state.

v Rollforward was to a point-in-time, not to theend of logs. Any tables with DATALINKcolumns in that tablespace are placed in DRPstate.


v DATALINK column information does not existat the DB2 Data Links Manager(s). Affectedtables are placed in DRNP state.

v Rollforward involved DATALINK columnsdefined with the ″RECOVERY NO″ option.Affected tables are placed in DRP state.

If ″,...″ is displayed at the end of the node list,see the diagnostic log for the complete list ofnodes.


User Response: Look in the db2diag.log file tofind out what tables are put in DRP/DRNP state.See the Administration Guide for information onreconciling tables that are in DRP/DRNP state.

SQL4910N Overflow log path log-path is notvalid.

Explanation: The overflow log path specified onthe ROLLFORWARD command is not valid. Theoverflow log path must be a directory in a filesystem. This directory must be accessible by theinstance owner id.

User Response: Resubmit the command with avalid overflow log path.

SQL4911N The host variable data type is notvalid.

Explanation: The data type of the host variableis not valid.


User Response: Correct the data type of thehost variable and call the function again.

SQL4912N The host variable data length isout of range.

Explanation: The length of the host variable isnot valid.


User Response: Correct the length of the hostvariable and call the function again.

SQL4913N The host variable token ID hasalready been used.

Explanation: The token ID of the host variablehas already been used. The token ID must beunique within the module.


User Response: Correct the token ID of the hostvariable and call the function again.

SQL4914N The host variable token ID is notvalid.

Explanation: The token ID of the host variableis not valid.


User Response: Correct the token ID of the hostvariable and call the function again.

SQL4915N The “sqlainit” function hasalready been called.

Explanation: Precompiler Services has alreadybeen initialized.

User Response: No action is required. Continueprocessing.

SQL4916N The “sqlainit” function has notbeen called.

Explanation: Precompiler Services must beinitialized before the requested function call canbe processed.


User Response: Issue an sqlainit function call toinitialize Precompiler Services.

SQL4917N Element number in the optionarray is not valid.

Explanation: The option array contains anelement with an option.type or option.value that isnot valid. The element number in the message is


the nth element in the option portion of theoption array.


User Response: Correct the values stored in theoption array. Call the function again.

SQL4918N The term_option parameter offunction “sqlainit” is not valid.

Explanation: The term_option parameter is notvalid.


User Response: Correct the term_optionparameter and call the function again.

SQL4919N The task_array parameter offunction “sqlacmpl” is too small.

Explanation: The task array structure passed toPrecompiler Services on the sqlacmpl functioncall is too short.

The function did not complete successfully.

User Response: Increase the size of theprecompiler task array structure allocated by theprecompiler. Recompile the application program.

SQL4920N The token_id_array parameter offunction “sqlacmpl” is too small.

Explanation: The token id array structurepassed to Precompiler Services on the sqlacmpl()function call is too small.

The function did not complete successfully.

User Response: Increase the size of theprecompiler token id array structure allocated bythe precompiler. Recompile the applicationprogram.

SQL4930N Bind or precompile option oroption value option-name isinvalid.

Explanation: Either option-name is an invalidbind or precompile option or the value specified

for this option is invalid. The bind or precompilecannot continue.

User Response: Correct the bind or precompileoption or option value and retry the bind orprecompile command.

SQL4940N The clause clause is not permittedor is required.

Explanation: The indicated clause is either notallowed in the context where it appears in theSQL statement or it is required in the 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 statements used in cursordeclarations cannot have an INTO clause.

An embedded SELECT statement must have anINTO clause.


User Response: Remove or add the clause tocorrect the statement.

SQL4941N The SQL statement is blank orempty.

Explanation: The text following EXEC SQL wasblank or empty.


User Response: Ensure that a valid SQLstatement is provided following the word EXECSQL.

SQL4942N The statement selects anincompatible data type into hostvariable name.

Explanation: An embedded SELECT statementselects into a host variable name but the datatype of the variable and the correspondingSELECT list element are not compatible. If thedata type of the column is date and time, thedata type of the variable must be character with


an appropriate minimum length. Both musteither be numeric, character, or graphic. For auser-defined data type, the host variable mightbe defined with an associated built-in data typethat is not compatible with the result type of theFROM SQL transform function defined in thetransform group for the statement.


User Response: Verify that the table definitionsare current and that the host variable has theproper data type.

SQL4943W The number of host variables inthe INTO clause is not the sameas the number of items in theSELECT clause.

Explanation: The number of host variablesspecified in both the INTO clause and theSELECT clause must be the same.

The function is processed.

User Response: Correct the application programto specify the same number of host variables asSELECT list expressions.

SQL4944N An update or insert value isNULL but the object columncannot contain NULL values.


v The update or insert value was NULL but theobject column is declared as NOT NULL in thetable definition. Therefore, null values cannotbe inserted into that column, and values inthat column cannot be set to NULL by anupdate.

v The column name list for the INSERTstatement omits a column that was declared asNOT NULL in the table definition.

v The view for the INSERT statement omits acolumn that was declared as NOT NULL inthe base table definition.


User Response: Examine the definition of theobject table to determine which columns of the

table have the NOT NULL attribute, and correctthe SQL statement.

SQL4945N The use of a parameter marker isnot valid.

Explanation: Parameter markers can be usedonly in dynamic SQL statements.


User Response: Use host variables instead ofparameter markers for static SQL statements.

SQL4946N The cursor or statement namename is not defined.

Explanation: The cursor or statement namename specified in the statement is not defined.


User Response: Check the application programfor completeness and possible spelling errors inthe cursor or statement names.

SQL4947W An INCLUDE SQLDA statementwas encountered and ignored.

Explanation: The FORTRAN precompilershipped by the database manager does notsupport the INCLUDE SQLDA statement.

The statement is ignored. Processing continues.

User Response: No action is required. Toprevent this message, remove the INCLUDESQLDA statement from the program.

SQL4950N Compound SQL statementscontaining user-defined SQLDAsare not supported in thisenvironment.

Explanation: Compound SQL statementscontaining user-defined SQLDAs are notsupported in a 16-bit application.

User Response: Move the statement out of thecompound SQL block or replace the statementwith one that uses host variables instead of anSQLDA.


SQL4951N The sqlda_id parameter offunction name is not valid.

Explanation: The sqlda_id parameter of thespecified function in the application program isnot valid. The sqlda_id parameter cannot be null.


User Response: Correct the sqlda_id parameterin the application program.

SQL4952N The sqlvar_index parameter offunction name is not valid.

Explanation: The sqlvar_index parameter of thespecified function in the application program isnot valid. The sqlvar_index may be larger than thenumber of sqlvar elements in the SQLDA.


User Response: Correct the sqlvar_indexparameter in the application program.

SQL4953N The call_type parameter offunction name is not valid.

Explanation: The call_type parameter of thespecified function in the application is not valid.


User Response: Correct the call_type parameterin the application program.

SQL4954N The section_number parameter offunction name is not valid.

Explanation: The section_number parameter ofthe specified function in the application programis not valid. Note that for the following SQLstatements, the section_number parameter of thefunction sqlacall() is used to pass in thestatement type:

v CONNECT

v SET CONNECTION

v RELEASE

v DISCONNECT


User Response: Correct the section_numberparameter in the application program.

SQL4970N Roll-forward recovery on databasename cannot reach the specifiedstop point (end-of-log orpoint-in-time) because of missinglog file(s) on node(s) node-list.

Explanation: This message is returned in thefollowing situations:

v a request was made to bring the specifieddatabase out of roll-forward pending state byspecifying caller actionSQLUM_ROLLFWD_STOP, SQLUM_STOP,SQLUM_ROLLFWD_COMPLETE, orSQLUM_COMPLETE but the RollforwardDatabase utility cannot find the necessaryarchive log file(s) in the database log directoryor the overflow log directory on the specifiednode(s) to reach the stopping point from theprevious ROLLFORWARD DATABASEcommand.

v in a multi-node environment, if theRollforward Database utility cannot find thenecessary archive log file(s) to bring a nodeinto synchronization with the catalog node.


Roll-forward recovery has stopped. The databaseis left in roll-forward pending state.

Note : if you are using a partitioned databaseserver, the node number(s) indicate whichnode(s) the error occurred on. Otherwise, it isnot pertinent and should be ignored.

User Response: Use the ROLLFORWARDDATABASE command with the QUERY STATUSoption to determine which log files are missing.

Do one of the following:

v Make sure that all archive log files areavailable in the database log directory or theoverflow log path, and issue theROLLFORWARD DATABASE command again.


v If you cannot find the missing log files, restorethe database/table space on all nodes, then dopoint-in-time recovery using a timestamp thatis earlier than that of the earliest missing logfile.

SQL4971N Roll-forward recovery on databasename on node node-number failedpreviously while stopping.Roll-forward recovery must bestopped.

Explanation: A request was made to continuerolling forward the specified database byspecifying caller action SQLUM_ROLLFWD. Theprevious iteration of roll-forward recovery failedwhile stopping. If rolling forward at the databaselevel, this means that it failed during logtruncation. Roll-forward recovery for thisdatabase must now be stopped by specifyingcaller action SQLUM_ROLLFWD_STOP,SQLUM_STOP,SQLUM_ROLLFWD_COMPLETE, orSQLUM_COMPLETE.

Note : if you are using a partitioned databaseserver, the node number indicates which nodethe error occurred on. Otherwise, it is notpertinent and should be ignored.

User Response: Reissue the ROLLFORWARDDATABASE command with caller actionSQLUM_ROLLFWD_STOP, SQLUM_STOP,SQLUM_ROLLFWD_COMPLETE, orSQLUM_COMPLETE. Any stoptime specifiedwill be ignored since the previous stoptime isalready being processed.

SQL4972N Log extent extent on nodenode-number could not be movedto the database logpath.

Explanation: The Rollforward utility wasinvoked with the STOP option. As part ofroll-forward processing, the log extent extent hasto be truncated. This extent must exist in thedatabase logpath. Currently, the extent exists inthe overflow log path. An attempt was made tomove the extent from the overflow log path tothe database logpath. The attempt failed.Roll-forward processing has been stopped.

Note : if you are using a partitioned databaseserver, the node number indicates which nodethe error occurred on. Otherwise, it is notpertinent and should be ignored.

User Response: Move the extent from theoverflow log path to the database logpath andthen resubmit the ROLLFORWARD DATABASEcommand.

SQL4973N Forward recovery on databasename cannot complete because thelog information on node(s)node-list does not match thecorresponding record(s) on thecatalog node.

Explanation: The Rollforward utility processedall the log files found on each node, but the stoppoints on the specified nodes do not match thecorresponding records on the catalog node. Thiscan be caused by missing log files on either thecatalog node or on the specified nodes, or thecatalog node must be included in the list ofnodes to be rolled forward.

The ROLLFORWARD DATABASE processingstops.


v Check if the catalog node needs to be rolledforward. If it does, submit theROLLFORWARD DATABASE command againand include the catalog node.

v Use the ROLLFORWARD DATABASEcommand with the QUERY STATUS option todetermine which log files are missing. Whenyou find the log files, put them in the log pathor overflow log path and resume forwardrecovery.

v If you cannot find the missing log files, restorethe database on all nodes, then dopoint-in-time recovery using a stoptime that isearlier than that of the earliest missing log file.

SQL4974W The ROLLFORWARD DATABASEQUERY STATUS commandencountered sqlcode sqlcode.

Explanation: The ROLLFORWARD DATABASEQUERY STATUS command encountered an error


with the sqlcode sqlcode. The query might not besuccessful on some nodes for various reasons.The most severe error is indicated by sqlcode. Theroll-forward status is only returned for thesuccessful nodes.

User Response: Look up the sqlcode sqlcode inthe Message Reference, or online to determine theproblems on the failed nodes. Take the requiredcorrective actions, then continue the forwardrecovery on these nodes.

SQL4975W Roll-forward operation wascancelled successfully. Thedatabase or selected table spaceshave to be restored on node(s)node-list.

Explanation: A roll-forward operation wascancelled before it successfully completed, andthe database or selected table spaces are left in inan inconsistent state. The database or selectedtable spaces are in restore pending state on thelisted nodes.


Note : if you are using a partitioned databaseserver, the node number(s) indicate whichnode(s) the error occurred on. Otherwise, it isnot pertinent and should be ignored.

User Response: Restore the database or selectedtable spaces on the listed nodes. The table spacesthat are in restore pending state can be identifiedon the specified node(s) by the LISTTABLESPACES command or the db2dart utility.

SQL4976N The ROLLFORWARD DATABASEcommand cannot be submitted ona non-catalog node.

Explanation: The ROLLFORWARD DATABASEcommand is only accepted on the catalog node.

User Response: Submit the command on thecatalog node.

SQL4977N Dropped table export directorydirectory is not valid.

Explanation: The export directory path specifiedon the ROLLFORWARD command is not valid.The export directory path must be a directory ina file system. This directory must be accessibleby the instance owner id.

User Response: Resubmit the command with avalid export directory path.

SQL4978N The dropped table can not beaccessed.

Explanation: The dropped table can not beaccessed. This may be due to the table being putinto unavailable state because of a LOADwithout copy or a NOT LOGGED INITIALLYoperation.

User Response: The table can not be recoveredusing the DROPPED TABLE RECOVERY option.

SQL4979W Unable to export the droppedtable data.

Explanation: The command was unable toexport the data of the dropped table whoserecovery is being attempted. This can happenwhen the dropped table id specified on theROLLFORWARD command is invalid, or whennot all of the logs are available for roll forward.This warning will be generated when an erroroccurs during a dropped table recovery using aROLLFORWARD ... AND STOP command.

User Response: Resubmit the command afterensuring that the dropped table id provided isvalid, and that all of the logs are available forroll forward.

SQL4994N Precompilation was endedbecause of a user interruptrequest.

Explanation: Precompilation was terminatedbecause of an interrupt. The user may havepressed an interrupt key sequence.

Processing is terminated. No package wascreated.


User Response: Resubmit the precompilation ifneeded.

SQL4997N The authorization ID is not valid.

Explanation: The authorization ID for theapplication was specified previously but it wasdefined with more than 8 characters or withcharacters that are not valid for an authorizationID.

The authorization ID must not be PUBLIC(public) and it must not begin with SYS (sys),IBM (ibm), or SQL (sql). Also, it must not containthe underscore character or any charactersoutside the database manager base character set.


User Response: Retry the application with avalid authorization ID.

SQL4998C The application state is in error;the database connection has beenlost.

Explanation: The connection to the database hasbeen lost.


User Response: Reconnect to the database.

SQL4999N A Precompiler Services orRun-Time Services error occurred.

Explanation: A database manager erroroccurred that prevents Precompiler Services orRun-Time Services from processing function calls.

No Precompiler Services or Run-Time Servicesfunction calls can be processed.

User Response: Record the message number(SQLCODE) and all error information from theSQLCA if possible.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt.v Environment: Outer Precompiler Using

Precompiler Services API

v Required information:

– Problem description

– SQLCODE

– SQLCA contents if possible

– Trace file if possible.

SQL5000 - SQL5099

SQL5001N authorization-ID does not have theauthority to change the databasemanager configuration file.

Explanation: The user attempted to Update orReset the database manager configuration filewithout having SYSADM authority.


User Response: Do not attempt to change thedatabase manager configuration file withoutappropriate authorization. Contact a user withSYSADM authority if a change is required.

SQL5005C System Error.

Explanation: A system error, probably an I/Oerror, was encountered while accessing aconfiguration file.



If the error persists, check the db2diag.log file fordetails and ensure that the configuration file isaccessible. If unable to resolve the problem,contact an IBM Service Representative forassistance.

SQL5010N The path name to the databasemanager configuration file is notvalid.

Explanation: An error occurred whiledetermining the path for the database managerconfiguration file. The database managerdirectory structure may have been altered.


User Response: Resubmit the command. If theerror continues, reinstall the database manager.


SQL5012N Host variable host-variable is notan exact numeric data type.

Explanation: A host variable host-variable wasspecified, but it is not valid in the context inwhich it was used. Host variable host-variable wasspecified as part of ABSOLUTE or RELATIVE ina FETCH statement, or in a ROWS clause of aFETCH or INSERT statement. The host variablewas not usable for one of the following reasons:

v The host variable is not an exact numeric datatype. Decimal data types with a scale of zeroand integer data types are exact numeric datatypes.

v The host variable is a decimal data type, butthe scale is not zero. Decimal data types musthave zero decimal digits to have a scale ofzero.


User Response: Change the host variable to bean exact numeric data type.

sqlcode: -5012

sqlstate: 42618

SQL5018N The entry in the databasemanager configuration file for themaximum number of remoteconnections to the workstation(numrc) is not in the valid range.

Explanation: The value for the maximumnumber of remote connections to the workstationmust be between 1 and 255.


User Response: Resubmit the command with avalid value for the maximum number of remoteconnections to the workstation.

SQL5020N The entry in the databasemanager configuration file for thenode name for the workstation(nname) is not valid.

Explanation: The node name specified in theconfiguration command is not valid. The nodename may be 1 to 8 characters. All the characters

must be chosen from the database manager basecharacter set.


User Response: Resubmit the command with avalid node name.

SQL5021N The entry in the databasemanager configuration file for theindex recreation time (indexrec) isnot valid. Possible values are 1(during index access) and 2(during database restart).

Explanation: An invalid value was passed toConfiguration Services for the Index RecreationTime flag (indexrec) in the database managerconfiguration file. The invalid value may havebeen entered through the Command LineProcessor or through a program API call. Theonly valid values for the API call are 1 (duringdatabase access), and 2 (during database restart).The valid values for the command line processorare ACCESS and RESTART.

The update to the database managerconfiguration file is rejected.

User Response: Repeat the update request,entering one of the possible values.

SQL5022N The entry in the databaseconfiguration file for the indexrecreation time (indexrec) is notvalid. Possible values are 0 (usesystem setting), 1 (during indexaccess), and 2 (during databaserestart).

Explanation: An invalid value was passed toConfiguration Services for the Index RecreationTime flag (indexrec) in a database configurationfile. The invalid value may have been enteredthrough the Command Line Processor or througha program API call. The only valid values for theAPI call are 0 (use system setting), 1 (duringindex access), and 2 (during database restart).

The valid values for the command line processorare SYSTEM, ACCESS, and RESTART.


The update to the database configuration file isrejected.

User Response: Repeat the update request,entering one of the possible values.

SQL5025C The database managerconfiguration file is not current.

Explanation: The database managerconfiguration file has been updated since youconnected to the database. It is not compatiblewith the configuration for the database to whichyou are connected.

No access is allowed to the database managerconfiguration file.

User Response: Wait until all applicationsdisconnect from the databases. Issue the stopdatabase manager command, and then issue thestart database manager command.


SQL5028N The value of sysadm_group mustbe the primary group of theinstance owner.

Explanation: An attempt was made to updatesysadm_group in the database managerconfiguration file. For Version 2 of DB2 onUnix-based platforms, this value is only allowedto be the primary group of the instance owner.

User Response: Use the primary group of theinstance owner to update this field in thedatabase manager configuration file onUnix-based platforms.

SQL5030C The release number is not valid.

Explanation: The release number in thedatabase manager configuration file or databaseconfiguration file is not valid.


User Response: Verify that the release levels ofyour database and DB2 match.


sqlcode: -5030

sqlstate: 58031

SQL5035N The database requires migrationto the current release.

Explanation: The database was created on alower level system release. The Migrate Databasecommand must be used to convert the databaseto the current release level.


User Response: Perform the Migrate Databasecommand before attempting to use the databasewith the current system release.

If this message is received during a restore, dropthe existing database before proceeding.

sqlcode: -5035

sqlstate: 55001

SQL5040N One of the socket addressesrequired by the TCP/IP serversupport is being used by anotherprocess.

Explanation: One of the socket addressesrequired by the server either is in use by anotherprogram, or has not been freed completely by theTCP/IP subsystem after the database managerhas been stopped.

User Response: If you have just issued db2stop,wait for a couple of minutes so that the TCP/IPsubsystem has enough time to clean up itsresources. Otherwise, make sure no otherprograms on your workstation are using the portnumbers reserved for your service name in the/etc/services file. The port number is acomponent of a socket address.

SQL5042N One of the communicationprotocol server support processesfailed to start up.

Explanation: Due to system call failure, or acommunication subsystem call failure, one of thecommunication protocol server support processesdid not start up successfully.


User Response: You can investigate the problemby either:

v examine the system log records;

v turning on trace, run db2start again, thenexamine the trace record.

SQL5043N Support for one or morecommunications protocols failedto start successfully. However,core database managerfunctionality started successfully.

Explanation: Communication protocol supportdid not start successfully for one or moreprotocols. Possible reasons can include thefollowing:

v Communication subsystem configuration error.

v Communication subsystem call failure.

v Database manager configuration error.

v System call failure.

v Database manager licensing error.

You can still connect to the server withcommunication protocols that did startsuccessfully. Local clients can also connect to theserver.

User Response: The database manager attemptsto start all communication protocols specified bythe DB2COMM environment variable.

Check the administration notification log fordetails on this error. The log will contain moreinformation on the cause of the error and alsowhich communication protocol(s) did not startsuccessfully.

This error only affects communication protocolsspecified by the DB2COMM environmentvariable.

SQL5047C Insufficient memory to executethis function.

Explanation: There is not enough memoryavailable to execute this function.


User Response: Stop the application. Possiblesolutions include:v Terminate other processes.

v Decrease the values of the configurationparameters that define allocation of memory.

v Ensure that your system has sufficient real andvirtual memory.

SQL5048N The release level of the databaseclient is not supported by therelease level of the databaseserver.

Explanation: Database clients can only accessdatabase servers with a release level which is inthe range of one level lower than the client totwo levels higher than the client.


v Upgrade the client release level to fall withinthe range of releases supported by the currentserver release level.

v Upgrade the server release level to a levelsupported by the current client release level.

SQL5050C The content of the databasemanager configuration file is notvalid.

Explanation: The database managerconfiguration file is not valid. The file may havebeen altered by a text editor or a program otherthan the database manager.


User Response: Reinstall the database manager.

SQL5051N An object qualified by qualifiercannot be created in schemaschema-name.

Explanation: An object created in a CREATESCHEMA statement is qualified by qualifierwhich is different from the schema name. Allobjects created in a CREATE SCHEMA statementmust be either qualified by the schema nameschema-name or not qualified. Unqualified objectsare implicitly qualified by the schema name.



User Response: Explicitly qualify the object inthe schema with schema-name or remove qualifierfrom the object name.

sqlcode: -5051

sqlstate: 42875

SQL5055C The content of the databaseconfiguration file is not valid.

Explanation: The database configuration file forthe database is not valid. The file may have beenaltered by a text editor or a program other thanthe database manager.

User Response: Recreate the database or restoreit from a backup version.

sqlcode: -5055

sqlstate: 58031

SQL5060N The configuration parametertoken specified is invalid.

Explanation: A token number specified in thesqlfupd structure passed to a ConfigurationServices API is not valid. It does not representany of the supported configuration parameters.Alternatively, if an UPDATE was attempted, thetoken specified may be that of an unmodifiableconfiguration parameter.

User Response: Choose a valid token numberfrom those specified in the description of theConfiguration Services API in the ApplicationDevelopment Guide. Recode the call to the API,and rerun the program.

SQL5061N An invalid pointer to structuresqlfupd was passed toConfiguration Services.

Explanation: The pointer to structure sqlfupdpassed as a parameter to one of theConfiguration Services APIs was invalid. It iseither NULL, or does not point to an allocatedblock of memory of the size indicated by thecount parameter. See the Application DevelopmentGuide for more information.

User Response: Correct the code which invokes

the Configuration Services API, and retry the APIcall.

SQL5062N An invalid pointer was passedwithin the sqlfupd structure toConfiguration Services.

Explanation: The structure sqlfupd passed as aparameter to one of the Configuration ServicesAPIs contained an invalid pointer. The pointer iseither NULL, or does not point to an allocatedblock of memory. Each token passed in thestructure must have a corresponding pointer to afield that is either passed in or out of the API.See the Application Development Guide for moreinformation.

User Response: Correct the code which invokesConfiguration Services, and rerun the program.

SQL5065C The nodetype value in databasemanager configuration file is notvalid.

Explanation: The nodetype parameter in thedatabase manager configuration file is not valid.


User Response: Reinstall the database manager.

SQL5066W The database configurationparameter value for tokentoken-name has been truncated.

Explanation: The database configurationparameter value is larger than the specifiedtoken can contain.

A new token now represents this databaseconfiguration parameter value and should beused if the value is larger than can be containedby the old token.

User Response: Use the new token for thisdatabase configuration parameter.


SQL5070N The count parameter in theconfiguration command is notvalid. It must be greater than 0.

Explanation: The count value passed as aparameter to a Configuration Services API mustbe greater than 0.


User Response: Correct the code which invokesConfiguration Services, and rerun the program.

SQL5075N The configuration utility wasinterrupted.

Explanation: An interrupt was received by theconfiguration utility. The user may have pressedthe interrupt key sequence.

The command was not processed. Any requestedchange is not made.


SQL5076W The update completedsuccessfully. The current value ofNOTIFYLEVEL will cause somehealth monitor notifications not tobe issued to the notification log.

Explanation: Health Monitor issues notificationsto the notification log and to specified e-mail andpage contacts. The current value ofNOTIFYLEVEL is set too low to havenotifications be issued for alarms and warnings.NOTIFYLEVEL must be set to 2 or higher foralarm notifications and 3 or higher for warningnotifications.

User Response: Increase the value of thedatabase manager configuration parameterNOTIFYLEVEL.

SQL5077N The parameter parameter is notsupported by the ConfigurationAdvisor for this server release.Supported parameters includesupported-parameters.

Explanation: The parameter specified is notsupported by this server release.

User Response: Reissue the command withoutthe parameter or replace it with anothersupported parameter.

SQL5081N The entry in the databaseconfiguration file for the size ofthe buffer pool (buffpage) is notin the valid range.

Explanation: The minimum value for the size ofthe buffer pool is two times the maximumnumber of active processes (maxappls). Themaximum value for the size of the buffer pool is524288 (number of 4KB pages) and is operatingsystem dependent. The maximum value underAIX is 51000 (204000 for Extended ServerEdition) (4KB pages). Under HP-UX, the valuemust be between 16 and 150000 (4KB pages).


User Response: Resubmit the command with avalid value for the size of the buffer pool.

SQL5083N The entry in the databaseconfiguration file for the initiallog file size (logfile) is not in thevalid range.

Explanation: The value for the initial log filesize must be between 12 and (2**32 − 1).


User Response: Resubmit the command with avalid value for the initial log file size.

SQL5091N The entry in the databaseconfiguration file for the size ofone log file extension (logext) isnot in the valid range.

Explanation: The value for the size of one logfile extension must be between 4 and 256.


User Response: Resubmit the command with avalid value for the size of one log file extension.


SQL5092N The entry in the databaseconfiguration file for themaximum allowable number oflog file extensions (logmaxext) isnot in the valid range.

Explanation: The value for the maximumallowable number of log file extensions must bebetween 0 and (2 * 10**6).


User Response: Resubmit the command with avalid value for the maximum allowable numberof log file extensions.

SQL5093N The entry for the databaseconfiguration parameter for thesize of the agent heap is not inthe valid range.

Explanation: The value for the size of the agentheap must be between 2 and 85.


User Response: Resubmit the command with avalid value for the agent heap size.

SQL5099N The path path-name indicated bythe database configurationparameter parameter is not valid,reason code reason-code.

Explanation: The path is not valid for one ofthe following reasons:

1 The path string is longer than 242 bytes.

2 The path does not exist.

3 The first directory in the path has aname in the form SQLNNNNN, whereNNNNN is a value from 00001 to 99999.

4 A file with the correct name was foundin the specified path, but is not a log filefor this database.

5 The path is currently being used byanother database.

6 The path is currently being used by thesame database for another purpose.

7 The device specified by the path is notbig enough to hold the log files.

8 A raw device cannot be specified as amirror log path or an overflow log path.

9 The path cannot be accessed.


User Response: Resubmit the command with avalid value for the path.

sqlcode: -5099

sqlstate: 08004

SQL5100 - SQL5199

SQL5100N The entry in the databasemanager configuration file for thenumber of allowed concurrentdatabases is too large.

Explanation: The requested change would cause(1) the number of allowed concurrent databasesto be too large or (2) the number of segmentsallowed for DB2 to be too small.

The number of allowed concurrent databases isrestricted by the maximum number of segmentsallowed for DB2. The following condition mustalways be true:

segments >=((number of databases * 5) + 1)



v Increase the maximum number of segmentsallowed for DB2.

v Decrease the number of allowed concurrentdatabases.


SQL5101N The entries in the databaseconfiguration file define log fileparameters (logprimary andlogsecond) that are not in thevalid range.

Explanation: The requested change would causethe total number of logfiles to be out of range.The following condition must always be true:

logprimary + logsecond <= 128


User Response: Do one or both of thefollowing:

v Decrease the number of primary log files.

v Decrease the number of secondary log files.

SQL5103N The entry in the databaseconfiguration file for the size ofthe buffer pool (buffpage) is toosmall for the maximum number ofactive applications (maxappls).

Explanation: The requested change would causethe maximum number of active applications tobe too large for the size of the buffer pool. Thefollowing condition must always be true:

bufferpool_size >(number of active_processes * 2)


User Response: Do one or both of thefollowing:

v Increase the size of the buffer pool.

v Decrease the maximum number of activeprocesses allowed.

SQL5112N The value of the configurationparameter parameter must be either0 or 1.

Explanation: The request is not completedbecause the value given for parameter is invalid.

User Response: Ensure that the value specifiedfor parameter is either 0 or 1, then try the requestagain.

SQL5120N Old and new log parameterscannot both be modified at thesame time.

Explanation: The user is attempting to modifyboth the previous log parameters and the newparameters. The application should only supportthe parameters of the current release.

The request is denied.

User Response: Modify only the parameters ofthe current release and retry the command.

SQL5121N The entry in the databaseconfiguration file forconfiguration options is not valid.

Explanation: The value set for database options(SQLF_DETS) is not valid. Valid settings arebetween 0 and 15. The requested change is notmade.


User Response: Resubmit the command with avalid database options value.

SQL5122N Access to the database was invalidbecause of a machine dependentcheck.

Explanation: The database and databaseconfiguration file cannot be accessed because ofcopy protection.

The user request is denied.

User Response: Return to the original databaseand modify the configuration file to turn thecopy protection off, then create a new backupwhich may be used to restore the database. Thismust be done by an individual with SYSADMauthority. If the original database is no longeravailable, contact your service representative.

SQL5123N Database name cannot beconfigured because an I/O erroroccurred while accessing the logcontrol file.

Explanation: An error occurred while accessingSQLOGCTL.LFH for the specified database.



User Response: Restore the database from abackup copy or recreate the database.

SQL5126N An attempt was made to modifythe database managerconfiguration parameter parmwhich is not valid for a node typeof node-type-code.

Explanation: The user attempted to modify adatabase manager configuration parameter whichis invalid for the given node type.″<node-type-code″> is defined as follows:

1 Database server with local and remoteclients

2 Client

3 Database server with local clients

4 Partitioned Database Server with localand remote clients

5 Satellite Database Server with localclients


User Response: Resubmit the request with avalid parameter for the given nodetype.

SQL5130N The value specified for theconfiguration parameter parameteris not in the valid range ofstart-of-range to end-of-range.

Explanation: The request is not done becausethe value of parameter is not within the validrange.

User Response: Ensure that the value specifiedfor parameter is within the valid range, then trythe request again.

SQL5131N The value specified for theconfiguration parameter parameteris not in the valid range. Thevalid range is ″-1″, or fromstart-of-range to end-of-range.

Explanation: The request is not done becausethe value of parameter is not within the validrange.


SQL5132N The configuration parameter isnull or too long. The maximumlength is maximum-length.

Explanation: The configuration parameter is notset or too long.

User Response: Change the value of theconfiguration parameter to within the maximumlength given.

SQL5133N The value value for configurationparameter parm is invalid. Thevalid set of values is value-list.

Explanation: value was the value specified forthe configuration parameter parm. This value isnot one of the allowable values shown in thevalue_list.

Consult the Application Development Guide(SQLFUPD entry) and the Administration Guidefor the meanings of these values.

User Response: Change the value of theconfiguration parameter to one of the valuesshown in the valid list.

SQL5134N The configuration parametertpname contains invalidcharacters.

Explanation: One or more characters in thetpname is not in the valid range. The charactersin the tpname must be one of the following:

v A - Z

v a - z


v 0 - 9

v $

v #

v @

v . (period)

User Response: Change the tpname and retrythe command or function call.

SQL5135N The settings of the maxlocks andmaxappls configurationparameters do not use all of thelocklist space.

Explanation: The number of active processes(maxappls) times the maximum percentage oflock list space for each application (maxlocks)must be greater than or equal to 100. That is:

maxappls * maxlocks >= 100

This ensures that all of the allocated locklistspace can be used.

User Response: Increase the setting formaxappls, maxlocks, or both.

SQL5136N The entry in the databasemanager configuration file for thedefault database path (dftdbpath)is invalid.

Explanation: An invalid value was specified bydftdbpath. The rules for the default databasepath on UNIX-based systems are:

1. the path must follow the operating system’snaming conventions

2. the path must exist

3. the path must be less than or equal to 215characters

The rules for other platforms (such as OS/2 andWindows) are:

1. the path must be a drive letter

2. the drive must exist

User Response: Change the dftdbpath and retrythe command or function call.

SQL5137N The entry in the databasemanager configuration file for thediagnostic directory path(diagpath) is invalid.

Explanation: An invalid value was specified fordiagpath. The rules for the diagnostic directorypath are:

1. the path must follow the operating system’snaming conventions

2. the path must exist

3. the path must be less than or equal to 215characters

User Response: Change the diagpath and retrythe command or function call.

SQL5140N The entry in the databasemanager configuration parameter“authentication” must be one ofSERVER, CLIENT, DCE,KERBEROS, SERVER_ENCRYPT,DCE_SERVER_ENCRYPT, orKRB_SERVER_ENCRYPT.

Explanation: The allowed values for theconfiguration parameter ″authentication″ are:

v SERVER = 0

v CLIENT = 1

v DCE = 3

v SERVER_ENCRYPT = 4

v DCE_SERVER_ENCRYPT = 5

v KERBEROS = 7

v KRB_SERVER_ENCRYPT = 8


User Response: Resubmit the command with avalid value for ″authentication″.

SQL5141N The configuration parameteravg_appls is out of range. Thevalid range is from 1 to the valueof maxappls.

Explanation: The allowable range for avg_applsis from 1 to the value of maxappls.




v Change the value of avg_appls to a value in thevalid range.

v Increase the value of maxappls to a highervalue, then set avg_appls again.

SQL5142N The configuration parameteragentpri is not in the valid range.

Explanation: The valid values for agentpri are-1, or a three digit number of which the firstdigit is a priority class ranging from 2 to 4 andthe last two digits are a priority level within theclass in the range of 00 to 31. The priority class isdefined as follows:

2 REGULAR

3 TIMECRITICAL

4 FOREGROUNDSERVER

For example, the number 304 would correspondto a priority class of 3 (TIMECRITICAL), with apriority level of 4.

User Response: Change the value of theconfiguration parameter to a value within thevalid range.

SQL5150N The value specified for theconfiguration parameter parameteris less than the minimumallowable value of minimum-value.

Explanation: The request is not completedbecause the value given for parameter is too low.parameter may not be less than minimum value


SQL5151N The value specified for theconfiguration parameter parameteris less than the minimumallowable value of minimum-valueand is not -1.

Explanation: The request is not completedbecause the value given for parameter is invalid.Except for an allowable value of -1, parameter

may not be less than minimum value.


SQL5152N The value specified for theconfiguration parameter parameteris greater than the maximumallowable value of maximum-value.

Explanation: The request is not completedbecause the value given for parameter is too high.parameter may not be greater than maximum value


SQL5153N The update cannot be completedbecause the following relationshipwould be violated: condition

Explanation: A valid configuration file mustmaintain the following relationship:

condition.

The update request could not be completedbecause the resulting configuration would violatethat relationship.

User Response: Resubmit the request, ensuringthat the relationship is satisfied.

SQL5154N The requested combination ofconfiguration values for″authentication″ and parameter isnot allowed.

Explanation: The database managerconfiguration parameter ″authentication″ musthave the value ″CLIENT″ if the value ofparameter is non-default.


User Response: Resubmit the command with avalid combination of configuration parametervalues.


SQL5155W The update completedsuccessfully. The current value ofSORTHEAP may adversely affectperformance.

Explanation: The value of SORTHEAP iscurrently greater than half the value of thedatabase manager configuration parameterSHEAPTHRES. This may cause performance tobe less than optimal.

User Response: Increase the value of thedatabase manager configuration parameterSHEAPTHRES and/or decrease the value ofSORTHEAP so that SHEAPTHRES is at leasttwice as large as SORTHEAP.

A larger ratio is desirable in most cases. See theAdministration Guide for recommendations onconfiguration parameter tuning.

SQL5156N The value of the databasemanager configuration parameter″trust_allclnts″ must be one ofNO, YES, or DRDAONLY.

Explanation: The allowed values for theconfiguration parameter ″trust_allclnts″ are:

v NO = 0

v YES = 1

v DRDAONLY = 2


User Response: Resubmit the command with avalid value for ″trust_allclnts″.

SQL5180N DB2 is unable to read thefederation configuration filefile-name.

Explanation: The federated configuration filecould not be found, or it could not be opened forreading.

User Response: Specify the federationconfiguration file in the DB2_DJ_INI registryvariable. Be sure that the file exists and isreadable.

SQL5181N The format of line line-number inthe federation configuration filefile-name is invalid.

Explanation: The specified line does not havethe proper format. The format should be:<variable-name> = <value>.

User Response: Put the specified line in theformat described in the preceding paragraph.

SQL5182N A required environment variable,variable-name, has not been set.

Explanation: In the federated configuration file,the environment variable variable-name isunlisted, or it is listed but has no value.

User Response: Consult the “AdministrationGuide” to find out what values can be assignedto the environment variable variable-name. Thenuse the db2set command to set this variable tothe value that you want it to have.

SQL5185N Pass-through to server-type datasources is not supported.

Explanation: The Pass-Through facility cannotbe used to access server-type data sources.


sqlcode: -5185

sqlstate: 428EV

SQL6000 - SQL6099

SQL6000N DB2 Conversion of QMF Data.

Explanation: This is the normal terminationmessage.



SQL6001N The prefix for the filename wasnot specified.

Explanation: The user executed a module of theSQLQMF facility directly rather than using theSQLQMF facility command.


User Response: Use the provided SQLQMFfacility command.

SQL6002N Communications Managerencountered a download error.

Explanation: Communications Managerencountered an error during the download of thehost file.


User Response: Review the CommunicationsManager message log.

SQL6003N The file exported from QMFcontains rows that are too long.The row length is number.

Explanation: The computed row size (the sumof the computed column sizes) exceeds themaximum of 7000 bytes.


User Response: Return to your QMF hostsession and run a query with fewer datacolumns selected. EXPORT the data again andthen try the SQLQMF facility command again.

SQL6004N function returned the unexpectedreturn code code.

Explanation: An unexpected error occurredduring processing. The CommunicationsManager or DB2 may not be installed orconfigured correctly.


User Response: Ensure that CommunicationsManager has been installed and the appropriatehost communications session is active. Retry thecommand after checking for other errors. If theproblem persists, contact your Communications

Manager system administrator.

SQL6005N An error occurred while readingthe downloaded QMF file.

Explanation: One of the following conditionswas encountered:

v The file could not be opened.

v The end of file was encountered prematurely.

v There was an I/O error while reading the file.


User Response: Review the CommunicationsManager message log. Retry the command. If theerror continues, contact your CommunicationsManager system administrator.

SQL6006N An error occurred while writing toan output file.


v Not enough space exists on the C: drive towrite the data.

v An output file could not be opened.

v An I/O error occurred while writing the file.

v An I/O error occurred while closing the file.

v The file is in use by another OS/2 process.

Federated system users: there isn’t enough spaceto hold the db2djlink output. Additional space isrequired for the temporary files that db2djlinkcreates and uses.


User Response: Check for sufficient disk spaceon the C: drive. Retry the command.

Federated system users: increase the size of thefile system where the federated server isinstalled. To estimate the amount of free spacedb2djlink needs on an AIX operating system,enter:

ls -e /install_directory/lib/libdb2euni.a


This command returns the number of bytes usedby the listed file. Multiply that number by 3. Theresult is an estimate of how much free space isneeded on the file system. Increase the size ofthe file system as necessary and retry thecommand.

SQL6007N The decimal number in row row,column column cannot beconverted to ASCII.

Explanation: The indicated decimal field couldnot be converted.


User Response: Verify that the host columndata type is DECIMAL. Retry the QMF EXPORTand then try the SQLQMF facility commandagain. If the error continues, rerun the QMFquery without the named column.

SQL6008N The file specified in the commandis not in QMF data format.

Explanation: The file specified by the filenameparameter is not in the expected QMF format.


User Response: Verify that you have typed thename correctly. If correct, return to your QMFhost session and issue the command EXPORTDATA TO filename again. Be sure to export usingthe QMF data format.

SQL6009N The file exported from QMFcontains Column name with awidth width that is too long. Themaximum column width is 4000bytes.

Explanation: The downloaded QMF file has acolumn width greater than 4000 bytes.


User Response: Return to your QMF hostsession, rerun the QMF query without the namedcolumn, and export the data again. Then run theSQLQMF facility command again.

SQL6010N The downloaded QMF file hasmore than 255 data columns.

Explanation: The file being processed has morethan 255 data columns.


User Response: Return to your QMF hostsession and rerun a query, selecting 255 or fewerdata columns. EXPORT the data again and thenrun the SQLQMF facility command again.

SQL6011N The data type number (type-text) ofcolumn name (positioned atcolumn number) cannot beprocessed.

Explanation: The QMF file contains a columnwith data type that is not supported.

The SQLQMF facility does NOT support thefollowing data types:

v LONG VARCHAR

v LONG VARGRAPHIC.

Only the SQLQMF facility SQLQMFDB supportsgraphic data types.


User Response: Return to your QMF hostsession and rerun the query without selecting thenamed column. Then run the SQLQMF facilitycommand again.

SQL6012N Too many parameters werespecified for the command.

Explanation: Too many parameters werespecified with the command.


User Response: Retry the command with thecorrect number of parameters.


SQL6013N Host filename host-filename iseither too long or does not beginwith an alphabetic character.

Explanation: The host filename does not beginwith an alphabetic character; or, if the host is aVM System, the host filename, filetype, or filemodeare too long.


User Response: Retry the command with acorrect host filename syntax.

SQL6014N Invalid command syntax, colon(’:’) should follow a keyword.

Explanation: Keyword parameters withoperands require the keyword to be immediatelyfollowed by a “:” character and then theoperand.


User Response: Verify the command syntax andretry the command.

SQL6015N The keyword is not recognized.

Explanation: The keyword parameter indicator(“/”) was followed by a value that is not akeyword.


User Response: Retry the command using adifferent keyword value.

SQL6016N Too many operands for theSystem/370 filename name.

Explanation: If the host is a VM System, thehost file name contains more than threespace-separate tokens. If the host is an MVSSystem, the host filename contains embeddedblanks.


User Response: Retry the command using adifferent keyword value.

SQL6017N More information may becontained in the Import messagelog name.

Explanation: The database IMPORT operationterminated with warning or error messages.

The command has left its work files allocated.

User Response: Use the message preceding thismessage and the IMPORT message log, if itexists, to decide if the IMPORT was successfuland to determine corrective action. If the importwas successful, erase the DEL, CRE, COL, andIML files.

SQL6018N No S/370 filename was specified.

Explanation: The S/370 filename is a requiredparameter.


User Response: Retry the command with a hostfilename.

SQL6019N Communications short session IDID is either too long or is invalid.

Explanation: The value provided for thecommunications short session ID is either longerthan one byte or is not alphabetic.


User Response: Retry the command with avalid value.

SQL6020N An import option was specifiedwithout also providing a databasename.

Explanation: No database name was providedand an import option was specified.

The command has terminated.

User Response: Retry the command andinclude a database name.


SQL6021N Data was successfully imported.

Explanation: This is a normal ending messagewhen the SQLQMF facility imports data to adatabase.


SQL6022N System database directory is notshared by all nodes.

Explanation: All nodes should be accessing onephysical copy of the system database directory.


User Response: Ensure that all nodes areaccessing the system database directory thatresides in the sqllib directory, then try therequest again.

SQL6023N The user does not have theauthority to run the Get TablePartitioning Information utility ontable name.

Explanation: The user attempted to retrievepartitioning information on the specified tablewithout the appropriate authorization (either theSYSADM or DBADM authority or theCONTROL or SELECT privilege on the table).


User Response: Do not attempt to call the GetTable Partitioning Information utility withoutappropriate authorization. Contact your systemadministrator for assistance.

SQL6024N Table or index name is not definedon node node-number.

Explanation: The application is connected tonode node-number, and the table or index name isnot defined.

The cause is one of the following:

v The node to which the application isconnected is not a member of the nodegroupin which the table or index was created.

v The node is not in use by that nodegroup.


User Response: Connect the application to anode on which the table or index is defined.Determine the nodegroup in which the table wascreated and obtain the list of nodes in thenodegroup by selecting the appropriate rowsfrom the NODEGROUPDEF catalog view. Thenodes whose IN_USE value is set to Y are theones on which the table or index is defined.

SQL6025N Database backed up on nodenode1 cannot be restored to nodenode2.

Explanation: The backup image used for therestore is a backup of the database on a differentnode.

User Response: Ensure that you have thecorrect backup image for the node, then try therequest again.

SQL6026N Database with catalog node node1cannot be restored to a databasewith catalog node node2.

Explanation: The catalog node can exist on onlyone node and there is a discrepancy between thebackup image and the node being restored to.This can occur in the following cases:

v The backup image specified catalog node node1and the restore was attempted on an existingdatabase whose catalog node is node node2.

v The restore was attempted to a new databaseand the catalog node has not been restoredfirst. (Restore the catalog node first to createthe database on all nodes).

User Response: Verify that the correct backupimage is being restored.

If you are restoring to an existing database andwant to change the catalog node to node2, theexisting database must be dropped first.

If you are restoring to a new database, restorethe catalog node node1 first.


SQL6027N The path path for the databasedirectory is not valid.

Explanation: The path path specified for eitherthe CREATE DATABASE or the CATALOGDATABASE command starts with the character’.’ or contains the character string ’/.’.


User Response: Ensure that the specified pathis a fully qualified path, does not start with thecharacter ’.’, and does not contain the characterstring ’/.’. Then try the request again.

SQL6028N Catalog database failed becausedatabase dbname was not found inthe local database directory.

Explanation: When cataloguing a local databaseinto the system database directory, thecommand/API has to be issued from a node onthe server where the database resides.

User Response: Reissue the command/APIfrom a node where the database resides.

SQL6030N START or STOP DATABASEMANAGER failed. Reason codereason-code.

Explanation: The reason code indicates theerror. The statement cannot be processed.

(1) Cannot access the sqllib directory of theinstance.

(2) The full path name added to the profilefilename is too long.

(3) Cannot open the profile file.

(4) The nodenum parameter value is notdefined in the db2nodes.cfg file in thesqllib directory.

(5) The nodenum parameter must bespecified when a command option isspecified.

(6) The port parameter value is not valid.

(7) The new couple hostname/port is notunique.

(8) The FORCE option cannot be specifiedwhen the NODENUM option isspecified.

(9) The hostname and port parameters mustbe specified when using the ADDNODEoption.

(10) Cannot update the db2nodes.cfg file inthe sqllib directory for the ADDNODEor RESTART option.

(11) The hostname parameter value is notvalid.

(12) The pointer to the sqledbstrtopt orsqledbstopopt structure is not valid.

(13) No port value is defined for your DB2instance id (/etc/services file onUNIX-based systems).

(14) The port value is not in the valid portrange defined for your DB2 instance id(/etc/services file on UNIX-basedsystems).

(15) A hostname value has no correspondingport 0 defined in the db2nodes.cfg filein the sqllib directory.

(16) The value specified for the command oroption parameter is not valid.

(17) The DROP option cannot be specifiedwhen the NODENUM option is notspecified.

(18) The value specified for the calleracparameter is not valid.

(19) Unable to create the UNIX socketdirectory /tmp/db2_<ver>_<rel>/$DB2INSTANCE.

(20) The node number specified with theADDNODE option already exists in thedb2nodes.cfg file or the node has beenalready been added since the last stopdatabase manager command was issued.

(21) The tablespace type specified with theADDNODE option is not valid.

(22) The tablespace node specified with theADDNODE option is out of range.


(23) The computer name parameter must bespecified for the ADDNODE option.

(24) The user name parameter must bespecified for the ADDNODE option.

(25) The computer name is not valid.

(26) The user name is not valid.

(27) The password is not valid.

(28) The password is expired.

(29) The user account specified is eitherdisabled, expired, or restricted.


(1) Ensure that the $DB2INSTANCE useridhas the required permissions to accessthe sqllib directory of the instance.

(2) Change the profile name to a shortername so that the total length of the fullyqualified path added to the profile namelength is smaller than theSQL_PROFILE_SZ defined in the filesqlenv.h.

(3) Ensure that the profile file exists.

(4) Ensure that the nodenum valuespecified is defined in the db2nodes.cfgfile in the sqllib directory and isbetween 0 and 999.

(5) Resubmit the command with thenodenum parameter specified.

(6) Ensure that the port value is between 0and 999. If a value is not specified, theport value defaults to 0.

(7) Ensure that the new couplehostname/port is not already defined inthe db2nodes.cfg file in the sqllibdirectory.

(8) Do not specify the FORCE option whenyou specify the NODENUM option.

(9) Ensure that the hostname and the portvalues are specified when you specifythe ADDNODE option.

(10) Ensure that the $DB2INSTANCE

username has write access to the sqllibdirectory of the instance, that there issufficient disk space, and the file exists.

(11) Ensure that the specified hostname isdefined on the system.

(12) Ensure that the pointer is not NULL andpoints to the sqledbstrtopt for thesqlepstr() API, or to the sqledbstopoptstructure for the sqlepstp() API.

(13) Ensure that the services file(/etc/services on UNIX-based systems)contains an entry for your DB2 instanceid.

(14) Ensure that you only use port valuesthat are specified in the services file(/etc/services file on UNIX-basedsystems) for your instance.

(15) Ensure that all the hostname valueshave a port 0 defined in thedb2nodes.cfg file in the sqllib directoryincluding the restart option parameters.

(16) Ensure that the value specified for theoption parameter is within the validrange.

(17) Specify the NODENUM option whenyou specify the DROP option.

(18) Ensure that the value specified for thecallerac parameter is within the validrange.

(19) Check the permission of the /tmpfilesystem to make sure all intermediatedirectories of /tmp/db2_<ver>_<rel>/$DB2INSTANCE can be created.

(20) Ensure that the correct node number isbeing specified. You must stop thedatabase manager to update thedb2nodes.cfg file with nodes that havebeen added to the system since theprevious stop database managercommand.

(21) Ensure that the value specified for thetablespace type is within the validrange.

(22) Ensure that the tablespace node value


specified is defined in the db2nodes.cfgand is between 0 and 999.

(23) Specify the computer name of thesystem on which the new node iscreated using the COMPUTER option.

(24) Specify a valid domain account username and password for the new nodeusing the USER and PASSWORDoptions.

(25) Resubmit the command with a validcomputer name.

(26) Resubmit the command with a validuser name.

(27) Resubmit the command with a validpassword.

(28) Change/update the account passwordand resubmit the command.

(29) Resubmit the command with a validuser account.

SQL6031N Error in the db2nodes.cfg file atline number line. Reason codereason-code.

Explanation: The statement cannot be processedbecause of a problem with the db2nodes.cfg file,as indicated by the following reason codes:

(1) Cannot access the sqllib directory of theinstance.

(2) The full path name added to thedb2nodes.cfg filename is too long.

(3) Cannot open the db2nodes.cfg file in thesqllib directory.

(4) A syntax error exists at line line of thedb2nodes.cfg file in the sqllib directory.

(5) The nodenum value at line line of thedb2nodes.cfg file in the sqllib directoryis not valid.

(6) The nodenum value at line line of thedb2nodes.cfg file in the sqllib directoryis out of sequence.

(7) The nodenum value at line line of thedb2nodes.cfg file in the sqllib directoryis not unique.

(8) The port value at line line of thedb2nodes.cfg file in the sqllib directoryis not valid.

(9) The hostname/port couple at line line ofthe db2nodes.cfg file in the sqllibdirectory is not unique.

(10) The hostname at line line of thedb2nodes.cfg file in the sqllib directoryis not valid.

(11) The port value at line line of thedb2nodes.cfg file in the sqllib directoryis not defined for your DB2 instance idin the services file (/etc/services onUNIX-based systems).

(12) The port value at line line of thedb2nodes.cfg file in the sqllib directoryis not in the valid port range defined foryour DB2 instance id in the services file(/etc/services on UNIX-based systems).

(13) The hostname value at line line of thedb2nodes.cfg file in the sqllib directoryhas no corresponding port 0.

(14) A db2nodes.cfg file with more than oneentry exists, but the database managerconfiguration is not MPP.

(15) The netname at line line of thedb2nodes.cfg file in the sqllib directoryis not valid.


(1) Ensure that the $DB2INSTANCE useridhas the required permissions to accessthe sqllib directory of the instance.

(2) Make the instance home directory pathname shorter.

(3) Ensure that the db2nodes.cfg file existsin the sqllib directory and is not empty.

(4) Ensure that at least 2 values are definedper line in the db2nodes.cfg file and thatthe file does not contain blank lines.


(5) Ensure that the nodenum value definedin the db2nodes.cfg file is between 0and 999.

(6) Ensure that all the nodenum valuesdefined in the db2nodes.cfg file are inascending order.

(7) Ensure that each nodenum valuedefined in the db2nodes.cfg file isunique.

(8) Ensure that the port value is between 0and 999.

(9) Ensure that the new couplehostname/port is not already defined inthe db2nodes.cfg file.

(10) Ensure the hostname value defined indb2nodes.cfg at line line is both definedon the system and operational.

(11) Ensure that the services file(/etc/services on UNIX-based systems)contains an entry for your DB2 instanceid.

(12) Ensure that you only use port valuesthat are specified in the services file(/etc/services file on UNIX-basedsystems) for your instance.

(13) Ensure that the port value 0 has beendefined for the corresponding hostnamein the db2nodes.cfg file.

(14) Perform one of the following actions:

v Remove the db2nodes.cfg file.

v Alter the db2nodes.cfg file to containexactly one entry.

v Install Enterprise Server Edition.

(15) Ensure the netname value defined indb2nodes.cfg at line line is both definedon the system and operational.

SQL6032W Start command processing wasattempted on total-number node(s).number-started node(s) weresuccessfully started.number-already-started node(s) werealready started. number-not-startednode(s) could not be started.

Explanation: The database manager did notstart successfully on all the nodes. Not all of thedata in the database may be accessible. Data onthe nodes that started successfully or werealready running is accessible.

User Response: Check the log file created in thelog directory of the sqllib directory for theinstance to see which nodes did not start.

SQL6033W Stop command processing wasattempted on total-number node(s).number-stopped node(s) weresuccessfully stopped.number-already-stopped node(s) werealready stopped.number-not-stopped node(s) couldnot be stopped.

Explanation: The database manager did notstop successfully on all the nodes. The databasemanager is still active on the nodes that couldnot be stopped.

User Response: Check the log file created in thelog directory of the sqllib directory for theinstance to see which nodes did not stop.

SQL6034W Node node is not being used byany databases.

Explanation: During DROP NODE VERIFYprocessing, all databases are scanned to verifythat this node does not exist in the nodegroupsof any database, and that no event monitor isdefined on this node.

User Response: This node can now be removedfrom the system by issuing the ’db2stop dropnodenum <node>’ command.


SQL6035W Node node is being used bydatabase database.

Explanation: During DROP NODE VERIFYprocessing, databases are scanned to verify thatthis node does not exist in the nodegroups ofany database, and that no event monitor isdefined on this node. Node node is being used bydatabase database and cannot be dropped.

User Response: You must do the followingbefore dropping the node:

1. Redistribute the data to remove it from thenode using the REDISTRIBUTENODEGROUP command. Use either theDROP NODE option of the REDISTRIBUTENODEGROUP command or the ALTERNODEGROUP statement to drop the nodefrom the nodegroup. This must be done forall nodegroups in which the node to bedropped is a member.

2. Drop any event monitors that are defined onthe node.

3. Issue the ’db2stop drop nodenum <node>’command to drop the node.

SQL6036N START or STOP DATABASEMANAGER command is alreadyin progress.

Explanation: A START DATABASE MANAGERor a STOP DATABASE MANAGER command isalready in progress on the system.

User Response: Wait for the command inprogress to complete, then try the request again.

SQL6037N START or STOP DATABASEMANAGER timeout value wasreached.

Explanation: The start_stop_time value definedin the database manager configuration wasreached at the node. This value specifies thetime, in minutes, in which a node must respondto a Start Database Manager, Stop DatabaseManager or Add Node command.


v Check the administration notification log tosee if an error message has been logged for thenode which timed out. If an error has not beenlogged, and timeouts persist, you may need toincrease the start_stop_time value specified inthe database manager configuration file.

v If the timeout occurred during a StartDatabase Manager command, you should issuea Stop Database Manager command for allnodes which timed out.

v If the timeout occurred during a Stop DatabaseManager command, you should issue a StopDatabase Manager command for all nodeswhich timed out or for all nodes. Any nodewhich is already stopped will return with amessage stating that the node is stopped.

SQL6038N No partitioning key is defined.

Explanation: The user attempted to use the GetRow Partitioning Information utility withoutspecifying a partitioning key.


User Response: Ensure that you specify apartitioning key, then try the request again.

SQL6039N Partitioning column column-numberis currently defined as notnullable.

Explanation: An attempt was made to assign anull value to partitioning column column-number,which is not nullable.


User Response: Assign a non-null value orchange the type of the partitioning column to benullable.

SQL6040C No FCM buffers are available.

Explanation: No FCM buffer is available.


User Response: Try the request again.

If the error persists, increase the number of FCMbuffers ( fcm_num_buffers) specified in the


database manager configuration file, then try therequest again.

sqlcode: -6040

sqlstate: 57011

SQL6041C No FCM connection entries areavailable.

Explanation: No FCM connection entry isavailable. FCM is unable to increase the numberof connection entries automatically because themaximum value has been reached.


User Response: Try the request again afterother processes have freed up some of thisresource.

sqlcode: -6041

sqlstate: 57011

SQL6042C No FCM message anchors areavailable.

Explanation: No FCM message anchor isavailable. FCM is unable to increase the numberof message anchors automatically because themaximum value has been reached.


User Response: Try the request again afterother processes have freed up some of thisresource.

sqlcode: -6042

sqlstate: 57011

SQL6043C No FCM request blocks areavailable.

Explanation: No FCM request block is available.FCM is unable to increase the number of requestblocks automatically because the maximum valuehas been reached.


User Response: Try the request again after

other processes have freed up some of thisresource.

sqlcode: -6043

sqlstate: 57011

SQL6044N The syntax of the stringrepresentation string with value ofdatatype datatype-value and lengthlength is not correct.

Explanation: The specified string cannot berecognized as the target datatype. (TheApplication Development Guide containsinformation on datatypes.) Either the syntax isnot valid or the value is out of range.


User Response: Ensure that the stringrepresentation or the datatype is correct, then trythe request again.

SQL6045N The datatype datatype-value oflength datatype-length is notsupported.

Explanation: The datatype and data length arenot supported for a partitioning key.


User Response: See the Administration Guide forinformation about datatypes. See the APIReference for information about the Get RowPartitioning Information API.

SQL6046N Specified DROP NODE action isnot valid.

Explanation: The value specified for the actionparameter of the DROP NODE command is notvalid. Only the verify mode is supported for theDROP NODE command. The parameter must beset to the value SQL_DROPNODE_VERIFY.


User Response: Ensure that the action is set toSQL_DROPNODE_VERIFY, then try the requestagain.


SQL6047N Nodegroup cannot beredistributed because table namedoes not have a partitioning key.

Explanation: At least one table in thesingle-node nodegroup does not have apartitioning key. All tables in the single-nodenodegroup must have a partitioning key beforethe nodegroup can be redistributed to amultiple-node nodegroup.

The operation was not performed.

User Response: Use the ALTER TABLEcommand to specify partitioning keys for tablesthat do not have one. Then try the request again.

SQL6048N A communication error occurredduring START or STOPDATABASE MANAGERprocessing.

Explanation: A TCP/IP communication erroroccurred while the START or STOP DATABASEMANAGER command was trying to establishconnection with all the nodes defined in thesqllib/db2nodes.cfg file.


v Ensure that the node has the properauthorization defined in the .rhosts or thehost.equiv files.

v Ensure that the application is not using morethan (500 + (1995 - 2 *total_number_of_nodes)) file descriptors at thesame time.

v Ensure all the Enterprise Server Editionenvironment variables are defined in theprofile file.

v Ensure the profile file is written in the KornShell script format.

v Ensure that all the host names defined in thedb2nodes.cfg file in the sqllib directory aredefined on the network and are running.

SQL6049N The log control file for databasename could not be found onnode(s) node-list.

Explanation: The SQLOGCTL.LFH file for thedatabase is not in the database directory on thespecified node(s).

The database was not started.


User Response: Either restore the database froma backup on the specified node(s), or re-createthe database.

SQL6050N An I/O error occurred whileaccessing the log control file fordatabase name on node(s) node-list.

Explanation: An error occurred while accessingthe SQLOGCTL.LFH file for the database on thespecified node(s).

The database cannot be used.


User Response: Either restore the database froma backup on the specified node(s), or re-createthe database.

SQL6051N Database name is not configuredfor roll-forward recovery onnode(s) node-list.

Explanation: The specified database is notconfigured for roll-forward recovery on thespecified node(s).

The database is not rolled forward on all nodes.


User Response: Ensure that recovery is requiredon the specified node(s), then restore the mostrecent backup version of the database on thesenodes.


SQL6052N Cannot roll forward database namebecause it is not in roll-forwardpending state on node(s) node-list.

Explanation: The specified database is not inthe roll-forward pending state on the specifiednode(s). This may be because the database hasnot been restored, or was restored with theWITHOUT ROLLING FORWARD option, orroll-forward recovery is complete on these nodes.




1. Ensure that recovery is required on thespecified node(s).

2. Restore a backup version of the database onthese nodes.

3. Issue the ROLLFORWARD DATABASEcommand.

SQL6053N Error exists in file file. Reasoncode = reason-code.

Explanation: There is an error in the specifiedfile as indicated by the reason code:

(1) The number of values in thepartitioning map file is not 1 or 4,096.

(2) The number of values in the distributionfile is not 4,096.

(3) The data in the distribution file is not ina valid format.

(4) The node number in the partitioningmap is not between 0 and 999.

(5) The sum of all the values in thedistribution file is greater than4,294,967,295.

(6) The specified target partition mapcontains a node number that is notdefined in SYSCAT.NODEGROUPDEFfor the specified nodegroup.


(1) Ensure that the partitioning map filecontains only a single value (if theresultant nodegroup is a single-nodenodegroup) or exactly 4,096 values (ifthe resultant nodegroup is a multinodenodegroup).

(2) Ensure that the distribution file containsexactly 4,096 values, one per hashpartition.

(3) Ensure that the values in thedistribution file are integers greater thanor equal to 0, and that the sum of all thedistribution values is less than or equalto 4,294,967,295.

(4) Ensure that the node numbers are in therange of greater than or equal to 0 andless than or equal to 999.

(5) Ensure that the sum of all thedistribution values for the 4,096partitions is less than or equal to4,294,967,295.

(6) Either issue ALTER NODEGROUP toadd the missing node(s) or change thepartitioning map file to exclude thenode(s) not defined insysibm.sysnodegroupdef.

SQL6054N The archive file name is not avalid log file for the databasename on node node-number.

Explanation: An archive log file exists in the logdirectory on the specified node, but it is notvalid.


User Response: To determine the correctarchive log file, issue the ROLLFORWARDDATABASE command with the QUERY STATUSoption. Move the correct archive log file to thedatabase log directory or, if the database is in aconsistent state, change the log path to point tothe correct archive file and issue theROLLFORWARD DATABASE command again.


SQL6055N The archive file name does notbelong to database name on nodenode-number.

Explanation: An archive log file in the logdirectory on the specified node does not belongto the specified database.



SQL6056N Nodegroup cannot beredistributed. Reason code =reason-code.

Explanation: The operation cannot be executed.The reason code indicates the error.

(1) The nodegroup specification is not legal.The resulting nodegroup afterredistribution would not contain anynodes.

(2) A previous redistribution operation didnot complete successfully.

(3) A redistribution operation is already inprogress.

(4) There is no previously abortedredistribution command to CONTINUEor ROLLBACK.

(5) No data redistribution is performedbecause the data in the nodegroup isalready distributed as specified.

(6) The REDISTRIBUTE NODEGROUPcommand was not submitted from thecatalog node.

(7) The REDISTRIBUTE NODEGROUPcommand is not available nor applicablein this non-partitioned version of theproduct.

(8) Redistribution is not allowed if there areuser temporary table spaces in thenodegroup with existing declaredtemporary tables.

(9) The REDISTRIBUTE NODEGROUPcommand is not allowed if there aretable spaces in the nodegroup withtables in the access mode No DataMovement (ACCESS_MODE=’D’ inSYSCAT.TABLES).


(1) Do not drop all the nodes of thenodegroup during redistribution.

(2) Identify why the previous redistributionfailed and take the required correctiveaction. Submit the REDISTRIBUTENODEGROUP command using eitherthe CONTINUE or ROLLBACK option.CONTINUE will complete thepreviously aborted redistributionoperation and ROLLBACK will undothe effects of the previously abortedoperation.

(3) Issue the next REDISTRIBUTIONNODEGROUP command after thecurrent one completes.

(4) You cannot invoke the CONTINUE orROLLBACK option on a nodegroup thatis not associated with a failedredistribution operation.

(5) Try using a different target partitioningmap or distribution file. Otherwise,redistribution is not necessary.

(6) Issue the command again from thecatalog node.

(7) Do not issue the REDISTRIBUTENODEGROUP command using thisversion of the product.

(8) Request redistribution again when thereare no declared temporary tables usingthe user temporary table spaces in thenodegroup.

(9) Execute SET INTEGRITY IMMEDIATE


CHECKED statement on the dependentimmediate materialized query andstaging tables of the tables in No DataMovement mode, and then issue theREDISTRIBUTE NODEGROUPcommand again.

SQL6057N Archive file name is not associatedwith the database name that wasrestored, or with the log filepreviously processed on nodenode-number.

Explanation: An archive log file is found in thelog directory on the specified node, but does notbelong to the specified database.



SQL6058N Roll-forward recovery stoppedbecause of error error whileretrieving log file name fordatabase name on nodenode-number.

Explanation: Roll-forward processing invokesthe db2uexit to retrieve the log file for thedatabase on the specified node. The error mayhave occurred in the db2uexit.


User Response: See the user exit documentationin the Administration Guide for a description ofthe error, and either resume or terminate theroll-forward recovery.

SQL6059N The point-in-time passed to theRollforward utility must begreater than or equal to timestamp,because database name on node(s)node-list contains information laterthan the specified time.

Explanation: An advanced virtual timestamp isin the database backup.



v Issue the command again with a point-in-timethat is greater than or equal to timestamp.

v Restore an earlier backup on node(s), thenissue the ROLLFORWARD DATABASEcommand again.

SQL6061N Roll-forward recovery on databasename cannot reach the specifiedstop point (end-of-log orpoint-in-time) because of missinglog file(s) on node(s) node-list.

Explanation: The Rollforward Database utilitycannot find the necessary log file(s) in thelogpath.


v Use the ROLLFORWARD DATABASEcommand with the QUERY STATUS option todetermine which log files are missing. Whenyou find the log files, put them in the log pathand resume forward recovery.

v If you cannot find the missing log files, restorethe database on all nodes, then dopoint-in-time recovery using a timestamp thatis earlier than that of the earliest missing logfile.


SQL6062N Roll-forward recovery on databasename cannot complete because thelog information on node(s)node-list does not match thecorresponding record(s) on thecatalog node.

Explanation: The Rollforward utility processedall the log files found on each node, but the stoppoints on the specified nodes do not match thecorresponding records on the catalog node. Thiscan be caused by missing log files on either thecatalog node or on the specified nodes, or thecatalog node must be included in the list ofnodes to be rolled forward.



v Check if the catalog node needs to be rolledforward. If it does, submit theROLLFORWARD command again and includethe catalog node.

v Use the ROLLFORWARD DATABASEcommand with the QUERY STATUS option todetermine which log files are missing. Whenyou find the log files, put them in the log pathand resume forward recovery.

v If you cannot find the missing log files, restorethe database on all nodes, then dopoint-in-time recovery using a timestamp thatis earlier than that of the earliest missing logfile.

SQL6063N Roll-forward recovery on databasename has stopped on node(s)node-list due to a change in log filesize.

Explanation: The Rollforward Database utilityhas stopped rolling forward because the log fileshave changed in size. It must be restarted toestablish the new log file size.

If ″,...″ is displayed at the end of the node list,see the diagnostic log for the complete list ofnodes.

Roll-forward recovery has stopped.

(Note : if you are using a partitioned database

server, the node number(s) indicate whichnode(s) the error occurred on. Otherwise, it isnot pertinent and should be ignored.)

User Response: Reissue the ROLLFORWARDcommand to continue.

SQL6064N SQL error sqlcode occurred duringdata redistribution.

Explanation: An error occurred during dataredistribution.


User Response: Look at the SQLCODE(message number) in the message for moreinformation. Make any required changes and trythe request again.

SQL6065N An error occurred while writing tofile file.


v The file could not be opened.

v An I/O error occurred while writing to thefile.

v An I/O error occurred while closing the file.

The command or the utility cannot be processed.

User Response: Ensure that the file exists andthat the file permissions allow write access. Trythe command or the utility again.

SQL6067W ROLLFORWARD DATABASEQUERY STATUS commandencountered sqlcode sqlcode.

Explanation: The ROLLFORWARD DATABASEQUERY STATUS command encountered an errorwith the sqlcode sqlcode. The query might not besuccessful on some nodes for various reasons.The most severe error is indicated by sqlcode. Theroll-forward status is only returned for thesuccessful nodes.

User Response: Look up the sqlcode sqlcode inthe DB2 Messages Reference, or online todetermine the problems on the failed nodes. Take


the required corrective actions, then continue theforward recovery on these nodes.

SQL6068W Rollforward operation wascancelled successfully. Thedatabase has to be restored onnode(s) node-list.

Explanation: A Rollforward operation wascancelled before it successfully completed, andthe database is left in an inconsistent state. Therestore pending flag is on for the listed nodes.


User Response: Restore the database on thelisted nodes.

SQL6069N The ROLLFORWARD DATABASEcommand cannot be submitted ona non-catalog node.

Explanation: The ROLLFORWARD DATABASEcommand is only accepted on the catalog node.

User Response: Submit the command on thecatalog node.

SQL6071N The requested operation cannotbe processed because a new nodehas been added to the system.The system must be stopped andstarted again before the operationcan be done.


v The request was issued from the new node,and this node cannot communicate with othernodes.

v A CREATE or DROP DATABASE operationwas requested before all nodes were stoppedand started again to include the new node.

User Response: Issue db2stop to stop all thenodes. When all nodes are successfully stopped,issue db2start to start all the nodes, including thenew node, then try the request again.

sqlcode: -6071

sqlstate: 57019

SQL6072N DB2START with the RESTARToption cannot proceed because thespecified node is already active.

Explanation: The node specified for restart isalready active on the system.

User Response: If necessary, issue a DB2STOPspecifying the node to stop and issue theDB2START command again to restart the node.

SQL6073N Add Node operation failed.SQLCODE = sqlcode.

Explanation: The Add Node operation failedwith sqlcode sqlcode.

User Response: Check the message associatedwith the sqlcode that is returned in either theDB2 Messages Reference, or online.

Take any required corrective action, then try therequest again.

SQL6074N Add Node operation failedbecause a Create or DropDatabase operation is currentlyexecuting.

Explanation: An Add Node operation cannotexecute concurrently with a Create or DropDatabase operation.

User Response: Wait for the Create or DropDatabase operation to complete, then try therequest again.

SQL6075W The Start Database Manageroperation successfully added thenode. The node is not active untilall nodes are stopped and startedagain.

Explanation: The db2nodes.cfg file is notupdated to include the new node until all nodesare simultaneously stopped by the STOPDATABASE MANAGER (db2stop) command.Until the file is updated, the existing nodescannot communicate with the new node.

User Response: Issue db2stop to stop all thenodes. When all nodes are successfully stopped,


issue db2start to start all the nodes, including thenew node.

SQL6076W Warning! This command willremove all database files on thenode for this instance. Beforecontinuing, ensure that there is nouser data on this node by runningthe DROP NODE VERIFYcommand.

Explanation: This procedure will remove all thedatabase partitions from the specified node.

User Response: Ensure that the DROP NODEVERIFY command was run before dropping thisnode. If using the API, ensure that the calleracparameter is specified correctly.

SQL6077W The db2stop DROP NODENUMprocedure ended successfully, butcould not remove all the files. Seethe file file for details.

Explanation: The db2stop DROP NODENUMprocedure ended successfully, but some user datafiles are still on the node.

User Response: Information in file file willindicate the directory structure from which filescould not be deleted.

SQL6078N The db2stop DROP NODENUMprocedure could not update thedatabase information for databasedbname.

Explanation: The db2stop DROP NODENUMprocedure could not access the catalog node fordatabase dbname.

User Response: Try the request again. If theproblem persists, contact your servicerepresentative.

SQL6079W The db2stop DROP NODENUMcommand was cancelledsuccessfully.

Explanation: The db2stop DROP NODENUMcommand was stopped before it beganprocessing.

User Response: None.

SQL6080W The Start Database Manageroperation successfully added inthe node, but no databasepartitions have been created onthe node. The node is not activeuntil all nodes are stopped andstarted again.

Explanation: The db2nodes.cfg file is notupdated to include the new node until all nodesare simultaneously stopped by the STOPDATABASE MANAGER (DB2STOP) command.Until the file is updated, the existing nodescannot communicate with the new node.

User Response: Issue DB2STOP to stop all thenodes. When all nodes are successfully stopped,issue DB2START to start all the nodes, includingthe new node. When all nodes are successfullystarted, the database system can be used.

SQL6081 A communication error caused aDB2STOP FORCE command totime out on this node.

Explanation: A communication error occurredon one or more of the database nodes, causingthe DB2STOP FORCE command to time out onthe current node, or, DB2STOP FORCEterminated because a severe error occurredduring FORCE on one or more nodes. Any nodewhere the communication error occurred willreceive the SQL6048N message.


1. Correct the communication error on the node(or nodes) that received the SQL6048Nmessage.

2. Issue a DB2START command and ensure thatall nodes that received the SQL6048Nmessage started successfully.


3. Issue the DB2STOP FORCE command againfrom any node.

SQL6100 - SQL6199

SQL6100N The partitioning map in the datafile and the partitioning map forthe database are not the same.

Explanation: The data to be loaded has eithernot been partitioned, or was partitioned with apartitioning map other than the current one forthe nodegroup to which the table belongs. Thedata cannot be loaded.

User Response: If the data was not partitioned,use the db2split program to partition the data,then load the partitioned data.

If the data was partitioned, do one of thefollowing:

v Use the partitioning map from the header ofthe data file to redistribute the nodegroup towhich the table belongs. Then try the requestagain.

v Repartition the data with the currentpartitioning map for the nodegroup. Then trythe request again to load the newly partitioneddata.

SQL6101N This data file contains data fornode node-1 but the Load utility isconnected to node node-2.

Explanation: The data to be loaded is associatedwith a node number that differs from the nodenumber of the node to which the application isconnected. The data cannot be loaded.

User Response: Either find the data fileassociated with this node and try the requestagain with that data file, or connect to the nodeassociated with this data file and issue therequest at that node.

SQL6102W The parameter name is reservedfor future use. Its value should beset to default-value.

Explanation: A parameter reserved for futurecapabilities has been set to a value that is not its

default value. It should be set to the defaultvalue to ensure future compatibility.

User Response: Ensure that the parameter nameis set to the value, default-value, then try therequest again.

SQL6103C An unexpected utility erroroccurred. Reason code =reason-code.

Explanation: An unexpected utility erroroccurred.

User Response: Record the message number(SQLCODE) and reason code in the message.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. See the Administration Guide forinformation on how to use this facility. Thencontact your technical service representative withthe following information:




v Trace file if possible

SQL6104N The load utility does not supportthe creation of indexes.

Explanation: The load utility does not supportthe creation of indexes, but the table to be loadedhas at least one index defined on it. The indexmay have been explicitly created with theCREATE INDEX statement or implicitly createdwhen a primary key was defined for the table.

User Response: Drop all indexes defined on thetable with the DROP INDEX statement. Drop theprimary key with the ALTER TABLE statement.Resubmit the command.

Use CREATE INDEX and ALTER TABLE asrequired to recreate indexes and primary keyafter the load completes successfully.


SQL6105W The Load utility has completedprocessing. A Rollforward done toa point in time after the load willnot succeed. Take a databasebackup now if databaserecoverability is required.

Explanation: No logging is done by the Loadutility. If you try to roll forward with a backupmade before the load, the operation will failwhen it encounters references to the data thatwas loaded.

User Response: To ensure databaserecoverability after the load, do a backup beforethe data is modified.

SQL6106N The filetype modifier″NOHEADER″ was specified, butthe nodegroup on which the tableis defined is not a single-nodenodegroup.

Explanation: The data to be loaded wasspecified as having no header information.However the target table specified is not asingle-node table. The data cannot be loaded.

User Response: The data must be split usingdb2split, then loaded without the ″NOHEADER″option.

SQL6107N The partitioning key informationin the data file is not correct.

Explanation: Either the data was not split withdb2split or the db2split operation was notsuccessful.

User Response: Use the db2split program topartition the data and then try the request againwith the partitioned data. If the insert-columnoption is being used, ensure that all of thepartitioning columns are specified in the columnlist.

If the problem persists, contact your technicalservice representative with the followinginformation:





SQL6108N The number of partitioning keysdefined in the data file header(number-1) does not match thenumber of partitioning keysdefined for the table (number-2).

Explanation: The partitioning columns specifiedin the db2split configuration file were notcorrect. The data was not correctly split.


1. Ensure that the correct partitioning columnsare specified in the db2split configuration file.

2. Split the data.

3. Issue the Load operation with the newlypartitioned data.

SQL6109N Utility expected partitioningcolumn column-name-1, but foundpartitioning columncolumn-name-2.

Explanation: In the db2split configuration file:

v One of the partitioning columns defined forthe table was not specified.

v The order of the partitioning columns wasincorrect

v A column was specified that is not apartitioning column for the table.


1. Ensure that the db2split configuration file iscorrect.

2. Split the data.


SQL6110N Utility expected partitioningcolumn type column-type-1 forcolumn column-name-1, but thedata file lists it as typecolumn-type-2.

Explanation: The db2split configuration file isnot correct.



1. Ensure that the db2split configuration file iscorrect.

2. Split the data.


SQL6111N Cannot create a subdirectoryunder the path specified bynewlogpath.

Explanation: When the newlogpath parameteris updated, the system attempts to create asubdirectory under the specified path using thenode name as the name of the subdirectory. Oneof the following operating system errorsprevented the creation of the subdirectory:

v The file system or path does not have theappropriate permissions for file creation.

v The file system does not have enough diskspace.

v The file system does not have enough fileblocks or inodes.


User Response: Do one of the following, thentry the request again:

v Ensure that the specified path exists and thatthe filesystem and path have read/writepermissions.

v Specify a different newlogpath.

If the problem persists, see your systemadministrator.

SQL6112N The requested change cannot bedone. The resulting configurationparameter settings are not valid.Reason code reason-code.

Explanation: Three rules govern the settings ofsome configuration parameters. The rule thatwould be violated is indicated by the reason-code:

(1) max_coordagents + num_initagents <=maxagents

(2) num_initagents <= num_poolagents

(3) maxdari <= max_coordagents

User Response: Ensure that the values youspecify do not violate any of the above rules,then try the request again.

SQL6500 - SQL6599

SQL6500W RESTARTCOUNT in the loadcommand may cause someproblems.

Explanation: Since multiple loading processesfor the same table are completely independent, itis almost impossible to have an identicalrestartcount for those multiple loading processes.

User Response: Please make sure you have thecorrect load command.

SQL6501N Database name was not given inthe load command.

Explanation: Database name has to be specifiedin the load command.

User Response: Please specify the database

name and rerun the command.

SQL6502N The path name (parameter:data_path) for data file was notspecified.

Explanation: If the input data file is remote, thefile will be transferred locally. The path to the fileon the remote machine must be supplied.

User Response: Please specify the path name tothe remote data file and rerun the command.


SQL6504N There are errors in the outputnode list specification (parameter:outputnodes) in the configurationfile.

Explanation: The output node list specificationis not valid.

User Response: Check the sample configurationfile, correct your output node list specification,and rerun the command.

SQL6505N There are errors in thepartitioning database partition listspecification (parameter:PARTITIONING_DBPARTNUMS)in the load command.

Explanation: The partitioning database partitionlist specification is not valid.

User Response: Correct your partitioningdatabase partition list specification, and rerun thecommand.

SQL6506N The program failed to extractpartitioning key information fortable table-name from the systemcatalog table.

Explanation: Either the table is not defined, orit is not defined in an MPP environment.

User Response: Make sure you have the tableproperly defined.

SQL6507N Checking level (parameter:check_level) in the configurationfile is not valid.

Explanation: Checking level (parameter:check_level) can be either CHECK orNOCHECK. The default is CHECK.

User Response: Correct the parameter in theconfiguration file, and rerun the command.

SQL6508N The program failed to create theoutput pipe for the ftp process.

Explanation: If input data files are remote, theywill be transferred to a local pipe. If this local

pipe already exists, the process will fail.

User Response: Please ensure your workingspace is clean.

SQL6509N The program failed to create inputpipes for the partitioning agents.

Explanation: The program can not createtemporary input pipes for the splitter processes.


SQL6510N The program failed to create thetemporary directory at localnon-NFS space of partitionpartition-num.

Explanation: The program needs a temporaryworking directory at local non-NFS space of allpartitioning and loading partitions.


SQL6511N Load failed to create output forthe partitioning agent at partitionpartition-num.

Explanation: The program can not createtemporary output pipes for the partitioningagent at partition partition-num.


SQL6512N Load failed to create input pipesfor the merging agent at partitionpartition-num.

Explanation: The program can not createtemporary input pipes for the merging agent atpartition partition-num.



SQL6513N Load failed to create the inputpipe for the loading agent atpartition partition-num.

Explanation: The program can not createtemporary input pipe for the loading agent atpartition partition-num.


SQL6514N The program can not read thenode configuration file:node-cfg-file.

Explanation: Either the file does not exist, or itis not readable.

User Response: Please check the existence andpermissions of the node configuration file.

SQL6515N The program failed to find a loadcommand in the configurationfile.

Explanation: A CLP load command must besupplied in the configuration file.

User Response: Please specify a CLP loadcommand in the configuration file.

SQL6516N The program failed to connect todatabase db-name.

Explanation: Either the database manager hasnot been started yet, or it encountered problems.

User Response: Check your database managerstatus.

SQL6517N Load failed to extract the partitionlist, where the table tbl-name isdefined, from the system catalogtable.

Explanation: Either the table is not defined, orit is not defined in an MPP environment.

User Response: Check how the table wasdefined in the database.

SQL6518N The record length (reclen in theload command) is not valid.

Explanation: Valid record is between 1 to 32768.

User Response: Please correct the record length,and rerun the command.

SQL6519N The mode (parameter: mode) modein the configuration file is notvalid.

Explanation: The running mode of this programcan be: SPLIT_ONLY, LOAD_ONLY,SPLIT_AND_LOAD (default), or ANALYZE.

User Response: Please correct the mode in theconfiguration file.

SQL6520N The program failed to createoutput pipes for the process,which generates the headerinformation for split file.

Explanation: The program can not create outputpipes for the process, which generates the headerinformation for split file.


SQL6521N The configuration file cfg-file forthis program doesn’t exist.

Explanation: The program needs aconfiguration file.

User Response: Please create a configurationfile.

SQL6522N The program found a path namefor the input data files in the loadcommand.

Explanation: Path name for input data files inthe load command is not allowed. There is aseparate parameter (data_path) for this purpose.

User Response: Please correct the configurationfile.


SQL6523N The element partition-num in thepartitioning database partition list(parameter:PARTITIONING_DBPARTNUMS)is not defined in the nodeconfiguration (db2nodes.cfg) file.

Explanation: All partitions in the partitioningdatabase partition list must have an entry in thenode configuration file.

User Response: Please correct your partitioningdatabase partition list.

SQL6524N The element partition-num in theoutput partition list (parameter:OUTPUT_DBPARTNUMS) is nota member of the partition listwhere the table is defined.

Explanation: All partition in the outputpartition list must be members of the partitionlist where the table is defined.

User Response: Please correct your outputpartition list.

SQL6525N The program can not read theinput data file file-name.

Explanation: Either the input data file was notfound, or it is not readable.

User Response: Please check the existence andpermissions of the input data file.

SQL6526N The program can not write incurrent working directory cwd.

Explanation: The current working directory isnot writable.

User Response: Please check the permission ofcurrent working directory.

SQL6527N The partition where statistic datawill be collected, (parameter:RUN_STAT_DBPARTNUM), isnot a member of the outputpartition list.

Explanation: The partition where statistic datawill be collected must be a member of the outputpartition list.

User Response: Please correct theRUN_STAT_DBPARTNUM parameter.

SQL6528N Record length was not specifiedin the load command.

Explanation: If the BINARYNUMERICS orPACKEDDECIMAL modifier is specified in theload command, record length (reclen) must bespecified in the load command as well.

User Response: Please correct the loadcommand.

SQL6529N The No Header option(NOHEADER) was not specifiedin the load command.

Explanation: If a table is defined in a singlenode nodegroup, the NOHEADER modifier mustbe specified in the load command.


SQL6530N The data type of one partitioningkey is float or double.

Explanation: If the input file is a non-binarydata file, float or double columns can not bedefined as partitioning key.

User Response: Supply a binary data file, orchange the definition of your table.

SQL6531N The program failed to resettablespace quiesce.

Explanation: There are probably on-goingloading processes. Make sure all previousloading processes are completed before anotherAutoLoader session can be started.


User Response: Check the processes status onyour machine.

SQL6532N A savecount in the load commandcan not be set to non-zero.

Explanation: The savecount in the loadcommand can not be set to non-zero if there aremultiple partitioning nodes, the mode isPARTITION_AND_LOAD, and the command iseither a REPLACE INTO or INSERT INTO loadcommand.


SQL6533N A restartcount in the loadcommand can not be set tonon-zero.

Explanation: Because multiple partitioningnodes produce random order of records forloading process(es), using RESTART INTO with arestartcount can not guarantee a successfulrecovery.


SQL6534N There is an error in the .netrc filenetrc-file.

Explanation: Either the .netrc file could not befound, or there is no entry for remote hostmachine, or the permissions of the file are notcorrect.

User Response: Please check the existence andpermission of the .netrc file.

SQL6535N The mode PARTITION_ONLY orANALYZE is not valid.

Explanation: If a table is defined in a singlenode nodegroup, either partitioning or analyzingis not necessary.

User Response: Please change the mode toLOAD_ONLY or PARTITION_AND_LOAD.

SQL6536N The program progname failed toopen file filename for reading.

Explanation: An AutoLoader process can notsuccessfully open a file or pipe for reading.

User Response: Please ensure everything iscorrect in the configuration file.

SQL6537N The program progname failed toopen file filename for writing.

Explanation: An AutoLoader process can notsuccessfully open a file or pipe for writing.

User Response: Please ensure everything iscorrect in the configuration file.

SQL6538N Load failed to read the partitionedfile partitioned-file.

Explanation: When Load is invoked inLOAD_ONLY mode, the input data file musthave already been partitioned, and all partitionedfiles must be readable by the Load.

User Response: Check whether or not the inputdata file has been partitioned, and the accesspermissions of the resulting partitioned files.

SQL6539N There is at least one command incmd-list not found in the workingenvironment.

Explanation: The execution of this programdepends on a number of common Unixcommands. The process fails if any one of themis not available in the working environment.

User Response: Make sure you have allnecessary commands properly installed on yoursystem.

SQL6540N File type file-type specified in theload command is not valid.

Explanation: Valid file types are ASC (positionalASCII) or DEL (delimited ASCII).

User Response: Correct the load command inthe configuration file.


SQL6550N The partitioning map filemap-file-name could not be openedfor writing.

Explanation: The file name and path for thepartitioning map could not be opened. An erroroccurred.

User Response: Confirm that the partitioningmap file name and file path were specifiedcorrectly and that the file can be opened forwriting.

SQL6551N An error occurred whileattempting to write to thepartition map file.

Explanation: A filesystem error occurred whenwriting to the partitioning map file.

User Response: Check that the file path iscorrect, and that the target device has sufficientspace to hold the partitioning map output.

SQL6552N An error occurred whileattempting to open a temporaryconfiguration file filename forwriting.

Explanation: The file name and path for atemporary file could not be opened. An erroroccurred.

User Response: Confirm that the utilitytemporary file storage path was specifiedcorrectly and that the path allows for files to beopened for writing.

SQL6553N An error occurred whileattempting to write to a temporaryconfiguration file filename.

Explanation: A filesystem error occurred whenwriting to a temporary file.

User Response: Check that the file path iscorrect, and that the target device has sufficientspace for the file data.

SQL6554N An error occurred whenattempting to remotely execute aprocess.

Explanation: The utility attempted to start achild process on a different database partition,but an error occurred.

User Response:

v If no user ID or password was provided to theutility for remote access, ensure that the userID invoking the utility is authorized to executeprograms on the target node(s).

v If a user ID and password were supplied tothe utility confirm that they were suppliedcorrectly.

v If running on NT make sure the DB2installation has correctly defined an NTService for the splitter operation on all nodes.

v If you are unable to resolve this problem,please contact DB2 service.

SQL6555N The load utility encountered anunexpected communications error.

Explanation: The utility encountered an errorattempting one of the following operations:

v Attempting to connect to a TCP/IP socket.

v Attempting to read or write a TCP/IP msg.

v Attempting to initialize TCP/IPcommunications

v Attempting to retrieve a complete host name.

v Attempting to select an active TCP/IP socket.

v Attempting to close an active socket.

v Attempting to retrieve a port number.

User Response:

v If service name setup was required for theversion of the load utility you are using,ensure that the service names have beendefined correctly.

v If you are running concurrent load utility jobs,ensure that you have followed thedocumented setup requirements to avoidservice name conflicts between the concurrentutility jobs.


v If the problem persists, contact your DB2Service representative.

SQL6556W An incomplete record wasdetected at the end of file filename.

Explanation: An incomplete data record wasfound at the end of a data file provided to theutility by the user.

User Response: Examine the source data forsyntactical correctness.

SQL6557N Failed to retrieve the default nodenumber.

Explanation: The utility attempted to determinea default node number, but was unable to.

User Response: State source and target nodenumbers explicitly in the utility configurationfile, or contact DB2 Service for assistance.

SQL6558N The utility failed to determine thecurrent working directory and/ordrive.

Explanation: The utility attempted to determinethe current working directory and/or drive butencountered an error.

User Response: Contact DB2 Service forassistance.

SQL6559N An invalid command line optionwas provided to the AutoLoaderutility.

Explanation: The user specified a command lineoption for the AutoLoader utility which is eithernot supported, or obsolete.

User Response: Refer to the AutoLoaderdocumentation, or online help, for the supportedoptions and features.

SQL6560N Node node-number which is anexecution node for partitioningdoes not appear in thedb2nodes.cfg file.

Explanation: A node specified as an executionnode for partitioning does not appear to be amember in the db2nodes.cfg file. The workintended to complete on this node can not bestarted.

User Response: Add the node to the node listdefinition in the db2nodes.cfg file, or specify analternate node for the partition operation whichis a member of the node configuration.

SQL6561N Target node node-number for loaddoes not appear in the nodegroup.

Explanation: A node was specified as a targetnode for loading, but this node is apparently nota member of the node group being loaded.

User Response: Check the nodegroup definitionand confirm that the target node specified forloading is part of this nodegroup. If the node isnot part of the nodegroup correct the utilitytarget node specification to include the correctlist of nodes. If the node is part of thenodegroup, please contact DB2 Service forassistance.

SQL6562N The utility is unable to retrievethe instance name.

Explanation: The utility attempted to retrievethe instance name but encountered an error.

User Response: Confirm that the utility isrunning on a node with DB2 installed, and avalid instance is running. For additional help,please contact DB2 Service.

SQL6563N Failed to retrieve the current userID.

Explanation: The utility attempted to retrievethe current user ID for the ID, but an error wasencountered.

User Response: Contact DB2 Service.


SQL6564N The password supplied is notvalid.

Explanation: The user supplied an explicitpassword to the utility, but the password is notvalid.

User Response: Supply a valid password.

SQL6565I Usage: db2atld [-configconfig-file] [-restart] [-terminate][-help]

Explanation:

v The ’-config’ option will run this programusing a user specified configuration file; thedefault is autoload.cfg.

v The ’-restart’ option will run this program inrestart mode; the configuration file should notbe modified since the last incompleteAutoLoader job.

v The ’-terminate’ option will run this programin terminate mode; the configuration fileshould not be modified since the lastincomplete AutoLoader job.

v The ’-help’ option will generate this helpmessage.

The AutoLoader configuration file is a usersupplied file which contains the LOADcommand to be executed, the target database,and several optional parameters that the usermay specify. The sample configuration file,’AutoLoader.cfg’, supplied in the samplesdirectory contains inline comments whichdescribe the available options and their defaults.When running this program with ’-restart’ and’-terminate’ option, user should not modify theconfiguration file from their last incomplete job.

User Response: Refer to the DB2documentation for further details about theAutoLoader utility.

SQL6566N The LOAD command is missingfrom the AutoLoaderconfiguration file.

Explanation: The LOAD command is missingfrom the AutoLoader configuration file. The

parameter must be specified.

User Response: Ensure that you have specifiedthe correct configuration file for the AutoLoader,and that the LOAD command is specified inside.

SQL6567N The option-name option appearsmultiple times in the AutoLoaderconfiguration file.

Explanation: An option parameter was specifiedmultiple times inside the AutoLoaderconfiguration file.

User Response: Correct the configuration file sothat each option appears at most only once.

SQL6568I The Load utility is now issuingall request-type requests.

Explanation: The Load utility is nowdispatching the request-type operation on each ofthe partitions.

User Response: This is an informationalmessage.

SQL6569I The AutoLoader is now issuingall split requests.

Explanation: The AutoLoader is now issuingthe split operation on each of the target splitpartitions.


SQL6570I The AutoLoader is waiting for allsplitters to complete.

Explanation: The AutoLoader is waiting for allsplitters to complete.


SQL6571I The Load utility is waiting for alloperations to complete.

Explanation: The Load utility is waiting foroperations to complete.



SQL6572I The LOAD operation has begunon partition node-number.

Explanation: The LOAD operation has begunon the specified partition.


SQL6573I The remote execution of thesplitter utility on partitionnode-number finished with remoteexecution code code.

Explanation: The remote execution of thesplitter utility on the specified partition hascompleted.


SQL6574I The utility has read MB-countmegabytes from the source data.

Explanation: This information is generatedperiodically to provide status to the user on theprogress of large Load jobs.


SQL6575I The utility has completed readingMB-count megabytes from the userdata.

Explanation: This message is written at thecompletion of the Load to indicate the totalvolume of user data that has been processed.


SQL6576N The AutoLoader utilityencountered a threading error.Reason code reason-code, returncode ret-code.

Explanation: The following is an explanation ofthe reason code reason-code:

v 1 - The AutoLoader utility tried to create athread but failed with return code ret-code.

v 2 - The AutoLoader utility tried to wait for athread to finish, but failed with return coderet-code.

User Response: Ensure that you are running onan operating system which supports threadedapplications, and that your thread limit perprocess is sufficient. The thread requirements areas follows:

v One thread for every load process which mustbe started,

v One thread for every splitter process,

v One thread for data feeding to the splitterprocesses.

SQL6577N The AutoLoader utility does notsupport the ROWCOUNT optionin the load command.

Explanation: The ROWCOUNT option in theload command is not supported in theAutoLoader utility.

User Response: Correct your load command inthe AutoLoader configuration file, and resubmityour command.

SQL6578N Invalid AutoLoader option.RESTART/TERMINATE optioncan only be specified withSPLIT_AND_LOAD orLOAD_ONLY mode.

Explanation: RESTART/TERMINATE option inAutoLoader can only work withSPLIT_AND_LOAD or LOAD_ONLY mode.

User Response: Please check the AutoLoaderconfiguration file or the autloader option flags.


SQL6579N Invalid LOAD command in theAutoLoader configuration file.RESTART and TERMINATEoptions of the AutoLoader areused to perform LOAD RESTARTand LOAD TERMINATEoperation respectively.

Explanation: Users should not specify RESTARTnor TERMINATE in the LOAD command.Instead, the RESTART and TERMINATE optionsof the AutoLoader should be used.

User Response: Without modifying theAutoLoader configuration file, users shouldlaunch db2atld with option RESTART orTERMINATE.

SQL6580I LOAD is restarting on nodenode-num in phase restarting-phase.

Explanation: AutoLoader has acknowledgedthat LOAD is restarting in eitherLOAD/BUILD/DELETE phase.


SQL6581I Load cannot restart on nodenode-num.

Explanation: AutoLoader has acknowledgedthat LOAD cannot be restarted on a given node.


SQL6582I Restarting LOAD on nodenode-num is not required.

Explanation: AutoLoader has acknowledgedthat LOAD does not need to be restarted on agiven node.


SQL6583N The partitioning key definition isincompatible with partitioneddatabase load mode load-mode.

Explanation: An identity column was specifiedas part of the partitioning key definition, but theload mode specified was notPARTITION_AND_LOAD and theidentityoverride modifier was not specified.

User Response: Either change the load mode toPARTITION_AND_LOAD, specify theidentityoverride modifier, or remove the identitycolumn from the partitioning key definition.

SQL7000 - SQL7099

SQL7001N Unknown command command wasrequested.

Explanation: The command submitted to REXXcould not be recognized.


User Response: Verify that the command is avalid SQL statement and rerun the procedure.Note that all commands must be in uppercase.

SQL7002N The cursor name is invalid.

Explanation: The user specified an incorrectcursor name.


User Response: Verify that the cursor name isone of the form “c1” through “c100”.

SQL7003N The statement name is invalid.

Explanation: The user has specified an incorrectstatement name.


User Response: Verify that the statement nameis of the form “s1” through “s100”.


SQL7004N The syntax of the request isinvalid.

Explanation: REXX was unable to parse thecommand string submitted.


User Response: Use proper command syntax.

SQL7005W The cursor used by this OPENstatement has not been declared.

Explanation: An OPEN statement wasattempted without a declaring a cursor.


User Response: Insert a DECLARE statementbefore the OPEN statement and rerun theprocedure.

SQL7006N Invalid keyword keyword given onrequest.

Explanation: The statement contains a not validkeyword keyword.


User Response: Specify the correct keywordformat.

SQL7007N REXX variable variable does notexist.

Explanation: A REXX variable that did not existin the REXX variable pool was passed.


User Response: Verify that all variable names inthe host-variable list are assigned before thecommand that failed. Then run the procedureagain.

SQL7008N REXX variable variable containsinconsistent data.

Explanation: A variable that containedinconsistent data was passed to REXX.


User Response: If the variable is an SQLDA,verify that the data and length fields have beenassigned correctly. If it is a REXX variable, verifythat the type of data is appropriate to thecommand where it is being used.

SQL7009N Truncated REXX variable variable.

Explanation: The variable variable passed toREXX contained inconsistent data. The datastring from variable was truncated.


User Response: Verify that the data length isconsistent with the length given in the inputSQLDA, and run the procedure again.

SQL7010N Invalid scan ID ID.

Explanation: The scan ID variable passed toREXX did not exist or contained inconsistent ormissing data.


User Response: Verify that the data containedin the scan ID has been assigned correctly, andrun the procedure again.

SQL7011N Required parameter parameter notgiven.

Explanation: The parameter parameter isrequired by REXX command syntax but was notspecified.


User Response: Specify the required parametervalue, and run the procedure again.

SQL7012N Attempted ISL change whileconnected to a database.

Explanation: Isolation level (ISL) may not bechanged while connected to a database.

The command is ignored.

User Response: If a change in isolation level isnecessary, disconnect from the current database,


then set the isolation level and connect to thedatabase.

SQL7013N Mismatched cursor and statementname or hold attribute.

Explanation: In REXX, the cursor and statementname form must be ’cnn’ and ’snn,’ where ’nn’ isa number from 1 to 100. The numbers must bethe same for a cursor and statement pair. Also, c1through c50 are declared without hold and c51through c100 with hold.


User Response: Verify that the cursor andstatement numbers match and rerun theprocedure.

SQL7014N Incorrect number of host variablecomponents.

Explanation: In REXX, the first component of acompound host variable lists a number which isnot equal to the actual number of componentsdefined.


User Response: Verify that the number in thefirst component matches the number ofcomponents actually defined and rerun theprocedure.

SQL7015N The variable name variable is notvalid in REXX.

Explanation: The variable name specified is notvalid in REXX. The name must conform to thelanguage requirements.


User Response: Change the name to one thatconforms to the REXX requirements andresubmit the command.

SQL7016N Invalid syntax provided to theSQLDB2 interface. Related Error:db2-error. The command cannot beprocessed.

Explanation: Invalid syntax was provided to theSQLDB2 interface, e.g. both an input file and acommand were specified.

User Response: Look up the related error codefor more information.

SQL7032N SQL procedure procedure-name notcreated. Diagnostic file is file-name.

Explanation: SQL Procedure procedure-name wasnot created. One of the following has occurred:

v Support for SQL stored procedures is notinstalled and configured on this server. Youneed to have the DB2 ApplicationDevelopment Client and a C compiler installedon the server to create SQL procedures. Youmay need to set the DB2 registry variableDB2_SQLROUTINE_COMPILER_PATH topoint to a script or batch file that containsenvironment settings for the C compiler onyour platform.

v DB2 failed to precompile or compile the SQLstored procedure. DB2 creates an SQLprocedure as a C program that containsembedded SQL. Errors not found during theinitial parsing of the CREATE PROCEDUREstatement can be found during the precompileor compile stage.

For UNIX platforms, the full path of the file thatcontains diagnostic information is:

$DB2PATH/function/routine/sqlproc/ \$DATABASE/$SCHEMA/tmp/file-name

where $DATABASE represents the name of thedatabase, and $SCHEMA represents the schemaname of the SQL procedure.

For OS/2 and Windows operating systems, thefull path of the file that contains diagnosticinformation is:


%DB2PATH%\function\routine\sqlproc\ \%DATABASE%\%SCHEMA%\tmp\file-name

where %DATABASE% represents the name of thedatabase, and %SCHEMA% represents theschema name of the SQL procedure.

User Response: Ensure that both a compatibleC compiler and a DB2 Application DevelopmentClient are installed on the server. If a precompileor compile error occurred, refer to the messagesfrom the precompiler or compiler in thediagnostic file file-name.

Ensure that the DB2 registry variableDB2_SQLROUTINE_COMPILER_PATH is set topoint to a script or batch file that sets up the Ccompiler environment. On a UNIX operatingsystem, for example, you may create a scriptcalled “sr_cpath” in the/home/DB2INSTANCE/sqllib/function/routinedirectory. To set the DB2 registry variableDB2_SQL_ROUTINE_COMPILER_PATHaccordingly, issue the following command:

db2set DB2_SQLROUTINE_COMPILER_PATH = \“ \/home/DB2INSTANCE/sqllib/function/ \routine/sr_cpath”

sqlcode: -7032

sqlstate: 42904

SQL7035W The executable of the SQLprocedure procedure-name is notsaved in the database catalog.

Explanation: The executable of the SQLprocedure exceeds the limit of 2 megabytes and

therefore cannot be stored in the databasecatalog. It will not be recovered automatically atdatabase restore time or on ROLLBACK of aDROP PROCEDURE statement.

User Response: If the warning resulted from aCREATE PROCEDURE statement, ensure thatyou keep a backup of the executable associatedwith SQL procedure procedure-name. If thewarning was issued during a restore operation ora ROLLBACK of a DROP PROCEDUREstatement, then the executable associated withprocedure-name must be manually synchronizedwith the SQL procedure that is defined in thecatalog.

sqlcode: +7035

sqlstate: 01645

SQL7099N Invalid error error has occurred.

Explanation: A REXX internal error hasoccurred.


User Response: Verify that REXX is installedproperly and rerun the procedure. If the errorcontinues, note the error number and call thedealer.

SQL8000 - SQL8099

SQL8000N DB2START processing failed; avalid product license was notfound.

Explanation: A valid license key could not befound and the evaluation period has expired.

User Response: Install a license key for thefully entitled version of the product. You can

obtain a license key for the product by contactingyour IBM representative or authorized dealer.

SQL8001N DB2 connect processing failed; avalid product license was notfound.



User Response: Install a license key for thefully entitled version of the product. You canobtain a license key for the product by contactingyour IBM representative or authorized dealer.

sqlcode: -8001

sqlstate: 42968

SQL8002N DRDA connect processing failed;a valid product license was notfound.


User Response: Install a license key for thefully entitled version of the product. You canobtain a license key for the product by contactingyour IBM representative or authorized dealer.

sqlcode: -8002

sqlstate: 42968

SQL8006W The product product-name does nothave a valid license key installed.If you have licensed this product,please ensure the license key isproperly installed. If a license keyis not installed, this product willbe enabled for a number dayevaluation period. USE OF THEPRODUCT FOR THEEVALUATION PERIODCONSTITUTES ACCEPTANCEOF THE TERMS OF THE IBMEVALUATION AGREEMENT INTHE EVALUATE.AGR FILE,LOCATED IN THE FOLLOWINGDIRECTORY: directory-name.

Explanation: A valid license key has not beeninstalled for this product. The product will beenabled to operate for a limited period of timefor evaluation purposes. THE EVALUATIONPERIOD IS CONTROLLED BY A TIMEDISABLING DEVICE.

User Response: If you have purchased a fullyentitled version of this product, please installyour license key as described in the productinstallation documentation. If you have already

installed the license key, please verify yourlicense file for accuracy.

USE OF THE PRODUCT FOR THEEVALUATION PERIOD IS SUBJECT TO THETERMS OF THE IBM EVALUATIONAGREEMENT IN THE EVALUATE.AGR FILE.YOUR USE OF THE PRODUCT DURING THEEVALUATION PERIOD CONSTITUTES YOURACCEPTANCE OF THESE TERMS.

If you do not accept the terms, you are notauthorized to use the product and you mustde-install it. You can obtain a license key for thefully authorized program with the product bycontacting your IBM representative or authorizeddealer.

SQL8007W There are number day(s) left in theevaluation period for the producttext. For evaluation license termsand conditions, refer to the IBMEvaluation Agreement in theEVALUATE.AGR file, located inthe following directory: text.

Explanation: A valid license key has not beeninstalled for this product. The evaluation periodwill expire after the specified number of days.

User Response: The product is operating inevaluation mode, and is enabled for a limitedperiod of time. When the evaluation period hasexpired it will not execute until a license key forthe fully entitled version of the product isinstalled.

You can obtain a license key for the product bycontacting your IBM representative or authorizeddealer.

SQL8008N The product text does not have avalid license key installed and theevaluation period has expired.Functions specific to this productare not enabled.


User Response: Install a license key for thefully entitled version of the product. You can


obtain a license key for the product by contactingyour IBM representative or authorized dealer.

SQL8009W The number of concurrent usersof the DB2 Workgroup producthas exceeded the definedentitlement of number. Concurrentuser count is number.

Explanation: The number of concurrent usershas exceeded the number of defined DB2concurrent user entitlements.

User Response: Contact your IBMrepresentative or authorized dealer to obtainadditional DB2 user entitlements and update theDB2 license information in the License Center.

sqlcode: +8009

sqlstate: 01632

SQL8010W The number of concurrent usersof the DB2 Connect product hasexceeded the defined entitlementof number. Concurrent user countis number.



sqlcode: +8010

sqlstate: 01632

SQL8011W One or more database partitionsdoes not have a valid DB2 licensekey installed for the product-nameproduct.

Explanation: A valid license key has not beeninstalled for this product on all databasepartitions. The product will be enabled tooperate for a limited period of time forevaluation purposes. THE EVALUATIONPERIOD IS CONTROLLED BY A TIMEDISABLING DEVICE.

User Response: If you have purchased a fullyentitled version of this product, please installyour license key as described in the productinstallation documentation. If you have alreadyinstalled the license key, please verify yourlicense file for accuracy.

USE OF THE PRODUCT FOR THEEVALUATION PERIOD IS SUBJECT TO THETERMS OF THE IBM EVALUATIONAGREEMENT IN THE EVALUATE.ARG FILE.YOUR USE OF THE PRODUCT DURING THEEVALUATION PERIOD CONSTITUTES YOURACCEPTANCE OF THESE TERMS.

If you do not accept the terms, you are notauthorized to use the product and you mustde-install it. You can obtain a license key for thefully authorized program with the product bycontacting your IBM representative or authorizeddealer.

SQL8012W The number of concurrent usersof the DB2 Enterprise product hasexceeded the defined entitlementof number. Concurrent user countis number.



sqlcode: +8012

sqlstate: 01632

SQL8013W The number of concurrentdatabase connections to the DB2Connect product has exceeded thedefined entitlement of number.Database connection count isnumber.

Explanation: The license for the DB2 Connectproduct you are using supports a limited numberof concurrent database connections. You have


requested a number of connections that exceedsthis limit.

User Response: Upgrade to a version of theDB2 Connect product with a higher limit ofconcurrent database connections.

DB2 Connect Enterprise Edition users: obtainlicenses for additional users by purchasingAdditional User Packs.

sqlcode: +8013

sqlstate: 01632

SQL8014N The version of the DB2 Connectproduct you are using is notlicensed for use with TCP/IPprotocol. Upgrade to a fullfunction DB2 Connect product touse TCP/IP.

Explanation: This version of DB2 Connect islimited to SNA connectivity. TCP/IP connectionsare not supported.

User Response: Upgrade to a full function DB2Connect product such as DB2 Connect PersonalEdition or DB2 Connect Enterprise Edition to useTCP/IP.

sqlcode: -8014

sqlstate: 42968

SQL8015N The version of the DB2 Connectproduct you are using is notlicensed for updating multipledatabases in the same transaction.

Explanation: This version of DB2 Connect islimited to working with a single database in atransaction. It does not support 2-phase commitprotocol.

User Response: Upgrade to a full function DB2Connect product such as DB2 Connect PersonalEdition or DB2 Connect Enterprise Edition to beable to update multiple databases in a singletransaction.

sqlcode: -8015

sqlstate: 42968

SQL8016N The user user-name is not definedas a registered user for theproduct product-name.

Explanation: The user has not been registeredto use this product.

User Response: Contact your IBMrepresentative or authorized dealer to obtainadditional DB2 registered user entitlements andupdate the registered user list for this product inthe License Center.

SQL8017W The number of processors on thismachine exceeds the definedentitlement of licensed-quantity forthe product product-name. Thenumber of processors on thismachine is processor-quantity. Youshould purchase additionalprocessor based entitlements fromyour IBM representative orauthorized dealer and update yourlicense using the License Centeror the db2licm command lineutility. For more information onupdating processor based licenses,refer to the Quick Beginningsmanual. For more information onthe db2licm utility, refer to theCommand Reference.

User Response: sqlcode: +8017

SQL8018W The number of concurrent usersof this product has exceeded thedefined entitlement of number.Concurrent user count is number.

Explanation: The number of concurrent usershas exceeded the number of defined concurrentuser entitlements.

User Response: Contact your IBMrepresentative or authorized dealer to obtainadditional user entitlements and update the DB2license information in the License Center.

sqlcode: +8018

sqlstate: 01632


SQL8019N There was an error updating thelicense for the OLAP Starter Kit.RC = reason-code.

Explanation: The license utility could notupdate the OLAP Starter Kit license because ofan unknown error.

User Response: Try the command again. If theproblem persists, please contact an IBM servicerepresentative.

sqlcode: -8019

SQL8020W The number of concurrentnon-DB2 data sources for oneserver has exceeded the definedentitlement of number-sources.Current number of non-DB2 datasources is number-entitled.

Explanation: The number of concurrentnon-DB2 data sources has exceeded the numberof defined entitlements.

User Response: Contact your IBMrepresentative or authorized dealer to obtainadditional entitlements and then update the DB2license information in the License Center.

sqlcode: +8020

SQL8021W The data source source-name is notdefined as a registered data sourcefor product-name.

Explanation: The data source has not beenconfigured as a registered data source. You mustpurchase entitlements for all non-DB2 datasources.

User Response: Contact your IBMrepresentative or authorized dealer to obtainadditional data source entitlements and updatethe registered data source list for this product inthe License Center.

sqlcode: +8021

SQL8100 - SQL8199

SQL8100N The table is full.

Explanation: When creating a database thefollowing parameters may be specified:

v maximum number of pages per segment perfile

v number of segments

Each table part may now have multiple fileswithin the database segments. The file can growuntil it reaches its maximum size in a segment(maximum number of pages per segment) andthen it moves to the next segment to add moredata. This occurs until it has used the maximumnumber of pages per segment in all configuredsegments, and the table becomes full.

Therefore, the total amount of space per databasepart is the product of the maximum number ofpages and the number of segments. The tablewill be full if any of the table parts use all oftheir configured space.


User Response:

v Delete rows from the table

v Reorganize the table to make more space

v Create a new database with larger values formaximum pages per segment and number ofsegments, back up the original database andrestore to the new database.

Federated system users: isolate the problem tothe data source failing the request (refer to theTroubleshooting Guide to determine which datasource is failing to process the SQL statement)and:

v Take the necessary steps to increase the spacein the table at the data source.

v If the table is on the federated server, create anew database with larger values for maximumpages per segment and number of segments.Back up the original database and restore tothe new database.


SQL8101N A database segment may beincorrect.

Explanation: This error could occur in twoways:

1. Every database segment has an identifier file.The file may be missing or the contents of thefile may be incorrect.

2. One, or more, previously allocated databasesegments are missing.

User Response:

v Check to ensure that the file systems aremounted correctly

v Restore the database from a backup

v Call your IBM service representative

SQL9300 - SQL9399

SQL9301N An invalid option is specified oran option parameter is missing.

Explanation: Either the option specified isinvalid or an option parameter is not specified.


User Response: Correct the option and resubmitthe command.

SQL9302N Invalid option parameter:option-parameter.

Explanation: The option parameter specified isinvalid.


User Response: Correct the option parameterand resubmit the command.

SQL9303N No option is specified.

Explanation: The required option option is notspecified.


User Response: Resubmit the command withthe required option.

SQL9304N Unable to open file filename forwriting.

Explanation: The command cannot beprocessed.

User Response: Ensure that the system canaccess the file.

SQL9305N The name is too long. Themaximum length is max-length.

Explanation: The <name> is longer than themaximum length of <max-length>.


User Response: Ensure that the <name> doesnot exceed the maximum length.

SQL9306N One or more of the field namesare too long. The maximumlength is max-length.

Explanation: The total length of a field nameincludes the specified prefix and/or a columnsuffix, which can either be its name or itsnumber. This total length must not exceed themaximum length.


User Response: Ensure that all the field namesdo not exceed the maximum length.

SQL9307N Remarks cannot be retrieved fromthe database. Error code = sqlcode.

Explanation: An error has occurred whenattempting to retrieve the remarks of a columnfrom the database.


User Response: Check the error code for moreinformation.


SQL9308W SQL data type sqltype of thecolumn colname is not supported.

Explanation: The SQL data type sqltype is notsupported in the specified host language.

No declaration is generated for this column.

User Response: Ensure that this is the desiredtable.

SQL9320I Connecting to the databasedatabase...

Explanation: The utility is attempting toconnect to the database database.

User Response: See the error message fordetails if it fails.

SQL9321I Binding the utility automatically...

Explanation: The utility is attempting to binditself to the database.


SQL9322I Retrieving column informationfrom the table table...

Explanation: The utility is attempting to retrievecolumn information from the table table.


SQL9323I Generating declarations to the filefilename...

Explanation: The utility is attempting togenerate declarations to the file filename.


SQL9324I Disconnecting from the databasedatabase...

Explanation: The utility is attempting todisconnect from the database database.


SQL10000 - SQL10099

SQL10002N The password supplied is toolong.

Explanation: The length of the password isexpected to be 18 characters or less. However, ifthe password is to be verified for an APPCconversation, it must be 8 characters or less.

User Response: Ensure that the password is notlonger than the limit allowed.

sqlcode: -10002

sqlstate: 28000

SQL10003C There are not enough systemresources to process the request.The request cannot be processed.

Explanation: The database manager could notprocess the request due to insufficient systemresources. The resources that can cause this errorinclude:

v The amount of memory in the system

v The number of message queue identifiersavailable in the system.



v Terminate other applications using the aboveresources.

v If you are using Remote Data Services,increase the Remote Data Services heap size(rsheapsz) in the server and clientconfiguration because at least one block isused per application.

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

v Decrease the values of the configurationparameters that define allocation of memory,including udf_mem_sz if UDFs are involved inthe failing statement.


sqlcode: -10003

sqlstate: 57011

SQL10004C An I/O error occurred whileaccessing the database directory.

Explanation: Either the system databasedirectory or the local database directory cannotbe accessed. This error may occur not only whenthe system is cataloging or uncataloging adatabase but also when the system is accessing adatabase that is cataloged in the directory.

This error is returned if a connection isattempted between 32-bit and 64-bit platforms.Connections between 32-bit and 64-bit platformsare not supported.



v If the local database directory is damaged,restore the databases that were cataloged therefrom backup versions and catalog them.


sqlcode: -10004

sqlstate: 58031

SQL10005N The mode parameter parameter inthe CONNECT TO statement isnot valid. It must be SHARE forshared access, EXCLUSIVE forexclusive use or EXCLUSIVEMODE ON SINGLE NODE forexclusive use on single node. ForDB2 Connect connections, onlySHARE mode is supported.EXCLUSIVE MODE ON SINGLENODE is only supported in MPPconfiguration.

Explanation: The mode parameter of theCONNECT TO statement must be SHARE forshared, EXCLUSIVE for exclusive use orEXCLUSIVE MODE ON SINGLE NODE forexclusive use on single node. If connecting to a

database using DB2 Connect, only shared accessis allowed. EXCLUSIVE MODE ON SINGLENODE is only supported in MPP configuration.


User Response: Resubmit the command with avalid mode parameter.

SQL10007N Message msgno could not beretrieved. Reason code: code.

Explanation: The requested message <msgno>could not be retrieved from the message file.Reason code <code> is one of the following:

1. The environment variable “DB2INSTANCE”is either not set, or is set to an invalidinstance. Correct it and try again.

2. The message file was found, but the filecould not be opened because of permissions.Check the file permissions of the files underthe message directory.

3. The message file could not be found. Eitherthe file does not exist, or the directory themessage file should be in does not exist.Check that a either a ’prime’ directory (thedefault) or a directory with the same name asthe ’LANG’ environment variable existsunder the message directory.

4. The requested message does not exist in themessage file. Either the message file isoutdated, or it is the wrong one.

5. Either DB2CODEPAGE is set to a code pagewhich the database does not support, or theclient’s locale is not supported by thedatabase.

6. An unexpected system error occurred. Tryexecution again. If problem persists, contactyour IBM representative.

7. Not enough memory. An attempt to getprivate memory failed. Try again.

User Response: Reissue the command afterverifying the following:

v ensure that the DB2INSTANCE environmentvariable is set to the correct literal string forthe username attempting this command


v ensure that correct home directory is specifiedfor the username attempting this command(i.e. in the /etc/passwd file)

v ensure that the LANG environment variable isset to the correct value for the installedlanguage, or is set to ’C’ (defaults to whateveris in the ’prime’ directory), on the usernameattempting this command

If all of the above are correct and the error stilloccurs, reinstall DB2.

SQL10009N The codeset codeset and/or territoryterritory that has been specified isnot valid.

Explanation: This version of the databasemanager does not support the active codeset orterritory or both, as specified by the CreateDatabase command.


User Response: Refer to the Create Databasecommand in the Administration Guide for detailsof valid codeset and territory pairs supported bythe database manager.

SQL10010N The specified library, name, wasloaded, but the function functioncould not be executed.

Explanation: The function routine within thelibrary cannot be found.


User Response:

1. If it is a DARI library, ensure the DARIlibrary is built correctly. Make sure that thefunction routine is exported through the’export file’.

2. For other libraries, user may have to reinstallthe database manager instance or thedatabase manager product.

sqlcode: -10010

sqlstate: 42724

SQL10011N An interrupt was received whileloading the specified DARIlibrary name.

Explanation: When loading the DARI library,the command was interrupted, perhaps by theinterrupt key (usually Ctrl+Break or Ctrl+C).



sqlcode: -10011

sqlstate: 42724

SQL10012N An unexpected operating systemerror was received while loadingthe specified library name.

Explanation: An unexpected error occurredwhen trying to load the library module specifiedin the program name field.

User Response: Resubmit the current command.If the error continues, stop the database managerand start it again. If the error continues, reinstallthe database manager.

If reinstallation does not correct the error, recordthe message number (SQLCODE) and allinformation in the SQLCA if possible.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Then contact IBM as specified in thisguide.

sqlcode: -10012

sqlstate: 42724

SQL10013N The specified library name couldnot be loaded.

Explanation: The library module could not befound.

User Response: For DARI users, ensure that thespecified library is available.

v If the client application uses a fully qualifiedpath name to specify the DARI library, theDARI library must be stored in the givendirectory path. If the client application does


not use the path name, the DARI library mustbe stored in the default directory(<InstanceHomeDir>/sqllib/function). Where<InstanceHomeDir> is the home directory ofthe database manager instance.

v If the error message occurs during databasemanager start time then the user will have toreinstall the DB2 instance or the databasemanager product.

Federated system users: if the error messageoccurs as a result of issuing db2start on thefederated system and the name is “fromDB2_DJ_COMM” then the federated serverexperienced a problem loading one of thewrapper modules identified by theDB2_DJ_COMM environment variable. TheDB2_DJ_COMM environment variable must beupdated to contain only valid wrapper modules.

If the error message occurs as a result of issuingdb2start on the federated system and the name isnot “from DB2_DJ_COMM”, the user mustre-install the federated instance.

If the library identifies a wrapper module, thatmodule must be installed, link-edited (asrequired), and available in the correct directory.Refer to the Installation and ConfigurationSupplement for more information aboutconfiguring wrapper modules.

sqlcode: -10013

sqlstate: 42724

SQL10014N The invoking DARI programname name specified is not valid.

Explanation: The DARI library module or theDARI program name syntax is not correct.

User Response: Ensure that the DARI library orprogram name is specified correctly.

sqlcode: -10014

sqlstate: 42724

SQL10015N There are not enough systemresources to load the specifiedlibrary name.

Explanation: There is not enough memory toload the library module.

User Response: Stop the application. Possiblesolutions are:


v Decrease the values of the configurationparameters that define the allocation ofmemory.

v Install more memory.

sqlcode: -10015

sqlstate: 42724

SQL10017N The SQL CONNECT RESETstatement is not allowed in aDatabase Application RemoteInterface (DARI) procedure.

Explanation: The remote procedure contains anSQL CONNECT RESET statement.

User Response: Remove the SQL CONNECTRESET statement and retry the remote procedure.

sqlcode: -10017

sqlstate: 38003

SQL10018N The disk is full. Processing wasended.

Explanation: The disk is full. During the exportto a PC/IXF file, either the PC/IXF data file is ona fixed disk, or the PC/IXF data file and thedatabase are on the same file system, or thePC/IXF data file and the message file are on thesame file system.

The EXPORT utility stops processing. Theexported data is not complete.

User Response: Provide more space on the diskor specify that the data file be located on adifferent file system than the database or themessage file and resubmit the command.


SQL10019N The database cannot be accessedin the specified path.

Explanation: The database cannot be accessedfor one of the following reasons:

v The path does not contain a database image.

v Permissions on the path are incorrect.

User Response: Ensure that the path referencesa valid database and that the permissions arecorrect.

sqlcode: -10019

sqlstate: 58031

SQL10021N The file permissions do not allowwrite access to the database.

Explanation: A write operation was attemptedto a database residing on a file system whichdoes not allow write access.


User Response: Verify that the file permissionsfor the file system on which the database residesallow write access.

SQL20000 - SQL20099

SQL20005N The internal identifier limit oflimit has been exceeded for objecttype object-type.

Explanation: An internal identifier uniquelyidentifies objects of type object-type. The limit forinternal identifiers for this type of object hasbeen exceeded. This can happen during aCREATE DISTINCT TYPE, CREATE FUNCTION,CREATE PROCEDURE or CREATE SEQUENCEstatement, or an ALTER TABLE or CREATETABLE statement that defines an identitycolumn.


User Response: Drop objects of type object-typethat are no longer being used.

sqlcode: -20005

sqlstate: 54035

SQL20010N Mutation method method-ID is notallowed when the instance of thestructured type is NULL.

Explanation: The method method-ID is amutator method that is specified with aninstance of a structured type that is null. Mutatormethods cannot be processed on a null instance.In some cases, the method name is not available.


User Response: Determine the null instance that

is used with a mutator method. Use aconstructor function to create a non-null instanceof the structured type before using any mutatormethods on the instance.

To determine the method name associated withthe method-ID, use the following query:

SELECT FUNCSHEMA, FUNCNAME,SPECIFICNAME

FROM SYSCAT.FUNCTIONSWHERE

FUNCID = INTEGER(method-ID)

sqlcode: -20010

sqlstate: 2202D

SQL20011N Transform group group-name isalready defined for a subtype orsupertype of data type type-name.

Explanation: A transform group calledgroup-name already exists for a type in the samehierarchy as type-name. It may be defined for asupertype or subtype of type-name. A transformgroup name can only be used once within astructured type hierarchy.


User Response: Change the name of thetransform group.


sqlcode: -20011

sqlstate: 42739

SQL20012N Type type-name does not have anyassociated transform groups todrop.

Explanation: There are no transforms definedfor type-name. There is nothing to drop.

The statement did not drop any transformgroups.

User Response: Ensure the name of the type(including any required qualifiers) is correctlyspecified in the SQL statement and that the typeexists.

sqlcode: -20012

sqlstate: 42740

SQL20013N The object super-object-name is notvalid as a supertype, supertable,or superview of objectsub-object-name.

Explanation: If the statement resulting in theerror is creating a type, then super-object-name is atype that cannot be a supertype of sub-object-namebecause it is not a user-defined structured type.

If the statement resulting in the error is creatinga table, then super-object-name is a table thatcannot be a supertable of table sub-object-namebecause it is not defined as a typed table or thetype of table super-object-name is not the directsupertype of the type used in defining tablesub-object-name.

If the statement resulting in the error is creatinga view, then super-object-name is a view thatcannot be a superview of view sub-object-namebecause it is not defined as a typed view or thetype of view super-object-name is not the directsupertype of the type used in defining viewsub-object-name.


User Response: Specify a valid type, table, orview in the UNDER clause of the CREATEstatement.

sqlcode: -20013

sqlstate: 428DB

SQL20014N The transform group group-nametransform-type transform functionfor type type-name is not valid.Reason code = reason-code.

Explanation: The transform-type transformfunction in transform group group-name is notvalid. The reason is based on the reason-code asfollows.

1 There can only be one parameter for aFROM SQL transform function.

2 The parameter of a FROM SQLtransform function must be of typetype-name.

3 The RETURNS data type of a TO SQLtransform function must be of typetype-name.

4 The RETURNS type of a FROM SQLtransform function that returns a scalarmust be a built-in data type other thanDECIMAL.

5 All of the RETURNS types of a FROMSQL transform function that returns ascalar must be built-in data types otherthan DECIMAL.

6 There must be at least one parameter fora TO SQL transform function.

7 The parameter types for a TO SQLtransform function must all be built-indata types other than DECIMAL.

8 The TO SQL transform function must bea scalar function.

9 The FROM SQL transform functionmust be written using LANGUAGESQL, or must use another FROM SQLtransform function that is written usingLANGUAGE SQL.

10 The TO SQL transform function must bewritten using LANGUAGE SQL or use aTO SQL transform function that iswritten using LANGUAGE SQL.



User Response:

1 Specify a FROM SQL transform functionwith a signature that has only oneparameter.

2 Specify a FROM SQL transform functionwhere the type of the parameter is thesame as type-name.

3 Specify a TO SQL transform functionwhere the RETURNS type is the same astype-name.

4 Specify a FROM SQL transform functionwith a RETURNS type that is a built-indata type other than DECIMAL.

5 Specify a FROM SQL transform functionwhere each element of the row has aRETURNS type that is a built-in datatype other than DECIMAL.

6 Specify a TO SQL transform functionwith a signature that has at least oneparameter.

7 Specify a TO SQL transform functionwhere all the parameter types arebuilt-in data types other thanDECIMAL.

8 Specify a TO SQL transform functionthat is a scalar function.

9 Specify a FROM SQL transform functionthat is written using LANGUAGE SQL,or that uses another FROM SQLtransform function that is written usingLANGUAGE SQL.

10 Specify a TO SQL transform functionthat is written using LANGUAGE SQLor that uses a TO SQL transformfunction that is written usingLANGUAGE SQL.

sqlcode: -20014

sqlstate: 428DC

SQL20015N A transform group group-name isnot defined for data typetype-name.

Explanation: A specified transform groupgroup-name is not defined for the data typetype-name. The data type type-name may havebeen explicitly specified in the statement or maybe implicit based on the use of a structured typethat requires the existence of the transform groupfor the data type.

If group-name is empty, either the TRANSFORMGROUP bind option or the CURRENT DEFAULTTRANSFORM GROUP special register was notspecified and therefore there was no transformfor type-name.


User Response: Define transform grouptransform-type for data type type-name using theCREATE TRANSFORM statement. If the erroroccurred when dropping the transform, no actionis required because the transform group did notexist for the data type.

If group-name is empty, specify the TRANSFORMGROUP bind option on the CURRENTDEFAULT TRANSFORM GROUP special register.

sqlcode: -20015

sqlstate: 42741

SQL20016N The value of the inline lengthassociated with type or columntype-or-column-name is too small.

Explanation: For the definition of structuredtype type-or-column-name, it has an INLINELENGTH value specified that is smaller than thesize returned by the constructor function (32 + 10* number_of_attributes) for the type and is lessthan 292. For the altering of columntype-or-column-name, the INLINE LENGTHspecified is smaller than the current inline length.


User Response: Specify an INLINE LENGTHvalue that is large enough. For a structured type,that is at least the size returned by theconstructor function for the type or is at least


292. For a column, it must be larger than thecurrent inline length. If this error occurs whenaltering the type (or some supertype of this type)to add an attribute, either the attribute cannot beadded or the type must be dropped andre-created with a larger INLINE LENGTH value.

sqlcode: -20016

sqlstate: 429B2

SQL20017N Addition of this subtype exceedsthe maximum number of levels ofa type hierarchy.

Explanation: The maximum number of levels ina type hierarchy is 99. Adding this type wouldexceed the maximum.


User Response: Do not add any more subtypesto this type hierarchy.

sqlcode: -20017

sqlstate: 54045

SQL20018N Row function function-name mustreturn at most one row.

Explanation: The function is a defined to returna single row. The result of the processing thefunction is more than one row.

User Response: Ensure that the function isdefined in such a way that at most one row isreturned.

sqlcode: -20018

sqlstate: 21505

SQL20019N The result type returned from thefunction body cannot be assignedto the data type defined in theRETURNS clause.

Explanation: The data type of each columnreturned by the function body must beassignable to the corresponding column specifiedin the RETURNS clause. If the function is ascalar function, there is only one column.

User Response: Change the RETURNS type orthe type returned from the function body so thatthe data types of corresponding columns areassignable.

sqlcode: -20019

sqlstate: 42866

SQL20020N Operation operation-type is notvalid for typed tables.

Explanation: The operation identified byoperation-type cannot be performed on a typedtables.


User Response: Remove the ADD COLUMNclause or SET DATATYPE clause from the ALTERstatement. Columns can only be added byre-defining the table with a structured type thatincludes the new column as an attribute.Similarly, the data type of a column can only bechanged by re-defining the table with a type thatincludes the column with a different data type.

sqlcode: -20020

sqlstate: 428DH

SQL20021N Inherited column or attribute namecannot be changed or dropped.

Explanation: The value of name identifies eithera column name or an attribute name (dependingon the statement context) that is inherited from atyped table, typed view, or structured type aboveit in the table, view, or type hierarchy.

v In the CREATE TABLE statement, the WITHOPTIONS clause cannot be specified forcolumn name in the CREATE TABLE statementbecause it is inherited from a supertable in thetable hierarchy.

v In the ALTER TABLE statement, the SETSCOPE clause or COMPRESS clause cannot bespecified for column name because it isinherited from a supertable in the tablehierarchy.

v In the CREATE VIEW statement, the WITHOPTIONS clause cannot be specified for


column name in the CREATE VIEW statementbecause it is inherited from a superview in theview hierarchy.

v In the ALTER TYPE statement, the DROPATTRIBUTE clause cannot be specified forattribute name because it is inherited from asupertype in the type hierarchy.


User Response: The options for a column mayonly be set or altered for the table or view in thetyped table hierarchy or typed view hierarchywhere the column is introduced. An attribute canonly be dropped from the data type in the typehierarchy where the attribute was introduced.

sqlcode: -20021

sqlstate: 428DJ

SQL20022N The scope for the referencecolumn column-name is alreadydefined.

Explanation: The scope for the referencecolumn column-name cannot be added because itis already defined.


User Response: Remove the ADD SCOPEclause from the ALTER TABLE statement.

sqlcode: -20022

sqlstate: 428DK

SQL20023N Parameter parm-number of theexternal or sourced function has ascope defined.

Explanation: A reference type parameter shouldnot have a scope defined when used withexternal or sourced user defined functions.


User Response: Remove the SCOPEspecification from the definition of the parameter.

sqlcode: -20023

sqlstate: 428DL

SQL20024N The scope table or viewtarget-name is not defined withstructured type type-name.

Explanation: The scope table or viewtarget-name is not valid for use as the scope ofthis reference because it is:

v not a typed table or

v not a typed view or

v the type of the table or view is not the same asthe target type of the REF type.


User Response: Specify the scope of thereference using a typed table or typed view withthe same type as the target type of the REF type.

sqlcode: -20024

sqlstate: 428DM

SQL20025N SCOPE is not specified in theRETURNS clause of an externalfunction or is specified in theRETURNS clause of a sourcedfunction.

Explanation: There are two possible causes:

v A reference type must have a scope definedwhen used as the result of a user-definedexternal function.

v A reference type cannot have a scope definedwhen used as the result of an user-definedsourced function. The function will use thescope of the source function.


User Response: When defining an externalfunction with a reference type as a returns type,ensure that the SCOPE clause is specified. Whendefining SOURCED function with a referencetype as a returns type, ensure that the SCOPEclause is not specified.

sqlcode: -20025

sqlstate: 428DN


SQL20026N The type type-name is not astructured type or is not aninstantiable structured type.

Explanation: The statement requires astructured type that can be instantiated. The typetype-name is either:

v not a structured type; or

v a structured type that is defined as notinstantiable.


User Response: Verify that the correct typename is used in the statement.

sqlcode: -20026

sqlstate: 428DP

SQL20027N The subtable or subviewsub-object-name was not createdbecause subtable or subviewobject-name with type type-namealready exists.

Explanation: Within a typed table or viewhierarchy, only one subtable or subview mayexist of a particular subtype. The table or viewsub-object-name cannot be created since there isalready a table or view of type type-name defined.The table or view that already exists isobject-name.


User Response: Verify that the subtable orsubview is being created with the correct typeand that the subtable is being created under thecorrect supertable or the subview is beingcreated under the correct superview.

sqlcode: -20027

sqlstate: 42742

SQL20028N The table or view table-namecannot have a different schemaname from the other tables orviews in the same hierarchy.

Explanation: All tables in a typed tablehierarchy must have the same schema name and

all views in a typed view hierarchy must havethe same schema name.


User Response: Verify that the schema name ofthe table or view is correct. If a hierarchy nameis specified, verify that its schema name matchesthe schema name of the root table or view. If asubtable is being created, verify that it is beingcreated under the correct supertable. If a subviewis being created, verify that it is being createdunder the correct superview.

sqlcode: -20028

sqlstate: 428DQ

SQL20029N operation cannot be applied to asubtable.

Explanation: The operation operation wasapplied to a table that is not the root of a tablehierarchy.


User Response: Specify the root table of thetable hierarchy in the operation.

sqlcode: -20029

sqlstate: 428DR

SQL20030N Attributes of a structured typetype-name cannot be added ordropped when a typed table,typed view, or index extensionobject-name is dependent on thetype.

Explanation: The attributes of a structured typecannot be added or dropped if a typed table ortyped view of the structured type or any of itssubtypes currently exists. Attributes of astructured type also cannot be added or droppedwhen a column exists in the table that directly orindirectly uses type-name. Also, attributes of astructured type cannot be added or droppedwhen the type type-name or one of its subtypes isused in an index extension. The table, view, orindex extension object-name is one table, view, orindex extension that is dependent on thestructured type type-name. There may be other


tables, views, or index extensions that aredependent on the type or one of its propersubtypes.


User Response: Verify that the right type isbeing altered or drop any tables, views, andindex extensions that are dependent on thestructured type type-name.

sqlcode: -20030

sqlstate: 55043

SQL20031N Object may not be defined on asubtable.

Explanation: Primary key and uniqueconstraints can only be defined on the root tableof a typed table hierarchy. Similarly, uniqueindexes can only be defined on the root table ofa typed table hierarchy.


User Response: Unique indexes, Primary key orunique constraints can only be defined on theroot table of a table hierarchy.

sqlcode: -20031

sqlstate: 429B3

SQL20032N Index on the specified columnscannot be defined on subtabletable-name.

Explanation: The columns specified for theindex were all introduced at a higher level in thetyped table hierarchy than subtable table-name.Therefore, the index cannot be created on thissubtable.


User Response: Determine the table in the tablehierarchy where all of the columns are includedfor the first time. Use this as the table namewhen creating the index.

sqlcode: -20032

sqlstate: 428DS

SQL20033N An expression includingpartial-expression does not include avalid scoped reference.

Explanation: The expression that includespartial-expression requires an operand that isreference type with a scope defined. If theexpression includes the DEREF function, theargument of the function must be a referencetype with a scope defined.

For the dereference operator (->), the leftoperand needs to be a reference type with ascope defined.


User Response: Correct the SQL statementsyntax so the operand or argument is a referencetype with a scope defined.

sqlcode: -20033

sqlstate: 428DT

SQL20034N The data type list-type-name is notincluded in a structured data typehierarchy that includes the datatype left-type-name of the leftoperand of the TYPE predicate.

Explanation: All the data types listed in theTYPE predicate must be included in a data typehierarchy that includes the data type of the leftoperand of the TYPE predicate. The data typeleft-type-name is not a structured data type (notpart of any type hierarchy) or the data typelist-type-name is not included in the data typehierarchy that includes left-type-name.


User Response: Ensure that the data type of theexpression and all listed data types in the TYPEpredicate are structured data types within thesame data type hierarchy. If left-type-name isSYSIBM.REFERENCE, use DEREF to make theresult data type of the expression a structureddata type.

sqlcode: -20034

sqlstate: 428DU


SQL20035 Invalid left operand of adereference operator. Pathexpression starts withexpression-string.

Explanation: The left operand of the dereferenceoperator in a path expression is not valid.Possible causes are:

v The left operand includes a column functionthat uses a column function as an argument.

v The left operand expression includes a columnfunction and a reference to a column that isnot in the GROUP BY clause.

User Response: Correct the left operand of thedereference operator for the path expression thatstarts with expression-string.

sqlcode: -20035

sqlstate: 428DV

SQL20036N The object identifier columncolumn-name cannot be referencedusing the dereference operator.

Explanation: The dereference operator is usedwith column-name as the right operand. Thiscolumn is the object identifier column of thetarget table of the dereference and is not validfor this operator.


User Response: Correct the name of the columnin the dereference operation.

sqlcode: -20036

sqlstate: 428DW

SQL20037N Object identifier column isrequired to create the root table orroot view object-name of a typedtable or view hierarchy.

Explanation: When creating the root table of atyped table hierarchy, an object identifier (OID)column must be defined (using the REF ISclause) on the CREATE TABLE statement.

When creating the root view of a typed viewhierarchy, an object identifier (OID) column must

be defined (using the REF IS clause) on theCREATE VIEW statement.


User Response: Add the required OID column(REF IS clause) to the CREATE TABLE orCREATE VIEW statement.

sqlcode: -20037

sqlstate: 428DX

SQL20038N The keywords clause cannot bespecified with the EXTENDUSING clause.

Explanation: The EXTEND USING clause in theCREATE INDEX statement cannot be specifiedwith the keywords clause.


User Response: Remove the specification ofkeywords clause or the EXTEND USING clausefrom the CREATE INDEX statement.

sqlcode: -20038

sqlstate: 42613

SQL20039N The definition of index index-namedoes not match the definition ofindex extension index-ext-name.

Explanation: The index definition and the indexextension definition do not match. The followinglists the possibilities for where the definitions donot match.

v The number of arguments following the indexextension name in the EXTEND USING clauseis not the same as the number of instanceparameters of the index extension.

v The data types of the arguments following theindex extension name in the EXTEND USINGclause do not match exactly (including lengthor precision and scale) the data types of thecorresponding instance parameters of theindex extension.

v The number of columns specified for the indexis not same as the number of source keyparameters of the index extension.


v The data types of the index columns do notmatch exactly (including length or precisionand scale) the data types of the correspondingsource key parameters of the index extension.There is an exception to exact matching ofdata types for the case of subtypes. Thecolumn of the index may be a subtype of thedata type specified as the correspondingsource key parameter.


User Response: Change the index definition sothat the index extension matches.

sqlcode: -20039

sqlstate: 428E0

SQL20040N Number or type of the result ofthe range-producing tablefunction range-function-name, isinconsistent with that of keytransformation table functiontransform-function-name for indexextension index-ext-name.

Explanation: The range-producing functionmust:

v return up to twice as many columns asreturned by the key transformation function

v have an even number of columns (the first halfof the return columns are the start key valuesand the second half of the return columns arethe stop key values)

v have the each start key column with the sametype as the corresponding stop key column

v have the type of each start key column be thesame as the corresponding transformationfunction column.

More precisely, let a 1:t 1,... a n:t n be the functionresult columns and data types of the keytransformation function. The function resultcolumns of the range-producing function mustbe b 1:t 1,...,b m:t m,c 1:t 1,...,c m:t m, where m <= nand the ″b″ columns are the start key columnsand the ″c″ columns are the stop key columns.


User Response: Specify a range-producing tablefunction that is consistent with the keytransformation table function.

sqlcode: -20040

sqlstate: 428E1

SQL20041N Number or the type of target keyparameters does not match withthe number or type of keytransform function function-namefor index extension index-ext-name.

Explanation: The number of target keyparameters has to match with the number ofresults returned by the key transform function. Inaddition, the type of the target key parametersmust exactly match the corresponding functionresult types.


User Response: Specify the correct number andtype of parameters as the target key parameters.

sqlcode: -20041

sqlstate: 428E2

SQL20042N The maximum allowable parm-typeparameters is exceeded in indexextension index-ext-name. Themaximum is max-value.

Explanation: Too many parameters werespecified. If parm-typeis INDEX EXTENSION,then up to max-value instance parameters may bespecified. If parm-typeis INDEX KEYS, then up tomax-value key source parameters may bespecified.


User Response: Specify no more than themaximum number of parameters.

sqlcode: -20042

sqlstate: 54046


SQL20043N Argument for routine routine-nameis not valid. Reason code =reason-code.

Explanation: The routine routine-name could bethe transformation function, the range-producingfunction, or a routine (function or method)referenced in the FILTER USING clause. Thereason code indicates why an argument is notvalid:

1 For a key transformation function, theargument is not an observer method oran index extension instance parameter.

2 The expression used as the argumentuses a routine that specifiesLANGUAGE SQL.

3 The expression used as the argument isa subquery.

4 The data type of an expression used asthe argument cannot be a structuredtype.

5 The argument of a key transformationfunction cannot have a data type ofstructured data type, LOB, DATALINK,LONG VARCHAR, or LONGVARGRAPHIC.


User Response: Specify a valid argument forthe function.

sqlcode: -20043

sqlstate: 428E3

SQL20044N The routine routine-name or theCASE expression is not valid in aCREATE INDEX EXTENSION orCREATE FUNCTION statement.Reason code = reason-code.

Explanation: A routine (function or method)routine-name used in the CREATE INDEXEXTENSION or CREATE FUNCTION statementis not valid where it is used. If routine-name isempty, then the CASE expression used forfiltering is not valid. The reason code indicatesthe reason.

1 The key transformation function is not atable function.

2 The key transformation function is notan external function.

3 The key transformation function is avariant function.

4 The key transformation function is anexternal action function.

5 The range-producing function is not atable function.

6 The range-producing function is not anexternal function.

7 The range-producing function is avariant function.

8 The range-producing function is anexternal action function.

9 The index-filter function is not anexternal function.

10 The index-filter function is a variantfunction.

11 The index-filter function is an externalaction function.

12 The result type of a filter function orCASE expression is not an integer datatype.

13 A subquery is used in a CASEexpression or as an argument of a filterfunction.


User Response: If routine-name is not empty,specify a routine that conforms to the rules for afunction or method specified in the specificclause of the CREATE INDEX EXTENSION orCREATE FUNCTION statement. Otherwise,specify a CASE expression that conforms to therules for a CASE expression in the FILTERUSING clause.

sqlcode: -20044

sqlstate: 428E4


SQL20045N The data type of instanceparameter parameter-name isinvalid in index extensionindex-ext-name.

Explanation: An instance parameter must beone of the following data types: VARCHAR,VARGRAPHIC, INTEGER, DECIMAL, orDOUBLE.


User Response: Specify a valid data type forthe instance parameter parameter-name.

sqlcode: -20045

sqlstate: 429B5

SQL20046N SELECTIVITY clause followingpredicate-string can only bespecified for a valid user-definedpredicate.

Explanation: The SELECTIVITY clause isspecified with a predicate that does not include avalid user-defined function. A valid user-definedfunction includes a PREDICATES clause with aWHEN clause that matches the predicate. TheSELECTIVITY clause cannot be specified exceptwith a user-defined predicate.


User Response: Remove the SELECTIVITYclause following the predicate.

sqlcode: -20046

sqlstate: 428E5

SQL20047N The search method method-name isnot found in the index extensionindex-ext-name.

Explanation: The method method-namereferenced in an exploitation rule of theuser-defined predicate has to match one of thesearch methods specified in the index extensionindex-ext-name.


User Response: Specify a method defined in theindex extension.

sqlcode: -20047

sqlstate: 42743

SQL20048N The search argument of methodmethod-name does not match theone in the corresponding searchmethod in the index extensionindex-ext-name.

Explanation: The search argument provided formethod method-name does not match theargument of the corresponding search method inthe index extension index-ext-name. Either thenumber of arguments or the type of thearguments do not match the defined number ortype of the parameters.


User Response: Specify a search argument thatmatches the parameters defined in the indexextension.

sqlcode: -20048

sqlstate: 428E6

SQL20049N Type of an operand following thecomparison operator in the ASPREDICATE WHEN clause doesnot exactly match the RETURNStype.

Explanation: The definition of the user-definedpredicate is not valid. In the AS PREDICATEWHEN clause, the type of the operand followingthe the comparison operator is not an exactmatch with the RETURNS type of the function.


User Response: Specify an the operand with thecorrect data type.

sqlcode: -20049

sqlstate: 428E7


SQL20050N The search target or searchargument parameter-name does notmatch a name in the functionbeing created.

Explanation: Each search target in an indexexploitation rule has to match some parametername of the function that is being created. Eachsearch argument in an index exploitation rulemust match either an expression name in theEXPRESSION AS clause or a parameter name ofthe function being created. Parameter namesmust be specified in the parameter list for thefunction.


User Response: Specify only valid names of thefunction in the search target or search argument.

sqlcode: -20050

sqlstate: 428E8

SQL20051N The argument parameter-namecannot appear as both a searchtarget and a search argument inthe same exploitation rule.

Explanation: In the exploitation clause, afunction parameter cannot be specified as anargument following KEY and as an argument ofthe method specified following the USEkeyword.


User Response: Specify a parameter name ofthe function in no more than on of the searchtarget or the search argument.

sqlcode: -20051

sqlstate: 428E9

SQL20052N Column column-name is an objectidentifier column which cannot beupdated.

Explanation: The UPDATE statement includessetting a column that is an object identifier (OID)column. An OID column cannot be updated.


User Response: Remove the SET of column-namefrom the UPDATE statement.

sqlcode: -20052

sqlstate: 428DZ

SQL20053N Fullselect in typed view view-nameis not valid. Reason code =reason-code.

Explanation: The fullselect specified in thedefinition of typed view view-name does notconform to the rules for the fullselect of a typedview. Possible reason codes follow.

1 A subview definition contains acommon table expression, OR a branchin a subview definition does not rangeover a single table, view, nickname oran alias.

2 The row-set of a branch over atable-hierarchy cannot be proven by thedatabase manager to be distinct fromthe row-set of all branches over thesame table-hierarchy in the rest of thetyped view hierarchy.

3 The first expression of a branch over ahierarchy in the root view is:

v not the object identifier column of thetyped table or typed view referencedin the FROM clause and theUNCHECKED option in the REF ISclause is not used OR

v if the table in the FROM clause is nottyped, the column is nullable or doesnot have a unique index defined ononly that column and theUNCHECKED option in the REF ISclause is not used OR

v not identical to the expression in thebranch over the same hierarchy in thesubview.

4 A table or view over which a branch ofa subview ranges is not a subtable orsubview of the table or view referencedin any branch of the superview andeither the subview uses EXTEND AS or


the root view does not have theUNCHECKED option in the REF ISclause turned on.

5 The fullselect includes references to theNODENUMBER or PARTITIONfunctions, non-deterministic functions,or functions defined to have externalaction.

6 A branch in a subview cannot rangeover an OUTER table or view if anybranch in its superview ranges over atable or view in the same hierarchywithout using OUTER.

7 A subview ranges over a view in itsown view hierachy.

8 A subview uses a set operation otherthan UNION ALL in its definition ORUNION ALL is used in the definitionwithout specifying the UNCHECKEDoption in the REF IS clause of the rootview.

9 A subview contains two branches of aUNION ALL that range over the sametable hierarchy or view hierarchy.

10 The subview definition contains aGROUP BY or HAVING clause.

User Response: Change the fullselect of theview definition based on the reason-code.

1 Use only one table or view in the FROMclause. Encapsulate complex selects intoviews that the typed view can rangeover using the UNCHECKED option ofthe root view’s REF IS clause.

2 Specify a different table or view in theFROM clause of each branch that is notthe same as one already used in theview hierarchy or use a predicates thatclearly define the row-set for eachbranch as distinct compared to therow-sets for other branches in the typedview hierarchy.

3 Ensure that the first column of the rootview conforms to the rules to be a validobject identifier column for the typed

view. Consider using the UNCHECKEDoption in the ref is clause.

4 Specify a subtable or subview of thetable or view specified in the FROMclause of a branch of the superview. Oruse the UNCHECKED option in the rootview definition in conjunction with theAS (without EXTEND) clause in thesubview definition.

5 Remove the reference to the functionfrom the fullselect.

6 If this is the first subview to use OUTERin a branch over this hierarchy, changethe FROM clause so that OUTER is notused. If the superview uses OUTER,include OUTER in the FROM clause ofthe subview.

7 Do not source a subview on other viewsin the same hierarchy.

8 If UNION ALL was used, use theUNCHECKED option in the REF ISclause of the rootview to allow multiplebranches in the subview definition. Forother set operations encapsulate the setoperation into a view and use theUNCHECKED option in the subview toallow sourcing on common views.

9 Unify the branches to a select over theircommon supertable or superview anduse predicates (e.g. the type predicate)to filter for the desired rows.

10 Encapsulate the GROUP BY andHAVING clause into a view and use theUNCHECKED option in the root viewto allow sourcing on common views.

sqlcode: -20053

sqlstate: 428EA

SQL20054N The table table-name is in aninvalid state for the operation.Reason code = reason-code.

Explanation: The table is in a state that doesnot allow the operation. The reason code


indicates the state of the table that prevents theoperation.

21 The table is in Datalink ReconcilePending (DRP) state or DatalinkReconcile Not Possible (DRNP) state.

22 The function cannot be used in agenerated column.



21 Refer to the Administration Guide forinformation on Datalink ReconcilePending (DRP) and Datalink ReconcileNot Possible (DRNP) states to takeappropriate action.

22 Use SET INTEGRITY FOR <table-name>OFF before altering the table. Then alterthe table and use SET INTEGRITY FOR<table-name> IMMEDIATE CHECKEDFORCE GENERATED to generate thevalues for the new or altered column.

sqlcode: -20054

sqlstate: 55019

SQL20055N A result column data type in theselect list is not compatible withthe defined data type for columncolumn-name.

Explanation: The data type of the select listexpression corresponding to column-name isincompatible with the data type for the attributeof the structured type. Both must be:

v Numeric

v Character

v Graphic

v Dates or character

v Times or character

v Timestamps or character

v Datalinks

v the same distinct types

v reference types where the target type of theselect list expression is a subtype of the targettype of the attribute.


User Response: Examine the current definitionfor the table and the associated structured type.Ensure the select list expression data type for thespecified column is a compatible type.

sqlcode: -20055

sqlstate: 42854

SQL20056N Processing on DB2 Data LinksManager name encountered anerror. Reason code = reason-code.

Explanation: The processing on the DB2 DataLinks Manager for the statement encountered anerror as indicated by the following reason codes.

01 An inconsistency was detected betweenthe data on the DB2 Data LinksManager and a DATALINK value in atable.

02 The DB2 Data Links Manager reached aresource limit during the processing.

03 The DB2 Data Links Manager does notsupport file pathnames longer than 128characters.

99 The DB2 Data Links Managerencountered an internal processingerror.



01 Run the reconcile utility on the table.

02 The DB2 Data Links Manageradministrator should identify theresource from the diagnostic logs andtake corrective action.

03 You should ensure that the filepathname (excluding the file systemprefix) to be stored in the DATALINKcolumn does not exceed 128 characters.


For example, in the URL″http://server.com/dlfiles/dir1/.../file1″-- assuming the DLFS file system prefixis ″/dlfiles″ -- the file pathname″/dir1/.../file1″ must not exceed 128characters.

99 Save the diagnostic logs from the DB2Data Links Manager and the databasemanager and contact IBM service.

sqlcode: -20056

sqlstate: 58004

SQL20057N Column column-name in subviewview-name cannot be defined asread only when the correspondingcolumn is updatable in thesuperview.

Explanation: The column identified bycolumn-name in the subview view-name is defined(implicitly) as read only. The superview ofview-name includes the corresponding columnthat is updatable. A column cannot be changedfrom updatable to read only in a typed viewhierarchy.


User Response: Change the CREATE VIEWstatement so that the column of the subviewview-name is updatable or drop the superview(s)and recreate them using the READ ONLY clauseto force the column to be read only.

sqlcode: -20057

sqlstate: 428EB

SQL20058N The fullselect specified for thematerialized query table table-nameis not valid.

Explanation: The materialized query tabledefinition has specific rules regarding thecontents of the fullselect. Some rules are basedon the materialized query table options(REFRESH DEFERRED or REFRESHIMMEDIATE) while others are based on whetheror not the table is replicated. The fullselect in the

CREATE TABLE statement that returned thiscondition violates at least one of the rules asdescribed in the SQL Reference.


User Response: Change the fullselect in theCREATE TABLE statement so that it conforms tothe rules based on the materialized query tableoptions and whether or not the materializedquery table is replicated.

sqlcode: -20058

sqlstate: 428EC

SQL20059W The materialized query tabletable-name may not be used tooptimize the processing ofqueries.

Explanation: The materialized query table isdefined with REFRESH DEFERRED and afullselect that is currently not supported by thedatabase manager when optimizing theprocessing of queries. The rules are based on thematerialized query table options (REFRESHDEFERRED or REFRESH IMMEDIATE). Thefullselect in the CREATE TABLE statement thatreturned this condition violates at least one ofthe rules as described in the SQL Reference.

The materialized query table is successfullycreated.

User Response: No action is required. If thematerialized query table was intended for use asa summary table to optimize the processing ofqueries, redefine the fullselect to ensure that it isa subselect that includes a GROUP BY clause.

sqlcode: +20059

sqlstate: 01633

SQL20060N The key transform table functionused by the index extension ofindex index-id of table table-id intbspace-id generated duplicaterows.

Explanation: The key transform table functionspecified by the GENERATE USING clause of theindex extension used by index index-id generated


duplicate rows. For a given invocation of the keytransform table function, no duplicate rowsshould be produced. This error is occurred wheninserting or updating the key value for the indexindex-id of table table-id in table space tbspace-id.


User Response: The code for the key transformtable function used by the index extension ofindex index-id must be modified to avoid thecreation of duplicate rows.

To determine the index name, use the followingquery:

SELECT IID, INDSCHEMA, INDNAMEFROM SYSCAT.INDEXES AS I,

SYSCAT.TABLES AS TWHERE IID = <index-id>

AND TABLEID = <table-id>AND TBSPACEID = <tbspace-id>AND T.TBASCHEMA = I.TABSCHEMAAND T.TABNAME = I.TABNAME

sqlcode: -20060

sqlstate: 22526

SQL20062N Transform function transform-typein transform group group-name fortype type-name cannot be used fora function or method.

Explanation: The transform function defined inthe transform group group-name for typetype-name cannot be used for a function ormethod because the transform function is notwritten in SQL (defined with LANGUAGE SQL).The transform group cannot be used for thisfunction or method.


User Response: Specify a transform group fortype type-name that has the transform functionsdefined with LANGUAGE SQL.

sqlcode: -20062

sqlstate: 428EL

SQL20063N TRANSFORM GROUP clausemust be specified for typetype-name.

Explanation: The function or method includes aparameter or returns data type of type-name thatdoes not have a transform group specified.


User Response: Specify a TRANSFORMGROUP clause with a transform group name thatis defined for type-name.

sqlcode: -20063

sqlstate: 428EM

SQL20064N Transform group group-name doesnot support any data typespecified as a parameter orreturned data type.

Explanation: The transform group group-namespecified in the TRANSFORM GROUP clause isnot defined for any data type that is included inthe parameter list or the RETURNS clause of afunction or method.


User Response: Remove the transform groupfrom the function or method definition.

sqlcode: -20064

sqlstate: 428EN

SQL20065N Transform group group-name fordata type type-name cannot beused to transform a structuredtype for use with a clientapplication.

Explanation: The transform group group-namefor data type type-name defines a transformfunction that cannot be used when performingtransforms for client applications. The possiblereasons for this are based on the definition of thetransform function that is not supported forclient applications. The unsupported transformfunction may be:

v a FROM SQL function that is a ROW function


v a TO SQL function has more than oneparameter


User Response: For static embedded SQL,specify a different transform group using theTRANSFORM GROUP bind option. For dynamicSQL, specify a different transform group usingthe SET DEFAULT TRANSFORM GROUPstatement.

sqlcode: -20065

SQL20066N The transform-type transformfunction is not defined in thetransform group group-name fordata type type-name.

Explanation: The transform-type transformfunction of transform group group-name for datatype type-name is required for a transform groupused in a function or method definition.


User Response: If creating a function ormethod, specify a different transform group inthe function or method definition. If referencinga structured type in a dynamic SQL statement,specify a different transform group for theCURRENT DEFAULT TRANSFORM GROUPspecial register. Alternatively, add a transform-typetransform function to the transform groupgroup-name for data type type-name.

sqlcode: -20066

sqlstate: 42744

SQL20067N The transform-type transformfunction is defined more thanonce in the transform groupgroup-name for data type type-name.

Explanation: A TO SQL or FROM SQLtransform function can only be specified once ina transform group. The transform groupgroup-name for data type type-name has at leasttwo FROM SQL or TO SQL (or both) transformfunctions defined.


User Response: Delete the TO SQL or FROMSQL definitions from group-name in the transformdefinition so that there is only one of each.

sqlcode: -20067

sqlstate: 42628

SQL20068N The structured type type-name maynot be defined so that one of itsattribute types directly orindirectly uses itself. The attributeattribute-name causes the direct orindirect use.

Explanation: Direct use: Type A is said todirectly use type B if one of the following is true:

v Type A has an attribute of type B

v Type B is a subtype of A, or a supertype of A.

Indirect use: Type A is said to indirectly use typeB if the following is true:

v Type A uses type C, and type C uses type B.

You cannot define a type so that one of itsattribute types directly or indirectly uses itself.The type for attribute attribute-name is the causeof the direct or indirect use.

User Response: Evaluate the type and removethe attribute type that causes the direct orindirect use.

sqlcode: -20068

sqlstate: 428EP

SQL20069N The RETURNS type of theroutine-type routine-name is not thesame as the subject type.

Explanation: The method method-name specifiesSELF AS RESULT. The RETURNS data type ofthe method must be the same as the subject datatype of the method.

User Response: Change the RETURNS type ofthe method method-name to match the subjecttype.

sqlcode: -20069

sqlstate: 428EQ


SQL20075N The index or index extensionindex-name cannot be created oraltered because the length ofcolumn-name is more than 255bytes.

Explanation: The index could not be created oraltered because the key column length is greaterthan 255.

v index-name is the index name.

v column-name is the name of the key column. Ifthis error was returned from an ALTER TABLEoperation, then the value of column-name is thecolumn number.

The index extension could not be created becausea column returned by the GENERATE KEYfunction is greater than 255 bytes.

v index-name is the index extension name.

v column-name is the name of a column returnedby the GENERATE KEY function.

The statement could not be processed. Thespecified index or index extension was notcreated, or the table could not be altered.

User Response: If creating an index, eliminatethe column from the index definition. If alteringa table, reduce the new column length to thepermitted maximum. If creating an indexextension, specify a different GENERATE KEYfunction, or redefine the function to eliminate thecolumn.

sqlcode: -20075

sqlstate: 54008

SQL20076N The instance for the database isnot enabled for the specifiedaction or operation. Reason code =reason-code.

Explanation: An error has been detected at theinstance level. The requested operation cannot becompleted because a specified functional areawas not installed or because a specifiedfunctional area was not enabled to the instance.

The following is the list of reason codes and

associated functional areas you can enable at theinstance level:

1. The ability to execute distributed requestoperations against multiple data sources in asingle statement.

User Response: Enable the instance for therequested action or operation. First, install thespecified functional area if it is missing. Then,enable the specified functional area. Enablementsteps vary by reason-code:

1. Set the DBM variable <DREQ> to ON andthen restart the database manager. For afederated server, set the DBM variable<FEDERATED> to YES and then restart thedatabase manager.

sqlcode: -20076

sqlstate: 0A502

SQL20077N Cannot construct structured typeobjects that have Datalink typeattributes.

Explanation: An attempt was made to invokethe constructor of a structured type which has aDatalink and/or a Reference type attribute. Thisfunctionality is currently not supported. InVersion 6.1 or earlier, this error may also beissued for a structured type object with aReference type attribute.


User Response: The error can be corrected bydoing one of the following:

1. Removing the invocation of the constructor ofthe type from the program.

2. Removing any Datalink (or Reference) typeattributes from the definition of thestructured type (this may not be possible ifthere are any tables that depend on this type).

sqlcode: -20077

sqlstate: 428ED


SQL20078N Hierarchy object object-name oftype object-type can not beprocessed using operationoperation-type.

Explanation: The operation operation-type wasattempted using a hierarchy object namedobject-name of type object-type. This operationdoes not support processing of a hierarchyobject.


User Response: Verify that the correct objectname was used. For objects types TABLE orVIEW, the object must be the name of a subtablein the table or view hierarchy. In some cases, theobject must specifically name the root table. Forobjects of type index, the name must be a nameof an index created on a subtable.

sqlcode: -20078

sqlstate: 42858

SQL20080N Method specification formethod-name cannot be droppedbecause a method body exists.

Explanation: The method specificationmethod-name still has an existing method bodythat must be dropped before the methodspecification can be dropped.


User Response: Use the DROP METHODstatement with the same method specification todrop the method body and then issue the ALTERTYPE statement again to drop the methodspecification.

sqlcode: -20080

sqlstate: 428ER

SQL20081N The method body cannot bedefined for a LANGUAGElanguage-type method specificationmethod-name.

Explanation: The method specificationmethod-name is defined with LANGUAGE language-type.If the LANGUAGE is SQL, the method body

must be an SQL control statement. For otherlanguages, the EXTERNAL clause must bespecified.


User Response: Change the method body tomatch the LANGUAGE specified in the methodspecification.

sqlcode: -20081

sqlstate: 428ES

SQL20082N The dynamic type expression-type-idof the expression is not a subtypeof the target data typetarget-type-id in a TREATspecification.

Explanation: The dynamic data type of theresult of the expression specified in the TREATspecification is expression-type-id. The specifiedtarget data type target-type-id is a proper subtypeof expression-type-id which is not allowed.


User Response: Change the target-type-id of theTREAT specification to a supertype ofexpression-type-id or change the expression so thatthe dynamic data type of the result is a subtypeof target-type-id.

To determine the data type names forexpression-type-id and target-type-id, use thefollowing query:

SELECT TYPEID, TYPESCHEMA, TYPENAMEFROM SYSCAT.DATATYPESWHERE TYPEID IN INTEGER(

expression-type-id),INTEGER(

target-type-id)

)

sqlcode: -20082

sqlstate: 0D000


SQL20083N The data type of the valuereturned by routine-type routine-iddoes not match the data typespecified as RESULT.

Explanation: The method routine-id specifiesSELF AS RESULT and therefore requires that thedata type of the value returned must be the sameas the subject data type used to invoke themethod. The RETURN statement in either theSQL method body or in the TO SQL transformfunction for the type of an external methodresulted in the incorrect data type.


User Response: Change the RETURN statementof the method or transform function to ensurethat the data type of the returned value is alwaysthe subject type used to invoke the method.

To determine the routine name associated withthe routine-id, use the following query:

SELECT FUNCSCHEMA, FUNCNAME,SPECIFICNAME

FROM SYSCAT.FUNCTIONSWHERE FUNCID = INTEGER(

routine-id)

sqlcode: -20083

sqlstate: 2200G

SQL20084N The routine-type routine-namewould define an overridingrelationship with an existingmethod.

Explanation: A method MT, with subject type T,is defined to override another method MS, withsubject type S, if all of the following conditionsare true:

v MT and MS have the same unqualified nameand the same number of parameters.

v T is a proper subtype of S.

v The non-subject parameter-types of MT are thesame as the corresponding non-subjectparameter-types of MS. (Here, “same” appliesto the basic type, such as VARCHAR,disregarding length and precision).

A function and a method may not be in anoverriding relationship. This means that if thefunction were a method with its first parameteras subject S, it must not override another methodof any supertype of S and it must not beoverridden by another method of any subtype ofS.

Furthermore, overriding relationships are notsupported for:

v table and row methods

v external methods with PARAMETER STYLEJAVA

v system generated mutator and observermethods


User Response: Change the routine that isbeing defined to use a different routine namethan routine-name or change the parameters ofthe routine.

sqlcode: -20084

sqlstate: 42745

SQL20085N A routine defined withPARAMETER STYLE JAVA cannothave structured type type-name asa parameter type or as the returnstype.

Explanation: A routine is defined withPARAMETER STYLE JAVA and one of theparameter types or a returns type is definedusing the structured type type-name. This is notsupported by this version of DB2.


User Response: Change to a different parameterstyle for the routine or remove the structuredtype from the routine definition.

sqlcode: -20085

sqlstate: 429B8


SQL20086N Length of the structured typevalue for a column exceeds thesystem limit.

Explanation: The value for a structured typecolumn exceeds 1 gigabyte in overall size,including descriptor data for the instance. Thecolumn could be one that is being inserted orupdated directly or it may be a column that isgenerated.


User Response: Reduce the size of thestructured type value that is being assigned tothe column.

sqlcode: -20086

sqlstate: 54049

SQL20087N DEFAULT or NULL cannot beused in an attribute assignment.

Explanation: The UPDATE statement is usingan attribute assignment to set the value of anattribute in a structured type column. This formof assignment statement does not allow the useof the keyword DEFAULT or the keyword NULLas the right hand side of the assignment.


User Response: Specify an expression for theright hand side of the attribute assignment orchange the assignment so it is not using theattribute assignment syntax.

sqlcode: -20087

sqlstate: 428B9

SQL20089N A method name cannot be thesame as a structured type namewithin the same type hierarchy.

Explanation: A specified method name is thesame as the structured type which is defined forone of the supertypes or subtypes of thestructured type.


User Response: Specify a different name for themethod.

sqlcode: -20089

sqlstate: 42746

SQL20090W The use of the structured typehaving attribute attribute-name oftype DATALINK is effectivelylimited to the type of a typedtable or type view.

Explanation: The attribute attribute-name isdefined with a type of DATALINK or a distincttype based on a DATALINK. A structured typethat includes such an attribute can only be usedas the type of a table or view. If used as the typeof a column of a table or view it can only beassigned the null value.

The statement continued processing.

User Response: Consider the intended use ofthe structured type. If the type will be used as acolumn data type, then remove the attributeattribute-name from the structured type or use adata type other than DATALINK for theattribute.

sqlcode: +20090

sqlstate: 01641

SQL20093N The table table-name cannot beconverted to or from amaterialized query table. Reasoncode = reason-code.

Explanation: The ALTER TABLE statement isbeing used to change a table from a materializedquery table to DEFINITION ONLY or to converta regular table to a materialized query table. TheALTER TABLE statement failed as indicated bythe following reason codes.

1 The table is a typed table or hierarchytable.

2 The table is not a materialized querytable and DEFINITION ONLY wasspecified.

3 The table is a replicated materializedquery table and DEFINITION ONLYwas specified.


4 The table has at least one triggerdefined.

5 The table has at least one checkconstraint defined.

6 The table has at least one uniqueconstraint or unique index defined.

7 The table has at least one referentialconstraint defined.

8 The table is referenced in the definitionof an existing materialized query table.

9 The table is referenced directly orindirectly (through a view, for example)in the fullselect.

10 The table is already a materializedquery table.

11 The number of columns of the existingtable does not match the number ofcolumns defined in the select list of thefullselect.

12 The data types of the columns of theexisting table do not exactly match thecorresponding columns in the select listof the fullselect.

13 The column names of the columns ofthe existing table do not exactly matchthe corresponding column names in theselect list of the fullselect.

14 The nullability characteristics of thecolumns of the existing table do notexactly match the nullabilitycharacteristics of the correspondingcolumns in the select list of thefullselect.

15 The conversion cannot be performed ifthere are any other table alterations inthe same ALTER TABLE statement.


1 The table cannot be converted to amaterialized query table. Create a newmaterialized query table instead.

2 There is no need to convert this table.No action required.

3 A replicated table can only be amaterialized query table. Create a newtable instead.

4 Drop any triggers and try the ALTERTABLE statement again.

5 Drop any check constraints and try theALTER TABLE statement again.

6 Drop any unique constraints and uniqueindexes. Try the ALTER TABLEstatement again.

7 Drop any referential constraints and trythe ALTER TABLE statement again.

8 Drop the materialized query table thatreferences the table and try the ALTERTABLE statement again.

9 A materialized query table cannotreference itself. Modify the fullselect toremove the direct or indirect referenceto the table being altered.

10 The operation is not allowed since thetable is already a materialized querytable.

11 Modify the fullselect to include thecorrect number of columns in the selectlist.

12 Modify the fullselect so that the resultcolumn data types exactly match thedata types of the corresponding existingcolumns.

13 Modify the fullselect so that the resultcolumn names exactly match thecolumn names of the correspondingexisting columns.

14 The table cannot be converted to amaterialized query table unless thenullability characteristics can bematched. Create a new materializedtable instead.

15 Perform the other table alterations in anALTER TABLE statement that does notinclude the SET MATERIALIZEDQUERY AS clause.

sqlcode: -20093


sqlstate: 428EW

SQL20094N The column column-name isGENERATED using an expressionand cannot be used in theBEFORE trigger trigger-name.

Explanation: The value for column column-nameis generated using an expression and cannot be

named in the column name list of a BEFOREUPDATE trigger or referenced as a newtransition variable in a BEFORE trigger.

User Response: Remove the reference tocolumn-name in the trigger trigger-name.

sqlcode: -20094

sqlstate: 42989

SQL20100 - SQL20199

SQL20102N The CREATE or ALTER statementfor the routine routine-namespecified the option-name optionwhich is not allowed for theroutine.

Explanation: The option option-name wasspecified when creating or altering the routineroutine-name. The option does not apply to theroutine because of other characteristics of theroutine.

User Response: For an ALTER statement,ensure that the correct routine is being specified.Otherwise, remove the failing option and reissuethe statement.

sqlcode: -20102

sqlstate: 42849

SQL20108N A result set contains anunsupported data type in positionposition-number for the cursorcursor-name opened by the storedprocedure procedure-name.

Explanation: The stored procedure named byprocedure-name cannot return at least one of itsquery result sets named by cursor-name becauseat least one of the columns, columnposition-number contains a data type which isnot supported by either the DRDA ApplicationRequestor (client) or the DRDA ApplicationServer (server). As such the call to the storedprocedure fails.

User Response: Modify the OPEN statement(and subsequent FETCH statements) for cursorcursor-name in the stored procedure

procedure-name on the server to not select theunsupported data type in columnposition-number. The client application whichinvoked the stored procedure may need to bemodified to reflect the change in the storedprocedure.

sqlcode: -20108

sqlstate: 56084

SQL20109W Error in DB2 debugger support.Reason code: reason-code.

Explanation: The debugger support had anerror situation which will disable debugging, butnot affect normal execution. The following is alist of reason codes:

1. The debugger support is not installed.

2. There has been a syntax error in IP address ofdebugger client in the debugger table.

3. A timeout in the communication between thedebugger backend and the debugger clientoccurred.

4. A problem occurred accessing the debuggertable DB2DBG.ROUTINE_DEBUG.

User Response:

1. Verify that you install the debugger option onthe DB2 server machine.

2. Make sure that the IP address in thedebugger table has the correct syntax.

3. Check that the debugger demon on the clientis started and that the ports on the client andserver match.

4. Verify that you have created the debuggertables with the correct layout.


sqlcode: +20109

sqlstate: 01637

SQL20111N A SAVEPOINT, RELEASESAVEPOINT, or ROLLBACK TOSAVEPOINT statement cannot beissued in this context. Reasoncode = reason-code.

Explanation: The statement cannot be processedbecause it violates a restriction as indicated bythe following reason code:

1. Savepoint cannot be issued inside a trigger.

2. Savepoint cannot be issued inside a globaltransaction.


User Response: Remove the SAVEPOINT,RELEASE SAVEPOINT, or ROLLBACK TOSAVEPOINT statement in the trigger or globaltransaction.

sqlcode: -20111

sqlstate: 3B503

SQL20112N A SAVEPOINT cannot be setbecause a SAVEPOINT alreadyexists and nested SAVEPOINTSare not supported.

Explanation: An error occurred in aSAVEPOINT or atomic compound SQLstatement. A savepoint already exists and nestedsavepoints are not supported in thisenvironment.

User Response: If re-establishing an existingsavepoint is necessary, issue the RELEASESAVEPOINT statement to free the existingsavepoint, and then reissue the SAVEPOINTstatement. For atomic compound SQL, aSAVEPOINT cannot be set until after the end ofthe compound statement.

sqlcode: -20112

sqlstate: 3B002

SQL20113N Null cannot be returned frommethod method-id defined withSELF AS RESULT.

Explanation: The method with methodidentifier method-id is defined with SELF ASRESULT. The invocation of the method used anon-null instance of a structured type so themethod cannot return a null instance.

User Response: Change the methodimplementation to ensure that a null value is notreturned as the return value for the method. Onepossibility is to set all the attributes of thereturned structured type to null value. Todetermine the name of the method that failed,use the following query:

SELECT FUNCSCHEMA, FUNCNAME,SPECIFICNAME

FROM SYSCAT.FUNCTIONSWHERE FUNCID = method-id

sqlcode: -20113

sqlstate: 22004

SQL20114W Column column-name in tabletable-name is not long enough forthe defined length of the USERdefault value.

Explanation: The column column-name isdefined with a length that is less than 128 bytes.The clause DEFAULT USER has been specifiedfor this column. Since the USER special registeris defined as VARCHAR(128), any attempt toassign the default value for table-name by a userwith a user ID longer than the column lengthresults in an error. A user with a user ID longerthan the column length would never be able toinsert or update this column to the default value.

User Response: If your system standards wouldnot allow a user ID to exceed the length of thecolumn, then this warning may be ignored. Toprevent this warning from occurring, the lengthof the column must be at least 128 bytes. You canchange the column length by dropping andcreating the table again, or, if the data type isVARCHAR, by using ALTER TABLE to increasethe length of the column.


sqlcode: +20114

sqlstate: 01642

SQL20115N The routine-type routine-namecannot be used as a transform-typetransform function in transformgroup group-name.

Explanation: If routine-type is FUNCTION, thenthe function defined by routine-name cannot beused as a transform function because it is abuilt-in function. If routine-type is METHOD, thenthe method defined by routine-name cannot beused as a transform function because it is amethod.


User Response: Specify a different function forthe transform-type transform function oftransform group group-name.

sqlcode: -20115

sqlstate: 428EX

SQL20116N The data type of the search targetparameter-name does not match thatof the source key specified in theindex extensionindex-extension-name.

Explanation: If the search target is of a built-inor distinct data type, its type must exactly matchthat of the source key specified in the indexextension. If the data type of the search target isa structured type, it must be in the samestructured type hierarchy as the data type of thesource key in the index extension.


User Response: Specify a search target with adata type that matches that of the source key inthe index extension.

sqlcode: -20116

sqlstate: 428EY

SQL20117N A window specification for anOLAP function is not valid.Reason code = reason-code.

Explanation: The window specification (OVERclause) of an OLAP function invocation is notcorrectly specified. The incorrect specification isindicated by the reason-code.

1 RANGE or ROWS is specified withoutan ORDER BY in the windowspecification.

2 RANGE is specified and the windowORDER BY clause includes more thanone sort-key-expression.

3 RANGE is specified and the data typeof the range value cannot be used in asubtraction expression with the datatype of the sort-key-expression in thewindow ORDER BY clause.

4 UNBOUNDED PRECEDING is specifiedafter CURRENT ROW or UNBOUNDEDFOLLOWING is specified beforeCURRENT ROW.


User Response: Change the windowspecification to correct the invalid specificationindicated by the reason-code.

1 Add a window ORDER BY clause toeach window specification that specifiesRANGE or ROWS.

2 Ensure that each window specificationthat includes RANGE has exactly onesort-key-expression in the windowORDER BY clause.

3 For each window specification thatincludes RANGE, ensure that the rangevalue can be subtracted from thesort-key-expression in the windowORDER BY clause, which must be anumeric type or a datetime type. Fordatetime sort-key-expressions, the rangevalue must be the specific datetimeduration DECIMAL type with thecorrect precision and scale.


4 Ensure that any window specificationusing “BETWEEN” and “CURRENTROW” has the “UNBOUNDEDPRECEDING” before “AND CURRENTROW” or “UNBOUNDEDFOLLOWING” after “CURRENT ROWAND”.

sqlcode: -20117

sqlstate: 428EZ

SQL20118N Structured type type-name hasmore than the maximum numberof allowable attributes. Themaximum is max-value.

Explanation: The maximum number ofattributes, including inherited attributes, allowedfor each structured type has been exceeded withthe definition of structured type type-name. Themaximum number of attributes, includinginherited attributes, is max-value.


User Response: Ensure that the number ofattributes for the structured type does not exceedthe limit.

sqlcode: -20118

sqlstate: 54050

SQL20119N A ROW function must define atleast two columns.

Explanation: A function that specifies ROW inthe RETURNS clause must include a column listwith at least two columns.

User Response: Either remove the ROWkeyword from the RETURNS clause to make it ascalar function or specify multiple columns inthe column list of the RETURNS clause.

sqlcode: -20119

sqlstate: 428F0

SQL20120N An SQL TABLE function mustreturn a table result.

Explanation: An SQL function that specifiesTABLE in the RETURNS clause must return aresult that is a table. With the exception of ascalar fullselect, a scalar expression cannot bereturned as the result of an SQL TABLE function.

User Response: Either remove the TABLEkeyword from the RETURNS clause to make it ascalar function or specify a fullselect in theRETURN statement of the TABLE function body.

sqlcode: -20120

sqlstate: 428F1

SQL20121N Only one of WITH RETURN orSCROLL can be specified forcursor cursor-name.

Explanation: Both WITH RETURN andSCROLL were specified for cursor cursor-name,but this is not allowed.


User Response: Change the DECLARECURSOR statement to either specify NOSCROLL (or remove the SCROLL keyword), orremove the WITH RETURN clause.

sqlcode: -20121

sqlstate: 428F3

SQL20123 CALL to stored procedureprocedure failed because the resultset returned for a scrollable cursoris not positioned before the firstrow.

Explanation: A scrollable result set has beenreturned by a CALL to stored procedureprocedure, and one or more of these cursors is notpositioned before the first row.

The CALL to the stored procedure was notsuccessful. All result set cursors defined in thestored procedure were closed before returning tothe caller. The scrollable cursor cannot be used toFETCH from the result set. Actions done by thestored procedure are not rolled back, and any


external actions initiated by the stored procedurehave completed because the error was detectedat the end of the execution of the storedprocedure.

User Response: Modify the content of thestored procedure to make sure that the result setcursors are positioned before the first row beforereturning to the caller.

sqlcode: -20123

sqlstate: 560B1

SQL20128 Cursor cursor-name is scrollable,but the result table cannot includeoutput from a table function.

Explanation: The cursor cursor-name is definedto be scrollable, but the result table includesoutput from a table function. This combination isnot supported.


User Response: Either modify the definition ofthe cursor so it is not scrollable, or ensure thatthe result table does not include output from atable function.

sqlcode: -20128

sqlstate: 428F6

SQL20131N Object number object-number oftype object-type was specified morethan once in a list of objects.

Explanation: In a list of object names of typeobject-type, the object numbered object-number wasspecified more than once. The operation of thestatement cannot be performed on the objectmore than once.

User Response: Correct the duplicated object inthe list removing duplicate occurrences. (In theMDC case, the object type will be “dimension”.)

sqlcode: -20131

sqlstate: 42713

SQL20133N Operation operation-name cannot beperformed on external routineroutine-name. The operation canonly be performed on SQLroutines.

Explanation: You attempted to performoperation operation-name on external routineroutine-name. However, you can only performthat operation on SQL routines. The operationdid not complete successfully.

User Response: Ensure the name you provideidentifies an SQL routine.

sqlcode: -20133

sqlstate: 428F7

SQL20134N The SQL Archive (SAR) file forroutine routine-name could not becreated on the server.

Explanation: The creation of the SQL archive(SAR) for routine routine-name failed because DB2could not find either the library or the bind filefor the specified routine. Bind files are onlyavailable for SQL routines created with DB2Version 7.1, FixPak 2 or later.

User Response: Recreate the procedure on aserver with DB2 Version 7.1, FixPak 2 or later,and try the operation again.

sqlcode: -20134

sqlstate: 55045

SQL20135N The specified SQL archive doesnot match the target environment.Reason code = reason-code.

Explanation: The specified SQL archive doesnot match the target environment for one of thefollowing reasons:

1 The operating system of the targetenvironment is not the same as theoperating system on which the SQLarchive was created.

2 The database type and level of thetarget environment is not the same as


the database type and level on whichthe SQL archive was created.

User Response: Ensure that the environment onwhich the SQL archive was created matches thetarget environment and reissue the command. Ifthe environments do not match, you mustmanually create the SQL routine using the targetenvironment.

sqlcode: -20135

sqlstate: 55046

SQL20136N Routine routine-name (specificname specific-name) is declaredNOT FEDERATED but the SQLstatement attempted to access afederated object.

Explanation: This SQL statement attempted toaccess one or more federated objects. Thisstatement is executed from routine routine-name(specific name specific-name) which is defined asNOT FEDERATED. It is not permitted to access afederated object from a NOT FEDERATEDroutine.

User Response: Either remove the references tofederated objects from the statement, or ALTERthe routine to define it as FEDERATED.

sqlcode: -20136

sqlstate: 55047

SQL20138N The statement may not beexplained because the routineroutine-name (specific namespecific-name) is not defined asMODIFIES SQL DATA.

Explanation: The routine routine-name (specificname specific-name) is defined as eitherCONTAINS SQL or READS SQL DATA andattempted to explain an SQL statement.Explaining an SQL statement requires writing tothe explain tables, which is only permitted in aMODIFIES SQL DATA routine.

User Response: Do not attempt to explain SQLstatements from a routine defined as eitherCONTAINS SQL or READS SQL DATA.

sqlcode: -20138

sqlstate: 42985

SQL20139N SQL statements may not be issuedin routine routine-name (specificname specific-name) because of aprevious statement failed or wasinterrupted.

Explanation: During the execution of routineroutine-name (specific name specific-name), or anested routine, either a statement failed andrequires a roll back or an interrupt occurred. It isnecessary for all routines invoked from theouter-most statement to finish executing and forcontrol to be passed back to the outer-moststatement so that the database manager mayperform the necessary recovery. Until thisrecovery has been completed, SQL statementsmay not be issued.

User Response: The routine continues toexecute. The routine should not execute anyfurther SQL statements and should return controlto the invoking statement as quickly as possible.

The recovery for the initial failure of interruptwill be automatically performed by the databasemanager once all routines have completed.

sqlcode: -20139

sqlstate: 51038

SQL20140W COMPRESS column attributeignored because VALUECOMPRESSION is deactivated forthe table.

Explanation: One of the following situationsoccurred.

1. The COMPRESS SYSTEM DEFAULT specifiedfor the column was ignored because VALUECOMPRESS is deactivated for the table.

2. DEACTIVATED VALUE COMPRESSION wasspecified and columns are defined withCOMPRESS SYSTEM DEFAULT.

User Response: To allow COMPRESS to bespecified for the column, ALTER the table andactivate VALUE COMPRESSION for the table.


sqlcode: 20140

sqlstate: 01648

SQL20142N Sequence sequence-name cannot beused as specified.

Explanation: sequence-name was referenced in acontext in which it cannot be used. sequence-nameis a sequence generated by the system for anidentity column. These sequences cannot bereferenced in a COMMENT ON SEQUENCE,DROP SEQUENCE, GRANT or REVOKEstatement, or in a NEXTVAL or PREVVALexpression.

User Response: Specify the name of auser-defined sequence object in this context.

sqlcode: -20142

sqlstate: 428FB

SQL20143N The encryption or decryptionfunction failed, because theENCRYPTION PASSWORD valueis not set.

Explanation: The ENCRYPTION PASSWORDvalue is not set.

User Response: Issue the SET ENCRYPTIONPASSWORD statement to set the ENCRYPTIONPASSWORD value. The length of the passwordmust be a minimum of 6 bytes and a maximumof 127 bytes.

sqlcode: -20143

sqlstate: 51039

SQL20144N The encryption password isinvalid because the length of thespecified password was less than6 bytes or greater than 127 bytes.

Explanation: The data must be encrypted witha password length between 6 and 127.

User Response: Ensure that the passwordlength is between 6 and 127.

sqlcode: -20144

sqlstate: 428FC

SQL20145N The decryption function failed.The password used for decryptiondoes not match the password usedto encrypt the data.

Explanation: The data must be decrypted usingthe same password that was used to encrypt thedata.

User Response: Ensure that the same passwordis used to encrypt and decrypt the data.

sqlcode: -20145

sqlstate: 428FD

SQL20146N The decryption function failed.The data is not encrypted.

Explanation: The data must be a result of theENCRYPT function.

User Response: Ensure that the data type is aresult of the ENCRYPT function.

sqlcode: -20146

sqlstate: 428FE

SQL20147N The ENCRYPT function failed.Multiple pass encryption is notsupported.

Explanation: Data that has already beenencrypted cannot be encrypted again.

User Response: Ensure that the data has notalready been encrypted.

sqlcode: -20147

sqlstate: 55048

SQL20148N Routine routine-name with specificname specific-name must have theRETURN statement as the lastSQL statement of the compoundbody.

Explanation: The RETURN statement must bethe last SQL statement of the compound body inan SQL ROW or TABLE function. No other


RETURN statement is allowed within the routinebody.

User Response: Ensure there is only oneRETURN statement and it is the last SQLstatement of the compound body.

sqlcode: -20148

sqlstate: 429BD

SQL20149W The buffer pool configuration hascompleted but will not take effectuntil the next database restart.

Explanation: The buffer pool has beensuccessfully configured, but the changes will nottake effect immediately. The changes will takeeffect when the database is restarted.

User Response: To have the changes take effectat next database restart time, no further action isrequired.

sqlcode: 20149

sqlstate: 01649

SQL20150N The number of block pages for abuffer pool is too large for thesize of the buffer pool.

Explanation: The number of block pages, asspecified by NUMBLOCKPAGES, must not begreater than 98 percent of the number of pagesfor the buffer pool, as specified by SIZE.

User Response: Either disable block-based I/Ofor this buffer pool by settingNUMBLOCKPAGES to zero or ensure the valueof NUMBLOCKPAGES is not greater than 98percent of the value for SIZE.

sqlcode: -20150

sqlstate: 54052

SQL20151N The value specified forBLOCKSIZE is not in the validrange.

Explanation: The valid range for the value ofBLOCKSIZE is 2 to 256.

User Response: Change the value forBLOCKSIZE to be greater than or equal to 2 andless than or equal to 256. An optimal valuewould be the extent size.

sqlcode: -20151

sqlstate: 54053

SQL20152N The specified buffer pool is notcurrently block-based.

Explanation: The BLOCKSIZE option was usedwithout specifying the number of pages to use inthe block area of the buffer pool.

User Response: Specify a value forNUMBLOCKPAGES along with the BLOCKSIZEoption.

sqlcode: -20152

sqlstate: 428FF

SQL20153N The database’s split image is inthe suspended state.

Explanation: The database split image cannotbe used while it is in the suspended state.

User Response: Issue the db2inidb commandwith one of the following three options toresume I/O for this database split image:

v db2inidb <db-name> as mirror

v db2inidb <db-name> as snapshot

v db2inidb <db-name> as standby

In a multi-node environment, the db2inidb toolmust be run on every node before the databasecan be used. The db2inidb tool can runconcurrently on each node of a multi-nodedatabase.

sqlcode: -20153

sqlstate: 55040


SQL20154 The requested insert operationinto view view-name is not allowedbecause no target table can bedetermined for a row. Reasoncode = reason-code.

Explanation: The specified view contains aUNION ALL query. The reason-code indicates thata given row either:

1. does not satisfy the check constraint of anyunderlying base table, or

2. satisfies all the check constraints for morethan one underlying base table.

Federated system users: Some other data sourcespecific limitation may be preventing the rowfrom being inserted.

User Response: Ensure that the checkconstraints used by the underlying base tables topartition their rowsets cover the set of rows to beinserted. For example, given the checkconstraints (T1.c1 in (1,2)) on T1, and (T2.c1 in(2,3)) on T2, and view V1 as a union of T1 andT2,

1. the row c1 = 4 does not satisfy the checkconstraints of either underlying base tableand

2. the row c1 = 2 satisfies the check constraintsof both underlying base tables.

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: -20154

sqlstate: 23513

SQL20155N The specified event monitor targettables are invalid. Reason code =reason-code.

Explanation: While processing a CREATEEVENT MONITOR statement, or while activatingan event monitor, it was determined that a target

table is not valid reason-code is one of thefollowing:

1. At least on column name does not match anevent monitor data element identifier.

2. At least one column has a data type that isincompatible with the data type for an eventmonitor data element identifier.

3. At least one column name matches an eventmonitor data element identifier, but thatelement is not allowed in the target table.

4. The row size for the table is too large for thepage size of the table space.

5. A mandatory column is missing.

User Response: Check the administrationnotification log for detailed information andcorrect the table definition.

sqlcode: -20155

sqlstate: 55049

SQL20156W The event monitor was activatedsuccessfully, however somemonitoring information may belost.

Explanation: An event monitor activatedsuccessfully, however it was determined that theevent monitor may lose some informationbecause of one of the following:

v The data type for a column is smaller than thedata type required to hold an event monitorelement identifier. This data will be truncated.

v A target table was found in theSYSCAT.EVENTTABLES, but that table doesnot exist in the database. All monitorinformation for the corresponding table willnot be recorded.

User Response: Check the administrationnotification log for detailed information. Ifnecessary, recreate the event monitor to create alltarget tables.

sqlcode: 20156

sqlstate: 01651


SQL20157N User authorization-ID does not havethe QUIESCE_CONNECTprivilege.

Explanation: The specified authorization IDdoes not have the QUIESCE_CONNECTprivilege to access a database or instance that iscurrently in a quiesced mode. TheQUIESCE_CONNECT privilege must be grantedbefore the user can connect to a quiesceddatabase or instance.

User Response: Wait for the unquiesce tocomplete or contact the system administrator ordatabase administrator for the database andrequest a GRANT QUIESCE_CONNECT for theauthorization ID. Resubmit the command.

sqlcode:-20157

sqlstate:08004

SQL20158N Function not supported for thelevel of the connected DB2 DataLinks Manager.

Explanation: The underlying DATALINKfeature is not supported for the given level of theconnected DB2 Data Links Manager.

User Response: The error can be corrected byremoving the use of any unsupportedDATALINK feature or by upgrading the DB2Data Links Manager to the same release level asthe database server.

sqlcode: -20158

sqlstate: 42997

SQL20159W The isolation clause is ignoredbecause of the statement context.

Explanation: The isolation clause is specified ona statement that is included in a compoundstatement that is processed as inline SQL. Theisolation clause is ignored and the defaultisolation level is used for all statements in thecompound statement.

User Response: No response required. Removethe isolation clause to prevent this warning.

sqlcode: 20159

sqlstate: 01652

SQL20160W The authorizations were grantedto USER userid. Groups were notconsidered because theauthorization name is more than 8bytes.

Explanation: The authorization name has alength of more than 8 bytes. The privilege isgranted to the user with authorization nameuserid without considering groups defined in thesystem that might have a matching name.Processing continues.

User Response: If the grant was intended for auser, no action is required. If the grant wasintended for a group, consider choosing analternate group because group names greaterthan 8 bytes are not supported. To avoid thiswarning message, specify the USER keywordbefore the authorization name.

sqlcode: 20160

sqlstate: 01653

SQL20161W The column name column-name isnot a valid column for an eventmonitor table.

Explanation: The column name specified in theINCLUDES or EXCLUDES clause does not matchany valid column for the event monitor table(s)being created.

User Response: Examine and correct thespecified column name.

sqlcode: -20161

sqlstate: 428AA

SQL20162N Buffer pools cannot use bothblock-based I/O and extendedstorage.

Explanation: An attempt was made to create oralter a buffer pool to use both block-based I/Oand extended storage.

User Response: Ensure that the buffer pool is


not using both block-based I/O and extendedstorage.

sqlcode: -20162

sqlstate: 428FF

SQL20167N The shared memory set is notlarge enough to process therequest.

Explanation: There is insufficient memory in ashared memory set for one of the followingresource requests:

v FCM connection entries

v FCM message anchors

v FCM request blocks

User Response: Try the request again. If theerror persists, stop and restart the instance toallow the larger shared memory set size(automatically updated by DB2) to take effectand try the request again.

sqlcode: -20167

sqlstate: 57011

SQL20168N The ALTER BUFFERPOOLstatement is currently in progress.

Explanation: A buffer pool cannot be droppedor altered if an ALTER operation is already inprogress.

User Response: Wait until the ALTER operationhas completed. Use the snapshot monitor tocheck the progress of the ongoing ALTERoperation.

sqlcode: -20168

sqlstate: 55051

SQL20169W The buffer pool is not started.

Explanation: The statement was successful, butit will only take effect when the buffer pool isstarted.

User Response: The statement has completedsuccessfully, and will take effect when thedatabase is activated. This happens after all

applications disconnect. For the statement to takeeffect immediately, re-submit it when the bufferpool is started. To start the buffer pool, it ispossible in some cases to drop and re-create thebuffer pool using the IMMEDIATE option.

sqlcode: +20169

sqlstate: 01654

SQL20170N There is not enough space in thetable space tablespace-name for thespecified action.

Explanation: Space is being removed from atablespace using one or more of the DROP,REDUCE, and RESIZE container actions.However, the amount of space being removed isgreater than the amount of space above thehigh-water mark.

User Response: Use the snapshot monitor tofind the number of useable pages in thetablespace and the tablespace high-water mark.The difference between these values is themaximum number of pages that can be removed.

sqlcode: -20170

sqlstate: 57059

SQL20173W The event monitor was createdsuccessfully but at least one eventmonitor target table already exists.

Explanation: While an event monitor was beingcreated, the database manager tried to create oneor more target tables but determined that tableswith those names already exist. The eventmonitor was successfully created and targettables were not created to replace tables of thesame name that already exist. When the eventmonitor is activated, it will attempt to use thesetables. Event monitor activation may fail ifactivation processing determines these tables arenot suitable.

User Response: Check the administrationnotification log for detailed information. Ifnecessary, drop all target tables and recreate theevent monitor to create all target tables.

sqlcode: 20173


sqlstate: 01655

SQL20178N View view-name already has anINSTEAD OF operation triggerdefined.

Explanation: The view view-name already has anINSTEAD OF trigger defined for the indicatedoperation (UPDATE, DELETE, INSERT). Onlyone INSTEAD OF trigger can be defined for eachoperation on the view.

The statement cannot be processed. TheINSTEAD OF trigger was not created.

User Response: If a new INSTEAD OF triggeris required, drop the existing trigger and thencreate the new trigger.

sqlcode: -20178

sqlstate: 428FP

SQL20179N The INSTEAD OF trigger cannotbe created because the viewview-name is defined using theWITH CHECK OPTION.

Explanation: An INSTEAD OF trigger cannot bedefined on a symmetric view (a view definedusing WITH CHECK OPTION) or a view onwhich a symmetric view has been defineddirectly or indirectly. The view view-name may bethe target view of the INSTEAD OF trigger or itmay be a view that depends directly or indirectlyon the target view of the trigger.

The statement cannot be processed. TheINSTEAD OF trigger was not created.

User Response: INSTEAD OF triggers cannotbe defined on the view unless the symmetricview is replaced by a view that is not symmetric.The view would have to be dropped andre-created to allow an INSTEAD OF trigger.

sqlcode: -20179

sqlstate: 428FQ

SQL20188N The primary key or a unique keyidentified by name is a subset ofthe columns in the ORGANIZEBY clause.

Explanation: All the columns in a primary orunique key are included in the table’sORGANIZE BY clause. This is not allowed, sinceeach block of pages in the table would containjust one row, wasting all the rest of the space inthe block.

name is the constraint name, if specified, of theprimary key or unique constraint. If a constraintname was not specified, name is the first columnname specified in the primary key or uniqueconstraint clause followed by three periods. If aunique index is being created, name is the nameof the unique index.


User Response: Modify the primary or uniquekey definition, the unique index definition or theORGANIZE BY clause, if possible, so that thekey is not a subset of the dimensions.

sqlcode: -20188

sqlstate: 429BE

SQL20189W The buffer pool operation(CREATE/ALTER) will not takeeffect until the next databasestartup due to insufficientmemory.

Explanation: The CREATE or ALTERBUFFERPOOL statement was issued andcompleted successfully, however due toinsufficient memory the create/alter was doneDEFERRED. The changes will take effect on thenext database startup.

User Response: If you do not want to wait untilthe next startup to activate or resize the bufferpool, you can free memory resources and tryagain (with the same or different size). Memoryresources that can be reduced include otherbuffer pools, the database heap, the catalogcache, the package cache, and the utility heap.These can be reduced using the ALTER/DROPBUFFERPOOL or UPDATE DATABASE


CONFIGURATION command depending on theresource. In the future, to reserve extra memoryfor the dynamic allocation of buffer poolmemory, you can increase theDATABASE_MEMORY database configurationparameter.

If you do not try again:

1. If it is an ALTER BUFFERPOOL that failed,you will continue to run with the currentruntime size of the buffer pool. You can usethe database monitor to see the currentruntime size of the buffer pool.

2. If it is a CREATE BUFFERPOOL that failed,any table spaces that are created in the bufferpool will temporarily (until next startup) beput in a hidden buffer pool with thematching pagesize. Since the hidden bufferpools are small, this can result in lower thandesired performance.

To try again:

1. For ALTER BUFFERPOOL, resubmit thecommand.

2. For CREATE BUFFERPOOL drop the bufferpool and then resubmit the command.

sqlcode: 20189

sqlstate: 01657

SQL20190N Federated insert, update, or deleteoperation cannot be compiledbecause of potential datainconsistency.

Explanation: When the data source does notprovide application savepoint support and theserver option ’iud_app_svpt_enforce’ is set to ’Y’,the federated insert, update, or delete operationis blocked during precompile. This will preventpotential data inconsistency, which may occur atruntime execution if an error is encountered inthe middle of federated insert, update, or deleteprocessing.


v Change server option ’iud_app_svpt_enforce’to ’N’.

v Apply the insert, update, or delete directly onthe data source.

sqlcode: -20190

sqlstate: 0A503

SQL20191N For an INOUT parameter in adynamically prepared CALLstatement, the same host variablemust be used in both the USINGand INTO clauses.

Explanation: In a CALL statement, an INOUTparameter must correspond to a single hostvariable. When executing a dynamically preparedCALL statement, it is necessary to specify thesame host variable in both the USING and INTOclauses of the EXECUTE statement.

User Response: When specifying a host variablethat corresponds to a parameter marker for anINOUT parameter, use the same host variable inboth the USING and INTO clauses of theEXECUTE statement. When using SQLDAs tospecify a host variable that corresponds to aparameter marker for an INOUT parameter, thenthe SQLDATA pointers of the correspondingSQLVARs must point to the same host variable.

sqlcode: -20191

sqlstate: 560BB

SQL20192N The specified modes are onlysupported in a partitioneddatabase environment.

Explanation: Either RECOMMENDPARTITIONINGS or EVALUATEPARTITIONINGS was not invoked in apartitioned database environment. These twomodes are only supported in a partitioneddatabase environment.

User Response: Invoke RECOMMENDPARTITIONINGS or EVALUATEPARTITIONINGS in a partitioned databaseenvironment.

sqlcode: -20192

sqlstate: 56038


SQL20193N An error has occurred whenaccessing the file file-name. Reasoncode: reason-code.

Explanation: If the file name is db2nodes.cfg,some possible reason codes include:

1. Indicates that the db2nodes.cfg file containsformat errors.

2. The command could not be completedbecause of communication errors.

3. The command could not be completedbecause of memory allocation errors.

User Response: Fix any format errors in thedb2nodes.cfg file. Check the db2diag.log file formore information to help resolve thecommunication or memory allocation errors.Rerun the application.

sqlcode: -20193

sqlstate: 560BC

SQL20194N Buffer pool bufferpool-name doesnot exist on database partitiondbpartitionnum.

Explanation: The ALTER BUFFERPOOLstatement is specifying a buffer pool,bufferpool-name, that does not exist on thedatabase partition dbpartitionnum.

User Response: Using the ALTER DATABASEPARTITION GROUP statement, add the databasepartition dbpartitionnum to a database partitiongroup that has the buffer pool bufferpool-namealready defined for it. If the buffer pool is notassociated with any specific database partitiongroup, then add the database partition to anydatabase partition group or create a newdatabase partition group for this databasepartition. Issue the ALTER BUFFERPOOLstatement again.

sqlcode: -20194

sqlstate: 53040

SQL20195N An error was encountered whileprocessing line numberline-number in the path renameconfiguration file config-file.Reason code = reason-code.

Explanation: The path rename configuration fileconfig-file is being used to rename containersduring the current crash or rollforward recoveryprocess. However, while processing thestatements in this file, an error was encounteredat line line-number that is preventing the recoveryprocess from proceeding. An explanation of theerror is indicated by the following reason code:

1. Invalid syntax.

2. The length of the container path exceeds themaximum allowed length for a containerpath.

3. The container path specified has already beenlisted on a previous line.

4. The length of the database path exceeds themaximum allowed length for a database path.

5. The database path specified has already beenlisted on a previous line.

6. The database path must be an absolute path.

7. The database path is specified incorrectly.

User Response: Make the corresponding changeto the configuration file as described below andreissue the command again.

1. Correct the syntax error.

2. Specify a shorter container path.

3. Remove the duplicate container path from thefile.

4. Specify a shorter database path.

5. Remove the duplicate database path from thefile.

6. Use an absolute database path instead of arelative one.

7. Specify the database path in the form of adrive letter followed by a colon (for exampleC:).

sqlcode: -20195

sqlstate: 08504


SQL20196N The one or more built-in typeswhich are returned from theFROM SQL function or methoddoes not match the correspondingbuilt-in types which areparameters of the TO SQLfunction or method.

Explanation: The built-in types which arereturned by a FROM SQL transform function ormethod have to match the types in the parameterlist of the corresponding TO SQL transformfunction or method.

User Response: Choose a different FROM SQLtransform function or method or TO SQLtransform function or method or alter either theFROM SQL transform function or method or TOSQL transform function or method to make surethat each built-in type returned from the FROMSQL function or method matches thecorresponding built-in type that is a parameter ofthe TO SQL transform function or method.

sqlcode: -20196

sqlstate: 428FU

SQL20197N Cannot define method-name as anoverriding method. Reason codereason-code.

Explanation: An attempt was made to definemethod-name as an overriding method. Anoverriding relationship between this method andan original method cannot be created because ofone of the following reasons, as specified byreason-code:

1 Cannot find an original method with thesame name.

2 The original method and the overridingmethod do not have the same numberof parameters.

3 The data type of the parameter of theoverriding method does not match thedata type of the correspondingparameter of the original method.

4 The parameter name of the parameter ofthe overriding method does not match

the parameter name of thecorresponding parameter of the originalmethod.

5 The locator indication of the parameterof the overriding method does notmatch the locator indication of thecorresponding parameter of the originalmethod.

6 The FOR BIT DATA indication of theparameter of the overriding methoddoes not match the FOR BIT DATAindication of the correspondingparameter of the original method.

7 The RETURNS clause of the overridingmethod contains as AS LOCATORclause, a CAST FROM clause or a FORBIT DATA clause.

8 One of the following inherited methodattributes is specified: SELF AS RESULT,SQL routine characteristics, or externalroutine characteristics.

9 Return type of the overriding methoddoes not match the return type of theoriginal method.

10 The return type of the overridingmethod is a structured type that is not asubtype of either:

v the return type of the original methodor

v every return type for all methods thatalready override the original method.

User Response: Modify the method definitionbased on the reason specified by the reason-codeas follows:

1 Use a method name that identifies anexisting method for the supertype of thestructured type.

2 Define the same number of parametersfor the overriding method as exists forthe original method.

3 Change the data type to match the datatype of the corresponding parameter ofthe original method.

4 Change the parameter name to match


the name of the correspondingparameter of the original method.

5 Change the locator indication to matchthe locator indication of thecorresponding parameter of the originalmethod.

6 Change the FOR BIT DATA indication tomatch the FOR BIT DATA indication ofthe corresponding parameter of theoriginal method.

7 Remove the AS LOCATOR clause, CASTFROM clause and FOR BIT DATA clausefor the overriding method.

8 Remove the SELF AS RESULT methodattribute and any SQL routinecharacteristic or external routinecharacteristic.

9 Change the return type to match thereturn type of the original method.

10 Change the return type so that it is asubtype of the original method and allmethods that already override theoriginal method.

sqlcode: -20197

sqlstate: 428FV

SQL20198N Method method-name calls itselfrecursively.

Explanation: A method attempted to call itselfrecursively. The recursion might be direct orindirect in nature.

User Response: Modify the method definition.

sqlcode: -20198

sqlstate: 55054

SQL20200 - SQL20299

SQL20200N The install or replace of jar-idfailed as url could not be located.

Explanation: The URL specified on the install orreplace jar procedure did not identify a valid jarfile.

User Response: Reissue the install or replace jarprocedure with a URL that identifies a valid jarfile.

sqlcode: -20200

sqlstate: 46001

SQL20201N The install, replace or remove ofjar-id failed as the jar name isinvalid.

Explanation: The jar name specified on theinstall, replace or remove jar procedure wasinvalid. For example, the jar id may be of theimproper format, may not exist to be replaced orremoved, or can not be installed as it alreadyexists.

User Response: Ensure the jar id is of the

correct format. If the jar id exists, it may need tobe removed before it can be installed. For theremove or replace procedures, ensure the jar idexists.

sqlcode: -20201

sqlstate: 46002

SQL20202N The replace or remove of jar-idfailed as class is in use.

Explanation: The specified class in the jar file iscurrently in use by a defined procedure, or thereplacement jar file does not contain the specifiedclass for which a procedure is defined.

User Response: Ensure all proceduresreferencing the classes being removed aredropped and resubmit the replace or removeprocedure.

sqlcode: -20202

sqlstate: 46003


SQL20203N User defined function orprocedure function-name has a Javamethod with an invalid signature.

Explanation: The signature of the java methodused to implement the function or procedure wasinvalid. For example, the method may haveparameters that are not mappable to theparameters on the corresponding createstatement or the method for a procedure mayspecify a return value.

User Response: Reissue the correspondingCREATE statement specifying parameters thatmatch the Java method, or correct the parametersor return type of the Java method and rebuildthe class.

sqlcode: -20203

sqlstate: 46007

SQL20204N The user defined function orprocedure function-name wasunable to map to a single Javamethod.

Explanation: The identified function orprocedure either failed to find a matching Javamethod, or found more than 1 matching Javamethod.

User Response: Correct either the Java methodor corresponding create statement so that thefunction or procedure call resolves to a singleJava method.

sqlcode: -20204

sqlstate: 46008

SQL20205N The user defined function orprocedure function-name has aninput argument with a null valuethat could not be passed to themethod.

Explanation: A function created with ″CALLEDON NULL INPUT″ or procedure has an inputparameter with a null value but the Javadatatype of this argument does not support nullvalues. Examples of Java datatypes that do notsupport null values are BOOLEAN, BYTE,

SHORT, INT, LONG or DOUBLE.

User Response: If the method is to be calledwith null values, ensure the input Java types arecapable of accepting a null value. For functions,the function could also be created with″RETURNS NULL ON NULL INPUT″.

sqlcode: -20205

sqlstate: 39004

SQL20206W The procedure function-namereturned too many result sets.

Explanation: The specified procedure returnedmore results sets than were specified on theCREATE PROCEDURE statement.

User Response: Modify the procedure to returnfewer result sets, or drop and recreate theprocedure specifying the correct number of resultsets.

sqlcode: +20206

sqlstate: 0100E

SQL20207N The install or remove jarprocedure for jar-id specified theuse of a deployment descriptor.

Explanation: The DEPLOY or UNDEPLOYparameter of the install or replace jar procedurewas non-zero; this parameter is not supportedand must be zero.

User Response: Reissue the procedure with theDEPLOY or UNDEPLOY parameter set to zero.

sqlcode: -20207

sqlstate: 46501

SQL20208N Table table-name cannot be created.Reason code = reason-code

Explanation: The table cannot be createdbecause it violates a restriction as indicated bythe following reason code:

1. The table used to define a staging table is nota materialized query table with the REFRESHDEFERRED option.


2. The table used to define the staging tablealready has a staging table associated with it.



1. Specify a materialized query table with theREFRESHED DEFERRED option to define thestaging table.

2. Specify a materialized query table that is notassociated with a staging table.

sqlcode:-20208

sqlstate:428FG

SQL20209N The option-type option is not validfor table table-name with reasoncode reason-code

Explanation: The specified option is not valid asindicated by the following reason codes:

1. The READ ACCESS option cannot bespecified on a table that is in the checkpending no access state.

2. The FULL ACCESS option is not valid if thetable still has integrity types that are notchecked.

3. The FULL ACCESS option is not valid on atable that is not in the no data movementmode.

4. The FULL ACCESS option cannot be specifiedwith the IMMEDIATE UNCHECKED clauseif the table is in the no data movement mode.

5. The PRUNE option is not valid on a tablethat is not a staging table.

6. The PRUNE and INCREMENTAL optionscannot be specified simultaneously.

User Response:

1. Do not specify the READ ACCESS option.

2. Use the FULL ACCESS option with the SETINTEGRITY ... IMMEDIATE CHECKEDstatement, or specify ALL as the integrityoption for the SET INTEGRITY ...IMMEDIATE UNCHECKED statement.

3. Use the FULL ACCESS option with theIMMEDIATE CHECKED option.

4. Use the FULL ACCESS option without theIMMEDIATE UNCHECKED clause.

5. Remove the table that is not a staging tablefrom the statement.

6. Specify only one of PRUNE orINCREMENTAL.

sqlcode:-20209;

sqlstate:428FH;

SQL20210N ORDER OF table-designator wasspecified. But thistable-designator does not containan ORDER BY clause.

Explanation: It was specified to order based onthe order of table-designator but table-designator isnot ordered since it does not contain an ORDERBY clause.

User Response: Add an ORDER BY clause tothe specification of table-designator or use asort-key specification instead of ORDER BY.

sqlcode: -20210

sqlstate: 428FI

SQL20211N The specification ORDER BY orFETCH FIRST n ROWS ONLY isinvalid.

Explanation: An ORDER BY or FETCH FIRST nROWS ONLY is not allowed in:

v the outer fullselect of a view

v the outer fullselect in the RETURN statementof an SQL Table function

v a materialized query table definition

v a subselect which is not enclosed inparenthesis

User Response: In case of:

subselectEnclose the subselect including theORDER BY or FETCH FIRST n ROWSONLY in parenthesis.


FETCH FIRST n ROWS ONLYUse the ROW_NUMBER() OVER()clause in conjunction with a predicate inthe where clause. Example:

SELECT name FROM(SELECT

ROW_NUMBER() OVER() AS m, nameFROM emp

) AS eWHERE m < 10

ORDER BYUse ORDER BY in the query using theview, the materialized query table, orthe SQL table function instead.

sqlcode: -20211

sqlstate: 428FJ

SQL20212N User defined routine function-nameencountered an exceptionattempting to load Java classclass-name from JAR JAR-name.Original exceptionunderlying-exception.

Explanation: A ClassNotFoundException hasoccurred. The ClassNotFoundException mayreference an original Java exception whichfurther describes why the class wasn’t found. Forexample, the underlying exception might be anI/O error that occurred trying to read a JAR file,or an SQL error occurred reading the JAR fromthe data dictionary. As much of the followingtokens that will fit within the SQLCA limits willbe returned, as appropriate.

The function-name identifies the specific name ofthe external Java function or procedure whoseexecution encountered theClassNotFoundException.

The class-name identifies the Java class whosedefinition could not be found.

The JAR-name optionally identifies the installedJAR expected to contain the identified class.’(none)’ will be present unless the external Javafunction or procedure is defined to be in aninstalled JAR.

The underlying-exception optionally contains thetoString() of the underlying exception thatresulted in this ClassNotFoundException, if any.’(none)’ will be present if there is no underlyingexception.

User Response: Execute an ALTERPROCEDURE to specify where the class is to befound, make sure the class is in the specified JARor the system classpath, or correction thecondition reported by the underlying-exception.

sqlcode: -20212

sqlstate: 46103

SQL20214N ORDER OF table-designator wasspecified but this table designatoris not ordered.

Explanation: The ORDER OF clause specifiesordering of the result table based on the orderoftable-designaotr, which is not ordered. There isno ORDER BY clause on the query associatedwith table-designator, or the sort key of theORDER BY clause is a constant expression.

User Response: Add a valid ORDER BY clauseto the query associated with table-designator, oruse a sort-key specification instead of using theORDER OF clause.

sqlcode: -20214

sqlstate: 428FI

SQL20223N The ENCRYPT or DECRYPTfunction failed. Encryption facilitynot available.

Explanation: The encryption facility is notavailable to service the encryption or decryptionrequest.

User Response: If the encryption facility is notinstalled, then install it before using theENCRYPT or DECRYPT functions. If theencryption facility is installed, then verify that itis working correctly.

sqlcode: -20223

sqlstate: 560BF


SQL20225W The buffer pool operation (DROP)will not take effect until the nextdatabase startup because thebuffer pool is in use.

Explanation: The DROP BUFFERPOOLstatement was issued and completed successfully,however a table space is still using this bufferpool. Even though a table space may bereassigned to a different buffer pool, the tablespace reassignment may only take effect on thenext database restart. If the table space inquestion is dropped by the time this operation

commits, then this buffer pool will be removedfrom memory at that time. Until the nextdatabase restart, this buffer pool may remain inmemory and a CREATE or ALTER of any otherbuffer pool that would reuse this buffer pool IDmay be deferred.

User Response: Restart the database to deletethe buffer pool from memory.

sqlcode: 20225

sqlstate: 01657

SQL22000 - SQL22099

SQL22000W Cannot find the requestedconfiguration for objectobject-name. Returning defaultconfiguration for object-type.

Explanation: The object does not have a specificconfiguration of its own so the defaultconfiguration for that object type will bereturned.

User Response: If the behavior of the defaultconfiguration is correct, no action has to betaken.

SQL22001W Cannot find the defaultconfiguration for objectobject-name. Returning installconfiguration for object-type.

Explanation: The object does not have a specificconfiguration of its own so the installconfiguration for that object type will bereturned.

User Response: If the behavior of the installconfiguration is correct, no action has to betaken.

SQL22004W Cannot find the requestedconfiguration for the given object.Returning default configurationfor object-name.

Explanation: The object does not have a specificconfiguration of its own so the default

configuration for that object type will bereturned.

User Response: If the behavior of the defaultconfiguration is correct, no action has to betaken.

SQL22005W Cannot find the defaultconfiguration for the given object,returning install configuration forobject-name.

Explanation: The object does not have a specificconfiguration of its own so the installconfiguration for that object type will bereturned.

User Response: If the behavior of the installconfiguration is correct, no action has to betaken.

SQL22006N Cannot update or deleteobject-action-or-contact-name becauseit does not exist.

Explanation: The API was requested to updatethe configuration of an element which does notexist.

User Response: Create the element and thenre-issue the API call.


SQL22007N The specified Health Indicatoridentifier or name,Health-Indicator-name, is invalid.

Explanation: The requested action can only beperformed against a valid Health Indicator. Thesupplied Health Indicator does not exist.

User Response: Determine the correct theidentifier or name, and resubmit the request.

SQL22008N The value parameter-value ofparameter parameter-name is not ofthe correct format, type, or value.

Explanation: The requested action can not betaken because the supplied value for thisparameter is not of an acceptable format, type, orvalue.

User Response: Determine the correct formatand type of, or value for, this parameter, andresubmit the request.

SQL22009W There is no health contactinformation for this instance.

Explanation: There is no health contactinformation for this instance.

User Response: If the current contactinformation is correct, no action has to be taken.

SQL22010N The value parameter-value ofparameter parameter-name is notwithin the acceptable range ofvalues for this parameter, which isgreater than parameter-max-valueand/or less thanparameter-min-value.

Explanation: The requested action can not betaken because the supplied value for thisparameter is not within the acceptable range ofvalues.

User Response: Resubmit the request with anacceptable value for this parameter.

SQL22011W Cannot find the configuration forobject-name-or-type.

Explanation: The object or object type does nothave a specific or default configuration of itsown.


SQL22012W Implicit instance attach failed.

Explanation: An explicit instance attachmentdoes not exist and an implicit attachment to thedefault instance failed. The command cannot beexecuted.

User Response: Make sure that DB2 is startedand that environment variables are set properly.

SQL22013N Cannot add obj-act-contact becauseit already exists.

Explanation: The API was requested to add anaction or notification which already exists.

User Response: Modify or delete the existingactions and notifications.

SQL22014W The health monitor returned nohealth related data.

Explanation: There is no health data for thisinstance or the health monitor is off.

User Response: Verify that the health monitor isrunning on this instance.

SQL22015N The specified Health Indicatoridentifier or name,Health-Indicator-name, is invalid forthis object type.

Explanation: The supplied Health Indicatordoes not exist for this object type.

User Response: Verify the object type andidentifier or name, and resubmit the request.

SQL22200 - SQL22299


SQL22200N The DB2 Administration Servercannot be stopped.

Explanation: The DB2 Administration Servercannot be stopped because it is currentlyhandling at least one request from a client.

User Response: Issue the DB2ADMIN STOPcommand with the /FORCE option to cancel allcurrent requests being handled by the DB2Administration Server and force the DB2Administration Server to stop.

SQL22201N The DB2 Administration Serverfailed to authenticate the userauthorization-ID on the hosthostname. Reason code reason-code.

Explanation: The DB2 Administration Serverwas unable to authenticate the userauthorization-ID for the following reason:

1. Invalid user ID or password.

2. Password expired.

3. User account is disabled.

4. User account is restricted.

5. The DB2 Administration Server is unable toprocess requests submitted as the root user.

6. Authorization failed.

User Response: Depending on the reason code,try the following:

1. Verify that a valid user ID and passwordwere specified for the host hostname.

2. Change the password on host hostname foruser authorization-ID. Contact your systemadministrator for assistance. Attempt therequest again once the password has beenchanged.

3. Contact your system administrator to unlockthe account.

4. Contact your system administrator to find outthe restrictions placed on the account.

5. Resubmit the request as a user other thanroot.

6. An internal authentication error has occurred.

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

SQL22202W The DB2 Administration Servercannot be quiesced. Reason codereason-code.

Explanation: The DB2 Administration Serverquiesce operation failed for one of the followingreasons:

1. The DB2 Administration Server is alreadyquiesced.

2. The DB2 Administration Server is currentlyprocessing requests on behalf of DB2 clients.

User Response: Depending on the reason forthe failure, attempt one of the following:


2. Wait until the DB2 Administration Server isnot processing any requests, or resubmit thequiesce request and specify the force option.Forcing a quiesce will terminate any requeststhat are currently being processed.

SQL22203W The DB2 Administration Servercannot be unquiesced. Reasoncode reason-code.

Explanation: The DB2 Administration Serverunquiesce operation failed for one of thefollowing reasons:

1. The DB2 Administration Server is notquiesced.

2. There is at least one administration request inprogress.



2. Wait until the DB2 Administration Server hascompleted processing all administrationrequests, or resubmit the unquiesce requestand specify the force option. Forcing theunquiesce operation will allow normalrequests to be handled concurrently with theadministration requests, which may preventthe administration requests from completingsuccessfully.


SQL22204N The DB2 Administration Serverencountered a non-severe errorwhile executing a request.

Explanation: A non-severe error occurred in theDB2 Administration Server while it wasprocessing a request.

User Response: Refer to the DB2Administration Server’s First Failure DataCapture Log for additional information.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Contact DB2 Customer Support with thefollowing required information:





SQL22205C The DB2 Administration Serverencountered an unexpected errorwhile executing a request.

Explanation: An unexpected error occurred inthe DB2 Administration Server while it wasprocessing a request.

User Response: Refer to the DB2Administration Server’s First Failure DataCapture Log for additional information.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt. Contact DB2 Customer Support with thefollowing required information:





SQL22206N An error occurred while accessinga message queue. Reason codereason-code.

Explanation: An unexpected error or badmessage was received on a message queue. Thefollowing is a list of reason codes:

1. Unable to create a message queue. Thenumber of message queues allowed mayhave been exceeded.

2. An error was encountered while reading froma message queue.

3. An error was encountered while writing to amessage queue.

4. An invalid message was received from amessage queue.

5. An error was encountered while opening amessage queue.

6. An error was encountered while closing amessage queue.

7. An error was encountered while querying amessage queue.

8. An error was encountered while deleting amessage queue.

User Response: Ensure the number of messagequeues allowed is not reached. Reduce thenumber of message queues in use if necessaryand resubmit the request.

If you continue to receive this error messageafter attempting the suggested solutions, pleasecontact DB2 Customer Support.

SQL22207N The DB2 Administration servercannot execute the script at hosthostname. Reason code reason-code.

Explanation: The DB2 Administration Serverfailed to execute the script for one of thefollowing reasons:

1. The user specified an existing script and thescript does not exist.

2. The script working directory is invalid.

3. The last line of the script failed to runbecause a statement termination charactercould not be found.

4. A system error occurred while attempting toexecute the script.


1. Verify that the script specified exists on hosthostname at the path provided.


2. Verify that the working directory is valid onhost hostname.

3. Verify the script contents and resubmit therequest.

4. Refer to the DB2 Administration Server’s FirstFailure Data Capture Log for additionalinformation.

If you continue to receive this error messageafter attempting the suggested response, refer tothe DB2 Administration Server’s First FailureData Capture Log for additional information orcontact IBM Customer Support.

SQL22208N The DB2 Administration Serverfailed to execute function/methodfunction-name in library/classlibrary-name at host hostname.Reason code reason-code.

Explanation: The DB2 Administration serverencountered an error while trying to execute afunction/method in a library/class for one of thefollowing reasons:

1. The library/class library-name could not befound.

2. The function/method function-name could notbe found in the library/class library-name.

3. The version of the function/method invokedat the DB2 Administration Server is notsupported.


1. Verify that the library library-name exists onhost hostname.

2. Refer to the DB2 Administration Server’s FirstFailure Data Capture Log for additionalinformation. If trace was active, invoke theIndependent Trace Facility at the operatingsystem command prompt. Contact DB2Customer Support with the followingrequired information:





3. See response for reason code 2.

SQL22209N The DB2 Administration Serverencountered an unexpected Javaerror on host hostname.

Explanation: An error occurred while the DB2Administration Server was attempting to start orcommunicate with a Java Interpreter. Thefollowing could be the cause of the problem:

1. Java has been improperly installed orconfigured on host hostname.

2. The DB2 Administration Server jdk_pathconfiguration parameter has been setincorrectly.

User Response: Attempt the following:

1. Contact the system administrator for hosthostname to verify that Java is properlyinstalled and configured.

2. Verify that the DB2 Administration Serverjdk_path configuration parameter has beenset correctly. The jdk_path configurationparameter can be viewed using CLP. Theparameter should point to the location whereJava is installed on the host hostname.

If you continue to receive this error messageafter attempting the suggested response, pleasecontact DB2 Customer Support.

SQL22210N The DB2 Administration servercannot execute the specifiedrequest while quiesced.

Explanation: The DB2 Administration Serverfailed to execute the request because the DB2Administration Server is currently quiesced. Onlyadministrative requests can be executed whilethe DB2 Administration Server is quiesced.

User Response: Try the request again when theDB2 Administration Server is no longer quiesced.Contact your database administrator todetermine when the DB2 Administration Serverwill be unquiesced.


SQL22211N An error occurred setting the DB2Administration Serverconfiguration parameterparameter-token. Reason codereason-code.

Explanation: The DB2 Administration Serverconfiguration was not updated due to thefollowing error:

1. Configuration parameter is unknown.

2. Configuration parameter value is not in thecorrect range.

3. A system error occurred while updating theDB2 Administration Server configurationparameters.

User Response: Depending on the reason code,verify the following:

1. The configuration parameter exists.

2. The value specified for the configurationparameter is in the correct range. See thedescription of the configuration parameter inthe DB2 Administration Guide: Performancevolume for the range of allowable values.

3. Refer to the DB2 Administration Server’s FirstFailure Data Capture Log for additionalinformation or contact IBM CustomerSupport.

SQL22212N A DB2 Administration Servercommunication error has beendetected. Client system:client-ip-address. Server system:server-ip-address.

Explanation: A DB2 Administration Servercommunication error has been detected. Possiblecauses include the following:

1. The DB2 Administration Server at the serversystem was shut down by the systemadministrator.

2. The DB2 Administration Server at the serversystem was terminated due to an internal orsystem error.

3. The DB2 Administration Server is notinstalled at the server system.

4. The DB2 Administration Server has not beencataloged correctly at the client system.

5. The communication subsystem at the clientsystem or server system has not beenconfigured correctly, or has not been startedsuccessfully.

6. A network error has caused the connection togo down.

7. An internal error in the DB2 AdministrationServer caused the connection to go down.

User Response: Verify the following:

1. The DB2 Administration Server has not beenshut down.

2. The DB2 Administration Server has not beenterminated.

3. The DB2 Administration Server has beeninstalled at the server system.

4. The remote DB2 Administration Server iscataloged properly on the client system.

5. The communication subsystems on bothclient and server systems are configured andstarted up properly.

6. The network is operating properly.

7. Nothing to verify.

If the problem persists, consult with yournetwork administrator or contact IBM CustomerSupport.

SQL22213N DB2ADMIN processing wassuccessful. The scheduler was notstarted successfully.

Explanation: The DB2ADMIN commandsuccessfully started the DB2 AdministrationServer, but the DB2 Administration Server wasunable to start the scheduler.


v Ensure the Tools Catalog Databaseconfiguration in the DB2 AdministrationServer configuration parameters is correct. Forinstructions on configuring the Tools CatalogDatabase, refer to the section on the DB2Administration Server in the DB2Administration Guide.

v Ensure the database manager containing theTools Catalog Database has been started.


v If the Tools Catalog Database is remote to theTools Catalog Instance, ensure the scheduleruser ID and password are set correctly. Thescheduler user ID must have SYSADMauthority on the Tools Catalog Database. Youcan change the scheduler user ID andpassword using the DB2ADMIN SETSCHEDIDcommand.

v Ensure the Tools Catalog Database is not beingused by another scheduler.

After verifying the above, try stopping and thenrestarting the DB2 Administration Server. If youcontinue to receive this error message afterattempting the suggested response, pleasecontact DB2 Customer Support.

SQL22214N The admin node node-name doesnot exist in the DB2 nodedirectory.

Explanation: The admin node node-name isinvalid. The node name does not exist in the DB2node directory.

User Response: Verify that the node namenode-name is cataloged in the admin nodedirectory using the LIST ADMIN NODEDIRECTORY command. If the admin node is notlisted in the admin node directory, submit aCATALOG ADMIN ... NODE command tocatalog the admin node. If you continue toreceive this error message after attempting thesuggested response, please contact DB2Customer Support.

SQL22215W The DB2 Administration Serverconfiguration parameters wereupdated successfully.

Explanation: The configuration parameters wereupdated successfully, however, you must restartthe DB2 Administration Server to have thechanges become effective.

User Response: Restart the DB2 AdministrationServer to have the changes become effective.

SQL22216N An error occurred whileperforming an extended consoleoperation. Reason code =reason-code.

Explanation: While performing the operation,an unexpected error occurred. The possiblereason codes are as follows:

1 The console name used to active theconsole has more than 8 characters.

2 The operator command that was issuedis longer than the allowed 126characters.

3 For an activate request, the issuer doesnot have read authority to resourcename, MVS.MCSOPER.*, where * is thename of the console.

4 For an activate request, the console wasalready active.


1 Check if the user name supplied as theconsole name has more than 8characters.

2 Check if the operator command is morethan 126 characters in length.

3 Provide the required read authority tothe resource MVS.MCSOPER.*, where *is the name of the console.

4 Ensure that the extended console youwant to activate is not active.

SQL22220N The DB2 Administration Serverencountered a script error. Scripterror code error-code.

Explanation: A script error was encounteredwhile the DB2 Administration server wasexecuting the script. The script exited with errorcode error-code.

User Response: Verify that the script is correct.

If you continue to receive this error messageafter attempting the suggested response, refer tothe DB2 Administration Server’s First Failure


Data Capture Log for additional information orcontact IBM Customer Support.

SQL22221N The scheduler is not active.Reason code reason-code.

Explanation: The scheduler was unable tohandle the request because the scheduler is notactive for one of the following reasons:

1. The scheduler is not enabled.

2. The scheduler is not configured properly.

User Response: Check the following:

1. Verify that the scheduler has been enabled.The scheduler is enabled using theSCHED_ENABLE DB2 Administration Serverconfiguration parameter. Verify the currentsetting of the SCHED_ENABLE parameter byviewing the DB2 Administration Serverconfiguration parameters using the GETADMIN CONFIGURATION command. Tomodify the value of any configurationparameter, use the UPDATE ADMINCONFIGURATION command.

2. Verify that the scheduler is properlyconfigured. To configure the scheduler, referto the section on the DB2 administrationserver in the DB2 Administration Guide.


SQL22222N The logon user account for theScheduler is invalid.

Explanation: The scheduler requires a validlogon account to connect to the tools catalogdatabase if the tools catalog database is remote tothe DB2 Administration Server. This error iscaused by the account not being setup, or thelogon user account does not contain a valid DB2user ID.

User Response: If a logon user account hasbeen set up, then ensure that the account uses avalid DB2 user ID. You can set up the logon user

account for the Scheduler by using the followingcommand:

DB2ADMIN SETSCHEDID <userid> <password>

SQL22223N The instance instance-name doesnot exist on host hostname.

Explanation: The DB2 Administration Server onhost hostname failed to execute a request becausethe instance instance-name provided in the requestdoes not exist on the host.


v The remote instance field of the node entry inthe local node directory corresponding to theinstance instance-name is correct.

v The instance instance-name exists on hosthostname.


SQL22230N The data set dataset could not belocated on the system.

Explanation: One of the following reasons mayapply:

1. The data set has not been cataloged.

2. The volume on which the data set is locatedis not mounted.

3. The data set does not exist on the volumespecified in the catalog.

4. A data set or PDS/E member name requiredfor this operation was not specified.

5. The data set or PDS/E member namecontains invalid characters or is longer thanthe maximum length allowed by the system.

For more information on the first three of thesereasons refer to the MVS system messagesIGW01021T, IGW01508T and IGW01511E.

User Response: Ensure that the name of thedata set is entered correctly, that the data set hasbeen cataloged and that the volume on which itis located is mounted on the system.


SQL22231N The requested operation is notsupported for the data set dataset.

Explanation: Certain properties of the specifieddata set prevent it from being used inconjunction with the requested operation, whichmay include an inapplicable record format ordata set type. For example, a member namecannot be specified for a PS data set.

User Response: Ensure that the data set hasproperties that are appropriate for the selectedoperation. Refer to the DB2 AdministrationServer’s (DAS) First Failure Data Capture Log foradditional information.

SQL22232N The job ID jobid was not found onthe Job Entry Subsystem (JES).

Explanation: Possible reasons include:

1. The job with the specified job ID has notbeen submitted to the JES.

2. The job with the specified job ID has beenpurged from the JES.

User Response: Ensure that the job ID belongsto a job that has been submitted to the JES andthat has not been purged yet.

SQL22236N A file I/O error occurred. Reasoncode = reason-code.

Explanation: An error occurred while accessingthe file system. The reasons codes are as follows:

1. An invalid directory was specified.

2. An attempt was made to open a non-existentfile.

3. An attempt was made to create an existingfile.


1. Specify a valid directory.

2. Specify a file that exists.

3. Specify a file that does not already exist.

SQL22245N JCL generation failed. Reason(code[, token]) = reason-code.

Explanation: JCL generation failed as indicatedby the following reason code:

01 A card with the reserved JCL skeletonparameter &JOB is not found or ismisplaced in the main JCL skeleton.This card should be the firstnon-comment card in the main JCLskeleton after the TEMPLATE card.

02 Incorrect use of a reserved JCL skeletonparameter. The token in this messagecontains the name of the parameter thatcaused the problem.

03 There are more occurrences of thereserved JCL skeleton parameter&CTLSTMT in the main JCL skeletonthan expected. The token in thismessage is set to the expected numberof the &CTLSTMT parameters.

04 There are more occurrences of thereserved JCL skeleton parameter&STEPLIB in the main JCL skeletonthan expected. The token in thismessage is set to the expected numberof the &STEPLIB parameters.

05 The main JCL skeleton does not beginwith the TEMPLATE statement. Thisstatement should be the firstnon-comment statement in the main JCLskeleton.

06 The jobname or stepname in the JCLskeleton does not contain the JCLskeleton built-in function &SEQrequired for job or step sequencing. TheJCL skeleton built-in function &SEQshould be specified in the jobname orstepname of the JCL skeleton. The tokenin this message contains a fragment ofthe incorrect JCL statement.

07 The keyword JOB is not found in thefirst non-comment statement in the JCLskeleton for //JOB-statement. It might


be commented out, mistyped, or misseddelimiting spaces, especially after thekeyword.

08 The main JCL skeleton is incomplete orhas incorrect structure. The requiredstandard JCL statements may becommented out, missed or misplaced,especially if in-stream JCL proceduresare being used in this JCL skeleton.

09 The syntax of jobname, stepname, orddname in the JCL skeleton is invalid.Possible reasons for this: incorrectlength of the name field, or the fieldincludes some non-alphanumericalcharacters. The token in this messagecontains a fragment of the incorrect JCLstatement.

10 An incorrect use of ampersand in theJCL skeleton. The JCL skeleton containsone or more stand-alone ampersandcharacters. An ampersand is the firstsymbol of any JCL skeleton parameterand should not be used without anaccompanying identifier. The token inthis message contains a fragment of theincorrect JCL statement.

11 The reserved JCL skeleton parameter&OBJECT was not found in the JCLskeleton.

12 A user-defined JCL skeleton parametershould not appear in the JCL skeleton.The token in this message contains thename of the JCL skeleton parameter thatcaused the problem.

13 A reserved JCL skeleton parametershould not appear in the JCL skeleton.The token in this message contains thename of the reserved JCL skeletonparameter that caused the problem.

14 The generated JCL is too long and thebuffer for it cannot be allocated. Thetoken in this message contains requestedsize that caused the problem. To avoidthis problem, decrease the number ofdatabase objects selected for processing.

User Response: Correct the problem according

to the given explanation. If the problem persists,contact your Database Administrator or DB2Customer Support.

SQL22247N The known discovery operationfailed.

Explanation: Discovery is disabled on the targetDB2 Administration Server.

User Response: Enable discovery by modifyingthe value of the DISCOVER configurationparameter on the DB2 Administration Server.Change the value to KNOWN if you only wantknown discovery enabled. Change the value toSEARCH if you want both known and searchdiscovery enabled. To modify the value of theconfiguration parameter, use the UPDATEADMIN CONFIGURATION command.

SQL22250W Usage: DASMIGR migrates a DB2Administration Server.

Explanation: The DASMIGR command syntaxis:

DASMIGR <source server> <target server>/h


source serverthe name of the DB2 AdministrationServer to be migrated

target serverthe name of the new DB2Administration Server that will containthe migrated information from thesource server

/h display the help information

User Response: Issue the DASMIGR commandwith one of the valid command options.


SQL22251N Migration of the DB2Administration Server fromsource-dasname to target-dasnamefailed. Reason code reason-code.

Explanation: The DB2 Administration Serversource-dasname could not be migrated for one ofthe following reasons:

1. The Tools Catalog Database has not beencreated at the target DB2 AdministrationServer.

2. The Tools Catalog Database has beenconfigured improperly at the target DB2Administration Server.

User Response: Attempt the following at thetarget DB2 Administration Server target-dasname:

1. Verify that the Tools Catalog Database exists.

2. Verify the TOOLSCAT_DB andTOOLSCAT_SCHEMA DB2 AdministrationServer configuration parameters are correct.They should be set to the name and schemaof the Tools Catalog Database. View thecurrent settings of TOOLSCAT_DB andTOOLSCAT_SCHEMA using the GETADMIN CONFIGURATION command. Tomodify the value of any DB2 AdministrationServer configuration parameter, use theUPDATE ADMIN CONFIGURATIONcommand

If you continue to receive this error messageafter attempting the suggested response, pleasecontact IBM Customer Support.

SQL22252N DAS migration failed with reasoncode reason-code.

Explanation: An error has occurred whilemigrating the DB2 Administration Server. Thereason codes are as follows:

1. The system resources available wereinsufficient to complete the migration.

2. The DB2 Administration Server’sconfiguration parameters do not identify avalid tools catalog.

3. A non-severe error occurred duringmigration.

User Response:

1. Verify that enough system resources areavailable for DAS migration.

2. Verify that a tools catalog is created and isidentified correctly by the DB2Administration Server’s configurationparameters.


SQL22255W Usage:

dasauto [-h|-?] -on|-off

Explanation: An incorrect argument wasentered. Valid arguments for this command are:

-h|-? display the usage information

-on|-offenables or disables autostarting of theDB2 Administration Server

User Response: Enter the command again asfollows:

dasauto [-h|-?] -on|-off

SQL22256W The dasauto command wassuccessful.



SQL22270N The contact, or contact group,with name name cannot be addedto the contact list.

Explanation: The contact, or contact group,already exists in the contact list.

User Response: Create a new contact, or contactgroup, with a unique name.


SQL22271N The contact, or contact group,information with name namecould not be found.

Explanation: The contact, or contact group,could not be found in the contact list.

User Response: Check and correct the name,and try again.

SQL22272N The record with key key cannot beinserted.

Explanation: The system tried to insert a recordand the new record’s key key already exists inthe system.

User Response: Remove the duplicate from thesystem; or, insert a new record with another key.

SQL22273N The record with key key could notbe found.

Explanation: The record with key key could notbe found because the record does not exist.

User Response: Check and correct the key, andtry again.

SQL22280N This action cannot be performedbecause the scheduler is quiesced.

Explanation: No action can be performed untilthe scheduler is activated again.

User Response: Activate the scheduler.

SQL22281N The scheduler is already active.

Explanation: The scheduler cannot be madeactive because it is already active.


SQL22282N The scheduler is unable to accessthe Tools Catalog Database.Reason code = reason-code andSQLCODE sqlcode.

Explanation: The scheduler function cannot beprocessed because the scheduler is unable toaccess the Tools Catalog Database for the reason

specified by the reason-code as follows:

1. The given user ID, or password, is incorrect.

2. Incorrect Tools Catalog Databaseconfiguration in the DB2 AdministrationServer configuration parameters. One or moreof the following DB2 Administration Serverconfiguration parameters is incorrect:

v TOOLSCAT_DB

v TOOLSCAT_SCHEMA

3. The Tools Catalog Database is already beingused by another scheduler on the samesystem.

4. The Tools Catalog Database is only supportedthrough TCP/IP as a communicationprotocol.

5. Unexpected errors. Refer to SQLCODE sqlcodefor more details.


1. Check your user ID and password and tryagain.

2. Verify that the DB2 Administration ServerTOOLSCAT_DB and TOOLSCAT_SCHEMAconfiguration parameters have been setcorrectly. View the current settings ofTOOLSCAT_DB and TOOLSCAT_SCHEMAusing the GET ADMIN CONFIGURATIONcommand. To modify the value of any DB2Administration Server configurationparameter, use the UPDATE ADMINCONFIGURATION command. If youcontinue to receive this error message afterattempting the suggested response, pleasecontact IBM Support.

3. Contact your system administrator.

4. Attempt the following:

v If the tools catalog database is local to thescheduler, then set up the instancespecified by the DB2 Administration Serverconfiguration parameter toolscat_inst touse TCP/IP communications.

v If the tools catalog database is remote tothe scheduler, then ensure that the nodeused by the toolscat_db adminconfiguration parameter supports TCP/IPas the communication protocol.



Contact IBM Support if you continue to receivethis message after attempting the suggestedsolutions.

SQL22283N Task taskid.suffix does not exist inthe Tools Catalog Database.

Explanation: The scheduler cannot retrieve thetask from the Tools Catalog Database. The taskmight have been removed from the Tools CatalogDatabase or never existed.

User Response: Check for the existence of thetask using the Task Center.

SQL22284N Task taskid.suffix is not scheduled.

Explanation: The requested action, Run ascheduled task now, cannot be performedbecause the task is not currently scheduled torun.

User Response: Attempt one of the following:

v Perform a Run now instead

v Activate all of the task’s schedules andperform Run a scheduled task now again.

SQL22285N The scheduler is unable to get thecorresponding hostname from thepartitioned database on partitionnumber partition-number.

Explanation: The requested partition numberdoes not exist in the partitioned database.

User Response: Verify that the partition numberexists by displaying the list of nodes using theLIST DBPARTITIONNUMS command.

SQL22286N Unable to execute the requiredtask.

Explanation: The scheduler failed to run thetask because an unexpected error occurred.

User Response: Refer to the DB2Administration Server’s First Failure Data

Capture Log for additional information.

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt.

SQL22287N User userid does not havepermission to execute Tasktaskid.suffix.

Explanation: The task failed to execute becausethe user does not have sufficient authority to runthe task.

User Response: Users must be granted runpermission by the owner of the task before theycan run the task.

SQL22295N Unable to communicatesuccessfully with the SMTP serverat host host-name using portport-number. Reason code =reason-code.

Explanation: The SMTP server at host host-nameusing port port-number failed to successfullynegotiate the protocol to send mail. Anexplanation of the error is indicated by thefollowing reason code:

1. There is no SMTP server running at host-nameon port port-number.

2. An unexpected error was encountered whilecommunicating with the SMTP server.

User Response:

1. Verify that the SMTP server name is specifiedcorrectly and that the SMTP port specified inthe services file corresponds to the portnumber being used by the SMTP server.

2. Invoke the Independent Trace Facility at theoperating system command prompt. ContactIBM Customer Support if the problempersists.

SQL22296N Unable to send mail using theSMTP protocol due to invalidrecipient addresses.

Explanation: The SMTP server failed tosuccessfully negotiate the send mail protocol for


all the specified recipients.

User Response: Verify that the recipientaddresses are specified correctly.

This error might also be returned if the SMTPserver is unable to reach the recipient addresses.This can be independently verified by using anyother mail client to send mail to the recipientsusing the same SMTP server. If this is successful,invoke the Independent Trace Facility at theoperating system command prompt. Contact IBMCustomer Support if the problem persists.

SQL22297I Configuration changes will not beeffective until the DB2Administration Server is restarted.

Explanation: The DB2 Administration Serverhas been successfully configured, but the changes

will not take effect immediately. The changes willtake effect when the DB2 Administration Serveris restarted.

User Response: To have the change take effectat the next DB2 Administration Server restart, nofurther action is required.

SQL27900 - SQL27999

SQL27902N LOAD RESTART/TERMINATE isnot allowed on a table that is notin LOAD PENDING state.

Explanation: No RESTART or TERMINATE isnecessary. The RESTART and TERMINATEmodes of the LOAD utility should be used toresume or cancel a previously failed/interruptedLOAD operation. They are only supported ontables where a previous load operation failed andthe table is in LOAD PENDING state. For tablesthat are not in LOAD PENDING state, only theINSERT and REPLACE modes of the LOADutility are supported.

User Response: To populate the table with thecontents of the input source re-issue your LOADcommand using the INSERT or REPLACE mode.You can use the LOAD QUERY utility to find outthe current state of the table.

SQL27903I agenttype has started on partitionpartitionnumber at time timestamp.

Explanation: This is an informational messageindicating that a DB2 agent is about to begin ona given partition.


SQL27904I The input file was not found.Using standard input as the input.

Explanation: This is an informational messageindicating that an DB2 agent is about to begin ona given partition.


SQL27907I Maximum input record lengthrecord-length.

Explanation: This is an informational messageindicating the record length used for the Loadoperation.


SQL27908I Program is running with checklevel: check-level.

Explanation: This is an informational messageindicating whether truncation checking isenabled or not.



SQL27909I Tracing numberofrecordsnon-delimited record(s).

Explanation: This is an informational messageindicating that tracing is enabled for the firstnumofrecords record(s).


SQL27910I The string delimiter is chardel, thecolumn delimiter is coldel, and thedecimal point is decept. Tracingnumofrecords delimited record(s).

Explanation: This is an informational messageindicating what delimiters are used for string,column and decimal point. In addition, thismessage also shows tracing is enabled for thefirst numofrecords record(s).


SQL27911I The input partition map filefilename was opened successfullyfor reading.

Explanation: This informational messageindicates the input partition map file was openedsuccessfully for reading.


SQL27912I Reading of input partitioning mapis in progress.

Explanation: This informational messageindicates that reading of the input partition mapfile is in progress.


SQL27913I Input partitioning map wassuccessfully read.

Explanation: This informational messageindicates that the input partition map file wassuccessfully read.


SQL27914I The mode of operation is mode.

Explanation: This informational messageindicates the mode of operation for thepartitioning agent.

There are two different modes of operation:

v Partition

v Analyze


SQL27915I Output partitioning map file notused.

Explanation: This is an informational messageindicating that the output partitioning map file isnot used.


SQL27916I The output partitioning map filefilename was opened successfully.

Explanation: This is an informational messageindicating that the output partitioning map filewas opened successfully.


SQL27918I Distribution file name: filename.

Explanation: This is an informational messageindicating the name of the distribution file usedin the utility.


SQL27919I The distribution file filename wasopened successfully for writing.

Explanation: This informational messageindicates the distribution file was openedsuccessfully for writing.



SQL27920I This utility is using numkeyspartitioning keys.

Explanation: This informational messageindicates the number of partitioning keys used inthe utility.


SQL27921I keyname Start:index Len:lengthPosition:position Type:type.

Explanation: This informational messagedescribes attributes of a partitioning key.


SQL27922I Output data files are not createdbecause the run type isANALYZE.

Explanation: This is an informational messageindicating that the output data files are notcreated because the mode of operation isANALYZE.


SQL27926I Output data for partitionpartitionnum will be sent tostandard output.

Explanation: This is an informational messageindicating that the output data on partitionpartitionnum will be sent to standard output.


SQL27927I Processed numofrecords records (orlines).

Explanation: This is an informational messageindicating that numofrecords records (or lines)were processed.


SQL27928I Processing record number num.

Explanation: This informational messageindicates which record is being processed. This

message will only be reported when the TRACEoption is specified.


SQL27929I Partitioning number returnedfrom hash function: hexvalue (hex)decvalue (decimal).

Explanation: This informational message reportsthe result of the hashing function in both hexand decimal format.


SQL27931I Writing output partition map tofile filename.

Explanation: This is an informational messageindicating that the output partition map iswritten to filename.


SQL27932I Writing distribution map tofilename.

Explanation: This is an informational messageindicating that the distribution map is written tofilename.


SQL27935I agenttype has ended on partitionpartitionnumber at time timestamp.

Explanation: This is an informational messageindicating that an DB2 agent has just completedoperation on a given partition.


SQL27936I Elapsed time: hr hours, minminutes, sec seconds.

Explanation: This informational message reportsthe total time elapsed.



SQL27937I Throughput: throughputrecords/sec.

Explanation: This is an informational messageindicating the throughput of a given DB2 agent.


SQL27939I Record counts for outputpartitions: partition numberpartitionnum. Record count:numofrecords.

Explanation: This informational messageindicates the number of records processed for agiven partition.


SQL27941I Program terminated abnormally.

Explanation: This informational messageindicates the utility program has terminatedabnormally.


SQL27942I There are numofwarnings warningmessage(s) and numofdisrecdiscarding records.

Explanation: This informational message reportsthere are numofwarn warning message(s) andnumofdisrec discarding record(s) encounteredduring the operation.


SQL27945I Key Index: index. Data: data1 data2data3 data4 data5.

Explanation: This informational message reportsthe attributes of a given partition key.


SQL27947I The input data file specified atline linenum of the configurationfile is ignored.

Explanation: The input data file specified at linelinenum of the configuration file is ignored. The

command line option will be used if it isspecified; otherwise, the first specification ofinput data file in the configuration file will beused.


SQL27948I The output data file specified atline linenum of the configurationfile is ignored.

Explanation: The output data file specified atline linenum of the configuration file is ignored.The command line option will be used if it isspecified; otherwise, the first specification ofoutput data in the configuration file will be used.


SQL27949I The distribution data filespecified at line linenum of theconfiguration file is ignored.

Explanation: The distribution file specified atline linenum of the configuration file is ignored.The command line option will be used if it isspecified; otherwise, the first specification ofdistribution file in the configuration file will beused.


SQL27950I The type of the input data file isfiletype.

Explanation: This is an informational messageindicating that the format of the input data isfiletype.

v 0-ASC

v 1-DEL

v 2-BIN

v 3-CUR


SQL27951I The NEWLINE flag is ignored incase of binary or delimited inputdata file

Explanation: This informational message reportsthat the NEWLINE flag is ignored for binary or


delimited input data files.


SQL27952I The NEWLINE flag is turned on.

Explanation: This informational message reportsthat the NEWLINE flag is in effect.


SQL27953I Usage: db2split[-c configuration-file-name][-d distribution-file-name][-i input-file-name][-o output-file-name][-h help message]

Explanation:

-c option will run this program using auser specified configuration file

-d option specifies the distribution file

-i option specifies the input file

-o option specifies the output file

-h option will generate the help message

SQL27959N The partitioned databaseconfiguration option option-name isinvalid. Reason code = reason-code.

Explanation: The partitioned databaseconfiguration option named in the error messageis incorrectly specified or is incompatible withone of the other load options specified.

The possible reason codes are as follows:

1 Partitioned database configurationoptions cannot be specified in anon-partitioned database environmentor when theDB2_PARTITIONEDLOAD_DEFAULTregistry variable is set to OFF.

2 Partitioned database configurationoptions may not be specified more thanonce.

3 Invalid pointer detected in thepiPartLoadInfoIn input structure passedto the db2Load API.

4 Invalid pointer detected in thepoPartLoadInfoOut output structurepassed to the db2Load API.

5 The argument supplied to the MODEoption must be one of the following:

v PARTITION_AND_LOAD

v PARTITION_ONLY

v LOAD_ONLY

v LOAD_ONLY_VERIFY_PART

v ANALYZE

6 The maximum number of partitioningagents must be less than or equal to themaximum number of partitionsallowable in a cluster.

7 The maximum number of partitionnumbers in a partition list must be lessthan or equal to the maximum numberof partitions allowable in a cluster.

8 The arguments supplied to theISOLATE_PART_ERRS option must beone of the following:

v SETUP_ERRS_ONLY

v LOAD_ERRS_ONLY

v SETUP_AND_LOAD_ERRS

v NO_ISOLATION

9 The value supplied to theSTATUS_INTERVAL option must be inthe range 1-4000.

10 The maximum port number must begreater than or equal to the minimumport number.

11 The only legal arguments for theCHECK_TRUNCATION, NEWLINE andOMIT_HEADER options are TRUE andFALSE.

12 The argument supplied toRUN_STAT_DBPARTNUM must be alegal partition number.


13 If the mode is ANALYZE, theMAP_FILE_OUTPUT option must bespecified.

14 If the mode is PARTITION_ONLY thePART_FILE_LOCATION option must bespecified. If the mode is LOAD_ONLYor LOAD_ONLY_VERIFY_PART, thePART_FILE_LOCATION option must bespecified if the input file name is notfully qualified.

15 The load actions RESTART andTERMINATE can only be used when themode is PARTITION_AND_LOAD,LOAD_ONLY orLOAD_ONLY_VERIFY_PART.

16 The HOSTNAME option cannot bespecified unless theFILE_TRANSFER_CMD option is alsospecified.

17 The partition isolation error modesLOAD_ERRS_ONLY andSETUP_AND_LOAD_ERRS are notcompatible with the ALLOW READACCESS or COPY YES options of theload command.

18 The LOAD_ONLY andLOAD_ONLY_VERIFY_PART modes arenot compatible with the CLIENT optionof the load command.

User Response: Resubmit the LOAD commandwith the correct partitioned databaseconfiguration options.

SQL27960N PART_FILE_LOCATION mustspecify a fully qualified basefilename when the file type isCURSOR.

Explanation: When loading from an input fileof type CURSOR, the PART_FILE_LOCATIONoption must specify a fully qualified basefilename instead of a directory.

User Response: Resubmit the LOAD commandwith a proper argument for thePART_FILE_LOCATION partitioned databaseconfiguration option.

SQL27961N ROWCOUNT cannot be specifiedin a partitioned databaseenvironment unless the mode isANALYZE.

Explanation: The ROWCOUNT option of theload command is not supported except when themode is ANALYZE.

User Response: Resubmit the load commandwithout the ROWCOUNT option.

SQL27990W During loading, at least one rowwas found to be on the wrongpartition.

Explanation: When loading a partitioneddatabase using the load utility withLOAD_ONLY_VERIFY_PART mode, any rows inthe input file that are found to be on the wrongpartition will be discarded. If the ″dumpfile″modifier is specified, the discarded rows will besaved to the dump file. This message will appearonly once per partition per load job, even whenthere are multiple partition violations present.

User Response: If the discarded rows are savedto a dump file, they can be loaded to the correctpartition by simply issuing another loadcommand with the MODE option set toPARTITION_AND_LOAD.

SQL27991W Too many partitioning agentsspecified in the load command.

Explanation: Too many partitioning agents havebeen specified in thePARTITIONING_DBPARTNUMS partitioneddatabase configuration option of the loadcommand. The maximum number of partitioningagents is specified by theMAX_NUM_PART_AGENTS load option, whichdefaults to 25 if not specified.

User Response: Resubmit the command withthe correct number of partitioning agents.Alternatively, thePARTITIONING_DBPARTNUMS option can beomitted and the load utility will automaticallyselect an appropriate number of partitioningagents.


SQL27992N The data file contains a validpartitioning map, but the loadmode isPARTITITON_AND_LOAD.

Explanation: Load has detected a validpartitioning map at the beginning of the file.PARTITION_AND_LOAD mode would treat thisas user data, possibly causing undesired results.

User Response: If the reason the data filebegins with a partitioning map header is that thedata in the file has already been partitioned, then

use LOAD_ONLY mode to load the file. In thiscase it will also be necessary to use theOUTPUT_DBPARTNUMS option to specify thesingle partition to which the data should beloaded.

If the partitioning map detected by load at thebeginning of the file is actually user data, thenuse PARTITION_AND_LOAD mode with theIGNOREHEADER modifier to disable thepartition map detection and load the entire datafile.

SQL29000 - SQL29099

SQL29000N The value specified forDYN_QUERY_MGMT is notvalid. DB2 Query Patroller is notinstalled on this server.

Explanation: The attempt to update thedatabase configuration parameterDYN_QUERY_MGMT to ENABLE failed becausethe DB2 Query Patroller server is not installed.

User Response: Install the DB2 Query Patrollerserver.

SQL29001N This database client level is notcompatible with the level of DB2Query Patroller server you arerunning on.

Explanation: The client and server code are notcompatible.

SQL29002N DB2 Query Patroller is notinstalled on this server.

Explanation: DB2 Query Patroller server tablesdo not exist on the server.

User Response: Install the DB2 Query Patrollerserver.

SQL29003N DB2 Query Patroller could notload Java class class-name, reasoncode reason-code.

Explanation: An error occurred while trying toload the Java class class-name. The reason codesare:

1 The class was not found on theCLASSPATH.

User Response: Ensure the class-name isinstalled in the CLASSPATH.

SQL29004N DB2 Query Patroller classclass-name cannot call methodmethod-name with signaturesignature.

Explanation: The Java method method-namecannot be found.

User Response: Ensure that the correct versionof the DB2 Query Patroller client is installed.

SQL29005N User user-ID is not defined in theuser profile table.

Explanation: User user-ID is not defined in theuser profile table. The user, or the group towhich the user belongs, must be defined in theuser profile table.

User Response: Use Query Administration todefine the user in the user profile table.


SQL29006N Java exception exception-string wasthrown.

Explanation: Java exception exception-string wasthrown.

User Response: If the problem persists contactyour technical service representative.

SQL29007N DB2 Query Patroller Server is notavailable.

Explanation: DB2 Query Patroller server is notrunning.

User Response: Start DB2 Query Patrollerserver and resubmit your query.

SQL29008N Error encountered during jobsequence number generation.

Explanation: An error was encountered duringjob sequence number generation.

User Response: If the problem persists contactyour technical service representative.

SQL29009N Error encountered whensubmitting a new job. Reasoncode reason-code.

Explanation: An error was encountered duringsubmission of a new job.

User Response: Examine the reason code andresubmit the query.

SQL29010N The query has been cancelled.

Explanation: User has cancelled the query.

SQL29011I Job job-ID has been submitted.

Explanation: Job job-ID has been submitted tothe DB2 Query Patroller server.

SQL29012N Job job-ID has been aborted.

Explanation: Job job-ID has been aborted.

User Response: Use QueryMonitor or theiwm_cmd command to examine the reason for

the aborted job and resubmit the query.

SQL29013I Job job-ID has been held.

Explanation: Job job-ID has been put on hold.

SQL29014N The value specified for DB2registry variable registry-variable isinvalid.

Explanation: The value specified forregistry-variable is invalid because of thefollowing restrictions by registry-variable:

DQP_NTIERThe value must be one of OFF,RUN[:timeout], or CHECK[:timeout].

DQP_LAST_RESULT_DESTThe length must not exceed 32characters.

DQP_TRACEFILEThe length must not exceed 256characters.

User Response: Correct the value of the DB2registry variable registry-variable with the db2setcommand and resubmit the query.

SQL29015N Error encountered during jobcancellation. Reason code:reason-code.

Explanation: An error was encountered whiletrying to cancel a job. The reason code maps toan SQL or DB2 message.

User Response: Examine the reason code,correct the error, and retry the action again.

SQL29016N The data source on the client doesnot match the data source on theDB2 Query Patroller server.

Explanation: The data source to which theclient is connected does not match the datasource that is used by the DB2 Query Patrollerserver.

User Response: Ensure that the DB2DBDFTprofile variable on the DB2 Query Patrollerserver matches the client data source name.


SQL29017N Job job-id has been cancelled.

Explanation: Job job-id has been cancelled.


SQL29018N The DB2 Query Patroller Client isnot installed.

Explanation: The user is querying a databasewhich has enabled the database configurationparameter DYN_QUERY_MGMT. However, theDB2 Query Patroller client code is not installedon the client machine.

User Response: Install the QueryEnablercomponent of the DB2 Query Patroller client.

SQL29019N Jobs have been scheduled on theDB2 Query Patroller server.

Explanation: Jobs have been scheduled on theDB2 Query Patroller server.


SQL30000 - SQL30099

SQL30000N Execution failed because of aDistributed Protocol Error thatwill not affect the successfulexecution of subsequentcommands or SQL statements:Reason Code reason-code(subcode).

Explanation: A system error occurred thatprevented successful processing of the currentenvironment command or SQL statement. Thismessage (SQLCODE) is produced at statementcompilation or execution time.

The command or statement cannot be processed.The current transaction is not rolled back and theapplication remains connected to the remotedatabase.

User Response: Record the message numberand the reason code. Record all error informationfrom the SQLCA, if possible. Attempt to rerunthe application.




v SQLCODE and reason code



sqlcode: -30000

sqlstate: 58008

SQL30002N The SQL statement cannot beexecuted due to a prior conditionin a chain of statements.

Explanation: An SQL statement was chained toPREPARE, but the PREPARE statement hasreceived a warning SQLCODE that requires theprogram or end user to either re-issue thechained statement or issue a different SQLrequest. This error can occur only in aclient/server environment.

v A distributed client using DRDA has chainedan OPEN statement to a PREPARE, but thePREPARE statement received SQLCODE+1140.

The statement cannot be executed as chained.

User Response: The statement must be sentagain as a separate request.

sqlcode: -30002

sqlstate: 57057


SQL30020N Execution failed because of aDistributed Protocol Error thatwill affect the successfulexecution of subsequentcommands and SQL statements:Reason Code reason-code.

Explanation: A system error occurred thatprevented successful execution of the currentenvironment command or SQL statement, as wellas any subsequent commands or SQL statements.

Reason code 124C indicates that the DRDA datastream for the request contains a syntax error.

The command or statement cannot be processed.The current transaction is rolled back and theapplication is disconnected from the remotedatabase.

User Response: Record the message number(SQLCODE) and the reason code. Record allerror information from the SQLCA, if possible.Attempt to connect the remote database andrerun the application.







Some possible reason codes include:

121C Indicates that the user is not authorizedto perform the requested command.

1232 The command could not be completedbecause of a permanent error. In mostcases, the server will be in the processof an abend.

1254 A command sent from the client hasresulted in an unarchitected andimplementation specific condition on theremote server for which there is noarchitected message to return to theclient.

If the remote server is DB2 UDB forOS/390,zOS then check the console logfor information about this error.

If the remote server is DB2 UDB foriSeries, the job log of the server job,and/or a first failure data capture(FFDC) spooled file is usually necessaryto determine the cause of the error.

If the remote server is DB2 UDB forUnix/Windows then check the remotedatabase server’s administrationnotification log for informationregarding this error.

220A The target server has received an invaliddata description. If a user SQLDA isspecified, ensure that the fields areinitialized correctly. Also, ensure that thelength does not exceed the maximumallowed length for the data type beingused.

If you are using the DB2 Connectproduct in a gateway serverenvironment with downlevel clients, thiserror may occur if your application’shost variables and the queried table’scolumn descriptions do not match.

sqlcode: -30020

sqlstate: 58009

SQL30021N Execution failed because of aDistributed Protocol Error thatwill affect the successfulexecution of subsequentcommands and SQL statements:Manager manager at Level level notsupported.

Explanation: A system error occurred thatprevented successful connection of theapplication to the remote database. This message(SQLCODE) is produced for SQL CONNECTstatement. manager and level are numeric valuesthat identify the incompatibility between theclient and the server.



User Response: Record the message number,the manager, and level values. Record all errorinformation from the SQLCA, if possible.Attempt to connect to the remote database again.

If the problem persists, invoke the IndependentTrace Facility at the operating system commandprompt. Then, contact your service representativewith the following information:





sqlcode: -30021

sqlstate: 58010

SQL30040N Execution failed because ofunavailable resources that will notaffect the successful execution ofsubsequent commands and SQLstatements: Reason reason. Type ofResource resource-type. Resourcename resource-name. Product IDproduct-ID.

Explanation: The application cannot process thecommand or SQL statement because the specifiedresource has run out. The current transaction isnot rolled back and the application remainsconnected to the remote database.


User Response: Increase the size of thespecified resource and resubmit the command.

sqlcode: -30040

sqlstate: 57012

SQL30041N Execution failed because ofunavailable resources that willaffect the successful execution ofsubsequent commands and SQLstatements: Reason reason. Type ofResource resource-type. Resourcename resource-name. Product IDproduct-ID.

Explanation: The application cannot process thecommand or SQL statement because resourcesare not available at the remote database. ThisSQLCODE is produced at statement compilationor processing time.


If the resource name is “Encrypt” or “Decrypt”,the user exits for password encryption ordecryption are unavailable or had an error.


User Response: Investigate the remote databasesystem environment.

Federated system users:

v If the password encryption or decryption userexit failed, reason is the integer value that thefederated server received when invoking theuser exit. Ensure that no errors occurred whenthe encryption and decryption user exits werelink-edited with the federated server.

If using a user-supplied user exit, please checkthe user exit source code to determine why thereason was returned. If the error is found in theuser exit source code, fix the error, link-editthe object code with the federated server, andreissue the failing command or statement.

v For all other cases, isolate the problem to thedata source failing the request (refer to theproblem determination guide to determinewhich data source is failing in processing anSQL statement), correct the problem at thedata source, and reissue the failing commandor statement.

sqlcode: -30041

sqlstate: 57013


SQL30050N number command or SQLstatement invalid while bind is inprogress.

Explanation: An application attempted to issuea command or SQL statement that is not validwhile a precompile/bind operation is inprogress. <number> is a numeric value thatidentifies the erroneous command or SQLstatement.

The command or statement is not processed.

User Response: If the application is not thedatabase manager precompiler/binder, verifythat bind is not active before issuing thecommand or SQL statement.

If the application is the database managerprecompiler/binder, record the message number(SQLCODE) and the <number> value. Record allerror information from the SQLCA, if possible.Attempt to perform the bind operation again.


Contact your technical service representativewith the following information:






sqlcode: -30050

sqlstate: 58011

SQL30051N Bind process with the specifiedpackage name and consistencytoken not active.

Explanation: An attempt has been made toissue a precompile/bind operation whenprecompile/bind is not active or an attempt wasmade to use an invalid package name and/orconsistency token during an activeprecompile/bind operation.


User Response: If the application is not thedatabase manager precompiler/binder, verifythat precompile/bind is active before issuing thebind operation and that correct information isbeing passed on the bind operation.

If the application is the database managerprecompiler/binder, record the message number(SQLCODE) and all error information from theSQLCA, if possible. Attempt to perform theoperation again.








sqlcode: -30051

sqlstate: 58012

SQL30052N Program preparation assumptionsare incorrect.

Explanation: The SQL statement being compiledis not recognized by the precompiler and cannotbe processed by the database.


User Response: Ensure that the statement iscorrect and attempt to perform the operationagain. If the problem continues, remove thestatement from the program.

sqlcode: -30052

sqlstate: 42932


SQL30053N The value for OWNER failed theauthorization check at the remotedatabase.

Explanation: The value specified for theOWNER option on the precompile/bind failedthe authorization check at the remote database.This SQLCODE is produced duringprecompile/bind. It is not produced by thedatabase manager precompiler/binder.

The precompile/bind operation cannot beprocessed.

User Response: Ensure that you are authorizedto use the ID specified for the OWNER option,or do not use the OWNER option.

sqlcode: -30053

sqlstate: 42506

SQL30060N authorization-ID does not have theprivilege to perform operationoperation.

Explanation: Authorization ID<authorization-ID> attempted to perform thespecified <operation> without having beengranted the proper authorization to do so. ThisSQLCODE is produced at statement compilationor processing time.


User Response: Ensure that the<authorization-ID> has been granted theauthorization necessary to perform the desiredoperation.

sqlcode: -30060

sqlstate: 08004

SQL30061N The database alias or databasename name was not found at theremote node.

Explanation: The database name is not anexisting database at the remote database node.


User Response: Resubmit the command withthe correct database name or alias.

Federated system users: check to ensure that theentry in SYSCAT.SERVERS correctly specifies thedatabase name of the data source.

sqlcode: -30061

sqlstate: 08004

SQL30070N command-identifier Command is notsupported.

Explanation: The remote database received acommand that it does not recognize. The currentenvironment command or SQL statement cannotbe processed successfully, nor can anysubsequent commands or SQL statements.

The current transaction is rolled back and theapplication is disconnected from the remotedatabase. The statement cannot be processed.

User Response: Record the message number(SQLCODE) and the command identifier. Recordall error information from the SQLCA, ifpossible. Attempt to connect to the remotedatabase and rerun the application.





v SQLCODE and command identifier



sqlcode: -30070

sqlstate: 58014

SQL30071N object-identifier Object is notsupported.

Explanation: The remote database received datait does not recognize. The current environmentcommand or SQL statement cannot be processed


successfully, nor can any subsequent commandsor SQL statements.

The current transaction is rolled back and theapplication is disconnected from the remotedatabase. The command cannot be processed.

User Response: Record the message number(SQLCODE) and the object identifier. Record allerror information from the SQLCA, if possible.Attempt to connect to the remote database andrerun the application.

If sufficient memory resources exist and theproblem continues,

If trace was active, invoke the Independent TraceFacility at the operating system commandprompt.




v SQLCODE and object identifier



sqlcode: -30071

sqlstate: 58015

SQL30072N parameter-identifier Parameter is notsupported.

Explanation: The remote database received datait does not recognize. The current environmentcommand or SQL statement cannot be processedsuccessfully, nor can any subsequent commandsor SQL statements.

The command cannot be processed.. The currenttransaction is rolled back and the application isdisconnected from the remote database.

User Response: Record the message number(SQLCODE) and the parameter identifier. Recordall error information from the SQLCA, ifpossible. Attempt to connect to the remotedatabase and rerun the application.

If sufficient memory resources exist and the

problem continues, invoke the Independent TraceFacility at the operating system commandprompt.




v SQLCODE and parameter identifier



sqlcode: -30072

sqlstate: 58016

SQL30073N parameter-identifier Parameter valuevalue is not supported.

Explanation: The remote database received datait does not recognize. The current environmentcommand or SQL statement cannot be processedsuccessfully, nor can any subsequent commandsor SQL statements.

The current transaction is rolled back and theapplication is disconnected from the remotedatabase. The command cannot be processed.

User Response: Record the message number(SQLCODE) and the parameter identifier. Recordall error information from the SQLCA, ifpossible. Attempt to connect to the remotedatabase and rerun the application.

If sufficient memory resources exist and theproblem continues,




v SQLCODE, parameter identifier, and value



Some possible parameter identifiers include:


002F The target server does not support thedata type requested by the applicationrequester. For example, when DB2Connect is used to connect to DB2 2.3,this error will be returned unless theproper PTF is applied to DB2 2.3.Ensure that the level of the server issupported by the requester.

119C, 119D, 119EThe target server does not support theCCSID requested by the applicationrequester. Ensure the CCSID used by therequester is supported by the server.

v 119C - Verify the single-byte CCSID.

v 119D - Verify the double-byte CCSID.

v 119E - Verify the mixed-byte CCSID.

sqlcode: -30073

sqlstate: 58017

SQL30074N reply-identifier Reply is notsupported.

Explanation: The client received a reply it doesnot recognize. The current environmentcommand or SQL statement cannot be processedsuccessfully, nor can any subsequent commandsor SQL statements.

The current transaction is rolled back and theapplication is disconnected from the remotedatabase. The statement cannot be processed.

User Response: Record the message number(SQLCODE) and the reply identifier. Record allerror information from the SQLCA, if possible.Attempt to connect to the remote database andrerun the application.





v SQLCODE and reply identifier



sqlcode: -30074

sqlstate: 58018

SQL30080N A communication error reason-codeoccurred sending or receiving datafrom the remote database.

Explanation: The reason-code contains theoriginal error codes reported by CommunicationsManager.

For APPC error codes, the format ispppp-ssssssss-dddddddd where pppp is the primaryreturn code, ssssssss is the secondary return codeand dddddddd is the sense data. Each of theseerror code values is represented in hexadecimalnotation. Possible primary and secondary errorcodes include 0003-00000004 and 0003-00000005,which indicate that a conversation with theDatabase Server could not be allocated. Sensedata will only be displayed for an APPCALLOCATE error.

The command cannot be processed. Theconnection attempted to the database isunsuccessful or the current transaction to theconnected database is rolled back and theapplication is disconnected from the remotedatabase.

Refer to the document IBM CommunicationsManager 1.0 APPC Programming Guide andReference (SC31-6160) for explanation of theAPPC primary and secondary return codes. Fordetails of APPC sense data, refer to the IBMCommunications Manager 1.0 Problem DeterminationGuide (SC31-6156).

User Response: Ensure that both the databasemanager and Communications Manager arestarted at the Database Server and that allCommunications Manager configurationparameters are correct.

Note: If the reason code embedded in yourmessage is 0003-084C0001 one possible


cause for this message is that you aretrying to make a remote connection to aworkstation that is not a server. Verify thatthe remote workstation is a server. If it isnot a server, install the database manageras a server.

sqlcode: -30080

sqlstate: 08001

SQL30081N A communication error has beendetected. Communication protocolbeing used: protocol.Communication API being used:interface. Location where the errorwas detected: location.Communication functiondetecting the error: function.Protocol specific error code(s): rc1,rc2, rc3.

Explanation: An error has been detected by thecommunication subsystem.

If the connection has already been established,possible causes include the following:

v A communication subsystem error at the clientnode or server node has caused the connectionto go down.

v A communication subsystem error at theSOCKS server, if one is being used, has causedthe connection to go down.

v A network error has caused the connection togo down.

v The database agent at the server was forced offby the system administrator.

v The database agent at the server wasterminated due to an abnormal termination ofa key database manager process.

If you are trying to establish a new connection,possible causes include the following:

v The remote database server has not beencataloged correctly at the client.

v The database manager configuration file at theserver has not been configured with the propercommunication parameters.

v The communication subsystem at the clientnode or server node has not been configuredcorrectly, or has not been started successfully.

v The communication subsystem at the SOCKSserver, if one is being used, has not beenconfigured correctly, or has not been startedsuccessfully.

v The DB2COMM environment variable at theserver doesn’t specify the communicationprotocol used by the client.

v The database manager at the server has notbeen started, or has not been startedsuccessfully. One or more of thecommunication protocols specified byDB2COMM may not have been successfullystarted.

Refer to the token values for details. Dependingon the protocol being used and thecommunication function invoked, some tokensmay not be applicable. The following is theexplanation of the token values:

<protocol>The actual communication protocolbeing used. Valid token values are:

v TCP/IP

v APPC

v NETBIOS

v IPX/SPX

<interface>The application programming interfaceused to invoke the abovecommunication protocol services. Validtoken values are:

v SOCKETS

v SOCKS

v CPI-C

v DLR or DD

v TLI or Connection/Bindery

<location>This is a protocol specific ID whichuniquely identifies the node thatdetected the error. If the protocol beingused is:

v TCP/IP


The format of the ID is the Internetaddress in dot notation.

v APPC

The format of the ID is the fullyqualified LU name(networkID.LUname).

v NETBIOS

The format of the ID is theWorkstation name (nname).

v IPX/SPX

The format of the ID is the networkaddress and node address inhexadecimal notation (network.node).

If the location information is notavailable at the time that the erroroccurred, this token is not filled in.

<function>The name of the communicationsubsystem function that returned theerror code(s).

<rc1>, <rc2>, <rc3>The list of the available error codes andsubcodes that are specific to eachprotocol being used. Tokens that are notapplicable contain ″*″.

If the protocol being used is:

v TCP/IP

– If present, <rc1> contains theglobal errno value from the TCP/IPsockets function call. When usingWindows Sockets, if present, <rc1>contains the error from the TCP/IPsockets function call returned byWSAGetLastError().

– If present, <rc2> contains theglobal h_errno value from theTCP/IP name resolution functioncall. When using Windows Sockets,if present, <rc2> contains the errorfrom the TCP/IP database functioncall returned byWSAGetLastError().

– If <rc3> is present and contains″0″, it means that the TCP/IP

connection has been closed. Thiscould be caused by one of thefollowing:

- The database agent at the serverwas forced off by the systemadministrator.

- A database agent could not bestarted at the server because themaxagents database managerconfiguration parameter hasbeen exceeded. Check theadministration notification log tosee if an error message has beenlogged.

- The connection may have beenclosed by the remote server atthe TCP/IP level.

- The database agent at the serverwas terminated due to anabnormal termination of a keydatabase manager process.

Note: When using Windows Sockets,if the <function> isWSAStartup, and <rc1> is 0,then <rc2> contains theWindows Sockets Specificationversion level requested by DB2,and <rc3> contains theWindows Sockets Specificationversion level supported by theWindows Sockets DLL.

v APPC

<rc1> contains the return code fromthe CPI-C function. If present, <rc2>contains the global errno value fromthe CPI-C function call. <rc3> is notapplicable.

v NETBIOS

<rc1> contains the return code fromthe call to NetBIOS. <rc2> and <rc3>are not applicable.

v IPX/SPX

<rc1> contains the global t_errnovalue from the call to TLI Services, orthe return code from the call toNetWare Connection or Bindery


Services. If the <rc1> t_errno isTLOOK, <rc2> contains the TLI eventthat has occurred. If the <rc2> eventis T_DISCONNECT, <rc3> containsthe disconnect reason code. On AIX, ifthe <rc1> t_errno is TSYSERR, <rc3>contains the system errno (defined insys/errno.h). If <rc1> contains theerror return code from a call to AIXNetWare Connection or BinderyServices, <rc2> contains the errorgenerator.

See the Communications Errors appendix of theMessage Reference for more information onspecific communication error codes.

User Response:

If the connection has already been established,check if:

1. The database agent at the server has beenforced off.

2. The database manager at the server hasabnormally terminated.

3. A communication subsystem or network errorhas occurred. See the Message Reference formore information on specific communicationerror codes.

If you are trying to establish a new connection,check if:

1. The remote database server is catalogedproperly on the client node.

2. The database manager configuration file atthe server is configured with the propercommunication related parameters. If thedatabase manager configuration parametershave been updated at the server, ensure thatyou stop and then re-start the databasemanager, for the changes to take effect.

3. The communication subsystems on bothclient and server nodes are configured andstarted up properly.

4. The DB2COMM environment variable at theserver specifies the communication protocolused by the client.

5. The database manager at the server issuccessfully started. Start database manager

processing at the server should have returnedSQL1063, and not SQL5043. If SQL5043 isreturned, check the administrationnotification log for more information.

6. A communication subsystem or network errorhas occurred.

If the problem persists, consult with yournetwork administrator and/or communicationexpert to determine the cause of the problemusing the set of tokens provided.

sqlcode: -30081

sqlstate: 08001

SQL30082N Attempt to establish connectionfailed with security reasonreason-code (reason-string).

Explanation: The attempt to connect to theremote database server was rejected due toinvalid or incorrect security information. Thecause of the security error is described by the<reason-code> and corresponding<reason-string> value.

The following is a list of reason codes andcorresponding reason strings:

0 (NOT SPECIFIED)The specific security error is notspecified.

1 (PASSWORD EXPIRED)The password specified in the requesthas expired.

2 (PASSWORD INVALID)The password specified in the request isnot valid.

3 (PASSWORD MISSING)The request did not include a password.

4 (PROTOCOL VIOLATION)The request violated security protocols.

5 (USERID MISSING)The request did not include a userid.


6 (USERID INVALID)The userid specified in the request is notvalid.

7 (USERID REVOKED)The userid specified in the request hasbeen revoked.

8 (GROUP INVALID)The group specified in the request is notvalid.

9 (USERID REVOKED IN GROUP)The userid specified in the request hasbeen revoked in the group.

10 (USERID NOT IN GROUP)The userid specified in the request is notin the group.

11 (USERID NOT AUTHORIZED AT REMOTELU) The userid specified in the request is not

authorized at the remote Logical Unit.

12 (USERID NOT AUTHORIZED FROMLOCAL LU)

The userid specified in the request is notauthorized at the remote Logical Unitwhen coming from the local LogicalUnit.

13 (USERID NOT AUTHORIZED TO TP)The userid specified in the request is notauthorized to access the TransactionProgram.

14 (INSTALLATION EXIT FAILED)The installation exit failed.

15 (PROCESSING FAILURE)Security processing at the server failed.

16 (NEW PASSWORD INVALID)the password specified on a changepassword request did not meet theserver’s requirements.

17 (UNSUPPORTED FUNCTION)the security mechanism specified by theclient is invalid for this server. Sometypical examples:

v The client sent a new password valueto a server that does not support thechange password function.

v The client sent SERVER_ENCRYPTauthentication information to a serverthat does not support passwordencryption.

v The client sent a userid (but nopassword) to a server that does notsupport authentication by userid only.

v The client has not specified anauthentication type, and the serverhas not responded with a supportedtype. This may include the serverreturning multiple types from whichthe client is unable to choose.

18 (NAMED PIPE ACCESS DENIED)The named pipe is inaccessible due to asecurity violation.

19 (USERID DISABLED or RESTRICTED)The userid has been disabled, or theuserid has been restricted fromaccessing the operating environment atthis time.

20 (MUTUAL AUTHENTICATION FAILED)The server being contacted failed topass a mutual authentication check. Theserver is either an imposter, or the ticketsent back was damaged.

21 (RESOURCE TEMPORARILYUNAVAILABLE)

Security processing at the server wasterminated because a resource wastemporarily unavailable. For example,on AIX, no user licenses may have beenavailable.

24 (USERNAME AND/OR PASSWORDINVALID)

The username specified, passwordspecified, or both, are invalid.

User Response: Ensure that the proper useridand/or password is supplied.

The userid may be disabled, the userid may berestricted to accessing specific workstations, orthe userid may be restricted to certain hours ofoperation.

For reason code 17, retry the command with asupported authentication type.


For reason code 20, make sure the authenticationmechanism for the server is started, and retry.

sqlcode: -30082

sqlstate: 08001

SQL30083N Attempt to change password foruser id uid failed with securityreason reason-code (reason-string).

Explanation: The attempt to change passwordwas rejected due to invalid or incorrect securityinformation. The cause of the security error isdescribed by the reason-code and correspondingreason-string values.

The following is a list of reason codes andcorresponding reason strings:

0 (NOT SPECIFIED)The specific security error is notspecified.

1 (CURRENT PASSWORD INVALID)The old password specified in therequest is not valid.

2 (NEW PASSWORD INVALID)The password specified in the request isnot valid under the password rulesimposed by the system where passwordwas to be changed.

3 (CURRENT PASSWORD MISSING)The request did not include an oldpassword.

4 (NEW PASSWORD MISSING)The request did not include a newpassword.

5 (USERID MISSING)The request did not include a userid.

6 (USERID INVALID)The userid specified in the request is notvalid.

7 (USERID REVOKED)The userid specified in the request hasbeen revoked. Passwords can not bechanged for revoked userids.

14 (INSTALLATION EXIT FAILED)The installation security exit failed.

15 (PROCESSING FAILURE)Security processing at the server failed.

17 (UNSUPPORTED FUNCTION)Change password function is notsupported by the system.

19 (USERID DISABLED or RESTRICTED)The userid has been disabled, or theuserid has been restricted fromaccessing the operating environment atthis time.

23 (CHGPWD_SDN in DCS entry is notconfigured)

To change an MVS password on a hostsystem connected via SNA, the DCSdatabase must be cataloged with the,,,,,,,CHGPWD_SDN parameter string.The ,,,,,,,CHGPWD_SDN parameterstring identifies the symbolic destinationname for Password ExpirationManagement (PEM).

24 (USERNAME AND/OR PASSWORDINVALID)

The username specified, passwordspecified, or both, are invalid.

User Response: Ensure that the proper userid,current and new passwords are supplied.

The userid may be disabled, the userid may berestricted to accessing specific workstations, orthe userid may be restricted to certain hours ofoperation.

Instructions for some specific reason codesfollow:

14 Check the file db2pem.log in theinstance subdirectory (typically ″db2″)for a detailed description of the problemencountered.

23 Catalog the DCS database using the,,,,,,,CHGPWD_SDN parameter, asspecified in the DB2 Connect User’sGuide.

sqlcode: -30083

sqlstate: 08001


SQL30090N Operation invalid for applicationexecution environment. Reasoncode = reason-code

Explanation: The operation is invalid for theapplication execution environment. For example,an operation might be invalid for applicationsthat have special restrictions on statements orAPIs - applications such as those that operate inan XA Distributed Transaction Processingenvironment, such as CICS; those that operatewith CONNECT type 2 connection settings; orthose that use federated system functionality toupdate multiple heterogeneous data sources. Theoperation was rejected.


01 an SQL request that changes data (suchas an INSERT or a CREATE) was issuedagainst a read-only database; or, astored procedure was invoked against aread-only database. Read-only databasesinclude the following types:

v Databases accessed using DRDAwhen operating in a unit of workwhich has connection settingSYNCPOINT TWOPHASE andexecuting in a non-XA/DTPenvironment when either aSynchpoint Manager is not beingused or the remote DRDA databasedoes not support level 2 DRDAprotocol.

v Databases accessed by DRDA in anXA/DTP environment when either aSynchpoint Manager gateway isunavailable or the remote DRDAdatabase does not support level 2DRDA protocol.

v Databases which were not the firstdatabase updated when theSYNCPOINT ONEPHASE connectionsetting is in effect for the unit ofwork.

02 an API such as Precompile, Bind, orReorganize Table which causes internalcommits was issued in an application

which has the setting CONNECT type 2or is operating in an XA/DTPenvironment.

03 an SQL OPEN for a held cursor wasissued while in an XA/DTPenvironment when using an ENCINA orTUXEDO transaction processingmonitor.

04 a DISCONNECT statement was issuedwhile in an XA/DTP environment.

05 A compound SQL statement whichcontains a COMMIT statement wasissued in a CONNECT type 2 orXA/DTP environment.

06 The SET CLIENT API was issued in anXA/DTP environment.

07 A second database is being accessedwithin a unit of work for whichtwo-phase commit coordination is notbeing supplied by the transactionmanager. To ensure data integrity, theoperation has been disallowed.

08 An attempt was made to access adatabase for use of commit coordinationfrom a source different from aconcurrently connected database. Thetwo types of coordination cannot bemixed, and operations against thecurrent database are rejected.

09 An attempt was made to execute anXA/DTP local transaction against adatabase accessed under SynchpointManager coordination.

10 An SQL OPEN for a held cursor wasissued in either of these cases:

v XA/DTP environment, or

v federated server accessing a nicknamedefined on a two phase commitdatasource

Cursor hold is not supported in theseenvironments.

11 An operation is not supported forpass-through.


12 The insert/update/delete operationrequires the existence of a timestampcolumn and a unique index due to therestriction on the data source. For anupdate/delete operation accessing datasources:

v Fujitsu RDB2 requires the existence ofa unique index.

13 A positioned UPDATE or DELETEoperation requires the existence of acolumn in the SELECT list of the cursor,but that column does not exist in theSELECT list of the cursor.

14 An illegal combination of updatablecursors, cursor hold, and isolation levelof Repeatable Read exists. Invalidcombinations are:

v Isolation level Repeatable Read and aWITH HOLD cursor

v A WITH HOLD cursor with FORUPDATE

15 Reserved for future use

16 Illegal type column and protocol columnvalue combination in SYSCAT.SERVERS.

17 The REORG utility cannot be issuedagainst a nickname.

18 An update request (or, a DDL operationthat results in the update of a systemcatalog table) has been issued thatwould result in multiple data sourcesbeing updated when one or more of thedata sources in the unit of work onlysupports one-phase commit. Possiblecauses are:

v An attempt was made to update adata source that only supportsone-phase commit, but a differentdata source has already been updatedin the same unit of work.

v An attempt was made to update adata source that supports two-phasecommit, but a different data sourcethat only supports one-phase commithas already been updated in the sameunit of work.

v An attempt was made to update alocal federated server table, but a datasource that only supports one-phasecommit has already been updated inthe same unit of work.

v An attempt was made to update adata source that only supportsone-phase commit when theapplication is operating with aCONNECT type 2 connection setting.

19 The application host variable data typeis not supported by the data source in apass-through session.

20 SET CLIENT INFORMATION wasissued while a Unit of Work is inprogress.

21 The operation that you want performedat the specified data source(s) is notsupported by the wrapper by whichDB2 accesses the data source(s). Consultthe documentation to find out whatoperations this wrapper supports.

22 A federated insert, update, or deleteoperation is invalid in an applicationexecution environment where a

v SAVEPOINT is in effect

v scrollable cursor is used

v target view contains multiple tablesor nicknames

v trigger is in effect.

23 The API, data structure, or setting is notsupported.

User Response: Correct the problem by doingone of the following steps:

For reasons 01, 02, 03, 04, 06, or 19,remove the statement or API which isnot supported.

Alternately, for reasons 01, 02, 03, 04, or 06,execute the application in a differentenvironment which supports the failingstatement or API.

For reason 05,move the COMMIT request outside ofthe compound statement.


For reason 07,ensure that only one database isaccessed within a unit of work forwhich EXEC SQL COMMIT or EXECSQL ROLLBACK will be issued in placeof syncpoint requests to an externaltransaction manager. If multipledatabases must be accessed within theunit of work, utilize the commitmentcontrol interface provided by theexternal transaction manager product.

For reason 08,ensure that all databases being accessedwithin a unit of work are under thecommitment control of the same type ofrequest: external transaction processingmonitor (such as CICS SYNCPOINT) orlocal COMMIT and ROLLBACK EXECSQL.

For reason 09,do one of the following steps:

v Execute the transaction as anXA/DTP global transaction.

v Access the database in anon-XA/DTP environment.

v Do not use the services of theSynchpoint Manager for the databaseconnection if the transaction isread-only.

For reasons 10 through 17 (federated serverusers), isolate the problem to the data source

failing the request (see theTroubleshooting Guide) and examine therestrictions for that data source.

For reason 18,do one of the following steps:

v Submit a COMMIT or ROLLBACKbefore issuing an update to a differentdata source.

v If multiple data sources need to beupdated within a unit of work, makesure the two_phase_commit serveroption has been set to ’Y’ for all thedata sources that need to be updated.See the SQL Reference for informationon setting the value used for thetwo_phase_commit setting.

v If the data source to be updatedsupports only one-phase commit andthe application is operating with aCONNECT type 2 connection setting,change the application to operatewith a CONNECT type 1 connectionsetting.

For reason 20,submit a Commit or Rollback beforeinvoking the API.

For reason 22,Either remove the federated insert,update or delete operation or:

v release the savepoint that is in effect

v remove the use of the scrollablecursor

v redefine the target view to refer toonly one table or nickname

v execute the federated insert, update,or delete operation outside of thetrigger.

For reason 23,Refer to the Administrative APIReference for a list of supported APIs,data structures, and settings.

sqlcode: -30090

sqlstate: 25000

SQL30100 - SQL30199

SQL30101W Bind options specified onREBIND request are ignored.

Explanation: Bind options were specified on theREBIND request however the database server

does not support respecification of any bindoptions. The bind options specified will beignored and the options from the original BINDrequest will be used.


User Response: No action is required. This is awarning situation only.

If the database server returned an additionalwarning SQLCA, the ″sqlerrmc″ tokens willindicate the following information about thisadditional SQLCA in this order:

v sqlcode (SQL return code)

v sqlstate (universal SQL return code)

v sqlerrp (product name)

v sqlerrmc (SQL message tokens)

sqlcode: +30101

sqlstate: 01599

SQL30104N Error in BIND or PRECOMPILEoption option-name with valuevalue-name.

Explanation: While processing the BIND orPRECOMPILE parameters, either the BIND orPRECOMPILE option or the value is notacceptable, or the option and value pair is notappropriate.


User Response: Examine the command optionsand values to determine the error and resubmitthe command.

sqlcode: -30104

sqlstate: 56095

SQL30106N Invalid input data detected for amultiple row INSERT operation.INSERT processing is terminated.

Explanation: An error was detected with theinput data for one row of a multiple row INSERToperation. No further rows will be inserted. Foran atomic operation, all inserted rows are rolledback. For a non-atomic operation, rows insertedsuccessfully before the row containing the invalidinput data was encountered are not rolled back.

User Response: Correct the row containing theinvalid input data and submit the multiple row

INSERT again for the rows that did not getinserted.

sqlcode: -30106

sqlstate: 22527



Chapter 3. SQLSTATE Messages

This section lists the SQLSTATEs and their meaning. The SQLSTATEs aregrouped by class code; for subcodes, see the corresponding tables.

Table 1. SQLSTATE Class Codes

ClassCode

Meaning For subcodes, refer to...

00 Unqualified Successful Completion Table 2 on page 556

01 Warning Table 3 on page 556

02 No Data Table 4 on page 560

07 Dynamic SQL Error Table 5 on page 560

08 Connection Exception Table 6 on page 561

09 Triggered Action Exception Table 7 on page 561

0A Feature Not Supported Table 8 on page 561

0D Invalid Target Type Specification Table 9 on page 562

0F Invalid Token Table 10 on page 562

0K Invalid RESIGNAL Statement Table 11 on page 562

20 Case Not Found for CASE Statement Table 12 on page 562

21 Cardinality Violation Table 13 on page 562

22 Data Exception Table 14 on page 563

23 Constraint Violation Table 15 on page 564

24 Invalid Cursor State Table 16 on page 565

25 Invalid Transaction State Table 17 on page 565

26 Invalid SQL Statement Identifier Table 18 on page 566

28 Invalid Authorization Specification Table 19 on page 566

2D Invalid Transaction Termination Table 20 on page 566

2E Invalid Connection Name Table 21 on page 567

34 Invalid Cursor Name Table 22 on page 567

36 Cursor Sensitivity Exception Table 23 on page 567

38 External Function Exception Table 24 on page 567

39 External Function Call Exception Table 25 on page 568

3B Invalid SAVEPOINT Table 26 on page 569

40 Transaction Rollback Table 27 on page 569


Table 1. SQLSTATE Class Codes (continued)

ClassCode

Meaning For subcodes, refer to...

42 Syntax Error or Access Rule Violation Table 28 on page 569

44 WITH CHECK OPTION Violation Table 29 on page 582

46 Java DDL Table 30 on page 582

51 Invalid Application State Table 31 on page 582

53 Invalid Operand or InconsistentSpecification

Table 32 on page 583

54 SQL or Product Limit Exceeded Table 33 on page 584

55 Object Not in Prerequisite State Table 34 on page 585

56 Miscellaneous SQL or Product Error Table 35 on page 586

57 Resource Not Available or OperatorIntervention

Table 36 on page 587

58 System Error Table 37 on page 588

Class Code 00 Unqualified Successful Completion

Table 2. Class Code 00: Unqualified Successful Completion

SQLSTATEValue

Meaning

00000 Execution of the operation was successful and did not result in any typeof warning or exception condition.

Class Code 01 Warning

Table 3. Class Code 01: Warning

SQLSTATEValue

Meaning

01002 A DISCONNECT error occurred.

01003 Null values were eliminated from the argument of a column function.

01004 The value of a string was truncated when assigned to a host variable.

01005 Insufficient number of entries in an SQLDA.

01007 A privilege was not granted.

0100C One or more adhoc result sets were returned from the procedure.

0100D The cursor that was closed has been re-opened on the next result setwithin the chain.


Table 3. Class Code 01: Warning (continued)

SQLSTATEValue

Meaning

0100E The procedure generated more than the maximum allowed number ofresult sets. Only the first integer result sets have been returned to thecaller.

01503 The number of result columns is larger than the number of host variablesprovided.

01504 The UPDATE or DELETE statement does not include a WHERE clause.

01506 An adjustment was made to a DATE or TIMESTAMP value to correct aninvalid date resulting from an arithmetic operation.

01509 Blocking was cancelled for a cursor because there is insufficient storagein the user virtual machine.

01515 The null value has been assigned to a host variable, because the non-nullvalue of the column is not within the range of the host variable.

01516 An inapplicable WITH GRANT OPTION has been ignored.

01517 A character that could not be converted was replaced with a substitutecharacter.

01519 The null value has been assigned to a host variable, because a numericvalue is out of range.

01524 The result of a column function does not include the null values thatwere caused by evaluating an arithmetic expression.

01526 Isolation level has been escalated.

01539 Connection is successful but only SBCS characters should be used.

01543 A duplicate constraint has been ignored.

01545 An unqualified column name has been interpreted as a correlatedreference.

01550 The index was not created, because an index with the specifieddescription already exists.

01560 A redundant GRANT has been ignored.

01562 The new path to the log (newlogpath) in the database configuration fileis invalid.

01563 The current path to the log file (logpath) is invalid. The log file path isreset to the default.

01564 The null value has been assigned to a host variable, because division byzero occurred.

01586 Setting OFF the constraints for a parent table in a referential structurehas resulted in one or more descendent tables being automatically placedinto a check-pending state

01589 A statement contains redundant specifications.

Chapter 3. SQLSTATE Messages 557


SQLSTATEValue

Meaning

01592 In a CREATE FUNCTION statement that references a SOURCE function,either:v an input parameter has a larger length, precision, or scale than that of

the corresponding parameter of the source function; orv the RETURNS or CAST FROM parameter has a smaller length,

precision, or scale than that of the source function; orv the CAST FROM parameter in the CREATE FUNCTION statement has

a larger length, precision, or scale than that of the RETURNSparameter.

Truncation may occur at run time (and may result in an error at thattime).

01594 Insufficient number of entries in an SQLDA for ALL information (i.e. notenough descriptors to return the distinct name).

01595 The view has replaced an existing, invalidated view.

01596 Comparison functions were not created for a distinct type based on along string data type.

01598 An attempt has been made to activate an active event monitor ordeactivate an inactive event monitor.

01599 Bind options were ignored on REBIND.

01602 The optimization level has been reduced.

01603 CHECK DATA processing found constraint violations and moved themto exception tables.

01604 The SQL statement was explained and not executed.

01605 A recursive common table expression may contain an infinite loop.

01606 The node or system database directory is empty.

01607 The difference between the times on nodes in a read-only transactionsexceed the defined threshold.

01609 The procedure generated more than the maximum allowed number ofresult sets. Only the first integer result sets have been returned to thecaller.

01610 One or more ad hoc result sets were returned from the procedure.

01611 The cursor that was closed has been re-opened on the next result setwithin the chain.

01616 The estimated CPU cost exceeds the resource limit.

01618 Redistribute nodegroup is required to change data partitioning.

01620 Some base tables of UNION ALL may be the same table.

01621 The retrieved LOB value may have been changed.



SQLSTATEValue

Meaning

01622 Statement completed successfully but a system error occurred after thestatement completed.

01623 Value of DEGREE is ignored.

01626 The database has only one active bufferpool.

01627 The DATALINK value may not be valid because the table is in reconcilepending or reconcile is not possible state.

01632 The number of concurrent connections has exceeded the definedentitlement for the product.

01633 The materialized query table may not be used to optimize the processingof queries.

01636 Integrity of non-incremental data remains unverified by the databasemanager.

01637 Debugging is not enabled.

01639 The federated object may require the invoker to have necessaryprivileges on data source objects.

01641 Datalink type attributes limit the use of the structured type.

01642 Column not long enough for the largest possible USER default value.

01643 Assignment to an SQLSTATE or SQLCODE variable in an SQL routinemay be over-written and does not activate any handler.

01645 The executable for the SQL procedure is not saved in the databasecatalog.

01648 COMPRESS column attribute ignored because VALUE COMPRESSION isdeactivated for the table.

01649 The buffer pool configuration has been completed but will not take effectuntil the next database restart.

01650 Index and table statistics are inconsistent.

01651 The event monitor was activated successfully, however some monitoringinformation may be lost.

01652 The isolation clause is ignored because of the statement context.

01653 The authorizations were granted to USER. Groups were not consideredbecause the authorization name is more than 8 bytes.

01654 The buffer pool is not started.

01655 The event monitor was created successfully but at least one eventmonitor target table already exists.

01657 The bufferpool operation will not take effect until the next databasestartup.



SQLSTATEValue

Meaning

01H51 An MQSeries Application Messaging Interface message was truncated.

01HXX Valid warning SQLSTATEs returned by a user-defined function orexternal procedure CALL.

Class Code 02 No Data

Table 4. Class Code 02: No Data

SQLSTATEValue

Meaning

02000 One of the following exceptions occurred:v The result of the SELECT INTO statement or the subselect of the

INSERT statement was an empty table.v The number of rows identified in the searched UPDATE or DELETE

statement was zero.v The position of the cursor referenced in the FETCH statement was

after the last row of the result table.

02501 The cursor position is not valid for a FETCH of the current row.

02502 Delete or update hole detected

Class Code 07 Dynamic SQL Error

Table 5. Class Code 07: Dynamic SQL Error

SQLSTATEValue

Meaning

07001 The number of host variables is not correct for the number of parametermarkers.

07002 The call parameter list or control block is invalid.

07003 The statement identified in the EXECUTE statement is a select-statement,or is not in a prepared state.

07004 The USING clause or the INTO clause is required for dynamicparameters.

07005 The statement name of the cursor identifies a prepared statement thatcannot be associated with a cursor.

07006 An input host variable cannot be used, because of its data type.


Class Code 08 Connection Exception

Table 6. Class Code 08: Connection Exception

SQLSTATEValue

Meaning

08001 The application requester is unable to establish the connection.

08002 The connection already exists.

08003 The connection does not exist.

08004 The application server rejected establishment of the connection.

08007 Transaction resolution unknown.

08502 The CONNECT statement issued by an application process running witha SYNCPOINT of TWOPHASE has failed, because no transactionmanager is available.

08504 An error was encountered while processing the specified path renameconfiguration file.

Class Code 09 Triggered Action Exception

Table 7. Class Code 09: Triggered Action Exception

SQLSTATEValue

Meaning

09000 A triggered SQL statement failed.

Class Code 0A Feature Not Supported

Table 8. Class Code 0A: Feature Not Supported

SQLSTATEValue

Meaning

0A001 The CONNECT statement is invalid, because the process is not in theconnectable state.

0A502 The action or operation is not enabled for this database instance.

0A503 Federated insert, update, or delete operation cannot be compiled becauseof potential data inconsistency.


Class Code 0D Invalid Target Type Specification

Table 9. Class Code 0D: Invalid Target Type Specification

SQLSTATEValue

Meaning

0D000 The target structured data type specification is a proper subtype of thesource structured data type.

Class Code 0F Invalid Token

Table 10. Class Code 0F: Invalid Token

SQLSTATEValue

Meaning

0F001 The LOB token variable does not currently represent any value.

Class Code 0K Invalid RESIGNAL statement

Table 11. Class Code 0K: Invalid RESIGNAL statement

SQLSTATEValue

Meaning

0K000 RESIGNAL statement is not within a handler.

Class Code 20 Case Not Found for Case Statement

Table 12. Class Code 20: Case Not Found for Case Statement

SQLSTATEValue

Meaning

20000 The case was not found for the CASE statement.

Class Code 21 Cardinality Violation

Table 13. Class Code 21: Cardinality Violation

SQLSTATEValue

Meaning

21000 The result of a SELECT INTO is a result table of more than one row, orthe result of the subquery of a basic predicate is more than one value.

21501 A multiple-row INSERT into a self-referencing table is invalid.


Table 13. Class Code 21: Cardinality Violation (continued)

SQLSTATEValue

Meaning

21502 A multiple-row UPDATE of a primary key is invalid.

21504 A multiple-row DELETE from a self-referencing table with a delete ruleof RESTRICT or SET NULL is invalid.

21505 A row function must return not more than one row.

Class Code 22 Data Exception

Table 14. Class Code 22: Data Exception

SQLSTATEValue

Meaning

22001 Character data, right truncation occurred; for example, an update orinsert value is a string that is too long for the column, or a datetimevalue cannot be assigned to a host variable, because it is too small.

22002 A null value, or the absence of an indicator parameter was detected; forexample, the null value cannot be assigned to a host variable, because noindicator variable is specified.

22003 A numeric value is out of range.

22004 A null value cannot be returned either from a procedure defined asPARAMETER STYLE GENERAL, or from a type-preserving methodinvoked with a non-null argument.

22007 An invalid datetime format was detected; that is, an invalid stringrepresentation or value was specified.

22008 Datetime field overflow occurred; for example, an arithmetic operationon a date or timestamp has a result that is not within the valid range ofdates.

2200G The most specific type does not match.

22011 A substring error occurred; for example, an argument of SUBSTR is outof range.

22012 Division by zero is invalid.

22018 The character value for the CAST, DECIMAL, FLOAT, or INTEGERscalar function is invalid.

22019 The LIKE predicate has an invalid escape character.

22021 A character is not in the coded character set.

22024 A NUL-terminated input host variable or parameter did not contain aNUL.


Table 14. Class Code 22: Data Exception (continued)

SQLSTATEValue

Meaning

22025 The LIKE predicate string pattern contains an invalid occurrence of anescape character.

2202D Null instance used with a mutator method.

22501 The length control field of a variable length string is negative or greaterthan the maximum.

22504 A mixed data value is invalid.

22506 A reference to a datetime special register is invalid, because the TODclock is malfunctioning or the operating system timezone parameter isout of range.

22522 A CCSID value is not valid at all, not valid for the data type or subtype,or not valid for the encoding scheme.

22526 A key transform function generated no rows or duplicate rows.

22527 Invalid input data detected for a multiple row INSERT operation.

Class Code 23 Constraint Violation

Table 15. Class Code 23: Constraint Violation

SQLSTATEValue

Meaning

23001 The update or delete of a parent key is prevented by a RESTRICT updateor delete rule.

23502 An insert or update value is null, but the column cannot contain nullvalues.

23503 The insert or update value of a foreign key is invalid.

23504 The update or delete of a parent key is prevented by a NO ACTIONupdate or delete rule.

23505 A violation of the constraint imposed by a unique index or a uniqueconstraint occurred.

23510 A violation of a constraint on the use of the command imposed by theRLST table occurred.

23511 A parent row cannot be deleted, because the check constraint restricts thedeletion.

23512 The check constraint cannot be added, because the table contains rowsthat do not satisfy the constraint definition.

23513 The resulting row of the INSERT or UPDATE does not conform to thecheck constraint definition.


Table 15. Class Code 23: Constraint Violation (continued)

SQLSTATEValue

Meaning

23514 Check data processing has found constraint violations.

23515 The unique index could not be created or unique constraint added,because the table contains duplicate values of the specified key.

23520 The foreign key cannot be defined, because all of its values are not equalto a parent key of the parent table.

23521 The update of a catalog table violates an internal constraint.

23522 The range of values for an identity column or sequence is exhausted.

Class Code 24 Invalid Cursor State

Table 16. Class Code 24: Invalid Cursor State

SQLSTATEValue

Meaning

24501 The identified cursor is not open.

24502 The cursor identified in an OPEN statement is already open.

24504 The cursor identified in the UPDATE, DELETE, SET, or GET statement isnot positioned on a row.

24506 The statement identified in the PREPARE is the statement of an opencursor.

24510 An UPDATE or DELETE operation was attempted against a delete holeor update hole.

24512 The result table does not agree with base table.

24513 FETCH NEXT, PRIOR, CURRENT or RELATIVE is not allowed becausethe cursor position is not known.

24514 A previous error has disabled this cursor.

24516 A cursor has already been assigned to a result set.

24517 A cursor was left open by an external function or method.

Class Code 25 Invalid Transaction State

Table 17. Class Code 25: Invalid Transaction State

SQLSTATEValue

Meaning

25000 An update operation is invalid for the application executionenvironment.


Table 17. Class Code 25: Invalid Transaction State (continued)

SQLSTATEValue

Meaning

25001 The statement is only allowed as the first statement in a unit of work.

25501 The statement is only allowed as the first statement in a unit of work.

Class Code 26 Invalid SQL Statement Identifier

Table 18. Class Code 26: Invalid SQL Statement Identifier

SQLSTATEValue

Meaning

26501 The statement identified does not exist.

Class Code 28 Invalid Authorization Specification

Table 19. Class Code 28: Invalid Authorization Specification

SQLSTATEValue

Meaning

28000 Authorization name is invalid.

Class Code 2D Invalid Transaction Termination

Table 20. Class Code 2D: Invalid Transaction Termination

SQLSTATEValue

Meaning

2D521 SQL COMMIT or ROLLBACK are invalid in the current operatingenvironment.

2D522 COMMIT and ROLLBACK are not allowed in an ATOMIC Compoundstatement.

2D528 Dynamic COMMIT is invalid for the application execution environment.

2D529 Dynamic ROLLBACK is invalid for the application executionenvironment.


Class Code 2E Invalid Connection Name

Table 21. Class Code 2E: Invalid Connection Name

SQLSTATEValue

Meaning

2E000 Connection name is invalid.

Class Code 34 Invalid Cursor Name

Table 22. Class Code 34: Invalid Cursor Name

SQLSTATEValue

Meaning

34000 Cursor name is invalid.

Class Code 36 Invalid Cursor Specification

Table 23. Class Code 36: Invalid Cursor Specification

SQLSTATEValue

Meaning

36001 A SENSITIVE cursor cannot be defined for the specified select-statement.

Class Code 38 External Function Exception

Table 24. Class Code 38: External Function Exception

SQLSTATEValue

Meaning

38XXX Valid error SQLSTATEs returned by an external routine, or trigger.

38001 The external routine is not allowed to execute SQL statements.

38002 The routine attempted to modify data, but the routine was not defined asMODIFIES SQL DATA.

38003 The statement is not allowed in a routine.

38004 The routine attempted to read data, but the routine was not defined asREADS SQL DATA.

38501 Error occurred while calling a user-defined function, external procedure,or trigger (using the SIMPLE CALL or SIMPLE CALL WITH NULLScalling convention).

38502 The external function is not allowed to execute SQL statements.

38503 A user-defined function has abnormally terminated (abend).


Table 24. Class Code 38: External Function Exception (continued)

SQLSTATEValue

Meaning

38504 A user-defined function has been interrupted by the user to stop aprobable looping condition.

38505 An SQL statement is not allowed in a routine on a FINAL CALL.

38506 Function failed with error from OLE DB provider.

38552 A function in the SYSFUN schema (supplied by IBM) has abnormallyterminated.

One of the following reason codes can be found in the message text:01 Numeric value out of range02 Division by zero03 Arithmetic overflow or underflow04 Invalid date format05 Invalid time format06 Invalid timestamp format07 Invalid character representation of a timestamp duration08 Invalid interval type (must be one of 1, 2, 4, 8, 16, 32, 64, 128,

256)09 String too long10 Length or position in string function out of range11 Invalid character representation of a floating point number

38553 A routine in a system schema has terminated with an error.

38H01 An MQSeries function failed to initialize.

38H02 MQSeries Application Messaging Interface failed to terminate the session.

38H03 MQSeries Application Messaging Interface failed to properly process amessage.

38H04 MQSeries Application Messaging Interface failed in sending a message.

38H05 MQSeries Application Messaging Interface failed to read/receive amessage.

38H06 An MQSeries Application Messaging Interface (un)subscription requestfailed.

Class Code 39 External Function Call Exception

Table 25. Class Code 39: External Function Call Exception

SQLSTATEValue

Meaning

39001 A user-defined function has returned an invalid SQLSTATE.

39004 A null value is not allowed for an IN or INOUT argument.


Table 25. Class Code 39: External Function Call Exception (continued)

SQLSTATEValue

Meaning

39501 The eye-catcher associated with an argument was modified.

Class Code 3B Invalid SAVEPOINT

Table 26. Class Code 3B: Invalid SAVEPOINT

SQLSTATEValue

Meaning

3B001 The savepoint is not valid.

3B002 The maximum number of savepoints has been reached.

3B501 A duplicate savepoint name was detected.

3B502 A RELEASE or ROLLBACK TO SAVEPOINT was specified, but asavepoint does not exist.

3B503 A SAVEPOINT, RELEASE SAVEPOINT, or ROLLBACK TO SAVEPOINTis not allowed in a trigger or global transaction.

Class Code 40 Transaction Rollback

Table 27. Class Code 40: Transaction Rollback

SQLSTATEValue

Meaning

40001 Deadlock or timeout with automatic rollback occurred.

40003 The statement completion is unknown.

40504 A system error has caused the unit of work to be rolled back.

40506 The current transaction was rolled back because of an SQL error.

40507 The current transaction was rolled back as a result of a failure creating anindex.

Class Code 42 Syntax Error or Access Rule Violation

Table 28. Class Code 42: Syntax Error or Access Rule Violation

SQLSTATEValue

Meaning

42501 The authorization ID does not have the privilege to perform the specifiedoperation on the identified object.


Table 28. Class Code 42: Syntax Error or Access Rule Violation (continued)

SQLSTATEValue

Meaning

42502 The authorization ID does not have the privilege to perform theoperation as specified.

42504 A specified privilege cannot be revoked from a specifiedauthorization-name.

42506 Owner authorization failure occurred.

42508 The specified database privileges cannot be granted to PUBLIC.

42509 SQL statement is not authorized, because of the STATICRULES option.

42511 Unable to retrieve a DATALINK value.

42601 A character, token, or clause is invalid or missing.

42602 A character that is invalid in a name has been detected.

42603 An unterminated string constant has been detected.

42604 An invalid numeric or string constant has been detected.

42605 The number of arguments specified for a scalar function is invalid.

42606 An invalid hexadecimal constant has been detected.

42607 An operand of a column function is invalid.

42608 The use of NULL or DEFAULT in VALUES is invalid.

42609 All operands of an operator or predicate are parameter markers.

42610 A parameter marker is not allowed.

42611 The column or argument definition is invalid.

42612 The statement string is an SQL statement that is not acceptable in thecontext in which it is presented.

42613 Clauses are mutually exclusive.

42614 A duplicate keyword is invalid.

42615 An invalid alternative was detected.

42617 The statement string is blank or empty.

42618 A host variable is not allowed.

42620 Read-only SCROLL was specified with the UPDATE clause.

42621 The check constraint is invalid.

42622 A name or label is too long.

42623 A DEFAULT clause cannot be specified.

42625 A CASE expression is invalid.

42627 RETURNS clause must be specified prior to predicate specification usingthe EXPRESSION AS clause.



SQLSTATEValue

Meaning

42628 A TO SQL or FROM SQL transform function is defined more than oncein a transform definition.

42629 Parameter names must be specified for SQL routines.

42630 An SQLSTATE or SQLCODE variable declaration must not be in a nestedcompound statement.

42631 A RETURN statement in an SQL function or method must include areturn value.

42701 A duplicate column name in an INSERT or UPDATE statement wasdetected.

42702 A column reference is ambiguous, because of duplicate names.

42703 An undefined column, attribute, or parameter name was detected.

42704 An undefined object or constraint name was detected.

42705 An undefined server-name was detected.

42707 A column name in ORDER BY does not identify a column of the resulttable.

42709 A duplicate column name in a PRIMARY, UNIQUE, or FOREIGN KEYclause was detected.

42710 A duplicate object or constraint name was detected.

42711 Duplicate column name or attribute name was detected in the objectdefinition or ALTER statement.

42712 A duplicate table designator was detected in the FROM clause.

42713 A duplicate object was detected in a list of objects.

42720 The nodename for the remote database was not found in the nodedirectory.

42723 A function with the same signature already exists in the schema.

42724 Unable to access an external program used for a user-defined function ora procedure.

42725 A function or method was referenced directly (not by either signature orby specific instance name), but there is more than one specific instance ofthat function or method.

42726 Duplicate names for named derived tables were detected.

42727 No default primary tablespace exists for the new table.

42728 A duplicate node was detected in the nodegroup definition.

42729 The node is not defined.

42730 The container name is already used by another tablespace.



SQLSTATEValue

Meaning

42731 The container name is already used by this tablespace.

42732 A duplicate schema name in the SET CURRENT PATH statement wasdetected.

42734 A duplicate parameter-name, SQL variable-name, cursor-name,condition-name, or label was detected.

42735 Nodegroup for the table space is not defined for the buffer pool.

42736 The label specified on the LEAVE statement is not found or not valid.

42737 The condition specified in the handler is not defined.

42738 A duplicate column name or unnamed column was specified in aDECLARE CURSOR statement of a FOR statement.

42739 A duplicate transform was detected.

42740 No transforms were found for the specified type. No transforms weredropped.

42741 A transform group is not defined for a data type.

42742 Subtable or subview of the same type already exists in the typed table ortyped view hierarchy.

42743 The search method is not found in the index extension.

42744 A TO SQL or FROM SQL transform function is not defined in atransform group.

42745 The routine would define an overriding relationship with an existingmethod.

42746 A method name cannot be the same as a structured type name within thesame type hierarchy.

42802 The number of insert or update values is not the same as the number ofcolumns.

42803 A column reference in the SELECT or HAVING clause is invalid, becauseit is not a grouping column; or a column reference in the GROUP BYclause is invalid.

42804 The result expressions in a CASE expression are not compatible.

42805 An integer in the ORDER BY clause does not identify a column of theresult table.

42806 A value cannot be assigned to a host variable, because the data types arenot compatible.

42807 The INSERT, UPDATE, or DELETE is not permitted on this object.

42808 A column identified in the INSERT or UPDATE statement is notupdateable.



SQLSTATEValue

Meaning

42809 The identified object is not the type of object to which the statementapplies.

42810 A view is identified in a FOREIGN KEY clause.

42811 The number of columns specified is not the same as the number ofcolumns in the SELECT clause.

42813 WITH CHECK OPTION cannot be used for the specified view.

42815 The data type, length, scale, value, or CCSID is invalid.

42816 A datetime value or duration in an expression is invalid.

42818 The operands of an operator or function are not compatible.

42819 An operand of an arithmetic operation or an operand of a function thatrequires a number is not a number.

42820 A numeric constant is too long, or it has a value that is not within therange of its data type.

42821 An update or insert value is not compatible with the column.

42823 Multiple columns are returned from a subquery that is allowed only onecolumn.

42824 An operand of LIKE is not a string, or the first operand is not a column.

42825 The rows of UNION, INTERSECT, EXCEPT, or VALUES do not havecompatible columns.

42826 The rows of UNION, INTERSECT, EXCEPT, or VALUES do not have thesame number of columns.

42827 The table identified in the UPDATE or DELETE is not the same tabledesignated by the cursor.

42828 The table designated by the cursor of the UPDATE or DELETE statementcannot be modified, or the cursor is read-only.

42829 FOR UPDATE OF is invalid, because the result table designated by thecursor cannot be modified.

42830 The foreign key does not conform to the description of the parent key.

42831 A column of a primary or unique key cannot allow null values.

42832 The operation is not allowed on system objects.

42834 SET NULL cannot be specified, because the foreign key does not allownull values.

42835 Cyclic references cannot be specified between named derived tables.

42836 The specification of a recursive, named derived table is invalid.



SQLSTATEValue

Meaning

42837 The column cannot be altered, because its attributes are not compatiblewith the current column attributes.

42838 An invalid use of a tablespace was detected.

42839 Indexes and long columns cannot be in separate tablespaces from thetable.

42840 An invalid use of the AS CAST option was detected.

42841 A parameter marker can not be a user-defined type or reference type.

42842 A column definition is invalid, because a specified option is inconsistentwith the column description.

42845 An invalid use of a VARIANT or EXTERNAL ACTION function wasdetected.

42846 Cast from source type to target type is not supported.

42852 The privileges specified in GRANT or REVOKE are invalid orinconsistent. (For example, GRANT ALTER on a view.)

42853 Both alternatives of an option were specified, or the same option wasspecificed more than once.

42854 A result column data type in the select list is not compatible with thedefined type in a typed view or materialized query table definition.

42855 The assignment of the LOB to this host variable is not allowed. Thetarget host variable for all fetches of this LOB value for this cursor mustbe a locator or a LOB variable.

42858 Operation cannot be applied to the specified object.

42863 An undefined host variable in REXX has been detected.

42866 The data type in either the RETURNS clause of the CAST FROM clausein the CREATE FUNCTION statement is not appropriate for the datatype returned from the sourced function or RETURN statement in thefunction body.

42872 FETCH statement clauses are incompatible with the cursor definition.

42875 The object to create within CREATE SCHEMA must have the samequalifier as the schema name.

42877 The column name cannot be qualified.

42878 An invalid function or procedure name was used with the EXTERNALkeyword.

42879 The data type of one or more input parameters in the CREATEFUNCTION statement is not appropriate for the corresponding data typein the source function.



SQLSTATEValue

Meaning

42880 The CAST TO and CAST FROM data types are incompatible, or wouldalways result in truncation of a fixed string.

42881 Invalid use of a row based function.

42882 The specific instance name qualifier is not equal to the function namequalifier.

42883 No function or method was found with a matching signature.

42884 No routine was found with the specified name and compatiblearguments.

42885 The number of input parameters specified on a CREATE FUNCTIONstatement does not match the number provided by the function named inthe SOURCE clause.

42886 The IN, OUT, or INOUT parameter attributes do not match.

42887 The function is not valid in the context where it occurs.

42888 The table does not have a primary key.

42889 The table already has a primary key.

42890 A column list was specified in the references clause, but the identifiedparent table does not have a unique constraint with the specified columnnames.

42891 A duplicate UNIQUE constraint already exists.

42893 The object or constraint cannot be dropped, because other objects aredependent on it.

42894 The DEFAULT value is invalid.

42895 For static SQL, an input host variable cannot be used, because its datatype is not compatible with the parameter of a procedure or user-definedfunction.

428A0 An error occurred with the sourced function on which the user-definedfunction is based.

428A1 Unable to access a file referenced by a host file variable.

428A2 A table cannot be assigned to a multi-node node group, because it doesnot have a partition key.

428A3 An invalid path has been specified for an event monitor.

428A4 An invalid value has been specified for an event monitor option.

428A5 An exception table named in a SET INTEGRITY statement either doesnot have the proper structure, or it has been defined with generatedcolumns, constraints, or triggers.



SQLSTATEValue

Meaning

428A6 An exception table named in a SET INTEGRITY statement cannot be thesame as one of the tables being checked.

428A7 There is a mismatch in the number of tables being checked and in thenumber of exception tables specified in the SET INTEGRITY statement.

428A8 Cannot reset the check-pending state using the SET INTEGRITYstatement on a descendent table while a parent table is in thecheck-pending state.

428A9 The node range is invalid.

428AA The column name is not a valid column for an event monitor table.

428B0 Illegal nesting inside ROLLUP, CUBE, or GROUPING SETS.

428B1 Incorrect number of table space container specifications that are notdesignated for specific nodes.

428B2 The path name for the container is not valid.

428B3 An invalid SQLSTATE was specified on RAISE_ERROR.

428B7 A number specified in an SQL statement is out of the valid range.

429BE The primary key or unique key is a subset of the columns in thedimensions clause.

428C0 The node cannot be dropped, because it is the only node in thenodegroup.

428C1 Only one ROWID column can be specified for a table.

428C2 Examination of the function body indicates that the given clause shouldhave been specified on the CREATE FUNCTION statement.

428C4 The number of elements on each side of the predicate operator is not thesame.

428C5 No data type mapping was found for a data type from the data source.

428C9 A ROWID column cannot be specified as the target column of an INSERTor UPDATE.

428CA A table in append mode cannot have a clustered index.

428CB The page size for a table space must match the page size of theassociated bufferpool.

428D1 Unable to access a file referenced by a DATALINK value.

428D4 A cursor specified in a FOR statement cannot be referenced in an OPEN,CLOSE, or FETCH statement.

428D5 The ending label does not match the beginning label.

428D6 UNDO is not allowed for NOT ATOMIC statements.



SQLSTATEValue

Meaning

428D7 The condition value is not allowed.

428D8 The declaration or use of the SQLSTATE or SQLCODE variable is notvalid.

428DB An object is not valid as a supertype, supertable, or superview.

428DC The function or method is not valid as the transform for this type.

428DD A required transform is not defined.

428DE PAGESIZE value is not supported.

428DF Data types specified in CREATE CAST are not valid.

428DG Function specified in CREATE CAST is not valid.

428DH Operation is not valid for typed tables.

428DJ Inherited column or attribute cannot be changed or dropped.

428DK The scope for the reference column is already defined.

428DL Parameter of external or sourced function has a scope defined.

428DM The scope table or view is not valid for the reference type.

428DN SCOPE is not specified in the RETURNS clause of an external function oris specified in the RETURNS clause of a sourced function.

428DP The type is not a structured type.

428DQ A subtable or subview cannot have a different schema name than itssupertable or superview.

428DR Operation cannot be applied to a sub-table.

428DS Index on the specified columns cannot be defined on subtable.

428DT Operand of expression is not a valid scoped reference type.

428DU A type is not included in the required type hierarchy.

428DV Invalid left operand of a dereference operator.

428DW Object identifier column cannot be referenced using the dereferenceoperator.

428DX Object identifier column is required to define the root table or root viewof a typed table or typed view hierarchy.

428DY Table statistics cannot be updated for a subtable.

428DZ An object identifier column cannot be updated.

428E0 Definition of index does not match the definition of the index extension.

428E1 Result of the range-producing table function is inconsistent with that ofthe key transformation table function for the index extension.



SQLSTATEValue

Meaning

428E2 Number or the type of key-target parameters does not match with thenumber or type of key transform function for the index extension.

428E3 Argument for function in index extension is not valid.

428E4 Function is not supported in CREATE INDEX EXTENSION statement.

428E5 SELECTIVITY clause can only be specified with a user-defined predicate.

428E6 The search argument of method in the user-defined predicate does notmatch the one in the corresponding search method of the indexextension.

428E7 Type of the operand following the comparison operator in theuser-defined predicate does not match the RETURNS data type.

428E8 A search target or search argument parameter does not match aparameter name of the function being created.

428E9 An argument parameter name cannot appear as both a search target andsearch argument in the same exploitation rule.

428EA A fullselect in a typed view is not valid.

428EB A column in a subview cannot be read only when the correspondingcolumn in the superview is updatable.

428EC The fullselect specified for the materialized query table is not valid.

428ED Structured types with Datalink or Reference type attributes cannot beconstructed.

428EE Option is not valid for this data source.

428EF Value for the option is not valid for this data source.

428EG Missing required option for this data source.

428EH Cannot ADD an option that is already defined.

428EJ Cannot SET or DROP an option that has not been ADDed.

428EK The qualifier for a declared global temporary table name must beSESSION.

428EL A transform function is not valid for use with a function or method.

428EM The TRANSFORM GROUP clause is required.

428EN A transform group is specified that is not used.

428EP A structured type cannot depend on itself either directly or indirectly.

428EQ The returns type of the routine is not the same as the subject type.

428ER A method specification cannot be dropped before the method body isdropped.



SQLSTATEValue

Meaning

428ES A method body does not correspond to the language type of the methodspecification.

428EU TYPE or VERSION is not specified in the server definition.

428EV Pass-through facility is not supported for the type of data source.

428EW The table cannot be converted to or from a materialized query table.

428EX Routine cannot be used as a transform function because it is either abuiltin function or a method.

428EY The data type of the search target in a user-defined predicate does notmatch the data type of the source key of the specified index extension.

428EZ A window specification for an OLAP function is not valid.

428F0 A ROW function must include at least two columns.

428F1 An SQL TABLE function must return a table result.

428F2 The data type of the RETURN statement value in an SQL proceduremust be INTEGER.

428F3 SCROLL and WITH RETURN are mutually exclusive.

428F4 The SENSITIVITY specified on FETCH is not allowed for the cursor.

428F6 Cursor is scrollable, but the result table involves output from a tablefunction.

428F7 An operation that applies only to SQL routines was attempted on anexternal routine.

428F9 A sequence expression cannot be specified in this context.

428FA The scale of the decimal number must be zero.

428FB The sequence-name must not be a sequence generated by the system foran identity column.

428FC The length of the encryption password is not valid.

428FD The password used for decryption does not match the password used toencrypt the data.

428FE The data is not a result of the ENCRYPT function.

428FF The buffer pool specification is not valid.

428FG The table used to define a staging table is not valid.

428FH The SET INTEGRITY option is not valid

428FI ORDER OF was specified, but the table-designator does not contain anORDER BY clause.

428FJ ORDER BY is not allowed in the outer fullselect of a view ormaterialized query table.



SQLSTATEValue

Meaning

428FP One INSTEAD OF trigger is allowed for each kind of operation on asubject view.

428FQ The view name of an INSTEAD OF trigger must not specify a view thatis defined using WITH CHECK OPTION (a symmetric view) or a viewon which a symmetric view has been defined directly or indirectly.

428FU Built-in type returned from the FROM SQL transform function or methoddoes not match the corresponding built-in type for the TO SQL transformfunction or method.

428FV Cannot define the method as an overriding method.

42901 A column function does not include a column name.

42903 A WHERE clause or SET clause includes an invalid reference, such as acolumn function.

42904 The SQL procedure was not created because of a compile error.

42907 The string is too long.

42908 The statement does not include a required column list.

42910 The statement is not allowed in a Compond statement.

42911 A decimal divide operation is invalid, because the result would have anegative scale.

42912 A column cannot be updated, because it is not identified in the UPDATEclause of the select-statement of the cursor.

42914 The DELETE is invalid, because a table referenced in a subquery can beaffected by the operation.

42915 An invalid referential constraint has been detected.

42916 The alias cannot be created, because it would result in a repetitive chainof aliases.

42917 The object cannot be explicitly dropped or altered.

42918 A user-defined data type cannot be created with a system-defined datatype name (for example, INTEGER).

42919 Nested compound statements are not allowed.

42921 Containers cannot be added to the tablespace.

42925 Recursive named derived tables cannot specify SELECT DISTINCT andmust specify UNION ALL.

42928 WITH EMPTY TABLE cannot be specified for the table.

42932 The program preparation assumptions are incorrect.

42939 The name cannot be used because the specified identifier is reserved forsystem use.



SQLSTATEValue

Meaning

42962 A long column, LOB column, or structured type column cannot be usedin an index, a key, or a constraint.

42968 The connection failed, because there is no current software license.

42969 The package was not created and the current unit of work was rolledback, because of internal limitations or an invalid section number.

42972 An expression in a join-condition references columns in more than one ofthe operand tables.

42985 The statement is not allowed in a routine.

42987 The statement is not allowed in a procedure or trigger.

42989 A GENERATED column that is based on an expression cannot be used ina BEFORE trigger.

42991 The BOOLEAN data type is currently only supported internally.

42993 The column, as defined, is too large to be logged.

42994 Raw device containers are not currently supported on this system.

42995 The requested function does not apply to global temporary tables.

42997 Capability is not supported by this version of the DB2 applicationrequester, DB2 application server, or the combination of the two.

429A0 A foreign key cannot reference a parent table defined as not loggedinitially.

429A1 Nodegroup is not valid for the table space.

429A9 SQL statement cannot be processed by DataJoiner.

429B2 Specified inline length value for the structured type or column is toosmall.

429B3 Object may not be defined on a subtable.

429B4 Data filter function cannot be a LANGUAGE SQL function.

429B5 Data type of instance parameter in index extension is not valid.

429B8 A routine defined with PARAMETER STYLE JAVA cannot have astructured type as a parameter or returns type.

429B9 DEFAULT or NULL cannot be used in an attribute assignment.

429BA The FEDERATED keyword must be used with a reference to a federateddatabase object.

429BB A data type specified for a parameter or variable is not supported in aSQL routine.

429BC There are multiple container actions in the ALTER TABLESPACEstatement.


Class Code 44 WITH CHECK OPTION Violation

Table 29. Class Code 44: WITH CHECK OPTION Violation

SQLSTATEValue

Meaning

44000 The INSERT or UPDATE is not allowed, because a resulting row doesnot satisfy the view definition.

Class Code 46 Java DDL

Table 30. Class Code 46: Java DDL

SQLSTATEValue

Meaning

46001 Java DDL - Invalid URL.

46002 Java DDL - Invalid jar name.

46003 Java DDL - Invalid class deletion.

46007 Java DDL - Invalid signature.

46008 Java DDL - Invalid method specification.

46103 A Java routine encountered a ClassNotFound exception.

46501 Java DDL - Optional component not implemented.

Class Code 51 Invalid Application State

Table 31. Class Code 51: Invalid Application State

SQLSTATEValue

Meaning

51002 The package corresponding to an SQL statement execution request wasnot found.

51003 Consistency tokens do not match.

51004 An address in the SQLDA is invalid.

51005 Thr previous system error has disabled this function.

51008 The release number of the precompiled program is not valid.

51015 An attempt was made to execute a section that was found to be in errorat bind time.

51017 The user is not logged on.

51021 SQL statements cannot be executed until the application process executesa rollback operation.


Table 31. Class Code 51: Invalid Application State (continued)

SQLSTATEValue

Meaning

51022 A CONNECT that specifies an authorization name is invalid when aconnection (either current or dormant) already exists to the server namedin that CONNECT statement.

51023 The database is already in use by another instance of the databasemanager.

51024 A view cannot be used, because it has been marked inoperative.

51025 An application in the XA transaction processing environment is notbound with SYNCPOINT TWOPHASE.

51026 An event monitor cannot be turned on, because its target path is alreadyin use by another event monitor.

51027 The IMMEDIATE CHECKED option of the SET INTEGRITY statement isnot valid since a table is a user maintained materialized query table or isnot in the check-pending state.

51028 A package cannot be used, because it is marked inoperative.

51030 The procedure referenced in a ALLOCATE CURSOR, or an ASSOCIATELOCATORS statement has not yet been called within the applicationprocess.

51034 A routine defined with MODIFIES SQL DATA is not valid in the contextin which it is invoked.

51035 A PREVVAL expression cannot be used because a value has not beengenerated for the sequence yet in this session.

51038 SQL statements may no longer be issued by the routine.

51039 The ENCRYPTION PASSWORD value is not set.

Class Code 53 Invalid Operand or Inconsistent Specification

Table 32. Class Code 53: Invalid Operand or Inconsistent Specification

SQLSTATEValue

Meaning

53040 The specified buffer pool does not exist on the specified databasepartition.


Class Code 54 SQL or Product Limit Exceeded

Table 33. Class Code 54: SQL or Product Limit Exceeded

SQLSTATEValue

Meaning

54001 The statement is too long or too complex.

54002 A string constant is too long.

54004 The statement has too many table names or too many items in a SELECTor INSERT list.

54006 The result of concatenation is too long.

54008 The key is too long, has too many columns, or a key column is too long.

54010 The record length of the table is too long.

54011 Too many columns were specified for a table or view.

54023 The limit for the number of parameters or arguments for a function or aprocedure has been exceeded.

54028 The maximum number of concurrent LOB handles has been reached.

54029 The maximum number of open directory scans has been reached.

54030 The maximum number of event monitors are already active.

54031 The maximum number of files have already been assigned the eventmonitor.

54032 The maximum size of a table has been reached.

54033 The maximum number of partitioning maps has been reached.

54034 The combined length of all container names for the tablespace is toolong.

54035 An internal object limit exceeded.

54036 The path name for the container is too long.

54037 The container map for the tablespace is too complicated.

54038 Maximum depth of nested routines or triggers was exceed.

54045 Maximum levels of a type hierarchy exceeded.

54046 The maximum allowable parameters is exceeded in an index extension.

54047 The maximum size of a table space is exceeded.

54048 A temporary table space with sufficient page size does not exist.

54049 Length of an instance of a structured type exceeds system limit.

54050 The maximum allowable attributes is exceeded in a structured type.

54052 The number of block pages for a buffer pool is too large for the size ofthe buffer pool.

54053 The value specified for BLOCKSIZE is not in the valid range.


Class Code 55 Object Not in Prerequisite State

Table 34. Class Code 55: Object Not in Prerequisite State

SQLSTATEValue

Meaning

55001 The database must be migrated.

55002 The explanation table is not defined properly.

55006 The object cannot be dropped, because it is currently in use by the sameapplication process.

55007 The object cannot be altered, because it is currently in use by the sameapplication process.

55009 The system attempted to write to a read-only file or a write-protecteddiskette.

55012 A clustering index already exists on the table.

55019 The table is in an invalid state for the operation.

55022 The file server is not registered with this database.

55023 An error occured calling a routine.

55024 The tablespace cannot be dropped, because data related to a table is alsoin another tablespace.

55025 The database must be restarted.

55026 A temporary tablespace cannot be dropped.

55031 The format of the error mapping file is incorrect.

55032 The CONNECT statement is invalid, because the database manager wasstopped after this application was started.

55033 An event monitor cannot be activated in the same unit of work in whichit is created or modified.

55034 The event monitor is in an invalid state for the operation.

55035 The table cannot be dropped, because it is protected.

55036 The node cannot be dropped, because it has not been removed from thepartitioning map.

55037 The partitioning key cannot be dropped, because the table is in amulti-node nodegroup.

55038 The nodegroup cannot be used, because it is being rebalanced.

55039 The access or state transition is not allowed, because the tablespace is notin an appropriate state.

55041 Containers cannot be added to a tablespace while a rebalance is inprogress.


Table 34. Class Code 55: Object Not in Prerequisite State (continued)

SQLSTATEValue

Meaning

55043 Attributes of a structured type cannot be altered when a typed table ortyped view based on the type exists.

55045 The SQL Archive (SAR) file for the routine cannot be created because anecessary component is not available at the server.

55046 The specified SQL archive does not match the target environment.

55047 A routine declared as NOT FEDERATED attempted to access a federatedobject.

55048 Encrypted data cannot be encrypted.

55049 The event monitor table is not properly defined.

55051 The ALTER BUFFERPOOL statement is currently in progress.

55054 Cannot define the method as an overriding method.

Class Code 56 Miscellaneous SQL or Product Error

Table 35. Class Code 56: Miscellaneous SQL or Product Error

SQLSTATEValue

Meaning

56031 The clause or scalar function is invalid, because mixed and DBCS dataare not supported on this system.

56033 The insert or update value of a long string column must be a hostvariable or NULL.

56038 The requested feature is not supported in this environment.

56084 LOB data is not supported in DRDA.

56091 Multiple errors occurred as a result of executing a compound SQLstatement.

56092 The type of authorization cannot be determined, because theauthorization name is both a user id and group id.

56095 A bind option is invalid.

56097 LONG VARCHAR and LONG VARGRAPHIC fields are not permitted inTABLESPACEs which are built on DEVICEs.

56098 An error occurred during implicit rebind or prepare.

56099 The REAL data type is not supported by the target database.

560A0 Action on a LOB value failed.

560AA The clause or scalar function is invalid, because UCS-2 is not supportedon this system.


Table 35. Class Code 56: Miscellaneous SQL or Product Error (continued)

SQLSTATEValue

Meaning

560AC Wrapper definition cannot be used for the specified type or version ofdata source.

560AF PREPARE statement is not supported when using gateway concentrator.

560B0 Invalid new size value for table space container resizing.

560B1 Invalid cursor specification in stored procedure.

560B7 For a multiple row INSERT, the usage of a sequence expression must bethe same for each row.

560BB For an INOUT parameter in a dynamically prepared CALL statement,the same host variable must be used in both the USING and INTOclauses.

560BC An error has occurred when accessing a file.

560BD A federated server received an unexpected error code from a data source.

560BF Encryption facility not available.

Class Code 57 Resource Not Available or Operator Intervention

Table 36. Class Code 57: Resource Not Available or Operator Intervention

SQLSTATEValue

Meaning

57001 The table is unavailable, because it does not have a primary index.

57003 The specified bufferpool has not been activated.

57007 The object cannot be used, because a DROP or ALTER is pending.

57009 Virtual storage or database resource is temporarily unavailable.

57011 Virtual storage or database resource is not available.

57012 A non-database resource is not available. This will not affect thesuccessful execution of subsequent statements.

57013 A non-database resource is not available. This will affect the successfulexecution of subsequent statements.

57014 Processing was canceled as requested.

57016 The table cannot be accessed, because it is inactive.

57017 Character conversion is not defined.

57019 The statement was not successful, because of a problem with a resource.

57020 The drive containing the database is locked.

57021 The diskette drive door is open.


Table 36. Class Code 57: Resource Not Available or Operator Intervention (continued)

SQLSTATEValue

Meaning

57022 The table could not be created, because the authorization ID of thestatement does not own any suitable dbspaces.

57030 Connection to application server would exceed the installation-definedlimit.

57032 The maximum number of concurrent databases have already beenstarted.

57033 Deadlock or timeout occurred without automatic rollback.

57036 The transaction log does not belong to the current database.

57046 A new transaction cannot start because the database or instance isquiesced.

57047 An internal database file cannot be created, because the directory is notaccessible.

57048 An error occurred while accessing a container for a tablespace.

57049 The operating system process limit has been reached.

57050 The file server is not currently available.

57051 The estimated CPU cost exceeds the resource limit.

57052 Node is unavailable, because it does not have containers for alltemporary table spaces.

57053 The operation cannot be performed on the table because of conflictingoperations.

57055 A temporary table space with sufficient page size was not available.

57056 Package is not available because the database is in NO PACKAGE LOCKmode.

57057 The SQL statement cannot be executed due to a prior condition in aDRDA chain of SQL statements.

57059 There is not enough space in the table space for the specified action.

Class Code 58 System Error

Table 37. Class Code 58: System Error

SQLSTATEValue

Meaning

58004 A system error (that does not necessarily preclude the successfulexecution of subsequent SQL statements) occurred.


Table 37. Class Code 58: System Error (continued)

SQLSTATEValue

Meaning

58005 A system error (that prevents the successful execution of subsequent SQLstatements) occurred.

58008 Execution failed due to a distribution protocol error that will not affectthe successful execution of subsequent DDM commands or SQLstatements.

58009 Execution failed due to a distribution protocol error that causeddeallocation of the conversation.

58010 Execution failed due to a distribution protocol error that will affect thesuccessful execution of subsequent DDM commands or SQL statements.

58011 The DDM command is invalid while the bind process in progress.

58012 The bind process with the specified package name and consistency tokenis not active.

58014 The DDM command is not supported.

58015 The DDM object is not supported.

58016 The DDM parameter is not supported.

58017 The DDM parameter value is not supported.

58018 The DDM reply message is not supported.

58023 A system error has caused the current program to be canceled.

58030 An I/O error has occurred.

58031 The connection was unsuccessful, because of a system error.

58032 Unable to use the process for a fenced mode user-defined function.

58034 An error was detected while attempting to find pages for an object in aDMS tablespace.

58035 An error was detected while attempting to free pages for an object in aDMS tablespace.

58036 The internal tablespace ID specified does not exist.



Appendix A. Communications Errors

If your application returns an sqlcode of -30081, it means that acommunications error has been detected. The actual error encountered by thecommunication subsystem is returned in the list of error tokens for the 30081error message. The following lists possible communications errors that can bereturned.

The error codes are grouped by protocol as follows:v “TCP/IP”v “APPC” on page 595v “NETBIOS” on page 596

TCP/IP

When using TCP/IP in a Unix environment, the following table lists some ofthe errnos which the user may encounter most frequently. It is NOT acomplete list of errors. Errnos can be found in the file /usr/include/sys/errno.h.On Linux, the errnos are located in /usr/include/asm/errno.h. The errnonumber itself is indicated for each operating system.

Table 38. Unix TCP/IP errnos.

ErrnoErrno Number

DescriptionAIX HP-UX Solaris Linux

EINTR 4 4 4 4 Interrupted system call.

EAGAIN 11 11 11 11Resource temporarilyunavailable.

EBUSY 16 16 16 16 Resource busy.

EMFILE 24 24 24 24The per-process filedescriptor table is full.

EPIPE 32 32 32 32 Broken pipe.

EADDRINUSE 67 226 125 98The specified address isalready in use.

ENETDOWN 69 228 127 100 The network is down.

ENETUNREACH 70 229 128 101No route to the networkis available.

ENETRESET 71 230 129 102The network has droppedthe connection on reset.


Table 38. Unix TCP/IP errnos. (continued)

ErrnoErrno Number

DescriptionAIX HP-UX Solaris Linux

ECONNRESET 73 232 131 104Connection has been resetby the partner.

ENOBUFS 74 233 132 105

Insufficient buffer spaceresources were availablein the system to completethe call.

ENOTCONN 76 235 134 107The socket is notconnected.

ETIMEDOUT 78 238 145 110 The connection timed out.

ECONNREFUSED 79 239 146 111

The connection has beenrefused. If you are tryingto connect to thedatabase, check that thedatabase manager andTCP/IP protocol supportat the server have beenstarted successfully.

If using SOCKS protocolsupport, also ensure thatTCP/IP protocol supportat the SOCKS server hasbeen started successfully.

EHOSTDOWN 80 241 147 112 The host is down.

EHOSTUNREACH 81 242 148 113No route to the host isavailable.

For more information on Unix TCP/IP communication errors, refer to thetechnical reference manuals for the appropriate operating system. You can alsoissue the following command:

man function-name

where function-name represents the name of the function that returned anerror. The man pages might provide you with additional information abouterrors returned by specific functions.

When using TCP/IP on a Windows operating system, the following is a list oferror codes which the user may encounter most frequently. It is NOT acomplete list of errors. Errors returned by WSAGetLastError() can be found inthe file winsock2.h. This file may not be installed on your system if you donot have a development environment installed. Detailed information about


errors returned by specific functions are documented in the Windows Sockets2 Application Programming Interface. You can get a copy of this specificationfrom the following website: http://www.sockets.com/winsock2.htm#Docs.v WSAEINVAL (10022): Invalid argument. It can also mean that the current

state of the socket is not compatible with the TCP function being called, orthe socket may no longer be valid.

v WSAEMFILE (10024): Too many open files. Too many open sockets. Eachimplementation may have a maximum number of socket handles available,either globally, per process, or per thread.

v WSAEWOULDBLOCK (10035): Resource temporarily unavailable. This erroris returned from operations on non-blocking sockets that cannot becompleted immediately.

v WSAEINPROGRESS (10036): A blocking Windows Sockets operation is inprogress. Windows Sockets only allows a single blocking operation to beoutstanding per task (or thread), and if any other function call is made, thefunction fails with WSAEINPROGRESS.

v WSAENOPROTOOPT (10042): Bad protocol option. An unknown, invalid,or unsupported option or level was specified in a getsockopt() orsetsockopt() call.

v WSAEADDRINUSE (10048): Address already in use. Only one usage ofeach socket address (protocol/IP address/port) is normally permitted. Thiserror occurs if an application attempts to bind() a socket to an IPaddress/port that has already been used for an existing socket, or a socketthat wasn’t closed properly, or one that is still in the process of closing.

v WSAENETDOWN (10050): Network is down. A socket operationencountered a dead network. This could indicate a serious failure of thenetwork system (i.e. the protocol stack that the WinSock DLL runs over),the network interface, or the local network itself.

v WSAENETUNREACH (10051): Network is unreachable. A socket operationwas attempted to an unreachable network. This usually means the localsoftware knows no route to reach the remote host.

v WSAENETRESET (10052): Network dropped connection on reset. Theconnection has been broken due to “keep-alive” activity detecting a failurewhile the operation was in progress. May also be returned by stsockopt() ifan attempt is made to set SO_KEEPALIVE on a connection that has alreadyfailed.

v WSAECONNABORTED (10053): Software caused connection abort. Anestablished connection was aborted by the software on your machine,possibly due to a data transmission timeout or protocol error.

v WSAECONNRESET (10054): Connection reset by peer. An existingconnection was forcibly closed by the remote peer. This normally results ifthe peer application on the remote machine is suddenly stopped, themachine is rebooted, or the peer application used a ″hard close″ on the

Appendix A. Communications Errors 593

http://www.sockets.com/winsock2.htm#Docs

remote socket. This error may also result if a connection was broken due to“keep-alive” activity detecting a failure while one or more operations are inprogress. Operations in progress fail with WSAENETRESET. Subsequentoperations fail with WSAECONNRESET.

v WSAENOBUFS (10055): No buffer space available. An operation on a socketcould not be performed because the system lacked sufficient buffer space orbecause a queue was full.

v WSAENOTCONN (10057): The socket is not connected.v WSAETIMEDOUT (10060): Connection timed out. A connection attempt

failed because the connected party did not properly respond after a periodof time.

v WSAECONNREFUSED (10061): The connection has been refused. If you aretrying to attach to the instance or connect to the database, check that thedatabase manager and TCP/IP protocol support at the server has beenstarted successfully.

v WSAEHOSTUNREACH (10065): No route to host. A socket operation wasattempted to an unreachable machine.

v WSASYSNOTREADY (10091): The underlying network subsystem is notready for network communication. User should check that the appropriateWindows Sockets DLL is in the current path and that they are not trying touse more than one WinSock implementation simultaneously. If there is morethan one WinSock DLL on you system, be sure the first one in the path isappropriate for the network subsystem currently loaded and that allnecessary components are currently installed and configured correctly.

v WSAVERNOTSUPPORTED (10092): The version of Windows Sockets APIsupport requested is not provided by this particular Windows Socketsimplementation. Check that no old Windows Sockets DLL files are beingaccessed.

v WSA_E_NO_MORE (10110), WSAENOMORE (10102): There is no moredata available. In Windows Sockets Version 2, conflicting error codes aredefined for WSAENOMORE and WSA_E_NO_MORE. The error codeWSAENOMORE will be removed in a future version and onlyWSA_E_NO_MORE will remain.

v WSAHOST_NOT_FOUND (11001): Host not found.v WSATRY_AGAIN (11002): Host not found. Request to retrieve the

hostname’s IP address from the name server failed because the localmachine did not receive a response from the name server.

v WSANO_DATA (11004): Valid name, no data record of requested type. Thename server or hosts file does not recognize the hostname, or the servicename is not specified in the services file.

For more information on TCP/IP communication errors under Windows, referto the Windows Sockets documentation.


APPC

Below is a list of CPI-C function return codes which the user may encountermost frequently. It is NOT a complete list of return codes. The number inparentheses indicates the defined number corresponding to the return code.v CM_ALLOCATE_FAILURE_NO_RETRY (1): Allocation failed because of a

non-temporary condition. For example, the session cannot be activated dueto a system definition error or session-activation protocol error. This returncode is also returned when the session is deactivated because of a sessionprotocol error before the conversation can be allocated.

v CM_ALLOCATE_FAILURE_RETRY (2): Allocation failed because of atemporary condition. For example, the session cannot be activated due to atemporary lack of resources at the local system or remote system.

v CM_CONVERSATION_TYPE_MISMATCH (3): Allocation failed because theremote program does not support the conversation type in the allocationrequest. This is likely a problem with the TP at the server. Ensure that theTP at the server is configured to support a conversation type of basic.

v CM_TPN_NOT_RECOGNIZED (9): This error occurs when the allocaterequest is sent to the remote system. It indicates that the remote systemdoes not recognize the transaction program name specified in the request. Ifyou are not using global directory services, ensure that the TP namespecified in the CPI-C Side Information profile at the client, matches the TPname specified at the server. If you are using global directory services,request your database administrator’s help to ensure that the TP namespecified in the global directory entry matches the TP name specified at theserver.

v CM_TP_NOT_AVAILABLE_NO_RETRY (10): This error occurs when theallocate request is sent to the remote system. It indicates that the remote LUrecognizes the TP name sent, but cannot start the program. Also check thatthe userid specified in the TPN profile at the server is valid.

v CM_TP_NOT_AVAILABLE_RETRY (11): This error occurs when the allocaterequest is sent to the remote system. It indicates that the remote LUrecognizes the TP name sent, but for some reason which may be temporary,it cannot start the program. Ensure that the database manager and APPCprotocol support at the server have been started successfully.

v CM_DEALLOCATED_ABEND (17): This error occurs when the remoteprogram deallocates the conversation. This can occur if the remote programhas abnormally terminated, or has encountered a fatal error condition.

v CM_PRODUCT_SPECIFIC_ERROR (20): A product-specific error has beendetected, and a description of the error has been stored in the product’ssystem error log. Check that the local APPC subsystem has been startedsuccessfully. For Communication Server for AIX, to get more information


about a product-specific error, it is necessary to check the value of theglobal variable errno. See the section below for more information onpossible errnos that can be returned.

v CM_RESOURCE_FAILURE_NO_RETRY (26): This error occurs when theconversation terminates prematurely (on either the remote or local end)from an error related to resources (such as sessions or links).

v CM_RESOURCE_FAILURE_RETRY (27): This error occurs when theconversation terminates prematurely (on either the remote or local end) forabout the same reason as the NO_RETRY condition described above. Theonly difference is that the error may not be permanent.

For the most part, CPI Communications return codes are enough to deducethe cause of the error. But when CM_PRODUCT_SPECIFIC_ERROR isreturned, additional information is provided.

For Communication Server for AIX, the errno provides additional information.Below is a list of some of the more common errnos. It is NOT a complete list.Errnos numbered 101 and higher can be found in the file/usr/include/luxsna.h, which contains the Communication Server for AIXspecific errnos. Most of these errnos are translated to CPI-C return codes.Lower-numbered errnos are related to AIX problems and can be found in thefile /usr/include/sys/errno.h. The errno number itself is in parentheses.v EBADF (9): This is a ″bad file descriptor″ error. If this error occurs when

trying to connect to the database, it usually means that the SNA subsystemat the server has not been started, or that there is some problem with theSNA configuration profiles. Check that the SNA subsystem at the server hasbeen started. Check that the link station to the server node can be activated.

v EACCESS (13): This is a ″permission denied″ error. If this error occurs whentrying to connect to the database, it usually means that there is someproblem with the SNA configuration profiles.

On HP-UX, for SNAPlus2, please refer to the /usr/include/sys/errno.h filefor a description of the error.

For more information on CPI Communications errors, refer to SystemsApplication Architecture Common Programming Interface CommunicationsReference.

NETBIOS

When using NetBIOS, the following is a list of hexadecimal return codes thatthe user may encounter most frequently. It is NOT a complete list of returncodes.01 Invalid buffer length03 Invalid command


05 Command timed out06 Message incomplete07 Data not received08 Invalid local session number09 No resource available0A Session closed

This error could be caused by one of the following:v The database agent at the server was forced off by the system

administrator.v A database agent could not be started at the server because the

maxagents database manager configuration parameter has beenexceeded. Check the First Failure Service Log (DB2DIAG.LOG) atthe server to see if an error message has been logged.

v The database agent at the server was terminated due to anabnormal termination of a key database manager process.

0B Command cancelled0D Duplicate name used on the network. Ensure that the nname

parameter defined in the database manager configuration file isunique on the network.

0E Name table full0F Command completed (name has active sessions and is now

deregistered)11 Local session table full12 Session open rejected13 Invalid name number14 Remote name not found

If this error occurs when trying to connect to the database, ensurethat:v The database manager has been successfully started at the server,

and NetBIOS support has also been successfully started.v The server nname specified in the NETBIOS node entry at the

client, matches the workstation name specified in the databasemanager configuration file at the server.

15 Local name not found16 Name in use on remote node17 Name deleted18 Session ended abnormally19 Name conflict detected21 Interface busy22 Too many commands outstanding23 Invalid adapter24 Command already completed26 Command invalid to cancel30 Name defined by another environment


34 Environment not defined, RESET must be issued35 Required operating system resources exhausted, retry later36 Max applications exceeded37 No SAPs available38 Requested resources not available39 Invalid NCB address3A Invalid reset3B Invalid NCB DD ID3C Segment lock unsuccessful3F Device driver open error.40 OS error detected4F Perm ring statusF6 Unexpected CCB errorF8 Adapter open errorF9 Adapter support software internal errorFA Adapter checkFB NetBIOS not operationalFC Open failuresFD Unexpected adapter closeFF Command in process

For more information on NetBIOS return codes, refer to the Local AreaNetwork technical reference.


Appendix B. DB2 Universal Database technical information

Overview of DB2 Universal Database technical information

DB2 Universal Database technical information can be obtained in thefollowing formats:v Books (PDF and hard-copy formats)v A topic tree (HTML format)v Help for DB2 tools (HTML format)v Sample programs (HTML format)v Command line helpv Tutorials

This section is an overview of the technical information that is provided andhow you can access it.

FixPaks for DB2 documentationIBM may periodically make documentation FixPaks available. DocumentationFixPaks allow you to update the information that you installed from the DB2HTML Documentation CD as new information becomes available.

Note: If you do install documentation FixPaks, your HTML documentationwill contain more recent information than either the DB2 printed oronline PDF manuals.

Categories of DB2 technical informationThe DB2 technical information is categorized by the following headings:v Core DB2 informationv Administration informationv Application development informationv Business intelligence informationv DB2 Connect informationv Getting started informationv Tutorial informationv Optional component informationv Release notes

The following tables describe, for each book in the DB2 library, theinformation needed to order the hard copy, print or view the PDF, or locatethe HTML directory for that book. A full description of each of the books in


the DB2 library is available from the IBM Publications Center atwww.ibm.com/shop/publications/order

The installation directory for the HTML documentation CD differs for eachcategory of information:htmlcdpath/doc/htmlcd/%L/category

where:v htmlcdpath is the directory where the HTML CD is installed.v %L is the language identifier. For example, en_US.v category is the category identifier. For example, core for the core DB2

information.

In the PDF file name column in the following tables, the character in the sixthposition of the file name indicates the language version of a book. Forexample, the file name db2d1e80 identifies the English version of theAdministration Guide: Planning and the file name db2d1g80 identifies theGerman version of the same book. The following letters are used in the sixthposition of the file name to indicate the language version:

Language IdentifierArabic wBrazilian Portuguese bBulgarian uCroatian 9Czech xDanish dDutch qEnglish eFinnish yFrench fGerman gGreek aHungarian hItalian iJapanese jKorean kNorwegian nPolish pPortuguese vRomanian 8Russian rSimp. Chinese cSlovakian 7Slovenian l



Spanish zSwedish sTrad. Chinese tTurkish m

No form number indicates that the book is only available online and does nothave a printed version.

Core DB2 informationThe information in this category covers DB2 topics that are fundamental to allDB2 users. You will find the information in this category useful whether youare a programmer, a database administrator, or you work with DB2 Connect,DB2 Warehouse Manager, or other DB2 products.

The installation directory for this category is doc/htmlcd/%L/core.

Table 39. Core DB2 information

Name Form Number PDF File Name

IBM DB2 Universal DatabaseCommand Reference

SC09-4828 db2n0x80

IBM DB2 Universal DatabaseGlossary

No form number db2t0x80

IBM DB2 Universal DatabaseMaster Index

SC09-4839 db2w0x80

IBM DB2 Universal DatabaseMessage Reference, Volume 1

GC09-4840 db2m1x80

IBM DB2 Universal DatabaseMessage Reference, Volume 2

GC09-4841 db2m2x80

IBM DB2 Universal DatabaseWhat’s New

SC09-4848 db2q0x80

Administration informationThe information in this category covers those topics required to effectivelydesign, implement, and maintain DB2 databases, data warehouses, andfederated systems.

Appendix B. DB2 Universal Database technical information 601

The installation directory for this category is doc/htmlcd/%L/admin.

Table 40. Administration information

Name Form number PDF file name

IBM DB2 Universal DatabaseAdministration Guide:Planning

SC09-4822 db2d1x80

IBM DB2 Universal DatabaseAdministration Guide:Implementation

SC09-4820 db2d2x80

IBM DB2 Universal DatabaseAdministration Guide:Performance

SC09-4821 db2d3x80

IBM DB2 Universal DatabaseAdministrative API Reference

SC09-4824 db2b0x80

IBM DB2 Universal DatabaseData Movement Utilities Guideand Reference

SC09-4830 db2dmx80

IBM DB2 Universal DatabaseData Recovery and HighAvailability Guide andReference

SC09-4831 db2hax80

IBM DB2 Universal DatabaseData Warehouse CenterAdministration Guide

SC27-1123 db2ddx80

IBM DB2 Universal DatabaseFederated Systems Guide

GC27-1224 db2fpx80

IBM DB2 Universal DatabaseGuide to GUI Tools forAdministration andDevelopment

SC09-4851 db2atx80

IBM DB2 Universal DatabaseReplication Guide and Reference

SC27-1121 db2e0x80

IBM DB2 Installing andAdministering a SatelliteEnvironment

GC09-4823 db2dsx80

IBM DB2 Universal DatabaseSQL Reference, Volume 1

SC09-4844 db2s1x80

IBM DB2 Universal DatabaseSQL Reference, Volume 2

SC09-4845 db2s2x80

IBM DB2 Universal DatabaseSystem Monitor Guide andReference

SC09-4847 db2f0x80


Application development informationThe information in this category is of special interest to application developersor programmers working with DB2. You will find information aboutsupported languages and compilers, as well as the documentation required toaccess DB2 using the various supported programming interfaces, such asembedded SQL, ODBC, JDBC, SQLj, and CLI. If you view this informationonline in HTML you can also access a set of DB2 sample programs in HTML.

The installation directory for this category is doc/htmlcd/%L/ad.

Table 41. Application development information


IBM DB2 Universal DatabaseApplication DevelopmentGuide: Building and RunningApplications

SC09-4825 db2axx80

IBM DB2 Universal DatabaseApplication DevelopmentGuide: Programming ClientApplications

SC09-4826 db2a1x80

IBM DB2 Universal DatabaseApplication DevelopmentGuide: Programming ServerApplications

SC09-4827 db2a2x80

IBM DB2 Universal DatabaseCall Level Interface Guide andReference, Volume 1

SC09-4849 db2l1x80

IBM DB2 Universal DatabaseCall Level Interface Guide andReference, Volume 2

SC09-4850 db2l2x80

IBM DB2 Universal DatabaseData Warehouse CenterApplication Integration Guide

SC27-1124 db2adx80

IBM DB2 XML ExtenderAdministration andProgramming

SC27-1234 db2sxx80

Business intelligence informationThe information in this category describes how to use components thatenhance the data warehousing and analytical capabilities of DB2 UniversalDatabase.


The installation directory for this category is doc/htmlcd/%L/wareh.

Table 42. Business intelligence information


IBM DB2 Warehouse ManagerInformation Catalog CenterAdministration Guide

SC27-1125 db2dix80

IBM DB2 Warehouse ManagerInstallation Guide

GC27-1122 db2idx80

DB2 Connect informationThe information in this category describes how to access host or iSeries datausing DB2 Connect Enterprise Edition or DB2 Connect Personal Edition.

The installation directory for this category is doc/htmlcd/%L/conn.

Table 43. DB2 Connect information


APPC, CPI-C, and SNA SenseCodes

No form number db2apx80

IBM Connectivity Supplement No form number db2h1x80

IBM DB2 Connect QuickBeginnings for DB2 ConnectEnterprise Edition

GC09-4833 db2c6x80

IBM DB2 Connect QuickBeginnings for DB2 ConnectPersonal Edition

GC09-4834 db2c1x80

IBM DB2 Connect User’sGuide

SC09-4835 db2c0x80

Getting started informationThe information in this category is useful when you are installing andconfiguring servers, clients, and other DB2 products.

The installation directory for this category is doc/htmlcd/%L/start.

Table 44. Getting started information


IBM DB2 Universal DatabaseQuick Beginnings for DB2Clients

GC09-4832 db2itx80


Table 44. Getting started information (continued)


IBM DB2 Universal DatabaseQuick Beginnings for DB2Servers

GC09-4836 db2isx80

IBM DB2 Universal DatabaseQuick Beginnings for DB2Personal Edition

GC09-4838 db2i1x80

IBM DB2 Universal DatabaseInstallation and ConfigurationSupplement

GC09-4837 db2iyx80

IBM DB2 Universal DatabaseQuick Beginnings for DB2Data Links Manager

GC09-4829 db2z6x80

Tutorial informationTutorial information introduces DB2 features and teaches how to performvarious tasks.

The installation directory for this category is doc/htmlcd/%L/tutr.

Table 45. Tutorial information


Business Intelligence Tutorial:Introduction to the DataWarehouse

No form number db2tux80

Business Intelligence Tutorial:Extended Lessons in DataWarehousing

No form number db2tax80

Development Center Tutorialfor Video Online usingMicrosoft Visual Basic

No form number db2tdx80

Information Catalog CenterTutorial

No form number db2aix80

Video Central for e-businessTutorial

No form number db2twx80

Visual Explain Tutorial No form number db2tvx80

Optional component informationThe information in this category describes how to work with optional DB2components.


The installation directory for this category is doc/htmlcd/%L/opt.

Table 46. Optional component information


IBM DB2 Life Sciences DataConnect Planning, Installation,and Configuration Guide

GC27-1235 db2lsx80

IBM DB2 Spatial ExtenderUser’s Guide and Reference

SC27-1226 db2sbx80

IBM DB2 Universal DatabaseData Links ManagerAdministration Guide andReference

SC27-1221 db2z0x80

IBM DB2 Universal DatabaseNet Search ExtenderAdministration andProgramming GuideNote: HTML for thisdocument is not installedfrom the HTMLdocumentation CD.

SH12-6740 N/A

Release notesThe release notes provide additional information specific to your product’srelease and FixPak level. They also provides summaries of the documentationupdates incorporated in each release and FixPak.

Table 47. Release notes


DB2 Release Notes See note. See note.

DB2 Installation Notes Available on productCD-ROM only.

Available on productCD-ROM only.

Note: The HTML version of the release notes is available from theInformation Center and on the product CD-ROMs. To view the ASCIIfile on UNIX-based platforms, see the Release.Notes file. This file islocated in the DB2DIR/Readme/%L directory, where %L represents thelocale name and DB2DIR represents:v /usr/opt/db2_08_01 on AIXv /opt/IBM/db2/V8.1 on all other UNIX operating systems


Printing DB2 books from PDF files

You can print DB2 books from the PDF files on the DB2 PDF DocumentationCD. Using Adobe Acrobat Reader, you can print either the entire book or aspecific range of pages.

Prerequisites:

Ensure that you have Adobe Acrobat Reader. It is available from the AdobeWeb site at www.adobe.com

Procedure:

To print a DB2 book from a PDF file:1. Insert the DB2 PDF Documentation CD. On UNIX operating systems,

mount the DB2 PDF Documentation CD. Refer to your Quick Beginningsbook for details on how to mount a CD on UNIX operating systems.

2. Start Adobe Acrobat Reader.3. Open the PDF file from one of the following locations:

v On Windows operating systems:x:\doc\language directory, where x represents the CD-ROM drive letterand language represents the two-character territory code that representsyour language (for example, EN for English).

v On UNIX operating systems:/cdrom/doc/%L directory on the CD-ROM, where /cdrom represents themount point of the CD-ROM and %L represents the name of the desiredlocale.

Ordering printed DB2 books

Procedure:

To order printed books:v Contact your IBM authorized dealer or marketing representative. To find a

local IBM representative, check the IBM Worldwide Directory of Contacts atwww.ibm.com/planetwide

v Phone 1-800-879-2755 in the United States or 1-800-IBM-4YOU in Canada.v Visit the IBM Publications Center at

www.ibm.com/shop/publications/order

You can also obtain printed DB2 manuals by ordering Doc Packs for your DB2product from your IBM Reseller. The Doc Packs are subsets of the manuals inthe DB2 library selected to help you to get started using the DB2 product that


http://www.adobe.com/



you purchased. The manuals in the Doc Packs are the same as those that areavailable in PDF format on the DB2 PDF Documentation CD and contain thesame content as the documentation that is available on the DB2 HTMLDocumentation CD.

Accessing online help

The online help that comes with all DB2 components is available in threetypes:v Window and notebook helpv Command line helpv SQL statement help

Window and notebook help explain the tasks that you can perform in awindow or notebook and describe the controls. This help has two types:v Help accessible from the Help buttonv Infopops

The Help button gives you access to overview and prerequisite information.The infopops describe the controls in the window or notebook. Window andnotebook help are available from DB2 centers and components that have userinterfaces.

Command line help includes Command help and Message help. Commandhelp explains the syntax of commands in the command line processor.Message help describes the cause of an error message and describes anyaction you should take in response to the error.

SQL statement help includes SQL help and SQLSTATE help. DB2 returns anSQLSTATE value for conditions that could be the result of an SQL statement.SQLSTATE help explains the syntax of SQL statements (SQL states and classcodes).

Note: SQL help is not available for UNIX operating systems.

Procedure:

To access online help:v For window and notebook help, click Help or click that control, then click

F1. If the Automatically display infopops check box on the General pageof the Tool Settings notebook is selected, you can also see the infopop for aparticular control by holding the mouse cursor over the control.

v For command line help, open the command line processor and enter:– For Command help:


? command

where command represents a keyword or the entire command.

For example, ? catalog displays help for all the CATALOG commands,while ? catalog database displays help for the CATALOG DATABASEcommand.

v For Message help:? XXXnnnnn

where XXXnnnnn represents a valid message identifier.

For example, ? SQL30081 displays help about the SQL30081 message.v For SQL statement help, open the command line processor and enter:

? sqlstate or ? class code

where sqlstate represents a valid five-digit SQL state and class coderepresents the first two digits of the SQL state.

For example, ? 08003 displays help for the 08003 SQL state, while ? 08displays help for the 08 class code.

Finding topics by accessing the DB2 Information Center from a browser

The DB2 Information Center accessed from a browser enables you to accessthe information you need to take full advantage of DB2 Universal Databaseand DB2 Connect. The DB2 Information Center also documents major DB2features and components including replication, data warehousing, metadata,and DB2 extenders.

The DB2 Information Center accessed from a browser is composed of thefollowing major elements:

Navigation treeThe navigation tree is located in the left frame of the browser window.The tree expands and collapses to show and hide topics, the glossary,and the master index in the DB2 Information Center.

Navigation toolbarThe navigation toolbar is located in the top right frame of the browserwindow. The navigation toolbar contains buttons that enable you tosearch the DB2 Information Center, hide the navigation tree, and findthe currently displayed topic in the navigation tree.

Content frameThe content frame is located in the bottom right frame of the browserwindow. The content frame displays topics from the DB2 Information


Center when you click on a link in the navigation tree, click on asearch result, or follow a link from another topic or from the masterindex.

Prerequisites:

To access the DB2 Information Center from a browser, you must use one ofthe following browsers:v Microsoft Explorer, version 5 or laterv Netscape Navigator, version 6.1 or later

Restrictions:

The DB2 Information Center contains only those sets of topics that you choseto install from the DB2 HTML Documentation CD. If your Web browser returnsa File not found error when you try to follow a link to a topic, you mustinstall one or more additional sets of topics from the DB2 HTMLDocumentation CD.

Procedure:

To find a topic by searching with keywords:1. In the navigation toolbar, click Search.2. In the top text entry field of the Search window, enter one or more terms

related to your area of interest and click Search. A list of topics ranked byaccuracy displays in the Results field. The numerical ranking beside thehit provides an indication of the strength of the match (bigger numbersindicate stronger matches).Entering more terms increases the precision of your query while reducingthe number of topics returned from your query.

3. In the Results field, click the title of the topic you want to read. The topicdisplays in the content frame.

To find a topic in the navigation tree:1. In the navigation tree, click the book icon of the category of topics related

to your area of interest. A list of subcategories displays underneath theicon.

2. Continue to click the book icons until you find the category containingthe topics in which you are interested. Categories that link to topicsdisplay the category title as an underscored link when you move thecursor over the category title. The navigation tree identifies topics with apage icon.

3. Click the topic link. The topic displays in the content frame.


To find a topic or term in the master index:1. In the navigation tree, click the “Index” category. The category expands to

display a list of links arranged in alphabetical order in the navigation tree.2. In the navigation tree, click the link corresponding to the first character of

the term relating to the topic in which you are interested. A list of termswith that initial character displays in the content frame. Terms that havemultiple index entries are identified by a book icon.

3. Click the book icon corresponding to the term in which you areinterested. A list of subterms and topics displays below the term youclicked. Topics are identified by page icons with an underscored title.

4. Click on the title of the topic that meets your needs. The topic displays inthe content frame.

Finding product information by accessing the DB2 Information Center from theadministration tools

The DB2 Information Center provides quick access to DB2 productinformation and is available on all operating systems for which the DB2administration tools are available.

The DB2 Information Center accessed from the tools provides six types ofinformation.

Tasks Key tasks you can perform using DB2.

ConceptsKey concepts for DB2.

ReferenceDB2 reference information, such as keywords, commands, and APIs.

TroubleshootingError messages and information to help you with common DB2problems.

SamplesLinks to HTML listings of the sample programs provided with DB2.

TutorialsInstructional aid designed to help you learn a DB2 feature.

Prerequisites:

Some links in the DB2 Information Center point to Web sites on the Internet.To display the content for these links, you will first have to connect to theInternet.

Procedure:


To find product information by accessing the DB2 Information Center fromthe tools:1. Start the DB2 Information Center in one of the following ways:

v From the graphical administration tools, click on the InformationCenter icon in the toolbar. You can also select it from the Help menu.

v At the command line, enter db2ic.2. Click the tab of the information type related to the information you are

attempting to find.3. Navigate through the tree and click on the topic in which you are

interested. The Information Center will then launch a Web browser todisplay the information.

4. To find information without browsing the lists, click the Search icon to theright of the list.Once the Information Center has launched a browser to display theinformation, you can perform a full-text search by clicking the Search iconin the navigation toolbar.

Viewing technical documentation online directly from the DB2 HTMLDocumentation CD

All of the HTML topics that you can install from the DB2 HTMLDocumentation CD can also be read directly from the CD. Therefore, you canview the documentation without having to install it.

Restrictions:

As the Tools help is installed from the DB2 product CD and not from the DB2HTML Documentation CD, you must install the DB2 product to view the help.

Procedure:

1. Insert the DB2 HTML Documentation CD. On UNIX operating systems,mount the DB2 HTML Documentation CD. Refer to your Quick Beginningsbook for details on how to mount a CD on UNIX operating systems.

2. Start your HTML browser and open the appropriate file:v For Windows operating systems:

e:\program files\IBM\SQLLIB\doc\htmlcd\%L\index.htm

where e represents the CD-ROM drive, and %L is the locale of thedocumentation that you wish to use, for example, en_US for English.

v For UNIX operating systems:/cdrom/program files/IBM/SQLLIB/doc/htmlcd/%L/index.htm


where /cdrom/ represents where the CD is mounted, and %L is the localeof the documentation that you wish to use, for example, en_US forEnglish.

Updating the HTML documentation installed on your machine

It is now possible to update the HTML installed from the DB2 HTMLDocumentation CD when updates are made available from IBM. This can bedone in one of two ways:v Using the Information Center (if you have the DB2 administration GUI

tools installed).v By downloading and applying a DB2 HTML documentation FixPak .

Note: This will NOT update the DB2 code; it will only update the HTMLdocumentation installed from the DB2 HTML Documentation CD.

Procedure:

To use the Information Center to update your local documentation:1. Start the DB2 Information Center in one of the following ways:

v From the graphical administration tools, click on the InformationCenter icon in the toolbar. You can also select it from the Help menu.

v At the command line, enter db2ic.2. Ensure your machine has access to the external Internet; the updater will

download the latest documentation FixPak from the IBM server ifrequired.

3. Select Information Center —> Update Local Documentation from themenu to start the update.

4. Supply your proxy information (if required) to connect to the externalInternet.

The Information Center will download and apply the latest documentationFixPak, if one is available.

To manually download and apply the documentation FixPak :1. Ensure your machine is connected to the Internet.2. Open the DB2 support page in your Web browser at:

www.ibm.com/software/data/db2/udb/winos2unix/support.3. Follow the link for Version 8 and look for the ″Documentation FixPaks″

link.


http://www.ibm.com/software/data/db2/udb/winos2unix/support

4. Determine if the version of your local documentation is out of date bycomparing the documentation FixPak level to the documentation level youhave installed. This current documentation on your machine is at thefollowing level: DB2 v8.1 GA.

5. If there is a more recent version of the documentation available thendownload the FixPak applicable to your operating system. There is oneFixPak for all Windows platforms, and one FixPak for all UNIX platforms.

6. Apply the FixPak:v For Windows operating systems: The documentation FixPak is a self

extracting zip file. Place the downloaded documentation FixPak in anempty directory, and run it. It will create a setup command which youcan run to install the documentation FixPak.

v For UNIX operating systems: The documentation FixPak is acompressed tar.Z file. Uncompress and untar the file. It will create adirectory named delta_install with a script called installdocfix. Runthis script to install the documentation FixPak.

Copying files from the DB2 HTML Documentation CD to a Web server

The entire DB2 information library is delivered to you on the DB2 HTMLDocumentation CD and may be installed on a Web server for easier access.Simply copy to your Web server the documentation for the languages thatyou want.

Note: You might encounter slow performance if you access the HTMLdocumentation from a Web server through a low-speed connection.

Procedure:

To copy files from the DB2 HTML Documentation CD to a Web server, use theappropriate source path:v For Windows operating systems:

E:\program files\IBM\SQLLIB\doc\htmlcd\%L\*.*

where E represents the CD-ROM drive and %L represents the languageidentifier.

v For UNIX operating systems:/cdrom/program files/IBM/SQLLIB/doc/htmlcd/%L/*.*

where cdrom represents the mount point for the CD-ROM drive and %Lrepresents the language identifier.


Troubleshooting DB2 documentation search with Netscape 4.x

Most search problems are related to the Java support provided by webbrowsers. This task describes possible workarounds.

Procedure:

A common problem with Netscape 4.x involves a missing or misplacedsecurity class. Try the following workaround, especially if you see thefollowing line in the browser Java console:Cannot find class java/security/InvalidParameterException

v On Windows operating systems:From the DB2 HTML Documentation CD, copy the supplied x:programfiles\IBM\SQLLIB\doc\htmlcd\locale\InvalidParameterException.classfile to the java\classes\java\security\ directory relative to your Netscapebrowser installation, where x represents the CD-ROM drive letter and localerepresents the name of the desired locale.

Note: You may have to create the java\security\ subdirectory structure.v On UNIX operating systems:

From the DB2 HTML Documentation CD, copy the supplied /cdrom/programfiles/IBM/SQLLIB/doc/htmlcd/locale/InvalidParameterException.classfile to the java/classes/java/security/ directory relative to your Netscapebrowser installation, where cdrom represents the mount point of theCD-ROM and locale represents the name of the desired locale.

Note: You may have to create the java/security/ subdirectory structure.

If your Netscape browser still fails to display the search input window, try thefollowing:v Stop all instances of Netscape browsers to ensure that there is no Netscape

code running on the machine. Then open a new instance of the Netscapebrowser and try to start the search again.

v Purge the browser’s cache.v Try a different version of Netscape, or a different browser.

Searching the DB2 documentation

You can search the library of DB2 documentation to locate information thatyou need. A pop-up search window opens when you click the search icon inthe navigation toolbar of the DB2 Information Center (accessed from abrowser). The search can take a minute to load, depending on the speed ofyour computer and network.


Prerequisites:

You need Netscape 6.1 or higher, or Microsoft’s Internet Explorer 5 or higher.Ensure that your browser’s Java support is enabled.

Restrictions:

The following restrictions apply when you use the documentation search:v Search is not case sensitive.v Boolean searches are not supported.v Wildcard and partial searches are not supported. A search on java* (or java)

will only look for the literal string java* (or java) and would not, forexample, find javadoc.

Procedure:

To search the DB2 documentation:1. In the navigation toolbar, click the Search icon.2. In the top text entry field of the Search window, enter one or more terms

(separated by a space) related to your area of interest and click Search. Alist of topics ranked by accuracy displays in the Results field. Thenumerical ranking beside the hit provides an indication of the strength ofthe match (bigger numbers indicate stronger matches).Entering more terms increases the precision of your query while reducingthe number of topics returned from your query.

3. In the Results list, click the title of the topic you want to read. The topicdisplays in the content frame of the DB2 Information Center.

Note: When you perform a search, the first (highest-ranking) result isautomatically loaded into your browser frame. To view the contents ofother search results, click on the result in the results list.

Online DB2 troubleshooting information

With the release of DB2® UDB Version 8, there will no longer be aTroubleshooting Guide. The troubleshooting information once contained in thisguide has been integrated into the DB2 publications. By doing this, we areable to deliver the most up-to-date information possible. To find informationon the troubleshooting utilities and functions of DB2, access the DB2Information Center from any of the tools.

Refer to the DB2 Online Support site if you are experiencing problems andwant help finding possible causes and solutions. The support site contains alarge, constantly updated database of DB2 publications, TechNotes, APAR


(product problem) records, FixPaks, and other resources. You can use thesupport site to search through this knowledge base and find possible solutionsto your problems.

Access the Online Support site atwww.ibm.com/software/data/db2/udb/winos2unix/support, or by clickingthe Online Support button in the DB2 Information Center. Frequentlychanging information, such as the listing of internal DB2 error codes, is nowalso available from this site.

Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. These are themajor accessibility features in DB2® Universal Database Version 8:v DB2 allows you to operate all features using the keyboard instead of the

mouse. See “Keyboard Input and Navigation”.v DB2 enables you customize the size and color of your fonts. See “Accessible

Display”.v DB2 allows you to receive either visual or audio alert cues. See “Alternative

Alert Cues” on page 618.v DB2 supports accessibility applications that use the Java™ Accessibility API.

See “Compatibility with Assistive Technologies” on page 618.v DB2 comes with documentation that is provided in an accessible format.

See “Accessible Documentation” on page 618.

Keyboard Input and Navigation

Keyboard InputYou can operate the DB2 Tools using only the keyboard. You can use keys orkey combinations to perform most operations that can also be done using amouse.

Keyboard FocusIn UNIX-based systems, the position of the keyboard focus is highlighted,indicating which area of the window is active and where your keystrokes willhave an effect.

Accessible DisplayThe DB2 Tools have features that enhance the user interface and improveaccessibility for users with low vision. These accessibility enhancementsinclude support for customizable font properties.

Font SettingsThe DB2 Tools allow you to select the color, size, and font for the text inmenus and dialog windows, using the Tools Settings notebook.


http://www.ibm.com/software/data/db2/udb/winos2unix/support

Non-dependence on ColorYou do not need to distinguish between colors in order to use any of thefunctions in this product.

Alternative Alert CuesYou can specify whether you want to receive alerts through audio or visualcues, using the Tools Settings notebook.

Compatibility with Assistive TechnologiesThe DB2 Tools interface supports the Java Accessibility API enabling use byscreen readers and other assistive technologies used by people withdisabilities.

Accessible DocumentationDocumentation for the DB2 family of products is available in HTML format.This allows you to view documentation according to the display preferencesset in your browser. It also allows you to use screen readers and otherassistive technologies.

DB2 tutorials

The DB2® tutorials help you learn about various aspects of DB2 UniversalDatabase. The tutorials provide lessons with step-by-step instructions in theareas of developing applications, tuning SQL query performance, workingwith data warehouses, managing metadata, and developing Web servicesusing DB2.

Before you begin:

Before you can access these tutorials using the links below, you must installthe tutorials from the DB2 HTML Documentation CD.

If you do not want to install the tutorials, you can view the HTML versions ofthe tutorials directly from the DB2 HTML Documentation CD. PDF versions ofthese tutorials are also available on the DB2 PDF Documentation CD.

Some tutorial lessons use sample data or code. See each individual tutorial fora description of any prerequisites for its specific tasks.

DB2 Universal Database tutorials:

If you installed the tutorials from the DB2 HTML Documentation CD, you canclick on a tutorial title in the following list to view that tutorial.

Business Intelligence Tutorial: Introduction to the Data Warehouse CenterPerform introductory data warehousing tasks using the DataWarehouse Center.


Business Intelligence Tutorial: Extended Lessons in Data WarehousingPerform advanced data warehousing tasks using the Data WarehouseCenter.

Development Center Tutorial for Video Online using Microsoft® Visual BasicBuild various components of an application using the DevelopmentCenter Add-in for Microsoft Visual Basic.

Information Catalog Center TutorialCreate and manage an information catalog to locate and use metadatausing the Information Catalog Center.

Video Central for e-business TutorialDevelop and deploy an advanced DB2 Web Services application usingWebSphere® products.

Visual Explain TutorialAnalyze, optimize, and tune SQL statements for better performanceusing Visual Explain.

DB2 Information Center accessed from a browser

The DB2® Information Center gives you access to all of the information youneed to take full advantage of DB2 Universal Database™ and DB2 Connect™

in your business. The DB2 Information Center also documents major DB2features and components including replication, data warehousing, theInformation Catalog Center, Life Sciences Data Connect, and DB2 extenders.

The DB2 Information Center accessed from a browser has the followingfeatures if you view it in Netscape Navigator 6.1 or later or Microsoft InternetExplorer 5 or later. Some features require you to enable support for Java orJavaScript:

Regularly updated documentationKeep your topics up-to-date by downloading updated HTML.

SearchSearch all of the topics installed on your workstation by clickingSearch in the navigation toolbar.

Integrated navigation treeLocate any topic in the DB2 library from a single navigation tree. Thenavigation tree is organized by information type as follows:v Tasks provide step-by-step instructions on how to complete a goal.v Concepts provide an overview of a subject.v Reference topics provide detailed information about a subject,

including statement and command syntax, message help,requirements.


Master indexAccess the information installed from the DB2 HTML DocumentationCD from the master index. The index is organized in alphabeticalorder by index term.

Master glossaryThe master glossary defines terms used in the DB2 InformationCenter. The glossary is organized in alphabetical order by glossaryterm.


Appendix C. Notices

IBM may not offer the products, services, or features discussed in thisdocument in all countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringeany IBM intellectual property right may be used instead. However, it is theuser’s responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact theIBM Intellectual Property Department in your country/region or sendinquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or anyother country/region where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY,OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allowdisclaimer of express or implied warranties in certain transactions; therefore,this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseWeb sites. The materials at those Web sites are not part of the materials forthis IBM product, and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for thepurpose of enabling: (i) the exchange of information between independentlycreated programs and other programs (including this one) and (ii) the mutualuse of the information that has been exchanged, should contact:

IBM Canada LimitedOffice of the Lab Director8200 Warden AvenueMarkham, OntarioL6G 1C7CANADA

Such information may be available, subject to appropriate terms andconditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM CustomerAgreement, IBM International Program License Agreement, or any equivalentagreement between us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems, and there is no guarantee that thesemeasurements will be the same on generally available systems. Furthermore,some measurements may have been estimated through extrapolation. Actualresults may vary. Users of this document should verify the applicable data fortheir specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements, or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility, or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.


All statements regarding IBM’s future direction or intent are subject to changeor withdrawal without notice, and represent goals and objectives only.

This information may contain examples of data and reports used in dailybusiness operations. To illustrate them as completely as possible, the examplesinclude the names of individuals, companies, brands, and products. All ofthese names are fictitious, and any similarity to the names and addresses usedby an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information may contain sample application programs, in sourcelanguage, which illustrate programming techniques on various operatingplatforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM for the purposes of developing, using,marketing, or distributing application programs conforming to the applicationprogramming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested underall conditions. IBM, therefore, cannot guarantee or imply reliability,serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative workmust include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBMCorp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. Allrights reserved.

Appendix C. Notices 623

Trademarks

The following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both, and have been usedin at least one of the documents in the DB2 UDB documentation library.

ACF/VTAMAISPOAIXAIXwindowsAnyNetAPPNAS/400BookManagerC Set++C/370CICSDatabase 2DataHubDataJoinerDataPropagatorDataRefresherDB2DB2 ConnectDB2 ExtendersDB2 OLAP ServerDB2 Universal DatabaseDistributed Relational

Database ArchitectureDRDAeServerExtended ServicesFFSTFirst Failure Support TechnologyIBMIMSIMS/ESAiSeries

LAN DistanceMVSMVS/ESAMVS/XANet.DataNetViewOS/390OS/400PowerPCpSeriesQBICQMFRACFRISC System/6000RS/6000S/370SPSQL/400SQL/DSSystem/370System/390SystemViewTivoliVisualAgeVM/ESAVSE/ESAVTAMWebExplorerWebSphereWIN-OS/2z/OSzSeries

The following terms are trademarks or registered trademarks of othercompanies and have been used in at least one of the documents in the DB2UDB documentation library:

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Intel and Pentium are trademarks of Intel Corporation in the United States,other countries, or both.


Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

Other company, product, or service names may be trademarks or servicemarks of others.

Appendix C. Notices 625


Index

Aaccessing help 1ADM messages 3AUD messages 3

DDIA messages 3

GGOV messages 3

HHelp 1

Iintroduction to messages 1

Mmessage prefix 1message structure 1message suffix 1Messages 1

ADM 3AUD 3DIA 3GOV 3SQL 5SQLSTATE 555

messages, introduction 1

Oonline help 1other message sources 4

SSQL messages 5SQLSTATE messages 555



Contacting IBM

In the United States, call one of the following numbers to contact IBM:v 1-800-237-5511 for customer servicev 1-888-426-4343 to learn about available service optionsv 1-800-IBM-4YOU (426-4968) for DB2 marketing and sales

In Canada, call one of the following numbers to contact IBM:v 1-800-IBM-SERV (1-800-426-7378) for customer servicev 1-800-465-9600 to learn about available service optionsv 1-800-IBM-4YOU (1-800-426-4968) for DB2 marketing and sales

To locate an IBM office in your country or region, check IBM’s Directory ofWorldwide Contacts on the web at www.ibm.com/planetwide

Product information

Information regarding DB2 Universal Database products is available bytelephone or by the World Wide Web atwww.ibm.com/software/data/db2/udb

This site contains the latest information on the technical library, orderingbooks, client downloads, newsgroups, FixPaks, news, and links to webresources.

If you live in the U.S.A., then you can call one of the following numbers:v 1-800-IBM-CALL (1-800-426-2255) to order products or to obtain general

information.v 1-800-879-2755 to order publications.

For information on how to contact IBM outside of the United States, go to theIBM Worldwide page at www.ibm.com/planetwide




��

Printed in U.S.A.

GC09-4841-00

Spin

ein

form

atio

n:

��

�IB

M®

DB

2U

nive

rsal

Dat

abas

e™

Mes

sage

Ref

eren

ce,V

olum

e2

Vers

ion

8

Date post:	09-Feb-2022
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Message Reference, Volume 2

Documents