DB2 Messages V1

IBM®

DB2 Universal Database™

Message ReferenceVolume 1

Version 8

GC09-4840-00

��

IBM®

DB2 Universal Database™

Message ReferenceVolume 1

Version 8

GC09-4840-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. ADM Messages . . . . . . . 5

Chapter 3. ASN messages. . . . . . . 31

Chapter 4. CCA Messages . . . . . . 123

Chapter 5. CLI Messages. . . . . . . 133

Chapter 6. DBA Messages . . . . . . 147

Chapter 7. DBI Messages . . . . . . 217

Chapter 8. DBT Messages . . . . . . 273

Chapter 9. DB2 Messages . . . . . . 279

Chapter 10. DWC Messages. . . . . . 321

Chapter 11. ICC Messages . . . . . . 445

Chapter 12. GSE Messages . . . . . . 473

Chapter 13. SAT Messages . . . . . . 527

Chapter 14. SPM Messages . . . . . . 537

Chapter 15. XML Extender messages . . 555

Appendix A. SPM Protocol ViolationRecords . . . . . . . . . . . . 571Resync Protocol Violation Record . . . . 571Syncpoint Protocol Violation Record . . . 571

XLN Protocol Violation Record . . . . . 572

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

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

Printing DB2 books from PDF files . . . . 581Ordering printed DB2 books . . . . . . 581Accessing online help . . . . . . . . 582Finding topics by accessing the DB2Information Center from a browser . . . . 583Finding product information by accessingthe DB2 Information Center from theadministration tools . . . . . . . . . 585Viewing technical documentation onlinedirectly from the DB2 HTML DocumentationCD. . . . . . . . . . . . . . . 586Updating the HTML documentation installedon your machine . . . . . . . . . . 587Copying files from the DB2 HTMLDocumentation CD to a Web server . . . . 588Troubleshooting DB2 documentation searchwith Netscape 4.x . . . . . . . . . . 589Searching the DB2 documentation . . . . 589Online DB2 troubleshooting information . . 590Accessibility . . . . . . . . . . . 591

Keyboard Input and Navigation . . . . 591Accessible Display . . . . . . . . 591Alternative Alert Cues . . . . . . . 592Compatibility with Assistive Technologies 592Accessible Documentation . . . . . . 592

DB2 tutorials . . . . . . . . . . . 592DB2 Information Center accessed from abrowser . . . . . . . . . . . . . 593

Appendix C. Notices . . . . . . . . 595Trademarks . . . . . . . . . . . . 598

Index . . . . . . . . . . . . . 601

Contacting IBM . . . . . . . . . . 603Product information . . . . . . . . . 603

© Copyright IBM Corp. 1993 - 2002 iii

iv Message Reference, Volume 1

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 1

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 1

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. ADM Messages

This section contains the Administration Notification (ADM) messages. Themessages are listed in numeric sequence.

ADM0001C A severe error has occurred.Examine the administrationnotification log and contact IBMSupport if necessary.

ADM0500E The DB2 Service does not havethe necessary authority tocomplete the command. If a useraccount has been associated withthe DB2 Service, ensure that theuser account has the correct accessrights on the local system andaccess to the Domain SecurityDatabase for user authenticationand group enumeration.

ADM0501C A stack overflow exception hasoccurred. The DB2 instance hasterminated abnormally. To remedythis problem, you may increasethe default stack size fordb2syscs.exe using the db2hdrutility as follows: db2hdr\sqllib\bin\db2syscs.exe/s:<stackreserve>[,<stackcommit>]Note that increasing the defaultstack size will consume virtualmemory space and may reduce themaximum number of concurrentconnections. Contact IBM Supportfor further assistance.

ADM0502C The DB2 instance has terminatedabnormally. To remedy thisproblem, increase theAGENT_STACK_SZ DBMconfiguration parameter. ContactIBM Support for furtherassistance.

ADM0503C An unexpected internal processingerror has occurred. ALL DB2PROCESSES ASSOCIATEDWITH THIS INSTANCE HAVEBEEN SHUTDOWN. Diagnosticinformation has been recorded.Contact IBM Support for furtherassistance.

ADM0504C An unexpected internal processingerror has occurred. ALL DB2PROCESSES ASSOCIATEDWITH THIS INSTANCE HAVEBEEN SUSPENDED. Diagnosticinformation has been recorded.Contact IBM Support for furtherassistance.

ADM0505E DB2 received a SIGDANGERsignal from the operating system.This signal indicates that thesystem is running low on pagingspace. If the paging space gets toolow, the operating system willforcibly terminate user processes.Contact your system administratorto increase your paging space.

ADM0506I DB2 has automatically updatedthe parameter kernel parameterfrom originalValue to therecommended valuerecommendedValue.


ADM0507W DB2 could not automaticallyupdate the parameter kernelparameter to the recommendedvalue recommendedValue. Updatethis kernel parameter manually.

ADM0508E DB2 was unable to load the Javainterpreter library libraryPath. Thiserror commonly occurs because ofrestrictions imposed by theoperating system. Consult theIBM DB2 documentation for asolution. If this problem persists,contact IBM support.

ADM1010I Reconcile started on tabletableName.

ADM1011I Reconcile has completedsuccessfully on table tableName.

ADM1012W Reconcile has failed on tabletableName. The table will now beplaced into DATALINK ReconcileNot Possible (DRNP) state.

ADM1013W Reconcile for table tableName issuccessful on Data LinksManagers (DLMs) that were upand is pending on DLMs thatwere down. The table will now beplaced in DATALINK ReconcilePending (DRP) state.

ADM1014E Reconcile has failed on tabletableName.

ADM1022W The metadata information for theDATALINK column(s) is missingon DB2 Data Links ManagerserverName.

ADM1023W Reconcile processing is PENDINGon Data Links ManagerserverName.

ADM1024W Reconcile processing isCOMPLETE on Data LinksManager serverName.

ADM1500W DB2 is unable to locate log filefilename.

ADM1510W A file sharing violation hasoccurred while accessing log filefileName. Another process may beusing this file. DB2 will try todelete it later.

ADM1511W The error error has occurred whiledeleting log file filename. DB2 willtry to delete this file later.

ADM1512E The error error has occurred whiledeleting log file filename. Usermust manually delete this file.

ADM1513W The log file fileName has beendeleted.

ADM1514W The log file fileName no longerexists.

ADM1530E Crash recovery has been initiated.

ADM1531E Crash recovery has completedsuccessfully.

ADM1532E Crash recovery has failed withSQLCODE SQLCODE.

ADM1533W Database has recovered. However,one or more table spaces areoffline.

ADM1550W The active log space exceeds theLOGPRIMARY DB configurationparameter. ROLLBACK may beslow if log files have to beretrieved from archive.


ADM1551W DB2 is retrieving the active logfile fileName from archive. Thismay result in a delay.

ADM1552E DB2 is unable to open active logfile filename. This could be causedby problem in retrieving the logfile from archive. DB2 will tryagain every 5 minutes.

ADM1600W There was not enough memory toenable parallel recovery; however,recovery is proceeding. Increaseeither the DBHEAP orUTIL_HEAP_SZ configurationparameters by blockSize for anyfuture recoveries.

ADM1601W Another request was made to rollthe database forward. However,the current invocation ofrollforward did not read as far inthe logs as the previousinvocation. The log filescontaining log records for LSNLSN were not available in thedatabase LOGPATH or theOVERFLOW LOG PATH. Makesure that all the log files areavailable in the databaseLOGPATH or the OVERFLOWLOG PATH and re-issue therollforward command. Thedatabase has been left inrollforward pending state.

ADM1602W Rollforward recovery has beeninitiated.

ADM1603I DB2 is invoking the forwardphase of the database rollforwardrecovery.

ADM1604I DB2 is invoking the forwardphase of the table spacerollforward recovery.

ADM1605I DB2 is invoking the backwardphase of database rollforwardrecovery.

ADM1606I DB2 is invoking the backwardphase of table space rollforwardrecovery.

ADM1607I DB2 is invoking the completionphase of the database rollforwardrecovery.

ADM1608I DB2 is invoking the completionphase of the table spacerollforward recovery.

ADM1609W DB2 is canceling the databaserollforward recovery.

ADM1610W DB2 is canceling the table spacerollforward recovery.

ADM1611W The rollforward recovery phasehas been completed.

ADM1612W Online table space rollforwardrecovery could not complete dueto the high volume of databaseactivity. Either reduce thedatabase activity, increase theMAXAPPLS configurationparameter, or perform an offlinetable space rollforward.

ADM1613W The table space tablespaceName (IDtablespaceID) was previously rolledforward to timestampPIT attimestampRFWD.

ADM1614W The table space tablespaceName (IDtablespaceID) has been placed intorestore pending state. The rest ofthe table spaces have been rolledforward to the end of logs.

Chapter 2. ADM Messages 7

ADM1615W DB2 cannot roll forward tablespace tablespaceName (IDtablespaceID) because it is stillused by an active transaction. Theapplication handle is appHandle.Terminate this application byCOMMIT, ROLLBACK, orFORCE APPLICATION.

ADM1616E DB2 could not find the droppedtable log record that matches thegiven dropped table with IDtablespaceID during recovery.

ADM1617W The table space tablespaceName (IDtablespaceID) that was included inthe last rollforward has not yetcompleted. It has not beenincluded in the table space listprovided for this rollforward. Ithas been placed into restorepending state.

ADM1618W DB2 cannot recover table spacetablespaceName (ID tablespaceID)during database rollforward. Thetable space has been placed inrollforward pending state. Torecover, perform a table spacerollforward after the databaserollforward is complete.

ADM1619W Rollforward cannot stop here.Rollforward to LSN rollforwardLSNin log file logFilename.

ADM1700W DB2 is unable to use the log pathspecified by the backup image;Switching to the default log path.

ADM1701W The USEREXIT DB configurationparameter is not enabled becausethe LOGRETAIN DBconfiguration parameter is set toCAPTURE.

ADM1800E DB2 was unable to confirm loglogNumber was archived on the oldlog path. Take a database backupto ensure that the database maybe recovered.

ADM1801W DB2 could not access more than2GB of file storage on the rawdevice. Therefore, only 2GB offile storage will be used forlogging.

ADM1802W Database was put into offlinebackup pending state because theLOGFILSIZ DB configurationparameter has changed whileusing raw device for logging.

ADM1803W There is not enough space left onraw device path for log files. Theactual device size is actualDevice4K pages. The minimum requireddevice size is minimumDevice 4Kpages.

ADM1804W The raw device is too small tosupport active log space.actualDeviceSize 4K pages areavailable, however,minimumDeviceSize 4K pages arerequired. Use a larger device orreduce the LOGPRIMARY and/orthe LOGFILSIZ DB configurationparameters.

ADM1805E DB2 is unable to use theNEWLOGPATH DB configurationparameter because the raw deviceis already being used as a log ortable space container elsewhere.

ADM1806E Unable to use the NEWLOGPATHDB configuration parameternewLogPath DB2 will continue touse the current log path.


ADM1807E The new DB configurationparameter values forNEWLOGPATH andMIRRORLOGPATH are identical,this is not allowed. Ensure thatthe values are different for thetwo parameters.

ADM1810E The new value of theMIRRORLOGPATH DBconfiguration parameter is invalidor cannot be used. DB2 willignore the new value. Confirm thenew path value and ensure that itis valid.

ADM1811E DB2 will now switch to thedefault log path logpath.

ADM1812E The new value of theMIRRORPATH DB configurationparameter newMirrorPath is notusable. DB2 will continue to usethe existing mirror pathdefaultMirrorPath.

ADM1813E The current mirror pathcurrentMirrorPath is invalid.

ADM1814E The current log pathcurrentLogPath is invalid.

ADM1815E An error occurred while DB2 wastrying to remove log files fromlogFilePath.

ADM1817E DB2 was unable to execute theuser exit program when archivinglog file logFilename from dirPathfor database DBName. The errorcode was returnCode. Verify userexit program by manually runningit.

ADM1818E An error was received from theuser exit program. DB2 will notcall the user exit program for thisdatabase for 5 minutes.

ADM1819C DB2 was unable to switch to thenew log file size because an erroroccurred while archiving an oldlog on the raw device. As a result,the database cannot be accessed.

ADM1820W For USEREXIT to be enabled, youcannot have both DBconfiguration parametersLOGRETAIN set to CAPTUREand USEREXIT turned on.Therefore, USEREXIT is disabled.

ADM1821E The log path has been reset to thedefault value.

ADM1822W The active log is being held bydirty pages. This is not an error,but database performance may beimpacted. If possible, reduce thedatabase work load. If thisproblem persists, either decreasethe SOFTMAX and/or increase theNUM_IOCLEANERS DBconfiguration parameters.

ADM1823E The log is full. The active log isheld by application handle handle.Terminate this application byCOMMIT, ROLLBACK or FORCEAPPLICATION.

ADM1824W DB2 cannot delete the log filefilename. User must manuallydelete the log file.

ADM1825W DB2 cannot create the next log filebecause of a user exit problem.


ADM1826E DB2 cannot continue because thedisk used for logging is full.

ADM1827E There is no space left on rawdevice used for logging. Usermust make an offline backup ofthe database.

ADM1828C DB2 will attempt to create the logfile again in 5 minutes.

ADM1830E The active log path is set to thedefault value.

ADM1831E DB2 was unable to execute userexit program when retrieving logfile logFilename to dirPath fordatabase DBName. The error codewas returnCode. Verify the userexit program by manually runningit.

ADM1832E DB2 was unable to find the userexit program when archiving logfile logFilename from dirPath fordatabase DBName. The error codewas returnCode.

ADM1833E The user exit program returned anerror when archiving log filelogFilename from dirPath fordatabase DBName. The error codewas returnCode.

ADM1834E DB2 was unable to find the userexit program when retrieving logfile logFilename to dirPath fordatabase DBName. The error codewas returnCode.

ADM1835E The user exit program returned anerror when retrieving log filelogFilename to dirPath for databaseDBName. The error code wasreturnCode.

ADM1836W The table tableID (ID tableID) ontablespaceName (ID tablespaceName)is in DATALINK ReconcilePending (DRP) state.

ADM1837W The table tableName (ID tableID) ontablespaceName (ID tablespaceID) isin DATALINK Reconcile NotPossible (DRNP) state.

ADM1838W An application is waiting for alock held by an indoubttransaction. This will cause theapplication to wait indefinitely.Use the LIST INDOUBTTRANSACTION command toinvestigate and resolve theindoubt transactions.

ADM1839W An error occurred while DB2 waswriting log data to log file logFileon path logPath1. The log file isstill available on log pathlogPath2. DB2 will attempt to useboth paths for subsequent logfiles. In the meantime, check thatthe specified log path in whichthe error occurred exists and isaccessible. Also check that there isspace available in the file system.

ADM1840W The error on log path logPath hasbeen resolved. DB2 will nowwrite log files to this path.


ADM1841W DB2 was unable to locate loglogNumber while attempting toarchive it. Your existing recoverystrategy may not work if themissing log file is required duringrecovery. A database backup isrequired to ensure therecoverability of the database.However, the backup should betaken after the First Active Logfile (LOGHEAD) DBconfiguration parameter is beyondthe log specified above. Youmight want to considerdeactivating the database now tohave the First Active Log file(LOGHEAD) move up, and thentake a backup.

ADM2000E The Event Monitor eventMonitorwas deactivated because itencountered an I/O error.

ADM2001W The Event Monitor eventMonitorwas deactivated because theMAXFILES and MAXFILESIZECREATE EVENT MONITORparameters’ limits have beenreached.

ADM2002E The Event Monitor eventMonitorwas deactivated when the processreading from the target pipe haddisconnected.

ADM2003W The Event Monitor eventMonitorwas not activated because thelimit on the number of activeevent monitors has already beenreached.

ADM2004E The Event Monitor eventMonitorwas not activated because therewas not enough storage space inthe database monitor heap. Toremedy this problem, increase theMON_HEAP_SZ DBMconfiguration parameter.

ADM2005W The database monitor heap isexhausted. Increase theMON_HEAP_SZ DBMconfiguration parameter.

ADM2006W The database monitor heap isexhausted. Statement elementsmay be unreliable. Increase theMON_HEAP_SZ DBMconfiguration parameter.

ADM2007W The Event monitor wasdeactivated due toPCTDEACTIVE limit reached. Toreactivate the Event Monitor,either increase the table space sizeor increase the PCTDEACTIVEthreshold.

ADM2009C The Event Monitor eventMonitordetected on table tableName (IDtableID) that the column namecolName is invalid.

ADM2010C The Event Monitor eventMonitordetected on table tableName (IDtableID) that the column colName isnot allowed.

ADM2011C The Event Monitor eventMonitordetected on table tableName (IDtableID) that the column colNamehas an invalid dataType data type.

ADM2012C For table tableName, (ID tableID)the row size is bigger than thepage size.


ADM2013C The Event Monitor eventMonitordetected on table tableName (IDtableID) that the column colName isincorrect. The first column mustbe PARTITION_KEY.

ADM2014W The Event Monitor eventMonitordetected on table tableName (IDtableID) that the size of thecolumn colName is smaller thanthe default size ofdefaultColumnSize. Therefore,contents will be truncated to theuser specified size.

ADM2015W The SQLCODE received from theremote target node is SQLCODE.

ADM2016W The table tableName (ID tableID)was not found.

ADM2500E A serious error has occurred at thedatabase serverDRDAApplicationServer which hasmade continued processingimpossible. A dump has beengenerated. If the remote server isDB2 UDB for OS/390,zOS, checkthe console log for informationabout this error. If the remoteserver is DB2 UDB for iSeries, thejob log of the server job, and/or afirst failure data capture (FFDC)spooled file is usually necessaryto determine the cause of theerror. If the remote server is DB2UDB for Unix/Windows, checkthe remote database server’sadministration log for informationregarding this error.

ADM2501C The amount of data received for adata type at the database serverdid not match the amount whichwas expected. A dump has beengenerated. If the remote server isDB2 UDB for OS/390,zOS, checkthe console log for informationabout this error. If the remoteserver is DB2 UDB for iSeries, thejob log of the server job, and/or afirst failure data capture (FFDC)spooled file is usually necessaryto determine the cause of theerror. If the remote server is DB2UDB for Unix/Windows, checkthe remote database server’sadministration log for informationregarding this error.

ADM2502C The remote database server hasencountered an error. If theremote server is DB2 UDB forOS/390,zOS, check the console logfor information about this error. Ifthe remote server is DB2 UDB foriSeries, the job log of the serverjob, and/or a first failure datacapture (FFDC) spooled file isusually necessary to determine thecause of the error. If the remoteserver is DB2 UDB forUnix/Windows, check the remotedatabase server’s administrationlog for information regarding thiserror.

ADM2503C A datastream parsing error hasbeen detected. A dump has beengenerated.


ADM2504C The LOB data type is notsupported on this database server.APAR fixes are required. If thisdatabase server is DB2 for OS/390v6 and v7, apply the fixes forAPARs PQ50016 and PQ50017. Ifthe database server is DB2 foriSeries, any release prior to V5.1is not supported. For DB2 foriSeries v5.1, the PTF for APAR9A00531 must be applied. If thedatabase server is DB2 for VMand VSE, contact IBM Support.

ADM2505E While DB2 was attempting toutilize sysplex support, aconnection could not beestablished to the database serverat SNA address SNAAddress dueto an unknown cpic symbolicdestination name destName. Checkyour SNA configuration andvalidate it with network supportpersonnel or disable sysplexsupport at the DB2 ConnectServer.

ADM3000C The network host entrynetworkHostEntry at line lineNumberof db2nodes.cfg cannot beresolved.

ADM3001C DB2 cannot create theintermediate socket directorysocketDirectory. Check thepermissions of this path.

ADM3003C The node node is no longerpresent in db2nodes.cfg, eventhough this node had existedwhen FCM had started up. Thismay indicate a communicationfailure.

ADM3006C The retry limit was reached whileattempting to establish aconnection to node node. DB2 willnow initiate node recovery.

ADM3008C The connection with node nodehas been unexpectedly severed.DB2 will now initiate noderecovery.

ADM3019C The link between node node1 andnode node2 is broken. Check yourswitch and cables.

ADM3020C The number of FCM buffers istoo small. This will impactcommunication between DB2agents and lead to runtime errors.If this message persists, youshould adjust theFCM_NUM_BUFFERS DBMconfiguration parameter.

ADM3021W VI is enabled on this node.

ADM4000W A catalog cache overflowcondition has occurred. There isno error but this indicates that thecatalog cache has exceeded theconfigured maximum size. If thiscondition persists, you may wantto adjust theCATALOGCACHE_SZ DBconfiguration parameter.

ADM4001I A failure has occurred whileregenerating the view viewName.

ADM4002W The Event Monitor target tabletargetTableName (table schematableSchema ) already exists.


ADM4500W A package cache overflowcondition has occurred. There isno error but this indicates that thepackage cache has exceeded theconfigured maximum size. If thiscondition persists, you may wantto adjust the PCKCACHESZ DBconfiguration parameter.

ADM5500W DB2 is performing lock escalation.The total number of lockscurrently held is locksHeld, and thetarget number of locks to hold istargetNumber.

ADM5501I DB2 is performing lock escalation.The total number of lockscurrently held is locksHeld, and thetarget number of locks to hold istargetNumber. The currentstatement being executed iscurrentStatement.

ADM5502W The escalation of numLocks lockson table tableName to lock intentlockIntent was successful.

ADM5503E The escalation of numLocks lockson table tableName to lock intentlockIntent has failed. TheSQLCODE is SQLCODE.

ADM5510E The table space tableSpace (IDtableSpace) is full. There is nomore room in the internal objecttable of this table space.

ADM5511E The object object of table tableNamehas reached the maximumpossible size.

ADM5520E The migration path isunsupported.

ADM5521C The table tableName is missing orit was truncated and was notmigrated. Database migration willcontinue, but this table will beinaccessible.

ADM5530E The COMMIT processing of tabletableName that used NOTLOGGED INITIALLY has beeninitiated. It is recommended thatyou take a backup of this table’stable space(s).

ADM5550C The table space tablespaceName (IDtablespaceID) is being removedfrom the rollforward set. TheSQLCODE is SQLCODE.

ADM5560C DB2 is unable to redo thereorganization of a table unlessboth the data table spacedataTablespaceName (IDdataTablespaceID) and the longtable space LongTablespaceName (IDdataTablespaceID) are being rolledforward together. Ensure that bothof the table spaces are beingrolled forward together, or restorea backup image taken after thereorganization to eliminate theneed for reorganization to beredone.

ADM5561C DB2 is unable to redo thereorganization of a table unlessboth the data table spacedataTablespaceName (IDdataTablespaceID) and the longtable space longTablespaceName (IDdataTablespaceID) are at the samepoint in time. Ensure that abackup of both table spaces areeither from before the tablereorganization (so that it can beredone) or from after the tablereorganization (so that it does nothave to be redone).


ADM5562C DB2 is unable to undo thein-place reorganization of a tableunless both the data table spacedataTablespaceName (IDdataTablespaceID) and the indextable space indexTablespaceName(ID dataTablespaceID) are beingrolled forward together. Ensurethat both table spaces are beingrolled forward together.

ADM5570W Access was attempted on anunavailable table tableName. Thistable must be dropped.

ADM5571W DB2 is marking object object oftable tableName unavailable. Thistable will have to be dropped.

ADM5572I The index(es) on table tableNameare marked invalid and willrequire rebuilding. DB2 willautomatically rebuild theindex(es) on this table, which willresult in a super exclusive Z tablelock for the duration of therebuild and the unit of work inwhich this is done.

ADM5580W The table space with IDtablespaceID either does not existor is not in the set of table spacesbeing recovered. Recovery willcontinue, but filtering of thistable space or tables/objects inthis table space will be ignored.

ADM5581W DB2 has successfully filtered tablespace with ID tablespaceID, objectID object-ID.

ADM5582C Internal error error occurred whileattempting to filter table space IDtablespaceID, object ID objectID.

ADM5583W The total alloted time of 16.7hours per Data Links Managerhas been exceeded.

ADM5590E The specified INPLACE tablereorganization action on tabletableName is not allowed on thisnode because of SQLCODE -2219reason code reasonCode.

ADM6001I A container was renamed basedon the rules defined in the pathrename configuration fileconfigFile. The container oldNamehas been renamed to newName.

ADM6002E A container path of an invalidlength was specified. The pathspecified was containerName. Referto the documentation forSQLCODE -297.

ADM6003I A container was not renamedbecause it was not affected by therules defined in the path renameconfiguration file configFile. Itsname remains as contname.

ADM6014W EXTENDED STORAGE isenabled for use with the databasebut no buffer pools areconfigured to use it. Memory forEXTENDED STORAGE will notbe allocated. If buffer pools maybe configured to use it in thefuture then it is recommendedthat this message be ignored.EXTENDED STORAGE can bedisabled by changing theNUM_ESTORE_SEGS databaseconfiguration parameter.


ADM6015W EXTENDED STORAGE isdisabled for the database but oneor more buffer pools areconfigured to use it. IfEXTENDED STORAGE may beenabled in the future then it isrecommended that this messagebe ignored. EXTENDEDSTORAGE can be enabled bychanging theNUM_ESTORE_SEGS databaseparameter.

ADM6016W EXTENDED STORAGE isenabled for the database but it isnot supported on this platform.These settings will be ignoredand memory for EXTENDEDSTORAGE will not be allocated.EXTENDED STORAGE can bedisabled by changing theNUM_ESTORE_SEGS databaseconfiguration parameter.

ADM6017E The table space tablespaceName (IDtablespaceID) is full. Detected oncontainer contPath (ID containerID).The underlying file system is fullor the maximum allowed spaceusage for the file system has beenreached. It is also possible thatthere are user limits in place withrespect to maximum file size andthese limits have been reached.

ADM6018I Unmounting filesystem atdirectory-path.

ADM6019E All pages in buffer pool bpname(ID bpid) are in use. Refer to thedocumentation for SQLCODE-1218.

ADM6020I Leaving mounted filesystem usedfor contPath.

ADM6022W Asynchronous drop of atemporary table failed. Theresources associated with thistable will not be freed until nextdatabase startup. You are advisedto restart the database for thisreason. You are also advised tocontact IBM support to determinethe reason for the failure.

ADM6023I The table space tablespaceName (IDtablespaceID) is in state0xtablespaceState. The table spacecannot be accessed. Refer to thedocumentation for SQLCODE-290.

ADM6024C The database cannot be restartedbecause table spaces cannot bebrought ONLINE as a result of anoutstanding WRITE SUSPEND.To restart the database specifyWRITE RESUME on theRESTART DATABASE command.

ADM6025I The table space tsname (ID tsid) isin state 0xstate). operation is notpossible. Refer to thedocumentation for SQLCODE-290.

ADM6027E AWE is not being used for bufferpool bpname (ID bpid) due to anAWE initialization failure. Ensurethat AWE is configured correctlyon the operating system platformand for use with DB2.

ADM6028W The registry variable settingregvarstr was ignored because ofan out of memory condition thatdid not permit the processing ofthe registry variable setting.


ADM6029W The registry variable setting(regvarstr) was ignored because thespecified setting is invalid.

ADM6030W AWE is not being used for bufferpool ID bpid because the registryvariable setting in DB2_AWE(regvarstr) is invalid. This bufferpool or it’s size parametersspecified in the registry variableare invalid.

ADM6031W EXTENDED STORAGE wasconfigured for use with bufferpool bpname (ID bpid) but thisconfiguration will be ignoredbecause AWE is enabled for thedatabase. EXTENDED STORAGEshould be disabled and bufferpools should be configured not touse it.

ADM6032W Buffer pool bpname (ID bpid)which is configured to be blockbased will not be made blockbased because AWE is in use forthe specified buffer pool.

ADM6033E AWE initialization failed. AWEsettings will be ignored. Ensurethat AWE is configured correctlyon the operating system platformand for use with DB2. Bufferpools will be using sizes definedin the catalogs.

ADM6034W EXTENDED STORAGE wasconfigured for use with bufferpool bpname (ID bpid) but thisconfiguration will be ignoredbecause the DB2_OVERRIDE_BPFregistry variable is set. Thisregistry variable is only meant tobe used under the direction ofIBM support.

ADM6035W Scattered read could not be usedbecause the registry variableDB2NTNOCACHE was not set.Set the DB2NTNOCACHEregistry variable to enablescattered read.

ADM6036W EXTENDED STORAGE is beingused for multiple page sizes.Performance may not be optimal.Refer to the DB2 documentationfor more information regardingthe use of EXTENDEDSTORAGE.

ADM6037W Container path was created to beuserBytes KB in size on a devicethat is userBytes KB in size. Extrastorage will be wasted. Thecontainer can be extended to usethe wasted space by using ALTERTABLESPACE.

ADM6038E Unable to perform an operationon container path because it doesnot exist in table space tsname (IDtsid). Refer to the documentationfor SQLCODE -298.

ADM6039E Invalid stripe set sset specified inALTER TABLESPACE for tablespace tsname (ID tsid). Maximumstripe set in table space is maxsset.

ADM6040E Invalid container size specifiedfor container contpath. The numberof pages specified for use is toolarge. Refer to the documentationfor SQLCODE -1422.


ADM6041E An operation for table spacetsname (ID tsid) was not successfulbecause the size of a REGULARor USER TEMPORARY tablespace cannot exceed maxPagespages. Refer to the documentationfor SQLCODE -1139.

ADM6042E An operation for table spacetsname (ID tsid) was not successfulbecause the size of a LONG orSYSTEM TEMPORARY tablespace cannot exceed 2 TB.

ADM6044E The DMS table space tsname (IDtsid) is full. Additional space canbe added to the table space byeither adding new containers orextending existing ones using theALTER TABLESPACE SQLstatement.

ADM6045I WRITE_SUSPEND state has beenremoved from table space tsname(ID tsstate) because the WRITERESUME option was issued.

ADM6046I Multi-page file allocation alreadyenabled. Enabling it again has noeffect.

ADM6047W The table space tsname ( ID tsid) isin the DROP_PENDING state.The table space will be keptOFFLINE. The table space state is0xstate. This table space isunusable and should be dropped.

ADM6048I The table space tsname (ID tsid),which was previously OFFLINEhas been brought back ONLINE.The table space state is 0xstate.

ADM6049E The database cannot be restartedbecause one or more table spacescannot be brought online. Torestart the database specify the″DROP PENDINGTABLESPACES″ option on theRESTART DATABASE command.WARNING! PUTTING ATABLESPACE INTO THE DROPPENDING STATE MEANS THATNO FURTHER ACCESS TO THETABLESPACE WILL BEALLOWED. ITS CONTENTSWILL BE INACCESSIBLETHROUGHOUT THEREMAINDER OF THE LIFE OFTHE TABLESPACE AND THEONLY OPERATION THAT WILLBE ALLOWED ON IT IS ″DROPTABLESPACE″. There is no wayin which it can be brought back.It is important that you considerthe consequences of this action asdata can be lost as a result. Beforeproceeding consult the DB2documentation and contact IBMsupport if necessary. The tablespaces to specify in the DROPPENDING TABLESPACES listare: tsnames.

ADM6050W The ALTER BUFFERPOOLstatement for buffer pool bpname(ID bpid) was successful but couldnot be performed immediatelybecause of insufficient memory.The change will take effect on thenext database startup. Refer to thedocumentation for SQLCODE20189.


ADM6051E Reorg failure has occurred duringRESTART DATABASE (CrashRecovery). An index will fail tobe recreated because theassociated table is in a table spacethat is in DROP_PENDING. Toprevent this failure, set theINDEXREC databaseconfiguration parameter to″ACCESS″ to delay indexrecreation until RESTARTDATABASE completes.

ADM6052E Invalid container size specifiedfor container contpath in ALTERTABLESPACE. The number ofpages specified for use is toosmall. Refer to the documentationfor SQLCODE -1422.

ADM6053W The CREATE BUFFERPOOLstatement for buffer pool bpname(ID bpid) could not be performedimmediately because not enoughfree memory existed in thedatabase shared memory. Thebufferpool will be created on thenext database restart. Refer to thedocumentation for SQLCODE20189.

ADM6054I DB2DART encountered tablespace tsname (ID tsid) which iscurrently not accessible. SinceDB2DART is a diagnostic utility itwill continue working on thistable space.

ADM6055I Page pagenum was requested fromtable space tsname (ID tsid) but isnot yet available because arebalance which is in progress onthis table space has not yet madethat space useable. The requestorwill wait for the page to becomeavailable.

ADM6056I Prefetch queue full has beenencountered. A prefetch requesthas not been queued as a resultand performance will not beoptimal. Reconsider the prefetcherconfiguration (NUM_IOSERVERS,PREFETCHSIZE) and number ofcontainers in each table space.

ADM6057I Prefetch queue full has beenencountered. Agent will wait forspace to free up on the queue andthus performance will not beoptimal. Reconsider the prefetcherconfiguration (NUM_IOSERVERS,PREFETCHSIZE) and number ofcontainers in each table space.

ADM6058I Rebalancer for table space tsname(ID tsid) was started.

ADM6059I Rebalancer for table space tsname(ID tsid) was restarted.

ADM6061I Rebalance for table space tsname(ID tsid) stopping. The last extentmoved by the rebalance waslastext.

ADM6062I Rebalance for table space tsname(ID tsid) has been completed.

ADM6063I Rebalance for table space tsname(ID tsid) has been paused.

ADM6064I Rollforward is waiting onrebalance of table space tsname(ID tsid) to complete.

ADM6065I An attempt was made to removethe OFFLINE state from tablespace tsname (ID tsid) but it wasnot offline. This command will beignored. The table space state is0xtsstate.


ADM6066I An attempt was made to removethe OFFLINE state from tablespace tsname (ID tsid) but theaction was not successful and sothe table space will remain in thisstate. The table space state is0xtsstate. Refer to thedocumentation for SQLCODE-293.

ADM6067W The specified AWE win/phys sizefor buffer pool ID bpid. was lowerthan the allowable minimum. Ithas been raised to the allowableminimum of newsize.

ADM6068I The buffer pool bpname (ID bpid)is using AWE. Physical size isphysize. Window size iswindowSize.

ADM6069W Buffer pool bpname (ID bpid) has aNUMBLOCKPAGES value ofoldNumBlockPages which exceedsthe maximum supported value fora buffer pool of this size. TheNUMBLOCKPAGES value forthis buffer pool has been reducedto newNumBlockPages for itscurrent activation. The value ofNUMBLOCKPAGES can bepermanently changed by usingthe ALTER BUFFERPOOL SQLstatement.

ADM6070W Buffer pool bpname (ID bpid) has aNUMBLOCKPAGES value ofnumBlockPages. This value issmaller than the smallestallowable value forNUMBLOCKPAGES which is theBLOCKSIZE of blockSize. As aresult the buffer pool will not bemade block based for its currentactivation. The value forNUMBLOCKPAGES can bepermanently changed by usingALTER BUFFERPOOL SQLstatement.

ADM6071I The maximum number of pinnedpages allowed concurrently wasreached in buffer pool bpname (IDbpid). As a result performance maynot be optimal. Increasing theSORTHEAP databaseconfiguration parameter mayreduce the chances of thiscondition occurring in the future.

ADM6072W Disk full was encountered whenwriting out a temporary pagefrom buffer pool bpname (ID bpid).The buffer pool cannot bedecreased in size until allnecessary pages have been writtento disk. Refer to previousmessages in the administrationnotification log for detailsregarding the disk full condition.DB2 will continue to retry writingthis page to disk until the diskfull condition is resolved.

ADM6073W The table space tsname (ID tsid) isconfigured to use buffer pool IDondiskBP, but this buffer pool isnot active at this time. In theinterim the table space will usebufferi pool ID RTBP. Theinactive buffer pool shouldbecome available at next databasestartup.


ADM6074I An attempt was made to put tablespace tsname (ID tsid) in theWRITE_SUSPEND state but thistable space is already in theWRITE_SUSPEND state.

ADM6075W The table space tsname (ID tsid)has been placed in theWRITE_SUSPEND state. All writeI/O for this table space will besuspended until a WRITERESUME is issued.

ADM6076W The table space tsname (ID tsid)which was previously in theWRITE_SUSPEND state is nolonger in that state. Write I/O hasbeen resumed to the table space.

ADM6077I An attempt was made to removetable space tsname (ID tsid) fromthe WRITE_SUSPEND state butthis table space was not in theWRITE_SUSPEND state.Specifying WRITE RESUME hasno effect in this case.

ADM6078W The following table spaces werespecified on the RESTARTDATABASE command to beplaced in the DROP_PENDINGstate: tsnames.

ADM6079E The table space tsname (ID tsid),was in theROLLFORWARD_IN_PROGRESSstate but can no longer beaccessed. The table space hasbeen taken offline and put intothe RESTORE_PENDING state.

ADM6080E The table space tsname (ID tsid),was put OFFLINE and inROLLFORWARD_PENDING.Tablespace state is 0xtsstate.

ADM6081W The table space tsname (ID tsid) isin the OFFLINE state and is notaccessible. The table space state is0xtsstate. Refer to thedocumentation for SQLCODE-293.

ADM6500W The connection for theDATALINK file server fileServerhas failed. The server is blocked.

ADM6501W The connection for theDATALINK file server fileServerhas failed to restart.

ADM6502W The connection for theDATALINK file server fileServerhas failed.

ADM6510W The DATALINK file serverfileServer has not been registered.

ADM6511W The DATALINK file serverfileServer is not active.

ADM6512W DB2 is unable to read from theDATALINK configuration file.

ADM6513W DB2 is unable to create theDATALINK configuration filefileName.

ADM6514W An error has occurred while DB2was writing to the DATALINKconfiguration file.

ADM6515W An error has occurred while DB2was closing the DATALINKconfiguration file.

ADM6516W DB2 is unable to open theDATALINK configuration filefileName.


ADM6517W Either an attempt to add a DataLinks Manager of a type differentthan that of the existing DataLinks Manager(s) (typeOfServers)or an attempt to add a secondDFS Data Links Manager wasmade. All Data Links Managersfor a database must be of thesame type, and only one DataLinks Manager of type DFS maybe added.

ADM7000W An invalid SEARCH discoveryprotocol, fileName, was specified inthe DISCOVER_COMM registryvariable.

ADM7001E The DB2 functionsqloinstancepath has failed. Theinstance path was not set. If youare on UNIX, check theDB2INSTANCE registry variable.If you are on Windows, check theDB2INSTANCE, DB2PATH, andDB2INSTPROF registry variables.

ADM7004E An invalid value (value) wasspecified for the DB2COMMregistry variable.

ADM7005W The DISCOVER mode was set toSEARCH. However, theDISCOVER_COMM registryvariable was not configured withany protocols.

ADM7006E The SVCENAME DBMconfiguration parameter was notconfigured. Update theSVCENAME configurationparameter using the service namedefined in the TCP/IP servicesfile.

ADM7007E The SVCENAME DBMconfiguration parameter,socketAddress, is configured with aport or a service name. When it isconfigured with a service name,the TCP/IP services files is usedto map the service name to a portnumber. The port specified in thisfield is being used by anotherprocess. Resolve this problem byeither deleting the process usingthe port or use another port.

ADM7008W The DB2TCPCONNMGRSregistry variable value, userValue,is invalid. A valid value is from 1to 8. A defaultDB2TCPCONNMGRS value ofdefaultValue has been used.

ADM7009E An error was encountered in theprotocolTCPIP protocol support. Apossible cause is that themaximum number of agents hasbeen exceeded.

ADM7011E The Sync Point Manager does notsupport the version of MicrosoftSNA Server installed on thismachine. Minimum requirementis Microsoft SNA Server V4Service Pack 3.

ADM7500W Instance quiesce has beenrequested.

ADM7501W Instance quiesce request hascompleted successfully.

ADM7502E Instance quiesce request hasfailed. The SQLCODE isSQLCODE.

ADM7503W Instance unquiesce request hascompleted successfully.


ADM7504W Instance unquiesce has beenrequested.

ADM7505E Instance unquiesce request hasfailed. The SQLCODE isSQLCODE.

ADM7506W Database quiesce has beenrequested.

ADM7507W Database quiesce request hascompleted successfully.

ADM7508E Database quiesce request hasfailed. The SQLCODE isSQLCODE.

ADM7509W Database unquiesce request hascompleted successfully.

ADM7510W Database unquiesce has beenrequested.

ADM7511E Database unquiesce request hasfailed. The SQLCODE isSQLCODE.

ADM7512E A transaction resynchronizationerror has occurred, contact IBMSupport for assistance.

ADM7513W Database manager has started.

ADM7514W Database manager has stopped.

ADM7515W The concentrator has beenenabled without directory cachingsupport which may result in aperformance penalty. To correctthis problem, enable directorycaching in the database managerconfiguration.

Explanation: Directory caching is a feature withrelatively low overhead that is enabled bydefault in the engine. There are only a few validreasons why a user may want to disable it. Theconcentrator configurations are particularlysensitive to having directory caching turned offbecause the dispatcher processes, which are thebottleneck for concentrator, could be potentiallyrequired to go to disk with every newconnection.

User Response: Enable directory caching, or runin a non-concentrator configuration.

ADM7516W The MAX_CONNECTIONSconfiguration parameter has beenset to maxConnectionsValue, but dueto hardware limitations amaximum number of actualValueconnections will be supported.You may be able to increase thislimit by decreasing the NUM_DBdatabase configuration parameter.

Explanation: On non-threaded (UNIX)platforms, the concentrator scalability is boundedby the maximum number of file-descriptorsavailable to an individual process. Differentoperating systems allow various levels offlexibility in this parameter, and hence eachoperating system will have a different physicallimit on the maximum number of connectionssupported. The defined range ofMAX_CONNECTIONS (1..64000) should besupported, but in cases where it isn’t, the defaultvalue at runtime will be used.

Additionally, the NUM_DB DB configurationparameter affects the way file descriptors areallocated, and reducing this configurationparameter will free up file descriptors and thuswill increase the limits on the number ofconnections that can be supported.


User Response: If possible, lower the NUM_DBDB configuration parameter to increase thephysical limit on the number of connections. Ifthe warning still occurs, lower theMAX_CONNECTIONS parameter to thespecified physical limit in the warning.

ADM7517W When the concentrator is enabled,the maximum number ofapplications per application groupin the database databaseName willbe limited to maxApp. To correctthis problem, decrease the valueof the APPGROUP_MEM_SZconfiguration parameter.

ADM7518C dbName marked bad.

ADM7519W DB2 could not allocate an agent.The SQLCODE is SQLCODE.

ADM7520E Mount unmounted filesystem(s)has failed on node nodeNum.Manual remount is requiredbefore retrying migration. CheckerrorFile and remount thefilesystems before retryingmigration.

ADM7521E Unmount mounted filesystem(s)has failed on node nodeNum.Remount the unmountedfilesystem(s) and try the databasemigration again.

ADM7522E Remount unmounted filesystem(s)to new mount points has failed onnode nodeNum. Restart databasemigration is needed.

ADM7523E DB2 was unable to allocate theapplication group memory set.This will cause databaseactivation to fail. Reduce theAPPGROUP_MEM_SZ DBconfiguration parameter and retry.

ADM8000C Backup has been terminated. TheSQLCODE returned is SQLCODE.

ADM8001W Incremental backup was notenabled for this database becausethe TRACKMOD DBconfiguration parameter was notenabled.

ADM8002W This backup image cannot beused for ROLLFORWARDbecause the logs associated withthis backup has been overwrittenon the raw device. Use a morerecent backup image.

ADM8003C Restore has been terminated. TheSQLCODE returned is SQLCODE.

ADM8004W Incremental backup was notenabled for table spacetablespaceName (ID tablespaceID)because the TRACKMODconfiguration parameter was notenabled.

ADM8005W Incremental backup was notenabled for table spacetablespaceName (ID tablespaceID). Anon-incremental backup of thistable space is required.

ADM8006W DB2 cannot use the specifiedrestore buffer size ofrestoreBufferSize 4K pages. Arestore buffer size must bemultiple of backup buffer size ofbackupBufferSize 4K pages. Therestore operation will continuewith the default buffer size.

ADM8007W DB2 cannot perform multipleconcurrent incremental restores.


ADM8008W DB2 could not find and/or deletethe online reorganization statefiles for all table spaces duringrestore. Manual intervention maybe needed to remove the file(s).

ADM8009W Could not find and/or delete theonline reorganization state filesfor table space tablespaceName (IDtablespaceID ) during restore.Manual intervention may beneeded to remove the file(s).

ADM8500W DB2 has failed to read from thehistory file because of a possibledata corruption. Ensure that thefile exists and is intact.

ADM8501W DB2 has failed to write to thehistory file because the disk isfull.

ADM8502W The history file is corrupt. Anunrecoverable error has beendetected with the file. Theexisting file has been deleted anda backup has been made. If youwould like to determine the rootcause of the problem, contact IBMSupport. Otherwise, no furtheraction is needed.

ADM8503W DB2 was unable to record ahistory entry for operationoperation.

ADM9000W Prefetching was disabled duringsort merge; performance may besuboptimal. If this messagepersists, consider increasing thebuffer pool size for temporarytable space tablespaceName (IDtablespaceID) or increase the valueof the SORTHEAP DBconfiguration parameter to reducethe extent of sort spilling.

ADM9500W Too many concurrent updates hadoccurred on table tableName (IDtableID) and table spacetablespaceName (ID tablespaceID)during online indexcreate/reorganization. Thus, it willtake a longer time to finish onlineindex create/reorganization. Youmay want to increase yourUTIL_HEAP_SZ DB configurationparameter.

ADM9501W BEGIN online indexreorganization on table tableName(ID tableID) and table spacetablespaceName (ID tablespaceID).

ADM9502W END online index reorganizationon table tableName (ID tableID) andtable space tablespaceName (IDtablespaceID).

ADM9503W Online index reorganizationproceeds on index ID indexID intable tableName (ID tableID) andtable space tablespaceName (IDtablespaceID).

ADM9504W Online index reorganization ontable tableName (ID tableID) andtable space tablespaceName (IDtablespaceID) failed on this nodewith SQLCODE SQLCODE reasoncode reasonCode. To resolve thisproblem, re-submit the REORGINDEXES command on the failingnode(s).


ADM9505W Online index reorganization ontable tableName (ID tableID) andtable space tablespaceName (IDtablespaceID) has been switched tooffline mode because the indexesare marked for rebuild. Theseindexes may have been markedfor rebuild during a roll forwardthrough an index creation and/orrecreation. If this is the case,consider setting the INDEXRECdatabase manager configurationparameter to RESTART. This willcause indexes that are marked forrebuild during roll forward to berebuilt during RESTARTDATABASE processing.

ADM10000W A Java exception has beencaught. The Java stack tracebackhas been written to thedb2diag.log.

ADM10500E Health indicatorHealth-Indicator-Short-Description(Health-Indicator-Short-Name)breached the Threshold-Bound-Namealarm threshold ofThreshold-Bound-Value with valueHealth-Indicator-Value onMonitored-Object-TypeMonitored-Object-Name. Calculation:Formula-String =Formula-with-Values =Health-Indicator-Value. History(Timestamp, Value, Formula):Health-Indicator-History-List

Explanation: The health monitor generated analert because the alarm threshold for this healthindicator was breached. This situation should beaddressed immediately as it can lead to adegradation in database performance or aninterruption in operation.

User Response: You can use one of thefollowing tools to obtain recommendations, andin some cases take actions, to resolve this alert.

Health Center:

If the Control Center tools are installed, you canlaunch this tool in one of the following ways:

v Start Menu on Windows

v Control Center toolbar

v command line as ″db2hc″

Health indicator description, recommendedactions, and links to tools to effect the actions areprovided.

Web Health Center:

If the Web-based tools are installed, then you canlaunch this tool from a web browser using theURL provided to you by your web administrator.

Health indicator description, recommendedactions, and some links to tools to effect theactions are provided.

Command Line Processor (CLP):

From the CLP, you can obtain the Healthindicator description and recommended actionsby executing the following commands:

v GET RECOMMENDATIONS FOR HEALTHINDICATOR Health-Indicator-Short-Name

v GET DESCRIPTION FOR HEALTHINDICATORHealth-Indicator-Short-Name

ADM10501W Health indicatorHealth-Indicator-Short-Description(Health-Indicator-Short-Name)breached the Threshold-Bound-Namewarning threshold ofThreshold-Bound-Value with valueHealth-Indicator-Value onMonitored-Object-TypeMonitored-Object-Name. Calculation:Formula-String =Formula-with-Values =Health-Indicator-Value. History(Timestamp, Value, Formula):Health-Indicator-History-List

Explanation: The health monitor generated analert because the warning threshold for thishealth indicator was breached. This condition


does not necessarily require immediate attention,but rather it may lead to a degradation indatabase performance or an interruption inoperation if the condition worsens over time.


Health Center:






Web Health Center:





v GET ALERT RECOMMENDATION FORHealth-Indicator-Short-Name

v GET ALERT HEALTH INDICATORDESCRIPTION FOR Health-Indicator-Short-Name

ADM10502W Health indicatorHealth-Indicator-Short-Description(Health-Indicator-Short-Name) is instate Health-Indicator-Value onMonitored-Object-TypeMonitored-Object-Name.

Explanation: The health monitor generated analert because the state value of this healthindicator was non-normal. This condition doesnot necessarily require immediate attention, butrather it will depend on the expected state of thedatabase given operations being performed on itat the time, and the prevailing workload.


Health Center:






Web Health Center:





v GET ALERT RECOMMENDATION FORHealth-Indicator-Short-Name


v GET ALERT HEALTH INDICATORDESCRIPTION FOR Health-Indicator-Short-Name

ADM10503I The health monitor has initiatedan alert action, runningAlert-Action-Type Alert-Action-Nameon system System-Name, becausethe Health IndicatorHealth-Indicator-Short-Description(Health-Indicator-Short-Name) is inthe Alert-State alert state onMonitored-Object-TypeMonitored-Object-Name.

Explanation: The health monitor wasconfigured to initiate the action when the healthindicator is in this alert state. This message is anindication that the action was indeed initiated.

User Response: No action is required.

ADM10504E The health monitor failed, withsqlcode SQLCODE, to initiate analert action, runningAlert-Action-Type Alert-Action-Nameon system System-Name, when theHealth IndicatorHealth-Indicator-Short-Description(Health-Indicator-Short-Name) wentinto the Alert-State alert state onMonitored-Object-TypeMonitored-Object-Name.

Explanation: The health monitor wasconfigured to initiate the action when the healthindicator is in this alert state, but received thisSQLCODE when it called the API to execute theaction. The alert action was not initiated.

User Response: Check the First Failure Servicelog (DB2DIAG.LOG) for a record detailing thefailure.

ADM10505E The DB2 Service does not havethe necessary authority to run theHealth Monitor. The HealthMonitor has been shut down. Ifthe service is configured to log onusing the Local System account(SYSTEM), then it must bechanged to log on with aparticular user account. If it isconfigured to log on with aparticular user account, then youmust ensure that the user accountis valid and has the necessaryaccess rights to run the DB2service. Once the log onconfiguration has been corrected,it is necessary to restart the DB2service to start the HealthMonitor.

ADM10506E The health monitor is unable tosend an alert notification becausethe SMTP Server (smtp_server)DB2 Administration Serverconfiguration parameter is not set.Update the smtp_serverconfiguration parameter with thename of a valid SMTP server.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because no SMTP server name wasspecified for the SMTP Server DAS configurationparameter.

User Response: Update the smtp_serverconfiguration parameter with the name of a validSMTP server.


ADM10507E The health monitor was unable tosend an alert notification becausethe server SMTP-Server-Name,specified in the SMTP Server DB2Administration Serverconfiguration parameter(smtp_server), does not appear tobe an SMTP server. Ensure that avalid SMTP server name isspecified in the DB2Administration Serverconfiguration.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because the server specified in theDB2 Administration Server configuration doesnot have SMTP server functionality.

User Response: Ensure that a valid SMTPserver name is specified in the DB2Adminstration Server configuration for thesmtp_server parameter.

ADM10508E The health monitor was unable tosend an alert notification becauseinvalid recipient(s) were specifiedin the health notification listwhich contains Notification-List.Update the Contact record withthe invalid address.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because one or more addresses forthe contacts specified on the health notificationlist are invalid.

User Response: Check the Contact record forthe contacts specified for health notification andupdate the invalid recipient address.

ADM10509E The health monitor was unable tosend an alert notification becausethe notification was sent by aninvalid Sender with the addressSender-Address. Look at the SMTPserver configuration. If all thesettings are correct, contact DB2Support.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because the Sender address wasrejected as unacceptable by the SMTP server. TheSender address has the format <instancename>@<host>, where ’instance’ is running on’host’.

User Response: Look at the SMTP serverconfiguration. If all the settings are correct,contact DB2 Support.

ADM10510E The health monitor was unable tosend an alert notification becausethe SMTP server issued thefollowing error: SMTP_ERROR.Check the SMTP serverdocumentation for information onthe error code that was returned.If the problem cannot beremedied, contact DB2 Support.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because the SMTP serverencountered an error.

User Response: Check the SMTP serverdocumentation for information on the error codethat was returned. If the problem cannot beremedied, contact DB2 Support.


ADM10511E The health monitor was unable tosend an alert notification becausethere was a communication errorwith the SMTP server. Check theFirst Failure Service log(DB2DIAG.LOG) for a recorddetailing the failure.

Explanation: The health monitor wasconfigured to send notifications upon alertoccurrence, but was unable to send thenotification because there was a communicationerror when trying to reach the SMTP server.

User Response: Check the First Failure Servicelog (DB2DIAG.LOG) for a record detailing thefailure.


Chapter 3. ASN messages

This section contains the messages issued by DB2 replication for thereplication programs on all of the database management systems except DB2for iSeries. The messages are listed in numeric sequence.

ASN0004E CAPTURE capture_schema. TheCapture program could not startthe trace. The return code isreturn_code. The reason code isreason_code.

Explanation: An error occurred when theSTART TRACE DB2 command was issued, orwhen the Capture program read the DB2 log.

User Response: See the DB2 Codes section inthe messages and codes documentation of theDB2 database manager on your operating systemto find the appropriate reason code. For moreinformation, see either of the followingadministration documentation: the CallAttachment Facility (CAF) for START TRACEDB2 errors, or the Instrumentation FacilityInterface (IFI) for DB2 log read errors, or contactyour DBA. If the CAF or the IFI returned amessage, it is also printed on the system displayconsole.

ASN0005E CAPTURE capture_schema. TheCapture program encountered anerror when reading the DB2 log.The log sequence number is lsn,the SQLCODE is sql_return_code,and the reason code is reason_code.

Explanation: An error occurred when theCapture program read the DB2 log. There mightbe an SQL error.

v For DB2 Replication, the sqlcode value is forthe Asynchronous Read Log API.

v For Capture for VSE, the sqlcode is for theVSE/VSAM GET macro.

v For Capture for VM, the sqlcode is for DiagnoseX’A4’.

User Response: See the DB2 Codes section in

the messages and codes documentation of theDB2 database manager on your operating systemfor the appropriate reason code, as suggestedbelow:

v For Capture program for z/OS, see theInstrumentation Facility Interface (IFI) sectionin the administration documentation of theDB2 database manager on your operatingsystem, or contact your DBA.

v For Capture for VSE, see the VSE/VSAMCommands and Macros, VSE/ESA SystemMacro Reference, and VSE/ESA V2R3Messages and Codes manuals for moreinformation.

v For VM/ESA, see the VM/ESA ProgrammingServices for more information.

v For Capture on Linux, Windows, UNIX, andOS/2, see the active and archived databaselogs administration documentation for DB2Universal Database, or contact IBM SoftwareSupport.

ASN0006E CAPTURE capture_schema. TheCapture program encountered anunexpected log error of unknownlog variation.

Explanation: An unexpected log error occurredwhen the Capture program was processing theDB2 log records, and was not reported by eitherof the following interfaces:

v The Instrumentation Facility Interface (IFI) forCapture program for z/OS

v The Asynchronous Read Log API for theCapture program

The Capture program could not determine whichtype of SQL update was associated with the logrecord.


User Response: Contact IBM Software Support.

ASN0008I CAPTURE capture_schema. TheCapture program was stopped.

Explanation: The Capture program has stopped.

User Response: This message is for yourinformation only, and no action is required.

ASN0009E CAPTURE capture_schema. Theregistered source tablesrc_owner.src_table does not havethe DATA CAPTURE CHANGESattribute.

Explanation: When attempting to initialize aregistration, the Capture program encountered asource table that is incorrectly defined. TheCapture program cannot process the log recordsassociated with a source table if the DATACAPTURE CHANGES attribute of the sourcetable is not set. This registration is not valid andtypically occurs only if you generated thisregistration outside of the suppliedadministration tools. This message is issuedduring a Capture program warm start or whenthe first CAPSTART signal is received for asubscription set against this registration. If thiserror occurs during the processing of aCAPSTART signal, the Capture program does notactivate the registration. If this error occursduring a reinitialization (from a warm start or areinit capture command), the Capture programplaces the registration in the ″stopped″ state,indicating that you must repair the registrationbefore the Apply program can resynchronize theassociated subscription sets.

User Response:

1. Alter the source table to turn on data capturechanges. For example:

v alter table regress.table3 data capture changes

2. If the registration has been deactivated by theCapture program (state = stopped), updatethe registration to set the state to inactive.

3. Use the Replication Center to force the Applyprogram to perform a full refresh for allsubscription sets that replicate from thissource table.

ASN0011E CAPTURE capture_schema. TheCapture program log read failedbecause the DB2 compressiondictionary that was used to createthe compressed log record nolonger exists. The log record thatcould not be read was for theregistered source tablesrc_owner.src_table. The reasoncode is reason_code.

Explanation: The Capture program received anonzero response code from the DB2 log readIFI. The response code indicates that the data ona log record cannot be processed because thecompression dictionary for the correspondingDB2 table space is not available.

The compressed table space containing thissource table was probably reorganized by theREORG utility that ran without theKEEPDICTIONARY option. The Captureprogram must deactivate this registration,because the remaining compressed log recordscannot be read. The Capture program cannotcontinue unless this registration is deactivated orremoved. This error does not cause the Captureprogram to terminate.

User Response: See the Maintaining yourreplication environment chapter for restrictionsabout compressed table spaces and for moreinformation about deactivated registrations andcorresponding full refreshes by the Applyprograms.

ASN0013E CAPTURE capture_schema. TheCapture program required acolumn that was not defined inthe change data (CD) table. Thetable name is table_name.

Explanation: A required column in the changedata table is not defined.

User Response: Ensure that the change datatable definition is correct. Refer to the Tablesstructures documentation in the DB2 ReplicationGuide and Reference for more information.


ASN0019E CAPTURE capture_schema. TheCapture program libraries are notauthorized for the AuthorizedProgram Facility (APF).

Explanation: The Capture program cannot start.

User Response: Authorize the Capture linklibrary for APF, and restart the program.

ASN0020I CAPTURE capture_schema. NetviewGeneric Alerts Interface failure.The Netview return code isreturn_code.

Explanation: The Network Major VectorTransport (NMVT) could not be sent to Netviewby the program because the program interfacefailed. This is a secondary informationalmessage.

User Response: See the Netview programmingdocumentation for a description of the returncode to determine the interface error. TheCapture program alerts are not received by theSystem Services Control Point (SSCP) until theerror is corrected.

ASN0021I CAPTURE capture_schema. NetviewProgram to Program Interfaceunavailable. The Netview returncode is return_code.

Explanation: Netview is unavailable. This is asecondary informational message.

User Response: See the Netview programmingdocumentation for a description of the returncode to determine the Netview problem. Forexample, the subsystem might not have beenstarted.

ASN0023I CAPTURE capture_schema. TheCapture program has beenreinitialized and is capturingchanges for number registrations.Stopped_number registrations are ina stopped state. Inactive_numberregistrations are in an inactivestate.

Explanation: A REINIT command was issued tothe Capture program. The Capture program thentried to refresh all the internal controlinformation for all the registrations.

User Response: If the Capture program iscapturing changes for all the registrations, noaction is required. Otherwise, examine thepreceding error messages to determine the causeof the failure, and follow the suggested userresponse to repair the failing registrationdefinition. After you repair the registration,re-issue the REINIT command to the Captureprogram.

ASN0028I CAPTURE capture_schema. TheCapture program is suspended byan operator command.

Explanation: An operator command hassuspended the Capture program, and theprogram has entered a wait state.


ASN0029I CAPTURE capture_schema. TheCapture program is resumed byan operator command.

Explanation: An operator command hasresumed the Capture program from a suspendedstate, and the Capture program has continuedrunning.


Chapter 3. ASN messages 33

ASN0031E CAPTURE capture_schema. Theprogram parameter tableIBMSNAP_CAPPARMS can haveonly one row.

Explanation: The Capture program parameterstable was not defined correctly or has beenupdated with rows that are not valid.

User Response: Make sure that there is onlyone row in the IBMSNAP_CAPPARMS table.Refer to the Table structures documentation inthe DB2 Replication Guide and Reference foradditional information.

ASN0035E CAPTURE capture_schema. A rowwith an unsupported architecturelevel was found in the tableIBMSNAP_REGISTER. The rowis not valid and specifies CDtable cd_owner.cd_table, and thearchitecture level is arch_level.

Explanation: The Capture program tried toinitialize a registration and found that theregistration definition contains an architecturelevel that is not valid. The Version 8 Captureprogram can use only registrations that are at thearchitecture level of 0801. This registration is notvalid and typically occurs if you generated thisregistration without using the Replication Center.This message is issued during Capture warmstart or when the first CAPSTART signal isreceived for a subscription against thisregistration. This error does not cause theCapture program to terminate.

User Response: Refer to the Tables structuresdocumentation in the DB2 Replication Guide andReference to check the required value for theARCH_LEVEL column in the register table.Verify that the value in the register table at thesource server is correct. If the value is notcorrect, update the value of the architecturallevel of the registration and use compatibleversions of the Replication Center and theCapture program.

ASN0049I CAPTURE capture_schema. A rowfor the SIGNAL_SUBTYPECAPSTOP was inserted into thetable IBMSNAP_SIGNAL.

Explanation: The Capture program received asignal to stop capturing data. The Captureprogram commits current work in progress andterminates.


ASN0055E CAPTURE capture_schema. TheCapture program encountered acolumn column_name with anunsupported SQLTYPE in tabletable_name.

Explanation: The Capture program tried toinitialize a registration and found that theregistration definition contains an unsupportedSQL type such as an abstract type. Thisregistration is not valid and typically occurs ifyou generate this registration outside of thesupplied administration tools. This message isissued during Capture warm start or when thefirst CAPSTART signal is received for asubscription against this registration. This errordoes not cause the Capture program toterminate.

User Response: Remove this registration; itcannot be supported by DB2 replication.

ASN0057E CAPTURE capture_schema. TheCapture program encounterederror errno on operation for filefilename.

Explanation: An error occurred when theCapture program was handling files. TheCapture program terminates.

User Response: Ensure that the Captureprogram has correct access and securitypermissions for all required paths and files. Also,ensure that adequate space is available on yoursystem. If you believe that this message wasissued because of product failure, contact IBMSoftware Support for assistance.


ASN0058W CAPTURE capture_schema. TheMAP_ID mapid in a CAPSTARTrow in the IBMSNAP_SIGNALtable does not correspond to anyentry in theIBMSNAP_PRUNCNTL table.

Explanation: The value for the MAP_ID that isspecified by the CAPSTART signal does notmatch any current value in the MAP_ID columnof the IBMSNAP_PRUNCNTL table. Thesubscription set might have been deleted, or auser might have inserted the CAPSTART signalincorrectly.

User Response: If this CAPSTART was issuedby a user, check that the MAP_ID for the Signaltable insert is correct, and try again. If thisCAPSTART signal was issued by the Applyprogram, verify that the subscription set stillexists.

ASN0059W CAPTURE capture_schema. TheSYNCHPOINT field in theIBMSNAP_PRUNCNTL table isnot zeros for the CAPSTART ofsubscription with MAP_IDmap_id.

Explanation: When the Apply program signalsa full refresh to the Capture program, the Applyprogram inserts a row for the CAPSTART signalin the IBMSNAP_SIGNAL table. At the sametime, the SYNCHPOINT column of theIBMSNAP_PRUNCNTL table is set to hex zeroes.The Capture program then responds to theApply program to confirm that the Captureprogram received the CAPSTART signal, asfollows: the Capture program sets the value forthe SYNCHPOINT column in theIBMSNAP_PRUNCNTL table to the number ofthe log sequence that corresponds to theCAPSTART log record. Because the Applyprogram set the value in the SYNCHPOINTcolumn to hex zeroes, the Apply program checksif a nonzero value has been inserted by theCapture program. The Capture program updatesthe value for SYNCHPOINT, even if the valuewas not hex zeroes. However, if the value forSYNCHPOINT is not hex zeroes, the Capture

program issues this warning that the value itfound was not expected.

This warning can occur if you issue the APPLYCAPSTART signal yourself and do notcompletely simulate the actions of the Applyprogram.


ASN0060E CAPTURE capture_schema. TheCapture program encountered aninternal error error_code.

Explanation: An unexpected error occurred inthe Capture program. The Capture programterminates.

User Response: Contact IBM Software Supportfor assistance.

ASN0061E CAPTURE capture_schema. Aregistration that is not valid hasbeen found. Source tablesource_owner.source_table does notexist in the system catalog tables.

Explanation: The Capture program tried toinitialize a registration and found that the sourcetable specified in the registration was not in thesource system catalog. This message is issuedduring Capture warm start or when the Applyprogram issues the first CAPSTART signal for asubscription set that contains a registration thatis not valid. This error does not cause theCapture program to terminate. The values for thecolumns source_owner and source_table in theCapture control table IBMSNAP_REGISTERmight have been incorrectly specified, or thesource table was dropped and no longer exists.

User Response: If the registration is in error,correct the values for the columns source_ownerand source_table. If the source table no longerexists, then the registration is no longer validand can be removed.


ASN0062E CAPTURE capture_schema. Aregistration that is not valid hasbeen found. CD tablephys_change_owner.phys_change_tabledoes not exist in the systemcatalog tables.

Explanation: The Capture program tried toinitialize a registration and found that the CDtable specified in the registration was not in thesource system catalog tables. This message isissued during Capture warm start or when thefirst CAPSTART signal is received for asubscription against this registration. This errordoes not cause the Capture program toterminate. The values for the columnsphys_change_owner and phys_change_table in theCapture control table IBMSNAP_REGISTERmight have been incorrectly specified, or the CDtable was dropped and no longer exists.

User Response: If the registration is in error,correct the values in the columnsphys_change_owner and phys_change_table. If theCD table no longer exists, then the registration isno longer valid and can be removed.

ASN0063E CAPTURE capture_schema. Thesource tablesource_owner.source_table associatedwith the subscription havingMAP_ID mapid does not exist inthe system catalog tables. TheCapture program could not startcapturing changes for thissubscription.

Explanation: The Capture program tried torespond to a CAPSTART signal for a subscriptionand found that the source table whichcorresponds to the subscription was not in thesource system catalog tables. This error messageis issued when the first CAPSTART signal isreceived for a subscription that is not valid. Thiserror does not cause the Capture program toterminate. The values for the columnssource_owner and source_table in the Capturecontrol table IBMSNAP_PRUNCNTL might havebeen incorrectly specified, or the source tablewas dropped and no longer exists.

User Response: If the subscription is in error,correct the values for the columns source_ownerand source_table. If the source table no longerexists, then the subscription is no longer validand can be removed.

ASN0064E CAPTURE capture_schema. Theregistration is not valid for anassociated subscription havingMAP_ID mapid. The Captureprogram cannot start capturingchange data for this subscription.

Explanation: The Capture program tried toinitialize a registration associated with aparticular subscription and found that theregistration contains one or more column valuesthat are not valid. This message is issued whenthe first CAPSTART signal for a subscription isreceived against this registration. This error doesnot cause the Capture program to terminate. Thevalues for the columns phys_change_owner andphys_change_table in the Capture control tableIBMSNAP_REGISTER might have beenincorrectly specified, or the CD table wasdropped and no longer exists.

User Response: If the registration is in error,correct the values for the columnsphys_change_owner and phys_change_table. If theregistration is no longer needed, you can removeit.

ASN0065E CAPTURE capture_schema. Aregistration that is not valid hasbeen found. The source tablesource_owner.source_table is not alocal physical table.

Explanation: The Capture program tried toinitialize a registration and found that the sourcetable for the registration is a not a local physicaltable, but is instead on a non-DB2 relationalserver that is used as a source and called by anickname. When a non-DB2 relational server isused as a source, data from each server iscaptured through a trigger program. Each sourcetable must be in its own register table built onthe non-DB2 relational server. This message isissued during a Capture warm start or when the


first CAPSTART signal against this registration isreceived for a subscription. This error does notcause the Capture program to terminate. Theregistration has been created incorrectly in anIBMSNAP_REGISTER table in a DB2 database.

User Response: This registration must be rebuiltand made valid at the correct non-DB2 relationalserver.

ASN0066E CAPTURE capture_schema. Aregistration that is not valid hasbeen found. The CD tablephys_change_owner.phys_change_tableis not a local physical table.

Explanation: The Capture program tried toinitialize a registration and found that the CDtable for the registration that corresponds to thesubscription is a nickname for a non-DB2relational database used as a source. Thismessage is issued when the first CAPSTARTsignal is received for a subscription against thisregistration. This error does not cause theCapture program to terminate.

User Response: Non DB2 relational sources arecaptured through trigger programs, and must bein their own register table in the non DB2relational source system. CCD tables for suchsources are also created in the non DB2 relationalsource system. Somehow the non-DB2 relationalsource table registration has been incorrectlyregistered in a register table in a DB2 database.This registration must be rebuilt at the correctnon-DB2 relational server.

ASN0067E CAPTURE capture_schema. Theview registration associated withthe subscription having MAP_IDmap_id was not found in the tableIBMSNAP_REGISTER. TheCapture program could not startcapturing change data for thissubscription.

Explanation: The Capture program tried toinitialize a registration and found that the viewregistration that corresponds to the subscriptiondoes not exist. This message is issued duringCapture warm start or when the first CAPSTART

signal is received for a subscription against thisregistration. This error does not cause theCapture program to terminate. The values of thecolumns source_owner, source_table, andsource_view_qual in the IBMSNAP_REGISTER orIBMSNAP_PRUNCNTL Capture control tablecould have been incorrectly specified. Therefore,either no match was found or the registrationwas dropped and no longer exists.

User Response: If the subscription or theregistration is in error, correct the values in thecolumns source_owner, source_table, andsource_view_qual. If the registration no longerexists, then the subscription is no longer validand can be removed.

ASN0068E CAPTURE capture_schema. Theinsert statement is too long forCD tablephys_change_owner.phys_change_table.

Explanation: The number of columns in the CDtable is too large; the SQL INSERT statementexceeds the 32K Capture coding limit.

User Response: If all of the table columns aredefined in the registration but only a subset ofthese columns are needed at the target, reducethe number of columns for that registration.Alternatively, split the table over tworegistrations so that each registration has adifferent subset of the table columns.

ASN0069E CAPTURE capture_schema.SQLCODE sqlcode was returnedduring an insert into the CD tablephys_change_owner.phys_change_table.The CD table appears to havebeen dropped.

Explanation: The Capture program tried toinsert a row into a CD table, and DB2 returned aSQLCODE indicating that the CD table no longerexists. The CD table could inadvertently havebeen dropped, or the whole registration couldhave been dropped. If there are still rows in theIBMSNAP_REGISTER table that refer to this CDtable, the Capture program deactivates theseregistrations by setting the value of theCD_OLD_SYNCHPOINT column to NULL and


no longer attempts to capture changes for thisCD table. This error does not cause the Captureprogram to terminate.

User Response: If the CD table no longer existsand is no longer required, the registration is nolonger valid and should be removed. It isrecommended that you deactivate theregistration before you remove it. Anysubscription sets associated with registrationsthat use this CD table should also be deactivated.Additionally, the associated subscription-setmembers should be removed so that thesesubscription sets can be activated and can runsuccessfully.

ASN0070E CAPTURE capture_schema. Thecombination of column namecolumn_name in the CD tablephys_change_owner.phys_change_table,and the value ofBEFORE_IMG_PREFIXbefore_img_prefix in the tableIBMSNAP_REGISTER for thisregistration matches multiplecolumn names in the source table.The ambiguity in the registrationdefinition cannot be resolved bythe Capture program.

Explanation: The Capture program tried toinitialize a registration and found that a columnwithin the CD table for the registration isambiguous. The column could refer to either abefore image for one source column or to anafter image for another source column. Thismessage is issued during Capture warm start orwhen the first CAPSTART signal is received for asubscription against this registration. This errordoes not cause the Capture program toterminate.

User Response: In the IBMSNAP_REGISTERtable, change the current value in theBEFORE_IMG_PREFIX column to a charactervalue that does not produce this ambiguity.

ASN0071E CAPTURE capture_schema. Thedata type attribute of the columncolumn_name in the CD tablephys_change_owner.phys_change_tableis not compatible with the datatype attribute of thecorresponding source column.

Explanation: The Capture program tried toinitialize a registration and found that a columnwithin the CD table for the registration is notcompatible with the corresponding sourcecolumn. This message is issued during Capturewarm start or when the first CAPSTART signal isreceived for a subscription against thisregistration. This error does not cause theCapture program to terminate.

User Response: Correct the CD table for thisregistration.

ASN0072E CAPTURE capture_schema. Thebefore-image column column_namein the CD tablephys_change_owner.phys_change_tablemust allow NULL values.

Explanation: The Capture program tried toinitialize a registration and found that thebefore-image column within the CD table for theregistration was not defined to accept nullvalues. This message is issued during Capturewarm start or when the first CAPSTART signal isreceived for a subscription against thisregistration. This error does not cause theCapture program to terminate.

User Response: Correct the CD table for thisregistration.

ASN0073E CAPTURE capture_schema. Thespecification input_in describingthe CD table on a CAPSTOPsignal is not valid.

Explanation: The Capture program found thatthe INPUT_IN value specified on the CAPSTOPsignal is not in a valid format ofphys_change_owner.phys_change_table. This errordoes not cause the Capture program toterminate, and no action is taken for this signal.


User Response: Ensure that the value ofINPUT_IN matches the name of the CD tableassociated with the registration that you want todeactivate. Insert a new row into theIBMSNAP_SIGNAL table.

ASN0074E CAPTURE capture_schema. There isno row in theIBMSNAP_REGISTER table thatcorresponds to src_owner.src_tablethat is specified on a CAPSTOPsignal.

Explanation: The Capture program found thatthe INPUT_IN value specified on the CAPSTOPsignal is in a valid format, and there is no matchfor the value of source_owner.source_table in theregistration table. This error does not cause theCapture program to terminate.

User Response: Correct the value of INPUT_IN,and insert the signal again.

ASN0075W CAPTURE capture_schema. Theregistration corresponding to theINPUT_IN, src_owner.src_table on aCAPSTOP signal was notcapturing changes. No action istaken.

Explanation: The Capture program found thatthe INPUT_IN value specified on the CAPSTOPsignal is in a valid format and matches the valueof a source_owner.source_table in the registrationtable, but this registration is already inactive.This error does not cause the Capture program toterminate, and the Capture program takes noaction for the signal.


ASN0076I CAPTURE capture_schema. Capturehas stopped capturing changes forsource tablesource_owner.source_table inresponse to a CAPSTOP signal.

Explanation: The Capture program successfullydeactivated a registration that was specified in aCAPSTOP signal.


ASN0077E CAPTURE capture_schema. Thevalues specified for thePHYS_CHANGE_OWNER andPHYS_CHANGE_TABLE columnsin the IBMSNAP_PRUNCNTLtable where MAP_ID = mapid areNULL or do not match a validrow in the IBMSNAP_REGISTERtable.

Explanation: The Capture program tried toinitialize a registration and found that thecolumn values of PHYS_CHANGE_OWNER andPHYS_CHANGE_TABLE within theIBMSNAP_PRUNCNTL table for the subscriptiondo not match a registration row in theIBMSNAP_REGISTER table. The message wasissued during Capture warm start or when thefirst CAPSTART signal was received for asubscription against this registration. This errordoes not cause the Capture program toterminate.

User Response: Correct the values in theIBMSNAP_PRUNCNTL table for thissubscription. If this subscription was built usingthe Replication Center, contact IBM SoftwareSupport to report a potential administrationproblem.

ASN0078E CAPTURE capture_schema. Thebefore-image column column_namein the CD tablephys_owner.phys_table has nocorresponding after-image columnin the CD table for thisregistration. The registration isnot valid.

Explanation: The Capture program tried toinitialize a registration and found a before-imagecolumn within the CD table of the registrationthat has no corresponding after-image column.This registration is not valid and typically occursonly if you generated this registration outside ofthe supplied administration tools. This messageis issued during a Capture program warm start


or when the first CAPSTART signal is receivedfor a subscription against this registration. Thiserror does not cause the Capture program toterminate.

User Response: Correct the CD table for thisregistration by ensuring that before-imagecolumns are included in the CD table only whenthe corresponding after-image column is alsoincluded.

ASN0079E CAPTURE capture_schema.SQLCODE sqlcode was returnedduring an update to theIBMSNAP_REGISTER table forthe registrations associated withthe CD tablephys_change_owner.phys_change_table.The rows might have beendeleted.

Explanation: The Capture program tried toupdate the IBMSNAP_REGISTER table toindicate that data has been captured for thenamed CD table, and DB2 returned a SQLCODEindicating that the rows no longer exist. Theregistrations could have been dropped. This errordoes not cause the Capture program toterminate.

User Response: If the registration has beendropped, no further action is required for theregistrations. When dropping registrations, it isrecommended that you deactivate theregistrations first. If the rows in theIBMSNAP_REGISTER table were inadvertentlydeleted, drop the associated CD table andrebuild the registrations. Deactivate anysubscription sets that are associated with theregistrations. If a registrations must be dropped,remove the associated subscription-set membersso that these subscription sets can be activatedand can run successfully. If the registrations arerebuilt, a signal is sent to the Apply programindicating that a full refresh should be performedfor the associated subscription sets.

ASN0080E CAPTURE capture_schema. A tablespace full condition has beenencountered for CD tablephys_change_owner.phys_change_table,which is associated with theregistration for source tablesource_owner.source_table.

Explanation: The Capture program tried toprocess an insert into the named CD table butwas unable to process the insert due to a tablespace full condition. Typically this conditionresults from insufficient space allocation for CDtable spaces, infrequent pruning, or ineffectivepruning. This error causes the Capture programto terminate.

User Response: Take the following steps todetermine the cause of the table space fullcondition:

1. Ensure that sufficient space has beenallocated to the table space for this CD tablein order to accommodate normal processingconditions.

2. Ensure that pruning is performed oftenenough to reduce the storage requirementsfor the Capture control tables.

3. Ensure that the Apply programs are runningoften enough to accommodate normalpruning processing.

4. Verify that no subscription sets have beendeactivated for a long period of time withouttaking the additional steps necessary fornormal pruning.

Refer to the DB2 Replication Guide andReference for additional information.


ASN0082W CAPTURE capture_schema. TheCapture program encountered aregistration with a columncolumn_name in the CD tablephys_change_owner.phys_change_tablewith a column lengthCD_column_length that is shorterthan the length of thecorresponding column in thesource tablesource_owner.source_table, with alength of src_column_length.

Explanation: During the initialization of aregistration, the Capture program found that theregistration definition contains a column in theCD table with a column length that is shorterthan the corresponding column length in thesource table. This is not a recommendedregistration definition and typically occurs only ifyou generated or altered this registration outsideof the supplied administration tools. Theregistration definition is allowed, but a warningmessage is issued to inform you that thecaptured source table data might not fit withinthe defined CD table column. This message isissued during a Capture program warm start orwhen the first CAPSTART signal is received for asubscription against this registration. Theregistration initializes successfully.

User Response: Unless there is a specific reasonwhy you need to define the registration in thismanner (for example, if you are certain that thelength of the changed data will never be largerthan the length of the CD table column), youshould define the registration so that the sourcetable and the CD table data definitions matchexactly.

ASN0083E CAPTURE capture_schema.SQLCODE sqlcode was returnedwhen trying to process an insertinto the CD tablephys_change_owner.phys_change_table.The CD table column column_nameis too short and cannot containthe captured data from thecorresponding column in thesource table,source_owner.source_table. Theregistration has been stopped bythe Capture program.

Explanation: The Capture program tried toprocess an insert into a CD table andencountered a SQLCODE from DB2 thatindicates that the CD table contains a columnthat is shorter than the length of thecorresponding column in the source table. This isnot a recommended registration definition andtypically occurs only if you generated or alteredthis registration outside of the suppliedadministration tools. This error does not causethe Capture program to terminate, but theregistration is placed in the stopped state.

User Response: Re-evaluate this registrationdefinition. Either alter the registration so that thelengths of the source table column and the CDtable column match or add a trigger to the CDtable to truncate the data.

ASN0084E CAPTURE capture_schema. Theregistration with the source tablesource_owner.source_table and theCD tablephys_change_owner.phys_change_tablehas been stopped by the Captureprogram.

Explanation: This error message is issued anytime that a registration is placed in the stoppedstate (with the STATE column set to a value of’S’ in the IBMSNAP_REGISTER table) by theCapture program. The reason for this action isdescribed in one or more of the precedingmessages.

User Response: Examine the preceding errormessages to determine the cause of the failure,


and follow the suggested user response to repairthe failing registration definition. After yourepair the registration definition, you mustmanually set the value of the STATE column to’I’ in the IBMSNAP_REGISTER table to indicatethat the registration can be used again by theApply program.

ASN0100I CAPTURE capture_schema. TheCapture program initialization issuccessful.

Explanation: This message is for yourinformation only.


ASN0101W CAPTURE capture_schema. TheCapture program warm startfailed because existing data is tooold. A cold start will beattempted.

Explanation: The data in the change data tablesis too old. A cold start is performed.

User Response: See the documentationregarding Capture program operations in theDB2 Replication Guide and Reference.

ASN0102W CAPTURE capture_schema. TheCapture program switches to coldstart because the warm startinformation is insufficient.

Explanation: A problem occurred during theretrieval of the restart information. The restarttable data is not valid. A cold start is performed.

v For DB2 Universal Database, an AsynchronousRead Log API error occurred during warmstart while DB2 was reading the log.

v For z/OS, an Instrumentation FacilityInformation (IFI) error occurred during warmstart while DB2 was reading the log.

User Response: See the documentationregarding Capture program operations in theDB2 Replication Guide and Reference.

ASN0104I CAPTURE capture_schema. Inresponse to a CAPSTART signalwith MAP_ID mapid, changecapture has started for the sourcetable source_owner.source_table forchanges found on the logbeginning with log sequencenumber log_sequence_number.

Explanation: The Capture program successfullyprocessed a CAPSTART signal. If this is the firstCAPSTART signal associated with a particularsource table, this message indicates that theCapture program is now capturing updates tothe source table. If this is a CAPSTART signal fora table for which changes are already beingcaptured, this message indicates that the Captureprogram received the signal and performed therequired processing to allow the Apply programto start receiving changes for the subscription setthat is associated with the input MAP_ID value.


ASN0105I CAPTURE capture_schema. n rowshave been pruned from the tabletable_owner.table_name at timestamp.

Explanation: The Capture program prunedrecords from a CD, UOW, TRACE, MONITOR,or SIGNAL table.


ASN0109I CAPTURE capture_schema. TheCapture program has successfullyinitialized and is capturing datachanges for number registrations.Stopped_number registrations are ina stopped state. Inactive_numberregistrations are in an inactivestate.

Explanation: This message is issued when theCapture program completes the reinitialization ofregistration entries. The reinitialization can occurduring a warm start, during the processing of aCAPSTART signal, or in response to a CaptureREINIT command.


User Response: If the Capture program iscapturing the changes for all the registrations, noaction is required. Otherwise, examine thepreceding error messages to determine the causeof the failure, and follow the suggested userresponses to repair the failing registrationdefinition. After you have repaired theregistration definition, issue the asnccmdcommand with the reinit parameter.

ASN0111I CAPTURE capture_schema. Thepruning cycle started at timestamp.

Explanation: This message is issued at thebeginning of each pruning cycle.


ASN0112I CAPTURE capture_schema. Thepruning cycle ended at timestamp.

Explanation: This message is issued at thetermination of each pruning cycle.


ASN0113W CAPTURE capture_schema. Thepruning retention limit will bereached in the next 24 hours.

Explanation: This warning message is issuedwhen the values in the IBMSNAP_UOW tableindicate that retention limit pruning could occurin the next day.

User Response: Check to see why regularpruning is not occurring. Usually this is becauseone or more Apply programs have not been runfor a period of many days, and therefore the CDand UOW tables cannot be effectively pruned.Another potential hazard is the removal ordeactivation of a subscription set, without theremoval or reset of the corresponding synchpointvalue in the table IBMSNAP_PRUNE_SET. TheReplication Analyzer tool can be used to providea detailed analysis of the situation.

ASN0114E CAPTURE capture_schema. Pruninghas failed with SQL code sqlcodewhen pruning the tabletable_owner.table_name.

Explanation: This error message is issued whenpruning fails with an unexpected SQL error code.Pruning terminates and tries again at the nextinterval or command invocation. This error doesnot cause the Capture program to terminate.

User Response: If this SQL code indicates atemporary error, then no action is required.Otherwise, take action as indicated for the SQLerror in the DB2 Messages and Codes manual.

ASN0121E CAPTURE capture_schema. TheCapture program warm startfailed because existing data is tooold. The Capture program willterminate.

Explanation: The time of the warm startinformation exceeded the lag limit.

User Response: No response required; theCapture program will terminate.

ASN0122E CAPTURE capture_schema. Anerror occurred while reading therestart information or DB2 log.The Capture program willterminate.

Explanation: A problem occurred whileretrieving the restart information. The restarttable data was not valid or for z/OS, anInstrumentation Facility Interface (IFI) erroroccurred while reading the log during a restart.When the error is resolved, you can restart usingthe warm start option.

User Response: No response required; theCapture program terminates.


ASN0123I CAPTURE capture_schema. Atprogram termination, the highestlog sequence number of asuccessfully captured log record ismax_commitseq and the lowest logsequence number of a record stillto be committed is min_inflightseq.

Explanation: The Capture program terminatesand records the values of the restart table at thattime for auditing purposes.


ASN0133I CAPTURE capture_schema. TheCapture program has reached theend of the active log and willterminate because theAUTOSTOP feature is specified.

Explanation: The Capture program terminatedwhen it reached the end of the active log asrequested by the user option of AUTOSTOP.


ASN0142E CAPTURE capture_schema. TheCapture program is unable toperform an insert operation on themonitor tableIBMSNAP_CAPMON. The SQLcode is sqlcode. The monitoringinformation for this interval willbe skipped.

Explanation: This error message is issued whenthe monitoring thread has failed with anunexpected SQL code. Monitor functions for thisinterval are skipped, and the program tries againat the next interval. This error does not cause theCapture program to terminate.

User Response: If this SQL code indicates atemporary error, then no action is required.Otherwise, take action as indicated for the SQLerror in the DB2 Messages and Codes manual.

ASN0143W CAPTURE capture_schema. Theprogram detected that the sourcedatabase src_db_name has beenrestored or rolled forward. TheCapture program has switchedfrom a warm start to a cold start.

Explanation: The Capture program started witha startmode of warmsa or warmsi. When theCapture program attempted to warm start, itreceived a return code from the DB2 log readAPI that indicates that the source database hasbeen restored or rolled forward and that logsequence numbers have been reused; the state ofthe source database and the state of the captureddata are no longer consistent. The Captureprogram switched to a cold start.


ASN0144E CAPTURE capture_schema. Theprogram detected that the sourcedatabase src_db_name has beenrestored or rolled forward. A coldstart is recommended to restoreconsistency.

Explanation: The Capture program started witha startmode of warmns or warmsi. When theCapture program attempted to warm start, itreceived a return code from the DB2 log readAPI that indicates that the source database hasbeen restored or rolled forward and that logsequence numbers have been reused; the state ofthe source database and the state of the captureddata are no longer consistent. The Captureprogram terminates and does not automaticallyswitch to a cold start.

User Response: If you are certain that it is safeto perform a Capture program warm start, restartthe Capture program; it will not terminate on asecond attempt. If you are not certain whetherthe captured data will be in a consistent stateafter a Capture program warm start, it isrecommended that you perform a Captureprogram cold start.


ASN0180W CAPTURE capture_schema. Thetable IBMSNAP_SIGNAL is notan EBCDIC table as required bycapture. The signal has beenprocessed.

Explanation: The Capture program detectedthat the IBMSNAP_SIGNAL table is not definedas an EBCDIC table. Additional processing isrequired to translate signals to EBCDIC toprocess them properly. The additional processingrequires a small performance degradation.

User Response: At your earliest convenience,perform the following steps:

1. Stop the Capture program.

2. Drop and re-create the IBMSNAP_SIGNALtable with EBCDIC encoding.

3. Restart the Capture program.

ASN0181W CAPTURE capture_schema. The rowfor the signal with timestampsignal_time no longer exists in theIBMSNAP_SIGNAL table. Thesignal has been processed.

Explanation: The Capture program processedthe request from the signal but could not updatethe SIGNAL_STATE and SIGNAL_LSN.Therefore, the issuer of the signal cannotdetermine that the Capture program received thesignal.

User Response: Determine if another process isexpecting the update for the signal from theCapture program, and if necessary, re-send thesignal.

ASN0182W CAPTURE capture_schema. The rowfor signal with timestampsignal_time no longer exists inIBMSNAP_SIGNAL table and thetable is not EBCDIC. The signalwill be ignored by capture.

Explanation: An initialization failure occurred,because the Capture program received a signalthat was not encoded in EBCDIC. The Captureprogram could not translate the signal toEBCDIC, because the row in the

IBMSNAP_SIGNAL table no longer exists. TheCapture program cannot determine what signalwas sent and so ignores it.

User Response: Determine what signal wassent, and re-send the signal.

At your earliest convenience, perform thefollowing steps:

1. Stop the Capture program.

2. Drop and re-create the IBMSNAP_SIGNALtable with EBCDIC encoding.

3. Restart the Capture program.

ASN0500E pgmname : program_qualifier : Theparameter input input_valuesupplied for parameter nameparameter_name is not valid.

Explanation: The program or a commandprogram has been invoked with a specified inputparameter that is not valid. The messageindicates the name of the program that isreporting the error, along with the parametername and the parameter value.

User Response: Check the documentation onvalid invocation parameters, correct the input,and resubmit the task or command.

ASN0501E pgmname : program_qualifier : Thevalue input_value supplied for theparameter parameter_name is notthe correct data type.

Explanation: The program or a commandprogram was invoked with an input value withan associated data type that is not valid. Themessage indicates the name of the program thatis reporting the error, the incorrect input value,and the name of the parameter for which thisinput value was specified.

User Response: Correct the invocation toinclude the correct data type for the parameterinput and resubmit it.


ASN0502E pgmname : program_qualifier : Thevalue input_value of lengthinvalid_string_length, supplied forparameter parameter_name, isgreater than the maximumallowed string length ofallowed_string_length.

Explanation: The program or a commandprogram has been invoked using an input valuewith a string length that is not valid. Themessage indicates the name of the program thatis reporting the error, what input value isincorrect, and for which parameter this inputvalue was specified.

User Response: Correct the invocation toinclude the correct string length for theparameter input and resubmit it.

ASN0503E pgmname : program_qualifier : Theinteger value input_value, suppliedfor parameter parameter_name, isoutside the supported range forthis parameter.

Explanation: The program or a commandprogram was invoked with an input valuespecified which is outside the supported range.The message indicates the name of the programthat is reporting the error, which input value isincorrect, and for which parameter this inputvalue was specified.

User Response: Correct the invocation toinclude the correct range value for the parameterinput and resubmit it.

ASN0504E pgmname : program_qualifier : Theprogram did not recognize theinvocation parameterincorrect_input.

Explanation: The program or a commandprogram has been invoked with a specifiedparameter or command that is not valid. Themessage indicates which program issued thismessage, and the invocation input that isunrecognized.

User Response: Check the documentation on

valid input parameters, correct the input andresubmit the task or command.

ASN0505E pgmname : program_qualifier : Theprogram was unable to get or setan IPC key.

Explanation: The program or a commandprogram was unable to initialize the inter-processcommunications needed to process commands.This error causes the failing program toterminate.

User Response: Retry the failing program orcommand. Contact IBM Software Support if theproblem persists.

ASN0506E pgmname : program_qualifier : Theprogram could not attach to thereplication communicationsmessage queue.

Explanation: The program or commandencountered an error while trying to process auser command or a response to a command. Theprogram did not terminate and the commanddid not get executed. Possible reasons for thisfailure include:

v No program is running for the givenprogram_qualifier, database, and server. Eitherthe program has not been started or the inputparameters were incorrect.

v This program does not have permission to usethe IPC resources needed to communicate withthe other program.

v The program’s IPC resource has beenremoved. An administrator may have removedthe resource.

User Response: If this message was issued by acommand:

1. Ensure that you specified the parameterscorrectly.

2. If the parameters are correct, ensure that thereceiving program is running.

3. If the problem persists, ensure that bothprograms are running with the same user IDor that they have permission to access eachothers’ IPC resources.


If this message was issued by a process, re-issuethe command that initiated communication withthe process. If the problem persists, stop theprocess using operating-system commands andrestart it. Retry the failing command.

Contact IBM Software Support if the problempersists.

ASN0507E pgmname : program_qualifier : Theprogram could not create thereplication communicationsmessage queue.

Explanation: The program or a commandprogram encountered an internal error whiletrying to process a user command. The programdid not terminate for this failure, but thecommand did not get executed

User Response: Retry the failing command.Contact IBM Software Support if the problempersists.

ASN0508E pgmname : program_qualifier : Theprogram could not send a messageto the replication communicationsmessage queue.

Explanation: The program or a commandprogram encountered an internal error whiletrying to process a user command. The programdid not terminate for this failure, but thecommand did not get executed.


ASN0509E pgmname : program_qualifier : Theprogram could not process areceived message because of anincorrect message version.

Explanation: The program or a commandprogram encountered an internal error whiletrying to process a user command. The programdid not terminate for this failure, but thecommand did not get executed.

User Response: Retry the failing command.

Contact IBM Software Support if the problempersists.

ASN0510E pgmname : program_qualifier : Theprogram encountered a timeoutwhile waiting for reply messages.

Explanation: The command programencountered an internal error while trying toprocess a user command. The program did notterminate for this failure, but the command didnot get executed.


ASN0511E pgmname : program_qualifier : Theprogram was unable to processthe received message because ofan unknown message function.

Explanation: The program encountered aninternal error while trying to process a usercommand. The program did not terminate forthis failure, but the command did not getexecuted.


ASN0512E pgmname : program_qualifier : Theprogram could not read from itsreplication communicationsmessage queue.

Explanation: The program encountered aninternal error while trying to process a usercommand. The program did not terminate forthis failure, but the command did not getexecuted.



ASN0513E pgmname : program_qualifier : Theprogram could not open themessage file named msg_file.

Explanation: This message file used by theprogram has been installed incorrectly, or thelanguage environment variables are not setcorrectly.

User Response: Refer to the documentation forinformation about installation and configuration.

ASN0514E pgmname : program_qualifier : Theprogram could not open the logfile log_file.

Explanation: The program encountered aninternal error while trying to open a file for itsown program message log, and terminatesabnormally because of this failure. This problemmight have occurred because the file wasinadvertently deleted, or because the useridassociated with this process does not have thesufficient authority to open the file.

User Response: Verify that sufficient authorityis provided to the processing userid. If the filewas inadvertently deleted, restart the program tocreate a new log file.

ASN0515E pgmname : program_qualifier : Theprogram could not close the logfile.

Explanation: The program encountered aninternal error while trying to close the file usedfor its own program message log. The file mighthave been deleted inadvertently before theprogram tried to terminate. Final terminationmessages might not be issued.

User Response: If the file was inadvertentlydeleted, restart the program to create a new logfile.

ASN0516E pgmname : program_qualifier : Theprogram could not close themessage catalog.

Explanation: The program encountered aninternal error while trying to close the message

catalog file. The file might have been deletedinadvertently before the program tried toterminate. Final termination messages might notbe issued.

User Response: If the message file has beendeleted, it needs to be reinstalled.

ASN0517E pgmname : program_qualifier : Theprogram has recovered the abilityto read from its replicationcommunications message queue.

Explanation: The program was able toreinitialize its read capability from the messagequeue needed to process commands after aprevious failure.


ASN0518E pgmname : program_qualifier : Theprogram does not accept multiplecommands.

Explanation: The command program wasinvoked with multiple commands specified. Eachcommand invocation must be performed with asingle input command, along with any otherrequired command input. Note: The CHGPARMScommand allows multiple parameters to bechanged with one invocation of the CHGPARMScommand.

User Response: Correct the command input,and resubmit the command.

ASN0519E pgmname : program_qualifier : Theparameter input parameter_valuesupplied for CHGPARMSparameter parameter_name is notvalid.

Explanation: The CHGPARMS command wasinvoked with incorrect parameter input.

User Response: Correct the command inputand resubmit the command.


ASN0520I pgmname : program_qualifier : TheSTATUS command response:thread_type thread is in thestatus_condition state.

Explanation: In response to the statuscommand, one of these messages will be issuedfor each of the threads associated with theprogram that received the command, in eachcase providing the current state of that thread.


ASN0521I pgmname : program_qualifier : TheQRYPARMS command response:parameter_name was set toparameter_value by the followingmethod: method.

Explanation: In response to the QRYPARMScommand, a message will be issued for each ofthe program parameters. For each parameter, themessage provides the name of the parameter, thecurrent setting of the parameter, and the method(by default, by changing theIBMSNAP_CAPPARMS table, by the startupoption, or by the use of the CHGPARMScommand) that was employed by the user to setthe value of the parameter.


ASN0522I pgmname : program_qualifier : Theprogram received thecommand_type command.

Explanation: The program received a commandto be processed.


ASN0523I pgmname : program_qualifier : TheCHGPARMS command response:parameter_name has been set toparameter_value.

Explanation: In response to the CHGPARMScommand, one of these messages will be issued

for each of the program parameters that waschanged. For each parameter, the messageprovides the new value for the parameter.


ASN0524E pgmname : program_qualifier : Theprogram required parameterparameter_name was not specified.

Explanation: The program or a commandprogram was invoked without one of therequired parameters specified. If the parametermissing is the capture_server or control_server, theprogram or command also tried accessing thedatabase name implicitly through the DB2DBDFTenvironment variable setting, where applicable,and this also was not successful.

User Response: Correct the invocation toinclude the appropriate parameter and itscorresponding input value.

ASN0525E pgmname : program_qualifier : Theprogram could not read from itsexternal communications messagequeue.

Explanation: The program or a commandprogram was unable to initialize its readcapability from the external communicationsmessage queue needed to process commands.

User Response: Retry the failing command, andif the problem persists, contact IBM SoftwareSupport.

ASN0526E pgmname : program_qualifier : Theprogram was invoked without anycommand input.

Explanation: The command program wasinvoked without a command to process. Nocommand processing is performed.

User Response: Resubmit the command with allthe required input.


ASN0527E pgmname : program_qualifier : Theprogram was invoked without anyCHGPARMS command input.

Explanation: The commands program wasinvoked with the CHGPARMS command butwithout any command input to process. Nocommand processing is performed.

User Response: Resubmit the command with allthe required input.

ASN0528E pgmname : program_qualifier : Theprogram will terminate becausethe required control tablecontrol_table_name does not exist.

Explanation: The Capture or the Applyprogram tried to execute an SQL operationagainst a required Capture control table. Theprogram received a not found return code fromDB2. The return code occurs either if themigration has not been completed or if arequired Capture control table has beenaccidentally dropped from the environment.

User Response: See the message text for thename of the missing control table. Correctiveaction for this problem depends on which tableis missing. For example, if the table isIBMSNAP_PRUNE_LOCK, then the table cansimply be recreated, and the Capture programcan be restarted. However, if the table isIBMSNAP_RESTART, and if the correct tablecontents cannot be restored, then the table needsto be recreated, and the Capture programrequires a cold start.

ASN0529I pgmname : program_qualifier : Thevalue of parameter_name was set toparameter_value at startup by thefollowing method: method.

Explanation: The program started, and theprogram parameters were initialized based onthe combination of startup options specified andthe existing contents of the tableIBMSNAP_CAPPARMS. These messages werewritten for auditing purposes. The parameterswere set by one of the methods: by default, by

changing the IBMSNAP_CAPPARMS table, or bythe startup option.


ASN0530E pgmname : program_qualifier : Theprogram could not connect todatabase database_name. TheSQLCODE is sql_code.

Explanation: An error occurred when theprogram issued one of the following functions:

v a CONNECT function to DB2 for VSE and VM

v a CONNECT function to DB2 Call AttachmentFacility (CAF)

v an implicit connect to DB2 UDB

User Response: See the DB2 codes in themessages and codes publication of the DB2database manager on your operating system forthe appropriate reason code.

For DB2 for z/OS errors, see the section in theadministration guide that describes the CallAttachment Facility. Contact your DBA forquestions and diagnosis.

If you are running the program under DB2 UDBfor UNIX, ensure that the LIBPATH environmentvariable is set to the same environment in whichthe program starts. Refer to the Setting up forreplication documentation in the DB2 ReplicationGuide and Reference for additional information.

ASN0531E pgmname : program_qualifier : Theprogram could not open the plan.The SQL return code isreturn_code, the reason code isreason_code, the subsystem name isDB2_subsystem, and the plan nameis plan_name.

Explanation: An error occurred when theprogram tried to open the plan, ASNLPLAN.

User Response: See the DB2 Codes section inthe messages and codes publication of the DB2database manager on your operating system tofind the appropriate reason code. See the section


in the administration guide that describes theCall Attachment Facility.

ASN0532E pgmname : program_qualifier : DB2release release_number is notsupported.

Explanation: The program does not support thisrelease of DB2.

User Response: Run the program with theappropriate release of DB2.

ASN0533E pgmname : program_qualifier : DB2was terminated abnormally.

Explanation: DB2 was terminated while theprogram was still active.

For z/OS, VSE/ESA, or VM/ESA, DB2 wasterminated while program was active and theuser did not specify the NOTERM invocationparameter.

User Response: Start DB2 and start theprogram.

ASN0534E pgmname : program_qualifier : DB2database cannot be used, because itis in the state state.

Explanation: DB2 was terminated while theprogram was still active. The database is in oneof the following states: UNDETERMINED,TERMINATED, QUIESCED, ROLLWARD, orACTIVE.

User Response: Start DB2, and then start theprogram.

ASN0535E pgmname : program_qualifier : Theprogram could not disconnectfrom the database db_server. Thereturn code is return_code, and thereason code is reason_code.

Explanation: While terminating the connectionto DB2, the program received an error code fromthe Call Attachment Facility (CAF).

User Response: Restart the program.

ASN0536E pgmname : program_qualifier : Anerror was returned while gettingthe instance name. TheSQLCODE is sqlcode.

Explanation: The SQLEGINS API of DB2Universal Database returned an error.

User Response: See the DB2 Universal DatabaseAPI Reference for information about theSQLEGINS API to determine the error, or contactIBM Software Support.

ASN0537E pgmname : program_qualifier : Theprogram could not connect todatabase database_name, the returncode is return_code, and the reasoncode is reason_code.

Explanation: An error occurred when theprogram issued one of the following functions:

v a CONNECT function to DB2 for VSE and VM

v a CONNECT function to DB2 Call AttachmentFacility (CAF)

v an implicit connect to DB2 UDB

User Response: See the DB2 codes in themessages and codes publication of the DB2database manager on your operating system forthe appropriate reason code.

For DB2 for z/OS errors, see the section in theadministration guide that describes the CallAttachment Facility. Contact your DBA forquestions and diagnosis.

If you are running the program under DB2 UDBfor UNIX, ensure that the LIBPATH environmentvariable is set to the same environment in whichthe program starts. Refer to the Setting up forreplication documentation in the DB2 ReplicationGuide and Reference for additional information.

ASN0538I pgmname : program_qualifier : Theprogram is waiting for DB2 tocome up.

Explanation: When the program is initiallybrought up, if DB2 is not up at that time, theprogram waits until DB2 is up. After DB2 is up,the Capture program makes the connection and


begins to capture changes.

If the NOTERM option is specified in theCapture invocation parameters, and DB2 comesdown smoothly, the Capture program waits for itto come back up.


ASN0539E pgmname : program_qualifier :Database or subsystem nameddatabase_server_name needs to beconfigured withLOGRETAIN=RECOVERY.

Explanation: The Capture program tried toperform a cold or warm start and the sourcedatabase was not defined properly in order forthe log read interface to be used by the Captureprogram. The accepted settings for the databaseconfiguration parameter LOGRETAIN isRECOVERY (also known as ON).

User Response: Use the update databaseconfiguration for command to alter the setting ofthe LOGRETAIN parameter. Please note thatwhen you set this parameter to RECOVERY (orON), you must then use the backup command tobackup the database before using this databasewith any application.

ASN0540E pgmname : program_qualifier : Theprogram was not able to executethe autobind operationsuccessfully on package pkg_namefrom the file path_filename. TheSQLSTATE sqlstate was returned.

Explanation: The program discovered that abind or rebind is required in order to run. Theprogram attempted to autobind, and theautobind was unsuccessful. The program failedto initialize.

User Response: Check for correspondingdatabase messages that might provide additionaldetails about the source of the autobind failure.Possible problems include authorization failures,missing or incorrect control tables, or bind filesthat do not match the program. Correct thesituation, and restart the program.

ASN0541E pgmname : program_qualifier : Anincorrect value column_value wassupplied for column column_nameof the program parameter tableparms_table.

Explanation: This message is issued duringinitialization of the Capture program if thevalidation of the IBMSNAP_CAPPARMS tablefound that one of the parameter value settings isnot valid. The Capture program terminates withthis error.

User Response: Check the documentation forpermitted parameter values allowed in this table.Correct the values and restart the Captureprogram.

ASN0542E pgmname : program_qualifier : Themaximum number of locktime-out or deadlock retries hasbeen reached, SQLSTATE sqlstatewas returned.

Explanation: The Capture program hasinternally retried a time-out or deadlockcondition multiple times. If the program task thatreceives the persistent lock condition is critical,such as the Capture worker thread, the wholeCapture program terminates. If the program taskis not critical, such as pruning or monitoring,then the task will be retried at a later time, andthe Capture program remains active.

User Response: Check for correspondingdatabase messages that might provide additionaldetail about the source of the locking contention.Correct the situation if the error is a user error,such as a user held lock. If the condition persists,contact IBM Software Support for assistance.

ASN0543E pgmname : program_qualifier : Theprogram cannot obtainbytes_number bytes of storage for aobject.

Explanation: The program is unable to obtainmemory for a necessary in-memory storagestructure. The program terminates.

User Response: Consider allowing a larger


memory allowance to the program, then restartthe program.

ASN0544E pgmname : program_qualifier : Theprogram is already active.

Explanation: You tried to start more than oneCapture program per DB2 subsystem ordatabase.

v For VSE/ESA, Capture for VSE generates aunique lock name for each database. This lockname is already in use, indicating that Capturefor VSE is already active for the database.

v For VSE/ESA, Capture for VM has determinedthat the resource ID used as a lock is alreadyin use. The resource ID is specified on theENQ_NAME parameter of the CAPTUREASNPARMS file.

User Response:

v For DB2 for z/OS subsystems, either run onlyone instance of the Capture program for allsubsystems that are members of a data-sharinggroup, or run only one instance of the Captureprogram on any stand-alone system. Displaythe ENQ resource to determine the uniqueresource name violation.

v For other DB2 database operating systems, runonly one Capture program per database.

v For Capture for VM, you can change theENQ_NAME parameter in the CAPTUREASNPARMS to ensure unique values for eachCapture program if you want to run Capturefor VM for more than one DB2 database on asystem.

ASN0545E pgmname : program_qualifier : Theprogram started with the startupparameter PWDFILE, but thepassword file password_file was notfound.

Explanation: The program cannot find thepassword file. The user specifies the passwordfilename through the PWDFILE parameter. If theuser specifies a path startup parameter, thepassword file should reside in the specifieddirectory. If the user did not specify a pathstartup parameter, the password file should

reside in the current directory in which theprogram is running.

User Response: Ensure that the password filename is correctly specified and is located in theproper directory.

ASN0546W pgmname : program_qualifier : Theprogram call issued to theAutomatic Restart Manager failed.The invoked IXCARM macro isarm_call, the return code isreturn_code, and the reason code isreason_code.

Explanation: The Capture or Apply programcannot connect to, disconnect from, or receive aready status indication from the AutomaticRestart Manager (ARM). The message displaysthe unsuccessful call and the return or reasoncode that returned to the program from theARM. The program does not terminate butcannot continue ARM processing.

User Response: Check the Automatic RestartManager documentation for more informationabout the cause of this failure.

ASN0547I pgmname : program_qualifier : Thenumber of substitution variablespassed, nbr_vars, does not matchthe number of tokens, nbr_tokens,in the text of message numbermsg_nbr.

Explanation: The program code and theprogram message file do not match; the releaselevel of the program and the message file catalogmight not match.

User Response: Verify that the programmessage file is correctly installed with theappropriate file permission settings.

ASN0548I pgmname : program_qualifier : Theprogram received an operator stopcommand.

Explanation: This informational messageindicates that a stop command was issued to theprogram.



ASN0552E pgmname : program_qualifier : Theprogram encountered an SQLerror. The server name isserver_name.The SQL request issql_request. The table name istable_name. The SQLCODE issqlcode. The SQLSTATE is sqlstate.The SQLERRMC is sql_tokens. TheSQLERRP is error_module.

Explanation: A nonzero SQLCODE returnedwhen the Capture, Apply, or Monitor programissued an EXEC SQL statement or CLI call. ThisSQLCODE might be caused by a DB2 problemthat needs to be investigated, such as, an out ofspace condition, or DB2 is unavailable for use byapplications. This message is sometimes followedby a second message that provides informationabout what replication was doing when thisSQLCODE was encountered.

User Response: See the messages and codesdocumentation of the DB2 database manager onyour operating system for an explanation of thisSQLCODE and for information about correctiveactions that might need to be taken in DB2. Ifreplication issued another message immediatelyfollowing this one, see the explanation and userresponse for that message.

ASN0553E pgmname : program_qualifier :Internal error error_numberoccurred for message numbermsg_number containing num_tokenssubstitution fields: sub_tokens.

Explanation: The error number is a decimalinternal error number which is defined as:

1 Instance is not valid

2 Access denied

3 No files

4 No message

5 Locale is not valid

6 System error

7 Not enough memory

The msg_number is the message that the programwas trying to issue. The num_tokens is thenumber of substitution tokens given for themessage (not including the pgmname andprogram_qualifier tokens). The sub_tokens is thesubstitution tokens for the message in errorseparated by commas.

User Response: Take any corrective actionpossible based on the error code given. Forexample, if the message file was not found orcould not be accessed, you should also seemessage ASN0513 which gives you the file name.Verify that the message file exists with thecorrect permissions. If you get error code 4, youmight have an old message file.

ASN0554E pgmname : program_qualifier : Theprogram encountered a DB2 logfull condition on serverserver_name.

Explanation: The program tried to process aninsert or update which was denied by DB2because the DB2 transaction log is full. Theprogram will stop processing.

User Response: Check the amount of spaceremaining on the filesystem containing yourdatabase files. Consider increasing the maximumlog size in the database configuration file.

ASN0555W pgmname : program_qualifier : Theprogram cannot register withAutomatic Resource Manager(ARM) because it is not APFauthorized.

Explanation: The Capture, Apply or Monitorprogram cannot register to use AutomaticResource Manager services because the programlibraries are not APF authorized.

User Response: If you desire Capture, Apply, orMonitor program to register with AutomaticResource manager, authorize the programlibraries for APF and restart the program.


ASN0556E pgmname : program_qualifier : Aregistration that is not valid hasbeen found. The CD tablephys_chg_owner.phys_chg_tbl doesnot have any columns that matchthe base tablesource_owner.source_table.

Explanation: The Capture program tried toinitialize a registration and found that the CDtable does not have any columns that match thesource table. Nothing can be captured for thisregistration and so it is considered not valid. Theregistration remains inactive if theSTOP_ON_ERROR column in the register(IBMSNAP_REGISTER) table for this registrationis set to N, otherwise, the Capture programstops.

User Response: Make sure that there is at leastone column in the CD table that matches thesource table for the registration.

ASN0557E pgmname : program_qualifier : Thevalue column_value for columncolumn_name of owner.table withsource tablesource_owner.source_table, is notvalid.

Explanation: The Capture program tried toinitialize a registration and found a value that isnot valid for a column in the register(IBMSNAP_REGISTER) table.

User Response: Correct the value for thecolumn in error. Refer to the description of theregister table for valid values for the column inerror.

ASN0558E pgmname : program_qualifier : Theparameter table parameter_table canhave only one row correspondingto program qualifierprogram_qualifier.

Explanation: The program parameters table wasnot defined correctly or was updated with rowsthat are not valid.

User Response: Ensure that there is only one

row in the parameter table corresponding to theprogram_qualifier. Ensure that the parameterstable has a unique index on the programqualifier. Refer to the description of theparameter tables for additional information.

ASN0777I pgmname : program_qualifier :Additional informationmessage_text, reason code(s): rc1,rc2, rc3.

Explanation: The Additional information shownin this message refers to an informational textmessage. The reason codes provide supplementalreturn code information related to this messagetext. If an informational code field is notapplicable, it contains ″*″ (an asterisk).


ASN0888E pgmname : program_qualifier : EEEerror condition message_text, errorcode(s): rc1, rc2, rc3.

Explanation: The EEE error condition shown inthis message is the description of an EEE-specificerror that occurred in the specified program withthe specified qualifier (if displayed). The errorcodes provide supplemental information relatedto this message text. If an error code field is notapplicable, it contains ″*″ (an asterisk).

User Response: Use the information from theEEE error condition and from the specified errorcodes to determine the cause of the error.Contact IBM Software Support if you cannotresolve the error.

ASN0999E pgmname : program_qualifier : Errorcondition message_text, errorcode(s): rc1, rc2, rc3.

Explanation: The Error condition shown in thismessage is the description of an error thatoccurred in the specified program with thespecified qualifier (if displayed). The error codesprovide supplemental information related to thismessage text. If an error code field is notapplicable, it contains ″*″ (an asterisk).


User Response: Use the information from theError condition and from the specified error codesto determine the cause of the error. Contact IBMSoftware Support if you cannot resolve the error.

ASN1001E APPLY apply_qualifier. The Applyprogram encountered an SQLerror. The ERRCODE is error_code.The SQLSTATE is sqlstate. TheSQLCODE is sqlcode. TheSQLERRM is sqlerrm. TheSQLERRP is sqlerrp. The servername is server_name. The tablename is table_name.

Explanation: An error occurred during theexecution of an SQL statement.

User Response: Refer to your database messagereference for an explanation of the SQL errorcode.

ASN1002E APPLY apply_qualifier. Thetable_name could not be locked.ERRCODE is error_code,SQLSTATE is sqlstate, SQLCODEis sqlcode, SQLERRM is sqlerrm,SQLERRP is sqlerrp, server nameis server_name, table name istable_name

Explanation: The Apply program could not lockthe table.

User Response: Refer to your database messagereference.

ASN1003E APPLY apply_qualifier. The Applyprogram could not connect to theserver server. The error code iserror_code. The SQLSTATE issqlstate. The SQLCODE is sqlcode.The SQLERRM is sqlerrm. TheSQLERRP is sqlerrp.

Explanation: The Apply program attempted toconnect to the database and received a failingreturn code. There are many possible reasonswhy the Apply program could not connect to thedatabase. For example, the Apply programwould receive a failing return code if the

database was down or too many users wereaccessing it.

User Response: Look up the SQLCODE in theDB2 messages and codes manual to determinewhy the connection failed. Refer to the Settingup for replication documentation in the DB2Replication Guide and Reference for informationabout storing user IDs and passwords.

Refer to your database message reference for anexplanation of the SQL error code.

ASN1006E APPLY apply_qualifier. The productregistration module hasunexpected content.

Explanation: The content of the registrationmodule (ASNAPR61) for DB2 Replication is notas expected for this version of the DB2. Nofurther use of the product is possible until youprovide the correct registration module.

User Response: Verify that DB2 was installedwithout errors. If errors occurred, correct themand try again.

If DB2 installed without error and you arecorrectly accessing the feature-registrationmodule (ASNAPR61), contact IBM SoftwareSupport for assistance.

ASN1008E APPLY apply_qualifier. Thesubscription set with Applyqualifier qualifier and set nameset_name is not defined correctly.ERRCODE is error_code.

Explanation: The subscription set is not definedcorrectly.

User Response: Make sure that theWHOS_ON_FIRST column in the subscription settable is specified correctly.

ASN1009E APPLY apply_qualifier. There is nosubscription set defined for Applyqualifier qualifier.

Explanation: There is no subscription setdefined for Apply qualifier qualifier.

User Response: Define at least one subscription


set for Apply qualifier qualifier.

ASN1010E APPLY apply_qualifier. The Applyprogram could not insert row rowinto the audit trail table due tothe following error: error_code.

Explanation: This is an SQL return codeindicating that the audit trail table was not setup with the same structure as theIBMSNAP_APPLYTRAIL table.

User Response: Refer to the Table structuresdocumentation in the DB2 Replication Guide andReference and to your database SQL manual.

ASN1011E APPLY apply_qualifier. The copyrequest has incompatible sourceand target attributes. The SQLcode is error_code.

Explanation: This is an SQL code indicatingthat the attributes of the target table must becompatible with the attributes of the source table.

User Response: Refer to theSOURCE_STRUCTURE column in the registertable for the compatibility of the source andtarget attributes.

ASN1012E APPLY apply_qualifier. The sourcetable structure is not valid. Theerror code is error_code.

Explanation: This is an SQL return codeindicating that the source table structure in theregister table was not set up according to theSOURCE_STRUCTURE column in the registertable.

User Response: Refer to the Table structuresdocumentation in the DB2 Replication Guide andReference for valid SOURCE_STRUCTUREcolumn values used in the IBMSNAP_REGISTERtable.

ASN1013E APPLY apply_qualifier. The targettable structure is not valid. Theerror code is error_code.

Explanation: The target table structure in thesubscription-targets-member table was not valid.

User Response: Refer to the Table structuresdocumentation in the DB2 Replication Guide andReference for valid target table structures.

ASN1014E APPLY apply_qualifier. The Applyprogram could not find a sourcefor the copy request because itcould not find the change datatable. The error code is error_code.

Explanation: The change data table was notdefined in the register table because either theApply program did not find the change datatable name in the register table or the sourcetable was not registered correctly.

User Response: Refer to the Table structuresdocumentation in the DB2 Replication Guide andReference, and verify that the change data tableis correctly defined in the register table.

ASN1015I APPLY apply_qualifier. The Applyprogram is waiting for theCapture program at serverserver_name to advance the globalSYNCHTIME. Verify that theCapture program is running.


User Response: Verify that the Captureprogram is running.

ASN1016I APPLY apply_qualifier. Refreshcopying has been disabled. Theerror code is error_code.

Explanation: While attempting to perform a fullrefresh, the Apply program encountered aDISABLE_REFRESH column in the register tablewhich was set on.

User Response: Either turn off theDISABLE_REFRESH column or bypass the Apply


program and perform a manual refresh.

ASN1017E APPLY apply_qualifier. The Applyprogram could not find any targetcolumn names. The error code iserror_code.

Explanation: The Apply program could not findany columns in the subscription columns table.

User Response: Redefine the subscription setand subscription-set members. Refer to theSetting up for replication documentation in theDB2 Replication Guide and Reference for moreinformation.

ASN1018I APPLY apply_qualifier. The Applyprogram is processingsubscription setset_name(whos_on_first).(set_numberof total_sets).



ASN1019E APPLY apply_qualifier. The targettable does not have any keycolumns. The error code iserror_code.

Explanation: The Apply program cannot findkey column names in one of the columnsrequiring a unique index or primary key.

User Response: Redefine the subscription setand the subscription-set members. Refer to theSetting up for replication documentation in theDB2 Replication Guide and Reference for moreinformation.

ASN1020E APPLY apply_qualifier. The Applyprogram could not reserve astorage block. The error code iserror_code.

Explanation: The Apply program could notobtain the required (memory) storage.


ASN1021E APPLY apply_qualifier. The Applyprogram cannot read the work filefilename. The error code iserror_code.

Explanation: The Apply program cannot readthe work file due to a system error.

User Response: Determine if the problem iscaused by lack of space, and contact your systemadministrator to obtain what is needed.

ASN1022E APPLY apply_qualifier. The Applyprogram cannot write to the workfile filename. The error code iserror_code.

Explanation: Either the user does not have theproper access authority for one or all of the files,or there is insufficient space remaining afterwriting to the target file.

User Response: Determine whether the problemis caused by a lack of access authority or a lackof space, and contact your system administratorto obtain what is needed.

ASN1023E APPLY apply_qualifier. The Applyprogram cannot open the workfile filename. The error code iserror_code.

Explanation: The Apply program cannot openthe work file.


ASN1024E APPLY apply_qualifier. The Applyprogram cannot close the workfile filename. The error code iserror_code.

Explanation: The Apply program cannot closethe work file.



ASN1025I APPLY apply_qualifier. The Applyprogram completed processing forsubscription setset_name(whos_on_first). The returncode is return_code.



ASN1026I APPLY apply_qualifier. The Applyprogram encountered an errorwhile trying to bind. SQLSTATEis sqlstate, SQLCODE is sqlcode.

Explanation: An error occurred during theexecution of bind.


ASN1027E APPLY apply_qualifier. There aretoo many large object (LOB)columns specified. The error codeis error_code.

Explanation: Too many large object (BLOB,CLOB, or DBCLOB) columns are specified for asubscription set member. The maximum numberof columns allowed is 10.

User Response: Remove the excess large objectcolumns from the subscription set member.

ASN1028I APPLY apply_qualifier. Thebefore-image column for a keycolumn is not found. The errorcode is error_code.

Explanation: The subscription set up for amember with TARGET_KEY_CHG=Y’ isincorrect.

User Response: For each key column(IS_KEY=Y), there must be a before-imagecolumn included in the IBMSNAP_SUBS_COLStable. It can be a col_type=B (specified by theuser), or col_type=P (provided by Replication). Ifthe subscription is set up manually, then youmust correct the problem yourself. If the

subscription is set up by using the ReplicationCenter or the Replication Commands, contactIBM Software Support.

ASN1029E APPLY apply_qualifier. The SQLstatement of the subscription setnamed set_name with awhos_on_first value ofwhos_on_first did not executesuccessfully. The statement failedwith SQLCODE sqlcode andSQLSTATE sqlstate. The applyprogram internal error code iserror_code.

Explanation: The user-specified SQL statementdid not execute successfully.

User Response: Refer to the correspondinginformation in the IBMSNAP_APPLYTRAIL tableand to the SQL manual of your database fordetailed information.

ASN1031E APPLY apply_qualifier. The SQLstatement is empty. The error codeis error_code.

Explanation: The SQL statement is an emptystring.

User Response: Specify the SQL statement to beexecuted.

ASN1032E APPLY apply_qualifier. The Applyprogram log file could not beopened. The error code iserror_code, and the return code isreturn_code.

Explanation: The Apply program could notopen the log file.

User Response: For more information on thereturn code, refer to the manual that describesproblem determination for your particularoperating system.


ASN1033E APPLY apply_qualifier. The Applyprogram could not write to theApply log file. The error code iserror_code, and the return code isreturn_code.

Explanation: The Apply program could notwrite to the log file.

User Response: For more information on thereturn code, refer to the manual that describesproblem determination for your particularoperating system.

ASN1034I APPLY apply_qualifier. The Applyprogram initialization issuccessful.

Explanation: This message is issued atsuccessful initialization of the Apply process.


ASN1035E APPLY apply_qualifier. The Applyprogram could not access thesubscription columns table. Theerror code is error_code. TheSQLSTATE is sqlstate. TheSQLCODE is sqlcode. TheSQLERRM is sqlerrm. TheSQLERRP is sqlerrp. The servername is server_name. The tablename is table_name.


User Response: Refer to your database messagereference for SQL.

ASN1036E APPLY apply_qualifier. The columntype col_type for expressionexpression is not valid. The errorcode is error_code.

Explanation: The value for the COL_TYPEcolumn in the subscription columns table is notvalid.

User Response: Change the value to A, B, C, D,F, L, or R.

ASN1038E APPLY apply_qualifier. No columnnames or expressions werespecified in the subscriptioncolumns table.

Explanation: Column names or expressions fora copy statement must be specified.

User Response: Refer to the Setting up forreplication documentation in the DB2 ReplicationGuide and Reference for more information aboutrequirements for subscription definitions.

ASN1039E APPLY apply_qualifier. The Applyprogram plan, plan_name, couldnot be opened. The error code iserror_code. The return code isreturn_code. The reason code isreason_code.

Explanation: The Apply program plan couldnot be opened.

User Response: Refer to the Apply for z/OSProgram Directory.

ASN1040E APPLY apply_qualifier. The Applyprogram encountered an z/OSerror. The error code is error_code,and the return code is return_code.

Explanation: Execution of a z/OS systemoperation failed.

User Response: Refer to your z/OS systemlibrary information.

ASN1041I APPLY apply_qualifier. The Applyprogram was started usingsubsystem name: subsystem.

Explanation: This message informs you that theApply program started using the specifiedsubsystem name.



ASN1042W APPLY apply_qualifier. There aretoo many invocation parameters.

Explanation: The number of parameters youspecified when you invoked the Apply programexceeds the maximum allowed.

User Response: Refer to the Capture and Applychapter for your operating system forinformation on the appropriate number ofinvocation parameters.

ASN1043E APPLY apply_qualifier. There isalready one Apply instancerunning with this Apply programqualifier qualifier. The error codeis error_code, and the reason codeis reason_code.

Explanation: Verification attempt failed.

User Response: Make sure that only oneinstance of the Apply program with the specifiedApply qualifier is running under this user ID onthis subsystem or database.

ASN1044I APPLY apply_qualifier. The Applyprogram will become inactive fornumber minutes and numberseconds.

Explanation: The Apply program is inactive.


ASN1045I APPLY apply_qualifier. The Applyprogram was started usingdatabase database.

Explanation: This message informs you fromwhich database the Apply program is running.


ASN1047I APPLY apply_qualifier. There aretoo many columns specified. Theerror code is error_code.

Explanation: There are too many columnsspecified for a member in the subscription.

User Response: The user must reduce thenumber of columns specified for the member inthe subscription. The maximum number ofcolumns supported is determined by the totallength of all the column names. More columnscan be specified if the length of the columnnames is shorter.

ASN1048E APPLY apply_qualifier. Theexecution of an Apply cyclefailed. See the Apply trail tablefor full details: text

Explanation: An Apply cycle failed. In themessage, text identifies the target_server,target_owner, target_table, stmt_number, andcntl_server.

User Response: Check the APPERRM fields inthe audit trail table to determine why the Applycycle failed.

ASN1049E APPLY apply_qualifier. The Applyprogram encountered a systemerror. The error code is error_code.The return code is return_code.

Explanation: Execution of a system operationfailed.

User Response: Refer to the system libraryinformation for your operating system.

ASN1050E APPLY apply_qualifier. The Applyprogram encountered an operationthat is not valid while updatingthe target table. The error code iserror_code. The operation to beapplied is operation.

Explanation: The operation field of a rowfetched from the source table is not valid.



ASN1051E APPLY apply_qualifier. The Applyprogram detected a gap betweenthe source source table and thetarget table. The error code iserror_code.

Explanation: The Apply program has detectedthat the Capture program lost change data beforethe Apply program could copy it. For example,the Capture program might have been coldstarted or retention limit pruning might haveoccurred.

User Response: Check the control tables todetermine why the gap is present. Take properaction to preserve data integrity before you resetthe control table information to execute thedefinition again.

ASN1052E APPLY apply_qualifier. The Applyprogram could not find theASNLOAD program.

Explanation: The Apply program cannot findthe ASNLOAD program in the current directory.

User Response: Make sure that ASNLOAD is inthe directory from which you are invoking theApply program.

ASN1053E APPLY apply_qualifier. Theexecution of the ASNLOAD exitroutine failed. The return code isreturn_code.

Explanation: The ASNLOAD exit routinedetected an error and passed the errorinformation back to the Apply program. Thefollowing values are valid return codes:

98

unexpected error has occurred (The ASNLOADexit routine has failed with an unexpected error.No processing will be performed.)

99

DB2 pwdfile keyword supplied - password filenot found (The pwdfile parameter was passed,but no password file was found. This is an error,and no connections or other processing will beperformed.)

100

DB2 connect with a user/using phrase failed -pwdfile found (A connect with a user/usingphase was made using values supplied in theencrypted Apply password file. The passwordfile and a userid/password combination for theDB2 server were found, but the connectionfailed.)

101

DB2 connect without a user/using phrase failed -no pwdfile found (A connection without auser/using phrase was made because nopassword file was provided. The connectionfailed.)

102

DB2 connect without a user/using phrase failed -pwdfile found, no entry (A connection without auser/using phrase was made, because no serverentry was found in the pwdfile for the DB2server. The connection failed.)

103

DB2 connect with a user/using phrase failed -uid/pwd from asnload.ini used (A connectionwith a user/using phrase was made using valuessupplied in the asnload.ini file. This file and auserid/password combination for the DB2 serverwere found, but the connection failed.)

104

DB2 connect without a user/using phrase failed -no asnload.ini found (A connection without auser/using phrase was made, because noasnload.ini file was found. The connectionfailed.)

105

DB2 connect without a user/using phrase failed -no uid/pwd found for server (A connectionwithout a user/using phrase was made. Theasnload.ini file was found, but no uid/pwdcombination was provided. The connectionfailed.)

106

user specified LOADX_TYPE = 2, no user codeprovided (The value of LOADX_TYPE in the


table ASN.IBMSNAP_SUBS_MEMBR was set bythe user to the value of 2, indicating that the userwas supplying custom code in the ASNLOADexit routine. However this code was not found,and the ASNLOAD exit routine failed when theApply program passed a LOADX_TYPE value of2.)

107

DB2 import utility failed (The import utilityfailed to execute. The SQL code returned by theutility is passed as the reason code.)

108

DB2 export utility failed (The export utility failedto execute. The SQL code returned by the utilityis passed as the reason code.)

109

DB2 load utility failed (The load utility failed toexecute. The SQL code returned by the utility ispassed as the reason code.)

110

DB2 load utility failed - invoked as crossload(The load utility failed to execute. The loadutility was invoked with the load from cursoroption. The SQL code returned by the utility ispassed as the reason code.)

111

user has set LOADX_TYPE to an not valid value(The ASNLOAD exit routine was invoked with aLOADX_TYPE value that was set by the user.The LOADX_TYPE value is not valid for thisenvironment, and the ASNLOAD exit routinefailed.)

112

LOADX_TYPE 3 requires a nickname for select(The ASNLOAD exit routine failed. TheASNLOAD exit routine was invoked with aLOADX_TYPE value that was set by the user.The LOADX_TYPE value is not valid for thisenvironment unless a nickname is created for theremote DB2 source table and stored in theASN.IBMSNAP_SUBS_MEMBR table.)

113

LOADX_TYPE 4 is incompatible with target table

(The ASNLOAD exit routine failed. TheASNLOAD exit routine was invoked with aLOADX_TYPE set by the user. TheLOADX_TYPE value is not valid for thisenvironment, because the target table cannot beserviced by the DB2 Linux/UNIX/Windows loadutility.)

114

LOADX_TYPE 5 is incompatible with target table(The ASNLOAD exit routine failed . TheASNLOAD exit routine was invoked with aLOADX_TYPE set by the user. TheLOADX_TYPE value is not valid for thisenvironment, because the target table cannot beserviced by the DB2 import utility.)

115

the ASNDLCOPY exit routine has failed (TheASNLOAD exit routine called the ASNDLCOPYexit routine, because there were DATALINKcolumns for the subscription–set member. TheASNDLCOPY exit routine failed; therefore, theprocess that loads this subscription–set memberalso failed.)

User Response: Check the return code and thecorresponding explanation (above). Check foradditional information in the ASNLOADmessage file and in the message files generatedby the DB2 utility, if applicable.

ASN1054E APPLY apply_qualifier. The Applyprogram could not find a row inthe IBMSNAP_REGISTER orIBMSNAP_PRUNCNTL table thatcorresponds to the subscriptionset member with a set nameset_name, for source ownersrc_ownr, source table src_tbl, andsource view qualifiersrc_view_qual.

Explanation: The source table registration isincorrect or incomplete.

User Response: Drop and redefine theregistration.


ASN1055E APPLY apply_qualifier. The Applyprogram could not find the prunecontrol information for sourceowner src_ownr, source tablesrc_tbl, source view qualifiersrc_view_qual, target ownertgt_ownr, and target table tgt_tbl.

Explanation: The source table registration isincorrect.

User Response: Drop the subscription and redoit.

ASN1056E APPLY apply_qualifier. The Applyprogram could not connect to theserver due to lack of userID/password. The error code iserror_code.

Explanation: The Apply program could not findthe password and user ID to connect to theserver.

User Response: Make sure that the Applyprogram password file exists. The Applyprogram password file resides in the samedirectory from which you start the Applyprogram. If you are using DB2 UniversalDatabase Satellite Edition, make sure that thepassword and user ID are defined to the clientsystems.

ASN1057E APPLY apply_qualifier. The Applyprogram could not read thepassword in the Apply passwordfile. The error code is error_code.

Explanation: The Apply program found nopassword.

User Response: If you want to use theAUTHENTICATION=SERVER scheme, you mustprovide a password, as described in the Applyprogram section in the Capture and Applychapter for your operating system.

ASN1058E APPLY apply_qualifier. The Applyprogram could not close thepassword file. The error code iserror_code.

Explanation: The Apply program could notclose the password file.


ASN1059E APPLY apply_qualifier. The Applyprogram detects syntax that is notvalid for line line in the passwordfile. The error code is error_code.

Explanation: The Apply program could notrecognize a line in the password file.

User Response: Correct the syntax error in thepassword file. See the Apply program section inthe Capture and Apply chapter for youroperating system.

ASN1060E APPLY apply_qualifier. Thedynamic allocation for thetemporary work file failed. Theerror code is error_code.

Explanation: A system error was encounteredduring dynamic allocation.


ASN1061E APPLY apply_qualifier. Thespecified keyword parameter isnot valid. The error code iserror_code.

Explanation: An invocation parameter that isnot valid has been specified and has beenignored by the Apply program.

User Response: Correct the invocationparameter. See the Apply program section in theCapture and Apply chapter for your operatingsystem.


ASN1062W APPLY apply_qualifier. The Applyprogram must use SELECT andINSERT statements to perform afull refresh of thissubscription-set member. Thefollowing information pertains tothis subscription-set member: theset name is set_name, the sourceowner is source_owner, the sourcetable is source_table, the sourceview qualifier is source_view_qual,the target owner is target_owner,and the target table is target_table.

Explanation: The ASNLOAD exit routine cannotdetect a user-specified LOADX_TYPE value, andno utilities are available to process thissubscription-set member. Therefore, theASNLOAD exit routine passes full refresh controlback to the Apply program. The ASNLOAD exitroutine does not currently support and is notable to process some target table types (such asthe Sybase and MS SQL Server target tables).

User Response: This message is for yourinformation only, and no action is required.However, you can set the value of theLOADX_TYPE to 1 for these subscription-setmembers in order to avoid unnecessaryprocessing by the ASNLOAD exit routine.

ASN1063E APPLY apply_qualifier. Asubscription set cannot have morethan 200 members. The error codeis error_code.

Explanation: The number of subscriptions hasexceeded the maximum allowed number of 200.

User Response: Remove excess members fromthe subscription set.

ASN1064W APPLY apply_qualifier. The Applyprogram cannot perform a fullrefresh for the subscription setnamed set_name, because theCapture program for this sourcehas not yet been cold started.

Explanation: The Apply program cannotattempt a full refresh for the subscription set,

because the Capture program for this source hasnever been cold started and is not ready toprocess the CAPSTART signals are be inserted bythe Apply program.

User Response: Start the Capture program forthis source.

ASN1065E APPLY apply_qualifier. The Applyprogram cannot perform a fullrefresh for the subscription setnamed set_name, because theregistered source tablesource_owner.source_table is in astopped state.

Explanation: The Apply program cannotperform a full refresh for this subscription set,because one of the source registrations is in thestopped state (the value of the STATE column isset to ’S’ in the IBMSNAP_REGISTER table). TheCapture program places a registration in thestopped state if there is a problem with theregistration that requires user intervention. Theintegrity of the captured data for the registrationmight be compromised, and the Apply programmust perform a full refresh. (This could occur ifthe registered source table has been altered withdata capture none.)

User Response: Fix the stopped registrationsusing the information from the generatedCapture error messages. Manually set the valueof the STATE column to ’I’ (Inactive) in theIBMSNAP_REGISTER table. The Apply programcan then perform a full refresh.

ASN1066E APPLY apply_qualifier. An internalApply program error occurred.The error code is error_code.

Explanation: An internal Apply program erroroccurred.



ASN1067E APPLY apply_qualifier. The Applyprogram has detected updateconflicts and compensatedrejected transactions. See theunit-of-work table for details. Theerror code is error_code.

Explanation: More than one applicationupdated the same row in a table from differentlocations. Some transactions have been rejectedand compensated.

User Response: Refer to the Tables structuresdocumentation in the DB2 Replication Guide andReference for more information.

ASN1068E APPLY apply_qualifier. The Applyprogram has deactivated thesubscription due to an RIviolation. The error code iserror_code.

Explanation: A referential integrity violationwas detected when copying data from the sourcetable to a replica. The Apply program hasterminated and the subscription has beendeactivated.

User Response: Correct the referential integrityerror and reactivate the subscription.

ASN1070E APPLY apply_qualifier. The Applyprogram could not lock the targettable. The ERRCODE is error_code.The SQLSTATE is sqlstate. TheSQLCODE is sqlcode. TheSQLERRM is sqlerrm. TheSQLERRP is sqlerrp. The servername is server_name. The tablename is table_name.

Explanation: The Apply program could not lockthe target tables before it was to check updateconflicts.

User Response: Verify that all the target tablesare available before restarting Apply.

ASN1071E APPLY apply_qualifier. The Applyprogram could not reposition thework file. The error code iserror_code.

Explanation: The Apply program has detectedan error while reading the temporary work file.


ASN1072E APPLY apply_qualifier. The Applyprogram could not find theASNDONE program.

Explanation: The Apply program could not findthe user exit program, ASNDONE.

User Response: Verify that the ASNDONEprogram is located in the correct directory.

ASN1073E APPLY apply_qualifier. Theexecution of the ASNDONEprogram failed. The return code isreturn_code.

Explanation: An error occurred while callingthe user exit program, ASNDONE.


ASN1074E APPLY apply_qualifier. The Applyprogram could not find theASNDLCOPY program.

Explanation: The Apply program did not findthe ASNDLCOPY program in the current searchpath.

User Response: Add the ASNDLCOPY programto the search path and run the Apply programagain.

ASN1075E APPLY apply_qualifier. TheASNDLCOPY program failed. Thereturn code is return_code.Additional information can befound in the ASNDLappl_qualset_namecapture_servertarget_server.LOG file.

Explanation: The ASNDLCOPY programdetected an error and passed the error


information back to the Apply program. Thefollowing values are valid return codes:

98

Unexpected error occurred.

99

The arguments passed to the ASNDLCOPYprogram are not valid.

100

Unable to allocate memory.

101

Unable to open the ASNDLSRVMAPconfiguration file.

102

The number of entries in the ASNDLSRVMAPconfiguration file exceeds the maximum limit.

103

An entry that is not valid has been found in theASNDLSRVMAP configuration file.

104

No user login information was found in theASNDLUSER configuration file for a given fileserver.

105

An entry that is not valid has been found in theASNDLPARM configuration file.

106

Unable to open the ASNDLUSER configurationfile.

107

An entry that is not valid has been found in theASNDLUSER configuration file.

108

An I/O error occurred when reading from theinput file.

109

An entry that is not valid has been found in theinput file.

110

Unable to open the input file.

111

Unable to open the result file.

112

An I/O error occurred when writing to the resultfile.

113

An error occurred when initializing the controlchannel of the FTP protocol.

114

An error occurred when sending data throughthe control channel.

115

Unable to log on to the file server with the givenuser and password.

116

The copy daemon has not yet started.

117

An error occurred when initializing the datachannel of the FTP protocol.

118

Unable to retrieve the file from the source fileserver.

119

Unable to store the file on the target file server.

120

An error occurred when transferring files in thepassive mode.

121

Cannot find the path mapping for the given filereference.

122

An error occurred when executing the FTPBINARY command.

123


An error occurred when executing the FTP SIZEcommand.

124

An error occurred when executing the FTPMODTIME command.

125

An error occurred when executing the FTP SITEUMASK command.

126

An error occurred when executing the FTP SITETOUCH command.

127

An error occurred when executing the FTP SITECHMOD command.

User Response: Check the return code and itscorresponding meaning (above). The return codeis based on the sample ASNDLCOPY programthat is shipped with the product. Additionalinformation is provided in the log file.

ASN1076E The Apply program cannot readthe format of the result file thatwas generated by theASNDLCOPY program.

Explanation: The result file that was generatedby the ASNDLCOPY program is not in anexpected format.

User Response: If you modified theASNDLCOPY program, check that your changesare not causing the invalid format. If yourchanges are not the cause of the problem, checkthat your machine has enough space for theresult file.

ASN1077E APPLY apply_qualifier. The Applyprogram encountered anDATALINK column value that isnot valid while updating thetarget table. The error code iserror_code.

Explanation: The DATALINK column field of arow fetched from the source table is not valid.


ASN1078E APPLY apply_qualifier. TheASNDLCOPY program wasterminated by the signalsignal_number. Additionalinformation can be found in thefilename file.

Explanation: The ASNDLCOPY programterminated abnormally by the given signal.

User Response: Check the specified log file forthe cause of the error. If you modified theASNDLCOPY program and the signal isgenerated by the modified code, fix the code andrerun. Otherwise, contact IBM Software Support.

ASN1097I APPLY apply_qualifier. The Applyprogram stopped.

Explanation: The error reported previouslycaused the Apply program to stop.

User Response: Fix the error reported beforethis message.

ASN1207E APPLY apply_qualifier. Thesubscription for subscription wasnot activated.

Explanation: The selected subscription isinactive.

User Response: Either activate the subscriptionor select another one.

ASN1210E APPLY apply_qualifier. An Applyqualifier must be specifiedfollowing the keyword -q.

Explanation: You must specify an Applyqualifier following the keyword -q.

User Response: Specify an Apply qualifierfollowing the keyword -q.


ASN1212E APPLY apply_qualifier. A read-onlyset name set_name is foundfollowing the keyword keyword.

Explanation: A read-only set name wasspecified following the keyword U or D.

User Response: Specify only replica for thekeywords U and D.

ASN1221I APPLY apply_qualifier. Set set_namehas been successfully refreshedwith number rows at time.



ASN1242E APPLY apply_qualifier. An SQLerror occurred. ERRCODE iserror_code, SQLSTATE is sqlstate,SQLCODE is sqlcode, SQLERRMis sqlerrm, SQLERRP is sqlerrp,table name is table_name.



ASN1243E APPLY apply_qualifier. There is noeligible subscription in theASN.IBMSNAP_SUBS_SET table.

Explanation: Either a subscription set has notbeen selected or the apply qualifier is not valid.

User Response: Verify the subscription namesand apply qualifier.

ASN1304E APPLY apply_qualifier. TheASNSAT program terminated dueto a Capture error.

Explanation: The Capture program returned anerror.

User Response: Determine the error from theCapture log file.

ASN1305E APPLY apply_qualifier. TheASNSAT program terminated dueto an Apply error.

Explanation: The Apply program returned anerror.

User Response: Determine the error from theApply log file.

ASN1310E APPLY apply_qualifier. TheASNSAT program encountered asystem error while attempting toinvoke the Capture program.Return code is return_code.

Explanation: An operating system erroroccurred while calling ASNCAP.

User Response: Make sure that the Captureprogram is in the execution path.

ASN1311E APPLY apply_qualifier. TheASNSAT program encountered asystem error while attempting toinvoke the Apply program.Return code is return_code.

Explanation: An operating system erroroccurred while calling ASNAPPLY.

User Response: Make sure that the Applyprogram is in the execution path.

ASN1312E APPLY apply_qualifier. The defaulttarget server, DB2DBDFT, is notset.

Explanation: The user did not specify the targetserver name, and the ASNSAT program couldnot determine the default database name fromDB2DBDFT.

User Response: Specify the target server namefollowing the -t keyword.


ASN1314E APPLY apply_qualifier. An SQLerror occurred while ASNSAT wasgetting the default Applyqualifier. SQLSTATE is sqlstate,SQLCODE is sqlcode.

Explanation: The user did not specify the Applyqualifier. The ASNSAT program encountered anerror while retrieving the USER special register.

User Response: Specify the Apply qualifierfollowing the -q keyword.

ASN1315E APPLY apply_qualifier. Cannotconnect to database server.SQLSTATE is sqlstate, SQLCODEis sqlcode.

Explanation: An error occurred whileattempting to connect to the target database.


ASN1316E APPLY apply_qualifier. ASNSATencountered an error while tryingto bind. The SQLSTATE is sqlstate,SQLCODE is sqlcode.

Explanation: An error occurred whileattempting to auto bind.

User Response: Make sure that the bind fileexists in the sqllib\bnd directory.

ASN1317E APPLY apply_qualifier. An SQLerror occurred while ASNSAT wasgetting the CD_TABLE value fromASN.IBMSNAP_REGISTER table.SQLSTATE is sqlstate, SQLCODEis sqlcode.

Explanation: An SQL error occurred whileselecting from the register table.


ASN1318E APPLY apply_qualifier. An SQLerror occurred while ASNSATattempted to get the DB2 nodetype. SQLSTATE is sqlstate,SQLCODE is sqlcode.

Explanation: An error occurred while retrievingthe node type configuration parameter.


ASN1500I The Replication action action_namestarted at timestamp witharchitecture level architecture_level.The Capture server iscapture_serveralias and the Captureschema is capture_schema.

Explanation: Valid values for action name areCreate Capture server control tables and DropCapture server control tables.


ASN1501I The Replication action action_namestarted at timestamp witharchitecture level architecture_level.The Capture server iscapture_serveralias, the remoteserver is remote_servername, andthe Capture schema iscapture_schema.

Explanation: Valid values for action name areCreate Capture server control tables and DropCapture server control tables.


ASN1502I The Replication action action_namestarted at timestamp witharchitecture level architecture_level.The Apply control server isapply_serveralias.

Explanation: Valid values for action name areCreate Apply server control tables and Drop Applyserver control tables.



ASN1503I The Replication action action_namestarted at timestamp. The Captureserver is capture_serveralias, theCapture schema is capture_schema,the source owner is source_owner,and the source table, view, ornickname is source_table.

Explanation: Valid values for action name areCreate Registration, Drop Registration, AlterRegistration, Add Registration, and PromoteRegistration.


ASN1504I The Replication action action_namestarted at timestamp. The Captureserver is capture_serveralias, theremote server is remote_server, theCapture schema is capture_schema,the source owner is source_owner,and the source table, view, ornickname is source_table.

Explanation: Valid values for action name areCreate Registration and Drop Registration.


ASN1505I The Replication action action_namestarted. The subscription setinformation follows: the Applycontrol server is control_server, theApply qualifier is apply_qualifier,the set name is set_name, the targetserver is target_server for remoteserver remote_servername, theCapture server is capture_server forremote server remote_servername,and the Capture schema iscapture_schema.

Explanation: Valid values for action name areCreate Subscription Set, Drop Subscription Set, AlterSubscription Set, and Promote Subscription Set.


ASN1506I The Replication action action_namestarted at timestamp. Thesubscription set informationfollows: the Apply control serveris control_server, the Applyqualifier is apply_qualifier, the setname is set_name, the target serveris target_server, the Capture serveris capture_server for remote serverremote_servername, and the Captureschema is capture_schema.



ASN1507I The Replication action action_namestarted at timestamp. Thesubscription set informationfollows: the Apply control serveris control_server, the Applyqualifier is apply_qualifier, the setname is set_name, the target serveris target_server for remote serverremote_server, the Capture server iscapture_server, and the Captureschema is capture_schema.




ASN1508I The Replication action action_namestarted at timestamp. Thesubscription set informationfollows: the Apply control serveris control_server, the Applyqualifier is apply_qualifier, the setname is set_name, the target serveris target_server, the Capture serveris capture_server, and the Captureschema is capture_schema.



ASN1510I The Replication action action_nameended successfully at timestamp.

Explanation: Valid values for action name areCreate Capture server control tables, Drop Captureserver control tables, Create Apply control servercontrol tables, and Drop Apply control server controltables.


ASN1511I The Replication action action_nameended successfully for sourceowner source_owner and sourcetable, view, or nicknamesource_table.

Explanation: Valid values for action name areCreate Registration, Drop Registration, AlterRegistration, Add Registration Column, and PromoteRegistration.


ASN1512I The Replication action action_nameended successfully for Applyqualifier apply_qual, set nameset_name.

Explanation: Valid values for action name areCreate Subscription Set, Drop Subscription Set, Alter

Subscription Set, Add Statements to Subscription Set,Drop Statements from Subscription Set, and PromoteSubscription Set.


ASN1513I The Replication action action_nameended successfully for Applyqualifier apply_qual, set nameset_name, who’s on firstwhos_on_first, source ownersource_owner, source tablesource_table, source view qualifiersource_view_qual, target ownertarget_owner, and target tabletarget_table.

Explanation: The following values are valid foraction name:

v Add Subscription Member

v Add Subscription Member Column

v Drop Subscription Member


ASN1514I The Replication action ended attimestamp with successful successes,errors errors, and warningwarnings.



ASN1550E The Replication action action_nameended in error. The value for theinput parameter input_parameter ismissing.

Explanation: The input parameter is mandatoryfor this action and is missing.

User Response: Provide the mandatoryparameter and rerun the Replication action.


ASN1551E The Replication action action_nameended in error. The value value forthe input parameterinput_parameter is incorrect. Thereason code is reason_code.

Explanation: The value provided for the inputparameter is not a valid value. The followingvalues are valid for the reason code:

0 Blocking minutes value should bebetween 0-999.

1 Commit Count value should be between0-999.

2 Server Type value should be 1.

3 Tables type value should be either 1 or2.

4 Remote Server Name value should beNULL.

5 Server Type value should be either 1, 2,4 or 5.

6 Internal CCD tables must benoncomplete.

7 The Apply qualifier exceeds themaximum length of 18 characters.

8 The set name exceeds the maximumlength of 18 characters.

9 Event names must be 18 characters orfewer in length.

10 The source Capture schema nameexceeds the maximum length of 30characters.

11 The target Capture schema nameexceeds the maximum length of 30characters.

12 The BEFORE_OR_AFTER statementvalue must be ’A’, ’B’, or ’S’.

13 The EI_OR_CALL value must be ’C’ or’E’.

14 SQLSTATES must be 50 digits or fewerin length.

15 SQLSTATES must be numeric

16 The CONFLICT_LEVEL must be zero(0) or NONE.

17 The CHGONLY value must be ’N’.

18 The external CCD table is noncondensedand contains LOB columns.

19 The CONFLICT_LEVEL must bebetween 0 and 2.

20 The CHGONLY value must be ’Y’ or’N’.

21 The RECAPTURE value must be ’Y’ or’N’.

22 The DISABLE_REFRESH value must be0 or 1.

23 The CHG_UPD_TO_DEL_INS valuemust be ’Y’ or ’N’.

24 The STOP_ON_ERROR value must be’Y’ or ’N’.

25 The BEFORE_IMG_PREFIX value mustbe only one character.

26 The corresponding table space does nothave the New Tablespace flag set to truein any of the previous scenarios.

27 The table name is not a valid controltable. Refer to the Replication Guideand Reference for a valid list of controltables.

User Response: Provide a valid value for theinput parameter, and rerun the replication action.See the online help for details.

ASN1552E The Replication action action_nameended in error. The value value1for input parameterinput_parameter1 is incompatiblewith the value value2 for inputparameter input_parameter2.

Explanation: The value provided for theReplication parameter clashes with anotherparameter specification.

User Response: Provide valid values for theinput parameters and rerun the Replicationaction. See the online help for details.


ASN1553E The value value1 for inputparameter input_parameter1 isincompatible with the value value2for the existing subscription setsubscription_set, Apply qualifierapply_qual, and who’s on firstwhoson_first.

Explanation: The value provided for theReplication parameter clashes with one of thevalues for the existing subscription set.

User Response: Provide a valid value for theinput parameter or change the subscription setdefinition, and rerun the Replication action. Seethe online help for details.

ASN1560E The replication action ended inerror. An SQL error wasencountered. SQL Message:sql_message.


User Response: Refer to your database messagereference for SQL.

ASN1561E Connection to the serverserver_alias cannot be established.An SQL error was encountered.SQL message: sql_message.

Explanation: The connection to the specifiedserver could not be established.

User Response: Refer to your database messagereference for SQL. Verify that the userid andpassword information is correct.

ASN1562E The Replication action ended inerror. An unexpected erroroccurred. Reference Codereference_code.

Explanation: The specified action cannot beperformed because of a run time error.


ASN1563E The Replication action action_nameended in error. The Replicationarchitecture level arch_level doesnot support server server_alias.

Explanation: The specified Replicationarchitecture level is not supported on thespecified server operating system, version, orrelease. The only valid value for arch_level at thistime is 0801.

User Response: Refer to the section in the DB2Replication Guide and Reference informationabout supported operating systems, versions,and releases for the replication architecture thatwas specified in the message.

ASN1564E The Replication action action_nameended in error. The Capture serverReplication architecture level forCapture schema capture_schemadoes not support this Replicationaction.

Explanation: The replication architecture levelfound in thecaptureschema.IBMSNAP_REGISTER does notallow the specified replication action.

User Response: Migrate the Capture servercontrol tables to 0801 before attempting thisaction.

ASN1565E The Replication action action_nameended in error. The Apply ControlServer Replication architecturelevel does not support thisreplication action.

Explanation: The Replication architecture levelfound in the ASN.IBMSNAP_SUBS_SET does notallow the specified Replication action.

User Response: Migrate the Apply controlserver control tables to 0801 before attemptingthis action.


ASN1567W The table space containerinformation for table spacetablespace_name cannot be read,because the DB2 stored procedureprocedure_name in the librarylibrary_name cannot be found.

Explanation: The DB2 Stored ProcedureREADTSCINFOS cannot be found on theCapture or target DB2 server. The storedprocedure is required to retrieve DB2 table spacecontainer information for that server.

User Response: Determine whether the storedprocedure exists on the server: check if the filedb2rtsc exists in the function directory of thesqllib directory. The file db2rtsc might not exist ifthe server is a pre-V8 server. If the storedprocedure does not exist, then edit the tablespace container definition provided in the outputscript.

ASN1568E The name length length for theDB2 object, objectname exceeds theallowed limit of allowed_limit.

Explanation: The DB2 object type provided inthe second parameter allows a length that issmaller than the length of the actual objectprovided in the third parameter. As in theProperties file, the following values are valid forobject: Table, Index, Tablespace, Table owner.

User Response: Refer to the DB2 SQLReference, and provide the correct name length.

ASN1569E The name of the DB2 object to becreated is identical to the existingname objectowner.objectname of typeobjecttype.

Explanation: The DB2 object cannot be createdbecause there is already a DB2 object of the sametype with the same name. As in the Propertiesfile, the following values are valid for object:Table, Index, Tablespace, Table owner.

User Response: Provide a name for that objectthat does not already exist in DB2, and reissuethe Replication task.

ASN1570E The DB2 object object,objectowner.objectname does notexist.

Explanation: The DB2 object does not exist inthe DB2 catalog. This object must exist in orderto be defined as a source or target of asubscription set, as per the replication action.This object might have been defined as part of anexisting registration or subscription-set definitionbut is not found in the DB2 catalog. As in theProperties file, the following values are valid forobject: Table, Index, Tablespace, Table owner.

User Response: Provide a name that alreadyexists in DB2, and reissue the Replication task. Ifthe object was defined as part of an existingregistration or subscription-set definition, verifythat the object exists in the DB2 catalog.

ASN1571E The DB2 table tableowner.tablenamecannot be created: the DB2definition is not valid for datatype datatype and columncolumn_name. The reason code isreason_code.

Explanation: The following values are valid forthe reason code:

0 The datatype is not supported on thisplatform.

1 The length of the column is notsupported on this platform.

2 The precision or scale of the column isnot supported on this platform.

User Response: Refer to the SQL Reference forthe appropriate DB2 platform.

ASN1572E The row size row_size for DB2object objectowner.objectname oftype object_type exceeds its DB2buffer pool row sizebufferpool_rowsize. The DB2 objectcannot be created.

Explanation: The row size of a table cannotexceed the table space page size for that table.The table space page size is derived from the


buffer pool page size to which it belongs. Noscript is generated.

User Response: You might have to create thetable in a different table space. Refer to your DB2operating system documentation.

ASN1573E The number of columnsnumber_columns for the DB2 objectobjectowner.objectname of typeobject_type exceeds the DB2 limitdb2_limit. The DB2 object cannotbe created.

Explanation: The number of columns a DB2object (table or index) can contain depends onthe DB2 operating system but cannot exceed apredefined number. No script is generated. Thefollowing values are valid for object type: table,index.

User Response: Redesign the DB2 object.

ASN1574E The DB2 page size page_size forTablespace tablespace_name is notvalid. Reason code reason_code.

Explanation: The PageSize must be valid for thetable space to be created successfully. Thefollowing values are valid for reason code:

0 PageSize is not equal to the PageSize ofthe given buffer pool.

1 PageSize is not equal to one of thefollowing: 4K, 8K, 16K, 32K.

User Response: Refer to the DB2 SQL Referencefor appropriate PageSize ranges or values.

ASN1575W The DB2 table tableowner.tablenamewill be created in the DB2 defaultTablespace.

Explanation: No table space name was specifiedindicating where to create the specified table, sothe table will be created in the DB2 default tablespace. This might be a problem if the defaulttable space specifications are not appropriate forthe specified table.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the table to be in

its own table space, then reissue the Replicationtask with the appropriate specifications. Noaction is required if the default is appropriate forthe table.

ASN1576W The DB2 index index_name will becreated in the DB2 defaultIndexspace or Tablespace.

Explanation: A table space (for workstationoperating systems) or an indexspace (for z/OSoperating systems) was not provided into whichthe specified index might be created. Therefore,the index is created using the DB2 defaults. Thismight be a problem if the default specificationsare not appropriate for the specified index.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the index to bein its own table space or indexspace, then reissuethe Replication task with the appropriatespecifications. No action is required if the defaultis appropriate for the index.

ASN1577W The DB2 table space tablespace willbe created in the DB2 defaultdatabase.

Explanation: For z/OS operating systems only,a database was not provided into which thespecified table space might be created. Therefore,the table space is created using the DB2 defaults.This might be a problem if the defaultspecifications are not appropriate for thespecified table space.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the table spaceto be in its own database, then reissue theReplication task with the appropriatespecifications. No action is required if the defaultis appropriate for the table space.

ASN1578I The DB2 table space tablespace willbe created in the DB2 defaultstorage group.

Explanation: For workstation and z/OSoperating systems only, a storage group was notprovided into which the specified table spacemight be created. Therefore, the table space is


created using the DB2 defaults. This might be aproblem if the default specifications are notappropriate for the specified table space.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the table spaceto be in its own storage group, then reissue theReplication task with the appropriatespecifications. No action is required if the defaultis appropriate for the table space.

ASN1579I The DB2 index index_name will becreated in the DB2 default storagegroup.

Explanation: For workstation and z/OSoperating systems only, a storage group was notspecified into which the DB2 index might becreated. Therefore, DB2 created the index usingthe default specification. This might be aproblem if the default specifications are notappropriate for the specified index.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the index to bein its own storage group, then reissue theReplication task with the appropriatespecifications. No action is required if the defaultis appropriate for the index.

ASN1580I The DB2 table space tablespace willbe created in the DB2 defaultbuffer pool.

Explanation: For workstation and z/OSoperating systems only, a buffer pool was notprovided into which the specified table spacemight be created. Therefore, the table space iscreated using the DB2 defaults. This might be aproblem if the default specifications are notappropriate for the specified table space.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the table spaceto be in its own buffer pool, then reissue theReplication task with the appropriatespecifications. No action is required if the defaultis appropriate for the table space.

ASN1581I The DB2 index index_name will becreated in the DB2 default bufferpool.

Explanation: For workstation and z/OSoperating systems only, a buffer pool was notprovided into which the specified index might becreated. Therefore, the index is created using theDB2 defaults. This might be a problem if thedefault specifications are not appropriate for thespecified index.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the index to bein its own buffer pool, then reissue theReplication task with the appropriatespecifications. No action is required if the defaultis appropriate for the index.

ASN1582W The Tablespace tablespace will becreated in Buffer Pool buffer_poolbut the buffer pool does not existor is not active.

Explanation:

v For applications on a DB2 UDB database, thebuffer pool does not exist into which thespecified table space might be created.

v For applications on a DB2 for z/OS database,the buffer pool is not active into which thetable space might be created.

User Response:

v For the DB2 UDB database, make sure that thebuffer pool exists at the time of running thescript.

v For a DB2 for z/OS database, make sure thebuffer pool is active at the time of running thescript.

v

ASN1583E The PageSize page_size forTablespace tablespace does notmatch the default buffer poolPageSize.

Explanation: The given PageSize does notmatch the PageSize of the default buffer pool.The table space cannot be created.


User Response: Change the PageSize or chooseanother buffer pool.

ASN1584E The Replication action action_nameended in error. The Capture serverReplication architecture levelarch_level for Capture schemacapture_schema is not a validarchitecture level.

Explanation: The Replication architecture levelfound in thecaptureschema.IBMSNAP_REGISTER does notallow the specified Replication action.

User Response: Drop the control tables on theCapture control server manually because thearchitecture level is not supported. Create thecontrol tables with a valid architecture level.

ASN1585E The Replication action action_nameended in error. The Apply controlserver Replication architecturelevel arch_level is not a validarchitecture level.

Explanation: The Replication architecture levelfound in the ASN.IBMSNAP_SUBS_SET does notallow the specified Replication action.

User Response: Drop the control table on theApply control server manually because thearchitecture level is not supported. Create thecontrol tables with a valid architecture level.

ASN1586W The DB2 table tableowner.tablenamewill be created in the DB2 defaultdatabase.

Explanation: For z/OS operating systems only,a database was not provided into which thespecified table might be created. Therefore, thetable is created using the DB2 defaults. Thismight be a problem if the default specificationsare not appropriate for the specified table.

User Response: Refer to the SQL Reference forthe DB2 defaults. If you require the table spaceto be in its own database, then reissue theReplication task with the appropriatespecifications. No action is required if the default

is appropriate for the table.

ASN1587E The value value for the parameterparameter_name of the DB2 objectdb2object_name, which has a typeof type, is not valid.

Explanation: The provided value is not valid orconflicts with another parameter value.

User Response: Refer to the SQL Reference forvalid values.

ASN1588E The value encoding_schemeprovided for the parameterencoding scheme is not valid forthe DB2 server server_name.

Explanation: The provided value for theencoding scheme is not valid for the DB2 versionof the server. No script is generated.

User Response: Refer to the SQL Reference fora valid value of the encoding schema for the DB2version.

ASN1589W The calculation of the size of thetable space container container ofthe table space tspace resulted inan incorrect container size.Therefore the container size hasbeen changed to size sizemegabytes.

Explanation: The calculation of the table spacecontainer size has resulted in a value that is toolow to be used in a valid table space containerdefinition. To ensure that the definition will beaccepted by DB2, a replication specific minimumcontainer size has been provided for the tablespace container definition.

User Response: For the calculation based on apercentage of the current source table size, checkwhether the source table contains data and if thestatistics of the source table are up to date (usingthe RUNSTATS utility) . For the calculation basedon a number of rows, check whether the numberof rows is realistic.


ASN1590E The DB2 table space table_sp_nameis partitioned and in the DB2object_type group. It should not bepartitioned and it should be inthe object_type IBMCATGROUP.

Explanation: The provided table space is apartitioned table space and does not reside onthe DB2 catalog node or partition group.Creation of the Replication control tables in apartitioned table space is not supported. NoScript is generated.

User Response: Specify a table space that is notpartitioned.

ASN1600E The REMOTE SERVERremote_servername cannot be found.

Explanation: The specified remote server namecannot be found in the Federated Catalog tableSYSIBM.SYSSERVERS, columnREMOTE_SERVER. The non-DB2 relationalserver cannot be accessed.

User Response: Verify the input provided forthe remote server name and call the action again,or populate the Federated Catalog tableappropriately.

ASN1601E The REMOTE AUTHIDinformation for the REMOTESERVER remote_servername cannotbe found.

Explanation: The remote authenticationinformation cannot be found in the FederatedCatalog table SYSIBM.SYSXXXXX, for theREMOTE_SERVER value provided. The non-DB2relational server cannot be accessed.

User Response: Verify the input provided forthe remote server name and call the action again,or populate the Federated Catalog tableappropriately.

ASN1602E The server server_alias does notsupport access to Federatedservers.

Explanation: The Federated replicationfunctions are only supported on the DB2 UDBWorkstation V8 and higher.

User Response: Make sure the specifieddatabase server is one of those listed above or donot issue the replication task against a server thatdoes not support it.

ASN1603E The Replication Apply controlserver cannot reside on a non-IBMserver.

Explanation: Non-DB2 relational servers can bereplication Capture control servers or targetservers, but they cannot be Apply controlservers.

User Response: Specify a DB2 server as theReplication Apply control server.

ASN1604E The remote tableremoteowner.tablename exists in thenon-IBM server, but the providednickname nicknameowner.nicknamecannot be found in the Federatedserver.

Explanation: The specified remote table exists inthe remote database but the correspondingnickname is not found in the federated database.

User Response:

1. Refer to the DB2 Federated manuals on howto create a nickname.

2. Create the nickname in the federateddatabase.

3. Issue the Replication task again.


ASN1605E The nicknamenicknameowner.nickname exists inthe Federated server but theremote table remoteowner.remotetablecannot be found in the non-IBMserver.

Explanation: The nickname for the specifiedremote table exists but the corresponding remotetable does not exist in the remote database. Thisis an inconsistent state of definitions whencreating Replication definitions.

User Response:

1. Drop the nickname.

2. Depending on the table type, perform thefollowing actions:

v If the table is a user table, create theremote table in the remote server.

v If the table is a replication control table onthe Capture control server, perform thefollowing actions:

a. Copy the data from the existing controltables on the Capture control server.

b. Drop the control tables on the Capturecontrol server.

c. Create the control tables on the Capturecontrol server.

3. Create the Nickname in the federated server.

4. Issue the Replication task again.

ASN1606W The nicknamenickname_owner.nickname_nameexists in the Federated server butthe remote tabletable_owner.table_name cannot befound in the non-IBM server.

Explanation: The nickname for the specifiedremote table exists but the corresponding remotetable does not exist in the remote database.Although this is an orphan nickname, thisinconsistent state is still tolerated when droppingReplication definitions. A script is generated.

User Response: The source nickname is notdropped when dropping the replicationdefinitions. To ensure a consistent catalog, dropthe nickname.

ASN1607W It is strongly recommended toalter the nicknamenickname_owner.nickname_namedefined for the Replicationsubscription target: to alter thelocal data type of columncolumn_name fromexisting_local_datatype torecommended_local_datatype andensure the proper source to targetcolumn data type mapping.

Explanation: A mismatch was found between asource column data type and its correspondingnickname target column data type, that does notviolate DB2 compatibility rules, but that mightcause a problem to native non-IBM end-userapplications. The problem does not occur duringreplication of the column data. The problem doesoccur if end-user applications retrieve the data.For example, if the nickname data type is createdusing the default mappings from the non-DB2relational data type to the DB2 data type, thecolumn will hold the broadest range of data typevalues, which might clash with the end-userapplication requirement of a more restrictive datatype. A script is generated.

User Response: Check the target to ensure thatthe nickname data type you need at the target isindeed the source column data type. If it is, thenissue an ’ALTER NICKNAME’ statement tochange the local data type of the nicknamecolumn. When you alter the nickname local datatype to be the same as the source column datatype, you enforce that the end-user applicationon the non-DB2 relational server sees the samedata type as the source column data type.


ASN1608I The nickname source_nickname forthe source and the nicknameccd_nickname for the ConsistentChange Data table have a columndata type that is altered: the localdata type column local_datatype isset to changed_datatype because theremote data type isremote_datatype. Reason Codereason_code.

Explanation: This message is issued at the timeof creating the nickname for the CCD. Thenickname is altered based on the data type of theCCD created in the non-DB2 relational server, toensure the proper data type setting. Failure to doso would result in improper Replicationbehavior. A script is generated, that updateduser-provided definitions.

User Response: No action is required if theReplication updates are acceptable.

ASN1609E The nicknamenicknameowner.nickname exists inthe Federated server but theremote table remoteowner.remotetabledoes not contain all the necessarycolumns.

Explanation: The target table nickname exists,and contains only a subset of the columnsrequested in the subscription.

User Response: Use another Nickname as thetarget table or change the subscription to matchthe columns in the existing nickname.

ASN1620E Both Capture server control tablesand Apply control server controltables already exist. Captureserver control tables exist witharchitecture level capturearch_leveland Capture Schemacapture_schema. Apply controlserver control tables exist witharchitecture level applyarch_level.

Explanation: The tablescaptureschema.IBMSNAP_REGISTER and

captureschema.IBMSNAP_SUBS_SET alreadyexist at the given server.

User Response:

v If the architecture level of the existingcaptureschema.IBMSNAP_REGISTER controltable is 0201:

– if the existingcaptureschema.IBMSNAP_REGISTER isalready populated with valid Replicationdefinitions, migrate the Capture servercontrol tables to the 0801 architecture,

– if the table is empty, simply drop the pre-V8Capture server control tables and reissuethe Replication task again.

v If the architecture level of the existing controltables is not 0201, consider creating Captureserver control tables with a different captureschema name.

v If the architecture level of the existingIBMSNAP_SUBS_SET control table is 0201:

– if the existing ASN.IBMSNAP_SUBS_SETtable is already populated with validReplication definitions, migrate the Applycontrol server control tables to the 0801architecture,

– if the table is empty, simply drop the pre-V8Apply control server control tables andreissue the Replication task again

v If the architecture level of the existing controltables is not 0201, consider creating Applycontrol server control tables on a differentserver.

ASN1621W At least one row was found in thecontrol tablecontrolowner.controltable. Droppingof this control table will result indropping of all Replicationdefinitions stored in the table.

Explanation: The control tables that aredropped are not empty. Replication controlinformation is deleted if the generated scripts areexecuted.

User Response: Run the generated scripts onlyif you can ensure the following dependencies:


v Understand the impact to existing dependentsubscription sets of dropping the control tablesfrom the Capture control server.

v Understand the impact to existing dependentsubscription sets (for multi-tier scenarios) ofdropping control tables from the Apply controlserver.

v You do not want Replication to run theCapture or the Apply processes for thesedefinitions anymore.

If the architecture level is 0201, migrate theCapture or Apply control server control tables tothe 0801 architecture before dropping the controltables.

ASN1622E The Replication action action_nameended in error. The requiredcontrol tablecontrolowner.controltable could notbe found.

Explanation: Replication definitions are storedin Replication control tables. These tables mustexist before a registration or subscriptiondefinition can be created. The existence of theIBMSNAP_REGISTER table is used to check ifthe control tables for the Capture control serveralready exist for a particular Capture schema.The existence of the IBMSNAP_SUBS_SET tableis used to check if the control tables on theApply control server already exist. The existenceof IBMSNAP_SUBS_MEMBR is checked at thetime of checking for the existence of asubscription member.

User Response: If the control tableIBMSNAP_SUBS_MEMBR table does not exist,then your environment is in an inconsistent state.You must drop all the control tables from theApply control server and then create them beforeattempting the action.

Alternatively, if the control tablesIBMSNAP_REGISTER or IBMSNAP_SUBS_SETdo not exist, create them before addingregistration or subscription definitions on acontrol server. Otherwise, you can do thefollowing:

1. If you are doing a registration-related action,check if the appropriate Capture schema was

provided; or if the appropriate Capturecontrol server was provided as input.

2. If you are doing a subscription-related action,check if the appropriate Apply control serverwas provided as input.

3. If you are creating a subscription set thatcontains target tables that need to beauto-registered at the target server (CCD orreplica), then check if the appropriate controltables for the Capture control server exist atthe subscription target server.

ASN1623W The Replication control table,controlowner.controltable could notbe found and is not dropped.

Explanation: The Drop Capture control tables orDrop Apply control server control tables action wasissued and the control table was missing. Thescript will not generate the appropriate DROPstatement for that control table.


ASN1624I The server server_alias is not aknown Replication Capture serverfor capture_schema.

Explanation: Thecaptureschema.IBMSNAP_REGISTER table couldnot be found. A server is defined as a ReplicationCapture server when the appropriate Captureserver control tables (including theIBMSNAP_REGISTER table) exist on the server.

User Response: Create the appropriate Captureserver control tables, if needed.

ASN1625I The server server_alias is not aknown Replication Apply controlserver.

Explanation: The ASN.IBMSNAP_SUBS_SETtable could not be found. A server is defined as aReplication Apply control server when theappropriate Apply control server control tables(including the IBMSNAP_SUBS_SET table) existon the server.

User Response: Create the appropriate control


tables on the Apply control server, if needed.

ASN1626E Capture server control tablesalready exist for architecture levelarch_level with the same Captureschema.

Explanation: The tablecaptureschema.IBMSNAP_REGISTER alreadyexists at the given server.

User Response:

v If the architecture level of the existingcaptureschema.IBMSNAP_REGISTER table is0801, consider the following options:

– Running the command is not necessarybecause the tables already exist with thesame Capture schema.

– Run the command under a differentCapture schema.

v If the architecture level of the existingcaptureschema.IBMSNAP_REGISTER controltable is 0201:

– Migrate the Capture control server controltables to the 0801 architecture, if the existingcaptureschema.IBMSNAP_REGISTER isalready populated with valid Replicationdefinitions.

– If the control table is empty, simply dropthe pre-V8 Capture server control tables andissue the Replication task again.

Otherwise, the architecture level is not valid.You need to drop the tables manually beforeattempting to create the tables.

ASN1627E Some Capture server controltables already exist with the sameCapture Schema but for which anarchitecture level cannot bedetermined.

Explanation: The tablecaptureschema.ASN.IBMSNAP_REGISTER doesnot exist although other Capture server controltables were found at the given server. Captureserver control tables cannot be created until thetables are dropped. The Replication definitions atthe Capture server are in an inconsistent state.

User Response: Drop the remaining Captureserver control tables to clean up the Capturecontrol server definitions, and reissue the Createcontrol table task. Loss of data occurs, so look atthe content of the remaining control tables beforeissuing the drop task.

ASN1628E The Capture server control tablesare not at the architecture levelrequested.

Explanation: The tablecaptureschema.IBMSNAP_REGISTER does notexist with the provided architecture level. Noscript is generated.

User Response: Issue the replication task againat the appropriate architecture level for theappropriate Capture control server and Captureschema.

ASN1629E No Capture server control tableswere found for the providedCapture schema.

Explanation: No control tables exist on theCapture control server. No control tables aredropped, and no script is generated.

User Response: Issue the replication task againat the appropriate architecture level for theappropriate Capture control server and Captureschema.

ASN1630W Some Capture server controltables already exist with CaptureSchema capture_schema but theirarchitecture level cannot bedetermined. The Replicationaction action_name for theprovided architecture levelarch_level and Capture Schemawill drop control tables that mightnot belong to the architecturelevel provided.

Explanation: The tablecaptureschema.IBMSNAP_REGISTER does notexist on the Capture server. The Replicationarchitecture level is unknown, and if you providean incorrect architecture level, you might lose


critical data. No checks occur to determinewhether a particular Capture server control tablearchitecture level can be inferred. The controltable is dropped if it exists. A script is generated.

User Response: Issue the task again with theappropriate architecture level for DB2 replication.

ASN1631E Apply control server controltables already exist forarchitecture level arch_level.

Explanation: The tableASN.IBMSNAP_SUBS_SET already exists at thegiven server. No script is generated.

User Response: If the architecture level of theexisting ASN.IBMSNAP_SUBS_SET control tableis 0201:

v If the existing ASN.IBMSNAP_SUBS_SET isalready populated with valid Replicationdefinitions, Apply control server control tablesto the 0801 architecture,

v If the table is empty, simply drop the pre-V8Apply control server control tables and reissuethe Replication task again.

Otherwise, the architecture level is not valid. Youneed to drop the tables manually beforeattempting to create the tables.

ASN1632E Some Apply control server controltables already exist but for whichan architecture level cannot bedetermined.

Explanation: The tableASN.IBMSNAP_SUBS_SET does not existalthough other Apply control server controltables were found at the given server. Applycontrol server control tables cannot be createduntil the tables are dropped. The Replicationdefinitions at the Apply control server are in aninconsistent state. No script is generated.

User Response: Drop the remaining controltables on the Apply control server to clean upthe Apply control server replication definitions.Reissue the Create control table task. Loss of dataoccurs, so look at the content of the remainingcontrol tables before issuing the Drop task.

ASN1633E The Apply control server controltables are not at the architecturelevel requested.

Explanation: The tableASN.IBMSNAP_SUBS_SET does not exist withthe provided architecture level. No script isgenerated.

User Response: Issue the replication task againat the appropriate architecture level for theappropriate Apply control server.

ASN1634E No Apply control server controltables were found.

Explanation: There are no control tables to dropfrom the Apply control server. No script isgenerated.

User Response: Issue the replication task againat the appropriate architecture level for theappropriate Apply control server.

ASN1635W Some Apply control server controltables already exist but theirarchitecture level cannot bedetermined. The Replicationaction action_name for theprovided architecture levelarch_level will drop control tablesthat might not belong to thearchitecture level provided.

Explanation: The tableASN.IBMSNAP_SUBS_SET does not exist on theApply control server. The Replication architecturelevel is unknown, and if you provide anincorrect architecture level, you might losecritical data. No checks occur to determinewhether a particular Apply control server controltable architecture level can be inferred. If thecontrol table exists, it is dropped. A script isgenerated.

User Response: Reissue the task with theappropriate architecture level for DB2 replication.


ASN1636E The Replication Action of ManualFull Refresh ended with an errorfor the Apply qualifier apply_qualand set name set_name. Thesynchpoint in thecaptureschema.IBMSNAP_PRUNCNTLtable for the source membersourceowner.sourcetable and thetarget membertargetowner.target_table is nottranslated by the Captureprogram.

Explanation: The synchpoint is either less than0 or equal to hex zeros.

User Response: Make sure you run the beforeload script to translate the hex zeros and captureis running on the server.

ASN1637E The replication action ’ManualFull Refresh’ ended in error forthe Apply qualifier apply_qualifierand the set name set_name. Thetarget structure of at least one ofthe target subscription-setmembers in the givensubscription set is greater thaneight. None of thesubscription-set members iseligible for a manual full refresh.

Explanation: The target structure of at least oneof the target subscription-set members in thegiven subscription set is greater than eight. Amanual full refresh does not support targetstructures that are greater than eight.

User Response: Make sure that the targetstructure of the subscription-set member is lessthan or equal to eight, and then reissue thereplication task.

ASN1638W The subscription-set member witha target of targetowner.targetnameand a source ofsourceowner.sourcename is notcomplete. This subscription-setmember is not included in themanual full refresh.

Explanation: The manual full refresh supportscomplete targets only. The given subscription-setmember is not complete and cannot be included.


ASN1639E The replication action ’ManualFull Refresh’ ended in error forthe Apply qualifier apply_qualifierand the set name set_name. Noneof the target subscription-setmembers in the givensubscription set is complete oreligible for a manual full refresh.

Explanation: The manual full refresh supportscomplete targets only, and none of the targets iscomplete.

User Response: Make sure that at least one ofthe subscription-set members in the subscriptionset is complete, and reissue the replication task.

ASN1640E The replication action ended inerror for the Apply qualifierapply_qualifier and the set nameset_name. There are nosubscription-set members in thesubscription set.

Explanation: The subscription set does notcontain any subscription-set members.

User Response: Add at least onesubscription-set member to the subscription set,and reissue the replication task.


ASN1641E The replication action action_nameended in error. This action on anOS/400 system is supported onlythrough OS/400 commands.

Explanation: Neither the replication center northe command line supports the replication actionon an OS/400 system. The possible actions mightbe: creating capture server control tables, creatingapply server control tables, dropping captureserver control tables, or dropping apply servercontrol tables.

User Response: Issue OS/400 commands toperform the replication action.

ASN1650I The replication action action_namestarted at timestamp. The monitorserver is server_name and theGroup_or_Contact name isgroup_name_or_contact_name.

Explanation: The replication action started atthe specified monitor server.


ASN1653I The replication action action_namefor group_contact_or_condition_nameended successfully at timestamp.The monitor server is server_name.

Explanation: The replication action endedsuccessfully at the specified monitor server.


ASN1654E The replication action action_nameended in error. The length of theinput parameter parameter-name,parameter_length exceeds the limitmaximum-limit.

Explanation: The length of the specified inputparameter is longer than the maximum allowablelength. No script is generated.

User Response: Verify the input parametervalue, and re-enter the parameter value.

ASN1655E The replication action action_nameended in error. The valueinput_value of the input parameterinput_parameter is incorrect.

Explanation: The value of the specified inputparameter is not correct.

User Response: Refer to your documentationfor valid parameter values.

ASN1656E The replication action action_nameended in error. The value of theinput parameter input_parameter ismissing.

Explanation: A value for this specified inputparameter is mandatory for this action. However,the value is missing. No script is generated.

User Response: Enter a value for thismandatory input parameter, and rerun thereplication action.

ASN1657E The replication action action_nameended in error. At least oneoptional parameter value must bespecified.

Explanation: You must specify at least oneoptional parameter value when issuing acommand in which each parameter value isoptional. No script is generated.

User Response: Issue the command again withthe correct parameters.

ASN1658E The replication action action_nameended in error. The value value1 ofthe input parameterinput_parameter1 must be differentthan the value value2 of the inputparameter input_parameter1.

Explanation: The value of one input parameteris the same as the value of another inputparameter and will result in the creation ofinconsistent definitions. No script is generated.

User Response: Issue the command again withvalid parameter values.


ASN1659E The replication action action_nameended in error. The contactcontact-name already exists.

Explanation: The specified contact namealready exists in one of the rows in theASN.IBMSNAP_CONTACTS table. Contactnames must be unique. No script is generated.

User Response: Issue the command again witha different contact name.

ASN1660E The replication action action_nameended in error. The contactcontact-name does not exist.

Explanation: The specified contact name doesnot exist in any of the rows in theASN.IBMSNAP_CONTACTS table. The contactname must exist in theASN.IBMSNAP_CONTACTS table before youcan alter, substitute, delegate, or drop the name.No script is generated.

User Response: Issue the command again witha different contact name.

ASN1661E The replication action action_nameended in error. The contactcontact-name cannot be dropped,because dropping the contactempties each associated group.

Explanation: A group should have at least oneassociated contact. The specified contact is thelast contact in each associated group, and the lastcontact cannot be dropped. No script isgenerated.

User Response: Drop each associated groupbefore attempting to drop the contact.

ASN1662E The replication action action_nameended in error. The contactcontact-name cannot be dropped,because the contact is associatedwith one or more conditions.

Explanation: The contact name that you areattempting to drop is the only contact associatedwith conditions for either the Capture or Apply

components. No script is generated.

User Response: Use the SUBSTITUTE option inthe DROP CONTACT command, or use theSUBSTITUTE command to change the contactname of the conditions. If you do not need theconditions, drop the conditions and then dropthe contact.

ASN1663E The replication action action_nameended in error. The valuestartdate_value that is specified forthe start date is greater than thevalue enddate_value, which isspecified for the end date.

Explanation: You cannot enter a start date thatis beyond the end date. No script is generated.

User Response: Issue the command again witha valid combination of dates.

ASN1664E The replication action action_nameended in error. The groupgroup-name already exists.

Explanation: The specified group name alreadyexists in one of the rows in theASN.IBMSNAP_GROUPS table. Group namesmust be unique.

User Response: Change the group name, andissue the command again.

ASN1665E The replication action action_nameended in error. The groupgroup_name does not exist.

Explanation: The specified group name doesnot exist in any of the rows in theASN.IBMSNAP_GROUPS table. The group namemust exist in the ASN.IBMSNAP_GROUPS tablebefore you can alter or drop the group name. Noscript is generated.

User Response: Verify the group name, andreissue the command.


ASN1666E The replication action action_nameended in error. The groupgroup_name cannot be droppedbecause it is associated with oneor more conditions.

Explanation: The group that you are attemptingto drop is the only group associated withconditions for either the Capture or Applycomponents. No script is generated.

User Response: In order to drop the group,alter the contacts of the associated conditions andthen reissue the command.

ASN1667E The replication action action_nameended in error. The contactcontact-name is not associated withthe specified group group_name.

Explanation: The contact name that you areattempting to drop is not associated with thespecified group.

User Response: Verify the specified contactname and reissue the command.

ASN1668E The replication action action_nameended in error. The contactcontact-name is already associatedwith the specified groupgroup_name.

Explanation: The contact name that youspecified is already associated with the specifiedgroup.


ASN1671E The replication action action_nameended in error. The alert conditioncondition-name already exists forthe monitor qualifier mon-qual, theserver server-name, the schema orqualifier schema-or-qualifier, andthe subscription-set nameset-name.

Explanation: The alert condition that you areattempting to create already exists with the same

specified parameters on the monitor controlserver.

User Response: Verify this alert condition andissue the command again.

ASN1672E The replication action action_nameended in error. The alert conditioncondition-name does not exist forthe monitor qualifier mon-qual, theserver server-name, the schema orqualifier schema-or-qualifier, andthe subscription-set nameset-name.

Explanation: The alert condition that you areattempting to drop or to alter does not exist onthe monitor control server.

User Response: Verify the alert name and issuethe command again.

ASN1673W The condition condition_name isvalid only at the apply qualifierlevel.

Explanation: The condition name is not validwith a subscription-set name value. The name ofthe subscription set will be ignored.

User Response: Do not specify thesubscription-set name value.

ASN1674W The condition condition_name isvalid only with update-anywheresubscription sets.

Explanation: The condition name is valid onlywith update-anywhere subscription sets.

User Response: Do not set this condition. Thiscondition will be ignored.

ASN1675I This is a test message from theReplication Center.

Explanation: This message is used to send a teste-mail verifying the e-mail address entered in thecontact.



ASN1677E The replication action action_nameended in error. The applyqualifier apply-qual and thesubscription-set name set-name donot exist on the server server-name.

Explanation: The apply qualifier and thesubscription-set name do not exist in theASN.IBMSNAP_SUBS_SET table on the specifiedapply control server.

User Response: Supply a valid apply qualifierand a valid subscription-set name.

ASN1678E The replication action action_nameended in error. The captureschema cap-schema does not existon the server server-name.

Explanation: The capture schema does not existin the ASN.IBMSNAP_CAPSCHEMAS table onthe specified capture control server.

User Response: Supply a valid capture schema.

ASN1679E The replication action action_nameended in error. The contactcontact_name that you attempted tosubstitute is not associated with acondition.

Explanation: The contact name does not exist inthe ASN.IBMSNAP_CONDITIONS table. Acontact can be substituted only if it exists in theASN.IBMSNAP_CONDITIONS table. No script isgenerated.

User Response: Supply a valid contact name.

ASN1680I The Replication action action_namestarted at time. The Monitor serveris server_name.


User Response: No action required.

ASN1681E The Replication action ended inerror. Monitor control tablesalready exist for ArchitectureLevelarch_level.

Explanation: The monitor control tables alreadyexists at the monitor server.

User Response: If the architecture level of theexisting monitor tables is 0801, there is no needto run the command since the tables alreadyexist.

ASN1682E The Replication action ended inerror. No Monitor control tableswere found.

Explanation: There are no Monitor controltables to drop. No script will be generated.

User Response: Issue the replication task againfor the appropriate server containing the Monitorcontrol tables.

ASN1700E The columntableowner.tablename.columnname ofdata type data_type cannot beincluded in the registration.Reason Code reason_code.

Explanation: The column cannot be supportedby the Replication Capture mechanism, asdefined. No script for the registration of thecolumn specified is generated. The followingvalues are valid for the reason code:

0 The data type is not supported.

1 The column is already registered.

2 z/OS fieldproc column.

3 This column does not qualify as abefore-image column.

4 The data type is not supported throughDB2 for federated.

5 The column does not exist in the sourceobject.

6 The maximum number of registeredLOB columns was exceeded for thattable.


7 The column name starts with thebefore-image prefix.

8 This column does not qualify as abefore-image column or as anafter-image column.

User Response: Check the Reason Code to getthe reason why the column cannot be registered.Refer to the DB2 Replication Guide andReference for additional explanations orrestrictions.

ASN1701E The provided locksize valuelock_size for the given table spacetablespace_name is not valid.

Explanation: Locksize should be equal to theP(PAGE), R(ROW) or A(ANY), in the case ofz/OS operating system.

User Response: Provide the correct locksize andsubmit your action again.

ASN1702W Replication definitions for theregistered columnobjectowner.objectname.columnnamehas been changed to support nullvalues.

Explanation: before-image columns are requiredto support null values. If no before-imagecolumn value is present, an INSERT statementwill fail. A script is generated to updateuser-provided definitions.

User Response: This message is for yourinformation only; no action is required.

ASN1703E The table tableowner.tablenamecannot be registered forchange-capture replication.Reason code reason_code.

Explanation: The table cannot be supported bythe Replication Capture mechanism, as defined.No script is generated. The following values arevalid for the reason code:

0 The table with a z/OS validproc.

1 Existing internal CCD table.

2 Existing CD table.

3 DB2 catalog table (Windows, UNIX,iSeries)

4 The table is already registered.

5 The source for an internal CCD table isnot a registered source.

6 The source is a CD table and cannot beregistered.

7 This source name is a duplicate for thissession.

8 The source is a replication control table.

9 Not one of the source columns qualifiesfor registration.

10 The maximum number of registeredLOB columns has been exceeded for thistable.

11 Structured data types are not supported.

12 The before-image prefix can be only onecharacter.

13 An internal error occurred.

User Response: Check the Reason Code to getthe reason why the table cannot be registered forchange-capture replication. Refer to the DB2Replication Guide and Reference for additionalexplanations and restrictions.

ASN1704E The view viewowner.viewnamecannot be registered. Reason codereason_code.

Explanation: The view cannot be supported bythe Replication Capture mechanism, as defined.No script is generated. The following values arevalid for the reason code:

0 None of the dependent tables for theview are registered.

1 The registered source columns on whichthe view is dependent are notregistered.

2 The view is on an internal ccd.

3 The view is already registered.


4 The view has an ’OUTER JOIN’ syntax.

5 The view includes more than one tableor view column with a function, and nocorrelation is provided in the viewdefinition for each table.

6 The view contains a reference to anaggregate function.

7 The view contains a subselect/subquery.

8 The view contains a reference to anotherview.

9 The view has an UNION.

10 No correlation is provided for thecolumn.

11 The base table does not have the schemaname.

12 The base table does not exist.

13 The view contains Table Expression asTable.

14 The dependent table does not exist.

15 A view on view cannot be registered.

16 The given source object is not a view.

17 This source view is a duplicate for thissession.

18 The view definition cannot besupported.

19 The view has an asterisk (*) instead of aspecific column name in the viewdefinition.

20 The view contains the join of a CCDand a non-CCD table.

User Response: Check the Reason Code to getthe reason why the view cannot be registered.Refer to the DB2 Replication Guide andReference for additional explanations andrestrictions.

ASN1705E The change data object,objectowner.objectname already existsin the server.

Explanation: The change data table or viewcannot be used for the current source to beregistered, because it already exists at theCapture server. No script is generated.

User Response: Provide a different name for thechange data object.

ASN1706W A column column_name is added toa registered sourcesourceowner.sourcename. Theregistered source maintains anInternal CCD table. The newcolumn has to be first added tothe CCD table subscriptionmember before adding to anyexisting or not-yet existingsubscription member.

Explanation: If the new column is needed independent subscription sets, you first have toadd the column to the internal CCD subscriptionmember before adding the column to anysubscription member needed.

User Response: Provide a different name for thechange data object.

ASN1707W The Replication action AlterRegistration forsourceowner.sourcename is not ineffect until a Capture REINITcommand is issued at the Captureserver.

Explanation: The registered source issuccessfully updated. However, the Captureprogram does not recognize the correspondingcaptureschema.IBMSNAP_REGISTER tableupdates until a REINIT command forces it to doso. A script is generated. A Capture command isrequired afterwards for the effect of the script tobe in action.

User Response: To make the changes effectiveimmediately:

1. Run the generated script.


2. Issue a REINIT of the appropriate Captureprogram, for the appropriate Capture schema.

ASN1708E The table, view or nicknameobjectowner.objectname is not aReplication registered source.

Explanation: The Replication object specifiedabove is not defined in the replication controltables. No script is generated.

User Response: Ensure that the object iscorrectly specified in the command and it exists.

ASN1709W Associated subscription sets willnot be valid after the registeredsource sourceowner.sourcename isdropped.

Explanation: Subscription members rely on theunderlying source registrations that define thesource member. If you drop a registered sourcetable, the dependent source members of asubscription set are no longer valid. Thesubscription sets that are associated with thespecified registration source can be found in thecaptureserver.IBMSNAP_PRUNCNTL table at theCapture control server, where theSOURCE_OWNER and SOURCE_TABLEcorrespond to the registered source that isdropped. The appropriate Apply control serverand subscription set names are columns in theIBMSNAP_PRUNCNTL table. The associatedsubscription sets fail if Apply is running. A scriptis generated.

User Response: Deactivate or drop thedependent subscription sets before running thescript, if the registered source has dependentsubscription sets.

ASN1710W Dependent view registeredsources will not be valid after theregistered sourcesourceowner.sourcetable is dropped.

Explanation: View registrations rely on theunderlying registration of the tables that makeup the view definition. If you drop a registeredsource table, you invalidate any view registrationthat is based on the table. The views that might

be affected can be found in thecaptureserver.IBMSNAP_REGISTER table at theCapture server, where thePHYS_CHANGE_OWNER andPHYS_CHANGE_TABLE are the same as theCD_OWNER and CD_TABLE of the registeredsource that is dropped. The associatedsubscription sets, which depend on the viewregistrations, fail, if Apply is running. A script isgenerated.

User Response: Deactivate or drop theappropriate subscription sets, or viewregistrations, before running the script, if theregistered source has dependent viewregistrations.

ASN1711W The source sourceowner.sourcenameis still active so dropping it willresult in a Capture failure.

Explanation: An active registration has aSYNCHPOINT value that is not null in itscaptureschema.IBMSNAP_REGISTER table.When the Capture program started, it expectedall active registrations to always exist and bevalid. So the Capture program needs to besignaled that a registered source was droppedbecause the drop action invalidates theregistration information. Failure to provide thatinformation to the Capture program causes theCapture program to fail. A script is generated,but is NOT ready to run.

User Response:

1. Deactivate the appropriate registration (viathe Replication Center GUI, or by issuing theSTOP signal and a command type of CMD).

2. Wait for a SIGNAL_STATE of Complete inthe captureschema.IBMSNAP_SIGNAL table.

3. Run the script that drops the registration.

ASN1712E The table, view, or nicknameobjectowner.objectname is not a validReplication registered source.Reason code reason_code.

Explanation: Inconsistent information wasfound for this registered source in the Captureserver control tables. No script is generated.


User Response: Drop the registered source andcreate the registration again.

ASN1713E The registered sourcesourceowner.sourcename cannot bedeactivated. Reason codereason_code.

Explanation: The following values are valid forreason code:

0 The source is registered as a FULLREFRESH and therefore cannot bedeactivated.

1 The source is a CCD and CCDregistrations cannot be deactivated.

2 The source is a view and viewregistrations cannot be deactivated.


ASN1714E The registered sourcesourceowner.sourcename cannot bealtered. Reason code reason_code.


0 The CD table for this source has RRNcolumn (iSeries only). The RRN columnmust be the last column in the table, sothe source cannot be altered.

1 The source is a view, and viewregistrations cannot be altered.

2 The source is registered for full refreshand cannot be altered.

3 The source table column does not matchthe column being altered.

4 The column is a LOB, DATALINK, orROWID data type and does not qualifyfor a before-image value.

5 The before-image column value cannotbe null.

6 An after-image value has not beenregistered for the given column.

7 The before-image prefix cannot beupdated if it is used with an existingregistered source.

8 The use of the current before-imageprefix makes one of the columnsambiguous in this registered source.

9 The before-image prefix can be only onecharacter.

10 An internal error occurred.


ASN1715E The Replication action ended inerror. The native OS/400 messageis as400native_message.

Explanation: An error was encountered whileissuing the appropriate command on the OS/400operating system or iSeries servers. No script isgenerated.

User Response: Refer to the OS/400 ConsoleLog for more detailed error information.

ASN1716W The Replication action ended witha warning. The native OS/400message is as400native_message.

Explanation: A warning was encountered whileissuing the appropriate command on the OS/400operating system or iSeries server. A script isgenerated.

User Response: Refer to the iSeries Console Logfor more detailed warning information.

ASN1717I The Replication action ended withan Informational Clause. Thenative OS/400 message isas400native_message.

Explanation: An informational message wasencountered while issuing the appropriatecommand on the OS/400 operating system oriSeries server. A script is generated.



ASN1718E The nicknamenicknameowner.nickname cannot beregistered. Reason code reasoncode.

Explanation: The nickname is not supported bythe replication capture mechanism, as defined.No script is generated. The following values arevalid for the reason code:

0 The internal CCD table (your cd table)already exist.

1 The nickname is on the native catalogtable.

2 The nickname is already registered.

3 A federated registration expects anickname as a source to be registered

4 No columns are eligible for the Captureprogram.

5 The provided nickname is a duplicatefrom an earlier registration, but thecorresponding script has not beenexecuted.

6 A federated registration supports onlyuser tables.

7 A federated registration supports onlynoncondensed and noncomplete CCDtables.

8 The CCD nickname provided is aduplicate of a CCD nickname from anearlier registration, but the script forthat registration has not yet beenexecuted.

User Response: Check the reason code todetermine why the nickname cannot beregistered. See the online help for additionalexplanations or restrictions.

ASN1719W The non-IBM triggers that weredefined for registered sourcenicknameowner.nickname will bedropped. Any additional logiclater provided by users in thesetriggers will be lost.

Explanation: Dropping a registered sourceimplies dropping all the objects that were created

during the source registration, regardless of laterupdates. A script is generated.

User Response: Copy the trigger logic beforedropping the registered source, if needed.

ASN1720E Change Data table information forthe source nicknamenicknameowner.nickname is notfound in thecaptureschema.IBMSNAP_REGISTERtable.

Explanation: A row is found in thecaptureschema.IBMSNAP_REGISTER table forthe given source nickname but the CCD tableinformation for that source is missing. TheChange data table information is required todrop the replication definitions. A script is notgenerated.

User Response: Please make sure the correctsource name is given and call the action again.

ASN1722W The view view_owner.viewname willbe registered as full refresh,because all the base tables of thisview are registered as full refresh.

Explanation: The view must be registered asfull refresh, because the base tables of this vieware registered as full refresh only or are notregistered replication sources.


ASN1723W The view viewowner.viewname willbe registered for change-capturereplication, because one or morebase tables from this view areregistered for change-capturereplication.

Explanation: The view must be registered forchange-capture replication, because the basetables of this view are registered forchange-capture replication.



ASN1724E The name of the object that youare creating on the non-DB2relational server is identical to theobjectowner.objectname of typeobjecttype.

Explanation: The object that you specifiedcannot be created, because there is an existingobject with the same type and same name on thenon-DB2 relational server.

User Response: Provide a unique name for theobject, and reissue the Replication task.

ASN1725W The trigger namedtriggerowner.trigger_name alreadyexists on the remote tableremoteowner.remotetablename. Youmust not run the generated scriptuntil you have determined how tomerge the contents of the existingtrigger with the generated triggerdefinition.

Explanation: An trigger with this name alreadyexists on the remote table in the non-DB2relational database. The RDBMS might notindicate a conflict and might subsequentlyoverwrite your existing trigger if you run theCREATE TRIGGER statement in the generatedscript. Or the RDBMS might return a SQL errorindicating that the object already exists.Generated trigger names cannot be customized,because customized triggers cannot be droppedwhen the registration is dropped.

User Response: First, determine how to mergethe pre-existing triggers with the generatedtriggers. Then, either create your own script tomerge your existing logic with the trigger logicthat is generated by the replication tool, orupdate the script that is generated by thereplication tool to include your existing triggerdefinitions.

ASN1726W The trigger namedtriggerowner.trigname does not existin the remote table owner.tablenameon the remote serverrmtservername.

Explanation: The trigger does not exist on theremote database. The trigger might have beendropped.


ASN1727I The registered sourceregistered_source is deactivated.

Explanation: The specified registered source hasalready been deactivated.


ASN1728W The CCSIDUnicode_ASCII_EBCDIC of thechange data (CD) tablecdowner.cdname for the source tablesourceowner.sourcetable does notmatch the CCSIDUnicode_ASCII_EBCDIC of theIBMSNAP_UOW table for thecapture schema capture_schema.

Explanation: For the given capture schema, theApply program will join the IBMSNAP_UOWtable and the CD table of the given source if thecolumn JOIN_UOW_CD in theASN.IBMNSNAP_MEMBR table is set to Y. Thiscolumn contains Y if the target type of theassociated subscription–set member is not usercopy, or if any columns of the IBMSNAP_UOWtable are used in the WHERE clause of thesubscription–set member. If the Apply programjoins tables with different encoding schemes, anerror will occur. For more information aboutencoding schemes, refer to Appendix B of theReplication Guide and Reference.

User Response: For subscription members thatwill use this registration, define the target tablewith a type of user copy and do not use anyIBMSNAP_UOW columns in the WHERE clause.


ASN1729E The registration for the nicknamenicknameowner.nickname cannot bedropped. The reason code isreasoncode.

Explanation: The registration for this nicknamecannot be dropped. No script is generated. Thefollowing value is valid for the reason code:

0 The specified nickname is a duplicate ofa nickname included with a priorregistration drop. However, the scriptfor that registration drop has not yetbeen executed.

User Response: Review the reason codeexplanation, and refer to the DB2 ReplicationGuide and Reference for additional explanationsand restrictions.

ASN1800E The subscription set set_namealready exists for the Applyqualifier apply_qual, Who’s OnFirst whos_onfirst, at the Applycontrol server server_alias.

Explanation: There can only be one subscriptionset with the same name, for a given Applyqualifier and Apply control server. No script isgenerated.

User Response: Create a new set name, or addnew members to the existing set.

ASN1801E The statement numberstatement_number is associatedwith a statement string lengthstatement_stringlength that exceedsthe maximum statement length forthe Apply qualifier apply_qual, theset name set_name, who’s on firstvalue whos_onfirst, at the Applycontrol server server_alias.

Explanation: The length of the statementexceeds the allowed limit (1024 in V8). No scriptis generated.

User Response: Rework the statement string sothat its length is less than the allowed limits.

ASN1802W The Replication subscriptionsource member is defined withRECAPTURE=’N’. All changes tothe replica target will not bepropagated to the other replicatargets.

Explanation: In an update-anywhere scenario,changes made in one target replica will not berecaptured at the source when RECAPTURE=’N’.If there is more than one target replica thatsubscribes to the same source, then the changesmade to one target replica will not be reflected inthe other replica targets.

User Response: If you want the changespropagated to the other replica targets, setRECAPTURE=’Y’.

ASN1803I There exist orphan_statementsReplication subscription setstatements from a previouslydefined subscription set that waslater dropped. These orphanstatements are not dropped for thesubscription set, for the providedApply qualifier, at the providedApply control server.

Explanation: A previous subscription set wasdropped, without dropping all its appropriatestatements. A script is generated for the newsubscription set which shares the same name asthe previous subscription set that was dropped.The previous subscription Statements are notdropped.

User Response: Issue a Drop SubscriptionStatements to delete the orphan statements.

ASN1804I The Replication subscription setMAX_SYNCH_MINUTESmaxsynch_minutes is not within theallowed range for the providedsubscription set and Applyqualifier, at the provided Applycontrol server. The Replicationdefault value is used instead.

Explanation: The valid range for this column is0 to 999.


User Response: No action is required if thedefault value of 30 minutes is acceptable.

ASN1805I The Replication subscription setCOMMIT_COUNTcommitcount_value is not within theallowed range for the providedsubscription set and Applyqualifier, at the provided Applycontrol server. The Replicationdefault value is used instead.

Explanation: The valid range for this column is0 to 999.

User Response: No action is required if thedefault value of 0 minutes is acceptable.

ASN1806E The replication action ended inerror for the Apply qualifierapply_qualifier, subscription-setname set_name, who’s on firstvalue whos_on_first, sourcemember sourceowner.sourcetable,source view qualifiersource_view_qual, target membertargetowner.targettable. Thesubscription-set member cannotbe added to the providedsubscription set. Reason codereason_code.

Explanation: The subscription set would be notbe valid if the member were added. No script isgenerated. The following values are valid for thereason code:

0 The subscription set has reached itsmaximum limit for members.

1 The source member for the Captureschema is not the same as thesubscription set for the Capture schema.

2 The iSeries source member is not thesame as the subscription set journal.

3 The condensed table member structureis incompatible with the other memberstructures.

4 The source member does not supportchange-capture replication, but the

target member relies on change-capture.The target structure is either a CCD orreplica table, but the source has no CDtable.

5 The source member is not a completetable.

6 The target member definition expectsthe existence of the target table, but thetarget table does not exist.

7 The target member definition asks forcreation of the target table, but thetarget table already exists.

8 The set contains only full refreshsupported target tables, but the newmember supports change-capturereplication.

10 The set contains only target tablessupported by change-capturereplication, but the new membersupports full refresh only.

11 Replica rule: if target member is areplica, the source member can be eithera replica or a user table.

12 The target structure is not supported forthis operating system.

13 The target structure is a CCD, which isset as a registration source(autoregistration), but the structure isnot complete

14 The source member is not registered.

15 The source member columns havecolumn definitions, but the target typeis not an aggregate.

16 At least one of the excluded targetcolumns from the subscription set isneither nullable nor NOT NULL withdefaults.

17 The target member is a view that cannotbe updated.

18 The subscription-set member alreadyexists.


19 Unable to find a target column orexpression with a valid mapping to theregistered source.

20 Multiple effective sources have beenfound but have not been definedconsistently.

21 The external CCD table is noncondensedand contains either DataLink or LOBcolumns.

22 The source member journal library orjournal name does not match.

23 The remote journal name is not valid.

24 The journal name or library is not valid.

25 A replica table with remote journaling isnot allowed.

26 An internal CCD table already exists forthe specified registered source table.

27 The source and target servers must bethe same for internal CCD tables.

28 The internal CCD table must benoncomplete.

29 The source table is remotely journalledand contains LOBs or DATALINKcolumns.

30 No related information exists in theIBMSNAP_PRUNCNTL table.

31 No related information exists in theIBMSNAP_PRUNE_SET table.

32 An internal CCD table with a view as asource is not allowed.

User Response: Based on the reason code,either create the new member in a differentsubscription set or create a new subscription setfor the new member.

ASN1807I The replication subscriptionmember is added to the providedsubscription set and Applyqualifier, at the provided Applycontrol server with aninformational clause. Reason codereason_code.

Explanation: This message is for yourinformation only, and no action is required. Ascript is generated. The following values arevalid for reason code:

0 The new set results in a mixture ofreplica and read-only target members.

1 The subscription set supportstransaction commit counts, but thetarget member does not qualify fortransaction processing.

2 At least one member has a targetmember that is a CCD table, but not allmembers have a target member CCDtable. Different generations of tables arecontained in the same set.

3 The target member is a non-condensed,non-complete CCD table, without extracolumns from IBMSNAP. This targettable is essentially the same as the CDtable.

User Response: Review the reason codes in theexplanation, and respond with the followingoptions:

0 Consider keeping all the replica tablesin one set, and the read-only tables inanother.

1 Consider keeping all the target typesthat support transaction processing inthe same set, and other tables in anotherset.

2 To maintain a consistent age of dataacross sets, consider keeping all theCCD target tables, which are part of thesame generation, in the same set. Also,consider keeping all non-CCD targettables in a different set. The second set


depends on the data being in the firstset, as, for example in the middle-tierstage.

3 Consider whether you need the CCDtarget table.

ASN1808E The Replication action ended inerror for Apply qualifierapply_qualifier, set name set_name,Who’s On First whos_on_first,source membersourceowner.sourcetable, source viewqualifier source_view_qual, targetmember targetowner.targettable. Thesubscription target memberexpects its index key columns tobe updated but at least one indexkey does not have itsbefore-image column registered inthe subscription source member.

Explanation: The target table allows its indexkeys to be updated (PRIMARY_KEY_CHG = ’Y’).To support this requirement, the Apply programneeds to access the before-image columns of theindex keys. So these before-image columns mustexist in the Change Data table for the sourcemember. If they do not exist, the Apply programfails. A script is not generated.

User Response: For each column of thesubscription target index:

v Check if the before-image column for thatcolumn is already registered in the sourcemember, at the Capture server.

v If not, register the appropriate before-imagecolumn.

ASN1809W The Replication action expects asubscription index key columns tobe updated but the subscriptionmember will be added to thesubscription set without allowingupdates to the target index keycolumns. Reason code reason_code.

Explanation: In the cases listed above, thePRIMARY_KEY_CHG settings are meaningless.A script is generated that was updated with

Replication definitions that overrideuser-provided definitions. The following valuesare valid for reason code:

0 The target table type CCD:PRIMARY_KEY_CHG is not valid.

1 The value of theCHG_UPD_TO_DEL_INS in theIBMSNAP_REGISTER table is set to ’Y’.

2 The target table is not condensed.


ASN1810W The Replication subscriptionsource member is defined on thesource server with DB2Referential Integrity constraints,but the subscription targetmember is a Replica that does notpreserve these constraints.

Explanation: Referential integrity constraints atthe target table are not enforced by DB2 at thereplica site. This might not be the intendedbehavior at the replica site. A script is generated,and the script might not be ready to execute.

User Response: Update the generated script toinclude the appropriate referential constraints atthe target, if needed.

ASN1811W The index definition for the targetsubscription member cannotguarantee proper uniqueness atthe target. Reason codereason_code.

Explanation: The Apply program relies on theunique index definition to correctly update anddelete rows in the target table, for some targettypes. If the provided index does not guaranteeuniqueness, the Apply program will have somerework. Understand your application to ensurethat this will not be the case. The followingvalues are valid for reason code:

0 At least one column is generated by anSQL function, which does not guaranteethe uniqueness of the index.


1 In a unique index, nullable columns arenot generated by SQL functions.

User Response: For each column of thesubscription target index:

v Check if the column type in the Apply controlserver ASN.IBMSNAP_SUBS_COLS,COL_TYPE, is ’F’

v If so, redefine the index column expression notto include a SQL expression, or remove thatcolumn from the index key(ASN.IBMSNAP_SUBS_COLS, IS_KEY columnis set to ’N’).

ASN1812E The Replication action ended inerror for Apply qualifierapply_qualifier, set name set_name,who’s on first value whos_on_first,source membersourceowner.sourcetable, source viewqualifier source_view_qual, targetmember targetowner.targettable. Thesubscription target membercannot be added because therequired target key is not valid.Reason code reason_code.

Explanation: Target members that require aunique index are target types of point-in-time,user copy, and replica tables, and condensedCCDs. If these targets do not have a uniqueindex, the Apply program fails. A script is notgenerated. The following values are valid forreason code:

0 The target table does not already existbut the target key information could notbe derived from the source table.

1 The target key information cannot befound nor derived, and the RRN is notdefined for the CD table (iSeries only).

2 The target table or view already existsbut the required target key informationis missing.

3 The target table or view already existsbut the target key information isincompatible with the existingpartitioning key information.

User Response: Define a valid target key. Takethe specific actions for the following reasoncodes:

0 Create the appropriate unique index onthe source table so that it can be used toderive the replication suggested index.

2 Provide the required target keyinformation.

3 Refer to the SQL Reference for the DB2rules on partitioning indexes. Forexample, the key that you providedmight not include the requiredpartitioning key.

ASN1813I The Replication subscriptionsource member is defined on thesource server with some DB2constraints, but the subscriptiontarget member does not preservethese constraints. Reason codereason_code.

Explanation: Constraints at the source table arenot be enforced by DB2 if they are not specifiedduring the target member definition. This mightnot be the intended behavior at the replica tableserver. A script is generated that might not beready to execute. Constraints are described in thefollowing valid values for reason code:

0 At least one NOT NULL WITHDEFAULT clause in the target member.

1 Partitioned table space.

User Response: Update the generated script toinclude the appropriate DB2 constraints at thetarget, if needed.

ASN1814E The target column column_name ofdata type datatype cannot be addedto subscription target membertableowner.tablename. Reason Codereason_code.

Explanation: The subscription member fails thesubscription column checks. A script is notgenerated. The following values are valid forreason code:


0 The column data type is not supportedby Replication. Data types that are notsupported by DB2 issue messageASN1648E.

1 The target data type is incompatiblewith the corresponding source datatype.

2 The column is not found in the sourcetable registration.

3 The column type is not supported forfederated targets.

4 The target column is a LOB. Themaximum number of LOB columns isexceeded for the target member.

5 The source column contains SQLcolumn function, but the target memberstructure is neither base aggregate norchange aggregate.

6 The target table type is replica, and thesource column is a LOB column.

7 The target table type is replica, andsource column is DATALINK value. Butthe CONFLICT_LEVEL > 0.

8 A noncondensed CCD target table withLOB columns is not supported.

9 The column is not in the existing targettable.

User Response: Review the reason code in theexplanation and respond as follows:

0 Change the data type to one that issupported.

1 Make sure the target data type matchesthe source data type.

2 Register the column of the source table.

3 Choose a valid data type that issupported for federated targets.

4 Make sure the number of LOB columnsat the target member does not exceedthe allowable limit.

5 Change either the source columnexpression or the target table structure.

6 Remove the LOB column for the replicatarget from the subscription member.

7 Remove the DATALINK column fromthe subscription member if the replicaneeds a conflict level greater than 0.Otherwise, change the replica conflictlevel.

8 Remove the LOB columns.

9 Verify the column name.

ASN1815E The Replication action ended inerror. The subscription setset_name for Apply qualifierapply_qual, Who’s On Firstwhos_on_first is to be dropped ifempty, but at least one memberexists for this set. Thesubscription set cannot bedropped.

Explanation: The subscription set is notdropped because at least one member exists inthe ASN.IBMSNAP_SUBS_MEMBR at theprovided Apply control server, for the providedApply qualifier of the particular subscription set.A script is not generated.

User Response: Drop the subscription membersthat still exist, and then drop the subscription set.Alternatively, issue the Drop Subscription Set task,with no requirement for the subscription set tobe empty.

ASN1816W The Replication subscription setcontains at least one member thatwill be dropped once thesubscription set is dropped.

Explanation: When a subscription set isdropped successfully, all the set members areautomatically dropped also.



ASN1818W The Replication subscriptionmember is updated with newsubscription Where Clausepredicates. Previous predicatesalready exist for the subscriptionmember. They will be overwrittenby the new predicate information.

Explanation: The specified member alreadycontains a predicate. The new predicateoverwrites the old one. A script is generated.

User Response: Provide the complete predicateclause for the replication task. You might need toupdate the predicate clause if does not containall of the existing predicate clause.

ASN1819W The Replication subscription setis disabled successfully. Notehowever that disabling asubscription set has a directimpact to the Capture pruninglogic of all source members forthat subscription set.

Explanation: The Capture pruning logic doesnot prune any CD table until the dependentsubscription members have been populated bythe Apply program. A script is generated. Itmight need to be updated, if the disabling of thesubscription set is not the ideal choice, anddropping the subscription set is a better option.See below.

User Response: If the subscription set is goingto be disabled for a considerable amount of timethat the pruning process of the CD tables will beimpacted, or if the impact to the CD tables forthe dependent registered sources will impactdramatically the Capture program and theCapture server CD tables, then considerdropping the subscription set and creating itagain later, instead of simply disabling it.Alternatively, deactivate the appropriateregistrations.

ASN1820E The Replication string forsubscription set set_name, applyqualifier apply_qual, Who’s OnFirst whos_on_first contains DB2syntax that is not valid. The stringtype is string_type, string text isstring_text and SQL Message issql_message.

Explanation: The specified string is not a valid.A script is not generated.

User Response: Please correct the appropriateobject syntax and issue the Replication taskagain.

ASN1821W Dependent subscription sets willno longer be valid after theexisting subscription set isdropped, if this subscription setcontains target members that areregistered sources at its targetserver.

Explanation: The dependent subscriptions relyon their source member tables to exist. If thesesource members are maintained as replicationtargets, and these targets are dropped, then theApply program fails when it processes thedependent subscription sets. Dependentsubscription sets might be impacted if thecaptureserver.IBMSNAP_PRUNCNTL table at thetarget server contains SOURCE_OWNER orSOURCE_TABLE rows for which these values arethe target tables being dropped. A script isgenerated.

User Response: Deactivate or drop thedependent subscription sets before running thescript, if required.


ASN1822E The Replication action ended inerror for Apply qualifierapply_qual, set name set_name,source membersourceowner.sourcename, targetmember targetowner.targetname. Theprovided subscription memberdoes not exist for the providedsubscription set.

Explanation: The specified member cannot befound in the ASN.IBMSNAP_SUBS_MEMBR forthe provided Apply qualifier at the providedApply control server.

User Response: Make sure the Apply qualifier,set name, member name, and control serverprovided are correct.

ASN1823E The subscription set set_name doesnot exist for the Apply qualifierapply_qual, Who’s On Firstwhos_onfirst, at the Apply controlserver server_alias.

Explanation: The specified subscription setcannot be found in theASN.IBMSNAP_SUBS_SET for the providedApply qualifier at the provided Apply controlserver.

User Response: Make sure the Apply qualifier,set name, member name, and control serverprovided are correct.

ASN1824W The Replication subscription setwas updated with aCOMMIT_COUNT of 0.

Explanation: The source is a view of multipletables, and the commit count is null for the set.A Commit count of 0 is enforced for the set.


ASN1825W The Replication action to drop amember did not drop the view.

Explanation: Even though the request wasmade to drop the view the action was notcompleted as requested.

User Response: You need to manually drop theview.

ASN1826W The Capture schemacapture_schema does not exist at theprovided source server.

Explanation: Please make sure the Captureschema exists before adding any members to thesubscription set.

User Response: Create the Capture servercontrol tables at the source server with theCapture schema specified.

ASN1827W The column target_columnname ofthe target member target_memberdoes not preserve a DB2 columnattribute of the correspondingcolumn source_columnname of thesource member source_member.Reason Code reason_code.

Explanation: A DB2 column attribute of thesource column differs from the correspondingtarget column. The following values are valid forreason code:

1

The source column is nullable and the targetcolumn is not nullable.

2

The source column is not nullable and the targetcolumn is nullable.

3

The source column has a default value and thetarget column has none.

4

The target column has a default value and thesource column has none.


User Response: If the reason code is 1, thencheck whether there are null values in the sourcecolumn that will be applied to the target column.If necessary, change the target column toNULLABLE. Alternatively, update the generatedscript to include the appropriate DB2 attributesat the target, if needed.

ASN1828E The Replication action ended inerror for Apply qualifierapply_qual, set name set_name,source membersourceowner.sourcename, targetmember targetowner.targetname.When the subscription targetserver is a non-IBM target server,either the action is not supportedor is supported with restrictions.Reason Code is reason_code.

Explanation: These are current restrictions. Noscript is generated. The following values arevalid for reason code:

0 Not supported.

1 Supported for the following target tablestructures: point-in-time, CCD, usercopy.


ASN1829I A valid nicknamenicknameowner.nickname is foundfor the subscription target table.Column data type mapping rulesare enforced. The nickname isused as is.

Explanation: An existing target nickname wasfound in the federated database that is valid forthis subscription (the column data type mappingchecks are valid); however, there is no check tovalidate the existence of the target table on thenon-DB2 relational database server.

User Response: Make sure that the remote tableexists for the provided nickname. Otherwise, theApply program fails.

ASN1830E The Replication action ended inerror for the Apply qualifierapply_qualifier, subscription setset_name, whos on first value ofwhos_on_first, source membersourceowner.sourcetable, source viewqualifier source_view_qual, targetmember targetowner.targettable, andpredicate of predicate. TheSubscription-set member cannotbe added to this subscription set.The reason code is reason_code.

Explanation: The subscription-set member isinvalid, and no script is generated. A possiblereason code is:

0 The predicate references columns fromnon-existing CD or UOW tables.

User Response: Verify the accuracy of thespecified predicate, and refer to thedocumentation on advanced change predicatefeatures.

ASN1831E The Replication action ended inerror. No subscription statementsexist for the subscription setset_name for the Apply qualifierapply_qual, with a whos on firstvalue of whos_onfirst, at the Applycontrol server control_server.

Explanation: No subscription statements existfor the specified subscription-set name with thisApply qualifier.

User Response: Verify that the specifiedsubscription-set name under this Apply qualifiercontains subscription-set statements.

ASN1832W A column named column_namealready exists in theASN.IBMSNAP_SUBS_COLScontrol table.

Explanation: The specified column alreadyexists in the ASN.IBMSNAP_SUBS_COLS table.



ASN1833E The CCSIDUnicode_ASCII_EBCDIC of thechange data (CD) tablecdowner.cdname for the source tablesourceowner.sourcetable does notmatch the CCSIDUnicode_ASCII_EBCDIC of theIBMSNAP_UOW table for thecapture schema capture_schema.The provided subscriptionmember definition would requirea join of these two tables.

Explanation: For the given capture schema, theApply program will join the IBMSNAP_UOWtable and the CD table of the given source ifeither the target type of the associatedsubscription-set member is not user copy, or ifany columns of the IBMSNAP_UOW table areused in the WHERE clause of thesubscription-set member. If the Apply programprocesses such a subscription-set memberdefined with the given source table and captureschema by joining the CD table of the sourcetable with the IBMSNAP_UOW table, an errorwill occur because of the different encodingschemes of the tables. For more informationabout encoding schemes, refer to Appendix B ofthe Replication Guide and Reference.

User Response: You can either

v select a target type of user copy and do notuse columns of the IBMSNAP_UOW table inthe WHERE clause of the subscriptionmember, or

v register the source using a different captureschema and create the CD table in a tablespacewith the same encoding scheme as those of theIBMSNAP_UOW table of the new captureschema.

ASN1834W The default target capture schemaof ’ASN’ will be used for thesubscription set.

Explanation: The subscription set requires atarget Capture schema, and the default value of’ASN’ is used.

User Response: No action is required if the

default is appropriate for the target CaptureSchema column in this subscription set.

ASN1835W The target column column_name ofdata type datatype has been addedto the subscription-set membertarget tableowner.tablename, but thecorresponding source columncolumn_name of data type datatypecan contain data that is notapplicable to the target column.Reason code reason_code.

Explanation: The source column definition doesnot exactly match with the target columndefinition. Therefore, if the data that is selectedfrom the source by the Apply program is notappropriate for the target column, the Applyprogram might fail or might modify the sourcedata (by truncating it). Note: If your applicationdoes not generate data that will make the Applyprogram fail, there is no problem with thedefinition mismatch.

The following values are valid for the reasoncode:

1

The target column length is less than theresolved source column expression.

2

The target column scale is less than the resolvedsource column expression.

3

The target column precision is less than theresolved source column expression.

4

The target and source column data types arecompatible only for certain source values.

User Response: If possible, change thedefinitions at the target site to be compatiblewith the source definitions. (This is usuallydriven by the applications that run at the targetsite.)

If you must keep the definition mismatch(because you have a specific reason why the


target definitions must be different than thesource definitions), review your applications toensure that the definition mismatch will notcause a run-time problem.

ASN1836W The target table owner.name willnot be dropped because it isregistered as a source under theCapture schema schemaname.

Explanation: The target table is registered as asource under the specified Capture schema. If thetable is dropped, the registration will no longerbe valid.

User Response: Drop the registration for thetable, and then drop the table.

ASN1837W The DB2 target tableowner.tablenameis not dropped.

Explanation: The target table is a replica or anexternal Consistent Change Data table (CCD)and it is also registered at the target server so itmay be the source for dependent targets. Thetable cannot be dropped automatically.

User Response: Drop the registered source forthe replica or external CCD table. Then,manually drop the DB2 target table or delete thereplica or external CCD subscription member.The deletion of the member will drop the DB2target table.

ASN1900E The table or viewobjectowner.objectname cannot bepromoted to the new server.Reason code reason_code.

Explanation: The following values are valid forreason code:

0 The table type on this operating systemis not supported for promote request.

1 The source server operating systemrequired for the promote needs to matchthe target server operating system.

2 The table or view does not exist.

User Response: Review the reason code in theexplanation and respond as follows:

0 This message is for your informationonly, and no action is required.

1 Current restriction.

2 Verify that the table or view exists onthe source server operating system.

ASN1901E The registered sourcesourceowner.sourcename cannot bepromoted for Capture schemacaptureschema at Capture servercapture_server. Reason codereason_code.


0 The table or view is not a registeredsource.

1 The registered source is a replica table.

2 The registered source is on DB2 foriSeries but has a remote journal.

3 The table or view has already beenpromoted.

4 A view on a view is not supported bythe replication promote registrationfunction.

User Response: Review the reason code in theexplanation, and respond as follows:

0 The table or view name that youspecified in the IBMSNAP_REGISTERtable contained no entries for thespecified Capture schema. The table orview registration cannot be promotedfor this particular Capture schema.

1 The table you specified is of type replica(with a SOURCE_STRUCTURE columnvalue of 7) in thecaptureschema.IBMSNAP_REGISTERtable. The table cannot be promoted as aregistered source. A replica can bepromoted only within the context of asubscription set to ensure that properdefinitions are maintained between thesource user table and the replica target.

2 The registered source is maintained on


DB2 for iSeries with a remote journal,which can be promoted only with SQLscript.

ASN1902W Make sure that the schemas existon the promoted Capture serverbefore running the script. TheReplication definitions will beincomplete if the object does notexist at the promoted Captureserver.

Explanation: The promote tasks allows you toprovide a new Capture server and new Captureserver schemas. However, the promote tasks donot connect to the new Capture server to verifythe names and existence of the Capture serverand schemas. You must verify this informationbefore running the script to ensure that the scriptexecutes successfully.

User Response: To generate the requiredobjects, run the appropriate SQL prior to runningthe script.

ASN1903W The object objectowner.objectnamedoes not exist on the promotedApply control server, yet somepromoted objects depend on itsexistence. Failure to create thisobject will result in incompleteReplication definitions atpromoted Apply control server.Reason code reason_code.

Explanation: Since the promote tasks allow youto provide a new Apply control server name, thetasks detect whether some required objects existto ensure proper execution of the generatedscript. A script is generated, but is not ready torun. The following values are valid for reasoncode:

0 The Apply control server control tablesdo not exist.

1 The registration information for allsource members of a promoted set.

User Response: To generate the requiredobjects, run the appropriate SQL prior to runningthe script.

ASN1904I The Replication subscriptionmember is promoted successfullyfor the provided Apply qualifier,at the provided Apply controlserver. Reason code reason_code.

Explanation: This message is for yourinformation only; no action is required. A scriptis generated that might need some updatesbefore being executed. The following values arevalid for reason code:

0 The source member structure isincompatible with the target memberstructure.

1 The target member is a replica (replica1)that is also the source member ofanother replica (replica2.) TheDISABLE_FORWARDING value for theregistration row of replica2 does notallow updates from the user table to bereplicated at replica2.

2 The source member is a user table thatis also the source member of more thanone replica (replica1 and replica2). TheDISABLE_FORWARDING value for theregistration row of the user table doesnot allow updates at replica1 to bereplicated at replica2, and vice-versa.

User Response: Review the reason code in theexplanation, and respond as follows:

0 Check theASN.IBMSNAP_SUBS_MEMBR table,TARGET_STRUCTURE column. Thevalue in the column should becompatible with the correspondingsource membercaptureschema.IBMSNAP_REGISTERtable, SOURCE_STRUCTURE column.

1, 2 Update the values, if needed.


ASN1905W The Capture server alias and theCapture schema name on both thehost system and new system arethe same. The generatedreplication definitions cannotwork if run on the host system.

Explanation: The promote task detected that theCapture server alias and the Capture schemaname are the same on both on the host and newsystem. The generated SQL script must bemodified, or it will fail when executed.

User Response: Take one of the followingactions: 1) Run the same task with differentCapture server alias and Capture schema namevalues for the host or new system. 2) Or, changethe Capture server alias or Capture schema namein the generated script.

ASN1950E ASNCLP : An unexpected tokentoken_name was found. Validtokens include list_of_tokens.

Explanation: The command was entered withincorrect syntax.

User Response: Check the documentation toverify your command syntax.

ASN1951E ASNCLP : The command wasentered with profile profile_namethat is not valid.

Explanation: A profile must exist before it canbe used in a command.

User Response: Issue the corresponding SETPROFILE command, and then re-enter thecommand that failed.

ASN1952E ASNCLP : The programencountered an internal error.

Explanation: The Replication command lineprocessor encountered an unrecoverable errorcondition.

User Response: Obtain the log file with theerror, and contact IBM Software Support.

ASN1953I ASNCLP : Command completed.

Explanation: All commands of this ASNCLPsession completed successfully. Please note thatsome individual commands in this session mayhave produced errors, warnings, or informationalmessages.

User Response: Check the ASNCLP log file forany errors, warnings, or informational messagesproduced by the commands in this session.

ASN1954E ASNCLP : Command failed.

Explanation: At least one command in theASNCLP session failed, and processing stopped.

User Response: Look in the ASNCLP log file todiagnosis the error. Then fix the error, and trythe command again.

ASN1955I ASNCLP : The program will usethe following files:capture_script_file_name for theCapture SQL script,control_script_file_name for thecontrol SQL script,target_script_file_name for the targetSQL script, and log_file_name forthe log file.

Explanation: The ASNCLP session generatedinformation in the specified files.


ASN1956I ASNCLP : The program nowgenerates the script for action:action_name.

Explanation: All input for this command hasbeen successfully parsed, and the command thatgenerates the script is now invoked.



ASN1957E ASNCLP : The value value for theinput parameter input_parameter isincorrect. The reason code isreason_code.

Explanation: The value of the input parameteris incorrect. The following values are validreason codes:

1 The input parameter is a character valuebut should be a numeric value.

2 The input parameter is a numeric valuebut should be a character value.

3 The command line processor cannotaccess the specified file.

User Response: Check the reason code, andprovide a valid input parameter value.

ASN1976E ASNPWD : The specifieddatabase alias db_alias_namealready exists in the password filepassword_file_name.

Explanation: The key that you specified alreadyexists in the password file.

User Response: Enter this command againusing the MODIFY parameter instead of theADD parameter.

ASN1977E ASNPWD : The value of the inputparameter parameter_name ismissing.

Explanation: The above input parameter mustbe specified.

User Response: Invoke the utility again using avalid input parameter value.

ASN1978E ASNPWD : The value of the inputparameter parameter_name is toolong.

Explanation: The asnpwd command supports amaximum of eight characters for the length ofthe database alias and a maximum of 128characters for the length of both the user ID andthe password. The specific lengths of the user IDand the password are dependent upon the

operating system that you are using.

User Response: Invoke the API using an inputparameter with a valid length.

ASN1979E ASNPWD : The programencountered an unexpected tokentoken_name. Expected tokensinclude list_of_tokens.

Explanation: The command was entered withincorrect syntax.

User Response: Check the documentation toverify your command syntax.

ASN1980E ASNPWD : The program did notcomplete successfully becausereason.

Explanation: The asnpwd commandencountered system problems as indicated in themessage.

User Response: Take action based on theinformation in the message. Enter the commandagain after fixing the error.

ASN1981I ASNPWD : The programcompleted successfully usingpassword file password_file_name.

Explanation: The asnpwd command completedsuccessfully.


ASN1982E ASNPWD : The specifieddatabase alias db_alias_name doesnot exist in the password filepassword_file_name.

Explanation: The key that you specified withthe MODIFY or DELETE parameter does notexist in the password file.

User Response: Enter the command again usingthe ADD parameter.


ASN1983E ASNPWD : The program cannotfind the password filepassword_file_name.

Explanation: No password file was found.

User Response: Verify that the password fileexists in the specified path. If you are using thePassword Management utility for the first time,use the INIT parameter.

ASN1984E ASNPWD : The program cannotbe initialized because thepassword file password_file_namealready exists.

Explanation: The password file already exists inthe specified path.

User Response: Verify that the password filehas been deleted. Then retry the command.

ASN1985E ASNPWD : The programencountered an internal errorwhen using the password filepassword_file_name.

Explanation: The operating system produced anunexpected error when trying to access thepassword file. No information about this error isavailable. However, this error might haveoccurred if the password file was manuallyedited causing the format of the file to change.

User Response: Retry the command. If theproblem persists, use the INIT parameter tocreate a new password file.

ASN5101I MONITOR monitor_qualifier. TheReplication Alert Monitorprogram started successfully.

Explanation: This message appears after asuccessful start of the Replication Alert Monitorprogram.


ASN5102I MONITOR monitor_qualifier. TheReplication Alert Monitorprogram initialized successfullyand is monitoringnumber-of-alert-conditions alertconditions.

Explanation: The Replication Alert Monitorprogram successfully started.


ASN5103I MONITOR monitor_qualifier. TheReplication Alert Monitorprogram re-initialized successfullyand is monitoringnumber-of-alert-conditions alertconditions.

Explanation: The Replication Alert Monitorprogram successfully re-initialized.


ASN5104W MONITOR monitor_qualifier.number-of-alert-conditions alertconditions were ignored.

Explanation: The Replication Alert Monitorprogram initialized or re-initialized. Some alertconditions that are not valid might be excludedas noted in previously issued messages.

User Response: Check theIBMSNAP_CAPTRACE table for messages aboutexcluded alert conditions.

ASN5107I MONITOR monitor_qualifier. TheReplication Alert Monitorprogram stopped.

Explanation: The Replication Alert Monitorprogram terminated.



ASN5110I MONITOR monitor_qualifier. TheAlert Monitor programencountered an SQL error. TheERRCODE is error_code. TheSQLSTATE is sqlstate. TheSQLCODE is sqlcode. TheSQLERRM is sqlerrm. TheSQLERRP is sqlerrp. The servername is server_name. The tablename is table_name.


User Response: Refer to your database messagereference for an explanation of the SQL errorcode.

ASN5111I MONITOR monitor_qualifier.number-of-rows rows were prunedfrom the table schema.table-name.

Explanation: The Replication Alert Monitorprogram pruned rows from theIBMSNAP_ALERTS or theIBMSNAP_MONTRACE table.


ASN5112E MONITOR monitor_qualifier. Thepruning program failed with aSQLCODE of sqlcode when theprogram pruned the tableschema.table-name.

Explanation: The pruning program failed whenexecuting a pruning operation.

User Response: Read the corresponding actionregarding this SQLCODE, and correct the error.

ASN5116E MONITOR monitor_qualifier. Themonitor qualifier does not existon the monitor control servermonitor-server.

Explanation: The Replication Alert Monitorprogram cannot find the monitor qualifier on thismonitor control server.

User Response: Verify that the monitor qualifier

name used with the monitor_qual parameter iscorrect.

ASN5117E MONITOR monitor_qualifier. Thereare no valid Alert Conditions forthis monitor qualifier on MonitorServer monitor_server.

Explanation: The Replication Alert Monitorprogram cannot find any alert conditions for thismonitor qualifier.

User Response: Verify that the monitor qualifiername used with the monitor_qual parameter iscorrect, and check that the alert conditions areenabled. Also, check any previously issuedmessages.

ASN5118E MONITOR monitor_qualifier. Theprogram cannot connect to themonitor control server server_name.The SQLCODE is sqlcode, and theSQLSTATE is sqlstate.

Explanation: The Monitor program tried toconnect to the monitor control server and failedwith the corresponding SQLCODE.

User Response: Read the corresponding actionfor this SQLCODE, and correct the error.

ASN5119E MONITOR monitor_qualifier. Theprogram cannot connect to theserver server_name. The SQLCODEis sqlcode, and the SQLSTATE issqlstate.

Explanation: An SQL CONNECT statementfailed when the Monitor program tried toconnect to the monitored Capture or Applycontrol server.

User Response: Read the corresponding actionregarding this SQLCODE, and correct the error.


ASN5121E MONITOR monitor_qualifier. Acontact does not exist for the alertcondition with a component ofcomponent, a server of server, aschema or qualifier ofschema_or_qualifier, and a conditionname of condition.

Explanation: The specified contact does notexist in the IBMSNAP_CONTACTS table for thisalert condition.

User Response: Verify the contact information,and correct the alert condition.

ASN5122E MONITOR monitor_qualifier. Thecontact group group-name does notexist or is empty. The componentis component, the server is server,the schema or qualifier isschema_or_qualifier, and thecondition name is condition.

Explanation: The contact group specified in analert condition does not have correspondingcontacts in the IBMSNAP_CONTACTGRP tableor does not exist in theIBMSNAP_CONTACTGRP table. A contact groupcannot be empty.

User Response: Verify the contacts for thisgroup, and correct the alert condition.

ASN5123E MONITOR monitor_qualifier. Thetable table-name is not found. TheCapture control server iscapture-server. The schema isschema. The condition name iscondition-name.

Explanation: The Replication Alert Monitorprogram cannot find a table when attempting tomonitor a condition on the Capture controlserver.

User Response: Verify that the table exists onthe Capture control server, or correct the alertcondition.

ASN5124E MONITOR monitor_qualifier. Thetable table-name is not found. TheApply control server isapply-control-server. The Applyqualifier is apply-qualifier. Thesubscription-set name is set-name.The condition name iscondition-name.

Explanation: The Replication Alert Monitorprogram cannot find a table when attempting tomonitor a condition on the Apply control server.

User Response: Verify that the table exists onthe Apply control server, or correct the alertcondition.

ASN5125E MONITOR monitor_qualifier. TheApply qualifier apply-qualifier orthe subscription set set-name is notfound.

Explanation: The Replication Alert Monitorprogram cannot find the Apply qualifier or thesubscription set when attempting to monitor acondition on the Apply control server.

User Response: Verify that the Apply qualifierand the subscription set exist on the Applycontrol server, or correct the alert condition.

ASN5126E MONITOR monitor_qualifier. Thereis an error sending a notification.The return code is rc.

Explanation: When an alert notification wasattempted, the ASNMAIL exit returned an error.The reasons for the error may include:

1 SMTP protocol failed. Verify the addressof your e-mail server with youradministrator.

2 SMPT socket failed. Verify theconfiguration of your e-mail server orclient.

3 The e-mail address is not valid. Verifythe e-mail address.

4 Software error.

99 ASNMAIL exit not found.


User Response: For return codes 1 and 2, verifythe configuration of your e-mail server andclient. For return code 3, check whether thee-mail address is correct. For return code 99,verify if the ASNMAIL exit properly installed.

ASN5127E MONITOR monitor_qualifier. Aninvalid value value exists in thecolumn column-name of the tabletable-name.

Explanation: This message indicates that theReplication Alert Monitor program found acolumn with a value that is not valid duringprogram initialization.

User Response: Verify the values of the columndefinitions in the specified table.

ASN5129I MONITOR monitor_qualifier. TheReplication Alert Monitor onserver server-name reports ane-mail alert.

Explanation: The Replication Alert Monitorprogram sent an e-mail alert.


ASN5130I MONITOR monitor_qualifier.capture_message. The Capturecontrol server is capture-server. Theschema is schema. The monitorcontrol server is monitor-server.

Explanation: The Replication Alert Monitorprogram retrieved a Capture program messagefrom the IBMSNAP_CAPTRACE table whenprocessing CAPTURE_ERRORS orCAPTURE_WARNINGS conditions.

User Response: Read the Capture programmessage, and take appropriate action. Also,check any errors or warnings from the Capturecontrol server.

ASN5131I MONITOR monitor_qualifier.apply_message. The Apply controlserver is apply-server. The Applyqualifier is apply-qualifier. Themonitor control server ismonitor-server.

Explanation: The Replication Alert Monitorprogram retrieved an Apply program messagefrom the IBMSNAP_APPLYTRAIL or theIBMSNAP_APPLYTRACE table when processingAPPLY_SUBSFAILING, APPLY_ERRORS, orAPPLY_WARNINGS alert conditions.

User Response: Read the Apply programmessage, and take appropriate action. Also,check any errors or warnings from the Applycontrol server.

ASN5133I MONITOR monitor_qualifier. Thefollowing alert message_number hasoccurred number_of_times times inthe last number_of_minutesminutes. The notification for thisalert will be suspended.

Explanation: This message is issued after analert has been detected the number of timesspecified in theMAX_NOTIFICATIONS_PER_ALERT parameter(the default is 3) for the number of minutesspecified in theMAX_NOTIFICATIONS_MINUTES parameter(the default is 60 minutes).


ASN5134I MONITOR monitor_qualifier. Alertsissued.

Explanation: The text of this message appearsin the subject line of the e-mail alerts sent by theReplication Alert Monitor program.



ASN5135W MONITOR monitor_qualifier. Toomany alerts number_of_alerts forserver server_name betweenlower_bound_time andupper_bound_time, schema orqualifier schema_qual_name,condition name condition_name.

Explanation: The Alert Monitor reached themaximum of alerts allowed for a monitor cycle(1024), or memory can not be allocated for them.The Alert Monitor will send the notifications andwill update the Monitor control server and willreconnect to the server starting in the nextcondition. Some alerts for the specified alertcondition might not be sent and inserted in theMonitor control server.

User Response: You should verify the specifiedalert condition directly in the server to check ifalerts were lost.

ASN5136W MONITOR monitor_qualifier. Therehas been an error calling DAScomponent. The return code is rcfor server server_name for schemaor qualifier schema_qual_name andcondition name condition_name.

Explanation: While processing the conditionname for the given server, the DAS componentreturned an error.

User Response: Verify that DAS is runningproperly in both the client and the remote server.

ASN5150W MONITOR monitor_qualifier. TheCapture program is not running.The Capture control server iscapture_server, and the schema isschema.

Explanation: The alert conditionCAPTURE_STATUS indicates that the Captureprogram is not running.

User Response: Verify the status of the Captureprogram on the specified Capture control server.

ASN5151W MONITOR monitor_qualifier. Theelapsed time since the last commitof Capture program exceeds thethreshold value. The Capturecontrol server is capture-server. Theschema is schema. The last committime is time. The threshold isminutes minutes.

Explanation: The CAPTURE_LASTCOMMITalert condition detects that the differencebetween the current timestamp value and thevalue of the MAX_COMMIT_TIME column inthe IBMSNAP_RESTART table is greater than thethreshold value of this alert condition asspecified by the PARM_INT column value in theIBMSNAP_CONDITIONS table.

User Response: Check the Capture controlserver, and determine the reason for the commitdelay.

ASN5152W MONITOR monitor_qualifier. Thecurrent Capture latency exceedsthe threshold value. The Capturecontrol server is capture_server. Theschema is schema. The Capturelatency is latency seconds. Thethreshold is threshold seconds.

Explanation: The CAPTURE_CLATENCY alertcondition detects that the difference between theCURR_COMMIT_TIME and theMAX_COMMIT_TIME column values in theIBMSNAP_RESTART table is greater than thethreshold value of this alert condition asspecified by the PARM_INT column value in theIBMSNAP_CONDITIONS table.

User Response: Check the Capture controlserver, and determine the reason for the Capturelatency.


ASN5153W MONITOR monitor_qualifier. Thehistoric Capture latency exceedsthe threshold value. The Capturecontrol server is capture_server. Theschema is schema. The Capturelatency is latency seconds. Thethreshold is threshold seconds.

Explanation: The CAPTURE_HLATENCY alertcondition detects that the difference between theMONITOR_TIME and the SYNCHTIME columnvalues in the IBMSNAP_CAPMON table isgreater than the threshold value of this alertcondition as specified by the PARM_INT columnvalue in the IBMSNAP_CONDITIONS table. Thislatency value might correspond to past latencybut might help track latency trends over time.

User Response: Check the Capture controlserver, and determine the reason for the Capturelatency.

ASN5154W MONITOR monitor_qualifier. Thememory used by the Captureprogram exceeds the thresholdvalue. The Capture control serveris capture_server. The schema isschema. The amount of memoryused is memory megabytes. Thethreshold is threshold megabytes.

Explanation: The CAPTURE_MEMORY alertcondition detects that the value of theCURRENT_MEMORY column in theIBMSNAP_CAPMON table is greater than thethreshold value of this alert condition asspecified by the PARM_INT column value in theIBMSNAP_CONDITIONS table.

User Response: Check the Capture controlserver, and determine the reason for theexcessive memory usage. Modify thememory_limit parameter of the Captureprogram, if necessary.

ASN5160W MONITOR monitor_qualifier. TheApply program is not running.The Apply control server isapply_server, and the Applyqualifier is apply-qualifier.

Explanation: The APPLY_STATUS alertcondition detects that the Apply program is notrunning.

User Response: Verify the status of the Applyprogram at the specified Apply control server.

ASN5161W MONITOR monitor_qualifier. Thesubscription set is inactive and isin an error state. The Applycontrol server isapply-control-server. The Applyqualifier is apply-qualifier. Thename of the subscription set isset-name. The who’s on first valueis wof, and the last success valueis timestamp.

Explanation: The APPLY_SUBSINACT alertcondition detects that the subscription set isinactive and that the status is not equal to zero(0).

User Response: If the subscription set should beactive, check this subscription set on the Applycontrol server.

ASN5162W MONITOR monitor_qualifier. A fullrefresh occurred. The Applycontrol server isapply-control-server. The Applyqualifier is apply-qualifier. Thename of the subscription set isset-name. The who’s on first valueis wof, and the target table istable-name.

Explanation: The APPLY_FULLREFRESH alertcondition detects that the target table wasrefreshed during the past monitor cycle.

User Response: If the full refresh was in error,verify the cause of the full refresh for thisspecified target table.


ASN5163W MONITOR monitor_qualifier. Thesubscription is delayed beyondthe threshold. The Apply controlserver is apply-control-server. TheApply qualifier is apply-qualifier.The name of the subscription setis set-name. The who’s on firstvalue is wof. The time delayed istime, and the threshold is thresholdseconds.

Explanation: The APPLY_SUBSDELAYED alertcondition detected a subscription set thatcomplies with the following conditions:CURRENT TIMESTAMP minus LASTRUN isgreater than the threshold.

User Response: Check any previous messagesto see if this subscription set has an error and toverify that the Apply program is running.

ASN5164W MONITOR monitor_qualifier. Therows reworked in a subscriptionexceeds the threshold. The Applycontrol server isapply-control-server. The Applyqualifier is apply-qualifier. Thename of the subscription set isset-name. The who’s on first valueis wof. The number of reworkedrows is rows, and the threshold isthreshold rows.

Explanation: The APPLY_REWORKED alertcondition detects a subscription set with aSET_REWORKED column value (in theIBMSNAP_APPLYTRAIL table) that exceeds thespecified threshold.

User Response: Verify the reason why thisnumber of rows have been reworked.

ASN5165W MONITOR monitor_qualifier.Transactions have been rejected inthe subscription set. The Applycontrol server isapply-control-server. The Applyqualifier is apply-qualifier. Thename of the subscription set isset-name. The who’s on first valueis wof. The number of rejectedtransactions is transactions.

Explanation: The APPLY_TRANSREJECT alertcondition detects rejected transactions for thissubscription set.

User Response: Verify the reason why thesetransactions were rejected.

ASN5166W MONITOR monitor_qualifier. Amanual full refresh is required.The Apply control server isapply-control-server. The Applyqualifier is apply-qualifier. Thename of the subscription set isset-name.

Explanation: A full refresh is needed for thespecified subscription set.

User Response: Verify the reason why a fullrefresh is required.

ASN5167W MONITOR monitor_qualifier.End-to-end latency exceeded thethreshold. The Apply controlserver is apply-control-server. TheApply qualifier is apply-qualifier.The name of the subscription setis set-name End-to-End latency islatency seconds, and the thresholdis threshold seconds.

Explanation: The APPLY_LATENCY alertcondition detects that the end-to-end latency ofthis subscription set is greater than the thresholdvalue of this alert condition as specified by thePARM_INT column value in theIBMSNAP_CONDITIONS table.

User Response: Check the Apply control serverto determine the reason for this excessive


end-to-end latency value.

ASN5190W MONITOR monitor_qualifier. Astored procedure failed with anSQLCODE of sqlcode and with anSQL message of sql_message.

Explanation: A user-defined alert condition(implemented as an DB2 stored procedure)returned a nonzero SQLCODE value.

User Response: The action depends on theimplementation of the stored procedure. If themessage indicates an abnormal condition, contactyour DBA.

ASN5191W MONITOR monitor_qualifier.message

Explanation: This message appears when auser-defined alert condition issues a warningmessage.

User Response: Read the issued message, andtake appropriate action.

ASN5192E MONITOR monitor_qualifier.message

Explanation: This message appears when auser-defined alert condition issues an errormessage.

User Response: Read the issued message, andtake appropriate action.

ASN5200E ASNSCRT: The replicationprocess type is a requiredparameter and must be specifiedwhen invoking the asnscrtcommand.

Explanation: The asnscrt command wasinvoked without a specified replication processtype.

User Response: Enter the command again witha replication process type of -C, -A, or -M.

ASN5201E ASNSCRT: The database instanceis a required parameter and mustbe specified when invoking theasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified database instance.

User Response: Enter the command again witha database instance name.

ASN5202E ASNSCRT: A replication processpath is a required parameter andmust be specified when invokingthe asnscrt command.

Explanation: The asnscrt command wasinvoked without a specified replication processpath.

User Response: Enter the command again witha path to the asncap, asnapply, or asnmoncommand.

ASN5203E ASNSCRT: The Capture server isa required parameter and must bespecified when invoking thisasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified Capture controlserver.

User Response: Enter the command again witha Capture control server name.

ASN5204E ASNSCRT: The Apply controlserver is a required parameter andmust be specified when invokingthis asnscrt command.

Explanation: The asnscrt command wasinvoked without a specified Apply control server.

User Response: Enter the command again withan Apply control server name.


ASN5205E ASNSCRT: The Apply qualifier isa required parameter and must bespecified when invoking thisasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified Apply qualifier.

User Response: Enter the command again withan Apply qualifier.

ASN5206E ASNSCRT: The monitor controlserver is a required parameter andmust be specified when invokingthis asnscrt command.

Explanation: The asnscrt command wasinvoked without a specified monitor controlserver.

User Response: Enter the command again witha monitor control server name.

ASN5207E ASNSCRT: The monitor qualifieris a required parameter and mustbe specified when invoking thisasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified monitor qualifier.

User Response: Enter the command again witha monitor qualifier.

ASN5208I ASNSCRT: The replication serviceservice_name was createdsuccessfully.

Explanation: The asnscrt command successfullycreated the specified service.


ASN5209I ASNSCRT: The replication serviceservice_name started successfully.

Explanation: The asnscrt command successfullystarted the specified service.


ASN5210E ASNSCRT: The replication serviceservice_name was not created,because the display name alreadyexists (either as a service name oras another display name) in theservice control manager database.

Explanation: The asnscrt command cannotcreate the specified service, because the displayname already exists as another service name ordisplay name in the service control managerdatabase.

User Response: Go to service control managerdatabase, and remove the service with theduplicate service or display name. Then re-enterthe command.

ASN5211E ASNSCRT: The replication serviceservice_name was not created,because the specified servicename is not valid.

Explanation: The asnscrt command cannotcreate the specified service, because the systemAPI returned an error code indicating that theservice name is incorrect. The specified servicemight contain special characters in the instancename, database name, or schema name. Specialcharacters are not allowed in the service name.

User Response: Change the instance name,database name, or schema name if possible. Thenre-enter the command.

ASN5212E ASNSCRT: The replication serviceservice_name was not created,because the specified servicename already exists.

Explanation: The asnscrt command cannotcreate the specified service, because anotherservice with the same service name already existsin the service control manager.

User Response: Remove the existing servicewith the same service name. Then re-enter thecommand.


ASN5213E ASNSCRT: The replication serviceservice_name was not started,because the service binary filecould not be found.

Explanation: The asnscrt command cannot startthe specified service, because the correspondingasncap, asnapply, or asnmon command cannot beinvoked using the system path specified by thePATH environment variable. If the fully qualifiedpath is provided, the asnscrt command cannotfind the asncap, asnapply or asnmon commandin that path.

User Response: Make sure the specified path iscorrect. Then re-enter the command.

ASN5214E ASNSCRT: The replication serviceservice_name did not start, becausean instance of the service isalready running.

Explanation: The asnscrt command cannot startthe specified service, because the service isalready running.


ASN5215E ASNSCRT: The replication serviceservice_name did not start, becausethe service depends on a DB2instance service that does not existor has been marked for deletion.

Explanation: The asnscrt command cannot startthe specified service, because the correspondingDB2 instance service does not exist or has beendeleted.

User Response: Verify that the correspondingDB2 instance service exists in the service controlmanager. Then re-enter the command.

ASN5216E ASNSCRT: The replication serviceservice_name did not start, becausethis service depends on anotherservice that failed to start.

Explanation: The asnscrt command cannot startthe specified service, because the corresponding

DB2 instance service failed to start.

User Response: Verify that the correspondingDB2 instance service started in the service controlmanager. Then re-enter the command.

ASN5217E ASNSCRT: The replication serviceservice_name did not start, becausethe service is disabled.

Explanation: The asnscrt command cannot startthe specified service, because the service hasbeen disabled in the service control manager.

User Response: Verify that the service startuptype is set to either automatic or manual in theservice control manager. Then re-enter thecommand.

ASN5218E ASNSCRT: The replication serviceservice_name did not start, becausethe service cannot log on. Thiserror occurs if the service startsfrom an account that does nothave the proper ″Log on as aservice″ access right.

Explanation: The asnscrt command cannot startthe specified service, because the correspondingDB2 instance service cannot log on.

User Response: Go to service control manager,and locate the specified service. Verify that theprovided account name and passwords arecorrect. Then re-enter the command.

ASN5219E ASNSCRT: The replication serviceservice_name was not created,because the service is marked fordeletion.

Explanation: The asnscrt command cannotcreate the specified service, because the servicehas been deleted.

User Response: Close the service controlmanager window. Then re-enter the command.


ASN5220E ASNSDROP: The service name isa required parameter and must bespecified when invoking theasnsdrop command.

Explanation: The asnsdrop command wasinvoked without a specified service name.

User Response: Re-enter the command with aservice name.

ASN5221I ASNSDROP: The serviceservice_name has been successfullyremoved.

Explanation: The asnsdrop command wasinvoked with a specified service name.


ASN5222E ASNSDROP: The replicationservice service_name cannot beremoved, because the requestedaccess is denied.

Explanation: The asnsdrop command cannotremove the specified service name, because theuser does not have the appropriate permission toremove it.

User Response: Verify that the current user haspermission to log on to the corresponding DB2instance. Then re-enter the command.

ASN5223E ASNSDROP: The replicationservice service_name cannot beremoved, because the specifiedservice name is not valid.

Explanation: The asnsdrop command cannotremove the specified service name, because theservice name contains illegal special characters.

User Response: Go to service control manager,and locate the specified service. Verify that theservice name is valid, and re-enter the command.

ASN5224E ASNSDROP: The replicationservice service_name cannot beremoved, because the specifiedservice does not exist.

Explanation: The asnsdrop command cannotremove the specified service name, because theservice name does not exist in the service controlmanager.

User Response: Go to service control manager,and locate the specified service. Verify that theservice name is correct, and re-enter thecommand.

ASN5225E ASNSDROP: The replicationservice service_name cannot bestopped, because other runningservices are dependent on it. Theservice_name is not removed.

Explanation: The asnsdrop command cannotremove the specified service, because otherservices that are dependent on this specifiedservice are currently running.

User Response: Go to service control manager,and stop all services that are dependent on thisspecified service. Then re-enter the command.

ASN5226E ASNSDROP: The replicationservice service_name cannot beremoved, because the system isshutting down.

Explanation: The asnsdrop command cannotremove the specified service, because theoperating system is shutting down.

User Response: Enter the command again aftersystem restarts.

ASN5227I ASNSDROP: The replicationservice service_name cannot beremoved, because it has alreadybeen marked for deletion.

Explanation: The asnsdrop command cannotremove the specified service, because thespecified service has already been deleted.

User Response: This message is for your


information only, and no action is required.

ASN5228E pgmname : The command cannotcommand_action the replicationservice service_name, because thesystem call API_func_namereturned an unexpected error codeerror_code.

Explanation: The asnscrt and asndropcommands make system calls in order to workwith the services. The specified system callreturned an unexpected error code that preventsthe given command from completing therequested action.

User Response: Enter the command again. Thiserror code might indicate only a temporarysystem condition. For further information aboutthe error code, check your operating systemdocumentation.

ASN5229E ASNSCRT: The account is arequired parameter and must bespecified when invoking theasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified account name forthe corresponding DB2 instance.

User Response: Re-enter the command with anaccount name for the corresponding DB2instance.

ASN5230E ASNSCRT: The password is arequired parameter and must bespecified when invoking theasnscrt command.

Explanation: The asnscrt command wasinvoked without a specified password for thecorresponding DB2 instance.

User Response: Re-enter the command with thepassword for the corresponding DB2 instance.

ASN5231E ASNSCRT: The replication serviceservice_name was not created,because the account namespecified on the accountparameter does not exist.

Explanation: The asnscrt command wasinvoked with an unknown account name for thecorresponding DB2 instance.

User Response: Verify that the providedaccount name and passwords are correct. Thenre-enter the command.

ASN5232E ASNSCRT: The requiredparameter path was not specified.

Explanation: When started as a service, areplication command must contain a pathspecified by the path keyword that is specific tothe command (capture_path for asncap,apply_path for asnapply, and monitor_path forasnmon). If the path keyword is specified, theservice is registered if no errors occur.

If the path keyword is not specified, the asnscrtcommand retrieves the DB2 global registryprofile variable DB2PATH. If this variablecontains a non-null value, the asnscrt commandadds the appropriate path keyword to thecommand using the value of DB2PATH. If thisvariable is not set, the asnscrt command cannotregister the service.

User Response: Enter the command again afteryou specify the appropriate path keyword orafter you define the DB2 global registry profilevariable DB2PATH.

ASN5233E ASNSCRT: The replication serviceservice_name was not created,because the specified databaseinstance database_instance does notexist.

Explanation: The asnscrt command cannotcreate the specified service because the specifieddatabase instance does not exist in the system.

User Response: Verify that the specifieddatabase instance exists in the system. Thenreissue the command.



Chapter 4. CCA Messages

This section contains the Configuration Assistant Interface (CCA) messages.The messages are listed in numeric sequence.

CCA1001I Use alphanumeric characters only.The first character cannot benumeric.

CCA1002I Use decimal numbers, 0 to 9, only.

CCA1003I No DB2 system was found on thenetwork.

CCA1004I No DB2 instance was found onthe selected system(s).

CCA1005I No DB2 database was found onthe selected instance(s).

CCA2001W No files were found matching thefile pattern specified.

Explanation: A request was made to read fromfiles matching the specified file pattern. No fileswere found matching the pattern.

User Response: Correct the file patternspecified and retry the operation.

CCA2002W An error was encountered whileupdating the TCP/IP services file.

Explanation: An attempt to add a service nameand port number to the TCP/IP services filefailed or Network Information Services is beingused and only the local services file wasupdated. The port number was used to catalogthe node instead of the service name.

User Response: To use the service name insteadof the port number in the node directory entry,the node must be manually uncataloged andthen recataloged using the service name. The

services file must also be updated manually. IfNetwork Information Services (NIS) is beingused, the local services file may have beenupdated but the NIS server must be updatedmanually. In this case, the node was alsocataloged using the port number.

CCA2003W The Discover request did notreturn data for one or more DB2systems.

Explanation: The discover request did notreturn data for one or more of the requested DB2systems. One of the following may haveoccurred:

v The Administration Server to which thediscover request was sent has not been started.

v An error occurred attempting to perform thediscover request.

v The DB2 system to which the discover requestwas sent is not configured for discovery.

User Response: Verify that the DB2 system towhich the discover request was sent is enabledfor discovery. If enabled for discovery, ensurethat the Administration Server on the DB2system is running.

CCA2004W The nname value specified is notunique.

Explanation: The nname value specified isalready being used by another NetBIOSapplication on the network.

User Response: Select ’YES’ to use the specifiednname or ’NO’ to cancel the request. If ’YES’ isselected, any application using the existingnname will be affected.


CCA2005W The socket number specified isnot unique.

Explanation: The socket number specified isbeing used by another DB2 instance on theworkstation.

User Response: Select ’YES’ to use the specifiedsocket or ’NO’ to cancel the request. If ’YES’ isselected, any application using the existingsocket number will be affected.

CCA2006W An entry already exists in theTCP/IP services file for the servicename and port number specified.

Explanation: An entry already exists in theTCP/IP services file for the service name andport number specified. Another application maybe using the entry.

User Response: Select ’YES’ to use the existingentry or ’NO’ to cancel the request. If ’YES’ isselected, any application using the existing entrywill be affected.

CCA2007W The port number specified isbeing used with a differentservice name.

Explanation: The TCP/IP services file containsan entry that uses the port number specified butthe associated service name does not match theservice name specified.

User Response: Select ’YES’ to use the specifiedservice name and port number or ’NO’ to cancelthe request. If ’YES’ is selected, a new entry willbe added to the services file. Any applicationsusing the entry with the existing port numbermay be affected.

CCA2008W The service name specified isbeing used with a different portnumber.

Explanation: The TCP/IP services file containsan entry that uses the service name specified butthe associated port number does not match theport number specified.

User Response: Select ’YES’ to use the specified

service name and port number or ’NO’ to cancelthe request. If ’YES’ is selected, the existing entryin the services file, using the service name, willbe updated to use the port number specified.This may affect any applications using theexisting entry.

CCA2009W The request was canceled by theuser.

Explanation: The request was canceled by theuser.

User Response: None.

CCA2010W An attempt to update the APPCstack failed.

Explanation: An attempt to add the TransactionProgram name to the APPC stack failed.

User Response: The APPC stack must bemanually updated. If the Transaction Programname is not added to the stack, remoteconnections to the server will not be possible.

CCA2011W An attempt to add the servicename and port number to theTCP/IP services file failed.

Explanation: An attempt to add the servicename and port number to the TCP/IP servicesfile failed. The database manager configurationfile has been updated with the service namespecified.

User Response: The service name and portnumber must be manually added to the TCP/IPservice file. If the entry is not added to theservices file, remote connections to the serverwill not be possible.

CCA2012W The Discover request did not findany DB2 systems.

Explanation: A request to search the networkfor DB2 systems completed successfully but noDB2 systems were found. Following is a list ofpossible reasons why no DB2 systems werefound:


v Search discovery was not enabled on any DB2systems (that is, in the DBM configuration fileof the administration server on the DB2system, DISCOVER = SEARCH was notspecified).

v The DB2 system was not set up with theappropriate discovery protocol for the client tofind it (that is, DISCOVER_COMM on theadministration server does not contain aprotocol that matches one specified forDISCOVER_COMM on the client).

v The DB2 system is on the other side of arouter or bridge, and the routers and bridgeson the network were configured such that thediscovery packet was filtered out and notpassed on.

User Response: Following is a list of possibleactions to take in order for discovery to find DB2systems:

v Set DISCOVER = SEARCH in the DBMconfiguration file of the administration serveron all DB2 systems that you wish to be found.

v Set DISCOVER_COMM for the administrationserver to include the protocol that the clientwill use to issue a discover request (that is, setDISCOVER_COMM to include at least one ofthe protocols specified in DISCOVER_COMMon the client).

v Have the network administrator reconfigurethe router or bridge to allow discovery packets(for the specified protocol) to be passedthrough.

CCA2013W Remote database cataloged usingAPPC but the stack was notconfigured.

Explanation: A request to catalog a databaseresulted in a node being cataloged that uses theAPPC protocol. The node was cataloged usingthe symbolic destination name which wasretrieved from the profile specified. The APPCstack was not configured because there wasinsufficient information in the profile toconfigure the stack or APPC was not detected onthe DB2 system. It was not possible to use adifferent protocol because no other matchingprotocol was detected on the client.

User Response: If APPC is not installed on theclient, uncatalog the database and recatalog thedatabase manually using a protocol that isavailable on both the client and server. If APPCis installed, configure the stack if it has notalready been configured.

CCA2014W The transaction program namespecified is not unique or hasalready been configured.

Explanation: The transaction program namespecified is already being used by another DB2instance or a non DB2 application on this server.

User Response: Select ’YES’ to use the specifiedtransaction program name or ’NO’ to cancel therequest. If ″YES″ is selected, for all applicationsusing the transaction program nameconcurrently, APPC will only be operational forthe first one started. If any new APPC parametervalues have been specified, the APPC stack willbe updated with these values.

CCA2015W The service name and portnumber specified are being usedin different entries in the servicesfile.

Explanation: The TCP/IP services file containsentries that use the service name and portnumber specified but they are not being used inthe same entry.

User Response: Select ’YES’ to use the specifiedservice name and port number or ’NO’ to cancelthe request. If ’YES’ is selected, the existing entryin the services file, using the service name, willbe updated to use the port number specified.This may affect any applications using theexisting entries.

CCA2016W The password will be saved asclear text.

Explanation: The password will be saved asclear text in db2cli.ini file.

User Response: If password security is aconcern, deselect the ’Save password’ check box.

Chapter 4. CCA Messages 125

CCA3000C An internal error has occurred.Reason code reason-code.

Explanation: An unexpected internal error hasoccurred.

User Response: Turn trace on and retry thesteps that caused the error. If the problemreoccurs, save the trace information to a file andcontact IBM Support with the followinginformation:

v Problem description

v Message number

v Reason code

v Trace file

CCA3001N The specified service name andport number conflicts withexisting values in the TCP/IPservices file.

Explanation: The service name and portnumber entered by the user conflicts withexisting values in the TCP/IP services file. Theservice name may already be used with adifferent port number, the port number mayalready be used with a different service name orboth.

User Response: Specify a service name and portnumber that does not conflict with existingentries in the services file.

CCA3002N An I/O error occurred.

Explanation: An error was encountered whileattempting to open, read, change the file positionor close a file.

User Response: If a file name was specified,verify that the file name is valid and that theuser has permission to access the file. Also checkfor any disk and operating system errors.

CCA3003N The format of the file is not valid.

Explanation: An error was encountered whilereading from a file. The format of the file is notvalid. Possible errors include:

v The file contains invalid data.

v The file does not contain expected data.

v The order of the data in the file is incorrect.

User Response: If a file name was specified,and the file has been modified by the user,regenerate the file and retry the operation. If theproblem persists, and the file was not modifiedby the user, or the problem occurred during aDiscover request, turn trace on and retry thesteps that caused the error. If the problemreoccurs, save the trace information to a file andcontact IBM Support with the followinginformation:


v Message number

v Trace file

v File which is causing the error if a file namewas specified

CCA3004N An attempt to allocate memoryfailed.

Explanation: An error was detected whileattempting to allocate memory.

User Response: Terminate other applicationsrunning on the system that may be using largeamounts of memory. If the problem persists, turntrace on and retry the operation. If the problemreoccurs, save the trace information to a file andcontact IBM Support with the followinginformation:


v Message number

v Trace file

CCA3005N An error was encountered whilewriting to a file.

Explanation: An error was detected whilewriting to a profile. The error could also beencountered when updating a host systempassword and errors are being recorded in thefile db2pem.log.

User Response: Verify that the file system onwhich the file resides is not full and is notdamaged. Also check for any operating systemerrors.


CCA3006N No matching communicationprotocol was detected.

Explanation: The database cannot be catalogedbecause none of the protocols available on theclient match any of the protocols available at theserver.

User Response: Ensure that the client andserver have at least one matching communicationprotocol that can be detected on both. If amatching protocol is installed on both the clientand the server, the protocol could not bedetected. In this case, catalog the database andnode manually.

CCA3007N The database alias name specifiedis not valid.

Explanation: The length of the database aliasspecified is not a valid or the alias containsinvalid characters.

User Response: Correct the alias name andresubmit the request.

CCA3009N The application requestor namespecified is not valid.

Explanation: The length of the applicationrequestor name specified is not valid or the namecontains invalid characters.

User Response: Correct the applicationrequestor and resubmit the request.

CCA3010N The length of the parameter valuespecified is not valid.

Explanation: The length of the parameter valuespecified for the application requestor is notvalid.

User Response: Correct the parameter valueand resubmit the request.

CCA3011N The target database namespecified is not valid.

Explanation: The length of the target databasename specified is not valid or the name containsinvalid characters.

User Response: Correct the target databasename and resubmit the request.

CCA3012N Add ODBC data source failed.

Explanation: A request to add an ODBC datasource failed. The error could be caused by anout of memory error, a disk full condition or adisk failure.

User Response: Verify that the disk on whichthe ODBC.INI and DB2CLI.INI files reside is notfull and that the disk is not damaged. Inaddition, if other applications are using largeamounts of memory, terminate the applicationsand retry the operation.

CCA3013N Remove ODBC data source failed.

Explanation: A request to remove an ODBCdata source failed. The error could be caused byan out of memory condition or a disk failure.

User Response: If other applications are usinglarge amounts of memory, terminate theapplications and retry the operation. Also verifythat the disk on which the ODBC.INI andDB2CLI.INI files reside is not damaged.

CCA3014N The bind request cannot beprocessed.

Explanation: The bind request cannot beprocessed because another bind operation isalready in progress.

User Response: Complete or terminate the bindin progress and resubmit the bind request.

CCA3015N The adapter specified is not valid.

Explanation: The adapter specified was notdetected on the DB2 system.

User Response: Specify an adapter that isavailable and resubmit the request.

CCA3016N The nname value specified is notunique.

Explanation: The nname value specified isalready being used by another NetBIOS


application on the network.

User Response: Specify a unique nname andretry the operation.

CCA3017N The path specified for the file isnot valid.

Explanation: An attempt was made to open thespecified file, but the path specified is invalid ordoes not exists.

User Response: Ensure that the path specifiedis valid and the path for the file exists.

CCA3018N The user does not have sufficientauthority to access the file.

Explanation: An attempt was made to accessthe requested file, but the user does not have therequired authority to access the file.

User Response: Ensure that the user has therequired authority to access the file.

CCA3019N The file name specified is adirectory.

Explanation: An attempt to access the filespecified failed because the name specified is adirectory and not a file.

User Response: Specify a valid file name andretry the operation.

CCA3020N An attempt to access the specifiedfile failed because of a shareviolation.

Explanation: An attempt to access the filespecified failed because of a share violation.Another process may have the file opened inexclusive mode.

User Response: The file is currently beingaccessed by another process in exclusive mode.Ensure that no other process is accessing the fileand retry the operation or specify another filename.

CCA3021N An attempt to retrieve, add orremove variable variable-name fromthe DB2 Profile Registry failedwith Return Code return-code.

Explanation: An attempt to retrieve, add orremove the indicated variable from the DB2Profile Registry failed. The return code indicatesthe cause of the problem. The possible returncodes are as follows:

v -2 The specified parameter is invalid

v -3 Insufficient memory to process the request

v -4 Variable not found in the registry

v -7 DB2 Profile Registry is not found on thisDB2 system

v -8 Profile not found for the given instance

v -9 Profile not found for the given node

v -10 UNIX registry file lock time-out

User Response: For return code:

v -2 Ensure that the parameter has beenspecified correctly.

v -3 Terminate other applications using largeamounts of memory and retry the operation.

v -4 Ensure that the variable is set in the DB2Profile Registry.

v -7 Ensure that the DB2 Profile Registry hasbeen created.

v -8 Ensure that the profile has been created forthe instance.

v -9 Ensure that the profile has been created forthe node.

v -10 Ensure that the registry file is not lockedby another process.

CCA3022C An attempt to retrieve the addressof the function procedure-namefrom library library-name failedwith Return code return-code.

Explanation: An attempt to retrieve the addressof a function from the indicated library failed.

User Response: Verify that the correct versionof the library is being used. If the incorrectversion is being used, install the correct version.If the problem persists, turn trace on and retry


the steps that caused the error. If the problemreoccurs, save the trace information to a file andcontact IBM Support with the followinginformation:


v Message number

v Return code

v Trace file

CCA3023C An attempt to load librarylibrary-name failed with Returncode return-code.

Explanation: An attempt to load the indicatedlibrary failed.

User Response: Verify that the path in whichthe library resides is included in the library path.Also ensure that there is enough memoryavailable to load the library. If the problempersists, turn trace on and retry the steps thatcaused the error. If the problem reoccurs, savethe trace information to a file and contact IBMSupport with the following information:


v Message number

v Return code

v Trace file

CCA3024C An attempt to unload librarylibrary-name failed with Returncode return-code.

Explanation: An attempt to unload theindicated library failed.

User Response: Turn trace on and retry thesteps that caused the internal error. If theproblem reoccurs, save the trace information to afile and contact IBM Support with the followinginformation:


v Message number

v Return code

v Trace file

CCA3025N One or more of the IPX/SPXparameters specified is not valid.

Explanation: One or more of the inputparameters is not valid. Following is a list ofpossible errors:

v One or more of the fileserver, objectname andipx_socket parameters is NULL.

v Only the fileserver parameter or objectnameparameter is set to ″*″.

v The fileserver and/or objectname parametersare not set to ″*″ for Windows NT and Solaris.

v The objectname value specified is not unique.

v The ipx_socket value specified is not unique.

v The ipx_socket value specified is not in thevalid range.

v The DB2 system failed to attach to thefileserver specified.

User Response: Verify the following:

v The fileserver, objectname and ipx_socketparameters are not NULL.

v If the value specified for fileserver is ″*″, thevalue for objectname must also be ″*″.

v On Windows NT and Solaris, both fileserverand objectname must be ″*″.

v The value specified for objectname, if not ″*″,is unique for all DB2 instances and IPX/SPXapplications registered at the fileserver.

v The value specified for ipx_socket is uniqueacross all DB2 instances on the DB2 system.

v The value specified for ipx_socket is within thevalid range.

v The fileserver specified exists and that it is upand running.

Correct all errors and retry the operation.

CCA3026N No available NetBIOS adaptersdetected.

Explanation: A NetBIOS adapter was notdetected on the DB2 system. The database cannotbe cataloged.

User Response: Catalog the database and node


manually if an adapter is available on the DB2system.

CCA3027N The port number specified is outof range.

Explanation: The TCP/IP port number specifiedis out of range. The maximum value that can bespecified for the port number if 65534.

User Response: Specify a port number thatdoes not exceed the maximum value and retrythe operation.

CCA3028N The DB2INSTANCE variable isnot valid.

Explanation: The DB2INSTANCE environmentvariable is not set or is set to the AdministrationServer instance. The Configuration Assistantcannot run under the Administration ServerInstance.

User Response: Set the DB2INSTANCE variableto an instance other than the AdministrationServer instance.

CCA3029N Updating of the ODBC datasource settings failed.

Explanation: A request to update the settings ofan ODBC data source failed. The error could becaused by an out of memory error, a disk fullcondition or a disk failure.

User Response: Verify that the disk on whichthe DB2CLI.INI file resides is not full and thatthe disk is not damaged. In addition, if otherapplications are using large amounts of memory,terminate the applications and retry theoperation.

CCA3030N Values missing for configuringAPPC.

Explanation: A request was made to catalog adatabase using APPC or to configure a serverinstance for APPC. The request could not becompleted because one or more parameters werenot specified.

User Response: Ensure that all required

parameters have been specified and retry theoperation.

CCA3031N The APPC stack has not beenconfigured for the databaseselected.

Explanation: The database selected is usingAPPC for the database connection. However, theAPPC stack has not been configured for theconnection.

User Response: Configure the APPC stack forthe database selected.

CCA3051N A protocol protocol interfacefailure has occurred with Returncode return-code.

Explanation: The failure occurred whileattempting to access the protocol interface.

User Response: Verify that the protocol isoperational.

CCA3052N The specified item item-name wasnot found.

Explanation: The specified item name could notbe found in the configuration data.

User Response: Verify that you have specifiedthe item name correctly.

CCA3053N The ODBC DSN specifiedDSN-name is invalid.

Explanation: The ODBC DSN specified is aninvalid name.

User Response: Ensure that you are using validcharacters for the ODBC DSN name.

CCA3054N The ODBC DSN could not beregistered.

Explanation: The ODBC DSN registrationattempt failed.

User Response: Verify that ODBC is installedproperly and is functional.


CCA3055N The specified item item-namealready exists.

Explanation: The specified item name alreadyexists in the configuration data.

User Response: Verify that you have specifiedthe item name correctly. Use a different itemname or delete the old item and resubmit therequest.

CCA3056N The hostname host-name was notfound.

Explanation: The specified hostname could notbe resolved on the network.

User Response: Ensure that the hostname, asspecified, is correct and is a valid hostname onyour network.

CCA3057N The service name service-name wasnot found.

Explanation: The specified service name wasnot found in the local services file.

User Response: Ensure that the service name,as specified, is correct and that there is a validentry for that service name in your local servicesfile.

CCA3058N The local system object is notallowed to be removed.

Explanation: The local system object appears ifthis is a server installation, and does not appearif this is a client installation. You have no directcontrol over the removal of this object because ithas special properties that are required by theserver installation type.


CCA3059N The local system object is notallowed to be changed.

Explanation: The local system object appears ifthis is a server installation, and does not appearif this is a client installation. You have no directcontrol over the changing of this object because it

has special properties that are required by theserver installation type.


CCA3060N The selected system object is notallowed to be changed.

Explanation: The selected system is usingcommunication protocol that is not supported bythe DB2 Administration Tools.


CCA3061N Incomplete server configuration.

Explanation: The server configurationinformation contained in the server profile ismissing data necessary to complete the requestedoperation. Refer to the db2diag.log for details.

User Response: Contact your systemadministrator to verify that the serverconfiguration is correct.

CCA3062N ″Common″ is a reserved datasource name.

Explanation: ″Common″ is a reserved datasource name by DB2 CLI.

User Response: Re-enter another data sourcename.

CCA3063N The specified service name andport number conflicts withexisting values in the TCP/IPservices file. Do you wish tooverwrite the existing values inthe services file?

Explanation: The service name and portnumber entered by the user conflicts withexisting values in the TCP/IP services file. Theservice name may already be used with adifferent port number, the port number mayalready be used with a different service name orboth.

User Response: Click Yes to overwrite theexisting values in the services file with the newvalues.


Click No to cancel the action and keep theexisting values in the services file.

CCA3064N The new data source namespecified already exists.

Explanation: A data source entry already existswith the same name and its content does notmatch the specification of the new entry.Therefore, it cannot be reused.

User Response: Use a different data sourcename.

CCA5000N The user ID specified is not valid.

Explanation: The user ID specified does notexist.

User Response: Enter the correct user ID andresubmit the request.

CCA5001N The password specified isincorrect.

Explanation: The password specified for theuser ID is incorrect.

User Response: Enter the correct password forthe user ID and resubmit the request.

CCA5002N The password for the user ID hasexpired.

Explanation: The password for the user ID hasexpired and cannot be updated.

User Response: Contact your systemadministrator to have the password reset.

CCA5003N The new password specified isnot valid.

Explanation: The new password specified is notvalid.

User Response: Enter a valid password andresubmit the request.

CCA5004N An unexpected error occurred.

Explanation: An unexpected error occurredwhile attempting to update the password for theuser ID specified. Additional information mayhave been written to the file db2pem.log in theinstance directory.

User Response: Contact your systemadministrator for further assistance and providethe information from the file db2pem.log.

CCA5005N The new password does notmatch the verify password.

Explanation: The new password does not matchthe verify password.

User Response: Type the new password in bothtext boxes again.


Chapter 5. CLI Messages

This section contains the Call Level Interface (CLI) messages. The messagesare listed in numeric sequence.

CLI0001W Disconnect error.

Explanation: An error occurred during thedisconnect. However, the disconnect succeeded.

User Response: Validate that thecommunication between the client and the serverare still active.

CLI0002W Data truncated.

Explanation: An output buffer specified is notlarge enough to contain the data.

User Response: Increase the size of the outputbuffer.

CLI0003W Privilege not revoked.

Explanation: The statement was a REVOKEstatement and the user did not have the specifiedprivilege.

User Response: No action needed.

CLI0004W Invalid connection stringattribute.

Explanation: An invalid or unsupportedconnection string attribute was specified in theconnection string but the driver was able toconnect to the data source anyway.


CLI0005W Option value changed.

Explanation: The driver did not support thespecified option value and substituted a similarvalue.


CLI0006W SQLCancel treated like a close.

Explanation: The SQLCancel call was treatedlike a SQLFreeStmt call with the SQL_CLOSEoption.


CLI0100E Wrong number of parameters.

Explanation: The number of parametersspecified in SQLSetParam or SQLBindParameterwas less than number of parameters in the SQLstatement.

User Response: Respecify the SQL statement orprovide more input parameters throughSQLSetParam or SQLBindParameter.

CLI0101E The statement did not return aresult set.

Explanation: The previous statement does notresult in a result set.

User Response: Respecify the SQL statement.

CLI0102E Invalid conversion.

Explanation: The conversion between theapplication data type and SQL data type is notsupported by the driver.

User Response: Respecify a data conversionwhich is supported by the driver.

CLI0103E Too many columns.

Explanation: The number of columns specifiedin SQLBindCol is greater than the number ofcolumns in the current result set.

User Response: Respecify the SQL statement or


reset the bound column information inSQLBindCol.

CLI0104E Unable to connect to data source.

Explanation: The driver was unable to establisha connection with the data source.

User Response: Ensure the server is started andthat the communications between the client andserver are correct.

CLI0105E Connection in use.

Explanation: The specified connection handle isalready being used and the connection is stillopened.

User Response: Allocate a new connectionusing SQLAllocConnect and retry the connectionor terminate the existing connection.

CLI0106E Connection is closed.

Explanation: The connection specified by theconnection handle is no longer active.

User Response: Establish a new connection.

CLI0107E Connection failure duringtransaction.

Explanation: The connection failed during theexecution of the function and it cannot bedetermined whether the COMMIT orROLLBACK occurred before the failure.


CLI0108E Communication link failure.

Explanation: The connection between the driverand the data source failed during execution ofthis function.


CLI0109E String data right truncation.

Explanation: The data specified throughSQLSetParam or SQLBindParameter is largerthan the maximum size allowed for the

corresponding use of a parameter marker.

User Response: Respecify the parameter usingSQLSetParam or SQLBindParameter.

CLI0110E Invalid output or indicator bufferspecified.

Explanation: The returned data was NULL butthe output or indicator buffer specified was aNULL buffer.

User Response: Respecify the output orindicator buffer supplying a non-NULL bufferand retry the operation.

CLI0111E Numeric value out of range.

Explanation: Returning the numeric data wouldhave caused the whole part of the number to betruncated.

SQLPutData was called more than once for aparameter and the input data was not of typecharacter or binary.

User Response: Respecify the output bindingseither through SQLBindCol or SQLGetData toavoid creating a numeric data truncation.

Do not call SQLPutData for a parameter if theapplication data type specified for that parameterthrough SQLSetParam or SQLBindParameter isnot SQL_C_CHAR or SQL_C_BINARY.

CLI0112E Error in assignment.

Explanation: The data sent for a parameter orcolumn was incompatible with the data type ofthe associated table column.

User Response: Respecify the output bindingthrough SQLBindCol or SQLGetData or the inputbinding through SQLSetParam orSQLBindParameter.

CLI0113E Invalid date/time format.

Explanation: The data sent for a date/time fieldwas invalid. An invalid datetime format wasdetected; that is, an invalid string representationor value was specified.


User Response: Respecify the date data.

CLI0114E Datetime field overflow.

Explanation: The data sent for a date, time, ortimestamp parameter, or column, was invalid.

User Response: Respecify the date, time, ortimestamp data.

CLI0115E Invalid cursor state.

Explanation: The statement is not positioned ona row.

User Response: Position the statement on a rowby calling SQLFetch or SQLExtendedFetch andretry the operation.

CLI0116E Invalid transaction state.

Explanation: There was a transaction inprogress when SQLDisconnect was called.

User Response: Call SQLTransact before callingSQLDisconnect.

CLI0117E Invalid cursor name.

Explanation: An invalid or duplicate cursorname was specified in SQLSetCursorName.

User Response: Respecify a valid cursor namethrough SQLSetCursorName.

CLI0118E Invalid SQL syntax.

Explanation: An invalid or incorrect SQLstatement was specified.

User Response: Respecify a valid SQLstatement.

CLI0119E Unexpected system failure.

Explanation: An unexpected system failureoccurred while processing the function.

User Response: Restart the application and tryagain.

CLI0120E Memory allocation failure.

Explanation: The driver was unable to allocatememory required to support execution orcompletion of the function.

User Response: Verify that your system hasenough memory to complete the desiredoperation.

CLI0121E Invalid column number.

Explanation: The value specified in iCol is lessthan zero, greater than the number of columns inthe result set, or greater than the maximumnumber of columns allowed in a result set.

User Response: Respecify a valid value for iCol.

CLI0122E Program type out of range.

Explanation: The value specified for fCType isnot valid.

User Response: Respecify a valid value forfCType.

CLI0123E SQL data type out of range.

Explanation: The value specified for fSQLTypeis not valid.

User Response: Respecify a valid value forfSQLType.

CLI0124E Invalid argument value.

Explanation: The value specified for anargument was invalid. Possible reasons may be anull pointer, invalid length, invalid option, etc.

User Response: Re-examine the argumentpassed in to the function and determine whichargument is invalid.

CLI0125E Function sequence error.

Explanation: This function was called in aninvalid sequence.

User Response: Correct the sequence in yourapplication and retry the operation.

Chapter 5. CLI Messages 135

CLI0126E Operation invalid at this time.

Explanation: The operation the system is tryingto perform is invalid at this time.

User Response: Correct the sequence ofoperation and retry the operation.

CLI0127E Invalid transaction code.

Explanation: The transaction option specified inSQLTransact was not SQL_COMMIT orSQL_ROLLBACK.

User Response: Specify either SQL_COMMIT orSQL_ROLLBACK and retry the operation.

CLI0128E Unexpected memory handlingerror.

Explanation: Memory handling error.

User Response: An unexpected error occurredin the driver while handling some internalmemory buffer. Restart your application.

CLI0129E No more handles.

Explanation: A call was made to SQLAllocEnv,SQLAllocConnect, or SQLAllocStmt but no morehandles are available in the driver.

User Response: Call SQLFreeEnv,SQLFreeConnect, or SQLFreeStmt to free upsome handles which are no longer being used inthe application.

CLI0130E No cursor name available.

Explanation: There was no open cursor on thestatement and no cursor had been set withSQLSetCursorName.

User Response: Specify a cursor name throughSQLSetCursorName.

CLI0131E Invalid string or buffer length.

Explanation: The length of the buffer specifiedis invalid.

User Response: Specify a valid buffer length.

CLI0132E Descriptor type out of range.

Explanation: The description type specified isnot valid.

User Response: Specify a valid descriptor type.

CLI0133E Option type out of range.

Explanation: The option type specified is notvalid.

User Response: Specify a valid option type.

CLI0134E Invalid parameter number.

Explanation: The number specified for theparameter number is less than zero or greaterthan the maximum parameter supported by thedata source.

User Response: Specify a valid parameternumber.

CLI0135E Invalid scale value.

Explanation: The scale value specified isinvalid.

User Response: Specify a valid scale value.

CLI0136E Function type out of range.

Explanation: The function type is invalid.

User Response: Specify a valid function typevalue.

CLI0137E Information type out of range.

Explanation: The information type is invalid.

User Response: Specify a valid informationtype value.

CLI0138E Column type out of range.

Explanation: The column type is invalid.

User Response: Specify a valid column typevalue.


CLI0139E Scope type out of range.

Explanation: The scope type is invalid.

User Response: Specify a valid scope typevalue.

CLI0140E Uniqueness option type out ofrange.

Explanation: The uniqueness option type isinvalid.

User Response: Specify a valid uniquenessoption type value.

CLI0141E Accuracy option type out of range.

Explanation: The accuracy option type isinvalid.

User Response: Specify a valid accuracy optiontype value.

CLI0142E Direction option out of range.

Explanation: The direction option is invalid.

User Response: Specify a valid direction optionvalue.

CLI0143E Invalid precision value.

Explanation: The precision value is invalid.

User Response: Specify a valid precision value.

CLI0144E Invalid parameter type.

Explanation: The parameter type is invalid.

User Response: Specify a valid parameter typevalue.

CLI0145E Fetch type out of range.

Explanation: The fetch type is invalid.

User Response: Specify a valid fetch type value.

CLI0146E Row value out of range.

Explanation: The row value is invalid.

User Response: Specify a valid row value.

CLI0147E Concurrency option out of range.

Explanation: The concurrency option is invalid.

User Response: Specify a valid concurrencyoption value.

CLI0148E Invalid cursor position.

Explanation: The cursor position is invalid.

User Response: Specify a valid cursor positionvalue.

CLI0149E Invalid driver completion.

Explanation: The driver completion is invalid.

User Response: Specify a valid drivercompletion value.

CLI0150E Driver not capable.

Explanation: The operation is valid but notsupported by either the driver or the data source.

User Response: Specify a valid operation.

CLI0151E No data pending.

Explanation: SQLParamData or SQLPutDatawas called but there is no data at executepending on this statement.

User Response: Respecify the parametersthrough SQLSetParam or SQLBindParameter.

CLI0152E Not a string value.

Explanation: The function expected a stringargument to be supplied.

User Response: Respecify the argument to thefunction.


CLI0153E Invalid file name length.

Explanation: The length specified for the filename is invalid.

User Response: Specify a valid file namelength.

CLI0154E Invalid connection state.

Explanation: An attempt to change theconnection type was made but the connection oranother connection (in the case of DistributedUnit of Work) is already opened.

User Response: Do not attempt to change theconnection type once the connection is opened.

CLI0155E File name length is too long.

Explanation: The length supplied for the filename is greater than supported.

User Response: Specify a valid file namelength.

CLI0156E Error closing a file.

Explanation: An unexpected condition occurredwhile closing a file.

User Response: Retry the operation.

CLI0157E Error opening a file.

Explanation: An unexpected condition occurredwhile opening a file.


CLI0158E Error writing to a file.

Explanation: An unexpected condition occurredwhile writing to a file.


CLI0159E Error deleting a file.

Explanation: An unexpected condition occurredwhile deleting a file.


CLI0164E Nullable type out of range.

Explanation: An invalid nullable value wasspecified.

User Response: Respecify the nullable value.

CLI0165E Error in row.

Explanation: An error occurred while fetchingone or more rows. (Function returnsSQL_SUCCESS_WITH_INFO.)


CLI0166E PARMLIST syntax error.

Explanation: The PARMLIST value in the storedprocedures catalog table contains a syntax error.

User Response: Respecify the row for thisstored procedure.

CLI0167E Operation was cancelled.

Explanation: SQLCancel was called on thestatement.

User Response: Resubmit the operation.

CLI0171E The database was unable toconnect. Reason: reason-text.

Explanation: The database connection failed.The ’Reason:’ will explain why the database wasunable to connect.

User Response: Fix the problem, and try theconnect again.

CLI0172E The database was unable toconnect. Would you like tocontinue with the configuration?Reason: reason-text.

Explanation: The database connection failed.The ’Reason:’ will explain why the database wasunable to connect.

User Response: Fix the problem, and try theconnect again or continue with the configuration.


CLI0175E No ODBC Driver Manager hasbeen found. Cannot openODBCINST.INI file.

Explanation: Neither one of the Visigenic or theIntersolv ODBC Driver Managers have beeninstalled. An ODBC Driver Manager must bepresent before the DB2 ODBC Driver can beregistered into the associated ODBCINST.INI file.

User Response: Install an ODBC DriverManager, and try running this command again.

CLI0176E Unable to write to theODBCINST.INI file.

Explanation: An error has occurred whilewriting to an ODBCINST.INI file to be used withan ODBC Driver Manager. This may be due toinvalid format of the original ODBCINST.INI file.

User Response: Rename the existingODBCINST.INI file to something else and tryrunning this command again. If this errorpersists, contact your technical support.

CLI0177E Cannot determine where the DB2OS/2 Client is installed.

Explanation: An error has occurred while tryingto locate where the DB2 OS/2 client is installed.

User Response: Check that the DB2 OS/2 Clienthas been correctly installed.

CLI0178I The DB2 ODBC Driver has beensuccessfully registered.

Explanation: The DB2 ODBC Driver has beenregistered with the installed ODBC DriverManager(s).

User Response: The user can now use theappropriate ODBC Administrator tool from theODBC Driver Manager vendor to configure theODBC data sources.

CLI0179E Unable to display dialog box.

Explanation: The DB2 ODBC Driver cannotopen a dialog box with the window handleprovided by the application.

User Response: The application must pass avalid window handle.

CLI0180E Invalid bookmark value.

Explanation: The argument fFetchOrientationwas SQL_FETCH_BOOKMARK and thebookmark pointed to by te valueSQL_ATTR_FETCH_BOOKMARK_PTR statementattribute was not valid.

User Response: Re-specify a valid bookmarkvalue.

CLI0181E Invalid descriptor index.

Explanation: The value specified for the columnnumber argument is invalid.

User Response: Re-specify a valid columnnumber.

CLI0182W Fractional truncation.

Explanation: The data for one of the columnswas truncated.

User Response: None needed.

CLI0183E Associated statement is notprepared.

Explanation: The descriptor handle wasassociated with an IRD, and the associatedstatement handle was not in a prepared state.

User Response: Prepare the statementassociated with the descriptor.

CLI0184E Cannot modify an implementationrow descriptor.

Explanation: The descriptor handle wasassociated with an IRD, and IRD record fieldscannot be updated.

User Response: Specify a valid descriptor andfield.


CLI0185E Invalid use of an automaticallyallocated descriptor handle.

Explanation: Only explicit descriptors allocatedusing the SQLAllocHandle function can be usedin this manner.

User Response: Use an explicitly allocateddescriptor.

CLI0186E Server declined cancel request.

Explanation: Communication errors caused theserver to decline the cancel request.

User Response: None needed.

CLI0187E Non-character and non-binarydata sent in pieces.

Explanation: SQLPutData was called more thanonce for a column that was not a character orbinary column.

User Response: Only call SQLPutData once fornon-character and non-binary data.

CLI0188E Attempt to concatenate a nullvalue.

Explanation: A previous call to SQLPutData forthis parameter specified an input buffer length ofSQL_NULL_DATA

User Response: Call SQLPutData with a validinput buffer length or ensure SQLPutData iscalled the correct number of times.

CLI0189E Inconsistent descriptorinformation.

Explanation: The associated descriptor failed aconsistency check.

User Response: Ensure that descriptor fields arevalid, and all interdependent fields are setcorrectly.

CLI0190E Descriptor invalid on indirectreference.

Explanation: The descriptor handle was invalid,or the TYPE, OCTECT_LENGTH, DATA_PTR,INDICATOR_PTR, or OCTECT_LENGTH_PTRfield of the ARD contained an invalid value.

User Response: Ensure the indirect descriptorhandle is valid and that the deferred fields areset correctly.

CLI0191E Invalid attribute value.

Explanation: The value given was not correctfor the specified attribute.

User Response: Use a correct value for thespecified attribute.

CLI0192E Invalid database alias specified.

Explanation: You have specified an invalid ornon-existent database alias name through the -dparameter of the DB2CAP command.

User Response: Specify the name of an existingdatabase alias. To find out which databases arecurrently catalogued, use the LIST DATABASEDIRECTORY command.

CLI0193E Capture file capture-file-name notfound or in use.

Explanation: DB2CAP is unable to open the file<capture-file-name> that you specified as a BINDparameter value. Either the file does not exist orsome other process is using it exclusively.

User Response: Specify the name of an existingcapture file or wait until the file is released bythe other process.

CLI0194E Command syntax error. Thecorrect syntax is: db2cap [-h | -?]bind capture-file -d db-alias [-uuserid [-p password]]

Explanation: The parameters of the DB2CAPcommand, as well as the command name itself,must be typed exactly as shown in the syntaxdiagram above. They are case-sensitive on UNIX


platforms and case-insensitive on Intel platforms.There must be at least one space between theparameter and its value. For example: -u useridis correct, but -uuserid is incorrect.

In the syntax diagram, square brackets ([ ])denote optional parameters. If you specify theuserid but omit the password, you will beprompted to enter the password, in which case itwon’t be visible when you type it.

If you specify the -h or -? parameter, thecommand will display the syntax help and noother parameter will be processed.

User Response: Make sure the syntax of thecommand is as described in the diagram.

CLI0195E Invalid capture file: does notcontain any valid statementgroups.

Explanation: A valid capture file must containat least one valid statement group.

User Response: Re-capture the applicationusing the same capture file and make sure that atleast one SQL statement was captured, or editthe capture file and add statement groupsmanually. When adding a statement groupmanually, make sure you specify all the requiredkeywords for the type of SQL statement you areadding. Then submit your request again.

CLI0600E Invalid connection handle orconnection is closed.

Explanation: Connection had been closed priorto the operation.

User Response: Ensure connection close is notcalled prior to the operation.

CLI0601E Invalid statement handle orstatement is closed.

Explanation: Statement had been closed prior tothe operation.

User Response: Ensure statement close andstatement connection close are not called prior tothe operation.

CLI0602E Memory allocation error on server.

Explanation: Cannot allocate memory on server.

User Response: Ask your databaseadministrator to check the DB2 JDBC log file fordetails. Rerun your program.

CLI0603E CallableStatement get*** methodwas called withoutregisterOutParameter.

Explanation: Get*** method was called on aparameter that was not registered usingregisterOutParameter.

User Response: Add registerOutParameter callfor the parameter.

CLI0604E CallableStatement get*** methodwas called without callingexecute.

Explanation: The CallableStatement get***method was called prior to callingCallableStatement execute.

User Response: Make sure thatCallableStatement execute is called prior to anyCallableStatement get*** method.

CLI0605E CallableStatement get*** methoddid not match the type used inregisterOutParameter.

Explanation: The CallableStatement get***method was not the one that corresponds to thetype used in registerOutParameter for thisparameter.

User Response: Change to the get*** methodthat matches to the type used inregisterOutParameter for this parameter. (Referto JDBC specification)

CLI0606E The returned value from a columnis incompatible with the data typecorresponding to the get***method.

Explanation: The value in aCHAR/VARCHAR/LONGVARCHAR column is


not a valid numeric value.

User Response: Use the appropriate getmethods other than the ones that return numericvalues.

CLI0607E Invalid datetime format.

Explanation: The value in CHAR, VARCHAR,LONGVARCHAR, GRAPHIC, or VARGRAPHICcolumn is invalid date/time/ timestamp value.

User Response: Use appropriate get*** methodother than getDate/getTime/ getTimestamp.

CLI0608E Invalid conversion.

Explanation: The get*** method is invalid onthis column type.

User Response: Use the valid get*** method(see JDBC specification) to retrieve data from thiscolumn.

CLI0609E Numeric value out of range.

Explanation: The value of this column is toolarge/small for a short or int value, conversionwill cause data loss.

User Response: Use the get method that canaccommodate the value.

CLI0610E Invalid column number.

Explanation: The column number is less than 1or greater than the total number of columns inthe ResultSet.

User Response: Make sure the column numberis no less than 1 and no greater than the totalnumber of columns.

CLI0611E Invalid column name.

Explanation: The given column name cannot befound in the ResultSet.

User Response: Ensure the column name iscorrect.

CLI0612E Invalid parameter number.

Explanation: The given parameter number isless than 1 or greater than the total number ofparameters.

User Response: Ensure the parameter numberis no less than 1 and no greater than the totalnumber of parameters.

CLI0613E Program type out of range.

Explanation: The object given in thePreparedStatement/CallableStatement setObjectis not a valid object type.

User Response: Make sure the object to be set isone of the object types allowed in setObject (seeJDBC specification).

CLI0614E Error sending to the socket, serveris not responding.

Explanation: Error happened while sendingdata to server, server may be down.

User Response: Ensure the server is up, andrerun your program.

CLI0615E Error receiving from socket, serveris not responding.

Explanation: Error happened while receivingfrom server, server may be down.

User Response: Ensure JDBC server is up, andrerun your program.

CLI0616E Error opening socket.

Explanation: Cannot open the socket to server,server may be down.


CLI0617E Error closing socket.

Explanation: Cannot close the socket to server.Server may be down.



CLI0618E Userid and/or password invalid.

Explanation: The given userid/password is notvalid.

User Response: Make sure the userid/passwordis correct, and rerun your program.

CLI0619E Invalid UTF8 data format.

Explanation: When getUnicodeStream is calledon columns that are not DBCS columns, thedecoding from UTF8 format is done, but the datacannot be decoded properly.

User Response: Use getString, getBytes,getAsciiStream, or getBinaryStream instead.

CLI0620E IOException, error reading frominput stream.

Explanation: Error happened when readingdata to be put from input stream.

User Response: Make sure the file exists, andfile length is correctly given.

CLI0621E Unsupported JDBC Serverconfiguration.

Explanation: The target JDBC Serverconfiguration is not supported. If you arerunning the Control Center, the target JDBCServer must be a standalone db2jd process(started via db2jstrt) and not a 2-tier native JDBCServer.

User Response: Reconfigure the JDBC Serverusing db2jstrt on the port targeted by the ControlCenter.

CLI0622E Error accessing JDBCadministration service extensions.

Explanation: The Control Center depends uponadministration support services that run with theJDBC server. The Control Center was not able tolocate or access these administration services.

User Response: Ensure that the ControlCenter’s administration services are installedwith the JDBC server.

CLI0623E Code page conversion tables donot exist.

Explanation: Cannot find the codepageconversion tables.

User Response: Ensure the conversion tables(from the local codepage to Unicode and fromUnicode to the local codepage) are installed.

CLI0624E Code page conversion tables arenot loaded.

Explanation: Cannot load the codepageconversion tables.

User Response: Ensure your JDBC applicationhas access to the code page tables and the tablesare not corrupted.

CLI0625E You specified JDBC 1.22 behavior;cannot use JDBC 2.0 functions.

Explanation: The function you are trying to callis a new function defined in JDBC 2.0, but youspecified you want JDBC 1.22 behavior.

User Response: Do not set the JDBCVERSIONkeyword to ″122″ if you want to use JDBC 2.0functions. It should remain unset or be set to″200″.

CLI0626E function-name is not supported inthis version of DB2 JDBC 2.0driver.

Explanation: This feature is not supported bythis version of the DB2 UDB JDBC 2.0 driver.

User Response: Do not use this feature.

CLI0627E The result set is not scrollable.

Explanation: The result set is not scrollable.

User Response: Ensure you set thestatement/result set attribute to SCROLLABLE.


CLI0628E No. parameter-number parametermarker in parameter set no.set-number is not set.

Explanation: The set<data-type> method hasnot been called for this input parameter.

User Response: Call the set<data-type> methodto specify the data type of and input value forthis input parameter.

CLI0629E function-name is not supported forthis column.

Explanation: This operation cannot be called forthis column.

User Response: Change to other method.

CLI0630E Unknown result settype/concurrency number.

Explanation: An invalid value for result settype or concurrency has been specified.

User Response: Change the value to the propervalue given in the specification.

CLI0631E No random access for mixedchar/clob column.

Explanation: Random access is not supportedfor this mixed char column.

User Response: Retrieve the data sequentially.

CLI0632E Invalid fetch size; it must bebetween 0 and maxRows,inclusively.

Explanation: The fetch size specified must begreater than or equal to 0, and less than or equalto maxRows.

User Response: Modifiy the value.

CLI0633E Cannot call relative() when thereis no current row.

Explanation: The relative method was calledwhen the cursor is not at a valid row.

User Response: First move the cursor to a validrow (using absolute, next, etc), then call relative.

CLI0634E Error allocating CLI environmenthandle.

Explanation: SQLAllocEnv failed duringinitialization.

User Response: Ensure the DB2INSTANCEenvironment variable is set properly.

CLI0635E function-name is not supported inan applet.

Explanation: <function-name> is not supportedin an applet.

User Response: Avoid using <function-name>in an applet.

CLI0636E Property property-name is notspecified for the Context object.

Explanation: Property property-name is notspecified for the Context object in your Javaapplication.

User Response: Ensure that the propertyproperty-name is specified for the Context objectin your Java application.

CLI0637E object cannot be found.

Explanation: <object> does not exist.

User Response: Ensure that the <object> exists.

CLI0638E object already exists.

Explanation: <object> cannot be created as italready exists.

User Response: Ensure that the operation iscorrect.

CLI0639E Empty string.

Explanation: An empty string is not allowed.

User Response: Correct the string specified.


CLI0640E object cannot be listed.

Explanation: <object> cannot be listed.

User Response: Ensure that the <object> can belisted.

CLI0641E There is a SELECT statement inthe batch.

Explanation: A SELECT statement is notallowed in the batch.

User Response: Remove the SELECT statementfrom the batch.

CLI0642E Invalid fetch direction.

Explanation: The fetch direction specified is notsupported.

User Response: Correct the fetch direction.

CLI0643E There is no statement in thebatch.

Explanation: The batch does not have anystatement.

User Response: Add a statement to the batch.

CLI0644E Invalid row value to theabsolute() call.

Explanation: The row value specified toabsolute() is invalid.

User Response: Correct the row value.

CLI0645E Error registering driver class-name.Message: message. SQLSTATE:sqlstate. SQLCODE: sqlcode.

Explanation: The DriverManager is unable toregister the DB2 JDBC driver.

User Response: Correct the problem asindicated by the returned message, SQLSTATEand SQLCODE, and run your program again.

CLI0646E Cannot find library library-name.

Explanation: library-name cannot be found in thelibrary path. The library path is defined by theenvironment variable for the following operatingsystems:

AIX (Java 1.1)LD_LIBRARY_PATH

AIX (Java 1.2 or later)LIBPATH

HP-UX SHLIB_PATH

Linux LD_LIBRARY_PATH

OS/2 LIBPATH

Silicon Graphics IRIXLD_LIBRARY_PATH

Solaris Operating EnvironmentLD_LIBRARY_PATH

Windows operating systemsPATH

User Response: Ensure your applicationenvironment is configured correctly to use DB2.On UNIX platforms, ensure that thesqllib/db2profile script has been run to set yourenvironment variables.

CLI0647E Error allocating DB2 environmenthandle. Return code = return-code.

Explanation: The DB2 CLI environment couldnot be established.

User Response: Ensure your applicationenvironment is configured correctly to use DB2.On UNIX platforms, ensure that thesqllib/db2profile script has been run to set yourenvironment variables. To interpret the returncode, refer to the CLI Guide and Reference sectionon SQLAllocHandle().

CLI0648N The ResultSet is closed.

Explanation: The ResultSet was closed prior tothe operation.

User Response: Ensure ResultSet.close() was notcalled prior to the operation. If you are


processing multiple ResultSets usinggetMoreResults(), please ensure you callgetResultSet() prior to accessing the newResultSet.

CLI0649N executeQuery is only allowed forstatements that return a ResultSet.

Explanation: executeQuery is only allowed forstatements that return a ResultSet. Such SQLstatements include SELECT, VALUES, WITH,and CALL statements.

User Response: Use executeUpdate() orexecute().

CLI0650N A query is not allowed in anexecuteUpdate().

Explanation: You cannot issue a query withexecuteUpdate().

User Response: Use executeQuery() orexecute().

CLI0651N The stream contains more or lessdata than is specified.

Explanation: The number of bytes or charactersin the stream is not equal to the given length.

User Response: Specify the correct length.


Chapter 6. DBA Messages

This section contains the messages generated by the Database Administration(DBA) tools. The messages are listed in numeric sequence.

DBA0000I The function completedsuccessfully.



DBA0001E An internal error occurred whenallocating memory.

Explanation: An internal error occurred whenallocating memory. The application is terminated.

User Response: Try closing some applicationsto release memory. If the problem persists,contact IBM Service.

DBA0002E An internal error occurred.Unexpected input was receivedfrom the request.

Explanation: An unexpected input value wasreceived from the request. The application isterminated.

User Response: Contact IBM Service.

DBA0003E An inconsistency in the tabledefinition was detected whenprocessing the alter request.

Explanation: When processing an alter tablerequest, an inconsistency was detected betweenthe last known table definition and the tabledefinition fetched from the database. The tabledefinition might have changed outside of thecontext of the administration tool. The tablecannot be altered. The request is terminated.

User Response: Select the ″Refresh″ action onthe ″Tables″ pop-up menu to get an updated list

of tables from the database. Try altering the tableagain.

DBA0004E An error occurred when validatinga connection to a database.

Explanation: An invalid connection wasdetected. A problem can occur if the server isbrought down, the currently held connections areno longer valid, and a new connection cannot beobtained. The request is terminated.

User Response: Ensure that the server isstarted. Select the ″Connect″ action in the pop-upmenu of the database that you want to connectto. Try the action again.

If the action fails again, ensure that your networkis operating for the target system and that thedatabase is up and running on that system.

If the network is operational, a system internalerror might have occurred. Contact IBM Service.

DBA0005E An error occurred when validatingan attach to an instance.

Explanation: An invalid connection wasdetected. The database might have stopped orthe connection might no longer exist. The requestis terminated.


If the action fails again, ensure that your networkis operating for the target system and that thedatabase is up and running on that system.



DBA0006E An error occurred when validatinga handle for a persistent databaseconnection or instance attach.

Explanation: An invalid connection wasdetected. The database might have stopped orthe connection might no longer exist. The requestis terminated.


If the action fails again, ensure your network isoperating for the target system and that thedatabase is up and running on that system.


DBA0007E An internal error occurred whensetting the context type forconnections.

Explanation: An error occurred when settingthe context type for connections established bythe application. The application is terminated.


DBA0008E An internal error occurred. Anunexpected list type wasrequested.

Explanation: The type of object to be listed wasnot recognized as a valid type by the application.The application is terminated.


DBA0009E An internal error occurred. Anunexpected request type wasreceived.

Explanation: The type of request to beperformed was not recognized as a valid type bythe application. The application is terminated.


DBA0010E An internal error occurred. Anunexpected object type wasdetected.

Explanation: The type of object to be processedwas not recognized as a valid type by theapplication. The application is terminated.


DBA0011E There are too many openconnections.

Explanation: The maximum number of opendatabase connections was reached. The request isterminated.

User Response: Either:

v Disconnect from other databases and connectto the database you want. Select the″Disconnect″ action in the pop-up menu of thedatabases from which you want to disconnect.Select the ″Connect″ action in the pop-upmenu of the database to which you want toconnect.

v Update the configuration parameter to increasethe number of connections allowed.

DBA0012E Unable to allocate a connectionhandle.

Explanation: An error occurred whenattempting to allocate a connection handle. Theapplication is terminated.


DBA0013W The maximum number of objectsthat can be listed was reached.

Explanation: The maximum number of objectsthat can be listed by the application was reached.The maximum number is 20,000.

User Response: None


DBA0014E An internal error occurred. Anunexpected drop type wasrequested.

Explanation: The type of object to be droppedwas not recognized as a valid type by theapplication. The application is terminated.


DBA0015E An internal error occurred. A latchrequest failed.

Explanation: A latch request failed. Theapplication is terminated.


DBA0016E An internal error occurred. Anunlatch request failed.

Explanation: An unlatch request failed. Theapplication is terminated.


DBA0017E No error information is available.See the administration tools log.

Explanation: No error information can bedisplayed.

User Response: See the administration tools logfor error information.

DBA0018E The Administration Server is notstarted. Start the AdministrationServer and try the action again.

Explanation: The Administration Server is notstarted.

User Response: Start the Administration Serverusing the DB2ADMIN START command on thetarget system and try the action again.

DBA0019E The object object-name is in use.Try the action again at a latertime.

Explanation: The object on which the actionwas requested or a related object is already being

used in another action. Modifications to theobject or a related object might be in progress.

The requested action cannot be performed at thesame time as the current action.

Examples:

v If a table is being altered, a request to renamethe same table will not be allowed until theinteraction with the Alter window is complete.However, a request to sample the contents ofthat table is allowed.

v A request to drop an object (such as a table)will not be allowed if any other actions arepending on related objects (such as thedatabase, views, or triggers).

The action is not performed.

User Response: Try the action again at a latertime when the object is available.

DBA0020E An error occurred opening theadministration tools trace file.

Explanation: An error occurred opening theadministration tools trace file.


DBA0021E An error occurred writing to theadministration tools trace file.

Explanation: An error occurred writing to theadministration tools trace file.


DBA0022W An error occurred closing theadministration tools trace file.

Explanation: An error occurred whenattempting to close the administration tools tracefile. Processing continues.

User Response: Ensure that the administrationtools log file was specified correctly.

Chapter 6. DBA Messages 149

DBA0023W An error occurred opening theadministration tools log file.

Explanation: An error occurred whenattempting to open the administration tools logfile. Processing continues.


DBA0024W An error occurred writing to theadministration tools log file.

Explanation: An error occurred whenattempting to write to the administration toolslog file. Processing continues.

User Response: Ensure that the administrationtools log file was specified correctly and can bewritten to.

DBA0025W An error occurred closing theadministration tools log file.

Explanation: An error occurred whenattempting to close the administration tools logfile. Processing continues.


DBA0026E An internal administration toolserror occurred.

Explanation: An unrecoverable error occurred.


DBA0027E An internal error occurred. A lockcontention in the administrationtools was detected.

Explanation: Lock contention in theadministration tools was detected.


DBA0028I The current administration toolssession will be terminated due toan unrecoverable error.

Explanation: A severe internal error occurred.


DBA0029C The application programminginterface program did not completesuccessfully for object name withreason code name. Try again orcontact your local support.

Explanation: An application programminginterface call did not complete.

User Response: Try the operation again orcontact your system administrator.

DBA0030E An error occurred whileattempting to connect to databasename.

Explanation: The requested operation could notcomplete because it requires a connection todatabase name. The connection was notsuccessful.

User Response: Make sure the database isaccessible. Try explicitly connecting to thedatabase using the connect action on thedatabase pop-up menu. A common error onconnection is an invalid userid and password.Make sure you have supplied the proper useridand password. Try the operation again or contactyour system administrator.

DBA0031E An error occurred whileattempting to attach to instancename.

Explanation: The requested operation could notcomplete because it requires an attachment to theinstance name. The attachment was notsuccessful.

User Response: Make sure the instance isaccessible. Try explicitly connecting to theinstance using the connect action on the instancepop-up menu. A common error on connection isan invalid userid and password. Make sure you


have supplied the proper userid and password.Try the operation again or contact your systemadministrator.

DBA0032C An error occurred whileattempting to load DLL name.

Explanation: Either the dynamic link libraryname was not found or an error occurred whilereading the file.

User Response: Verify that the DLL is installedand undamaged, and its location is part of theLIBPATH parameter in the CONFIG.SYS file.

DBA0033C name cannot be dropped becauseit is currently in use by theadministration tools. Close somewindows and retry the command.

Explanation: Either the object name you selectedto drop, or an item that is owned by the objectyou selected to drop, is still being used byanother administration tool. For example, youmight have and ALTER table window open for adatabase that you are trying to drop. In this case,you cannot drop the database until you close itsALTER table window.

User Response: Close all the windows usingthe object you selected, or close all the windowsusing items owned by that object, and then retrythe command.

DBA0034C name cannot be removed becauseit is currently in use by theadministration tools. Close somewindows and retry the command.

Explanation: Either the object name you selectedto remove, or an item that is owned by the objectyou selected to remove, is still being used byanother administration tool. For example, youmight have and ALTER table window open for adatabase that you are trying to remove. In thiscase, you cannot remove the database until youclose its ALTER table window.

User Response: Close all the windows usingthe object you selected, or close all the windows

using items owned by that object, and then retrythe command.

DBA0035C The operation operation cannot beperformed because the objectname is currently in use by theadministration tools. Close somewindows and retry the command.

Explanation: This operation operation requiresname to be in a name state.

User Response: Make sure all other pendingoperations on the selected object are complete,and then retry the command.

DBA0036I The database configuration wassuccessfully updated. Allapplications must disconnect fromdatabase name before the changescome into effect. If a backup hasalready been taken it isrecommended to take anotherbackup of the database in order topick up the new configurationvalues.

Explanation: The database configuration wassuccessfully updated, but the active databaseconfiguration cannot be changed until allapplications are disconnected from the database.Once all applications are disconnected, thechanges will come into effect with the firstconnection to the database.

User Response: Ensure that all applications aredisconnected from the database, and thenreconnect to the database.

DBA0037I The instance configuration wassuccessfully updated. Theinstance name must be stoppedbefore most changes come intoeffect.

Explanation: The instance configuration wassuccessfully updated.

Changes to the configuration parameter″dftdbpath″ take effect immediately.

For the remaining configuration parameters, the


changes do not take effect until all applicationshave disconnected from the database, and theinstance is successfully stopped and startedagain.

User Response: To make all changes take effect,ensure that all applications have disconnectedfrom the database, stop the instance, and thenstart it again.

You can stop the instance by selecting the stopaction on the instance pop-up menu in theControl Center. You can then start the instanceby selecting the start action on the instancepop-up menu in the Control Center.

DBA0039W There are currently databaseobjects locked or databaseconnections in use. Continueshutdown?

Explanation: The database objects in theControl Center are locked when actions, such asAlter Table, are taken against them. Other actionswill maintain connections to the database thatare required to complete the task.

User Response: If you choose to continue withthe shutdown, then all locks and connections areforced and the tools will shut down. It can bedangerous to do so, however, because forcingsome actions (like Restore Database) halfwaythrough the task can leave the database in acorrupted state.

It is safest to first go back to the DB2 tools andmake sure there are no database operationsoutstanding.

DBA0040W Shutting down will stop theSnapshot monitor. Continueshutdown?

Explanation: Snapshot monitoring has beenstarted on one or more database objects and tocontinue the monitoring, you must have the DB2tools running.

User Response: Choose to continue theshutdown only if you no longer require theSnapshot monitor.

DBA0041I The requested operation could notbe performed because the DB2Administration Tools is anuntrusted applet.

Explanation: Applets loaded over the networkare usually considered to be untrusted. DifferentWeb browsers and applet viewers may imposedifferent restrictions on untrusted appletsincluding most local system operations (Forexample, read files, write files, and print files).

User Response: Consult your systemadministrator and see if these restrictions can berelaxed or customized.

DBA0042I Do you want to clear the settingfor the userid and password thatwas used to connect to thisdatabase.

Explanation: If you choose to clear this setting,you will prevent unauthorized access to thisdatabase from this workstation. However, youwill be prompted to enter the correct userid andpassword the next time you connect to thisdatabase.

User Response: Click on Yes to clear the useridand password setting. Click on No to save theuserid and password setting until you exit theControl Center.

DBA0043I The command has not beenexecuted.

Explanation: The operation did not occur andhas been aborted.

User Response: Resubmit the command.

DBA0100I Control Center is updating nodedirectory information for instanceinstance. Incorrect information isbeing corrected. The currentrequest cannot be performed.

Explanation: The Control Center detected thatthe nodetype changed at the instance and isrecataloging the instance based on the newinformation. Depending on the nodetype value


for the instance, actions from the Control Centermay be different.

User Response: If available, try the requestagain.

DBA0101W Entries specified in the exceptionlist will not be used. Do you wantto continue?

Explanation: The Nodes Contain Exceptionscheck box is deselected, but exception containersare specified in the List Exception dialog.

User Response: Click on Yes to clear theexception containers list, or click on No orCancel to reselect the Nodes Contain Exceptionscheck box.

DBA0102W Unable to detect nodetype forinstance - instance. Reason Code:reason-code.

Explanation: Nodetype is a database managerconfiguration parameter that identifies whetherthe instance is a single-partition or partitionedenvironment.

Discovery tries to resolve the nodetype value foryou. This distinction between instances isrequired because actions in the Control Centercan be different between single-partition andpartitioned environments.

If the reason code is -1, discovery could not mapthe catalogued instance to a valid DB2 instance.

All other reason codes map to a valid SQLmessage. Check the help for the correspondingSQL message.

User Response: Discovery has the followingrequirements:

1. DB2 Administration Server must be set upand running at the remote instance you wantto catalog or access.

2. Ensure the instance is listed in the registry.Issue db2set -l from the host you arecataloging.

3. The following global DB2 Registry valuesmust be set:

v DB2SYSTEM

v DB2ADMINSERVER

4. The following instance DB2 Registry valuesmust be set:

v DB2COMM

5. The following administration serverconfiguration parameters must be set:

v DISCOVER = KNOWN andDISCOVER_COMM = null

or

v DISCOVER = SEARCH andDISCOVER_COMM = protocol (forexample, TCPIP )

Verify the setting of these registry values byentering db2set -all.

DBA0103W Changes made to theconfiguration parameter valueswill not be used. Do you want tocontinue?

Explanation: Another database partition wasselected, but the changes to the configurationparameters apply to the previously selecteddatabase partition.

User Response: Click on Yes to obtain theconfiguration parameter values for the nextdatabase partition and discard the changes thatwere specified for the previously selecteddatabase partition.

DBA0113E Exception containers are specified,but not all nodes in thenodegroup are included. Nocontainers are specified for thefollowing nodes: node-list.

Explanation: The specified exception containershave no common container. Because no commoncontainer is specified, the exception containermust be defined at every node in the nodegroup.

User Response: Click on OK to add containersto the specified nodes.


DBA0114W Control Center detected incorrectnode directory information forinstance - instance. Incorrectinformation is being corrected.Please exit and restart the ControlCenter. The current request cannotbe performed.

Explanation: The Control Center detected thatthe nodetype changed at the instance.

User Response: Exit the Control Center andrestart it.

DBA0115I Node directory information hasbeen corrected for this instance.Instance instance should berefreshed.

Explanation: Because the cataloged informationfor the instance is updated, the displayed objectsand actions may not be correct.

User Response: Select the ″Refresh″ action fromthe instance pop-up menu to update the ControlCenter, then try the request again.

DBA0116I The operation cannot beperformed by the JDBC server atthis time. Retry this operationlater.

Explanation: The JDBC server is currently busywith an existing operation and cannot performthe user operation.

User Response: Wait until the JDBC servercompletes the existing operation and retry theoperation.

DBA0117W Partition information could not beretrieved. Reason code =reason-code, object = object.

Explanation: Function which relies onsuccessful retrieval of partition information willbe disabled or removed. This may include menuitems as well as actual dialog function.

User Response: Make sure that the DAS isstarted at the server where the object exists. Ifthe DAS is started, then treat the return code as a

DAS error and continue troubleshooting.

DBA0200N An attempt to open or read fromfile filename failed. Error code =error-code.

Explanation: An attempt was made to eitheropen or read from a file using the DatabaseAdministration Server (DAS). The attempt failed.

User Response: Verify that the DAS is running,and that the file exists and has read permissionfor the userid associated with the DAS.

If the problem persists, contact your IBM servicerepresentative with the corresponding file nameand error code.

DBA0201N An attempt to open or write tofile filename failed. Error code =error-code.

Explanation: An attempt was made to eitheropen or write to a file using the DatabaseAdministration Server (DAS). The attempt failed.

User Response: Verify that the DAS is running,and that the file system is not full and has writepermission for the userid associated with theDAS.


DBA0202N An attempt to open or read fromfile filename failed. Error code =error-code.

Explanation: An attempt was made to eitheropen or read from a file. The attempt failed.

User Response: Verify that the file exists andhas appropriate read permission.



DBA0203N An attempt to open or write tofile filename failed. Error code =error-code.

Explanation: An attempt was made to eitheropen or write to a file. The attempt failed.

User Response: Verify that the file system is notfull and that the it has appropriate writepermission.


DBA1005W This action will force both LocalDatabases and Gatewayapplications. Do you want tocontinue?

Explanation: You requested to force allapplications on the instance.

User Response: Click Yes to process the requestor No to cancel it.

DBA1006E An invalid plugin extension hasbeen detected by the ControlCenter.

Explanation: The file ″db2plug.zip″ has beencorrupted or not properly setup.

User Response: If the Control Center is runningas an application, check to see if ″db2plug.zip″ isincluded in the ″CLASSPATH″ environmentvariable. If the Control Center is running as anapplet, check to see if ″db2plug.zip″ is includedin the ″archive″ tag of the db2cc.htm HTML file.If the problem persists, contact you DB2 systemadministrator.

DBA1007W An invalid object name orparameter was entered. TheControl Center will start with theSystems folder as the root of thenavigator tree.

Explanation: An invalid object name means thatthe system, instance, subsystem, or databasename entered cannot be found, either because itdoes not exist or because the combination of

names entered is invalid. For example, thedatabase name entered may exist but not withinthe specified system name. An invalid parametermeans that something other than -h, -i, -sub, or-d was entered.

User Response: Ensure that you are using validobject names and parameters, and try again.

DBA1100W Less than number MB of memoryis dedicated to your server. Norecommendation has been made.The current values on the ResultsPage match the suggested values.

Explanation: Because the amount of memorydedicated to the server is so small, theConfiguration Advisor cannot make arecommendation.

The suggested values in the ″Results Page″ arethe same as the current values.

User Response: If you can dedicate morememory to the server, turn to the ″Server Page″,increase the amount of memory, and try again.Otherwise, click on Cancel to close theConfiguration Advisor.

DBA1101I Unable to obtain stripe setsinformation on the table spacecontainer. Stripe sets will not beshown.

Explanation: The connected user may not havesufficient authority to obtain stripe setsinformation.

User Response: SYSADM authority is requiredto obtain stripe sets information.

DBA1102E An error occurred when theConfiguration Advisor tried tosave the suggested values in asystem file.

Explanation: Either the Configuration Advisorcould not create a CFG subdirectory under yourinstance directory or it could not save a systemfile containing recommendations into the CFGsubdirectory of your instance directory.


User Response: Make sure the disk containingthe instance directory is not full and you havewrite access to this disk. Afterwards, click onDone to try again.

DBA1104I The instance and databaseconfiguration parameters weresuccessfully updated. Theinstance name must be stoppedbefore most changes come intoeffect. You may want to rebindyour packages after the newconfiguration parameters takeeffect so that the new values willbe used during the bind.

Explanation: The Configuration Advisor hasupdated the database manager configurationparameters, database configuration parameters,and buffer pool sizes in the SYSBUFFERPOOLScatalog.

The changes will not take effect until the instanceis stopped on the server.

Packages were bound with the old configurationparameters. They need to be rebound, after thenew parameters take effect, to exploit these newparameters.

User Response: When you are ready to use thenew configuration parameters, stop the instance,and then start the instance.

Rebind your packages if necessary.

DBA1107E An error occurred when theConfiguration Advisor tried to getsystem information from yourserver.

Explanation: An unexpected error occurred. TheConfiguration Advisor cannot continue.

User Response: Contact your systemadministrator.

DBA1108W The Configuration Advisor wasunable to increase the sizes of thebuffer pools due to other memoryrequirements determined fromyour responses. The buffer poolsizes are left unchanged. The useof the suggested set ofconfiguration values may causepaging on the server.

Explanation: This is a warning that there maynot be enough memory dedicated to your serverto run the workload that you specified.

User Response: Review your selections onprevious pages of the Configuration Advisor tocheck that the workload description isappropriate or add more memory to your server.

DBA1109W The transactions rate you enteredis more than ten times the averagenumber of connected applications.If you are using a transactionmanager, ignore this message. Ifnot, consider changing the rate.

Explanation: The Configuration Advisor verifiesthat the transactions rate is reasonable. Thetransaction rate may be too high if you are notusing a transaction manager.

User Response: If you are using a transactionmanager, ignore this message. Otherwise, use alower number of transactions per minute, orincrease the average number of connectedapplications.

DBA1110I The system database directory hasno entries.

Explanation: There are currently no entriesfound in this database directory.


DBA1111E The database alias name alreadyexists for another database.

Explanation: You requested that a backup berecovered into a new database, but the database


name you specified is already used as an aliasfor an existing database.

When a database is created, the database iscataloged in the system database directory usingthe database name as the alias, and this aliasmust be unique.

User Response: Specify a database name that isnot being used as an alias, or request that thebackup be recovered into the existing database.

DBA1112E The database alias name was notfound in the system databasedirectory.

Explanation: You requested that a backup berecovered into an existing database, but adatabase no longer exists with this alias.

User Response: Select an existing database, orrequest that the backup be recovered into a newdatabase.

DBA1113E Restart failed because indoubttransactions exist against thedatabase and the connection tothe database was dropped.

Explanation: The restart operation encounteredindoubt transactions. This left the database in aninconsistent state. The DBA Utility dropped theconnection to the database.

User Response: Resolve the indoubttransactions. If they are not resolved, applicationsmust restart the database whenever it is required.

If you are in an XA/DTP environment, and thetransaction manager that was using the databaseis available, instruct it to resolve the indoubttransactions.

Otherwise, use the Command Line Processor tomanually complete each indoubt transaction.

DBA1114E Database name is in backuppending state. A full backup mustbe done before the database canbe used.

Explanation: This state will prevent thedatabase from being updated. The database must

be backed up before any updates can happen.

User Response: Back up the database.

DBA1115E Enter a value for name.

Explanation: A value is required.

User Response: Provide the value and retry therequest.

DBA1116E The value for parameter must bebetween minimum and maximum.

Explanation: The value must be within thespecified range.

User Response: Enter a value in the specifiedrange and retry the request.

DBA1117E The value for name is not valid.

Explanation: The value entered is not valid.

User Response: Correct the value and retry therequest.

DBA1118E The value for name must notexceed maximum.



DBA1119E The value for name must not besmaller than minimum.



DBA1121I A job was created for the requestdescription on system system. Itsjob number is number. To view thestatus and output of the job, usethe Jobs page on the Journal.

Explanation: The job was successfully started.

User Response: To view the status and outputof the job, use the Jobs page on the Journal.


DBA1122I The job has completed for therequest description on systemsystem. For the status and outputof the job, view job number in theJobs page on the Journal.

Explanation: The job has completed.

User Response: To view the status and outputof the job, use the Jobs page on the Journal.

DBA1123I Job description is terminated.

Explanation: The job was canceled in responseto a user request.


DBA1126I The database has no table spaces.

Explanation: The database has no table spaces.


DBA1127I The table space has no containers.

Explanation: The table space has no containers.


DBA1128E No containers have beenspecified. Select ″Add″ in order tocreate containers.

Explanation: The current list does not containany new containers.

User Response: Select ″Add″ and fill in thenecessary fields to add a container to the list.

DBA1129E Provide a value for name.

Explanation: The operation you requested canbe performed only if you enter a value for name.

User Response: Enter a value, and then click onOK.

DBA1130E The name entries must not exceedmaximum characters.

Explanation: You entered a value that exceededthe maximum number of characters.

User Response: Enter a valid value, and thenclick on OK.

DBA1131E device is not a valid tape device.

Explanation: The operating system did notaccept the specified tape device. Local tapedevices are of the form ″\\.\TAPEn″, where nrepresents the drive number (0 is the first).

User Response: Enter a valid name for the tapedevice, and then click on OK.

DBA1132E Tape device device does notsupport a tape mark blocksize ofblocksize.

Explanation: The Control center uses a tapemark blocksize that is not supported by thespecified tape device.

User Response: Use the Command LineProcessor to submit the request. Specify asupported blocksize in the DB2 INITIALIZETAPE command.

DBA1133E An error occurred operating tapedevice device.

Explanation: An unexpected error occurredwhile operating the specified tape device.

User Response: Resubmit the request. If theproblem persists, contact your systemadministrator.

DBA1134I A job was created for the requestdescription. However, nojob-related entries can be createdin the Journal because thedatabase administrative server(DAS) instance could not beaccessed.

Explanation: The job started successfully, butthe status and output of the job will not be


logged in the Journal. This can happen if theDAS instance is not started.

User Response: To have the status and outputof the job logged in the Journal, start the DASinstance first before starting a backup operation.

DBA1135I The job has completed for therequest description.

Explanation: The job has completed.


DBA1136E A backup at the table space levelcannot be performed because thedatabase db is not enabled forforward recovery.

Explanation: You can only back up a databaseat the table space level if you have first enabledthat database for forward recovery.

User Response: To enable the database forforward recovery, you can either:

v Use the Database Logging Wizard to changeyour logging type to ARCHIVE logging.

v Set either the LOGRETAIN or the USEREXITdatabase configuration parameters to ON,disconnect all existing applications from thedatabase, and perform an offline backup of thedatabase.

DBA1137E The value for name must not besmaller than minimum units.

Explanation: The value entered is smaller thanthe minimum minimum units.

User Response: Enter a valid value and retrythe request.

DBA1138E The value for name must notexceed maximum units.

Explanation: The value entered exceeded themaximum of maximum of units.


DBA1139E You must allocate at least pages forthe system catalog.

Explanation: There cannot be more than pagesin each table space container. Each page of datarequires 4 KB. So 1 MB of storage is equal to 256of these 4 KB pages.


DBA1140E You cannot allocate more thanpages pages in a single container.

Explanation: Each page of data requires 4 KB.So 1 MB of storage is equal to 256 of these 4 KBpages.


DBA1141E You must allocate at least pagespages in each container.

Explanation: The minimum number of pages ina table space container is related to the extentsize of the table space. It is 5 times the extentsize plus one page. So for a table space with anextent size of 32 pages (the default value), theminimum size of a single container is 161 pages.


DBA1142W The LOGARCHIVE databaseconfiguration parameter hascurrently been set to ON fordatabase name. As soon as allapplications have disconnectedfrom the database, the databasewill be in backup pending state.This state prevents the databasefrom being updated. The databasemust be backed up before anyadditional updates can occur.

Explanation: Before the database manager canstart logging each transaction in your database, itmust have a full offline database backup to useas a starting point.

User Response: Make a full offline database


backup as soon as possible. If this is not possible,set the LOGARCHIVE parameter to OFF.

DBA1143E You cannot perform an offlinebackup right now because at leastone application is still connectedto the database. You can either tryagain later, or disconnect allapplications connected to thedatabase immediately by selectingforce from the instance object’spop-up menu.

Explanation: An offline backup cannot beperformed until all applications connected to theselected database have stopped. You can eitherwait for the applications to disconnectthemselves, or you can force the connectedapplications right now.

User Response: Either try the action later, or, toforce all applications connected to the selecteddatabase immediately, select ″Force″ from theinstance object’s pop-up menu.

DBA1144E The container container-namealready exists.

Explanation: Each table space container must beunique.

User Response: Specify a file name or directorythat does not currently exists on the system.

DBA1145E The container container-name hasbeen specified more than once.


User Response: Specify a file name or directorythat is not currently in your list of newcontainers.

DBA1146E The container container-name isincluded in both the user andtemporary storage spaces.


User Response: Change the file name or

directory of the container in either the user ortemporary table space.

DBA1147E The container container-name isincluded in both the catalog andtemporary storage spaces.


User Response: Change the file name ordirectory of the container in either the catalog ortemporary table space.

DBA1148E The container container-name isincluded in both user and catalogstorage spaces.


User Response: Change the file name ordirectory of the container in either the user orcatalog table space.

DBA1149E param-1 does not have enough freespace for the containers youspecified.

Explanation: When a DMS container is createdit consumes the full amount of space youallocated to it.

User Response: Change the location of thecontainer to an area that has more storage, orincrease the available storage in the currentlocation of the container.

DBA1150E A column with the same namealready exists.

Explanation: The column was not addedbecause a column with the same name is alreadyspecified or exists in the table being created oraltered.

User Response: Specify a different columnname.


DBA1151W The requested operation was notperformed against the column orconstraint. Reason code =reason-code.

Explanation: An attempt was made to add,alter, or remove a column or constraint duringtable creation or alteration. The reason codegiven indicates the actual rule violation, asfollows:

1 A column or constraint with the samename already exists.

2 The column participates in the primaryor partitioning key and cannot beremoved.

3 The column participates in a unique keyand cannot be removed.

4 The column participates in a foreign keyand cannot be removed.

5 The column participates in a tabledimension and cannot be removed.

6 The column may participate in a tablecheck constraint. The operation wasallowed.

7 Primary and unique keys cannot bedefined as a subset of all dimensioncolumns.

8 Dimensions cannot defined such thatany primary or unique key becomes asubset of all dimension columns.

9 Primary and unique keys must bedefined as supersets of the partitioningkey.

10 The partitioning key must be defined asa subset of all existing primary andunique keys.

11 An object with that column set alreadyexists.

User Response: Correct the condition that iscausing the operation to fail and retry theoperation.

DBA1152E A constraint with the same namealready exists.

Explanation: The constraint was not addedbecause a constraint with the same name isalready specified or exists in the table beingcreated or altered.

User Response: Specify a different constraintname.

DBA1153E The object is already in the list.

Explanation: The specified object already existsin the list. The action is not performed.

User Response: Specify another object or closethe window.

DBA1154E The specified system, instance,and database do not identify arecognized database.

Explanation: The system, instance, and databasespecifications do not identify a database that isknown to the application. The action is notperformed.

User Response: Either ensure that the system,instance, and database names are correct; or addthe system, instance, and database that you wantto access to the application.

DBA1155E The object object-name no longerexists in the database. The requestcannot be performed.

Explanation: The specified object no longerexists in the database and cannot be operated on.The request is terminated.

User Response: Select the ″Refresh″ action inthe pop-up menu of the object folder to get anupdated list of objects.

DBA1156W The request completed withwarnings. See the administrationtools log for details.

Explanation: The requested action completed,but one or more warning messages were issued.


User Response: See the administration tools logfor more information.

DBA1157E No authorities or privileges weregranted or revoked on object-namefor user-name. See theadministration tools log fordetails.

Explanation: The requested action completed.No action was taken against the authorities orprivileges on the specified object for the specifieduser or group.

User Response: None

DBA1158I Number of records read duringthe load = count. Number ofrecords skipped before the loadbegins = count. Number of rowsloaded into the target table =count. Number of records thatcould not be loaded = count.Number of duplicate rows deleted= count. Number of records loadedsuccessfully and committed to thedatabase = count.

Explanation: The action completed with thespecified results.

User Response: None

DBA1159I Export completed. item-description= count.

Explanation: The export action completedsuccessfully with the specified results.

User Response: None

DBA1160I Import completed. Number ofrecords read during the import =count. Number of records skippedbefore the import begins = count.Number of rows imported intothe target table = count. Numberof records that could not beimported = count. Number ofduplicate rows deleted = count.Number of records importedsuccessfully and committed to thedatabase = count.

Explanation: The import action completedsuccessfully with the specified results.

User Response: None

DBA1161I item-description = count.

Explanation: The import or export completedwith the specified results.

User Response: None

DBA1162I Load completed. Number ofrecords read during the load =count. Number of records skippedbefore the load begins = count.Number of rows loaded into thetarget table = count. Number ofrecords that could not be loaded =count. Number of duplicate rowsdeleted = count. Number ofrecords loaded successfully andcommitted to the database = count.

Explanation: The load action completedsuccessfully with the specified results.

User Response: None

DBA1163E The table was not copied. See theadministration tools log fordetails.

Explanation: One or more warnings or errorsoccurred when copying the table. The table wasnot copied.

User Response: See the administration tools logfor more information.


DBA1164E The specified target table alreadyexists. The source table was notcopied.

Explanation: The copy table action failedbecause the target table exists.

User Response: Either specify a new targettable or delete the existing target table and trythe action again.

DBA1165E No privileges were granted orrevoked for user-name.

Explanation: Privileges were not granted to orrevoked from the specified user or group sinceno privileges have been changed.

User Response: Resubmit the command aftermaking changes to the current privileges.

DBA1166E The identifier identifier-namecontains unbalanced quotes.Correct the identifier and try theaction again.

Explanation: The specified identifier containsunbalanced single or double quotes. The namingrules require balanced quotes. The action is notperformed.

User Response: Correct the identifier and trythe action again.

DBA1167E The identifier identifier-namecontains embedded blanks.Correct the identifier and try theaction again.

Explanation: The specified identifier containsblank characters, which violates the naming rulesfor ordinary identifiers. The action is notperformed.

User Response: Remove the blanks or delimitthe identifier with double quotes and try theaction again.

DBA1168E The first character in theidentifier identifier-name is notvalid. Correct the identifier andtry the action again.

Explanation: The first character of the specifiedidentifier is invalid. It must follow the namingrules for ordinary identifiers. The action is notperformed.

User Response: Replace the first character witha valid one or delimit the identifier with doublequotes then try the action again.

DBA1169I The command script that canupdate the instance and databaseconfiguration parameters wascreated successfully. Use theScript Center to run or schedulethe script.

Explanation: A new script was savedsuccessfully in the Script Center. You may openthe Script Center to view, run or schedule thenew command script.

After the script is run, the changes will not takeeffect until the instance is stopped on the server.


User Response: To view, run or schedule thenewly saved script, open the Script Center byselecting the Script Center icon from the icon bar.

After you have run the script and when you areready to use the new configuration parameters,stop the instance, and then start the instance.

Rebind your packages if necessary.

DBA1170E The page size of the table spaceand the page size of the bufferpool buffer-pool must be equal.

Explanation: You must choose an existingbuffer pool whose page size matches that of thetable space you wish to create. The default bufferpool has the default page size of 4K. If any otherpage size is desired for the table space, a buffer


pool with a matching page size must exist.

User Response: From the Advanced Table Spacewindow, change the page size of the table spaceto match that of the buffer pool or change thebuffer pool to one whose page size matches thatof the table space. If there are no buffer pools ofthe desired page size, you can create one fromthe Create Buffer Pool window.

DBA1171N The temporary table spacetablespace specified cannot be usedfor this utility operation.

Explanation: The backup and restore commandscannot be performed on a temporary table space.

User Response: Resubmit the command usingonly valid non-temporary table spaces.

DBA1172W Since the database is in backuppending state, you must performan offline database backup. Thishas been preselected for you.Other options that are no longeravailable having been disabled.

Explanation: The only valid operation for adatabase in Backup Pending state is to performan offline database backup. The wizard hasensured that these options are selected. It hasalso disabled the other options in the wizard thatare no longer available.

User Response: Complete the wizard, and runthe command. It is recommended that youperform a full database backup.

DBA1173N A restore at the table space levelcannot be performed because thedatabase database is not enabledfor forward recovery.

Explanation: You can only restore a database atthe table space level if you have enabled thedatabase for forward recovery.

User Response: To enable the database forforward recovery, set the database configurationparameters LOGRETAIN or USEREXIT to ON,disconnect all existing applications from the

database, and perform an offline backup of thedatabase.

DBA1174I You have chosen more than oneimage for the same partition. Inmost cases, you will not wish todo this.

Explanation: In most scenarios, choosing morethan one backup image to restore is not useful,and will actually slow down the total time tocomplete the restore.

User Response: Make sure only one image foreach partition appears on the right hand side ofthe slosh bucket.

DBA1175W This functionality requires animage for each partition.

Explanation: Rolling forward to a point in timerequires an image for each partition. You havenot chosen all partitions on the Available Imagespage, and so cannot use this option.

User Response: Return to the Available Imagespage and select one image for each partition inyour database.

DBA1176N The Control Center failed toautomatically catalog the ToolsCatalog Database database-name forsystem system-name.

Explanation: Possible explanations are:

v The database is specified incorrectly at theDB2 Administration Server for systemsystem-name.

v The database manager that contains thedatabase is not configured for TCP/IPcommunication.

User Response: Possible solutions include:

v Verify that the DB2 Administration Serverconfiguration parameters are correctlyspecified.

v Verify that the database manager is configuredfor TCP/IP communications.

If the problem persists, contact IBM Support.


DBA1177N A database connection to theTools Catalog Databasedatabase-name cannot be made.SQLCODE sqlcode

Explanation: A database connection to the ToolsCatalog Database database-name cannot be made.SQLCODE sqlcode

User Response: Refer to the user response forthe SQLCODE returned from the connectoperation.

DBA1178W Task task-name was created with amore recent version of the ControlCenter.

Explanation: The selected task was created witha more recent version of the Control Center.Some functionality for the task are not supportedby the Control Center on the local machine.

User Response: You can choose to proceed andedit the task. When saving the task, you can:

v Save the changes to the existing task. This willcause the loss of functionality that was specificto the more recent version of the ControlCenter.

v Save changes by creating a new task. This willnot alter the original task.

DBA1179W Task task-name created with a morerecent version of the ControlCenter will be overwritten.

Explanation: A task originally created with amore recent version of the Control Center will beoverwritten. Proceeding with this operation willcause the loss of functionality that was specific tothe more recent version of the Control Center.

User Response: You can choose to:

v Save the changes to the existing task. This willcause the loss of functionality specific to themore recent version of the Control Center.

v Save changes by creating a new task. This willnot alter the original task.

DBA1180W No SQL available to display.

Explanation: Show SQL only displays the SQLstatements that change the current privileges. Ifno privileges have been changed, no SQLstatements are generated.

User Response: Resubmit the command aftermaking changes to the current privileges.

DBA1181W The catalog partition cannot bebacked up at the same time asother database partitions in anoffline backup.

Explanation: In an offline backup, the catalogpartition cannot be backed up at the same timeas other database partitions. If you continue, thebackup will fail.

User Response: Ensure that the catalogpartition has not been grouped with otherdatabase partitions on the ″Partitions″ page ofthis wizard.

DBA1183N Unable to edit task task-name

Explanation: The selected task was created witha more recent version of the Control Center.There is no editor associated with this type oftask in this version of the Control Center.

User Response: Use a newer version of theControl Center to edit this task.

DBA1350I The Design Advisor was not ableto recommend any indexes. Set alonger time limit on the Calculatepage and try calculatingrecommended objects again.

Explanation: The Design Advisor was not ableto recommend any objects because the maximumsearch time was too short.

User Response:

1. On the Calculate page in the Design Advisor,set a longer time limit or no limit at all.

2. Try running the Design Advisor again.


DBA1351I The Design Advisor was not ableto recommend any objects. Set alarger size limit on the Limitspage and try calculatingrecommended objects again.

Explanation: The Design Advisor was not ableto recommend any object because the maximumlogical size of all objects was too small.

User Response:

1. On the Limits page in the Design Advisor, seta larger maximum logical size or nomaximum at all.

2. Try running the Design Advisor again.

DBA1352I The Design Advisor was not ableto recommend any objects thatwill improve the performance ofyour workload.

DBA1353W You specified only one SQLstatement in your workload. Yourdatabase might have additionalactivity. Do not drop any objectsunless you are sure they are notneeded for other reasons.

Explanation: Since you only specified one SQLstatement in your workload, it is unlikely that itrepresents all of the activity against yourdatabase.

The Drop page of the Design Advisor lists allexisting objects that were not recommended forthis one SQL statement.

User Response: Do not drop any objects unlessyou are sure they are not needed for otherreasons.

DBA1500E The local system object is notallowed to be removed.

Explanation: The local system object appears inthe tree if this is a server installation, and doesnot appear if this is a client installation. You haveno direct control over the removal of this objectbecause it has special properties that are requiredby the server installation type.


DBA1501E The local system object is notallowed to be changed.

Explanation: The local system object appears inthe tree if this is a server installation, and doesnot appear if this is a client installation. You haveno direct control over the changing of this objectbecause it has special properties that are requiredby the server installation type.


DBA1502E The unknown system object is notallowed to be removed.

Explanation: The unknown system objectappears in the tree only if orphaned instancesthat are not recognized as belonging to anyexisting system are found. You have no directcontrol over the removal of this object because itis shown automatically only when needed.

User Response: No action is required. However,if you want to remove the need to show thisobject in the tree, then do the following steps:

v Expand the unknown system object to showall orphaned instances.

v If necessary, add new system objects to thecontrol center to contain the orphanedinstances.

v If necessary, use the change action to alter thesystem name on any remaining orphanedinstances.

v If the unknown instance object also appears,then you also have orphaned databases thatare not recognized as belonging to any existinginstance Remove the need to show theseobjects by doing steps similar to these, addinginstances or altering databases until noorphans are left to be shown.

DBA1503E The unknown system object is notallowed to be changed.

Explanation: The unknown system objectappears in the tree only if orphaned instancesthat are not recognized as belonging to anyexisting system are found. You have no direct


control over the changing of this object because itis shown automatically only when needed andhas only special properties that cannot bechanged.


DBA1510E Specify a system name.

Explanation: You must specify a system namebefore you can add this new system object.

User Response: Specify a system name in theappropriate entry field, and then try the actionagain.

DBA1511E The specified system name isalready in use. You must specify asystem name that is unique.

Explanation: You specified a system name thatmatches the name used for another system objectin the tree. System names must be unique withinthe control center, and are case-sensitive. Youcannot use the names ’Local’ or ’Unknown’because these are system names reserved for useby the local and unknown system objects. Toavoid confusion, you should also try not to usethe names of existing instances or databases assystem names, although the tool does notprevent you from doing this.

User Response: Specify a unique system name,and then try the action again.

DBA1520W The operating system type for thissystem object has been detected tobe newos, but the localinformation shows it to be oldos.Do you want to update the localinformation now to reflect thecorrect operating system type?

Explanation: When you add a new systemobject, you specify an operating system type,which is stored locally for that remote system.Later, when actual connections are made to theremote system, the true operating system type isreported back. It is possible for the originaloperating system type information to have beenset incorrectly so that it does not match the true

settings on the remote system. In this case, it isbest to update the local information to matchwhat settings truly exist on the remote system.

User Response: Select Yes to update the localinformation now, or select No to leave the localinformation as it is.

DBA1521W The server version type for thissystem object has been detected tobe newtyp, but the localinformation shows it to be oldtyp.Do you want to update the localinformation now to reflect thecorrect server version type?

Explanation: When you add a new systemobject, the server version type is automaticallyset to be either DB2 V5 or DRDA, depending onthe operating system type you choose. Later,when actual connections are made to the remotesystem, the true server version type, which maybe a previous release such as DB2 V2, is reportedback. In this case, it is best to update the localinformation to match what settings truly exist onthe remote system.


DBA1522W The operating system type andserver version type for this systemobject have been detected to benewos and newtyp respectively, butthe local information shows theseto be oldos and oldtyp respectively.Do you want to update the localinformation now to reflect thecorrect settings for these values?

Explanation: When you add a new systemobject, you specify an operating system type,which is stored locally for that remote system.Also, the server version type is automatically setto be either DB2 V5 or DRDA, depending on theoperating system type you choose. Later, whenactual connections are made to the remotesystem, the true operating system type andserver version type are reported back. Theoriginal settings for this information may have


been incorrect so that they do not match the truesettings on the remote system. In this case, it isbest to update the local information to matchwhat settings truly exist on the remote system.


DBA1530E The specified system has not beenconfigured to support anyprotocols that your local systemuses.

Explanation: The specified system has beendetected on the network, however theAdministration Server for this remote system hasnot been configured to support any protocolsthat your local system uses.

User Response: You must configurecommunications on the remote systemAdministration Server, including the DB2COMMparameter, before you can successfully access it.

DBA1533E Unable to export the serverprofile.

Explanation: The target file system might nothave enough disk space to complete the exportoperation.

User Response: Free some disk space on thetarget file system and retry the operation. If theproblem persists, contact your DB2 systemadministrator.

DBA1540E The active local instance object isnot allowed to be removed.

Explanation: The active local instance objectappears in the tree always as the first instanceunder the local system object. This is a specialinstance object used to represent the currentDB2INSTANCE environment variable setting.You have no direct control over the removal ofthis object because it has special properties thatare required by the local system.


DBA1541E The active local instance object isnot allowed to be changed.

Explanation: The active local instance objectappears in the tree always as the first instanceunder the local system object. This is a specialinstance object used to represent the currentDB2INSTANCE environment variable setting.You have no direct control over the changing ofthis object because it has special properties thatare required by the local system.


DBA1550E Specify an instance name.

Explanation: You must specify an instancename before you can add this new instanceobject.

User Response: Specify an instance name in theappropriate entry field, and then try the actionagain.

DBA1551E The specified instance name isalready in use. You must specifyan instance name that is unique,otherwise do not specify theinstance name and one will begenerated for you automatically.

Explanation: You specified an instance namethat either matches the name used for anotherinstance object in the tree, or is being used by asystem object in the tree. Instance names must beunique within the control center, and are alwayscapitalized. System objects also use anautomatically generated instance name to storetheir own protocol information, with the instancename usually being a short form of the chosensystem name. You cannot use the name ’LOCAL’or the current DB2INSTANCE environmentvariable setting for the instance name.

User Response: Specify a different instancename, and then try the action again.


DBA1552E Specify a remote instance.

Explanation: You must specify a remoteinstance before you can add this new instanceobject.

User Response: Specify a remote instance in theappropriate entry field, and then try the actionagain.

DBA1560E Specify a destination name.

Explanation: You must specify a destinationname for the selected protocol before you cancorrectly add this new object.

User Response: Specify a destination name inthe appropriate entry field, and then try theaction again.

DBA1561E Specify a file server.

Explanation: You must specify a file server forthe selected protocol before you can correctlyadd this new object.

User Response: Specify a file server in theappropriate entry field, and then try the actionagain.

DBA1562E Specify a workstation name.

Explanation: You must specify a workstationname for the selected protocol before you cancorrectly add this new object.

User Response: Specify a workstation name inthe appropriate entry field, and then try theaction again.

DBA1563E Specify a host name.

Explanation: You must specify a host name forthe selected protocol before you can correctlyadd this new object.

User Response: Specify a host name in theappropriate entry field, and then try the actionagain.

DBA1564E Specify a service name.

Explanation: You must specify a service namefor the selected protocol before you can correctlyadd this new object.

User Response: Specify a service name in theappropriate entry field, and then try the actionagain.

DBA1565E Specify a computer name.

Explanation: You must specify a computername for the selected protocol before you cancorrectly add this new object.

User Response: Specify a computer name in theappropriate entry field, and then try the actionagain.

DBA1566E Specify an instance name.

Explanation: You must specify an instancename for the selected protocol before you cancorrectly add this new object.

User Response: Specify an instance name in theappropriate entry field, and then try the actionagain.

DBA1567E This action or function is notavailable for this instance type orthe associated system.

Explanation: The selected action, or associatedfunction, is currently not supported for the typeof instance against which the action or functionwas initiated. Some instance types, for exampleSatellite Edition, necessarily do not support fullfunctionality.

User Response: Refer to the documentationdescribing available function for this instancetype.

DBA1568W Database connection wasestablished but did not establish asyncpoint two-phase connection.

Explanation: An attempt was made to connectto a database using syncpoint two-phaseconnection type. A connection was established


but failed to make a syncpoint two-phaseconnection. Multisite updates involving thisdatabase connection will not be successful.

User Response: Check that the multisite updatescenario has been configured properly for yourenvironment, ensuring that the coordinatinginstance is restarted after configuration iscomplete. If DB2’s Syncpoint Manager is beingused, check in the db2diag.log to see if it wasstarted successfully.

DBA1569E The action cannot be completedon this instance because itsremote instance name is notknown.

Explanation: The remote instance name field isan optional parameter and was not specified. Toperform this action on a remote instance, theremote instance name must be known.

User Response: Invoke the Change Instancewindow and specify the name of the remoteinstance.

DBA1570E The DB2 Administration Serverfor this system has not beendefined.

Explanation: The current operation requires anattachment to the system’s administration serverbut its instance name has not been specified.

User Response: Invoke the change action on thetarget system and specify its instance name,operating system and any other protocolparameters.

DBA1571W The name of the local system doesnot match the DB2SYSTEMenvironment variable.

Explanation: The system name of the localadmin node is different from the value of theDB2SYSTEM environment variable.

User Response: There are three options:

v Change the value of the DB2SYSTEMenvironment variable to match the systemname of the local admin node.

v Uncatalog the local admin node and invokethe Control Center, which will automaticallyrecatalog it.

v Uncatalog the local admin node and recatalogit with a system name that matches the valueof the DB2SYSTEM environment variable.

DBA1572E The instance name instance-namespecified is not valid.

Explanation: The instance name specified is notvalid. The instance name may be 1 to 8characters and all of the characters must be fromthe database manager base character set. Also,the instance name must not match that of anyother catalogued instance.

User Response: Specify a different value for theinstance name.

DBA1573E This action is not available for theselected system.

Explanation: Some Control Center actionsrequire that an Administration Server beavailable on the target system. The system thatyou selected does not have an AdministrationServer. The requested action is not available forthis system.


DBA1580E New database objects are notallowed to be added to theunknown instance.

Explanation: The unknown instance objectappears in the tree only if orphaned databasesthat are not recognized as belonging to anyexisting instance are found. The tool tries toprevent you from creating new orphanswhenever possible, so you are not allowed toadd new ones to the unknown instance.


DBA1581E Specify a database name.

Explanation: You must specify a database namebefore you can add this new database object.


User Response: Specify a database name in theappropriate entry field, and then try the actionagain.

DBA1582E Specify an alias.

Explanation: You must specify an alias beforeyou can add this new database object.

User Response: Specify an alias in theappropriate entry field, and then try the actionagain.

DBA1583E The specified alias is already inuse.

Explanation: You specified an alias that matchesthe alias used for another database object in thetree. Database aliases must be unique within thecontrol center, and are always capitalized.

User Response: Specify a unique alias, and thentry the action again.

DBA1590W The dbase database was createdusing an earlier version of DB2than DB2 V5. Only limitedfunction will be allowed for thisdatabase until it is migrated.

Explanation: All databases that are found underDB2 V5 type system objects are first assumed tobe DB2 V5 databases. This database has nowbeen detected to actually be a back-leveldatabase that has not yet been migrated to theDB2 V5 level. You can still access this database,but only limited function is available forback-level databases until you actually migratethem.


DBA2000E You have not specified a jobdescription.

Explanation: A description for the job isrequired information.

User Response: Enter a job description in theentry field, and then click on OK.

DBA2001E You have not specified thenumber of hours for yourselection.

Explanation: The number of hours for yourselection is required information.

User Response: Enter a number in the hoursentry field.

DBA2002E You must select at least 1 day ofthe week for your selection.

Explanation: To schedule a recurring job, youmust specify at least one day of the week for thejob.

User Response: Select at least one day of theweek when scheduling a recurring job.

DBA2003E You specified a date that is notvalid.

Explanation: The date you specified is notvalid. Perhaps the date you have specified is inthe past.

User Response: Enter a valid date.

DBA2004E You specified a date or time orcombination of date and time thatis not valid.

Explanation: The next execution date and timecannot be calculated, so no jobs can bescheduled. One possible error is when the timespecified for a job to be run once is in the past.Remember that the date and time combinationmust be valid on the managed host where theschedule job is to be run.

User Response: Enter a valid date and timecombination.

DBA2005E You have not specified a scriptname.

Explanation: A name for the script is requiredinformation.

User Response: Enter a name for the script file,and then click on OK.


DBA2006E You have not specified acomment.

Explanation: You indicated that you want torecord a comment when the job is completed, butthe comment entry field is empty.

User Response: Enter a comment, or clear the’Record a comment’ check box.

DBA2007E You specified a script name that isnot valid.

Explanation: The command script is saved as afile in the file system. The script path is at most255 bytes long. The file name part of the scriptname can be at most 8 bytes long. If an extensionis specified, it cannot be longer than 3 bytes. Thescript name must not contain any blanks. Forexample, valid script names can be:j:\script\new.cmd c:\data\test\crtdb.bat

User Response: Enter a valid script name, andthen click on OK.

DBA2008I Job job-id was created successfully.

Explanation: A new job was scheduledsuccessfully. You may turn to the journal jobsummary to view the newly created job.

User Response: To view the newly created job,turn to the journal job summary by selecting theJournal icon from the icon bar.

DBA2009E A system error occurred. AScheduler InfoBase call wasunsuccessful. RC = return-code.Restart the Admin. Server, andthen retry the command.

Explanation: An internal error occurred.

User Response: Restart the Admin. Server, andthen retry the command. If the problem persists,contact your system administrator.

DBA2010E The Scheduler service is not upand running. Restart the Admin.Server, and then retry thecommand.

Explanation: To perform any action involvingthe Job Scheduler or the Script Center, theScheduler service must be up and running.

User Response: Restart the Admin. Server, andthen retry the command.

DBA2011E A system error occurred.Scheduling type (DBA or PGM) isnot valid. Restart the Admin.Server, and then retry thecommand.



DBA2012E A system error occurred. OS errorwas detected. RC = return-code.Restart the Admin. Server, andthen retry the command.



DBA2013E The job id was not found. Restartthe Admin. Server, and then retrythe command.




DBA2014E A system error occurred. Unableto change the status of the job.Restart the Admin. Server, andthen retry the command.



DBA2015E A system error occurred. Memoryallocation was unsuccessful inclient. Restart the Admin. Server,and then retry the command.



DBA2016E A system error occurred. Scanhandle is not valid. Restart theAdmin. Server, and then retry thecommand.



DBA2017I Are you sure you want to removethe selected jobs?

Explanation: You specified to remove theselected jobs. You have the chance now todouble-check the jobs that you selected toremove, and either to continue or to cancel therequest.

User Response: Select YES to remove theselected jobs. Select NO to cancel the removerequest.

DBA2018I Are you sure you want to removethe selected saved scripts?

Explanation: You specified to remove theselected scripts that are currently saved. Youhave the chance now to double-check the scripts

that you selected to remove, and either tocontinue or to cancel the request.

User Response: Select YES to remove theselected scripts. Select NO to cancel the removerequest.

DBA2019E You have not specified thenumber of days for your selection.

Explanation: The number of days for yourselection is required information.

User Response: Enter a number in the daysentry field.

DBA2020E A system error occurred. Unableto determine script type.Command script was notexecuted.

Explanation:

User Response:

DBA2021I Are you sure you want to discardyour changes?

Explanation: You specified to have yourchanges not saved in the Script Center. You havethe chance now either to continue discardingyour changes, or to cancel the request andresume editing.

User Response: Select YES to discard thechanges. Select NO to resume editing thecommand script.

DBA2022I Command script script-id wascreated successfully.

Explanation: A new script was savedsuccessfully in the Script Center. You may turn tothe Script Center to view the new commandscript.

User Response: To view the newly saved script,turn to the Script Center by selecting the ScriptCenter icon from the icon bar.


DBA2023E Instance instance-name does notexist. Command script was notexecuted.

Explanation: The instance name associated withthe script file does not exist.

User Response: You may select ″Edit″ from theScript Center to update the instance name to anexisting instance.

DBA2024E Command script script-id does notexist.

Explanation: The scheduled job cannot beexecuted because the script file associated withthe job does not exist.

User Response:

DBA2025E A system error occurred. Thisproblem may also be related tomemory allocation on the client.Restart the Admin. Server, andthen retry the command.



DBA2026I Are you sure you want to removethe selected job?

Explanation: You specified to remove theselected job. You have the chance now todouble-check the job that you selected to remove,and either to continue or to cancel the request.

User Response: Select YES to remove theselected job. Select NO to cancel the removerequest.

DBA2027I Are you sure you want to removethe selected saved script?

Explanation: You specified to remove theselected script that is currently saved. You havethe chance now to double-check the script thatyou selected to remove, and either to continue orto cancel the request.

User Response: Select YES to remove theselected script. Select NO to cancel the removerequest.

DBA2028E You have not specified thenumber of weeks for yourselection.

Explanation: The number of weeks for yourselection is required information.

User Response: Enter a number in the weeksentry field.

DBA2029E A system error occurred.Scheduler key was not found.Restart the Admin. Server, andthen retry the command.



DBA2030E You did not specify a systemname. Select one from the list.

Explanation: The system name is requiredinformation to process the action.

User Response: Select a system name from thedrop-down list.

DBA2031I Job job-id was rescheduledsuccessfully.

Explanation: A job that you requested to berescheduled was rescheduled successfully.

User Response:

DBA2032E You have not specified a scriptname.

Explanation: A name for the script is requiredinformation.

User Response: Enter the script name in theentry field, and then click on OK.


DBA2033E You have not entered thecommand script.

Explanation: The command script is empty.

User Response: Enter the command scriptcontent, and then click on OK.

DBA2034I Command script script-id wasupdated successfully.

Explanation:

User Response:

DBA2035E A system error occurred. Unableto retrieve the command scriptscript-id. Restart the Admin.Server, and then retry thecommand.



DBA2036E A system error occurred. Unableto create the command script.Restart the Admin. Server, andthen retry the command.



DBA2037E A system error occurred. Unableto replace the command scriptscript-id. Restart the Admin.Server, and then retry thecommand.



DBA2038E A system error occurred. Unableto copy the command scriptscript-id. Restart the Admin.Server, and then retry thecommand.



DBA2039E You have not specified thenumber of months for yourselection.

Explanation: The number of months for yourselection is required information.

User Response: Enter a number in the monthsentry field.

DBA2040E You must select at least 1 day ofthe month for your selection.

Explanation: To schedule a recurring job, youmust specify at least one date per month for thejob.

User Response: Select at least one date permonth when scheduling a recurring job.

DBA2041E A system error occurred. Unableto remove the command scriptscript-id. Restart the Admin.Server, and then retry thecommand.




DBA2042E A system error occurred. Unableto run the command scriptscript-id. Restart the Admin.Server, and then retry thecommand.



DBA2043I Job job-id was created successfullyfor running command scriptscript-id.

Explanation:

User Response:

DBA2044E You have not specified a scriptdescription.

Explanation: A description for the script file isrequired information.

User Response: Enter a description for thescript file, and then click on OK.

DBA2045E Command script associated withjob job-id is system-generated.Content cannot be shown.

Explanation: The script associated with abackup or reorganize table action is not inreadable format.

User Response: Select a different commandscript (file?) to view the content of.

DBA2046E Command script script-id issystem-generated. Content cannotbe edited.

Explanation: The script associated with abackup or reorganize table action is not inreadable format.

User Response: Select a different commandscript file to edit.

DBA2047E A system error occurred. Thescript type is unknown. Restartthe Admin. Server., and then retrythe command.



DBA2048E The file name you specifiedalready exists. Specify a differentscript file name.

Explanation: The name of each script file mustbe unique. You specified a file name that alreadyexists.

User Response: Specify an unique script filename.

DBA2049E A system error occurred. Fileaccess was denied.

Explanation: The application was unable toaccess the file in the file system.

User Response: Retry the command. If theproblem persists, contact your systemadministrator.

DBA2050E A system error occurred. The diskis full.

Explanation: There is no more room on thedisk. Processing cannot continue.

User Response: Delete unwanted files from thefile system. If the problem persists, contact yoursystem administrator.

DBA2051E A system error occurred. A harddisk error occurred.

Explanation: An internal error relating to thehard disk occurred. The application was unableto access a file.

User Response: Retry the command. If theproblem persists, contact your systemadministrator.


DBA2052E Unable to execute the job due tologon failure. Userid = user-id.

Explanation: The password was invalid for thegiven userid or the userid is invalid.

User Response: Enter a valid userid andpassword when prompted.

DBA2053E A system error occurred. Unableto remove job history entry.



DBA2054E A system error occurred. Unableto run job job-id.



DBA2055E Command script script-id has beenremoved from the Script Center.

Explanation:

User Response:

DBA2056I Command script script-id was notchanged.

Explanation:

User Response:

DBA2057E A system error has occurred. Thepath was not valid.



DBA2058E A line in the file is greater thannumber bytes.

Explanation: The maximum number of bytes ina line is exceeded.

User Response: Rewrite the long line intoseparate lines without exceeding the limit.

DBA2059E A system error occurred. Therewas a sharing violation.



DBA2060E A system error occurred. Unableto copy script script-id.



DBA2061I Script script-name was createdsuccessfully.

Explanation: A new script file with the namescript name was created successfully.

User Response: To view the newly createdscript, turn to the Script Center by selecting theScript Center icon from the icon bar.

DBA2062E A system error occurred. Unableto create a new script. Restart theAdmin. Server, and then retry thecommand.




DBA2063E A system error occurred. Unableto retrieve the results of job job-id.Restart the Admin. Server, andthen retry the command.



DBA2064E A Script Center record alreadyexists for this script file name.Specify a different script filename.

Explanation: The name of each script file mustbe unique within the Script Center. You specifieda file name that already exists.

User Response: Specify an unique script filename.

DBA2065E A system error occurred. Thescript file does not exist in the filesystem.

Explanation: The script file was not found inthe file system. The file may have been erased.

User Response: Remove the script entry andrecreate it.

DBA2067I The REORG TABLE commandcompleted successfully.

Explanation:

User Response:

DBA2068E You have not entered the instancename.

Explanation: The name of the instance isrequired information.

User Response: Enter the instance name in theentry field, and then click on OK.

DBA2069W The maximum number of numberjobs has been created. Pleaseremove obsolete jobs.

Explanation:

User Response: Remove jobs that are no longerneeded before creating another new job.

DBA2070W The maximum number of numberscripts has been created. Pleaseremove obsolete scripts.

Explanation:

User Response: Remove scripts that are nolonger needed before creating another new script.

DBA2071W The maximum number of numberbytes has been reached. Datashown is truncated. The completefile file-name can be found at theserver.

Explanation: The editor cannot handle a file aslarge as the current one. Data shown had to betruncated.

User Response: The entire file can be viewed atthe server in the indicated location.

DBA2072E The script associated with jobjob-id has been removed from theScript Center.

Explanation: The script file does not existanymore.

User Response:

DBA2073E You have not specified a useridand password.

Explanation: A userid and password forrunning the job are required.

User Response: Enter a valid userid andpassword for running the job, and then click onOK.


DBA2074E A system error occurred. Theworking directory path was notvalid.

Explanation: The specified working directorydoes not exist so it cannot be used to run thescript.

User Response: Use the Browse... button toselect a valid working directory path.

DBA2075I Job job-id has been submitted. Usethe Jobs page on the Journal toview the results.

Explanation:

User Response:

DBA2076E The job terminated abnormally.

Explanation:

User Response:

DBA2077E File name file-name already existsin the file system.

Explanation: File name must be unique.

User Response: Specify another file name.

DBA2078E An unexpected error occurred.There is no job output.

Explanation: There is no job output fromrunning the job.

User Response: A possible error could be aninvalid file extension is used on the operatingsystem. Recreate the script with a validextension.

DBA2081W The file file-name exceeds themaximum number of bytes(maximum-bytes) for the ScriptCenter. You must use an externaleditor to view or edit the file.

Explanation: The file is larger than themaximum size that the Script Center can display.

User Response: Use an external editor to viewor edit the file.

DBA2082W The file permissions for the scriptdo not allow Script Center to readthe script with the current userID.

Explanation: The file permissions for the scriptdo not allow Script Center to read the script withthe current user ID.

User Response: Ensure that you have setappropriate file permissions for the script.

DBA2151E The script cannot be scheduledbecause it was not saved.

Explanation: The script cannot be scheduledbecause you canceled the save action andtherefore, the script was not saved in the ScriptCenter.

User Response: Save the script and then tryscheduling again.

DBA2152I The script has to be saved to theScript Center before it can bescheduled.

Explanation: Only scripts that are saved in theScript Center can be scheduled and run.

User Response: Select OK to save the script tothe Script Center, or Cancel if you do not want toschedule the script.

DBA2153I File file-name was openedsuccessfully.

Explanation:

User Response:

DBA2154I Script script-name was openedsuccessfully.

Explanation:

User Response:


DBA2155I Do you want to overwrite filefile-name?

Explanation: The file file name currently exists inthe file system and the save operation willoverwrite its contents.

User Response: Select OK if you want tooverwrite the contents of the file, or Cancel ifyou do not want to alter its contents.

DBA2156I Do you want to overwrite scriptscript-name?

Explanation: The script script name currentlyexists in the Script Center and the save operationwill overwrite its contents.

User Response: Select OK if you want tooverwrite the contents of the script, or Cancel ifyou do not want to alter its contents.

DBA2157I File file-name was updatedsuccessfully.

Explanation:

User Response:

DBA2158I File file-name was createdsuccessfully.

Explanation: A new file with the name file namewas created successfully in the file system.

User Response:

DBA2171I Do you want to discard all yourchanges to the script, and exitfrom the Command Center?

Explanation: You specified to exit from theCommand Center, but the changes to the currentscript have not yet been saved. Your changes willbe lost unless you cancel your exit request.

User Response: Select Yes to discard yourchanges and exit from the Command Center, orselect No to cancel the exit request.

DBA2172I Do you want to discard yourchanges to the current script, andcreate a new script?

User Response: Select Yes to discard yourchanges and to create a new script, or select Noto cancel the request.

DBA2173I The Command Center is stillprocessing a command. Try againlater.

Explanation: You tried to run a script or issue aset of commands, but the Command Centercannot process your command until it hasfinished processing the current one.

User Response: Please wait a few moments andtry the command again. To stop the currentcommand, click on the turning gears icon on thetool bar or select ″Terminate″ from the Resultsmenu on the Results page.

DBA2174E The file file-name specified on thecommand line could not beopened. Make sure that the fileexists and that you have readaccess to the file, and then tryagain.

Explanation: You specified the name of a filecontaining a script that you want to import, butthe Command Center could not access that file.

User Response: Make sure that you haveentered the file name correctly on the commandline, that the file exists, and that your user IDhas read access to that file.

DBA2175E There is not enough memory tocreate the Command Centerwindow. The application cannotcontinue.

Explanation: The system encountered a memoryallocation problem when trying to create theCommand Center window.

User Response: Make sure there is enoughmemory on your system to run the CommandCenter, and then try again.


DBA2176E The system environment did notinitialize. The application cannotcontinue. Restart the databasemanager and try again, or contactyour local support personnel.

Explanation: The command processorenvironment did not initialize properly.

User Response: Make sure you have enoughdisk space and then try again.

DBA2177E The system could not create anaccess plan because a problemrelating to Visual Explain hasoccurred.

Explanation: Command Center has encountereda problem when trying to create an access plan.

User Response: Please refer to the help fromthe previous messages.

DBA2178E You need a database connection inorder to create an access plan. Usethe ″Connect″ statement toconnect to a database, and thentry the command again.

User Response: Establish a database connectionfirst using the ″Connect″ statement, and thencreate an access plan for that database. To see alist of available databases, issue the command″list database directory″.

DBA2179E An access plan cannot be createdbecause the statement you used isnot in the correct format or is nota query.

Explanation: The statement you used to try tocreate an access plan is either not in the correctformat for a query or is not a query.

User Response: Check your statement for errorsin query format, make necessary changes, andretry the statement. Refer to Visual Explaindocumentation for guidance on forming validqueries.

DBA2180I The program name ″db2″ beforethe statement will be ignoredbecause it is not required.

Explanation: You don’t need to type ″db2″before a statement in the Command Center. It isonly required at the operating system commandprompt.


DBA2181I The Command Center is notavailable at this time. Retry thisoperation later.

Explanation: The JDBC server does not supportmultiple WEBCC Command Center sessions. TheJDBC server is already busy with an existingCommand Center session.

User Response: Wait until the currentCommand Center session is finished and retrythe operation.

DBA2182N A script name following thepattern script-name-pattern cannotbe saved because the ScriptCenter already contains too manyscripts with names that follow thesame pattern. Remove old scriptsthat follow this pattern from theScript Center then invoke thetool-name again.

Explanation: There are too many automaticallygenerated scripts with names likescript_name_pattern.

User Response: In the Script Center, remove atleast one script with a name likescript_name_pattern, then invoke the tool_nameagain.

DBA2193W window-name cannot run withoutprogram-name. Ensure that theDatabase Tools subcomponent isinstalled.

Explanation: To invoke window-name, theprogram-name application must be installed onthe server. By default, the Database Tools


subcomponent of the Administration andConfiguration Tools component is selectedduring installation. The Database Toolssubcomponent must be selected duringinstallation in order for the program-nameapplication to be installed.

User Response: Ensure the Database Toolssubcomponent is installed. If Database Tools wasnot selected during the installation of thedatabase server, you will need to run DB2 Setupagain.

1 Stop all DB2 services.

2 Run DB2 Setup.

3 Select Custom install.

4 Uncheck all components exceptAdministration and Configuration Tools.

5 In the details for Administration andConfiguration Tools, select DatabaseTools.

6 Complete the install.

7 Restart all DB2 services.

8 Use the window-name.

DBA3007W Are you sure you want to deletethe explained statement?

Explanation: You are about to delete theexplained statement. This will delete the rows inthe explain tables.

User Response: Ensure that you want to deletethe explained statement.

DBA3008W Are you sure you want to deletethe explained statements?

Explanation: You are about to delete theexplained statements. This will delete the rows inthe explain tables.

User Response: Ensure that you want to deletethe explained statements.

DBA3009E A system error occurred. TheVisual Explain tool could notcontinue processing.

Explanation: An unexpected error occurredcausing the operation to stop.


v Verify that your system has sufficient memory.

v Where appropriate, stop other programs usingthe system.

If the problem persists, contact your systemadministrator.

DBA3010E The explain snapshot has beendeleted. Your request cannot becompleted.

Explanation: The explain snapshot that isrequested has been deleted from the explaintables.

User Response: Regenerate the snapshot.

DBA3011E This explain snapshot was createdusing a different version of thedatabase manager from the VisualExplain Tool. Your request cannotbe completed.

Explanation: The explain snapshot was createdusing a newer version or an older version of thedatabase manager from the Visual Explain Tool.The access plan graph cannot be constructed bythe Tool.

User Response: Use the same version of thedatabase manager as the Visual Explain Tool tograph the explain snapshot.

DBA3012I String not found.

Explanation: The search string is not found inthe text being displayed.



DBA3013E Text is missing. You must specifythe text string to be found.

Explanation: You did not specify a searchstring.

User Response: Specify a search string.

DBA3014E No selection is made in the list.You must select at least one entryin the list.

Explanation: You did not make a selection inthe list.

User Response: Select at least one entry in thelist.

DBA3015I There are no referenced columnsassociated with this access plan.

Explanation: There were no columns referencedin the query for the referenced table.


DBA3016I There are no page fetch pairsstatistics associated with thisindex.

Explanation: There are no page fetch pairsstatistics stored in the catalog table for this index.Refer to the System Catalog Statistics section inthe Administration Guide for more details.


DBA3017I There are no referenced functionsassociated with this access plan.

Explanation: This access plan did not requirethe use of any functions.


DBA3018I There are no column distributionstatistics associated with thiscolumn.

Explanation: There are no column distributionstatistics stored in the catalog table for thiscolumn. Refer to the System Catalog Statistics

section in the Administration Guide for moredetails.


DBA3019I There are no indexes associatedwith this table.

Explanation: There were no indexes defined onthe referenced table at the time of explain andthere are no indexes currently defined in thetable.


DBA3020E An error occurred while aCOMMIT against the databasewas being attempted and noSQLCODE can be returned.

Explanation: An unexpected error occurred.


DBA3021E An error occurred while aROLLBACK against the databasewas being attempted and noSQLCODE can be returned.



DBA3022E The Get Database ManagerConfiguration API passed back anon-zero return code.



DBA3023E The Get Database ConfigurationAPI passed back a non-zero returncode.




DBA3024E An error occurred while saving tothe file file.

Explanation: Possible problems include:

v The file cannot be opened for write.

v The file name does not conform to the filesystem convention.


v Change the file attribute to read write.

v Specify the correct file name.

DBA3025E An error occurred while retrievingfrom the file file.

Explanation: Possible problems include:

v The file is not readable.

v The file does not exist.

User Response: Specify the correct file name.

DBA3026E No printers are installed.

Explanation: There are no printers installed onyour machine.

User Response: Install a printer on yourmachine.

DBA3033I There are no referenced tablespaces associated with this accessplan.

Explanation: This access plan did not referenceany database objects contained in a table space.


DBA3034W The snapshot was created usingcode page codepage but is notconverted to the code page of thewindow running the VisualExplain Tool.

Explanation: The snapshot of the access plangraph displayed was created on a code pagedifferent from the code page of the window

running the Visual Explain Tool. Code pageconversion is not successful because the snapshotis too large. The access plan graph is displayedwithout code page conversion. You may not beable to display the current statistics when youopen the statistics windows.

User Response: Change the code page of thewindow running the Visual Explain Tool to thesame one used to create the snapshot anddisplay the access plan graph again.

DBA3035W The snapshot was created usingcode page codepage but is notconverted to the code page of thewindow running the VisualExplain Tool. The value of thedatabase manager configurationparameter UDF_MEM_SZ is toosmall.

Explanation: The snapshot of the access plangraph displayed was created on a code pagedifferent from the code page of the windowrunning the Visual Explain Tool. Code pageconversion is not successful because the userdefined function used to convert between thecode pages do not have enough memory to run.The access plan graph is displayed without codepage conversion. You may not be able to displaythe current statistics when you open the statisticswindows.


v Change the database manager configurationparameter UDF_MEM_SZ of your server to512 and display the access plan graph again.Note that the configuration parameter may nottake effect until the next time you do adb2start on your server.

v Change the code page of the window runningthe Visual Explain Tool to the same one usedto create the snapshot and display the accessplan graph again.


DBA3036I Explain tables have been createdto process your dynamic explainrequest.

Explanation: One or more explain tables havebeen created under the current user ID. Thesetables will be used to store the informationneeded by your dynamic explain request.


DBA3037E The explain snapshot has beencorrupted. Your request cannot becompleted.

Explanation: The explain snapshot that isrequested has been corrupted in the explaintables.

User Response: Regenerate the snapshot.

DBA3038I There are no referenced bufferpools associated with this accessplan.

Explanation: This access plan did not referenceany database objects contained in a buffer pool.


DBA3039E Explain tables cannot be found.

Explanation: Explain tables do not exist.

User Response: Create explain tables using oneof the following methods:

v Use the sample command file that is providedin the EXPLAIN.DDL file. This file is locatedin the sqllib\misc directory. To run thecommand file, go to this directory and issuethe db2 -tf EXPLAIN.DDL command.

v From the Control Center or from theExplained Statements History window, selectExplain SQL from the menu selections. Usethe Explain SQL Statement window todynamically explain an SQL statement andautomatically create the explain tables.

DBA3040E The command is specifiedincorrectly.

Explanation: The command has invalid syntax.

User Response: Issue the command with the -hoption to see the correct syntax.

DBA3041E The name of the database must bebetween 1 and maximum characterslong.

Explanation: The specified database name iseither empty or too long.

User Response: Reissue the command with avalid database name.

DBA3042E The explainable statement textmust be between 1 and maximumcharacters long.

Explanation: The specified explainablestatement text is either empty or too long.

User Response: Reissue the command withvalid explainable statement text.

DBA3043E The query tag cannot have morethan maximum characters.

Explanation: The specified query tag is toolong.

User Response: Reissue the command with avalid query tag.

DBA3044E The user ID cannot have morethan maximum characters.

Explanation: The specified userid is too long.

User Response: Reissue the command with avalid userid.

DBA3045E The valid range for query numberis from 0 to maximum.

Explanation: The specified query number iseither too small or too large.


User Response: Reissue the command with avalid query number.

DBA3046E The valid values for optimizationclass are 0, 1, 2, 3, 5, 7 and 9.

Explanation: The specified optimization class isnot one of the valid values.

User Response: Reissue the command with avalid optimization class.

DBA3047E The database name cannot befound.

Explanation: The database name specified inthe command does not exist in the systemdatabase directory.

User Response: Reissue the command with anexisting database name or catalog the database inthe system database directory.

DBA3059I There is no details informationassociated with the selectedoperator operator.

Explanation: The details information of theselected operator is not available for the currentrelease of the DB2 Administration Tools.


DBA3060I There is no help informationassociated with the selectedoperator operator.

Explanation: The help information of theselected operator is not available for the currentrelease of the DB2 Administration Tools.


DBA3061I There are no column groupsassociated with this table.

Explanation: There were no column groupsdefined on the referenced table at the time ofexplain and there are no column groupscurrently defined in the table.

User Response: No response required.

DBA3062N Generate DDL cannot beperformed on system tables.

Explanation: Tables with schema SYSIBM,SYSCAT, or SYSSTAT are system tables.

User Response: Perform generate DDL onnon-system tables.

DBA3063N One or more system tables havebeen selected for GeneratingDDL. DDL will be generate forselected user tables only. Do youwant to continue?

User Response: Tables with schema SYSIBM,SYSCAT, and SYSSTAT are system tables.

User Response: Click Yes to generate DDL fornon-system tables only. Click No to abortGenerate DDL operation.

DBA3064N Only the first number tables willbe processed by db2look.

Explanation: The db2look -t option will onlyprocess number tables.

User Response: Move the list of selected tablesto the list of available tables.

DBA3065E Snapshot cannot be processed dueto a CLI error.

Explanation: A CLI error has occurred duringsnapshot processing. An access plan cannot bedisplayed.

User Response: Check the CLI configuration byissuing the following command:

db2 get cli cfgfor section <db-name>

If LONGDATACOMPAT is set to 1, trycataloging the database with a different alias:

catalog db <db-name> as <db-alias-name>

Set LONGDATACOMPAT=0 for the databasealias:


db2 update cli cfg for section <db-alias-name> usinglongdatacompat 0

Submit the query for EXPLAIN in the aliasdatabase.

If LONGDATACOMPAT is not set to 1, or theparameter is not being set in the CLIconfiguration, contact IBM Service.

DBA3066E Statement text for a snapshotcontains an empty string.

Explanation: The statement text of an explainrecord contains an empty string. Explainedstatement history cannot be retrievedsuccessfully.

User Response: Check the CLI configuration byissuing the following command:

db2 get cli cfgfor section <db-name>

If LONGDATACOMPAT is set to 1, trycataloging the database with a different alias:

catalog db <db-name>as <db-alias-name>

Set LONGDATACOMPAT=0 for the databasealias:

db2 update cli cfgfor section <db-alias-name> usinglongdatacompat 0

Submit the query for EXPLAIN in the aliasdatabase.

If LONGDATACOMPAT is not set to 1, or theparameter is not being set in the CLIconfiguration, contact IBM Service.

DBA4000W Are you sure you want to stopmonitoring?

Explanation: You have requested to stopmonitoring all database objects that are currentlymonitored and to exit the Performance Monitor.

User Response: Click ″Yes″ to process therequest or ″No″ to cancel it.

DBA4001I There is no monitor summary foryour selection.

Explanation: You requested to show monitoractivity on a level of object in which nothing isbeing monitored. There is no summary activityto be shown.

User Response: Retry the action when amonitor is started on a object that corresponds tothe level you have selected.

DBA4002W Are you sure you want to stopmonitoring name?

Explanation: You have requested to stopmonitoring an object that is currently beingmonitored.


DBA4003I Only the default level is changedfor IBM supplied monitors.

Explanation: For an IBM-supplied monitor, theonly attribute that you can change is the level forwhich this monitor is designated as the default.

User Response:

DBA4004E Multiple selection is only allowedfor the Remove action.

Explanation: You selected more than onemonitor from the list of monitors. The onlyaction you can perform on multiple objects isRemove.

User Response: Deselect all monitors exceptone from the list and retry the action.

DBA4005W Are you sure you want to removethe selected monitors?

Explanation: You requested to remove theselected monitors from the list.

User Response: Click ″Yes″ to process the


request or ″No″ to cancel it.

DBA4006W Are you sure you want to resetthe counters?

Explanation: You requested to reset thedatabase counters.


DBA4007W Are you sure you want to stopmonitoring all objects in thislevel?

Explanation: You have requested to stopmonitoring all objects in this level that arecurrently being monitored.


DBA4008W Are you sure you want to stopmonitoring all partitions in thisobject?

Explanation: You have requested to stopmonitoring all partitions in this object that arecurrently being monitored.


DBA4009I The IBM supplied monitors arebeing created.

Explanation: The IBM supplied monitors arebeing created. This may take a while.

User Response:

DBA4010E The Performance Monitorencountered a problem andcannot continue. Retry the action.If the problem persists, take atrace at the client and the server,and contact support personnel.

Explanation: Unexpected error has occurred.

User Response: Take a trace at the client andthe server and contact support.

DBA4011E The program name is not a validname. The program cannot be run.Check the name and retry theaction.

Explanation: You have specified an invalidprogram name.

User Response: Specify a valid program nameand retry the action.

DBA4012E The program name cannot be run.The currently executing thread isnot allowed to execute thespecified program.

Explanation: A security exception is thrownwhen executing the program specified. Runcommand works in application mode only.

User Response: Retry the action when you runControl Center as an application.

DBA4013I Database manager node name isdown.

Explanation: From the Tools settings, nodestatus page, you have selected to be informedabout database manager node status when it isdown.

User Response: Restart the database managernode to continue processing.

DBA4014I The state of database managernode name is unknown.

Explanation: From the Tools settings, nodestatus page, you have selected to be informedabout database manager node status when thestate is unknown.

User Response:

DBA4015E name contains invalid input.Please re-enter the entry.

Explanation: Your entry contains invalidcharacter.

User Response: Retry your action with newentry.


DBA4016E New monitor cannot be created.The maximum number ofmonitors is number.

Explanation: The create or save as or copyrequest fails. The maximum number of monitorshas been reached.

User Response: Remove unused monitors andretry your action.

DBA4017E The monitoring connection cannotbe established. The maximumnumber of monitoringconnections is number.

Explanation: The maximum number ofmonitoring connections has been reached.

User Response: Retry your action later or stopany running monitoring session on yourmachine.

DBA4018W Your entry in name is too long.The maximum number ofcharacters is number. Your entry istruncated.

Explanation: Your entry has exceeded the limit.

User Response:

DBA4019E Your entry in name is too long.The maximum number ofcharacters is number. Retry youraction with valid input.

Explanation: Your entry has exceeded the limit.

User Response: Retry the action with validinput.

DBA4020W You made changes to theperformance monitor name. Doyou want to save your changes?

Explanation: You made one or more changes tothe performance monitor that are not yet saved,and you requested to exit from the ShowMonitor window or set the running monitor adifferent monitor. Your changes will be lostunless you click Yes.


DBA4021W You made changes to theperformance variable settings forname. Do you want to apply yourchanges to the next snapshot?

Explanation: You made one or more changes tothe performance variable settings that are not yetsaved, and you selected a different performancevariable to work with. Your changes will be lostunless you click Yes.

User Response: Click ″Yes″ to apply thechanges to the next snapshot of ″No″ cancel it.

DBA4023E You entered a combination ofalarm and warning thresholdvalues that is not valid forperformance variable name.Change one or more thresholdvalues and try again.

Explanation: The upper alarm threshold valuemust be greater than the upper warningthreshold value and so on; that is, upper alarmthreshold value > upper warning threshold value> lower warning threshold value > lower alarmthreshold value. The threshold value is a float nolonger than 9 digits.

User Response: Verify the threshold values andtry the operation again.

DBA4024W The Summary page cannot showmore than number columns. Turnto the Details page to see all theperformance variables.

Explanation: The Summary page currentlydisplays as many columns as it canaccommodate, but some performance variablesare not shown.

User Response: Turn to the Details page to seeall the performance variables.


DBA4025W The type view cannot show morethan number performancevariables.

Explanation: The maximum number ofperformance variables are shown.

User Response: Remove one or moreperformance variables from the type view beforeadding more.

DBA4026E A non-applicable monitor hasbeen set as default for this level.

Explanation: The monitor must include at leastone performance variable for this level.

User Response: Modify the monitor to includeat least one performance variable for this level.

DBA4027I Monitoring has not been startedas there is nothing to monitor.

Explanation: Currently there are no databasesor gateway connections to be monitored for thisinstance.

User Response: Catalog a database or gatewayconnection to start monitoring.

DBA4060E The Performance Monitor iscurrently active with anothermonitor for this instance.

Explanation: Only one monitor can be active ata time per instance. For example, if your defaultmonitor for databases is different from yourdefault monitor for connections, you will not beable to monitor databases and monitor (or list)connections at the same time.

User Response: In the List Monitors window,you can:

1. Find out which monitor is running and stopit so you can specify a different one.

2. Find out which monitor is running andspecify it for your next monitoring action.

3. Create a monitor that contains performancevariables for all levels, and then select it asyour default monitor for each level.

DBA4065E The threshold value cannot beblank or contain more than 9characters. Enter a valid thresholdvalue.

Explanation: You entered a threshold valuewhich is not valid or your value has beenmodified internally. For example, 123456789 willbe modified to 123,456,789.0 which exceeds thenumber of characters allowed in the threshold.

User Response: Re-enter the threshold valueand retry your action.

DBA4070E The JDBC server encountered aproblem. The list of performancemonitors could not be processed.

Explanation: An unexpected problem isencountered.

User Response: Verify that the JDBC server isup and running. If it is, take a trace at the JDBCserver and then contact support personnel.

DBA4071W Some monitors are currently inuse locally. The refreshed listshows local monitors only.

Explanation: The list of monitors is refreshedwith local monitors only.

User Response: To show the complete list, stopthe active monitors and retry the operation.

DBA4072E This monitor name already exists.Specify a unique name.

Explanation: Performance monitor names in aJDBC server must be unique regardless of themonitor’s creator.

User Response: Specify a unique monitor name.

DBA4074E The JDBC server encountered aproblem. The operation could notbe performed.

Explanation: An unexpected problem isencountered.

User Response: Verify that the JDBC server is


up and running. If it is, take a trace at the JDBCserver and then contact support personnel.

DBA4075E This performance monitor isempty so it cannot be saved. Addat least one performance variableto the monitor and retry theoperation.

Explanation: Monitors need to contain at leastone performance variable in order to be valid.

User Response: Add at least one performancevariable to the monitor and retry the operation.

DBA4076E The action cannot be performedbecause you are not the creator ofthe monitor.

Explanation: You must own the monitor to beable to change, rename or remove it.

User Response: If you were trying to change amonitor, copy it under a different name and thenchange it.

DBA4079E This monitor is currently in uselocally. Stop the monitor, and thenremove or rename it.

Explanation: You cannot remove or rename anactive monitor.

User Response: Stop the monitor beforeremoving or renaming it.

DBA4080E This monitor is currently in useremotely. Wait till the monitor isstopped, and then remove orrename it.

Explanation: You cannot remove or rename anactive monitor.

User Response: Wait till the monitor is stoppedbefore removing or renaming it.

DBA4083E This monitor could not be found.Another user might have removedit. Stop all monitoring and thenrefresh your list of monitors.

Explanation: Another user might have removedthe monitor that you are using.

User Response: Stop all monitoring and refreshyour list of monitors.

DBA4090E Connection to the JDBC serverhas ended abnormally. Close theControl Center and retry theoperation. If the problem persists,take a trace at the JDBC serverand contact support personnel.

Explanation: An unexpected error has occurred.

User Response: Close the Control Center andretry the operation. If the problem persists, takea trace at the JDBC server and contact supportpersonnel.

DBA4095I This function has not beenimplemented on this object.

Explanation: This function has been planned fora future release but is not currently implementedon this object.


DBA4220I Full database restore cannot bedone from a table space backupimage.

Explanation: Full database restore cannot bedone from a table space backup image.


DBA4221I Table space selection is notallowed for the media type.

Explanation: Table space selection is notallowed for the media type.



DBA4222I Table space selection is notallowed since the database is inbackup pending state.

Explanation: Table space selection is notallowed since the database is in backup pendingstate.


DBA4223I Full database required whenbackup image information isentered manually.

Explanation: Full database required whenbackup image information is entered manually.


DBA4730E Performance monitoringencountered a problem whileaccessing the monitor server.Monitoring cannot continue.smcode: Error-code

Explanation: See the Administration Servererror logs for more information.

User Response: Contact your technical servicerepresentative with the smcode.

DBA4731E A resource problem occurred onthe Monitor Server. smcode:Error-code


User Response: Free up some server resourceand retry the operation. If the problem persists,contact your technical service representative withthe smcode.

DBA4732E A problem occurred when tryingto attach to the database instance.smcode: Error-code


User Response: Retry the operation. If theproblem persists, contact your technical service

representative with the smcode.

DBA4733W The monitored database instanceis stopped. Restart the instance.smcode: Error-code


User Response: Restart the instance. If theproblem persists, contact your technical servicerepresentative with the smcode.

DBA4734E Performance monitoringencountered a problem whileaccessing the monitor server.smcode: Error-code


User Response: Retry the operation. If theproblem persists, contact your technical servicerepresentative with the smcode.

DBA4735E A problem occurred when tryingto attach to the database instance.smcode: Error-code



DBA4736E Unable to determine the currentterritory code or current code pagein use on the client. smcode:Error-code

Explanation: The client’s territory code andcode page must be sent to the server so that thedata is returned in the correct code page. TheMonitor Server was unable to determine theactive territory code or code page.

User Response: Refer to your operating systemdocumentation to determine how to set theterritory code and active code page for yoursystem. Retry the operation after setting theterritory code and code page.


DBA4737E Unable to set the current clientterritory code or current code pageon the server. smcode: Error-code

Explanation: The client’s territory code andcode page must be sent to the server so that thedata is returned in the correct code page. TheMonitor Server was unable to set the client’sactive territory code or code page on the server.

User Response: Refer to your operating systemdocumentation to determine how to activate theclient’s territory code and active code page onyour server’s system. Retry the operation afteractivating the territory code and code page.

DBA4738E The Administration Server onsystem name is not started.smcode: Error-code

Explanation: The listed Administration Serveron system name is not started.

User Response: Start the Administration Serverand retry the operation.

DBA4739E The client system’s code pagecould not be determined. Theclient system might not be set upcorrectly. smcode: Error-code

Explanation: This is a client system setupproblem.


DBA4740E The client code page name is notavailable on instance name.smcode: Error-code

Explanation: The listed code page has not beeninstalled on instance name.

User Response: Contact your systemadministrator. Your administrator should installcode page name on instance name.

DBA4741E The client code page name is notavailable on instance name, atnode name. smcode: Error-code

Explanation: The listed code page has not beeninstalled on instance name, at node name.

User Response: Contact your systemadministrator. Your administrator should installcode page name on instance name at node name.

DBA4742E The Administration Server namecannot be found. smcode:Error-code

Explanation: Possible reasons for this probleminclude: 1) Remote instance name is not valid.2)Hostname is not valid.


DBA4743E The Administration Server namedetected a problem. sqlcode:Error-code. smcode: Error-code

Explanation: The Administration Server namehad an internal error.


DBA4744E The Control Center could notcommunicate with the paralleltools on instance name at nodename. Try startingcommunications. smcode:Error-code

Explanation: Communications may not havebeen started.



DBA4745E The TCP/IP port configurationbetween the Control Center andits listener (db2cclst) on instancename at node name is not correct.smcode: Error-code

Explanation: The /etc/services file at nodename might contain incorrect information.

User Response: Contact your systemadministrator. Your administrator should checkthat the port name of db2ccmsrv is enteredcorrectly in the /etc/services file on node name.

DBA4746E Instance node host name name isnot valid on instance name.smcode: Error-code

Explanation: The db2nodes.cfg file for instancename might contain incorrect information.

User Response: Contact your systemadministrator. Your administrator should validatethe host name found in the db2nodes.cfg file forinstance name.

DBA4747E The Performance Monitor did notreceive a response from node namewithin the snapshot captureinterval. smcode: Error-code

Explanation: A performance or communicationsproblem on the listed node is preventing aresponse from being sent, or the snapshotcapture interval is not long enough to allow eachnode time to respond to the request.

User Response: Contact your systemadministrator. Your administrator can 1) Validatethe performance on the listed node. 2) Increasethe snapshot capture interval to allow more timefor the node to respond to the snapshot request.

DBA4748E Logical node name on instancename is not valid. smcode:Error-code

Explanation: The db2nodes.cfg file for instancename might contain incorrect information.


DBA4749E The Monitor Server on instancename is unable to establishcommunications with node name.smcode: Error-code

Explanation: The communications subsystemmay not have been started.

User Response: Start the db2cclst process on thenode specified above. If problem still persists,contact your system administrator.

DBA4750E The instance being switched todoes not exist. smcode: Error-code



DBA5006E evname is an Event Monitor thatwrites to a named pipe. EventAnalyzer does not support PIPEEvent Monitors.

Explanation: The Event Analyzer only handlestraces produced by FILE Event Monitors.

User Response: Use a FILE Event Monitor.

DBA5007E Event Monitor event-monitor doesnot exist.

Explanation: The Event Monitor namesspecified with the -evm option could not befound in the catalogs for the database specifiedwith the -db option. The Event Monitor mayhave been dropped or you may be trying toconnect to the wrong database.

User Response: Make sure that the Databasealias specified with the -db is properly catalogedand that the Event Monitor has not beendropped. If the latter is the case, re-create theevent monitor.


DBA5250I The number of records retrievedexceeded the limits of thewindow. A partial list isdisplayed.

Explanation: The window height required todisplay the retrieved objects exceeds a systemlimit.

User Response: You can reduce the number ofobjects displayed in the window by doing thefollowing:

v If the “Include” choice is available on the“View” menu, you can specify a subset of theobjects to display in the window. When youselect “Include”, a window appears andprompts you for a sub set of the criteria.

DBA5300E Event Analyzer invocation error.Usage:db2eva [ - db database-alias

-evm evmon-name ]

Explanation: The command parameters for thedb2eva command are:

-db database-aliasspecifies the database for which theEvent Monitor is defined, as catalogedon the machine where the trace isanalyzed.

-evm evmon-namethe Event Monitor trace tables you wantto analyze. The event monitor must bedefined in the database specified in the-db parameter.

If you specify the database and event monitornames, db2eva connects to the database, andissues a ’select target fromsysibm.syseventmonitors’ to locate the tablewhere the Event Monitor writes its trace. TheEvent Monitor and related tables must not havebeen dropped when using this mode.

If you do not specify any parameter, a dialog boxwill be opened to prompt for the database aliasand the event monitor name you want toanalyze.

User Response: Re-issue the command withvalid arguments.

DBA5311E Event Monitor invocation error.Usage: db2emcrt database-alias

Explanation: The command parameter for thedb2emcrt command is:

database-aliasspecifies the database for which theevent monitors are to be created oranalyzed, as cataloged on the machinethe db2emcrt command is invoked.database-alias overrides the databasename specified in the trace.

User Response: Re-issue the command withvalid arguments.

DBA5350E An error occurred while openingfile file-name.

Explanation: The specified file could not beopened in read-only mode for an unknowncause.

User Response: Check the spelling of thedirectory specified by the -path option, its accessauthority, and that it contains a non-empty,readable trace file called 00000000.evt.

NOTE: The first trace file for an Event Monitor isalways named 00000000.evt and cannot berenamed.

DBA5351E File file-name cannot be found.

Explanation: There is no 00000000.evt file in thedirectory specified by -path.

User Response: Check the spelling of thedirectory specified by the -path option, its accessauthority, and that it contains the trace file00000000.evt.



DBA5352E Path path-name cannot be found.

Explanation: The -path option specifies adirectory that does not exist.

User Response: Check the spelling of thedirectory specified by the -path option, its accessauthority, and that it contains the trace file00000000.evt.


DBA5353E Access to param-1 was denied.

Explanation: The specified file could not beopened in read-only mode. The -path option maybe specifying a directory to which you do nothave sufficient access authority.

User Response:

v Check the access authority to the directoryspecified by the -path option.

v Verify that no one has locked the specified filein exclusive mode.

DBA5354E The data cannot be read fromfile-name.

Explanation: The Event Monitor trace filecontains unexpected data, or cannot be accessed.

The trace file was likely corrupted duringtransmission or has been removed.

User Response: Transmit your trace files fromyour server again. When transmitting trace filesfrom a remote server, ensure that thetransmission is done in binary mode.

DBA5355E An Event Monitor log headercould not be found in file-name.

Explanation: The first file written to by anEvent Monitor is named 00000000.evt andcontains a data structure that identifies the tracecharacteristics. This data structure could not beread. Possible causes:

v The trace file was corrupted.

v The trace file is empty. This can happen if theEvent Monitor is active but, has not flushed itsbuffers yet.

User Response:

v If the trace was transmitted from a remoteserver, retransmit, ensuring that thetransmission is done in binary mode.

v If the trace file is empty, turn off the EventMonitor to force it to flush its buffer.

DBA5356E Byte order not valid in file-name.

Explanation: The Event Monitor log header (thefirst record written to a new trace) specifieswhether the trace contains little-endian (e.g.,OS/2) or big-endian (e.g., AIX) data. The valuefound in the trace file specified neither of thesetwo supported types of data.

The trace file was likely corrupted duringtransmission.

User Response: Transmit your trace files fromyour server again. When transmitting trace filesfrom a remote server, ensure that thetransmission is done in binary mode.

DBA5357E Unexpected data was found atoffset offset-value in file file-name.

Explanation: The Event Monitor trace filecontains unexpected data.

The trace file was likely corrupted duringtransmission.

User Response: Retransmit your trace files fromthe server, ensuring that the transmission is donein binary mode.

DBA5358I Cannot browse local file systemwithout an active localAdministration Server.

Explanation: The file browser requires aDatabase Administration Server (DAS) instanceto browse file systems. If this is a clientinstallation, the DAS instance is not present andlocal file browsing is disabled.

User Response: For server installations, ensure


the DAS instance is started and retry theoperation.

DBA5500E A system error has occurred. TheEvent Analyzer tool could notcontinue processing.

Explanation: For an unknown reason a systemerror has occurred when trying to initialize theapplication environment.

User Response: Re-issue the command.

DBA5501W Do you want to delete the eventfiles associated with the eventmonitor evname that you areremoving?

Explanation:

User Response: To delete the event files for theselected event monitor, click on OK. If you donot want to delete the event files, but still wantthe event monitor removed, click on NO. If youdo not want to remove the event monitor, ordelete the event files click on CANCEL.

DBA5502E No selection was made from thelist of Event types. You mustselect one or more types from thelist.

Explanation: When creating an event monitor,at least one Event type must be selected.

User Response: Select one or more of the Eventtype check boxes from the Create Event Monitorwindow.

DBA5503I An Event monitor evname hasbeen successfully created.

Explanation: The event monitor has beensuccessfully created and has been added to thedatabase list of event monitors.

User Response: Click on OK to remove themessage.

DBA5504W Some event monitors were notremoved because their event filescould not be deleted. See themessages page from the journalnotebook for the list of eventmonitors not removed.

Explanation: Some of the selected eventmonitors may have been successfully removed,but others were not, because their associatedevent trace files could not be deleted.

This occurs when either event files are read-only,or they are being used by another active process.

User Response: See the message page of thejournal notebook for the list of event monitorsthat were not removed. To delete the files, endthe process using them and check the accessauthority for the files. Then select the eventmonitor from the list of event monitors andchoose remove from the menu.

DBA5505E Maximum file size was notspecified.

Explanation: If maximum file size in 4K pagesis selected on the create event monitor Optionswindow, then the maximum size of the eventfiles must be specified.

User Response: Enter a maximum file size ofbetween 1 and 2,147,483,647 4K pages, or youcan select the No Maximum option. If the NoMaximum option is selected, the maximumnumber of event files is 1.

DBA5506E Maximum number of files wasnot specified.

Explanation: If Maximum number of files isselected on the create event monitor Optionswindow, then the maximum number of eventfiles must be specified.

User Response: Enter a maximum number ofevent files of between 1 and 2,147,483,647, or youcan select No Maximum option.


DBA5507E Buffer size was not specified.

Explanation: An event monitor Buffer size in4K pages must be specified.

User Response: You must enter an eventmonitor buffer size of between 1 and2,147,483,647 4K pages.

DBA5508W Do you want to delete the eventfiles associated with the eventmonitors that you are removing?

User Response: To delete the event files for theselected event monitors, click on OK. If you donot want to delete the event files, but still wantthe event monitors removed, click on NO. If youdo not want to remove the selected eventmonitors, or delete the event files click onCANCEL.

DBA5509E The name entered for the eventmonitor is not valid.

Explanation: The name entered in the eventmonitor Name field contains one or morecharacters that are not allowed. An eventmonitor can contain alphanumerics and mustbegin with a letter.

User Response: Remove from the name anycharacters that are not alphanumeric and makesure the name begins with a letter.

DBA5510E When trying to activate themonitor, the directory for its datafiles was not found.

Explanation: When activating an event monitor,the directory that was specified when the eventmonitor was created must exist. In order to flushits buffers, an event monitor needs an existingfile and path.

User Response: Create the directory that wasspecified when creating the event monitor. Try toactivate the event monitor again.

DBA5511E Entry name is not valid becausethe value is out of the acceptablerange.

Explanation: The values for an event monitor’sMaximum file size, Maximum number of files,and Buffer size must be between 1 and2,147,483,647.

User Response: Enter a value in the entry fieldsthat is within the given range.

DBA5512E The character character entered forthe event monitor name is notallowed.

Explanation: A character entered in the eventmonitor name entry field is not a valid characterfor an event monitor name.

User Response: Remove from the event monitorname any characters that are not alphanumericand make sure the name begins with a letter.

DBA5513E The dynamic link library“DB2EVA.DLL” could not beloaded successfully.

Explanation: During the initialization of theevent analyzer the dll could not be loadedbecause the dll has been deleted or removed.

User Response: Reinstall the event analyzer byselecting the performance monitor during theinstallation process.

DBA5514I The event files for event monitorevname could not be deleted.

Explanation: The event files for the eventmonitor could not be deleted because the filesare being used by an active process or areread-only.

User Response: To delete the files, end theprocess that is using them and check the accessauthority for the files. Select the event monitoragain and choose remove from the menu.


DBA5515E The database alias name ordatabase name dbname could notbe found.

Explanation: The alias name that was enteredon the command line has not been cataloged onthis machine.

User Response: Either catalog the alias on thismachine and reenter the command or re-issuethe command with a valid alias name.

DBA5516W Viewing the trace for this eventmonitor may take some time. Doyou wish to continue processing?

Explanation: The user has requested to view alarge trace for an event monitor. Reading the filescould take some time to complete.

User Response: If you want to continueprocessing the trace click on OK. If you do notwish to continue processing the trace file thenclick on NO.

DBA5517E The event monitor could not bestarted due to a reason code ofreason-code.

Explanation: The event monitor could not bestarted for the reason specified by reason-code:

1. The event monitor path is invalid.

2. The device, where the event monitor is to bestarted, is not ready.

3. Attachment to the admin server failed.

User Response: To start the event monitor,make sure that the event monitor path is valid,the admin server started, and the properauthorities exist on the device. Click on OK.

If the problem persists, manually create the eventmonitor directory on the device and click on OK.

To create the event monitor without starting it,deselect the Start now check box and click onOK.

DBA5518E The event monitor could not bestarted because its outputdirectory could not be created.

Explanation: The directory could not be createdfor one of the following reasons.

1. Proper authorities do not exist for creatingdirectories on the requested file system.

2. Create event monitor does not supportdirectory creation on non-Intel platforms.

3. Cannot create a directory of greater than 8characters on a FAT file system.

User Response: Make sure the properauthorities exist for directory creation.

On non-Intel platforms create the event monitoroutput directory manually.

DBA5519I Event monitor table cannot befound in the event sourcedatabase.

Explanation: The event monitor table that holdsthe event monitor records cannot be found in thesource database specified.

User Response: Ensure that the event monitortable exists in the source database and the tablename is in the SYSIBM.EVENTTALBLES.

DBA5520E Event monitor control tablecannot be found in the eventsource database.

Explanation: The event monitor control tablecannot be opened.

User Response: Ensure that the event monitorcontrol table exists in the source database andthe table name is in theSYSIBM.EVENTTALBLES.

DBA5521I Connection to the database is notestablished. The event monitorlist cannot be retrieved.

Explanation: A connection to the database is notestablished.

User Response: Please make sure the database


manager command has been issued. If theproblem persists, contact IBM Service.

DBA6001I The replication subscription set,subscription-set, is in use. Please tryagain later.

Explanation: The Apply program is currentlyprocessing the replication subscription and thisaction cannot be deactivated. Wait until theApply program has completed its processing andretry your command.


DBA6002I The replication source,source-name-1.source-name-2, wasdefined successfully. To begincapturing changes to thereplication source, start theCapture program from thecommand line.

Explanation: The Capture program requires adefined replication source in order to run.

User Response: Make sure the Captureprogram is running.

DBA6003I The replication subscription wasdefined successfully. To beginreplicating the subscription set,ensure that the Apply programhas been started from thecommand line.

Explanation: The Apply program requires adefined replication source in order to run.

User Response: Make sure the Apply programis running.

DBA6004I The replication subscription wassuccessfully changed.

Explanation: This is for your information only.


DBA6005I The replication sources weresuccessfully removed.



DBA6006I The replication source,source-name, could not be removed.



DBA6007I The replication subscription,subscription-name, could not beremoved.



DBA6008I The replication subscriptions weresuccessfully removed.



DBA6009I file-name is locked by anotheraction.

Explanation: The file is currently being used byanother action.

User Response: Wait until the action iscompleted and retry your command.

DBA6010I The join was successfully defined.




DBA6012I The replication source wasdefined successfully. To begincapturing changes to thereplication source, ensure that theCapture program has been startedfrom the command line.

Explanation: The Capture program requires adefined replication source in order to run.

User Response: Make sure the Captureprogram is running.

DBA6013I The replication subscription wassuccessfully updated.



DBA6014I The replication subscription wassuccessfully cloned.



DBA6015I The SQL statements for thisaction have been saved in a filefor future editing and execution.



DBA6016I The SQL script file has been runsuccessfully.



DBA6100I The Apply program will onlyperform full refresh copies to thisset.



DBA6101E The table, table-name-1.table-name-2,cannot be found.

Explanation: The control table specified couldnot be located in the database or wasaccidentally dropped.

User Response: Create the control table. See theTables Chapter for more details.

DBA6102I This action may take some time tocomplete. Please wait...



DBA6103E The SQL file, file-name, cannot berun.

Explanation: The user may have edited the SQLstatement file for a replication action, such asdefining a replication source, and there is anerror in the SQL statement file.

User Response: Correct the error in the SQLstatement file and run the file again.

DBA6104W No unique prefix character wasfound. The prefix character willbe set to NULL.

Explanation: A prefix character is analphabetical or numerical character used todistinguish before-image columns in the sourcetable. If a prefix character connot be assignedbecause all possible prefix characters are alreadyin use, you will receive this warning. The changedata table cannot be created.

User Response: Uncheck the before-imagecolumns and rerun the action.

DBA6105E The field, field-name, requires yourinput.

Explanation: The user has not filled in arequired field.


User Response: Specify a parameter and selectOK.

DBA6106E The replication action does notcurrently support this databasesystem.

Explanation: The replication action mustsupport your database system in order to run.

User Response: Contact your IBM Servicerepresentative.

DBA6107E Please enter a different value forthe field, field-name.

Explanation: When cloning a replicationsubscription, the target server and Applyqualifier fields must be different from theoriginal target server and Apply qualifier fields.

User Response: Enter a different target servername or Apply qualifier and select OK.

DBA6108E The action cannot be completeddue to a syntax error.

Explanation: The SQL statement contains asyntax error.

User Response: Check the SQL reference for theproper syntax. For subscription actions, check thewhere clause, the rows page, or the CREATEcolumn. For define-join actions, check theCREATE VIEW statement.

DBA6109E SHOW COLUMNS action cannotbe completed.

Explanation: The SHOW COLUMNS actionrequires that a table be selected.

User Response: Select a table from the SelectedTable list box and then press the SHOWCOLUMNS key.

DBA6110E The SQL file, file-name, cannot beopened.

Explanation: The SQL file either does not exist,is in the wrong subdirectory, or is engaged inanother process.

User Response: Make sure you enter the correctfile name and that the file is in the correctsubdirectory. If the file is engaged in anotherprocess, terminate the process and reenter the filename.

DBA6111E The file, file-name, cannot beopened.

Explanation: The file either does not exist or isin the wrong subdirectory.

User Response: Make sure you enter the correctfile name on the Replication page of the ToolSettings notebook.

DBA6112I You have chosen to substituteuser-defined values to definereplication objects in the ToolSettings notebook. Please supplythese values in the file file-name.


User Response: No action is required if youhave already supplied user-defined values in thefile.

DBA6113E keyword is an invalid keyword infile file-name.

Explanation: The specified keyword is invalidand may be a typographical error.

User Response: Use the keywords as given inthe default file ″DPREPL.DFT″.

DBA6114E The value for keyword keywordcannot be found in file file-name.

Explanation: The value of this keyword isrequired for this action to complete.

User Response: Specify a value for thiskeyword in the file.


DBA6115E None of the items in the columnlist were selected. This actioncannot be completed.

Explanation: At least one item in the columnlist must be selected for this action to complete.

User Response: Select one or more items fromthe column list and press OK.

DBA6116E The value for keyword keyword isinvalid in file file-name.

Explanation: The value of this keyword is eithertoo long, an incorrect data type, or in anincorrect format.

User Response: Correct the value and invokethe action again.

DBA6117W The before-image columncolumn-list was truncated to numberbytes because the length of theoriginal column was at thedatabase limit before beingappended to the before-imageprefix before-image-prefix.

Explanation: The length of the column from theoriginal source table was at the database limit.When appended to the before-image prefix, somecharacters at the end of the column name weretruncated to fit the database limit. This newbefore-image column name may no longer beunique because the truncated characters may beneeded to guarantee a unique name.

User Response: Uncheck the before-imagecolumn when the truncated name is not uniqueand rerun the action.

DBA6118W Datatypes datatype-list are notsupported on the databasedatabase. The datatypes will beconverted to datatype-list in theSQL script.

Explanation: Some datatypes from the sourceare not supported on the named database.However, equivalent datatypes could be foundon the named database. The generated SQL

statements will use the converted datatypes inplace of the unsupported datatypes.

User Response: No action is necessary if theconverted datatypes are acceptable. If they arenot acceptable, uncheck the target columns andrerun the action.

DBA6119W Datatypes datatype-list are notsupported on the databasedatabase. The columns containingthese datatypes will be excludedfrom the SQL script.

Explanation: Some datatypes from the sourceare not supported on the named database. Noequivalent datatypes could be found on thenamed database. The generated SQL statementswill exclude any columns containing theunsupported datatypes.

User Response: Contact IBM service if youwould like to recommend a specific datatype besupported on the named database in the future.

DBA6120W The source table table-name wasnot defined with a primary key.Specify a primary key for thetarget table in the Target Columnspage.

Explanation: The define subscription actioncould not find a qualifying primary key for thesource table, therefore the define subscriptioncould not determine an appropriate primary keyfor the target table.

User Response: Specify a primary key for thetarget table in the Target Columns page of theAdvanced notebook.

DBA6121W An incompatible Java RuntimeEnvironment has been detected.Please verify that the requiredlevel of the Java RuntimeEnvironment has been installed.

Explanation: The installed Java runtime is notsupported by the DB2 Java application.

User Response: Refer to the Control Centerreadme.htm for information on prerequisite Java


Runtime Environment levels.

DBA6123E The requested action cannot beperformed because the schemanames of the objects exceednumber bytes in length.

Explanation: The data replication componentssupport schema names up to 18 bytes in length.You tried to perform a replication action againstobjects that have longer schema names. Theaction cannot be performed.

User Response: Select objects whose schemanames are 18 bytes or less, and perform theaction again.

DBA6124W The requested action cannot beperformed on some of the objectsyou selected because the schemanames of the objects exceednumber bytes in length.

Explanation: The data replication componentssupport schema names up to 18 bytes in length.You tried to perform a replication action againstsome objects that have longer schema names.The action will be performed only on thoseobjects whose schema names are 18 bytes or less.


DBA6125W The field field, contains a schemaname exceeding number bytes inlength. The schema name will betruncated to number bytes.

Explanation: The data replication componentssupport schema names up to 18 bytes in length.The schema name in the field exceeds 18 bytesand it will be truncated to 18 bytes.

User Response: No action is required. However,you can type a shorter schema name in the field,if you do not want the existing schema nametruncated.

DBA7000E The license for product-name couldnot be removed. RC = return-code.

Explanation: The license could not be removed.Either the license could not be found in thenodelock file or the nodelock file could not beupdated.

User Response: Check the permissions of thenodelock file and that the license exists in it.

The location of the file is platform specific:

v AIX - /var/ifor/nodelock

v Windows operating systems -$DB2PATH/license/nodelock

v All other operating systems -/var/lum/nodelock

DBA7001E The license could not be added tothe nodelock file. RC = return-code.

Explanation: There was an error transmittingthe license file or installing the license.

User Response: Please check the permissions ofthe nodelock file. The location of the file isplatform specific:

v AIX - /var/ifor/nodelock

v Windows operating systems -$DB2PATH/license/nodelock

v All other operating systems -/var/lum/nodelock

Alternatively you can also add the license usingthe command line utility db2licm.

If the problem persists please contact IBMService.

DBA7002E The license certificate is invalid.Please try the command againwith a valid license file. RC =return-code.

Explanation: The license certificate contained inthe file specified does not contain a valid db2license or is in an unrecognizable format.

User Response: Please obtain a valid DB2


license certificate from your IBM representativeor authorized dealer.

DBA7003W The list of current users could notbe retrieved. RC = return-code.

Explanation: The daemon or service that tracksthe users is not functioning correctly or has notbeen started. You must have either theconcurrent user policy or registered user policyactivated.

User Response: Turn on a either the concurrentuser policy or registered user policy and restartall the instances.

If the problem persists contact IBM Service.

DBA7004E The registered user could not beremoved from the registered userlist. RC = return-code.

Explanation: The registered user list on theserver could not be updated with the changesyou have requested.

User Response: Check to make sure the userexists and that this is a valid action for thisproduct. If the problem persists contact IBMService.

DBA7005E The registered user could not beadded. RC=return-code.

Explanation: The registered user list on theserver could not be updated with the changesyou have requested.

User Response: Check to make sure theusername is valid and ensure that the registereduser policy is valid for this product. If theproblem persists contact IBM Service.

DBA7006E The license policy could not beupdated. RC = return-code.

Explanation: The attempt to update the licensepolicy for this product did not succeed.

User Response: Please restart the instance andthe License Server using the command db2licd

-xxx or on Window NT by using the ServicesControl Manager.

If the problem persists contact IBM Service

DBA7007E The statistics regarding licenseusage could not be retrieved. RC= return-code.

Explanation: Either the statistics are corrupt,there was a communication error, or no data isavailable. Data is generated on connects anddisconnects after a policy is updated and theinstances are restarted.

User Response: If the statistics are corrupt youcan remove the statistics database. This willremove all previously collected statistics. Thelocation is platform specific and depends onwhere the product is installed.

v UNIX - DB2 installationdirectory/misc/db2licst

v Windows operating systems -DB2 installationdirectory\license\db2licst.dat

DBA7008I The license policy will not takeeffect fully until the instances arerestarted.

Explanation: When the instances are restarted itrereads the license configuration.

User Response: Restart the instances on theserver.

DBA7009E This product product does notsupport the specified licensepolicy. RC = return-code.

Explanation: The license policy specified is notavailable for use with this product.

User Response: Specify a valid license policy.

DBA7010E The License Center was unable toretrieve a list of products from thespecified server. RC = return-code.

Explanation: The list of products on this servercould not be obtained.

User Response: Please restart the


administration instance and the Control Centerand try again. If the problem persists contactIBM Service.

DBA7011E You do not have proper authorityto perform the specified action.

Explanation: The user does not have permissionto perform this operation.

User Response: Please login with a userid thathas the proper permissions to perform thiscommand.

DBA7012E No statistics are available for thespecified time period.

Explanation: No statistics are available for thetime period that you specified.

User Response: Please enter a valid date rangewhere statistics exist.

DBA7013E The license certificate filenamecould not be found. Please try thecommand again with a validlicense file. RC = return-code.

Explanation: The file specified does not exist orcannot be read.

User Response: Please obtain a valid DB2license certificate from your IBM representativeor authorized dealer.

DBA7014E Restart the Control Center and theadministration instance and trythe command again.

Explanation: Restart the Control Center and theadministration instance and try the commandagain.

User Response: If the problem persists pleasecall IBM Service.

DBA7015E The license for DB2 OLAP Servercannot be updated. The DB2OLAP processes are currentlyactive.

Explanation: DB2 cannot update the license forDB2 OLAP Server while DB2 OLAP Server isrunning.

User Response: To update your OLAP license,please stop all OLAP processes and reinstall thisDB2 license.

DBA7016E The selected system does not haveany instances specified.

Explanation: A valid DB2 instance for theselected system was not found. Verify that youhave properly cataloged at least one valid DB2instance residing on the selected DB2 system.

User Response: Catalog a valid DB2 instancefor the selected system, restart Control Centerand try the command again.

DBA7017E No valid DB2 instances werefound on the selected system.

Explanation: A valid DB2 instance for theselected system was not found. Verify that theselected systems has at least one working DB2instance.

User Response: Create a valid DB2 instance onthe selected system and try the command again.

DBA7100W The file file-name could not beopened. The page page-name in theInformation Center, whichcorresponds to that file, will notbe shown.

Explanation: The data for the InformationCenter is stored in a number of NDX files. Thefile file-name might be missing from the correctdirectory.

User Response: Ensure that the NDX files areinstalled on the file system.

Pages in the Information Center and theircorresponding NDX files:


v Concepts - db2booksuc.ndx

v Tasks - db2tasksuc.ndx

v Reference - db2refsuc.ndx

v Troubleshooting - db2msgsuc.ndx

v Sample Programs - db2sampsuc.ndx

v Tutorials - db2webuc.ndx

DBA7101E The Information Center cannot bedisplayed because none of theInformation Center’s NDX filescan be opened.

Explanation: The Information Center must readat least one NDX file to display any links to DB2information.

The data for the Information Center is stored in anumber of NDX files. The files might be missingfrom the file system.

User Response: Ensure that the NDX files arelocated in the file system.

Pages in the Information Center and theircorresponding NDX files:

v Concepts - db2booksuc.ndx

v Tasks - db2tasksuc.ndx

v Reference - db2refsuc.ndx

v Troubleshooting - db2msgsuc.ndx

v Sample Programs - db2sampsuc.ndx

v Tutorials - db2webuc.ndx

DBA7102W The file file-name is not formattedproperly. The following lineswere ignored: line-numbers. Ensurethat these lines are formattedcorrectly.

Explanation: Each line in an NDX file must bein the form of a comma-separated list. Here is anexample:

"IBM",1,"IBM Home Page",http://www.ibm.com

The format of the list is as follows:

1 The name of the entry as it appears inthe tree or list of items in theInformation Center

2 The number representing the categoryof this entry

3 The description that appears on thestatus line when this item is selected

4 The full Web address indicating thelocation of the entry

User Response: If you have edited this file,ensure that each line is formatted properly asfollows:

v The name and description must start and endwith double quotation marks.

v The name and description cannot contain anydouble quotation marks.

v Use commas as separators.

v The first entry in the file is a numbercorresponding to the number of entries in thefile. You must update this number manually ifyou add or remove entries.

DBA7200E A maximum of 10 columns can beselected as input to a geocoder.

Explanation: More than 10 columns wereselected as input to a geocoder.

User Response: Move column names from theSelected columns box to the Available columnsbox until the Selected Columns box lists 10names or fewer.

DBA7201E The database is not enabled toperform Spatial Extenderoperations.

Explanation: The database must be enabled forSpatial Extender before you can perform SpatialExtender operations.

User Response: Right-click the database andselect Spatial Extender->Enable from the menu.

DBA7300W Database database-name cannot bedisplayed because it does nothave a valid node cataloged.

Explanation: There is no entry in the nodedirectory corresponding to the node name


provided for the specified database in thedatabase directory.

User Response: Ensure that there is a nodecatalog entry corresponding to the node at whichthe database was cataloged.

DBA7301W There are no instances to displayin the Health Center.

Explanation: There are no entries in the nodecatalog and DB2INSTANCE is not set.

User Response: Catalog a node or specify thedefault DB2 instance on the client.

DBA7302E Alert information cannot beretrieved for instance instance-nameor any of its objects because theinstance catalog partition is down.

Explanation: The health monitor cannot bequeried for alert information because the instancepartition and monitor are down.

User Response: Restart the partition and try theaction again.

DBA7303E Alert information cannot beretrieved for instance instance-nameor any of its objects because theinstance is down.

Explanation: The health monitor cannot bequeried for alert information because the instanceand monitor are down.

User Response: Restart the instance and try theaction again.

DBA7304W The object that was selectedobject-name is no longer presentunder the current toggle filter.

Explanation: The selected object changed stateon the most recent refresh of the data. Therefore,the object is no longer viewable in the navigationview on the current toggle filter selection.

User Response: Select another instance ordatabase from the current toggle filter selection

or select a different toggle button to view otherstates.

DBA7405E The alert that was selected nolonger exists.

Explanation: The selected alert no longer existsin the health monitor.

User Response: If the NOTIFYLEVEL setting isset to include the alert type, go to the JournalNotification Log page to see details on the alert.

DBA7306E The alert no longer exists. Do youwant to close the Details dialog?

Explanation: The current details dialog isshowing information on an alert that no longerexists.

User Response: Click on Yes to close the dialog,or click on No to leave the details dialog open.

DBA7307W The database managerconfiguration parameter value haschanged since the dialog was lastrefreshed. Do you want tocontinue?

Explanation: The value for the configurationparameter was changed since this details dialogwas last refreshed.

User Response: Click on Yes to apply thechange and overwrite the current setting, or clickon No to return to the details dialog. If you clickon No, refresh the contents of the dialog to seethe current setting of the configurationparameter.

DBA7308W The database configurationparameter value has changedsince the dialog was lastrefreshed. Do you want tooverwrite the current value?

Explanation: The value for the configurationparameter was changed since this details dialogwas last refreshed.

User Response: Click on Yes to apply thechange and overwrite the current setting, or click


on No to return to the details dialog. If you clickon No, refresh the contents of the dialog to seethe current setting of the configurationparameter.

DBA7309W One or both threshold settingvalues have changed since thedialog was last refreshed. Do youwant to overwrite the currentvalues?

Explanation: The value for the warning and/oralarm thresholds have changed since the detailsdialog was last refreshed.

User Response: Click on Yes to apply thechange and overwrite the current setting, or clickon No to return to the details dialog. If you clickon No, refresh the contents of the dialog to seethe current setting of the threshold values.

DBA7310I The threshold settingconfiguration updates have beenapplied.

Explanation: The threshold setting configurationupdates have been applied.


DBA7311I The configuration parameterupdate has been applied.

Explanation: The configuration parameterupdate has been applied. It can take some timebefore the changes take effect.


DBA7312I The configuration settings havebeen reset to the original installdefault settings.

Explanation: The configuration settings havebeen reset to the original install default settings.These health indicator settings were used atproduct install time as the initial settings for thehealth monitor.


DBA7313I The configuration settings forobject object-name have been resetto the current object defaulthealth indicator settings.

Explanation: The configuration settings for thespecified object have been reset to the currentobject default health indicator settings. Thesesettings are based on the global health indicatordefault settings for the object type of thespecified object.


DBA7314W The updated configurationsettings can be applied to existingobjects. Do you want to propagateall changes to existing objects andoverwrite current settings onthose objects? If you select No,only the default settings will beupdated.

Explanation: The new global default healthindicator settings can be propagated to allexisting objects that are affected based on theobject type for the changed health indicators. Theglobal settings can be updated withoutpropagating changes to existing objects.

User Response: Click on Yes to apply the globaldefault health indicator updates and thesechanges to existing objects, or click on No toapply only the global default health indicatorsetting updates.

DBA7315W You must provide a script locationthat is accessible by all partitionsfor the action to succeed on allpartitions. Do you want tocontinue creating the script?

Explanation: The script being defined must beaccessible to all partitions for the alert action tosucceed on all partitions.

User Response: Click on Yes to continuecreating the script, or click on No to return to theScript Details dialog.


DBA7316E You have chosen a start recordvalue greater than the highestrecord number in the notificationlog. No records can be returned.

Explanation: There are fewer records in thenotification log than specified as the argumentfor start record. No records can be displayed.

User Response: Decrease the start recordnumber in the filter condition.

DBA7317W You have chosen an end recordvalue greater than the highestrecord number in the notificationlog. Do you want to continue?

Explanation: The notification log has fewerrecords that are specified as the end recordcount. Log records can only be retrieved to theend of the file.

User Response: Click on Yes to retrieve all thelog records up to the end of the file, or click onNo to change the filter condition.

DBA3718I There are currently number alertsin the Health Center. For moredetails, launch the Health Centerfrom the toolbar or from thebeacon on the status line.

Explanation: There are current alerts to beviewed in the Health Center.


DBA7319E The selected instance instance-namehas been dropped since the lastrefresh.

Explanation: The selected object no longerexists so alert information cannot be retrieved.

User Response: Recreate the object and re-trythe action.

DBA7320E The selected databasedatabase-name has been droppedsince the last refresh.

Explanation: The selected object no longerexists so alert information cannot be retrieved.


DBA7321E The object object-name for whichthis alert was generated has beendropped. The requested actioncannot be completed.

Explanation: The selected object no longerexists so the action cannot be completed.


DBA7323I Removing the contact from thecontact list does not change anyconfigured notification settings inthe Task Center or HealthMonitor.

Explanation: Any notification actions using theremoved contact will not be updated. Thesenotification actions will fail.

User Response: Remove any notification actionsinvolving the removed contact.

DBA7324I Contact contact-name selected fornotification no longer exists. Thecontact has been removed fromthe selected list.

Explanation: Invalid contacts have beenremoved from the list selected for healthnotification.


DBA7325W There are unsaved changes in thedialog. Do you want to discardthe changes and refresh thedetails?

Explanation: You have chosen the refresh orreset option on this dialog. All unapplied


changes will be discarded.

User Response: Select No, if you want to retainthe changes. Otherwise, select Yes to discard anyunapplied changes.

DBA7326E No scheduler systems could befound. Task actions cannot bespecified.

Explanation: No scheduler systems arecataloged in the admin node directory. Therefore,no tasks can be located for the Select Tasksdialog.

User Response: Ensure the DB2 AdministrationServer for the scheduler system is cataloged inthe admin node directory.

DBA7327I The configuration parameterupdates have been applied. Thesechanges to the global object typedefaults do not affect existingsettings for specific databaseobjects.

Explanation: The updated configuration settingsapply only to the global default health indicatorsettings. If you have previously specified settingsfor a health indicator on a particular object, thosesettings will not be affected by these changes.


DBA7328I Evaluation has been disabled onthe health indicator for theselected alert. The health indicatorwill not be evaluated on theHealth Monitor refresh.

Explanation: The alert configuration for thehealth indicator of the selected alert has beenupdated to disable evaluating thresholds orstates. This change will not be reflected in theHealth Center until the next time the healthmonitor refreshes.


DBA7500N The threshold value specified isnot within the threshold range.

Explanation: The threshold value specified isnot valid. It has been reset to its previous value.

User Response: Specify a value within the validrange.

DBA7501N The configuration parameter valuespecified is not within the validrange.

Explanation: The configuration parameter valuespecified is not valid. It has been reset to itsprevious value.

User Response: Specify a value within the validrange.

DBA7502N The specified configurationparameter value is not valid.

Explanation: The configuration parameter valuespecified is not valid. It has been reset to itsprevious value.

User Response: Specify a valid configurationparameter value.

DBA7503N The specified threshold value isnot valid.

Explanation: The threshold value specified isnot valid. It has been reset to its previous value.

User Response: Specify a valid number.

DBA7504N An instance attachment isrequired to invoke MemoryVisualizer.

Explanation: Memory Visualizer requires aninstance attachment in order to be able to displaythe memory utilization and allocation.

User Response: Select or specify a version 8.1instance or higher.


DBA7510W The action is not currentlyavailable with this version of theDB2 server. For this action, theDB2 server must be at leveldb2-version.

Explanation: The Control Center client and theDB2 Server are at different levels. The requestedaction is not available for the current level of theDB2 server. The DB2 server must be at leveldb2-version.

User Response: Upgrade the DB2 server to therequired level.

DBA7511W The action is not currentlyavailable with this version of thedatabase. For this action, thedatabase must be at leveldb-version.

Explanation: The requested action is notavailable for the current level of the database.The database must be at level db-version.

User Response: Upgrade the database to therequired level.

DBA7512W The action is not currentlyavailable because the requiredlicense is not found.

Explanation: The requested action is notavailable because the DB2 Administration Serveris not started or because the license is notinstalled.

User Response: Ensure the DB2 AdministrationServer is started and that the required license isinstalled.

DBA7513W The action is not currentlyavailable.

Explanation: The action may not be availablefor the following reasons:

1. The correct license is not installed

2. The correct product is not installed.

3. The Control Center client and the DB2 Serverare at different levels.

4. The DB2 Administration Server is not started.

User Response:

1. Ensure the proper license is installed.

2. Ensure the product is installed.

3. Ensure the client and the server are at thesame level.

4. Ensure the DB2 Administration server isstarted.

DBA7514W A satellite control database couldnot be found for the instanceinstance.

Explanation: A satellite control database doesnot exist in instance instance, or it is notcataloged in the database directory.

User Response: To work with a satellite controldatabase in instance instance, ensure that it iscreated and cataloged in the database directory.Or you can work with satellite control databasesin other instances (if any).

DBA7515W Since the database is a down levelserver, new options that are notavailable in previous versionshave been removed or disabled.

Explanation: Since you are connected to a downlevel server, the new options that are notavailable on your server version have beendisabled or are no longer available.

User Response: Complete the dialog, and runthe command.

DBA7516N Memory Visualizer could not findthe specified data file.

Explanation: The specified file does not exist orit is an invalid Memory Visualizer data file.

User Response: Verify that the file namespecified is correct.

DBA7517N Memory Visualizer could notwrite to the specified data file.

Explanation: Memory Visualizer could not savethe data file to the specified path and file name.


User Response: Verify that the specified pathexists and that the file permissions are correct.

DBA7604N No storage management snapshotfor the current database partitiongroup can be found.

Explanation: To take a storage managementsnapshot, from the Control Center, expand theobject tree until you find the database partitiongroup object. Right-click the database partitiongroup object and select Manage Storage from thepop-up menu.

User Response: Choose a different option onthe Redistribute Strategy page to proceed withthe redistribute wizard, or close the wizard andtake a storage snapshot first before continuingwith the redistribute operation.

DBA7608N An error occurred whenattempting to create the registryfor stepwise redistribute settingsfor database-name.database-partition-group-name.

Explanation: Without the registry records thestepwise redistribute tasks will fail.

User Response: Verify your file permissions andrecreate the redistribute settings registry recordsusing the Wizard.

DBA7609W The database partition group isnot partitioned.

Explanation: The current database partitiongroup contains only one partition.

User Response: There is no need for runningredistribute utility for it.

DBA7610W The table is not partitioned.

Explanation: The table is defined under adatabase partition group which contains only onepartition.

User Response: No data distribution file iscreated for the given table.

DBA7611N The stepwise redistribute propertytype is not valid.

Explanation: The requested stepwiseredistribute property entry cannot be retrieved orupdated.

User Response: Enter a valid property type.

DBA7612N An error has occurred whenaccessing file.

Explanation: The possible reasons include:

v File format error

v Communication error

v Memory allocation error when reading fromfile

User Response: Fix any format errors in the file.Check the db2diag.log file for more informationto help resolve the communication or memoryallocation errors. Rerun the application.

DBA7613W Affected tables within thedatabase partition group may belocked and unavailable for longperiods of time.

Explanation: Redistribution can be alog-intensive activity.

User Response: It is recommended to runredistribute on a test database before running iton your production system to determine howlong the redistribution will take.

To minimize the risk of running out of active logspace during a redistribute, it is recommendedthat you perform some or all of the followingactions:

v Reduce or eliminate other log-intensivedatabase activities

v Use infinite logging

v Use stepwise redistribution as recommendedby the Wizard


DBA7614W Affected tables within thedatabase partition group may belocked and unavailable for longperiods of time whenredistributing multiple databasepartition groups.

Explanation: Redistribution can be alog-intensive activity.

User Response: It is recommended to runredistribute on a test database before running iton your production system to determine howlong the redistribution will take.

To minimize the risk of running out of active logspace during a redistribute, it is recommendedthat you perform some or all of the followingactions:

v Reduce or eliminate other log-intensivedatabase activities

v Use infinite logging

v Schedule the redistribution of each databasepartition group to happen at a different timeto minimize contention for available log space

v Use stepwise redistribution as recommendedby the Wizard

DBA7615N One or more tables required bythe application are not definedwith the expected definition.

Explanation: The tables the application is tryingto access do not match the expected definition.This may be caused by one or more of thefollowing problems:

v Table does not exist

v Table column definition is not the same asexpected

User Response: The tables may have to bedropped and recreated with the appropriatedefinition. If this error is being encounteredduring a drop, then you can force the tables tobe dropped by specifying the FORCE option inthe drop command.

DBA7616N Invalid partition weight forstepwise redistribute operation.

Explanation: The value of the partition weightmust be between 0 to 32767.

User Response: Enter an integer within thevalid range and try again.

DBA7617N One or more input parameters donot contain valid values expectedby the routine.

Explanation: This may be caused by one ormore of the following problems:

v Numerical parameter is out of the expectedrange

v Object referenced by a parameter may nolonger exist

User Response: Verify your input parameterswith the routine specification, and try again.

DBA7618W Verify that all databases atinstance instance-name arecataloged.

Explanation: When adding partitions to aninstance, all temporary table spaces for alldatabases must be altered with new containerson the new partitions. A database must becataloged at that instance for the Add Partitionwizard to detect its temporary table spaces.

User Response: Review the list of databases onthe first page of the Add Partition wizard.

If there are any databases missing:

1. Close the wizard.

2. Close the Add Partitions launchpad.

3. Add the missing databases to the databasesfolder in the Control Center.

If there are databases listed that do not actuallyexist at the instance, remove them from thedatabases folder in the Control Center.


DBA7619W Verify that all databases atinstance instance-name arecataloged.

Explanation: When dropping partitions from aninstance, all data in all databases needs to bemoved off the affected partitions. A databasemust be cataloged at that instance for the AddPartition wizard to detect its database partitiongroups.

User Response: Review the list of databases inthe Drop Database Partition from DatabasePartition Groups window.

If there are any databases missing:

1. Close the window.

2. Close the Drop Partitions launchpad.

3. Add the missing databases to the databasesfolder in the Control Center.

If there are databases listed that do not actuallyexist at the instance, remove them from thedatabases folder in the Control Center.

DBA7620N There is no partitioning keydefined for the given table.

Explanation: A partitioning key is a column (orgroup of columns) that is used to determine thepartition in which a particular row of data isstored. Tables without a partitioning key are onlyallowed in single-partition database partitiongroups. Without a partitioning key, a datadistribution file cannot be generated, and datadistribution analysis cannot be performed.

User Response: You can add or droppartitioning keys, using the ALTER TABLEstatement. Altering the partition key can only bedone to a table whose table space is associatedwith a single-partition database partition group.

DBA7627N Unable to load snapshot data.

Explanation: The selected snapshot no longerexists.

User Response: Select a different snapshot fromthe Current Snapshot list on the StorageManagement toolbar.

If no other snapshot exists, you can capture anew snapshot by right clicking on a database,database partition group, or table space, andselecting the Capture Snapshot menu option.

DBA7628N Drop Partition task must startafter the last data redistribution iscomplete. The last redistributiontask is scheduled to start atstart-date start-time.

Explanation: All data redistribution tasks mustbe completed before the drop partition task canrun. Redistribution moves the data off thepartitions that will be dropped.

User Response: Choose a new start time for theDrop Partition task or just save it to the TaskCenter and run it manually once all theredistribution tasks are complete.

DBA7630W The following hosts could not befound: host-names.

Explanation: Add Partition will fail if these hostnames cannot be found on the network. Hostnames specified must refer to existing systems atthe time that this Add Partition task is scheduledto execute.

User Response: Verify that all of the listed hostnames are correct. Ensure that the specified hostnames exist when this task is scheduled toexecute.

DBA7631W The instance instance-name will bestopped and restarted when thistask is run.

Explanation: The script to be executed containsthe following commands:

db2stop forcedb2start

This will stop the database instance, refusingaccess to all connected applications. All databasesin this instance will not be available while theinstance restarts.

User Response: Run this task, which will restartthe instance at the scheduled time, or schedule


the task to run at a different time, or save thetask to the Task Center and run it later.

DBA7632N The database partitionsdatabase-partitions cannot beremoved from the followingdatabase partition groupspartition-groups.

Explanation: All database partition groups musthave at least one database partition.

User Response: When altering a databasepartition group, you must keep at least onedatabase partition in the database partitiongroup. If you do not want any databasepartitions in the database partition group, youmust drop that database partition group and loseany existing data.

DBA7633N The partitions partition-namescannot be dropped because theyare catalog partitions for one ormore databases.

Explanation: A catalog partition cannot bedropped without first dropping thecorresponding database. On Windows systems,you cannot drop partition 0.

User Response: Select one or more otherpartitions to drop from the instance, or drop thedatabases for the catalog partition you wish todrop before trying to drop the partition.

DBA7634N The container name container-nameis invalid.

Explanation: The container name must be avalid path if the container type is directory orfile, or a valid raw device if the container type israw device.

User Response: Redefine the container name toa valid path or raw device then attempt tochange it, or add a new container and thenremove the invalid one.

DBA7666W Configuration changes have beenmade for the previously selecteddatabase partition. Do you wantto save the changes?

Explanation: Another database partition wasselected, but the configuration changes to thepreviously selected database partition have notbeen saved.

User Response: Click Yes to obtain theconfiguration parameter values for the nextdatabase partition and save the changes thatwere specified for the previously selecteddatabase partition.

Click No to obtain the configuration parametervalues for the next database partition anddiscard the changes that were specified for thepreviously selected database partition.

Click Cancel to go back to the configurationparameter values for the previously selecteddatabase partition.


Chapter 7. DBI Messages

This section contains the error messages which may be generated duringinstallation and configuration of DB2 products. The messages are listed innumeric sequence.

DBI1001I Usage:

db2icrt [-a AuthType][-p PortName][-s InstType][-w WordWidth]-u FencedID InstName

Explanation: An invalid argument was enteredfor the db2icrt command. Valid arguments forthis command are:

-h|-? display the usage information.

-d turn debug mode on.

-a AuthTypeis the authentication type (SERVER,CLIENT, or SERVER_ENCRYPT) for theinstance.

-p PortNameis the port name or port number to beused by this instance.

-s InstTypeis the type of instance to be created(wse, ese, or client).

-u FencedIDis the name of the user under whichfenced UDFs and fenced storedprocedures will be run. This flag is notrequired if only a DB2 client is installed.

-w WordWidthis the width, in bits, of the instance tobe created (32 or 64). (AIX, SolarisOperating Environment) You must havethe requisite version of DB2 installed(32-bit or 64-bit) for this to work. Thedefault width value is 32-bit.

InstNameis the name of the instance.

User Response: For more information aboutthis command, please refer to the “QuickBeginnings” manual. Enter the command againas follows:

db2icrt [-a AuthType]-u FencedID InstName

DBI1002I Usage:

db2uit [-d] [-Q] [-D][-q <field>][-i <id>][-a <action>][-r <runlevels>][-p <process>]

Explanation: An invalid argument was enteredfor the db2uit command. Valid arguments forthis command are:

-d turn debug mode on

-q query a field given the searchparameters. Without -q, this becomes anupdate (if -i ID is already present) orinsert. Valid fields: i, r, a, p

-i ID of the entry

-r run levels

-a action to perform

-p process to launch

-Q Quiet: no output

-D Delete record


FileNamefile to modify

RETURN CODES:

-q If no field matches, non-zero, zerootherwise

update/insertIf file could not be updated, non-zero,zero otherwise

User Response: For more information aboutthis command, please refer to the QuickBeginnings manual. Try this command again.

DBI1003I Usage:

dlfmcrt [-b BackupDir]-p PortName-g DLFMGidDLFMAdmin

Explanation: An invalid argument was enteredfor the dlfmcrt command. Valid arguments forthis command are:


-p PortName is the port name or portnumber to be used by this instance.

-b BackupDir is the directory to be used tocreate the backup of the dlfm databasein.

-g DLFMGidis the DLFM Admin group (this groupmust be a secondary group ofDLFMAdmin)

DLFMAdminis the name of the DB2 Data LinksManager Administrator.

User Response: Enter the command again asfollows:

dlfmcrt -p PortNum -g DLFMGid DLFMAdmin

DBI1005I Usage:

db2idrop InstName

Explanation: An incorrect argument wasentered for the db2idrop command. Validarguments for this command are:

-h|-? display the usage information


InstNameis the name of the instance


db2idrop InstName

DBI1006I Usage:

db2idrop [-f] InstName




-f is the force applications flag. If this flagis specified then all applications usingthe instance will be forced to terminate.



db2idrop [-f] InstName

DBI1007I Usage:

dlfmdrop DLFMAdmin

Explanation: An invalid argument was enteredfor the dlfmdrop command. Valid arguments forthis command are:



DLFMAdminis the name of the DB2 data LinksManager Administrator.


dlfmdrop DLFMAdmin

DBI1008E Install media and AIX versionmismatch.

Explanation: Installing DB2 64-bit on AIXrequires different CDs for AIX version 4 and AIXversion 5.

db2setup has detected that your system isrunning AIX version 5, but you are installingfrom the DB2 for AIX version 4 CD.

User Response: Insert the DB2 for AIX version5 CD and try the installation again.

DBI1009E Install media and AIX versionmismatch.

Explanation: Installing DB2 64-bit on AIXrequires different CDs for AIX version 4 and AIXversion 5.

db2setup has detected that your system isrunning AIX version 4, but you are installingfrom the DB2 for AIX version 5 CD.

User Response: Insert the DB2 for AIX version4 CD and try the installation again.

DBI1011I Usage:

db2iupdt [-h|-?] [-d] [-k] [-s] [-D][-a AuthType][-w WordWidth][-u FencedID]{-e|InstName}

Explanation: An incorrect argument wasentered for the db2iupdt command. Validarguments for this command are:



-k keep the current instance type duringthe update.

-s ignore existing SPM log directory

-D updates the instance to a code level thatis lower than the current code level.This option is only valid in a multipleFixPak environment.

-a AuthTypeis the authentication type (SERVER,CLIENT, DCS, SERVER_ENCRYPT, orDCS_ENCRYPT) for the instance. Thedefault is SERVER.

-w WordWidthis the width, in bits, of the instance tobe created (32 or 64). (AIX, SolarisOperating Environment). Ignored if -e isspecified. You must have the requisiteversion of DB2 installed (32-bit or 64-bit)for this to work.

-u FencedIDis the name of the user under whichfenced UDFs and fenced StoredProcedures will be run. This flag is notrequired if only a DB2 client is installed.

-e specifies that every instance is updated.


User Response: Enter the command again withthe proper options and arguments.

DBI1012I Usage:

db2iupdt [-f] -u FencedIDInstName

Explanation: An incorrect argument wasentered for the db2iupdt command. Validarguments for this command are:




Chapter 7. DBI Messages 219




db2iupdt [-f] -u FencedID InstName

DBI1013I Usage:

dlfmupdt [-h|-?] DLFMAdmin

Explanation: An invalid argument was enteredfor the dlfmupdt command. Valid arguments forthis command are:


DLFMAdminis the name of the DB2 Data LinksManager Administrator.


dlfmupdt [-h|-?] DLFMAdmin

DBI1014E Instance migration to 32-bit is notsupported.

Explanation: Migration from 64-bit to 32-bit isnot supported in this version.

User Response: No actions required.

DBI1015I Usage:

db2imigr [-a AuthType]-u FencedID-g DLFMGidInstName

Explanation: An incorrect argument wasentered. Valid arguments for this command are:



-a AuthTypeis the authentication type (SERVER,CLIENT, or SERVER_ENCRYPT) theinstance.


-g DFLMGidneeds to be specified if migration aDLFM instance version 7 or earlier


User Response: For more information aboutthis command, please refer to the “QuickBeginnings” manual. Enter the command againas follows:

db2imigr [-a AuthType]-u FencedID InstName

DBI1018I Usage:

db2istop [-h|-?] [-d][-f] InstName







db2istop [-h|-?] [-d] [-f] InstName


DBI1020I Usage:

db2setup [-h|-?] [-d][-r RespFile]




-r RespFileis the name of the response file whichwill be used to install DB2.


db2setup [-h|-?] [-d] [-r RespFile]

DBI1021I Usage:

db2imigrev [-h|-?] [-m Version]InstName




-m specify DB2 version.

Versionis the version the instance will bemigrated backward to.

InstNameis the name of the instance which willbe migrated backward from version 8 tothe previous version of DB2.


db2imigrev [-h|-?] InstName

DBI1022I Usage:

db2imigrev [-h|-?][-f] InstName





InstNameis the name of the instance which willbe migrated backward from version 8 toa previous version of DB2.


db2imigrev [-h|-?] [-f] InstName

DBI1023I Usage:

db2ginfo [-h|-?] [-y][-c InstName[-a AuthType][-u FencedID]]OutputDir

Explanation: An invalid argument was enteredfor the db2ginfo command. Valid arguments forthis command are:

-h|-? display usage information.

-y executes script (only shows warningotherwise).

-c InstNamespecify instance to test.

-a AuthTypespecify authentication type (SERVER,CLIENT, or SERVER_ENCRYPT).

-u FencedIDspecify fenced user ID.

OutputDiris the directory where the output file,dbginfo.txt, will go.



db2ginfo [-h|-?] [-y][-c InstName [-a AuthType][-u FencedID]] OutputDir

DBI1024I Usage:

db2iauto [-h|-?] -on|-offInstName



-on|-offenables or disables autostarting of aninstance.



db2iauto [-h|-?] -on|-off InstName

DBI1025I Usage:

dascrt [-d] -u ASUser

Explanation: An invalid argument was enteredfor the dascrt command. Valid arguments for thiscommand are:

-d enters debug mode, for use with DB2Service

-u ASUseris the user the DAS will run under

User Response: For more information aboutthis command, please refer to the QuickBeginnings manual. Enter the command again asfollows:

dascrt -u ASUser

DBI1026I Usage:

dlfmfsmd [-h|-?] [-j] dlfsMntPt

Explanation: An invalid argument was entered

for the dlfmfsmd command. Valid arguments forthis command are:


-j modify the named filesystem from dlfsto jfs on AIX or ufs on Solaris OperatingEnvironment.

dlfsMntPtMount Point for Data Links ManagerFilter file system (including the slash: /).


dlfmfsmd dlfsMntPt

DBI1027I Usage:

dasdrop [-d]

Explanation: An invalid argument was enteredfor the dasdrop command. Valid arguments forthis command are:



dasdrop

DBI1028I Usage:

dasupdt [-d]

Explanation: An invalid argument was enteredfor the dasupdt command. Valid arguments forthis command are:



dasupdt


DBI1029I Usage:

db2nqadm [start|stop]

Explanation: An invalid argument was enteredfor the db2nqadm command. Valid argumentsfor this command are:

start start all NetQ services and daemonstop stop all NetQ services and daemon

You must specify one of the arguments.

User Response: Enter the command again withthe proper argument.

DBI1030E Kernel parameter name must beset to value.

Explanation: DB2 requires certain kernelparameters to be updated.

User Response:

v Update all necessary kernel parameters asdocumented in the “Quick Beginnings”manual.

v Reboot the system

v Try this command again

DBI1031E The product you selected requireseither DB2 UDB WorkgroupServer Edition or DB2 UDBEnterprise Server Edition installedfirst.

User Response:

v Install either DB2 UDB Workgroup ServerEdition or DB2 UDB Enterprise Server Edition.

v Try to install the product again.

DBI1032E The product you selected can notbe installed on AIX with a versionless than 4.3

Explanation: The DB2 product you selectedrequires an AIX version that is 4.3 or greater.

DBI1033E The product you selected requiresDB2 UDB Enterprise ServerEdition installed first.

User Response:

v Install either DB2 UDB Enterprise ServerEdition


DBI1034W Missing prerequisite package.

Explanation: One of the following packages hasbeen selected for installation: “<pkg-name>”Either the installed “<pkg-name>” fileset level isbelow “<name>” or it cannot be detected.

User Response: Ensure the “<pkg-name>”fileset is version “<name>” or higher.

Your “<pkg-name>” level will not affect theinstallation of DB2.

DBI1035E Failed to mount file systemFile-System.

Explanation: An attempt to mount the specifiedfile system has failed.

User Response: Verify that the file system isdefined. Correct any errors from the mountcommand and try again.

DBI1036E Failed to unmount file systemFile-System.

Explanation: An attempt to unmount thespecified file system has failed.

User Response: Correct any errors from theumount command and try again.

DBI1037E File system File-System does notexist.

Explanation: The file system specified is notdefined on this workstation.

User Response: Define the file system on theworkstation and try again.


DBI1038E File system File-System cannot bemodified.

User Response: Ensure that you have writepermission to the system file that contains filesystem definition, and try again.

DBI1039W Missing prerequsite package.

Explanation: One of the following packages hasbeen selected for installation: “<name>”However, the installed “<name>” fileset level isbelow “<name>”

User Response: Install the “<name>” filesetversion “<name>” which is provided on the CD.

DBI1040I The translated version offollowing message is not availableon this system.

User Response: The translated version offollowing message is not available on thissystem. Please refer to the “Installation.Notes”file in the PRODDIR/Readme/LOCALEdirectory, where PRODDIR is the productdirectory and LOCALE is the locale name. Forexample, the product directory is:

/usr/opt/db2_08_xx, where xx is 01 or FPn,where n is the FixPak number

or /opt/IBM/db2/V8.x, where x is 1 or FPn,where n is the FixPak number

DBI1041E File system inputMntPt cannot beconverted to dlfs.

Explanation: The File-systems ″/″, ″/var″,″/usr″, and ″/tmp″ cannot be converted to a dlfsFile-system. This has been done to avoid bootingproblems that may arise by making these dlfsFile-systems.

User Response: Run the command againspecifying a different File-system.

DBI1042E Base File-system BaseFS cannot bechanged to dlfs.

Explanation: On Aix, a File-system can bechanged to dlfs only if its vfs is fsm or jfs. Dlfs is

not supported for any other vfs.

User Response: Run the command again on ajfs or fsm file system.

DBI1043E The product you selected requiresDB2 Administration Clientinstalled first.

User Response:

v Install DB2 Administration Client.


DBI1050E Unsupported operating system -OS-name, version OS-ver.

Explanation: Your current operating system isnot supported or this version of the operatingsystem is not supported. Refer to the “QuickBeginnings” manual.

DBI1051E You cannot execute this programas root.

Explanation: This program can only be rununder a non-root user ID.

User Response: Login as an user ID other thanroot, and issue the command again.

DBI1052E You must be root to execute thisprogram.

Explanation: This program can only be rununder the root user ID. Special privileges arerequired to execute this program.

User Response: Login as root and issue thecommand again.

DBI1053E File system of type fsys-type is notsupported.

Explanation: Creating the instance’s homedirectory on this type of file system is notsupported. Instance’s home directory must existeither on a local file system or on a NFSmounted filesystem.

User Response: Change the home directory to asupported file system and recreate the instance.


DBI1055E The message file file-name cannotbe found.

Explanation: The message file required by theinstance commands is missing from the system;it may have been deleted or the databaseproducts may not be installed properly.

User Response: Verify that the product optioncontaining the message file is installed correctly.If there are verification errors, reinstall theproduct option.

DBI1057E Required locale locale is notavailable.

Explanation: The required locale directory,/usr/lib/locale/LANG/LC_MESSAGES, doesnot exist, where LANG is the name of yourcurrent locale.

User Response: Verify that the specified localehas been installed correctly. Also check for theread and execute permissions are set correctly onthat directory.

DBI1060E Invalid package name pkg-name.

Explanation: An incorrect name has beenentered. The package either does not exist or thename has been entered incorrectly.

User Response: Check to see if the name of thegiven package exists on the distribution media. Ifso, examine the name to see if it has beenmisspelled. All package names should be inlower case.

DBI1061E A fileset or package namepkg-name is missing.

Explanation: An error occurred when verifyingsoftware pre-requisites. The above fileset orpackage must be installed before using thiscommand.

User Response: Check to see if the name of thegiven package has been installed on your system.

DBI1062E A fileset or package namepkg-name is missing.

Explanation: The above fileset or package mustbe installed before using this command.

User Response: Install the fileset or packageand then reissue this command.

DBI1063E PTF or patch patch-name ismissing.

Explanation: The above PTF or patch must beinstalled before using this command. This PTF orpatch is required to complete this commandsuccessfully.

User Response: Install the required PTF orpatch and and enter this command again.

DBI1065E Program program-name terminatedprematurely.

Explanation: An error has occurred during theexecution and that has caused this program toterminate prematurely.

User Response: Correct the problem and try thecommand again.

DBI1066E Program program-name terminatedby request.

Explanation: This program has been terminatedby the user.

User Response: Issue the same command torestart the program.

DBI1067E DB2 Product Library for localelocale-name is not installed.

Explanation: No compressed-tar HTML files canbe found in the DB2DIR/doc/“<locale-name>”/html directory, where

DB2DIR =/usr/opt/db2_08_xx, where xx is 01 or FPn,where n is the FixPak number



User Response: Install the DB2 Product Libraryfor the required locale and issue this commandagain.

DBI1068E There is not enough space touncompress and un-tar all theHTML file in the directorydir-name.

Explanation: After uncompress and un-tar, allthe HTML files cannot be saved in the abovedirectory because the filesystem is full.

User Response: Increase the size of thefilesystem or free up sufficient disk space in thefilesystem. Issue the command again.

DBI1069E Unexpected error. Function =fname, Return code = return-code.

Explanation: An unexpected error occurredduring the execution of this program.

User Response: If the problem persists, contactIBM Support with the following information:

v Message number

v Function name

v Return code


DBI1070I Program program-name completedsuccessfully.

DBI1072I db2licm failed to update thenodelock file. Refer to the log filelog-name for more information.

Explanation: db2licm failed to add the licenseto the nodelock file, so DB2 will run with aTry-and-Buy license until a product license isinstalled.

User Response: Try the command again and ifit continues to fail, manually add the license keyto the nodelock file. Refer to the QuickBeginnings guide for more information onlicensing.

DBI1079I Output is saved in the log filelog-name.

Explanation: All processed and failedoperations have been saved into this log file.

User Response: Do not modify this file in anyway. This file is for IBM Technical Supportreference.

DBI1080E Disk full. Minimum spacerequired in dir-name is KB KB,whereas only KB KB space isavailable.

Explanation: There is not enough free spaceavailable in the file system or directory.

User Response: Free more disk space and retrythe command.

DBI1081E The file or directory file-name ismissing.

Explanation: A file or directory that is requiredto process this command is missing.

User Response: If the file belongs to one of thedatabase products then verify that the product isinstalled correctly and reinstall the product ifnecessary. If the file belongs to an instance thenthe instance may have already been removed orit may be corrupted.

Check to see if the name of the given directoryexists on your file system. If so, examine thename to see if it has been misspelled. Note thatall file and directory names are case-sensitive onUnix.

DBI1082E The file or directory file-namealready exists.

Explanation: A file or directory that thecommand needs to create already exists.

User Response: Examine the specified file ordirectory. If the file or directory exists as a resultof a previous successful completion of thecommand then no action is required. Otherwise,you will need to either rename or remove the


specified file or directory before trying thecommand again.

DBI1083E An attempt to remove file-namefailed.

Explanation: An error occurred when removingthe given file or directory. This may be due to aninappropriate ownership on this given file ordirectory.

User Response: Adjust the file permissions orownership of the specified file or directory andthen issue the command again.

DBI1084E An attempt to create file-namefailed.

Explanation: An error occurred when creatingthe given file or directory.

User Response: Check that there is enoughspace in the file system and that you have writepermission for the required directory. Suggesteddirectory permissions are u=rwx,go=rx.

DBI1085E An attempt to move the file ordirectory file-name to file-namefailed.

Explanation: An error occurred whenattempting to relocate the given file or directory.The command could not be processedsuccessfully.

User Response: Determine why the specifiedfile or directory could not be moved and then trythe command again.

DBI1086E An attempt to copy the file ordirectory file-name to file-namefailed.

Explanation: An error occurred whenattempting to duplicate the given file ordirectory. The command could not be processedsuccessfully.

User Response: Determine why the specifiedfile or directory could not be copied and then trythe command again.

DBI1087E An attempt to create the linkfilename failed.

Explanation: The given link cannot be created.It could be that the write permission on itsparent directory has been turned off, or that afile or directory with the same name alreadyexists.

User Response: Check permissions for theparent directory and restart the install process.Suggested directory permissions areu=rwx,go=rx.

DBI1088E Invalid access permission detectedfor directory directory.

Explanation: There may be several reasons forthis error. It is likely that one of the followingsituations has occurred:

v Either the given name is not a directory, or itdoes not have read and execute permission.

v The given directory can be created but cannotbe accessed. It could be that the permissionson any of its parent directories in its path havebeen set incorrectly.

User Response: Check permissions for thegiven directory and restart the install process.Suggested directory permissions areu=rwx,go=rx.

DBI1089E Error in saving current instancerelated information in thebackup-dir directory.

Explanation: There may be several reasons forthis error. It is likely that one of the followingsituations has occurred:

v The given directory does not have sufficientpermissions or does not have the writepermisssion.

v There is no space left on the filesystem.

User Response: Take an appropriate correctiveaction and issue the command again.


DBI1090E An attempt to update parameter infile-name failed.

Explanation: An error occurred while updatingthe given file.

User Response: Verify that all occurances of“<parameter>” are set to “<value>” in“<file-name>”.

DBI1091E An attempt to change permissionsfor directory failed.

Explanation: An error occurred when changingpermissions on the given file or directory. Thismay be due to an inappropriate ownership onthis file or directory.

User Response: Check permissions andownership for the given directory and restart theinstall process. Suggested directory permissionsare u=rwx,go=rx.

DBI1092E An attempt to change ownershipfor directory failed.

Explanation: An error occurred when changingownership on the given file or directory. Thismay be due to an inappropriate ownership onthis given file or directory.

User Response: Check ownership for the givendirectory and restart the install process.

DBI1093E An attempt to change groupownership for directory failed.

Explanation: An error occurred when changinggroup ownership on the given file or directory.This may be due to an inappropriate ownershipon this file or directory.

User Response: Check ownership for the givendirectory and restart the install process.

DBI1094E Directory access error.

Explanation: The tool encountered an accesserror during an I/O operation with the directoryserver.

User Response: Ensure the directory server is

on-line and accessible over the LAN.

DBI1095W The file or directory name cannotbe found.

User Response: Verify that the fileset/packageproviding the file/directory has been installed.

DBI1096E The file or directory file-namealready exists.

Explanation: A file or directory that thecommand needs to create already exists.

User Response: Examine the specified file ordirectory. If you no longer need this file ordirectory, remove it and then run the commandagain. Otherwise, you will need to either renameor remove the specified file or directory beforetrying the command again.

DBI1097E The file or directory file-name doesnot exist.

Explanation: A file or directory that thecommand requires does not exist.

User Response: If the file or directory does notexist, you may have to install the software thatprovides the file/directory. If the file or directorydoes exist, check to see that the PATH variablehas been set properly. Once the file or directoryis there in your PATH, try the command again.

DBI1100E An instance lock is found.Another instance managementcommand is running.

Explanation: The command failed becauseanother instance management command (eg.db2icrt, db2idrop, db2iupdt, or db2imigr) isrunning. The instance management commandsacquire an exclusive lock to avoid conflictingsimultaneous commands against the sameinstance.

User Response: Wait for all other occurrences ofthe instance commands to finish executing beforetrying the command again. If no other instancecommands are running then delete the file


“instance.lock” in one of the followingdirectories:



DBI1101E The instance name is invalid.

Explanation: Instance name must be the loginname of an existing user and cannot:

1. be more than 8 characters long.

2. start with “sql”, “ibm” or “sys”.

3. start with a numeral or contain charactersother than a-z, $, #, @, _, or 0-9.

User Response: Try the command again with avalid instance name.

DBI1103E The Administration Serveralready exists.

Explanation: The system detects that theAdministration Server has already been createdon your system. You can only create oneAdministration Server on each system.

User Response: If you want to re-create theAdministration Server, you have to drop theAdministration Server first before re-creating it.

DBI1104E The Administration Server cannotbe dropped.

Explanation: An attempt to drop theAdministration Server failed. The system detectsthat the Administration Server does not exist.


DBI1105E The DB2 Data Links ManagerAdministrator already exists.

Explanation: The system detects that the DB2Data Links Manager Administrator has alreadybeen created on your system. You can only createone DB2 Data Links Manager Administrator oneach system.

User Response: If you want to re-create the

DB2 Data Links Manager Administrator, youhave to drop the DB2 Data Links ManagerAdministrator first before re-creating it.

DBI1106E The DB2 Data Links ManagerAdministrator cannot be dropped.

Explanation: An attempt to drop the DB2 DataLinks Manager Administrator failed. The systemdetects that the DB2 Data Links ManagerAdministrator does not exist or has been createdunder a different user ID.

User Response: Verify that the name of the DB2Data Links Manager Administrator as reportedby the “dlfmlist” command is correct and tryagain.

DBI1107E The DB2 Data Links ManagerAdministrator cannot be created.

Explanation: Creating a DB2 Data LinksManager Administrator using DCE requires DFSon your system to be of version 3.1 or higher.

DBI1108E Valid group name or number notspecified.

Explanation: While migrating a dlfm instance,-g DLFMGid must be specified if instance beingmigrated is DB2 v7 or earlier.

DLFMGid can be a numeric group id or a groupname. This group must be a secondary group ofDLFMAdmin

User Response: If migrating a V8 or later dlfminstance, if -g DLFMGid is specified which is notthe same as the DLFMGid already set up for theinstance, the specified parameter will be ignoredand the old Gid will be used.

DBI1109E The kernel parameters must beupdated before using thiscommand.

Explanation: Some of the kernel parameters arenot configured properly.

User Response:


v Update all necessary kernel parameters asdocumented in the “Quick Beginnings”manual.

v Reboot the system

v Try this command again

DBI1111E The FencedID parameter must bespecified using -u flag with thiscommand.

Explanation: The FencedID parameter must bespecified with this command. The FencedIDparameter is set to the name of the user underwhich fenced User Defined Functions (UDFs)and fenced Stored Procedures will be run.

User Response: Enter the command againadding the arguments “-u FencedID” whereFencedID is the name of the user that you wantyour fenced UDFs or fenced Stored Procedures torun under.

For security reasons it is recommended that youdo not use the instance name as the FencedID.However, if you are not planning to use fencedUser Defined Functions (UDFs) or fenced StoredProcedures then setting the FencedID to theinstance name may save you the step of havingto create another user for the FencedID.

DBI1112E The FencedID parameter fenced-idis not valid.

Explanation: The FencedID parameter whichspecifies the user name under which fenced UserDefined Functions and fenced Stored Procedureswill be run:

v Must be the login name of an existing user.

v Cannot be set to the root or the bin user.

User Response: Try the command again with avalid FencedID parameter.

DBI1113W Previous value of FencedIDparameter old-value is different.New value new-value is ignored.

Explanation: The FencedID parameter enteredon the command line is different from the one

used before for this userid. New value for thisparameter is ignored.

DBI1115E Invalid AuthType parameterauth-type specified with -a flag.

Explanation: The AuthType parameter whichspecifies the authentication type used for theinstance is not valid. Valid authentication typesare:

v SERVER

v CLIENT

v SERVER_ENCRYPT

User Response: Try the command again with avalid AuthType parameter.

DBI1120E Instance inst-name cannot bedropped.

Explanation: An attempt was made to drop aninstance which may still be active.

DBI1121E Cannot drop the AdministrationServer using “db2idrop”.

Explanation: An attempt was made to drop theAdministration Server using “db2idrop”. Thisoperation is not allowed since it will cause theregistry to be in an inconsistent state.

User Response: Use the “dasidrop” commandto remove the Administration Server.

DBI1122E Instance inst-name cannot beupdated.

Explanation: An attempt was made to updatean instance. This instance cannot be updatedbecause:

v This “db2iupdt” command cannot be used toupdate this instance.

v The instance is still active.

User Response: Ensure that you are using thecorrect version of the “db2iupdt” command. Alsoensure that there are no db2 processes running atthe instance. Retry the command.


DBI1123E Cannot update the AdministrationServer using “db2iupdt”.

Explanation: An attempt was made to updatethe Administration Server using “db2iupdt”. Thisoperation is not allowed since it will cause theregistry to be in an inconsistent state.

User Response: Use the “dasiupdt” commandto update the Administration Server.

DBI1124E Instance inst-name cannot bemigrated.

Explanation: An attempt was made to migratean instance. This instance cannot be migratedbecause:

v The instance is still active.

v Migration of this instance is not supported

v This version of the “db2imigr” commandcannot be used to migrate this instance.

User Response: Ensure that instance is readyfor migration and you are using the correctversion of the “db2imigr” command. For moreinformation on instance migration, please refer tothe “Quick Beginnings” manual.

DBI1125E Cannot drop the DB2 Data LinksManager Administrator using“db2idrop”.

Explanation: An attempt was made to drop theDB2 Data Links Manager Administrator using“db2idrop”. This operation is not allowed since itwill cause the registry to be in an inconsistentstate.

User Response: Use the “dlfmdrop” commandto remove the DB2 Data Links ManagerAdministrator.

DBI1126W One or more views may affectdatabase migration.

Explanation: DB2 has detected some views thatare dependent on database entity that haschanged. This may cause database migration tofail. Please consult the Release.Notes for userresponse.

DBI1128E Cannot drop the AdministrationServer using “dlfmdrop”.

Explanation: An attempt was made to drop theAdministration Server using “dlfmdrop”. Thisoperation is not allowed since it will cause theregistry to be in an inconsistent state.

User Response: Use the “dasidrop” commandto remove the Administration Server.

DBI1129E Cannot update the AdministrationServer using “dlfmupdt”.

Explanation: An attempt was made to updatethe Administration Server using “dlfmupdt”.This operation is not allowed since it will causethe registry to be in an inconsistent state.

User Response: Use the “dasiupdt” commandto update the Administration Server.

DBI1131E The user ID user-id is invalid.

Explanation: An attempt to access the givenuser ID failed. One of the following situationshas occurred:

v This user ID does not exist on the system.

v The home directory of this user is not set upproperly.

v One of the user attributes needed by DB2 isunset.

v The UID of this user is 0

User Response: Make sure a valid user ID withvalid home directory, shell, primary group andsecondary group has been used. Create a newuser if necessary.

DBI1135E The primary group group-name ofuser ID user-id is invalid.

Explanation: The primary group name of theinstance user ID cannot:

1. be one of “guests”, “admins”, “users” or“local”.

2. start with “sql” or “ibm”.

3. start with a numeral or contain charactersother than a-z, $, #, @, or 0-9.


User Response: Change the primary group ofthe instance user ID to a group with a validname and then try the command again.

DBI1136W OLAP Start Kit not installed.

Explanation: The instance you are migratinghas OLAP functionality. OLAP Starter Kit is notavailable in DB2 V8. The instance will bemigrated only if the -F parameter was specified.

User Response: If program aborts, rerun thesame db2imigr command with the -F parameterto force migration. OLAP functionality will notbe present.

DBI1137W Server Product not installed.

Explanation: The instance you are migrating isa Server instance. A DB2 V8 Server Product hasnot been detected. The instance will be migratedonly if the -F parameter was specified.

User Response: If program aborts, rerun thesame db2imigr command with the -F parameterto force migration. DB2 Server functionality willnot be present. You must install a DB2 ServerProduct and and manually run db2iupdt on theinstance you are migrating to reenable Serverfunctionality.

DBI1138W Query Patroller not installed.

Explanation: The instance you are migratinghas Query Patroller functionality. Query Patrollernot detected in installed DB2 V8. The instancewill be migrated only if the -F parameter wasspecified.

User Response: If program aborts, rerun thesame db2imigr command with the -F parameterto force migration. Query Patroller will not bepresent. You must install Query Patroller for V8and manually run dqpcrt on the instance you aremigrating to reenable Query Patrollerfunctionality.

DBI1139E Data-Links File Manager is notinstalled.

Explanation: The instance you are migratinghas Data-Links functionality. Data-Links FileManager not detected in installed DB2 V8. Theinstance will not be migrated.

User Response: Please install Data-Links FileManager for DB2 V8 and try the same commandagain.

DBI1140W Command is being Forced. Youhave specified the -F flag to forcethe issued command past thepoint of failures mentioned in theabove warning(s).

DBI1141E Visual Warehouse 3.1 instancedetected. Visual Warehouse 3.1instance migration to V8 is notsupported. Only VisualWarehouse 5.2 and above can bemigrated to V8.

DBI1142W Visual Warehouse 5.2 instancedetected. Instance will bemigrated but warehouse metadatawill not be migrated.

DBI1143W Relational Connect is notinstalled.

Explanation: Relational Connect was notdetected in the version you are migrating to, buta setting file for DB2 and/or non-DB2datasources was detected for the instance you aremigrating. This configuration will be migratedbut Relational Connect for DB2 V8 has to beinstalled to make use of these configurationparameters.

User Response: Install Relational Connect forDB2 V8 to make use of the configurationparameters.


DBI1144E Relational Connect is notinstalled.

Explanation: Relational Connect was notdetected in the version you are migrating to butenvironment variables have been found thatindicate that you have non-DB2 data sources.This instance cannot be migrated if RelationalConnect is not installed.

User Response: Please install RelationalConnect and try the command again.

DBI1145W An existing Sync Point Manager(SPM) log directory was found.

Explanation: An existing Sync Point Manager(SPM) log directory was found. This new versionof the SPM cannot process the old version of thelog. You must verify that there are no indoubttransactions prior to using this new version ofthe SPM.

User Response:

v If you are not concerned with indoubttransactions, you may continue with instanceupdate by re-issuing the db2iupdt commandwith the -s flag. This will create a copy of thesqllib/spmlog directory undersqllib/spmlog50.

v If you are concerned about the existance ofindoubt transactions, you need to bring theDB2 product back to the previous version, andthen follow the instructions in the productreadme regarding indoubt transactions.

DBI1170E The -w flag only accepts 64 or 32as possible input.

Explanation: When using the db2icrt ordb2iupdt command, you can only specify a valueof 32 or 64 for the optional flag -w. You specify-w 64 for db2icrt when creating a 64 bit instance.You can also specify -w 64 for db2iupdt whenupdating a 32 bit instance to become a 64 bit.The -w flag is not needed otherwise.

User Response: Re-issue the command with theproper argument.

DBI1171E DB2 64-bit support is notinstalled.

Explanation: 64-bit instances are not supportedor implicit on this platform.

User Response:

v For Linux IA64, reissue the command withoutthe -w option to create a 64-bit instance.

v For other platforms, reissue the commandwithout the -w 64 option to create a 32-bitinstance.

DBI1172W While attempting to create orupdate a 64-bit instance, it wasdetected that the installed level ofone or both of bos.rte.libc andbos.adt.prof is lower than theminimum requirement for 64-bitinstances.

Explanation: The installed level of one or bothof bos.rte.libc and bos.adt.prof is lower than4.3.3.50, the minimum required level forsupporting 64-bit instances.

User Response: Before proceeding, downloadone or both of the following PTFs and updateyour system.

v For bos.rte.libc, the PTF is U473728.bff

v For bos.adt.prof, the PTF is U473581.bff

Information on downloading PTFs is availablefrom http://www.ibm.com/aix.

You can reissue the command with a -Fparameter to force execution past the point ofwarning.

DBI1173W db2iupdt has updated thisinstance to a 64-bit non-serverinstance.

Explanation: You can only update a 32-bitWorkgroup server instance to a 64-bit serverinstance if you have Enterprise Server Editioninstalled.

User Response: If you do not wish to update toa server instance, you can continue to use the


updated instance. If you wish to change thisinstance back to a 32-bit Workgroup serverinstance, run the following command:

db2iupdt -w 32 <instance-name>

DBI1174E db2icrt/db2imgr has created a64-bit non-server instance.

Explanation: You cannot create or migrate to a64-bit Workgroup server instance. If you wish torun a 64-bit server instance, you must have theEnterprise Server Edition installed.

User Response: If you do not require a serverinstance, you may continue to use thecreated/migrated instance. If you wish to use a64-bit server instance then you should installDB2 V8 Enterprise Server Edition, and run thefollowing command:

db2iupdt -w 64 <instance-name>

DBI1175W While attempting to create orupdate a 64-bit instance, it wasdetected that the installed level ofthe Solaris OperatingEnvironment is lower than theminimum requirement for 64-bit.

Explanation: The installed level of the SolarisOperating Environment is lower than 5.7, theminimum required level for supporting 64-bitinstances.

User Response: Before proceeding, update yoursystem to the minimum required level of theSolaris Operating Environment.

You can reissue the command with a -Fparameter to force execution past the point ofwarning.

DBI1176I Usage:

installAltFixPak [-h] [-s]

Explanation: An incorrect argument wasspecified. Valid argument for this command are:

-h display the usage information

-s install the exact same filesets/packagesto the alternate path (for supported

products) as those installed in/usr/opt/db2_08_01 or/opt/IBM/db2/V8.1.

If installAltFixPak detects that DB2 is notinstalled in /usr/opt/db2_08_01 or/opt/IBM/db2/V8.1, the -s option will not beused. In that case, it will call the db2_installutility.


installAltFixPak [-h] [-s]

DBI1177W Updating an instance to a codelevel that is lower than thecurrent level used by the instance.

Explanation: An attempt has been made toupdate an instance to a code level that is lowerthan the one being used by the instancecurrently.

User Response: To update an instance to a codelevel that is lower than the current level, issuethe db2iupdt command with the -D option asfollows:

db2iupdt -D <instance-name>

DBI1181E DB2 64-bit support is notinstalled.

Explanation: 64-bit instances are not supportedon this platform.

User Response: Before proceeding, either

v update your system to the minimum requiredlevel to run 64-bit DB2, and reissue thecommand again, or

v drop the instance you are migrating orupdating, and recreate it as a 32-bit instance.

DBI1182W Warehouse Manager Connectorsnot installed.

Explanation: The instance you are migratinghas Warehouse Manager Connectorsfunctionality. Warehouse Manager Connectors


was not detected in installed DB2 V8. Theinstance will be migrated only if the -Fparameter was specified.

User Response: Rerun the db2imigr commandwith the -F parameter to force migration.Warehouse Manager Connectors will not bepresent. You must install Warehouse ManagerConnectors for V8 and manually run db2iupdton the instance you are migrating in order tore-enable Warehouse Manager Connectorsfunctionality.

DBI1183W Spatial Extender not installed.

Explanation: The instance you are migratinghas Spatial Extender functionality. SpatialExtender was not detected in installed DB2 V8.The instance will be migrated only if the -Fparameter was specified.

User Response: Rerun the db2imigr commandwith the -F parameter to force migration. SpatialExtender will not be present. You must installSpatial Extender for V8 and manually rundb2iupdt on the instance you are migrating inorder to re-enable Spatial Extender functionality.

DBI1184W Life Sciences Data Connect notinstalled.

Explanation: The instance you are migratinghas Life Sciences Data Connect functionality. LifeSciences Data Connect was not detected ininstalled DB2 V8. The instance will be migratedonly if the -F parameter was specified.

User Response: Rerun the db2imigr commandwith the -F parameter to force migration. LifeSciences Data Connect will not be present. Youmust install Life Sciences Data Connect for V8and manually run db2iupdt on the instance youare migrating in order to re-enable Life SciencesData Connect functionality.

DBI1185I Server protocol protocol is nolonger supported. It has beenremoved from DB2COMM.

DBI1186I Usage:

db2cdbcr [-d] -n CDBName

Explanation: An incorrect argument wasentered for the db2cdbcr command. Validarguments for this command are:



-n CDBNameCDBName is the name of theWarehouse Control Database you wantto create.


db2cdbcr -n CDBName

DBI1187E Unable to complete DB2Warehouse Control Databasesetup.

Explanation: An attempt to create the DB2Warehouse Control Database has failed.

User Response: A nodegroup (created on node0) and a tablespace (both called FLG32K) needsto be created as well. See DB2 DataWarehousedocumentation for details.

DBI1190I db2setup is preparing the DB2Setup Wizard which will guideyou through the program setupprocess. Please wait.

DBI1191I db2setup is installing andconfiguring DB2 according to theresponse file provided. Pleasewait.

DBI1200E The directory directory-name is nota version version-number instance.

Explanation: The command cannot proceedbecause the specified directory does not point tothe required version of the database products.


User Response: The command cannot be runwith the specified instance.

DBI1202E Migration of instance inst-name isnot supported.

Explanation: The instance cannot be migratedbecause:

1. Migration from this version of the instance isnot supported.

2. The instance is already using the currentversion of the product and no migration isrequired.

User Response: Make sure that the instance isvalid for migration and then try the commandagain with a valid instance name.

DBI1205E One or more local databases havebeen detected that cannot bemigrated to the newest version.Check the logfile logfile-name forthe list of errors.

Explanation: Possible errors on the databaseare:

v Backup pending

v Roll-forward pending

v Database inconsistent

v One or more tablespace is not in normal state

v Database contains database objects that have aschema name of SYSCAT, SYSSTAT orSYSFUN

v Database contains database objects that have adependency on the SYSFUN.DIFFERENCESfunction. Possible violated objects are:

– constraint

– function

– trigger

– view

User Response: Take the following correctiveaction for each database from the file“<logfile-name>” :

v Backup pending - Perform backup of thedatabase.

v Roll-forward pending - Perform a roll-forwarddatabase to end of logs and stop.

v database inconsistent - Restart database toreturn it to a consistent state.

v Tablespace not in normal state - Perform aroll-forward database.

v Invalid schema - Drop the object and re-createthe object with a correct schema name(qualifier). If the object is a table you shouldfirst export its data, drop the table, re-createthe table with a correct schema name, andthen import or load the data to the new table.

v Object having SYSFUN.DIFFERENCESdependency -

– Constraint - alter table to drop theconstraint

– Function - drop the function

– Trigger - drop the trigger

– View - drop the view

DBI1211E Migration of the directory-namefailed.

Explanation: A system error such as runningout of disk space or memory has beenencountered during the migration of thedirectory. Instance migration failed.

User Response: Make sure there is sufficientdisk space and memory before trying thecommand again.

DBI1212W Migration of the local databasedirectory on path failed.

Explanation: The process of migrating localdatabase directory is not complete because of anunexpected error occurred.

User Response: An error file “db2mgdbd.err”and a local database directory backup“sqldbdir/sqldddir.bak” are created in thedirectory path mentioned above.

Keep these two files and contact IBM service forinstruction of possible ways to repair yourdirectory. Without the local database directory,databases that are catalogued in the localdatabase directory will no longer be accessible.


DBI1220W Migration of the node directoryon path failed.

Explanation: The process of migrating nodedirectory is not complete because of anunexpected error occurred.

User Response: Two options to recover:

1. Remove node directry and re-catalog nodeentry.

2. An error file “db2mgndd.err” and a nodedirectory backup “sqlnodir/sqlnddir.bak” arecreated in the directory path mentionedabove.

Keep these two files and contact IBM servicefor instruction of possible ways to repair yourdirectory. Contact IBM services to recoveryour node directory.

DBI1221W The node directory is corruptedand cannot be migrated.

Explanation: Either the node directory files arenot the same or the node directory file iscorrupted.

User Response: Remove node directry andre-catalog node entry.

DBI1222W The system database directory iscorrupted and cannot be migrated.

Explanation: Either the primary and backupsystem database directory files are not the sameor system database directory is corrupted.

User Response: Remove system databasedirectry and re-catalog all database entry.

DBI1223W The local database directory iscorrupted and cannot be migrated.

Explanation: Either the primary and backupdatabase directory files are not the same or thelocal database directory file is corrupted.

User Response: An error file “db2mgdbd.err”and a local database directory backup“sqldbdir/sqldddir.bak” are created in thedirectory path mentioned above.

Keep these two files and contact IBM service forinstruction of possible ways to repair yourdirectory. Without the local database directory,databases that are catalogued in the localdatabase directory will no longer be accessible.

DBI1225W The authentication type of acatalogued local database hasbeen changed.

Explanation: One or more catalogued databaseentries were detected that have an authenticationtype that is different from the authentication typethat was specified for the instance. If no action istaken then all catalogued local database entrieswill assume the authentication type of theinstance they belong to.

User Response: Check the file migration.log inthe home directory of the instance for a list ofthe catalogued local database entries that are notthe same as the authentication specified for theinstance. If you want the database to maintainit’s previous authentication type then you caneither change the authentication type of theinstance or you can move the database toanother instance that has the desiredauthentication type. Before changing theauthentication type of the instance, however, youshould make sure that you want all thecatalogued local database entries to have the newauthentication type.

DBI1240E The database manager could notbe started.

Explanation: The database manager could notbe started when attempting to check ifcatalogued local databases can be migrated.

User Response: Resolve why the databasemanager could not be started and then try thecommand again.

DBI1250E Applications are still usinginstance instance-name.

Explanation: There are applications that are stillrunning that are using the specified instance. Allapplications using this instance must beterminated before the command can be


completed successfully. You can get a list of theapplications that are currently using the instanceby issuing the command:

db2 list applications

User Response: You can either wait for theapplications to end by themselves, or you canexplicitly force the applications to end. You canlogon as the instance owner and run thecommand

db2 force application all

Note that some applications may haveunexpected behaviour when terminated usingthe above command. After all the applicationshave stopped, stop the database manager using“db2istop” command.

DBI1260E Cannot read from response file.

Explanation: An attempt was made to readfrom the given response file failed. Ensure thatthe response file has read access permission andthe given path to the response file is correct.

User Response: Correct the access permissionand the location of the response file and tryagain.

DBI1261E The value is not valid for thekeyword.

Explanation: The value specified in theresponse file is not valid for its correspondingkeyword. Refer to the sample response file for alist of valid entries.

User Response: Correct the problem in thefollowing line of the response file and try again.

DBI1262E Unknown keyword detected inthe response file.

Explanation: The given keyword in theresponse file is not valid. Refer to the sampleresponse file for a list of valid keywords.


DBI1264E Errors were encountered inrunning program-name. Please referto the installation log file log-namefor more information.



DBI1266I Refer to the log file log-name formore information.



DBI1268E The fileset fileset is not availableon the installation media.

Explanation: One of the filesets to be installedis not found on the installation media. If thefileset is not located on the installation mediathen it cannot be installed.

User Response: Ensure that the fileset is locatedon the installation media. If the fileset is notlocated on the installation media de-select it andtry again.

DBI1270E Error detected in the response file.

Explanation: An error has been detected whenprocessing the response file. Install cannot becontinued unless the problem has been corrected.


DBI1278W Warning issued from the responsefile.

Explanation: A warning has been raised whenprocessing the response file. DB2 Installer willcarry on without stopping.

User Response: If required, correct the problem


in the following line of the response file and tryagain.

DBI1279I Notice issued from the responsefile.

Explanation: A notice has been issued whenprocessing the response file. DB2 Installer willcarry on without stopping.

User Response: This is for your informationonly. No action is required.

DBI1281E The database managerconfiguration file could not beinitialized.

Explanation: An error occurred whenattempting to initialize the database managerconfiguration file. A DB2 instance could not becreated or migrated.

User Response: Refer to the log file for problemdetermination. Resolve the problem and try thecommand again. If the problem persists, pleasecontact IBM Support.

DBI1282W The database managerconfiguration files could not bemerged.

Explanation: An error was detected whenattempting to merge two database managerconfiguration files. The previous databasemanager configuration file could not be mergedwith the new database manager configurationfile.

User Response: Check the values in the newdatabase manager configuration file and updatethe parameters as required.

DBI1283E Unable to update thecommunication information forinstance.

Explanation: The SVCENAME parameterand/or the DB2COMM registry values could notbe updated during instance creation.

User Response: Make sure that theSVCENAME parameter is set to

“<profile-name>” in the database managerconfiguration file and update using

db2 update dbm cfg usingSVCENAME “<profile-name>”

Also update the DB2COMM variable to tcpip byrunning

db2set DB2COMM=tcpip

DBI1290E An attempt to create the profileregistry profile-name failed.

Explanation: An error occurred when creatingthe profile registry. One of the followingsituations occurred:

v Incorrect access permission on the filecontaining the profile registry.

v Profile registry is not set up properly.

v There is not enough space on your file system.

User Response: Check the file permissions onthe instance list profile in one of the followingdirectories:



DBI1291E The instance instance-name was notfound in the instance list.

Explanation: The specified instance was notfound in the instance list.

User Response: Verify that the list of instancesas reported by the “db2ilist” command is correct.Retry the command with a valid instance name.

DBI1292E The instance instance-name isalready in the instance list.

Explanation: The instance that is being createdor migrated is already in the instance list.

User Response: Use a different instance namethat is not part of the instance list as reported bythe “db2iset -l” command.


DBI1293E There is no DB2 Query PatrollerServer set up on this system.

User Response: If DB2 Query Patroller was notinstalled via the DB2 Installer, please use theInstaller to properly set up an instance for usewith the DB2 Query Patroller Server. If one hasbeen set up, then verify that it is recorded in thedefault.env file, and that the file is worldreadable. default.env can be found in



DBI1295E The instance list could not beupdated.

Explanation: The instance could not be addedto or removed from the instance list. An errorhas occurred when adding or removing theinstance from the instance list. One of thefollowing situations occurred:

v Incorrect access permission on the registryprofile.






DBI1297E The instance profile profile-namecould not be updated.

Explanation: An error occurred when updatingthe instance profile registry. One of the followingsituations occurred:

v Incorrect access permissions on the instanceprofile registry.






DBI1300N db2set displays, sets, or removesDB2 profile variables.

db2set [[[variable=[value]][-g|-i instance[node-number]]][-all] [-null][-r instance[node-number]][-n DAS node[-u user[-p password]]][-l|-lr] [-v] [-ul|-ur][-?|-h]

Explanation: The command options are:

-g Access the global profile variables.

-i Specifies the instance profile to useinstead of the current or default.

-n Specifies the remote DB2 AdministrationServer node name.

-u Specifies the user ID to use for theAdministration Server attachment.

-ul Access the user profile variables

-ur Refreshes user profile variables

-p Specifies the password to use for theadmin server attachment.

-r Resets the profile registry for the giveninstance

-l Lists all instance profiles.

-lr Lists all supported registry variables.

-v Verbose mode.

-? Displays the command help message.

-h Same as -? option.


-all Displays all occurrences of the localenvironment variables as defined in:

v The environment, denoted by [e]

v The user level registry, denoted by [u]

v The node level registry, denoted by[n]

v The instance level registry, denoted by[i] and

v The global level registry, denoted by[g]

-null Sets the variables value to null at thespecified registry level to preventlooking up the value in the next registrylevel as defined in the variable valuesearch order.

Notes:

v db2set with no variable name displays alldefined variables.

v db2set <variable> displays <variable>’s value.

v db2set <variable>= (nothing) deletes the<variable>.

v db2set <variable>=<value> modifies the<variable>’s value.

v db2set <variable> -null sets <variable>’s valueto NULL.

v db2set <variable> -all displays all defined<variable>’s values.

v db2set -ur refreshes the current user profile.

v db2set <variable> -ul displays defined<variables> at the user level.

v db2set -all displays all defined variables in allregistry levels.

DBI1302E Invalid parameter detected.

Explanation: An invalid parameter was used.

User Response: Use the -? option for the usagehelp message.

DBI1303W Variable not set.

Explanation: The variable was not set in theprofile registry.

User Response: No further action is required.

DBI1304E Unexpected error.

Explanation: The tool encountered anunexpected system error.

User Response: Contact your DB2 servicerepresentative.

DBI1305E The profile registry was notfound.

Explanation: The target machine does not havea profile registry setup.

User Response: Create the registry on the targetmachine by installing DB2.

DBI1306N The instance profile is notdefined.

Explanation: The instance is not defined in thetarget machine registry.

User Response: Specify an existing instancename or create the required instance.

DBI1307N The instance node profile is notdefined.

Explanation: The instance node is not definedin the target machine registry.

User Response: Create the registry by installingthe required DB2 product parts.

DBI1308E Out of memory conditionencountered.

Explanation: The tool encountered an “out ofmemory resource” error.

User Response: System is low on memoryresources. Terminate non-essential applications ortry again later.

DBI1309E System error.

Explanation: The tool encountered an operatingsystem error.


User Response: A system error wasencountered during registry access. Ensure thatthere is enough space on the file system wherethe registry is located, and that there is a validLAN connection if the registry is remote.

DBI1310E Remote registry access is notsupported.

Explanation: The tool does not support theremote registry option.

User Response: Consult the CommandReference on how to access the registry remotely.

DBI1311I Listing registry instance profiles...

DBI1312I Listing defined global variables...

DBI1313I Listing defined instancevariables...

DBI1314I Listing all supported registryvariables...

DBI1315W Unknown message!

DBI1316E Instance is not MPP.

Explanation: The target instance is not a DB2MPP instance.

User Response: Choose an MPP instance.

DBI1317E Instance node already exists.

Explanation: A duplicate instance node alreadyexists.

User Response: Choose a different instancenode.

DBI1320W WARNING:

Explanation: This script is used to gatherinformation useful to IBM Support to debug theproblems you may be experiencing. Thisinformation may be of a sensitive nature. You

may wish to edit the output file, db2ginfo.txt,before sending it to IBM Support.

User Response: To signal your awareness andacceptance of the above warning, run this scriptwith the -y flag specified.

DBI1330W The action might affect otherinstances.

Explanation: The file IWH.environmentcontains global information for all instances.Updating this file might affect all instances. Doyou wish to continue?

DBI1332E Missing template file forIWH.environment.

Explanation: The template file forIWH.environment is needed.

DBI1351E You must be the instance ownerto run this command.

Explanation: To run this command, you mustbe the DB2 Query Patroller Server instanceowner.

User Response: Verify that the DB2 QueryPatroller Server instance is correctly recorded inthe file default.env. Log in as the DB2 QueryPatroller Server instance owner and issue thecommand again. default.env can be found in



DBI1352E The instance instance-name is notan ESE instance.

Explanation: DB2 Query Patroller Server/Agentmust be created on an ESE instance.

User Response: Run this command again usinga valid ESE instance name, or you may createand set up a new ESE instance first beforerunning this command again.


DBI1353E DB2 Query Patroller Server hasbeen set up on an instancealready.

Explanation: DB2 Query Patroller Server can beset up on one DB2 UDB instance only.

User Response: Run the command dqplist tofind out the named of the instance being used asthe DB2 Query Patroller Server. If the instancename is correct then there is no need to rundqpcrt to set up a server. For setting up an agentyou need to use the correct instance name. If thisinstance is no longer being used for thatpurpose, run the command

dqpdrop inst_name

to remove it. Then re-run the dqpcrt commandagain.

DBI1354E The instance instance-name is notan DB2 Query Patroller Serverinstance.

User Response: Use dqplist to find out theproper server instance name and re-run thecommand again.

DBI1355I Usage:

dqpcrt [-h|-?] -s|-a-p PortName InstName


PortNamePort name to be used with the DB2Query Patroller Server/Agent

InstaNamename of an instance that is to bedesignated as an DB2 Query PatrollerServer instance

-s Creating a DB2 Query Patroller Serveron the named instance

-a Creating a DB2 Query Patroller Agenton the named instance.


The -a option is only valid on a multiplepartitioned database instance.

User Response: Re-enter the command with theproper syntax.

DBI1356I Usage:

dqplist [-h|-?]




DBI1357I Usage:

dqpdrop [-h|-?] InstName


InstNamename of the instance that you wish toremove the DB2 Query Patroller Serverfrom


This command can only be issued on the nodewhere the DB2 Query Patroller Server wascreated.


DBI1358W Failed to modify the DB2 QueryPatroller profile files.

Explanation: An attempt to update thedqpprofile and/or dqpcshrc files have failed.Possible causes can be

v These files do not exist in the sqllib directoryunder the instance home directory.

v There is no write permission on these files.


v Failure to create a temporary file in /tmpdirectory.

User Response: Check the existence andpermission on these files. Verify that you canwrite to /tmp. Issue the command again.

DBI1359E Unable to remove the DB2 QueryPatroller Server from instanceinstance-name.

Explanation: An attempt to remove the DB2Query Patroller Server from the named instancehas failed.

User Response: Manually remove the filesqllib/cfg/dqplevel from the instance owner’shome directory. Also edit the file default.env andremove the DQPSERVER line from this file.default.env can be found in



DBI1360E Unable to complete DB2 QueryPatroller set up.

Explanation: An attempt to set up the DB2Query Patroller Server has failed. Possible causeinclude:

v Failed to create a database for the DB2 QueryPatroller Server

v Failed to create a nodegroup on the specifiednode

v Failed to create a tablespace in the nodegroup

User Response: If the database or thenodegroup creation failed, try to create themmanually and re-run the command.

If it failed at creating the table space, check tosee that you have write permission to the pathyou have designated. Try to create the tablespacemanually.

DBI1361E DB2 Query Patroller Server codehas not been installed.

Explanation: The DB2 Query Patroller Servercode has not been installed, and is required forthe current operation to complete.

User Response: Install the DB2 Query PatrollerServer code, and try the command again.

DBI1362W IWM schema objects have beendetected.

Explanation: DB2 has detected IWM schemaobjects, possibily from a previous install of IWM.

User Response: If you wish to keep the existingIWM schema objects, there is nothing to do. Ifyou wish to remove them and re-create newones, re-issue the dqpsetup command with the -oflag.

DBI1363E Failed to create IWM schemaobjects.

Explanation: An attempt to create the IWMschema objects has failed.

User Response: Verify that the filesdb2_qp_schema and iwm_schema.sql are both inthe directory /usr/opt/db2_08_xx/bin, where xxis 01 or FPn, where n is the FixPak number.

If both files exist, then the output of the IWMschema creation procedure can be found in/tmp/iwmschcr.log. Correct any error and re-runthe dqpsetup command again.

DBI1364E No previous DB2 Query Patrollerschema objects exist.

Explanation: No previous DB2 Query Patrollerschema objects exist to be migrated.

User Response: Run dqpsetup again with thecorrect syntax. Use ’dqpsetup -h’ to see thesyntax.

DBI1365E Node number is not defined.

Explanation: The node number is not defined inthe db2nodes.cfg.


User Response: Examine the db2nodes.cfg fileand make sure the entry you want is there. Enterthe command again using the correct nodenumber exactly as recorded in the db2nodes.cfgfile.

DBI1366E The container sms-path is alreadyin use.

Explanation: The directory named as acontainer for the tablespace already exists.

User Response: Run the command again usinga different path for the container for thetablespace.

DBI1367E Failed to bind the files listed inbind-list.

Explanation: There was a problem binding thebind files listed in named file(s).

User Response: Perform the binding manually.

DBI1368E Failed to connect to DQP databasedb2dbdft.

Explanation: The database likely doesn’t exist.

User Response: Specify that you would like tosetup a new DQP instance using all the requiredparameters to dqpsetup. This instance cannot bemigrated.

DBI1370W Unable to modify the .profile orthe .login file of user inst-name.

Explanation: DB2 has failed to modify the.profile file or the .login file of this user. Thesefiles may not exist, or you may not have writepermission to them. Without the modificationyou need to set your environment manually eachtime when you log in as this user to use DB2Query Patroller.

User Response: See the Quick Beginning Guidefor more details on how to set the DB2environment automatically.

DBI1371E Missing arguments for setting upa Query Patroller Server.

Explanation: A Query Patroller instance mustbe set up as server when DB2 Query PatrollerServer is installed. Therefore the followingarguments must be supplied:

1. Node group.

2. Node number.

3. Database name.

4. Tablespace.

5. Result tablespace.

6. Tablespace path.

And optionaly:DMS Tablespace size.

User Response: Specify the required and/oroptional arguments in the response file.

DBI1372E Cannot set up a Query Patrollerserver instance.

Explanation: To set up a Query Patroller serverinstance, you must have DB2 Query PatrollerServer installed.

User Response:

v Install DB2 Query Patroller Server.

v If you wish to set up a Query Patroller agent,take out the arguments for node group, nodenumber, database name, tablespace, resulttablespace, tablespace path and DMStablespace size.

DBI1373E Cannot set up Query Patrollerserver instance when creating anew ESE instance.

User Response: Create the ESE instance and setup the instance as a Query Patroller server inseparate steps.

DBI1375E Cannot set up a Query Patrollerinstance without ESE installed.

User Response: Install ESE, and DB2 QueryPatroller Agent/Server.


DBI1376E To set up a Query Patrollerinstance, you need to provide theservice name and port number ofthe IWM user.

User Response:

v If you wish to set up a Query Patrollerinstance, enter the service name and portnumber of the IWM user.

v If you do not wish to set up a Query Patrollerinstance, take out the specification of nodegroup, node number, database name,tablespace, result tablespace, tablespace pathand DMS tablespace size from the responsefile.

DBI1377N db2isetup was unable to locate asuitable Java RuntimeEnvironment on your computer. Ifa Java Runtime Environment v.13is present, please set yourJAVA_HOME environmentvariable and try running thecommand again. Otherwise,please refer to the DB2Installation Notes for informationon the recommended Javaenvironment for your operatingsystem.

DBI1378N db2setup was unable to locate asuitable Java RuntimeEnvironment on your computer. Ifa Java Runtime Environment v.13is present, please set yourJAVA_HOME environmentvariable and try running thecommand again. Otherwise,please refer to the DB2Installation Notes for informationon the recommended Javaenvironment for your operatingsystem. If you are unable toobtain a suitable Java RuntimeEnvironment you can install thisproduct from the command usingthe doc_install script. Run thisscript without any parameters forinformation on how to use it.

DBI1400N The syntax of the db2licmcommand is incorrect.

Explanation: The db2licm tool performs basiclicense functions in the absence of the ControlCenter. It adds, removes, lists, and modifieslicenses installed on the local system:

db2licm [-a filename][-e HARD | SOFT][-p prod-passwordREGISTERED | CONCURRENT |INTERNET | MEASURED][-r prod-password][-u prod-password num-users][-n prod-password num-processors][-l][-v][-?]

The command options are:

-a Adds a license for a product. Specify afile name containing valid licenseinformation. This can be obtained fromyour licensed product CD or contactyour IBM representative or authorizeddealer.

-n Updates the number of entitledprocessors. Specify the number ofprocessors that you are entitled to usethis product with.

-e Updates the enforcement policy on thesystem. Valid values are: HARD andSOFT. HARD specifies that unlicensedrequests will not be allowed. SOFTspecifies that unlicensed requests will belogged but not restricted.

-l Lists all the products with availablelicense information.

-p Updates the license policy type to useon the system. The keywordsCONCURRENT, REGISTERED, orCONCURRENT REGISTERED can bespecified. In addition, you can specifiyINTERNET for DB2 UDB WorkgroupServer products. Alternatively you can


also specify MEASURED for DB2Connect Unlimited products.

-r Removes the license for a product. Afterthe license is removed, the productfunctions in ″Try & Buy″ mode. To getthe password for a specific product,invoke the command with the -l option.

-u Updates the number of userentitlements that have been purchased.Specify the password of the product forwhich the entitlements were purchasedand the number of users.

-v Displays version information.

-? Displays help information. When thisoption is specified, all other options areignored, and only the help informationis displayed.

User Response: Enter the command again usingthe valid parameters.

DBI1401I Command line DB2 LicenseManager.

Explanation: The db2licm tool performs basiclicense functions in the absence of the ControlCenter. It adds, removes, lists, and modifieslicenses installed on the local system:

db2licm [-a filename][-e prod-password HARD | SOFT][-p prod-passwordREGISTERED | CONCURRENT |INTERNET | MEASURED][-r prod-password][-u prod-password num-users][-n prod-password num-processors][-l][-v][-?]


-a Adds a license for a product. Specify afile name containing valid licenseinformation. This can be obtained fromyour licensed product CD or contactyour IBM representative or authorizeddealer.

-n Updates the number of entitledprocessors. Specify the number ofprocessors that you are entitled to usethis product with.

-e Updates the enforcement policy on thesystem. Valid values are: HARD andSOFT. HARD specifies that unlicensedrequests will not be allowed. SOFTspecifies that unlicensed requests will belogged but not restricted.

-l Lists all the products with availablelicense information.

-p Updates the license policy type to useon the system. The keywordsCONCURRENT, REGISTERED, orCONCURRENT REGISTERED can bespecified. In addition, you can specifiyINTERNET for DB2 UDB WorkgroupServer products. Alternatively you canalso specify MEASURED for DB2Connect Unlimited products.

-r Removes the license for a product. Afterthe license is removed, the productfunctions in ″Try & Buy″ mode. To getthe password for a specific product,invoke the command with the -l option.

-u Updates the number of userentitlements that have been purchased.Specify the password of the product forwhich the entitlements were purchasedand the number of users.

-v Displays version information.

-? Displays help information. When thisoption is specified, all other options areignored, and only the help informationis displayed.

DBI1402I License added successfully.

DBI1403I License removed successfully.

DBI1404N Product password not found.

Explanation: The given password is eitherinvalid, or a license for this product was not


found in the nodelock file.

User Response: Issue this command with -loption to check that the password entered is thecorrect product password for the product thatyou want to perform this action on. If you areusing nodelock passwords, check that the licensekey for this product is installed in the nodelockfile.

DBI1405I License policy type updatedsuccessfully.

DBI1406N Invalid license policy type.

Explanation: The license policy type that wasentered was not valid for the product specified.

User Response: Please enter a valid licensepolicy. Options are:

v CONCURRENT

v REGISTERED

v INTERNET

v CONCURRENT REGISTERED

v CONCURRENT INTERNET

v REGISTERED INTERNET

v CONCURRENT REGISTERED INTERNET

v MEASURED

INTERNET policy is valid for DB2 UDBWorkgroup Server products.

MEASURED policy is valid for DB2 ConnectUnlimited products.

DBI1407N Invalid license certificate file.

Explanation: License certificate file is not in thecorrect format.

User Response: Enter the name of a file withthe correct license certificate format.

DBI1408N The file file-name could not beopened.

Explanation: The file is not found or access tothe file is denied.

User Response: Enter the name of a file thatexists and can be opened and try the commandagain.

DBI1409N Invalid enforcement policy type.

Explanation: The enforcement policy typespecified is not valid for this product.

User Response: Please enter a valid enforcmentpolicy type that is supported by the specifiedproduct.

DBI1410I Concurrent users updatedsuccessfully.

DBI1411I Enforcement policy type updatedsuccessfully.

DBI1412W A hard stop enforcement policystops the use of the product byunlicensed users when licensinginfractions have been exceeded.

DBI1413W A soft stop enforcement policylogs license infractions, butallows unlicensed users to stilluse the product.

DBI1416N The license could not be added tothe nodelock file automatically.

Explanation: The return code is“<return-code>”.

User Response: Please ensure the licensecertificate is readable. You may also enter thelicense into the nodelock file manually. Please seethe license file for instructions.

DBI1417N The license specified could not beremoved from the nodelock file.


User Response: Ensure that the license for thisproduct exists in the nodelock file.


DBI1418I The number of licensedprocessors on this system hasbeen updated successfully.

DBI1419N There was an error updating thenumber of licensed processors.


DBI1420N This product does not supportthis type of license policy.

Explanation: The license policy specified doesnot apply to this product or is not supported.

User Response: Please enter a valid licensepolicy.

DBI1421N This product specified is notinstalled on this system.

Explanation: You can not configure a licensepolicy for a product until the product is installed.

User Response: Install the product beforerunning this command or specify the correctproduct password. To list the products install onthe system issue db2licm -l.

DBI1422N The number of concurrent userswas not updated.


User Response: Please ensure the concurrentpolicy is enabled for this product.

DBI1423N This option requires the creationof an instance.

Explanation: Features that are required toperform this action are only accessible once aninstance has been created.

User Response: Please create an instance andissue this command again.

DBI1424N An unexpected error occuredwhile accessing processorinformation.



DBI1425E The license for DB2 OLAP Servercannot be updated. The DB2OLAP processes are currentlyactive.

Explanation: DB2 cannot update the license forDB2 OLAP Server while DB2 OLAP Server isrunning.

User Response: To update your OLAP license,please stop all OLAP processes and reinstall thisDB2 license.

DBI1426I This product is now licensed foruse as specified in the LicenseAcceptance and LicenseInformation documents pertainingto the licensed copy of thisproduct. USE OF THE PRODUCTCONSTITUTES ACCEPTANCEOF THE TERMS OF THE IBMLICENSE ACCEPTANCE ANDLICENSE INFORMATIONDOCUMENTS, LOCATED INTHE FOLLOWING DIRECTORY:dir-name

DBI1427I This product is now licensed foruse as specified in the LicenseAcceptance and LicenseInformation documents pertainingto the evaluation (″Try and Buy″)copy of this product. USE OFTHE PRODUCT CONSTITUTESACCEPTANCE OF THE TERMSOF THE IBM LICENSEACCEPTANCE AND LICENSEINFORMATION DOCUMENTS,LOCATED IN THE FOLLOWINGDIRECTORY: dir-name


DBI1428N There was an error updating thenumber of licensed processors.

Explanation: The number of licensed processorsentered exceeds the number of maximumlicensed processors allowed for this product.

User Response: Please enter number of licensedprocessors that does not exceed the definedmaximum. If the number of processors on yoursystem exceeds the maximum number ofprocessors allowed for this product, pleasecontact your IBM representative or authorizeddealer.

DBI1429N This product does not supportthis combination of licensepolicies.

User Response: Please enter a validcombination of license policies. For example, youcan specify ″CONCURRENT REGISTERED″ as avalid combination.

DBI1430N The license could not be added tothe nodelock file because thelicense date is greater thanoperating system date.

User Response: Please check your certificate fileto ensure that the license start date precedes thecurrent date (the date set on the operatingsystem).

DBI1431N This user does not have properauthority to perform the specifiedaction.

Explanation: This program can be only beexecuted under the root user ID or a user IDwith SYSADM authority.

User Response: Please login with a userid thathas the proper permissions to perform thiscommand.

DBI1500I Usage:

db2inst [-f response-file]

Explanation: An incorrect argument was

entered. The command accepts an optional flag -fwhich is followed by the path of the “DB2Installer” response file.

User Response: Re-enter the command with avalid argument.

DBI1501E An internal error wasencountered.

Explanation: An error was detected whileperforming an internal operation.

User Response: Verify that the file system onwhich the file resides is not damaged. If theproblem persists, contact IBM Support with thefollowing information:

1. Message number

2. Internal error message description

3. Problem description

DBI1502E An error was encountered whenopening or reading from file,file-name.

Explanation: An error was encountered whenopening or reading from a file. One of thefollowing errors occurred:

v An I/O error occurred opening or readingfrom the file.

v An expected value was not found in the file.

v The order of the data in the file is incorrect.

User Response: If the file was modified by theuser, verify that the data in the file is valid. If thefile was not modified by the user, contact IBMSupport with the following information:

1. Message number

2. Message description


DBI1503E An error was encountered whenopening or writing to file,file-name.

Explanation: An error was encountered whenwriting data to a file. One of the following errorsoccurred:


v Incorrect access permissions on a givendirectory.


User Response: Check to see if the permissionson the file’s parent directory have been setcorrectly. If the problem persists, contact IBMSupport with the following information:

1. Message number



DBI1504E An error occurred openingmessage files.

Explanation: An attempt to open and read from“DB2 Installer” message catalog files failed.Before DB2 Installer starts up, it looks for tworesource files -- db2inst.rcx and db2inst.cat in thefollowing locations:

v DB2 product directory, or

v on the distribution media, or

v environment variables DB2IRCX andDB2ICAT.

User Response: Set the environment variablesDB2IRCX and DB2ICAT to the absolute locationof db2inst.rcx and db2inst.cat respectively.

DBI1505E An attempt to allocate memoryfailed.

Explanation: An error was detected whenattempting to allocate memory.

User Response: Terminate other applicationsrunning on the system that may be using largeamounts of memory. If the problem persists,contact IBM Support with the followinginformation:

1. Message number



DBI1507E An instance of the DB2 Installeris already started.

Explanation: An error was detected whenattempting to start up the DB2 Installer. Another

instance of the DB2 Installer is still running.

User Response: Terminate all instances of theDB2 Installer and restart the install process. If theproblem persists, remove the lock file/tmp/.db2inst.lck and restart the DB2 Installer.

DBI1515E An attempt to allocate resource fora subprocess failed.

Explanation: An error was detected whenattempting to startup a subprocess.

User Response: Terminate other applicationsrunning on the system that may be using largeamounts of resources. If the problem persists,contact IBM Support with the followinginformation:

1. Message number


DBI1516E An attempt to terminate asubprocess failed.

Explanation: An error was detected whenattempting to terminate a subprocess.

User Response: Terminate other applicationsrunning on the system that may be using largeamounts of resources. If the problem persists,contact IBM Support with the followinginformation:

1. Message number


DBI1517E An attempt to execute a commandin a subprocess failed.

Explanation: An error was detected whenattempting to execute a command in asubprocess. One of the following problemsoccurred:

v The command does not exist.

v Incomplete command search path.

v Incorrect access permissions on the command.

v System resource problem.

User Response: Correct the problem and tryagain. If the problem persists, contact IBMSupport with the following information:


1. Message number


DBI1520E Minimum terminal display size is24 x 80.

Explanation: Your current terminal or windowsize is not large enough. This program requires aminimum terminal display size of 24 lines by 80columns.

User Response: Check your terminal orwindow size and try again.

DBI1521E An attempt to read in the terminalcapability information failed.

Explanation: An error was detected whenattempting to initialize your terminal display.There are two conditions where this type of errorwould occur:

v The function cannot find the environmentvariable TERM or it is unable to find thecorrect terminfo database entry for theterminal.

v There is not enough memory space availablewhen initializing your terminal display.

User Response: Set your environment variableTERM to a correct terminal type. If the problempersists, try to terminate other applicationsrunning on the system that may be using largeamounts of memory. If the problem still occurs,contact IBM Support with the followinginformation:

1. Message number


DBI1522E An attempt to restore the terminalcapability information failed.

Explanation: An error was detected whenattempting to restore your terminal display tothe original state.

User Response: Set your environment variableTERM to a correct terminal type. If the problempersists, try to terminate other applicationsrunning on the system that may be using largeamounts of memory. If the problem still occurs,

contact IBM Support with the followinginformation:

1. Message number


DBI1530E Cannot unpack image file.

Explanation: An error has occurred whileunpacking the tar image from the distributionmedia. One of the following situations hasoccurred:

v The given path name is a non-existingdirectory.

v The file system does not have enough space.

v The access permission on the given path isincorrect.

v The tar command was not found in yourcurrent search path.

User Response: Restart the install process andretry with a correct path name.

DBI1540E An invalid distribution mediapath is specified.

Explanation: An error was detected whenattempting to locate the installable images on thedistribution media. One of the following errorsoccurred:

v The file system associated with the given pathis not properly mounted.

v An incorrect access permission has beenassigned to the given path.

User Response: Check the path and try thecommand again. Note that all file and directorynames in Unix are case sensitive.

DBI1541E An attempt to open or read fromthe given status file failed.

Explanation: An error was detected whenattempting to open or read from the status file. Ifthe status file has not been modified manually,then one of the following errors occurred:

v An incorrect file path has been specified.

v An incorrect access permission has beenassigned to the status file.


v The file system associated with the given pathis not properly mounted.

User Response: Check the path and try thecommand again. Note that all file and directorynames in Unix are case sensitive. If the problempersists, contact IBM Support with the followinginformation:

1. Message number


3. Status file

DBI1550E There is not enough disk space onthe file system.

Explanation: An error was encountered whentrying to allocate more disk space on the filesystem.

User Response: Retry the command afterenough space has been freed up for the specifiedoperation.

DBI1570I Usage:

db2olset InstName

Explanation: An incorrect argument wasentered for the db2olset command. Validarguments for this command are:



InstNameis the name of the instance you wish toset up to use with the OLAP Starter Kit


db2olset InstName

DBI1631E An error was encountered whilecreating a sample database.

Explanation: One of the following situations hasoccurred:

v There is not enough disk space on the filesystem.

v The DB2 product has not been installedproperly, or some of the component files aremissing.

User Response: If this is not a disk spaceproblem, try to re-install the product. If theproblem persists, turn trace on and retry thesteps to create a database through the CLP. Then,save the trace information to a file and contactIBM Support with the following information:

v Message number


v Trace file

DBI1632E An error was encountered whileconfiguring to “auto-start”instance.


v The feature to “auto-start” the instance isalready enabled.

v An error was encountered while adding anentry to “/etc/inittab” file. This could be a filepermission problem.

v The db2uit tool is missing.

User Response: If any of the above threesituations apply, then correct the problem andretry the command. If the problem persists,contact IBM Support with the followinginformation:

v Message number


DBI1633E An error was encountered whileremoving the configuration to“auto-start” instance.


v The feature to “auto-start” the instance is notenabled.

v An error was encountered while removing anentry to “/etc/inittab” file. This could be a filepermission problem.

v The db2uit tool is missing.


User Response: If any of the above threesituations apply, then correct the problem andretry the command. If the problem persists,contact IBM Support with the followinginformation:

v Message number


DBI1634W Unable to update /etc/rc.db2v08 toauto-mount dlfs file system.

Explanation: An attempt to update/etc/rc.db2v08 to enable the auto-mounting ofthe dlfs file system on system reboot has failed.

User Response: Manually edit the file/etc/rc.db2v08, and add the following lines to it:

if [ -x /etc/rc.dlfs ]; then/etc/rc.dlfs

fi

DBI1635E An error was encountered whileadding to the AdministrationServer group list.

Explanation: An error was detected whenattempting to add a DB2 instance to theAdministration Server group list.

User Response: If you are running thiscommand on an NIS client, try to append thegroup name of the DB2 instance to the secondarygroup of the Adminstration Server on your NISserver.

DBI1637W By clicking OK, your previoussettings for the instance will belost.

User Response: Click OK if you wish toproceed. Otherwise click Cancel.

DBI1639E Cannot set up a new instance.

Explanation: The given instance name does notbelong to an existing instance.

User Response:

v Create a new instance.

– If you are running the interactive installer,from the instance creation panel choose tocreate a new instance.

– If you are running the response file installer,provide additional information for the user.

v Enter the name of an existing instance.

DBI1640W The specified instance is not aserver instance.

Explanation: Some of the DB2 components canonly be configured for DB2 server instances.

User Response:

v If the specified instance is a client instance andDB2 server product is installed, run db2iupdtto update the client instance to a serverinstance.

v If the specified instance is a Data LinkAdministration Server, exit the installer and setup the instance from the command line, if youwish to do so.

DBI1651E The specified UID is invalid.

Explanation: An invalid UID has been entered.One of the following situations has occurred:

v The given UID is already assigned to anexisting user on the system.

v The given UID either is too long or consists ofinvalid characters.

v The given UID less than or equal to 100.

User Response: Retry with a different user ID.

DBI1652E The specified user name isinvalid.

Explanation: An invalid user name has beenentered. One of the following situations hasoccurred:

v The given user name already exists on thesystem.

v The given user name already exists on thesystem but under a different group name.

v The given user name either is too long orconsists of invalid characters.


User Response: Retry with a different username.

DBI1653E The specified group is invalid.

Explanation: An invalid group ID or groupname has been entered. One of the followingsituations has occurred:

v The given group ID already exists but under adifferent group name on the system, or thegiven group name already exists but under adifferent group ID.

v The given group ID or group name either istoo long or consists of invalid characters.

v The given group ID is less than or equal to100.

User Response: Retry with a different group IDor group name.

DBI1654E The specified directory is invalid.

Explanation: An invalid directory has beenentered. One of the following situations hasoccurred:

v The given user already exists but has adifferent home directory specified on thesystem.

v The given directory is either too long orconsists of invalid characters.

User Response: Retry with the user’s homedirectory specified on the system or a differentdirectory.

DBI1655E The specified password is invalid.

Explanation: An invalid password has beenentered. One of the following situations hasoccurred:

v The given password has a length of zero.

v The given password does not match with theverify password.

v The given password contains invalidcharacters.

User Response: Retry with a differentpassword.

DBI1657E Instance name already in use.

Explanation: An instance with the same namealready exists on your system.

User Response: Verify with the list of instancesas reported by the “db2ilist” command. Retrywith a different user name.

DBI1701E One or more of the TCP/IPparameters specified is invalid.


v The length of service name exceeds 14characters.

v The port number specified is out of range.This number must be between 1024 and 65535.

User Response: Correct the problem and tryagain.

DBI1702E The specified service name or portnumber conflicts with existingvalues in the TCP/IP services file.

Explanation: The service name or port numberentered by the user conflicts with existing valuesin the TCP/IP services file. The service namemay already be used with a different portnumber, or the port number may already be usedwith a different service name.

User Response: Specify a service name and portnumber that does not conflict with existingentries in the services file.

DBI1703E No valid service name or portnumber found.

Explanation: No valid service name or portnumber for this instance can be found in theTCP/IP services file. This information is eithermissing or is invalid.

If you installed “DB2 Extended Server Edition”product, a service name must be specified for theinstance before using this command.

User Response: For more information, refer tothe “DB2 Enterprise - Extended Edition”. Specifyvalid service name and port number for this


instance and enter this command again.

DBI1704W TCP/IP is not running on yoursystem.

Explanation: TCP/IP is not running on yoursystem. TCP/IP services file will not be updated.

DBI1709E An error was encountered whenupdating the TCP/IP services file.

Explanation: An attempt to add a service nameand port number to the TCP/IP services filefailed.

User Response: If the user wishes to use theservice name instead of the port number in thenode directory entry, the node must be manuallyuncatalogued and then recatalogued using theservice name. The services file must also beupdated manually. If Network InformationServices (NIS) is being used, the local servicesfile may have been updated but the NIS servermust be updated manually. In this case, the nodewas also catalogued using the port number.

DBI1711E One or more of the IPX/SPXparameters specified is invalid.


v the fileserver, objectname, or ipx_socketparameter is null.

v the fileserver parameter is set to * butobjectname is not *.

v the objectname or ipx_socket value specified isnot unique.

v the ipx_socket value specified is not in thevalid range.


DBI1715E NetWare User ID or NetWarePassword is invalid.

Explanation: The NetWare User ID andNetWare Password that you specify must alreadyexist and is used to register the DB2 ObjectName at a NetWare file server and must have

supervisory or equivalent authority.


DBI1720E The specified User ID or GroupID cannot be added since NIS isrunning.

Explanation: NIS is running on your system. Anew User ID or Group ID cannot be createdwhile you have NIS running on your system.

User Response: Use a previously created UserID or Group ID and try again.

DBI1722E The specified service cannot beadded to the /etc/services filebecause NIS is running.

Explanation: NIS is running on your system. Anew service cannot be added to the /etc/servicesfile while you have NIS running on your system.

User Response: Use a previously createdservice name and port number from the/etc/services file and try again.

DBI1725W Cannot create Agent Daemon andLogger services for DataWarehouse Agent.

Explanation: TCP/IP is not running on thesystem. The install will proceed but you need tocreate Agent Daemon and Logger servicesmanually.

User Response: Activate TCP/IP on the systemand run the installer.

DBI1740W Security Risk.

Explanation: Using the default instance user IDhere allows this instance to have full accesspermission to other instances on your system. Itis highly recommended to use a different user IDfor security reasons.

User Response: To avoid the possibility of asecurity risk, use a different user ID.


DBI1741W Protocol not detected.

Explanation: You have selected a protocol thatis not detected. DB2 Installer cannot update all ofthe protocol’s required settings. However, youcan provide values for this protocol’s settings.


DBI1744W The DB2 Data Links ManagerAdministrator is not created.

Explanation: You have not created the DB2Data Links Manager Administrator. Without theDB2 Data Links Manager Administrator, youcannot administer the DB2 Data Links Manager.


DBI1745W The Administration Server is notcreated.

Explanation: You have not created aAdministration Server. Without theAdministration Server, you cannot provideservices to support client tools that automate theconfiguration of connections to DB2 databases,and cannot administer DB2 from your serversystem or a remote client using the ControlCenter.


DBI1746W DB2 Instance is not created.

Explanation: You have not created a DB2Instance. A DB2 Instance is an environmentwhere you store data and run applications.


DBI1747W The specified directory alreadyexists.

Explanation: The directory specified in theHome Directory field already exists. If youchoose to use this directory you may run intopermission problems.

User Response: Choose a different directory ifthis may be a problem.

DBI1750W Security Risk.

Explanation: Using the default instance user IDhere allows this instance to have full accesspermission to other instances on your system. Itis highly recommended to use a different user IDfor security reasons.

User Response:

v Press OK to continue, or

v Press Cancel to enter a different user ID.

DBI1751W Protocol not detected.

Explanation: You have selected a protocol thatis not detected. DB2 Installer cannot update all ofthe protocol’s required settings. However, youcan provide values for this protocol’s settings.

User Response:

v Press OK to provide protocol settings, or

v Press Cancel to ignore.


Explanation: You have not created anAdministration Server. Without the DB2Administration Server, Data Warehouse Agentwill not be fully set up.

User Response:


v Press Cancel to go back.

DBI1754W The DB2 Data Links ManagerAdministrator is not created.

Explanation: You have not created the DB2Data Links Manager Administrator. Without theDB2 Data Links Manager Administrator, youcannot administer the DB2 Data Links Manager.

User Response:





Explanation: You have not created aAdministration Server. Without theAdministration Server, you cannot provideservices to support client tools that automate theconfiguration of connections to DB2 databases,and cannot administer DB2 from your serversystem or a remote client using the ControlCenter.

User Response:



DBI1756W DB2 Instance is not created.

Explanation: You have not created a DB2Instance. A DB2 Instance is an environmentwhere you store data and run applications.

User Response:



DBI1757W The specified directory alreadyexists.

Explanation: The directory specified in theHome Directory field already exists. If youchoose to use this directory you may run intopermission problems.

User Response:

v Press OK to use this directory, or


DBI1758W DB2 Instance or AdministrationServer detected.

Explanation: You have selected to removed theentire DB2 product. However, a DB2 Instance orAdministration Server has been detected on yoursystem. If you remove the DB2 product withoutdropping these instances first, your DB2Instances may not be able to function properlylater on.

User Response:



DBI1759W DB2 Instance or AdministrationServer configurations detected.

Explanation: You do not have theAdministration Server selected. This will causeall of your Administration Server and DB2Instance configurations to be discarded.

User Response:



DBI1760E To set up pkg-name, you will needto install the package.

Explanation: You have chosen to configure aDB2 component for an instance. You will not beable to do so unless the package is installed.

User Response: Install the package and tryagain.

DBI1761W Software pre-requisites violatedon fileset or package pkg-name.

Explanation: An error occurred when verifyingsoftware pre-requisites on the above fileset orpackage. Continuing may result in the productnot functioning properly. Do you want tocontinue without installing its pre-requisites?

User Response:

v Press OK to continue without installing itspre-requisites, or

v Press Cancel to abort installation.

DBI1762W Software dependencies violatedon fileset or package pkg-name.

Explanation: An error occurred when verifyingsoftware dependencies on the above fileset orpackage. Continuing may result in removing allof its software dependencies. Do you want toremove its software dependencies?

User Response:




DBI1763I English HTML documentationfiles will also be installed.

Explanation: The English HTML documentationfiles are required when you select anynon-English HTML documentation files forinstallation. This is to ensure that users will beable to search the entire DB2 documentationlibrary.

DBI1765W A non-existing user ID, InstName,has been detected from theregistry.

Explanation: The registry is containing anon-existing user ID. This can be caused by justremoving the instance user ID without firstdropping the instance. This will not affect thenormal operation of DB2, but it is recommendedto remove this obsolete user ID from the instancelist in the registry.

User Response: To remove this user ID fromthe registry with the command: db2iset -d“<InstName>”

DBI1766W Cannot change the secondarygroup list of userId.

Explanation: A code, “<code>”, is returnedwhen attempting to change the secondary grouplist of the given user ID. One of the followingsituations has occurred:

v NIS is running.

v One or more processes are currently beingexecuted under the given user ID.

User Response: You must add the group ID,“<groupId>”, to the secondary group list of theuser ID, “<userId>”, so that the AdminstrationServer can function properly.

v If there happens to be any process run underthe given user ID, terminate all of theseprocesses and follow the instructions above tosetup the secondary group list of this user ID.

v If you are running this command on an NISclient, try the above instructions to setup thesecondary group list of this user ID on yourNIS server.

DBI1767W DB2 registry may containcorrupted information.

Explanation: The registry may contain invalidinstance information. This is probably due to thefact that an instance or the Administration Serveris not deleted properly before removing the DB2product. If you are re-installing the product andwant to keep the existing instance information inthe registry, press Cancel. Otherwise, press OK tore-create the registry. Do you want to re-createthe registry?

User Response:

v Press OK to re-create the registry, or

v Press Cancel to keep the current registryinformation.

DBI1768W Unable to add db2profile to the.profile file or db2cshrc to the.login file of user inst-name.

Explanation: DB2 has failed to modify the.profile file or the .login file of this user. Thesefiles may not exist, or you may not have writepermission to them. Without the modificationyou need to set your environment manually eachtime when you log in as this user to use DB2.

User Response: Add the following line to the.profile file or the .login file:

. db2profile to the .profile file, orsource db2cshrc to the .login file

See the Quick Beginning Guide for more detailson how to set the DB2 environmentautomatically.

DBI1769W Unable to remove DB2 profileentry from the .profile or the.login file of inst-name.

Explanation: DB2 has failed to comment out theDB2 environment setting line in the .profile file


or the .login file of this user. The next time youlog in as this user, you may get a message sayingthat the file db2profile (or db2cshrc) cannot befound. There can be different reasons:

v The two files (.profile and .login) may notexist.

v You may not have write permission on thesefiles.

User Response: If you receive a messageconcerning missing db2profile or db2chsrc, locateyour .profile or .login file and comment out thefollowing:

. sqllib/db2profile from your .profile filesource sqllib/db2cshrc from your .login file

DBI1770E Unable to update the file /etc/vfs.

Explanation: The following DB2 Data LinksManager specific entry is required in the/etc/vfs file:

dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none

where dlfs_num is to be set to 12, or somenumber between 8 and 15 if 12 is alreadyassigned to another fs. The installation processhas failed to insert this line into the /etc/vfs file.There may be different reasons:

v You do not have write permission to this file.

v The range 8-15 is all taken up, no number canbe assigned to dlfs.

User Response: Manually edit the /etc/vfs file,and add the entry for dlfs into this file.

DBI1771I File /etc/vfs has been copied to/tmp/.db2.etcvfs.backup.

Explanation: For DB2 Data Links Manager towork, the following line has to be inserted intothe /etc/vfs file:

dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none

A backup copy of the original /etc/vfs file hasbeen placed in /tmp/.db2.etcvfs.backup.

DBI1775W Modified an existing /etc/rc.dlfsfile.

Explanation: DB2 has modified an existing/etc/rc.dlfs file with the new dlfs file systemmount entry.

User Response: Examine the file /etc/rc.dlfs toensure that all entries are correct.

DBI1780W DB2 Data Links Manager is notsupported on the version of yourcurrent operating system.

Explanation: The version of your currentoperating system is not supported to run DB2Data Links Manager. However, you can stillinstall and configure the product at your ownrisk. The following is a list of supportedoperating systems for DB2 Data Links Manager:

v “<OSlist>”

DBI1781E Usage: -l <language> -t <topic>[-p <path>] [-d]

Valid topics include:

core Core DB2 Information

admin Administration Information

ad Application DevelopmentInformation

wareh Business IntelligenceInformation

conn DB2 Connect Information

start Getting Started Information

tutr Tutorial Information

opt Optional ComponentInformation

Valid languages include:


DBI1782E No language specified.

Explanation: You must specify at least onelanguage from those available.

User Response: Issue the command with noparameters for a complete list.

DBI1783E No topics specified.

Explanation: You must specify at least one topicfrom those available.


DBI1784E Language not available.

Explanation: You specified a language that isnot available for installation.


DBI1785E Topic Package not available.

Explanation: You specified a documentationpackage that is not available for installation.


DBI1790E ODSSI utilities have not beeninstalled, unable to create DB2search index.

Explanation: ODSSI utilities have not beeninstalled. These utilities (config_search,config_view and config_help) are required tocreate the search index for the DB2 onlinedocumentation.

User Response: Install the ODSSI utilities, thenrun the following commands:

/opt/IBM/db2/V8.x/doc/db2insthtml lang_locale,where x is 1 or FPn,where n is the FixPak number

to create the search index for DB2 documentationin the language locale lang_locale. Note thatwhenever you install documentation in any

language, English documentation is installed aswell. So you should also run the followingcommand to index the English files:

/opt/IBM/db2/V8.x/doc/db2insthtml en_US,where x is 1 or FPn,where n is the FixPak number

DBI1791W Possible error increating/removing DB2 searchindex for html file.

Explanation: DB2 runs the system utilitiesconfig_view and config_help to create or removeDB2 search index to be used with SCOHELP.However, error messages may be returned ifthere exists other non-DB2 indexes on the systemthat have not been created/removed properly.

User Response:

v If you were creating the DB2 index, you canstart up SCOHELP and check to see if the DB2entry has been added to the topics panel. Testsearching for a string like ″TCP/IP″ and see ifyou get any results. If you are able to do thesearch, DB2 search index has been createdsuccessfully.

v If you were removing the DB2 index, you canstart up SCOHELP and verify that the DB2entry has been removed from the topics panel.If the entry is gone, then the DB2 index hasbeen successfully removed.

v If you cannot verify that the DB2 index hasbeen successfully created or removed, contactIBM support.

DBI1792I Creating search index for DB2documentation files, please wait ...

Explanation: Search index for DB2documentation files are being created. Dependingon the language(s) you have selected, this maytake some time.

DBI1793W The user ID userID is unknown.

Explanation: The specified user is unknown orcannot be found on the current system.

User Response: Please verify that the user


exists on this system and try again.

DBI1794E Attempt to put too many iconsinto one group.

Explanation: An attempt has been made toplace more icons into the required folder thanare allowed by the desktop manager.

User Response: Please remove any unnecessaryicons from your desktop and retry the command.

DBI1795E There is insufficient free memoryto create all the required icons.

Explanation: The icon creation utility ran out ofmemory during icon generation.

User Response: Close any unnecessaryprograms and try again.

DBI1796W Attempt to create icons in adirectory without properpermissions.

Explanation: This user ID does not have thepermissions required to create icons for therequested user.

User Response: Log on as a user with rootauthority or with the permissions required tocreate files in the user directory and retry thecommand.

DBI1797I Icons successfully created.

DBI1900N The Windows NT Cluster supportis not accessible.

Explanation: DB2 is unable to access theWindows NT Cluster.

User Response: Ensure the Windows NTCluster support has been correctly installed andthe Cluster Service has been started.

DBI1901N An error occurred whenattempting to update the userrights for the DB2/NT clusterservice.

Explanation: DB2 encountered an error whenattempting to grant the necessary user rights tothe account specified for use with the DB2service.

User Response: Ensure a valid account hasbeen specified and that you have the necessaryprivilege to grant user rights.

DBI1902N An error occurred whenattempting to update the DB2/NTcluster service configuration.

Explanation: DB2 encountered an error whenattempting to update the DB2/NT cluster serviceconfiguration.

User Response: Ensure the Service Database hasnot been locked and is accessible. Also ensurethe DB2/NT Cluster Service has been created.

DBI1903N An error occurred when accessingthe Cluster registry.

Explanation: DB2 encountered an error whenattempting to read or update the Windows NTCluster registry.

User Response: Ensure the Windows NTCluster support has been correctly installed andthe Cluster Service has been started. Ensure thatthe current logon user account has sufficientauthority to access the Cluster registry.

DBI1904N The DB2 instance is notClustered.

Explanation: DB2 attempted to access aninstance to perform cluster operations but theinstance was not identified as a DB2 Clusterinstance.

User Response: Verify the instance was createdwith the Cluster options. The instance may bedropped and re-created using the Cluster optionbut the Node directory, Database Directory, andDatabase Manager Configuration file will be lost.


DBI1905N A System Error occurred during aDB2 Cluster operation.

Explanation: A system error was detected whileDB2 was performing a Cluster operation.

User Response: Check to make sure theWindows NT operating system is at the correctlevel for Cluster Support.

Also ensure the Windows NT Cluster supporthas been correctly installed and the ClusterService has been started.

DBI1906N A error occurred while attemptingto add a node to a DB2 Clusterinstance.

Explanation: An error was encountered whileattempting to update a node to support a DB2Cluster instance.

User Response: Ensure the remote system ison-line and accessible over the LAN. Also ensureyou have the necessary privilege to update theRegistry on the remote system.

DBI1907N A error occurred while attemptingto delete a node from a DB2Cluster instance.

Explanation: An error was encountered whileattempting to delete a node from a DB2 Clusterinstance.


A workstation cannot drop cluster support fromitself. The instance must be dropped to performthis task.

DBI1908N A error occurred while attemptingcreate the instance profile on aremote system.

Explanation: A error was detected whileattempting to create the instance profile on aremote system to enable Cluster Support.

User Response: Ensure the remote system is

on-line and accessible over the LAN. Also ensureyou have the necessary privilege to update theRegistry on the remote system.

DBI1909N A error occurred while attemptingdelete the instance profile on aremote system.

Explanation: A error was detected whileattempting to delete the instance profile on aremote system to disable Cluster Support.


DBI1910N Usage : DB2NCRT -I:Instance-Name-C:cluster-node

Explanation: The user specified incorrectarguments to the DB2NCRT command.

User Response: Re-issue the commandspecifying a clustered instance and a validworkstation name for the cluster node.

DBI1911N Usage : DB2NLIST-I:Instance-Name

Explanation: The user specified incorrectarguments to the DB2NLIST command.

User Response: Re-issue the commandspecifying a clustered instance.

DBI1912I The DB2 Cluster command wassuccessful.

Explanation: The user request was successfullyprocessed.


DBI1913N Unable to connect to the remotemachine registry.

Explanation: DB2 encountered an error whenattempting to connect to the Windows NTregistry on a remote machine.

User Response: Ensure that the target machine


is running and that the computer name specifiedis correct. Also ensure that the current logon useraccount has sufficient authority to connect to theremote machine registry.

DBI1914N Unable to connect to the Clusterregistry.

Explanation: DB2 encountered an error whenattempting to connect to the Windows NTCluster registry.

User Response: Ensure that the Windows NTCluster support has been correctly installed andthe Cluster Service has been started.

DBI1915N The target machine does notbelong to the Windows NTCluster.

Explanation: The command failed for one of thefollowing reasons:

(1) The db2iclus utility attempted toremove a machine from a DB2 MSCSinstance but the target machine had notbeen added to the DB2 MSCS instance,or

(2) The db2iclus utility attempted to add amachine to a DB2 MSCS instance butthe target machine does not have therequired Windows NT Cluster supportsoftware installed.

User Response: Follow the actioncorresponding to the cause of the problem:

(1) Ensure that the machine is part of theDB2 MSCS instance by running the″db2iclus list″ command, or

(2) Install the Windows NT Clustersoftware on the target machine andissue the command again.

DBI1916N The instance name specified isnot valid.

Explanation: The instance specified by theinstance name parameter does not exist for thelocal machine.

User Response: To find a list of valid instances,run the db2ilist command. Issue the commandagain using a valid instance name.

DBI1918N An error occurred when accessingthe Windows NT registry.

Explanation: DB2 encountered an error whenattempting to read or update the Windows NTregistry of the target machine.

User Response: Ensure that the current logonuser account has sufficient authority to access theWindows NT registry of the target machine. Ifthe problem persists, contact your IBM servicerepresentative for assistance.

DBI1919N An error occurred when accessingthe TCP/IP services file.

Explanation: DB2 encountered an error whenreading or updating the TCP/IP services file.

User Response: Ensure that the services fileexists in the system and that the file can beaccessed for read and write authority. Also,ensure that the contents of the file are valid andno duplicate of entries exist in the services file.

DBI1920N The DB2 instance profile pathparameter is not valid.

Explanation: DB2 is unable to access the DB2instance profile path specified because the pathdoes not exists or write access has not beengiven to the current logon user account.

User Response: Ensure that the path name forthe DB2 instance profile points to a validdirectory and that the current logon user accounthas write access to the directory.

DBI1921N The user account or password isnot valid.

Explanation: The user account or the passwordis not valid.

User Response: Issue the command again withthe correct account.


DBI1922N The host name is not valid.

Explanation: The TCP/IP host name parameteris not valid or does not exist.

User Response: Ensure that TCP/IP isoperational on the system. If a domain nameserver is used, ensure that the domain nameserver machine is active. Issue the commandagain using the correct TCP/IP host name.

DBI1923N The TCP/IP port range parameteris not specified.

Explanation: The db2icrt utility requires theTCP/IP port range to be specified when creatinga partitioned database instance if the entries forTCP/IP port range for the instance have notbeen added to the services file.

User Response: Choose a range of TCP/IPports that are available for the system and issuethe db2icrt command again with the -r option.

DBI1924N The computer name is not valid.

Explanation: The computer name parameter isnot valid

User Response: Ensure that the target machineis running and that the computer name specifiedis correct. Also ensure that the current logon useraccount has sufficient authority to connect to thetarget machine registry.

DBI1925N Unable to query the status of theDB2 service.

Explanation: DB2 is unable to query the servicestatus for the DB2 service.

User Response: Ensure that the DB2 serviceexists on the target machine. Ensure that thecurrent logon user account has sufficientauthority to query the service status on the targetmachine.

DBI1926N The password is expired.

Explanation: The account password hasexpired.

User Response: Change your password, thenretry the request using the new password.

DBI1927N Usage:

db2iclus { ADD /u:Username,Password[/m:Machine name] |DROP [/m:Machine name] |MIGRATE /p:Instance profile path |UNMIGRATE }[/i:instance name][/DAS DASname][/c:Cluster name]

Explanation: Valid arguments for this commandare:

ADD to add an MSCS node to a DB2 MSCSinstance

DROP to remove an MSCS node from a DB2MSCS instance

MIGRATEto migrate a non-MSCS instance into anMSCS instance

UNMIGRATEto undo the MSCS migration

Valid options for this command are:

/DAS to specify the DAS instance name. Thisoption is required when performing thecluster operation against the DB2Administration Server.

/c to specify the MSCS cluster name ifdifferent from the default/currentcluster

/p to specify the instance profile path. Thisoption is required when migrating anon-MSCS instance into an MSCSinstance

/u to specify the account name andpassword for the DB2 service. Thisoption is required when adding anotherMSCS node to the DB2 MSCSpartitioned database instance

/m to specify the remote computer namefor adding or removing an MSCS node


/i to specify the instance name if differentfrom the default/current instance

User Response: Enter the command again usingvalid parameters

DBI1928N The user account is not specified.

Explanation: When creating a partitioneddatabase instance or adding a node to apartitioned database instance, you must specifythe user account parameter. Under the WindowsNT environment, each database managerpartition (or MPP node) is required to run undera valid Windows NT account to access thenetwork share which contains the instancedirectory.

User Response: Issue the command again withthe -u option to specify the user account nameand password.

DBI1929N The instance is already configuredfor MSCS support.

Explanation: An attempt to migrate an instanceinto an MSCS instance failed because the theinstance is already configured for MSCS support.


DBI1930N The target machine is already partof the DB2 MSCS instance.

Explanation: An attempt to add an MSCS nodeto the DB2 MSCS instance failed because Thetarget machine is already part of the DB2 MSCSinstance.

User Response: No action is necessary.

DBI1931N The database partition server(node) is active.

Explanation: The database partition server cannot be dropped or modified because it is active.

User Response: Ensure that the databasepartition server is stopped before attempting todrop or change it. To stop a database partitionserver, use the db2stop command as follow:

db2stop nodenum <node-number>

DBI1932N Can not add the databasepartition server on a remotemachine because the sameinstance on that machine alreadyexists.

Explanation: The db2ncrt command failed toadd a new database partition server on a remotemachine because there is an existing instance onthe remote machine.

User Response: If the instance on the remotemachine is no longer used, remove the instanceby running the db2idrop command on theremote machine.

DBI1933N The database partition server cannot be moved to a new machinebecause there is existingdatabase(s) in the system.

Explanation: When the db2nchg command isissued with the /m:machine option, thecommand will move the database partitionserver to a new machine. The db2nchg will fail ifthere is existing database(s) in the system.

User Response: To move the database partitionserver to a new machine when there isdatabase(s), use the db2start restart command.For more information on the db2start command,refer to the DB2 Command Reference.

DBI1934N Usage:

db2iupdt InstName/u:username,password[/p:instance profile path][/r:baseport,endport][/h:hostname]

Explanation: An invalid argument was enteredfor the db2iupdt command. Valid arguments forthis command are:

InstNamethe name of the instance

/u to specify the account name andpassword for the DB2 service. This


option is required when creating apartitioned database instance.

/p to specify the new instance profile pathfor the updated instance.

/r to specify a range of TCP/IP port to beused by the partitioned databaseinstance when running in MPP mode.The services file of the local machinewill be updated with the followingentries if this option is specified:

DB2_InstName baseport/tcpDB2_InstName_END endport/tcp

/h to override the default TCP/IPhostname if the there are more than oneTCP/IP hostname for the currentmachine.

User Response: Enter the command again usingvalid arguments.

DBI1935N The db2iupdt command failed toupdate the instance directory.

Explanation: The db2iupdt command failed toupdate the instance directory because of one ofthe following reasons:

(1) the db2audit.cfg file is missing from the\SQLLIB\CFG directory.

(2) the db2iupdt command does not havethe required authority to create files orsub-directories within the instancedirectory.

User Response: Ensure that the db2audit.cfg fileexists in the \SQLLIB\CFG directory and thatthe current logon account has sufficient authorityto create files and directories in the instancedirectory. The instance directory is located in\SQLLIB\InstName (where InstName is thename of the instance).

DBI1936N The db2iupdt command failed toupdate the database managerconfiguration file.

Explanation: The db2iupdt command failed toupdate the database manager configuration file

because the previous database managerconfiguration file is corrupted or missing. Thecurrent instance is in inconsistent state and cannot be used.

User Response: Copy the default databasemanager configuration file to the instancedirectory then re-submit the command. Theinstance directory is located in\SQLLIB\InstName. The default databasemanager configuration file is named db2systmand can be found in the \sqllib\cfg directory.

DBI1937W The db2ncrt commandsuccessfully added the node. Thenode is not active until all nodesare stopped and started 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, including thenew node.

DBI1940N The DB2 Administration Server isactive.

Explanation: The DB2 Administration Servercannot be modified because it is active.

User Response: Ensure that the DB2Administration Server is stopped beforeattempting to change it. To stop the DB2Administration Server, use the db2admincommand as follows:

db2admin stop

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


DBI1942N The DB2 Administration Serveralready exists on the targetmachine.

Explanation: The operation could not becompleted because the DB2 AdministrationServer already exists on the target machine.

User Response: Remove the DB2Administration Server from the target machineand retry the operation.

DBI1943N The DB2 Administration Server isnot Clustered.

Explanation: DB2 attempted to access a DB2Administration Server to perform clusteroperations but the DB2 Administration server isnot configured for MSCS support.

User Response: Verify the DB2 AdministrationServer is configured for MSCS support.

DBI1944N The DB2 Administration Server isalready configured for MSCSsupport.

Explanation: An attempt to migrate a DB2Administration Server failed because the DB2Administration Server is already configured forMSCS support.


DBI1950W The instance instance-name isalready in the instance list.

Explanation: The instance that is being createdor migrated is already in the instance list.

User Response: Verify that the list of instancesas reported by the db2ilist command is correct.

DBI1951W The instance instance-name was notfound in the instance list.

Explanation: The specified instance was notfound in the instance list.

User Response: Verify that the list of instancesas reported by the db2ilist command is correct.

DBI1952E The instance name instance-name isinvalid.

Explanation: The instance name is invalid. Itcannot:

1. be more than 8 characters long.

2. start with “sql”, “ibm” or “sys”.

3. start with a numeral or contain charactersother than a-z, $, #, @, _, or 0-9.

User Response: Try the command again with avalid instance name.

DBI1953E The instance is active.

Explanation: An attempt was made to drop aninstance which is active.

User Response: Make sure all applications thatare using the instance have finished executingbefore stopping the instance by issuing a db2stop(from that instance’s user ID.)

DBI1954E The instance name is currentlyused by the DB2 Admin Server.

Explanation: The instance cannot be createdbecaused it is currently used by the DB2 AdminServer.

User Response: Try the command again with adifferent instance name.

DBI1955E Usage: db2idrop [-h] [-f] InstName




InstNameis the name of the instance


db2idrop [-h] [-f] InstName


DBI1956E Usage: db2ilist [-w 32|64] [-p] [-a][inst_name]

Explanation: An incorrect argument wasentered for the db2ilist command. Validarguments for this command are:


-w 32|64lists the 32 or 64 bit instances. The -woption can be used with the -p option,and is superseded by the -a option.

-p lists the DB2 install path that aninstance is running from. The -p optioncan be used with the -a option, and issuperseded by the -a option.

-a returns all relevant informationincluding the DB2 install path associatedwith an instance, as well as its bitwidthinformation (32 or 64).

inst_namereturns the information for the specifiedinstance. If no instance is named,db2ilist returns information on allinstances of the current DB2 release.


db2ilist [-w 32|64] [-p] [-a] [inst_name]

DBI1957E The syntax of the db2icrtcommand is incorrect.

Explanation: The db2icrt utility creates adatabase instance:

db2icrt InstName [-s {ese|wse|client|standalone}][-p instance profile path][-u username,password][-h hostname][-c Cluster name][-r baseport,endport][-?]


-s to specify the type of instance created:

ese for Enterprise Server Edition

wse for Workgroup Server Edition

client for client

standalonefor database server with localclients

-p to specify the instance profile path.

-u to specify the account name andpassword for the DB2 service. Thisoption is required when creating an eseinstance.

-h to override the default TCP/IPhostname if the there are more than oneTCP/IP hostname for the currentmachine. The TCP/IP hostname is usedwhen creating the default node (node 0).

-c to specify the MSCS cluster name. Thisoption is specified to create a DB2instance that supports MSCS.

-r to specify a range of TCP/IP port to beused by the partitioned databaseinstance when running in MPP mode.The services file of the local machinewill be updated with the followingentries if this option is specified:

DB2_InstName baseport/tcpDB2_InstName_1 baseport+1/tcpDB2_InstName_2 baseport+2/tcpDB2_InstName_END endport/tcp

-? to display help

User Response: Enter the command again usingthe valid parameters.

DBI1958N The instance profile cannot beadded to the registry.

Explanation: An error occurred when addingthe instance profile to the registry. The instancewas not created.

User Response: Contact your IBM servicerepresentative.


DBI1959N The instance directory cannot becreated.

Explanation: An error occurred when creatingthe required files or directories for the newinstance. The instance was not created.

User Response: Ensure that you have writeaccess to the location where the instancedirectory is created. The instance directory iscreated under the path where the product isinstalled. You may use the DB2INSTPROF ProfileVariable to specify a different location for theinstance directory.

DBI1960N The DB2 service cannot becreated.

Explanation: An error occurred whenregistering a DB2 service because of one of thefollow reasons:

1. A service of the same name already exists orwas marked as deleted but not cleaned upuntil the next system reboot.

2. You don’t have sufficient access to create aWindows service

User Response:

1. Ensure that the name of the instance does notmatch any of the existing Windows services.The list of services in the system can befound in the Windows registry underHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services. If the servicewas marked as deleted, you have to rebootthe machine to have the service removedfrom the system.

2. Log on to a user account that belongs to thelocal Administrators group and retry theoperation.

DBI1961N The node key for the newinstance cannot be added to theregistry.

Explanation: An error occurred when adding anode key for the new instance in the instanceprofile registry.


DBI1962N The new node can not be addedto the registry.

Explanation: An error occurred when addingthe new node to the instance profile registry.


DBI1963N An error occurred when grantingthe user rights to the account forthe instance.

Explanation: When configuring the account forthe DB2 Service, the account must be granted theuser rights :

1. Act as part of the operating system

2. Create a token object

3. Increase quota

4. Logon as a service

5. Replace a process level token

An error occurred when granting the user rightsto the account for the instance.

User Response: If the machine belongs to anNT domain, ensure that the primary domaincontroller is active and accessible over thenetwork. Otherwise, contact your IBM servicerepresentative.

DBI1964N The logon account cannot beassigned to the DB2 service.

Explanation: An error occurred when assigninga logon account to the DB2 service.

User Response: Ensure user that the user nameand the password for the logon account is valid.

DBI1965N The node node-number was notfound in the node list.

Explanation: The specified node was not foundin the node list.

User Response: Verify that the node exists by


displaying the list of nodes using the DB2NLISTcommand.

DBI1966N The node cannot be deleted fromthe registry.

Explanation: An error occurred when removingthe specified node from the instance profileregistry.


DBI1967N The DB2 service cannot bede-registered.

Explanation: An error occurred whende-registering a DB2 service.

User Response: Ensure that you have sufficientauthority to delete an NT service.

DBI1968N An error occurred when changingthe node configuration in theprofile registry.

Explanation: An error occurred when changingthe node configuration in the profile registry.


DBI1969N An error occurred when creating anew file in the instance directory.

Explanation: An internal error occurred whencreating a new file in the instance directory.

User Response: Ensure that you have writeaccess to the instance directory.

DBI1970N An error occurred when readingfrom or writing to a file in theinstance directory.

Explanation: An internal error occurred whenreading from or writing to a file in the instancedirectory.


DBI1971N The instance profile cannot beremoved from the registry.

Explanation: An error occurred when removingthe instance profile from the registry.


DBI1972N The instance directory cannot beremoved.

Explanation: An error occurred when removingthe required files or directories belonging to thespecified instance.

User Response: Ensure that you have writeaccess to the location where the instancedirectory is located.

DBI1973N An attempt to configure the DB2service to start automaticallyfailed.

Explanation: An error occurred when settingthe DB2 service to start automatically.

User Response: Reboot the machine and try thecommand again. If the problem persists, contactyour IBM service representative.

DBI1974N The profile variableDB2ADMINSERVER cannot beset in the profile registry.

Explanation: An error occurred when settingthe profile variable DB2ADMINSERVER in theprofile registry.


DBI1975N The environment variableDB2ADMINSERVER cannot beremoved from the profile registry.

Explanation: An error occurred when removingthe environment variable DB2ADMINSERVER inthe profile registry.



DBI1980W Unable to create user ID userID inUPM.

Explanation: The user ID that you providedduring product installation could not be createdin User Profile Management (UPM). This user IDis required to start the DB2 AdministrationServer.

User Response: Manually create a user ID andpassword using UPM and then manually startthe DB2 Administration Server. You may need toset the DB2 Administration Server to use thisuser ID and password combination using the“db2admin” command.


Chapter 8. DBT Messages

DBT1000I The tool completed successfully.

Explanation: The tool’s processing completedwithout any errors.

User Response: No further action is required.

DBT1001N The syntax of the DB2INIDB toolis incorrect.

Explanation: The DB2INIDB tool has thefollowing syntax:

db2inidb <database_alias> AS < SNAPSHOT | STANDBY | MIRROR >[ RELOCATE USING config_file ]

User Response: Resubmit the command usingthe correct syntax.

DBT1002N Database name database-name isinvalid.

Explanation: The database name specified inthe command is not valid. The database namemust contain 1 to 8 characters and all of thecharacters must be from the database managerbase character set.

User Response: Resubmit the command using avalid database name.

DBT1003N Unable to find programprogram-name.

Explanation: An attempt to execute thespecified program failed because it could not befound.

User Response: Ensure that the specifiedprogram exists and verify that the program’spath exists in the PATH environment variable.Correct the problem and resubmit the command.

DBT1004N Unable to execute programprogram-name.

Explanation: An error occurred whileattempting to execute the specified program.

User Response: Ensure that the specifiedprogram exists and that it contains theappropriate file permissions. Correct the problemand resubmit the command.

DBT1005N The file file-name1 could not becopied to file-name2.

Explanation: An error occurred whenattempting to duplicate the specified file. Thecommand could not be processed successfully.

User Response: Ensure that the specified sourcefile exists and that it contains the appropriate filepermissions, and ensure that the specified targetfile does not already exist. Correct the problemand resubmit the command.

DBT1006N The file/device file-device-namecould not be opened.

Explanation: An error occurred whileattempting to open the specified file/device.

User Response: Ensure that the file/deviceexists and that its permissions are correct.Correct the problem and resubmit the command.

DBT1007N An error occurred whileattempting to perform operationoperation-name on file/devicefile-device-name.

Explanation: An attempt to perform thespecified operation on the given file/device wasunsuccessful.


v Ensure that there is sufficient disk space.

v Ensure that the file permissions are correct.


Correct the problem and resubmit the command.If the problem persists, contact your technicalservice representative.

DBT1008N Database database-name is not asplit mirror image.

Explanation: An attempt was made to use theDB2INIDB tool on a database that is not a splitmirror image.

A split mirror image is a mirrored copy of adatabase that is taken while I/O writes aresuspended. I/O writes can be suspended usingthe following command while being connected tothe database:

SET WRITE SUSPEND FOR DATABASE

Once the split mirror image has been taken, I/Owrites on the primary database can be resumedwith the following command:

SET WRITE RESUME FOR DATABASE

Before the split mirror image can be used, theDB2INIDB tool must be run in order to removeits suspended state and initialize it by eitherperforming crash recovery or placing it inrollforward pending state.

User Response: Resubmit the command using asplit mirror image database.

DBT1009N Database database-name is not arecoverable database.

Explanation: An attempt was made to use theSTANDBY or MIRROR option of the DB2INIDBtool with a non-recoverable split mirror imagedatabase. The STANDBY and MIRROR optionsrequire the split mirror image to be recoverable.






The purpose of the STANDBY and MIRRORoptions are to place the split mirror image inrollforward pending state to permit logs from theprimary database to be applied. The primarydatabase must retain the log records for them tobe available to the split mirror image database.

User Response: Resubmit the command using asplit mirror image of a recoverable database. Adatabase can be made recoverable by turning onthe LOGRETAIN database configuration variable.

DBT1010N The split mirror image databasedatabase-name has been previouslyinitialized as a snapshot.

Explanation: An attempt was made to use theSTANDBY or MIRROR option of the DB2INIDBtool on a split mirror image that was previouslyinitialized with the SNAPSHOT option. TheSTANDBY and MIRROR options can no longerbe used to rollforward the log files from theprimary database because the SNAPSHOT optioncaused this split mirror image to start a new logchain.







User Response: Resubmit the command with anew split mirror image database.

DBT1011N Unable to restart databasedatabase-name with the WRITERESUME option. SQLCODE =sqlcode.

Explanation: An attempt to restart the specifieddatabase with the WRITE RESUME option failed.

User Response: Verify the specified SQLCODE,correct the problem and resubmit the command.

DBT1012N Unable to perform operationoperation-name on the databasedirectory.

Explanation: An attempt to perform thespecified operation on the database directory wasunsuccessful.

Possible reasons include:

v The database manager could not process therequest due to an insufficient amount ofmemory in the system.

v No database entries were found in the systemdatabase directory.

v The database does not exist in the systemdatabase directory.


v Ensure that there are sufficient systemresources available.

v Ensure that the database is cataloged correctly.

Correct the problem and resubmit the command.

DBT1013N The database database-name couldnot be found.

Explanation: The specified database is not anexisting database or the database could not befound in the local or system 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.

DBT1014N The instance name could not bedetermined.

Explanation: An attempt to determine thecurrent instance name was unsuccessful.

User Response: Ensure that the DB2INSTANCEenvironment variable is set to the currentinstance name. Correct the problem and resubmitthe command.

DBT1015N Unable to allocate memory.

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


v Ensure that your system has sufficient real andvirtual memory.

v Remove background processes.

DBT1016N Table space files file-name1 andfile-name2 are different sizes.

Explanation: The two specified table space fileshave a different size even though they aresupposed to be identical.

User Response: Contact your technical servicerepresentative with the following information:


v Contents of the table space catalog table

v Table space files

Chapter 8. DBT Messages 275

DBT1017N The syntax of theDB2RELOCATEDB tool isincorrect.

Explanation: The DB2RELOCATEDB tool hasthe following syntax:

db2relocatedb -f <config_file>

<configFile>: Name of file containingconfiguration information.

File format is:

DB_NAME=oldName,newNameDB_PATH=oldPath,newPathINSTANCE=oldInst,newInstNODENUM=nodeNumberLOG_DIR=oldDirPath,newDirPathCONT_PATH=oldContPath1,newContPath1CONT_PATH=oldContPath2,newContPath2...

Notes:

v Database name, database path, and instancename are all required fields. If one of thesefields is not changing then it is not necessaryto list the old and new value for it, just givethe old/current one.

v Blank lines or lines beginning with a commentcharacter (#) will be ignored.

User Response: Resubmit the command usingthe correct syntax.

DBT1018N field-name is a required field in theconfiguration file.

Explanation: The specified field is a requiredfield and does not exist in the configuration file.

User Response: Add the specified fieldinformation to the configuration file and thenresubmit the command.

DBT1019N Invalid database path specified inthe configuration file.

Explanation: The specified database path in theconfiguration file is invalid.

On Windows, the database path must include thedrive letter followed by a colon character. On

other platforms, the database path must beabsolute and end with a path separator.

User Response: Correct the erroneous databasepath and resubmit the command.

DBT1020N The configuration file contains aninvalid entry at line line-number.Reason code = reason-code.

Explanation: You cannot relocate with theDB2RELOCATEDB tool until the followingcondition indicated by the reason code isresolved:

1 The specified line is longer than themaximum number of characters.

2 A field was specified but no valuesfollow it.

3 A field has been specified more thanonce.

4 Either the old or new database namecontains too many characters.

5 Either the old or new database pathname contains too many characters.

6 Either the old or new instance namecontains too many characters.

7 An invalid node number has beenspecified in the NODENUM entry.

8 Either the old or new log directory pathcontains too many characters.

9 Either the old or new container namecontains too many characters.

10 A duplicate container name in aCONT_PATH entry has been found.

11 The specified line is invalid.

User Response: The action corresponding to thereason code is:

1 Ensure that the specified line contains atmost 1000 characters.

2 Ensure that the necessary values arespecified for the field in question.


3 Ensure that the field in question is onlyspecified once.

4 Ensure that the old and new databasenames contain no more than 8characters.

5 Ensure that the old and new databasepath names contain no more than 215characters.

6 Ensure that the old and new instancenames contain no more than 8characters.

7 Ensure that the node number containsno more than 4 digits.

8 Ensure that the old and new logdirectory paths contain no more than242 characters.

9 Ensure that the old and new containernames contain no more than 256characters.

10 Ensure that each container name is onlyspecified once in a CONT_PATH entry.

11 Verify the validity of the line inquestion.


DBT1021N The total size of all containernames is too large.

Explanation: The total space required to storethe list of containers exceeds the space allottedfor a given 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.


DBT1022N The DB2RELOCATEDB tool mustbe run under instanceinstance-name.

Explanation: An attempt has been made to runthe DB2RELOCATEDB tool from an incorrectinstance. If the instance is changing then the toolshould be run from the new instance.

User Response: Resubmit the command usingthe correct instance.

DBT1023N The database release release-numberis invalid.

Explanation: The tool that is being used is froma different release than the database’s currentrelease. The command cannot be processed.

User Response: Ensure that the correct versionof the tool is being used. Correct the problemand resubmit the command.

DBT1024N Change in database name hasresulted in duplicate names in thelocal database directory.

Explanation: An attempt to rename a databasefailed because an entry in the local databasedirectory already existed with the same name.

User Response: Either change the databasename to one that doesn’t already exist oruncatalog the database if it no longer exists.Correct the problem and resubmit the command.

DBT1025N Neither old nor new databasename were found in the databasedirectory.

Explanation: An attempt to determine thedatabase token necessary to find the databasepath failed because neither the old nor newdatabase names could be found in the databasedirectory.

User Response: Ensure the database with theold database name exists and that it is catalogedproperly. Correct the problem and resubmit thecommand.

Chapter 8. DBT Messages 277

DBT1026N Replacement of the new databasepath database-path in containername container-name will exceedlength restrictions.

Explanation: An attempt to rename thedatabase path failed because it exceeds containername length restrictions when appended to thefront of the specified container name.

User Response: Rename the database pathand/or container name such that they do notexceed length restrictions when appendedtogether. Correct the problem and resubmit thecommand.

DBT1027N Replacement of the new databasepath database-path in log directorypath log-path will exceed lengthrestrictions.

Explanation: An attempt to rename thedatabase path failed because it exceeds logdirectory path length restrictions when appendedto the front of the specified log directory path.

User Response: Rename the database pathand/or log directory path such that they do notexceed length restrictions when appendedtogether. Correct the problem and resubmit thecommand.

DBT1028N Unable to copy table space files.

Explanation: An attempt to duplicate the tablespace file SQLSPCS.1 failed.

User Response: Ensure there is sufficient diskspace for the duplicate table space file. Correctthe problem and resubmit the command.

DBT1029N Unable to copy buffer pool files.

Explanation: An attempt to duplicate the bufferpool file SQLBP.1 failed.

User Response: Ensure there is sufficient diskspace for the duplicate buffer pool file. Correctthe problem and resubmit the command.

DBT1030N Unable to copy local databasedirectory files.

Explanation: An attempt to duplicate the localdatabase directory file failed.

User Response: Ensure there is sufficient diskspace for the necessary duplicate local databasedirectory file. Correct the problem and resubmitthe command.

DBT1031N An error occurred while updatingthe log file header log-file-header.

Explanation: An attempt to update the log fileheader SQLOGCTL.LFH failed.

User Response: Ensure the log file header existsin the database directory and that there issufficient disk space. Correct the problem andresubmit the command.

DBT1032N The instance is not currentlyactive.

Explanation: The tool requires the instance tobe active before it can perform any processing.

User Response: Issue a db2start before issuingthe command.

DBT1033N Unable to attach to instanceinstance-name. SQLCODE = sqlcode.

Explanation: An attempt to attach to thespecified instance failed.

User Response: Verify the specified SQLCODE,correct the problem and resubmit the command.


Chapter 9. DB2 Messages

This section contains the messages generated by the command line processor.The command line processor returns DB2 and SQL messages. The messagesare listed in numeric sequence.

DB20000I The command command completedsuccessfully.

Explanation: No errors were encounteredduring the execution of this command.


DB21001E The option option-letter specifiedafter the ’db2’ command or in theDB2OPTIONS variable isincorrect.

Explanation: The option specified is notsupported. The supported options are:

Option Description------ --------------------------------a Display SQLCA-c Auto-commit-e Display SQLCODE/SQLSTATE-f Read from input file-l Log commands in history file-n Remove new line character-o Display output-p Display interactive prompt-r Save output report to file-s Stop execution on cmd error-t Set stmt termination character-v Echo current command-w Display FETCH/SELECT warnings-x Suppress printing of column

headings-z Save all output to file

The command cannot be processed.

User Response: Resubmit the command with avalid option.

DB21002E The parameter for optionoption-letter specified after the’db2’ command or in theDB2OPTIONS variable is missingor incorrect.

Explanation: The following lists the optionswith parameters:

Option Description------ ---------------------------ec Display SQLCODE-es Display SQLSTATE-f<filename> Read from input

file<filename>

-l<filename> Log commands inhistory file<filename>

-r<filename> Save output reportto file <filename>

-td<x> Set terminationchar to ’x’

-z<filename> Save all output tofile <filename>

User Response: Resubmit the command withthe valid option and parameter.

DB21003E The value value inenvironment-variable is not valid.

Explanation: The value for DB2BQTRY must bebetween 0 and 4294967295. The value forDB2BQTIME, DB2RQTIME or DB2IQTIME mustbe between 1 and 4294967295.

User Response: Set the environment variablewith the correct value and resubmit thecommand.


DB21004E You cannot specify both an inputfile and a command wheninvoking the Command LineProcessor.

Explanation: You cannot specify both the -foption and a command line command wheninvoking the command line processor.

User Response: Correct the error and issue thecommand again.

DB21005E An error occurred while accessingthe file filename.

Explanation: The following could have causedthe error:

v file permissions do not allow file access

v the file does not exist

User Response: Correct the error and try again.

DB21006E The input command is too long.The maximum length is length.

Explanation: The input command cannot exceedthe length specified.

User Response: Correct the error and resubmitthe command.

DB21007E End of file reached while readingthe command.

Explanation: The last command was notexecuted because end of file was reached.Terminate the last command with a ’;’ (or yourdefined termination character) if the -t optionwas used. Remove the ’\’ from the last line inthe command if the +t option was used.


DB21008E Commands can only be enteredfrom the command line processorinteractive mode or file inputmode.

Explanation: The user attempted to enter acommand line processor command from the DOSprompt.

User Response: Use command line processorinteractive mode or file input mode.

DB21010I Help given forhelp-command-phrase.

Explanation: This message only appears in thehistory file specified with the -l option.


DB21011I In a partitioned database serverenvironment, only the tablespaces on the current node arelisted.

Explanation: Only the table spaces on thecurrent node are visible to the LISTTABLESPACES command.

User Response: To list the table spaces onanother node, you must issue the LISTTABLESPACES command on that node.

DB21015E The Command Line Processorbackend process request queue orinput queue was not createdwithin the timeout period.

Explanation: Either the values for theDB2BQTRY and DB2BQTIME environmentvariables need to be increased or the commandline processor back-end program ″db2bp″ cannotbe started. The ″db2bp″ program must reside inthe correct database manager install path andusers must have execute permission on the file.



DB21016E The Command Line Processorencountered a system error whilesending the command to thebackend process.

Explanation: One of the following could havehappened:

v The backend process was abnormallyterminated.

v A system error occurred when reading from orwriting to the back-end process queues.

v A system error occurred when reading fromthe front-end process output queue.

User Response: Resubmit the command. If theerror occurs again, get help from your systemadministrator.

DB21017E The Command Line Processorencountered a system error withthe front-end process outputqueue. Reason code = reason-code.

Explanation: A system error occurred whilecreating or reading from the front-end processoutput queue.

If the reason code is -2499, the command lineprocessor output queue conflicts with an existingqueue.

User Response: Resubmit the command. If theerror occurs again, record the message numberand reason code, and get help from your systemadministrator.

DB21018E A system error occurred. Thecommand line processor could notcontinue processing.

Explanation: One of the following caused thesystem error:

v Too much data is being output to the screen.Pipe the output to a file that you can viewonce processing is complete.

v Command line processor did not successfullyinstall its interrupt signal handler.

v Command line processor did not successfullyopen the back-end process queues.

v Command line processor did not successfullystart up the back-end process.

v The back-end process was abnormallyterminated.

v The front-end process did not successfullyallocate or free memory.

v The front-end and/or back-end process didnot successfully dynamically load a library.

v Command line processor received one of thefollowing program termination signals:

– SIGILL

– SIGTRAP

– SIGEMT

– SIGBUS

– SIGSEGV

– SIGSYS

User Response: Retry the command. If theproblem persists, record the DB2 messagenumber. If the trace was active, save the traceinformation and contact your technical supportwith the following information:


v DB2 message number

v SQLCA if possible

v Trace file if possible

DB21019E An error occurred while accessingthe directory directory.

Explanation: The following could have causedthe error:

v directory permissions do not allow access

v the directory does not exist


DB21020E Unable to create the defaultmessage file file.

Explanation: To properly process this command,CLP needs a file where the messages issuedduring processing are saved before they aredisplayed on the console. It attempted to createsuch a file in a directory normally used for thatpurpose (such as /tmp on UNIX platforms or

Chapter 9. DB2 Messages 281

...\TMP on OS/2), but the attempt failed becausethe directory does not exist.


DB21021E No Admin Server instance isdefined. The command failed.

Explanation: You issued a command that needsto use an Administration Server instance, but nosuch instance is defined.

User Response: Define an AdministrationServer instance and resubmit the command.

DB21022E Unable to switch toAdministration Server instanceinstance-name.

Explanation: You issued a command that needsto use an Administration Server instance.Command line processor tried to switch toAdministration Server instance instance-name butfailed. The possible reasons may be:

v The Administration Server instance is not setcorrectly.

v Command line processor was already attachedto a DB2 instance.

v Command line processor was connected to adatabase.

User Response: Check that a validAdministration Server instance is set up beforeusing this command. Also, you may need toissue the DETACH, or CONNECT RESET, orTERMINATE command before trying yourrequest again.

DB21023E The command is not valid whenexecuted from AdministrationServer.

Explanation: You issued one of the followingcommands: GET DBM CONFIGURATION,RESET DBM CONFIGURATION, or UPDATEDBM CONFIGURATION, but these commandscannot be executed from Administration Server.

User Response: Issue one of the followingcommands that are valid on Administration

Server: GET ADMIN CONFIGURATION, RESETADMIN CONFIGURATION, or UPDATEADMIN CONFIGURATION.

DB21024I This command is asynchronousand may not be effectiveimmediately.

Explanation: This message is displayed afterexecuting either a FORCE command with theASYNC clause or a REORG TABLE commandwith the INPLACE clause.


DB21025I 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 detailsusing 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 those


cases 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

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

DB21027E Isolation level may not bechanged while connected to adatabase.

Explanation: The user attempted to change theisolation level while connected to a database. Thecommand is ignored.

User Response: If a change in isolation level isnecessary, disconnect from the current database,then set the isolation level and re-connect to thedatabase.

DB21028E The cursor cursor-name has notbeen declared.

Explanation: The specified cursor needs to bedeclared before issuing an OPEN, FETCH, orCLOSE SQL statement.

User Response: Declare the cursor and resubmitthe command.

DB21029E The cursor cursor-name has alreadybeen declared and opened.

Explanation: The user attempted to declare acursor that is open.

User Response: Close the cursor and resubmitthe open command.

DB21030E The cursor cursor-name has notbeen opened.

Explanation: The specified cursor needs to beopened.

User Response: Open the cursor and resubmitthe command.


DB21031E The SQL statement using thecursor cursor-name (internal-cursor)returned:

Explanation: This message shows the internalcursor name for the user defined cursor. SomeSQL error messages may show the internalcursor name. This message is displayed beforethe SQL message.

User Response: Correct the SQL error andresubmit the command.

DB21032E You have already declared themaximum number of cursors.

Explanation: Command line processor supports100 cursors declared with the WITH HOLDattribute and 100 cursors declared without theWITH HOLD attribute.

User Response: Re-declare one of the existingcursors and resubmit the command.

DB21033E The command is not valid fordatabases that reside on DRDAhosts.

Explanation: The following commands are notsupported for databases that reside on DRDAhost servers:

v LIST TABLES

v LIST PACKAGES

v REORGCHK

User Response: Do not issue the command forthis database.

DB21034E The command was processed asan SQL statement because it wasnot a valid Command LineProcessor command. During SQLprocessing it returned:

Explanation: This message is displayed beforethe SQL error message. The error may be causedby a syntax error in a non-SQL command.


DB21035E The maximum number of items inthe list-name list has beenexceeded. The maximum numberis number.

Explanation: The number of items in the listcannot exceed the maximum specified. This errormay be caused by an invalid range specification.


DB21036E The command command failed.

User Response: Retry the command with thetrace active. If the problem persists, save thetrace information and contact your technicalsupport with the following information:


v DB2 message number

v Trace file

DB21037W No data sources found.

User Response: There were no ODBC datasources found of the type (USER or SYSTEM)that you specified. Retry the command byspecifying the other type (SYSTEM or USER).

DB21040E number is not a valid in-doubttransaction number.

Explanation: number is not one of the listedin-doubt transaction numbers.

User Response: Select one of the listedtransaction numbers and resubmit the command.

DB21041W number indoubt transaction(s) notshown.

Explanation: Command line processor couldnot display all the in-doubt transactions. Thenumber of transactions not displayed is number.

User Response: Finish processing the currentlist of indoubt transactions in order to reduce thetotal number of indoubt transactions in thesystem. Next, reissue the list indoubt transactionscommand.


DB21042E You must specify a transactionnumber.

Explanation: A transaction number must bespecified with the commit (c), rollback (r), orforget (f) in-doubt transaction subcommands.

User Response: Reissue the command with theappropriate transaction number.

DB21043E subcommand is not a valid request.

Explanation: The in-doubt transactionsubcommand specified is not valid. Validsubcommands are:

Subcommand Description---------- ---------------------------c <number> Heuristically commit

the in-doubt transaction<number>.

r <number> Heuristically roll-back the in-doubttransaction <number>.

f <number> Heuristically forgetthe in-doubt transaction<number>.

l <number> List all in-doubttransactions or the in-doubt transaction<number>.

q Exit LIST INDOUBTTRANSACTION prompting.

NOTE: The number command is not available inDB2 Extended Enterprise Edition.


DB21044E Cannot COMMIT transactionnumber number.

Explanation: The transaction must be in aprepared state (i) when you issue the commit (c)subcommand.

User Response: Issue another command.

DB21045E Cannot ROLLBACK transactionnumber number.

Explanation: The transaction must be in aprepared (i) or idle (e) state. when you issue therollback (r) subcommand.


DB21046E Cannot FORGET transactionnumber number.

Explanation: The transaction must be in aheuristically committed (c) or heuristicallyrolled-back (r) state when you issue the forget (f)command.


DB21050E state is not a valid SQLSTATE.

Explanation: The sqlstate specified is not validor could not be found. Valid states are numericaland two or five digits in length.

User Response: Resubmit the command using adifferent state.

DB21051E The command is not supportedfor this environment.

Explanation: The command requested iscurrently not supported by the command lineprocessor in the environment being used.

User Response: Resubmit the command on adifferent platform or within a differentenvironment.

DB21052I command has been submitted forexecution.

Explanation: The command line processor isattempting to execute the indicated command. Itwill be unable to determine whether thecommand has completed successfully.

User Response: If the command appearsunsuccessful, submit it from outside thecommand line processor.


DB21053W Automatic escalation will occurwhen you connect to a databasethat does not supportisolation-level.

Explanation: Isolation levels are databasedependent. Some, like NC, are only supported byspecific databases. If you select an isolation levelthat is not supported by the database you areconnecting to, it will automatically escalate to asupported level.

User Response: Connect to a database thatsupports the isolation level you have selected, orselect a different isolation level.

DB21054E The command line processorencountered a system error withthe command command. Reasoncode = reason-code.

Explanation: The command line processor wasunable to get enough memory to process yourcommand. A system error occurred whileprocessing it.

Reasoncode Description Syntax---- -------------- ------------------1 Data file LOAD FROM

file/pipe/dev...2 Lob data LOBS FROM

lob-path...3 Directory USING directory...4 Source FROM dir/dev...5 Target TO dir/dev...6 Tablespace TABLESPACE

tblspace-name...7 Tblspace-def MANAGED BY...8 Container data USING (PATH...,

PATH...)orUSING ({FILE|DEVICE}...,{FILE|DEVICE}...)

9 Log path log-directory ...,log-directory ...

10 Node list node-number ...,node-number ...


DB21055W Command not valid for type 2connections.

Explanation: The information returned by theGET CONNECTION STATE command does notapply to type 2 connections.

User Response: Issue QUERY CLIENT to verifyCONNECT = 1.

DB21056W Directory changes may not beeffective until the directory cacheis refreshed.

Explanation: If directory caching (DBM CFGdir_cache) is enabled, database, node, and DCSdirectory files are cached in memory. Directorychanges may not become effective until thedirectory cache is refreshed. Refer to thedir_cache configuration parameter in the ADMINguide for a description on directory caching.

User Response: To refresh CLP’s directorycache, issue a db2 TERMINATE. To refresh thedirectory information for another application,stop and restart that application. To refresh thedirectory information for the database, stop(db2stop) and restart (db2start) the database.

DB21057E Invalid tape device specified.

Explanation: The tape device passed to theoperating system was not accepted. On WindowsNT it must be of the form ″\\.\TAPEx″ where xrepresents the drive number (0 is the first).

User Response: Reissue the commandspecifying a valid tape device.

DB21058E Invalid tape position specified.

Explanation: The tape mark position specified isnot valid. On Windows NT the first tape positionto which a backup is record is 1. Subsequentbackup images begin at tape mark 2 and so on.

User Response: Reissue the commandspecifying a valid tape position.


DB21059E Invalid tape blocksize specified.

Explanation: The tape mark blocksize specifiedis not in the range supported by the tape device.In addition, for backup/restore to work it mustalso be a factor of or multiple of 4096.

User Response: Reissue the commandspecifying a valid tape size.

DB21060E General tape failure.

Explanation: An unexpected return code wasreturned from the tape operation.

User Response: Resubmit the command. If theerror occurs again, get help from your systemadministrator.

DB21061E Command line environment notinitialized.

Explanation: You have tried to invoke thecommand line processor from a commandwindow that was not started by db2cmd.exe.

User Response: Issue DB2CMD to start acommand window that has the command lineprocessor environment initialized.

DB21070W One or more of the configurationparameters were set toAUTOMATIC in a case where theparameter 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.

DB21071W Configuration parameter valueswere changed on all nodes,however not all nodes were ableto change the values dynamically.

User Response: If parameter changes weresubmitted in a group, issue the update commandindividually for more detailed information.

At the next restart of the unsuccessful nodes, thenew values will take effect.

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.

To identify the nodes that failed in their dynamicapplication, attach to the instance on each nodeand issue the following command:

DB2 GET DBM CFG SHOW DETAIL

DB21080E No previous RESTOREDATABASE command withREDIRECT option was issued forthis database alias, or theinformation about that commandis lost.

Explanation: You have tried to run theRESTORE DATABASE command with theCONTINUE or ABORT option. However, eitheryou didn’t previously issue a RESTOREDATABASE command with the REDIRECToption, or you did issue such a command but fora different database alias than the one specifiedon the failing command. Another possible causefor this message could be that the informationabout a correctly issued previous RESTOREDATABASE ... REDIRECT command was lost.This can happen if the CLP back-end processterminates abnormally, or if you issue theTERMINATE command.

User Response: Restart the whole redirectedrestore process by issuing the RESTOREDATABASE ... REDIRECT command and SETTABLESPACE CONTAINERS commands again.Then issue the RESTORE DATABASE ...CONTINUE command.


DB21081E No sections were found in thedb2cli.ini file.

Explanation: You have tried to list CLIparameters in the db2cli.ini file by using the GETCLI CONFIGURATION command, but the file isempty. There are no sections in that file.

User Response: To update the db2cli.ini file, usethe UPDATE CLI CONFIGURATION command.

DB21082E You don’t have enough authorityto run the UPDATE CLICONFIGURATION command.

Explanation: You need to have SYSADMauthority to run this command.

User Response: Obtain the necessary authorityfrom your database administrator, then issue thecommand again.

DB21083E Section section not found.

Explanation: Section <section> was not foundin the db2cli.ini file.

User Response: Specify an existing section andissue the command again.

DB21084E NEW and CONFIRM passwordsnot the same.

Explanation: You were using the ATTACH orCONNECT command and specified that youwanted to change your password. The newpassword needs to be specified twice, by usingthe NEW and CONFIRM clauses, or byresponding to the prompts. The two passwordsyou specified as your new password weredifferent.

User Response: Specify the same passwordtwice.

DB21085I Instance instance-name uses 32 or64 bits and DB2 code releasever-rel-mod with level identifierlevel-id. Informational tokens arebuild-id1, build-id2, build-id3 andFixPak FixPak-number.

Explanation: This message is the output of thedb2level command and provides detailedinformation about the code level of a given DB2instance. The information may be requested byDB2 service personnel to aid in resolvingproblems.

User Response: Record all displayedinformation to provide to DB2 service personnel.

The db2level executable should not be copiedfrom one machine to another. Only DB2installation and service maintenance programsshould manipulate this file.

The db2level executable may not display allinformation about private test fixes that thecustomer has received from DB2 servicepersonnel and installed on top of an officiallysupported service level.

DB21086I The incremental RESTOREoperation of this backup imagecompleted successfully, but thereare additional backup images thatmust be restored to complete theentire incremental RESTOREoperation.

Explanation: To complete an incrementalRESTORE operation, every incremental backupimage in its restore chain must be restored. Thecurrent operation succeeded, but there areadditional backup images that must be restoredbefore the overall RESTORE operation iscomplete.

User Response: Restore the next backup image.

DB21100E Stored procedure procedure-nameexists in multiple schemas.

Explanation: The specified procedure name wasfound in more than one schema.


User Response: Re-issue the CALL commandwith a fully qualified procedure name(schema.procedure-name).

DB21101E Too few parameters werespecified for stored procedureprocedure-name (expected quantity).

Explanation: The definition of this storedprocedure contains more parameters than thosespecified in the CALL command.

User Response: Verify the number ofparameters in the stored procedure and re-issuethe command.

DB21102E Too many parameters werespecified for stored procedureprocedure-name (expected quantity).

Explanation: The definition of this storedprocedure contains fewer parameters than thosespecified in the CALL command.

User Response: Verify the number ofparameters in the stored procedure.

DB21103E The data type of parameterparameter-number is not supportedby the CALL command in CLP.

Explanation: Currently in CLP, one cannot callstored procedures with a parameter whose datatype is that of parameter parameter-number.

User Response: Do not call this storedprocedure from CLP.

DB21104E Parameter parameter-number forstored procedure procedure-nameshould be an INPUT parameter.

Explanation: The parameter parameter-number isdefined as an INPUT or INPUT/OUTPUTparameter. However a ″?″ was specified for thisparameter.

User Response: Replace the ″?″ in parameterparameter-number by the input value of thisparameter and re-issue the CALL command.

DB21105E Parameter parameter-number forstored procedure procedure-nameshould be an OUTPUT parameter.

Explanation: The parameter parameter-number isdefined as an OUTPUT parameter. However ainput value was specified for this parameter.

User Response: Replace the input value inparameter parameter-number by a ″?″ and re-issuethe CALL command.

DB21106E Stored procedure procedure-name isundefined.

Explanation: The stored procedure has not beendefined or it has not been cataloged in thesystem catalogs.

User Response: Verify that the stored procedureexists in the system catalogs. Try dropping andre-creating the stored procedure. Then re-issuethe CALL command.

DB21500I The DB2MSCS commandcompleted successfully.

Explanation: The user request was successfullyprocessed.


DB21501E Invalid option option-name wasspecified for the command.

Explanation: An invalid argument was enteredfor the DB2MSCS command. Valid arguments forthe command are:

v -f:InputFileName Specifies the DB2MSCS.CFGinput file to be used by the MSCS utility. Ifthis parameter is not specified, the DB2MSCSutility reads the DB2MSCS.CFG file that is inthe current directory.

v -d:TraceFileName Turns on debug tracing andspecifies the name of the trace output file.

v -u:InstanceName Undo the DB2MSCSoperation for the instance.

User Response: For more information aboutthis command, please refer to the″Administration Guide″. Enter the command


again as follow: DB2MSCS -f InputFileName

DB21502E Cannot open the configurationfile file-name.

Explanation: A configuration file could not beopened. Depending on the filename in themessage text, this error can be explained asfollow:

v If the filename in the message text was thename of the input file specified for theDB2MSCS command, then input file can notbe found.

v If the filename was ″db2systm″, then thedatabase manager configuration file for targetinstance is missing.

v If the filename was ″db2mscs.bak″, then thebackup configuration file could not be createdin the instance directory.

v If the filename was ″db2mscs.bak″ and anundo operation was performed, then thebackup configuration file from the instancedirectory could not be opened whenperforming the undo operation.

User Response: Depending on the file that wasin error, the problem may be corrected as follow:

v If the filename in the message text was thename of the input file specified for theDB2MSCS command, then ensure that the fileexists in the current directory, or that a fullyqualified filename is specified for thecommand.

v If the database manager configuration file fortarget instance is missing, then drop andrecreate the instance.

v If the backup configuration file could not becreated in the instance directory, then ensurethat the instance profile directory exists andthat the current logon account has write accessto the directory.

v If the backup configuration file from theinstance directory could not be opened whenperforming the undo operation, then ensurethat the MSCS disk that contains the instanceprofile directory is online on the currentmachine and retry the operation.

DB21503E Not enough memory is availableto process this command.

Explanation: There was not enough memory tocontinue processing the command.

User Response: Ensure that the system hassufficient real and vitual memory. Close allapplications that are not in use to free upadditional memory for the system.

DB21504E The value parameter-value specifiedfor parameter parameter-nameexceeded the maximum length forthat parameter. The maximumlength of the parameter is lengthbytes.

Explanation: The value parameter-value specifiedfor the keyword parameter-name exceeded themaximum allowable limit for that parameter.

User Response: Specify a value that isconformed with the following maximum lengthrestrictions:

v Maximum length for a group or resource nameis 64

v Maximum length for an IP Address or subnetmask is 15

v Maximum length for a DB2 instance name is 8

v Maximum length for a network name, clustername or computer name is 64

v Maximum length for a username name orpassword is 256

DB21505E Parameter parameter-name1 must bespecified before parameterparameter-name2 in the DB2MSCSconfiguration file file-name.

Explanation: The sequence of parametersspecified in the DB2MSCS configuration file isnot valid. The group name must be specifiedbefore any other resource parameter can bespecified. For each resource, the resource nameparameter must be specified before any resourceparameter can be specified.

User Response: Modify the DB2MSCS


configuration file so that the sequence ofparameters is correct.

DB21506E The cluster cluster-name cannot beaccessed. Ensure that the clustername is correct and the clusterservice on the current currentmachine has been started..

Explanation: The DB2MSCS utility could notopen the cluster because either the cluster namewas incorrect or the cluster service on the currentmachine has not been started.

User Response: If the cluster service has notbeen started on the current machine, then startthe cluster service by running the command ″netstart clussvc″ or by starting the ″Cluster″ servicefrom the Services dialog. If the cluster name wasspecified incorrectly in the DB2MSCSconfiguration file, then modify the cluster nameand resubmit the command.

DB21507E The instance name instance-name isnot valid.

Explanation: The instance name specified in theDB2MSCS configuration file is not valid, or theDB2INSTANCE environment variable was not setto a valid instance name.

User Response: If the instance name wasspecified in the DB2MSCS configuration file, thenverify that the instance name is valid andresubmit the command. If the instance name wasnot specified in the configuration file, thenensure the DB2INSTANCE environment variableis set to the name of a valid DB2 instance.

DB21509E The keyword keyword specified inconfiguration file file-name is onlyvalid for the partitioned databaseinstance.

Explanation: The keyword specified is onlyvalid if the target instance is a partitioneddatabase instance. For example, the DB2_NODEkeyword should only be specified for thepartitioned database instance.

User Response: Comment out the invalid

keyword in the configuration file and resubmitthe command.

DB21510E Internet address internet-addressspecified in configuration filefile-name is not valid.

Explanation: The value specified for either theIP address or the subnet mask does not conformwith the internet address format. A valid internetaddress format has the form: “nnn.nnn.nnn.nnn”,where nnn is a number from 0 to 255.

User Response: Correct the invalid address inthe configuration file and resubmit thecommand.

DB21511E Node node-number does not exist.

Explanation: The node number specified in theDB2_NODE keyword does not correspond to avalid database partition number.

User Response: Correct the DB2_NODEparameter to specify an existing node number.

DB21512E The keyword keyword is not avalid DB2MSCS keyword.

Explanation: The keyword specified was not avalid DB2MSCS keyword.

User Response: Use a valid DB2MSCSkeyword. For more information about thekeywords, please refer to the ″AdministrationGuide″.

DB21513E The DB2MSCS utility failed tocreate MSCS group group-namebecause of system error: error-msg

User Response: Please refer to the Windowssystem error message for further information.

DB21514E The DB2MSCS utility failed tocomplete because of system error:error-msg

Explanation: The DB2MSCS utility failed tocomplete because of a Windows system error.

User Response: Please refer to the Windows


system error message for further information.

DB21515E The required resource propertyspecified by keywordkeyword-name is missing for theresource resource-name.

Explanation: A resource could not be createdbecause one of its required parameters was notspecified. For example, for IP Address resource,the IP Address and the subnet mask must bespecified. For the Network Name resource, thenetwork name must be specified.

User Response: Ensure that the requiredparameter is specified and resubmit thecommand.

DB21516E DB2MSCS cannot bring resourceresource-name online. Ensure thatthe properties of the resource areset correctly.

Explanation: After a resource is created, theDB2MSCS utility validates the resource byattempting to bring the resource online. Failingto bring a resource online indicates that eitherthe resource property was not specified correctlyor that the cluster network was not functioningproperly.

User Response:

v If a disk resource was in error, then ensurethat the disk subsystem and the disk devicedriver is functioning properly. The EventViewer should be used to examine if any diskdevice driver problem was recorded in theEvent logs.

v If an IP Address resource was in error, thenensure that the IP parameters are correct andthat the network(s) where the IP addressresides on is functioning properly. Also, the IPaddress that is specified for DB2 must NOT beused by any other machine in the network. Ifyou are not sure what parameters to use forthe IP address, consult with your networkadministrator.

v If a Network Name resource was in error, thenensure that the network is functioningproperly, and that the value specified for the

Netname parameter has not been used by anymachine in the network. Note that theNetwork Name parameter is not required. Asa work around, you may want to comment outthe Network Name parameter and proceed.

v If a DB2 resource was in error, then thedb2diag.log should be examined for any DB2errors.

DB21517E MSCS Network network-name isnot active.

Explanation: The network parameter specifiedfor the IP address is not active.

User Response: From the ClusterAdministration view, activate or enable the targetnetwork and resubmit the command.

DB21518E There is no active MSCS network.

Explanation: The network parameter was notspecified for the IP address and there was nonetwork available to be used.

User Response: A valid MSCS network must beconfigured. Please refer to your clusterdocumentation for how to add and configure anMSCS network.

DB21519E DB2MSCS cannot bring theresource resource-name offline.Ensure that the properties of theresource are set correctly.

Explanation: The DB2MSCS could not bring aresource offline. The resource may be in use bythe cluster software.

User Response: Retry the operation. If theproblem persists, run with the trace option andcontact your IBM Service Representative forfurther assistance.

DB21520E The DB2PATH profile variable isnot defined.

Explanation: The DB2PATH registry profilevariable is not defined for the current machine.The DB2PATH must be set to the path whereDB2 is installed.


User Response: Set the DB2PATH to thedirectory where DB2 is installed using the db2setcommand. For example, db2set -gDB2PATH=D:\SQLLIB.

DB21521E DB2MSCS cannot read from filefile-name.

Explanation: The DB2MSCS utility can not readdata from the indicated file.

User Response: Ensure that the file is notlocked and that the current logon user havesufficient authority to read the file.

DB21522E Cannot open machine registry formachine machine-name. Ensure thatthe machine is active and that thecurrent logon account has LocalAdministrator authority.

Explanation: The DB2MSCS could not open theregistry for the remote machine for read andwrite access. By default, only users that belong tothe Local Administrator groups on that machinehave read and write access to the machineregistry. This error is also returned if the remotemachine is not active.

User Response: Ensure that the target machineis active, then logon to a domain account thatbelongs to the Local Administrator group on thetarget machine and resubmit the command.

DB21523E Cannot close machine registry formachine machine-name. Ensure thatthe machine is active and that thecurrent logon account has LocalAdministrator authority.

Explanation: After opening the remote registry,the DB2MSCS utility failed to close the handle tothe remote registry because of an internal error.

User Response: Run with the trace option andcontact your IBM Service Representative forfurther assistance.

DB21524E Failed to create the resourceresource-name. System error:error-msg

Explanation: The command failed to create thetarget resource because of a Windows systemerror.

User Response: Refer to the Windows systemerror message for additional information.

DB21525E Failed to add dependency to theresource resource-name. Systemerror: error-msg

Explanation: The command failed to adddependency for the target resource because of aWindows system error.


DB21526E Failed to move resourceresource-name. System error:error-msg

Explanation: The command failed to add moveresource because of a Windows system error.


DB21527E No disk resource is specified forthe group group-name.

Explanation: At least one disk resource must bespecified for each group.

User Response: Assign one or more diskresource to the group indicated in the errormessage.

DB21528E The value keyword-value specifiedfor the INSTPROF_DISKkeyword does not match any diskin the same group.

Explanation: The INSTPROF_DISK keywordwas used to specify the location where thecontent of instance profile directory will becopied to. The value for the INSTPROF_DISKkeyword did not match one the name of a disk


resource in the same group.

User Response: Set the INSTPROF_DISK to thename of one of the disk resources in the samegroup.

DB21529E The DB2MSCS utility cannotaccess the registry of machinemachine-name. Ensure that themachine is active and that thecurrent logon account has LocalAdministrator authority.

Explanation: The DB2MSCS utility cannotaccess the registry of the target machine.

User Response: Logon to a domain account thatbelongs to the Local Administrator group on thetarget machine and resubmit the command.

DB21530E The DB2MSCS utility cannotaccess the cluster registry for thecluster cluster-name. Ensure thatthe cluster is active and thecurrent logon account has LocalAdministrator authority.

Explanation: To administer a cluster, users musthave either administrative permissions on bothnodes or specific permissions to administer thecluster. By default, the local Administratorsgroup on both nodes has permissions toadminister the cluster.

User Response: Logon to an account that hassufficient access to the Cluster. To give a userpermissions to administer a cluster withoutgiving the user Administrative permissions onboth nodes: Run the Cluster Administration GUIRight-click the cluster name, and then clickProperties Click Security (or Permissions) Specifywhich users and groups that may administer thecluster.

DB21531E Cannot obtain property for MSCSdisk. System error: error-msg

Explanation: The DB2MSCS utility can notobtain the drive letter from the MSCS diskresource. This problem usually occurs when thedisk resource specified by the INSTPROF_DISK

keyword is an IBM Netfinity disk resource,″IPSHA Disk″.

User Response: Do not use theINSTPROF_DISK keywork. Instead, use theINSTPROF_PATH keyword to explicitly specifythe target location where the instance profiledirectory will be copied to.

DB21532E A internal error occurred. File:file-name, Line line-number. Pleasecontact your IBM ServiceRepresentative.

Explanation: The DB2MSCS failed because ofan internal error.

User Response: Run with the trace option andcontact your IBM Service Representative forfurther assistance.

DB21533E An error occurred during themigration of the DB2 instance, rc= error-code.

Explanation: After all the required MSCSresources had been created, the DB2MSCS utilityfailed to migrate the DB2 instance to run in aclustered environment because of an internalerror. During an instance migration, the utilityperforms the following steps:

v Copy the instance directory to the locationspecified by the INSTPROF_DISK orINSTPROF_PATH keyword.

v Move the DB2 registry profile variables fromthe machine registry to the cluster registry.

v Set the DB2INSTPROF registry variable topoint to the new instance profile location.

v Set the DB2CLUSTERLIST to the name of thecurrent machine.

User Response: Before running the DB2MSCSutility, ensure that:

v On the current machine, the instance can bestarted and stopped successfully from thecommand line.

v On other cluster node(s), the same instancemust be stopped and optionally dropped.


v All the disk resources are active on the currentmachine and can be moved back and forthsuccessfully between the cluster nodes.

v The current logon user has sufficient access tothe local machine registry and the clusterregistry.

v If the problem persists, contact your IBMService Representative and provide both theDB2MSCS traces and DB2 traces.

DB21534E An error occurred during additionof MSCS node to the DB2instance, rc = error-code.

Explanation: The utility failed to add the otherMSCS node to the DB2 instance. During thisoperation, the utility will do the followings:

v Update the DB2 cluster machine list by addingthe name of the target machine to theDB2CLUSTERLIST registry variable.

v Create the DB2 service and the registryinstance profile for the current DB2 instanceon the target node.

User Response: Before running the DB2MSCSutility, ensure that:

v On the current machine, the instance can bestarted and stopped successfully from thecommand line.

v On other cluster node(s), the same instancemust be stopped and optionally dropped.

v All the disk resources are active on the currentmachine and can be moved back and forthsuccessfully between the cluster nodes.

v The current logon user has sufficient access tothe target machine registry and the clusterregistry.

v If the problem persists, contact your IBMService Representative and provide both theDB2MSCS traces and DB2 traces.

DB21535E The instance-owning databasepartition server is not on thecurrent machine.

Explanation: When migrating a partitioneddatabase instance, the DB2MSCS utility must berun on the instance owning machine.

User Response: Run the DB2MSCS utility fromthe instance owning machine.

DB21536E The username userid is not valid.

Explanation: The username specified is notvalid.

User Response: Specify a valid username.

DB21537E The password password is notvalid.

Explanation: The password specified is notvalid.

User Response: Specify the correct password.

DB21538E The password for the accountaccount-name has expired.

Explanation: The password for the targetaccount has expired.

User Response: Reset the password andresubmit the command.

DB21540E Group group-name requires at leastone network name resource.

Explanation: When migrating a partitioneddatabase instance, a network name resource mustbe created for the group that contains theinstance owning node.

User Response: Specify to create a networkname resource in the group indicated.

DB21541E An error occurred when removingthe MSCS node from the DB2instance, rc = error-code.

Explanation: During an ″undo″ operation, theutility failed to remove an MSCS node from theDB2 instance because of an internal error.

User Response: Manual clean up is required. Tomanually clean up the instance do the following:

v Stop and drop the DB2 instance.


v Remove all DB2 resources and their dependentresources from the Cluster Administratorwindow.

DB21542E An error occurrred whileattempting to remove failoversupport for the instance. Failoversupport is still active for thisinstance, rc = error-code.

Explanation: During an ″undo″ operation, theutility failed to uncluster the DB2 instancebecause of an internal error.

User Response: Manual clean up is required. Tomanually clean up the instance do thefollowings: Stop and drop the instance. Removeall DB2 resources and their dependent resourcesfrom the Cluster Administrator window.

DB21543E The resource name resource-namedoes not match any IP resource inthe same group.

Explanation: A network name resource must beconfigured to depend on an IP Address resourcein the same resource group.

User Response: Specify the name of an IPAddress resource that resides in the same groupas a dependency for the Network Nameresource.

DB21544E The MSCS resource resource-namealready exists.

Explanation: The resouce name specifiedalready exists in the cluster.

User Response: Specify a different resourcename.

DB21545E The module file-name was loaded,but the function function-name isnot found. Ensure that you arerunning on the version of DB2that supports MSCS.

Explanation: The utility failed to obtain theaddress of a required function because theversion of DB2 is not compatible with the

version of the DB2MSCS utility.

User Response: Use the version of theDB2MSCS utility that is shipped with the DB2product.

DB21546E The module file-name could not beloaded.

Explanation: The utility failed to load therequired DLL.

User Response: Reinstall the DB2 product.

DB21547E Error occurred while movinggroup group-name to nodenode-number. System error:error-msg

Explanation: The utility failed to move thegroup to the target node because one or moreresources can not be moved.

User Response: Ensure that all cluster nodes areactive and that all disk resources can be movedback and forth between cluster nodes. If theproblem persists, contact your IBM ServiceRepresentative.

DB21548E A logon account for the DB2service must be specified for apartitioned database system.Specify a valid logon accountusing theDB2_LOGON_USERNAME andDB2_LOGON_PASSWORDkeywords.

Explanation: The DB2 service for a partitioneddatabase system must be configured to be rununder a valid domain account.

User Response: Specify a valid domain accountusing the DB2_LOGON_USERNAME andDB2_LOGON_PASSWORD keywords.

DB21549N Network name network-namespecified for node node-number isnot valid.

Explanation: The network name value specifiedcould not be resolved.


User Response: Ensure that the network nameis registered in the DNS server or in a localetc/hosts file.

DB21600N The command command did notcomplete successfully.

Explanation: Errors were encountered duringthe execution of this command.

User Response: Contact your technical servicerepresentative. Information in the db2diag.log filewill enable your service representative todetermine the cause of the failure.

DB29320W Output has been truncated.

Explanation: The full query result cannot befetched as supplied. Command line processoroutput can be a maximum ofMAX_STATETMENT_SIZE characters. Howeverthe output of any particular column cannotexceed MAX_COLUMN_SIZE characters inlength.

User Response: The CLP query can be rewrittento fetch a shorter string. Use of another interfaceto DB2 can also help in overcoming the CLP’slimitation.

DB29501E DB2 has detected an inconsistentenvironment. Please investigatethe following : error

Explanation: An error in the operatingenvironment has been detected.

User Response: This error may arise due to aninconsistent DB2 or operating systemenvironment. Attempt to correct the problemidentified in the error message and re-issue thecommand.

DB29502E An incompatible Java RuntimeEnvironment has been detected.Please verify that the requiredlevel of the Java RuntimeEnvironment has been installed.The Java application may belaunched using the Java runtimeinstalled with DB2.

Explanation: The installed Java runtime is notsupported by the DB2 Java application.

User Response: The installed DB2 Java runtimewill be used to launch the DB2 Java application.Other Java applications using the installed Javaruntime should be terminated prior to executingthe DB2 Java application to ensure correctbehaviour.

DB29503E Connections to multiple databasesis not supported.

Explanation: You cannot connect to more thanone database.

User Response: Connect to only one database.

DB29504E Connections to multiple users isnot supported.

Explanation: You cannot connect to more thanone user.

User Response: Connect to only one user.

DB29523W Are you sure you want toCANCEL the query?

DB29524E LogSQLError() Failed

DB29525E LogSQLError() param-1 param-2


DB29526E You cannot drop this table; it doesnot exist. Please select a job thathas results, and try again, or selecta recurring job that is scheduledand try again.

Explanation: A request was made to drop aresult table for a job which did not have anassociated result table.

User Response: Select a job that has a results orselect a recurring job that is scheduled and tryagain.

DB29527W Are you sure you want to canceljob #param-1?

DB29528W Are you sure you do NOT want todisplay job #param-1? WARNING:If you select this option this jobwill never be displayed again.

DB29530W This option will removeconfirmation messages fromactions like ’cancel’ and ’hide’. Isthis something you really want todo?

DB29537E Unknown Type: param-1

DB29542E Connection SQL error: param-1Error Number: param-2Error Message: param-3

DB29543E Resource DLL rqsres.dll notfound.

Explanation: Resource DLL rqsres.dll could notbe loaded succesfully.

User Response: During initialization of DB2Query Patroller Recurring Query Scheduler theresource DLL rqsres.dll could not be loaded as itwas either damaged or deleted. Please reinstallDB2 Query Patroller QueryEnabler.

DB29544E Resource DLL qeres.dll not found.

Explanation: Resource DLL qeres.dll could notbe loaded succesfully.

User Response: During initialization of DB2Query Patroller QueryEnabler the resource DLLqeres.dll could not be loaded as it was eitherdamaged or deleted. Please reinstall DB2 QueryPatroller QueryEnabler.

DB29545E Name invalid: Query Name canonly be 20 characters or less inlength. Please change the nameaccordingly and retry.

Explanation: A name for a query was specifiedwhich was longer than 20 characters.

User Response: Specify a query name that hasat most 20 characters.

DB29546E Name invalid: Query Name canonly contain alphanumericcharacters and spaces...( “a..z”,“A..Z”, “0..9” ). Please change thename accordingly and retry.

Explanation: A name for a query was specifiedwhich contained non-alphanumeric charcters.

User Response: Specify a query namecomposed of only alphanumeric charcaters.

DB29608E Script Load Failed.

Explanation: Script files required by DB2 QueryPatroller Tracker could not be found.

User Response: Please reinstall DB2 QueryPatroller Tracker.

DB29609I HERE !:L:

DB29610E Could not load the ODBC DriverManager.

Explanation: The ODBC driver dllODBC32.DLL could not be loaded.

User Response: The ODBC driver dllODBC32.DLL could not be loaded as it was


damaged or destroyed. Please reinstall ODBC.

DB29611E Three login attempts failed!Exiting Tracker!

Explanation: DB2 Query Patroller Trackerrequires to connect to the ODBC Data Sourcespecified on the login dialog. The userid,password combination specified on the logindialog was not authorized to connect to thespecified database.

User Response: Please relaunch DB2 QueryPatroller Tracker and provide a valid useridpassword combination for the ODBC Data sourcespecified on the login dialog.

DB29613E Resource DLL tkres.dll not found.

Explanation: DB2 Query Patroller Trackerrequires the resource dll tkres.dll for successfuloperation. The dll could not be loaded.

User Response: During initialization of DB2Query Patroller Tracker the resource DLLtkres.dll could not be loaded as it was eitherdamaged or deleted. Please reinstall DB2 QueryPatroller Tracker.

DB29614E The date or time specified is notvalid.

DB29615E The end date and time must beafter the start date and time.

DB29616E The time range must not begreater than two years.

DB29700E The application programminginterface program did not completesuccessfully for object name withreason code name. Try again orcontact your local support.

Explanation: An application programminginterface call did not complete.

User Response: Try the operation again orcontact your system administrator.

DB29701E Class class-name not found. Pleasecheck your classpath.

Explanation: The class_name cannot be locatedin the specified classpath.

User Response: Verify the classpath is correct. Ifyou are using QueryAdmin.bat orQueryMonitor.bat please check the classpathsetting in the batch file.

DB29702E User userID does not haveadministrative authority to useQueryAdministrator.

Explanation: User userID does not haveAdministrative authority defined in the DB2Query Patroller User Profile table.

User Response: Have a DB2 Query Patrolleradministrator ensure that userID has theauthorization necessary to perform the operation.

DB29703E User userID is not defined in UserProfile.

Explanation: User userID is not defined in theDB2 Query Patroller user profile table.

User Response: Have a DB2 Query Patrolleradministrator ensure that userID is defined in theUser Profile table.

DB29704E User iwm cannot be removed.

Explanation: User iwm is the mandatory useridneeded for DB2 Query Patroller so it cannot beremoved.

User Response:

DB29705W Invalid value entered forcolumn-name. Valid ranges arefrom minimum-value tomaximum-value.

Explanation: The value entered for column-nameis invalid.

User Response: Reenter a value that is specifiedwith the range.


DB29706E Job Queue queue-id cannot beremoved. There are one or moreincomplete jobs in this queue.

Explanation: This job queue queue_id cannot beremoved since there are still jobs running on thequeue.

User Response: Wait until all jobs that are onthe queue are completed before deleting it.

DB29707E Result destination destination-nameis already defined.

Explanation: The destination-name specified isalready defined. destination-name must be unique.

User Response: Specify an uniquedestination-name.

DB29708E User userID is already defined.

Explanation: The userID specified is alreadydefined. userID must be unique.

User Response: Specify an unique userID.

DB29709E Group group-id is already defined.

Explanation: The group_id specified is alreadydefined. group_id must be unique.

User Response: Specify an unique group_id.

DB29710E Job Queue queue-id is alreadydefined.

Explanation: The queue_id specified is alreadydefined. queue_id must be unique.

User Response: Specify an unique queue_id.

DB29720E User userID does not have thenecessary authority to useQueryMonitor.

Explanation: User userID is defined in the DB2Query Patroller User Profile table but has noauthority.

User Response: Have a DB2 Query Patrolleradministrator ensure that userID has the

authorization necessary to perform the operation.

DB29721E Error encountered whensubmitting a new job. Reasoncode : reason-code.

Explanation: An error was encountered whensubmitting a new query. Check the reason codereturned.

Reason codes map to a valid SQL message.Check the help for the corresponding SQLmessage.

User Response: Correct the problem and retrythis operation.

DB29722E Error encountered during jobsequence number generation.Reason code = reason-code. Job willnot be submitted.

Explanation: An error was encountered duringjob sequence number generation. Check thereason code returned.



DB29723E Error encountered during purgingof a result set for job job-id.Reason code : reason-code.

Explanation: An error was encountered whenpurging the specified result set. Check the reasoncode returned.


User Response: Correct the problem and retrythis operation. The table may have been droppedmanually outside of the system environment.


DB29724E Error encountered whenattempting to change status forjob job-id. Reason code: reason-code.

Explanation: An error was encountered whenchanging the status for the specified job. Checkthe reason code returned.



DB29725E Error encountered duringresubmit of job job-id with SQLstatement SQL-stmt. Reason code:reason-code.

Explanation: An error was encountered whenresubmiiting the specified job. Check the reasoncode returned.



DB29726E Request completed successfully.

Explanation: The request was successful.

User Response:

DB29727E DB2 Query Patroller server is notinstalled.

Explanation: DB2 Query Patroller server is notinstalled on the DB2 server.

User Response: Install the DB2 Query Patrollerserver.

DB29800E An unexpected error param-1 wasencountered during read.

DB29801E Invalid command line parameters.

Explanation: The parameter for command linespecified is missing or incorrect.


DB29802E Completed with Error.

Explanation: The program terminiated due toan error. Please see the associated error messagesfor the reason.


DB29803E DB2 registry variableregistry-variable is not set or isinvalid.

Explanation: The required DB2 registry variableregistry-variable is not set or has been set with aninvalid format.

User Response: If the DB2 registry variable isDQP_RUNTIME then set DQP_RUNTIME to thefully qualified path where DB2 Query Patroller isinstalled.

If the DB2 registry variable is DQP_SERVER orDQP_NET then set DQP_SERVER or DQP_NETto [host]:[port], where [host] represents the IPaddress of the machine where DB2 QueryPatroller server is installed, and [port] representsthe TCP port used by DB2 Query Patrollerserver.

For any other DB2 registry variable, please referto the DB2 Query Patroller documentation.

DB29804E A memory allocation error hasoccurred.

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

User Response: Ensure that your system hassufficient real and virtual memory.


DB29805E User ID userID is undefined.

Explanation: userID is not defined on theoperating system.

User Response: Create an operating systemuser account or use a correct user ID.

DB29806E Cannot change effective user IDto userID. Operating system error :OS-error.

Explanation:

User Response:

DB29807E An I/O error (reason = code)occurred while reading the filefile.

Explanation: The read operation against filefailed.

User Response: Determine if the I/O error canbe corrected and resubmit the command.

DB29808E An I/O error (reason = code)occurred while writing the file file.

Explanation: The write operation against filefailed.


DB29809E An I/O error (reason = code)occurred during a read operation.

Explanation: Incomplete data was read duringan I/O operation.


DB29810E An I/O error (reason = code)occurred during a write operation.

Explanation: An I/O error occurred during awrite operation. The data may be incomplete.


DB29811E File file-name could not be opened(reason = code).

Explanation: Error encountered while trying toopen file file-name.

User Response: Ensure that the file-name iscorrect and exists in the file system, and that thefile permissions are correct.

DB29812E Error occurred while terminatingprocess process-ID.

Explanation: Error encountered while trying tokill process process-ID.

User Response: Ensure the terminating processhas sufficient authority and the process exists.

DB29813E There is not enough memoryavailable to process the command.

Explanation: Not enough random accessmemory (RAM) is available to process thecommand.

User Response: Check if the system hassufficient paging space. Free up some memoryby stopping unused applications.

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

User Response: Increase the limit which wasreached (or have your system administratorincrease it).

DB29815E Execution of program-name failed(reason = reason-code).

Explanation: Error encountered while executingprogram-name.

User Response: Determine if the problem canbe fixed and retry the operation.


DB29816I Completed successfully.

Explanation: The request was successful.

User Response: No action necessary.

DB29820E Unknown job type type for jobjob-id.

Explanation: The iwm_nodemgr processencountered a job with an unrecognized type.

User Response: Resubmit the query. If problempersists contact an IBM Service representative.

DB29821E Another node manager is running.

Explanation: Only one iwm_nodemgr processcan run on each node.

User Response:

DB29822E Node manager could not recoverjobs.

Explanation: The iwm_nodemgr failed torecover jobs that were running when it lastfailed.

User Response:

DB29823W sysinfo statistics are not beingcollected.

Explanation: CPU utilization cannot becollected for this node because sysinfo facility isdisabled.

User Response:

DB29824E Job job-id not found.

Explanation: The job job-id was not found in thejob table.

User Response:

DB29825I Completion message for job job-idsaved to file file-name.

Explanation: The agent process has lost contactwith the Server component, and was unable to

notify it of job completion. When the NodeManager process successfully restarts on thisnode, the Server component receives notificationof the job’s completion.

User Response:

DB29826N Error encountered when executingSQL statement SQL-statement.Error: sqlcode.

Explanation: The SQL-statement failed.

User Response: Correct the SQL-statement andresubmit the job.

DB29827I Too many columns selected.

Explanation: The job’s SQL statement selectedtoo many columns.

User Response: Correct the SQL statement andresubmit the job.

DB29828E Cannot create result tableresult-table.

Explanation: The result-table could not becreated.

User Response: Make sure system has sufficientfree disk space and the table does not alreadyexist.

DB29829E SQLDA type type is not supportedfor column column-name.

Explanation: DB2 Query Patroller does notrecognize the database column type.

User Response:

DB29830E Job job-id cannot be updated.

Explanation: The request to update this jobcannot be performed because the request changeis not valid for the current state of the job.

User Response:


DB29831W Job job-id (process id process-ID) isno longer running.

Explanation: The job terminated withoutnotifying the Server component.

User Response:

DB29832E Node node-name not found.

Explanation: The RequestHandler NodeManager process is not active on the requestednode.

User Response:

DB29835W Node node-name has not respondedfor 5 minutes, attemptingrecovery.

Explanation: The iwm_nodemgr process hasnot updated the node information for fiveminutes. The iwm_sched process assumes thatthe node has crashed and will recover jobsscheduled for the node.

User Response:

DB29836E Scheduler could not recover jobsfor node node-name.

Explanation: An error occurred during noderecovery.

User Response:

DB29837W No active nodes available toassign jobs.

Explanation: There are no nodes with an activenode manager process.

User Response:

DB29838I number result tables over numberdays old have been purged.

Explanation: Purging of result tables has beenactivated through the DB2 Query Patrollersystem parameters. This message indicates howmany result tables have been purged.

User Response: No action necessary.

DB29839I number jobs over number days oldhave been purged.

Explanation: Purging of DB2 Query Patrollerjobs has been activated through the DB2 QueryPatroller system parameters. This messageindicates how many jobs have been purged.

User Response:

DB29840I PREPARE SQL statementSQL-statement failed for useruserID with SQLCODE sqlcode.

Explanation: The SQL statement could not bePREPARED.

User Response:

DB29841E SQL statement SQL-statementfailed. Exit code code.

Explanation:

User Response:

DB29842E Error sqlcode encountered duringexecution of the following SQLstatement: SQL-statement.

Explanation: The SQL statement failed.

User Response: Correct the SQL statement andresubmit request.

DB29843E Failed to connect to databasedatabase-alias with user ID userID.Error code: sqlcode.

Explanation: The SQL CONNECT statementfailed.

User Response:

DB29844E User userID is not defined in theUser Profile table.

Explanation: There is no row in the User Profiletable for the user.


User Response: Correct the user ID or have anAdministrator add a user to the User Profiletable.

DB29845E Error opening socket. Error :error-code.

Explanation: The socket specified cannot beopen.

User Response: Determine if the problem canbe corrected by examining the error-code.

DB29846E Error closing socket. Error :error-code.

Explanation: The socket specified cannot beclosed.


DB29847E Error occurred while sending orreceiving data. Error : error-code.

Explanation: Error happened while sending /receiving data.


DB29848E Error encountered on TCP/IPprotocol support. TCP/IP functionfunction. Socket was socket. Error :error-code.

Explanation: The TCP/IP function failed.


DB29849E The specified listener portlistener-port is not valid.

Explanation: The specified listener port is notvalid.

User Response: Verify the DB2 Query Patrollerconfiguration parameters are correctly set.

DB29850E The specified connect portconnector-port is not valid.

Explanation: The specified connect port is notvalid.


DB29851E Invalid internet addressinternet-addr.

Explanation: The specified internet address isnot valid.


DB29852E TCP/IP could not find host namehost-name in the local Hosts file.

Explanation: The host_name specified cannot notbe resolved.


DB29853E Service service-name is not definedin the TCP/IP services file.

Explanation: The service_name specified cannotnot be resolved in the TCP/IP service file.


DB29854E Invalid network identifiernetwork-string.

Explanation: The network identifier must be inthe form host-id:port-id where host-id representseither a resolvable host name or the dottedinternet address and port-id represents either aresolvable service name or a port number.



DB29855E DB2 Query Patroller server is notavailable.

Explanation: The Server component cannot becontacted.


DB29856E A severe internal processing errorhas occurred. Error error-code.

Explanation: An internal DB2 Query Patrollerfailure occurred.

User Response: Please contact an IBM Servicerepresentative.

DB29857E name value is missing.



DB29858E name value is invalid.



DB29859E Destination name is no longervalid.

Explanation: An destination name is no longeractive.

User Response:

DB29860E Expected response message notreceived.



DB29861E Connection to iwm_net lost.

Explanation: The iwm_net program is nolonger active.

User Response: Restart the Server componentor agent on this node.

DB29862E Not connected.



DB29863E Message not understood.



DB29864E iwm_local database access is notavailable.

Explanation: The iwm_local program failed orwas not started successfully.

User Response: Restart the DB2 Query Patrollerand all agents.

DB29865E iwm_remote database access is notavailable.

Explanation: The iwm_remote program failedor was not started successfully.

User Response: Restart the Server component.

DB29866E iwm_local database access failed.

Explanation: The iwm_local program failed orwas not started successfully.



DB29867E iwm_remote database accessfailed.

Explanation: The iwm_remote program failedor was not started successfully.


DB29868E Invalid ticket.



DB29869E Logon has expired.

Explanation: Your logon to DB2 QueryPatroller has expired.

User Response: Log on again.

DB29870E Not authorized.

Explanation: You are not authorized to performthe requested function.

User Response: Contact your SystemAdministrator to obtain the necessaryauthorization.

DB29871N Mail for job job-id job-status couldnot be sent to email-address.Reason : reason-code.

Explanation: Error encountered during sendingof user notification for job job-id.

User Response:

DB29986I Stopping param-1 process ...

DB29987E Failed to start param-1 - Pleasecheck system log param-2

DB29989I Starting param-1 process ...

DB29991E DB2 Query Patroller Server is notcorrectly installed.

Explanation: DB2 Query Patroller Server wasnot installed correctly.

User Response: Please reinstall DB2 QueryPatroller server.

DB29992E Cannot access param-1. param-2will be stopped.

DB29995I Listing param-1 processes ...

DB29997I param-1 started successfully

DB29998I param-1 stopped successfully

DB29999E param-1 terminated abnormally.param-2

DB210016E Cannot initialize TCP/IP (reason =reason-code). Ensure that theversion of WINSOCK.DLL onyour system is less than or equalto winsock-level.

Explanation: Cannot initialize TCP/IP. TheTCP/IP return code is invalid.

User Response: Ensure the WINSOCK versionis supported by DB2 Query Patroller. DB2 QueryPatroller supports versions of WINSOCK.DLLless than or equal to winsock-level.

DB210017E Unsupported WINSOCK.DLLlevel. Ensure that the version ofWINSOCK.DLL on your system isless than or equal to winsock-level.

Explanation: This version of the fileWINSOCK.DLL is not supported by DB2 QueryPatroller.

User Response: Ensure the WINSOCK versionis supported by DB2 Query Patroller. DB2 QueryPatroller supports versions of WINSOCK.DLLless than or equal to winsock-level.


DB210018E Could not register signal handlerfor process ID process-ID, reasoncode = reason-code.

Explanation: Failed to create the signal handlerfor the event object.

User Response:

DB210019E Could not wait on signal handlersemaphore for process IDprocess-ID, reason code =reason-code.

Explanation: Failed to wait for the signalhandler for the event object.

User Response:

DB210020E Could not create thread for signalhandler for process ID process-ID,reason code = reason-code.

Explanation: Failed to create a thread object forthe signal handler for the current process.

User Response:

DB210021E Could not post a signalsemaphore for process IDprocess-ID, reason code =reason-code.

Explanation: Failed to set the state of the eventto be signaled for the current process.

User Response:

DB210022E Could not logon, reason code =reason-code.

Explanation: The user ID and passwordprobably are not correct, or the user has not beengranted the required privileges.

User Response: Check the user ID andpassword, or ask the system administrator togrant the appropriate privileges for your user ID.

DB210023E Could not switch to a differentuser ID, reason code = reason-code.

Explanation: DB2 Query Patroller was unable toswitch to a different user ID, because the targetuser ID was already logged on.


DB210024E Load failed with reason code =reason-code.

Explanation: Failed to load data from files,tapes, or named pipes into a DB2 table.

User Response: Ensure that the data sourcesexist.

DB210025E Load failed after reading rowsrows. Reason code = reason-code.

Explanation: Failed to load data after readingrows, reason code = reason-code.

User Response:

DB210026E Load failed when reading linefrom file file-name.

Explanation: Error encountered when readingline from file-name.

User Response: Ensure that the message filefile-name exists.

DB210027E user-profile or userID is alreadydefined.

Explanation: The user ID userID already existsfor DB2 Query Patroller.

User Response: Define a unique user ID forDB2 Query Patroller.

DB210028E Destination destination-name isalready defined.

Explanation: The result destination alreadyexists for DB2 Query Patroller.

User Response: Define a unique resultdestination name for DB2 Query Patroller.


DB210030E MAPI not initialized, reason code= reason-code.

Explanation: Failed to initialize the MessagingApplication Programming Interface (MAPI).

User Response: Ensure that the file MAPI32.dllexists.

DB210031E MAPI is not available on thismachine.

Explanation: Messaging ApplicationProgramming Interface (MAPI) is not installedon this machine.

User Response: Ensure that MAPI is correctlyinstalled and initialized. Ensure that the fileMAPI32.dll exists.

DB210032E Could not invoke iwm_cmdprogram.

Explanation: Failed to invoke iwm_cmdprocess.

User Response: Check if the DB2 QueryPatroller server is running.

DB210033E The mail mail-subject could not besent to mail-address, reason code =reason-code.

Explanation: The mail mail-subject could not besent to mail-address.

User Response: Ensure that MessagingApplication Programming Interface (MAPI) iscorrectly installed and initialized. Ensure that thefile MAPI32.dll exists.

DB210034E Start date of the schedule must bebefore the end date.

DB210035E This schedule already exists.

DB210036E Result table result-table does notexist.

Explanation: Result table result-table does notexist in the database.

User Response: The selected result tableresult-table does not exist, please select anotherone.

DB210037I DQPSTART processing wassuccessful.

Explanation: The command to start DB2 QueryPatroller completed successfully.

DB210038I DQPSTOP processing wassuccessful.

Explanation: The command to stop DB2 QueryPatroller completed successfully.

DB210039E DQPSTART or DQPSTOPcommand is already in progress.

Explanation: The DB2 Query Patroller iscurrently processing a start or a stop command.

User Response: There is another instance ofDB2 Query Patroller start or stop commandbeing processed.

User Response: Wait until the currentlyprocessing command completes. If there are noother processes starting or stopping the DB2Query Patroller, you can remove ’dqpstst.lck’ filefrom the ’ctrl’ directory in the instance path andretry the command.

DB210040W DB2 Query Patroller service didnot start properly.

Explanation: One or more processes may nothave started successfully.

User Response: Check the ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210041E Request for DB2 Query Patrollerlicense failed.

Explanation: DB2 Query Patroller could not bestarted without a valid license file.


DB210044E Unexpected command parametercommnad-token was encountered.

Explanation: The issued command is invalid.

User Response: Check the documentation forvalid syntax.

DB210045E DB2 Query Patroller encountereda system error which terminatedprocessing.

Explanation: An error occurred whichterminated processing.

User Response: Check the ’syserr.log’ and’db2diag.log’ for more diagnostic information.

DB210046E File seek operation on filename hasfailed (reason = reason-code).

Explanation: During processing, the file mayhave become corrupted or otherwiseunoperational.

User Response: Retry the command and if theproblem persists, check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210047E Change of access permissions onfile filename has failed (reason =reason-code).

Explanation: The file access permissions couldnot be set. This condition may be due tounavailability of the file or other systemcondition that prevented the adjustment of filepermissions.

User Response: Retry the command and if theproblem persists, check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210048E Invalid file format of file filenameat line line-number.

Explanation: Processing could not continue dueto the unexpected tokens or an invalid fileformat.

User Response: Check the documentation for aproper setup.

DB210049E Could not retrieve instance path(reason = reason-code).

Explanation: The instance path could not beretrieved.

User Response: Ensure the DB2 is setupproperly before issuing the command again. Ifthe problem persists, check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210050E Could not retrieve the install path(reason = reason-code).

Explanation: The DB2 installation path couldnot be retrieved.

User Response: Ensure the DB2 is setupproperly before issuing the command again. Ifthe problem persists, check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210051E Could not retrieve instanceconfiguration (reason =reason-code).

Explanation: The instance database managerconfiguration could not be retrieved.

User Response: Ensure DB2 is setup properlybefore issuing the command again. If theproblem persists, check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210052E Could not get local host orcomputer name (reason =reason-code).

Explanation: The computer name (NT) or hostname (UNIX) could not be retrieved.

User Response: Contact your systemadministrator or check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210053E Could not resolve host namehostname.



DB210054E DQPSTART processing failed.

Explanation: DB2 Query Patroller could not bestarted.

User Response: Check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210055E System error. Registering servicecontrol handler failed.

Explanation: System error occurred whichterminated processing.


DB210056E System error. Check for servicestart-pending status failed.



DB210057E System error. Initialization ofservice security descriptor failed.



DB210058E System error. Create event failed.

Explanation: System error occurred whichterminated processing. Check ’syserr.log’ and’db2diag.log’ for more diagnostics.


DB210059E Processing of configuration filefilename failed (reason =reason-code).

Explanation: The configuration file could not beprocessed because it is in an invalid format, hasunexpected tokens, or is otherwise corrupted.

User Response: Check the documentation forproper formatting of the file. If the problempersists, contact your system administrator orcheck ’syserr.log’ and ’db2diag.log’ for morediagnostics.

DB210060E Attempt to start serviceservice-name failed (reason =reason-code).

Explanation: The service could not be started.The reason codes are as follows:

1 The service does not exist.

3 The service is already running.

5 The current user does not have theproper authority to start or stop theservice.

6 The service fails to start.

User Response:

1 Ensure the service exists. If the servicedoes not exist, then it might have beenmanually removed, or the installation ofDB2 Query Patroller did not completesuccessfully. In either case, DB2 QueryPatroller must be reinstalled.

3 The service was already started. Torestart the service, issue the DQPSTOPcommand and issue the DQPSTARTcommand again.

5 Ensure that the logon information forthe service is correct and issue thecommand again.

6 Issue the command again. If theproblem persists, contact your systemadministrator or check the ’syserr.log’and ’db2diag.log’ for more diagnostics.

DB210061E Attempt to stop serviceservice-name failed (reason =reason-code).

Explanation:

1 The service does not exist.


3 The service has not been started or wasalready stopped.

5 The current user does not have theproper authority to start or stop theservice.

6 The service fails to stop.

User Response:

1 Ensure the service exists. If the servicedoes not exist, then it might have beenmanually removed, or the installation ofDB2 Query Patroller did not completesuccessfully. In either case, DB2 QueryPatroller must be reinstalled.

3 The service was already stopped. Torestart the service, issue the DQPSTARTcommand.

5 Ensure that the logon information forthe service is correct and issue thecommand again.

6 Issue the command again. If theproblem persists, contact your systemadministrator or check the ’syserr.log’and ’db2diag.log’ for more diagnostics.

DB210062E System error. Commoninitialization routines failed(SQLCODE = sqlcode).

Explanation: Environment could not beinitialized because of SQLCODE sqlcode.

User Response: Check the SQLCODE and issuethe command again. If the problem persists,contact your system administrator or check’syserr.log’ and ’db2diag.log’ for morediagnostics.

DB210064E System error. Message queuefailed (reason = reason-code).


User Response: Retry the command and if theproblem persists, contact your systemadministrator or check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210065E DB2 Query Patroller node is notactivated.

Explanation: The selected node is not setup forprocessing.

User Response: Ensure that the specified nodeis defined in ’dqpnodes.cfg’ and retry thecommand.

DB210066E Node start or stop processingresults could not be retrievedfrom file filename (reason =reason-code).

Explanation: The contents of thecommunication file could not be retrieved. Thefile does not exist or could not be opened.

User Response: Ensure that the specified file isaccessible and retry the command. If the problempersists, contact your system administrator orcheck ’syserr.log’ and ’db2diag.log’ for morediagnostics.

DB210067E Node start or stop processing hasreached timeout value.

Explanation: The DB2 Query Patroller start orstop command has reached a timeout valuewhile waiting for results from the processingnode(s). The result files contents could not beobtained because they were not created or notaccessible.

User Response: Ensure that ’dqpnodes.cfg’ issetup correctly and all host names and IPaddresses and computer names are resolvable.See the documentation for proper setup. Checkfor proper setup of DQP_SERVER and DQP_NETvariables and their corresponding entries in the’services’ file. On ESE check for proper setup ofthe ’rah’ utility. Check ’syserr.log’ and’db2diag.log’ for more diagnostics.


DB210068E Communication error has beenencountered while waiting fornode(s) to complete processing(reason = reason-code).

Explanation: The DB2 Query Patroller start orstop command could not continue due to invalidresult file generated by one of the processingnodes. The result file could not be interpretedcorrectly.


DB210069E Process process-name has failed.

Explanation: Process failed.


DB210070E Execution of process process-namehas failed (reason = reason-code).

Explanation: Process could not be started.


DB210071E Execution of process process-namewas interrupted (reason =reason-code).

Explanation: Running process was interrupted.


DB210072E An external program program-namecould not be located (reason =reason-code).

Explanation: Could not find a specifiedexecutable.

User Response: Check your installation or

contact your system administrator before retryingthe command. Check ’syserr.log’ and’db2diag.log’ for more diagnostics.

DB210073E An external program program-namecould not be invoked due toinsufficient resources (reason =reason-code).

Explanation: Could not allocate resources tolaunch the process.


DB210074E An external program program-namecould not be invoked due toinsufficient authority (reason =reason-code).

Explanation: The user invoking the programdoes not have sufficient authority to do so.


DB210075E DQPSTART processing hascompleted. number-of node(s) werestarted successfully, number-ofnode(s) were already started,number-of node(s) have failed.

Explanation: DB2 Query Patroller start managercompleted processing however at least one nodereported a warning or an error while processingthe node start command.


DB210076E DQPSTOP processing hascompleted. number-of node(s) werestopped successfully, number-ofnode(s) were already stopped,number-of node(s) have failed.

Explanation: DB2 Query Patroller stop managercompleted processing however at least one node


reported a warning or an error while processingthe node stop command.


DB210085E The operation was abortedbecause it would violateconfiguration consistencyconstraint. SQLSTATE=state-code.

Explanation: SQLSTATE=88000,88001: Operationfailed because it would violate one of thefollowing constraints on theIWM003_JOB_QUEUE table:

MAX(MAX_JOBS) <=IWM003_DATA_SOURCE.MAX_JOBSANDMAX(MAX_COST) <=IWM003_DATA_SOURCE.COST_THRESHOLD

SQLSTATE=88002,88003,88004: Operation failedbecause it would violate one of the followingconstraints on the IWM003_DATA_SOURCEtable:

MAX_JOBS >=MAX(IWM003_JOB_QUEUE.MAX_JOBS)ANDMAX(MAX_JOBS) <=IWM003_SYS_PARMS.QRY_THRESHOLDANDCOST_THRESHOLD >=MAX(IWM003_JOB_QUEUE.MAX_COST)ANDMAX(COST_THRESHOLD) <=IWM003_SYS_PARMS.COST_THRESHOLD

SQLSTATE=88005: Operation failed because itwould violate one of the following constraints onthe IWM003_SYS_PARMS table:

QRY_THRESHOLD >=MAX(IWM003_DATA_SOURCE.MAX_JOBS)ANDCOST_THRESHOLD >=MAX(IWM003_DATA_SOURCE.COST_THRESHOLD)

SQLSTATE=88006,88007: TableIWM003_SYS_PARMS can have at most one row.This single row may be deleted if the tableIWM003_DATA_SOURCE is empty.

SQLSTATE=88008: A user or a group profile withmatching name and possibly different casealready exists.

User Response: Please revise your configurationand specify a valid value for the field.

DB210101E Read queue operation failedwhile waiting for a response fromprocess. Return code = return-code.Queue handle = queue-handle.Timeout = timeout-value.

Explanation: A read queue operation failedwhile waiting for a response from process. Thiserror can occur if the timeout period is too shortor if the queue handle is invalid.

User Response: Set DQP_CHILD_WAIT DB2profile variable to a value greater than thetimeout-value and try again. If the problempersists, contact your system administrator toremove queue-handle from your system.

DB210102E The DB2 instance was not found.Reason code = reason-code.

Explanation: The DB2 instance was not found.The DB2INSTANCE environment variable is notset to a valid DB2 instance.

User Response: Please ensure thatDB2INSTANCE environment variable or DB2profile variable DB2INSTDEF is set to a validDB2 instance.

DB210103E Error deleting message queue.Reason code = reason-code. Queuehandle = queue-handle.

Explanation: An error occurred deletingmessage queue queue-handle.

User Response: Please contact your systemadministrator to remove queue-handle from yoursystem.


DB210104E Error initializing message queue.Reason code = reason-code. Queuename = queue-name.

Explanation: An error occurred initializingmessage queue queue-name. This error can occurif a queue with that name already exists.

User Response: Please contact your systemadministrator to remove queue-name from yoursystem.

DB210105E Error writing to the primarymessage queue. Reason code =reason-code. Queue handle =queue-handle. Request type =request-type. Action type =action-type. Set type = group-type.Trace = trace-flag.

Explanation: An error occurred writing to theprimary message queue queue-handle. This errorcan occur if the queue handle is invalid.


DB210106E Error reading from the primarymessage queue. Reason code =reason-code. Queue handle =queue-handle. Timeout =timeout-value seconds.

Explanation: An error occurred reading fromthe primary message queue queue-handle. Thiserror can occur if the queue handle is invalid.


DB210107E Error opening message queue.Reason code = reason-code. Queuename = queue-name.

Explanation: An error occurred openingmessage queue queue-name. This error can occurif a queue with the name queue-name alreadyexists and this process does not have theauthority to open it.

User Response: Please contact your systemadministrator to remove queue-name from yoursystem.

DB210108E Error acquiring lock on filefile-name. Reason code =reason-code.

Explanation: Error acquiring a file lock on filefile-name. This error can occur if this process doesnot have the authority to lock file file-name in the/tmp directory.

User Response: If the file file-name exists in the/tmp directory, please contact your systemadministrator to remove it from your system.

DB210109E Error sending message on queue.Reason code = reason-code. Queuehandle = queue-handle. Message =message.

Explanation: An error occurred sendingmessage message on queue queue-handle. Thiserror can occur if this process does not haveauthority to write to the queue.


DB210110E Error closing message queue.Reason code = reason-code. Queuehandle = queue-handle.

Explanation: An error occurred closing messagequeue queue-handle. This error can occur if theprocess does not have the authority to close thequeue.



DB210111E For the selected interval andfrequency, no jobs can bescheduled between the chosenstart date and time and the enddate and time.

Explanation: The selected interval andfrequency does not allow any jobs to bescheduled between the chosen start date andtime and the end date and time.

User Response: To enable job scheduling,perform one of the following options:

v Increase the time range by adjusting the startdate and time or the end date and time.

v Choose a different interval and frequencyvalue for the given time range so that there isat least one scheduling opportunity.

DB210112E The DB2 Query Patroller serverprocess or processes server-processhave stopped. The remaining DB2Query Patroller server processeshave also stopped.

Explanation: If one or more DB2 QueryPatroller server processes, such as iwm_logmon,iwm_net, iwm_server, iwm_remote,iwm_nodemgr, or iwm_sched have stopped, theother DB2 Query Patroller server processes alsostop.

User Response: Check the syserr.log file todiagnose the cause of the stopped DB2 QueryPatroller server processes. Restart the DB2 QueryPatroller server.

DB210113E Node start or stop processing hasfailed. Reason code reason-code.

Explanation: DB2 Query Patroller cannot bestarted or stopped on the specified node. Thereason codes are as follows:

1 A server node already exists in thedqpnodes.cfg file. There can be only oneserver node.

2 There is no server node in thedqpnodes.cfg file.

3 There is an existing entry with the samenode number in the dqpnodes.cfg file.

4 The node number does not exist in thedqpnodes.cfg file.

5 There is an existing entry with the samehostname in the dqpnodes.cfg file.

6 The node type is invalid.

7 Cannot replace the server node entrywith an agent. A server node entry mustexist in the dqpnodes.cfg file.

8 Cannot drop the server node entry. Aserver node entry must exist in thedqpnodes.cfg file.

9 More than one server node entry isfound in the dqpnodes.cfg file. Therecan only be one server node.

10 There is an invalid node number in thedqpnodes.cfg file.

11 There are duplicate node numbers in thedqpnodes.cfg file.

12 There are duplicate host names in thedqpnodes.cfg file.

User Response:

1 Issue the command again withoutattempting to add or restart a secondserver node.

2 Add a server node in the dqpnodes.cfgfile.

3 Check the node number and issue thecommand again using a different nodenumber.

4 Check the node number and issue thecommand again using an existing nodenumber.

5 Check the hostname and issue thecommand again using a different hostname.

6 Issue the command again using thenode type ″server″ or ″agent″.


7 Issue the command again withoutattempting to replace the server nodewith an agent.

8 Issue the command again withoutattempting to drop the server node.

9 Determine which entry is the servernode, and remove the other server nodeentries from the dqpnodes.cfg file.

10 Check the node numbers in thedqpnodes.cfg file and ensure that theyare valid non-negative integers.

11 Check the node numbers in thedqpnodes.cfg file and ensure that theyare unique.

12 Check the host names in thedqpnodes.cfg file and ensure that theyare unique.

Note: You can restart a server node using adifferent hostname, but cannot drop orreplace the only server node entry.

DB210114E The machine name set in the DB2registry variable DQP_SERVERdoes not match the server nodeentry in the dqpnodes.cfg file.

Explanation: The DB2 registry variableDQP_SERVER is set to [host]:[port], where [host]represents the IP address of the machine whereDB2 Query Patroller server is installed. This IPaddress does not match the IP address of theserver node in the dqpnodes.cfg file.

User Response: Ensure the IP address of theserver node entry in the dqpnodes.cfg filematches the IP address set in the DB2 registryvariable DQP_SERVER.

DB210115E The current user is not authorizedto run the commandcommand-name.

Explanation: The current user does not have theproper authority to run the command. If thecommand is DQPSTART, DQPSTOP orIWM_TRACKER, only the user “iwm” is allowedto run it.

User Response: If the command is DQPSTART,DQPSTOP or IWM_TRACKER, log on as theuser “iwm” and issue the command again.

DB210116E The DB2 Query Patroller wasalready started on this node.

Explanation: DB2 Query Patroller was alreadyrunning when the DQPSTART command wasissued.

User Response: To restart the DB2 QueryPatroller, first issue the DQPSTOP command andthen issue the DQPSTART command.

DB210117E The DB2 Query Patroller wasalready stopped on this node.

Explanation: The DB2 Query Patroller Serverwas not running when the DQPSTOP commandwas issued.

DB210118E File filename could not be deleted(reason = reason-code).

Explanation: Error encountered while trying todelete file filename.

User Response: Ensure that the file filename iscorrect and exists in the file system, and that thefile permissions are correct.

DB210120E Failed to connect to databasedatabase-name with user ID useriddue to a recoverable error withSQLCODE sqlcode. Retryingconnect in retry-interval minute orminutes.

Explanation: DB2 Query Patroller server failedto connect to the database due to a recoverableerror with SQLCODE sqlcode.

User Response: Check the SQLCODE and fixthe recoverable error. The DB2 Query Patrollerserver will attempt to connect to the databaseagain in retry-interval minute or minutes.


DB210121E Cannot recover status of the jobswhich belong to an active node.

Explanation: The specified node is still active.Job status recovery is only allowed for jobsrunning on a node that failed.

DB210123E The scheduled date cannot be inthe past.

Explanation: The start and/or end datespecified is in the past.

User Response: Ensure that the scheduled dateis not in the past, or check that the date and timeof your operating system is set properly.

DB210200I All applications must disconnectfrom the database before thechanges become effective.

Explanation: The ADD or DROP DATALINKSMANAGER command has been successfullyprocessed. However, the change cannot be madeeffective until all applications have disconnectedfrom the database. After the applicationsdisconnect from the database, the first connectionto the database will cause the changes to becomeeffective.

User Response: Ensure that all applicationsdisconnect from the database and issue aCONNECT statement.

DB210201I Reconcile utility should be run ondatabase tables that contain linksto files on the DB2 Data LinksManager. The DB2 Data LinksManager does not perform anyunlink processing for these files.

Explanation: The DROP DATALINKSMANAGER command has been successfullyprocessed. Confirm that no database tablescontained links to files on the DB2 Data LinksManager before dropping the DB2 Data LinksManager. If such links exist, they should beremoved from the database tables by using thereconcile utility. Note that the files themselveswill remain in linked state on the file system. Foradditional details, see the usage notes for the

DROP DATALINKS MANAGER command in theCommand Reference.

DB210202E Less than number MB of memoryis dedicated to your server. Norecommendation has been made.The current values match thesuggested values.

Explanation: Because the amount of memorydedicated to the server is so small, thePerformance Configuration wizard cannot makea recommendation. Configuration parameterswill not be changed.

User Response: If you can dedicate morememory to the server, re-run the command witha larger value specified for the optionMEM_PERCENT.

DB210203I AUTOCONFIGURE completedsuccessfully. Database manager ordatabase configuration values mayhave been changed. The instancemust be restarted before anychanges come into effect. You mayalso want to rebind your packagesafter the new configurationparameters take effect so that thenew values will be used.

Explanation: The Configuration Advisor hasgenerated its recommendations, and has updatedthe configuration parameters and buffer poolsizes as requested by the user.

The changes will not take effect until the instanceis restarted on the server.


User Response: When you are ready to use thenew configuration parameters, stop the instance,and then restart the instance. Rebind yourpackages if necessary


DB210204E An error occurred when theConfiguration Advisor tried to getsystem information from yourserver.

Explanation: An unexpected error occurred. TheConfiguration Advisor cannot continue.


DB210205W The Configuration Advisor wasunable to increase the sizes of thebuffer pools due to other memoryrequirements determined fromyour responses. The buffer poolsizes are left unchanged. The useof the suggested set ofconfiguration values may causepaging on the server.

Explanation: This is a warning that there maynot be enough memory dedicated to your serverto run the workload that you specified.

User Response: Review your input for thiscommand to check that the workload descriptionis appropriate or add more memory to yourserver.

DB210206W The transactions rate you enteredis more than ten times the averagenumber of connected applications.If you are using a transactionmanager, ignore this message. Ifnot, consider changing this rate.

Explanation: The Configuration Advisor verifiesthat the transactions rate is reasonable. Thetransaction rate may be too high if you are notusing a transaction manager.

User Response: If you are using a transactionmanager, ignore this message. Otherwise, use alower number of transactions per minute, orincrease the average number of connectedapplications.

DB210207E Unable to autoconfiguredatabase-name. Creation of databasedatabase-name failed.

Explanation: An unexpected error occurred. TheConfiguration Advisor cannot continue, and thedatabase you were trying to create failed.

User Response: Try running CREATEDATABASE without the AUTOCONFIGUREoption, and then running AUTOCONFIGURE inorder to configure your database.

DB210208E Cannot autoconfigure databases inEEE system. Creation of databasedatabase-name failed.

Explanation: The AUTOCONFIGURE option isnot available for EEE. The database was notcreated.

User Response: Try running CREATEDATABASE without the AUTOCONFIGUREoption, and then running AUTOCONFIGURE inorder to configure your database.

DB210209I The database was createdsuccessfully. Please restart theinstance so configuration changestake effect.

Explanation: The Configuration Advisor hasupdated the database manager configurationparameters, database configuration parameters,and buffer pool sizes in the SYSBUFFERPOOLScatalog.

The changes will not take effect until the instanceis stopped on the server.


User Response: When you are ready to use thenew configuration parameters, stop the instance,and then start the instance. Rebind yourpackages if necessary.


DB210210E The parameter for APPLY is notsupported by the ConfigurationAdvisor for this server release.

Explanation: Only APPLY DB OR DBM orAPPLY NONE are valid parameters for theConfiguration Advisor for this server release.

User Response: Reissue the command usingAPPLY DB OR DBM or APPLY NONE.

DB210211W AUTOCONFIGURE completedsuccessfully, but has onlycalculated recommendations forthe current database partition. Youmay wish to runAUTOCONFIGURE on alldatabase partitions or propagatethese recommendations to alldatabase partitions on yoursystem.

Explanation: The Configuration Advisor hasgenerated its recommendations, and has updatedthe configuration parameters and buffer poolsizes as requested by the user for only thecurrent database partition.

The changes will not take effect until the instanceis restarted on the server, but should bepropagated to other database partitions on thissystem by running AUTOCONFIGURE for eachdatabase partition, or through separate useraction.


User Response: When you are ready to use thenew configuration parameters, stop the instance,and then start the instance. Rebind yourpackages if necessary.

DB210212W The recommendations made bythe Configuration Advisor requirea greater percentage of memorythan that specified. Norecommendation has been made.The current values match thesuggested values.

Explanation: There is not enough memoryavailable to be allocated for therecommendations made by the ConfigurationAdvisor.

User Response: Resubmit the command,specifying a greater percentage of memory.

DB210213W The recommended number ofdisks for the specified inputsexceeds the number available. Norecommendation has been made.The current values match thesuggested values.

Explanation: There are not enough disksavailable for the recommendations made by thePerformance Configuration Wizard.

User Response: Resubmit the command oncethere are more disks available.

DB210214W The recommended amount ofmemory for the specified inputsexceeds the amount available. Norecommendation has been made.The current values match thesuggested values.

Explanation: There is not enough memoryavailable to be allocated for therecommendations made by the ConfigurationAdvisor.

User Response: Resubmit the command eitherwith different input values or once a greateramount of memory is available.


Chapter 10. DWC Messages

This section contains the messages issued by the Data Warehouse Center(DWC). The messages are listed in numeric sequence.

DWC0771I Metadata was publishedsuccessfully. Check the log filelogfilename for details.

Explanation: The Data Warehouse Centercompleted the command to publish to aninformation catalog with a return code of zero.Detailed information about each item publishedis located in the log file.

User Response: Check the log file logfilename fordetails.

DWC0772N Metadata publish might haveencountered errors or warnings.Check the log file logfilename fordetails.

Explanation: The Data Warehouse Centercompleted the command to publish to aninformation catalog with a non-zero return code.Detailed information about each item publishedis located in the log file.

User Response: Check the log file logfilename fordetails.

DWC0773N Cannot find the object list filefilename.

Explanation: The object list file could not befound because the agent may have failed tocreate the file. The file should be generated bythe agent after it has read the list from theprogram parameters.

User Response: Run the agent trace to find outwhy the object list file was not created, or contactyour IBM service representative.

DWC0774N Cannot read the object list filefilename.

Explanation: The object list file cannot be readbecause the file is corrupted.

User Response: Check that the file is notcorrupt or contact your IBM servicerepresentative.

DWC0775N Cannot parse the object list filefilename.

Explanation: The object list file cannot beparsed because the file is corrupted or is in anillegal format.

User Response: Check the format of the file orcontact your IBM service representative.

DWC01000I User defined program executedsuccessfully.

DWC01001I User logged on with user IDuserID.

Explanation: Informational message.


DWC01002E Logon Failed. Password does notmatch with user ID userID toDatabase database-name withqualifier qualifier-name.

Explanation: You were unable to log on to thecontrol database because the password that youspecified is not set to your user ID.

User Response: Verify that your password, userID, database name, and table qualifier arecorrect.


DWC01003E Logon Failed. User already loggedon with user ID userID toDatabase database-name withqualifier qualifier-name.

Explanation: You tried to log on to the DataWarehouse Center with a different user ID whenyou are already logged on to the DataWarehouse Center.

User Response: Close the Data WarehouseCenter. Then, log on to the Data WarehouseCenter with the other user ID.

DWC01004E Cannot change the password foruser ID userID because the currentpassword is invalid.

Explanation: You cannot change an oldpassword to a new password because the oldpassword that you entered is incorrect.

User Response: Enter the correct old password.Then, enter the new password.

DWC01005E Invalid function call. Thisfunction cannot be called beforedddApp.LogonAsUser is called.



DWC01006E The Data Warehouse Centeraccess privileges for user IDuserID have been revoked.

Explanation: You are trying to log on to theData Warehouse Center with a user ID that nolonger has access privileges.

User Response: Log on with another user ID orcontact your Data Warehouse Centeradministrator.

DWC01007E Logon Failed. The databasespecified by the user does notmatch the database used by thewarehouse server.

Explanation: Logon Failed. The databasespecified by the user does not match the

database used by the warehouse server.

User Response: Ensure that the specifiedcontrol database is the same database that isused by the warehouse server.

DWC02001E Operation on an ODBC cursor isnot possible when the cursor isnot prepared.



DWC02002E The ODBC connection with theData Warehouse Center controldatabase has not been established.



DWC02003E Allocation of the ODBCenvironment failed (SQLAllocEnvfailed).



DWC02004E Free of the ODBC environmentfailed (SQLEnvFree failed).



DWC02005E Allocation of the ODBC Connectstatement failed(SQLAllocConnect failed).Database: database-name. User ID:user-ID.




DWC02006E Free of the ODBC Connectstatement failed (SQLFreeConnectfailed).

Explanation: An internal message occurred.


DWC02007E Allocation of the ODBC statementfailed (SQLAllocStmt failed).Statement or database:database-name.



DWC02008E Free of the ODBC statementfailed (SQLFreeStmt failed).



DWC02009E Connection to ODBC databasefailed (SQLConnect failed).Database name: database-name.User ID: user-ID.



DWC02010E Disconnect from ODBC databasefailed (SQLDisconnect failed).



DWC02011E Execution of prepared ODBCstatement failed (SQLExecutefailed).



DWC02012E Direct execution of ODBCstatement failed (SQLExecDirectfailed). Statement: statement-name.



DWC02013E Transaction to connected ODBCdatabase failed (SQLTransactfailed).



DWC02014E Prepare of ODBC statement failed(SQLPrepare failed). Statement:statement-type.



DWC02015E Fetch of ODBC data failed(SQLFetch failed).



DWC02016E Extended fetch of ODBC datafailed (SQLExtendedFetch failed).



DWC02017E Bind to ODBC parameter failed(SQLBindParameter failed).Parameter #: parameter-number.Parameter type: parameter-type.



Chapter 10. DWC Messages 323

DWC02018E Bind to ODBC column failed(SQLBindCol failed). Column #:column-number. Data type:data-type.



DWC02019E Set of ODBC statement failed(SQLSetStmtOption failed).Statement: Statement-name.



DWC03101E The new target table name is thesame as the source step targettable name.

Explanation: The step being copied has a newtarget table name specified that is the same asthe target table name of the old step beingcopied.

User Response: In the New Table Name fieldon the Copy step panel, change the name of thenew target table being created to one that isdifferent from the source step being copied.

DWC03102E RelationCollection entry alreadyexists in Relation Name:relation-name.

Explanation: A Data Warehouse Center internalerror occurred.

User Response: Record all details of this errormessage and contact IBM Software Support withthe information.

DWC03103E An invalid target element with anID of ’XXXXXXXXX’ was passedto addLocal for Relation Name:relation-name.


User Response: Record all details of this error

message and contact IBM Software Support withthe information.

DWC03104E object-type object named:object-name is not in a ’valid’ state.It may not have been retrieved orcreated properly.



DWC03105E object-type object named:object-name already exists in theData Warehouse Center database.

Explanation: A Data Warehouse Center usererror or a Data Warehouse Center internal erroroccurred. If the error occurred when you tried tocreate a Data Warehouse Center entity, such as astep, process, security group, user, or database,an entity by that name might already exist.

If the error occurred at a time when you havenot created a new entity, it may be a DataWarehouse Center internal error.

User Response: If you specified a name for anew Data Warehouse Center entity, check thename you specified and make sure an entity bythat name does not already exist.

If you suspect a Data Warehouse Center internalerror, record all details of this error message andcontact IBM Software Support with theinformation.

DWC03106E object-type object was passed aNULL pointer on the methodmethod.




DWC03109E An Invalid value was found inTimeStamp or step objects.



DWC03110E Length of input data for a setoperation of attributeattribute-name in the object object isnot valid.



DWC03112E Object type passed on the retrieveis not a valid Data WarehouseCenter object type.

Explanation: An internal error has occurred.


DWC03113E AttributeLink object does nothave its ’linkType’ operator setcorrectly.



DWC03114E Attribute object does not have its’nativeDataType’, ’Database’, or’Table/File’ attributes set correctly.



DWC03115E The specified native data type:type-name does not have aconversion to ODBC in the DataWarehouse Center.



DWC03116E The ODBC cursor for thelistNext() operation is notinitialized.

Explanation: An internal error message.

User Response: Contact IBM Customer Service.

DWC03117E The ’typeOfMap’ attribute in theMap object is not initialized.Create or update not performed.



DWC03118E The special character character isnot allowed in the object name.This is reserved for a delimiter forData Warehouse Center tokens.

Explanation: You tried to create a table orcolumn with the specified special character,which is reserved for Data Warehouse Centertokens that can be included in a SQL SELECTstatement. You cannot use this special characterin the name of a table or column.

User Response: Remove the specified specialcharacter from the table or column name beingcreated.


DWC03119E The object-type object namedobject-name is already beingupdated. Cannot update objects atthe same time.

Explanation: You are trying to update the DataWarehouse Center entity named object-name atthe same time as another user.

User Response: Wait until completion of theinitial update is finished.

DWC03120W Column column-name withprecision precision and scale scaleis created as a data-type withprecision precision and scale scalein the target table. This may causean error or possible loss of data.Verify the definition of columncolumn-name.

User Response: Verify the definition of columnstep-name.

DWC03127E An Object-in-use error occurred.

Explanation: You tried to remove a securitygroup that is in use by a step that uses aspecified database.

User Response: Before removing this securitygroup from the Selected Security Groups forthis database, you must delete or modify anyreferences to the database and security group inany steps that use the database.

DWC03142E object-type object: object-name wasnot found in the Data WarehouseCenter control database.

Explanation: If you were trying to open a DataWarehouse Center from a list, another user mighthave deleted the entity you were trying to open.Otherwise, an internal Data Warehouse Centererror occurred.

User Response: Refresh the list and open theentity again. If the same error occurs, record alldetails of this error message and contact IBMSoftware Support with the information.

DWC03148E An invalid site hostname waspassed to the Agent Site object.

Explanation: You specified a hostname for anagent site that is greater than 200 characters inlength.

User Response: In the Host Name field of theAgent Site notebook, shorten the name of theagent site to less than 200 characters.

DWC03149E An invalid OS type was passed tothe AgentSite object.



DWC03150E An invalid user ID was passed tothe AgentSite object.



DWC03151E An invalid password was passedto the AgentSite object.



DWC03153E Table table-name is being used bya step as a target table.




DWC03154E Target table table-name is beingused by a step as an input table.

Explanation: You are trying to delete a DataWarehouse Center table definition for a table thata step uses as a source table.

User Response: Before deleting the table, deleteor change any references to the source table inthe step to a different source table.

DWC03156E The Column object object-name isbeing used by a Map object as aninput attribute.

Explanation: You are trying to delete a columnof a table that a step uses as a source column.

User Response: Before deleting the column,delete or change any references to the sourcetable in the step that uses the column as a sourceto a different source table.

DWC03157E The Column object object-name isbeing used by an AttributeLinkobject as an Attribute1 column.



DWC03158E The Column object object is beingused by an AttributeLink objectas an Attribute2 column.



DWC03159E The Agent Site cannot be deletedbecause it is being used by one ormore steps.

Explanation: You are trying to delete an agentsite that one or more steps specify as their agentsite.

User Response: Before deleting the agent site,delete or change any references to the agent sitein the steps to a different agent site.

DWC03160E The target table for step step-nameis linked as a source to anotherstep.

Explanation: You are trying to delete a stepwhere the target table is linked as a source toanother step.

User Response: You can delete this step byunlinking it from its target table. The target tablewill still be used as a source to the other steps.You should define a new way for the target tableto be populated. You can view all the steps thatdepend on this target table by performing ashow related on either the step or the targettable.

Before deleting the step, delete or change anyreferences to the source step in the steps. Todetermine what steps use this step as a source,right-click the step that you want to delete, andclick Show Related. This action shows you all thesteps that are populated with data from this step.

DWC03163E The SecurityGroup object is beingused by the Data WarehouseCenter steps as the UpdateSecurity Group.

Explanation: You are trying to delete a securitygroup that one or more steps use as an updatesecurity group.

User Response: Before deleting the securitygroup, change the update security group to adifferent security group.

DWC03164E The SecurityGroup object is beingused by Data Warehouse Centerusers.

Explanation: The Data Warehouse Center useris trying to delete a security group that containsone or more Data Warehouse Center users.

User Response: Before deleting the securitygroup, remove the users from the security group.


DWC03165E The object-type object has a NULLpointer passed in on the copy()method.



DWC03168E The Agent Site cannot be deletedbecause it is being used by one ormore databases.

Explanation: You are trying to delete an agentsite that is in use by one or more targets, sources,or both.

User Response: Before deleting this agent site,change the databases that uses this agent site touse another agent site. In the Agent Sitenotebook, select the Resources tab, and removeall the databases from the Selected Database list.

DWC03169E The Attribute cannot be deletedbecause it is being used by one ormore Primary Keys.

Explanation: You are trying to delete a columnthat is part of the primary key definition for thetable.

User Response: Before deleting this column,remove it from the primary key definition for thetable. In the Table notebook, select the Primarytab, and remove the column from the definition.

DWC03170E The Attribute cannot be deletedbecause it is being used by one ormore Foreign Keys.

Explanation: You are trying to delete a columnthat is part of one or more foreign keydefinitions.

User Response: Before deleting this column,remove it from the foreign key definitions. Openthe Table notebook for the tables with the foreignkey definition. Select the Foreign tab, andremove the column from the definitions.

DWC03171E The Table/File cannot be deletedor renamed because it is beingused by one or more steps.

Explanation: You are trying to delete a table orfile that is specified for a Data Warehouse CenterProgram in use by a step.

User Response: Before deleting the table or file,remove it from the step. You can see a list ofsteps using the table by selecting the Usage tabon the Table Notebook.

DWC03301E A Resource attached to step -step-name - as a target Resourcedid not set the warehouse flag.



DWC03302E A resource that is attached to astep as a source resource doeshave the warehouse flag setindicating this is a warehouseresource.



DWC03303E A Resource is associated with aSecurity Group as both a sourceand target.




DWC03304E A Resource - resource-name - isassociated with a Security Groupas a source but the iswarehouseflag is set, indicating this is awarehouse.



DWC03305E A Resource - resource-name - isassociated with a Target Group asa target but the iswarehouse flagis NOT set, indicating this isNOT a warehouse.



DWC03306E A Resource - resource-name - isassociated with a Data WarehouseCenter program that is not a DB2stored procedure.



DWC03307E A Data Resource’s (table) file typeis not set correctly based on thedatabase type of the InformationResource it is associated with.



DWC03308E An Agent Site is being created orupdated with a blank name.



DWC03309E An Agent Site is being created orupdated with an invalid type.



DWC03310E An AIX Agent Site is beingcreated or updated with no userID specified.



DWC03311E The subdbType set for a resourceresource-name - is invalid for thedbType specified.



DWC03312E The target column being removedis associated with a step that is intest mode and is referencing thiscolumn.





DWC03466E The select parameter for thelistNext() method has not beeninitialized.



DWC03470E An invalid DB2columnbuffer listwas passed to the database object.



DWC03471E An invalid parameter pointer listwas passed to the database object.



DWC03477E A create or update was issuedwith the ’name’ field of thedatabase not initialized.



DWC03479E A create or update was issuedwith the ’dbType’ field of thedatabase - database-name - notinitialized.



DWC03480E A create or update was issuedwith the ’subdbType’ field of thedatabase - database - notinitialized.



DWC03483E The table being updated has oneor more steps associated with itthat are in production mode.Update was successful but thesteps may need to be modified.



DWC03484E The passed-in target databaseobject was not valid.



DWC03485E The table being created is missingthe ’IRName’ or ’name’ attributeinitialization.




DWC03486E The passed in table is not valid.



DWC03487E The database type must be a Localfiles or Remote files type to usethis method.



DWC03488E The password in the connectstring must be keyed in.



DWC03489E Database database-name cannot beremoved from agent siteagent-site-name because they arebeing used by one or more steps.

Explanation: You are trying to remove a sourceor target database from an Agent Site SelectedList and one or more steps use the database andthe agent site.

User Response: Before you can remove thedatabase from the agent site, you must removethe references to the database and agent site fromthe steps.

DWC03490E Target target name name exceedsmaximum length allowed fortable name for the target database.Maximum table name length isname-length.



DWC03491E Database subType not defined ininternal target table. Internalerror.



DWC03492E The parameter list for creating thenew KeyMap objects is empty.



DWC03493E The warehouse Primary Keycannot be deleted or changedbecause it is being used by one ormore warehouse Foreign Keys.

Explanation: You are trying to delete awarehouse primary key definition that is in useby one or more warehouse foreign keydefinitions.

User Response: Before deleting the warehouseprimary key definition, remove the reference tothis warehouse primary key in the warehouseforeign key definition.


DWC03501E User name cannot be removedfrom security group group-namebecause there are no othersecurity groups havingAdministrative Authority andhave this user in it.

Explanation: You are trying to remove thelogged on user, name, who has Administrativeprivileges, from a security group, but that userdoes not belong to any other security groupswith Administrative privileges. A logged-on userwho currently has Administrative privileges(through a security group) cannot lose thatauthority while logged on to the Data WarehouseCenter Desktop.

User Response: Before removing the logged-onuser from the security group, add the user toanother security group with Administrativeprivileges.

DWC03502E The current logged on DataWarehouse Center user cannot bedeleted.

Explanation: You are trying to delete alogged-on user, which cannot be deleted.

DWC03503E The Administration Privilegecannot be removed from SecurityGroup security-group-name becausethere are no other SecurityGroups having AdministrativeAuthority that have this user in it.



DWC03504E User ID user-ID cannot be createdbecause it contains a user ID thatis already assigned to an existinguser.

Explanation: Each user in the Data WarehouseCenter must have a unique user ID. Pleasechoose a unique user ID.

User Response: Choose a user ID that does notconflict with an existing user ID.

DWC03700E An invalid schedule type waspassed to calculate nextstepSchedule.



DWC03701E An invalid day-of-week waspassed to set-day-of-week instepSchedule.



DWC03702E An invalid day-of-month waspassed to set-day-of-month instepSchedule.



DWC03703E An invalid month-of-year waspassed to set-month-of-year instepSchedule.



DWC03704E An invalid schedule frequencywas passed to stepSchedule.




DWC03705E Invalid status for step for thisparticular operation.



DWC03706E A Data Warehouse Center internalerror occurred.



DWC03707E Step step-name is recursive witheither its children, parents, orcascades currently defined.



DWC03708E The step relationship to step aliasis not initialized.



DWC03709E The target database associatedwith this step alias’s step is notinitialized.



DWC03710E The step relationship toAttributeLink is not initialized.



DWC03711E The storage buffer for thelistNext() method has not beeninitialized.



DWC03712E The select parameter for thelistNext() method has not beeninitialized.



DWC03713E The target database is notinitialized in the step.



DWC03714E The input database list is notinitialized in the step.




DWC03716E The input parameters for thedeepCopy() method are not set.



DWC03717E The source step input parameteron the deepCopy() method hasnot been retrieved or created yet.



DWC03719E The object passed in is not atoken.



DWC03726E Step step-name cannot be promotedbecause it has a transient targetand it either has a schedule or acascade.



DWC03729E Step - step-name - has noassociated output database.



DWC03730E The step - step-name - has noAgent Site assigned.

Explanation: A Data Warehouse Center erroroccurred.

User Response: Please assign an Agent Site andre-promote.

DWC03735E Step step-name does not have atleast one column that is extractedfrom either a source table orliteral.

Explanation: You are trying to create a step.

User Response: Return to column mapping tabof the step notebook and add at least onecolumn.

DWC03737E Step name does not have at leastone column that is either pulledfrom a source table or a literal.

Explanation: You are trying to promote to Teststatus a step that specifies that the target table becreated by the Data Warehouse Center, but thetarget table does not have a column defined thatis either extracted from a source column or is aliteral.

User Response: You must add at least onecolumn to the target table that is either pulledfrom a source column or a literal.

DWC03743E The table table-name has nocolumns associated with it.

Explanation: This error can only occur if youare promoting to Test and the target table doesnot have any columns defined in the target tabledefinition.

User Response: Go to the Properties of theTarget Table notebook and make sure that youdefine the appropriate number of columns forthe target table. If the target table definition wascreated as a default target table by way of the


Step notebook, make sure that you have selectedcolumns from a source.

DWC03744E Step - A database has no inputattribute.



DWC03745E Step - A database has no outputattribute.



DWC03746E Step - A program function has noprogram name.



DWC03747E Step -step-name - A programfunction has no function name.



DWC03751E ’Max editions’ value for stepstep-name is set to 0.



DWC03754E An invalid map type wasencountered.



DWC03755E Step: step-name has a child stepnamed: step-name that is indevelopment.

Explanation: You are trying to promote to Teststatus a step that has one or more source (child)steps that are in Development status.

User Response: You must promote to Teststatus all the source (child) steps of the parentstep before the parent step can be promoted toTest status.

DWC03756E Step: step-name has a child stepnamed: step-name that is NOT inProduction state.

Explanation: You are trying to promote toProduction a step that has one or more source(child) steps that are still in Development or Teststatus.

User Response: You must promote toProduction status all the source (child) steps ofthe parent step before the parent step can bepromoted to Production status.

DWC03757E Step: step-name has a parent stepnamed: step-name that is in NOTin Development state.

Explanation: You are trying to demote toDevelopment status a step that has one or moretarget parent steps that are in Test or Productionstatus.

User Response: Before you can demote the stepto Development status, you must demote toDevelopment status any steps that use this stepas a source.


DWC03758E Can only change max editionsfield when a step hasdevelopment or test status.

Explanation: You are trying to change theedition number for a step. You cannot do thisbecause this step has production status.

User Response: Demote the step to test ordevelopment status. Then, change the stepedition.

DWC03759E Can only change atomic flag fieldwhen a step is in Developmentstate.



DWC03765E Step: step-name has a parent stepnamed: parent-step-name that is inProduction state.



DWC03766E Step: step-name cannot beactivated. It has no schedules,cascades, or no by requestcapability.



DWC03767E Step: name’s select statementrefers to a Data Warehouse Centertoken ’&cur_edtn.ddd.ttt’ where’ddd’ or ’ttt’ is invalid.

Explanation: You have specified a DataWarehouse Center Token &cur_edtn.ddd.ttt,where the values of ddd, the target databasename and ttt is the target table name, are notvalid. The Data Warehouse Center was unable tofind a step that has a target table name of ttt in awarehouse with a database name of ddd. The&cur_edtn.ddd.ttt token gets the current stepedition number for a step in the specifieddatabase with the specified target table.

User Response: Correct the value of ddd, ttt, orboth, to match a target table in a Data WarehouseCenter warehouse that is associated with a step.

DWC03768E Step: step-name’s select statementrefers to a Data Warehouse Centertoken ’&cur_edtn.ddd.ttt’ wherethere are no editions for the stepassociated with ’ddd.ttt’.

Explanation: You have specified a DataWarehouse Center Token &cur_edtn.ddd.ttt,where ddd is the target database name, and ttt isthe target table name. The step associated withthis target table in this target database does nothave any editions stored in the target table. The&cur_edtn.ddd.ttt token gets the current stepedition number for a step in the specifieddatabase with the specified target table.

User Response: Correct the value of ddd, ttt, orboth, to match a target table in a Data WarehouseCenter warehouse that is associated with a stepthat specifies one or more editions. Also, verifyon the Work in Progress window that the stephas run.

DWC03774E Cannot add new columns to stepstep-name because target Resourceis AS/400 V3.1 and does notsupport SQL ALTER command.

Explanation: A Data Warehouse Center erroroccurred.


User Response: Do not try to add columns aftera table has been created. Stop and create thetable again with the new columns.

DWC03775E The list of new ProgParms tocreate is empty.



DWC03776E Cannot delete the Data WarehouseCenter Program because it isbeing used by a step.

Explanation: You are trying to delete a DataWarehouse Center Program that is in use by oneor more steps.

User Response: Select the Usage Tab of theProgram notebook to determine what steps areusing this Data Warehouse Center Program.Before deleting this Data Warehouse CenterProgram, change any references to the DataWarehouse Center Program in the steps.

DWC03777E Cannot delete the Data WarehouseCenter Program because it isbeing used by one or more stepsas a Cascaded Data WarehouseCenter Program.

Explanation: You are trying to delete a DataWarehouse Center Program that one or moresteps uses as a conditional cascade program.

User Response: Select the Usage tab of theProgram notebook to determine what steps areusing this Data Warehouse Center Program.Before deleting this user - defined program,delete or change any references to the DataWarehouse Center Program in the steps byclicking Program in the Schedule page of thestep notebook.

DWC03778E Cannot delete a Data WarehouseCenter default Data WarehouseCenter Program Group.



DWC03779E Cannot delete the Data WarehouseCenter Program Group because itcontains one or more DataWarehouse Center Programs.



DWC03780E The Data Warehouse Center tokenselected in the Data WarehouseCenter Program parametercommand string is not a validone.



DWC03783E The Program Function -progfunc-name - associated object isnot set up.




DWC03784E The Program Type associated withthis Data Warehouse CenterProgram - prog-name - is not setup.



DWC03786E Step step-name-1 has a warehouseForeign Key that references aWarehouse Primary Keyassociated with step step-name-2that is NOT in Test or Productionstate.

Explanation: You are trying to promote a stepthat refers to a warehouse primary key that isassociated with a step that has developmentstatus. You must promote the step that isassociated with the warehouse primary key first.

User Response: Promote the step that isassociated with the warehouse primary key totest or production status. Then, you can promotethe step that has the warehouse foreign key thatrefers to the warehouse primary key.

DWC03787E Step step-name-1 has a warehousePrimary Key that references oneor more warehouse Foreign Keysassociated with step step-name-2that is NOT in DevelopmentState.

Explanation: You are trying to demote a childstep before you demote the parent step.

User Response: Demote the step that has thewarehouse foreign keys to development. Then,you can demote the step that has the warehouseprimary key.

DWC03788E The warehouse Primary Keydefined for step step-name cannotbe deleted or changed because itis being used by one or morewarehouse Foreign Keys.

Explanation: You cannot delete or change awarehouse primary key that is being referred toby one or more warehouse foreign keys.

User Response: Demote to development thesteps that have the warehouse foreign keys thatrefer to the warehouse primary key. Or, removethe warehouse foreign keys from these steps.Then, you can delete or change your warehouseprimary key.

DWC03791E Step step-name is using a DataWarehouse Center Program thathas a parameter containing blankdata in the Parameter Text field.This must be provided beforePromote.

Explanation: You cannot promote a step thatrefers to a program definition which containsundefined parameters.

User Response: Provide a definition for theundefined parameter. To do this, open theparameter list for your program and define anyparameters that have blank fields. If you want todefine the parameter for the program as it runswith a particular step, access the parameter listthrough the step notebook for the step. If youwant to define a parameter for the definition ofthe program, access the parameter list.

DWC03792E Each comparison value for IN andNOT IN must be enclosed insingle quotes. For example, entervalues abc and def as ’abc’, ’def’.Re-enter the correct values.

Explanation: The value you entered in theValues field is not valid for in or not inoperators. All string values entered for thefollowing comparison operators must beenclosed in single quotes:

v in


v not in

v like

v not like

v between

v not between

For more information on valid values, see theData Warehouse Center online help for ″Locate″.

User Response: Re-enter a valid string in theValues field.

DWC03793E Comparison values for IN andNOT IN cannot have non-blankcharacters in between the endingsingle quote of a value and thecomma separator. For example,enter values abc and def as ’abc’,’def’. Re-enter the correct values.

Explanation: The value you entered in theValues field is not valid for in or not inoperators. You cannot have non-blank charactersbetween the ending quote of a value and thecomma. This message applies to the followingcomparison operators:

v in

v not in

v between

v not between



DWC03794E Comparison values for IN andNOT IN cannot have non-blankcharacters in between the commaseparator and the beginningsingle quote of the next value. Forexample, enter values abc and defas ’abc’, ’def’. Re-enter the correctvalues.

Explanation: The value you entered in theValues field is not valid for in or not inoperators. You cannot have non-blank characters

in between the beginning single quote of a valueand the comma. For more information on validvalues, see the Data Warehouse Center onlinehelp for ″Locate″.


DWC03795E Comparison values IN and NOTIN require parameters, forexample, ’abc’, ’def’. Re-enter thecorrect values.

Explanation: The value you entered in theValues field is not valid for in or not inoperators. The value might not be enclosed inquotes or it is missing a closing single quote. Allstring values entered for the followingcomparison operators must be enclosed in singlequotes:

v in

v not in

v like

v not like

v between

v not between


User Response: You might need to enclose theValue in the Values field in quotes or you mightneed to add a closing single quote to the end ofthe value. See the Data Warehouse Center onlinehelp for the proper format of values that use theIN and NOT IN comparison operators.

DWC03796E A beginning single quote ismissing from the value in theValues field. Each comparisonvalue for BETWEEN and NOTBETWEEN must be enclosed insingle quotes. For example, entervalues abc and def as ’abc’, and’def’. Re-enter the correct values.

Explanation: The value you entered in theValues field is missing a beginning single quote.All string values entered for the following


operators must be enclosed in single quotes:

v in

v not in

v like

v not like

v between

v not between


User Response: Add a beginning single quoteto the value in the Values field.

DWC03797E An ending single quote is missingfrom the value in the Values field.Each comparison value forBETWEEN and NOT BETWEENmust be enclosed in single quotes.For example, enter values abc anddef as ’abc’, and ’def’. Re-enterthe correct values.

Explanation: The value you entered in theValues field is missing an ending single quote.All string values entered for the followingoperators must be enclosed in single quotes:

v in

v not in

v like

v not like

v between

v not between


User Response: Add an ending single quote tothe value in the Values field.

DWC03798E Comparison values for BETWEENand NOT BETWEEN cannot havenon-blank characters in betweenthe ending single quote of a valueand the AND separator. Forexample, enter values abc and defas ’abc’ and ’def’. Re-enter thecorrect values.

Explanation: The value you entered in theValues field is not valid for between or notbetween operators. You cannot have non-blankcharacters in between the ending quote of avalue and the and separator. For moreinformation on valid values, see the DataWarehouse Center online help for ″Locate″.


DWC03799E Comparison values for BETWEENand NOT BETWEEN cannot havenon-blank characters in betweenthe AND separator and thebeginning single quote of the nextvalue. For example, enter valuesabc and def as ’abc’ and ’def’.Re-enter the correct values.

Explanation: The value you entered in theValues field is not valid for between or notbetween operators. You cannot have non-blankcharacters in between the and separator and thebeginning quote of the next value. For moreinformation on valid values, see the DataWarehouse Center online help for ″Locate″.


DWC03800E Comparison values BETWEENand NOT BETWEEN cannot nothave non-blank characters afterthe last value. Delete extranon-blank characters that followthe ending quote for the lastvalue in the Values field.

Explanation: The value you entered in theValues field is not valid for between or notbetween operators. You cannot have non-blank


characters following the last value in the Valuesfield. For more information on valid values, seethe Data Warehouse Center online help for″Locate″.

User Response: Delete any non-blank charactersthat follow the ending quote for the last value inthe Values field.

DWC03801E Step is being created or updatedwithout a ’name’ specified. Mustspecify a unique name for a step.



DWC03802E Step step-name is being created orupdated with an invalid value forstepType.



DWC03803E Step is being created or updatedwith the atomicFlag setincorrectly. Step either has targetand source databases the same orshould set atomicFlag to FALSE.



DWC03804E Step step-name being created orupdated is not associated witheither a Warehouse or Subject.




DWC03805E Step step-name being created orupdated is associated with a targettable that is not in the step’sWarehouse.



DWC03806E Step step-name being created orupdated is associated with a targettable that is not in the step’sWarehouse.



DWC03807E Step step-name being created orupdated is associated with sourceresource but the source tables arenot associated with the step’ssource database.



DWC03808E Step step-name being created orupdated is associated with sourceresource but it has no sourcetables associated with it.




DWC03809E Step step-name being created orupdated is associated with asource table which is a targettable from another step but thatchild step is not in the child steprelationship.



DWC03810E Step step-name being created orupdated does not have an UpdateSecurity Group associated with it.



DWC03811E Data Warehouse Center programgrouping has no name on a createor update.



DWC03812E Data Warehouse Center programdefinition has no name on acreate or update.



DWC03813E Data Warehouse Center programdefinition has no program namespecified on a create or update.



DWC03814E Data Warehouse Center programdefinition definition-name is notassociated with a Program Group.



DWC03815E Data Warehouse Center programinstance instance-name is notassociated with a step.



DWC03816E Data Warehouse Center programinstance instance-name is notassociated with a programdefinition.



DWC03817E Data Warehouse Center programparameter is being created orupdated without a name.




DWC03818E Data Warehouse Center programparameter parameter-name isassociated with a ProgramFunction, Trigonometric Function,or Aggregate Function.



DWC03819E Data Warehouse Center programparameters associated with aProgram Function, TrigonometicFunction, or Aggregate Functioncalled function-name does not haveunique ordering.



DWC03820E Subject is being created orupdated without a specifiedname.



DWC03821E Step being demoted todevelopment has target table thatis being used by another step thatis in either test or productionstate.




DWC03826E stepSchedule - attribute mismatchduring equalize of two schedules.



DWC03827E stepSchedule - an invalid copy toitself was attempted.



DWC03828E stepSchedule - an invalid copyfrom itself was attempted.



DWC03829E stepSchedule - an invalid valuewas specified for set-minute.



DWC03830E stepSchedule - an invalid valuewas specified for set-second.




DWC03831E stepSchedule - an invalid valuewas specified for set-hour.



DWC03832E stepSchedule - an invalid valuewas specified for set-year.



DWC03834E The logged on user has not beeninitialized in the Data WarehouseCenter.



DWC03835E The subject cannot be deletedbecause it contains one or moreprocesses.

Explanation: You are trying to remove a subjectthat contains one or more processes. You need toremove the processes from the subject before youcan remove the subject.

User Response: Remove the processes from thesubject before you remove the subject.

DWC03836E The object has steps associatedwith it and cannot be removed.

Explanation: You are trying to remove aparticular object that still has steps associatedwith it. You must remove the associated stepsbefore you remove the object.

User Response: Remove the steps from the

object before you remove the object.

DWC03837E There are existing Steps that arein production that use this step asa source. Remove of target notdone.



DWC03838E There are existing steps in thisprocess that use this table as asource. The source table was notremoved.

Explanation: You are trying to remove a tablefrom a process but there are steps in the processthat are using this table as a source table. Youmust first remove the data links between thetable and the step(s) before removing the tablefrom the process.

User Response: Remove the data links betweenthe table and the step(s) before you remove thetable from the process.

DWC03839E There are existing steps in thisprocess that use this table as atarget. The target table was notremoved.

Explanation: You are trying to remove a tablefrom the process but one or more steps in theprocess are using this table as a target table.

User Response: Remove the data link betweenthis table and the step before you try to removethe table from the process.

DWC03840E The source or target table beingattached to this step is not one ofthe tables associated with thisprocess. The table was notattached.

Explanation: The source or target table that youare trying to attach to the step is not associatedwith this process.

User Response: The source or target table thatyou are trying to attach to the step is not


associated with this process.

DWC03846E The name of the step cannot bechanged because the step iscurrently running.

Explanation: You are trying to change the nameof a step that is in test or production mode andthat step is currently running.

User Response: Please change the name of thestep when the step is not running. You can usethe WIP to determine if the step is currentlyrunning.

DWC05001E A call to new failed. Memoryname: memory-name. Attemptedsize: attempted-size.

Explanation: An internal error occurred.Insufficient memory.

User Response: Close open windows orapplications to free up memory.

DWC05002E Invalid command line argumentsreceived.

Explanation: You are attempting to run a DataWarehouse Center program that has invalidcommand line arguments.

User Response: You entered an incorrectnumber of command line arguments for yourData Warehouse Center program. Re-enter thecommand.

DWC05003E An invalid log message type wasreceived.



DWC05004E The Log Server could not openthe Data Warehouse Centerlicense file file-name. Thewarehouse server could NOT bestarted.

Explanation: The Data Warehouse Centerlicense file is damaged or corrupt.

User Response: Reinstall Data WarehouseCenter.

DWC05005E The Log Server could not read theData Warehouse Center licensefile file-name. The Data WarehouseCenter server could NOT bestarted.

Explanation: The Data Warehouse Centerlicense file is damaged or corrupt.

User Response: Reinstall Data WarehouseCenter.

DWC05006E Your Data Warehouse Centerlicense file has expired. Thewarehouse server could NOT bestarted. Please contact your IBMsales representative.

Explanation: The Data Warehouse Centerlicense file expired.

User Response: Contact your IBM salesrepresentative.

DWC05007E Attention: Your Data WarehouseCenter license file will expire innumber-of days (the warehouseserver will be started). Pleasecontact your IBM salesrepresentative soon!

Explanation: Your Data Warehouse Centerlicense is about to expire.

User Response: Contact your IBM salesrepresentative.


DWC05008E The program cannot load thedb2licm.dll file.

Explanation: The db2licm.dll file cannot befound.

User Response: Make sure that db2licm.dll is inthe correct DB2 path (SQLLIB\BIN).

DWC05009E The entry point forLicRequestAccess cannot be foundin the db2licm.dll file.

Explanation: The db2licm.dll file may havebeen corrupted.

User Response: Make sure that the db2licm.dllfile is good.

DWC05010E The server, logger, or agentprogram cannot be started.

Explanation: The license has expired, or it doesnot have the authority to execute the command(agent), or the program has no license.

User Response: Check to make sure that thereis an appropriate license.

DWC06001E A Receive() or HaltReceive() wasattempted before callingInitializeReceive().


The secondary return code (if one exists) displaysan error number that is returned by youroperating system.


DWC06002E A call to new failed. Memoryname: name. Attempted size: size.




DWC06003E A Send() was attempted beforecalling InitializeSend().




DWC06004E The number of bytes specified inthe socket message is invalid.Expected receive count in bytes:count. Actual receive count inbytes: count.




DWC06005E The data buffer to be sent is toolong. Allowed length in bytes:length. Requested length in bytes:length.





DWC06100E Unable to initialize the TCP/IPenvironment.

Explanation: The Windows NT TCP/IP socketssoftware cannot initialize itself.


User Response: Make sure that TCP/IP is fullyinstalled and configured on this machine. If so,restart the machine and retry the operation.

DWC06101E The socket cleanup routine failed.

Explanation: The Windows NT TCP/IP socketssoftware cannot terminate itself.


User Response: Make sure that TCP/IP is fullyinstalled and configured on this machine. If so,restart the machine and retry the operation.

DWC06102E The call to the socket functionsocket() failed.



User Response: Make sure that TCP/IP is fullyinstalled and configured on this machine, andthe network is operational. If so, restart themachine and retry the operation.

DWC06103E The call to socket function bind()failed. Port#: port-number.

Explanation: One of the following errorsoccurred:

v A network subsystem failed.

v Either the port number that the DataWarehouse Center was trying to use is alreadyin use by something else or there are no morefree ports available.

v Too many TCP/IP connections already exist;there are not enough buffers available.


User Response: Verify that all local ports arenot in use. Make sure that TCP/IP is fullyinstalled and configured on this machine, andthe network is operational. If so, restart themachine and retry the operation.

DWC06104E The call to the socket functionlisten() failed. Instance count:count.




DWC06105E The call to the socket functionconnect() failed. Destination host:hostname. Destination port: port-ID.Retry count: count. Retry interval:interval.

Explanation: The Windows NT TCP/IP socketssoftware cannot connect to a partner process,failing with an error other thanECONNREFUSED.




DWC06106E Repeated calls to the socketfunction connect() failed. Themessage could not be sent.Destination host: hostname.Destination port: port-ID.Connections attempted: amount.This may mean that the partnerprocess is not loaded or is notlistening on the assumed port.

Explanation: Either the Data Warehouse Centercould not establish a TCP/IP connection to apartner process, an agent process terminatedabnormally, or your Data Warehouse Centerlicense has expired.


User Response: Ensure that the warehouseserver, logger, and remote agent daemon (ifapplicable) are running in NT Services. Or, ifyour Data Warehouse Center license has expired,contact your IBM Software Support.

DWC06107E The call to the socket functionaccept() failed.

Explanation: The TCP/IP sockets softwarecannot accept data from a partner process.



DWC06108E The call to the socket functionrecv() failed while attempting toreceive the message length bytes.Expected length in bytes: length.

Explanation: The TCP/IP sockets softwareaborted while receiving the first four bytes ofdata from a partner process.

The secondary return code (if one exists) displays

an error number that is returned by youroperating system.


DWC06109E The call to the socket functionrecv() failed while attempting toreceive the message data.Expected length in bytes: length.

Explanation: The TCP/IP sockets softwareaborted while receiving the message data from apartner process.



DWC06110E The call to the socket functionsend() failed. Destination host:hostname. Destination port: port-ID.Message length in bytes: length.

Explanation: The TCP/IP sockets softwareaborted while receiving the first four bytes ofdata from a partner process.



DWC06111E The call to the socket functionclosesocket() failed.

Explanation: The TCP/IP sockets softwarecannot close a socket connected to a partnerprocess.





DWC06112E The call to the socket functiongetsockname() failed. Port#:port-number.

Explanation: The TCP/IP sockets softwarecannot obtain the address of the current socket.



DWC06113E The call to the socket functiongethostbyname() failed.Hostname: hostname.

Explanation: The TCP/IP sockets softwarecannot retrieve the symbolic hostname. Verifythat the \etc\hosts file exists.



You may consider adding the target hostnamewith the domain name (if it is available) in your\etc\hosts file.

DWC06114E The call to the socket functiongethostname() failed.

Explanation: The TCP/IP sockets softwarecannot retrieve the symbolic hostname.




DWC06115E The call to the socket functiongetservbyname() failed. Servicename: service-name.

Explanation: The TCP/IP sockets softwarecannot retrieve the symbolic service name fromthe \etc\services file.


User Response: Verify that the etc\services fileexists. Make sure that TCP/IP is fully installedand configured on this machine, and the networkis operational. If so, restart the machine and retrythe operation.

DWC06116E The call to the socket functioninet_ntoa failed. Hostname:hostname.

Explanation: The TCP/IP sockets softwarecannot convert the 32 bit Internet address todotted decimal notation.



DWC06117E The warehouse server hostname onport# port-ID is not responding atthis time.

Explanation: The warehouse server hostname onport# port-id is not responding at this time.



User Response: Go to the Services applet on thecontrol panel and check the state of the DataWarehouse Center Server and the DataWarehouse Center Logger Services. Restart oneor both if necessary.

DWC06118E Your logon attempt to thewarehouse server failed.

Explanation: The Data Warehouse Center clientattempted to use all of the available local clientIP addresses to communicate to the warehouseserver. However, none of the local client IPaddresses were able to receive responses fromthe warehouse server.

User Response: Verify that your warehouseserver is active and that the TCP/IPcommunication between your local client and thewarehouse server is active.

DWC06119E The warehouse client failed toreceive a response from thewarehouse server.

User Response: Verify that the warehouseserver is active and that the TCP/IPcommunication between your local client andwarehouse server is active. Then close the DataWarehouse Center and logon again.

DWC06200E An unexpected communicationserror has occurred.

Explanation: Either TCP/IP is not configuredcorrectly or you specified the wrong server whenyou logged on.

User Response: Verify that TCP/IP isconfigured correctly. If TCP/IP is configuredcorrectly, ensure that the server you specifiedwhen you logged on is correct.

DWC07000E The warehouse server was unableto retrieve step step-name. Theerror occurred while processing ajob of type job-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the step.

User Response: Verify that the step definitionstill exists and the control database is stillaccessible from the warehouse server machine. Ifthe problem persists, record all details of thiserror message and contact IBM Software Supportwith the information.

DWC07001E The warehouse server was unableto update step step-name. The erroroccurred while processing a job oftype job-type.

Explanation: Data Warehouse Center wasunable to save in the control database changes toa step definition.

User Response: Verify that the step definitionstill exists and the control database is stillaccessible from the warehouse server machine. Ifthe problem persists, record all details of thiserror message and contact IBM Software Supportwith the information.

DWC07003E The warehouse server was unableto change the status of stepstep-name. The error occurredwhile processing a job of typejob-type.




DWC07005E The warehouse server was unableto construct the select statementfor step step-name. The erroroccurred while processing acommand of type command-type foredition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database theSQL defined for a step.

User Response: Check the secondary returncode (RC2) and take the recommended action.

DWC07006E The warehouse server was unableto construct the insert statementfor step step-name. The erroroccurred while processing acommand of type command-type foredition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to build the SQL to insertrows into the target table.


DWC07007E The warehouse server was unableto construct the delete statementfor step step-name. The erroroccurred while processing acommand of type command-type foredition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to build an SQL deletestatement.


DWC07008E The warehouse server was unableto construct the create statementfor step step-name. The erroroccurred while processing acommand of type command-type foredition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to build a CREATE TABLEstatement.


DWC07009E The warehouse server was unableto construct the drop statement forstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to build a DROP TABLEstatement.


DWC07010E The warehouse server was unableto retrieve the retry count for stepstep-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themaximum number of retry attempts for the step.


DWC07011E The warehouse server was unableto retrieve the retry interval forstep step-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database the


retry interval for the step.


DWC07012E The warehouse server was unableto list the child steps of stepstep-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thelist of child steps for the step.


DWC07013E The warehouse server was unableto list the concurrently-cascadedsteps of step step-name. The erroroccurred while processing a job oftype job-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thelist of steps that are cascaded by the given step.


DWC07014E The warehouse server was unableto list the cascaded steps of stepstep-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thelist of steps that are cascaded by the given step.


DWC07015E The warehouse server was unableto list the schedules of stepstep-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database theschedules for the step.


DWC07016E The warehouse server was unableto calculate the next scheduledpopulation of step step-name. Theerror occurred while processing ajob of type job-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to calculate the next date in a recurringschedule.


DWC07017E The warehouse server was unableto retrieve database database-name.The error occurred whileprocessing a job of type job-type.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the database.


DWC07018E The warehouse server was unableto retrieve the source database forstep step-name. The error occurredwhile during operation-typeprocessing for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the source database. The DataWarehouse Center attempted to retrieve the datawhile performing the specified type of operation.



DWC07019E The warehouse server was unableto retrieve the target database forstep step. The error occurredduring operation-type processingfor edition edition-number.

Explanation: The warehouse server was unableto retrieve the target database for step step-name.The error occurred while during operation-typeprocessing for edition edition-number.


DWC07020E The warehouse server was unableto retrieve the attribute mappinginformation for step step-name.The error occurred whileprocessing a command of typecommand-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to map the selected columnsof the SELECT statement for the source tables tothe columns of the INSERT statement for thetarget table.


DWC07021E The warehouse server was unableto retrieve an output attribute ofstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the columns of the INSERTstatement for the target table.


DWC07022E The warehouse server was unableto retrieve an input attribute ofstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the columns of the SELECTstatement for the source tables.


DWC07023E The warehouse server was unableto retrieve the agent site for stepstep-name. The error occurredwhile processing editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to connect to an agent site.


DWC07024E The warehouse server was unableto retrieve the agent site fordatabase database-name.

Explanation: Data Warehouse Center wasunable to retrieve from the control database theagent site metadata for the database.


DWC07025E The warehouse server was unableto retrieve the aggregationfunction for step step-name. Theerror occurred during operation-typeprocessing for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for a Data Warehouse Center Program.



DWC07026E The warehouse server was unableto retrieve the target database forstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the target database.


DWC07027E The warehouse server was unableto list the source databases forstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the target database.


DWC07028E The warehouse server was unableto retrieve the conditional cascadefunction for step step-name. Theerror occurred during job-typeprocessing for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for a conditional cascade program orpostprocessing program.


DWC07029E The warehouse server was unableto list the steps conditionallycascaded from step step-name. Theerror occurred while processing ajob of type job-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thelist of steps to which the given step conditionallycascades.


DWC07030E The warehouse server was unableto get the grant statements forstep step-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: The warehouse server was unableto retrieve from the control database the SQLGRANT statements for the step.


DWC07031E The warehouse server was unableto list the aliases for stepstep-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thelist of Data Warehouse Center-defined aliases forthe step.



DWC07032E The warehouse server was unableto get the create statement foralias alias-name of step step-name.The error occurred whileprocessing a command of typecommand-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to generate the SQL to createan alias for the step.


DWC07033E The warehouse server was unableto get the drop statement for aliasalias-name of step step-name. Theerror occurred while processing acommand of type command-type foredition edition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to generate the SQL to dropan alias for the step.


DWC07034E The warehouse server was unableto list the source columns for stepstep-name. The error occurredwhile processing a command oftype command-type for editionedition-number.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the attributes of the step.


DWC07035E The warehouse server was unableto retrieve user user-name. Theerror occurred in response to anauthentication request from clientclient-name.

Explanation: Data Warehouse Center wasunable to retrieve the specified user ID from thecontrol database.

User Response: Verify that the user IDprovided is correct and is still defined to theData Warehouse Center server.

DWC07036E The warehouse server was unableto retrieve the step from targetdatabase database-name. The erroroccurred while processing acommand of type command-type.

Explanation: Data Warehouse Center wasunable to retrieve from the control database astep associated with the target database.


DWC07037E The warehouse server was unableto retrieve the connect string foredition edition-number of stepstep-name. The error occurredwhile processing a command oftype command-type.

Explanation: Data Warehouse Center wasunable to retrieve from the control database theODBC connect string that must be used toconnect to the target database.


DWC07038E The warehouse server was unableto construct the alter statement forstep step-name. The error occurredwhile processing a command oftype command-type.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata required to build an SQL ALTER


TABLE statement for the step.


DWC07039E The warehouse server received aninvalid stepType, identifier, forstep step-name from the controldatabase.

Explanation: A Data Warehouse Center internalerror occurred or the control database containsinvalid metadata.


DWC07040E The warehouse server received aninvalid program type,program-type-identifier, for stepstep-name from the controldatabase.



DWC07041E The warehouse server could notgenerate a Data Warehouse CenterProgram command line for editionedition-number of step step-name.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thecommand-line parameters for a Data WarehouseCenter Program.


DWC07042E The warehouse server could notgenerate an SQL CALL statementfor edition edition-number of stepstep-name.

Explanation: Data Warehouse Center wasunable to retrieve from the control database the

metadata required to generate an SQL CALLstatement for a stored procedure.


DWC07043E The warehouse server could notretrieve the database data for astored procedure for editionedition-number of step step-name.

Explanation: The warehouse server could notretrieve the target database from the step.


DWC07044E The warehouse server was unableto list the fail-cascaded steps ofstep step-name. The error occurredwhile processing a job of typejob-type for edition edition-number.

Explanation: The warehouse server could notlist the fail-cascaded steps.


DWC07045E The warehouse server was unableto list the steps fail-triggered fromstep step-name. The error occurredwhile processing a job of typejob-type for edition edition-name.

Explanation: The warehouse server was unableto list the steps fail-triggered from step step-name.The error occurred while processing a job of typejob-type for edition edition-name.


DWC07046E The warehouse server could notretrieve the Data WarehouseCenter Program parameters datafor a stored procedure for editionedition-number of step step-name.

Explanation: Data Warehouse Center could notretrieve the data of the stored procedure’sparameter(s) from the control database.



DWC07047E The warehouse server was unableto update the configurationparameter of component namecomponent-name and value value.



DWC07048E The warehouse server was unableto retrieve the data resource IDfrom the control database.

Explanation: The warehouse server was unableto retrieve the data resource ID from the controldatabase.

User Response: Verify that a connection existsbetween the warehouse server and the controldatabase. If a connection still exists, record alldetails of this error message and contact IBMSoftware Support with the information.

DWC07049E The warehouse server was unableto retrieve the authority of theuser from the control database.

Explanation: The warehouse server was unableto retrieve the authority of the user from thecontrol database.

User Response: Verify that the user ID andpassword are correct. ( The user ID andpassword are case sensitive.) If the problempersists, record all the details of this errormessage and contact IBM Software Support withthe information.

DWC07050E The warehouse server was unableto create edition edition-number ofstep step-name.



DWC07051E The warehouse server was unableto schedule edition edition-numberof step step-name.

Explanation: The warehouse server was unableto update its control tables.

User Response: Verify that the warehouseserver still has connectivity to the controldatabase. If a connection still exists, record all thedetails of this error message and contact IBMSoftware Support with the information.

DWC07052E The warehouse server was unableto start the population of editionedition-number of step step-name.



DWC07053E The warehouse server was unableto complete the population ofedition edition-number of stepstep-name.



DWC07054E The warehouse server was unableto start the purge of editionedition-number of step step-name.


User Response: Verify that the warehouse


server still has connectivity to the controldatabase. If a connection still exists, record all thedetails of this error message and contact IBMSoftware Support with the information.

DWC07055E The warehouse server was unableto handle the failure of the purgeof edition edition-name of stepstep-name.



DWC07056E The warehouse server was unableto delete edition edition-number ofstep step-name.



DWC07057E The warehouse server was unableto delete the scheduled editions ofstep step-name.



DWC07058E The warehouse server was unableto delete the editions of stepstep-name.


User Response: Verify that the warehouseserver still has connectivity to the control

database. If a connection still exists, record all thedetails of this error message and contact IBMSoftware Support with the information.

DWC07059E The warehouse server was unableto retrieve edition edition-numberof step step-name. The erroroccurred during the processing ofa job of type job-type.

Explanation: The warehouse server was unableto query its control tables.


DWC07060E The warehouse server was unableto retrieve the oldest edition ofstep step-name. The error occurredduring the processing of a job oftype job-type.



DWC07061E The warehouse server was unableto retrieve the editions whichwere in progress when the serverwas last stopped.




DWC07062E The warehouse server hasdetected that editionedition-number of step step-name hasan invalid status for restart.



DWC07063E The warehouse server was unableto retrieve the editions which arescheduled to be populated.



DWC07064E The warehouse server was unableto update the edition with theedition number of its parent.



DWC07066E The warehouse server was shutdown before this edition finishedpopulating.

Explanation: Informational message. The stepedition did not finish populating before thewarehouse server was shut down; all changes tothe target table were rolled back. steps arepopulated in a single unit of work. If thewarehouse server shuts down while a step isrunning, all changes to the target table will berolled back.

User Response: Run the failed step again.

DWC07067E The warehouse server was shutdown before this edition finishedpurging.

Explanation: Informational message. The stepedition did not finish purging before the DataWarehouse Center server was shut down; allchanges to the target table were rolled back. Ifthe warehouse server shuts down while a step ispurging, all deleted rows will be restored in thetarget table.

User Response: Purge the step edition again.

DWC07068E The warehouse server was notrunning during the time periodthis edition was scheduled to run.

Explanation: This message is applicable only ifthe warehouse server is configured for manualrestart. This step was scheduled to run during atime period that the Data Warehouse Centerserver was shut down. You can avoid this errorby configuring the warehouse server forautomatic restart; then missed steps areautomatically restarted when the server isrestarted. Automatic restart, however, is notrecommended because it can start steps atundesirable times. Also, it can exhaust systemresources because all missed steps are startedconcurrently.

User Response: If you need to refresh this stepbefore the next scheduled time, manually restartor reschedule it.

Determine why the server was shut down at thetime this step edition was scheduled to run.

DWC07069E The warehouse server was shutdown before this edition finishedcancelling.

Explanation: The step edition did not finishcanceling before the warehouse server was shutdown.

User Response: Purge the step edition from theWork in Progress window.


DWC07070N The Data Warehouse Centerserver was unable to complete thepopulation of edition edition ofprocess process.

Explanation: The Data Warehouse Center servercould not complete the population because thedatabase could not be found.

User Response: Check that the Data WarehouseCenter server has connectivity to the database. Ifa connection exists, record all the details of thiserror message and contact your IBM servicerepresentative.

DWC07081N The Data Warehouse Centerserver was unable to list thecascaded processes of processprocess. The error occurred whileprocessing a job of type job-typefor edition edition.

Explanation: The Data Warehouse Center servercould not list the cascaded processes.

User Response: Check the secondary returncode RC2 and take the recommended action.

DWC07082N The Data Warehouse Centerserver was unable to list thefail-cascaded processes of processprocess. The error occurred whileprocessing a job of type job-typefor edition edition.

Explanation: The Data Warehouse Center servercould not list the fail-cascaded processes.


DWC07083N The Data Warehouse Centerserver was unable to list the rootsteps of step step. The erroroccurred while processing a job oftype job-type for edition edition.

Explanation: The Data Warehouse Center servercould not list the root steps.


DWC07100E The warehouse server was unableto connect to the control databasecontrol-database-name with user IDof user-ID.

Explanation: The warehouse server tried toconnect to the control database with an invaliduser ID. Either the user ID is no longerauthorized to access the control database, or aninvalid or misspelled user ID was providedduring initialization.

User Response: Verify that the user ID is stillan authorized user of the control database. Verifythat the spelling and case of the user ID iscorrect.

DWC07101E The warehouse server was unableto retrieve parameterparameter-name from the controldatabase.

Explanation: Data Warehouse Center wasunable to retrieve from the control database oneof its configuration parameters.


DWC07102E The warehouse server retrieved atimeout parameter parameter-namewith an invalid value oftimeout-value.

Explanation: The timeout value specified in theConfiguration notebook for the given parameteris not in the valid range of values.

User Response: Start the Data WarehouseCenter configuration applet. Change the timeoutvalue for the given parameter in theConfiguration notebook to a valid value.

DWC07103E The warehouse server was unableto retrieve the command-linearguments for its database agent.

Explanation: Data Warehouse Center wasunable to retrieve from the control database thecommand-line arguments used to start the DataWarehouse Center agent.



DWC07104E The warehouse server was unableto update configuration parameterparameter-name with valueparameter-value.

Explanation: Data Warehouse Center wasunable to update the given configurationparameter in the control database.


DWC07105E The warehouse server was unableto store value parameter-value intoconfiguration parameterparameter-name.

Explanation: Data Warehouse Center wasunable to store the given configuration parameterin the control database.


DWC07106E The warehouse server detectedthat its configured hostname(install-host-name) does not matchthe hostname of the node onwhich it is running(tcpip-host-name).

Explanation: The most common cause of thiserror is when the warehouse server machine ismoved to another physical location and given anew TCP/IP hostname.

User Response: Open the Data WarehouseCenter Configuration notebook, select the Servertab and change the value of the Server HostName field to match the TCP/IP DNS hostnameconfigured for the machine.

DWC07150E The warehouse server was unableto retrieve its TCP/IP hostname.

Explanation: The Data Warehouse Centercommunications subsystem detected an error.

User Response: Check the secondary return

code (RC2) and take the recommended action.

DWC07151E The warehouse server was unableto retrieve the TCP/IP portnumber for the agent daemon.



DWC07152E The warehouse server was unableto retrieve its TCP/IP portnumber. The service name of thewarehouse server istcpip-service-name.

Explanation: Using the Server Service Nameprovided to the Data Warehouse Center, theserver was unable to retrieve its port numberfrom the TCP/IP SERVICES file.

User Response: Open the Data WarehouseCenter properties notebook, select the Server tab,and record the value of the Server Service Namefield. Verify that this name has an a single entryin the TCP/IP SERVICES file. If there aremultiple entries for this name, delete any extraones. If the name is not in the SERVICES file,either add it manually or re-run the DataWarehouse Center initialization program. It isstrongly recommended that you use the defaultserver service name and port number that theData Warehouse Center automatically adds foryou at initialization time.

DWC07153E The warehouse server was unableto create a message queue toprocess a job of type job-type foredition edition-number of stepstep-name.




DWC07154E The warehouse server was unableto create its primary messagequeue.



DWC07155E The warehouse server was unableto destroy the message queueused to process a job of typejob-type for edition edition-numberof step step-name.



DWC07156E The warehouse server was unableto destroy its primary messagequeue.



DWC07157E The warehouse server was unableto monitor one of its agentprocesses.


User Response: The Data Warehouse Centercommunications subsystem detected an error.

DWC07158E The warehouse server was unableto successfully stop monitoringone of its agent processes.



DWC07159E The warehouse server was unableto format an agent message toprocess a command of typecommand-type for editionedition-number of step step-name.



DWC07160E The warehouse server was unableto format an agent message toprocess a command of typecommand-type for databasedatabase-name.



DWC07161E The warehouse server was unableto format a request to spawn anagent process on host host-name.



DWC07162E The warehouse server was unableto format a request to shut downan agent process.



DWC07163E The warehouse server was unableto format a request to shut downan agent process on hosthost-name.




DWC07164E The warehouse server was unableto format a request to kill anagent process on host host-name.



DWC07165E The warehouse server was unableto format a request to populateedition edition-number of stepstep-name.



DWC07166E The warehouse server was unableto format a request to purgeedition edition-number of stepstep-name.



DWC07167E The warehouse server was unableto format a request to populatecascaded step step-name.



DWC07168E The warehouse server was unableto format a job terminationnotification.



DWC07169E The warehouse server was unableto send an agent command of typecommand-type for editionedition-number of step step-name.



DWC07170E The warehouse server was unableto send a message to shut downan agent process.



DWC07171E The warehouse server was unableto send a notification of jobcompletion to a requester on portport-number of host host-name.



DWC07172E The warehouse server was unableto send a populate request foredition edition-number of stepstep-name to its main queue.




DWC07173E The warehouse server was unableto send a purge request foredition edition-number of stepstep-name to its main queue.



DWC07174E The warehouse server was unableto send a request to spawn anagent process on host host-name.

Explanation: The warehouse server could notcommunicate with the Data Warehouse Centeragent daemon on the given agent site. Thisproblem can occur if the agent daemon is notstarted or not responding, or if there is acommunications problem. The value of thesecondary return code (RC2) identifies the cause.

User Response: Verify that the warehouseserver machine has TCP/IP connectivity to theagent site, and that the Data Warehouse Centeragent daemon is up and running. If this does notcorrect the problem, stop and restart the DataWarehouse Center agent daemon. If the problemis still not resolved, look up the RC2 code andtake the recommended action.

DWC07175E The warehouse server was unableto send a request to shut down anagent process on host host-name.

Explanation: The warehouse server could notcommunicate with the Data Warehouse Centeragent daemon on the given agent site. Thisproblem can occur if the agent daemon is notstarted or not responding, or if there is acommunications problem. The value of thesecondary return code (RC2) identifies the cause.

User Response: Verify that the warehouseserver machine has TCP/IP connectivity to theagent site, and that the Data Warehouse Centeragent daemon is up and running. If this does notcorrect the problem, stop and restart the DataWarehouse Center agent daemon. If the problemis still not resolved, look up the RC2 code and

take the recommended action.

DWC07176E The warehouse server was unableto send a message to cascade astep from step step-name to itsmain queue.



DWC07177E The warehouse server was unableto send a notification of jobcompletion to its main queue.



DWC07178E The warehouse server was unableto send a request to kill an agentprocess on host host-name.



DWC07179E The warehouse serverencountered an unexpected errorwhile receiving a shutdownresponse from an agent process.



DWC07180E The warehouse serverencountered an unexpected errorwhile receiving a start responsefrom an agent process.




DWC07181E The warehouse serverencountered an unexpected errorwhile receiving a message.



DWC07182E The warehouse serverencountered an unexpected errorwhile receiving a message duringthe processing of a stepdependency tree.



DWC07183E The warehouse server tried tospawn an agent but did notreceive a validstartup-acknowledgment fromeither the agent or the daemon.


User Response: Try shutting down andrestarting the Data Warehouse Center agentdaemon. If the problem persists, record all detailsof this error message and contact IBM SoftwareSupport with the information.

DWC07184E The warehouse server received anunexpected message of typemessage-type and subtypemessage-sub-type.


User Response: This error can occur if thesending Data Warehouse Center component is ata different code level than the receiving DataWarehouse Center component. For example, the

messaging code in a Data Warehouse Centeragent at one level of maintenance may not becompatible with a Data Warehouse Center serverat a different level of maintenance. Record alldetails of this error message and contact IBMSoftware Support with the information.

DWC07185E The warehouse server received anunexpected message whileprocessing a command of typecommand-type for editionedition-number of step step-name.


User Response: This error can occur if thesending Data Warehouse Center component is ata different code level than the receiving DataWarehouse Center component. For example, themessaging code in a Data Warehouse Centeragent at one level of maintenance may not becompatible with a Data Warehouse Center serverat a different level of maintenance. Record alldetails of this error message and contact IBMSoftware Support with the information.

DWC07186E The warehouse server received anunexpected message whileprocessing a dependency tree fora job of type job-type for editionedition-number of step step-name.The message received was of typemessage-type and request typerequest-type.



DWC07187E The warehouse server received anunexpected message type ofmessage-type.


User Response: This error can occur if the


sending Data Warehouse Center component is ata different code level than the receiving DataWarehouse Center component. For example, themessaging code in a Data Warehouse Centeragent at one level of maintenance may not becompatible with a Data Warehouse Center serverat a different level of maintenance. Record alldetails of this error message and contact IBMSoftware Support with the information.

DWC07188E The warehouse server received anunsupported message type ofmessage-type.



DWC07189E The warehouse server timed outwhile waiting for a shutdownreply from an agent process.

Explanation: The agent process has already shutdown or is hung.

User Response: Verify that the agent processhas shut down on the agent site machine. If ithas, no further action is necessary. Otherwise, theagent process is hung; end the process or restartthe agent site machine. If this problem occursfrequently, contact IBM Software Support.

DWC07190E The warehouse serverencountered an unexpected errorwhile receiving a message duringthe processing of a command oftype command-type for editionedition-number of step step-name.



DWC07191E The warehouse server was unableto format a status changenotification message for editionedition-number of step step-name.



DWC07192E The warehouse server was unableto send a status changenotification message for editionedition-number of step step-name toa client listening on portport-number of host host-name.



DWC07193E The warehouse server was unableto format a cancel message foredition edition-number of stepstep-name.



DWC07194E The warehouse server was unableto send a cancel message foredition edition-number of stepstep-name.




DWC07195E The warehouse server was unableto determine the message type ofa message received whileprocessing a command of typecommand-type for editionedition-number of step step-name.



DWC07196E The warehouse server received anunexpected message with acommand type of command-typewhile starting an agent process.



DWC07197E The warehouse server was unableto format a row count message foredition edition-number of stepstep-name.



DWC07198E The warehouse server was unableto send a row count message foredition edition-number of stepstep-name.



DWC07199E The warehouse server was unableto receive the response to a rowcount query for editionedition-number of step step-name.



DWC07200E The warehouse server received aninvalid response to a row countquery for edition edition-number ofstep step-name.



DWC07201E The warehouse server was unableto create a message queue to useduring shutdown.



DWC07202E The warehouse server was unableto destroy the message queue itused during shutdown.



DWC07203E The warehouse server was unableto format the shutdown messageto send to the main messagequeue.


User Response: Check the secondary return


code (RC2) and take the recommended action.

DWC07204E The warehouse server unable tosend the shutdown message to themain message queue.



DWC07205E The warehouse server did notreceive a reply to the shutdownmessage sent to the main messagequeue.



DWC07206E The warehouse server was unableto retrieve its Internet Address.

Explanation: The warehouse server was unableto retrieve its Internet Address.

User Response: Contact the networkadministrator and make sure that the DataWarehouse Center hostname and the IP addressof the hostname are valid.

DWC07207E The warehouse server was unableto process this job because theuser does not have properauthority.

Explanation: The warehouse server was unableto process this job because the user does nothave proper authority.

User Response: Verify that the user has validauthority to perform the task. If the problempersists, record all the details of this errormessage and contact IBM Software Support withthe information.

DWC07220E The warehouse server was unableto start local agent processagent-executable-name.

Explanation: There is insufficient storage toexecute the agent process, or the executable forthe agent is missing, corrupted, or cannot beexecuted.

User Response: Verify that theagent-executable-name file is still in the BINsubdirectory of the IWH installation directory. Ifthe file is there, increase the amount of virtualstorage or run fewer agents concurrently. If theproblem persists, record all details of this errormessage and contact IBM Software Support withthe information.

DWC07221E A Data Warehouse Center agentprocess was unable to initialize.

Explanation: The agent process was started, butfailed during its initialization.


DWC07222E The Data Warehouse Center agentdaemon was unable to spawn aremote agent process.

Explanation: There is insufficient storage toexecute the agent process, or the executable forthe agent is missing, corrupted, or cannot beexecuted.

User Response: Verify that the agent executablefile is still in the BIN subdirectory of the IWHinstallation directory. If the file is there, increasethe amount of virtual storage or run feweragents concurrently. If the problem persists,record all details of this error message andcontact IBM Software Support with theinformation.

DWC07223E The warehouse server attemptedto shutdown an unknown agentprocess.




DWC07224E The Data Warehouse Center agentdaemon was unable to shut downa remote agent process.

Explanation: Data Warehouse Center attemptedto shut down an agent and failed. DataWarehouse Center then attempted to make theVW Daemon shut the agent down. The daemonwas also unable to shut down the agent.

User Response: If the agent was running as auser process, end the agent process manuallyusing whatever command is appropriate for theoperating system of the agent site. If the agentwas running as a system process, you mighthave to wait until the next time you restart thesystem to clean up the dead agent process. Youshould still be able to run other agents in themeantime.

DWC07225E The Data Warehouse Center agentdaemon was unable to terminate aremote agent process.

Explanation: Data Warehouse Center requestedthat the agent daemon forcibly terminate anagent with which the warehouse server was nolonger able to communicate. The attempt failed.The agent process is no longer responding tosystem commands or has already terminated.

User Response: If the agent was running as auser process, try to end the agent processmanually using whatever command isappropriate for the operating system of the agentsite. If the agent was running as a systemprocess, you will have to wait until the next timeyou restart the system to clean up the dead agentprocess. You should still be able to run otheragents in the meantime.

DWC07226E The warehouse server was unableto terminate a local agent process.

Explanation: The agent process has already shutdown or is hung.

User Response: Verify that the agent processhas terminated. If it has, no further action isnecessary. Otherwise, the agent process is hung;end the process or restart the agent site machine.

DWC07227E The previous error occurred whilethe warehouse server wasinitializing its agent dispatcher.


User Response: See the preceding errormessage in the log for the cause of the problem.

DWC07228E The previous error occurred whilethe warehouse server wasterminating its agent dispatcher.



DWC07229E The system page file is gettingfull. You should increase its sizeto handle the number of agentsyou are running.

Explanation: The amount of virtual storagedefined on your system is insufficient to startany more agent processes.

User Response: Increase the amount of virtualstorage or run fewer agents concurrently.

DWC07250E The warehouse server was unableto create a job for editionedition-number of step step-name inresponse to a message of typemessage-type.




DWC07251E The previous error occurred whilethe warehouse server wasprocessing a job of type job-typefor edition edition-number of stepstep-name.



DWC07252E The warehouse server was unableto start a thread to run a job oftype job-type for editionedition-number of step step-name.



DWC07253E The previous error occurred whilethe warehouse server wasbuilding a command list for a jobof type job-type for editionedition-number of step step-name.



DWC07254E The previous error occurred whilethe warehouse server wasbuilding a command list for a jobof type job-type for databasedatabase-name.



DWC07255E The previous error occurred whilethe warehouse server wasexecuting a command list for ajob of type job-type for editionedition-number of step step-name.



DWC07256E The previous error occurred whilethe warehouse server wasexecuting a command list for ajob of type job-type for databasedatabase-name.



DWC07257E The previous error occurred whilethe warehouse server wasverifying the currency of editionedition-number of step step-name toprocess a job of type job-type.



DWC07258E The previous error occurred whilethe warehouse server waspopulating a dependency tree fora job of type job-type for editionedition-number of step step-name.



DWC07259E The warehouse server attemptedto populate step dependencystep-name more than once in thesame execution tree.




DWC07260E The warehouse server attemptedto clean up step dependencystep-name more than once in thesame execution tree.



DWC07261E The warehouse server was unableto handle a completion messageduring the processing of theexecution tree for editionedition-number of step step-name.



DWC07262E The warehouse server was unableto handle a purge message duringthe processing of the executiontree for edition edition-number ofstep step-name.



DWC07263E The warehouse server was unableto set a row limit for thepopulation of editionedition-number of step step-namebecause the step type does notsupport row limits.

Explanation: Informational message. Row limitcannot be set in the current context.

DWC07264N The Data Warehouse Centerserver was unable to start a threadto run a job of type job-type foredition edition of process process.


User Response: Record all details of this errormessage and contact your IBM servicerepresentative.

DWC07300E The warehouse server does notsupport cancellation of jobs oftype job-type.

Explanation: Cancel is not possible at this time.

DWC07301E The job of type job-type for editionedition-number of step step-namewas not processed because thestep was not in production.

Explanation: You can perform this type ofoperation on a step only if it is in Productionstatus. This step is not in Production status.

DWC07302E The job of type job-type for editionedition-number of step step-namewas not processed because thestep was not persistent.

Explanation: You can perform this type ofoperation on a step only if it is not transient.This step is a transient step.

DWC07303E Step step-name was not promotedbecause it was not indevelopment status.

Explanation: You can promote a step to Teststatus only if it is in Development status. Thisstep is not in Development status.

User Response: If the step status isDevelopment on the interface window, refreshthe view. If the status does not update to a statusother than Development, record all details of thiserror message and contact IBM Software Supportwith the information.


DWC07304E Step step-name was not suspendedbecause it was not in productionstatus.

Explanation: You can demote a step to Teststatus only if it is in Production status. This stepis not in Production status.

User Response: If the step status is Productionstatus on the interface window, refresh the view.If the status does not update to a status otherthan Production, record all details of this errormessage and contact IBM Software Support withthe information.

DWC07305E Step step-name was not purgedbecause it was not in suspendedstatus.

Explanation: Demoting a step to Developmentstatus drops the step’s target table. You candemote a step to Development status only if it isin Test status. This step is not in Test status.

User Response: If the step appears to be in Teststatus on the interface window, refresh the view.If the status does not update to something otherthan Test status, record all details of this errormessage and contact IBM Software Support withthe information.

DWC07307E Edition edition-number of stepstep-name was not purged becauseit had not been populated orfailed population.

Explanation: You cannot purge an edition inthis status.

User Response: Wait until this edition hasfinished processing before attempting to purge it.If this error occurred on an edition that hasfinished processing, this is an internal error;record all details of this error message andcontact IBM Software Support with theinformation.

DWC07308E Edition edition-number of stepstep-name was not replacedbecause it had not been populatedor failed population.

Explanation: You cannot replace an edition inthis status.

User Response: Wait until this edition hasfinished processing before attempting to replaceit. If this error occurred on an edition that hasfinished processing, this is an internal error;record all details of this error message andcontact IBM Software Support with theinformation.

DWC07309E Edition edition-number of stepstep-name was not populatedbecause it had already started orfinished population.



DWC07310E Edition edition-number of stepstep-name was not replacedbecause it had not been populatedor failed population.



DWC07311E The warehouse server did notimport column data for databasedatabase-name. The command wasnot processed because no tablenames were specified.




DWC07312E The warehouse server did notprocess the request to process ajob of type job-type for editionedition-number of step step-namebecause it is already processing anidentical request.

Explanation: Data Warehouse Center could notperform the requested operation because it isalready performing it. This error could occur if auser at another Data Warehouse Centeradministrative client made the request beforeyour administrative client was updated with thenew status.

User Response: Wait awhile and try again.

DWC07313E The warehouse server could notstart a job of type job-type for thecurrent edition of step step-namebecause it is running a job of typejob-type for edition edition-numberof step step-name. The two jobscannot be run at the same time.

Explanation: Data Warehouse Center could notperform the requested operation because itwould interfere with another operation that isalready in progress.

User Response: Wait awhile and try again.

DWC07314E The warehouse server is alreadyin the process of terminating. Itwill shut down after thecompletion of all jobs that arecurrently processing.

Explanation: The warehouse server alreadyreceived a shut down request.

DWC07315E The current row count for editionedition-number of step step-namecannot be determined because theedition is no longer populating.

Explanation: Informational message. The agenthas already completed populating the givenedition and terminated. The final row count cannow only be obtained from the statistics window.

DWC07316E Catalog information cannot beimported from databasedatabase-name because the databasetype does not support suchqueries.

Explanation: The type of database from whichyou are trying to import metadata has no facilityfor querying metadata.

User Response: Consult the source vendor’sdocumentation for more information. Enter thedatabase description manually.

DWC07317E The schedules of step step-namecould not be activated because thestep was not in test state.



DWC07318E The warehouse server could notadd a row in the statistics tablefor step step-name.

Explanation: The statistics table could not beupdated.


DWC07319E The warehouse server could notre-grant authority for stepstep-name because the step was notin test state.




DWC07320E The warehouse server could notadd an alias for step step-namebecause the step was indevelopment state.



DWC07321E The warehouse server could notremove an alias of step step-namebecause the step was not indevelopment mode.



DWC07322E The warehouse server was unableto authenticate the passwordprovided for user user-name. Theerror occurred in response to anauthentication request from clientclient-name.

Explanation: The password provided wasincorrect. A common cause of this error is adifference in the case of one or more of thecharacters; passwords are case sensitive.

User Response: Re-enter the password.

DWC07323E The table for step step-name wasnot altered because step-name isnot in test status.

Explanation: You can add new columns to anexisting step table only if the step is in Teststatus.

User Response: Change the step status to Testand try the operation again.

DWC07324E The warehouse server could notsample data for database or tabletable-name because the ID stringwas not found.

Explanation: You were trying to sample datafrom a Data Warehouse Center table that was notfound in the Data Warehouse Center controldatabase.

User Response: Contact the Data WarehouseCenter support.

DWC07325E The warehouse server could notinstall transformers from thedatabase because the creation typeis not supported.

Explanation:


DWC07350E The previous error occurred whilethe warehouse server wasacquiring an agent to process acommand list of typecommand-list-type for editionedition-number of step step-name.

Explanation: The warehouse server was unableto start the agent process.


DWC07351E The previous error occurred whilethe warehouse server wasreleasing the agent used toprocess a command list of typejob-type for edition edition-numberof step step-name.

Explanation: An error occurred while DataWarehouse Center was shutting down an agentprocess.



DWC07352E The previous error occurred whilethe warehouse server wasbuilding a command list of typejob-type for edition edition-numberof step step-name.

Explanation: Informational Message.

User Response: See the previous error messagefor more information.

DWC07353E The previous error occurred whilethe warehouse server wasbuilding a command list of typecommand-list-type for databasedatabase-name.


User Response: See the previous error messagefor more information.

DWC07354E Step step-name has no agent sitedefined on which it should beprocessed.



DWC07355E There is no agent site definedwhich has connectivity todatabase database-name.



DWC07356E An agent’s processing of acommand of type command-typefailed for edition edition-number ofstep step-name.

Explanation: The agent encountered an errorwhile it was processing.


DWC07357E A row count query failed foredition edition-number of stepstep-name.

Explanation: The Data Warehouse Center agentdetected an error while processing a row countquery.


DWC07358E Alias alias-name of step step-namewas not found. The error occurredwhile processing a command oftype command-type.

Explanation: Data Warehouse Center wasunable to retrieve from the control database themetadata for the given alias name.


DWC07400E The warehouse server was unableto acquire semaphoresemaphore-name.



DWC07401E The warehouse server was unableto release semaphoresemaphore-name.




DWC07450E The previous error occurred whilethe warehouse server wasinitializing its scheduler.

Explanation: An error occurred that preventedthe warehouse server from starting its scheduler.


DWC07451E The previous error occurred whilethe warehouse server wasterminating its scheduler.

Explanation: An error occurred that preventedthe warehouse server from stopping itsscheduler.


DWC07454E The warehouse server was unableto start a thread for its scheduler.



DWC07500I The warehouse server cancelededition edition-number of stepstep-name.


DWC07501E The warehouse server was unableto cancel edition edition-number ofstep step-name because that editionwas not being populated.

Explanation: The step edition could not becancelled because it was no longer running whenthe cancel request was received.

DWC07502I The warehouse server received aduplicate request to cancel editionedition-number of step step-namewhile the edition was alreadybeing canceled.

Explanation: Informational message. A requestto cancel an edition of the given step was madewhile an earlier cancel request on the sameedition was being processed. The edition will becancelled.

DWC07550E The warehouse server is out ofmemory.

Explanation: There is not enough virtualstorage available for the warehouse server tooperate. The warehouse server service will shutdown after issuing this message.

User Response: Increase the amount of virtualstorage on the machine on which the DataWarehouse Center server resides and restart theData Warehouse Center services.

DWC07551E The warehouse server isterminating due to an unhandledexception.

Explanation: The operating system isterminating the warehouse server because of aprogram exception that could not be resolved.

User Response: Gather as much information aspossible about the exception and the eventspreceding it, and report the problem to IBMSoftware Support. Try to restart the warehouseserver.

DWC07552E The warehouse server isterminating unexpectedly.

Explanation: The warehouse server experienceda serious internal error and is shutting down.

User Response: Gather as much information aspossible about the exception and the eventspreceding it, and report the problem to IBMSoftware Support. Try to restart the warehouseserver.


DWC07700I The warehouse server received awarning from Agent.



DWC07900E Edition edition-number was notfound.



DWC07901E Edition edition-number of stepstep-name could not be marked ascompleted because the specifiedstatus of edition-status was notvalid.



DWC07902E Step step-name was not currentbecause edition edition-number wasscheduled to be populated attimestamp, but population had notyet begun.

Explanation: The failed step was dependent onthe data from another step. The failed step couldnot be populated because the other step wasrunning behind schedule at the time the failedstep was started.

User Response: Use the Run Now function ofthe Work in Progress window to force populationof the other step, then try running the dependentstep again.

DWC07903E Step step-name was not currentbecause edition edition-number wascurrently populating.

Explanation: The failed step was dependent onthe data from another step. The failed step couldnot be populated because the other step had notfinished processing at the time the failed stepwas started.

User Response: Wait for the other step to finishprocessing and try running the failed dependentstep again.

DWC07904E Step step-name was not currentbecause edition edition-number wascurrently waiting to be retried.

Explanation: The failed step was dependent onthe data from another step. It could not bepopulated because the other step was in themiddle of a retry attempt at the time the failedstep tried to run.

User Response: Wait for the other step to finishprocessing and try running the failed dependentstep again.

DWC07905E Step step-name was not currentbecause edition edition-number wascurrently being purged.

Explanation: The failed step was dependent onthe data from another step. It could not bepopulated because the other step was purging atthe time the failed step tried to run.

User Response: Wait for the other step to finishpurging and try running the failed dependentstep again.

DWC07906E Step step-name was not currentbecause edition edition-number wasthe last edition to be populatedand it was unsuccessful.

Explanation: The failed step was dependent onthe data from another step. It could not bepopulated because the other step failed its lastpopulation attempt.

User Response: Re-run the other step and try


running the failed dependent step again.

DWC07907E Step step-name was not currentbecause no edition had beensuccessfully populated.

Explanation: The failed step was dependent onthe data from another step. It could not bepopulated because the other step has no editionsthat successfully completed processing.

User Response: Run the other step and tryrunning the failed dependent step again.

DWC08000E The operation you attempted isnot currently supported by thisagent.

Explanation: The Data Warehouse Centerfeature you attempted to use is not currentlysupported on this agent site platform.

User Response: Do not attempt to use this DataWarehouse Center feature on the current agentsite. Check with Data Warehouse Center servicefor availability and alternatives.

DWC08005I The Data Warehouse Center agentis about to shut down.

Explanation: Informational message. The agentexecuted a shutdown command issued by theserver.

DWC08010E The agent message overflowedand it was truncated frominitial-count items to final-countitems in the returned cataloglisting.

Explanation: A Data Warehouse Center internalerror occurred. A possible cause is that the list oftables returned is too large.

User Response: Use a table qualifier to reducethe number of tables returned. If this is notsuccessful, then record all details of this errormessage and contact IBM Software Support withthe information.

DWC08205E The agent received too few inputparameters. The server port andhostname must be supplied.



DWC08206E The agent received too manyinput parameters.



DWC08207E The agent received invalid editiontype.



DWC08210E The agent received invalid inputparameters: parameter-name.



DWC08215E The agent commands are out ofsequence.




DWC08220E The agent daemon received aninvalid command.



DWC08221E The agent daemon cannotcommunicate through assignedport.


User Response: Verify that the port numbersrequired by the server, logger, and agent are notin use by other tools.

DWC08225E The system is running low onmemory. The page file hasreached the limit. No more agentscan be spawned.

Explanation: The Data Warehouse Center agentdaemon was unable to start an agent processbecause the system is running out of virtualstorage.

User Response: Increase the amount of virtualstorage on the agent site machine, shut downsome applications on that machine, or run feweragents concurrently.

DWC08405E The input command line was toolong. The command was: command.

Explanation: The file processing commandpassed to the agent was too long.

User Response: Shorten the command ifpossible. If this does not correct the problem,contact IBM Software Support with theinformation.

DWC08410E The agent was unable to execute aData Warehouse Center Program.

Explanation: If a secondary return code (RC2)was returned, then the agent ran, but failedduring execution. The value of RC2 is the return

code returned by the Data Warehouse CenterProgram.

If RC2 = 1 for an NT agent, this may indicatethat the fully qualified program name on theProgram page of the Program notebook isincorrect, or that the program is not installed.

If RC2 = 127 for an AIX agent, this may indicatethat the fully qualified program name on theProgram page of the Program notebook isincorrect, the program is not installed, or theuser ID specified for this agent site does nothave execute authority and read authority. Bothauthority types are required.

If RC2 was not returned, then either the file forthe Data Warehouse Center Program was notfound or was not in a format that could beexecuted.

User Response: Check the value of RC2. If anon-zero return code was returned by the DataWarehouse Center Program, take therecommended action for that return code in theData Warehouse Center Program documentation.If the program is one of the IBM programsshipped with Data Warehouse Center, thedocumentation is in the Data Warehouse CenterProgram directory of the CD-ROM.

If the value of RC2 is null or zero, verify that thepath and filename supplied for the DataWarehouse Center Program are still valid. If theyare, verify that the Data Warehouse CenterProgram is still in a format that can be executed.

See Appendix B of the Managing ETI*ExtractConversion Programs with Visual Warehousemanual for more return code explanations.

DWC08411E The agent was unable to issue anFTP command.

Explanation: The agent could not establish anFTP connection to the host.

User Response: Verify that the hostname, userID, and password provided to FTP are correct.

If the hostname, user ID, and password arecorrect, do the following:


v Verify that ftp is the command used at yoursite to initiate an FTP session

v Confirm that the FTP daemon process isrunning on the host.

v Issue the ping command from the agent site tothe host to verify that a TCP/IP connectionexists.

DWC08412E The agent was unable to deletethe FTP file.

Explanation: The FTP operation failed. The filethat was retrieved by FTP is no longer on theagent site, or the file is in use by another process.

User Response: Verify that the file wasretrieved to the path specified in the databasedefinition and the file exists. If it exists,determine if it is being used by another process.

DWC08413E The file is not executable or hasan invalid executable file format.

Explanation: The Data Warehouse CenterProgram has a bad or invalid format and cannotbe run. Either the file referenced is not really anexecutable or it is a damaged executable.

User Response: Verify that the Data WarehouseCenter Program file exists and is executable.

DWC08414E The command interpreter isdamaged or missing.

Explanation: The operating system commandinterpreter or shell is damaged or missing.

User Response: Verify that the operating systemcommand interpreter or shell program is stillfunctioning on the agent site.

DWC08420E There is not enough memory,available memory has beencorrupted, or an invalid blockexists.

Explanation: There was insufficient virtualstorage available on the agent site machine forthe agent to spawn a process or allocate a databuffer.

User Response: Increase the amount of virtualstorage on the agent site machine, shut downsome applications on that machine, or run feweragents concurrently. Restarting the agent sitemachine might also free up memory.

DWC08425E The file to be processed wasread-only. The filename was:filename.

Explanation: Data Warehouse Center wasunable to delete or write to a file transferred byFTP because the agent had read-only authority tothe file.

User Response: Change the system settings toensure that files transferred by FTP are createdon the agent site machine with both read andwrite authority granted to the agent user ID.

DWC08430E The file or the path was notfound. The filename was: filename.

Explanation: Data Warehouse Center wasunable to delete or write to a file transferred byFTP because it could not be found. Anotherprocess or user might have moved or deleted thefile.

User Response: Run the step again, and ensurethat no other processes or users delete or movethe target file after it is created. The DataWarehouse Center will delete the file whenprocessing is complete.

DWC08440E Failed to update the IntersolvODBC Driver profile.

Explanation: The Data Warehouse Center agentcould not update or create the QETXT.INI fileused by the ODBC drivers, or a Data WarehouseCenter internal error occurred.

User Response: Verify that the agent has readand write authority for the directory where theQETXT.INI file is to be created which is either inthe system directory or the directory in whichthe source text file resides. If the agent does haveread and write authority for this directory, recordall details of this error message and contact IBMSoftware Support with the information.


DWC08445E The text file had an invalid datatype for field field-name. The SQLdata type data-type is notsupported.



DWC08450E Failed to load user DLL dll-name.

Explanation: Data Warehouse Center wasunable to load a dynamic link library (DLL) DataWarehouse Center Program into memory or wasunable to find the DLL.

User Response: The DLL is missing ordamaged, or its path is incorrect. Verify that theDLL file still exists, that it is still valid, and thateither the agent site’s library path includes thepath specified in the Data Warehouse CenterProgram definition or that a path to the DLL isincluded in the agent site’s library path.

DWC08455E Failed to find the address of userfunction function-name.

Explanation: Data Warehouse Center wasunable to find the specified function in thespecified DLL.

User Response: Verify that the name of a validDLL entry point was specified in the definitionof the Data Warehouse Center Program. SelectSettings > Data Warehouse Center Program inthe Data Warehouse Center Desktop.

DWC08457E Failed to execute user functionfunction-name.

Explanation: The OS/2 agent failed to executean invoked DLL.


DWC08460E FTP failed. Please check your userID, password and file name. Theymight be case sensitive,depending on the host.

Explanation: The FTP command failed totransfer the source file to the agent site machine.

User Response: Verify that the file you aretrying to transfer exists on the FTP servermachine and that the user ID and password yousupplied to the FTP command are correct.

DWC08461E An error occurred either whenopening a code page conversiontable or when converting databetween Unicode and local locale.

Explanation: Your request was sent to a remoteData Warehouse Center agent for execution, butthe remote agent could not open a code pageconversion table to convert your request messageto local locale.

User Response: Ensure that the operatingsystem where the agent resides has the properUnicode to local locale conversion table. To findout which local locale is used by the agent onUNIX, you may browse the IWH.environmentfile. If the local locale is incorrect, please edit theIWH.environment file and restart the agentdaemon.

If you received this error while running on a SunSolaris platform, you may define your localSolaris code-set string using the environmentvariable VWA_LOCALE_TABLE. Restart theagent daemon and try again.

DWC08462E An error occurred whileconverting an agent message fromwide characters to multibytecharacters.

Explanation: Your remote agent attempted tosend a response to your warehouse server, but itencountered an error while converting yourresponse message from wide character format tomultibyte character format.

User Response: If your agent is running on theUNIX platform, ensure that you have the correct


locale set in the IWH.environment file. If not,edit the IWH.environment file and restart thedaemon. Otherwise, contact technical support foryour operating system to verify if the correctmaintenance is applied to your operating system.

DWC08463E An error occurred whileconverting agent message frommultibyte characters to widecharacters.

Explanation: Your remote agent attempted toprocess your request message and encounteredan error while converting the message frommultibyte character format to wide characterformat.

User Response: If your agent is running on theUNIX platform, ensure that you have the correctlocale set in the IWH.environment file. If not,edit the IWH.environment file and restart thedaemon. Otherwise, contact technical support foryour operating system to verify if the correctmaintenance is applied to your operating system.

DWC8470N The file filename cannot beopened.

Explanation: An error occurred while openingthe file.

User Response: Check that the file exists, andthat your user id has authority to access it.

DWC08472E The Data Warehouse CenterTransformers could not beregistered in the target database.

Explanation: The Data Warehouse CenterTransformers could not be registered in the targetdatabase.

User Response: Refer to the Data WarehouseCenter secondary return code and the systemmessage for more information.

DWC08474E Data Warehouse CenterTransformers could not bedropped from the target database.

Explanation: Data Warehouse CenterTransformers could not be dropped from thetarget database.

User Response: Refer to the Data WarehouseCenter secondary return code and the systemmessage for more information.

DWC08505E The agent failed to allocate theODBC environment handle.

Explanation: The ODBC driver manager couldnot allocate storage for the environment handle.Either your system is low on memory, or there isa serious error in your ODBC driver manager.

User Response: Check the amount of virtualstorage on your machine. If there does notappear to be a shortage of virtual storage, tryreinstalling the ODBC driver manager.

DWC08476C The Web Connector user-definedprogram did not execute. IBMWarehouse Manager Connectorfor the Web is not installed or theinstallation failed.

Explanation:

User Response: You must install IBMWarehouse Manager Connector for the Web ifyou want to make use of this WarehouseManager feature. Contact your IBM servicerepresentative if the product is already installed.

DWC08478C An error occurred while loadingthe SAP Connector.

Explanation: SAP Connector is not installed orthe settings were changed after installation.

User Response: Check that the SAP Connectoris installed and the settings are correct.


DWC08480N The notification program failed toexecute successfully.

Explanation: The notification step failed andRC2 contains the return code. The return codesare listed below:

v 1 - One or more recipient(s) is invalid

v 2 - Cannot open the input file which containsthe parameters to the notification program

v 4 - Error calling WSAStartup()

v 6 - Error calling socket()

v 8 - Cannot get SMTP server

v 10 - Invalid host name

v 12 - SMTP service not available

v 14 - SMTP command call failed

v 16 - Internal error

v 18 - Error receiving SMTP command

v 20 - Cannot open trace file

v 22 - Error sending SMTP command

v 24 - Error calling connect()

v 26 - All of the recipients specified are invalid

v 28 - Environmental error such asVWS_LOGING variable not set

User Response: Check the trace filetrc-smtp*.log in the VWS_LOGGING directoryfor a more detailed description of the error. Forsocket related errors, make sure that TCP/IP isfully installed and configured on the machine,and the network is operational. For SMTP errors,make sure that the name you specified as theMail Server on the Notification panel is a SMTPserver. sometimes, it may help to stop and restartthe SMTP server.

DWC08510E The agent failed to allocate theODBC connection handle.

Explanation: The agent could not obtain anODBC connection handle. This can be caused byan error allocating storage, database error, oroperating system error.

User Response: Check the amount of virtualstorage on your machine. If there does notappear to be a shortage of virtual storage, checkthe SQLSTATE that accompanied this error

message (if a value was returned).

DWC08515E The agent failed to connect to theODBC data source: source-name.

Explanation: An attempt to connect to the givendatabase failed. There are numerous reasons theattempt could fail. The following reasons are themost common: the database was not cataloged asan ODBC system DSN (if the agent is onWindows NT), connectivity from the agent sitemachine to the given database failed or was notconfigured correctly, or the user ID or passwordspecified was not correct.

User Response: Ensure that the user ID andpassword provided are valid.

If the agent is running on Windows NT, verifythat the given database was cataloged as asystem DSN in the ODBC driver manager. If youare using CA/400 to access an AS/400 database,verify that you have installed the latest CA/400service pack and run cwbcfg.exe to enableCA/400 to run as a system task. For moreinformation about the service pack andcwbcfg.exe, see the web page athttp://www.as400.ibm.com/clientaccess/service.htm. Otherwise, consultyour database vendor’s documentation forpossible causes of a connection failure.

DWC08516E The agent failed to set connectoptions to the ODBC source:source-name.

Explanation: The Data Warehouse Center agentattempted to issue a SQLExecute() call to thedatabase and it received a non-zero return code.Check the event log to see if there are anyadditional SQL error messages.

User Response: If there is no additional SQLerror messages event log, turn on the DB2 traceor ODBC trace, whichever is applicable.

DWC08520E The agent failed to allocate theODBC statement handle.

Explanation: The Data Warehouse Center agentwas unable to obtain an ODBC statement handle.


This error can occur if the connection to thesource was not established or the ODBC drivermanager was unable to allocate memory for astatement handle.

User Response: Check the amount of virtualstorage on your machine. If there does notappear to be a shortage of virtual storage,determine if the database connection wasdropped. If you can consistently recreate theproblem, you can determine if the databaseconnection was dropped by looking at yourdatabase vendor’s trace facility.

Check that you have set the correct environmentsettings, such as the binary path or library path.

DWC08525E The agent failed at execution ofSQL statement statement.

Explanation: The SQL statement that the DataWarehouse Center agent attempted to executefailed.

User Response: Look at the setting for SQLError Processing in the step notebook for yourstep. Ensure that the setting is set to handleerrors in the way that you like. If you aresatisfied with this setting, look up the value ofthe SQL code or SQLSTATE in your databasevendor’s documentation to determine theappropriate course of action.

DWC08530E The agent failed to fetch from thesource database.

Explanation: The Data Warehouse Center agentencountered an error while fetching a row fromthe source result set.

User Response: Look up the value of the SQLcode or SQLSTATE in your database vendor’sdocumentation to determine the appropriatecourse of action.

DWC08535E The agent failed to insert into thetarget database.

Explanation: The Data Warehouse Center agentencountered an error while inserting data intothe target table.


If SQL code is 30081 and SQLSTATE is 40003,check the DB2 log to ensure it has enough logspace for inserting the data into the target table.

DWC08540E The agent failed to disconnectfrom the ODBC source:database-name.

Explanation: The Data Warehouse Center agentwas unable to disconnect from the givendatabase.


DWC08541E There is no connection to theODBC source.

Explanation: The Data Warehouse Center agentreceived a command to disconnect from adatabase, but the connection had already ended.

DWC08545E The agent failed to retrieve thetotal number of columns in theresult set.

Explanation: The Data Warehouse Center agentwas unable to obtain a count of the number ofcolumns in the result set.


DWC08546E The agent failed to retrieve acolumn attribute.

Explanation: The Data Warehouse Center agentwas unable to obtain metadata for a columnfrom the database management system.

User Response: Look up the value of the SQLcode or SQLSTATE in your database vendor’s


documentation to determine the appropriatecourse of action.

DWC08547E The agent failed to retrieve thetotal number of rows inserted intothe target database.

Explanation: The Data Warehouse Center agentwas unable to obtain the number of rowsinserted into the target table from the targetdatabase.


DWC08550E The agent failed at ODBCSQLDescribeCol API call.

Explanation: The Data Warehouse Center agentwas unable to obtain metadata for a column.


DWC08555E The agent failed to bind columnattributes to the selected columnsfrom the source database.

Explanation: The Data Warehouse Center agentwas unable to bind a buffer to hold the datafetched from one column of the result set.


DWC08560E The agent failed to bind columnattributes to the insert columns ofthe target database.

Explanation: The Data Warehouse Center agentwas unable to bind a buffer to hold data to beinserted into a column of the target table.

User Response: Look up the value of the SQLcode or SQLSTATE in your database vendor’s

documentation to determine the appropriatecourse of action.

If your step refers to a transformer, check to seeif the Data Warehouse Center stored proceduresare installed in the target database.

Check that the stored procedure name is enteredexactly as it was defined, since it is a casesensitive field.

DWC08565E The agent failed at preparation ofan SQL string for execution. Thestatement was: statement.

Explanation: The Data Warehouse Center agentcould not prepare a dynamic SQL statement.


DWC08570E The agent failed with an internalerror.



DWC08575E The agent failed at ODBCSQLExecute API call.

Explanation: The Data Warehouse Center agentreceived a non-zero return code when itattempted to issue a SQLExecute() call to thedatabase.

User Response: Check the event log to see ifthere are any additional SQL error messages. Ifnot, then turn on the DB2 trace or ODBC trace(whichever is applicable) and run the step again.

DWC08580E The agent failed to commit forODBC source: data-source-name.

Explanation: The Data Warehouse Center agentcould not commit the changes made to the givenODBC source.



DWC08585E The agent failed to roll back forODBC source: data-source-name.

Explanation: The Data Warehouse Center agentcould not roll back the actions changes made tothe given ODBC source.


DWC08590E The agent failed to release astatement handle.

Explanation: The Data Warehouse Center agentwas unable to free an ODBC statement handle.


DWC08600E The agent failed to retrievecatalog table information.

Explanation: The Data Warehouse Center agentwas unable to retrieve the metadata for therequested table.


DWC08605E The agent failed to retrievecatalog column information.

Explanation: The Data Warehouse Center agentwas unable to retrieve the metadata for therequested column.


DWC08610E No data was updated or inserted.

Explanation: No rows were returned when thestep ran. This error message will only bereturned if you have specified that an emptyresult set is an error.

DWC08615E The import table name is casesensitive. The name specified iseither incorrect or does not exist.Table name: table-name.

Explanation: The table or tables that you triedto import were not found. This error is usuallycaused by an invalid table name or qualifier(creator).

User Response: Check the spelling and the caseof the table name and qualifier (creator) yousupplied. On some platforms, these values arecase sensitive.

DWC08620E The SELECT statement hadselect-list-count columns while theINSERT had insert-list-countcolumns.

Explanation: The number of values to beinserted into the target table differs from thenumber of columns being selected from thesource table.

User Response: Verify that the target table hasthe same number of columns as the select listdefined in the Column Mapping page of the stepnotebook.

DWC08625E The column type used an invalidor unsupported SQL data type:unknown-data-type. Please checkyour resource and stepdefinitions.




DWC08630E An error was encountered whileexecuting a stored procedure.Refer to the secondary return codeand the <your-control-database-qualifier>.logTable in the targetwarehouse database for moredetails.

Explanation: Your transformer failed to execute.

User Response: Examine the detail messages inthe designated log table in your target databasefor the transformer and correct the problem. Ifthe problem cannot be determined by examiningthe designated log table in your target database,turn on the DB2 CLI trace and look for any DB2diagnostic messages.

DWC08635E A ″no data found″ error wasencountered while executing astored procedure.

Explanation: You requested to execute a storedprocedure or transformer, but the databasemanager did not find any data for the storedprocedure or transformer to execute.

User Response: To diagnose this problem, turnon DB2 CLI trace or ODBC trace (whichever isapplicable) and look for diagnostic messages.

DWC08700E The agent failed to cancel theODBC execution.

Explanation: The Data Warehouse Center agentwas unable to interrupt the processing of an SQLstatement.


DWC08710E It is too late to cancel this job. Nocancel is performed. The currentcommand being executed iscommand-name.

Explanation: Informational message. Aftercommitting changes, rolling back changes, ordisconnecting from a source or target, you cannot

cancel a step edition. The changes to the targettable have already been made.

DWC08715E The Data Warehouse Center agentcould not retrieve the primary keyinformation from the source.

Explanation: This error can be caused by anumber of different problems. Specifically, thereis either a communication link failure, a memoryallocation problem, an expired timeout, or aninternal problem, such as an invalid cursor stateor an invalid string or buffer length.

User Response: Determine the source of theerror. Verify that your communications link isconnected, that enough memory is allocated, andthat an expired timeout has not occurred.

If your communications link is connected,enough memory is allocated, and an expiredtimeout does not exist, an internal error hasoccurred. Run an agent trace and contacttechnical support.

DWC08720E The Data Warehouse Center agentcould not retrieve the foreign keyinformation from the source.

Explanation: This error can be caused by anumber of different problems. Specifically, thereis either a communication link failure, a memoryallocation problem, an expired timeout, or aninternal problem, such as an invalid cursor stateor an invalid string or buffer length.

User Response: Determine the source of theerror. Verify that your communications link isconnected, that enough memory is allocated, andthat an expired timeout has not occurred.

If your communications link is connected,enough memory is allocated, and an expiredtimeout does not exist, an internal error hasoccurred. Run an agent trace and contacttechnical support.


DWC08730E The Data Warehouse Center agentreceived an invalid step typeparameter on start up.


User Response: Run an agent trace and contacttechnical support.

DWC08770N Replication Apply program endedwith an error while processing thesubscription. Apply-Error

Explanation: Apply program ended with statuscode = -1 (error) when processing the Replicationsubscription.

User Response: Check the subscription in theApply status columns of theIBMSNAP_APPLYTRAIL table for moreinformation on the subscription error. Check thatthe subscription is setup correctly. To perform anApply trace, set Data Warehouse Agent trace = 4and restart the Replication step. The Apply traceis written to the file: applyqual.trc for thesubscription Apply qualifier.

DWC08771N An error occurred whileattempting to start the ReplicationApply program. Error-Type

Explanation: The Agent attempted to start theReplication Apply program. Apply failed beforeit began processing the subscription and writingto the IBMSNAP_APPLYTRAIL table.

User Response: Use the Apply command lineinvocation to check that the Apply program canbe started outside of Data Warehouse Center forthe target system. For a V8 Replication system,check that the Apply password file has beencreated using the password utility program.

DWC08772N An error occurred while creatingthe Replication Apply programpassword file.

Explanation: Agent was unable to create theApply program password file.

User Response: Check that new files can be

created on the Apply target system.

DWC08773N An SQL error occurred whilecreating the ReplicationSubscription.

Explanation: Agent received an SQL error whiletrying to insert the Replication subscription intothe Replication Control tables.

User Response: Check that Replication Controltables are installed on the target system. Checkthat a subscription does not already exist for theApply Qualifier in the Control tables for theSource Replication table.

DWC08774N An SQL error occurred whiledeleting the Replicationsubscription.

Explanation: Agent received an SQL error whileattempting to delete the Replication subscriptionfrom the Replication Control tables.

User Response: Check that Replication Controltables are installed on the target system.

DWC08775N An SQL error occurred whileupdating the Replicationsubscription.

Explanation: Agent received an SQL error whileattempting to update the Replication subscriptionin the Replication control tables.

User Response: Check that the subscription hasnot been deleted from the Replication Controltables.

DWC08776N An SQL error occurred whileimporting the Replication sourcetables.

Explanation: Agent received an SQL error whilereading the IBMSNAP_REGISTER table for thedefined Replication sources.

User Response: Check that Replication Controltables are installed on the target system.


DWC08777N An SQL error occurred whileimporting the Replication captureschemas.

Explanation: Agent received an SQL error whilereading the IBMSNAP_CAPSCHEMAS table forthe Replication capture schemas.

User Response: Check that the ReplicationControl tables are installed on the target system.

DWC08800E The operation you attempted isnot currently supported by thisagent.

Explanation: The feature you attempted to useis not supported by this release of the DataWarehouse Center agent for the agent site thatyou selected.

User Response: Avoid using the function or usean agent running on a different platform thatsupports the feature.

DWC08900N Connection to WebSphere SiteAnalyzer failed because of invalidconnection parameters.

Explanation: The user-defined program wasunable to connect to the WebSphere SiteAnalyzer server due to incorrect parametersettings.

User Response: Check that the connectionparameters (WebSphere Site Analyzer servername and port number) specified when thesource was created are correct.

DWC08901N WebSphere Site Analyzerauthentication failed.

Explanation: The connector program failed toauthenticate on the Site Analyzer server due toan incorrect user id and/or password.

User Response: Make sure that you haveentered the correct WebSphere Site Analyzer’suser id and password.

DWC08902N Unable to connect to WebSphereSite Analyzer HTTP server.

Explanation: The connector program was notable to establish a connection to the WebSphereApplication Server HTTP server.

User Response: Make sure the WebSphereAdministration Server is up and running. Checkthe network connectivity status.

DWC08903N WebSphere Site Analyzer HTTPserver returned error codeerrorcode.

Explanation: The connector program was notable to get a valid HTTP return code whenconnecting to the WebSphere Site Analyzer HTTPServer.

User Response: Check that all WebSphere SiteAnalyzer application servers are up and running.Refer to the HTTP return code documentation(RFC 2068) for return code explanations.

DWC08904I The polling step programexecuted successfully. The lasttimestamp for processing WebTracker data is timestamp.

Explanation:

User Response:

DWC08906I Web Connector user definedprogram executed successfully.There were no data importsselected as input to the step.

Explanation:

User Response: You may want to select a dataimport for polling as input for the Web TrafficPolling step.

DWC08907W WebSphere Site Analyzer dataimport data-import returnedwarning code SAcode.

Explanation: WebSphere Site Analyzer warningcode SAcode was returned as the polling status ofdata import data-import.


User Response: Refer to the WebSphere SiteAnalyzer documentation for more information.

DWC08908N The WebSphere Site Analyzerclickstream data assimilationprocess is not complete.

Explanation: WebSphere Site Analyzer is still inthe process of extracting the Web Traffic data tothe WebSphere Site Analyzer Webmart from thedata imports selected as input to the polling step.

User Response: The Web Traffic Polling stepfailed after retrying the number of timesspecified on the processing options tab of theWeb Traffic Polling step properties. The data inthe WebSphere Site Analyzer Webmart is not yetready for extraction by Warehouse Manager.

DWC08909N WebSphere Site Analyzer dataimport data-import returned errorcode SAcode.

Explanation: WebSphere Site Analyzer errorcode SAcode was returned as the polling status ofdata import data-import.


DWC08910N WebSphere Site Analyzerreturned informational codeSAcode. Execution of the WebConnector program was notsuccessful.

Explanation:


DWC08911N WebSphere Site Analyzerreturned warning code SAcode.Execution of the Web Connectorprogram was not successful.

Explanation:


DWC08912N WebSphere Site Analyzerreturned error code SAcode.

Explanation: A global Site Analyzer errormessage identified by SAcode was returnedduring execution of the Web Connector program.


DWC08913N Unable to retrieve valid data fromWebSphere Site Analyzer.

Explanation: The data returned fromWebSphere Site Analyzer was either corrupt orWebSphere Application Server indicated aprogram exception.

User Response: Check that all WebSphere SiteAnalyzer application servers are running.Consult your IBM service representative.

DWC08914N Project name does not exist inWebSphere Site Analyzer.

Explanation: The project name specified in DataWarehouse Center does not exist in WebSphereSite Analyzer.

User Response: Make sure that the projectname entered in the Data Warehouse Centermatches the name specified in Websphere SiteAnalyzer. Redefine the WebSphere Site Analyzersource or change the Data Warehouse Center’ssource properties. Site Analyzer Project namesare case sensitive.

DWC08915N One or more of the data importsyou selected does not exist on theWebSphere Site Analyzer server.

Explanation: There is a mismatch between thedata import definitions stored in Data WarehouseCenter and the data import definitions inWebSphere Site Analyzer.

User Response: Make sure the data imports youwould like to poll exist on WebSphere SiteAnalyzer. If you recreated the data imports inSite Analyzer it is necessary to redefine them inData Warehouse Center.


DWC08916C Internal error: Invalid connectionstring passed from agent to WebConnector program.

Explanation:


DWC08917C Internal error: Failed to accessinput file.

Explanation:


DWC08918C Internal error: Corrupted inputfile content.

Explanation:


DWC08919C Internal error: WebSphere SiteAnalyzer did not return any data.

Explanation: A WebSphere Site Analyzerrequest did not return any data. An internalserver error may have occurred.

User Response: Check that all WebSphere SiteAnalyzer application servers are up and running.Contact your IBM service representative for moreinformation.

DWC08920C Internal error: No WebSphere SiteAnalyzer Project name.

Explanation:

User Response: Please contact your IBMrepresentative.

DWC08921C Internal error: An unexpectederror occurred while running theWeb Connector program.

Explanation:


DWC08922C Internal error: Abnormaltermination of executing thread.

Explanation: The thread executing the WebTraffic polling step program was interruptedunexpectedly.

User Response: Contact your IBMrepresentative.

DWC08923C No IBM JSSE provider found. Theibmjsse.jar file cannot be accessedby the Web Connector program.

Explanation: The ibmjsse.jar file is not in yourCLASSPATH or the file has been moved from itsinstallation directory.

User Response: Check that the Web Connectorsettings in the agent environment file are active.

DWC08928C Internal error: Unable to retrievemessage for user-definedprogram.

Explanation:


DWC08929C Internal Error: Failed to accessoutput file.

Explanation:



DWC08930E An internal SAP extractor erroroccurred. Message category =category-name. Message code =code-id in function function-name.

User Response: Please refer to the messagecategory, message code and the SAP message.

DWC08931E Cannot connect to the SAP server.Message category = category-name.Message code = code-id. SAPmessage = message-id.

Explanation: The SAP server is down or therewas an authentication problem.

User Response: Please refer to the messagecategory, message code and the SAP message forfurther explanation.

DWC08932E An error occurred during theretrieval of the Business Objectslist. Message category =category-name. Message code =code-id. SAP message = message-id.


DWC08933E An error occurred during theretrieval of the Business Objectsdetails. Message category =category-name. Message code =code-id. SAP message = message-id.


DWC08934E An error occurred during theretrieval of SAP data. Messagecategory = category-name. Messagecode = code-id. SAP message =message-id.


DWC08935E An error occurred during thepopulation of the target table.Message category = category-name.Message code = code-id. SAPmessage = message-id.

User Response: Please refer to the messagecategory, message code and the related messagefor further explanation.

DWC08936W Skipped function-name due toinconsistent metadata found inthe Business Object details.Message category = category-name.Message code = code-id. SAPmessage = message-id.

Explanation: This business object will not beretrieved because of inconsistent metadata.


DWC08937I Connecting to the SAP Server.Message category = category-name.Message code = code-id. SAPmessage = message-id.

DWC08938I Retrieving Business Objects list.Message category = category-name.Message code = code-id. SAPmessage = message-id.

DWC08939I Retrieving Business Objectsdetails. Message category =category-name. Message code =code-id. SAP message = message-id.

DWC08940I Retrieving SAP data. Messagecategory = category-name. Messagecode = code-id. SAP message =message-id.

DWC08941I Populating the target table.Message category = category-name.Message code = code-id. SAPmessage = message-id.


DWC08951I WebSphere Site Analyzer dataimport data-import returnedinformational code SAcode.

Explanation: WebSphere Site Analyzer errorcode SAcode was returned as the polling status ofdata import data-import.


DWC09001E A Data Warehouse Center processtimed out waiting for anoperating system event to occur.



DWC09002E An error occurred creating a newprocess.

Explanation: When this message is thesecondary return code for message 7220, it caneither be caused by an invalid user ID orpassword supplied on the agent site definition,or when the agent executable, IWH2AGNT, ismissing or damaged.

User Response: Check the user ID andpassword supplied for the agent site definition. Ifthis information is correct, contact IBM SoftwareSupport for additional help.

DWC09003E An error occurred terminating anexisting process.



DWC09004E A process which was alreadyrunning was requested to start.



DWC09005E A process which was no longeractive was requested to terminate.



DWC09006E An error occurred creating a newthread.



DWC09007E An error occurred terminating anexisting thread.



DWC09008E An attempt was made to create athread which already existed.



DWC09009E An attempt was made to terminatea thread which no longer existed.





DWC09010E An error occurred while acquiringa mutual exclusion semaphore.



DWC09011E An attempt was made to acquire amutual exclusion semaphorewhich was already acquired.



DWC09012E An error occurred releasing amutual exclusion semaphore.



DWC09013E An attempt was made to release amutual exclusion semaphorewhich was already released.



DWC09014E An error occurred while creating amutual exclusion semaphore.




DWC09015E An attempt was made to acquireor release a mutual exclusionsemaphore which was not open.



DWC09016E An error occurred signaling anevent semaphore.



DWC09017E An error occurred while waitingfor an event semaphore.



DWC09018E An error occurred creating anevent semaphore.



DWC09019E An error occurred opening theData Warehouse Center .INI file(in the Registry).

Explanation: The Data Warehouse Centerportion of the NT Registry could not be accessed.

User Response: Make sure that the user ID and


password specified during initialization hasAdministration authority, and that entries exist inthe NT registry forHKEY_LOCAL_MACHINE/SOFTWARE/IBM/DataWarehouse Center.

DWC09020E Failed to obtain the securityaccount information for the userID specified with the agent siteuser ID.



DWC09021E Failed on event semaphore setsignal.



DWC09022E Failed on event semaphore resetsignal.



DWC09102E A Message Queue already exists.



DWC09103E Message Queue creation failed.This may indicate that anotherprocess is using the same portnumber.



DWC09104E Message Queue destroy failed.



DWC09105E VWERR_Q_LISTEN_TERMINATEDMessage queue instance count isinvalid.



DWC09106E VWERR_Q_LISTEN_TERMINATEDMessage queue listen terminatedabnormally.



DWC09107E VWERR_Q_MSG_INVALIDInvalid message received byqueue.





DWC09108E VWERR_Q_MSGTYPE_INVALIDInvalid message type received.



DWC09109E VWERR_Q_MSGSIZE_INVALIDInvalid message queue sizespecified.



DWC09110E VWERR_Q_MSGNUM_INVALIDInvalid message number passed tomessage queue.



DWC09111E VWERR_Q_NAME_INVALIDInvalid message queue namereceived.



DWC09112E Message Queue not created.




DWC09113E VWERR_Q_PURGE_FAILEDMessage queue purge failed.



DWC09114E VWERR_Q_RECEIVE_FAILEDMessage receive failed.



DWC09115E VWERR_Q_ACCEPT_FAILEDMessage queue accept failed.



DWC09116E VWERR_Q_SEND_FAILEDMessage queue send failed.



DWC09117E VWERR_Q_TIMEOUT Messagequeue timeout occurred beforemessage received.


User Response:


1. If importing table names, restrict the list tofewer tables. Some ways to do this are:

v Request tables but not views.

v Use a table qualifier.

v Request a table qualifier and table name.

2. Increase the agent start/stop timeout in theconfiguration.

3. If this is not successful, record all details ofthis error message and contact IBM SoftwareSupport with the information.

DWC09118E VWERR_Q_MSG_NUMBER_INVALIDInvalid message numberspecified.



DWC09119E VWERR_Q_UNSUPPORTED_CHARTYPEInvalid message queue charactertype (non-Unicode) specified.



DWC09120E VWERR_Q_NO_MESSAGE_ON_QNo message received on messagequeue.



DWC09121E The maximum number of clientsis already being polled. Maximumclient count: count.



DWC09122E The client name is invalid. Clientname: name.



DWC09123E No room in the poll client tablefor another client. Current clientcount: count.



DWC09124E Polling a partner process failed,indicating that the partner has lostconnectivity or died. Pingmessage: message. Loop count:count.



DWC09125E There are no dead client names toreturn.




DWC09141E VWERR_M_SET_FAILEDMessage attribute set methodfailed.



DWC09142E VWERR_M_GET_FAILEDMessage attribute get methodfailed.



DWC09143E VWERR_M_SET_DATA_INVALIDMessage attribute set methodcontains invalid data.



DWC09144E VWERR_M_NOT_READY_FOR_SENDMessage not ready for send.



DWC09145E VWERR_M_CORRUPTEDMessage contents corrupted.



DWC09146E VWERR_M_UNSUPPORTED_CHAR_TYPEMessage contents containunsupported (non-Unicode)character type.



DWC09147E VWERR_M_PACK_FAILEDMessage pack method failed.



DWC09148E VWERR_M_BUFFER_TOO_LARGEMessage pack buffer too large.



DWC09149E The Data Warehouse Center clientmessage code is a down-levelversion and cannot communicatewith the installed warehouseserver.

Explanation: The Data Warehouse Center clientmessage code is a down-level version and cannotcommunicate with the installed warehouseserver.

User Response: You must upgrade the clientcode to match the warehouse server level.

DWC09152E Win32 function FormatMessage()failed. Attempted lookup forreturn code: return-code.




DWC09153E Win32 function LoadLibrary()failed. Attempted to load file:file-name.



DWC09154E Win32 function RegCreateKeyEx()failed. Subkey: subkey.



DWC09155E Win32 function RegSetValueEx()failed. Value: value.



DWC09156E Win32 functionRegisterEventSource() failed.Event source name: source-name.



DWC09157E Win32 function ReportEvent()failed. Event code: code. Eventtype: type.



DWC09158E Data Warehouse Center wasunable to delete a key from theWindows NT registry. Key:key-name.



DWC09159E Win32 function RegOpenKeyExfailed. Key: key.



DWC09160E Win32 function RegQueryValueExfailed. Value: value.



DWC09161E Win32 functionGetEnvironmentVariable failed.Variable name: name.




DWC09162E The configuration variablevariable-name was not found in theconfiguration table.



DWC09163E The configuration variablevariable-name is not a numericalvariable.



DWC09164E The configuration variablevariable-name is not a characterstring variable.



DWC09171E The NT Service service-name couldnot be started.



DWC09172E Win32 function OpenSCManager()failed.



DWC09173E Win32 function CreateService()failed. Service name: service-name.Service label: service-label.



DWC09181E A call to new failed. Memoryname: name.



DWC09191E A call to _wfopen() failed. Filename: file-name.



DWC09192E A call to fwprintf() failed. Filename: file-name. String: string.



DWC09203E An invalid number of argumentswas received.




DWC09204E An invalid argument wasreceived.



DWC09205E The Create Database DB2Command failed for the controldatabase.



DWC10004E WSAEINTR The (blocking) callwas canceled viaWSACancelBlockingCall().



DWC10009E WSAEBADF



DWC10013E WSAEACCES The requestedaddress is a broadcast address,but the appropriate flag was notset.



DWC10014E WSAEFAULT The argument is notin a valid part of the user addressspace.



DWC10022E WSAEINVAL The socket has notbeen bound to an address withbind, or the listen function wasnot invoked before accept.



DWC10024E WSAEMFILE The queue is emptyupon entry to accept and there areno descriptors available.



DWC10035E WSAEMFILE No more filedescriptors are available.



DWC10036E WSAEINPROGRESS A blockingwindows sockets operation is inprogress.



DWC10037E WSAEALREADY Theasynchronous routine beingcanceled has already completed.



DWC10038E WSAENOTSOCK The descriptoris not a socket.



DWC10039E WSAEDESTADDRREQ Adestination address is required.




DWC10040E WSAEMSGSIZE The datagramwas too large to fit into thespecified buffer and wastruncated.



DWC10041E WSAEPROTOTYPE The specifiedprotocol is of wrong type for thissocket.



DWC10042E WSAENOPROTOOPT The optionis unknown or unsupported bythe socket type in your operatingsystem.



DWC10043E WSAEPROTONOSUPPORT Thespecified protocol is notsupported.



DWC10044E WSAESOCKTNOSUPPORT Thespecified socket type is notsupported in this address family.



DWC10045E WSAEOPNOTSUPP Thereferenced socket is not of a typethat supports connection-orientedservice.



DWC10046E WSAEPFNOSUPPORT



DWC10047E WSAEAFNOSUPPORT Thespecified address family is notsupported by this protocol.



DWC10048E WSAEADDRINUSE The specifiedaddress is already in use.



DWC10049E WSAEADDRNOTAVAIL Thespecified address is not availablefrom the local computer.



DWC10050E WSAENETDOWN The WindowsSockets implementation hasdetected that the networksubsystem has failed.



DWC10051E WSAENETUNREACH Thenetwork cannot be reached fromthis host at this time.




DWC10052E WSAENETRESET The connectionmust be reset because theWindows Sockets implementationdropped it.



DWC10053E WSAECONNABORTED Thevirtual circuit was aborted due totimeout or other failure.



DWC10054E WSAECONNRESET The virtualcircuit was reset by the remoteside.



DWC10055E WSAENOBUFS No buffer spaceis available.



DWC10056E WSAEISCONN The socket isalready connected.



DWC10057E WSAENOTCONN The socket isnot connected.



DWC10058E WSAESHUTDOWN The sockethas been shut down.



DWC10059E WSAETOOMANYREFS



DWC10060E WSAETIMEDOUT The attempt toconnect timed out withoutestablishing a connection.



DWC10061E WSAECONNREFUSED Theattempt to connect was forcefullyrejected.



DWC10062E WSAELOOP



DWC10063E WSAENAMETOOLONG



DWC10064E WSAEHOSTDOWN



DWC10065E WSAEHOSTUNREACH



DWC10066E WSAENOTEMPTY




DWC10067E WSAEPROCLIM



DWC10068E WSAEUSERS



DWC10069E WSAEDQUOT



DWC10070E WSAESTALE



DWC10071E WSAEMFILE



DWC10091E WSASYSNOTREADY Theunderlying network subsystem isnot ready for networkcommunication.



DWC10092E WSAVERNOTSUPPORTED Theversion of Windows Socketssupport requested is not providedby this particular WindowsSockets implementation.



DWC10093E WSANOTINITIALISED Asuccessful WSA startup mustoccur before using this function.



DWC11001E WSAHOST_NOT_FOUNDAuthoritative answer host notfound.



DWC11002E WSATRY_AGAINNon-authoritative host not found,or SERVERFAIL.



DWC11003E WSANO_RECOVERYNonrecoverable errors:FORMERR, REFUSED, NOTIMP.



DWC11004E WSANO_DATA Valid name, butno data record of requested type.



DWC12001I The warehouse server has beensuccessfully started.



DWC12002I The warehouse server has beensuccessfully stopped.




DWC12003I The Data Warehouse CenterLogger has been successfullystarted.



DWC12004I The Data Warehouse CenterLogger has been successfullystopped.



DWC13001E Import/Export failed to open thetag language file filename.

Explanation: The tag language file could not beopened for input (Import) or output (Export) dueto one of the following reasons:

v The tag language file is in use.

v The file name is invalid.

v Import only: The file name is not an existingfile name. Use Find to select an existing taglanguage file.

v Import only: One of the associated files wasnot in the same directory as the tag file.

User Response: If a tag language file is beingreplaced on Export, ensure that it does not havethe read-only attribute set. On Import, ensure allthe associated files with numbered extensions arein the same directory as the tag file.

DWC13002E The tag language file contains novalid tags to import.

Explanation: An empty tag language file wasdetected on Import, or the tag language file thatyou specified does not contain any usable tags toimport.

User Response: Verify that you have specifiedthe name of a file containing valid tag languagefor Data Warehouse Center objects.

DWC13003E Import cannot read the taglanguage file.

Explanation: An error occurred while Importread the tag language file.

User Response: Verify that the tag language filehas not been corrupted during Import. Then,verify that there is enough memory available onyour system.

DWC13004E Incomplete object definition orrelationship definition in the taglanguage file.

Explanation: Import detected an incompleteobject or relationship definition at the end of thetag language file.

User Response: Verify that the tag language fileis not corrupt by attempting to export andimport it. If you still receive this error, theremight be a problem with the program thatgenerated the file. If you used an externalprogram, contact the vendor that provides theprogram or tag language file.

DWC13101E Export failed to open the inputfile.

Explanation: The input file could not be openedon Export. The file is in use or the file name isinvalid.

User Response: If you are using the interface toexport the file, verify that the file is not inalready in use and that the file name is correct. Ifthe error still occurs, contact IBM SoftwareSupport.

DWC13102E The input file contains no usabledata for export.

Explanation: An empty input file was detectedduring export.

User Response: Attempt to export again. If themessage occurs repeatedly, contact IBM SoftwareSupport.


DWC13103E Export cannot read the input file.

Explanation: Error occurred while reading theinput file on Export.

User Response: Verify the input file has notbeen corrupted during Export. Then, verify thatthere is an adequate amount of memoryavailable on your system.

DWC13105E The object type specified in arelationship does not exist.

Explanation: An attempt was made to export arelationship to or from an unknown type ofobject.


DWC13106E An installation error has occurred.Export cannot open the file(s)containing object definitions.

Explanation: To perform an export, DataWarehouse Center must access the followingfiles:

v Flgnyvw0.ty1

v Flgnyvw1.ty1

These files are missing.

User Response: Re-install Data WarehouseCenter.

DWC13201E Import failed to open the log file.

Explanation: The log file could not be openedon Import due to one of the following reasons:

v The filename is not valid.

v The pathname is not valid.

v You do not have write access to the log path.

User Response: Verify that you have writeaccess to the log path specified and that there isan adequate amount of memory and storageavailable on your system. If the problem persists,contact IBM Software Support.

DWC13202E Syntax error -- one or more tagsare out of sequence. An OBJECTtag must follow anACTION.OBJINST tag.

Explanation: The tag language file you tried toimport contains an incomplete object definition.An OBJECT tag was not found after anACTION.OBJINST tag.

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again).

If the tag language file is corrupted, correct thetag language file and run import again. If youstill receive this error contact IBM SoftwareSupport (or the vendor who provided the taglanguage file).

DWC13203E Syntax error -- OBJECT tag. TheTYPE keyword could not befound.

Explanation: The tag language file you tried toimport contains an incomplete object definition.The TYPE keyword of an OBJECT tag could notbe found or the syntax of the tag is incorrect.

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again).

If the tag language file is corrupted, correct thetag language file and rerun Import. If you stillreceive this error contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13204W OBJECT tag -- the value for theTYPE keyword is not a valid type.

Explanation: Import did not recognize the valueof the TYPE keyword for an OBJECT tag. TheTYPE keyword should be identical to one of theOBJECT TYPE values defined at the top of a taglanguage file.

User Response: Correct the syntax error andrerun Import. Then, verify that the tag languagefile is not being corrupted. To do this, run importagain (or attempt to export and import again). If


the tag language file is corrupted, correct the taglanguage file and rerun Import. If you stillreceive this error, contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13205E Import must end because morememory is needed. You mightneed to close other windows orapplications.

Explanation: Import could not allocate thememory it needed to represent a Data WarehouseCenter object .

User Response: Increase the virtual memoryavailable to your system (paging file size), orclose other windows or applications that arerunning. If problem persists, contact IBMSoftware Support.

DWC13206E Syntax error -- one or more tags isout of sequence. An INSTANCEtag could not be found after anACTION.OBJINST tag.

Explanation: The tag language file you tried toimport contains an incomplete object definition.To identify the object instance being updated, anINSTANCE must follow an ACTION.OBJINSTtag .

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again).Ifthe tag language file is corrupted, correct the taglanguage file and run Import again. If you stillreceive this error contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13207E Syntax error -- one or more tag isout of sequence. A RELTYPE tagcould not be found after anACTION.RELATION tag.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. A RELTYPE tag could not be foundfor an object definition.

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM SoftwareSupport (or the vendor who provided the tagfile).

DWC13208E Syntax error -- RELTYPE tag. TheTYPE keyword could not befound.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. The TYPE keyword for a RELTYPEtag could not be found or the syntax is incorrect.

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again). Ifthe tag language file is corrupted, correct the taglanguage file and rerun Import. If you stillreceive this error contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13209E Syntax error -- RELTYPE tag. TheSOURCETYPE keyword could notbe found.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. The SOURCETYPE keyword for aRELTYPE tag could not be found.

User Response: Verify that the tag language fileis not being corrupted. To do this, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM SoftwareSupport (or the vendor who provided the taglanguage file).

DWC13210W RELTYPE tag -- the value for theSOURCETYPE keyword is not avalid type.

Explanation: The value of the SOURCETYPEkeyword for a RELTYPE tag is not valid. TheSOURCETYPE keyword for a RELTYPE tagshould be one of the OBJECT TYPE valuesdefined at the top of the tag language file.


User Response: Correct the tag language fileand run Import again. If the error persists, verifythat the tag language file is not being corrupted.To do this, attempt to export and import the fileagain. If the tag language file is corrupted,correct the file and run Import again. If you stillreceive this error, contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13211E Syntax error -- RELTYPE tag. TheTARGETYPE keyword could notbe found.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. The TARGETYPE keyword for aRELTYPE tag could not be found.

User Response: Correct the tag language fileand run Import again. If the error persists,attempt to export and import again to verify thatthe tag language file is not corrupted. If the taglanguage file is corrupted, correct the taglanguage file and run Import again. If you stillreceive this error, contact IBM Software Support(or the vendor who provided the tag languagefile).

DWC13212W RELTYPE tag -- the value for theTARGETYPE keyword is not avalid type.

Explanation: The TARGETYPE keyword for aRELTYPE tag should be one of the OBJECTTYPE values defined at the top of the taglanguage file.

User Response: Verify that the tag language fileis not being corrupted. To do this, attempt toexport and import again. If the tag language fileis corrupted, correct the tag language file andrun Import again. If you still receive this error,contact IBM Software Support (or the vendorwho provided the tag language file).

DWC13213E Syntax error -- one or more tag isout of sequence. An INSTANCEtag could not be found after anACTION.RELATION tag.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. An INSTANCE tag could not be foundfor a relationship definition.


DWC13214E Syntax error -- RELTYPE tag. TheSOURCEKEY keyword could notbe found.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. The value for the SOURCETYPEkeyword of a RELTYPE tag could not be found.


DWC13215E Syntax error -- RELTYPE tag. TheTARGETKEY keyword could notbe found.

Explanation: The tag language file you tried toimport contains an incomplete relationshipdefinition. The value for TARGETYPE keywordof a RELTYPE tag could not be found.



DWC13216E Syntax error -- an ACTION tagcould not be found.

Explanation: The tag language file you tried toimport contains an incomplete object orrelationship definition. An ACTION tag for anobject or relationship definition could not befound.

User Response: Verify that the tag language fileis not being corrupted. To do this, attempt toexport and import again. If the tag language fileis corrupted, correct the file and run Importagain. If you still receive this error, contact IBMSoftware Support (or the vendor who providedthe tag language file).

DWC13217E An invalid tag name tag-name wasencountered.

Explanation: An invalid tag was found in thetag language file.

User Response: Consult the Information CatalogManager Administration Guide for a list of validtags. Then, insert the correct tag into the taglanguage file. Next, attempt to export and importagain to verify that the tag language file is notcorrupted. If you still receive this error, contactIBM Software Support (or the vendor whoprovided the tag language file).

DWC13218E Syntax error -- ACTION tag.:ACTION. must be followedimmediately by an OBJTYPE,OBJINST or RELATION keyword.

Explanation: The tag language file you tried toimport contains invalid tag language. It containsan :ACTION. tag that does not contain one of thekeywords OBJTYPE, OBJINST, or RELATION.

User Response: Add the proper syntax to thetag language file. Then, to verify that the taglanguage file is not being corrupted, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM SoftwareSupport (or the vendor who provided the taglanguage file).

DWC13219E An internal error has occurred.

Explanation: An internal error has occurred inImport.



Explanation: An internal error has occurred inImport.


DWC13221E Syntax error -- a tag containsinvalid nesting of parentheses.

Explanation: The tag language file you tried toimport contains invalid tag language. An:INSTANCE tag contains an invalid nesting ofparentheses.

User Response:

1. Correct the syntax error in the taglanguage file. Then, to verify that thetag language file is not being corrupted,run import again (or attempt to exportand import again). If you still receivethis error, contact IBM Software Support(or the vendor who provided the taglanguage file).

2. Verify that the tag language file doesnot contain ( ) in metadata. If the filedoes contain ( ), they must be enclosedin single quotes.

DWC13222E Syntax error -- a closingparenthesis for a keyword valuecould not be found.

Explanation: The tag language file you tried toimport contains invalid tag language. A closingparenthesis for a tag keyword could not befound.

User Response: Correct the syntax error in thetag language file. Then, to verify that the taglanguage file is not being corrupted, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM Software


Support (or the vendor who provided the taglanguage file).


Explanation: An internal error was introducedinto the import program.

User Response: Look up any other errors thatare reported. If no other errors are reported,contact IBM Software Support.

DWC13224E A Data Warehouse Center objectreferenced in the SOURCEKEY orTARGETKEY keyword of arelationship definition does notexist.

Explanation: A Data Warehouse Center objectreferenced in the SOURCEKEY or TARGETKEYvalue of a relationship definition was not definedin the target control database when Importprocessed the relationship. An object referencedin a relationship definition must either bedefined in the tag language file before therelationship definition is defined or the objectmust already exist in the target database.

User Response: Correct the syntax in the taglanguage file. Then, to verify that the taglanguage file is not being corrupted, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM SoftwareSupport (or the vendor who provided the taglanguage file).


Explanation: Import was unable to allocate aData Warehouse Center object corresponding to atag object definition.

User Response: Increase the virtual memoryavailable to your system (paging file size). If youstill receive this error, contact IBM SoftwareSupport.

DWC13227E Data Warehouse Center does notallow a relationship betweenSOURCETYPE source-type-nameand TARGETYPE target-type-name.

Explanation: Data Warehouse Center does notallow a relationship between objects of thespecified SOURCETYPE and objects of thespecified TARGETYPE.

User Response: Correct the error in the taglanguage file. Then, to verify that the taglanguage file is not being corrupted, run importagain (or attempt to export and import again). Ifyou still receive this error, contact IBM SoftwareSupports or the vendor who provided the taglanguage file).




DWC13230E A Data Warehouse Center objectreferenced in the SOURCEKEY orTARGETKEY keyword of arelationship definition does notexist.

Explanation: A Data Warehouse Center objectreferenced in the SOURCEKEY or TARGETKEYvalue of a relationship definition was not definedin the tag language file before Import processedthe relationship. Object types must appear in thetag language file before a relationship whichrefers to them appears in the tag language file.Or, the object types must already exist in thetarget database. These object types are usuallyrelated to steps. For example, these object typesmight be step maps or step aliases.

User Response: Correct the tag language file.Then, to verify that the tag language file is notbeing corrupted, run import again (or attempt toexport and import again). If you still receive thiserror, contact IBM Software Support (or thevendor who provided the tag language file).





DWC13232E A database object does not existfor table object table-object-name.

Explanation: A table object was found in a taglanguage file before its corresponding databaseobject was found in the tag language file. Thedatabase is not defined in the target controldatabase. When a table object is processed, itsdatabase must either be defined in the taglanguage file before the table is defined, or itmust already exist in the target database.

User Response: Correct the tag language fileand run Import again. Then, verify that the taglanguage file is not being corrupted. To do this,run import again (or attempt to export andimport again). If you still receive this error,contact IBM Software Support (or the vendorwho provided the tag language file).

DWC13233E An INSTANCE short_namerequired by an object could notbe found.

Explanation: The tag language file you tried toimport contains invalid tag language. One of theINSTANCE keywords required by an objectcould not be found.


DWC13234E One of the first five lines of thetag language file must be aCOMMENT tag with versioninformation.

Explanation: The tag language file you tried toimport is invalid. One of the first five lines in thetag language file must be:COMMENT.SYSTEM(WindowsNT) or

:COMMENT.SYSTEM(OS/2).


DWC13235E The value for the PGMTYPEkeyword of an IWHPROGF,IWHAGGRF, or IWHTRIGFobject is not valid.

Explanation: The tag language file you tried toimport is invalid. The value for the PGMTYPEkeyword of an IWHPROGF, IWHAGGRF, orIWHTRIGF object is not a valid program type. Itmust be one of the following numbers, or theequivalent keyword: 0 = Dynamic Load Library,1 = Command Program, 2 = Executable, 4 = DB2Stored Procedure


DWC13236E Cannot create object object-namebecause its associated object doesnot exist.

Explanation: An object cannot be createdbecause its associated object is not found.Currently, associated objects are relevant for:

v IWHAGGRF and IWHTRIGF objects that needa IWHPROGF object

v IWHFKEY objects that need IWHPKEY objects

v IWHKYMAP objects that need a COLUMNobject



DWC13237E Cannot update step step-namebecause it is not in developmentstatus.

Explanation: Data Warehouse Center cannotimport a step which is already defined in thetarget control database and is not indevelopment status.

User Response: Demote the step todevelopment status and import again. If youcannot demote the step, you must use the stepnotebook to update it (rather than using import).

DWC13238W The object of type object-typeidentified by object-key is definedtwice in the tag language file.

Explanation: An object was defined more thanonce in the same tag language file. The secondinstance was saved.

User Response: If errors or problems are causedby the duplicate instance, remove one of the setsof OBJINST tags for the object from the taglanguage file and attempt to import the fileagain. If the tag language file was created by ametadata export utility, contact IBM SoftwareSupport or the vendor who provided the taglanguage file.

Consult the log file for additional information.

DWC13239E No object or relationshipdefinitions were processed fromthe tag language file.

User Response: Ensure the tag language filecontains at least one object or relationshipdefinition. If you specified a starting checkpointID, ensure there is at least one object orrelationship definition after that checkpoint ID,or after any checkpoint ID that is greater thanthe one specified.

DWC13300E Can not open or read from filefilename.

Explanation: An error occurred during theattempt to open or read the file filename.

User Response: Ensure the file name and pathname are correct.

DWC13301E Cannot create or write filefilename.

Explanation: An error occurred during theattempt to create or write to file filename.

User Response: Ensure the file name and pathname are correct.

DWC13302E A parsing error occurred in theDB2 Extender DAD file filename intoken token-name. Reason code:reason-code.

Explanation: An error in the token token-nameoccurred while parsing the DAD file filename fora table definition, as indicated by the followingreason codes:

1. XML syntax error in DAD file.

2. A table tag has no name attribute.

3. A column or node does not contain therequired values for Name and Type.

4. No <DAD> element found in DAD file.

5. No Xcollection element found in DAD file.

6. Incorrect number of column tags: only onecolumn tag allowed in RDB-node.

7. Incorrect number of table tags: one table mustbe in a RDB-node if a column tag exists in thisRDB-node.

User Response: Correct the syntax error in theDAD file.

DWC13304E A parsing error occurred in theTrillium DDL file filename neartoken token-name. Reason code:reason-code.

Explanation: An error occurred near the tokentoken-name while parsing the Trillium DDL filefilename for a table definition, as indicated by thefollowing reason codes:

1. The attribute for a field is already defined orno field is defined.


2. A record requires information about type andlength.

3. A field requires information about type,length and starts.

4. Length and starts require numeric values.

5. Unexpected end of file. No fields defined forthe record.

6. Only one record is allowed per file.

User Response: Correct the syntax error in theDDL file.

DWC13600I The export process is complete.See the log file log-file for details.

Explanation: The Data Warehouse Centeralways creates a log file to capture all of thedetails from the export process, whether theexport was successful or if it had errors.

User Response: View the log file to see theresults of your export process.

DWC13601I The metadata from the controldatabase control-database exportedsuccessfully.

Explanation: This is an informational messageto confirm that the metadata was exportedwithout errors.

User Response: No action is necessary.

DWC13602E The Data Warehouse Centerencountered errors whileexporting metadata metadata.

Explanation: The Data Warehouse Center wasunable to export the metadata that you selectedbecause of errors.

User Response: To see more information onthese errors, view the log file. Data WarehouseCenter always creates a log file to capture thedetails from the export process, whether theexport was successful or if it had errors. If youare unable to correct the errors, contact IBMSoftware Support for help.

DWC13603E The export utility was unable toopen the log file logfile-name.

Explanation: The Data Warehouse Centeralways attempts to create a log file to capture allthe details of the export process. This errorindicates that Data Warehouse Center cannotaccess or open this log file. If the DataWarehouse Center cannot create the log file, theexport process cannot continue. Some typicalreasons that a log file could not be openedinclude:

v The file name is not valid.

v The path name is not valid.


User Response: Verify that you have writeaccess to the specified log path and that there isan adequate amount of memory and storageavailable on your system. If the problem persists,contact IBM Software Support.

DWC13604E The export utility was unable toopen the feedback file feedback-file.

Explanation: The Data Warehouse Centerattempts to create a feedback file in the samedirectory as the XML file that you are exporting.This error indicates that Data Warehouse Centercannot access or open the feedback file. If DataWarehouse Center cannot create this feedbackfile, the result of the export process cannot bedisplayed, and the export process cannotcontinue.

User Response: Verify that you have writeaccess to the specified path and that there is anadequate amount of memory and storageavailable on your system. If the problem persists,contact IBM Software Support.

DWC13700E The Data Warehouse Centerobject object1-type namedobject1-name, which is required toimport the Data WarehouseCenter object object2-type namedobject2-name, could not be found.

Explanation: This is an internal error thatoccurs when the import utility cannot find an


object that should already exist in the DataWarehouse Center. If the required object was notcreated during the import process, the importutility cannot continue.

User Response: Verify that the XML file thatyou are importing is not damaged. To do this,regenerate the XML file from its original sourceand then run the import again. If you still receivethis error message, contact IBM Software Supportor the vendor who provided the file.

DWC13701E Unable to import the DataWarehouse Center objectobject1-type named object1-name,because no common warehousemetamodel object of typeobject2-type was found.

Explanation: Creating an object of this typedepends on Data Warehouse Center finding anecessary common warehouse metamodel object.Without this common warehouse metamodelobject, the Data Warehouse Center object is notvalid. If you are getting this error message, it islikely that the XML file that you are importingdoes not contain the necessary commonwarehouse metamodel object.


DWC13702E A primary key already exists andcannot be updated. The importprocess cannot continue.

Explanation: Your warehouse control databasehas a primary key, and the data that you aretrying to import contains a different primary keyon the same table. To complete the importprocess, there must either be just one primarykey, or two primary keys that match. You cannothave two different primary keys.

User Response: To resolve the unmatchedprimary keys, take one of the following actions:

v Change your warehouse control database’sprimary key to match the primary key that isin the data that you want to import.

v Delete the primary key from the data that youwant to import and use the primary key thatis in your warehouse control database.

v Change the primary key in the data that youwant to import to match the primary key thatis in your warehouse control database.

DWC13703E A foreign key already exists andcannot be updated. The importprocess cannot continue.

Explanation: Your warehouse control databasehas a foreign key, and the data that you aretrying to import contains a different foreign keyon the same table. To complete the importprocess, there must either be just one foreign key,or two foreign keys that match. You cannot havetwo different foreign keys.

User Response: To resolve the unmatchedforeign keys, take one of the following actions:

v Change your warehouse control database’sforeign key to match the foreign key that is inthe data that you want to import.

v Delete the foreign key from the data that youwant to import and use the foreign key that isin your warehouse control database.

v Change the foreign key that is in the data youwant to import to match the foreign key that isin your warehouse control database.

DWC13704E The import utility was unable toimport the Data WarehouseCenter object object1-type namedobject1-name. This is because thevalue for the TaggedValue objectobject2-type, which was specifiedfor the UML object of typeobject3-type, is not valid.

Explanation: This is an internal error thatoccurs when Data Warehouse Center finds valuesin the TaggedValue object that are outside of theexpected range. For example, the file mightcontain text values instead of numeric values, orthe numeric values are incorrect.


User Response: Contact IBM Software Support,or the vendor who supplied the file.

DWC13705E The import utility was unable tocreate a temporary XML file in theEXCHANGE directory. Exception= exception-code.

Explanation: The Data Warehouse Center mustbe able to create a copy of the XML file in thesame directory as the CWM.DTD file. This errormessage indicates that Data Warehouse cannotcreate that XML file. If Data Warehouse Centercannot create this file, the import process cannotcontinue.

User Response: Verify that you have writeaccess to the specified EXCHANGE path andthat there is an adequate amount of memory andstorage available on your system. If the problempersists, note the exception code from this errormessage and contact IBM Software Support.

DWC13706E The XML file XML-file cannot beloaded. Exception = exception-code.

Explanation: This is an internal error thatoccurs when Data Warehouse Center is unable toread an XML file during the import process.Typical causes include files that have either beendamaged, or that do not contain XML data. IfData Warehouse Center cannot read the XMLfile, the import process cannot continue.


DWC13707E The import utility was unable toopen the log file logfile-name.

Explanation: The Data Warehouse Centeralways attempts to create a log file to capture allthe details of the import process. This errorindicates that Data Warehouse Center cannotaccess or open the log file. If the Data WarehouseCenter cannot create the log file, the importprocess cannot continue.

User Response: Some typical reasons that a logfile could not be opened on import include:v The file name is not valid.

v The path name is not valid.


Check to see if any of these problems exist and ifso, make the necessary changes, or call IBMSoftware Support.

DWC13708E The import utility was unable toopen the feedback file feedback-file.

Explanation: The Data Warehouse Centerattempts to create a feedback file in the samedirectory as the XML file that you are importing.This error indicates that Data Warehouse Centercannot access or open the feedback file. If DataWarehouse Center cannot create the feedback file,the result of the import process cannot bedisplayed.

User Response: Verify that you have writeaccess to the specified path and that there is anadequate amount of memory and storageavailable on your system. If the problem persists,contact IBM Software Support.

DWC13709N The import utility was unable tocopy the cwm.dtd file from theEXCHANGE directory to thecurrent directory. Exception =exception-id.

Explanation: The Data Warehouse Center mustbe able to create a copy of the cwm.dtd file inthe same directory that the import utility isinvoked. The Data Warehouse cannot copy theDTD file. If the Data Warehouse Center cannotcreate this file, the import process cannotcontinue.

User Response: Verify that you have readaccess to the specified EXCHANGE path andthat you have write access to the current runningdirectory. Verify that there is an adequate amountof memory and storage available on your system.If the problem persists, check the exception codefrom this error message and contact IBMSoftware Support. You may also try to copy the


cwm.dtd file manually from the EXCHANGEdirectory to the current running directory.

DWC14001E database-name: Database not found.

Explanation: A transformer internal erroroccurred. A translatable database was not foundin the resource property file.

User Response: Ensure the database is runningnormally. Verify that the process running thetransformer has the authority to create tables.Then, run the transformer again.

DWC14002E Log table access error.

Explanation: A transformer could not access thetransformer error log table.


DWC14003E Log table definition error.

Explanation: The structure of the transformererror log table does not match the structurerequired by the error logging function. If thetransformer code has been updated, the requirederror logging table structure may have changed.

User Response: Drop the transformer error logtable. It will be recreated by the transformer thenext time the transformer is run.

DWC14005E Run ID value is invalid. It must bean integer.

Explanation: The run ID value specified isinvalid. It must be an integer. The run ID is usedby the transformers in the log table to uniquelyidentify the process when the transformer isinvoked.

User Response: Change the run ID to aninteger.

DWC14006E Required parameter not specified:parameter-name.

Explanation: You did not supply a requiredparameter for the transformer.

User Response: Enter the missing parameterand run the transformer again.

DWC14007E Data type of column column-nameis not valid for column typespecified.

Explanation: The data type of the column doesnot match the required data type for the periodthat you specified.

User Response: Take one of the followingactions:

v Select a column that has a data type thatmatches the data type for the period that youspecified.

v Change the period to a period that has a datatype that matches the column you selected.

DWC14008E Could not access the specified runlog: table-name.

Explanation: A transformer could not access thetransformer error log table.


DWC14009E Data type of the column-namecolumn is not valid; it must bedata-type.

Explanation: The data type for the selectedcolumn is incorrect.

User Response: Correct the column data typeand run the transformer again.

DWC14010E Parameters name and name maynot both be specified.

Explanation: You specified information for twofields that cannot be used together.


User Response: Clear one of the fields.

DWC14011E One (and only one) of theparameters name and name mustbe specified.

Explanation: You specified information for twofields that cannot be used together.

User Response: Ensure that you specifyinformation for one (and only one) of the fields.

DWC14012E Specified column column-name notfound in table table-name.

Explanation: The specified column was notfound in the table that you selected.

User Response: Check that the specified columnis defined for the table that you selected or thatthe proper table is being used.

DWC14013E Unable to calculate statistics valuein method class-name.method-name.Error type: error.

Explanation: A statistics method was unable tocomplete the calculations for a statistics value.This might have occurred because of one of thefollowing:

v The input values passed to the statisticsroutine were too small or too large.

v The routine encountered a value of NaN (Nota Number) or Infinity in performing thecalculations.

User Response: Correct the input data andrerun the transformer.

DWC14016E Input table column data typesmust have a common promotabledata type.

Explanation: The specified input table columnsare expected to be either homogeneous or oftypes that are related to each other throughautomatic promotion.


v If you are defining a step that uses thePivotData Transformer, verify that the pivotgroups are related to each other throughautomatic promotion.

v If you are defining a step that uses theInvertData Transformer, verify that the sourcetable columns are related to each otherthrough data type promotion (except for thefirst column if that is to be used for the outputcolumn names).

To understand the groups of related data types,refer to the ″Promotion of Data Types″ section inthe SQL Reference.

DWC14017E Invalid parameter: parameter-name.

Explanation: The parameter passed to thetransformer is invalid.

User Response: In the transformerdocumentation, find the allowable data formatfor the parameter. Then, fix the parameter.

DWC14018E Primary Key not found for tabletable-name.

Explanation: The table specified does not havea primary key defined for it. The primary key isrequired for the table update.

User Response: Define a primary key for thespecified table.

DWC14019E Value value for parameter-nameparameter is invalid.

Explanation: The value specified for the field isinvalid.

User Response: Check the documentation forthe transformer to see the allowable data formatfor the field.

DWC14025E Table table-name has no keycolumn to use for updates.

Explanation: For the transformer to update thetable, the table must have a primary key columndefined.


User Response: Define a primary key on thetable and run the transformer again.

DWC14026E Could not access table table-name.

Explanation: A transformer could not access thespecified table.

User Response: Verify that the specified tableexists.

DWC14027E No rows in table table-name.

Explanation: The specified table is empty. Norows are defined for the table.

User Response: Verify that the correct table isspecified.

DWC14028E NaN or Infinity returned by aStatistics function.

Explanation: A statistics method was unable tocomplete the calculations for a statistics value.Not a Number (NaN) or Infinity was returnedfrom the calculate.


DWC14029E Both parameters name and namemust be specified if one is.

Explanation: You cannot use one field withoutusing the other.

User Response: Provide information for both ofthese fields.

DWC14030N The table table-name does not havea run id field.

Explanation: The first column of the target tableneeds to be an integer. The target error tablemust have a run id integer column or thetransformer cannot insert rows into the targettable. The target error table is created when thetransformer is run for the first time, or when thetransformer does not find the target error table inthe target database.

User Response: The target error table musthave a run id column. Add a run id integer

column to the target error table or drop thetarget error table, and let the transformer recreatethe table at run time. To add the run id column,you must alter the target error table.

DWC14031N The table table-name could not becreated.

Explanation: The table could not be created bythe transformer due to a database error. AnSQLException was returned by the DB2 JDBCdriver.

User Response: Check the privileges to createthe table in the target database. For more details,check the contents of the transformer log table.

DWC14100E A value sub-parameter was notspecified in the parameter-nameparameter.

Explanation: You provided information for afield without specifying the required secondaryinformation.

User Response: Specify the correct secondaryinformation and run the transformer again.

DWC14101E Data type of column-name columnmust be DATE, TIMESTAMP, orTIME.

Explanation: You specified a column that has anincorrect data type. The data type must beDATE, TIMESTAMP, or TIME.

User Response: Correct the data type to DATE,TIMESTAMP, or TIME and run the transformeragain.

DWC14102E Value for parameter-name parameteris earlier than parameter-nameparameter.

Explanation: The value specified for the firstparameter in the message must be later than thevalue specified for the second parameter in themessage.

User Response: Correct the value in the firstparameter (or second parameter if necessary) andrun the transformer again.


DWC14103E Invalid value sub-parameterspecified for column column-name.

Explanation: You specified an invalidsub-parameter for a column.

User Response: Specify a valid value for thesub-parameter and run the transformer again.

DWC14104E The specified Date or Time valuevalue is not in ISO format or hasincorrect values.

Explanation: You specified an incompatibleDate or Time value.

User Response: Correct the data type to Date,TimeStamp, or Time and run the transformeragain.

DWC14200E ANOVA supports up to 3Grouping columns.

Explanation: ANOVA supports from 1 to 3Grouping columns. The number of Groupingcolumns determines the type of ANOVAcalculation performed. One, two, or threegrouping columns results in either a One-way,Two-way, or Three-way ANOVA, respectively.

User Response: Change the number ofGrouping columns accordingly.

DWC14201E ANOVA Grouping column is thesame as Data column.

Explanation: An ANOVA Grouping column isthe same as the Data column.

User Response: Remove the column that youwant to use as the Data column from theGrouping columns.

DWC14202E ANOVA Cell count is less than 2.

Explanation: In the Two-way or Three-wayANOVA, the multi-dimensional cell count(number of data items in the subgroup) must be2 or greater.

User Response: Check the input data table and

ensure that the input data conforms to thisrequirement.

DWC14203E ANOVA Cell count is not equal inall cells.

Explanation: In the Two-way or Three-wayANOVA, the multi-dimensional cell count(number of data items in the subgroup) must beequal across all cells.

User Response: Check the input data table andensure that the input data conforms to thisrequirement.

DWC14204E Query returned incorrect numberof rows for grouping-column-name.

Explanation: During a query, an invalid numberof rows was returned for the Grouping columnspecified. The number of rows expected wasdetermined from an earlier query.

User Response: Rerun the function. Ensure thatthe input table is not being concurrently updatedby another process.

DWC14255E Table cannot be cross-tabulated.

Explanation: The input table for the Chi-squaretransformer cannot be converted into across-tabulated table. Two grouping columnshave been entered. Conceptually, Chi-square usesthe data in these two columns to form the rowsand columns of a cross-tabulated table populatedby the Observed Frequencies column data.

User Response: Check that the groupingcolumns in the input table contain data that canbe used to create a cross-tabulated table.

DWC14256E Cannot calculate expected valueswithout two grouping columns.

Explanation: Two grouping columns arerequired to calculate expected values.

User Response: Select an additional column tobe a grouping column or specify a column to beused as Expected frequencies column.


DWC14257E Cannot calculate expected valuesif Expected Frequencies column isspecified.

Explanation: You have entered an ExpectedFrequencies column name and an ExpectedValues output table name. Only one or the othercan be specified.

User Response: Remove either the ExpectedFrequencies column name or the Expected Valuesoutput table name from the step.

DWC14300E Input data column not specifiedfor rule definition rule-name.

Explanation: You did not provide a source datacolumn for a rule that you defined.

User Response: Verify that the source table hasbeen imported into the Data Warehouse Centerand that all columns that are used in the rulesdefinition exist in the imported table.

DWC14301E Two or more rows specifying thesame output column column-namehave different input columns.

Explanation: You defined two or more rulesthat write to the same target column.

User Response: Change the Clean Datatransformer rule definitions so that each columnin the target table is associated with only onecolumn in the source table.

DWC14302E Input column column-name andoutput column column-name datatypes do not match.

Explanation: One or more of the name columnsin the source and target tables that you definedin a rule have different data types.

User Response: Ensure that the name columnsin the source and target tables are of the sametype.

DWC14303E In rule definition rule-definition, norule type specified for tabletable-name.

Explanation: You did not specify a clean typefor a clean transformer.

User Response: Verify that you selected a cleantype for each entry in the Data WarehouseCenter Clean Data transformer window.

DWC14304E In rule definition rule-name, notable specified for rule typerule-type.

Explanation: You did not specify a rule table fora rule definition.

User Response: Ensure that all ″find andreplace″, ″clip″, and ″discretize″ rules have rulestables that exist and are known to the DataWarehouse Center.

DWC14305E In rule definition rule-name, nocolumns specified for tabletable-name.

Explanation: You did not specify columns for arule definition.

User Response: Verify that each ″find andreplace″, ″clip″, and ″discretize″ rule has a tablewith columns appropriate to the selected rule.

DWC14306E In rule definition rule-name, notable specified for specifiedcolumns column-names.

Explanation: You did not specify a rule table fora rule definition.

User Response: Verify that each ″find andreplace″, ″clip″, and ″discretize″ rule has a tablewith columns appropriate to the selected rule.

DWC14307E In rule definition rule-name, ruletype rule-type requires countcolumn names.

Explanation: You selected a rule table that doesnot have the correct number of columns selectedfor the rule that you are defining.


User Response: Select the correct number ofcolumns for the rule definition.

The find and replace rule requires 2 or 3columns, the extra column being the order bycolumn (see the ″Managing Data WarehouseCenter″ in the section titled ″Usingtransformers″).

The Discretization rule requires 3 or 4 columnswith the extra column specifying the order inwhich the rules are pulled from the rule table.The clip rules requires 4 or 5 columns, where theextra optional column is specified for the samereasons as the previous two rules.

DWC14308E In rule definition rule-name, inputand output column data types donot match those of the rule table.

Explanation: In a rule definition, you specifieda rule table that has different data types than thesource and column data type you specified.

User Response: Verify that the named columnsin the rule table (other than the order column)have the same data type as the named columnsin the source and target tables.

DWC14309E In rule definition rule-name, therow clean parameter name isinvalid. It must be a ″0″ or ″1″.

Explanation: The row clean parameter for a ruledefinition is invalid.

User Response: Ensure that the SQL stringcontains either a ″0″ or a ″1″ for this parameter.The default is ″0″.

DWC14310E In rule definition rule-name, thewhite space indicator parametername is invalid. It must be a ″0″ or″1″.

Explanation: You entered an invalid number inthe white space field in the Cleantransformer-numeric parameters window.

User Response: Ensure that the SQL stringcontains either a ″0″ or a ″1″ for this parameter.The default is ″0″ when nothing is entered.

DWC14311E In rule definition rule-name, therespect case parameter name isinvalid. It must be a ″0″ or ″1″.

Explanation: You entered an invalid number inthe respect case field in the Cleantransformer-numeric parameters window.

User Response: Ensure that the SQL stringcontains either a ″0″ or ″1″ for this parameter.The default is ″1″ when nothing is entered.

DWC14312E In rule definition rule-name, thecompress white space parametername is invalid. It must be a ″0″ or″1″.

Explanation: You entered an invalid number inthe compress white space field in the Cleantransformer-numeric parameters window.

User Response: Ensure that the SQL stringcontains either a ″0″ or ″1″ for this parameter.The default is ″0″ when nothing is entered.

DWC14313E In rule definition rule-name, thenumeric tolerance must be apositive integer or decimalnumber.

Explanation: You entered an invalid number inthe numeric tolerance field in the Cleantransformer-numeric parameters window.

User Response: Verify that the value entered forthis parameter is base 10 numeric and is greaterthan or equal to zero.

DWC14314N The error table table-name mustfollow the structure of the sourcetable.

Explanation: The target error table does nothave a structure similar to the transformer sourcetable. The first column of the target error tableshould be an integer for the run id, and the restof the table should have the same structure asthe transformer source table.

User Response: Drop the target error table inthe target database and let the transformerrecreate the table.


DWC14315N Output data column not specifiedfor rule definition rule-number.

Explanation: The output data column has notbeen specified for the particular rule definition.

User Response: Check the transformer columnmapping and make sure that every rule has amapped output data column.

DWC14316N The data type for rule rule-numbercannot be cleaned.

Explanation: The data type for the rule cannotbe cleaned by the clean transformer.

User Response: Remove the rule from the cleanstep because the data type cannot be cleaned bythe clean transformer.

DWC14350E Output table table-name is thesame as the input table.

Explanation: You ran a Calculate Statistics orCorrelation transformer using the same table forinput and output. For these transformers, theinput table must not be the same as the outputtable. The transformer reads data from the inputtable and writes results to the output table.

User Response: Rerun the transformer,providing the name of the table which containsthe input data and the name of a different tablewhere the results can be written.

DWC14351E Unexpected end of parameter-nameparameter reached.

Explanation: Parsing of a parameter in thetransformer stored procedure did not complete.The end of the parameter was detected soonerthan expected. This error might occur for anumber of reasons. For example:

v A left parenthesis does not have a matchingright parenthesis or an extraneous comma isincluded in the parameter string

v A statistic identifier is missing

User Response: Review the correct syntax forthe parameter in error, correct the parameter, andrerun the transformer.

DWC14352E Input column column-name has aninvalid data type data-type forstatistic statistic-name.

Explanation: Statistic calculations can only beperformed on specific types of data. A columnwith an unsupported data type was specified asan input column for a statistic calculation.

User Response: Review the valid input datatype(s) for the statistic in error, specify the nameof an input column that has a valid data type,and retry the calculation.

DWC14353E Output column column-name hasan invalid data type data-type forstatistic statistic-name and inputcolumn column-name.

Explanation: The data type of the outputcolumn specified for a statistic calculation isinvalid. Output from statistic calculations canonly be of specific data types. Valid data typesdepend on the statistic. For some statistics, validdata types depend also on the data type of theinput column. The error occurred because acolumn with an invalid data type was specifiedas an output column for a statistic calculation.

User Response: Review the valid output datatype(s) for the statistic in error, specify the nameof an output column that has a valid data type,and retry the calculation.

DWC14354E Output column column-name isspecified for statistic name and forstatistic name.

Explanation: You specified the same outputcolumn for two statistic calculations. An outputcolumn can be used for only one statisticcalculation.

User Response: Rerun the transformer,providing the name of a column which can beused for the results of one statistic calculationand the name of a different column which can beused for the results of the other statisticcalculation.


DWC14355E Statistic identifier number is notsupported.

Explanation: In Data Warehouse Center stepsfor the Calculate Statistics and CorrelationTransformers, only the names of each statistic canbe specified. Each statistic that can be calculatedby the Calculate Statistics or CorrelationTransformers is assigned a unique numericidentifier.

User Response: Contact IBM CustomerSupport.

DWC14356E Grouping column column-name isthe same as an input column.

Explanation: You specified a column in thegrouping columns field and as an input datacolumn in the statistics definition field of theCalculate Statistics or Correlation transformer.

User Response: Provide the name of a columnthat contains the input data and the name of adifferent column or columns that can be used togroup the results of the statistic calculation.Then, run the transformer again.

DWC14357E Grouping column column-name isspecified twice.

Explanation: Remove the duplicate columnname from the grouping column parameter andrun the transformer again.

User Response: Remove the duplicate columnname from the grouping column parameter andrun the transformer again.

DWC14358E Grouping column column-name isthe same as an output column.

Explanation: A column was specified as agrouping column in the grouping columnsparameter and as an output data column in thestatistics definition parameter of a CalculateStatistics or Correlation transformer.

User Response: You specified the same columnin the grouping columns field that you specifiedas an output data column statistics definition

field of a Calculate Statistics or Correlationtransformer.

DWC14400E One or more correlationcalculations resulted in a ″null″value.

Explanation: The result of a correlation statisticcalculation could not be represented as a number,so the result is represented in the output table asnull. The null result may have been caused byone of the following:

v You provided only one input value for acorrelation statistic calculation. For example,the input table may contain only one row ofdata or one or more grouping columns mayhave been specified and one or more of thegroups contains only one row of data.

v The p-value could not be calculated becausethe maximum number of iterations werereached during a continued fractioncomputation.

v The result of a correlation statistic calculationis negative or positive infinity.


v Ensure that the input table has at least tworows of data. After making your changes, runthe Correlation transformer again.

v If one or more grouping columns are specifiedin the Correlation transformer parameter list,you might be able to avoid null results byensuring that there are at least two rows ofinput data for each group.

DWC14401E Output column column-name hasdata type type, but the data typemust be type for this column.

Explanation: The Correlation transformer writesthe names of the two columns that contain inputdata to the first two columns in the output table.One of the first two columns in the output tablehas an invalid data type.

User Response: Correct the data type of thecolumn in the output table and run thetransformer again.


DWC14402E Output column column-name hasdata type type and output columncolumn-name has data type type,but the data type must be type foreach of these columns.

Explanation: The Correlation transformer writesthe names of the two columns which containinput data to the first two columns in the outputtable. Both of the first two columns in the outputtable have an invalid data type.

User Response: Correct the data type for eachof the two columns in the output table and runthe transformer again.

DWC14500E Too many rows (count) to Invert.Maximum amount is count.

Explanation: You tried to invert a table that hasmore rows than the maximum number ofcolumns that your database will support.

User Response: Verify that the source table hasa number of rows equal to or less than themaximum number of table columns supported inthe version of DB2 running this transformer.

DWC14600E Moving Average Type is invalid.

Explanation: The type of Moving Averagerequested is invalid. Three function types aresupported:

v Standard moving average

v Exponentially smoothed moving average

v Rolling sum

User Response: Change the Moving Averagetype to one of the three supported types.

DWC14601E Moving Average Period must begreater than 1.

Explanation: The period specified forcalculating the Moving Average or Rolling Sumis invalid. The period must be an integer greaterthan 1.

User Response: Change the Moving Averageperiod to an integer greater than 1.

DWC14602E Moving Average Data columnsame as Order By column.

Explanation: One of the Moving Average datacolumns selected is the same as one of the OrderBy columns.

User Response: Select data columns for MovingAverage that are different from the Order Bycolumns.

DWC14650E Carry over columns must bespecified in pairs.

Explanation: Both source and target columnnames are required for the carry-over parameter.

User Response: Verify that the source columnname exists and the specified target columnname is valid within the constraints of the DataWarehouse Center.

DWC14651E Invalid number of pivot columns.

Explanation: The pivot groups contain differentnumbers of columns. Each pivot group mustcontain the same number of columns.

User Response: Verify that the number ofcolumn names match the number of columns ineach group that is pivoted, unless only onecolumn name is specified.

DWC14652E Invalid number of aggregationcolumns.

Explanation: You did not specify any columnsin the pivot column field.

User Response: Specify one or more columns inthe pivot column field. Ensure that the numberof column names matches the number ofcolumns in each group that is provided.

DWC14653E Number of columns inaggregation group does not matchpivot column count.

Explanation: The number of data columns thatyou specified in the pivot columns field does notequal the total number of columns in your pivotgroups.


User Response: Verify that the pivot columnsparameter (as seen in the SQL) follows thefollowing rule: Each group is delimited by asemi-colon ″;″. The first parameter in a group isthe output column name. The second through nparameters in a group are the names of the inputtable columns. In the special case where there isonly one name in one group, that name is theoutput column name of the aggregated inputcolumns where the number and names of theinput columns are not known ahead of time.

DWC14654E Carry over columns not found intable table-name.

Explanation: The columns you selected in thecarry-over columns pair do not exist.

User Response: Verify that there are zero ormore carry-over column pairs and that thenamed columns exist in both the source andtarget tables.

DWC14700E Independent Data column equalsDependent Data column.

Explanation: You selected the same column forthe Criterion column as you selected for thePredictor column in a Regression transform. Thecolumn selected as the Criterion column cannotbe the same as the column selected for thepredictor column.

User Response: Remove the Criterion columnfrom the Predictor selection and run theregression transform again.

DWC14701E Duplicate Independent Datacolumns.

Explanation: A column has been selected as aPredictor column twice.

User Response: Remove one selection from thePredictor column field. Then run the regressiontransform again.

DWC14702E Count from result set andprevious row count not equal.

Explanation: During a query, an invalid numberof rows was returned. The number of rowsexpected was determined from an earlier query.

User Response: Run the transformer again.Ensure that the input table is not beingconcurrently updated by another process.

DWC14750E Subtotal Grouping column sameas Date column.

Explanation: One of the Subtotal Groupingcolumns selected is the same as the Date column.

User Response: Change the Grouping columnsso that the Date column is not included.

DWC14751E Subtotal Data column same asDate column.

Explanation: A Subtotal Data column is thesame as the Date column.

User Response: Change the Data columns sothat the Date column is not included.

DWC14752E Subtotal Data column same asGrouping column.

Explanation: A Subtotal Data column is thesame as a Grouping column.

User Response: Change the Data columns sothat the Grouping columns are not included.

DWC14753E Subtotal Period is invalid.

Explanation: The Subtotal Period requested isinvalid. Five Period types are supported:

v Week

v Semi-Month

v Month

v Quarter

v Year

User Response: Change the Subtotal Periodtype to one of the five supported types.


DWC15000N Unable to open VWS_LOGGINGenvironment.

Explanation: Set the VWS_LOGGINGenvironment variable during installation.

User Response: The VWS_LOGGINGenvironment variable is not set .

DWC15001N Cannot create temporary trace file.

Explanation: Might not have sufficient diskspace.

User Response: Verify that the VWS_LOGGINGdirectory has sufficient disk space for the tracefile. If the disk space is not sufficient, removeunused files and restart the program.

DWC15002N Unable to open trace file filename.

Explanation: Disk space might be insufficient ortrace file might not exist.

User Response: Check that the file exists bytrying to open it. Check that theVWS_LOGGING directory has sufficient diskspace. If the disk space is insufficient, removeunused files and restart the program.

DWC15003N Enter a password type for theseventh parameter.

Explanation: An error occurred because thevalue for the password type was incorrect.Correct password types are: EnterPassword,PasswordNotRequired, GetPassword.

User Response: Enter the correct value for thepassword type and restart the program.

DWC15004N The get password program failed.

Explanation: An error was returned by the getpassword program while retrieving thepassword. An error can occur because the getpassword program returned a nonzero returncode, the file containing the password did notexist or could not be opened, or the file couldnot be deleted after the password was retrieved.

User Response: Check that the get password

program works properly and that there issufficient disk space for the password file.

DWC15005N The ″Highest JES Return Code toConsider Success″ value must benumeric.

Explanation: An error was returned because thevalue of the parameter ″Highest JES return codeto Consider Success″ was not valid.

User Response: Correct the User DefinedFunction parameter value and restart theprogram.

DWC15007N Unable to create temporary filefor ftp log.

Explanation: The operating system was unableto create a unique file name. There might be toomany temporary file names in theVWS_LOGGING directory.

User Response: Check that there is sufficientdisk space in the VWS_LOGGING directory. Ifthe disk space is not sufficient, removeunnecessary files and restart the program.

DWC15008N Unable to create temporary filefor ftp command.

Explanation: Operating system unable to createa unique file name. There might be too manytemporary file names in the VWS_LOGGINGdirectory.


DWC15009N The User Defined Program cannotopen file filename for ftp call.

Explanation: The User Defined Program cannotopen the file in update mode.

User Response: Check that the program haswrite access to the file filename and restart theprogram.


DWC15010N Cannot execute a ftp connectioncommand.

Explanation: The User Defined Program tried toconnect to the remote host via ftp. The ftpprogram returned a non-zero return code. Checkthe ftp trace file or the ftp log file in theVWS_LOGGING directory.

User Response: Check that the system has aworking network connection. If needed, setupthe network connection and restart the program.

DWC15011N Cannot open the log file filename.

Explanation: The User Defined Program failedwhile trying to open the ftp log file to determineif the ftp was successful.

User Response: Check that the log file exists bytrying to open it. Check that theVWS_LOGGING directory has sufficient diskspace. If the disk space is insufficient, removeunused files and restart the program. If theproblem persists, contact your IBM servicerepresentative.

DWC15012N Cannot delete error file filename onOS/390.

Explanation: The User Defined Program failedwhile trying to delete the ETI error file in theVWS_LOGGING directory on the OS/390 host.This file must be deleted before running the ETIprogram.

User Response: Verify that the error file is notin use. Delete the file if it exists and restart theprogram.

DWC15013N Cannot create temporary file forjes log.

Explanation: The operating system was unableto create a unique file name. There might be toomany temporary file names in theVWS_LOGGING directory.


DWC15014N The JCL file does not exist on theMVS system specified.

Explanation: The JCL file that was to besubmitted for execution could not be found onthe MVS system specified. The file may also notbe in a proper MVS format. The file name shouldbe fully qualified and enclosed in double quotes.

User Response: Verify that the JCL file that wasspecified exists on the MVS system. The filename should be fully qualified and enclosed indouble quotes. If the file name is specifiedcorrectly, collect all details about this error andcontact your IBM service representative. Includeall trace and log files in the logging directory.

DWC15015N The JCL file is empty.

Explanation: The JCL file that was specified forjob submission contained no information.

User Response: Verify that the correct JCL filename was specified, or create the necessary jobcontrol statements in the file and resubmit thestep for execution. If the JCL file contains jobinformation, collect all details about this errorand contact your IBM service representative.Include all trace and log files in the loggingdirectory.

DWC15016N Error while attempting to FTP theJCL file.

Explanation: Verify that the Data WarehouseCenter agent that is executing the step hasauthority to FTP to the target MVS system. If theagent does have the authority to FTP files, collectall details about this error and contact your IBMservice representative. Include all trace and logfiles in the logging directory.

User Response: An error occurred while tryingto FTP the JCL file from the target MVS system.Check that FTP is a valid command on the agentsystem. Run the user-defined program again.


DWC15017N The JCL file cannot be created inthe local directory.

Explanation: An error occurred while trying towrite the JCL file to the local directory whileprocessing the file at the Data Warehouse Agentsite.

User Response: Verify that the file systemwhere the agent is writing the temporary file andthe log files is not full. This directory can beidentified by looking at the system environmentvariable VWS_LOGGING on the system wherethe agent is executing. If the file system is notfull, collect all details about this error andcontact your IBM service representative. Includeall trace and log files in the logging directory.

DWC15018N An internal error occurred whilechecking JOBID in the JCLfile:filename .

Explanation: The user-defined program failed toopen the JCL file filenameS to check the JOBID.

User Response: Check that the file exists in theVWS_LOGGING directory and that it can beopened. Collect all details about this error andcontact your IBM service representative. Includeall trace and log files in the logging directory.

DWC15019N The job name is not the same asthe remote ID.

Explanation: The job name specified in the JCLis not the same as the userid (plus one character)associated with the submitted job. These useridsmust match.

User Response: Change the job name in the JCLso that it matches the remote ID being used tosubmit the JCL for execution, or change theremote ID being used to submit the JCL forexecution to that of the userid specified on theJCL job name. If the job name matches that of theRemote ID being used to submit the job (plusone character), collect all details about this errorand contact your IBM service representative.Include all trace and log files in the loggingdirectory.

DWC15020N Unable to obtain unique error filename.

Explanation: The request to the operatingsystem to generate a unique file name failed.This error may be caused by too manytemporary file names in the VWS_LOGGINGdirectory.

User Response: Remove unnecessary files fromthe VWS_LOGGING directory and try the actionagain by resubmitting the step for execution. Ifthe failure still occurs, collect all the details ofthe error and contact your IBM servicerepresentative. Include the trace and log files inthe logging directory.

DWC15021N Local error file could not becreated.

Explanation: The Data Warehouse agent wasnot able create a temporary file to hold thecontents of the returned errors.

User Response: Verify that the agent has writeaccess to the temporary directory indicated bythe VWS_LOGGING directory and that the filesystem where the directory exists is not full. Ifthe file system is not full, collect all details aboutthis error and contact your IBM servicerepresentative. Include all trace and log files inthe logging directory.

DWC15022N Unable to open local error filefilename.

Explanation: The Data Warehouse Center agentwas not able to open temporary file filenamecontaining the errors that occurred during stepexecution.

User Response: Check that the agent hasread/write access to the directory indicated bythe VWS_LOGGING environment variable. If theagent does have access to the directory, contactyour IBM service representative. Include all traceand log files from the logging directory.


DWC15023N Local error file filename is empty.

Explanation: The Data Warehouse Center agentdid not find any information on errors from thestep execution in temporary file filename.

User Response: Check that the file systemwhere the temporary file was written, asspecified in the VWS_LOGGING environmentvariable, is not full. If the file system is not full,collect all details about this error and contactyour IBM service representative. Include all traceand log files in the logging directory.

DWC15024N Unable to remove local error file.

Explanation: The agent was not able to removethe temporary file containing the errors from thestep execution.

User Response: An internal error occurred.Collect all details about this error and contactyour IBM service representative. Include all traceand log files in the logging directory.

DWC15025N Unable to FTP error file.

Explanation: The Data Warehouse agent wasnot able to retrieve the error file that was createdas a result of the step execution.

User Response: Verify that the remote ID usedto run the step has access to the error file. If thefile does exist and the agent has access to thatfile, collect all details about this error and contactyour IBM service representative. Include all traceand log files in the logging directory.

DWC15026N Error executing JCL. Check JESoutput file: filename .

Explanation: Errors occurred while executingthe JCL.

User Response: Review the JES output for thisjob: filename. Make the necessary corrections toresolve the errors.

DWC15027N ETI errors occurred duringprocessing. Errors have beenwritten to the ETI error filefilename.

Explanation: ETI returned errors whileprocessing the job request.

User Response: Review the errors in error filefilename and make the necessary corrections.

DWC15028W ETI warnings occurred.

Explanation: ETI programs completed withwarnings.

User Response: Refer to the log file for detailedinformation.

DWC15029N ETI program failed.

Explanation: The ETI program has failed.

User Response: ETI program failed. Please referto the log file for detailed information.

DWC15030N ETI program did not complete.

Explanation: ETI program started but did notcomplete. The step has failed.

User Response: ETI program did not complete.Refer to the log file for detailed information.

DWC15031W ETI program completed. Unableto determine success/failure.

Explanation: ETI program completed. Theuser-defined program could not find theEXTRACT$ERROR or ET1007S in the ETI errorfile to determine success or failure. Stepcompletion status = warning.

User Response: ETI program completed. Theuser-defined program was unable to determinesuccess or failure of the ETI program. Refer tothe log file for more information.


DWC15032N Error calling API. Return code=ReturnCode.

Explanation: The call to the Essbase API wasnot successful.

User Response: Refer to the Essbasedocumentation for the return code from the API.

DWC15033N Incorrect syntax for membermember name: record name.

Explanation: The syntax for the member is notcorrect.

User Response: Correct the syntax for themember.

DWC15034N Member member: record notaccessible.

Explanation: The member was not accessable.

User Response: Check that the member existsin the Essbase database.

DWC15035N Member member: record not foundin database.

Explanation: The member was not found in theEssbase database.

User Response: Check that the Essbase databasecontains the member.

DWC15036N Unknown error for membermember: record with error typeerrortype.

Explanation: The member had unknown errors.

User Response: Please refer to the Essbasedocumentation.

DWC15037N Wrong dimension for membermember: record.

Explanation: The member member had a baddimension.

User Response: Please refer to the Essbasedocumentation for more information.

DWC15038N Wrong generation for membermember: record.

Explanation: The member member had a badgeneration.

User Response: Please refer to the Essbasedocumentation for more information.

DWC15039N Parameter parameter must be 0 or1.

Explanation: The parameter parameter must beeither 0 or 1.

User Response: Collect all trace and log filesand contact your IBM service representative.

DWC15040N Cannot open output fileoutputfilename.

Explanation: The Data Warehouse agent wasnot able to open the output file that would beable to contain the exported data.

User Response: Verify that the agent hasread/write access to the directory. If the agentdoes have access to that directory, collect all traceand log files and contact your IBM servicerepresentative.

DWC15041N Cannot create netrc filenetrcfilename

Explanation: The Data Warehouse agent wasnot able to create the netrc file in theVWS_LOGGING directory.

User Response: Verify that the agent hasread/write access to the directory pointed to bythe VWS_LOGGING environment variable. If theagent does have access to that directory, collectall trace and log files and contact your IBMservice representative.

DWC15042N Cannot create FTP command filecommandfilename.

Explanation: The user-defined program createsa temporary FTP command file which beginswith the string ’UDPFTPCMD’. This file containsthe FTP commands without the user id and


password in the original command file. It isnormally created in the directory that theVWS_LOGGING environment variable points to,and is deleted at the end of the process. Theprogram could not create the temporary FTPcommand file.

User Response: Check to ensure that

v the VWS_LOGGING environment variable isset, and that the user has permission to writeto that directory

v the userid has access to the directory

v the directory has sufficient space

DWC15043N Error issuing FTP command

Explanation: The user-defined program issuedan FTP command, and FTP returned an error.

User Response: The FTP log file displays theFTP command and the response from FTP. Youcan find the FTP log file in the directory that theVWS_LOGGING environment variable points to.The file name begins with ″ftp″ and ends with″.log″.

DWC15044N Cannot open FTP command fileftpcommandfile.

Explanation: The user-defined program createsa temporary FTP command file which beginswith the string ’UDPFTPCMD’. This file containsthe FTP commands without the user id andpassword in the original command file. It isnormally created in the directory that theVWS_LOGGING environment variable points to,and is deleted at the end of the process. Theprogram created the temporary FTP commandfile but could not open it.

User Response: Check that the user id that isexecuting the FTP command has access to theFTP command file.

DWC15045N Userid/password not found ininput file inputfile.

Explanation: The input FTP command file didnot contain the user id and password as the firstvalues in the file.

User Response: Check that the user id andpassword are in the input FTP command file andretry.

DWC15046N Cannot remove local file localfile.

Explanation: The local spool file is the filewhere the warehouse places the job output . Thewarehouse deletes the local spool file beforeexecuting the job. The warehouse tried to removethe local spool file localfile and failed.

User Response: If the file localfile exists, delete itand then retry.

DWC15047N Cannot open message filemessagefile.

Explanation: The message file, also known asthe FTP log file, is in the directory that theVWS_LOGGING environment variable points to.The name of the file begins with ″ftmp″ and endswith .log. Opening the message file failed.

User Response: Check that the user id haspermission to open files in the VWS_LOGGINGdirectory, that the file exists, and that the userhas read access to the file.

DWC15048N FTP command must be GET orPUT.

Explanation: The FTP command passed as aparameter must be GET or PUT.

User Response: Check that the FTP command iseither GET or PUT.

DWC15049N Invalid FTP user id/password.

Explanation: The user id and password enteredwere rejected by the remote site.

User Response: Correct the user id and/orpassword and retry.

DWC15050N FTP connection failed.

Explanation: The program could not establishan FTP connection.

User Response: Verify that the hostname, user


id, and password provided to FTP are correct. Ifthe hostname, user id, and password are correct,do the following:

v Verify that ftp is the command used at yoursite to initiate an FTP session.

v Confirm that the FTP daemon process isrunning on the host.

v Issue the ping command from the agent site tothe host to verify that a TCP/IP connectionexists.

DWC15051N FTP transfer type must be 0(binary) or 1 (ascii).

Explanation: The value passed to the programas the FTP transfer type must be 0 or 1.

User Response: Check that the value passed tothe program as the FTP transfer type is either 0or 1.

DWC15052N Error calling API, return code =returncode.

Explanation: The call to the DB2 API was notsuccessful.

User Response: Please refer to the DB2documentation for the return code from the API.

DWC15053N Parameters are missing;parameters must include server,application, database, userid, andpassword.

Explanation: This message is received if someof the parameters are missing when theprogram/step is called. Explanation for theparameters:

v server - Essbase server name

v application - Essbase application name

v database - Essbase database name

v userid - userid to logon to Essbase server

v password - password to logon to Essbaseserver

User Response: Collect all trace and log files inthe logging directory and contact your IBMservice representative.

DWC15054N Parameters are missing;parameters must include server,application, database, userid,password, calcFile, 0/1.







v calcFile - calc file that the program needs

v 0/1 - 0=calc file on server, 1=calc file on local


DWC15055N Parameters are missing;parameters must includesourceFile, server, application,database, userid, password.


v sourceFile - source file that the program needs








DWC15056N Parameters are missing;parameters must include server,application, database, userid,password, sourceFile, 0/1,loadRuleFile, 0/1, 0/1.







v sourceFile - the source file that this programneeds

v 0/1 - 0=source file on server, 1=source file onlocal

v loadRuleFile - the rule file that this programneeds

v 0/1 - 0=rule file on server, 1=rule file on local

v 0/1 - 0=do not abort on errors, 1=abort onerrors


DWC15057N Parameters are missing;parameters must include: server,application, database, userid,password, DB2Userid,DB2Password, loadRuleFile, 0/1,0/1.







v DB2Userid - DB2 userid for the source table

v DB2Password - DB2 password for the sourcetable





DWC15058N Parameters are missing;parameters must include server,application, database, userid,password, sourceFile, 0/1, 0/1.












DWC15059N Parameters are missing;parameters must include server,application, database, userid,password, sourceFile, 0/1,loadRuleFile, 0/1.












DWC15060N Parameters are missing;parameters must include server,application, database, userid,password, Db2Userid,DB2Password, loadRuleFile, 0/1.







v DB2Userid - DB2 userid for the source table

v DB2Password - DB2 password for the sourcetable




DWC15061N Parameters are missing;parameters must includesourceDB, userid, password,targetFileName, selectStatement,[fileTypeModifier].


v sourceDB - source database name

v userid - userid

v password - password

v targetFileName - output file that will containthe exported data

v selectStatement - the select statement whichshould be enclosed in double quotes

v fileTypeModifier - the file type modifierstring(optional). For example ″coldel,″indicates that column must be separated bycomma.


DWC15062N Parameters are missing;parameters must includesourceConnectString,targetFileName, selectStatement,[colDelimeter].



v sourceConnectString - source connect string.Format:DSN=database;UID=userid;PWD=password

v targetFileName - output file that will containthe exported data

v selectStatement - the select statement whichshould be enclosed in double quotes

v colDelimeter - the column separation character(optional)


DWC15063N Parameters are missing;parameters must includeremoteSite and FTPCommandFile.


v remoteSite - The remote host to FTP to

v FTPCommandFile - the full path and file nameof the FTP command file


DWC15064N Parameters are missing;parameters must includeMVSHostName, MVSUserid,MVSPassword, JCLFile, localFile.


v MVSHostName - the host name on the MVSsystem

v MVSUserid - userid on the MVS system

v MVSUserid - userid on the MVS system

v JCLFile - the jcl to submit on the MVS system

v localFile - the full path and file name for theoutput file

User Response: Collect all trace and log files in

the logging directory and contact your IBMservice representative.

DWC15065N Parameters are missing;parameters must includeremoteSite, GETorPUT,remoteUserid, remotePassword,remoteFile, localFile.


v remoteSite - remote host name

v GETorPUT - the FTP get or put command

v remoteUserid - userid on the remote system

v remotePassword - password on the remotesystem

v remoteFile - the full path and file name for theremote file

v localFile - the full path and file name for thelocal file


DWC15066N Parameters are missing;parameters must includesourceFile, targetDB, targetUserid,targetPassword, targetTable,backupFileName,[fileTypeModifier].


v sourceFile - the source file

v targetDB - the target database to load the datato

v targetUserid - the userid on the target database

v targetPassword - the password on the targetdatabase

v targetTable - the table on the target database

v backupFileName - the full path and file namefor the backup file for recovery purpose


v fileTypeModifier - the file type modifier string(optional). For example ″coldel,″ indicates thatcolumn must be separated by comma.


DWC15067N Parameters are missing;parameters must includesourceFile, targetDB, targetUserid,targetPassword, targetTable,[fileTypeModifier].


v sourceFile - the source file

v targetDB - the target database to load the datato

v targetUserid - the userid on the target database

v targetPassword - the password on the targetdatabase

v targetTable - the table on the target database

v fileTypeModifier - the file type modifier string(optional). For example ″coldel,″ indicates thatcolumn must be separated by comma.


DWC15068N Parameters are missing;parameters must include database,userid, password, table.


v database - the database

v userid - the userid

v password - the password

v table - the table on the database


DWC15069N The number of parameters is notvalid.

Explanation: Parameters must be:

1. MVS Host Name

2. MVS User ID

3. JCL File Name on MVS (Full Name)

4. ETI Error File Name

5. ETI Message File Name

6. ETI Warning File Name

7. Password Type (EnterPassword orPasswordNotRequired)

8. Password

OR

1. MVS Host Name

2. MVS User ID





7. Password Type (EnterPassword orPasswordNotRequired)

8. Password

9. ’-’

10. Highest JES Return Code to ConsiderSuccess (Optional)

User Response: Correct the parameters andrestart the program.

DWC15070N The parameters are not valid.

Explanation: The parameters must include:

1. MVS Host Name

2. MVS User ID





7. Password Type (GetPassword)

8. Password Program

9. Password Program parameters


10. Highest JES Return Code to ConsiderSuccess (Optional)


DWC15071N The Copy File using FTP programcould not find the ″TransferComplete″ message.

Explanation: The Copy File using FTP programwas unable to find the ″Transfer Complete″message to determine if the transfer of the filewas successful.

User Response: Check the log file for moreinformation.

DWC15073N No batch file name supplied.

Explanation: HISEXNT executes a batch file thatruns an OLAP Integration Server script file tobuild an OLAP cube from an Integration Servermetaoutline. The batch file name must be passedin as a parameter, and was not supplied.

User Response: To invoke the program from thecommand line, use the command hisexnt“<filename>”, where filename is the name of thebatch file that executes the script. To invoke theprogram from the Data Warehouse Center,supply the file name as a parameter to theprogram.

DWC15074N Unable to run batch file.

Explanation: The name of a batch script file waspassed to the program hisexnt, but hisexnt wasunable to execute the script.

User Response: Determine the error in thescript file by executing it from the command line.Correct the error and retry.

DWC15075I Successfully completed buildingthe OLAP cube.

Explanation: The OLAP cube was successfullybuilt.

User Response:

DWC15076W Building of the OLAP cubecompleted with warnings. Checkthe OLAPISVR.LOG file on theOLAP Integration Server fordetails.

Explanation: The OLAP cube was built, butOLAPICMD returned warnings.

User Response: Check the OLAPISVR.LOG fileon the OLAP Integration Server server fordetails.

DWC15077N Building of the OLAP cubecompleted with errors. Check theOLAPISVR.LOG file on theOLAP Integration Server fordetails.

Explanation: The OLAPICMD command tobuild the cube returned errors.

User Response: Check the OLAPISVR.LOG fileon the OLAP Integration Server for details.

DWC15078N Unable to build OLAP cube.Check the OLAPISVR.LOG fileon the OLAP Integration Serverfor details.

Explanation: The OLAPICMD command tobuild the cube returned errors. The cube was notbuilt.

User Response: Check the OLAPISVR.LOG fileon the OLAP Integration Server for details.

DWC15079N Execution of the system commandfailed. The command was:command.

Explanation: The program failed to issue asystem() function.

User Response: Check the trace file in theVWS_LOGGING for more information.

DWC15080N The FTP command file path(pathname) format is invalid.

Explanation: The format for the path of the FTPcommand file is invalid.


User Response: Fix the path format. The correctformat is: \n library/file.member.

DWC15081N Parameters are missing;parameters must includesourceFile, targetTable,backupFileName,[fileTypeModifier].


v sourceFile - the source file.

v targetTable - the table on the target database.

v backupFileName - the full path and file namefor the backup file for recovery purposes.

v fileTypeModifier - the file type modifier string(optional). For example ″coldel,″ indicates thatthe column must be separated by a comma.

User Response: Collect all trace and log files inthe VWS_LOGGING directory and contact yourIBM service representative.

DWC15082N Parameters are missing;parameters must includesourceFile, targetTable,[fileTypeModifier].


v sourceFile - the source file.

v targetTable - the table on the target database.

v fileTypeModifier - the file type modifier string(optional). For example ″coldel,″ indicates thatthe column must be separated by a comma.

User Response: Collect all trace and log files inthe VWS_LOGGING directory and contact yourIBM service representative.

DWC15101N The number of parameters are notvalid.


1. Remote Host Name

2. Remote User ID

3. Remote Shell Script Name

4. Remote Error File

5. Remote Warning File

6. Remote Log File

7. Remote OS Type (UNIX or WinNT)

8. Password Type (EnterPassword orGetPassword)

9. Password Value (case EnterPassword)

OR

1. Remote Host Name

2. Remote User ID



5. Remote Warning File

6. Remote Log File


8. Password Program (case GetPassword)

9. Password Program Parameters

User Response: Fix the parameters and restartthe program.

DWC15102N The number of parameters are notvalid.


1. Remote Host Name

2. Remote User ID



5. Warning File

6. Remote Log File


8. Password Type (GetPassword)

9. Password Program (case GetPassword)

10. Password Program Parameters



DWC15103N The eighth parameter mustindicate a password type.

Explanation: The value for the password type isnot correct. The password types are :EnterPassword, PasswordNotRequired,GetPassword.

User Response: Enter the correct value for thepassword type and run the program again.

DWC15104N Could not generate local warningfile filename.

Explanation: An error occurred because theVWS_LOGGING variable was not set.

User Response: Check that VWS_LOGGINGenvironment variable is set.

DWC15105N Failed to create local log filefilename.

Explanation: The VWS_LOGGING environmentvariable is not set.

User Response: Set the environment variableVWS_LOGGING.

DWC15106N Cannot setup the FTP commandfile.

Explanation: An error occurred because theprogram could not create or open the FTPcommand file.

User Response: Check that the directory allowsfiles to be created and that the disk space issufficient. If the disk space is not sufficient,remove unnecessary files and restart theprogram.

DWC15107N Cannot create a temporary file tocopy the error file. Return code=ReturnCode.

Explanation: Operating system failed to createda unique file name. This error might be causedby too many temporary file names in thedirectory.

User Response: Check that there is sufficient

disk space in the directory. If the disk space isnot sufficient, remove unnecessary files andrestart the program.

DWC15108I ETI program ran successfully.

Explanation:

User Response:

DWC15400N Parameter count is incorrect.Check log file log-file for moreinformation.

Explanation: The OLAP Publish to InformationControl Center program was invoked without allrequired parameters.

User Response: Check the log file for adescription of the parameters that were used toinvoke the OLAP Publish to Information ControlCenter program, and a description of therequired parameters. Provide all requiredparameters from the Data Warehouse Centerpublish dialog or the command line.

DWC15401N Exception occurred while parsinginput parameters: exception-string.Check log file log-file for moreinformation.

Explanation: The OLAP Publish to InformationControl Center program was invoked withincorrect parameters.

User Response: Check the log file for adescription of the parameters that were used toinvoke the OLAP Publish to Information ControlCenter program, and a description of therequired parameters. Modify the invocationparameters from the Data Warehouse Centerpublish dialog or the command line to correctthe error.


DWC15402N Unknown exception occurredwhile parsing input parameters.Check log file log-file for moreinformation.

Explanation: The OLAP Publish to InformationControl Center program was invoked withincorrect parameters.

User Response: Check the log file for adescription of the parameters that were used toinvoke the OLAP Publish to Information ControlCenter program, and a description of therequired parameters. Modify the invocationparameters from the Data Warehouse Centerpublish dialog or the command line to correctthe error.

DWC15403N An information catalogadministrator is currently loggedon. Check log file log-file for moreinformation.

Explanation: The OLAP Publish to InformationControl Center program was unable to create ormodify object definitions in Information ControlCenter because an administrator is currentlyusing the system.

User Response: Restart the OLAP Publishaction after all Information Control Centeradministrators have logged off the InformationControl Center system.

DWC15404N Error occurred while opening tagfile tag-file. Check log file log-filefor more information.

Explanation: OLAP Publish to InformationControl Center program creates a tag file ofobject definitions to import into InformationControl Center. The program was unable tocreate or open the tag file.

User Response: Check that the OLAP Publish toInformation Control Center program hasauthorization to create or modify the tag fileshown in the message. Check the log file foradditional information.

DWC15405N Unexpected error error-code wasreceived from Essbase APIAPI-function. Check log file log-filefor more information.

Explanation: An unexpected error conditionoccurred while the OLAP Publish to InformationControl Center program was using the EssbaseAPI to obtain information about the OLAPoutline to publish to Information Control Center.

User Response: Check the log file for errorinformation. Check the OLAP Server and OLAPapplication logs for additional error information.Correct the error and restart the action.

DWC15406N Error error-code occurred whileactivating Essbase application anddatabase. Check log file log-file formore information.

Explanation: An unexpected error conditionoccurred while the OLAP Publish to InformationControl Center program was initializing theEssbase API environment. The OLAP Publish toInformation Control Center program uses theEssbase API to obtain information about theOLAP outlines to publish to Information ControlCenter.

User Response: Check the log file for errorinformation. Check the OLAP Server and OLAPapplication logs for additional error information.Correct the error and restart the action.

DWC15407N Unexpected error code error-codewas received while connecting toOLAP outline outline-name. Checklog file log-file for moreinformation.

Explanation: An unexpected error conditionoccurred while the OLAP Publish to InformationControl Center program was using the EssbaseAPI to connect to the OLAP outline. The OLAPPublish to Information Control Center programmust connect to the OLAP outline in order to usethe Essbase API to obtain information to publishto Information Control Center.

User Response: Check the log file for error


information. Check the OLAP Server and OLAPapplication logs for additional error information.Correct the error and restart the action.

DWC15408N Unexpected error occurred whileopening file file-name of OLAPoutlines to publish . Check logfile log-file for more information.

Explanation: The Publish OLAP to InformationControl Center program is invoked with aparameter that identifies a control file of OLAPoutlines to publish. The program was unable toopen this control file to obtain the names of theoutlines to publish.

User Response: Check the log file for errorinformation. Check that the Publish OLAP toInformation Control Center program hasauthorization to open and read the control file.

DWC15409N Unexpected error occurred whileimporting tag file tag-file intoInformation Control Center.Check VWP log file dwc-log andInformation Control Center logfile icc-log for more information.

Explanation: The Publish OLAP to InformationControl Center program generates a tag file ofobject definitions to import into InformationControl Center. An unexpected error occurredimporting this tag file into Information ControlCenter.

User Response: Check the log files for errorinformation. Correct the error and restart theaction.

DWC15410I OLAP definitions weresuccessfully imported intoInformation Control Center.Check log file dwc-log andInformation Control Center logfile icc-log for more information.

Explanation: The Publish OLAP to InformationControl Center program generates a tag file ofobject definitions to import into InformationControl Center. The tag file was successfullyimported into Information Control Center.

User Response: The OLAP outlines weresuccessfully imported into Information ControlCenter. Check the Information Control Centerand Data Warehouse Center publish logs formore information about the information that wasimported into Information Control Center.

DWC15411N Unable to set current directory asspecified by VWS_LOGGINGenvironment variable: vws-logging.System error code is error-code.

Explanation: The Publish OLAP to InformationControl Center program creates files in adirectory specified by the VWS_LOGGINGenvironment variable. The Publish OLAP toInformation Control Center program was unableto set the current directory to the value specifiedby system environment variableVWS_LOGGING.

User Response: Check that the VWS_LOGGINGenvironment variable is defined at the systemlevel to point to a directory for which thePublish OLAP to Information Control Centerprogram has write access.

DWC15412I Information Catalog Import actionof OLAP tag file was startedsuccessfully. Check log file dwc-logand Information Control Centerlog file icc-log for moreinformation.

Explanation: The OLAP Publish to InformationControl Center program started the InformationCatalog Import action of a tag file containingOLAP definitions. Check the log files forinformation about the success or failure of theaction.

User Response: Check the log files forinformation about the import action.


DWC15413N The Information Catalog Importaction of the OLAP tag file wasnot started successfully. Check logfile dwc-log and InformationControl Center log file icc-log forinformation about why the actionfailed.

Explanation: The OLAP Publish to InformationControl Center program encountered an errorwhen it tried to start the Information ControlCenter Import action to import the generated tagfile of OLAP definitions.

User Response: Check the log files forinformation about why the action failed. Checkthat the system PATH and CLASSPATHenvironment variables are set correctly to run theInformation Control Center Import program.

DWC15414N Specified information catalog userIDuserid or password password wasnot valid. Check log file log-file formore information.

Explanation: The Publish OLAP to InformationControl Center program attempted to connect tothe Information Control Center database with aninvalid user ID or password. The Publishprogram must read or update entries in theEXCHANGE table in the Information ControlCenter database to manage the list ofmultidimensional database objects to update inthe Information Control Center.

User Response: Specify a valid user ID andpassword for connecting to the InformationControl Center database and start the actionagain.

DWC15415W No OLAP database objects werefound in the Information ControlCenter EXCHANGE table indatabase database using schemaschema. No OLAP objects havebeen updated in the InformationControl Center. Check log filelog-file for more information.

Explanation: The Publish OLAP to InformationControl Center program reads rows from the

EXCHANGE table in the Information ControlCenter database to identify multidimensionaldatabase objects to update. No entries werefound in the EXCHANGE table. No objects wereupdated in the Information Control Center.

User Response: Confirm that the correctdatabase and schema names were specified. Usethe Data Warehouse Center OLAP Publish toInformation Control Center dialog to specifymultidimensional database objects to publish.

DWC15416N Unknown Information ControlCenter database database orschema schema was specified.Check log file log-file for moreinformation.

Explanation: The Publish OLAP to InformationControl Center program attempted to connect toan unknown Information Control Centerdatabase. The Publish program must read orupdate entries in the EXCHANGE table in theInformation Control Center database to managethe list of multidimensional database objects toupdate in the Information Control Center.

User Response: Specify valid InformationControl Center database and schema names andstart the action again.

DWC15417N Unknown error error-code wasreceived while connecting to theInformation Control Centerdatabase. Check log file log-file formore information.

Explanation: The Publish OLAP to InformationControl Center program was unable to connect tothe Information Control Center database. ThePublish program must read or update entries inthe EXCHANGE table in the Information ControlCenter database to manage the list ofmultidimensional database objects to update inthe Information Control Center.

User Response: Use the IBM DB2 UniversalDatabase on-line help or the Message Referenceto find an explanation for the error code. Correctthe problem that corresponds to the error codeand try again.


DWC15418N Error code error-code was receivedwhile opening EXCHANGE tablein database database using schemaschema. Check log file log-file formore information.

Explanation: The Publish OLAP to InformationControl Center program was unable to connect tothe Information Control Center database. ThePublish program must read or update entries inthe EXCHANGE table in the Information ControlCenter database to manage the list ofmultidimensional database objects to update inthe Information Control Center.


DWC15419N Error code error-code was receivedwhile reading the EXCHANGEtable in database database usingschema schema. Check log filelog-file for more information.

Explanation: The Publish program must read orupdate entries in the EXCHANGE table in theInformation Control Center database to managethe list of multidimensional database objects toupdate in the Information Control Center. Anerror occurred while the program was readingfrom the EXCHANGE table.


DWC15420N Error code error-code was receivedwhile updating the EXCHANGEtable in database database usingschema schema. Check log filelog-file for more information.

Explanation: The Publish program must read orupdate entries in the EXCHANGE table in theInformation Control Center database to managethe list of multidimensional database objects to

update in the Information Control Center. Anerror occurred while the program was readingfrom the EXCHANGE table.


DWC15501W Could not trace because the logfile could not be opened.

Explanation: Cannot open the log file fortracing the execution of this program.

User Response: Verify that the dwcsmp.log filecan be opened in the DB2 samples directory inSQLLIB.

DWC15502N Cannot start database manager,rc=returncode, sqlcode=sqlcode.

Explanation: An error was returned by thedatabase manager while attempting to start.

User Response: Check the code returned by theDB2 database manager.

DWC15503N Cannot create databasedatabasename, rc=returncode.

Explanation: An error was returned whileattempting to create the listed database.

User Response: Check the code returned by theDB2 database manager.

DWC15504W Database databasename notregistered with ODBC.

Explanation: An attempt to automaticallyregister the database with ODBC failed.

User Response: Register the database withODBC.

DWC15505E Cannot connect to databasedbname, rc=returncode.

Explanation: Cannot connect to the database orcreate tables in the database.


User Response: Check that the user ID andpassword are correct.

DWC15506N Cannot import sample data intodatabase databasename,rc=returncode.

Explanation: Cannot import sample data usingthe Data Warehouse Center import function.


DWC15507N Cannot allocate a SQL handle fordatabase databasename,rc=returncode.

Explanation: A failure occurred while setting upthe ODBC environment for the database.

User Response: Check the code returned fromthe DB2 database manager.

DWC15508N Cannot create sample tabletablename in database databasename,rc=returncode.

Explanation: Cannot create table for sampledata.


DWC15509N Cannot load data into tabletablename in database databasename,rc=returncode.

Explanation: Cannot load data into the table forsample data.


DWC15510N An internal error occurred whilecreating sample data. Check thetrace file.

Explanation: An internal error occurred whilecreating the sample data. Check the trace file if itis active for further information.

User Response: Restart the function with the

trace option.


Chapter 11. ICC Messages

This section contains a list of messages issued by the Information CatalogCenter. The messages are listed in numeric sequence.

ICM00001N An SQL error occurred whileconnecting to the database.Database = databasename, Catalog =catalogname.

Explanation: An SQL error occurred when theAPI attempted to open a connection to thedatabase.

User Response: Consult the Message Referencefor more information on this SQL error.

ICM0002N An SQL error occurred whileregistering applicationapplicationname.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toregister the specified application.

User Response: Check the Message Referencefor more information on this SQL error.

ICM0003N An SQL error occurred whilesearching for objects.

Explanation: An SQL error occurred while theInformation Catalog Manager API wasperforming a search of the IBM DB2 UniversalDatabase tools catalog.

User Response: Check the Message Referencefor more information about this SQL error.

ICM0004N An SQL error occurred whileaccessing the Information CatalogManager API settings for theapplication applicationname.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toretrieve the settings for the application.


ICM0005N An SQL error occurred whileretrieving the user and groupinformation from the database.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toretrieve information about users and groupsfrom the database.


ICM0006N An SQL error occurred whileloading the list of registeredapplications.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toretrieve the list of applications.


ICM0007N An SQL error occurred whileretrieving the application ID forthe application applicationname.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toretrieve the application ID for the specifiedapplication.



ICM0008N An SQL error occurred whileloading an object type.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted toretrieve an object type definition from the IBMDB2 Universal Database tools catalog.


ICM0009N An SQL error occurred whilecreating object type objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingthe specified object type.


ICM0010N An SQL error occurred whileupdating the object type objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was updatingthe specified object type.


ICM0011N An SQL error occurred whiledeleting object type objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deletingthe specified object type.


ICM0012N An SQL error occurred whileretrieving a reference ID forobject type objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was retrievingthe next available reference ID for the specifiedobject type.


ICM0013N An SQL error occurred whileloading an object instance fromthe IBM DB2 Universal Databasetools catalog.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe data for an object instance from the DB2Universal Database tools catalog.


ICM0014N An SQL error occurred whilecreating instance instancename ofobject type objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingan object instance in the IBM DB2 UniversalDatabase tools catalog.


ICM0015N An SQL error occurred whileupdating an instance of objecttype objecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was updatingan object instance in the IBM DB2 UniversalDatabase tools catalog.


ICM0016N An SQL error occurred whiledeleting an instance of object typeobjecttype.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deletingan object instance from the IBM DB2 UniversalDatabase tools catalog.



ICM0017N An SQL error occurred whileloading property propertyname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe value for the specified object instanceproperty.


ICM0018N An SQL error occurred whileloading a relationship category.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loading arelationship category from the IBM DB2Universal Database tools catalog.


ICM0019N An SQL error occurred whilecreating relationship categorycategoryname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingthe relationship category in the IBM DB2Universal Database tools catalog.


ICM0020N An SQL error occurred whileupdating relationship categorycategoryname.

Explanation: An SQL error occurred while theInformation Catalog Manger API was updatingthe relationship category in the IBM DB2Universal Database tools catalog.


ICM0021N An SQL error occurred whiledeleting relationship categorycategoryname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deleting

the relationship category from the IBM DB2Universal Database tools catalog.


ICM0022N An SQL error occurred whileloading a relationship type.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loading arelationship type from the IBM DB2 UniversalDatabase tools catalog.


ICM0023N An SQL error occurred whilecreating relationship typetypename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingthe relationship type in the IBM DB2 UniversalDatabase tools catalog.


ICM0024N An SQL error occurred whileupdating relationship typetypename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was updatingthe relationship type in the IBM DB2 UniversalDatabase tools catalog.


ICM0025N An SQL error occurred whiledeleting relationship typetypename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deletingthe relationship type from the IBM DB2Universal Database tools catalog.


Chapter 11. ICC Messages 447

ICM0026N An SQL error occurred whileloading a relationship instance.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe information for a relationship instance fromthe IBM DB2 Universal Database tools catalog.


ICM0027N An SQL error occurred whilecreating an instance forrelationship type typename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingan instance of the relationship type in the IBMDB2 Universal Database tools catalog.


ICM0028N An SQL error occurred whileupdating an instance ofrelationship type typename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was updatingan instance of the relationship type in the IBMDB2 Universal Database tools catalog.


ICM0029N An SQL error occurred whiledeleting an instance ofrelationship type typename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deletingan instance of the relationship type from the IBMDB2 Universal Database tools catalog.


ICM0030N An SQL error occurred whilecommitting changes on thecontext.

Explanation: An SQL error occurred while theInformation Catalog Manager API wasattempting to commit a context to the database.


ICM0031N An SQL error occurred whilerolling back changes on thecontext.

Explanation: An SQL error occurred while theInformation Catalog Manager API attempted torollback a context to the database.


ICM0032N An SQL error occurred whilereleasing the context.

Explanation: An SQL error occurred while theInformation Catalog Manager API was releasinga context.


ICM0033N An SQL error occurred whileaccessing the context’s connectionproperties.

Explanation: An SQL error occurred while theInformation Catalog Manager API was accessingthe database connection details for a context.


ICM0034N An SQL error occurred whilecancelling a search operation.

Explanation: An SQL error occurred while theInformation Catalog Manager API wasprocessing a user request to cancel a searchoperation

User Response: Check the Message Reference


for more information on this SQL error.

ICM0035N An SQL error occurred whileloading an access control list.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadinginformation in an access control list from theIBM DB2 Universal Database tools catalog.


ICM0036N An SQL error occurred whileupdating access control listaccesslistname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was updatingthe access control list in the IBM DB2 UniversalDatabase tools catalog.


ICM0037N An SQL error occurred whileaccessing the data of Blobproperty propertyname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe data for the specified Blob property.


ICM0038N An SQL error occurred whileretrieving the version informationof the IBM DB2 UniversalDatabase tools catalog.

Explanation: An SQL error occurred while theInformation Catalog Manager API queried thedatabase for the version information of thedatabase engine and the DB2 Universal Databasetools catalog.


ICM0039N An SQL error occurred whileretrieving the access controlentries for an object.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe access control data for an object.


ICM0040N An SQL error occurred whilecreating access control listaccesslistname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was creatingthe access control list in the IBM DB2 UniversalDatabase tools catalog.


ICM0041N An SQL error occurred whiledeleting access control listaccesslistname.

Explanation: An SQL error occurred while theInformation Catalog Manager API was deletingthe access control list from the IBM DB2Universal Database tools catalog.


ICM0042N An SQL error occurred whilelocking object type typename.

Explanation: An SQL error occurred while theInformation Catalog Manager API was lockingthe object type to prevent access by otherapplications.


ICM0043N An SQL error occurred whileloading an object ID.

Explanation: An SQL error occurred while theInformation Catalog Manager API was loadingthe ID for an object instance from the IBM DB2


Universal Database tools catalog.


ICM0100N Unable to connect to the IBM DB2Universal Database tools catalog.Database = databasename, Catalog =catalogname).

Explanation: Incorrect values were provided forthe database or catalog names.

User Response: Provide valid values for thedatabase and catalog. The database name mustrefer to a database that has been cataloged on thesystem where the Information Catalog ManagerAPI is being run. The catalog name must refer tothe schema inside the database used to hold theDB2 Universal Database tools catalog.

ICM0101N This catalog object is alreadyconnected to an IBM DB2Universal Database tools catalog.

Explanation: Failed to open a connection to aDB2 Universal Database tools catalog using acatalog object that already had an openconnection.

User Response: Check that the catalog object isnot already open.

ICM0102N Schema schemaname in databasedatabasename does not contain avalid IBM DB2 UniversalDatabase tools catalog. Tabletablename’ was not found.

Explanation: Unable to find the required tabletablename while the catalog opened a connectionto the DB2 Universal Database tools catalog,

User Response: Check that the schema anddatabase names are correct, and that a DB2Universal Database tools catalog has beencreated for schema schemaname.

ICM0103N Incorrect arguments provided toorphan relationship search.

Explanation: The emptySource and emptyTargetparameters to the orphanRelationships( Context,Object, Collection, Collection, boolean, bJoolean,SearchRules ) method of the Catalog object wereboth false, which is incorrect.

User Response: One or both of the parametersemptySource and emptyTarget must be true.

ICM0104N applicationname is a reservedapplication name.

Explanation: The application nameapplicationname is reserved for use by theInformation Catalog Manager API.

User Response: Use a different name for theapplication name.

ICM0105N Application applicationname isalready registered.

Explanation: An application namedapplicationname has been previously registeredwith the Information Catalog Manager API.

User Response: Register the application using adifferent name or use the existing registeredapplication ID.

ICM0106N Application applicationname hasnot been registered.

Explanation: An attempt was made to use anunregistered application name for an application.

User Response: Register the application namebefore using it or use the name of an applicationthat has already been registered.

ICM0107N An application must be associatedwith the catalog object before theIBM DB2 Universal Databasetools catalog can be accessed.

Explanation: Attempted to access the DB2Universal Database tools catalog beforeassociating an application with the catalog object.


User Response: Associate an application withthe catalog object using the setApplicationName(String ) method of the catalog class before usingthe catalog object to access the DB2 UniversalDatabase tools catalog.

ICM0108N Unable to close catalog whilecontexts remain unreleased.

Explanation: One or more contexts were in anunreleased state while the close method of acatalog object was called.

User Response: Release all contexts openedagainst a catalog before closing the catalog.

ICM0109N Incorrect constraint objectencountered while savingconstraints.

Explanation: An I/O error occurred whilepreparing a constraint to be saved to thedatabase.

User Response: Check that the constraint objectis Serializable.

ICM0110N Incorrect constraint objectencountered while loadingconstraints.

Explanation: An I/O error occurred whilerecreating a constraint from the data stored inthe IBM DB2 Universal Database tools catalog.

User Response: Contact you IBM servicerepresentative.

ICM0111N Cannot register applicationapplicationname. No IDs areavailable.

Explanation: There are 63 available applicationIDs. Attempted to register a 64th application.

User Response: Remove any registeredapplications that are no longer being used withthis IBM DB2 Universal Database tools catalogand contact your IBM service representative.

ICM0112N Incorrect arguments provided togetACEsForPrincipal( Context,String, boolean, Collection )method.

Explanation: The value for the principal or thecollection of object types to retrieve accesscontrol entries was null.

User Response: Specify non-null values for theprincipal and the collection of object types.

ICM0113N Incorrect arguments provided togetObjectsOwnedByUser( Context,String, Collection) method.

Explanation: The value was null for the user orthe Collection of object types to retrieve theowned objects.

User Response: Specify non-null values for boththe user and the Collection of object types.

ICM0200N The setProperties( Collection )method of an object type cannotbe used after the object type hasbeen created.

Explanation: Attempted to use thesetProperties( Collection ) method on an objecttype that has already been created in the IBMDB2 Universal Database tools catalog.

User Response: Use the addProperty(MetadataPropertyDefinition ) method to addnew properties individually or create a newobject type.

ICM0201N System property propertynamemust be specified when settingthe properties of this object type.

Explanation: The system property propertynamewas not in the list of properties provided to thesetProperties( Collection ) method.

User Response: The list of properties providedto the setProperties( Collection ) method mustinclude all of the system properties.


ICM0202N Property propertyname is in use byindex indexname of object typetypename. The property must bespecified when setting the list ofproperties for the object type.

Explanation: The property propertyname mustremain in the set of properties for the object typebecause the property is being used by an index.

User Response: Remove the property from thespecified index, remove the index, or add theproperty to the set of properties for the objecttype.

ICM0203N Object object is not a metadataproperty object.

Explanation: An incorrect object was found inthe set of properties being assigned to an objecttype.

User Response: The set of properties providedto setProperties( Collection ) must contain onlyMetadataPropertyDefinition objects. Remove anyobjects that are of a different type.

ICM0204N Duplicate property namedpropertyname was found in list.

Explanation: A call to setProperties( Collection )had multiple property objects with the samename.

User Response: Remove or rename anyproperties with duplicate names.

ICM0205N No property definition namedpropertyname exists for this objecttype.

Explanation: A call to getProperty( String ) wasmade using a property that is not defined for theobject type.

User Response: Use the getProperties() methodto retrieve all properties if the name of a specificproperty is not known.

ICM0206N An object type named typenamealready exists in the datastore.

Explanation: Attempted to create or rename anobject type with an existing name.

User Response: Chose a unique name for thenew object type.

ICM0207N Unable to delete object typetypename while it has objectinstances defined.

Explanation: Attempted to delete an object typewith instances defined without selecting thedelete instances option.

User Response: Delete all of the instancesbefore deleting an object type or use the deleteinstances option of the delete( boolean ) methodof the object type.

ICM0208N Cannot use the setTableOptions(String) method of an object typeafter the object type has beencreated.

Explanation: Attempted to modify the tableoptions clause after the object type was created.The table options clause can only be used whencreating the table.

User Response: Set the desired table optionsbefore creating the object type.

ICM0209N The setSchemaName( String)method of an object type cannotbe used after the object type hasbeen created.

Explanation: Attempted to modify the schemafor the object instance table after the object typehas been created.

User Response: Set the desired schema beforecreating the object type.


ICM0210N Property propertyname specified forindex indexname is not a propertyof object type typename.

Explanation: An index provided to the objecttype contained one or more properties that donot belong to the object type.

User Response: Check that all properties in anindex are the correct property definition objectsdefined for an object type. Use thegetProperties() and getProperty( String ) methodsto retrieve the correct property definition objects.

ICM0211N The type of object instanceinstancename does not match objecttype (typename).

Explanation: One of the object instancesprovided did not match the createObjects(Context, Collection ) method object type.

User Response: The createObjects( Context,Collection ) method can only handle objectinstances that are of the same object type.

ICM0212N String searchcriteria is an invalidsearch criteria for the nameproperty.

Explanation: Failed to search object instances byname because the name parameter provided wasnot a value.

User Response: The name parameter cannot benull.

ICM0213N An incorrect query filter objectwas provided to thegetObjectInstances( Context,Object, QueryFilterObject,SearchRules, boolean ) method ofan object type.

Explanation: The query filter object was eithernull or was for a different object type than theone it was passed to.

User Response: Define a query filter object forthe object type that is being searched.

ICM0214N The list of object types is notvalid.

Explanation: A list of object types provided toone of the Information Catalog Manager APImethods was not valid. The object type list waseither null or empty.

User Response: Check that the list of objecttypes contains at least one object type.

ICM0215N The data type specified whilecreating a property definitionobject was not valid.

Explanation: The value specified did notidentify one of the allowed data types.

User Response: Check that the value for thedata type is a data type constant defined in theMetadataPropertyDefinition class.

ICM0216N Index indexname of object typetypename is not valid.

Explanation: An index provided to the objecttype typename did not have any propertiesdefined.

User Response: The index must have at leastone property specified.

ICM0217N Property propertyname is definedmultiple times in index indexnameof object type typename.

Explanation: An index provided to the objecttype typename has the same property definedmultiple times.

User Response: Remove all duplicate propertiesfrom the index.

ICM0218N Index indexname does not exist forobject type typename.

Explanation: Object type typename could notgrant a request to remove index indexnamebecause an index with that name does not exist.

User Response: Check that the index is defined


for the object type before attempting to removeit.

ICM0219N An index with the name indexnameis already defined for object typetypename.

Explanation: An index with the specified namehas already exists. Index names must be unique.

User Response: Chose a unique name for thenew index, or remove the existing one to replaceit with the new one.

ICM0220N Index duplicatename duplicates thedefinition of index indexname ofobject type typename.

Explanation: An index already exists with therequested definition for the object type.

User Response: Either modify the new index tomake it different than all existing indexes, or justuse the existing indexes if they provide sufficientindexing for the object type.

ICM0300N The requested object instance wasnot found in the datastore.

Explanation: Attempted to load the value of aproperty for an object instance that has not beencreated in the datastore.


ICM0301N A property update requestviolates property constraintconstraintname.

Explanation: The operation cannot beperformed because constraint constraintname doesnot allow it.

User Response: Choose a value allowed by theconstraint or remove the constraint from theproperty definition.

ICM0302N The object type has already beenset for this instance.

Explanation: Attempted to set the object typefor an instance that already had a type defined.

User Response: Instances that already have atype defined cannot have their type changed.

ICM0303N The specified object type is notvalid.

Explanation: The object type provided to theobject instance setType( ObjectType ) method isnot valid. The object type is either null or has notyet been created.

User Response: Check that the object typepassed to the setType(ObjectType) method hasbeen created.

ICM0304N No property named propertynameexists for this object instance.

Explanation: Attempted to retrieve a propertythat does not exist.

User Response: Check the spelling of theproperty name and that the case matches. Usethe getProperties() method to get a list of alldefined properties.

ICM0305N The object instance is not in avalid state.

Explanation: The object instance is not able tohandle requests for data or updates because it isnot valid.

User Response: Reload the object instance fromthe IBM DB2 Universal Database tools catalog. Ifit is a new instance check that an object type isset.

ICM0306N A name is required for the objectinstance.

Explanation: The object instance is not validbecause the name has not been set.

User Response: Provide a non-null value forthe name property of the object instance.


ICM0307N Property propertyname is not valid.

Explanation: The object instance is not validbecause the property value is null when theproperty is required or the property valueviolates one of the property constraints.

User Response: Provide a valid value for thespecified property.

ICM0308N The current application does nothave permission to update thisobject.

Explanation: The current application is not theowning application and does not haveapplication update authority on the specifiedobject.

User Response: Use the owning application togrant authority to the current application.

ICM0309N Property propertyname does notbelong to this object instance.

Explanation: Attempted to load a propertyvalue to an incorrect object instance.


ICM0310N The value for propertypropertyname exceeds the propertydefinition’s maximum length.

Explanation: The property value is longer thanthe maximum size allowed by the object type’sproperty definition.

User Response: Use a smaller property value.

ICM0311N Property propertyname must have avalue.

Explanation: The property propertyname isrequired but is set with a null value.

User Response: Set the property with anon-null value.

ICM0312N Property propertyname violatesconstraint constraintname.

Explanation: The value assigned to propertypropertyname is not allowed by constraintconstraintname.

User Response: Use a value that is allowed bythe constraint or remove the constraint from theproperty definition.

ICM0400N The list of relationship objects isnot valid.

Explanation: The list of relationship objects isnull or empty.

User Response: Check that the list ofrelationship objects contains at least onerelationship.

ICM0401N Adding the specified relationshipwould result in a loop in therelationship category tree.

Explanation: The requested change wouldresult in a relationship category containing itself.

User Response: Check that there are no loops inthe hierarchy of relationships.

ICM0402N The relationship categorycategoryname already exists.

Explanation: Failed to create a new relationshipcategory because the category had the samename as an existing category.

User Response: Use a unique name for the newrelationship category.

ICM0403N The relationship type typenamealready exists.

Explanation: Failed to create a new relationshiptype because the type had the same name as anexisting type. Failed to create a new relationshiptype because the type had the same name as anexisting type.

User Response: Use a unique name for the newrelationship type.


ICM0404N Unable to delete relationship typetypename because there arerelationship instances defined forit.

Explanation: Relationship types cannot bedeleted if relationship instances of that type exist.

User Response: Delete all instances of therelationship type before deleting the type or usethe delete instances option of the relationshiptype delete method.

ICM0405N The ObjectType being added totheObjectTypeRelationshipConstrainthas not been created.

Explanation: The relationship constraintattempted to use an object type that has not yetbeen created in the database.

User Response: Call the create() method of theobject type before using it in a relationshipconstraint.

ICM0500N The object passed to therelationship instance is not valid.All objects must beObjectInstance or ObjectIDobjects.

Explanation: The type of an object provided asa source or target to a relationship instance wasnot one of the allowed types.

User Response: Use only ObjectInstance orObjectID objects as sources and targets forrelationship instances.

ICM0501N An object instance must becreated in the database before itcan be added to a relationship.

Explanation: An object instance that has not yetbeen created in the database cannot be assignedto any relationships.

User Response: Call the create() method onnew object instances before attempting to addthem to a relationship.

ICM0502N Unable to add a null ObjectID torelationship.

Explanation: The Java object representing theObjectID that was provided to the relationshipobject was null.

User Response: Use a non-null value for theObjectID.

ICM0503N The relationship instance violatesone or more constraints.

Explanation: One or more of the relationshipinstance constraints were violated by the currentset of source and target objects defined for theinstance.

User Response: Check the defined constraintsand add or remove sources or targets as needed.

ICM0504N The relationship instance is not ina valid state.

Explanation: The relationship instance is in anunusable state.

User Response: Check that the relationship typefor the instance exists and that none of theconstraints are violated. Then reload therelationship instance from the database.

ICM0600N The current user does not havepermission to update this object.

Explanation: Failed to update an object becausethe user does not have sufficient authority.

User Response: The object’s owner must grantpermission to users before they can update theobject.

ICM0601N The current user does not havepermission to delete this object.

Explanation: Failed to delete an object becausethe user does not have sufficient authority.

User Response: The object owner must grantusers permission to delete the object.


ICM0602N The current user does not havepermission to delete one of theinstances of this relationship type.

Explanation: The current user is unable todelete a relationship type and its instancesbecause the user does not have authority todelete one of the instances.

User Response: User needs the authority todelete all the instances of a relationship type inorder to delete the relationship type.

ICM0603N A name must be specified for theaccess control list before it can besaved.

Explanation: Failed to update an access controllist because the name has been set to null.

User Response: Check that the access controllist has a valid name.

ICM0604N An access control list namedaccesslistname already exists in thedatastore.

Explanation: The new access control list cannotbe created because it has the same name as anexisting access control list.

User Response: Specify a unique name for thenew access control list.

ICM0605N An access control list namedaccesslistname is not valid.

Explanation: The access control list cannot besaved because it is no longer valid.

User Response: Reload the access control listfrom the IBM DB2 Universal Database toolscatalog.

ICM0700N The data for this object has beenmodified in the IBM DB2Universal Database tools catalogby a different process.

Explanation: Failed to update an object becausea different process modified the object datastored in the tools catalog while the object was in

use by the current process.

User Response: Reload the object from the toolscatalog or use the overwrite setting on theupdate method.

ICM0701N Object does not exist.

Explanation: Information Catalog Manager APIrequest failed because it attempted to use anobject that has not been created in the IBM DB2Universal Database tools catalog.

User Response: Call the create method of theobject before using the method.

ICM0702N Object already exists.

Explanation: The create method was called onan object that has already been created.

User Response: Use the update method ratherthan the create method to update objects thatalready exist.

ICM0703N Object is not in a valid state.

Explanation: The object cannot be created orupdated because it is not in an valid state.

User Response: Reload the object from the IBMDB2 Universal Database tools catalog.

ICM0704N Duplicate request ID idnamepassed to search method.

Explanation: The request ID provided to asearch method is already in use by a differentsearch.

User Response: Use a different request ID orwait for the already running search to finish.

ICM0705N Cannot switch to a null Context.

Explanation: The context for an InformationControl Center object cannot be set to null.

User Response: Specify a non-null value to thesetContext( Context ) method of the InformationControl Center object.


ICM00706N Cannot switch to a new contextwhile a transaction is pending onthe existing context.

Explanation: Attempted to switch the context ofan object while there was an active transactioninvolving the object.

User Response: Commit the current contextchanges to the object before switching to adifferent context.

ICM0707N Cannot switch to a context in adifferent catalog.

Explanation: Attempted to switch the context ofan object to a context opened against a differentcatalog.

User Response: Use only contexts and objectsfrom the same catalog.

ICM0708N An access control entry alreadyexists for specified principal(principalname).

Explanation: A new access control entry cannotbe created for the specified principal because onealready exists.

User Response: Retrieve the current accesscontrol entry and modify it. Do not create a newaccess control entry.

ICM0709N The context provided to access thedatastore is not valid.

Explanation: The context provided to theInformation Catalog Manager API is not valid.Cannot perform the requested operation.

User Response: Check that the context is notnull and has not been released.

ICM0710N An incorrect parameter type wasencountered in the parameterizedSQL statement: sqlstatement.

Explanation: The type of an object parameterthat was provided is not valid.

User Response: Use only objects of the types

specified in the documentation for theInformation Catalog Manager API method.

ICM0711N Permission value for thePermissionElement is not valid.

Explanation: The permission is not valid withthe current value in setPermission( int, Jboolean).

User Response: Set permissions using thepermission element constants defined in thePermissionElement class.

ICM00712N Incorrect number of values wereprovided to the query filtercondition. No parameters wereexpected.

Explanation: The number of parametersprovided for a query filter condition does notmatch the number expected for the operator ofthe condition.

User Response: Provide the correct number ofparameters. No parameters are allowed forOP_IS_NULL and OP_IS_NOT_NULL. Twoparameters are required for OP_BETWEEN andOP_NOT_BETWEEN. Any number of parametersgreater than zero are allowed for OP_IN andOP_NOT_IN. One parameter is required for allother operators.

ICM0713N Number of values provided to thequery filter condition was notvalid. One parameter wasexpected.




ICM0714N Number of parameters providedto the query filter condition wasnot valid. Two parameters wereexpected.



ICM0715N Type specified for relationshipsearch is not valid.

Explanation: The value of the type specified tothe setType( int ) method of a relationship searchis not valid.

User Response: Use the TYPE_SOURCE andTYPE_TARGET constants defined in theRelationshipSearch class for the setType( int )method.

ICM0716N Relationship specified forrelationship search is not valid.

Explanation: The relationship specified for arelationship search object was null.

User Response: Use a non-null value for therelationship of a relationship search.

ICM0717N The access control list for thisobject has not been created.

Explanation: Must create the access control listassigned to an object before the object can besaved to the IBM DB2 Universal Database toolscatalog.

User Response: Call the create method on theaccess control list.

ICM0718N The context has been released andcannot be used.

Explanation: Attempted to use a releasedcontext to access the IBM DB2 UniversalDatabase tools catalog.

User Response: Use the newContext() methodon the catalog object to retrieve a new contextand use it in place of the released one.

ICM0800N Specified a migration operationtype that was not valid.

Explanation: The value of the operation typespecified to the ICMMigration migrate( int )method was not a valid migration operationtype.

User Response: Use one of the migrationoperation types defined in the ICMDatastoreInitclass (MIG_REPLACE, MIG_SKIP orMIG_ERROR).

ICM0801N The definition of the propertypropertyname of the IBM DB2Universal Database Version 7object type typename beingmigrated is different than theexisting property definition forthe DB2 Universal DatabaseVersion 8 object type.

Explanation: An object type being migratedalready exists in the DB2 Universal DatabaseVersion 8 tools catalog. One of the properties ofthe object type differs in either data type or sizebetween the DB2 Universal Database Version 7and Version 8 object type definitions.

User Response: Use the replace migrationoperation type or delete the existing DB2Universal Database Version 8 object type beforemigrating the DB2 Universal Database Version 7catalog.


ICM0802N The property propertyname of theIBM DB2 Universal DatabaseVersion 8 object type typenamedoes not exist in the DB2Universal Database Version 7object type of the same namebeing migrated.

Explanation: An object type being migratedalready exists in the DB2 Universal DatabaseVersion 8 tools catalog, but one of the propertiesof the existing DB2 Universal Database Version 8object type does not exist in the DB2 UniversalDatabase Version 7 object type definition.

User Response: Run the migration using adifferent operation type than MIG_ERROR ordelete the existing DB2 Universal DatabaseVersion 8 object type before running themigration.

ICM0803N The property propertyname for theIBM DB2 Universal DatabaseVersion 7 object type typenamedoes not exist in the DB2Universal Database Version 8object type of the same name.

Explanation: The object type being migratedexists in the DB2 Universal Database Version 8tools catalog, but one of the object type’sproperties being migrated from DB2 UniversalDatabase Version 7 does not exist in the DB2Universal Database Version 8 object typedefinition.

User Response: If the missing property isoptional, use the Information Catalog Centerinitialization tool to add the missing property tothe DB2 Universal Database Version 8 object typebefore migrating. If the missing property isrequired, remove the DB2 Universal DatabaseVersion 8 object type from the tools catalogbefore migrating.

ICM0804N The value of the propertypropertyname for instanceinstancename of object typetypename is not in a validdate/time format.

Explanation: The value of a date/time propertyin a DB2 Universal Database Version 7 catalog isnot in a recognized date/time format.

User Response: Manually change the IBM DB2Universal Database Version 7 data to a validdate/time format for the current location.

ICM0805N The data type of the propertynameproperty for instance instancenameof object type objecttype is notsupported by the migration tool.

Explanation: The migration tool cannot migrateobject types with properties that have data typesother than character or date/time strings.

User Response: The object type cannot bemigrated. Check that the catalog has not beencorrupted.

ICM0806N Cannot recognize the relationshiptype flag typename in the IBM DB2Version 7 catalog being migrated.

Explanation: The value of the relationship typeflag is not a recognized value.

User Response: The IBM DB2 Version 7 catalogis not valid. The relationship instance with thistype flag will not be migrated.

ICM0807N Could not find relationship typetypename.

Explanation: The predefined relationship typetypename was not found in the IBM DB2Universal Database tools catalog.



ICM0808N Object instance instancenameviolates a unique index on objecttype typename and cannot becreated.

Explanation: The instance could not be createdbecause it violates one of the unique indexesdefined for the object type.

User Response: Remove the index or delete theIBM DB2 Universal Database Version 7 objectinstance that causes the index violation beforerunning the migration tool.

ICM0900N An I/O error occurred whileopening the log file filename.

Explanation: The initialization tool was unableto open the log file because of an I/O exception.

User Response: Check that the specified filepath exists and that the file is not read-only orbeing used by another application.

ICM0901N An SQL error occurred whilecreating the Information CatalogManager API tables.

Explanation: An SQL error occurred while theinitialization tool was creating the tables requiredby the Information Catalog Manager API.


ICM0902N An SQL error occurred duringmigration.

Explanation: An SQL error occurred while themigration tool was retrieving the IBM DB2Universal Database Version 7 data beingmigrated.


ICM0903N An SQL error occurred whilecreating the DB2 UniversalDatabase Version 7 InformationCatalog emulation views.

Explanation: An SQL error occurred while theinitialization tool was creating the views thatprovide emulation of the DB2 UniversalDatabase version 7 Information Catalog Managertables.


ICM0904N Table tablename is missing fromthe IBM DB2 Universal Databasetools catalog.

Explanation: The check option for theInformation Catalog Manager API initializationfound that table tablename was not defined.

User Response: Run the Information CatalogManager API initialization with the fix option torepair this error.

ICM0905N Table tablename contains at leastone column with a definition thatis not valid.

Explanation: The check option for theInformation Catalog Manager API initializationfound that table tablename contains at least onecolumn that has a different type than that whichis required.

User Response: Run the Information CatalogManager API initialization with the fix option inforce mode to repair this error. Using the forceoption may result in lost data.

ICM0906N Table tablename contains at leastone column that is not part of thedatastore definition.

Explanation: The check option for theInformation Catalog Manager API initializationfound that table tablename contains at least onecolumn that does not exist in the table definition.

User Response: If nulls are allowed for thiscolumn then it will not affect the Information


Catalog Manager API. To remove it, run theInformation Catalog Manager API initializationwith the fix option in force mode to repair thiserror. Using the force option may result in lostdata.

ICM0907N Column columnname of tabletablename is missing from thedatastore.

Explanation: The check option for theInformation Catalog Manager API initializationfound that table tablename is missing at least onecolumn that is required by the InformationCatalog Manager API.


ICM0908N Table tablename is missing itsprimary key definition.

Explanation: The check option for theInformation Catalog Manager API initializationfound that table tablename is missing the requiredprimary key definition.


ICM0909N Table tablename is missing itsprimary key definition.

Explanation: The check option for theInformation Catalog Manager API initializationfound that the primary key for table tablenamedoes not match the primary key that is requiredby the Information Catalog Manager API.


ICM0910N Table tablename is missing anindex definition.

Explanation: The check option for theInformation Catalog Manager API found thattable tablename is missing a required index.


ICM0911N Table tablename has an invalidindex defined.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that table tablename has an indexdefined which does not match the indexesrequired by the Information Catalog Manger API.

User Response: If the index is a unique index,it may interfere with the proper functioning ofthe Information Catalog Manager API. Run theInformation Catalog Manager API initializationwith the fix option in force mode to repair thiserror. Using the force option may result in lostdata.

ICM0912N Index indexname on table tablenameis not part of the datastoredefinition.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that table tablename has an indexdefined which does not match the indexesrequired by the Information Catalog ManagerAPI.

User Response: If the index is a unique index,it may interfere with the property functioning ofthe Information Catalog Manager API. Run theInformation Catalog Manager API initializationwith the fix option in force mode to repair thiserror. Using the force option may result in lostdata.


ICM0913N Function functionname is missingfrom the IBM DB2 UniversalDatabase tools catalog.

Explanation: The check option for theInformation Catalog Manager API initializationfound that the functionfunctionname is missingfrom the DB2 Universal Database tools catalog.


ICM0914N The definition of functionfunctionname is not valid.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that the definition offunctionfunctionname does not match that whichis required by the Information Catalog ManagerAPI.


ICM0915N Trigger triggername is missingfrom the IBM DB2 UniversalDatabase tools catalog.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that the trigger triggername is missingfrom the DB2 Universal Database tools catalog.


ICM0916N The definition oftriggertriggername is not valid.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that the definition oftriggertriggername does not match the definitionthat is required by the Information CatalogManager API.

User Response: Run the Information Catalog

Manager API initialization with the fix option inforce mode to repair this error. Using the forceoption may result in lost data.

ICM00917N Trigger triggername is not part ofthe datastore definition.

Explanation: The check option for theInformation Catalog Manager API initializationdiscovered that a trigger named triggername isdefined for one of the DB2 tools catalog tableswhich does not match any of the triggersrequired by the initialization tool.


ICM00918N The view viewname is missingfrom the DB2 tools catalog.

Explanation: The check option for theInformation Catalog Manager API initializationfound that the view named viewname was notdefined.


ICM0919N Property propertyname of objecttype typename has a different datatype than the property of thedefault object type.

Explanation: An existing object type matchesthe name of one of the default object types, butone of its properties has a different data typethan the default definition for the object type.

User Response: No change is required to keepthe current definition. To replace the object typewith the default definition, run the applicationinitialization with the APP_REPLACE option.


ICM00920N Property propertyname of objecttype typename does not exist in thedefault definition for the objecttype.


User Response: No change is required to keepthe current definition. To replace the object typewith the default definition, run the applicationinitialization with the APP_REPLACE option.

ICM00921N Property propertyname of objecttype typename exists in the defaultdefinition, but is missing fromthe existing object type.


User Response: No change is required to keepthe current definition. To replace the object typewith the default definition, run the applicationinitialization with the APP_REPLACE orAPP_MERGE options.

ICM00922N Could not access the ManageInformation Catalog wizardbecause a valid license for DB2Warehouse Manager could not befound. Please contact a localsoftware reseller or IBMmarketing representative.

Explanation: An attempt was made to initializeor migrate an information catalog without avalid license.

User Response: Purchase the DB2 WarehouseManager package and install the InformationCatalog Manager Tools component whichincludes the Manage Information Catalog wizard.

ICM0923N An SQL error occurred whiledropping the DB2 UniversalDatabase Version 7 InformationCatalog emulation views.

Explanation: An SQL error occurred while theinitialization tool was dropping the views thatprovide emulation of the DB2 UniversalDatabase version 7 Information Catalog Managertables.


ICM10001N The information catalog is alreadyopen.

Explanation: The open method of theICMCatalog class was called while theinformation catalog had already been opened.

User Response: Delete the redundant call toopen the catalog.

ICM10002N Cannot commit a batchcheckpoint while there is noactive batch.

Explanation: The checkpoint operation commitsa set of transactions which are pending changesto the catalog; the transactions are committed tothe information catalog. There are no pendingoperations while there is no active batch.

User Response: Commit a batch checkpointonly when there is an active batch. UsestartBatch to make a batch active and endBatchto end it. Use checkpoint to commit intermediatepoints in the batch of changes.

ICM10003N The information catalog is notopen.

Explanation: A catalog must be open beforeoperations can be performed against it.

User Response: Open the catalog beforeattempting this operation.


ICM10004N The access control list namedaccesslistname is not unique.

Explanation: The attempted retrieval of anaccess control list by name returned more thanone instance. This is an internal catalog error thatmust be repaired because access control lists arerequired to have unique names.

User Response: Repair the information catalog.

ICM10005N Batch mode is not active.

Explanation: The endBatch method was calledwhen no batch was active.

User Response: A batch must be started beforeit can end. Use the sequence startBatch, modifycatalog, checkpoint, modify catalog, checkpoint,modify catalog, endBatch for valid batchoperation.

ICM10006N Batch mode is already active.

Explanation: The startBatch method was calledwhile no batch was active.

User Response: A batch cannot start until aprevious batch has ended. Use the sequencestartBatch, modify catalog, checkpoint, modifycatalog, checkpoint, modify catalog, endBatch forvalid batch operation.

ICM10007N Failed to remove the last recordedcheckpoint.

Explanation: The Information Catalog ManagerAPI records checkpoints as they are committedduring a batch. This is done so that the batch canbe resumed from the last successful checkpoint ifa failure occurs. On successful completion of thebatch, the checkpoint record is removed. It is theremoval of the checkpoint record that failed.

User Response: Check the nested exception todetermine the cause of the failure.

ICM10008N An I/O error occurred whilecreating the export temporary filefilename.

Explanation: An error occurred while creating atemporary file that holds information during theexport process.

User Response: Check the nested exception andcorrect the problem.

ICM10009N Export operation to file filenamefailed.

Explanation: An error occurred during anexport operation.

User Response: Check the export log file andcorrect the problem.

ICM10010N Import failed. Last completedcheckpoint was checkpoint.

Explanation: An import operation was partiallysuccessful but failed before completion.

User Response: Check the import log file andcorrect the problem.

ICM10011N Import failed. No checkpointscompleted.

Explanation: An import operation failed beforecompleting any checkpoints.

User Response: Check the import log file andcorrect the problem.

ICM10012N The access control list is not thedefault access control list.

Explanation: The access control List provided tosetDefaultACL must be the access control listacquired from getDefaultACL.

User Response: Check the documentation forICMCatalog.setDefaultACL.


ICM10013N Checkpoint object instanceuser=username, host=hostname,batch=batchname in internal objecttype typename is not unique.

Explanation: Checkpoints are kept in aninternal object type with the unique ID set to theuser, host, batch properties. It should not bepossible for ambiguous checkpoint objectinstances to exist.

User Response: Contact a databaseadministrator for catalog repair.

ICM10014N Unable to retrieve host name forcheckpoint identification.

Explanation: An unknown host exception wasthrown while retrieving the host name.

User Response: Contact a system administratorto examine the nested exception.

ICM10015N Unexpected property constraintexception occurred while workingwith object instanceuser=username, host=hostname,batch=batchname of the internalobject type objecttype.

Explanation: A property constraint exceptionwas thrown while working with an instance ofthe internal checkpoint object type. An internalcatalog problem occurred because no propertyconstraints are placed on the properties of thisobject type.

User Response: Contact a databaseadministrator for catalog repair.

ICM10016N Unexpected security exceptionwhile working with objectinstance user=username,host=hostname, batch=batchname ofthe internal object type typename.

Explanation: Checkpoint object instances areowned by the current user at the time the batchcompleted a checkpoint. No security violationshould occur.

User Response: Determine the security violationand correct it.

ICM10017N Unexpected property constraintexception occurred whilerecording the delete history in theinternal object type objecttype.

Explanation: A property constraint exceptionwas thrown while working with an instance ofthe internal object type used to record the deletehistory. There is an internal catalog problembecause no property constraints are placed onthe properties of this object type.

User Response: Turn off the delete historyfeature and contact a database administrator forcatalog repair.

ICM10100N Internal object type objecttype wasnot found. This catalog is notusable.

Explanation: An internal object type used tosupport the Information Catalog Centerapplication was not found in the IBM DB2Universal Database tools catalog. The catalogwas not properly initialized for InformationCatalog Center use or it was corrupted.

User Response: Check that the metadata storecontaining the catalog has been properlyinitialized for the Information Catalog Centerapplication.

ICM10101N Internal relationship typerelationshiptype was not found.This catalog is not usable.

Explanation: An internal relationship type usedto support the Information Catalog Centerapplication was not found in the IBM DB2Universal Database tools catalog. The catalogwas not properly initialized for InformationCatalog Center use or it has been corrupted.

User Response: Check that the metadata storecontaining the catalog has been properlyinitialized for the Information Catalog Centerapplication.


ICM10200N A collection named name alreadyexists.

Explanation: The collection name supplied wasidentical to the name of an already existingcollection owned by the current user.

User Response: Specify a different name for thenew collection.

ICM10201N Unable to create a new collectionwith a default name.

Explanation: The Information Catalog ManagerAPI can create up to 1000 different defaultcollection names. Failed to create the newcollection because all 1000 default names alreadyexist.

User Response: Rename some collections tonon-default names.

ICM10202N Collection name is specified fordeletion but does not match anycollection owned by the currentuser.

Explanation: The collection name specified asthe target of a delete operation was not found inthe current user’s collections.

User Response: Specify an existing collection.

ICM10203N The relationship instanceidentifying members of collectionname could not be found.

Explanation: The internal relationship typeinstance, which is used to identify members of acollection, was not associated with the collection.An internal error occurred and the collection isnot usable.

User Response: Use the Information CatalogManager API to delete the collection.

ICM10204N Too many relationship instancesexist on collection name.

Explanation: More than one relationshipinstance was found attached to an instance of theinternal object type used to store collections. An

internal error occurred in the information catalogand this collection is not usable.


ICM10205N Relationship instance oncollection name is not valid.

Explanation: A relationship instance of anincorrect type was found attached to an instanceof the internal object type used to storecollections. This is an internal error in theinformation catalog and the collection is notusable.


ICM10300N Could not recognize the propertysearch type specified.

Explanation: The property search type suppliedto a DateSearchCriteria or TextSearchCriteria isnot one of those defined.

User Response: Specify one of the definedproperty search types.

ICM10301N No search date specified.

Explanation: Attempted to run a date searchwith no dates specified.

User Response: Specify a start date, end date,or both.

ICM10302N Search has no associated criteria.

Explanation: Attempted to call the createmethod to write a search with no associatedcriteria to the catalog.

User Response: Associate a criteria with thesearch before creating it.

ICM10303N Error occurred while loadingsearch criteria for search name.

Explanation: An exception was caught whilereading the search criteria for a search from thecatalog.


User Response: Check the nested exception todetermine the problem.

ICM10304N Error occurred while storingsearch criteria for search name.

Explanation: An exception was caught whilewriting the search criteria for a search to thecatalog.

User Response: Check the nested exception todetermine the problem.

ICM10305N Maximum returned object countcannot be negative. Count was:error-code.

Explanation: A SearchCriteria object was givena negative value for maximum objects returned.An error would occur if the SearchCriteria is run.

User Response: Specify a maximum objectcount which is not negative.

ICM10306N Object type search collectioncontains foreign object.

Explanation: Only ICMObjectTypes can bespecified to identify the types ofICMObjectInstances to search.

User Response: Check that the collection ofobject types only contains objects of typeICMObjectType.

ICM10307N The search name name is in use.

Explanation: A user cannot have two searcheswith the same name.

User Response: Specify a search name which isnot in use.

ICM10308N Unable to find a new defaultsearch name.

Explanation: The Information Catalog ManagerAPI can create up to 1000 different default searchnames when creating a new search. Failed tocreate a new default search name because alldefault names are in use.

User Response: Rename some searches thathave default names.

ICM10309N No search strings specified.

Explanation: Attempted to perform a textsearch with no text strings specified.

User Response: Specify search strings to bematched.

ICM10310N The search name specified fordeletion does not match existingsearches owned by the currentuser.

Explanation: The search name specified as thetarget of a delete was not found in the currentuser’s searches.

User Response: Specify an existing search.

ICM10311N Search values must be text strings.

Explanation: Attempted to set search values fora TextSearchCriteria which were not text strings.

User Response: Specify search text strings to bematched.

ICM10400N Message Text : Error occurredwhile retrieving property data foruser/group from the internal objecttype objecttype.

Explanation: An exception was caught whileretrieving the stored property information froman object instance of the internal object type.

User Response: Contact a databaseadministrator to check the nested exception.

ICM10401N Error occurred while storingproperty data for user/group to theinternal object type objecttype.

Explanation: An exception was caught whilestoring property information to an object instanceof the internal object type.



ICM10402N Unable to retrieve host name.

Explanation: An unknown host exception wasthrown while retrieving the host name.

User Response: Consult a system administratorto check the nested exception.

ICM10500N Error occurred while startingprogram with command stringcommand.

Explanation: An exception was thrown whileattempting to invoke a program on an objectinstance.

User Response: Check the nested exception andcorrect the program or path object.

ICM10501N Internal error occurred whileattempting to write aBlobProperty to a file.

Explanation: The BlobProperty has been createdin the database but the associated object instancehas not.


ICM10502N Property propertyname is anincorrect type.

Explanation: A property name passed towriteBlobToStream or writeClobToWriter was nota correct Blob or Clob property.

User Response: Check that the property is aBlob or Clob as needed by the method beingcalled.

ICM10503N Unable to retrieve the value fromthe propertyname property of aninstance of object type objecttype.

Explanation: An exception was caught whileretrieving a value from the property of the objecttype.


ICM10504N Unmatched parameter marker in aparameterized string. String =paramstring.

Explanation: A parameter marker opencharacter was found without a correspondingparameter marker close character whileformatting a parameterized string.

User Response: Check that the parameterizedstring is in a valid format.

ICM10505N Error occurred while writing datafrom BlobProperty orClobProperty propertyname to filefilename.

Explanation: A parameter of the typeBlobProperty or ClobProperty was encounteredas one of the parameters while formatting aparameterized string. An exception was caughtwhile writing the contents of the property to afile.

User Response: Check the nested exception.

ICM10506N An internal error occurred whileattempting to write propertypropertyname to a file.

Explanation: Attempted to write a property to afile while formatting a parameterized string. Theproperty was not a BlobProperty or aClobProperty, which are the only property typesallowed to be written to a file.


ICM10600N Icon data size datasize is largerthan maxsize bytes.

Explanation: The icon associated with an objecttype cannot be larger than the indicatedmaximum size.

User Response: Specify a smaller icon file.Contact a database administrator if the icon datahas been corrupted in the catalog.


ICM10601N Error occurred while retrievingicon data from catalog.

Explanation: An SQLException was caughtwhile reading the icon data from the object type.

User Response: Check the nested exception.

ICM10700N The name specified (typename)matches more than one objecttype.

Explanation: The name used to retrieve anobject type matched more than one object type.The inclusion of a wildcard character in thename might cause this error.

User Response: Supply a name which uniquelyidentifies an object type.

ICM10701N The object type typename does notexist.

Explanation: The object type name used withan Information Catalog Manager API method didnot match existing object types.

User Response: Use the name of an existingobject type.

ICM10702N The required relationship categorycategoryname can not be found.This catalog is not usable.

Explanation: One of the required relationshipcategories in an information catalog could not befound. This is a fatal error.

User Response: Contact a databaseadministrator.

ICM10703N The object type typename is not aninformation catalog user objecttype.

Explanation: The IBM DB2 Universal Databasetools catalog supports multiple applicationprograms. The object types seen by informationcatalog users are a subset of all the object typesin a tools catalog. An exception occurred whilepassing an object type to the Information CatalogManager API which is not one of the information

catalog user object types.

User Response: Only use the InformationCatalog Manager API with information cataloguser object types.

ICM10704N An operation to store the defaultproperty visibility flags for theobject type typename failed.

Explanation: An exception was caught whilestoring the information that defines defaultproperty visibility for this object type.


ICM10705N An operation to load the defaultproperty visibility flags for theobject type typename failed.

Explanation: An exception was caught whileloading the information that defines defaultproperty visibility for this object type.


ICM10706N The object type typename is not aninformation catalog user objecttype.

Explanation: The IBM DB2 Universal Databasetools catalog supports multiple applicationprograms. The object types seen by informationcatalog users are a subset of all the object typesin a tools catalog. An exception occurred becausean object instance of a type not in theinformation catalog user object type set waslinked by a relationship to an instance of anobject type which is in the information cataloguser object type set.

User Response: Use the Information CatalogManager API with information catalog userobject types.


ICM10800N The required relationshipconstraint constraintname may notbe removed.

Explanation: Relationship constraints placed onrelationship types enforce required behaviorswithin the information catalog. The constraintsmay not be removed.

User Response: Do not attempt to remove therequired relationship constraint.

ICM10801N Error occurred while enforcingrequired constraint constraintnameon relationship typerelationshiptype.

Explanation: An exception was thrown whileattempting to instantiate a required constraintobject to apply to a relationship type.




Chapter 12. GSE Messages

This section contains the IBM DB2 UDB Spatial Extender messages. Themessages are listed in numeric sequence.

GSE0000I The operation was completedsuccessfully.

Explanation: No errors were encounteredduring the execution of this operation.


msgcode: 0

sqlstate: 00000

GSE0001C An internal error occurred.

Explanation: Spatial Extender encountered anunexpected internal error.

User Response: Repeat the command. If theproblem persists, contact IBM Software Support.

msgcode: -1

sqlstate: 38S01

GSE0002C Spatial Extender could not accessits memory pool. Reason code =reason-code.

Explanation: Spatial Extender triedunsuccessfully to access its memory pool.

User Response: Note the reason codereason-code and contact IBM Software Support.

msgcode: -2

sqlstate: 38S02

GSE0003N Spatial Extender could notallocate number bytes of memory.

Explanation: Not enough memory wasavailable. Possible reasons are that the supply ofmemory was too low, or that memory was beingused by other applications.

User Response: Resolve the memory shortageand repeat the command.

msgcode: -3

sqlstate: 38S03

GSE0004C An internal parameter erroroccurred.

Explanation: Spatial Extender encountered anunexpected error in a parameter passed to aninternal function. The operation cannot becompleted successfully.


msgcode: -4

sqlstate: 38S04

GSE0005N Spatial Extender could notretrieve the instance path.

Explanation: Spatial Extender could not retrievethe instance path. The operation cannot becompleted successfully.

User Response: Verify the DB2 environment. Ifnecessary, contact IBM Software Support.

msgcode: -5

sqlstate: 38S05

GSE0006N An internal string error occurred.

Explanation: Spatial Extender encountered anunexpected error in an internal string operation.The operation cannot be completed successfully.



msgcode: -6

sqlstate: 38S06

GSE0007N The string string is missing eithera closing quotation mark or aclosing pair of quotation marks.

Explanation: This string lacks a closingdelimiter and therefore is not terminatedcorrectly.

User Response: Terminate the string correctly. Ifit starts with a quotation mark, close it with aquotation mark. If it starts with a pair ofquotation marks, close it with a pair of quotationmarks.

msgcode: -7

sqlstate: 38S07

GSE0008N An invalid error code error-codewas used to raise an error.

Explanation: There was an attempt to raise anerror identified by an invalid error-code.


msgcode: -8

sqlstate: 38S08

GSE0009N Not enough space is available inDB2’s application heap.

Explanation: The available memory for DB2’sapplication heap was exceeded by SpatialExtender. The operation cannot be completedsuccessfully.

User Response: On receipt of this message,terminate the application. Increase the databaseconfiguration parameter (APPLHEAPSZ) toallow a larger application heap.

Refer to the IBM DB2 UDB Spatial ExtenderUser’s Guide and Reference for moreinformation.

msgcode: -9

sqlstate: 38S09

GSE0010N Not enough log space is availableto DB2.

Explanation: All available space in DB2’stransaction log is being used. The operationcannot be completed successfully.

User Response: If the database is being used byother applications concurrently, retry theoperation. Log space may be freed up whenanother application finishes a transaction.

Increase the database configuration parameters toallow more log space. For example, the databaseconfiguration parameters LOGPRIMARY,LOGSECONDARY, and LOGFILSIZ can bemodified to increase the size of the availablelogs.

msgcode: -10

sqlstate: 38S0A

GSE0100N Spatial Extender could not open afile named file-name. Reason code= reason-code.

Explanation: Reasons why a file cannot beopened, preceded by their reason codes, are asfollows:

1 Access to the file is denied.

3 A disk error occurred.

8 A directory with the name of the filealready exists.

10 Spatial Extender tried either to create analready-existing file, or to open anexisting file that could not be found.

12 The disk is full.

17 The specified path to the file does notexist.

22 A sharing violation occurred.

All other reason codes indicate an internal error.

User Response: Verify the authorization for thefile and the directories, then repeat thecommand.

If a reason code that indicates an internal error


was encountered, contact IBM Software Support.

msgcode: -100

sqlstate: 38S10

GSE0101N An I/O error occurred while a filenamed file-name was beingprocessed. Reason code =reason-code.

Explanation: Reasons why an I/O error canoccur during file processing, preceded by theirreason codes, are as follows:



9 Spatial Extender attempted to read pastthe end of the file.




User Response: Verify that the file exists, thatyou have the appropriate access to the file, andthat the file is not in use by another process.

If a reason code that indicates an internal errorwas encountered, contact IBM Software Support.

msgcode: -101

sqlstate: 38S11

GSE0102N Spatial Extender could not close afile named file-name. Reason code= reason-code.

Explanation: Reasons why an error can occurduring an attempt to close a file, preceded bytheir reason codes, are as follows:




User Response: Verify that the file system is infully working condition and that enough diskspace is available.


msgcode: -102

sqlstate: 38S12

GSE0103N Spatial Extender could not deletea file named file-name. Reasoncode = reason-code.

Explanation: Reasons why an error can occurduring an attempt to delete a file, preceded bytheir reason codes, are as follows:



17 The specified path to file does not exist.



User Response: Given for each reason code:

1 Verify that you have sufficient privilegeson the file and all directories in the pathof the file.

3 Verify that the disk and file system arein proper working order.

17 Verify that the path to the file exists.

22 Verify that the file is not accessed byanother process.


msgcode: -103

sqlstate: 38S13

GSE0200N An attempt to connect to thedatabase failed. SQLERROR =sql-error.

Explanation: Spatial Extender was not able toconnect to the database. DB2 returned sql-error.

User Response: Refer to the description ofsql-error.

Chapter 12. GSE Messages 475

msgcode: -200

sqlstate: 38S20

GSE0201W An attempt to disconnect from thedatabase failed. SQLERROR =sql-error.

Explanation: Spatial Extender was not able todisconnect from the database. DB2 returnedsql-error.


msgcode: +201

sqlstate: 38S21

GSE0202N No connection to a databaseexists.

Explanation: Spatial Extender cannot connect toa database. The command cannot be executedsuccessfully.

User Response: Verify the Spatial Extender anddatabase setup. Make sure that a connection tothe database can be established.

msgcode: -202

sqlstate: 38S22

GSE0203W Spatial Extender was alreadyconnected to databasedatabase-name.

Explanation: Spatial Extender tried to connectto the database database-name but was alreadyconnected to it.


msgcode: +203

sqlstate: 38S23

GSE0204N An attempt to commit atransaction failed. SQLERROR =sql-error.

Explanation: Spatial Extender could not committhe current transaction successfully. DB2 returnedsql-error.


msgcode: -204

sqlstate: 38S24

GSE0205W An attempt to roll back atransaction failed. SQLERROR =sql-error.

Explanation: Spatial Extender could not rollback the current transaction. DB2 returnedsql-error.


msgcode: +205

sqlstate: 38S25

GSE0206N A SELECT statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executea SELECT statement successfully. DB2 returnedsql-error.


msgcode: -206

sqlstate: 38S26

GSE0207N A VALUES statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executea VALUES statement successfully. DB2 returnedsql-error.


msgcode: -207


sqlstate: 38S27

GSE0208N A PREPARE statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not preparean SQL statement successfully. DB2 returnedsql-error.


msgcode: -208

sqlstate: 38S28

GSE0209N An attempt to open an SQL cursorfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not open acursor over a result set successfully. DB2returned sql-error.


msgcode: -209

sqlstate: 38S29

GSE0210W An attempt to close an SQL cursorfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not close acursor over a result set successfully. DB2returned sql-error.


msgcode: +210

sqlstate: 38S2A

GSE0211N A fetch from an SQL cursorfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not fetch aresult from a cursor successfully. DB2 returnedsql-error.


msgcode: -211

sqlstate: 38S2B

GSE0212N An attempt to drop an objectfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not dropthe specified database object. DB2 returnedsql-error.


msgcode: -212

sqlstate: 38S2C

GSE0213N A bind operation failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not bindthe specified file to the current database. DB2returned sql-error.

This error can occur if the size of DB2’sapplication heap is too small.

User Response: Verify that the database isenabled for spatial operations.

If the error occurs during the enabling, verify theinstallation of Spatial Extender.

If the problem persists, increase the databaseconfiguration parameter (APPLHEAPSZ) for thesize of the application heap.

msgcode: -213

sqlstate: 38S2D

GSE0214N An INSERT statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executean INSERT statement successfully. DB2 returnedsql-error.


msgcode: -214

sqlstate: 38S2E


GSE0215N An UPDATE statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executean UPDATE statement successfully. DB2 returnedsql-error.


msgcode: -215

sqlstate: 38S2F

GSE0216N A DELETE statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executea DELETE statement successfully. DB2 returnedsql-error.


msgcode: -216

sqlstate: 38S2G

GSE0217N A LOCK TABLE statement failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not executea LOCK TABLE statement successfully. DB2returned sql-error.


msgcode: -217

sqlstate: 38S2H

GSE0218N A DECLARE GLOBALTEMPORARY TABLE statementfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not executea DECLARE GLOBAL TEMPORARY TABLEstatement successfully. DB2 returned sql-error.


msgcode: -218

sqlstate: 38S2I

GSE0219N An EXECUTE IMMEDIATEstatement failed. SQLERROR =sql-error.

Explanation: Spatial Extender could not executean EXECUTE IMMEDIATE statementsuccessfully. DB2 returned sql-error.


msgcode: -219

sqlstate: 38S2J

GSE0220N The setting of a savepoint failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not set asavepoint successfully. DB2 returned sql-error.


msgcode: -220

sqlstate: 38S2K

GSE0221N No database name was specified.

Explanation: Spatial Extender could not connectto a database because the name of the databasewas not specified.

User Response: Specify a database name.

msgcode: -221

sqlstate: 38S2L

GSE0222N An attempt to retrieve theauthorization list from DB2 failed.SQLERROR = sql-error.

Explanation: Spatial Extender could not retrievethe authorization list for the current user. DB2returned sql-error.


msgcode: -222


sqlstate: 38S2M

GSE0223N An attempt to quiesce a tablespace failed. SQLERROR =sql-error.

Explanation: Spatial Extender could not quiescea table space successfully. DB2 returned sql-error.


msgcode: -223

sqlstate: 38S2N

GSE0224N An attempt to load data into atable failed. SQLERROR =sql-error.

Explanation: Spatial Extender could not loaddata into a table successfully. DB2 returnedsql-error.


msgcode: -224

sqlstate: 38S2O

GSE0225N An attempt to retrieve thedatabase configuration or thedatabase manager configurationfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not retrievethe configuration for the current database or theconfiguration for the database managersuccessfully. DB2 returned sql-error.


msgcode: -225

sqlstate: 38S2P

GSE0226N An attempt to create a triggerfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not create atrigger successfully. DB2 returned sql-error.


msgcode: -226

sqlstate: 38S2Q

GSE0227N An ALTER TABLE statementfailed. SQLERROR = sql-error.

Explanation: Spatial Extender could not executean ALTER TABLE statement successfully. DB2returned sql-error.


msgcode: -227

sqlstate: 38S2R

GSE0228N An attempt to retrieve themessage for error gse-error andSQLCODE = sqlcode from theSpatial Extender message catalogfailed.

Explanation: Spatial Extender could not retrievethe message for error gse-error and SQLCODE =sqlcode successfully.

User Response: Verify the installation of SpatialExtender. Verify also that the message catalog inthe language that you want to use is installed.

msgcode: -228

sqlstate: 38S2S

GSE0229N An attempt to bind a file namedbind-file failed. Reason code =reason-code.

Explanation: Spatial Extender failed in anattempt to use the sqlabndx function to bind thefile named bind-file to the database. sqlabndxreturned the reason code reason-code.

User Response: Verify that the database isenabled for spatial operations.

Refer to the description of reason-code for thefunction sqlabndx.

msgcode: -229


sqlstate: 38S2T

GSE0230N The system catalog could not beupdated.

Explanation: Spatial Extender encountered anerror while attempting to use the DB2 service toupdate the system catalog.


msgcode: -230

sqlstate: 38S2U

GSE0300N The specified password is toolong.

Explanation: The password used in yourattempt to connect to the database is too long.

User Response: Verify that the password youspecified is correct. If it is the correct password,then shorten it and try the operation again.

msgcode: -300

sqlstate: 38S40

GSE0301N The specified schema name,schema-name, is too long.

Explanation: The requested operation cannot becompleted successfully because the length of theschema name exceeds DB2’s limit for schemanames.

User Response: Specify a valid, shorter schemaname. For more information on the schema namelength limit, refer to IBM DB2 UDB SpatialExtender User’s Guide and Reference and try theoperation again.

msgcode: -301

sqlstate: 38S41

GSE0302N The specified table name,table-name, is too long.

Explanation: The requested operation cannot becompleted successfully because the length of thetable name exceeds DB2’s limit for table names.

User Response: Specify a valid, shorter tablename.

For more information on the table name lengthlimit, refer to IBM DB2 UDB Spatial ExtenderUser’s Guide and Reference, and then try theoperation again.

msgcode: -302

sqlstate: 38S42

GSE0303N The specified column name,column-name, is too long.

Explanation: The requested operation cannot becompleted successfully because the length of thecolumn name exceeds DB2’s limit for columnnames.

User Response: Specify a valid, shorter columnname.

For more information on the column namelength limit, refer to IBM DB2 UDB SpatialExtender User’s Guide and Reference, and thentry the operation again.

msgcode: -303

sqlstate: 38S43

GSE0304N The specified index name,index-name, is too long.

Explanation: The requested operation cannot becompleted successfully because the length of theindex name exceeds DB2’s limit for index names.

User Response: Specify a valid, shorter indexname. For more information on the index namelength limit, refer to IBM DB2 UDB SpatialExtender User’s Guide and Reference, and thentry the operation again.

msgcode: -304

sqlstate: 38S44

GSE0305N The specified data type name,type-name, is too long.

Explanation: The requested operation cannot becompleted successfully because the length of the


data type name exceeds DB2’s limit for data typenames.

User Response: Specify a valid, shorter typename. For more information on the data typename length limit, refer to IBM DB2 UDB SpatialExtender User’s Guide and Reference, and thentry the operation again.

msgcode: -305

sqlstate: 38S45

GSE0306N A complete path that starts withpath would exceed the acceptablelimit of limit bytes.

Explanation: The file in a path that starts withpath cannot be accessed because the length of thecomplete path would exceed the limit of limitbytes. As a result, the statement that yousubmitted cannot be executed successfully.

User Response: Change the location of the fileto be accessed so that it can be found using ashorter path and re-submit the statement thatyou specified. On UNIX systems, symbolic linkscan be used to establish a shorter path name.

msgcode: -306

sqlstate: 38S46

GSE0307N The length of a dynamic SQLstatement statement-length wouldexceed the acceptable limit of limitbytes.

Explanation: The statement cannot beconstructed because it would be too long.

User Response: If the statement is constructedin the context of a stored procedure, verify thatthe WHERE clause is not too long. If necessary,shorten the WHERE clause and retry theoperation. If the problem persists, contact IBMSoftware Support.

msgcode: -307

sqlstate: 38S47

GSE0308N The string, string, exceeds thelimit of limit bytes.

Explanation: The requested operation cannot becompleted successfully because the string, string,is too long.

User Response: Specify a shorter string. Ifnecessary, contact IBM Software Support.

msgcode: -308

sqlstate: 38S48

GSE1000N Spatial Extender could notperform an operationoperation-name that was requestedunder user id user-id.

Explanation: You requested this operationunder a user id that does not hold the privilegeor authority to perform the operation.

User Response: Consult the IBM DB2 UDBSpatial Extender User’s Guide and Reference tofind out what the required authorization for theoperation is.

msgcode: -1000

sqlstate: 38S50

GSE1001N The specified value, value, is notvalid for the argument-nameargument.

Explanation: The value value that you enteredfor argument argument-name was incorrect ormisspelled.

User Response: Consult the IBM DB2 UDBSpatial Extender User’s Guide and Reference tofind out what value or range of values you needto specify.

msgcode: -1001

sqlstate: 38S51

GSE1002N A required argument,argument-name, was not specified.

Explanation: The requested operation cannot becompleted successfully because an argument that


it requires was not specified.

User Response: Specify argumentargument-name with the value that you want;then request the operation again.

msgcode: -1002

sqlstate: 38S52

GSE1003N The spatial column,schema-name.table-name.column-name,could not be registered with thespatial reference system srs-namebecause it is already registeredwith another spatial referencesystem.

Explanation: A spatial reference system isalready registered with the spatial column. Itcannot be registered again unless it isunregistered first.

User Response: Either unregister the spatialcolumn and then register it with the spatialreference system you want or do not attempt toregister it again.

msgcode: -1003

sqlstate: 38S53

GSE1004N The specified geocoder,geocoder-name, is alreadyregistered.

Explanation: This geocoder is alreadyregistered. It cannot be registered again unless itis unregistered first.

User Response: Register the geocoder with aunique name, or unregister the existing geocoderfirst and then try the operation again.

msgcode: -1004

sqlstate: 38S54

GSE1005N Geocoding has already been setup for the spatial column namedschema-name.table-name.column-name.

Explanation: Geocoding has already been set upfor this column. Geocoding cannot be set up

again unless the current setup is removed first.

User Response: Remove the existing geocodingsetup, or choose a column for which geocodingis already set up.

msgcode: -1005

sqlstate: 38S55

GSE1006N The spatial columnschema-name.table-name.column-nameis not registered.

Explanation: This spatial column was notregistered with a spatial reference system.Therefore, it cannot be unregistered.

User Response: Specify a spatial column that isalready registered, or do not attempt tounregister the column.

msgcode: -1006

sqlstate: 38S56

GSE1007N The specified geocodergeocoder-name is not registered.

Explanation: A geocoder named geocoder-namehas not been registered. Therefore, it cannot beunregistered.

User Response: Specify a geocoder that isalready registered, or do not attempt tounregister the geocoder.

msgcode: -1007

sqlstate: 38S57

GSE1008N A geocoder whose numericidentifier is geocoder-id is notregistered.

Explanation: A geocoder whose numericidentifier is geocoder-id is not registered. It cannotbe unregistered.

User Response: Specify a geocoder that isalready registered, or do not attempt tounregister the geocoder.

msgcode: -1008


sqlstate: 38S58

GSE1009N A table namedschema-name.table-name does notexist.

Explanation: The requested operation cannot becompleted successfully because the tableschema-name.table-name does not exist.

User Response: Specify a valid table name andretry the operation.

msgcode: -1009

sqlstate: 38S59

GSE1010N A spatial column namedschema-name.table-name.column-namedoes not exist.

Explanation: The requested operation cannot becompleted successfully becauseschema-name.table-name.column-name does notidentify an existing column.

User Response: Specify a valid spatial columnname and retry the operation.

msgcode: -1010

sqlstate: 38S5A

GSE1011N A data type namedschema-name.type-name does notexist.

Explanation: The requested operation cannot becompleted successfully because a data typeschema-name.type-name does not exist.

User Response: Specify a valid data type nameand retry the operation.

msgcode: -1011

sqlstate: 38S5B

GSE1012N The database has not beenenabled for spatial operations.

Explanation: The requested operation cannot becompleted successfully because the database hasnot been enabled for spatial operations and,

therefore, a Spatial Extender catalog has not beencreated.

User Response: Enable the database for spatialoperations.

msgcode: -1012

sqlstate: 38S5C

GSE1013N The database is already enabledfor spatial operations.

Explanation: The database is already enabledfor spatial operations. It cannot be enabled again.

User Response: Verify that the database hasbeen enabled as you expected. If necessary,disable the database.

msgcode: -1013

sqlstate: 38S5D

GSE1014N Spatial Extender was unable toregister a column namedschema-name.table-name.column-namebecause it is not a spatial column.

Explanation: Either this column does not have aspatial data type, or it does not belong to a localtable.

User Response: Define a spatial data type forcolumn schema-name.table-name.column-name, orspecify a column with a spatial data type asdeclared type.

msgcode: -1014

sqlstate: 38S5E

GSE1015N A spatial reference system namedsrs-name does not exist.

Explanation: The requested operation cannot becompleted successfully because a spatialreference system with the name srs-name doesnot exist.

User Response: Specify an existing spatialreference system and retry the operation.

msgcode: -1015


sqlstate: 38S5F

GSE1016N A spatial reference system whosenumeric identifier is srs-id doesnot exist.

Explanation: The requested operation could notbe completed successfully because a spatialreference system with the specified numericidentifier srs-id does not exist.

User Response: Specify an existing spatialreference system identifier and retry theoperation.

msgcode: -1016

sqlstate: 38S5G

GSE1017N A coordinate system namedcoordsys-name already exists.

Explanation: A coordinate system namedcoordsys-name already exists. Another coordinatesystem with the same name cannot be created.

User Response: Specify a unique name for thenew coordinate system.

msgcode: -1017

sqlstate: 38S5H

GSE1018N A coordinate system namedcoordsys-name does not exist.

Explanation: The requested operation cannot becompleted successfully because a coordinatesystem with the name coordsys-name does notexist.

User Response: Specify the name of an existingcoordinate system.

msgcode: -1018

sqlstate: 38S5I

GSE1019N No values of the spatialcoordinate system coordsys-nameare specified.

Explanation: You attempted to alter thecoordinate system coordsys-name, but did notspecify any new values.

User Response: Specify at least one new valuefor the coordinate system.

msgcode: -1019

sqlstate: 38S5J

GSE1020N A spatial reference system namedsrs-name already exists.

Explanation: A spatial reference system namedsrs-name already exists. Another spatial referencesystem with the same name cannot be created.

User Response: Specify a unique name for thespatial reference system to be created and retrythe operation.

msgcode: -1020

sqlstate: 38S5K

GSE1021N A spatial reference system namedsrs-name does not exist.

Explanation: The requested operation cannot becompleted successfully because a spatialreference system with the name srs-name doesnot exist.

User Response: Specify a name of an existingspatial reference system and retry the operation.

msgcode: -1021

sqlstate: 38S5L


Explanation: The requested operation cannot becompleted successfully because a spatialreference system with the numeric identifiersrs-id does not exist.


User Response: Specify an existing numericidentifier for the spatial reference system.

msgcode: -1022

sqlstate: 38S5M

GSE1023N A coordinate system whosenumeric identifier is coordsys-iddoes not exist.

Explanation: The requested operation cannot becompleted successfully because a coordinatesystem with the numeric identifier coordsys-iddoes not exist.

User Response: Specify an existing numericidentifier for the coordinate system and retry theoperation.

msgcode: -1023

sqlstate: 38S5N

GSE1024N No values of the spatial referencesystem srs-name are specified.

Explanation: You attempted to alter the spatialreference system srs-name, but did not specifyany new values.

User Response: Specify at least one new valuefor the spatial reference system and then try theoperation again.

msgcode: -1024

sqlstate: 38S5O

GSE1025N A geocoder whose function nameis schema-name.function-name couldnot be found in the database.

Explanation: The requested operation cannot becompleted successfully because Spatial Extendercould not locate a function namedschema-name.function-name for the geocoder.

User Response: Specify a geocoder with anexisting function name or create the function,then try the operation again.

msgcode: -1025

sqlstate: 38S5P

GSE1026N The specified number of defaultparameter values (number1 values),does not match with the numberof default parameter values(number2 values) that the specifiedgeocoder requires.

Explanation: The specified geocoder could notbe registered because you did not specify thecomplete list for all the parameter values that thegeocoder requires.

User Response: Correct the number of defaultparameter values. Specify a default value foreach of the parameters of the geocoder or specifya null value for the default parameter values.

msgcode: -1026

sqlstate: 38S5Q

GSE1027N The specified number ofparameter description values(number1 values) does not matchwith the number of parameterdescription values (number2values) that the specified geocoderrequires.

Explanation: The specified geocoder could notbe registered because you did not specify thecomplete list for all the parameter descriptionvalues that the geocoder requires.

User Response: Specify a description for eachof the parameters of the geocoder, or specify anull value for the parameter descriptions.

msgcode: -1027

sqlstate: 38S5R

GSE1028N A geocoder named geocoder-namedoes not exist.

Explanation: The requested operation cannot becompleted successfully because a geocoder withthe name geocoder-name does not exist.

User Response: Specify an existing geocodername or register the geocoder with the name thatyou specified and then try the operation again.

msgcode: -1028


sqlstate: 38S5S

GSE1029N Geocoding has not been set up fora column namedschema-name.table-name.column-name.

Explanation: The requested operation cannot becompleted successfully because geocoding hasnot been set up for the column namedschema-name.table-name.column-name.

User Response: Set up geocoding for thespecified column, or correct the table schema,table name, and column name.

msgcode: -1029

sqlstate: 38S5T

GSE1030N Auto-geocoding is enabled forcolumn schema-name.table-name.column-name and thegeocoding setup cannot beremoved.

Explanation: Auto-geocoding have beenenabled for the column namedschema-name.table-name.column-name. Therefore,the geocoding setup for this column cannot beremoved.

User Response: Disable auto-geocoding for thecolumn.

msgcode: -1030

sqlstate: 38S5U

GSE1031N Auto-geocoding for a columnnamed schema-name.table-name.column-name is not enabled.

Explanation: Auto-geocoding has not beenenabled for column schema-name.table-name.column-name. Therefore, auto-geocodingcannot be disabled for this column.

User Response: Specify a correct column nameon which auto-geocoding is enabled.

msgcode: -1031

sqlstate: 38S5V

GSE1032N Auto-geocoding for a columnnamed schema-name.table-name.column-name is alreadyenabled.

Explanation: Auto-geocoding has already beenenabled for the column namedschema-name.table-name.column-name.Auto-geocoding cannot be enabled again for thiscolumn unless it is disabled first.

User Response: Specify a correct name for acolumn for which (1) auto_geocoding is notenabled and (2) geocoding is set up.

msgcode: -1032

sqlstate: 38S5W

GSE1033N A geocoder whose numericidentifier is geocoder-id does notexist.

Explanation: The requested operation cannot becompleted successfully because a geocoder withthe numeric identifier geocoder-id does not exist.

User Response: Specify an existing numericidentifier for the geocoder, or register a geocoderwith numeric identifier geocoder-id.

msgcode: -1033

sqlstate: 38S5X

GSE1034N The parameters passed to thestored procedure do not include aparameter parameter-name.

Explanation: The SQLDA that was passed tothe stored procedure is too small. It does notcontain an entry for parameter parameter-name.

User Response: Correct the parameters that arebeing passed to the stored procedure.

msgcode: -1034

sqlstate: 38S5Y


GSE1035N The parameter-name parameter,which is being passed to thestored procedure, has an incorrectdata type.

Explanation: The data type for parameterparameter-name that is passed to the storedprocedure is not correct.

User Response: Correct the parameters that arebeing passed to the stored procedure.

msgcode: -1035

sqlstate: 38S5Z

GSE1036W The operation was successful. Butvalues of certain databasemanager and databaseconfiguration parameters shouldbe increased.

Explanation: The operation was successful, butSpatial Extender needs more database anddatabase manager resources. These resources canbe obtained by increasing the values of certaindatabase manager and database configurationparameters.

User Response: Some configuration parametersshould be increased. For example, for thedatabase manager configuration, check theUDF_MEM_SZ parameter, and for the databaseconfiguration, check the APPLHEAPSZparameter. Refer to the IBM DB2 UDB SpatialExtender User’s Guide and Reference for moredetails.

msgcode: +1036

sqlstate: 38S60

GSE1037N The definition of the specifiedcoordinate system namedcoordsys-name is invalid.

Explanation: A coordinate system namedcoordsys-name cannot be created because thedefinition given for it is invalid.

User Response: Specify a correct definition forthe coordinate system.

The function ST_EqualCoordsys can be used to

verify the definition by comparing the coordinatesystem with itself.

msgcode: -1037

sqlstate: 38S61

GSE1038N The WHERE clause specified forthe geocoder named geocoder-nameis invalid. When Spatial Extenderattempted to verify the clause, itencountered SQL error sql-error.

Explanation: The geocoding that you requestedcannot be completed successfully because thewhere clause that determines which rows are tobe geocoded is invalid.

User Response: Specify a syntactically correctWHERE clause.

msgcode: -1038

sqlstate: 38S62

GSE1039N A coordinate system identified bythe specified identifierorganization-coordsys-id incombination with the specifiedorganization organization alreadyexists.

Explanation: Your request to create a coordinatesystem could not be met because thecombination of identifiers that you specified forthe coordinate system (the name of theorganization that defined the system and anumber that this organization assigned to it) wasnot unique. Either these two values must beunique in combination, or they must be null.

User Response: Specify a unique set of valuesfor organization and organization-coordsys-id, orchoose null values for both.

msgcode: -1039

sqlstate: 38S63


GSE1040N A spatial reference system withthe numeric identifier srs-idalready exists.

Explanation: Your request to create a spatialreference system could not be met because thenumeric identifier srs-id that you assigned to italready identifies another spatial referencesystem. A spatial reference system’s identifiermust be unique.

User Response: Specify a unique numericidentifier for the spatial reference system.

msgcode: -1040

sqlstate: 38S64

GSE1041N A coordinate system with thenumeric identifier coordsys-idalready exists.

Explanation: Your request to create a coordinatesystem could not be met because the numericidentifier coordsys-id that you assigned to italready identifies another spatial coordinatesystem. A spatial coordinate system’s identifiermust be unique.

User Response: Specify a unique valuecoordsys-id for the coordinate system.

msgcode: -1041

sqlstate: 38S65

GSE1042N A geocoder with the numericidentifier geocoder-id already exists.

Explanation: Your request to register a geocodercould not be met because the numeric identifierfor the geocoder geocoder-id already identifiesanother geocoder. A geocoder’s identifier must beunique.

User Response: Specify a unique value for thenumeric geocoder identifier.

msgcode: -1042

sqlstate: 38S66

GSE1043N The specified grid indexschema-name.index-name alreadyexists.

Explanation: This index already exists. It mustbe dropped before an index with the same namecan be created.

User Response: Specify a name for the indexthat does not yet exist, or drop the existing indexand retry the operation.

msgcode: -1043

sqlstate: 38S67

GSE1044N The specified coordinate systemcoordsys-name cannot be droppedbecause an existing spatialreference system is based on thiscoordinate system.

Explanation: At least one spatial referencesystem exists that is based on the specifiedcoordinate system coordsys-name. The coordinatesystem cannot be dropped.

User Response: Drop all spatial referencesystems that are based on the specifiedcoordinate system. Then try to drop thecoordinate system again.

msgcode: -1044

sqlstate: 38S68

GSE1045N The specified spatial referencesystem srs-name cannot bedropped because a spatial columnis registered with this spatialreference system.

Explanation: At least one spatial column existsthat is associated with the specified spatialreference system srs-name. The spatial referencesystem cannot be dropped.

User Response: Unregister all spatial columnsthat are associated with the specified spatialreference system. Then try to drop the spatialreference system again.

msgcode: -1045


sqlstate: 38S69

GSE1046N The specified geocodergeocoder-name cannot beunregistered because it is used ina geocoding setup.

Explanation: At least one geocoding setupexists that uses the specified geocodergeocoder-name. The geocoder cannot beunregistered.

User Response: Remove all geocoding setupsthat use the specified geocoder. Then try tounregister the geocoder again.

msgcode: -1046

sqlstate: 38S6A

GSE2001N Spatial Extender could notperform the operation that yourequested.

Explanation: Spatial Extender could notperform the operation that you requested.

User Response: Consult your databaseadministrator.

msgcode: -2001

sqlstate: 38SX0

GSE2002N A database management systemerror has occurred.

Explanation: A database management systemerror has occurred.

User Response: Consult your databaseadministrator. If the problem persists, contactIBM Software Support with the information.

msgcode: -2002

sqlstate: 38SX1

GSE2003N The stored procedure that youinvoked cannot connect to yourworkstation.

Explanation: The stored procedure cannotaccess information that identifies yourworkstation to it.

User Response: Consult your databaseadministrator. If the problem persists, contactIBM Software Support with the information.

msgcode: -2003

sqlstate: 38SX2

GSE2004N Spatial Extender cannot validatethe coordinate system identifierspecified in the SDE transfer filethat you are importing.

Explanation: Spatial Extender cannot validatethe coordinate system identifier specified in theSDE transfer file that you are importing.

User Response: Try one or more of thesemethods:

v Make sure that the spatial reference systemidentifier in the SDE transfer file is pointing tothe right coordinate system identifier.

v Determine whether the correct coordinatesystem identifier is listed in theDB2GSE.ST_COORDINATE_SYSTEMS catalogview. If the identifier is not in this view, letyour database administrator know.

v Determine whether the SDE transfer file iscorrupted. If it is, try to acquire and import anintact copy of it.

msgcode: -2004

sqlstate: 38SX3

GSE2005N Spatial Extender cannot validatethe file that you want to export.

Explanation: There can be one or more reasonsfor this problem. For example, you might not beauthorized to access the file. Or Spatial Extendermight be unable to find or read it, or torecognize data types of the data within it.


User Response: Try one or more of thesemethods:

v Make sure that you specify the file’sfully-qualified path.

v Make sure that the user id under which youare running the gse_export_sde storedprocedure has both read and write access toeach directory in the path.

v Verify that the disk that contains thesedirectories is mounted on the same nodewhere DB2 runs, and that it uses the samemount point that is specified in the path.

v Verify also that Spatial Extender recognizes thedata types of the data that the file contains.

If the error recurs, try to determine whether thefile is corrupted. If it is, try to acquire and exportan intact copy of the file.

msgcode: -2005

sqlstate: 38SX4

GSE2006N An I/O error for a file namedfile-name has occurred.

Explanation: An I/O error for a file namedfile-name has occurred.

User Response: Verify that the file exists, thatyou have the appropriate access to the file, andthat the file is not in use by another process.

msgcode: -2006

sqlstate: 38SX5

GSE2007N Spatial Extender cannot validatethe spatial column into which youwant to import data.

Explanation: The name of the column that youwant to import data into might be specifiedincorrectly, or it might not follow standardnaming conventions. Similarly, the name of thetable to which the column belongs might bespecified incorrectly, or it might not followstandard naming conventions.

User Response: Make sure that the registered

spatial column is listed in theDB2GSE.ST_GEOMETERY_COLUMNS catalogview, that the names of the column and the tableit belongs to are correctly specified, and thatthese names follow standard namingconventions.

msgcode: -2007

sqlstate: 38SX6

GSE2008N Spatial Extender attempted toinsert a null into a registeredspatial column that has a NOTNULL constraint.

Explanation: Spatial Extender attempted toinsert a null into a registered spatial column thathas a NOT NULL constraint.

User Response: Either import the column nulldata into a spatial column that can accept nulls,or ask your database administrator to remove theNOT NULL constraint.

msgcode: -2008

sqlstate: 38SX7

GSE2009N The specified where clause isinvalid.

Explanation: There is a syntax error in thewhere clause you specified.

User Response: Specify a valid where clause.

msgcode: -2009

sqlstate: 38SX8

GSE2012N Spatial Extender was unable toaccess the registered spatialcolumn that you want to importdata into.

Explanation: The user id under which you wantto access the registered spatial column is notauthorized to change the column on which theregistered spatial column is defined.

User Response: Ask your databaseadministrator to grant you the authorization thatyou need (for example, you might need theINSERT or SELECT privilege on the table to


which the column belongs). For moreinformation, refer to IBM DB2 UDB SpatialExtender User’s Guide and Reference.

msgcode: -2012

sqlstate: 38SX9

GSE2014N Spatial Extender was unable toimport data into the registeredspatial column that you specified.

Explanation: Spatial Extender could not locatethe registered spatial column that you want toimport data into.

User Response: Determine whether the spatialcolumn is listed in theDB2GSE.ST_GEOMETRY_COLUMNS catalogview with an associated spatial reference system.If it is not, use the ST_register_spatial_columnstored procedure or the Spatial Columns windowin the Control Center to register the spatialcolumn.

msgcode: -2014

sqlstate: 38SXA

GSE2016N Spatial Extender was unable toimport the file that you requestedto the layer that you specified.

Explanation: The data type of the spatial datathat you want to import is incompatible with thedata type of the layer for which this spatial datais intended.

User Response: Create a new layer whose datatype is compatible with the data type of thespatial data that you want to import. Thenimport the data to this new layer. Alternatively,import a different file—one whose spatial data iscompatible with the layer that you want topopulate.

msgcode: -2016

sqlstate: 38SXB

GSE2021N Spatial Extender was unable toaccess the file that you want toimport.

Explanation: There are several possible reasonsfor this problem. For example, Spatial Extendermight not know the full path to the file, or itmight not recognize the file’s format, or the diskthat contains the file might not be mountedproperly.

User Response: Be sure to specify the file’scomplete path. If you do this, and the errorrecurs, then verify that the file is indeed a shapeor SDE file and not another kind of file that wasmistakenly specified as a shape or SDE file. If thefile is a shape OR SDE file, try one of thefollowing remedies:

v Determine whether the file is corrupted. If itis, attempt to acquire and import an intactcopy of the file.

v If you are accessing the file from anotherworkstation, make sure that:

– The disk that contains the file is mounted.

– This disk uses the same mount point asspecified in the file pathname.

– The user ID that you are using at the otherworkstation has read access to the file.

msgcode: -2021

sqlstate: 38SXC

GSE2023N Spatial Extender was unable toimport attribute data from the filethat you specified.

Explanation: The definition of an attributecolumn in the file could not be translated into adefinition for a corresponding column in thetable to which you want to import data.

User Response: Make sure that the data type,maximum length, and other characteristics of thisattribute column can be translated intoequivalents or counterparts for the attributecolumn to which you are importing data.

msgcode: -2023


sqlstate: 38SXD

GSE2027N Spatial Extender could notperform the import or exportoperation that you requested.

Explanation: There is not enough memory tocomplete the operation. The file that you areimporting or exporting might be corrupted,causing an excessive drain on memory.

User Response: Check to ensure that you havesufficient memory. Then, try to import or exportthe file again. If the error continues to recur, tryto determine whether the file is corrupted. If itis, acquire an intact copy of the file, and importor export this copy. If the problem persists,report it to your database administrator.

msgcode: -2027

sqlstate: 38SXE

GSE2030N Spatial Extender was unable toimport data to the column thatyou specified.

Explanation: The spatial column that youspecified has not been registered.

User Response: If you want to import SDEdata, use the DB2 Control Center or thegse_import_sde stored procedure to register thecolumn and import the data.

msgcode: -2030

sqlstate: 38SXF

GSE2031N Spatial Extender was unable toimport data into the spatialcolumn that you specified.

Explanation: The table on which the spatialcolumn was defined no longer exists.

User Response: If you want to import SDEdata, use the DB2 Control Center or thegse_import_sde stored procedure to recreate thetable and import the data.

msgcode: -2031

sqlstate: 38SXG

GSE2032N Spatial Extender could not importattribute data.

Explanation: One or more attribute columnsspecified in the import file do not havecounterparts in the table to which you areimporting the data.

User Response: Identify the column (or each ofthe columns) in the import file that has nocorresponding column in the table into which thefile is to be imported. Then provide the tablewith the missing column (or columns).Alternatively, you could change the target of theimport to be a table and set of columns otherthan the ones originally intended.

msgcode: -2032

sqlstate: 38SXH

GSE2033N Spatial Extender could not readthe complete file that you want toimport.

Explanation: The file might be corrupted ortruncated.

User Response: Try to import the file again. Ifthe error recurs, try to acquire and import a copyof the file that is not corrupted.

msgcode: -2033

sqlstate: 38SXI

GSE2034N Spatial Extender could not importthe SDE transfer file that yourequested.

Explanation: The data type of the spatial datathat you want to import is incompatible with thedata type of the spatial column for which thisspatial data is intended.

User Response: Create a new spatial columnwhose data type is compatible with the data typeof the spatial data that you want to import. Thenimport the data to this new column.Alternatively, import a different SDE transferfile—one whose spatial data is compatible withthe column that you want to populate.

msgcode: -2034


sqlstate: 38SXJ

GSE2035N The specified coordinate is out ofbounds.

Explanation: Spatial Extender encountered acoordinate that is either too large or too small tofit within the bounds of the coordinate systemassigned to the specified layer. This problemmight arise if the coordinate system isincompatible with layer data or with itsassociated spatial reference system. Alternatively,the problem might be due to a corrupted shapeor SDE transfer file, or to anomalous data thatwas inserted into the layer by mistake.

User Response: Verify that you specified theright identifier for the spatial reference systemthat the specified layer uses. If you did, thissystem might be incompatible with layer data orwith its underlying coordinate system. On thestrength of the possibilities, select or create adifferent spatial reference system for the layer. Ifthe problem recurs, report it to your databaseadministrator.

msgcode: -2035

sqlstate: 38SXK

GSE2100N The number of attribute columnsbeing imported (input-columnscolumns) does not match thenumber of attribute columns inthe target table (table-columnscolumns).

Explanation: If you are importing columns thatcontain attribute data, you have the choice ofeither specifying or not specifying whichattribute columns are being imported and whichcolumns are in the target table. If you specifythese values, this error occurs when the specifiednumber of attribute columns being importeddiffers from the specified number of columns inthe target table. If you do not specify thesevalues, this error occurs when the actual numberof columns being imported differs from theactual number of attribute columns in the targettable.

User Response: Make sure that the number of

specified or actual attribute columns beingimported matches the number of specified oractual columns in the target table.

msgcode: -2100

sqlstate: 38S70

GSE2101N The data typeschema-name.type-name to be usedduring import is unknown toDB2.

Explanation: The spatial data typeschema-name.type-name cannot be used during theimport of spatial data because it does not exist inthe database.

User Response: Create the data type in thedatabase or use a data type that exists.

msgcode: -2101

sqlstate: 38S71

GSE2102N The table specified for import,schema-name.table-name, does notexist.

Explanation: A table namedschema-name.table-name does not exist in thedatabase. Also, Spatial Extender was not asked tocreate a table to hold the data that is to beimported. The data was not imported.

User Response: If the table is to be created bySpatial Extender, specify the appropriate flag.Otherwise, create the table and retry theoperation.

msgcode: -2102

sqlstate: 38S72

GSE2103N The table specified for importschema-name.table-name alreadyexists.

Explanation: Spatial Extender was asked tocreate a table named schema-name.table-name forthe imported data, but a table with that namealready exists in the database. No data wasimported.


User Response: If the table is not to be createdby Spatial Extender, do not indicate that the tableis to be created. Otherwise, specify the name fora table which does not yet exist in the database.

msgcode: -2103

sqlstate: 38S73

GSE2104N The column schema-name.table-name.column-name to import datainto does not exist.

Explanation: The column into which you wantto import data column-name does not exist in thetable schema-name.table-name. No data can beimported into it.

User Response: Correct the column name orcreate the column in the table that is to beimported, or correct the table name.

msgcode: -2104

sqlstate: 38S74

GSE2105W The import operation completedsuccessfully but not all recordsfrom the file were imported.

Explanation: The import operation completedsuccessfully but not all records from the file wereimported. The exception file contains the recordsthat could not be imported, and the messages filethe contains information why those records werenot imported.

User Response: Consult the messages file forthe reason why not all records were imported,correct the problem and repeat the operationwith the original file or the exception file.

msgcode: +2105

sqlstate: 38S75

GSE2106N The data type of the columnschema-name.table-name.column-nameis column-type, which does notmatch the expected typeexpected-type for the data to beimported from file.

Explanation: The column column-name in thetable schema-name.table-name to import data intohas a declared type column-type. column-type doesnot match the type name expected-type for thedata to be imported from the file. No data can beimported.

User Response: Verify the definition of the tablewith the structure of the file to be imported.

msgcode: -2106

sqlstate: 38S76

GSE2107N The table to import data intocould not be created due to errorsql-error.

Explanation: Spatial Extender was asked tocreate a table to import data into, but the tablecould not be created successfully. DB2 returnedsql-error.

User Response: Refer to the description of thissql-error.

msgcode: -2107

sqlstate: 38S77

GSE2108N The method specification methodto identify the attribute columnsto be imported from the file is notcorrect.

Explanation: Either no method specificationwas given or method is not a valid methodspecification. Only ’N’ and ’P’ are supportedmethod specifications for importing spatial datafrom a file.

User Response: Correct the methodspecification and try the method again.

msgcode: -2108

sqlstate: 38S78


GSE2109N A character found-char was foundwhen a character expected-char wasexpected.

Explanation: An unexpected characterfound-char was found in the string that identifiesthe attribute columns to be imported from thefile but expected-char was expected. The statementcannot be processed successfully.

User Response: Correct the string that identifiesthe attribute columns to be imported from thefile.

msgcode: -2109

sqlstate: 38S79

GSE2110N The column position identifierposition in the string string isinvalid.

Explanation: The column position identifierposition specified in the string starting with stringis not in the valid range. Only values greaterthan 0 (zero) and less than or equal to thenumber of columns in the file to be imported canbe specified. The statement cannot be processedsuccessfully.

User Response: Correct the column positionidentifier.

msgcode: -2110

sqlstate: 38S7A

GSE2111N A column named dbf-column-namein the dBASE file is too long.

Explanation: The name of columndbf-column-name in the dBASE file (.dbf) exceedsDB2’s limit for column names.

User Response: Specify a dbf-column-name thatdoes not exceed DB2’s length limit.

msgcode: -2111

sqlstate: 38S7B

GSE2112N The column dbf-column-namecannot be found in the dBASEfile.

Explanation: The name dbf-column-name doesnot identify an existing attribute column in thedBASE file (.dbf). The operation cannot becompleted successfully.

User Response: Specify a column name thatexists in the dBASE file.

msgcode: -2112

sqlstate: 38S7C

GSE2113N The dBASE file data typedbf-data-type for the columndbf-column-name in the dBASE fileis not supported.

Explanation: The dBASE file data typedbf-data-type for the attribute columndbf-column-name in the dBASE file (.dbf) cannotbe mapped to a data type in the DB2 database.The shape file cannot be imported.

User Response: Exclude the column from thecolumn list.

msgcode: -2113

sqlstate: 38S7D

GSE2114N The column position position isout of range. The dBASE filecontains dbf-column-numbercolumns.

Explanation: The specified column positionposition must be a value within the valid range.A valid value must greater than 0 (zero) and lessthan or equal to the dbf-column-number.

User Response: Specify a valid position.

msgcode: -2114

sqlstate: 38S7E



Explanation: A spatial reference system whosenumeric identifier is srs-id does not exist. Thedata cannot be imported.

User Response: Either specify an existingspatial reference system, or create the spatialreference system before attempting the importoperation.

msgcode: -2115

sqlstate: 38S7F

GSE2116N The coordinate system definitioncoordsys-def is too long.

Explanation: The coordinate system definitioncoordsys-def used for the spatial data to beimported is too long. It could not be verifiedwith the coordinate system that underlies thespatial reference system that is to be used for theimported data.

User Response: Verify that the coordinatesystem defined in the projection file (.prj) iscorrect. To skip the verification step, do notsupply the projection file.

msgcode: -2116

sqlstate: 38S7G

GSE2117N The coordinate system definitioncoordsys-def does not match thecoordinate system definition onwhich the spatial reference systemsrs-id is based.

Explanation: The coordinate system coordsys-defdoes not match the coordinate system on whichthe spatial reference system srs-id is based. Bothcoordinate systems must be semanticallyidentical.

User Response: Verify that the coordinatesystem defined in the projection file (.prj)matches the coordinate system of the spatialreference system. To skip the verification step, donot supply the projection file.

msgcode: -2117

sqlstate: 38S7H

GSE2118N The spatial data does not fit intothe spatial reference system withthe numeric identifier srs-id.

Explanation: The spatial data covers an areathat exceeds the minimum and maximumcoordinates of the spatial reference system withthe numeric identifier srs-id.

User Response: Specify a spatial referencesystem which may fully contain the spatial datato be imported. Refer to theDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMScatalog view for the minimum and maximumcoordinate values applicable for the spatialreference system.

msgcode: -2118

sqlstate: 38S7I

GSE2119N The imported data’s spatialreference system, whosenumerical identifier is srs-id1,does not match the targetcolumn’s spatial reference system,whose numeric identifier issrs-id2. The target column’s nameis schema-name.table-name.column-name.

Explanation: The spatial columnschema-name.table-name.column-name wasregistered with a spatial reference system srs-id2assigned to it. This spatial reference system doesnot match the spatial reference system srs-id1,which is used for the spatial data to be importedinto that column. The data cannot be imported.

User Response: Either unregister the spatialcolumn, or specify the same spatial referencesystem for the data to be imported that thecolumn uses.

msgcode: -2119

sqlstate: 38S7J


GSE2120N No data was imported.

Explanation: None of the shape data could beimported. All rows were rejected and written tothe exception file.

User Response: Consult the message file for thereasons why all the spatial data was rejected.

msgcode: -2120

sqlstate: 38S7K

GSE2121N The value restart-count specifyingthe record to restart the operationis out of range. The shape filecontains record-count records.

Explanation: The specified restartCountrestart-count must be a greater than or equal to 0(zero), and less than or equal to record-count.

User Response: Specify a valid number forrestartCount, or specify a null value for theresartCount.

msgcode: -2121

sqlstate: 38S7L

GSE2122N The SQL statement used to importthe shape data does not fit intothe internal buffer.

Explanation: The SQL statement used to importthe shape data into the table does not fit into theinternal buffer. A possible reason for this mightbe too many columns are in the file.

User Response: Import a smaller set of theattribute columns in the shape file.

msgcode: -2122

sqlstate: 38S7M

GSE2123N A buffer to hold the data forrow-count rows cannot beallocated.

Explanation: Spatial Extender tried to use asingle INSERT statement to import at leastrow-count rows, but a buffer to hold the data for

these rows could not be allocated. Too muchmemory was required.

User Response: Specify a commit count for theimport that is less than row-count. Or, specify asmaller set of columns to be imported. This willreduce the amount of memory required.

msgcode: -2123

sqlstate: 38S7N

GSE2124N An invalid type identifier type-idwas found in the header of theshape file to be imported.

Explanation: The data in the shape file does notappear to have a valid spatial data type. Theshape file is possibly corrupted. The data wasnot imported.

User Response: Verify that the shape file isvalid.

msgcode: -2124

sqlstate: 38S7O

GSE2125N A column in the shape file has anunsupported data type type.

Explanation: The shape file contains a columnwhose data type is not supported by SpatialExtender. The shape file could not be imported.

User Response: Import only a smaller set of thecolumns of the shape file and omit the columnwith the unsupported data type.

msgcode: -2125

sqlstate: 38S7P

GSE2126N The header of the shape fileshape-file is invalid.

Explanation: The header of the shape fileshape-file is invalid. The shape file cannot beimported.

The extension of the file name shape-file indicatesin which part of the shape file the error wasencountered. The file extensions include:

.shp main file


.shx index file

.dbf dBASE file

.pri projection file

User Response: Verify and correct the header ofthe shape file.

msgcode: -2126

sqlstate: 38S7Q

GSE2127N The offset offset for the recordrecord-number in the shape indexfile shx-file is invalid.

Explanation: The offset offset for the recordrecord-number in the index file (.shx) shx-file isinvalid. The offset must be greater than or equalto 50 and less than the total length of the mainfile (.shp) of the shape file. The offset ismeasured in 16 bit words.

User Response: Verify and correct the shapefile.

msgcode: -2127

sqlstate: 38S7R

GSE2128N The length of the shape in recordrecord-number of the shape indexfile shx-file is too short.

Explanation: The length of the shape in recordrecord-number found in the shape index fileshx-file is too short. Each shape must consist of atleast 4 bytes (two 16 bit words).


msgcode: -2128

sqlstate: 38S7S

GSE2129N Spatial Extender found anincorrect record numberrecord-number in the shape fileshp-file when expecting recordnumber expected-number.

Explanation: Spatial Extender found anincorrect record number record-number in the

shape file shp-file when expecting record numberexpected-number.


msgcode: -2129

sqlstate: 38S7T

GSE2130N The size of the shape datarecord-size indicated in the shapefile shp-file does not match the sizeindicated in the shape index fileindex-size.

Explanation: The size of the shape datarecord-size indicated in the shape file shp-file doesnot match the size indicated in the shape indexfile index-size.

The main file of the shape file (.shp) is notconsistent with the index file (.shx) and cannotbe processed further.


msgcode: -2130

sqlstate: 38S7U

GSE2131N The data for record record-numberin the dBASE file dbf-file isinvalid.

Explanation: The data for record record-numberin the dBASE file dbf-file that contains theattribute information associated with thegeometries in the shape file is invalid.

Possible explanations are:

v The first byte of the record is neither anasterisk (’*’) nor a space (’ ’).

v The sum of all lengths of the columns in thedBASE file (.dbf) must be equal to the recordsize indicated in the header of the file.

User Response: Verify and correct the dBASEfile.

msgcode: -2131

sqlstate: 38S7V


GSE2132N The data in shape file shape-file isinvalid.

Explanation: The data in shape file shape-file iscorrupted. This shape file cannot be imported.

The file name shape-file indicates in which part ofthe shape file the error was encountered.


msgcode: -2132

sqlstate: 38S7W

GSE2133N The import operation failedbecause the columnschema-name.table-name.column-nameis not nullable.

Explanation: The definition of the columncolumn-name in the existing tableschema-name.table-name indicates that the columnmay not contain nulls. The column is notincluded in the list of columns to be importedand DB2 would not produce the values for thatcolumn by any other means like default values, agenerated column definition or any triggers.

The import operation cannot be completedsuccessfully.

User Response: Include the column in the listof columns to be imported, identify the columnas id-column, or define an alternate way for DB2to generate the values for that column during theimport operation.

msgcode: -2133

sqlstate: 38S7X

GSE2200N The results from the SELECTstatement did not include anyspatial column.

Explanation: The specified SELECT statementfor export operations must reference exactly onespatial column. No data can be exported.

User Response: Correct the SELECT statementso that it references exactly one spatial column.

msgcode: -2200

sqlstate: 38S90

GSE2201N The results from the SELECTstatement included more than onespatial column.

Explanation: The specified SELECT statementfor export operations must specify exactly onespatial column. No data can be exported.

User Response: Correct the SELECT statementso that it references exactly one spatial column.

msgcode: -2201

sqlstate: 38S91

GSE2202N The SQL data type data-type forcolumn column-number in thefullselect describing the data to beexported is not supported forshape files.

Explanation: The SQL data type data-type forcolumn column-number in the fullselect describingthe data to be exported is not supported forshape files. No data can be exported.

User Response: Do not specify a column withthe unsupported type in the SELECT statementfor the export shape operation. You can use theDESCRIBE command to verify the data types forall columns in the result of the SELECTstatement.

msgcode: -2202

sqlstate: 38S92

GSE2203N The data in column column-numberhas a length of length, which istoo long to be exported to a shapefile.

Explanation: The data in column column-numberhas a length of length, which is too long to beexported to a shape file.

User Response: Change the length of thecolumn to be shorter than 256 bytes. You can useDB2’s cast functions to shorten the length of thecolumn.

msgcode: -2203


sqlstate: 38S93

GSE2204N The column name column-nameexceeds the limit of 11 charactersfor dBASE files.

Explanation: The column name column-nameexceeds the restriction of 11 bytes for dBASEfiles. No data is exported.

User Response: Specify a column name with 11or less bytes for the attribute data to be exportedto the dBASE file (.dbf).

msgcode: -2204

sqlstate: 38S94

GSE2205W DB2 returned a SQL warningsql-warning when Spatial Extenderfetched the data to be exported.

Explanation: DB2 returned a SQL warningsql-warning when Spatial Extender fetched thedata to be exported. The warning was ignoredand the data exported.

User Response: Refer to the description ofsql-warning. If the warning is not acceptable,correct the source of the warning and export thedata again.

msgcode: +2205

sqlstate: 38S95

GSE2206W No data was exported.

Explanation: The SELECT statement specifiedfor the export did not retrieve any rows. No datawas exported.

User Response: Specify a SELECT statementthat returns at least one row to be exported.

msgcode: +2206

sqlstate: 38S96

GSE2207W Not all rows referenced by theSELECT statement were exported.

Explanation: The SELECT statement identifiedmore rows than were exported. This error can

occur if an error is encountered during theexport and the operation is terminated.

User Response: Consult the message file.

msgcode: +2207

sqlstate: 38S97

GSE2208N In row row-number, a geometry tobe exported is associated with aspatial reference system whosenumeric identifier is srs-id1. Thisidentifier does not match thenumeric identifier srs-id2 of thespatial reference system used forgeometries in the preceding rows.

Explanation: In row row-number, a geometry tobe exported is associated with a spatial referencesystem whose numeric identifier is srs-id1. Thisidentifier does not match the numeric identifiersrs-id2 of the spatial reference system used forgeometries in the preceeding rows. The rowrow-number was not exported.

User Response: Verify that all geometries to beexported have the same spatial reference systemidentifier. If not, use the ST_Transform method inthe SELECT statement to convert all geometriesto the same spatial reference system.

msgcode: -2208

sqlstate: 38S98

GSE2209N The geometry in row row-numberto be exported is a null value.

Explanation: The notion of null values is notsupported by the data in the file to which youwant to export geometries. The geometry to beexported in row row-number is a null value andcannot be exported.

User Response: Exclude rows with geometriesthat are null values from the export bymodifying the SELECT statement accordingly.

msgcode: -2209

sqlstate: 38S99


GSE2210N The spatial reference system forthe geometry in row row-number isinvalid. This spatial referencesystem’s numerical identifier issrs-id.

Explanation: In row row-number, the geometrythat is to be exported uses an invalid spatialreference system. The geometry cannot beexported.

User Response: Correct the indicated geometryor exclude the row from the export operation bymodifying the SELECT statement accordingly.

msgcode: -2210

sqlstate: 38S9A

GSE2211N The spatial data to be exported isassociated with a spatial referencesystem whose numeric identifieris srs-id. The coordinate system onwhich this spatial reference systeis based does not match thecoordinate system definitioncoordsys-def for the file to whichthe exported data is to beappended.

Explanation: The spatial data to be exported isassociated with a spatial reference system whosenumeric identifier is srs-id. The coordinatesystem on which this spatial reference system isbased does not match the coordinate systemcoordsys-def for the file to which the exporteddata is to be appended. No data was exported.

User Response: Append the data to a file whichhas a matching coordinate system, transform thespatial data to the corresponding coordinatesystem, or export the data to a separate file.

msgcode: -2211

sqlstate: 38S9B

GSE2212N The attribute data does not matchthe dBASE file.

Explanation: The specified SELECT statementfor the export operation produces attribute datathat does not match the dBASE file (.dbf).

The attribute data from the SELECT statementfor the export operation cannot be appended tothe dBASE file. Possible causes are:

v The number of columns do not match.

v The data type of column does not match.

v The attribute column name does not match.

User Response: Either correct the SELECTstatement, or do not append to the specifieddBASE file.

msgcode: -2212

sqlstate: 38S9C

GSE2213W The geometry to be exported tothe file in row row-number is anull value.

Explanation: The geometry to be exported tothe file in row row-number is a null value. Therow was not exported.

User Response: Modify the SELECT statementto exclude geometries that have null values.

msgcode: +2213

sqlstate: 38S9D

GSE2214W Not enough memory is availableto export the geometry in rowrow-number.

Explanation: Not enough memory is availableto export the geometry in row row-number. Therow was not exported, but the exportingoperation continued.

User Response: Provide more memory, ormodify the SELECT statement to exclude thegeometry from that row.

msgcode: +2214

sqlstate: 38S9E


GSE2215N The geometry to be appended tothe shape file as numberrecord-number has a shape typegeometry-shape-type which does notmatch the type in the shape filefile-shape-type.

Explanation: The geometry to be appended tothe shape file as number record-number has anshape type geometry-shape-type which does notmatch the type in the shape file file-shape-type.The geometry cannot be exported to that file.

Possible shape types are:

0 Empty geometry.

1 Point without Z coordinates andmeasures.

3 Linestring or multilinestring without Zcoordinates and measures.

5 Polygon or multipolygon without Zcoordinates and measures.

8 Multipoint without Z coordinates andmeasures.

9 Point with Z coordinate and nomeasures.

10 Linestring or multilinestring with Zcoordinates and no measures.

11 Point with Z coordinate and measure.

13 Linestring or multilinestring with Zcoordinates and measures.

15 Polygon or multipolygon with Zcoordinates and measures.

18 Multipoint with Z coordinates andmeasures.

19 Polygon or multipolygon with Zcoordinates and no measures.

20 Multipoint with Z coordinates and nomeasures.

21 Point with measure and no Zcoordinates.

23 Linestring or multilinestring withmeasures and no Z coordinates.

25 Polygon or multipolygon with measuresand no Z coordinates.

28 Multipoint with measures and no Zcoordinates.

User Response: Convert the geometry to thecorrect type, or export it to another shape file.

msgcode: -2215

sqlstate: 38S9F

GSE2216N The shape data to be exported isinvalid.

Explanation: Before Spatial Extender exportsgeometries to a shape file, it converts them intoshape data. This error was returned because theshape data into which a geometry was convertedis invalid. The geometry was not exported.

Possible explanations are:

v The shape data has an odd number of bytes.

v The shape data is too short to contain allinformation.

v An unknown shape indication was returned.

v The information about the minimum boundingrectangle is not consistent with the typeindication.


msgcode: -2216

sqlstate: 38S9G

GSE2299N The shape file file-name has aninvalid file size.

Explanation: Shape file file-name has an invalidfile size. Shape files have a file size that is amultiple of 16-bit words. Therefore, their size isalways even. The shape file might be corrupt. Itcannot be used.


msgcode: -2299

sqlstate: 38S9H


GSE3000N Null SRS identifier.

Explanation: A null value was passed to thefunction or method instead of a numeric spatialreference system identifier.

User Response: Specify a numeric spatialreference system identifier for an existing spatialreference system. Refer to the Spatial Extendercatalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMSfor the defined spatial reference systems.

msgcode: -3000

sqlstate: 38SU0

GSE3001N Invalid SRS identifier srs-id.

Explanation: The spatial reference systemidentifier srs-id that was provided to the spatialfunction or method does not identify an existingspatial reference system.

User Response: Specify an existing numericspatial reference system identifier that is definedin the Spatial Extender catalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS,or create a spatial reference system that isidentified by srs-id.

msgcode: -3001

sqlstate: 38SU1

GSE3002N Null unit name.

Explanation: A null was specified as a unit ofmeasure. The specification for a unit of measuremust be the unit itself (for example, “meter”). Itcannot be a null.

User Response: Either omit the unit of measurewhen calling the spatial function or method, orspecify an existing unit of measure. Consult theSpatial Extender catalog viewDB2GSE.ST_UNITS_OF_MEASURE forsupported units.

msgcode: -3002

sqlstate: 38SU2

GSE3003N Unknown unit unit-name.

Explanation: The unit unit-name that wasprovided to the spatial function or method doesnot identify an existing unit of measure.

User Response: Either omit the unit of measurewhen calling the spatial function or method, orspecify an existing unit of measure. Consult theSpatial Extender catalog viewDB2GSE.ST_UNITS_OF_MEASURE forsupported units.

msgcode: -3003

sqlstate: 38SU3

GSE3004N Unsupported conversion to unitunit-name.

Explanation: The conversion to the unitunit-name is not supported.

The functions ST_Area, ST_Buffer, ST_Length,and ST_Perimeter cannot accept a linear unit ofmeasure if the given geometry is not in aprojected coordinate system.

User Response: Use one of the followingmethods:

v Omit the unit of measure when calling thespatial function or method.

v Specify an angular unit of measure.

v Project the geometry into a projectedcoordinate system using the ST_Transformfunction. Consult the Spatial Extender catalogviewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMSfor applicable spatial reference system.

msgcode: -3004

sqlstate: 38SU4

GSE3005N No unit in SRS.

Explanation: The spatial reference system forthe geometry does not have an associated linearor angular unit. The operation cannot beperformed in the requested unit of measure.

User Response: Either represent the geometry


in a correct spatial reference system, which doeshave an associated linear or angular unit ofmeasure, or omit the unit parameter when yourequest the operation.

msgcode: -3005

sqlstate: 38SU5

GSE3006N Invalid internal type id.

Explanation: The internal data type identifierfor this geometry is a null value and thereforeinvalid.

This error can occur if the internal representationof the geometry is corrupted, or if the geometrywas not constructed by one of the supportedconstructor functions or methods.

User Response: Construct the geometry againby using one of the supported constructorfunctions or methods.

msgcode: -3006

sqlstate: 38SU6

GSE3007N Unknown internal type id type-id.

Explanation: The value of the internal typeidentifier type-id for the geometry is not valid.



msgcode: -3007

sqlstate: 38SU7

GSE3008N Internal type id mismatch(type-id1, type-id2).

Explanation: A mismatch of internal data typeidentifiers was found. Spatial Extender expectedto retrieve a geometry whose internal data typeidentifier is type-id2, but instead retrieved a

geometry whose internal data type identifier istype-id1.



msgcode: -3008

sqlstate: 38SU8

GSE3009W Invalid part number part-number.

Explanation: The specified part numberpart-number is not valid. A null value wasreturned.

User Response: If the geometry is not empty,then specify a valid part number, which shouldbe greater than 0 (zero) and less then or equal tothe maximum number of parts in the geometrycollection.

You can use the ST_NumGeometries function todetermine the number of parts of the geometrycollection.

If the geometry is empty, the method should notbe applied.

msgcode: +3009

sqlstate: 01HS0

GSE3010W Invalid ring number ring-number.

Explanation: The specified number ring-numberfor an internal ring is not valid. A null value wasreturned.

User Response: If the polygon value is notempty, then specify a valid ring number, whichshould be greater than or equal to 1 (one) andless than or equal to the maximum number ofinterior rings in the polygon.

If the polygon is empty, the function or methodshould not be applied. You can use the functionST_NumInteriorRings to determine the numberof interior rings of the polygon.


msgcode: +3010

sqlstate: 01HS1

GSE3011W Invalid point numberpoint-number.

Explanation: The specified point numberpoint-number is not valid. A null value wasreturned.

User Response: If the curve value is not empty,then specify a valid point number, which shouldbe greater than 0 (zero) and less than or equal tothe maximum number of points in the curve. Ifthe curve is empty, the function or methodshould not be applied.

You can use the ST_NumPoints function todetermine the number of points used to definethe curve.

msgcode: +3011

sqlstate: 01HS2

GSE3012N Invalid DE9-IM matrix.

Explanation: The intersection matrix matrixspecified for the ST_Relate function is not valid.The matrix must be exactly 9 characters long,and each character in the matrix must be one ofthe following: ’T’, ’F’, ’0’, ’1’, ’2’, or ’*’.

User Response: Specify a valid intersectionmatrix.

msgcode: -3012

sqlstate: 38SU9

GSE3013N Exterior ring is no ring.

Explanation: The linestring that is to to serve asthe new exterior ring for the polygon is not aring. To be a ring, the linestring must be bothsimple and closed. One or both of these twoconditions is not met.

User Response: Specify a simple and closedlinestring for the new exterior ring of thepolygon.

msgcode: -3013

sqlstate: 38SUA

GSE3014N Interior ring is no ring.

Explanation: The linestring that is to serve as anew interior ring for the polygon is not a ring.To be a ring, the linestring must be both simpleand closed. At least one of these two conditionsis not met.

User Response: Specify a simple and closedlinestring for the new interior ring of thepolygon.

msgcode: -3014

sqlstate: 38SUB

GSE3015N Transformation to SRS srs-idfailed. rc = reason-code.

Explanation: The geometry could not betransformed from the spatial reference system itis represented into the spatial reference systemwith the numeric identifier srs-id. The transformfailed with reason code reason-code.

The reason codes have the following meanings:

-2008 The geometry is invalid.

-2018 Not enough memory is available tosuccessfully complete thetransformation.

-2020 The spatial reference systems are notcompatible. Both spatial referencesystems must be based directly orindirectly on the same geographiccoordinate system.

-2021 One or more points of the resultinggeometry would be outside themaximum possible extent for the newspatial reference system. The resultinggeometry cannot be represented in thenew spatial reference system.

-2025 The definition of the new spatialreference system is not valid.

-2026 An internal error occurred during theprojection of the geometry.

User Response: Represent the geometry in a


spatial reference system that can be transformedinto the spatial reference system identified bysrs-id, or specify a different spatial referencesystem identifier to transform the geometry into.

msgcode: -3015

sqlstate: 38SUC

GSE3016N Unsupported cast type-id1, type-id2.

Explanation: The attempted cast operation fromthe data type with the internal type identifiertype-id1 to the data type with the internal typeidentifier type-id2 is not supported. The geometrycannot be processed further.

User Response: Specify a supported castoperation. For more information, refer to the IBMDB2 UDB User’s Guide and Reference for thesupported cast functions.

msgcode: -3016

sqlstate: 38SUD

GSE3017N XSLT path too long.

Explanation: The path to the style sheet fileGmlToWkt.xsl is too long. The absolute path toopen the file cannot be constructed.

User Response: Choose a shorter path for theDB2 instance. On Unix systems, symbolic linkscan be used to shorten the path name.

msgcode: -3017

sqlstate: 38SUE

GSE3018N XML Extender not available.

Explanation: IBM DB2 UDB XML Extender isrequired to process a geometry in GeographicMarkup Language (GML) representation. Thegeometry cannot be constructed successfully.

User Response: Install IBM DB2 UDB XMLExtender or provide the geometry information inwell-known text representation.

msgcode: -3018

sqlstate: 38SUF

GSE3019N XSLTranform failed (sqlstate).

Explanation: DB2 XML Extender’s functionXSLTransform could not convert therepresentation of the geometry encoded inGeographic Markup Language (GML) to awell-known text representation (WKT). Thefunction returned with SQLSTATE sqlstate. Thegeometry cannot be constructed successfully.

User Response: Verify the GML representationof the geometry. If the GML representation isvalid, refer to the SQLSTATE for theXSLTransform function from DB2 XML Extender.

msgcode: -3019

sqlstate: 38SUG

GSE3020N Invalid Z coordinate and measurecombination.

Explanation: The geometries that are to beprocessed by the function or method are notrepresented using the same dimensions withrespect to their Z coordinates and measures.

All the geometries must either contain Zcoordinates or contain no Z coordinates. All thegeometries must either contain measures orcontain no measures.

User Response: Provide geometries to thefunction or method that are represented usingthe same dimensions with respect to their Zcoordinates and measures.

msgcode: -3020

sqlstate: 38SUH

GSE3021N Locator failure. Reason code=reason-code.

Explanation: An internal error occurred when aspatial function or method operated on a LOBlocator. The reason code reason-code was returnedby a locator function.

User Response: Refer to the DB2 ApplicationDevelopment Guide to determine the meaning ofreason-code returned from the LOB locatoroperation and correct the problem. If theproblem persists, contact IBM Software Support.


msgcode: -3021

sqlstate: 38SUI

GSE3022N Representation too long(append-length vs. written-lengthbytes).

Explanation: The representation of the geometryin Geographic Markup Language (GML),well-known text (WKT), well-known binary(WKB), or the shape representation would be toolong. From append-length bytes, onlywritten-length bytes could be appended to theencoding. A representation of the geometrycannot be created.

User Response: Simplify the geometry byomitting points that are not essential for thegeometry. You can use the ST_Generalizefunction for this procedure. Alternatively, breakdown the geometry into several smallergeometries.

msgcode: -3022

sqlstate: 38SUJ

GSE3023N Representation too short (lengthbytes).

Explanation: The representation of the geometryin well-known binary (WKB) representation orthe shape representation is only length byteslong. It needs to be at least 4 bytes long and itmust also be long enough to contain all of thegeometry points.

User Response: Provide a valid well-knownbinary representation or shape representation tothe function or method.

msgcode: -3023

sqlstate: 38SUK

GSE3024N Internal geometry too short.

Explanation: The internal representation of thegeometry is too short. It could not be processedfurther.

This error can occur if the internal representationof the geometry is corrupted, or if the geometry

was not constructed by one of the supportedconstructor functions or methods.

User Response: Construct the geometry againusing one of the supported constructor functionsor methods.

msgcode: -3024

sqlstate: 38SUL

GSE3025N Geometry inconsistent.

Explanation: The geometry value is inconsistentand cannot be processed any further.

User Response: Recreate the geometry from avalid binary or text representation.

msgcode: -3025

sqlstate: 38SUM

GSE3026N Inconsistent no. of points(indicated-number vs. data-number).

Explanation: An internal parameter of thegeometry indicates that the geometry datacontains indicated-number points. But the actualgeometry data contains data-number points.Because of this inconsistency, the geometry willnot be used further in the processing.


User Response: Recreate the geometry using thefunctions or methods supported by SpatialExtender.

msgcode: -3026

sqlstate: 38SUN

GSE3027N Point is empty.

Explanation: It is invalid to specify an Xcoordinate, Y coordinate, Z coordinate, ormeasure for an empty point.

If the point is constructed by the constructorfunction ST_Point, the point’s X and Ycoordinates must both be null. Furthermore, no Z


coordinate or measure should be specified unlessit is a null value.

If the mutators ST_X, ST_Y, ST_Z, or ST_M areused to modify an empty point, the point’s Xand Y coordinates must both be null. No Zcoordinate or measure should be specified unlessit is null.

User Response: Use mutators ST_X, ST_Y,ST_Z, or ST_M to modify points that are notempty, or construct the point by specifying bothX and Y coordinates with values that are notnull.

msgcode: -3027

sqlstate: 38SUO

GSE3028N Inconsistent coordinates.

Explanation: If a new point is constructed, boththe X and Y coordinates must be specified. Bothcoordinates must be either null or not null.

If both coordinate values are null, the resultingpoint will be empty. In that case, no Z coordinateor measure should be specified unless it is null.

User Response: Specify null values for both theX and Y coordinates, or specify values that arenot null for both coordinates.

msgcode: -3028

sqlstate: 38SUP

GSE3029N Invalid byte order byte-order.

Explanation: The byte order in the binaryrepresentation of the geometry must be either 0(zero) or 1 (one), but it is byte-order.

In the well-known binary representation, a byteorder of 0 (zero) indicates big endian format, anda byte order of 1 (one) indicates little endianformat.

User Response: Correct the byte order in thebinary representation so that it is either 0 (zero)or 1 (one).

msgcode: -3029

sqlstate: 38SUQ

GSE3030N Invalid number of pointsnum-points in geometry.

Explanation: The geometry has an invalidnumber of points num-points. This number mustbe greater than or equal to 0 (zero).

If the geometry is not empty, then the followingconditions must be met:

point The geometry must have exactly onepoint.

linestringThe geometry must have 2 or morepoints defining it.

polygonThe geometry must have 3 or morepoints defining it.

User Response: Construct the geometry byusing the functions or methods supported bySpatial Extender.

msgcode: -3030

sqlstate: 38SUR

GSE3031N Invalid extent (min-coord vs.max-coord) in geometry.

Explanation: The extent of the geometry in oneof the dimensions is invalid. The minimumcoordinate min-coord must be less than or equalto the maximum coordinate max-coord for alldimensions of the geometry.

User Response: Construct the geometry byusing the functions or methods supported bySpatial Extender.

msgcode: -3031

sqlstate: 38SUS

GSE3032N Aggregation failure.

Explanation: A mismatch between internalidentifiers was encountered for the computationof a spatial aggregate.

Aggregate functions are not supported if used inany of the following situations:

v In the partitioned environment.


v A GROUP BY clause is used in the query thatcontains the spatial aggregate.

v Any function other than the DB2 aggregatefunction MAX is used.

v The aggregate function is not used in thecorrect context.

User Response: Make sure that you use theaggregate function in a way that is supported bySpatial Extender.

msgcode: -3032

sqlstate: 38SUT

GSE3033N Invalid binary data (type idstype-id1, type-id2).

Explanation: A binary representation that ispassed as input to this spatial function ormethod has to represent a geometry whose datatype identifier is type-id2. But the representationthat was actually passed to the function ormethod represents a geometry whose data typeidentifier is type-id1. No geometry could beconstructed.

User Response: Either call the correct functionor method which constructs geometries of typetype-id2 or correct the binary representation torepresent a geometry of type-id1.

msgcode: -3033

sqlstate: 38SUU

GSE3034N Invalid text data (type ids type-id1,type-id2).

Explanation: A text representation that ispassed as input to this spatial function ormethod has to represent a geometry whose datatype identifier is type-id2. But the representationthat was actually passed to the function ormethod represents a geometry whose data typeidentifier is type-id1. No geometry could beconstructed.

User Response: Either call the correct functionor method which constructs geometries of typetype-id1 or correct the text representation torepresent a geometry of type-id2.

msgcode: -3034

sqlstate: 38SUV

GSE3035W Curve not changed.

Explanation: The curve was not changedbecause the specified point to be appended tothe curve was empty.

User Response: Append a point that is notempty to the curve.

msgcode: +3035

sqlstate: 01HS3

GSE3036W Geometry not accurate.

Explanation: The resulting geometry could notbe represented accurately in the spatial referencesystem. One of the scale factors is too small anddoes not allow for a high enough precision torepresent each point that defines the resultinggeometry.

For example, consider a linestring with awell-known text representation of ’linestring m (10 10 8, 10 11 12 )’ represented in a spatialreference system that includes a scale factor of 1(one) for X coordinates and a scale factor of 1(one) also for Y coordinates. If the functionST_MeasureBetween is applied to that linestring,and the upper and lower bounds for themeasures are 9 and 10, respectively, the resultinglinestring, represented in its well-known textrepresentation, would have to be ’linestring m (10 10.25 9, 10 10.50 10 )’. However, the scalefactor of 1 (one) for the Y coordinates preventsthe representation of fractions. The coordinates10.25 and 10.50 cannot be represented withoutrounding that would produce an incorrect result.Such coordinates will be removed from thegeometry.

User Response: Represent the geometry in aspatial reference system that uses larger scalefactors. Alternatively, choose different parametersthat influence the resulting geometry.

msgcode: +3036

sqlstate: 01HS4


GSE3037N Invalid Geographic MarkupLanguage (GML).

Explanation: An invalid GML representationwas entered as input for the function that youinvoked to construct a geometry from it.

User Response: Correct the GMLrepresentation, and invoke the function again. Todetermine the proper format for the GMLrepresentaion, refer to the IBM DB2 UDB SpatialExtender User’s Guide and Reference.

msgcode: -3037

sqlstate: 38SUW

GSE3300N Invalid grid size grid-size-number.

Explanation: The grid size identified by itsposition grid-size-number is invalid. One of thefollowing invalid specifications was made whenthe grid index was created with the CREATEINDEX statement:

v A number less than 0 (zero) was specified asthe grid size for the first, second, or third gridlevel.

v 0 (zero) was specified as the grid size for thefirst grid level.

v The grid size specified for the second gridlevel is less than the grid size of the first gridlevel but it is not 0 (zero).

v The grid size specified for the third grid levelis less than the grid size of the second gridlevel but it is not 0 (zero).

v The grid size specified for the third grid levelis greater than 0 (zero) but the grid sizespecified for the second grid level is 0 (zero).

The function ST_GetIndexParms can be used toretrieve the values used for the parametersspecified when the index was created.

User Response: Drop the grid index and createa new grid index using valid grid sizes only.

msgcode: -3300

sqlstate: 38SI0

GSE3301N Invalid z-order parameterparameter-number.

Explanation: The parameter identified by itsposition parameter-number for a Z-Order indexcontains an invalid value. One of the followinginvalid specifications was made in the CREATEINDEX statement that was used to create theindex to which the geometry is to be added:

v A null value was specified for the parameter.

v A negative number was specified for a scalefactor (this rule applies to parameter numbers2 and 4 only).


User Response: Drop the spatial z-order indexand create a new index using only validparameters.

msgcode: -3301

sqlstate: 38SI1

GSE3302N No point to be indexed.

Explanation: The geometry to be indexed usinga Z-Order index is not a point. The Z-Orderindex supports only points, and the index entrycannot be generated.

User Response: Do not insert a geometry that isnot a point into a column that has a Z-Orderindex defined on it. Either drop the index or donot insert the geometry.

msgcode: -3302

sqlstate: 38SI2

GSE3303N Invalid quad tree parameterparameter-number.

Explanation: An invalid parameter wasspecified when the quad tree index was created.The parameter is identified by its positiongrid-size-number.

One of the following invalid specifications wasmade:


v A null value was specified for the parameter.

v A negative number was specified for a scalefactor (this rule applies to parameter numbers3 and 5 only).

v A value less than 1 (one) was specified for thefirst parameter.


User Response: Drop the spatial quad treeindex and create a new index using only validparameters.

msgcode: -3303

sqlstate: 38SI3

GSE3400C Unknown error error-code.

Explanation: An internal error with codeerror-code was encountered when a geometry wasprocessed.

User Response: Note the error and contact IBMSoftware Support.

msgcode: -3400

sqlstate: 38SS0

GSE3401N Invalid WKT.

Explanation: An invalid well-known textrepresentation was entered as input for thefunction that you invoked to construct ageometry from it.

User Response: Correct the well-known textrepresentation, and invoke the function again. Todetermine the proper format for well-known textrepresentaion, refer to the IBM DB2 UDB SpatialExtender User’s Guide and Reference.

msgcode: -3401

sqlstate: 38SS1

GSE3402C Insufficient memory.

Explanation: Not enough memory was availablefor the spatial function or method that youinvoked.

User Response: Make more memory availableto the DB2 process that executes the function ormethod.

msgcode: -3402

sqlstate: 38SS2

GSE3403N Invalid geometry type.

Explanation: An invalid type of geometry waspassed to the function or method that youinvoked.

User Response: Specify a valid geometry. Formore information, refer to the IBM DB2 UDBSpatial Extender User’s Guide and Reference.

msgcode: -3403

sqlstate: 38SS3

GSE3404N Parentheses not balanced.

Explanation: The number of openingparentheses in the well-known textrepresentation is not the same as the number ofclosing parentheses.

User Response: Reenter the well-known textrepresentation, providing matching pairs ofparentheses.

msgcode: -3404

sqlstate: 38SS4

GSE3405N Too many parts specified.

Explanation: The number of parts indicated inthe binary or text representation of the geometryis greater than the actual number of partssupplied. Either the number of parts indicated istoo high or not all the parts were supplied.

User Response: Specify the correct number ofparts or supply all parts for the geometry.

msgcode: -3405


sqlstate: 38SS5

GSE3406N Incorrect geometry type.

Explanation: The wrong type of geometry waspassed to the function or method that youinvoked. For example, a linestring might havebeen passed to a function or method that takesonly polygons as input.

User Response: Either pass to the function ormethod a type of geometry that it can process, oruse a function or method that accepts the type ofgeometry that you want to pass.

msgcode: -3406

sqlstate: 38SS6

GSE3407N Text is too long.

Explanation: The geometry contains too muchdetail to be converted to its well-known textrepresentation. The well-known textrepresentation exceeds the maximum allowablelength (2 gigabytes).

User Response: Simplify the geometry - forexample, by using the ST_Generalize function -or convert the geometry to its well-known binaryrepresentation.

msgcode: -3407

sqlstate: 38SS7

GSE3408N Invalid parameter value.

Explanation: An invalid parameter wasencountered.

User Response: Refer to the IBM DB2 UDBSpatial Extender User’s Guide and Reference forthe function’s correct syntax and retry theoperation. If the problem persists, contact IBMSoftware Support.

msgcode: -3408

sqlstate: 38SS8

GSE3409N Invalid geometry produced.

Explanation: The parameters provided for thefunction or method have produced an invalidgeometry; for example, an invalid shaperepresentation. An invalid geometry is one thatviolates a geometry property.

User Response: Construct the geometry againfrom a valid representation.

msgcode: -3409

sqlstate: 38SS9

GSE3410N Incompatible geometries.

Explanation: The function or method expectedtwo geometries of a certain type and did notreceive them. For example, the ST_AddPointfunction expects two geometries, one arepresentation and the other a point.

User Response: Specify geometries that thefunction or method accepts as valid input. Todetermine what types of geometries are valid forthis function or method, refer to the IBM DB2UDB Spatial Extender User’s Guide andReference.

msgcode: -3410

sqlstate: 38SSA

GSE3411N Invalid geometry.

Explanation: The function or method cannotprocess the geometry passed to it because one ormore properties of the geometry violate thegeometry’s integrity.

User Response: Use the ST_IsValid function tovalidate the geometry. Construct the geometryagain from a correct representation if it is notvalid.

msgcode: -3411

sqlstate: 38SSB

GSE3412N Too many points.

Explanation: The construction of a geometryhas exceeded the 1-megabyte storage limit; the


geometry has too many points.

User Response: Construct a geometry thatcontains fewer points. Or, if possible, removesome points. For performance and storageconsiderations, include only those points that areneeded to render a geometry.

msgcode: -3412

sqlstate: 38SSC

GSE3413N Geometry too small.

Explanation: The geometry returned by theST_Difference, ST_Intersection,ST_SymDifference, or ST_Union function is toosmall to be represented accurately in the currentspatial reference system.

For example, this can happen if the internalcomputation constructs a very thin polygon, butthe scale factor of the spatial reference system isso low that the geometry would collapse to alinestring if it were to be represented in thisspatial reference system. It would lose itsproperty as a polygon.

User Response: Use a spatial reference systemfor the calculation which allows for a higherresolution. The ST_Transform function can beused to convert a geometry from one spatialreference system into another.

msgcode: -3413

sqlstate: 38SSD

GSE3414N Buffer out of bounds.

Explanation: The ST_Buffer function has createda buffer around the provided geometry that isoutside the range of the coordinates to which thespatial reference system applies.

Refer to the Spatial Extender catalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS todetermine the minimum and maximum absolutevalues for each of the dimensions. These valuesmust not be exceeded by the calculated buffer.

User Response: Either reduce the distance to beused for the buffer calculation, or change thespatial reference system in which the calculation

is done. The ST_Transform function can be usedto convert geometries from one spatial referencesystem into another.

msgcode: -3414

sqlstate: 38SSE

GSE3415N Invalid scale factor.

Explanation: A scale factor for any of the fourdimensions (X, Y, Z, and M) must be greater thanor equal to 1 (one).

User Response: Use a correctly defined spatialreference system to represent the geometry.

msgcode: -3415

sqlstate: 38SSF

GSE3416N Coordinate out of bounds.

Explanation: A coordinate cannot berepresented in the spatial reference systembecause, in at least one dimension, it exceeds thepossible minimum or maximum absolute valuewithin the system’s range of values.

Refer to the Spatial Extender catalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS todetermine the minimum and maximum absolutevalues for each of the dimensions.

User Response: Determine whether thecoordinate is correct. If it is, determine whether itfits within the extent of the spatial referencesystem that you are using. For information aboutthis spatial reference system, consult theDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMScatalog view.

msgcode: -3416

sqlstate: 38SSG

GSE3417N Invalid coordsys definition.

Explanation: There are one or more errors inthe text representation of the definition of thecoordinate system on which the geometry’sspatial reference system is based. Therepresentation cannot be converted into a validprojection.


User Response: Verify the coordinate systemdefinition of the spatial reference system.Alternatively, construct the geometry in a spatialreference system that is associated with a validcoordinate system. The ST_EqualCoordsysfunction can be used to verify the coordinatesystem definition by comparing it with itself.

msgcode: -3417

sqlstate: 38SSH

GSE3418N Projection error.

Explanation: An error occurred during anattempt to project a geometry to another spatialreference system.

User Response: Make sure that the geometry iswithin the legal domain of the projection.

msgcode: -3418

sqlstate: 38SSI

GSE3419N Polygon rings overlap.

Explanation: The rings of a polygon overlap. Bydefinition, the inner and outer rings of a polygonmust not overlap. They can intersect only at atangent, which means the rings can only touchbut not cross each other.

User Response: Specify the coordinates for thepolygon that will not produce overlapping rings.Note that the scale factors of the spatial referencesystem for the geometry have an influence on theprecision.

msgcode: -3419

sqlstate: 38SSJ

GSE3420N Too few points.

Explanation: The error is a result of one of thefollowing:

v Linestrings must consist of at least two points,and polygons must consist of at least fourpoints.

v The geometry cannot be constructed from thepoints that you have specified.

Note that if the geometry to be constructed isempty, these rules do not apply.

User Response: Construct the geometry againfrom a valid set of points.

msgcode: -3420

sqlstate: 38SSK

GSE3421N Polygon is not closed.

Explanation: The inner and outer rings thatdefine the polygon must be closed. A ring isclosed if the start and end points are identical inthe X and Y dimensions. If the polygon has Zcoordinates, then the start and end points mustalso be identical to the Z coordinates. Note thatthis rule does not apply to measures, which canbe different for the start and end points.

User Response: Specify inner and outer ringsfor the polygon that have the same points for thestart and end points in the X and Y dimension. Ifthe polygon has Z coordinates, the start and endpoints of the Z coordinate points also have to beidentical. If the polygon has measures, the startand end points can be different.

msgcode: -3421

sqlstate: 38SSL

GSE3422N Invalid exterior ring.

Explanation: The exterior ring of the polygon isnot valid.

The exterior ring of a polygon must enclose allinterior rings of the polygon. All interior ringshave to be completely inside the area that isdefined by the outer ring and must not cross theexterior ring.

User Response: Specify a geometry that consistsof a valid set of interior and exterior rings, wherethe interior rings lie fully within the area that isenclosed by the exterior ring to represent it.

If the geometry has multiple polygons, use amultipolygon.

msgcode: -3422

sqlstate: 38SSM


GSE3423N Polygon has no area.

Explanation: The specified polygon lacks aninterior that covers an area that is not the emptyset in the X and Y dimensions.

A geometry is a polygon only if its coordinatesspan two dimensions in the 2-dimensional spacedefined by the X and Y coordinates.

User Response: Specify a polygon that enclosesan area that is not empty. If the polygon isempty, construct an empty polygon.

msgcode: -3423

sqlstate: 38SSN

GSE3424N Exterior rings overlap.

Explanation: The exterior rings of distinctpolygons in a multipolygon overlap. Distinctpolygons in a multipolygon must not overlap,and the boundaries must touch only at a finitenumber of points. That means the polygons mustnot share line segments.

The scale factors of the spatial reference systemthat is used to represent the geometry influencesthe precision that applies to the coordinates.Rounding operations performed when thegeometry is converted to the representation inthe spatial reference system might cause a loss inprecision and, subsequently, this error.

User Response: Specify coordinates for thepolygon that will not produce overlapping rings.

Note that the scale factors of the spatial referencesystem have an influence on precision.

Refer to the Spatial Extender catalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMSfor the scale factor used for the spatial referencesystem in which the geometry will berepresented.

msgcode: -3424

sqlstate: 38SSO

GSE3425N Polygon intersects itself.

Explanation: A ring of a polygon cannotintersect itself. The start and end points on each

ring of the polygon must be reached twice whentraversing the ring. All other points must only bereached once. This holds true also for the linesegments that define the rings of the polygon.

The scale factors of the spatial reference systemthat is used to represent the geometry influencesthe precision that applies to the coordinates.Rounding operations performed when thegeometry is converted to the representation inthe spatial reference system might cause a loss inprecision and, subsequently, this error.

User Response: Construct a valid polygon inwhich the rings do not intersect themselves.

Refer to the Spatial Extender catalog viewDB2GSE.ST_SPATIAL_REFERENCE_SYSTEMSfor the scale factor used for the spatial referencesystem in which the geometry will berepresented.

msgcode: -3425

sqlstate: 38SSP

GSE3426N Invalid number of parts.

Explanation: The number of parts indicated inthe binary or text representation of the geometryis not equal to the actual number of partssupplied. Either the number is too low or toomany parts were supplied to the function ormethod.

User Response: Specify the correct number ofparts or supply all parts for the geometry.

msgcode: -3426

sqlstate: 38SSQ

GSE3427N Incompatible SRSs.

Explanation: The two spatial reference systemsare not compatible. They cannot be transformedinto or compared with one another. Theoperation cannot be completed successfully.

User Response: Specify two compatible spatialreference systems.

msgcode: -3427

sqlstate: 38SSR


GSE3428N BLOB too small.

Explanation: The number of bytes in thespecified binary representation of the geometry istoo small.

User Response: Specify a valid binaryrepresentation of the geometry.

msgcode: -3428

sqlstate: 38SSS

GSE3429N Invalid geometry type.

Explanation: An invalid internal geometry typewas encountered. The geometry is not valid andwill not be processed any further.

User Response: Construct the geometry againfrom a valid binary or text representation.

msgcode: -3429

sqlstate: 38SST

GSE3430N Invalid byte order.

Explanation: The byte order in the binaryrepresentation of the geometry has an invalidvalue. The byte order must be 0 (zero) or 1 (one).

In the well-known binary representation, a byteorder of 0 (zero) indicates big endianess, and abyte order of 1 (one) indicates little endianess.

User Response: Specify a valid byte order inthe binary representation for the geometry.

msgcode: -3430

sqlstate: 38SSU

GSE3431N Empty geometry.

Explanation: An empty geometry was passed tothe ST_AsBinary function, even though it is notallowed as input.

User Response: Edit the SQL statement thatyou submitted so that only non-emptygeometries will be passed to the ST_AsBinaryfunction. For example, you can use theST_IsEmpty function in the WHERE clause toexclude empty geometries.

msgcode: -3431

sqlstate: 38SSV

GSE3432N Invalid end point.

Explanation: The specified point is intended tobe appended to the curve, but it is not valid.

User Response: Specify a valid point to beappended.

msgcode: -3432

sqlstate: 38SSW

GSE3433N Point not found.

Explanation: The specified point is intended tobe changed or removed, but it does not exist inthe curve.

User Response: Specify a point that does existin the curve.

msgcode: -3433

sqlstate: 38SSX

GSE3500N Instance path not found.

Explanation: The function implementing thegeocoder could not find the DB2 instance path.

User Response: Verify the correct installation ofDB2 and the IBM DB2 UDB Spatial Extender.Check that the DB2INSTANCE environmentvariable is set for the user running the processexecuting the function.

If the problem persists, contact IBM SoftwareSupport.

msgcode: -3500

sqlstate: 38SG0

GSE3501N Changing SRS id (new-srs-id,previous-srs-id).

Explanation: The geocoder is optimized togeocode addresses and produce the resultingpoints all in same spatial reference system in asingle SQL statement. But it encountereddifferent spatial reference systems in the same


SQL statement. The new spatial reference systemis identified by new-srs-id; the spatial referencesystem used for the preceeding rows wasidentified by previous-srs-id.

User Response: Specify the default parametersand overwriting parameters for the column thatthe geocoder runs on. This should be done insuch a way that the numerical spatial referencesystem identifier remains constant within an SQLstatement that is used to geocode multipleaddresses at once.

msgcode: -3501

sqlstate: 38SG1

GSE3502N Path too long.

Explanation: The path name specified for thelocator file parameter or the base map parameterexceeds 256 bytes and is too long.

User Response: Use a shorter path name for thelocator file parameter or the base map parameter.On Unix systems, symbolic links can be used toshorten the path name.

msgcode: -3502

sqlstate: 38SG2

GSE3503N Invalid line line-number in locatorfile.

Explanation: In the locator file, line line-numbercontains an invalid entry. Each entry in the filemust be of the form ″property name = propertyvalue″.

User Response: Correct the locator file.

msgcode: -3503

sqlstate: 38SG3

GSE3504N Non-matching quote in lineline-number in locator file.

Explanation: In the locator file, line line-numbercontains an entry where the quote characters arenot balanced. If quoted, the property name aswell as the property value must have an openingand a closing quote character.

User Response: Correct the locator file.

msgcode: -3504

sqlstate: 38SG4

GSE3505N Property failure. Reason code =reason-code.

Explanation: A failure occurred while handlingproperties defined in the locator file (.loc).


-502 A property is inconsistent with otherproperties.

-503 A required property was not found.

-504 A value of a property is invalid.

-505 An unexpected property wasencountered.

-506 An array of values was specified for aproperty that expected only a scalarvalue.

-507 A value of a property does not have theexpected data type.

-513 A value of a property is too long.

-533 The expression specified for a value of aproperty is invalid.

User Response: Correct the problem identifiedby the reason code; then retry the operation.

msgcode: -3505

sqlstate: 38SG5

GSE3506N Copy of properties failed.

Explanation: The copying of the properties intoan internal buffer failed. Not enough memory isavailable.

User Response: Ensure that enough memory isavailable for the geocoder to copy the propertiesfrom the locator file to the internal buffer.

msgcode: -3506

sqlstate: 38SG6


GSE3507N Too many properties.

Explanation: The locator file contains too manyproperties. At most 2048 properties can bespecified in the locator file.

User Response: Reduce the number ofproperties specified in the locator file.

msgcode: -3507

sqlstate: 38SG7

GSE3508N No point produced.

Explanation: The geocoder produced ageometry that is not an ST_Point geometry.


msgcode: -3508

sqlstate: 38SG8

GSE3509N Initialization of the geocoderfailed. Reason code = reason-code.

Explanation: The initialization of the geocoderfailed.


-522 A general failure occured while thegeocoder was being initialized.

-527 The initialization of the match keyfailed.

-529 The initialization of the addressnormalization failed.

User Response: Verify the installation of SpatialExtender.

msgcode: -3509

sqlstate: 38SG9

GSE3510N Address not normalized.

Explanation: The geocoder could not normalizethe address.


msgcode: -3510

sqlstate: 38SGA

GSE3511N Geocoder file operation failed. rc= reason-code.

Explanation: An internal error with reason codereason-code occurred during a file operation.

Possible reasons for the file operation failure,preceded by their reason codes, are as follows:

-543 The match rule file (.mat) could not beopened.

-544 The match rule file (.mat) is invalid.

-547 The reference data file (.edg) could notbe opened.

-548 The table in the reference data file (.edg)is either missing or inaccessible.

-549 A required column could not be foundin the reference data file (.edg).

-550 The index file could not be accessed.

User Response: Correct the problem identifiedby the reason code; then retry the operation.

msgcode: -3511

sqlstate: 38SGB

GSE3512N Geocoder failed. Reason code =reason-code.

Explanation: The geocoder failed with aninternal error of reason code reason-code.

User Response: Note the internal error andcontact IBM Software Support.

msgcode: -3512

sqlstate: 38SGC

GSE3600N No index specified.

Explanation: No valid index was specified. Theindex schema parameter, the index nameparameter, or both, are null. The index parametervalues cannot be derived.

User Response: Specify a valid spatial index toretrieve the parameter information.


msgcode: -3600

sqlstate: 38SQ0

GSE3601N Invalid spatial index nameschema-name.index-name.

Explanation: The specified name of the indexfor which you want parameter informationretrieved does not exist or does not identify aspatial index. This name is schema-name.index-name.

User Response: Specify an existing spatial indexto retrieve the parameter information.

msgcode: -3601

sqlstate: 38SQ1

GSE3602N Invalid parameter number numberspecified.

Explanation: The parameter number number isnot valid for the specified spatial index.

The following limits apply for the different typesof spatial indexes:

grid indexParameter numbers between 1 (one) and3.

z-order indexParameter numbers between 1 (one) and4.

quad-tree indexParameter numbers between 1 (one) and5.

User Response: Specify a valid parameternumber for the spatial index. Consult the DB2system catalog for the type of the spatial index.

msgcode: -3602

sqlstate: 38SQ2

GSE3603N Invalid column name.

Explanation: The specified column does notexist in the table. At least one of the following -table schema, table name, or column name - is anull value. The index parameter for an index on

a column cannot be derived.

User Response: Specify an existing columnwhich has a spatial index defined on it.

msgcode: -3603

sqlstate: 38SQ3

GSE4000N Required parameter parameter-nameis missing.

Explanation: The required parameter was notfound.

User Response: Specify the required parameterand try to execute the command again.

msgcode: -4000

sqlstate: 38SB0

GSE4001N An error occurred while SpatialExtender was allocating anenvironment handle.

Explanation: An environment handle could notbe allocated using the Call Level Interface (CLI).The operation cannot be completed successfully.

User Response: Verify the CLI configuration. Ifthe source of the problem cannot be found andcorrected, contact IBM Software Support.

msgcode: -4001

sqlstate: 38SB1

GSE4002N An error occurred while SpatialExtender was allocating aconnection handle. CLI errorcli-error and native error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was allocating aconnection handle.

User Response: Look up the detailed errormessage cli-error. Correct the error and executethe command again. If the problem persists,contact IBM Software Support.

msgcode: -4002


sqlstate: 38SB2

GSE4003N An error occurred while SpatialExtender was connecting to thedatabase. CLI error cli-error andnative error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was connecting to thedatabase.


msgcode: -4003

sqlstate: 38SB3

GSE4004N An error occurred while SpatialExtender was allocating astatement handle. CLI errorcli-error and native error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was allocating a statementhandle.


msgcode: -4004

sqlstate: 38SB4

GSE4005N An error occurred while an SQLstatement was being prepared.CLI error cli-error and native errorcode = native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was preparing an SQLstatement.

User Response: Look up the detailed error

message cli-error. Correct the error and executethe command again. If the problem persists,contact IBM Software Support.

msgcode: -4005

sqlstate: 38SB5

GSE4006N An error occurred while SpatialExtender was binding parametersto an SQL statement. CLI errorcli-error and native error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was binding parametersto an SQL statement.


msgcode: -4006

sqlstate: 38SB6

GSE4007N An error occurred while SpatialExtender was executing an SQLstatement. CLI error cli-error andnative error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was executing an SQLstatement.


msgcode: -4007

sqlstate: 38SB7


GSE4008N An error occurred while SpatialExtender was ending atransaction. CLI error cli-error andnative error code =native-error-code.

Explanation: An unexpected error cli-error withnative error code = native-error-code occurredwhile Spatial Extender was ending a transaction.


msgcode: -4008

sqlstate: 38SB8

GSE4009N The option, option, is invalid.

Explanation: The specified option, option, isinvalid.

User Response: Specify a valid option andrepeat the command.

msgcode: -4009

sqlstate: 38SB9

GSE4100N Column schema-name.table-name.column-name does not exist.

Explanation: The specified columnschema-name.table-name.column-name does notexist.

User Response: Specify an existing column inan existing table and execute the commandagain.

msgcode: -4100

sqlstate: 38SC0

GSE4101N Column schema-name.table-name.column-name does not have aspatial data type.

Explanation: The specified columnschema-name.table-name.column-name does nothave a spatial type. A spatial type isST_Geometry or one of its proper subtypes.

User Response: Specify a column with a spatialdata type and execute the command again.

msgcode: -4101

sqlstate: 38SC1

GSE4102N Spatial grid indexschema-name.index-name does notexist.

Explanation: The specified spatial grid indexschema-name.index-name does not exist.

User Response: Specify a spatial grid indexwhich does exist and execute the commandagain.

msgcode: -4102

sqlstate: 38SC2

GSE4103N An internal error occurred whileSpatial Extender was retrievingindex information for columnschema-name.table-name.column-name.

Explanation: Spatial Extender encountered anunexpected internal error while retrievinginformation about the spatial index on thecolumn schema-name.table-name.table-name.


msgcode: -4103

sqlstate: 38SC3

GSE4104N Spatial Extender could notretrieve grid sizes for spatial gridindex schema-name.index-name.

Explanation: Spatial Extender encountered anunexpected internal error while retrieving thegrid size definition for the grid indexschema-name.index-name.


msgcode: -4104

sqlstate: 38SC4


GSE4105W No rows to analyze in columnschema-name.table-name.column-name.

Explanation: The column schema-name.table-name.table-name does not contain any values thatthe Spatial Extender could analyze.

If sampling was used, the sample rate mighthave been too low.

User Response: Execute the command on acolumn that contains geometries. If sampling isused, use a higher sampling rate.

msgcode: +4105

sqlstate: 38SC5

GSE4106W Spatial Extender could not getenough memory to retrieve MBRhistogram for number entries.

Explanation: The histogram size of theminimum boundary rectangles for all thegeometries in the spatial column is too big. Notenough memory to store it could be allocated.The command cannot be executed successfully.

User Response: Do not specify the SHOWDETAIL option for the command or reduce thenumber of geometries to be analyzed bysampling them with a lower sample rate.

msgcode: +4106

sqlstate: 38SC6

GSE4107N Grid size value grid-size is notvalid where it is used.

Explanation: The specified grid size grid-size isnot valid.

One of the following invalid specifications wasmade when the grid index was created with theCREATE INDEX statement:

v A number less than 0 (zero) was specified asthe grid size for the first, second, or third gridlevel.

v 0 (zero) was specified as the grid size for thefirst grid level.

v The grid size specified for the second gridlevel is less than the grid size of the first gridlevel but it is not 0 (zero).

v The grid size specified for the third grid levelis less than the grid size of the second gridlevel but it is not 0 (zero).

v The grid size specified for the third grid levelis greater than 0 (zero) but the grid sizespecified for the second grid level is 0 (zero).

User Response: Specify a valid value for thegrid size.

msgcode: -4107

sqlstate: 38SC7

GSE4108W Geometries in columnschema-name.table-name.column-namedo not cover extent.

Explanation: All geometries in the columnschema-name.table-name.column-name do not spanan extent greater than 0 (zero). That means thatonly identical points exist in the column. Theindex information cannot be gathered.

User Response: Insert additional rows into thespatial column.

msgcode: +4108

sqlstate: 38SC8

GSE4109N An invalid query box of sizequery-box-size was specified.

Explanation: The specified query box sizequery-box-size is not valid. A query box must begreater than 0 (zero) and less than or equal to 1(one). The query box size indicates thepercentage of the extent for the data in thecolumn that is usually retrieved.

User Response: Correct the query box size bychoosing a value greater than 0 (zero) and lessthan or equal to 1 (one).

msgcode: -4109

sqlstate: 38SC9


GSE4110N An invalid number of rowsnum-rows to analyze was specified.

Explanation: The specified number of rows tobe analyzed (num-rows) is invalid. The numbermust be greater than 0 (zero).

User Response: Specify a valid number of rowsgreater than 0 (zero) and execute the commandagain.

msgcode: -4110

sqlstate: 38SCA

GSE4111N An invalid percentage percentagewas specified.

Explanation: The specified percentage percentageof rows to be analyzed is not valid. Thepercentage must be an integer that is greaterthan 0 (zero) and less than or equal to 100.

User Response: Specify a valid percentagegreater than 0 (zero) and less than or equal to100 and retry the command.

msgcode: -4111

sqlstate: 38SCB

GSE4112W No samples for the tableschema-name.table-name.column-nameat percent percent could beproduced.

Explanation: The Spatial Extender tried tosample percent percent of tableschema-name.table-name.column-name, but couldnot produce any sample rows that could beanalyzed any further.

User Response: If the table is not empty, choosea higher sampling rate and retry the command.

msgcode: +4112

sqlstate: 38SCC

GSE4113N No tablespace for a declaredglobal temporary table for thesampled data exists.

Explanation: A USER TEMPORARY tablespacewith a page size of at least 4096 bytes must existto declare a global temporary table that isneeded to sample the data that is to be analyzedby the Spatial Extender. A global temporary tableis needed so that Spatial Extender can sample thedata that it is going to analyze. A USERTEMPORARY tablespace with a page size of atleast 4096 bytes is required for declaring thistable.

User Response: Either create an appropriateUSER TEMPORARY tablespace and retry thecommand, or do not use the ANALYZE clause toavoid sampling the spatial data.

msgcode: -4113

sqlstate: 38SCD

GSE4200N Parameter value of data type typeis not expected in that context.

Explanation: The parameter value value of typetype is not expected in the context of thecommand.

User Response: Correct the command to beexecuted and then try the operation again.

msgcode: -4200

sqlstate: 38SD0

GSE4201N No command was specified.

Explanation: No command to be executed wasspecified.

User Response: Specify a command.

msgcode: -4201

sqlstate: 38SD1

GSE4202N Parsing of command failed.

Explanation: The given command syntax couldnot be parsed successfully.


User Response: Correct the syntax and executethe command again.

msgcode: -4202

sqlstate: 38SD2

GSE4203N Unexpected end-of-statementfound following token token.

Explanation: An unexpected end of thestatement was found after parsing token token.


msgcode: -4203

sqlstate: 38SD3

GSE4204N Parsing failed near token token.

Explanation: An unexpected parse erroroccurred near token token.


msgcode: -4204

sqlstate: 38SD4

GSE4205N Spatial Extender found more thanone type clause.

Explanation: While Spatial Extender parsed thecommand, it found more than one clause of datatype type.

User Response: Specify only one clause of typeand execute the command again.

msgcode: -4205

sqlstate: 38SD5

GSE9000N The database is not at the SpatialExtender Version 7 level.

Explanation: The database is not at the SpatialExtender Version 7 level and you are attemptingto perform an operation such as migration toVersion 8.

User Response: Verify the version of the

database and the operation you are attempting toperform.

msgcode: -9000

sqlstate: 38SZ0

GSE9001N The database is already at theSpatial Extender Version 8 level.

Explanation: The database is already at theSpatial Extender Version 8 level and you areattempting to perform an operation such asmigration to Version 8.

User Response: Verify the version of thedatabase and the operation you are attempting toperform.

msgcode: -9001

sqlstate: 38SZ1

GSE9002N An error occurred during anattempt to perform SpatialExtender database migration.

Explanation: An error was encountered duringan attempt to migrate the Spatial Extendercatalog and spatial functions.

User Response: Verify the version of thedatabase and the operation you are attempting toperform. Also verify that Spatial Extender wascorrectly enabled for the database you want tomigrate.

For more information, refer to the migrationmessage file.

msgcode: -9002

sqlstate: 38SZ2

GSE9003N A dependency betweenuser-defined objects and SpatialExtender objects exists.

Explanation: The Spatial Extender objects couldnot be migrated because some user-definedobjects have dependencies on Spatial Extenderobjects.

User Response: Review the migration message


file to see what dependencies exist. Specify theforce option in the migration command to saveand restore the user-defined objects that dependon the Spatial Extender objects.

msgcode: -9003

sqlstate: 38SZ3

GSE9990C An internal error occurred:error-text.

Explanation: Spatial Extender encountered anunexpected internal error with the text error-text.

User Response: Read the given error-text. If theproblem cannot be resolved, contact IBMSoftware Support.

msgcode: -9990

sqlstate: 38SZY

GSE9999C Internal message failure.

Explanation: An internal failure occurred whileSpatial Extender was retrieving an error message.


msgcode: -9999

sqlstate: 38SZZ



Chapter 13. SAT Messages

This section contains the Satellite (SAT) messages. The messages are listed innumeric sequence.

SAT1000I The first application version forthis group has been defaulted tomatch the value used for theTypical satellite install.

Explanation: If you install a satellite using theTypical method, the satellite’s application versionwill be set to a predefined value. This predefinedapplication version is the same as the defaultvalue for the first application version that iscreated for a group.

User Response: If you did not install thesatellites of this group using the Typical method,or you changed the application version for oneor more satellites after installation, ensure thatthe identifier you supply to create a newapplication version is consistent with thesatellite’s application version.

SAT1001I Mandatory information is missingfrom one of the notebook pages.The notebook will return to thepage that is missing information.

Explanation: All mandatory fields must befilled in for the action to complete.

User Response: Fill in the required informationand try the action again.

SAT1002I A test connection or attachment tothe selected target was successfulusing the specified authenticationcredentials.

Explanation: An attempt was made to connectto a target. The connection or attachment wasestablished successfully using the specifiedauthentication credentials.


SAT2000W Changes have not been saved.Save now?

Explanation: You are exiting from a window ornotebook without saving your changes.

User Response: To save your changes, click Yes.Otherwise, click No.

SAT2001W An ATTACH or CONNECTstatement was found in the script.

Explanation: The script contents appear tocontain either a CONNECT or an ATTACHstatement. On a satellite, the requiredinstance-level attach or database-level connect isautomatically established before a DB2 instanceor DB2 database script is executed. Consequently,it is not necessary to include ATTACH orCONNECT statements in DB2 instance ordatabase scripts, unless the script specifies morethan one execution target.

User Response: If the script does not specifymore than one target, remove the CONNECT orATTACH statement from the script.

SAT2002W Script contents may not beconsistent with the script type.

Explanation: Either the script contents havebeen modified in a way that causes aninconsistency with the script type, or the scripttype has been modified in a way that causes aninconsistency with the script contents.

User Response: Ensure that the script type andthe script contents are compatible.


SAT2003W Implicit table space was created.

Explanation: Promotion created at least oneimplicit table space.

User Response: Change the table spaces in thescript if the implicit table spaces that are createdare not suitable for your business requirements.

SAT2014W Are you sure that you want topromote the satellite satellite?

Explanation: Promoting a satellite causes thesatellite to start executing the group’s batches.Only promote a satellite when it has successfullyexecuted the fix batch and is ready to executegroup batches.

User Response: Click Yes to promote thesatellite back to executing group batches.Otherwise, click No.

SAT2015W Are you sure that you want to fixthe satellite satellite?

Explanation: Setting a satellite to fix mode willprevent the satellite from executing its groupbatches. The satellite will only be able to executea fix batch until it is promoted back to executingthe group batches. Only set a satellite to fixmode when the satellite requires servicing.

User Response: Click Yes to set the satellite tofix mode so it can execute a fix batch. Otherwise,click No.

SAT2016W An object with the name objectalready exists in the databasedatabase. Are you sure that youwant to overwrite it?

Explanation: Overwriting an object will causeall other objects that reference the object to beaffected.

User Response: Click Yes to overwrite theobject. Otherwise, click No.

SAT2017W An object with the name objectalready exists in the databasedatabase and is in use by anotherobject. Are you sure that youwant to change the definition ofthe object?

Explanation: Changing the definition of anobject will cause all other objects that referencethat object to be affected.

User Response: Click Yes to change thedefinition of the object. Otherwise, click No.

SAT2018W Are you sure that you want tochange the definition of objectobject?

Explanation: Changing the definition of anobject will cause all other objects that referencethat object to be affected.

User Response: Click Yes to change thedefinition of the object. Otherwise, click No.

SAT2019W An object with the name objectalready exists in the databasedatabase. Would you like torename object before it is createdin database?

Explanation: While creating object in database,another object with the same name was found toalready exist. Objects must have a unique name.

User Response: Click Yes to save the objectunder a different name. Otherwise, click No. Theobject will not be created.

SAT2020W At least one of the selectedsatellites is currently online. Noaction is taken on satellites thatare online.

Explanation: When a satellite is online andsynchronizing, it cannot be altered.

User Response: Determine which satellites arecurrently online. Wait until these satellites areoffline, and try the request again.


SAT2021W A test connection or attachment tothe selected target was notsuccessful using the specifiedauthentication credentials.

Explanation: An attempt was made to connector attach to a target. The connection could not beestablished because of an authentication error.

User Response: Verify that the authenticationcredentials are correct for the target, and try therequest again.

SAT2022W You will be able to makemodifications to this satellitewhen it is a test satellite. Careshould be taken to ensure thesatellite’s state remains consistent.

Explanation: Setting a satellite as a test satellitemeans that it will execute test batches. A testbatch may contain batch steps that produceuncertain outcomes, and may put the satelliteinto an inconsistent state. A satellite should onlybe set as a test satellite when it is acceptable tosubject it to these risks.

User Response: Click OK to set the satellite as atest satellite. Otherwise, click Cancel.

SAT2023W Are you sure that you want tochange this test satellite to aproduction satellite? Theadministrative function availablefor this satellite will be severelyrestricted.

Explanation: A test satellite is used to try outconfiguration changes before these changes aremade available to the production satellites.Consequently, a test satellite may becomeinconsistent when configuration changes do notsucceed. To repair the test satellite, return it to aconsistent state so that the configuration changescan be iteratively tested. More administrativeactions can be performed against a test satellite.If the satellite is changed to a productionsatellite, it can no longer be used for testpurposes. The administrative function availablefor this satellite will necessarily be severelyrestricted.

User Response: Click OK to set the satellite as aproduction satellite. Otherwise, click Cancel.

SAT2024W Synchronization session is inprogress. Are you sure that youwant to terminate it?

Explanation: A synchronization session was inprogress when the terminate action was issued.

User Response: If you continue with thetermination, the synchronization session will bestopped before it completes. You should cancelthe termination, and allow the synchronizationsession to complete.

SAT2025W If you use anything other than anoncomplete consistent-change-table in a consolidation scenario,the target table is refreshed whensatellites synchronize.

Explanation: In a consolidation replicationscenario, a noncomplete consistent-change-data-table does not result in a full refresh of the targettable when a satellite synchronizes. Any othertype of table (for example, a user copy or apoint-in-time target table) results in a full refreshof the target table when a satellite synchronizes.If, when defining your replication scenario, youspecified that the data capture is full refresh, thetarget table will be fully refreshed each time thata satellite synchronizes. If you did not specifythat the data capture is full refresh, the targettable is only fully refreshed the first time that theApply program is invoked on the satellite.

User Response: If you want the target table tobe refreshed when a satellite synchronizes, noaction is required. If you want to change the typeof the target table, you must remove the effectsof the generalization of the replicationsubscriptions from the DB2 control server, andreturn to the Control Center to modify thereplication scenario. Then, generalize thereplication subscriptions again.

Chapter 13. SAT Messages 529

SAT2026W The satellite should besynchronized once before the userchanges user data. User data thatis changed before the initialsynchronization of the satellitecannot be replicated.

Explanation: When the satellite synchronizes,the Capture and Apply programs are invoked onthe satellite. Depending on how you defined thereplication scenario, changes that are made to theuser data in the satellite database before the firstsynchronization session either cannot bereplicated to the corporate sources, or will beoverwritten at the satellite:

v If your replication scenario is eitherconsolidation, or update anywhere with thereplication direction defined from the satelliteto the corporate source, changes that are madeto the user data before the firstsynchronization session cannot be replicatedfrom the satellite to the corporate source.When the Capture program is invoked, itcannot capture these changes.

v If your replication scenario is eitherdistribution, or update anywhere with thereplication direction defined from thecorporate source to the satellite, changes thatare made to the user data before the firstsynchronization session will be overwrittenwhen a full refresh occurs at the satellite.

User Response: Instruct all satellite users tosynchronize before they change data on thesatellite.

SAT3000N The name name already exists.

Explanation: The name of the object you areattempting to create, name, already exists.

User Response: Specify a unique name.

SAT3001N The target name of a copy,targetname, already exists in thedatabase cdb.

Explanation: The name provided for the copy,targetname, is not unique in the target satellitecontrol database cdb.

User Response: Specify a unique name.

SAT3002N Application versionapplication-version-name alreadyexists for the group group-name.

Explanation: The name supplied for thisapplication version is already being used for thisgroup.

User Response: Specify a name for theapplication version that is not already in use bythe group group name.

SAT3003N No application versions exist forthis group.

Explanation: The requested action against thegroup requires at least one application version.

User Response: Create an application versionfor the group.

SAT3004N The object name does not exist.

Explanation: The specified object, name, doesnot exist. It may have been removed after theview containing the object was filled.

User Response: Refresh the view in which theobject appears.

SAT3005N The object name cannot be deletedbecause it is currently referred toby another object.

Explanation: The object name cannot be deletedbecause another object references it. Consistencycannot be maintained if name is deleted.

User Response: Delete all objects that aredependent on the object before deleting thisobject.

SAT3006N Group group-name cannot bedeleted because it has at least oneenabled satellite.

Explanation: Before a group can be deleted, allof its satellites be disabled so that they can bedeleted along with the group. At least onesatellite in the group was found to be enabled.


User Response: Disable all the satellites in thisgroup.

SAT3007N Group group-name cannot bedeleted because it has at least oneapplication version that has eithera test-level or a production-levelbatch.

Explanation: Production-level and test-levelbatches are considered to be active levels that areused by satellites. Consequently, they cannot bedeleted. Therefore, the application version, andhence the group, to which they belong cannot bedeleted.

User Response: Obsolete all theproduction-level batches and remove all thetest-level batches for this group. Then try therequest again.

SAT3008N Application versionapplication-version-name cannot bedeleted because it has either atest-level or a production-levelbatch.

Explanation: Production-level and test-levelbatches are considered to be active levels that areused by satellites. Consequently, they cannot bedeleted. Therefore, the application version towhich they belong cannot be deleted.

User Response: Obsolete the production-levelbatches and remove the test-level batches for thisapplication version. Then try the request again.

SAT3009N No generalized replicationsubscription sets exist for thegroup group-name.

Explanation: No generalized replicationsubscription sets exist for the group group-name.The specified action requires at least onegeneralized replication subscription to exist.

User Response: Define one or more generalizedreplication subscription sets for this group.

SAT3010N No application versions exist forthe group group-name.

Explanation: No application versions exist forthe group group-name. The specified actionrequires at least one application version to exist.

User Response: Define an application versionfor this group.

SAT3011N No default replicationsubscription sets exist forapplication versionapplication-version-name in groupgroup-name.

Explanation: Default replication subscriptionsets for application version application-version-name, in group group-name, are generated by thegeneralize action. Such subscription sets arenecessary before it is possible to customize thegeneralized replication subscription.

User Response: Ensure the generalized actioncompleted successfully, and try the request again.

SAT3012N A default replication controlserver for application versionapplication-version-name, in groupgroup-name, is generated by thegeneralize replication subscriptionaction. Such a control server isrequired before the generalizedreplication subscription can becustomized.

Explanation: A default replication control serverfor application version application-version-name ingroup group-name does not exist.

User Response: Ensure that the generalizing ofthe replication subscription completedsuccessfully. Then try the request again.

SAT3013N The confirmation password doesnot match the specified password.

Explanation: The confirmation password mustexactly match the specified password. Passwordsare case sensitive.

User Response: Type the confirmation


password again. Ensure that all characters typedare in the same case as the original password.

SAT3014N At least one of the specified batchsteps does not have a target alias,a success code set, or both.

Explanation: When a script is imported oradded as a new batch step, a target alias and asuccess code set must be added for the newbatch step is not provided.

User Response: Identify which batch steps aremissing a target alias or a success code set, andadd the missing information.

SAT3015N A target alias has not beenselected. You must select a targetalias before you can specify theauthentication credentials.

Explanation: A target alias must be specifiedbefore an authentication can be associated withit.

User Response: Specify a target alias. Then trythe request again.

SAT3016N An application version has notbeen set for this satellite. Thispage will be disabled until thesatellite reports its applicationversion.

Explanation: A satellite executes the batches ofan application version. This satellite has not yetreported its application version. Therefore, batchsteps cannot be specified for it.

User Response: Assign the satellite anapplication version on the satellite itself. Youcannot perform this action from the SatelliteAdministration Center.

SAT3017N The action cannot be performed.An application version has notbeen set.

Explanation: A satellite executes the batches ofan application version. This satellite has not yetreported its application version. Therefore, the

specified action cannot be performed.

User Response: Assign the satellite anapplication version on the satellite itself. Youcannot perform this action from the SatelliteAdministration Center.

SAT3018N The type of the execution targetspecified is not correct for thetype of the script.

Explanation: A target alias has been selectedthat is not correct. The script is designed toexecute against a different type of target.

User Response: Choose a target alias that is ofthe same type as the selected script. Then try therequest again.

SAT3019N The specified success code rangesare in conflict.

Explanation: A success code set cannot containa greater than (>) relation that specifies a rangeof numbers that overlap the range of numbersthat is specified by a less than (<) relation. Forexample, the following two relations are notallowed in the same success code set: > 10, < 11.

User Response: Either remove or correct thosesuccess relations from the success code set thatcause the overlap in ranges. To specify a finiterange of numbers between two numbers, a andb, an equals (=) relation must be specified foreach number in the range. For example, tospecify a finite range of numbers between 5 and10 as success codes, the following equalsrelations are required: =5,=6,=7,=8, =9 and =10.

SAT3022N Promotion failed with thefollowing error:SQLCODE=sqlcode,SQLSTATE=sqlatate, tokens: token1,token2, token3. The error wasdetected at location location.

Explanation: Promotion failed in an unexpectedway.

User Response: Contact the help desk or yoursystem administrator.


SAT3023N A system or internal erroroccurred.

Explanation: The possible errors include asystem error returned by the operating system,insufficient resources, or an incorrectconfiguration.

User Response: Verify your replicationconfiguration, or contact your systemadministrator or IBM Service.

SAT3024N A replication server is at a levelthat is not supported.

Explanation: The product level of a replicationserver is not supported.

User Response: Upgrade to a supported level.

SAT3025N An authentication failure occurredwhen connecting to a replicationserver.

Explanation: This action requires authenticationwith the replication servers. Authentication withone of the servers failed.

User Response: Ensure that you supplied thecorrect user ID and password. Either try therequest again, or contact your systemadministrator.

SAT3026N The size of a generated scriptexceeds the available storage.

Explanation: This action generates scripts. Atleast one of the generated scripts is larger thanthe maximum available storage.

User Response: Contact your systemadministrator or IBM Service.

SAT3027N The database directory entry for areplication source server, controlserver, or target server does notexist at the instance instance-name.

Explanation: This action requires the existenceof a database directory entry for the replicationsource servers, control server, and target serverat the instance instance-name. At least one of the

directory entries could not be found.

User Response: Catalog the replication sourceservers, control server, and target server atinstance-name. Or contact your systemadministrator or IBM Service.

SAT3028N The fix batch batch cannot bedeleted because it is being usedby at least one satellite.

Explanation: A batch cannot be deleted if it iscurrently being used.

User Response: Wait until the batch is nolonger used by any satellite. Then try the requestagain.

SAT3029N The script script cannot bechanged because it is being usedby at least one production orobsolete batch step.

Explanation: A script can only be modified if itis not being used by a production or obsoletebatch step.

User Response: Ensure that the script is notcurrently being used by a production or obsoletebatch step. Then try the request again.

SAT3030N The specified obsolete batch stepcannot be deleted because it isbeing used by a batch that is notobsolete.

Explanation: An obsolete batch step can only bedeleted if it is not being used by any batch thatis not obsolete.

User Response: If the batch that uses this batchstep is no longer in use by any satellite, move itto the obsolete level. Then try the request again.

SAT3031N The batch step cannot be deletedbecause it is not the last step inthe set of batch steps.

Explanation: A batch step cannot be deletedfrom the middle of a set of batch steps. All batchsteps after it must first be deleted.


User Response: Delete all the batch steps thatfollow the batch step to be deleted. Then try therequest again.

SAT3032N A production batch step cannot bedeleted.

Explanation: Production batch steps are used byproduction satellites for synchronization andcannot be deleted. Only test, unassigned, andobsolete batch steps can be deleted.

User Response: Take the batch step out ofproduction. Then try the request again.

SAT3033N Satellite synchronization failedbecause the satellite controldatabase SATCTLDB cannot befound in the database directory.

Explanation: The satellite control database isnot cataloged correctly in the database directory.


SAT3034N Satellite synchronization failedbecause of an authentication errorat the satellite control server.

Explanation: Either the user ID or the passwordsent to the control server is not correct.


SAT3035N Satellite synchronization failedbecause the satellite ID could notbe found locally.

Explanation: This error may result frombypassing the operating system logon.

User Response: If you are already logged on tothe operating system, contact the help desk oryour system administrator.

SAT3036N Satellite synchronization failedbecause the satellite control serverdoes not recognize this satellite.

Explanation: Either the satellite ID is notdefined correctly on the satellite or this satelliteis not defined correctly at the satellite controlserver.


SAT3037N Satellite synchronization failedbecause of an unknown error.

Explanation: Unknown.


SAT3038N The synchronizer has detected asevere DB2 error. Synchronizationcannot continue.

Explanation: The cause of this severe error isnot known.


SAT3039N Satellite synchronization failed.The satellite is in fail state at thesatellite control server.

Explanation: This satellite is in fail state, andmust be fixed.


SAT3040N Satellite synchronization failedbecause the satellite control servercannot be contacted.

Explanation: Communications could not beestablished between the satellite and its controlserver. One possible reason is that the controlserver is not operational, or communicationsconfiguration is not correct (for example, the hostname or port number for the satellite controlserver is not correct).



SAT3041N Satellite synchronization failedbecause communications with thesatellite control server was lost.

Explanation: A communication link failureoccurred. Either the satellite control serverbecame inactive, or a network failure wasexperienced.


SAT3042N The satellite synchronizationsession did not complete all taskssuccessfully.

Explanation: An error occured during thesatellite synchronization session.


SAT3043N The satellite synchronizationsession did not start successfully.

Explanation: An error occured during thestart-up phase of the satellite synchronizationsession.


SAT3044N The cleanup phase of the satellitesynchronization session did notcomplete successfully.

Explanation: An error occured during thecleanup phase of the satellite synchronizationsession.


SAT3045N control-server is not a validreplication control server.

Explanation: The selected server is not a validreplication control server. The request cannot becompleted.

User Response: Select a valid replication controlserver, then try the request again.

SAT3046N No generalized replicationsubscription sets exist forapplication versionapplication-version-name in groupgroup-name.

Explanation: There are no generalizedreplication subscription sets for the applicationversion application-version-name in the groupgroup-name. A generalized replicationsubscription set must exist before it can becustomized.

User Response: Generalize one or morereplication subscription sets for the applicationversion, and try the request again.

SAT3047N The input for field field-nameexceeds the limit. The maximumallowable length for this field ismaximum-length.

Explanation: The length of the input in fieldfield-name exceeds the limit maximum-length.

User Response: Ensure that the input is withinthe maximum limit, then try the request again.

SAT3048N More than one target server isassociated with apply qualifierapply-qualifier at control servercontrol-server.

Explanation: A target server of a replicationsubscription represents a satellite in the groupthat is executing the specified applicationversion. Consequently, there can only be onetarget server for a given apply qualifier. If yourreplication configuration specifies a single targetserver, then the associated apply qualifier maynot have been correctly specified. Otherwise,your replication configuration may not beacceptable for generalization to the satelliteenvironment.

User Response: First verify that the replicationconfiguration does not specify more than onetarget server. If it does, correct the replication


configuration, then try the generalize replicationsubscription request again. If the replicationconfiguration does not specify more than onetarget server, ensure that the correct applyqualifier is specified for the generalize replicationsubscription request. Then try the request again.

SAT3049N The file name is not valid.

Explanation: The file name is not valid becauseit contains at least one of the followingcharacters: \ / : * ? ″ < > |

User Response: Ensure that the file name doesnot contain any of the above characters. Then trythe request again.

SAT3050N One or more of the selectedsatellites does not have anapplication version.

Explanation: You cannot change the replicationparameters for a satellite that does not have anapplication version.

User Response: Ensure that every selectedsatellite has an application version. Then try therequest again.

SAT3051N The generalization of thereplication subscriptions failed.At least one of the generatedscripts is empty.

Explanation: At least one of the scriptsgenerated are empty.

User Response: Try the generalization again. Ifthe problem persists, contact IBM Service.

SAT3052N The database alias or databasename name cannot be found.

Explanation: The database name or the aliasthat is specified in the command cannot befound. Either the database is not cataloged in thedatabase directories, or does not exist.

User Response: Ensure that the specifieddatabase name exists in the system databasedirectory, and verify that the database exists.Then try the request again.

SAT4000C cdb is not a valid satellite controldatabase.

Explanation: The database named cdb is not avalid satellite control database. Any database thatis named SATCTLDB is initially assumed to be asatellite control database. Any action pertainingto satellite administration that is performedagainst such a database will first verify that thedatabase is valid. The action will not succeed ifthe database is not configured correctly. If cdb isa satellite control database, then its configurationhas been altered such that it can no longer beused. Otherwise, a non-control database has beengiven the name SATCTLDB.

User Response: To avoid misrepresenting adatabase as a satellite control database, renamethe database to anything other than SATCTLDB.If cdb is a satellite control database, verify itsconfiguration with the original definition.


Chapter 14. SPM Messages

This section contains the sync point manager (SPM) messages. The messagesare listed in numeric sequence.

SPM0400 Indoubt transaction resolutionwith DBALIAS=dbalias showsheuristic damage - the databaserolled back the UOW and thecoordinator withLUNAME=luname committed. Thetransaction is identified byLUWID=luwid.

Explanation: DB2 was the DRDA2 AS for thetransaction identified by luwid. Resolution withthe DB2 database shows heuristic damageoccurred. The database identified by dbaliasmanually resolved the indoubt transaction. TheDB2 database at luname rolled back thetransaction. This is inconsistent with the commitdecision of the DRDA2 coordinator at luname.

v The application was told that the transactionwas committed.

v Any resources updated at the participant wererolled back.

dbalias The alias name of the DB2 database.

lunameThe LU name of the coordinator.

luwid The SNA logical unit of work id of thetransaction.

The XID associated with the unit of work isprinted following this message.

Indoubt resolution with the participantcompletes.

User Response: Call the database administrator.

Database Administrator Action: Inform thedatabase administrators at both theCOORDINATOR luname and at the DATABASEdbalias that heuristic damage occurred for thetransaction with luwid. DB2 was a DRDA2 AS for

the transaction. The DRDA2 AR atCOORDINATOR luname made the decision toCOMMIT the database updates made by luwid.The dbalias PARTICIPANT made a heuristicdecision to ROLL BACK the updates made byluwid.

SPM0401 Indoubt transaction resolutionwith DBALIAS=dbalias showsheuristic damage - the databasecommitted and the coordinatorwith LUNAME=luname rolledback. The transaction is identifiedby LUWID=luwid.

Explanation: DB2 was the DRDA2 AS for thetransaction identified by luwid. Resolution withthe DB2 DATABASE shows heuristic damageoccurred. The database identified by dbaliasmanually resolved the indoubt transaction. Thedbalias committed the transaction. This isinconsistent with the roll back decision of theDRDA2 COORDINATOR at luname.

v The application was told that the transactionwas rolled back.

v Any resources updated at the participant werecommitted.

dbalias The alias name of the DB2 database.







Database Administrator Action: Inform thedatabase administrators at both theCOORDINATOR luname and at the DATABASEdbalias that heuristic damage occurred for thetransaction with luwid. DB2 was a DRDA2 AS forthe transaction. The DRDA2 AR atCOORDINATOR luname made the decision toroll back the database updates made by luwid. Atthe PARTICIPANT dbalias a heuristic decisionwas made to COMMIT the updates made byluwid.

SPM0402 Indoubt transaction resolutionwith participant withLUNAME=luname andDBALIAS=dbalias shows heuristicdamage - the participantcommitted and DB2 rolled back.The transaction is identified byLUWID=luwid.

Explanation: DB2 has coordinator responsibilityfor the transaction identified by luwid. Resolutionwith the participant shows heuristic damageoccurred. The participant identified by lunameand dbalias manually resolved the indoubttransaction. The action taken was to commit thetransaction. This is inconsistent with the roll backdecision of the coordinator.

v The application was told that the unit of workwas rolled back.

v Any resources updated at the participant werecommitted.

dbalias The database alias of the participant.

lunameThe LU name of the participant.





Database Administrator Action: Inform the localdatabase administrator and the databaseadministrator at luname that heuristic damageoccurred for the transaction with luwid. DB2 wasthe coordinator for the transaction and made thedecision to roll back the database updates madeby luwid. At luname a heuristic decision wasmade to COMMIT the updates made by luwid.

SPM0403 Indoubt transaction resolutionwith participant withLUNAME=luname andDBALIAS=dbalias shows heuristicdamage - the participant rolledback and DB2 committed. Thetransaction is identified byLUWID=luwid.

Explanation: DB2 has coordinator responsibilityfor the transaction identified by luwid. Resolutionwith the participant shows heuristic damageoccurred. The participant identified by lunameand dbalias manually resolved the indoubttransaction. The action taken was to roll back theUOW. This is inconsistent with the commitdecision of the coordinator.

v The application was told that the transactioncommitted.

v Any resources updated at the participant wererolled back.


dbalias The data base alias of the participant.





Database Administrator Action: Inform the localdatabase administrator and the databaseadministrator at luname that heuristic damageoccurred for the transaction with luwid. DB2 wasthe coordinator for the transaction and made the


decision to COMMIT the database updates madeby luwid. At luname a heuristic decision wasmade to ROLL BACK the updates made byluwid.

SPM0404 Protocol error during indoubttransaction resolution withcoordinator withLUNAME=luname1 - the DB2database with LUNAME=luname2has an indoubt transaction whichis identified by LUWID=luwid.

Explanation: DB2 was the DRDA2 AS for thetransaction identified by luwid. The DB2transaction associated at the database withLUNAME=luname2 is indoubt. A protocol erroroccurred during indoubt resolution with thecoordinator identified by luname1.

luname1The LU name of the partner acting asthe coordinator.

luname2The LU name of the database where thetransaction is indoubt.



The indoubt transaction remains indoubt. AResync Protocol Violation trace record is written.


Database Administrator Action: DB2 does notattempt to automatically resolve the indoubttransaction. The transaction must be manuallyresolved. The commit or abort decision made atthe coordinator must be determined so that thesame decision can be made at this participantDB2.

Contact the database administrator at thecoordinator with luname and dbalias, to determinewhether the transaction committed or aborted.

Use the LIST INDOUBT TRANSACTIONScommand at this (the participant) dbalias to

resolve the indoubt transaction.

SPM0405 A transaction with LUWID=luwidat the DB2 database withLUNAME=luname1 is indoubtbecause of a communicationfailure with the coordinator withLUNAME=luname2.

Explanation: During execution of the two phasecommit protocol with the coordinator at luname2,a communication failure occured. Phase 1 of theprotocol completed and the transaction at thedatabase with luname1 is indoubt.

The transaction is placed in the indoubt state andappears in the LIST DRDA INDOUBTSTRANSACTIONS report. Periodic attempts aremade to reestablish communication with thecoordinator for automatic resolution.


luname2The LU name of the coordinator.


The XID associated with the indoubt unit ofwork is printed following this message.

Periodic attempts will be made to automaticallyresolve the indoubt transaction.

User Response: Determine the cause of thecommunication failure and have the problemcorrected. DB2 periodically attempts to establishcommunication for automatic resolution. Ifautomatic resolution does not occur in areasonable amount of time, call the databaseadministrator. Manual resolution of the indoubttransaction might be necessary to release lockedresources.

Database Administrator Action: If manualresolution is necessary:

v Determine the commit or abort decision madeat the coordinator so that the same decisioncan be made at the DB2 database. Contact the

Chapter 14. SPM Messages 539

database administrator at the coordinator withluname to determine whether the transactioncommitted or aborted.

v Use the LIST INDOUBTS TRANSACTIONcommand at this (the participant) dbalias toresolve the indoubt transaction.

SPM0406 A transaction with LUWID=luwidat the participant withLUNAME=luname andDBALIAS=dbalias may be indoubtbecause of a communicationfailure. DB2 committed.

Explanation: During execution of the two phasecommit protocol with the participant at luname, acommunication failure occured. Phase 1 of theprotocol completed and the transaction isprepared for either commit or abort. The decisonto commit the transaction was made, but cannotbe communicated to the participant at this time.The participant is indoubt.

DB2 becomes responsible for indoubt resolutionwith the participant. This responsibility appearsin the LIST DRDA INDOUBTS TRANSACTIONreport. Periodic attempts are made to reestablishcommunication with the participant forautomatic resolution.

lunameThe LU unit name of the participant.

dbalias The database alias name of theparticipant.



Periodic attempts will be made to automaticallyresolve the indoubt transaction at the participant.

User Response: Determine the cause of thecommunication failure and have the problemcorrected. DB2 periodically attempts toreestablish communication for automaticresolution. If automatic resolution does not occurin a reasonable amount of time, call the databaseadministrator. Manual resolution of the

transaction might be necessary at the participantto release locked resources.

Database Administrator Action: If manualresolution is necessary, inform the databaseadministrator at the participant that the decisionis commit.

SPM0407 Automatic resolution of thetransaction with LUWID=luwidwith the coordinator atLUNAME=luname resulted incommit. The DB2 UniversalDatabase is = dbname.

Explanation: The indoubt transaction at thedatabase identified by dbname was automaticallyresolved by communication with the coordinatoridentified by luname. The transaction wascommitted.



luname2The LU name of the database where thechanges were made.


Processing continues normally.

SPM0408 A communication failure occurredduring automatic resolution withpartner with LUNAME=luname.Communication protocol beingused=protocol. Communication APIbeing used=api. Communicationfunction detecting theerror=function. Protocol specificerror codes: rc1, rc2, rc3.

Explanation: One or more indoubt transactionsexist with luname. DB2 attempted toautomatically resolve the indoubt transaction buta communication error occured.


protocolThe communication protocol being used.Only ″APPC″ is supported.

api The communication api being used.Either ″CM2 APPC″ or ″SNA/6000 OSSubroutines″ may be specified.

codes For ″CM2 APPC″ api, the rc1, rc2, andrc3 contain the primary return code,secondary return code and possibly anSNA sense code. For ″SNA/6000 OSSubroutines″ api, rc1 contains the errnoglobal variable.

User Response: Determine the cause of thecommunication failure and have the problemcorrected. DB2 periodically attempts toreestablish communication for automaticresolution. If automatic resolution does not occurin a reasonable amount of time, call the databaseadministrator. Manual resolution of thetransaction might be necessary at the participantto release locked resources.

Database Administrator Action: If manualresolution is necessary, inform the databaseadministrator at the participant that the decisionis commit.

SPM0409 A transaction with LUWID=luwidcannot be resolved due to a coldstart with LUNAME=luname. DB2transaction status=status. DB2responsibility=responsibility.

Explanation: An indoubt transaction exists withthe partner at luname. DB2 is unable to resolvethe indoubt transaction because the partner haslost all knowledge of indoubt transactions due toa previous cold start.


status The commit status of the transaction asknown by DB2. The commit status maybe indoubt, committed, or rolled back.

responsibilityDB2 transaction responsibility. DB2 maybe the coordinator or may be theparticipant.

User Response: There is probably inconsistentdata at the coordinator and participant. Informdatabase administrator of the status of thetransaction.

Database Administrator Action: Manualresolution is necessary. The heuristic decision(that is, to commit or roll back the transaction)should be coordinated with any otherparticipants and/or the coordinator. Theexistence of other participants might not be easyto determine. The information might be availablein the coordinators recovery log even though thecoordinator performed a cold start.

The commit or abort decision provided using theLIST INDOUBT TRANSACTIONS command forthe transaction are propagated to all downstreamparticipants, if any.

SPM0410 Warm start connection by partnerwith LUNAME=luname rejected.Partner changed at least 1 of - ourlog name oldourname(newourname),their log nameoldtheirname(newtheirname), syncpoint protocol oldpa(newpa), flagbyte sent oldfb(newfb), cclunamesent oldccls(newccls), and indoubttransactions require resolution.

Explanation: An attempt to make a warm startconnection with a partner was rejected becausethe partner specified a different set of sync pointparameters than the ones that were in use whencommunications were lost. DB2 has knowledgeof indoubt transactions that involve the partneras either the coordinator or a participant. Thiserror might be a recoverable error if the partnercan restart with the original sync pointparameters. If this is not possible, then thepartner must perform a cold start connectionwith DB2.

lunameThe LU name of the partner.

oldournameThe log name for this DB2 subsystem.This value is null if the partner did notinitiate the log name exchange.


newournameThe log name for this DB2 subsystem,as remembered by our partner and sentto us in the attempted warm startconnection. This value is null if thepartner did not initiate the log nameexchange.

oldtheirnameThe log name used by the partnerduring the last connection, asremembered by DB2.

newtheirnameThe log name used by the partner in theattempted warm start connection.

oldpa The sync point protocol used during thelast connection, as remembered by theDB2 (PA - Presumed Abort, PN -Presumed Nothing).

newpa The sync point protocol used during thelast connection, as remembered by thepartner (PA - Presumed Abort, PN -Presumed Nothing).

oldfb The use of the PS header byte 2 duringthe last connection, as remembered byDB2 (F - used as flag byte, N - not usedas flag byte).

newfb The use of the PS header byte 2 duringthe last connection, as remembered bythe partner (F - used as flag byte, N -not used as flag byte).

oldccls Whether the luname of the conversationcorrelator was exchanged as part of thesync point protocol during the lastconnection, as remembered by DB2. (E -was exchanged, N - was notexchanged).

newcclsWhether the luname of the conversationcorrelator was exchanged as part of thesync point protocol during the lastconnection, as remembered by thepartner (E - was exchanged, N - was notexchanged).

The connection with the partner is rejected. DB2retains indoubt knowledge.


Database Administrator Action: Contact thedatabase administrator at the partner luname anddetermine if it is possible for the partner toperform a warm start with same sync pointparameters as ours (’oldourname’,’oldtheirname’, ’oldpa’, ’oldfb’, ’oldccls’). If thisis possible, the next attempt to connect willsucceed.

If this cannot be done, then there are two otherpossible solutions:v Have the partner luname perform a cold start

connection with this DB2 subsystem.

v Force the next connection with the partner tobe a cold start connection.

SPM0411 Cold start connection bycoordinator withLUNAME=luname accepted.Indoubt transactions need manualresolution.

Explanation: DB2 was the DRDA2 AS and hasparticipant responsibility for indoubttransactions. The coordinator informed DB2 thatit performed a cold start operation and lost allknowledge of indoubt transactions. The indoubttransactions at this DB2 must be manuallyresolved with the LIST INDOUBTTRANSACTIONS command.

dbalias The database alias name of thecoordinator.

The connection with the partner is accepted. Atrace record is written.


Database Administrator Action: DB2 is aparticipant with one or more indoubttransactions where the coordinator is luname. TheDBMS at luname performed a cold start. The DB2participant assumes that the coordinator recoverylog was lost or damaged and indoubt transactionresolution cannot be achieved. There is probablyinconsistent data at the coordinator.

The heuristic decision (that is, to commit or abortthe transaction should be coordinated with anyother participants. The existence of other


participants might not be easy to determine. Theinformation might be available in thecoordinators recovery log even though thecoordinator performed a cold start.

The commit or abort decision provided using theLIST INDOUBT TRANSACTIONS command forthe transaction are propagated to all downstreamparticipants, if any.

SPM0412 Protocol error detected in syncpoint communications withcoordinator withLUNAME=luname1. Thetransaction with LUWID=luwid atthe DB2 database withLUNAME=luname2 may beindoubt.

Explanation: DB2 is a participant in thetransaction. A protocol error occurred during theSNA sync point exchange with the coordinatoridentified by luname. The protocol error fits intoone of the following categories:

v An unknown SNA PS header was received.

v An SNA PS header was received in the wrongsequence.

v An invalid LU6.2 verb sequence was used todeliver the SNA PS header.

v A DEALLOCATE TYPE(ABEND_SVC) wasreceived from the coordinator, indicating thatthe coordinator detected a protocol violation inthe PS headers transmitted by DB2.





If the protocol error was detected before thecommit decision, the transaction at the databasewith LU name=luname2 may be indoubt. DB2

does not automatically resolve such an indoubttransaction because of the protocol error.

If the protocol error was detected after thecommit decision, the transaction eithercompleted commit or abort processing.

A Syncpoint Protocol Violation trace is written.

User Response: The database administratormight need to manually resolve the indoubttransaction.

Database Administrator Action: Determine if thetransaction is indoubt. If it is indoubt, it must bemanually resolved using the LIST INDOUBTTRANSACTIONS command. The commit orabort decision made at the coordinator must bedetermined so that the same decision can bemade at DB2.

Contact the database administrator at thecoordinator dbalias to determine whether thetransaction with LUWID=luwid committed oraborted.

If the coordinator system is another DB2, thenthe following steps can be taken at the DB2coordinator to determine the commit or abortdecision.

SPM0413 Protocol error detected in syncpoint communications withparticipant with LUNAME=lunameand DBALIAS=dbalias. Thetransaction with LUWID=luwidmay be indoubt at the participant.DB2 committed.

Explanation: DB2 is the coordinator of thetransaction. A protocol error occurred during theSNA sync point exchange with the participantidentified by luname and dbalias. The protocolerror fits into one of the following categories:




v A DEALLOCATE TYPE(ABEND_SVC) wasreceived from the participant, indicating that


the participant detected a protocol violation inthe PS headers transmitted by DB2.





If application was told that the transactioncommitted.

There may be an indoubt transaction at theparticipant and if so, the indoubt transactionmust be manually resolved. DB2 does notautomatically resolve the indoubt transactionbecause of the protocol error.

A Syncpoint Protocol Violation trace record iswritten.

User Response: Call the database administrator.The participant might need to manually resolvethe indoubt transaction.

SPM0414 Protocol error during indoubttransaction resolution withparticipant with LUNAME=lunameand DBALIAS=dbalias. Thetransaction with LUWID=luwidmay be indoubt at the participant.DB2 rolled back.

Explanation: DB2 has coordinator responsibilityfor the transaction which was rolled back. Aprotocol error occurred during indoubt resolutionwith the participant identified by luname anddbalias.

The transaction at the participant remainsindoubt. DB2 will not attempt to automaticallyresolve the indoubt transaction because of theprotocol violation.





A Resync Protocol Violation trace record iswritten.


Database Administrator Action: If thetransaction is indoubt at the participant, it mustbe manually (heuristically) resolved.

SPM0415 Automatic resolution of thetransaction with LUWID=luwidwith the coordinator atLUNAME=luname resulted in rollback. The DB2 UniversalDatabase is = dbname.

Explanation: The indoubt transaction at thedatabase identified by dbname was automaticallyresolved by communication with the coordinatoridentified by luname. The transaction was rolledback.



luname2The LU name of the database where thechanges were made.




SPM0416 Cold start connection rejected bypartner with LUNAME luname.

Explanation: DB2 attempted to make acold-start connection with a partner dbalias. Thepartner rejected this attempted connection.


The connection was not made.


Database Administrator Action: DB2 is not ableto connect the partner luname until the partnerluname allows a cold-start connection with DB2.Contact the database administrator at the partnerluname.

Contact your IBM Support Center for furtherassistance.

SPM0417 Protocol error detected in syncpoint communications withparticipant with LUNAME=lunameand DBALIAS=dbalias. Thetransaction with LUWID=luwidmay be indoubt at the participant.DB2 rolled back.

Explanation: DB2 is the coordinator of thetransaction. A protocol error occurred during theSNA sync point exchange with the participantidentified by luname and dbalias. The protocolerror fits into one of the following categories:




v A DEALLOCATE TYPE(ABEND_SVC) wasreceived from the participant, indicating thatthe participant detected a protocol violation inthe PS headers transmitted by DB2.





If application was told that the transaction rolledback.

There may be an indoubt transaction at theparticipant and if so, the indoubt transactionmust be manually resolved. DB2 does notautomatically resolve the indoubt transactionbecause of the protocol error.

A Syncpoint Protocol Violation trace record iswritten.


SPM0420 Cold start connection byparticipant with LUNAME=lunameaccepted. Possible damage.

Explanation: DB2 has coordinator responsibilityfor indoubt transactions at a participant and justconnected with the participant, which lost allknowledge of indoubt transactions because of aprevious cold start. There might be damage atthe participant.

lunameThe LU name of the participant wherethere might be damage.

The connection with the partner is accepted.


Database Administrator Action: DB2 is thecoordinator with indoubt transaction resolutionresponsibility for one or more indoubt units ofwork at luname. The DBMS at luname performeda cold start. DB2 assumes that the participantrecovery log was lost or damaged and indoubttransaction resolution cannot be achieved. Thereis probably inconsistent data at the participant.Minimally, the participant might not completelyreflect the final outcome of the transactions that


were indoubt at the time the failure occurred.

SPM0421 SNA XLN protocol violation bypartner with LUNAME=luname.

Explanation: DB2 detected a protocol violationin the SNA Exchange Log Names (XLN)exchange with the partner at the specifiedluname.

lunameThe LU name of the partner that sentthe invalid XLN message.

The attempt to connect with the remote site fails.An XLN Protocol Violation trace record iswritten.

User Response: Contact the system programmerfor the remote site. The invalid XLN message isrecorded in the trace record. The system logicerror that causes the invalid XLN message mustbe corrected at the remote site.

SPM0422 Warm start connection by partnerwith LUNAME=luname rejectedbecause the partner remembersour log name incorrectly. Our logname is name1 and the partnerremembers it as name2.

Explanation: An attempt to make a warm startconnection with a partner was rejected becausethe partner specified our log name as name2.Our log name is name1, which is the luname ofthe local DB2. This error might be a recoverableerror if the partner can restart with our log nameas name1. If this is not possible, then the partnermust perform a cold start connection with DB2.

lunameThe LU name of the partner with whichthe connection failed.

name1 Our log name, as remembered by us.

name2 Our log name, as remembered by ourpartner and sent to us in the attemptedwarm start connection.

The connection with the partner is rejected.


Database Administrator Action: Contact thedatabase administrator at the partner luname anddetermine if it is possible for the partner toperform a warm start with our log namespecified as the luname of this DB2. If this ispossible, the next attempt to connect willsucceed. Or have the partner luname perform acold start connection with DB2.

SPM0423 Automatic resolution of thetransaction with LUWID=luwidwith the partner atLUNAME=luname andDBALIAS=dbalias resulted incommit.

Explanation: The indoubt unit of work wasautomatically resolved by communication withthe participant. The participant has been notifiedof the commit decision.






SPM0424 Automatic resolution of thetransaction with LUWID=luwidwith the participant atLUNAME=luname andDBALIAS=dbalias resulted in rollback.

Explanation: The indoubt unit of work wasautomatically resolved by communication withthe participant. The participant has been notifiedof the roll back decision.







SPM0425 A transaction with LUWID=luwidat the participant withLUNAME=luname andDBALIAS=dbalias may be indoubtbecause of a communicationfailure. DB2 rolled back.

Explanation: During execution of the two phasecommit protocol with the participant at luname, acommunication failure occured. Phase 1 of theprotocol completed and the transaction isprepared for either commit or abort. The decisonto roll back the transaction was made, but cannotbe communicated to the participant at this time.The participant is indoubt.

DB2 becomes responsible for indoubt resolutionwith the participant. This responsibility appearsin the LIST DRDA INDOUBTS TRANSACTIONreport. Periodic attempts are made to reestablishcommunication with the participant forautomatic resolution.

lunameThe LU unit name of the participant.




Periodic attempts will be made to automaticallyresolve the indoubt transaction at the participant.

User Response: Determine the cause of thecommunication failure and have the problemcorrected. DB2 periodically attempts toreestablish communication for automaticresolution. If automatic resolution does not occurin a reasonable amount of time, call the database

administrator. Manual resolution of thetransaction might be necessary at the participantto release locked resources.

Database Administrator Action: If manualresolution is necessary, inform the databaseadministrator at the participant that the decisionis roll back.

SPM0426 Protocol error detected duringindoubt transaction resolutionwith participant atLUNAME=luname andDBALIAS=dbalias. The transactionwith LUWID=luwid may beindoubt at the participant. DB2committed.

Explanation: DB2 has coordinator responsibilityfor the transaction which was committed. Aprotocol error occurred during indoubt resolutionwith the participant identified by luname anddbalias.

The transaction at the participant remainsindoubt. DB2 will not attempt to automaticallyresolve the indoubt transaction because of theprotocol violation.





A Resync Protocol Violation trace record iswritten.


Database Administrator Action: If thetransaction is indoubt at the participant, it mustbe manually (heuristically) resolved.


SPM0434 Sync point manager not available- incorrect communications level.

Explanation: The local communications releaselevel is older than the minimum release level orthe communication manager is incorrectlyconfigured to support APPCSYNCLEVEL(SYNC) conversations.

The attempt to create a protected conversationfails.

User Response: Install and configure the correctcommunications level required to supportSYNCLEVEL(SYNC) conversations.

SPM0438 The Sync point manager recoverylog is bad.

Explanation: The sync point manager recoverylog is inconsistent and cannot be used to performrecovery during DB2 start up processing.

User Response: Indoubt transactions may existat DRDA2 application servers. These indoubttransactions must be recovered manually.

Call the database administrator.

Database Administrator Action: To start thesync point manager, erase the spmlog directoryand start DB2. This will cause DB2 to create newsync point log files and to establish cold startconnections with all DRDA2 application servers.

SPM0439 Sync point manager unrecoverableerror while attempting to write tothe sync point manager recoverylog.

Explanation: The sync point manager log isinconsistent and cannot be used. Anunrecoverable error has been detected whileattempting to write to the SPM log during DB2processing.

User Response: The sync point manager willnot allow any new synclevel(twophase)connections. Issue the LIST DRDA INDOUBTTRANSACTIONS command to determine thestatus of any indoubt transactions.

Call the database administrator.

Database Administrator Action: To start thesync point manager, erase the spmlog directoryand start DB2. This will cause DB2 to create newsync point log files and to establish cold startconnections with all DRDA2 application servers.

SPM0440E Error encountered while trying tostart protocol protocol support.Return code from function was rc.The most probable cause for thiserror is that SNA has not beenstarted. Please stop DB2, startSNA, and restart DB2.

SPM0441 The sync point manager is notavailable for the sync pointmanager LU. The sync pointmanager LU is lu-name and the LUprofile is lu-profile.

Explanation: The sync point support could notbe enabled by DB2. The most likely causes ofthis are:

1. The AIX SNA communications level isinvalid. For sync point support AIX SNA V2or greater is required.

2. For AIX SNA V2, the Recovery ResourceManager (RRM) is not enabled. Thisparameter can be found in SNA SystemDefaults. Enable this parameter, verify theSNA profile, then stop and restart both AIXSNA and DB2.

3. For AIX SNA V3, the Recovery ResourceManager (RRM) is not enabled for the syncpoint manager LU lu-name. This parametercan be found in the LU definition for LUlu-name. Enable this parameter, verify theSNA profile, then stop and restart both AIXSNA and DB2.

User Response: Determine the reason based onthe previously described possibilities. Correctand retry.


SPM0442 Sync point manager not available.The most probable cause for thefailure is that a CPIC Sideinformation profile with the namename does not exist.

Explanation: The sync point manager requires aCPIC Side Information Profile with the namename. This profile cannot be found or containsincorrect information.

User Response: Please correct the profile, verifythe SNA profile, and stop and restart both DB2and SNA. Refer to the DB2 Connect QuickBeginnings for information on how to configuresync point manager support.

SPM0443 Sync point manager not available.The most probable cause for thefailure is that the instance whichis starting the sync point managerdoes not belong to one of theTrusted Group Names for AIXSNA.

Explanation: In order for the sync pointmanager to initialise itself the instance in whichDB2 is started needs certain authorities in orderto interact with the SNA support. AIX SNArequires that the Trusted Group Names includesany userID that will issue these commands.

User Response: In the SNA System Defaultsdialog, add the instance starting the sync pointmanager to one of the defined groups underTrusted Group Names. Stop and restart AIXSNA. Log off of the AIX Term, log back on to theinstance ID, and restart DB2.

If this does not enable you to start the sync pointmanager, apply the most recent PTF for AIXSNA and retry the previous instructions.

SPM0444 Sync point manager not available.The most probable cause for thefailure is that a TransactionProgram profile with the namename does not exist.

Explanation: The sync point manager requires aTransaction Program Profile of the name name.

This profile cannot be found or contains incorrectinformation.

User Response: Please correct the profile, verifythe SNA profile, and stop and restart both DB2and SNA. Refer to the DB2 Connect QuickBeginnings for information on how to configuresync point manager support.

SPM0445 The Transaction Program tp-namewill not be listened for by DB2.This is not a severe error but ifyou require this TransactionProgram then you must ensure itis NOT defined in the TransactionProfile of the AIX SNAconfiguration.

Explanation: When the sync point managerinitialises itself it registers Transaction Programsfor which it will listen. In order for the syncpoint manager to listen for the named TP, itisnecessary that no other Transaction ProgramProfile have this TP defined else there will be aconflict between the sync point manager and AIXSNA. If such a conflict exists then AIX SNA willlisten and the sync point manager will not.

User Response: If you require the sync pointmanager to listen for the named TP then youmust ensure that no other TP Profile referencesthis transaction program. The sync pointmanager has started succesfully regardless of thiserror.


SPM0446E The Transaction Program tp-namewill not be listened for by DB2.This is a severe error. The syncpoint manager has failed to start.Most probable cause is either thatanother instance has started thesync point manager using thesame SPM_NAME in theirdatabase manager configurationOR the Encina Peer to PeerGateway exists on this samemachine and the TransactionProgram named is defined in anAIX SNA Transaction Profile.

Explanation: The sync point manager tried toregister this TP but could not.

User Response: Remove the TP Profile fromAIX SNA. Stop and restart both DB2 and AIXSNA.

SPM0447E Error encountered while trying tostart protocol protocol support.Return code from function was rc.The most probable cause for thiserror is that the LU lu-name isalready in use for sync pointmanagement. Ensure the EncinaPeer to Peer Gateway or anothersync point manager is not usingthis LU.

Explanation: An LU can be registered with AIXSNA as supporting sync point by at most oneapplication. In this case, the requested sync pointmanager LU is already registered. The mostlikely cause is that the Encina Peer to PeerGateway is using this LU as a sync pointmanager or another DB2 instance is using this asa sync point manager.

User Response: Change the SPM_NAME in thedatabase manager configuration such that aunique LU is used. Stop and restart DB2.

SPM0448E Error encountered while trying tostart the sync point managerprotocol support. The sync pointmanager failed to registerLUNAME luname for sync pointsupport since this LU has beenconfigured for SNA API clientuse. Either choose a different LUfor the sync point manager ordisable the SNA API client use inthe Local LU 6.2 definition forthis LU.

Explanation: This error occurs when thecustomer is trying the start the sync pointmanager using CS/NT V5.01 and is using aLocal LU 6.2 definition where the SNA API clientuse flag has been set.

User Response: Either choose a different localLU 6.2 (without the SNA API client useconfigured) or disable the SNA API client useflag for the Local LU 6.2 definition.

SPM0449E Connection attempt failed. Themost probable cause for thefailure is that the LU specified inthe CPIC Side information profileprofile1 does not match the syncpoint manager LU specified in theCPIC Side information profileprofile2.

Explanation: In order to have propercommunications with the host system, any CPICSide information profile defined forcommunication must specifiy the same LU asdefined for the configured sync point manager.

User Response: Update SNA CPIC Sideinformation profile profile1 with the proper LU,verify the SNA profile, stop and restart bothSNA and DB2, and try the connection again.

SPM0450E Library could not be loaded.Access Permissions denied.

Explanation: The most probable cause for thisproblem is a result of a bug in Windows NT.

User Response: Ensure that all network drives


in your System and local PATH statement are atthe end of the PATH statement. SelectStart/Settings/ControlPanel/System/Environment/System/Path andmove all network drives to the end of the pathstatement. Then shutdown and restart thesystem.

SPM0451E MS SNA Server not started.

Explanation: The SNA server is not started.

User Response: Please start SNA Server andrestart DB2.

SPM0452I Ensure that the SPM_NAMEspecified in the database managerconfiguration is not the same asthe Control Point name name. TheSPM_NAME has been temporarilyreplaced with temp-name.

Explanation: The SPM_NAME cannot be thesame as the Control Point name. TheSPM_NAME has been temporarily replaced withan alternate name, but the database managerconfiguration file has not been changed.

User Response: Update the SPM_NAME in thedatabase manager configuration file. Specify aname that is not the Control Point name.

SPM0453C Sync point manager did not startbecause Microsoft SNA Server hasnot been started.

Explanation: This DB2 instance has beenconfigured to start the sync point manager.However, the underlying SNA stack, MicrosoftSNA Server, has not been started. Therefore thesync point manager support cannot be started.

User Response: Microsoft SNA Server must bestarted. Please stop DB2 by issuing the commandDB2STOP FORCE. Then perform the followingsteps:

1. Start

2. Settings

3. Control Panel

4. Double click Services

5. Click SnaServer

6. Click Start

Once Microsoft SNA Server has started, restartDB2 by issuing the command DB2START.

SPM0454C Sync point manager was notstarted because it requiresexclusive use of the Logical Unit(LU) represented by the LU Aliaslualias.

Explanation: The sync point manager requiresexclusive use of a Logical Unit (LU). The LUcurrently being used by the sync point manageris identified as part of the default outgoing LocalAPPC LU Pool. Therefore this LU is identified asbeing available for any application. The LU hasalso been identified as the LU to be used by thesync point manager via the SPM_NAMEDatabase Manager Configuration parameter.Since the sync point manager requires exclusiveuse of this LU, the LU cannot be a member ofthe default outgoing Local APPC LU Pool.

User Response: Modify the LU definition sothat the LU is not a member of the defaultoutgoing Local APPC LU Pool, or change theSPM_NAME value to an LU which is not amember of this default pool. Stop and restartSNA Server. Then stop and restart DB2.

Please refer to the DB2 Connect QuickBeginnings Manual or the DB2 UniversalDatabase Quick Beginnings Manual forinstructions on defining an LU within MicrosoftSNA Server to be used by the sync pointmanager.

SPM0455C Sync point manager was notstarted. The Logical Unit (LU)represented by the LU Alias lualiasis not properly configured to beused by the sync point manager.

Explanation: To use sync point manager, youmust configure the LU to be sync point enabled.

User Response: Modify the LU definition sothat the LU is sync point enabled and the Clientfield contains the name of the SNA Server.


Restart SNA Server and then restart DB2.


SPM0456C Sync point manager was notstarted. Ensure the Client field ofthe Logical Unit (LU) representedby the LU Alias lualias containsthe name of this SNA Server.

Explanation: To start sync point manager, theLU must be sync point enabled. To sync pointenable the LU, ensure that the “Enable SyncpointSupport” checkbox is checked and that the Clientfield contains the name of this SNA Server.

In this situation the “Enable Syncpoint Support”checkbox is checked but the Client field is notfilled in.

User Response: Modify the LU definition sothat the LU is sync point enabled and the Clientfield contains the name of the SNA Server. Stopand restart SNA Server and then stop and restartDB2.


SPM0457W Another DB2 instance is alreadylistening for transaction programDB2DRDA. This is not a fatalerror. However, this instance willnot listen for transaction programDB2DRDA.

Explanation: Unless the sync point manager isenabled, only a single DB2 instance can listen forTransaction Program DB2DRDA.

User Response: Define DB2 registry valueDB2SERVICETPINSTANCE at a global level todefine which instance listens for transaction

program DB2DRDA. Then restart all affectedinstances.

To define the DB2 registry valueDB2SERVICETPINSTANCE at a global level,issue the following command:

db2set -g DB2SERVICETPINSTANCE=<instance-name>

where <instance-name> represents the name ofthe instance.

SPM0458W Another DB2 instance is alreadylistening for transaction programx’07’6DB (hex 07F6C4C2). This isnot a fatal error. However, thisinstance will not listen fortransaction program x’07’6DB.

Explanation: Only a single DB2 instance canlisten for transaction program x’07’6DB unlessthe sync point manager is enabled.

User Response: Define DB2 registry valueDB2SERVICETPINSTANCE at a global level todefine which instance listens for transactionprogram x’07’6DB (hex 07F6C4C2). Then restartall affected instances.

To define the DB2 registry valueDB2SERVICETPINSTANCE at a global level,issue the following command:

db2set -g DB2SERVICETPINSTANCE=<instance-name>

where <instance-name> represents the name ofthe instance.

SPM0459W The version of SNA you haveinstalled is incompatible with thisversion of DB2.

Explanation: DB2 Connect for AIX and DB2Universal Database for AIX V6.1 and greaterrequire IBM eNetwork Communication Serverfor AIX V5.0.3 or higher for SNA connectivity.

The required version of IBM CommunicationServer is not installed on this machine.

User Response: You must upgrade to the IBMeNetwork Communications Server for AIX


V5.0.3. The PTF can be downloaded from:

http://service.software.ibm.com/cgi-bin/support/rs6000.support/downloads.

Select AIX General Software Fixes, AIX FixDistribution Service, AIX Version 4, and SearchBy PTF Number. Enter the search string sna.rte.Select Find Fix. Once the PTF is listed, select thePTF, then click Get Fix Package and follow theinstructions.

SPM0460W The version of Microsoft SNAServer installed on this machinedoes not support the sync pointmanager.

Explanation: This instance is configured to usethe DB2 SNA sync point manager with MicrosoftSNA Server. The version of Microsoft SNA Serverinstalled on this machine does not support thesync point manager.

User Response: To support the sync pointmanager, DB2 requires Microsoft SNA Server V4Service Pack 3 or above.

To perform multisite update with DB2 UniversalDatabase for OS/390, OS/400, or VM/VSE, youmust install Microsoft SNA Server V4 ServicePack 3 or above. Once you have installed thecorrect version of Microsoft SNA Server, stop andrestart DB2 Connect or DB2 Universal Database.



Chapter 15. XML Extender messages

DXXA000I Enabling column <column_name>.Please Wait.

Explanation: This is an informational messages.


DXXA001S An unexpected error occurred inbuild <build_ID>, file <file_name>,and line <line_number>.


User Response: If this error persists, contactyour Software Service Provider. When reportingthe error, be sure to include all the message text,the trace file, and an explanation of how toreproduce the problem.

DXXA002I Connecting to database <database>.

Explanation: This is an informational message.


DXXA003E Cannot connect to database<database>.

Explanation: The database specified might notexist or could be corrupted.

User Response:

1. Ensure the database is specified correctly.

2. Ensure the database exists and is accessible.

3. Determine if the database is corrupted. If it is,ask your database administrator to recover itfrom a backup.

DXXA004E Cannot enable database<database>.

Explanation: The database might already beenabled or might be corrupted.

User Response:

1. Determine if the database is enabled.

2. Determine if the database is corrupted. If it is,ask your database administrator to recover itfrom a backup.

DXXA005I Enabling database <database>.Please wait.



DXXA006I The database <database> wasenabled successfully.



DXXA007E Cannot disable database<database>.

Explanation: The database cannot be disabledby XML Extender if it contains any XMLcolumns or collections.

User Response: Backup any important data,disable any XML columns or collections, andupdate or drop any tables until there are no XMLdata types left in the database.

DXXA008I Disabling column <column_name>.Please Wait.

Explanation: This is an information message.


DXXA009E Xcolumn tag is not specified inthe DAD file.

Explanation: This stored procedure is for XMLColumn only.

User Response: Ensure the Xcolumn tag isspecified correctly in the DAD file.


DXXA010E Attempt to find DTD ID <dtdid>failed.

Explanation: While attempting to enable thecolumn, the XML Extender could not find theDTD ID, which is the identifier specified for theDTD in the document access definition (DAD)file.

User Response: Ensure the correct value for theDTD ID is specified in the DAD file.

DXXA011E Inserting a record intoDB2XML.XML_USAGE tablefailed.

Explanation: While attempting to enable thecolumn, the XML Extender could not insert arecord into the DB2XML.XML_USAGE table.

User Response: Ensure theDB2XML.XML_USAGE table exists and that arecord by the same name does not already existin the table.

DXXA012E Attempt to updateDB2XML.DTD_REF table failed.

Explanation: While attempting to enable thecolumn, the XML Extender could not update theDB2XML.DTD_REF table.

User Response: Ensure the DB2XML.DTD_REFtable exists. Determine whether the table iscorrupted or if the administration user ID hasthe correct authority to update the table.

DXXA013E Attempt to alter table <table_name>failed.

Explanation: While attempting to enable thecolumn, the XML Extender could not alter thespecified table.

User Response: Check the privileges required toalter the table.

DXXA014E The specified root ID column:<root_id> is not a single primarykey of table <table_name>.

Explanation: The root ID specified is either nota key, or it is not a single key of table table_name.

User Response: Ensure the specified root ID isthe single primary key of the table.

DXXA015E The column DXXROOT_IDalready exists in table<table_name>.

Explanation: The column DXXROOT_ID exists,but was not created by XML Extender.

User Response: Specify a primary column forthe root ID option when enabling a column,using a different different column name.

DXXA016E The input table <table_name> doesnot exist.

Explanation: The XML Extender was unable tofind the specified table in the system catalog.

User Response: Ensure that the table exists inthe database, and is specified correctly.

DXXA017E The input column <column_name>does not exist in the specifiedtable <table_name>.

Explanation: The XML Extender was unable tofind the column in the system catalog.

User Response: Ensure the column exists in auser table.

DXXA018E The specified column is notenabled for XML data.

Explanation: While attempting to disable thecolumn, XML Extender could not find thecolumn in the DB2XML.XML_USAGE table,indicating that the column is not enabled. If thecolumn is not XML-enabled, you do not need todisable it.



DXXA019E A input parameter required toenable the column is null.

Explanation: A required input parameter for theenable_column() stored procedure is null.

User Response: Check all the input parametersfor the enable_column() stored procedure.

DXXA020E Columns cannot be found in thetable <table_name>.

Explanation: While attempting to create thedefault view, the XML Extender could not findcolumns in the specified table.

User Response: Ensure the column and tablename are specified correctly.

DXXA021E Cannot create the default view<default_view>.

Explanation: While attempting to enable acolumn, the XML Extender could not create thespecified view.

User Response: Ensure that the default viewname is unique. If a view with the name alreadyexists, specify a unique name for the defaultview.

DXXA022I Column <column_name> enabled.



DXXA023E Cannot find the DAD file.

Explanation: While attempting to disable acolumn, the XML Extender was unable to findthe document access definition (DAD) file.

User Response: Ensure you specified the correctdatabase name, table name, or column name.

DXXA024E The XML Extender encounteredan internal error while accessingthe system catalog tables.

Explanation: The XML Extender was unable toaccess system catalog table.

User Response: Ensure the database is in astable state.

DXXA025E Cannot drop the default view<default_view>.

Explanation: While attempting to disable acolumn, the XML Extender could not drop thedefault view.

User Response: Ensure the administration userID for XML Extender has the privileges necessaryto drop the default view.

DXXA026E Unable to drop the side table<side_table>.

Explanation: While attempting to disable acolumn, the XML Extender was unable to dropthe specified table.

User Response: Ensure that the administratoruser ID for XML Extender has the privilegesnecessary to drop the table.

DXXA027E Could not disable the column.

Explanation: XML Extender could not disable acolumn because an internal trigger failed.Possible causes:

v The system is out of memory.

v A trigger with this name does not exist.

User Response: Use the trace facility to create atrace file and try to correct the problem. If theproblem persists, contact your Software ServiceProvider and provide the trace file.






Chapter 15. XML Extender messages 557











DXXA031E Unable to reset the DXXROOT_IDcolumn value in the applicationtable to NULL.

Explanation: While attempting to disable acolumn, the XML Extender was unable to set thevalue of DXXROOT_ID in the application tableto NULL.

User Response: Ensure that the administratoruser ID for XML Extender has the privilegesnecessary to alter the application table.

DXXA032E Decrement of USAGE_COUNT inDB2XML.XML_USAGE tablefailed.

Explanation: While attempting to disable thecolumn, the XML Extender was unable to reducethe value of the USAGE_COUNT column by one.

User Response: Ensure that theDB2XML.XML_USAGE table exists and that theadministrator user ID for XML Extender has thenecessary privileges to update the table.

DXXA033E Attempt to delete a row from theDB2XML.XML_USAGE tablefailed.

Explanation: While attempting to disable acolumn, the XML Extender was unable to deleteits associate row in the DB2XML.XML_USAGEtable.

User Response: Ensure that theDB2XML.XML_USAGE table exists and that theadministration user ID for XML Extender has theprivileges necessary to update this table.

DXXA034I XML Extender has successfullydisabled column <column_name>.

Explanation: This is an informational message


DXXA035I XML Extender is disablingdatabase <database>. Please wait.



DXXA036I XML Extender has successfullydisabled database <database>.



DXXA037E The specified table space name islonger than 18 characters.

Explanation: The table space name cannot belonger than 18 alphanumeric characters.

User Response: Specify a name less than 18characters.

DXXA038E The specified default view nameis longer than 18 characters.

Explanation: The default view name cannot belonger than 18 alphanumeric characters.



DXXA039E The specified ROOT_ID name islonger than 18 characters.

Explanation: The ROOT_ID name cannot belonger than 18 alphanumeric characters.


DXXA046E Unable to create the side table<side_table>.

Explanation: While attempting to enable acolumn, the XML Extender was unable to createthe specified side table.

User Response: Ensure that the administratoruser ID for XML Extender has the privilegesnecessary to create the side table.

DXXA047E Could not enable the column.

Explanation: XML Extender could not enable acolumn because an internal trigger failed.Possible causes:

v The DAD file has incorrect syntax.


v Another trigger exists with the same name.












































DXXA056E The validation value<validation_value> in the DAD fileis invalid.

Explanation: The validation element indocument access definition (DAD) file is wrongor missing.

User Response: Ensure that the validationelement is specified correctly in the DAD file.

DXXA057E A side table name<side_table_name> in DAD isinvalid.

Explanation: The name attribute of a side tablein the document access definition (DAD) file iswrong or missing.

User Response: Ensure that the name attributeof a side table is specified correctly in the DADfile.

DXXA058E A column name <column_name> inthe DAD file is invalid.

Explanation: The name attribute of a column inthe document access definition (DAD) file iswrong or missing.

User Response: Ensure that the name attributeof a column is specified correctly in the DADfile.

DXXA059E The type <column_type> of column<column_name> in the DAD file isinvalid.

Explanation: The type attribute of a column inthe document access definition (DAD) file iswrong or missing.

User Response: Ensure that the type attribute ofa column is specified correctly in the DAD file.

DXXA060E The path attribute <location_path>of <column_name> in the DAD fileis invalid.

Explanation: The path attribute of a column inthe document access definition (DAD) file iswrong or missing.

User Response: Ensure that the path attributeof a column is specified correctly in the DADfile.


DXXA061E The multi_occurrence attribute<multi_occurrence> of<column_name> in the DAD file isinvalid.

Explanation: The multi_occurrence attribute of acolumn in the document access definition (DAD)file is wrong or missing.

User Response: Ensure that themulti_occurrence attribute of a column isspecified correctly in the DAD file.

DXXA062E Unable to retrieve the columnnumber for <column_name> intable <table_name>.

Explanation: XML Extender could not retrievethe column number for column_name in tabletable_name from the system catalog.

User Response: Make sure the application tableis well defined.

DXXA063I Enabling collection<collection_name>. Please Wait.



DXXA064I Disabling collection<collection_name>. Please Wait.



DXXA065E Calling stored procedure<procedure_name> failed.

Explanation: Check the shared library db2xmland see if the permission is correct.

User Response: Make sure the client haspermission to run the stored procedure.

DXXA066I XML Extender has successfullydisabled collection<collection_name>.



DXXA067I XML Extender has successfullyenabled collection<collection_name>.



DXXA068I XML Extender has successfullyturned the trace on.



DXXA069I XML Extender has successfullyturned the trace off.



DXXA070W The database has already beenenabled.

Explanation: The enable database commandwas executed on the enabled database


DXXA071W The database has already beendisabled.

Explanation: The disable database commandwas executed on the disabled database


DXXA072E XML Extender couldn’t find thebind files. Bind the databasebefore enabling it.

Explanation: XML Extender tried toautomatically bind the database before enabling


it, but could not find the bind files

User Response: Bind the database beforeenabling it.

DXXA073E The database is not bound. Pleasebind the database before enablingit.

Explanation: The database was not bound whenuser tried to enable it.

User Response: Bind the database beforeenabling it.

DXXA074E Wrong parameter type. The storedprocedure expects a STRINGparameter.

Explanation: The stored procedure expects aSTRING parameter.

User Response: Declare the input parameter tobe STRING type.

DXXA075E Wrong parameter type. The inputparameter should be a LONGtype.

Explanation: The stored procedure expects theinput parameter to be a LONG type.

User Response: Declare the input parameter tobe a LONG type.

DXXA076E XML Extender trace instance IDinvalid.

Explanation: Cannot start trace with theinstance ID provided.

User Response: Ensure that the instance ID is avalid iSeries user ID.

DXXA077E The license key is not valid. Seethe server error log for moredetail.

Explanation: The software license has expiredor does not exist.

User Response: Contact your service provider

to obtain a new software license.

DXXC000E Unable to open the specified file.

Explanation: The XML Extender is unable toopen the specified file.

User Response: Ensure that the application userID has read and write permission for the file.

DXXC001E The specified file is not found.

Explanation: The XML Extender could not findthe file specified.

User Response: Ensure that the file exists andthe path is specified correctly.

DXXC002E Unable to read file.

Explanation: The XML Extender is unable toread data from the specified file.

User Response: Ensure that the application userID has read permission for the file.

DXXC003E Unable to write to the specifiedfile.

Explanation: The XML Extender is unable towrite data to the file.

User Response: Ensure that the application userID has write permission for the file or that thefile system has sufficient space.

DXXC004E Unable to operate the LOBLocator: rc=<locator_rc>.

Explanation: The XML Extender was unable tooperate the specified locator.

User Response: Ensure the LOB Locator is setcorrectly.

DXXC005E Input file size is greater thanXMLVarchar size.

Explanation: The file size is greater than theXMLVarchar size and the XML Extender isunable to import all the data from the file.


User Response: Use the XMLCLOB columntype.

DXXC006E The input file exceeds the DB2LOB limit.

Explanation: The file size is greater than thesize of the XMLCLOB and the XML Extender isunable to import all the data from the file.

User Response: Decompose the file into smallerobjects or use an XML collection.

DXXC007E Unable to retrieve data from thefile to the LOB Locator.

Explanation: The number of bytes in the LOBLocator does not equal the file size.

User Response: Ensure the LOB Locator is setcorrectly.

DXXC008E Can not remove the file<file_name>.

Explanation: The file has a sharing accessviolation or is still open.

User Response: Close the file or stop anyprocesses that are holding the file. You mighthave to stop and restart DB2.

DXXC009E Unable to create file to <directory>directory.

Explanation: The XML Extender is unable tocreate a file in directory directory.

User Response: Ensure that the directory exists,that the application user ID has write permissionfor the directory, and that the file system hassufficient space for the file.

DXXC010E Error while writing to file<file_name>.

Explanation: There was an error while writingto the file file_name.

User Response: Ensure that the file system hassufficient space for the file.

DXXC011E Unable to write to the tracecontrol file.

Explanation: The XML Extender is unable towrite data to the trace control file.

User Response: Ensure that the application userID has write permission for the file or that thefile system has sufficient space.

DXXC012E Cannot create temporary file.

Explanation: Cannot create file in system tempdirectory.

User Response: Ensure that the application userID has write permission for the file system tempdirectory or that the file system has sufficientspace for the file.

DXXC013E The results of the extract UDFexceed the size limit for the UDFreturn type.

Explanation: The data returned by an extractUDF must fit into the size limit of the returntype of the UDF, as defined in the DB2 XMLExtenders Administration and Programmingguide. For example, the results of extractVarcharmust be no more than 4000 bytes (including theterminating NULL).

User Response: Use an extract UDF that has alarger size limit for the return type: 254 bytes forextractChar(), 4 KB for extractVarchar(), and 2 GBfor extractClob().

DXXD000E An invalid XML document isrejected.

Explanation: There was an attempt to store aninvalid document into a table. Validation hasfailed.

User Response: Check the document with itsDTD using an editor that can view invisibleinvalid characters. To suppress this error, turn offvalidation in the DAD file.


DXXD001E <location_path> occurs multipletimes.

Explanation: A scalar extraction function used alocation path that occurs multiple times. A scalarfunction can only use a location path that doesnot have multiple occurrences.

User Response: Use a table function (add an ’s’to the end of the scalar function name).

DXXD002E A syntax error occurred nearposition <position> in the searchpath.

Explanation: The path expression issyntactically incorrect.

User Response: Correct the search pathargument of the query. Refer to thedocumentation for the syntax of pathexpressions.

DXXD003W Path not found. Null is returned.

Explanation: The element or attribute specifiedin the path expression is missing from the XMLdocument.

User Response: Verify that the specified path iscorrect.

DXXG000E The file name <file_name> isinvalid.

Explanation: An invalid file name wasspecified.

User Response: Specify a correct file name andtry again.

DXXG001E An internal error occurred inbuild <build_ID>, file <file_name>,and line <line_number>.

Explanation: XML Extender encountered aninternal error.

User Response: Contact your Software ServiceProvider. When reporting the error, be sure toinclude all the messages, the trace file and howto reproduce the error.

DXXG002E The system is out of memory.

Explanation: The XML Extender was unable toallocate memory from the operating system.

User Response: Close some applications and tryagain. If the problem persists, refer to youroperating system documentation for assistance.Some operating systems might require that youreboot the system to correct the problem.

DXXG004E Invalid null parameter.

Explanation: A null value for a requiredparameter was passed to an XML storedprocedure.

User Response: Check all required parametersin the argument list for the stored procedure call.

DXXG005E Parameter not supported.

Explanation: This parameter is not supported inthis release, will be supported in the futurerelease.

User Response: Set this parameter to NULL.

DXXG006E Internal ErrorCLISTATE=<clistate>, RC=<cli_rc>,build <build_ID>, file <file_name>,line <line_number>CLIMSG=<CLI_msg>.

Explanation: XML Extender encountered aninternal error while using CLI.

User Response: Contact your Software ServiceProvider. Potentially this error can be caused byincorrect user input. When reporting the error, besure to include all output messages, trace log,and how to reproduce the problem. Wherepossible, send any DADs, XML documents, andtable definitions which apply.

DXXG007E Locale <locale> is inconsistentwith DB2 code page <code_page>.

Explanation: The server operating system localeis inconsistent with DB2 code page.

User Response: Correct the server operating


system locale and restart DB2.

DXXG008E Locale <locale> is not supported.

Explanation: The server operating system localecan not be found in the code page table.

User Response: Correct the server operatingsystem locale and restart DB2.

DXXG017E The limit forXML_Extender_constant has beenexceeded in build build_ID, filefile_name, and line line_number.

Explanation: Check the XML ExtenderAdministration and Programming Guide to seewhether your application has exceeded a valuein the limits table. If no limit has been exceeded,contact your Software Service Provider. Whenreporting the error, include all output messages,trace files, and information on how to reproducethe problem such as input DADs, XMLdocuments, and table definitions.

User Response: Correct the server operatingsystem locale and restart DB2.

DXXM001W A DB2 error occurred.

Explanation: DB2 encountered the specifiederror.

User Response: See any accompanyingmessages for futher explanation and refer to DB2messages and codes documentation for youroperating system.

DXXQ000E <Element> is missing from theDAD file.

Explanation: A mandatory element is missingfrom the document access definition (DAD) file.

User Response: Add the missing element to theDAD file.

DXXQ001E Invalid SQL statement for XMLgeneration.

Explanation: The SQL statement in thedocument access definition (DAD) or the one

that overrides it is not valid. A SELECTstatement is required for generating XMLdocuments.

User Response: Correct the SQL statement.

DXXQ002E Cannot generate storage space tohold XML documents.

Explanation: The system is running out of spacein memory or disk. There is no space to containthe resulting XML documents.

User Response: Limit the number of documentsto be generated. Reduce the size of eachdocuments by removing some unnecessaryelement and attribute nodes from the documentaccess definition (DAD) file.

DXXQ003W Result exceeds maximum.

Explanation: The user-defined SQL querygenerates more XML documents than thespecified maximum. Only the specified numberof documents are returned.

User Response: No action is required. If alldocuments are needed, specify zero as themaximum number of documents.

DXXQ004E The column <column_name> is notin the result of the query.

Explanation: The specified column is not one ofthe columns in the result of the SQL query.

User Response: Change the specified columnname in the document access definition (DAD)file to make it one of the columns in the result ofthe SQL query. Alternatively, change the SQLquery so that it has the specified column in itsresult.

DXXQ005E Wrong relational mapping. Theelement <element_name> is at alower level than its child column<column_name>.

Explanation: The mapping of the SQL query toXML is incorrect.

User Response: Make sure that the columns in


the result of the SQL query are in a top-downorder of the relational hierarchy. Also make surethat there is a single-column candidate key tobegin each level. If such a key is not available ina table, the query should generate one for thattable using a table expression and the DB2built-in function generate_unique().

DXXQ006E An attribute_node element has noname.

Explanation: An attribute_node element in thedocument access definition (DAD) file does nothave a name attribute.

User Response: Ensure that everyattribute_node has a name in the DAD file.

DXXQ007E The attribute_node<attribute_name> has no columnelement or RDB_node.

Explanation: The attribute_node element in thedocument access definition (DAD) does not havea column element or RDB_node.

User Response: Ensure that everyattribute_node has a column element orRDB_node in the DAD.

DXXQ008E A text_node element has nocolumn element.

Explanation: A text_node element in thedocument access definition (DAD) file does nothave a column element.

User Response: Ensure that every text_node hasa column element in the DAD.

DXXQ009E Result table <table_name> does notexist.

Explanation: The specified result table couldnot be found in the system catalog.

User Response: Create the result table beforecalling the stored procedure.

DXXQ010E RDB_node of <node_name> doesnot have a table in the DAD file.

Explanation: The RDB_node of theattribute_node or text_node must have a table.

User Response: Specify the table of RDB_nodefor attribute_node or text_node in the documentaccess definition (DAD) file.

DXXQ011E RDB_node element of<node_name> does not have acolumn in the DAD file.

Explanation: The RDB_node of theattribute_node or text_node must have a column.

User Response: Specify the column ofRDB_node for attribute_node or text_node in thedocument access definition (DAD) file.

DXXQ012E Errors occurred in DAD.

Explanation: XML Extender could not find theexpected element while processing the DAD.

User Response: Check that the DAD is a validXML document and contains all the elementsrequired by the DAD DTD. Consult the XMLExtender publication for the DAD DTD.

DXXQ013E The table or column element doesnot have a name in the DAD file.

Explanation: The element table or column musthave a name in the document access definition(DAD) file.

User Response: Specify the name of table orcolumn element in the DAD.

DXXQ014E An element_node element has noname.

Explanation: An element_node element in thedocument access definition (DAD) file does nothave a name attribute.

User Response: Ensure that every element_nodeelement has a name in the DAD file.


DXXQ015E The condition format is invalid.

Explanation: The condition in the conditionelement in the document access definition (DAD)has an invalid format.

User Response: Ensure that the format of thecondition is valid.

DXXQ016E The table name in this RDB_nodeis not defined in the top elementof the DAD file.

Explanation: All tables must be defined in theRDB_node of the top element in the documentaccess definition (DAD) file. Sub-element tablesmust match the tables defined in the topelement. The table name in this RDB_node is notin the top element.

User Response: Ensure that the table of theRDB node is defined in the top element of theDAD file.

DXXQ017E The column in the result table<table_name> is too small.

Explanation: An XML document generated bythe XML Extender is too large to fit into thecolumn of the result table.

User Response: Drop the result table. Createanother result table with a bigger column. Rerunthe stored procedure.

DXXQ018E The ORDER BY clause is missingfrom the SQL statement.

Explanation: The ORDER BY clause is missingfrom the SQL statement in a document accessdefinition (DAD) file that maps SQL to XML.

User Response: Edit the DAD file. Add anORDER BY clause that contains theentity-identifying columns.

DXXQ019E The element objids has nocolumn element in the DAD file.

Explanation: The objids element does not havea column element in the document accessdefinition (DAD) file that maps SQL to XML.

User Response: Edit the DAD file. Add the keycolumns as sub-elements of the element objids.

DXXQ020I XML successfully generated.

Explanation: The requested XML documentshave been successfully generated from thedatabase.


DXXQ021E Table <table_name> does not havecolumn <column_name>.

Explanation: The table does not have thespecified column in the database.

User Response: Specify another column namein DAD or add the specified column into thetable database.

DXXQ022E Column <column_name> of<table_name> should have type<type_name>.

Explanation: The type of the column is wrong.

User Response: Correct the type of the columnin the document access definition (DAD).

DXXQ023E Column <column_name> of<table_name> cannot be longerthan <length>.

Explanation: The length defined for the columnin the DAD is too long.

User Response: Correct the column length inthe document access definition (DAD).

DXXQ024E Can not create table <table_name>.

Explanation: The specified table can not becreated.

User Response: Ensure that the user ID creatingthe table has the necessary authority to create atable in the database.


DXXQ025I XML decomposed successfully.

Explanation: An XML document has beendecomposed and stored in a collectionsuccessfully.


DXXQ026E XML data <xml_name> is too largeto fit in column <column_name>.

Explanation: The specified piece of data froman XML document is too large to fit into thespecified column.

User Response: Increase the length of thecolumn using the ALTER TABLE statement orreduce the size of the data by editing the XMLdocument.

DXXQ028E Cannot find the collection<collection_name> in theXML_USAGE table.

Explanation: A record for the collection cannotbe found in the XML_USAGE table.

User Response: Verify that you have enabledthe collection.

DXXQ029E Cannot find the DAD inXML_USAGE table for thecollection <collection_name>.

Explanation: A DAD record for the collectioncannot be found in the XML_USAGE table.

User Response: Ensure that you have enabledthe collection correctly.

DXXQ030E Wrong XML override syntax.

Explanation: The XML_override value isspecified incorrectly in the stored procedure.

User Response: Ensure that the syntax ofXML_override is correct.

DXXQ031E Table name cannot be longer thanmaximum length allowed by DB2.

Explanation: The table name specified by thecondition element in the DAD is too long.

User Response: Correct the length of the tablename in document access definition (DAD).

DXXQ032E Column name cannot be longerthan maximum length allowed byDB2.

Explanation: The column name specified by thecondition element in the DAD is too long.

User Response: Correct the length of thecolumn name in the document access definition(DAD).

DXXQ033E Invalid identifier starting at<identifier>

Explanation: The string is not a valid DB2 SQLidentifier.

User Response: Correct the string in the DADto conform to the rules for DB2 SQL identifiers.

DXXQ034E Invalid condition element in topRDB_node of DAD: <condition>

Explanation: The condition element must be avalid WHERE clause consisting of join conditionsconnected by the conjunction AND.

User Response: See the XML Extenderdocumentation for the correct syntax of the joincondition in a DAD.

DXXQ035E Invalid join condition in topRDB_node of DAD: <condition>

Explanation: Column names in the conditionelement of the top RDB_node must be qualifiedwith the table name if the DAD specifiesmultiple tables.

User Response: See the XML Extenderdocumentation for the correct syntax of the joincondition in a DAD.


DXXQ036E A Schema name specified under aDAD condition tag is longer thanallowed.

Explanation: An error was detected whileparsing text under a condition tag within theDAD. The condition text contains an id qualifiedby a schema name that is too long.

User Response: Correct the text of the conditiontags in document access definition (DAD).

DXXQ037E Cannot generate <element> withmultiple occurrences.

Explanation: The element node and itsdescendents have no mapping to database, butits multi_occurrence equals YES.

User Response: Correct the DAD by eithersetting the multi_occurrence to NO or create aRDB_node in one of its descendents.

DXXQ038E The SQL statement is too long:SQL_statement

Explanation: The SQL statement specified in the<SQL_stmt> element of DAD exceeds theallowed number of bytes.

User Response: Reduce the length of the SQLstatement to less than or equal to 32765 bytes forWindows and UNIX, or 16380 bytes for OS/390and iSeries.

DXXQ039E Too many columns specified for atable in the DAD file.

Explanation: A DAD file used fordecomposition or RDB composition can have amaximum of 100 text_node and attribute_nodeelements that specify unique columns within thesame table.

User Response: Reduce the total number oftext_node and attribute_node elements that referto unique columns within the same table 100 orless.

DXXQ040E The element name <element_name>in the DAD file is invalid.

Explanation: The specified element name in thedocument access definition (DAD) file is wrong.

User Response: Ensure that the element nameis typed correctly in the DAD file. See the DTDfor the DAD file.

DXXQ041W XML document successfullygenerated. One or more overridepaths specified is invalid andignored.

Explanation: Specify only one override path.

User Response: Ensure that the element nameis typed correctly in the DAD file. See the DTDfor the DAD file.

DXXQ043E Attribute <attr_name> not foundunder element <elem_name>.

Explanation: The attribute <attr_name> was notpresent in element <elem_name> or one of itschild elements.

User Response: Ensure the attribute appears inthe XML document everywhere that the DADrequires it.

DXXQ044E Element <elem_name> does nothave an ancestorelement<ancestor>.

Explanation: According to the DAD, <ancestor>is an ancestor element of <elem_name> . In theXML document, one or more element<elem_name> does not have such an ancestor.

User Response: Ensure that the nesting ofelements in the XML document conforms towhat is specified in the corresponding DAD.

DXXQ045E Subtree under element<elem_name> contains multipleattributes named<attrib_name>.

Explanation: A subtree under <elem_name> inthe XML document contains multiple instances ofattribute<attrib_name> , which according to the


DAD, is to be decomposed into the same row.Elements or attributes that are to be decomposedmust have unique names.

User Response: Ensure that the element orattribute in the subtree has a unique name.

DXXQ046W The DTD ID was not found in theDAD.

Explanation: In the DAD, VALIDATION is setto YES, but the DTDID element is not specified.No validation check is performed.

User Response: No action is required. Ifvalidation is needed, specify the DTDID elementin the DAD file.

DXXQ047E Parser error on line <mv>linenumber</mv> columncolnumber: msg

Explanation: The parser could not parse thedocument because of the reported error.

User Response: Correct the error in thedocument, consulting the XML specifications ifnecessary.

DXXQ048E Internal error - see trace file.

Explanation: The stylesheet processor returnedan internal error. The XML document or thestylesheet might not vaild.

User Response: Ensure the XML document andthe stylesheet are valid.

DXXQ049E The output file already exists.

Explanation: The specified output file alreadyexists in this directory.

User Response: Change the output path or filename for the output document to a unique nameor delete the existing file.

DXXQ050E Unable to create a unique filename.

Explanation: The UDF was unable to create aunique file name for the output document in the

specified directory because it does not haveaccess, all file names that can be generated are inuse or directory might not exist.

User Response: Ensure that the UDF has accessto the specified directory, change to a directorywith available file names.

DXXQ051E No input or output data.

Explanation: One or more input or outputparameters have no valid value.

User Response: Check the statement to see ifrequired parameters are missing.

DXXQ052E An error occurred while accessingthe DB2XML.XML_USAGE table.

Explanation: Either the database has not beenenabled or the table DB2XML.XML_USAGE hasbeen dropped.

User Response: Ensure that the database hasbeen enabled and the tableDB2XML.XML_USAGE is accessible.

DXXQ053E An SQL statement failed : msg

Explanation: An SQL statement generatedduring XML Extender processing failed toexecute.DB2XML.XML_USAGE has beendropped.

User Response: Examine the trace for moredetails. If you cannot correct the error condition,contact your softwaresService provider. Whenreporting the error, be sure to include all themessages, the trace file and how to reproduce theerror.

DXXQ054E Invalid input parameter: param

Explanation: The specified input parameter to astored procedure or UDF is invalid.

User Response: Check the signature of therelevant stored procedure or UDF, and ensure theactual input parameter is correct.


Appendix A. SPM Protocol Violation Records

This section shows the Protocol Violation records generated by the sync pointmanager. These records will be directed to the first failure service log(db2diag.log) and will follow the corresponding message.

Resync Protocol Violation Record/******************************************************************************* SQLCSPM_RESYNC_PROTOCOL_VIOLATION_206 - Resync Protocol error. ** ** This trace is produced when a protocol error occurs during a Resync Compare ** States (CS) exchange with a remote LU. The following are examples of SNA ** Compare States protocol errors: ** * an unknown STATE was found in the SNA CS message ** * an invalid data message was received from the remote site ** * an invalid LU6.2 verb sequence was detected ** *******************************************************************************/#define SQLCSPM_RPV_206_T "SQLCSPM_RESYNC_PROTOCOL_VIOLATION_206" /* Title.*/typedef struct sqlcspm_resync_protocol_violation_206{ /* */

SQLCSPM_LUNAME luname; /* Site involved in violation. */SQLCSPM_LUWID luwid; /* LUWID for the unit of work. */SQLXA_XID xid; /* XID of the thread. */char role; /* Role of DB2 in LUW -- C or P. */

/* C for coordinator. *//* P for participant. */

char status; /* Local thread status -- C, A or I *//* C for COMMIT. *//* A for ABORT. . *//* I for INDOUBT. */

SQLCSPS_TRACE comm_trace; /* Communication trace of violation. */} SQLCSPM_RESYNC_PROTOCOL_VIOLATION_206;

Syncpoint Protocol Violation Record/****************************************************************************** SQLCSPM_2PHASE_PROTOCOL_VIOLATION_208 - SNA syncpoint protocol error. ** ** This trace is produced when a protocol error occurs during the SNA ** syncpoint process with a remote LU. The following are examples of SNA ** syncpoint protocol errors: ** * an unknown SNA PS header was received. ** * an SNA PS header was received in the wrong sequence. ** * an invalid LU6.2 verb sequence was detected. ** * the remote site issued DEALLOCATE TYPE(ABEND_SVC). ******************************************************************************/#define SQLCSPM_2PPV_208_T "SQLCSPM_2PHASE_PROTOCOL_VIOLATION_208" /* Title.*/


typedef struct sqlcspm_2phase_protocol_violation_208{ /* */

SQLCSPM_LUNAME luname; /* Site involved in violation. */SQLCSPM_LUWID luwid; /* LUWID for the unit of work. */SQLXA_XID xid; /* XID of the thread. */char role; /* Role of DB2 in LUW -- C or P. */

/* C for coordinator. *//* P for participant. */

char local_status; /* Local thread status -- C, A or I *//* C for COMMIT. *//* A for ABORT. . *//* I for INDOUBT. */

char partner_status; /* Partner thread status -- C, A or I *//* C for COMMIT. *//* A for ABORT. . *//* I for INDOUBT. */

SQLCSPS_TRACE comm_trace; /* Communication trace of violation. */} SQLCSPM_2PHASE_PROTOCOL_VIOLATION_208;

XLN Protocol Violation Record/****************************************************************************** SQLCSPM_XLN_PROTOCOL_VIOLATION_236 - SNA XLN protocol error. ** ** This trace is produced when a protocol error occurs during the SNA ** syncpoint process with a remote LU. The following are examples of SNA ** syncpoint protocol errors: ** * an unknown SNA PS header was received. ** * an SNA PS header was received in the wrong sequence. ** * an invalid LU6.2 verb sequence was detected. ** * the remote site issued DEALLOCATE TYPE(ABEND_SVC). ******************************************************************************/#define SQLCSPM_XPV_236_T "SQLCSPM_XLN_PROTOCOL_VIOLATION_236" /* Title.*/typedef struct sqlcspm_xln_protocol_violation_236{ /* */

SQLCSPM_LUNAME luname; /* Site involved in violation. */SQLCSPX_XLN_INF xln_inf; /* Current XLN information

in LUB. */SQLCSPX_XLN_INF txln_inf; /* Temporary XLN information

in LUB. */SQLCSPM_GDSAREA xln; /* Current XLN GDS being

processed. */SQLCSPS_TRACE comm_trace; /* Communication trace of violation. */

} SQLCSPM_XLN_PROTOCOL_VIOLATION_236;


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 1. 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 575

The installation directory for this category is doc/htmlcd/%L/admin.

Table 2. 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 3. 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 4. 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 5. 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 6. Getting started information


IBM DB2 Universal DatabaseQuick Beginnings for DB2Clients

GC09-4832 db2itx80


Table 6. 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 7. 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 8. 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 9. 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 592.v DB2 supports accessibility applications that use the Java™ Accessibility API.

See “Compatibility with Assistive Technologies” on page 592.v DB2 comes with documentation that is provided in an accessible format.

See “Accessible Documentation” on page 592.

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 597

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 599


Index

Aaccessing help 1ADM messages 3, 5Administration Notification Log 5ASN messages 31AUD messages 3

CCCA messages 123CLI messages 133command line processor 279

Ddatabase administration tools

messages 147DB2 messages 279DBA messages 147DBI messages 217DBT messages 273DIA messages 3DWC 321DWC messages 321

GGOV messages 3GSE messages 473

HHelp 1

IICC 445ICM 445ICM messages 445installation messages 217introduction to messages 1

Mmessage prefix 1message structure 1message suffix 1Messages 1

ADM 3, 5ASN 31AUD 3CCA 123CLI 133DB2 279DBA 147DBI 217

Messages (continued)DBT 273DIA 3DWC 321GOV 3GSE 473ICC 445ICM 445replication messages 31SAT 527SPM 537

messages, introduction 1

Oonline help 1other message sources 4

Rreplication messages 31

SSAT messages 527SPM messages 537



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-4840-00

Spin

ein

form

atio

n:

��

�IB

M®

DB

2U

nive

rsal

Dat

abas

e™

Mes

sage

Ref

eren

ce,V

olum

e1

Vers

ion

8

Date post:	04-Dec-2014
Category:	Documents
Upload:	vpithani
View:	1,917 times
Download:	6 times

DB2 Messages V1

Documents