HP NonStop SQL/MP Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MP relational database management system and its associated subsystems. Product Version NonStop SQL/MP G07 and H01 Supported Release Version Updates (RVUs) This publication supports G06.27 and all subsequent G-series RVUs and H06.03 and all subsequent H-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 427720-002 NonStop SQL/MP G07 December 2003 427720-003 NonStop SQL/MP G07 April 2004 427720-004 NonStop SQL/MP G07 November 2004 427720-005 NonStop SQL/MP G07 and H01 September 2005 427720-006 NonStop SQL/MP G07 and H01 July 2006
HP NonStop SQL/MP Messages Manual Figures What’s New in This Manual v Manual Information v New and Changed Information About This Manual vii Audience vii Related Manuals vii Notation Conventions vi ix 1.
2. General Messages (0 to 999) Contents 2. General Messages (0 to 999) 3. SQL Catalog Manager Messages (1000 to 1999) 4. SQL Compiler Messages 5. SQL Compiler Parser Messages (3000 to 3999) 6. SQL Compiler Binder Messages (4000 to 4999) 7. SQL Compiler Normalizer Messages (5000 to 5999) 8. SQL Compiler Optimizer Messages (6000 to 6999) 9. SQL Compiler Generator Messages (7000 to 7999) 10. SQL Executor Messages (8000 to 8999) 11. SQLCI Utility Processor Messages (9000 to 9999) 12.
18. Audit Fix-Up EMS Messages Contents 18. Audit Fix-Up EMS Messages 19. ZSQL EMS Messages 20. Collation Compiler Messages 21. FastSort Messages Figures Figure i.
Contents HP NonStop SQL/MP Messages Manual—427720-006 iv
What’s New in This Manual Manual Information HP NonStop SQL/MP Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MP relational database management system and its associated subsystems. Product Version NonStop SQL/MP G07 and H01 Supported Release Version Updates (RVUs) This publication supports G06.27 and all subsequent G-series RVUs and H06.03 and all subsequent H-series RVUs until otherwise indicated by its replacement publication.
New and Changed Information What’s New in This Manual New and Changed Information Changes to the G06.29 manual: • Added these new error messages: ° ° ° ° ° • SQL 1080 on page 3-11 SQL 1262 on page 3-42 SQL 6104 on page 8-9 SQL 1186 on page 16-44 Preprocessor SQLFE for C in Section 13, Preprocessor Messages (11000 to 11999) Updated the error message, SQL 1353 on page 3-53. Changes to the G06.27 Manual Added a new error message, SQL 9915 on page 11-81. Changes to the G06.
About This Manual NonStop SQL/MP is the HP implementation of a relational database management system that uses the industry standard Structured Query Language (SQL) to define and manipulate data. This manual lists messages produced by NonStop SQL/MP and its related subsystems. Audience This manual was written for SQL/MP database administrators and programmers who are using the SQL/MP conversational or programmatic interface.
Related Manuals About This Manual Manual Title Description SQL/MP Version Management Guide Describes the rules governing version management for the SQL/MP relational database management system. SQL/MP Programming Manual for C and SQL/MP Programming Manual for COBOL Describes the SQL/MP programmatic interfaces for C and COBOL, respectively. SQL Programming Manual for Pascal and SQL Programming Manual for TAL Describes the SQL/MP programmatic interfaces for Pascal and TAL, respectively. Figure i.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i:i. !i,o In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Change Bar Notation About This Manual HP NonStop SQL/MP Messages Manual—427720-006 xiv
1 Message Handling SQL/MP components return messages through the conversational and programmatic interfaces. This manual lists messages that are returned by SQL/MP components.
Errors and Warnings Message Handling Errors and Warnings An SQL/MP message can be a warning or an error: • A warning has a positive number associated with it. A warning indicates that your request completed successfully but might not be optimal. The text of the message contains information that describes why the warning occurred. You might want to perform some action to ensure the most efficient request handling and outcome.
Message File Versions Message Handling Sometimes when variables are moved or deleted, HP adds a new message that replaces the old one. HP does not delete the old message until that version of the message file is no longer supported. Message File Versions The message file contains a record that describes the message file version. To display the version of an SQL message file, use the SQL/MP conversational interface (SQLCI) ENV command. The MESSAGEFILE VRSN variable lists the current version.
Interactive Recovery Information Message Handling Interactive Recovery Information When you submit SQL queries and other statements through SQLCI, the interface returns error numbers as necessary. To view error information, enter the ERROR command with an error number. SQLCI displays the error text associated with the specified error.
Programmatic Recovery Information Message Handling Programmatic Recovery Information This subsection contains guidelines for handling SQL/MP errors from within a program. For more information about your host language, see the SQL/MP programming manual. SQL/MP Error Philosophy SQL/MP messages are intended for an SQL user, system operator, system manager, or database administrator. They are not intended to be handled programmatically.
Obtaining Error Information Message Handling For more information about message processing, see the programming manual for your host language and the SQL/MP Programming Manual for COBOL, under “Error and Status Reporting.
2 General Messages (0 to 999) SQL 0 0 Successful SQL operation. Cause. The operation completed successfully. Effect. Control returns to you or to the calling program. Recovery. Informational message only; no corrective action is needed. SQL 100 100 No rows selected or modified. Cause. For a fetch operation, the fetch was at end-of-file or no rows qualified. For a delete or update operation, no rows were modified. Effect. No rows qualify for the operation. Recovery.
General Messages (0 to 999) SQL 105 105 A data value (character or numeric) was truncated. Cause. For character values, not all characters could fit in the target buffer (host variable). For numeric values, the scale was truncated. Effect. A truncated result is put in the target. Recovery. Declare larger host variables for those variables with insufficient length to receive values from the columns associated with them.
General Messages (0 to 999) SQL 203 203 The DEFINE for value-1 is not of CLASS TAPE or CLASS MAP. Cause. A DEFINE of CLASS TAPE or MAP was required, but the indicated DEFINE was not of CLASS TAPE or MAP. Effect. The statement fails. Recovery. Delete the current DEFINE and add a DEFINE with the correct CLASS value, or alter the attributes of the DEFINE, and reissue the statement. SQL 204 204 DEFMODE is set to OFF so no DEFINEs were mapped. Cause.
General Messages (0 to 999) ALLOCATESEGMENT procedure. If the value is positive, refer to the error codes for file system errors in the Guardian Procedure Errors and Messages Manual. If possible, correct the problem indicated by the ALLOCATESEGMENT error code. Refer to the Guardian Procedure Calls Reference Manual for a description of the error codes returned by ALLOCATESEGMENT.
General Messages (0 to 999) SQL 210 210 A new process could not be started with the program file value-2. See PROCESS_CREATE_ error value-1 for a description of the problem. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct this condition and reissue the statement. For more information on the PROCESS_CREATE_ procedure and the description of the error returned by PROCESS_CREATE_, refer to the Guardian Procedure Calls Reference Manual.
General Messages (0 to 999) SQL 213 213 A server could not be started using program file value-2. $CMON error: value-1. Cause. The process named could not be started. Effect. The statement fails. Recovery. Correct the condition indicated by the error code, and perform the operation again. SQL 214 214 The server (program file value-1) could not be opened. Cause. The indicated server could not be opened.
General Messages (0 to 999) SQL 217 217 A new process could not be started with the program file value-1 because PROCESS_CREATE_ could not obtain a process control block. Cause. PROCESS_CREATE_ could not obtain a process control block because your processor had too many processes running. Effect. The statement fails. Recovery. Start your program on a processor that has fewer processes running in it.
General Messages (0 to 999) SQL 222 222 A new process could not be started with the program file value-1 because the program file or its library file needs to be licensed with the FUP LICENSE command. Cause. The indicated program file was not licensed. Effect. The statement fails. Recovery. Contact your system manager to license the program file for you. SQL 223 223 Internal error: A new process could not be started with the program file value-1 because PROCESS_CREATE_ encountered a file system error.
General Messages (0 to 999) SQL 225 225 A new process could not be started with the program file value-1 because PROCESS_CREATE_ could not communicate with the system monitor process. Cause. Stated in the error message. Effect. The statement fails. Recovery. Contact your system manager. SQL 226 226 A server could not be started using program file value-1 because the length of the reply message from CMON was less than the expected reply length. Cause. The reply message from CMON was not the correct length.
General Messages (0 to 999) Recovery. Correct the file system error condition, and reissue the statement. SQL 229 229 A new process could not be started with the program file value-1 because a file system error was encountered on the extended segment swap file. Cause. The extended segment swap file could not be accessed properly. The file system error following this error indicates the cause. Effect. The statement fails. Recovery. Correct the file system error condition, and reissue the statement.
General Messages (0 to 999) SQL 232 232 A new process could not be started with the program file value-1. See PROCESS_CREATE_ error value-2 with error-detail value-3 for a description of the problem. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct this condition and reissue the statement. For more information on the PROCESS_CREATE_ procedure and the description of the error returned by PROCESS_CREATE_, refer to the Guardian Procedure Calls Reference Manual.
General Messages (0 to 999) Recovery. For more information on the description of this error, refer to the DEFINEPOOL procedure call in the Guardian Procedure Calls Reference Manual. Correct the condition, and reissue the statement. SQL 252 252 Unable to obtain the SQL software version for the system on which the SQL object or catalog value-1 resides. Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery.
General Messages (0 to 999) MOVEX procedure call and the description of the MOVEX error, refer to the Guardian Procedure Calls Reference Manual. SQL 255 255 Unable to obtain the SQL version of catalog value-1. Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery. Correct the file system error condition and reissue the statement. SQL 256 256 Unable to obtain the SQL software version for the local node. Cause.
General Messages (0 to 999) SQL 259 259 Unable to obtain the SQL version of value-1. Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery. Correct the file system error condition and reissue the statement. SQL 300 300 An unsupported version of the SQLCA was encountered. Cause. Either the program SQLCA was corrupted, or you ran the program with a version of the system library that precedes the version of the SQL/MP software. Effect.
General Messages (0 to 999) SQL 303 303 There are some parameters that could not fit in the SQLCA. Cause. The parameters buffer in the SQLCA was full. This condition happens only if other warnings or errors were reported in the SQLCA for this statement and their parameters have already occupied all available space in the parameters buffer of the SQLCA. Effect.
General Messages (0 to 999) SQL 515 515 SIO error: Access mode is incompatible. Cause. A sequential I/O (SIO) error occurred. Effect. The statement fails. Recovery. Report the entire message to your service provider. SQL 516 516 SIO error: Buffer address is not in lower 32K. Cause. A sequential I/O (SIO) error occurred. Effect. The statement fails. Recovery. Report the entire message to your service provider. SQL 517 517 SIO error: code. File code does not match the assigned file Cause.
General Messages (0 to 999) SQL 519 519 SIO error: buffer length. Assign block length is greater than block Cause. A sequential I/O (SIO) error occurred. Effect. The statement fails. Recovery. Report the entire message to your service provider. SQL 520 520 SIO error: This has 4 possible causes. 1) Record length equals 0. 2) Record length is greater than the MAXRECORDLENGTH of OPEN^FILE. 3) Record length for $RECEIVE file is less than 14.
General Messages (0 to 999) SQL 523 523 SIO error: EDIT READ error. Cause. Data in a corrupted EDIT file could not be used as input to the program you are executing. Effect. The statement fails. Recovery. Use the recovery facility of the editor to restore the file to a valid state. Reexecute the program with the recovered EDIT file. If the problem persists, report the entire message to your service provider. SQL 624 524 SIO error: File not open. Cause. A sequential I/O (SIO) error occurred. Effect.
General Messages (0 to 999) SQL 527 527 SIO error: Block buffer required for nowait fold or pad. Cause. A sequential I/O (SIO) error occurred. Effect. The statement fails. Recovery. Report the entire message to your service provider. SQL 528 528 SIO error: EDIT write directory overflow. Cause. A sequential I/O (SIO) error occurred. Effect. The statement fails. Recovery. Report the entire message to your service provider. SQL 629 529 SIO error: written.
General Messages (0 to 999) SQL 632 532 SIO error: Nowait I/O restarted. Cause. A sequential I/O (SIO) error occurred. Effect. The nowait I/O operation is restarted. Recovery. Correct the SIO error to continue waiting. SQL 633 533 Internal error: SIO error. Cause. Internal error: A sequential I/O (SIO) error occurred. Effect. SQLCI terminates abnormally. Recovery. Report the entire message to your service provider. SQL 534 534 SIO error: Common file control block (FCB) error. Cause.
General Messages (0 to 999) SQL 537 537 SIO error: An EDIT line overflow occurred. Cause. A sequential I/O (SIO) error occurred. Effect. SQLCI terminates abnormally. Recovery. Report the entire message to your service provider.
General Messages (0 to 999) HP NonStop SQL/MP Messages Manual—427720-006 2- 22
3 SQL Catalog Manager Messages (1000 to 1999) SQL 1001 1001 The Catalog Manager process received a fatal error and is terminating. Cause. An error occurred that might have caused Catalog Manager internal data structures to be inconsistent, so the Catalog Manager terminated itself. Effect. The Catalog Manager process terminates abnormally. It will be restarted the next time a Catalog Manager request is executed. Recovery. Informational message only; no corrective action is needed.
SQL Catalog Manager Messages (1000 to 1999) SQL 1005 1005 An SQl Statistics process could not be started from program file value-1 because $CMON denied permission to start the process. Cause. $CMON did not grant permission to start a program in the requested CPU. Effect. The operation fails. Recovery. Check the CMON configuration for restrictions that might apply. SQL 1006 1006 SQL Statistics server value-1 incurred SEGMENT_DEALLOCATE_ error value-2 trying to deallocate an extended memory segment. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1008 1008 Process value-1 incurred file system error in an Update Statistics operation. Cause. The file system error message indicates the cause. Effect. The operation fails. Recovery. Correct the error condition if possible and perform the operation again. If the error condition cannot be corrected, report the entire message to your service provider. SQL 1009 1009 A heap allocation error occurred in process value-1 in an Update Statistics operation. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1012 1012 SQLCAT made an out of sequence request to SQL Statistics server value-1. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1013 1013 An SQL Statistics server received a request with an invalid operation code. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1016 1016 An error occurred while reporting an event to the EMS collector during an Update Statistics operation, in process value-1. Cause. An EMS or SPI subsystem error occurred. Effect. The operation fails. Recovery. Check for an error condition in the reporting device. Correct the error condition if possible and perform the operation again. If the error condition cannot be corrected, report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1020 1020 SQL Statistics server process could not be started from program file value-1. Error value-2 was returned from PROCESS_CREATE_. Cause. For more information on the explanation of the PROCESS_CREATE_ error, refer to the Guardian Procedure Calls Reference Manual. Effect. The operation fails. Recovery. Correct the error condition if possible and perform the operation again.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Install the correct version of the system software on the indicated system. For assistance, contact your service provider. SQL 1024 1024 An internal error occurred : An unknown exception class was encountered: value-2, in SQL Statistics server. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1025 1025 SQL statistics process value-1 detected an internal error. Cause.
SQL Catalog Manager Messages (1000 to 1999) on the catalog tables and indexes to correct the file labels before performing the MODIFY CATALOG command. If this catalog is being prepared to be moved to a different node, the MODIFY CATALOG command must be performed before the MODIFY LABEL command. SQL 1062 1062 A file system error occurred during an operation on value-1. Cause. See the file system error indicated for a description of the cause. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1066 1066 The maximum timeout value that will be used in DP2 requests for label operations is value seconds. Cause. The =_SQL_CAT_SET_TIMEOUT DEFINE was specified with a valid value. Effect. Any DP2 label requests for DDL commands can take up to the specified timeout value. Recovery. No recovery is needed. SQL 1067 1067 The maximum timeout value specified for DP2 label requests is invalid. The default of value seconds will be used as the maximum. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1070 1070 The reused partition has the dependent object value. reused partition cannot have any dependent objects. A Cause. The USAGES table contains the objects that are dependent on the reused partition. Effect. The statement fails. The partition to be reused is intact. Recovery. Drop the dependent objects and reissue the statement. SQL 1071 1071 ALTER TABLE...REUSE PARTITION cannot be performed against the primary partition of a partitioned table.
SQL Catalog Manager Messages (1000 to 1999) SQL 1074 FORMAT 2 can only be specified if the partition array value of the object is "FORMAT2ENABLED". Cause. A table or index that has a partition array value of "STANDARD" or "EXTENDED" cannot have Format 2 partitions. Effect. The statement fails. Recovery. Reissue the statement without the FORMAT clause. SQL 1080 The inactivity timeout value specified for the Catalog Manager process is invalid. The default value of ~1~ minute will be used instead. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1105 1105 This version of the catalog manager cannot process your request. The catalog manager must be upgraded to a more recent release. Cause. You were running software from more than one version of the SQL product. Effect. The statement fails. Recovery. Contact your system manager to upgrade the catalog manager, SQLCAT, to a more current release, and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) SQL 1109 1109 The catalog manager received a request from a process with a process access ID different from the ID of the process that created the catalog manager. Cause. The process that started the catalog manager changed its process access ID, or a process other than the catalog manager's creator sent a request. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Correct the version number and reissue the command. SQL 1113 1113 Catalog value-1 was not upgraded because its version value-2 is the same as the target version number value-3. Cause. Upgrading a catalog to the same version is invalid. Effect. The command fails. Recovery. Check the target version number and the version of the catalog to be upgraded. Correct any errors and reissue the command.
SQL Catalog Manager Messages (1000 to 1999) SQL 1115 1115 Internal error: The catalog manager referenced an invalid address and caused an internal error. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1116 1116 Internal error: An instruction failed in the catalog manager and caused an internal error. Cause. Internal error: An error occurred in system software. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1119 1119 Internal error: System trap #value-1 occurred in the catalog manager and caused an internal error. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1120 1120 The SQL catalog manager is out of disk space because the extended segment is full. Cause. The catalog manager was out of disk space, or an error occurred in system software. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1123 1123 A programming error in the catalog manager caused an internal error. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1124 1124 The catalog manager cannot process the current request on the object value-1 due to a version error. Cause. The current request involved features that were incompatible with a node on which an object resides. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1126 1126 Version incompatibility: The current request cannot be processed because it contains features incompatible with catalog value-1 of version value-2. Cause. The version of the catalog was incompatible with the request. Effect. The statement fails. Recovery. Change the request, or upgrade the catalog with the UPGRADE CATALOG command, and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) SQL 1129 1129 Version incompatibility: View value-1 of this table resides on a remote system that has a lower NonStop SQL/MP version than this view. Cause. Using ALTER TABLE...ADD COLUMN changes the version of all associated views to that of the current table (depending on the column added). If the version of a view is later than its node's SQL/MP software version, the ALTER TABLE operation fails. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1132 1132 You do not have authority to downgrade the catalog value-1. Cause. You attempted to downgrade a catalog without sufficient authority, as follows: • • • you were not a generalized owner of the catalog, or you did not have read, write, and purge authority for each catalog table, or you did not have write authority for the CATALOGS table in the system catalog. Effect. The downgrade operation fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1135 1135 The DOWNGRADE CATALOG operation could not drop the temporary catalog file label value-1. Cause. See the file system or disk process error following this error for the cause. Effect. Temporary file labels created by Phase 1 of DOWNGRADE CATALOG might still exist. These files have names that begin with the pattern ZZDN*. Recovery. To remove the existing temporary file labels manually, use the CLEANUP utility or the GOAWAY utility.
SQL Catalog Manager Messages (1000 to 1999) SQL 1138 1138 The catalog value-1 specified in the DOWNGRADE CATALOG command does not exist. Cause. You cannot perform a DOWNGRADE CATALOG operation on a non-existent catalog. Effect. The statement fails. Recovery. Specify an existing catalog in the DOWNGRADE CATALOG command. SQL 1139 1139 The system catalog value-1 cannot be used with this command. Cause. You specified a system catalog for a command that only allows user catalogs. Effect. The statement fails.
SQL Catalog Manager Messages (1000 to 1999) SQL 1142 1142 The target version, value-1, must be less than the current version, value-2, of the catalog value-3. Cause. You attempted to downgrade a catalog to its current version or a later version. DOWNGRADE CATALOG and DOWNGRADE SYSTEM CATALOG can only be used to change the version of a catalog to an earlier version. To change the version of a catalog to a later version, see the UPGRADE CATALOG and UPGRADE SYSTEM CATALOG commands. Effect. The command fails.
SQL Catalog Manager Messages (1000 to 1999) SQL 1145 1145 The catalog value-1 is protected by the Safeguard subsystem. The DOWNGRADE CATALOG command does not support downgrading to version value-2 for catalogs protected by the Safeguard subsystem. Cause. Catalog tables protected by the Safeguard subsystem had an object version that was greater than the target version specified in the DOWNGRADE CATALOG command. Effect. The command fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1148 1148 Version Error. The object value-1 of version value-2 cannot be registered in the catalog value-3 of version value4 because the version of the object is higher than the version of the catalog. Cause. The version of the catalog is old than the version of the object. Effect. The statement fails. Recovery. Upgrade the catalog to a later version before reissuing the request. SQL 1149 1149 Version Error.
SQL Catalog Manager Messages (1000 to 1999) of the current release of the SQL software. However, the downgrade operation must be done by a system with a release version equal to or later than the version of the catalog. SQL 1152 1152 Version Error. The catalog table value-1 does not exist in catalog value-2 because the catalog version is too old. The version of the catalog is value-3. Cause. The current operation requires a catalog of a later version. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1155 1155 Version error. It is illegal for object value-1 of version value-2 to have a higher version than its dependent object value-3 of version value-4. The version information in the label(s) is incorrect. Cause. This could be caused by a label corruption. Effect. The statement fails. Recovery. Check the version information of the objects to determine if they contain incorrect values.
SQL Catalog Manager Messages (1000 to 1999) SQL 1202 1202 Catalog table value-1 could not be opened. Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery. Correct the file system error condition and reissue the statement. SQL 1203 1203 Data could not be retrieved from catalog table value-1. Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Correct the catalog name, and reissue the statement. If the name was not specified in your statement, report the entire message to your service provider. SQL 1207 1207 value-1 is not a valid name for a table. Cause. The statement specified an invalid name for a table. Effect. The statement fails. Recovery. Change the invalid table name to a valid name and enter the statement again. SQL 1208 1208 value-1 is not a valid security string. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1210 1210 value-1 is not a valid EXTENT size. Cause. The specified extent size was not in the correct range. The value range allowed for an extent size is 0 through 65,535 pages for Format 1 partitions and 0 through 512,000,000 pages for Format 2 partitions. For additional specifications, refer to the description of the EXTENT attribute in the SQL/MP Reference Manual. Effect. The statement fails. Recovery. Correct the extent size and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) SQL 1214 1214 Only relative files allow RECLENGTH to be specified, or value-1 is not a valid RECLENGTH value. Cause. You specified RECLENGTH for a file that was not a relative file, or the record length was out of the valid range. Effect. The statement fails. Recovery. Change the file organization, or make the record length a range from the total length of all columns in the column list through the value of the block size minus 24, and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Informational message only; no corrective action is needed. SQL 1218 1218 The specified or default MAXEXTENTS value is not sufficient. The MAXEXTENTS value has been automatically set to the new value of value-1 for the file (value-2). Cause. The value for MAXEXTENTS was not enough to load the data into the index. Effect. The statement completes successfully, and the MAXEXTENTS value is set to the new value. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1222 1222 The label of value-1 could not be altered. Cause. See the file system or disk process error following this error for the cause. Effect. The statement fails. Recovery. Correct the file system or disk process error condition and enter the statement again. SQL 1223 1223 The label of value-1 could not be dropped. Cause. See the file system or disk process error following this error for the cause. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1226 1226 Unable to alter the label of value-1 because the index entry for value-2 is missing. Cause. A DDL or utility operation involving the index entry did not complete successfully and left the index entries in an inconsistent state. Effect. The statement fails. Recovery. Use the TMF subsystem to recover the index entries or report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1231 1231 The catalog entry in the INDEXES table for value-1 indicates an invalid COLCOUNT because value-2 is too large. Cause. The catalog was damaged. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1232 1232 The catalog entry in the INDEXES table for value-1 indicates an invalid COLCOUNT because value-2 is too small. Cause. The catalog was damaged. Effect. The statement fails. Recovery. None.
SQL Catalog Manager Messages (1000 to 1999) SQL 1235 1235 The catalog entry in the TABLES table for value-1 indicates an invalid COLCOUNT because value-2 is too small. Cause. The catalog was damaged. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1236 1236 value-1 is not the type of object that is required. Your catalog does not agree with the file label, or related file labels do not agree with this label. Cause. The catalog was damaged. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1239 1239 Another user has locked value-1. Cause. Stated in the error message. Effect. The statement fails. Recovery. Wait until the other user releases the object and reissue the statement. SQL 1240 1240 value-1 could not be opened. Cause. The OPEN operation failed. See the file system or disk process error following this error for the cause. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1243 1243 The PROGRAMS table of the catalog must be empty except for an entry in the system catalog describing the SQLCI2 program. Cause. The PROGRAMS table contained entries for user-created programs. Effect. The statement fails. Recovery. Check that all user-created programs described in the PROGRAMS table are removed and then enter the statement again.
SQL Catalog Manager Messages (1000 to 1999) SQL 1247 1247 The data in the table does not satisfy the constraint. Cause. Stated in the error message. Effect. The statement fails. Recovery. Identify the rows that do not satisfy the constraint by issuing a SELECT statement that contains the negation of the constraint. Delete or modify the identified rows so that remaining rows satisfy the constraint. Enter the CREATE CONSTRAINT statement again.
SQL Catalog Manager Messages (1000 to 1999) SQL 1251 1251 A key-sequenced table with a SYSKEY column as the primary key cannot be partitioned. Cause. Stated in the error message. Effect. The statement fails. Recovery. For a CREATE TABLE statement, include the PRIMARY KEY clause or CLUSTERING KEY clause, and reissue the statement. If you are attempting to add a partition (ALTER statement), re-create the table with a user-defined primary key or clustering key, and load the newly created table.
SQL Catalog Manager Messages (1000 to 1999) SQL 1255 1255 Data compression (DCOMPRESS) does not apply to entrysequenced or relative tables. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct the statement by removing the DCOMPRESS attribute, and reissue the statement. SQL 1256 1256 Internal error: The partition name cannot be altered for a nonpartitioned object. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None.
SQL Catalog Manager Messages (1000 to 1999) SQL 1259 1259 The underlying table is not valid so that this operation could not be performed. Cause. Stated in the error message. Effect. The statement fails. Recovery. Use the VERIFY utility to determine why the table is not valid. Contact your system manager about validating the object, and reissue the statement. SQL 1260 1260 A PARTONLY clause must be specified with this operation. Cause. Stated in the error message. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1263 1263 Duplicate KEYTAG. Cause. Stated in the error message. Effect. The statement fails. Recovery. Change the KEYTAG value to avoid duplicate values. SQL 1264 1264 The primary key is value-1 byte(s) too long. Cause. The sum of the length of the columns that make up the primary key exceeded the limit. This limit depends on the object.
SQL Catalog Manager Messages (1000 to 1999) SQL 1267 1267 The NOPURGEUNTIL time must be on or after Jan 1, 1976. Cause. Stated in the error message. Effect. The statement fails. Recovery. Change the NOPURGEUNTIL time. SQL 1268 1268 The limit has been reached for the number of protection views that can be created for this table. Cause. Stated in the error message. Effect. The statement fails. Recovery. Drop unwanted protection views on the table until this view can be created.
SQL Catalog Manager Messages (1000 to 1999) SQL 1271 1271 The constraint value-1 to be dropped from table value-2 does not exist. Cause. The specified constraint was not in the catalog. Effect. The statement fails. Recovery. Correct the constraint name and reissue the statement. SQL 1272 1272 Column value-1 cannot be used in a unique index because the column can contain null values. Cause. A unique index cannot include columns that can contain null values. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) Recovery. If possible, correct the condition that caused the view to become invalid, and reissue the statement. If the condition cannot be corrected, DROP the view. SQL 1282 1282 The CLEANUP command does not remove a catalog description, a catalog table, or catalog index. Cause. You requested that the CLEANUP utility remove a catalog table or index by using the CATALOGS option.
SQL Catalog Manager Messages (1000 to 1999) returned from ABORTTRANSACTION, BEGINTRANSACTION, and ENDTRANSACTION. Contact your system manager to use the TMF subsystem to recover the transaction. SQL 1304 1304 Data in catalog table value-1 could not be updated. Cause. See the file system message following this error for the cause. Effect. The statement fails. Recovery. Reissue the statement. If another user has locked the data, wait and reissue the statement later.
SQL Catalog Manager Messages (1000 to 1999) Recovery. From SQLCI, enter HELP ALTER INDEX to find the attribute that is in error. Remove the attribute that is not allowed and reissue the statement. SQL 1308 1308 An attribute was specified that is not allowed in an ALTER TABLE statement. Cause. A specified attribute was not allowed. Effect. The statement fails. Recovery. From SQLCI, enter HELP ALTER TABLE to find the attribute that is in error.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Shorten the view definition by using smaller names or short correlation names for qualification. SQL 1312 1312 Too many values are specified for the key of value-1. Cause. The number of values in a FIRST KEY or LAST KEY clause exceeded the number of columns in the primary key. Effect. The statement fails. Recovery. Correct the FIRST KEY or LAST KEY value and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) SQL 1316 1316 value-1 must be described in the same catalog as value2. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct the catalog name. SQL 1317 1317 An access path through catalog table value-1 could not be established (START subset). Cause. See the file system error message following this error for the cause. Effect. The statement fails. Recovery. None. Report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1320 1320 Internal error: allowed. Unable to open more caches than Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. Stop the catalog manager (SQLCAT) process and reissue the statement. SQL 1321 1321 An access path through table value-1 could not be established (START subset). Cause. See the file system error following this error for the cause. Effect. The statement fails. Recovery. None.
SQL Catalog Manager Messages (1000 to 1999) SQL 1324 1324 The owner of this view must be value-1,value-2 to be consistent with the security of the table on which it is declared. Cause. The security of a view depends on the security of the underlying table. If you change the user ID for a table, the system changes the user ID for dependent protection views to the same user ID. You cannot change the user ID for a protection view. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1350 1350 Transaction processing has not been enabled. Cause. Stated in the error message. Effect. The statement fails. Recovery. Contact your system manager to enable TMF. SQL 1351 1351 A TMF error was encountered during transaction processing. Cause. Stated in the error message. Effect. The statement fails. Recovery. Contact your system manager to correct the TMF error condition. SQL 1352 1352 Transaction processing has been disabled. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1355 1355 The SQL compiler, the SQL utility, or the catalog manager must be licensed to perform this operation. Cause. Stated in the error message. Effect. The statement fails. Recovery. Contact your system manager to license the program with the FUP LICENSE command. SQL 1356 1356 The owner of the protection view must have read and write access to the underlying table unless the protection view is secured "-" for the operations that the owner lacks.
SQL Catalog Manager Messages (1000 to 1999) SQL 1359 1359 Catalog value-1 is logically inconsistent. The USAGES table does not show a required relationship for value-2. Cause. Stated in the error message. Effect. The statement fails. Recovery. Repair the USAGES tables. SQL 1360 1360 Internal error: A timestamp conversion error occurred. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1363 1363 You attempted to add a partition and the FIRST KEY value is already the FIRST KEY of another partition. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct the FIRST KEY value. SQL 1364 1364 The selection expression in the protection view definition is too large. Cause. The view definition would not fit in the file label. Effect. The statement fails. Recovery. Change the selection expression.
SQL Catalog Manager Messages (1000 to 1999) SQL 1366 1366 The default value for column value-1 could not fit in the label because too many default values were specified. Cause. All of the default values specified for the table do not fit in the file label. Effect. The statement fails. Recovery. Change some column definitions to reduce the space their definitions require. Consider using DEFAULT SYSTEM instead of specifying the value because the SYSTEM default value requires less space.
SQL Catalog Manager Messages (1000 to 1999) SQL 1370 1370 Constraint value-1 of value-2 is not described in catalog value-3. Cause. Stated in the error message. Effect. The statement fails. Recovery. Check the constraint name in the catalog. SQL 1371 1371 The BLOCKSIZE value was rounded from value-1 to value-2. Cause. Stated in the warning. Effect. The statement was executed. Recovery. Informational message only; no corrective action is needed. SQL 1372 1372 The user-defined TMF transaction was aborted.
SQL Catalog Manager Messages (1000 to 1999) SQL 1374 1374 A file system error occurred after the catalog manager altered some of the security attributes that you asked for, but before changing the owner of the program file. Your catalogs incorrectly reflect the new owner, but the label of the program file still records the old owner. Your data dictionary is inconsistent. Cause. Stated in the error message. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1378 1378 There are two catalog managers (SQLCAT) running under the same transaction. Cause. A catalog manager attempted to access a catalog that was already being accessed by another catalog manager running under the same transaction as the first catalog manager. This situation can only occur if you have introduced logic that begins a transaction and then starts two concurrent processes, each of which invokes catalog managers. Effect. The statement fails.
SQL Catalog Manager Messages (1000 to 1999) SQL 1382 1382 value-1 already exists for value-2 (see catalog table value-3). Cause. Stated in the error message. Effect. The statement fails. Recovery. If the information in your catalog does not agree with the disk directory, your dictionary is corrupted. Contact your system manager about repairing the catalog with the CLEANUP utility or a licensed SQLCI2 process.
SQL Catalog Manager Messages (1000 to 1999) SQL 1385 1385 A row could not be found in catalog table value-1. Cause. Stated in the error message. Effect. The statement fails. Recovery. If the information in your catalog does not agree with the disk directory, your dictionary is corrupted. Contact your system manager about repairing the catalog with the CLEANUP utility or a licensed SQLCI2 process. For more information on CLEANUP and licensed SQLCI2, refer to the SQL/MP Installation and Management Guide.
SQL Catalog Manager Messages (1000 to 1999) SQL 1388 1388 Catalog value-1 could not be found in the system catalog (see value-2 table). Cause. Stated in the error message. Effect. The statement fails. Recovery. If the CATALOGS table does not have an entry for an existing catalog, the CATALOGS table might be corrupted. Contact your system manager about using a licensed SQLCI2 process to insert the appropriate entry in the CATALOGS table or to drop the catalog without reference to the CATALOGS table.
SQL Catalog Manager Messages (1000 to 1999) SQL 1392 1392 The TRANSIDS or USAGES table of catalog value-1 has been secured so that some users who have read access do not also have write access. The users without write access cannot compile programs using objects in this catalog. Cause. Stated in the error message. Effect. Some users do not have write access to the TRANSIDS or USAGES table of the indicated catalog. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1400 1400 Altering the CATALOGS table to remove the entry for the catalog being dropped is not allowed. However, because this command was issued from a licensed requester, the catalog manager will attempt to complete this operation without reference to the CATALOGS table. Cause. Stated in the error message. Effect. If the statement does not complete successfully, there is no effect, and the CATALOGS table will not reflect the absence of the dropped catalog.
SQL Catalog Manager Messages (1000 to 1999) SQL 1403 1403 Resecuring an index of a catalog table with the ALTER INDEX statement is not allowed. Cause. Stated in the error message. Effect. The statement fails. Recovery. Informational message only; no corrective action is needed. SQL 1404 1404 One or more of the table partitions were empty, or the entire table was empty.
SQL Catalog Manager Messages (1000 to 1999) SQL 1407 1407 The CATALOGS table corresponding to this system is not available. Cause. The CATALOGS table corresponding to this system either does not exist or the disk on which the CATALOGS table resides is not operating. Effect. The CREATE CATALOG or DROP CATALOG statement fails. Recovery. If the disk is not operating, use PUP and TMFCOM to bring the disk up, issue an ENABLE VOLUMES command from TMFCOM, and reissue the command.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Correct the statement. Check the view text stored in the VIEWS table. SQL 1411 1411 DROP PARTITION cannot be performed against a nonempty partition of a partitioned table. Cause. DROP PARTITION can be performed only against a partition that is empty. Effect. The statement fails. Recovery. Correct the statement. For a partitioned table, verify that the object name identifies an empty partition.
SQL Catalog Manager Messages (1000 to 1999) SQL 1430 1430 You cannot alter the extents of an entry-sequenced or relative file. The option will be ignored. Cause. Stated in the warning message. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 1431 1431 You cannot change slack percentages for an entrysequenced or relative file. The option will be ignored. Cause. Stated in the warning message. Effect. None. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1434 1434 For a two-way split, the key values specified in the FROM...UP TO clauses must be identical. Cause. You specified a two-way split and used different key values in the FROM...UP TO clauses. Effect. The statement fails. Recovery. Specify the same key values in each clause and reissue the request. SQL 1435 1435 For a one-way split, the correct syntax is MOVE FROM KEY [UP TO LAST KEY] TO target-partition. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1438 1438 Only one-way or two-way split is allowed at this time. Cause. Stated in the error message. Effect. The statement fails. Recovery. Correct the syntax and reissue the statement. SQL 1439 1439 Unable to complete this DDL operation. Cause. A DDL operation involving a partition did not complete successfully, and the system is attempting to delete all temporary and target files. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1442 1442 value-1 has a Program Catalog Version (PCV) of value-2, which is greater than the catalog version of this operation. Cause. A program had a PCV that was greater than the catalog version of this operation. Effect. The operation fails. Recovery. Drop objects that have later PCVs and reissue the request. SQL 1443 1443 SQLCAT internal error. specified. Unknown catalog table number was Cause. SQLCAT internal error. Effect. The operation fails.
SQL Catalog Manager Messages (1000 to 1999) SQL 1501 1501 Cannot open the Character Processing Rules compiler process. Cause. Probable failure in the Character Processing Rules compiler. Effect. Fatal error: Transaction terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 1502 1502 Cannot send startup message to Character Processing Rules compiler. Cause. Probable failure in the Character Processing Rules compiler. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1505 1505 Collation compile terminated with errors; see listing file value-1. Cause. The collation source contained one or more errors. Effect. Fatal error: Transaction terminates abnormally. Recovery. Check the compile listing. Make corrections to the source, and then reissue the CREATE COLLATION command. SQL 1506 1506 Collation compile terminated with internal error value2; see listing file value-1. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1509 1509 Read of character processing rules source failed while copying to catalog. Cause. An I/O error occurred during the read operation. The following message lists the file system error code. Effect. Fatal error: Transaction terminates abnormally. Recovery. Correct the file system problem and reissue the CREATE COLLATION command. SQL 1510 1510 Unable to read =_DEFAULTS DEFINE. Cause. Internal error. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1514 1514 EDITREAD failed with code value-1 during CREATE COLLATION. Cause. The EDITREAD operation encountered an error while copying the collation source to the catalog CPRLSRCE table. Effect. The transaction terminates abnormally. Recovery. Check the collation source to verify that it has not been corrupted. If the error code indicates a bad EDIT file, correct the problem and reissue the request. SQL 1515 1515 The CPRULES table of the catalog is not empty.
SQL Catalog Manager Messages (1000 to 1999) Recovery. None. Report the entire message to your service provider. SQL 1518 1518 Collation value-1 is not a valid substitute for the specified partition. Cause. Internal error. Effect. The statement fails and the transaction terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 1519 1519 Error -value-1 occurred while comparing collations value-2 and value-3; the collations were treated as not equivalent. Cause.
SQL Catalog Manager Messages (1000 to 1999) Recovery. None. Report the entire message to your service provider. SQL 1522 1522 The collation resulting from a CREATE COLLATION operation has a version number higher than the system where the collation is to reside. Cause. You attempted to create a collation on a system that does not support the collation. Effect. Fatal error: Transaction terminates abnormally. Recovery. Create the collation on a system that is capable of supporting the collation.
SQL Catalog Manager Messages (1000 to 1999) SQL 1525 1525 Error value-1 occurred while writing EDIT file value-2 for source of collation value-3. Cause. The BACKUP utility attempted to copy a collation source from the catalog CPRLSRCE table to the EDIT file, and encountered an error while writing to the EDIT file. Effect. The BACKUP utility cannot back up the source for the collation. The collation is skipped and processing continues. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1529 1529 Table or index value-1 references too many collations. Cause. An SQL table and its constraints or an SQL index can reference a maximum of eight nonequivalent collations. Effect. The statement fails. Recovery. Correct the statement. SQL 1530 1530 Invalid character set name. Cause. The specified character set name was not valid. Effect. The statement fails and the transaction terminates abnormally. Recovery. Enter a supported character set name.
SQL Catalog Manager Messages (1000 to 1999) SQL 1533 1533 The overriding collation on UPSHIFTed column value-1 has different upshift rules than the collation in the base table. Cause. A COLLATE clause in the CREATE INDEX command specified a different collation than the column definition in the base table. If a column has the UPSHIFT attribute, the collation in the COLLATE clause must have the same upshift rules as the collation used in the base table. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1536 1536 Unable to get the largest possible value for the collation value-1. The procedure CPRL_GETLAST_ returned error code value-2. Cause. Internal error. Effect. Fatal error: The transaction terminates abnormally. The collation might be damaged. Recovery. None. Report the entire message to your service provider. SQL 1537 1537 Collation value-1 is invalid; the CPRL_GETUPSHIFTTABLE_ procedure returned error value-2. Cause. Internal error. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1550 1550 A SECURE clause was included in the CREATE statement for value-1, but the associated file name or user ID had Safeguard defaults, so the SQL object was created with Safeguard protection. The operating system security vector from the SECURE clause was added to the SQL object file label and catalog entry, but since the SQL object is now protected by the Safeguard subsystem, the security vector will be ignored when security is enforced. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1552 1552 The CLEARONPURGE option is not allowed in the CREATE or ALTER statement for value-1 because the SQL object is protected by the Safeguard subsystem. Cause. You cannot specify the CLEARONPURGE option in a CREATE or ALTER DDL command for an object protected by the Safeguard subsystem. The security attributes associated with an SQL object protected by Safeguard software can only be altered using a Safeguard interface such as SAFECOM. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1555 1555 Version incompatibility: Unable to write to catalog value-1 of version value-2. This version of the catalog cannot support program value-3 because the program file is protected by the Safeguard subsystem. Cause. An attempt was made to write to a catalog to describe a program that is protected by the Safeguard subsystem, and the catalog version does not support Safeguard protection. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1558 1558 Error #value-1 was returned by the Safeguard subsystem. Cause. An SPI request to the Safeguard subsystem failed. Effect. The statement fails. Recovery. Check the Safeguard error in the SQLCA to determine the cause. Report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1561 1561 Unable to access system number value-1 to check Safeguard user defaults for user value-2. The GETSYSTEMNAME procedure returned error #value-3. Cause. While attempting to obtain the node name associated with the current user to check for Safeguard user defaults, the GETSYSTEMNAME procedure reported an error. Effect. The statement fails. Recovery. Reissue the statement. If it fails again, report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1600 1600 Error occurred while closing the source partition during an ALTER TABLE or ALTER INDEX request. Cause. See the file system error listed in the message for the reason for the failure. Effect. The statement fails. Recovery. Correct the error condition and reissue the request. SQL 1601 1601 The WITH SHARED OPTION is currently not support for this command. Cause. The DDL request included the WITH SHARED ACCESS option.
SQL Catalog Manager Messages (1000 to 1999) SQL 1604 1604 An unsupported combination of options was requested. REPORT, COMMIT, and NAME clauses can only be specified with the WITH SHARED ACCESS option. Cause. An unsupported option was specified. Effect. The statement fails. Recovery. Change the option and reissue the command. SQL 1605 1605 The WITH SHARED ACCESS option has been specified on a non-audited object. WITH SHARED ACCESS only works with audited objects. Cause. Stated in the error message.
SQL Catalog Manager Messages (1000 to 1999) SQL 1608 1608 Not all event messages requested by the REPORT OPTION were reported to the EMS collector. Cause. Problems occurred during reporting that caused several events to be omitted from the report. Effect. None. Recovery. See the EMS log for a description of the situation. SQL 1609 1609 A unexpected error was detected while processing the REPORT OPTION. Cause. Internal error: An error occurred while processing the statement. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1612 1612 A sequential read error occurred while performing the data movement operation. Error returned is value-1. Cause. Internal error: An error occurred while processing the statement. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1613 1613 An unexpected error occurred while performing the data movement operation. Cause. Internal error: An error occurred while processing the statement. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1616 1616 The BEFORE and AFTER times do not specify a valid time interval to commit. Cause. You specified an invalid time interval. The command syntax requires valid BEFORE and AFTER times. The specified time values are disjoint; both cannot be valid. Effect. The statement fails. Recovery. Specify valid times for BEFORE and AFTER and reissue the statement. SQL 1617 1617 The AFTER time specified is more than 10 days in the future. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1620 1620 The ROLLBACK was requested as part of the commit criteria. The command has been aborted. Cause. The command syntax requested that the command be terminated with the commit option. Effect. The statement fails. Recovery. Reissue the statement at a later time. SQL 1621 1621 A CONTINUE command was expected for statement value-1, instead another DDL command was requested. Cause. There is an operation in progress with this SQLCAT.
SQL Catalog Manager Messages (1000 to 1999) SQL 1623 1623 A CONTINUE command was requested but there is no prior request in progress. Cause. A CONTINUE command requested that a previous command be continued, but there is no command in progress. Effect. The statement fails. Recovery. Enter a valid command. SQL 1624 1624 There are too many ONCOMMITERROR clauses in the request. Cause. The ONCOMMITERROR clause was specified too many times in the SQL statement. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1627 1627 The EMS collector specified in the REPORT clause is invalid. Cause. The collector name used in the REPORT clause was invalid because it did not specify a valid EMS collector. If a DEFINE was specified, it must be of type CLASS MAP. Effect. The statement fails. Recovery. Specify a valid EMS collector name and reissue the statement. SQL 1628 1628 Failed to open file value-1 during retryable error processing. See related file system error for details.
SQL Catalog Manager Messages (1000 to 1999) SQL 1630 1630 The requested ALTER request has completed either successfully or unsuccessfully, please run FUP RELOAD on value to reclaim any freespace. Cause. For certain alter requests, a special “in-place” split operation is executed. After an “in-place” split has completed, extra space exists in the file that needs to be reclaimed. A FUP RELOAD operation reclaims this space and allows it to be reused.
SQL Catalog Manager Messages (1000 to 1999) SQL 1633 1633 Partition value-1 is not adjacent to value-2. Cause. When moving the boundary between two table or index partitions, the name specified for the target partition was not adjacent to the source. The target must be logically prior to the source or logically after the source. Effect. The statement fails. Recovery. Specify the correct source and target partition, and reissue the request.
SQL Catalog Manager Messages (1000 to 1999) SQL 1636 1636 Cannot perform requested operation because value-1 has UNRECLAIMED FREESPACE set. Space needs to be reclaimed before continuing. Cause. The operation failed because the table or index has unreclaimed freespace. This can happen if a previous ALTER TABLE or ALTER INDEX operation caused unreclaimed freespace to be generated and a FUP RELOAD operation was not executed. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1639 1639 Attempting to move data to an existing partition value1. To perform this operation, WITH SHARED ACCESS must be specified. Cause. Merge and move boundary operations only work when WITH SHARED ACCESS is specified. Effect. The statement fails. Recovery. If a merge or move boundary operation is desired, specify WITH SHARED ACCESS and reissue the request.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Alter the audited attribute of the referencing table so that the audited attribute of the referencing table is the same as the referenced table. SQL 1703 1703 All referential constraints must be dropped prior to performing this DDL operation. Cause. SQL could not perform this DDL operation because the table has referential constraints. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) Recovery. None. Report the entire message to your service provider. SQL 1800 1800 Unable to modify the node number in the partition array in the file label of value-1 because the modified partition name in the partition array will have the same node number and volume name as the other partition. Cause. Two partitions cannot have the same node number and volume name. Effect. The command fails. Recovery. Specify the correct node number, and reissue the command.
SQL Catalog Manager Messages (1000 to 1999) SQL 1904 1904 Internal error: routines. Invalid slack value for SQL load Cause. Internal error: The values were not in the range 0 through 99. Effect. The statement fails. Recovery. Correct the values. SQL 1905 1905 SQL load routines: Target partition is full. If the operation is a two-way split, then the second target partition is full. Cause. The size of the target file is too small to hold the data. Effect. The statement fails. Recovery.
SQL Catalog Manager Messages (1000 to 1999) SQL 1908 1908 Internal error: There is an inconsistency between the file label and the partition array for a partition of the destination file. Cause. For each partition, the number of pages in the primary extent, the number of pages in the secondary extents, and the maximum number of extents are recorded both in the file label and in the partition array. The loader checks whether the values match.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Correct the error conditions. SQL 1912 1912 SQL load routines: error value-3. Sort receive error value-2, system Cause. For more information about the errors, refer to the FastSort Manual for the sort error and the Guardian Procedure Errors and Messages Manual for the system error. Effect. The statement fails. Recovery. Correct the error conditions. SQL 1913 1913 SQL load routines: error value-3. Sort finish error value-2, system Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1916 1916 SQL load routines: Keys out of order. Cause. Rows were not ordered by the value of the primary key. Effect. The statement fails. Recovery. Remove the SORTED option, or pass rows ordered by primary key value. SQL 1917 1917 SQL load routines: value-1. File system record routine error Cause. See the file system error for the cause. Effect. The statement fails. Recovery. Correct the file system error condition.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Check that the SQLUTIL and SQLCAT modules are compatible with the operating system version. SQL 1921 1921 SQL load routines: File system error value-1. Cause. See the file system error for the cause. Effect. The statement fails. Recovery. Correct the file system error condition. SQL 1922 1922 Internal error: value-1. Error setting or clearing a corrupt bit Cause. Some problem occurred when setting or clearing the corrupt flag on a file or table.
SQL Catalog Manager Messages (1000 to 1999) Recovery. None. Report the entire message to your service provider. SQL 1925 1925 Internal error: Caller aborted load operation. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1926 1926 Internal error: No load operation in progress. Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None.
SQL Catalog Manager Messages (1000 to 1999) SQL 1929 1929 SQL load routines: communications error. Record generator value-4 process Cause. Communications with the record generator failed because either an internal error occurred, or the record generator was stopped or abended. Effect. The statement fails. Recovery. Reissue the statement if the CPU went down or if the record generator was stopped. Otherwise, report the entire message to your service provider.
SQL Catalog Manager Messages (1000 to 1999) SQL 1933 1933 SQL load routines: Syntax error in configuration file for parallel index load, line value-1. Cause. The configuration file specified for loading the index partitions in parallel had a syntax error on the line specified in the error text. Effect. The statement fails. Recovery. Correct the syntax error and reissue the statement.
SQL Catalog Manager Messages (1000 to 1999) SQL 1937 1937 SQL load routines: File system error value-1 was returned during an attempted split operation. If the operation is a one-way split, then the error refers to the source partition. If the operation is a two-way split, then the error refers to the first target partition. Cause. See the file system error description.
SQL Catalog Manager Messages (1000 to 1999) Recovery. None. Report the entire message to your service provider. SQL 1941 1941 Internal error: record read routine. File could not be closed by sequential Cause. Internal error: Stated in the error message. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 1942 1942 Internal error: record read routine. Records could not be read by sequential Cause. Internal error: Stated in the error message. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1945 1945 Unable to upshift the default string in column value-1. Cause. One or more characters in the default string have no equivalent upshifted character. Effect. The command fails. Recovery. Correct the default string by using only characters that have an equivalent upshifted character or do not use the UPSHIFT clause. SQL 1958 1958 Test point value-1 error was triggered. Cause. The indicated test point error was triggered.
SQL Catalog Manager Messages (1000 to 1999) Recovery. Be sure the proper file is being specified as the recovery file. SQL 1961 1961 Internal error: The reply from RECGEN value-4 contains an invalid eyecatcher. Cause. Internal error: Stated in the error message. Effect. The parallel index load fails. Recovery. None. Report the entire message to your service provider. SQL 1962 1962 Internal error: The reply from RECGEN value-4 an invalid message type. contains Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1965 1965 SORTPROGvalue-4 value-3. does not support required feature level Cause. The SORTPROG program listed in the message was too old. Effect. The index load fails. Recovery. Install a later version of the SORTPROG program on the named node and reissue the request. SQL 1966 1966 SQL load routines: File system error value-1 occurred during an operation onvalue-4 . Cause. See the file system error listed in the message for a description of the cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1973 1973 Configuration file error: The second word of the statement is not a valid keyword, line value-1. Cause. The keyword after CREATEINDEX in a configuration file statement was not “BASETABLE”, “INDEX,” or “LOCALONLY”. Effect. The parallel index load fails. Recovery. Correct the syntax error in the configuration file, and reissue the statement. SQL 1974 1974 Configuration file error: value-1. Invalid delimiter, line Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1977 1977 Configuration file error: Invalid keyword, "DEFAULT" or partition name expected, line value-1. Cause. Syntax error. The third word in the statement was not the keyword “DEFAULT” or a valid partition name. Effect. The parallel index load fails. Recovery. Correct the syntax, and reissue the statement. SQL 1979 1979 Configuration file error: line value-1. Left parenthesis not found, Cause. Syntax error.
SQL Catalog Manager Messages (1000 to 1999) SQL 1982 1982 Configuration file error: attribute list, line value-1. Invalid attribute or Cause. The attribute or attribute list contains an invalid item. Effect. The parallel index load fails. Recovery. Correct the invalid item or items specified in the attribute list and reissue the SQL statement. SQL 1983 1983 Configuration file error: SEGMENT keyword, line value-1. Invalid value for NUMREC or Cause. Stated in the error message. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1986 1986 Configuration file error: value-1. Swap file must be local, line Cause. The swap file was not on the same node as the process associated with it. Effect. The parallel index load fails. Recovery. Correct the error in the configuration file, and reissue the SQL statement. SQL 1987 1987 Configuration file error: value-1. Invalid node name, line Cause. The current word was more than eight characters or was not a valid node name. Effect.
SQL Catalog Manager Messages (1000 to 1999) SQL 1990 1990 Configuration file error: 1. Invalid keyword, line value- Cause. An invalid keyword was detected by SQL. Effect. The parallel index load fails. Recovery. Correct the error in the configuration file, and reissue the statement. SQL 1991 1991 Configuration file error: Invalid keyword combination. "SCRATCHON" and "NOSCRATCHON" are mutually exclusive, line value-1. Cause.
SQL Catalog Manager Messages (1000 to 1999) SQL 1994 1994 Configuration file error: Program must reside on the system local to the index or basetable, line value-1. Cause. You specified a program that is remote to the index or base table. Effect. The parallel index load fails. Recovery. Correct the error in the configuration file, and reissue the SQL statement.
4 SQL Compiler Messages SQL 2001 2001 Internal error: SQL compiler. Cause. Internal error: The SQL compiler detected an error in its internal structures or in a received message. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2002 2002 Error value-1 encountered in allocating the extended segment of the process that called the SQL compiler. Cause.
SQL Compiler Messages SQL 2005 2005 Error encountered in closing the program file. file system error code for more information. See the Cause. The SQL compiler could not close the program file after compilation. Effect. The SQL compilation terminates abnormally. Recovery. Correct the file system error condition and recompile. SQL 2006 2006 Error encountered in reading SQL information from the program file. See the file system error code for more information. Cause.
SQL Compiler Messages SQL 2009 2009 No SQL source information found in program file. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery. Check that the host program is processed for SQL. For a COBOL host program, preprocess with the SQL COBOL process and then compile with COBOL. For C or Pascal host programs, compile with the language compiler. Finally, SQL compile the program. SQL 2010 2010 Error encountered sensing current transaction ID.
SQL Compiler Messages SQL 2012 2012 Internal error: SQL compiler exception number value-1 has occurred. Cause. Internal error: The SQL compiler detected an error in its internal structures or in a received message. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2013 2013 Internal error: value-1. SQL compiler information parameter is Cause.
SQL Compiler Messages SQL 2016 2016 SQL compiler tried to invalidate the program file, but the program file is not SQL sensitive. Mode parameter is value-1. Cause. The SQL compiler detected an error in its internal structures or in a received message. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2017 2017 Inconsistency detected in message received by the SQL compiler. Cause.
SQL Compiler Messages SQL 2020 2020 The name of the default SQL catalog could not be put in network form. Cause. The volume name of the catalog name had eight or more characters. Volume names for SQL catalogs cannot exceed seven characters, including the dollar sign ($). Effect. The SQL compilation terminates abnormally. Recovery. Correct the volume name for the catalog and recompile. SQL 2021 2021 The name value-1 of the SQL catalog that will contain the program cannot be put in network form. Cause.
SQL Compiler Messages SQL 2024 2024 The FORCE or NOFORCE option was specified more than once. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery. Remove the duplicate option and recompile. SQL 2025 2025 The compiler option value-1 specified for the SQL compiler is invalid. Cause. The SQLCOMP command includes an invalid compiler option. Effect. The SQL compilation terminates abnormally. Recovery.
SQL Compiler Messages SQL 2028 2028 Error encountered while opening the listing file for the SQL compiler. See the file system error code for more information. Cause. See the file system error following this error for the cause. Effect. The SQL compilation terminates abnormally. Recovery. Correct the file system error condition and recompile. SQL 2029 2029 Error encountered while checking the characteristics of the listing file. Cause.
SQL Compiler Messages SQL 2031 2031 Error encountered during OPEN of the program file to read SQL information. (Parameter is value-1.) Cause. See the file system error following this error for the cause. Typical causes are: • • • You do not have authority to read the program file The file does not exist The file was stripped by the Binder program The SQL compiler does not work with an object file that has been stripped by the Binder program.
SQL Compiler Messages SQL 2034 2034 Internal error: overflow. SQL compiler string operation caused an Cause. Internal error: The SQL compiler detected an error in its internal structures or in a received message. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2035 2035 Internal error: occurred. SQL compiler arithmetic overflow Cause. The SQL compiler detected an error in its internal structures or in a received message.
SQL Compiler Messages SQL 2038 2038 Error encountered in closing the listing file for the SQL compiler. See the file system error code for more information. Cause. The SQL compiler detected an error in its internal structures or in a received message. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2039 2039 Error encountered during initialization to read program file. See the file system error code for more information. Cause.
SQL Compiler Messages SQL 2041 2041 Conflicting EXPLAIN options or duplicate EXPLAIN options have been specified. Cause. EXPLAIN option conflict. Typical causes are: • • • • EXPLAIN and NOEXPLAIN are specified at the same time EXPLAIN is specified more than once An attribute of the EXPLAIN option contradicts another attribute An attribute is specified more than once. For example: EXPLAIN PLAN PLAN. Effect. The SQL compilation terminates abnormally. Recovery. Remove the option and recompile.
SQL Compiler Messages SQL 2044 2044 Error encountered in reading stored DEFINEs from the program file. Read count was value-1. See the file system error code for more information. Effect. The SQL compiler detected an error in its internal structures or in a received message. Cause. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2045 2045 Error encountered in recording an SQL compilation or recompilation event. Cause.
SQL Compiler Messages SQL 2048 2048 The RECOMPILE or NORECOMPILE option was specified more than once. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery. Remove the duplicate option and recompile. SQL 2049 2049 The RECOMPILEONDEMAND or RECOMPILEALL or RECOMPILEFAST option was specified more than once. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery. Remove the duplicate option and recompile.
SQL Compiler Messages SQL 2052 2052 A logical name can be up to 24 characters. Cause. A logical name longer than 24 character was specified. Effect. The SQL compilation terminates abnormally. Recovery. Specify a valid logical name and recompile. SQL 2053 2053 Input file is not a program file or an object file. Cause.
SQL Compiler Messages SQL 2056 2056 The owner of the SQL compiled program was changed from value-1,value-2 to value-3,value-4. Cause. The SQL compiler was invoked under Safeguard default protection, so the compiled program is protected by the Safeguard subsystem. The SQL compiler cannot reset the owner of the file to the original owner because the file is protected by the Safeguard subsystem. Effect. SQL compilation will proceed, but the owner of the file is different. Recovery.
SQL Compiler Messages SQL 2059 2059 The object file that is being SQL compiled is not an executable object. Cause. The object must be executable at SQL compilation time. But it was not. Effect. The SQL compilation terminates abnormally. Recovery. Link or bind the object first and recompile. SQL 2060 2060 The limit has been reached for the number of dependencies that can be added for this program. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery.
SQL Compiler Messages SQL 2070 2070 The OSS pathname does not exist. Cause. The SQL compiler could not find the OSS pathname program. Effect. The statement does not compile. Recovery. Correct the pathname and reissue the statement. SQL 2071 2071 An invalid OSS pathname was supplied. Cause. The pathname was not a valid OSS pathname. Effect. The statement does not compile. Recovery. Correct the pathname and reissue the statement.
SQL Compiler Messages SQL 2074 2074 The SQL compiler detected an error while reading or writing file owner or group ID information for the OSS program file. Cause. The SQL compiler detected an internal error in the ownership of an OSS SQL program file. Effect. The SQL compilation terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 2075 2075 The SQL compiler detected an error while reading or writing file security information for the OSS program file. Cause.
SQL Compiler Messages SQL 2103 2103 The program was modified using the Binder program after it was SQL compiled. Cause. Stated in the error message. Effect. SQL compilation fails. Recovery. SQL compile the program. SQL 2104 2104 The program was modified using the NLD program after it was SQL compiled. Cause. Stated in the error message. Effect. SQL compilation fails. Recovery. SQL compile the program.
SQL Compiler Messages SQL 2110 2110 The NOREGISTER ON option cannot be used on a program that has already been SQL compiled and registered in a catalog. Cause. Stated in the error message. Effect. SQL compilation fails. Recovery. Preprocess the program again and then SQL compile with the NOREGISTER ON option. SQL 2111 2111 The REGISTERONLY ON option cannot be used with other SQLCOMP options that influence how an SQL program is compiled. Cause.
SQL Compiler Messages SQL 2114 2114 The REGISTERONLY ON option cannot be used on a program that is already registered in a catalog. Cause. Stated in the error message. Effect. The SQL compilation fails. Recovery. Use the REGISTERONLY OFF option to SQL compile a program that is already registered in a catalog. SQL 2115 2115 The program was not SQL compiled. Cause. A program must be SQL compiled before it can be installed with the REGISTERONLY ON option. Effect. SQL compilation fails. Recovery.
SQL Compiler Messages SQL 2131 2131 The value-1 option was specified more than once. Cause. Stated in the error message. Effect. The SQL compilation terminates abnormally. Recovery. Remove the duplicate option and recompile. SQL 2132 2132 The subvolume name value-1 is invalid. Cause. See the file system error following this error for the cause. Effect. The SQL compilation terminates abnormally. Recovery. Correct the file system error condition and recompile.
SQL Compiler Messages SQL 2062 2062 The SQL-COMPILER option STOREDDEFINES applies only to programs that have been SQL compiled previously. Cause. The STOREDDEFINES option is specified while SQL compiling a program that have not been SQL compiled previously. Effect. The SQL compilation terminates. Recovery. Remove the option and recompile. SQL 2063 2063 The EXPLAIN TOKENIZED option must be followed by a file name. Cause. The SQLCOMP command includes an incomplete compiler option EXPLAIN TOKENIZED. Effect.
SQL Compiler Messages SQL 2135 2135 Recompiled because the statement was uncompiled. Cause. Recompilation was performed because the statement was uncompiled. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 2136 2136 Recompiled because the plan was corrupted. Cause. Recompilation was performed because the plan was corrupted. Effect. None. Recovery. Informational message only; no corrective action is needed.
SQL Compiler Messages SQL 2139 2139 Recompiled because the referenced name changed to value1. Cause. Recompilation was performed because a name changed. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 2140 2140 Recompiled because an error occurred while reading the file label for object value-1. Cause. Recompilation was performed because an error occurred while reading the file label for an object. Effect. None. Recovery.
SQL Compiler Messages SQL 2143 2143 Recompiled because the SQL compiler found the plan invalid on a previous compile, but at that time it did not recompile the plan because the plan was still operable. Cause. Recompilation was performed because the plan was invalid and had not be recompiled. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 2144 2144 Recompiled because object value-1 failed the similarity check or the object does not have the similarity check enabled.
SQL Compiler Messages HP NonStop SQL/MP Messages Manual—427720-006 4- 28
5 SQL Compiler Parser Messages (3000 to 3999) SQL 3001 3001 This clause appears in the SQL statement more than once. Cause. The clause was repeated in the SQL statement. Effect. The statement does not compile. Recovery. Remove the duplicate clause and recompile. SQL 3002 3002 Unsigned type NUMERIC or COMP items of 10 or more digits are not allowed. Unsigned LARGEINT is not allowed. Cause. Stated in the error message. Effect. The compilation fails. Recovery. Re-declare the item as signed and recompile.
SQL Compiler Parser Messages (3000 to 3999) SQL 3005 3005 A date-time literal must be specified in Greenwich Mean Time and qualified with the AT GMT clause. Cause. A date-time literal was required to be specified in Greenwich mean time, and the literal was specified without the AT GMT clause. Effect. The statement fails. Recovery. Convert the date-time literal to Greenwich mean time and add the AT GMT clause. SQL 3006 3006 Invalid security string. Cause.
SQL Compiler Parser Messages (3000 to 3999) Recovery. Correct the extent size and reissue the statement. SQL 3008 3008 Secondary extent size is out of range. Cause. You specified an invalid secondary extent size.
SQL Compiler Parser Messages (3000 to 3999) SQL 3011 3011 RECLENGTH value is too small. Cause. You specified a record length that was shorter than the row length. Effect. The statement does not compile. Recovery. Correct the RECLENGTH value and reissue the statement. SQL 3012 3012 An EXECUTE IMMEDIATE statement cannot be used to dynamically compile and execute a GET CATALOG or GET VERSION statement. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3015 3015 Syntax error. Cause. The SQL statement syntax is not correct. Effect. The statement does not compile. Recovery. Check the syntax. If you have access to SQLCI, you can display syntax by using the HELP command. SQL 3016 3016 Syntax error or reserved word. Cause. The SQL statement syntax is not correct, or a reserved word was used as a user-defined name. Effect. The statement does not compile. Recovery.
SQL Compiler Parser Messages (3000 to 3999) SQL 3019 3019 Missing parenthesis. Cause. The right parenthesis is missing. Effect. The statement does not compile. Recovery. Add the missing right parenthesis and recompile. SQL 3020 3020 This file attribute is not allowed with this SQL statement. Cause. The file attribute specified in the SQL statement is not allowed. Effect. The statement does not compile. Recovery. Remove the file attribute and recompile. SQL 3021 3021 Invalid value for SYNCDEPTH. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3023 3023 Key specifier can be either a 2-character string literal or a numeric literal with an integer value from 1 through 65535. Cause. The key specifier is invalid. Effect. The statement does not compile. Recovery. Correct the key specifier value and recompile. SQL 3024 3024 Invalid format in date-time string. Cause. The date-time format is not correct. Effect. The statement does not compile. Recovery. Correct the date-time format and recompile.
SQL Compiler Parser Messages (3000 to 3999) SQL 3027 3027 SQL identifiers, host variables, and parameter names cannot exceed 30 characters. Cause. The supplied SQL identifier, host variable, or parameter name is greater than 30 characters in length. Effect. The statement does not compile. Recovery. Shorten the SQL identifier, host variable, or parameter name, and recompile. SQL 3028 3028 The column requires a default value. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3031 3031 Invalid BLOCKSIZE value. Cause. You specified an invalid BLOCKSIZE value. Effect. The statement does not compile. Recovery. Specify a valid BLOCKSIZE and recompile. SQL 3032 3032 A numeric constant is required here. Cause. The SQL parser required a numeric constant. Effect. The statement does not compile. Recovery. Specify a numeric constant and recompile. SQL 3033 3033 A literal string is required here. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3035 3035 The COLLATE clause can only be specified for columns and expressions that have a character data type. Cause. You specified the COLLATE clause for a column or expression that does not have a character data type. Effect. The statement does not compile. Recovery. Remove the COLLATE clause, or correct the column or expression, and recompile.
SQL Compiler Parser Messages (3000 to 3999) SQL 3038 3038 Literal string length must not exceed column length. Cause. The number of characters in the default string for a column exceeds the length of the column. Effect. The statement does not compile. Recovery. Specify a default string that does not exceed the length of the column, and recompile. SQL 3039 3039 A literal string of up to 8 bytes is allowed. Cause. You specified a string that exceeds the maximum length allowed for a default string.
SQL Compiler Parser Messages (3000 to 3999) SQL 3042 3042 Cannot specify more than one access clause. These clauses are BROWSE ACCESS, STABLE ACCESS, or REPEATABLE ACCESS. Cause. The statement can include only one access clause. Effect. The statement does not compile. Recovery. Choose one of the access clauses, remove the others, and recompile. SQL 3043 3043 Cannot specify APPEND and ANYWHERE clauses at the same time. Cause. A single SELECT statement cannot include both the APPEND and ANYWHERE clauses.
SQL Compiler Parser Messages (3000 to 3999) SQL 3046 3046 Invalid logical DEFINE name. Cause. The DEFINE name is not syntactically valid. Effect. The statement does not compile. Recovery. Specify a valid DEFINE name and recompile. SQL 3047 3047 A volume name cannot exceed six characters, excluding the dollar sign ($). Cause. You specified a volume name that contains more than six characters, not including the dollar sign. Effect. The statement does not compile. Recovery.
SQL Compiler Parser Messages (3000 to 3999) SQL 3050 3050 [NO] VALID DEF[INITION] attribute is not allowed in the ALTER VIEW statement. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Remove the [NO] VALID DEF[INITION] attribute from the ALTER VIEW statement and recompile. SQL 3051 3051 The number of blocks to be sampled must be in the range 1 to 2147483647. Cause. An illegal value is specified for the number of blocks. Effect.
SQL Compiler Parser Messages (3000 to 3999) SQL 3054 3054 Invalid catalog name. Cause. The catalog name is not in the form: [\node.][$volume.]subvol Effect. The statement does not compile. Recovery. Specify a valid catalog name. SQL 3055 3055 The INTO clause is required. Cause. The INTO clause is missing from the statement. Effect. The statement does not compile. Recovery. Specify an INTO clause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3058 3058 BROWSE ACCESS cannot be specified for this SQL statement. Cause. In some SQL statements where STABLE or REPEATABLE ACCESS can be specified, BROWSE ACCESS is not allowed. For example, in a cursor declaration (DECLARE CURSOR statement), if you include a FOR UPDATE clause you cannot specify the BROWSE ACCESS option in the SELECT statement that defines the cursor. Effect. The statement does not compile. Recovery. Remove the BROWSE ACCESS clause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3062 3062 The PROGID attribute is not allowed in this ALTER statement. Cause. The PROGID attribute is not allowed in this form of the ALTER statement. The PROGID attribute is allowed only in an ALTER PROGRAM statement, and only if you do not specify the OWNER attribute. You can, however, specify NO PROGID and OWNER in the statement. Effect. The statement does not compile. Recovery. Either change the form of the ALTER statement, or remove the PROGID attribute.
SQL Compiler Parser Messages (3000 to 3999) SQL 3066 3066 The length of a character data type must be greater than 0 (zero). Cause. You specified a length of 0 (zero) for a character data type. Effect. The statement does not compile. Recovery. Correct the data type description by specifying a length greater than 0 (zero), and recompile. SQL 3067 3067 A parameter name was specified, but a host variable name is required. Cause. Stated in the error message. Effect. The statement does not compile. Recovery.
SQL Compiler Parser Messages (3000 to 3999) SQL 3070 3070 You cannot specify RETURN IF LOCKED and WAIT IF LOCKED in the same SQL statement. Cause. You specified RETURN IF LOCKED and WAIT IF LOCKED in the same SQL statement. Effect. The statement does not compile. Recovery. Choose one option, remove the other, and recompile. SQL 3071 3071 You cannot specify SKIP UNAVAILABLE PARTITION and STOP AT UNAVAILABLE PARTITION in the same SQL statement. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3074 3074 You cannot specify COUNT when ALL is specified. Cause. You specified the COUNT function and the ALL option. Effect. The statement does not compile. Recovery. Remove the ALL option when you specify the COUNT function, and recompile. SQL 3075 3075 You cannot specify a WHERE search condition and a WHERE CURRENT OF cursor name in the same DELETE or UPDATE statement. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3078 3078 Missing column or key. Cause. SQL/MP expected a column definition or PRIMARY KEY clause, but none was specified. Effect. The statement does not compile. Recovery. Include a column definition or PRIMARY KEY clause, and reissue the statement. SQL 3081 3081 The specified scale is more than the maximum allowed. Cause. Cause. You specified a scale with the SETSCALE function that is larger than the size of the variable. Effect. The statement fails.
SQL Compiler Parser Messages (3000 to 3999) SQL 3084 3084 The slack percentage must be an integer in the range from 0 to 99. Cause. You specified a slack percentage greater than 99 or less than 0. Effect. The statement fails. Recovery. Change the slack percentage to an integer in the range from 0 to 99, and reissue the statement. SQL 3085 3085 The SLACK clause cannot be specified with the DSLACK or ISLACK clause. Cause. You specified the SLACK clause with the DSLACK or ISLACK clause. Effect.
SQL Compiler Parser Messages (3000 to 3999) SQL 3091 3091 Dynamic COMMIT WORK is not allowed. Cause. The PREPARE statement contained a COMMIT WORK statement. Effect. The statement fails. Recovery. Do not prepare a COMMIT WORK statement. SQL 3092 3092 Dynamic BEGIN WORK is not allowed. Cause. The PREPARE statement contained a BEGIN WORK statement. Effect. The statement fails. Recovery. Do not prepare a BEGIN WORK statement. SQL 3093 3093 Dynamic ROLLBACK WORK is not allowed. Cause.
SQL Compiler Parser Messages (3000 to 3999) SQL 3095 3095 Invalid INTERVAL format. Cause. You specified an INTERVAL literal with invalid syntax. Effect. The statement fails. Recovery. Correct the syntax error and reissue the statement. SQL 3096 3096 INTERVAL value is out of range. Cause. The INTERVAL value was out of range either because the maximum limit was exceeded or because the precision specified was larger than it should be.
SQL Compiler Parser Messages (3000 to 3999) SQL 3099 3099 The fields are in the wrong order for a DATETIME or INTERVAL specification. Cause. The ordinal position of the start field must precede or equal the ordinal position of the end field. The implied order of the fields is YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, FRACTION. Effect. The statement fails. Recovery. Check the start and end values. One possible solution is to exchange the start and end fields, if they were specified in reverse order.
SQL Compiler Parser Messages (3000 to 3999) SQL 3104 3104 A CLUSTERING KEY clause and a PRIMARY KEY clause cannot appear in the same CREATE TABLE statement. Cause. You specified both a PRIMARY KEY and a CLUSTERING KEY clause in the CREATE TABLE statement. Effect. The statement fails. Recovery. Specify either a PRIMARY KEY clause or a CLUSTERING KEY clause in the CREATE TABLE statement; determine which key is appropriate for the table and remove the other clause. Reissue the statement.
SQL Compiler Parser Messages (3000 to 3999) SQL 3108 3108 Help text cannot exceed 132 characters. Cause. You specified a help text string that had more than 132 bytes. Effect. The statement fails. Recovery. Specify a string with 132 or fewer bytes. SQL 3109 3109 Help text is more than 77 characters. Cause. You specified a help text string that had more than 77 bytes. Effect. The SQL compilation continues. Recovery. Informational message only; no corrective action is needed.
SQL Compiler Parser Messages (3000 to 3999) SQL 3112 3112 The default date-time (DATE, TIME, TIMESTAMP, DATETIME) or INTERVAL value specified for the column must have the same precision as the column. Cause. You specified a date-time or INTERVAL literal as a default value for a column, but the value does not have the same precision as the column. That is, the range of date-time fields, the leading precision, or the fraction precision was different. Effect. The statement fails. Recovery.
SQL Compiler Parser Messages (3000 to 3999) SQL 3118 3118 JOIN SEQUENCE value must be greater than 0. Cause. You specified an invalid value for JOIN SEQUENCE. The value must be greater than 0. Effect. The statement does not compile. Recovery. Correct the JOIN SEQUENCE value and reissue the statement. SQL 3119 3119 You cannot specify MDAM options with CONTROL TABLE *. MDAM options must be associated with a specific table. Cause. You specified MDAM options with CONTROL TABLE *. Effect.
SQL Compiler Parser Messages (3000 to 3999) SQL 3301 3301 Invalid version number. Cause. You specified a version number that is not one of the SQL/MP versions supported by this version of SQL/MP software. Effect. The statement does not compile. Recovery. Specify a valid version number. SQL 3302 3302 UPSHIFT is not allowed on a multibyte character type column. Cause.
6 SQL Compiler Binder Messages (4000 to 4999) SQL 4002 4002 Column value-1 could not be found. Cause. The specified column was not found in any table in the FROM clause or in any table of an outer query FROM clause. Either the column name is misspelled, or the table containing the column is not specified in the query at the level of the error or in any outer query. Effect. The statement does not compile. Recovery. Check the column names of the tables that can apply at the level of the error.
SQL Compiler Binder Messages (4000 to 4999) SQL 4006 4006 value-1 is a duplicate column name. Cause. You specified a column name more than once for a unique column list, and SQL/MP requires that this list contain unique column names only. Effect. The statement does not compile. Recovery. Rename the duplicate column or remove the duplicate column from the SQL statement. SQL 4007 4007 Correlation name value-1 could not be found. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4012 4012 Column number reference value-1 is out of range. Cause. A specified column number referring to the select list was either less than 1 or greater than the number of columns in the select list. Effect. The statement does not compile. Recovery. Specify the correct column number for the column reference in the select list. SQL 4013 4013 Logical name value-1 could not be resolved. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4018 4018 A protection view or cursor definition used for update cannot contain a join. Cause. You specified a protection view or defined a cursor used for update that contains a join. Effect. The statement does not compile. Recovery. Remove the join. SQL 4019 4019 The DISTINCT keyword cannot be specified in a CREATE VIEW statement or in a DECLARE CURSOR statement with the FOR UPDATE clause. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4021 4021 A protection view definition cannot contain expressions in the select list. Cause. You specified a CREATE PROTECTION VIEW or DECLARE CURSOR statement with the FOR UPDATE clause, but the defining query expression contained expressions in the select list. A query expression with expressions in the select list cannot be updated; therefore, you cannot use the expression to define a protection view or a cursor that can be updated. Effect.
SQL Compiler Binder Messages (4000 to 4999) SQL 4024 4024 The view column list and the select column list have a different number of elements. Cause. A CREATE VIEW statement contained a column list with a different number of columns than elements in the select list in the defining query expression. If you want to specify new names for the columns in the view, the statement must supply a name for each column or expression in the select list. Effect. The statement fails. Recovery.
SQL Compiler Binder Messages (4000 to 4999) SQL 4029 4029 A column name must be provided for a view expression column. Cause. The select list of the query expression defining a view contained an expression, and no name was specified in the column list of the CREATE VIEW statement. If the column list was omitted, the names of the columns in the select list were used. If the select list contained an expression, however, no name could be derived. Effect. The statement does not compile. Recovery.
SQL Compiler Binder Messages (4000 to 4999) SQL 4032 4032 Object value-1 is not an SQL view. Cause. The statement required the name of an SQL view. The specified object referred to an existing SQL object that was not a view, such as a table or index. You might be trying an operation that is not allowed on the object type; for example, DROP VIEW. Effect. The statement does not compile. Recovery. Check the specified object name for correctness. Check the semantics of the SQL statement.
SQL Compiler Binder Messages (4000 to 4999) SQL 4035 4035 Key column value-1 is not in the list of columns defined for the table. Cause. In a CREATE TABLE statement, the PRIMARY KEY or CLUSTERING KEY clause included a column that did not appear in the list of columns for the table. The key column was either misspelled or omitted from the columns in the table's definition. Effect. The statement fails. Recovery. Specify the key columns from the column list for the table.
SQL Compiler Binder Messages (4000 to 4999) SQL 4039 4039 This operation cannot be performed on a shorthand view. Cause. An attempt was made to INSERT, DELETE, or UPDATE a shorthand view. A view must be a protection view to permit these operations. Effect. The statement does not compile. Recovery. If the query expression defining the view is valid for a protection view, recreate the view as a protection view and use the protection view. Updating a shorthand view is not allowed.
SQL Compiler Binder Messages (4000 to 4999) SQL 4042 4042 Internal error: SQL BINDER. Cause. Internal error: Stated in the error message. Effect. The statement does not compile. Recovery. Try the operation again. If the problem persists, report the entire message to your service provider. SQL 4043 4043 value-1 contains a 7-character volume name or is on an unnamed system. Cause. The indicated SQL object name had a 7-character volume name or was on a node that was not named.
SQL Compiler Binder Messages (4000 to 4999) SQL 4045 4045 Column value-1 cannot assume a default value. Cause. The INSERT statement did not supply a value for the indicated column. The column was defined with the NO DEFAULT option; therefore, the INSERT statement must supply a value for the column. Effect. The statement does not compile. Recovery. Supply a value for all columns in the table or view that were defined with the NO DEFAULT option. You can query the COLUMNS catalog table for this information.
SQL Compiler Binder Messages (4000 to 4999) SQL 4048 4048 The ANYWHERE clause is not allowed for this table type. Cause. An INSERT statement included an ANYWHERE clause for a key-sequenced or entry-sequenced table. The ANYWHERE clause applies only to relative tables; it indicates where to put inserted rows. Effect. The statement does not compile. Recovery. Remove the ANYWHERE clause from the INSERT statement. SQL 4049 4049 The DELETE operation cannot be used on an entrysequenced table. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4051 4051 A value for the system-defined primary key column (SYSKEY by default) must be provided. Cause. An INSERT operation was attempted on a protection view whose definition referred to the system-defined primary key column and whose underlying table had relative organization.
SQL Compiler Binder Messages (4000 to 4999) SQL 4054 4054 A constraint definition cannot refer to SYSKEY. Cause. A CREATE CONSTRAINT statement referred to the SYSKEY column in the defining predicate. Because SYSKEY is a system-generated value, this constraint would prevent normal insertions. Effect. The statement fails. Recovery. Use a placement option (APPEND or ANYWHERE) to control SYSKEY values where appropriate.
SQL Compiler Binder Messages (4000 to 4999) SQL 4057 4057 value-1 is not an SQL compiled program. Cause. The statement requires the name of an SQL compiled program, but the specified object was not a program, or it was not SQL compiled, or the program file was moved or restored. Effect. The statement does not compile. Recovery. SQL compile the program to make it SQL sensitive. SQL 4058 4058 Table value-1 could not be found. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4060 4060 Table or view value-1 could not be found. Cause. The statement required an SQL table or view name, but no SQL table or view with the indicated name existed. Effect. If the message is a warning at compile time, the table or view must exist before the statement executes. The statement is left uncompiled until an attempt is made to recompile it or execute it. Recovery. Create the table or view before executing the statement.
SQL Compiler Binder Messages (4000 to 4999) SQL 4065 4065 The select list and the host variable list have a different number of elements. Cause. The number of elements in the select list was not the same as the number of host variables in the INTO clause. This can occur if you use a SELECT * statement with a table in the FROM clause for which a new column has been added. Effect. The shorter list is used; the extra elements are ignored. Recovery. Informational message only; no corrective action is needed.
SQL Compiler Binder Messages (4000 to 4999) SQL 4068 4068 Table or view value-1 could not be accessed. Cause. The statement required an SQL table or view name. The specified table or view might exist; however, a file system error was encountered when accessing the table or view. See the file system error following this error for the cause. Effect. The statement does not compile. Recovery. Correct the file system error condition. SQL 4069 4069 Index value-1 could not be accessed. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4073 4073 An inconsistency in the creation time of an audited table was detected. Cause. The creation time for this table in your catalog does not agree with the creation time noted in the file label. This problem could be the result of a TMF rollforward recovery operation performed on this table. Do not perform any SQL operations on this table now. Effect. The statement does not compile. Recovery. None. Report the entire message to your service provider.
SQL Compiler Binder Messages (4000 to 4999) SQL 4086 4086 The select list of the UNION operands must have the same number of elements. Cause. The select lists of the left SELECT statements involved in the UNION operation did not have the same number of elements. Effect. The statement does not compile. Recovery. Check that the number of elements is the same in each select list. SQL 4089 4089 The value list of the INSERT statement cannot reference a column. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4094 4094 Only one ORDER BY clause can be specified for the result of a UNION operation, and it must follow the last SELECT statement. Cause. An ORDER BY clause was specified in one or more SELECT statements in the UNION clause. Effect. The statement does not compile. Recovery. Specify only one ORDER BY clause as the last clause following the final SELECT statement after the UNION operator. SQL 4097 4097 A protection view cannot contain a UNION operator.
SQL Compiler Binder Messages (4000 to 4999) SQL 4100 4100 System name and volume name of the old name, value-1, and new name, value-2, must be the same. Cause. You specified an ALTER... RENAME command, and the system and volume names of the old name and new name did not match. For example: ALTER TABLE \SYS1.$A.B.T RENAME \SYS2.$A.B.T Effect. The statement fails. Recovery. Correct the error.
SQL Compiler Binder Messages (4000 to 4999) SQL 4301 4301 Object value-1 is not a program. Cause. The statement requires the name of a code 100 file. Effect. The statement does not compile. Recovery. Specify the name of a program. SQL 4302 4302 File value-1 is not an SQL collation object. Cause. You specified a statement that requires the name of an SQL collation object, but the file is not an SQL collation object. Effect. The statement does not compile. Recovery.
SQL Compiler Binder Messages (4000 to 4999) SQL 4305 4305 Catalog table value-1 could not be accessed. Cause. The specified catalog table might exist; however, a file system error occurred when the table was accessed. See the file system error following this error for the cause. Effect. The statement does not compile. Recovery. Correct the file system error condition. SQL 4306 4306 Program value-1 could not be accessed. Cause. See the accompanying file system error. Effect. The statement does not compile.
SQL Compiler Binder Messages (4000 to 4999) SQL 4309 4309 Object value-1 is on a version value-2 system, but this operation requires the system to be at least version value-3. Cause. The version of the remote node is less than the minimum version required for this operation. Effect. The statement does not compile. Recovery. Upgrade the SQL/MP software on the remote node. SQL 4310 4310 The character set of the column value-1 does not match the character set of the collation that is specified for it. Cause.
SQL Compiler Binder Messages (4000 to 4999) SQL 4313 4313 Catalog value-1 is a version value-2 catalog, but this operation requires the catalog to be at least version value3. Cause. The version of the catalog is less than the minimum version required for this operation. Effect. The statement does not compile. Recovery. Upgrade the catalog. SQL 4314 4314 Catalog value-1 could not be found. Cause. The statement required an SQL catalog name, but no SQL catalog with the indicated name existed. Effect.
SQL Compiler Binder Messages (4000 to 4999) SQL 4321 4321 value-1 does not belong to the index that is being altered. Cause. The partition specified in the DROP PARTITION clause of the ALTER INDEX statement did not belong to the index. Effect. The statement does not compile. Recovery. Specify the name of a partition that belongs to the index and reissue the statement. SQL 4322 4322 Object value-1 is not a logical filename or a direct filename. Cause.
7 SQL Compiler Normalizer Messages (5000 to 5999) SQL 5001 5001 Aggregate function in argument of aggregate function. Cause. An aggregate function cannot have an aggregate function as an argument. For example, MAX(AVG (salary)) is invalid. Effect. The statement does not compile. Recovery. Correct the argument and recompile. SQL 5002 5002 Cursor could not be used for update because of one of these reasons: 1) It involves a join. 2) It has a GROUP BY clause, ORDER BY clause, or aggregate functions.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5004 5004 The SELECT statement is grouped, either because it has a GROUP BY clause or because it contains an aggregate function. A column in the select list that is not a GROUP BY column can only appear in the argument of an aggregate function. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the SELECT statement and recompile. SQL 5007 5007 Values cannot be selected from and inserted into the same table.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5010 5010 Column list or value list is empty. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement by specifying a column or value list, and recompile. SQL 5011 5011 Column list and value list do not have the same length. Cause. There must be a one-to-one correspondence between the items in the column list and the items in the value list. Effect. The statement does not compile. Recovery.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5014 5014 A FROM clause that refers to a grouped view cannot refer to any additional tables or views. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement and recompile. SQL 5015 5015 An aggregate function cannot appear in an update set expression. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement and recompile.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5018 5018 A subquery select list must contain only one expression. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the subquery select list and recompile. SQL 5019 5019 A SELECT statement that is grouped cannot refer to a view that is grouped. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement and recompile.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5022 5022 If a SELECT statement refers to a grouped view in the FROM clause, the SELECT statement cannot include any function on columns of that view in the select list. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement and recompile.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5026 5026 For a SELECT DISTINCT statement, the ORDER BY list can refer only to columns that appear in the select list. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Correct the statement and recompile.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5029 5029 A shorthand view whose definition contains an outer join operation cannot participate in an outer join with another table or view. Cause. The SQL compiler does not allow an outer join on a shorthand view whose definition also contains an outer join operation. Effect. The statement does not compile. Recovery. Remove the unsupported operation from the query.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5032 5032 The ORDER BY clause for a union of SELECT statements can only reference a column from the select list of the first SELECT statement. The column must be specified independently in that select list. If the column is specified as the argument of a function or as a part of an expression, but is not specified independently, then the column cannot be specified in the ORDER BY clause. Cause.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5034 5034 The ORDER BY clause for a union of SELECT statements can only reference a column from the select list of the first SELECT statement. If the same column name appears more than once in that select list, then the SQL compiler cannot decide which instance of the column to use for ordering rows; the column references are ambiguous. Cause.
SQL Compiler Normalizer Messages (5000 to 5999) SQL 5102 5102 A subquery cannot contain an ORDER BY clause. Cause. An ORDER BY clause was specified in a subquery block. Effect. The statement does not compile. Recovery. Specify only one ORDER BY clause as the last clause of the outermost SELECT statement. SQL 5103 5103 A non-column as argument of aggregate function, possibly after view expansion. Cause. You specified an aggregate function with a non-column as argument.
SQL Compiler Normalizer Messages (5000 to 5999) HP NonStop SQL/MP Messages Manual—427720-006 7- 12
8 SQL Compiler Optimizer Messages (6000 to 6999) SQL 6001 6001 Duplicate column in the update list. Cause. You specified the same column more than once in the list of columns to be updated. Effect. The statement does not compile. Recovery. Remove the duplicate column, and reissue the statement. SQL 6002 6002 More than 16 levels of nesting have been specified in a query. Cause. You cannot have more than 16 levels of query nesting specified in a query. Effect. The statement does not compile. Recovery.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6004 6004 The filename value specified for the define value-1 is incorrectly formatted. Cause. The user did not specify the filename according to the correct syntax for this define. Effect. The statement fails. Recovery. Add the define with a new filename value, specifying the correct syntax. SQL 6005 6005 A subquery may not appear within a SELECT list expression. Cause. You specified a subquery within a SELECT list expression. Effect.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6008 6008 Statistics or partitions for a table were not available so the access path chosen might not be the best available. Cause. Statistics on a table were not available during the compilation of a query. Effect. The access path chosen by the SQL compiler might not be the most efficient. Recovery. Issue the UPDATE STATISTICS command for all tables referred to by the query, and reissue the query.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6013 6013 You cannot specify a function in a WHERE clause unless all the columns in the function refer to outer tables. Cause. A function containing local column references was specified in a WHERE clause. Effect. The statement does not compile. Recovery. Move the function containing local column references to the HAVING clause, and reissue the statement. SQL 6014 6014 More than 16 tables are specified in the FROM clause of a query or subquery. Cause.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6016 6016 The current query requires one or more sorts, and no suitable disk volume exists to store the result of a sort on the current system. Cause. The optimizer attempted to sort a table on another node, and tried to choose a disk on the current node to hold the result of the sort. It can choose only an audited disk that is not $SYSTEM. No such disk exists on the current node. Effect. The statement does not compile. Recovery.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6020 6020 The CONTROL TABLE directives specified a set of JOIN SEQUENCE values that are not consistent with the query. Cause. The CONTROL TABLE directives specified join sequence values that cannot be used with this query. Effect. The statement fails. Recovery. Use CONTROL TABLE * JOIN SEQUENCE SYSTEM. Remove the CONTROL TABLE directives specifying JOIN SEQUENCE.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6023 6023 The CONTROL TABLE directives specified an access path that would cause the "Halloween update" problem. This index cannot be used for the update because it might cause rows to be updated to incorrect values. Cause. The CONTROL TABLE directives specified an index that cannot be used for this update query. Effect. The statement fails. Recovery. Use CONTROL TABLE * ACCESS PATH SYSTEM.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6026 6026 A CONTROL TABLE directive specified MDAM ON for a table when a CONTROL QUERY MDAM OFF directive was in effect. Cause. The CONTROL TABLE directive specifying MDAM ON for a table cannot be enforced if CONTROL QUERY sets MDAM OFF. Effect. The statement fails. Recovery. Use either the CONTROL TABLE directive with MDAM ON for the table or the CONTROL QUERY MDAM OFF, but not both.
SQL Compiler Optimizer Messages (6000 to 6999) SQL 6104 6104 The query may fail during execution if the size of the overflow files created for the relations in the Hybrid Hash join are greater than 1.5 GB. Cause. The CONTROL TABLE directive specified JOIN METHOD HASH. Statistics indicate that the overflow file size for inner or outer relation will be more than the limit of 1.5 GB. Effect. A warning is issued and the statement is compiled.
SQL Compiler Optimizer Messages (6000 to 6999) HP NonStop SQL/MP Messages Manual—427720-006 8- 10
9 SQL Compiler Generator Messages (7000 to 7999) SQL 7001 7001 The SQL Type Propagator detected an inconsistent internal data structure. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. None. Report the entire message to your service provider. SQL 7002 7002 The CASE statement has an invalid format. Cause. If a CASE operand is used, the WHEN clause cannot contain a relational operation. If a CASE operand is not used, the WHEN clause must have a relational operation.
SQL Compiler Generator Messages (7000 to 7999) SQL 7004 7004 The results of the CASE expression have incompatible data types value-1 and value-2. Cause. The results of the CASE expression have different and incompatible data types. Effect. The statement does not compile. Recovery. Check that the results have compatible data types. SQL 7005 7005 The results of the CASE expression have incompatible collations. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7010 7010 The numeric value or column used in this expression is either not exact or it does not have a scale of zero (0). Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Check that the numeric value or column used is exact with a scale of 0. SQL 7011 7011 The two date-time (DATE, TIME, TIMESTAMP, or DATETIME) operands in this arithmetic or relational expression do not have the same range of DATETIME fields. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7013 7013 The range of INTERVAL fields is not compatible with the INTERVAL value expression. Cause. The range of INTERVAL fields did not belong to the same INTERVAL class as the INTERVAL value expression. Effect. The statement does not compile. Recovery. Make the range of INTERVAL fields compatible with the INTERVAL value expression.
SQL Compiler Generator Messages (7000 to 7999) SQL 7016 7016 The expression contains an element or elements that must be converted to local civil time before being evaluated. Such expressions are not allowed in a constraint or protection view. Cause. Stated in the error message. Effect. The constraint or protection view is not created. Recovery. Check that an element that needs a date-time value in local civil time was not used in a constraint or protection view expression.
SQL Compiler Generator Messages (7000 to 7999) SQL 7030 7030 The operand of the CONVERTTIMESTAMP function must have a LARGEINT data type (binary 64) with a scale of zero. Cause. The operand of the CONVERTTIMESTAMP function was not declared to have a LARGEINT data type with a scale of zero. Effect. The statement does not compile. Recovery. Check that the operand is declared with a LARGEINT data type and a scale of zero.
SQL Compiler Generator Messages (7000 to 7999) SQL 7054 7054 The source character set value-1 and the target character set value-2 of the CAST function are incompatible. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Check that the source and target have the same character sets. SQL 7055 7055 The CAST function is not allowed between a multibyte data type and a noncharacter data type. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7100 7100 Comparisons between value-1 and value-2 data types are not allowed. Cause. You attempted a comparison between incompatible data types in a relational, LIKE, IN or BETWEEN predicate. For example, you cannot compare a numeric value and a character value. Effect. The statement does not compile. Recovery. Check the data types of the operands of the predicate, and correct those that are incompatible.
SQL Compiler Generator Messages (7000 to 7999) SQL 7103 7103 The data type of the host variable value-1 is not compatible with the value-2 data type of the corresponding SELECT list entry. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Use a host variable whose data type is compatible with that of the select list entry. SQL 7110 7110 Comparisons between value-1 and value-2 character sets are not allowed. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7112 7112 The character sets of the operands value-1 and value-2 of the corresponding elements of the SELECT list union operation are not compatible. Cause. The select lists of the left SELECT statements have incompatible character sets. Effect. The statement does not compile. Recovery. Make sure that the corresponding elements have the same character sets.
SQL Compiler Generator Messages (7000 to 7999) SQL 7118 7118 The collation specified on the SELECT list index in the GROUP BY or ORDER BY clause is not compatible with the collation specified on the corresponding select list entry. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. Check that the two collations do not result in a collation that conflicts with the result of the operation.
SQL Compiler Generator Messages (7000 to 7999) SQL 7123 7123 A range of DATETIME or INTERVAL fields can be specified only with DATETIME or INTERVAL values. Cause. You specified a range of DATETIME or INTERVAL fields with a numeric expression, a numeric column, or a character column. To specify a range of DATETIME or INTERVAL fields, use DATETIME or INTERVAL values. Effect. The statement does not compile. Recovery. Remove the range of DATETIME or INTERVAL fields.
SQL Compiler Generator Messages (7000 to 7999) SQL 7151 7151 The trim character operand of the TRIM operator is not a character string of length 1. Cause. The length of the trim character operand was not 1. Effect. The statement does not compile. Recovery. Change the operand so its length equals 1 and reissue the request. SQL 7152 7152 The two operands of the value-1 function have incompatible collations. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7170 7170 The data type of the host variable in the INTO clause of a GET VERSION statement must be numeric. Cause. You specified a host variable that did not have a numeric data type. Effect. The statement does not compile. Recovery. Check the data type of the host variable in the INTO clause. SQL 7171 7171 The host variable in the INTO clause of a GET CATALOG statement must have a character data type with a single-byte character set. Cause.
SQL Compiler Generator Messages (7000 to 7999) SQL 7499 7499 This is a place-holder error message. An actual error message has not yet been assigned. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. None. Report the entire message to your service provider. SQL 7501 7501 The SQL compiler generator detected an inconsistent internal data structure. Cause. Stated in the error message. Effect. The statement does not compile. Recovery. None.
SQL Compiler Generator Messages (7000 to 7999) SQL 7504 7504 Statement size and complexity are beyond the capacity of the present version of the SQL compiler generator. Cause. An internal structure or variable reached the limit of its capacity. The query is too large or complex. Effect. The statement does not compile. Recovery. Simplify the query or divide it into smaller steps. If the query uses a shorthand view, consider whether the view definition can be simplified.
10 SQL Executor Messages (8000 to 8999) SQL 8001 8001 Failure in ALLOCATESEGMENT. Cause. The ALLOCATESEGMENT procedure could not allocate the extended segment for the SQL executor. Effect. The statement or program fails. Recovery. Reissue the statement or rerun the program. If the problem persists, contact your system administrator. SQL 8002 8002 Internal error: Failure in USESEGMENT. Cause. Internal error: The USESEGMENT procedure could not bring the extended segment for the SQL executor into use.
SQL Executor Messages (8000 to 8999) SQL 8004 8004 The system does not support execution of non-Tandem SQL applications. Cause. SQL Runtime license has not been installed on this system. Effect. The program Execution terminates. Recovery. Purchase the All-Applications SQL Runtime license and install it on the system before you attempt to execute the program. SQL 8005 8005 The CONTROL EXECUTOR directive specified PARALLEL EXECUTION ON for a query in which parallel execution could not be enabled. Cause.
SQL Executor Messages (8000 to 8999) SQL 8011 8011 Cannot allocate a contiguous section of value-1 bytes in the SQL executor pool because the maximum is 131064 bytes at a time. Cause. The program exceeded the maximum contiguous space in the SQL executor pool that is supported by GETPOOL. Effect. The statement fails. Recovery. Rerun the program, or shorten the program and then rerun it. If the error persists, report the entire message to your service provider.
SQL Executor Messages (8000 to 8999) SQL 8014 8014 Internal error: Unable to resize the SQL executor pool after increasing the size of SQL executor's extended segment to value-1 bytes. Cause. Internal error: The SQL executor failed to resize the SQL executor pool after RESIZESEGMENT resized the SQL executor segment. A call to the procedure RESIZEPOOL failed. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8015 8015 Internal error: pool is corrupted.
SQL Executor Messages (8000 to 8999) SQL 8022 8022 The SQL object has an invalid version number. Cause. The SQL object was compiled with a compiler that was incompatible with the system on which the program was executed. Effect. The SQL object is not loaded, and the program fails. Recovery. Compile your program again with a compiler that is compatible with the software that will run the program. SQL 8023 8023 The SQL region is missing in the program file. Cause.
SQL Executor Messages (8000 to 8999) SQL 8026 8026 Your SQL program needed to be recompiled but had the NORECOMPILE option set. Cause. Either the program was marked invalid or the run time DEFINEs were different than the compile time DEFINEs, and the program was SQL compiled with the NORECOMPILE option. Effect. The program fails. Recovery. SQL compile and rerun the program. SQL 8027 8027 The SQL statement needed to be recompiled but the program had the NORECOMPILE option set. Cause.
SQL Executor Messages (8000 to 8999) SQL 8030 8030 SQL statement has an invalid object. Cause. The program corrupted the program file, or invalid code was generated for the statement. Effect. The statement fails. Recovery. Compile the program again. If the problem persists, report the entire message to your service provider. SQL 8031 8031 Statement must be prepared. Cause. You did not prepare the statement before attempting to execute it. Effect. The statement fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8041 8041 Unable to communicate with the SQL compiler process. Cause. An SQL compiler process could not be started as a new process, or the compiler failed while compiling a PREPARE statement or while dynamically recompiling a DML statement. Effect. The DML statement fails. If a user-defined TMF transaction was present and the failure occurred before the DML operation completed, the user-defined TMF transaction terminates abnormally. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8044 8044 Only local system version information can be requested. Remote system version information cannot be requested. Cause. In the C10 version of SQL/MP, an application cannot request remote system version information. Effect. The statement fails. Recovery. Request information about a local system version only. SQL 8100 8100 Invalid SQLIN address or content. Cause. The program passed an invalid SQLIN variable.
SQL Executor Messages (8000 to 8999) SQL 8102 8102 Invalid SLT-INDEX in SQLIN. Cause. The program passed an invalid SQLIN. Either the program is corrupted, or an invalid SQLIN was generated at preprocessing time. Effect. The statement fails. Recovery. Preprocess (SQL COBOL programs only), host-language compile, SQL compile, and execute your program again. If you are using SQLCI, report the entire message to your service provider. SQL 8103 8103 Invalid opcode in SQLIN. Cause.
SQL Executor Messages (8000 to 8999) SQL 8110 8110 Invalid pointer to IVARS, invalid IVARS, or IVARS missing but required. Cause. The program passed an invalid SQLIN. Either the program is corrupted, or an invalid SQLIN was generated at preprocessing time. This error can occur if the process you used for SQL processing is a version that is incompatible with the SQL compiler or executor.
SQL Executor Messages (8000 to 8999) SQL 8113 8113 The SQLDA used in a DESCRIBE call has more entries than necessary. Cause. The SQLDA for receiving the select items had more entries than the number of select items to be returned by the statement. Effect. Only the appropriate number of select items are returned. Recovery. No recovery is necessary. SQL 8114 8114 Invalid pointer to OVARS, invalid OVARS, or OVARS missing but required. Cause. The user program was corrupted. Effect. The statement fails.
SQL Executor Messages (8000 to 8999) SQL 8116 8116 Invalid reference to a cursor was made, or the specified (foreign) cursor could not be located in the program where the cursor was declared. Cause. Either the program is corrupted, or the program name qualifying the cursor name is not correct. Effect. The statement fails. Recovery. Check that the cursor references are correct. Preprocess (SQL COBOL program only), host-language compile, SQL compile, and execute your program again.
SQL Executor Messages (8000 to 8999) SQL 8121 8121 Invalid pointer to SQLSA or invalid SQLSA content. Cause. Your program is corrupted. Effect. The SQLSA will have undefined values. Recovery. None. Report the entire message to your service provider. SQL 8122 8122 There is an invalid pointer to name map, an invalid name map, or a required name map that is missing. Cause. Your program is corrupted. Effect. The program fails. Recovery. None. Report the entire message to your service provider.
SQL Executor Messages (8000 to 8999) SQL 8202 8202 Because of a label timestamp mismatch on file value-1, automatic recompilation will be attempted, if allowed. Cause. An object's definition changed since the statement was last SQL compiled. SQL/MP attempted to recompile the statement. Effect. The statement succeeds if the recompilation succeeds, else the SQLCA will have an appropriate error message. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8205 8205 Error in deallocating space of a temporary table. Cause. The system failed to purge data of a temporary table. See the SQLCA for the error returned by the file system. Effect. The statement fails. Recovery. Check the file system error in the SQLCA to determine the cause. The program can display the file system error by using the SQLCADISPLAY procedure described in the SQL/MP programming manual for the host language in which the program is written.
SQL Executor Messages (8000 to 8999) SQL 8208 8208 The program was dynamically recompiled because it was started with a set of DEFINEs that is different from the DEFINEs used at SQL compilation time. Cause. Stated in the error message. Effect. The first execution of an SQL statement in the program is delayed while an SQLCOMP process is started to recompile the program. An EMS message is created to record this event. No warning or error is returned to the SQLCA. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8217 8217 The statement being executed requires a cursor. Cause. You tried to EXECUTE a dynamic SELECT statement. Effect. The statement fails. Recovery. Declare a cursor for the prepared SELECT statement, and reissue the statement. SQL 8218 8218 A cursor operation has been attempted on a non-cursor statement. Cause. An OPEN, FETCH or CLOSE operation was attempted on a non-cursor statement.
SQL Executor Messages (8000 to 8999) SQL 8221 8221 Trying to FETCH an unopened cursor. Cause. The FETCH cursor statement was issued for a cursor that was not opened. Effect. The statement fails. Recovery. Open the cursor before reexecuting the FETCH statement. SQL 8222 8222 More than one row would satisfy a SELECT request with an INTO clause or a subquery. Cause. The table or tables had more than one row that satisfied the query, and only one row is allowed. Effect. The statement fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8224 8224 SQL does not generate this error. Your program has overwritten the error field with two blanks. Cause. The program has overwritten the SQLCA with blanks (a blank-filled INT buffer is equivalent to 8224). Effect. The SQLCA is corrupted. Recovery. Resolve this error and rerun the program. SQL 8225 8225 Cursor specified in an UPDATE or a DELETE WHERE CURRENT OF request must not use aggregate functions, GROUP BY clause, joins, or a parallel plan. Cause.
SQL Executor Messages (8000 to 8999) SQL 8227 8227 The row being inserted or updated in underlying table value-1 contains a key value that must be unique but is already present in a row. Cause. Duplicate values for columns requiring unique values are not allowed. Columns require unique values if they are columns of the primary key or columns of a unique index. Effect. The INSERT or UPDATE operation fails. Recovery. Correct the data values.
SQL Executor Messages (8000 to 8999) SQL 8231 8231 Internal error: the EXD. An unexpected EXDC was encountered in Cause. Internal error: The user program was corrupted, or a clause in a compiled expression was corrupted. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8232 8232 File system aborted the current transaction. occurred on value-1. Error code Cause. The file system aborted the transaction. See the file system error to determine the cause.
SQL Executor Messages (8000 to 8999) SQL 8235 8235 Unable to recompile statement. Cause. A file system error occurred. The statement might have referred to an object that did not exist at recompilation time. Effect. The statement fails. Recovery. Display all errors reported in the SQLCA to determine why recompilation failed. The program can display the file system error by using the SQLCADISPLAY procedure described in the SQL/MP programming manual for the host language in which the program is written.
SQL Executor Messages (8000 to 8999) SQL 8238 8238 Error value-1 was returned by the file system during flush of a sequential buffer for insert/update. Cause. The file system could not perform a buffered update or insert operation. To determine the cause, see the supplied file system error code. Effect. The current transaction is aborted. For nonaudited tables, data might be lost. Recovery. Reissue the statement.
SQL Executor Messages (8000 to 8999) SQL 8250 8250 Execution-time table (protection view) value-1 is not similar to compile-time table (protection view) for the following reason: The similarity check is not enabled. Cause. The similarity check failed. The similarity check was not enabled for the execution-time table (protection view). Effect. The statement cannot be executed without recompilation. SQL/MP attempts auto-recompilation. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8253 8253 The compile-time object has a different type than the run-time object. The error occurred on value-1. Cause. The similarity check failed. Effect. The statement cannot be executed without recompilation. SQL/MP attempts auto-recompilation. Recovery. To avoid future auto-recompilation, objects must meet the conditions of the similarity check. SQL 8254 8254 A file system error code was returned while trying to access the file label for value-1. Cause.
SQL Executor Messages (8000 to 8999) SQL 8256 8256 value-1 does not have an index equivalent to the one chosen as the access path at SQL compilation time (KEYTAG value-2). Cause. Stated in the error message. Effect. SQL/MP attempts to recompile the statement. Recovery. SQL compile the program again. Alternatively, create an index equivalent to the index chosen as the access path at SQL compilation time. SQL 8257 8257 Execution-time collation value-1 is not equivalent to the compile-time collation. Cause.
SQL Executor Messages (8000 to 8999) SQL 8259 8259 The execution-time table (protection view) value-1 is not similar to compile-time table (protection view) for the following reason: The number of columns is different. Cause. The similarity check failed. Effect. The statement cannot be executed without recompilation. SQL/MP attempts auto-recompilation. Recovery. The number of columns must be identical for protection views.
SQL Executor Messages (8000 to 8999) SQL 8262 8262 The execution-time table has a different key than the compile-time table. The error occurred on value-1. Cause. The similarity check failed. Effect. The statement cannot be executed without recompilation. SQL/MP attempts auto-recompilation. Recovery. To avoid future auto-recompilation, the compile-time table and the execution-time table must have identical key definitions.
SQL Executor Messages (8000 to 8999) SQL 8301 8301 Sort error encountered on value-1 value-2). (high word error is Cause. A sort operation failed on the indicated file. The high-word error in the message is the file system error number. Effect. The statement fails. Recovery. See the SQLCA for the error returned by FastSort to determine the cause.
SQL Executor Messages (8000 to 8999) SQL 8311 8311 A disk was not available to fetch required data. occurred for value-1. Error Cause. The disk was not operating. Effect. The statement fails. Recovery. Check the availability of the disk. If the problem persists, report the entire message to your service provider. SQL 8312 8312 The statement cannot be executed because no TMF transaction is currently in progress. The error was detected for value-1. Cause.
SQL Executor Messages (8000 to 8999) SQL 8313 8313 The transaction ID is invalid or obsolete. was detected for value-1. The error Cause. The program tried to execute the statement within different transactions, or a transaction was aborted by the system. For example, an application opened a cursor within a given transaction, but fetched from that cursor within a different or aborted transaction. Effect. The statement fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8316 8316 The statement was executed using a transaction ID of a TMF transaction that was aborted. The error was detected for value-1. Cause. You or the system aborted a user-defined transaction. Effect. The statement fails. Recovery. Start a new TMF transaction, and reissue the statement. SQL 8401 8401 Invalid value for a data type was encountered. Cause. Your program was corrupted. Effect. The statement fails. Recovery. SQL compile and run your program again.
SQL Executor Messages (8000 to 8999) SQL 8404 8404 Truncation of a character data value required, but not allowed. Effect. Not all characters could fit in the target buffer. Effect. The statement fails. Recovery. Check your data or data buffers (host variables). If necessary, declare larger host variables. SQL 8405 8405 Decimal data encountered with some nonnumeric digits. Cause. Bad data was supplied for decimal values. Effect. The statement fails. Recovery. Correct the decimal data.
SQL Executor Messages (8000 to 8999) SQL 8408 8408 Division by zero occurred. Cause. The denominator value for division was zero. Effect. The statement fails. Recovery. Correct the statement to remove division by zero. SQL 8409 8409 The program encountered a data type that has not been implemented. Wait for a future version or release. Cause. The data type was not implemented. Effect. The statement fails. Recovery. Do not use this data type. SQL 8410 8410 An invalid value for a data type was encountered.
SQL Executor Messages (8000 to 8999) SQL 8412 8412 Type incompatibility detected between data values of an operation. Cause. Your program was corrupted. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8413 8413 Division was requested in a data type for which the operation is not allowed. Cause. Your program was corrupted. Effect. The statement fails. Recovery. None. Report the entire message to your service provider.
SQL Executor Messages (8000 to 8999) SQL 8416 8416 Invalid pattern or escape clause for LIKE operator. Cause. The pattern or escape clause is invalid. The wild-card characters are the percent sign (%) and the underscore (_). The percent sign indicates zero, and the underscore indicates that any single character is acceptable. Effect. The statement fails. Recovery. Supply a valid pattern or escape clause. SQL 8417 8417 Scale of a numeric data value was truncated. Cause.
SQL Executor Messages (8000 to 8999) SQL 8421 8421 Error encountered during FILEINQUIRE call to determine SQL sensitivity and validity settings of the program file. See the file system error for more information. Cause. Either the program was not SQL compiled or it was invalid. Effect. Program execution fails. Recovery. SQL compile and run the program again. SQL 8422 8422 The value of the percentile number for the PTILE is not in range 1-99. Cause.
SQL Executor Messages (8000 to 8999) SQL 8425 8425 Either an invalid date-time value was entered, or the result of a date-time expression produced an invalid datetime value. Cause. The error message states the cause. Effect. The statement fails. Recovery. Avoid any computation that could result in an invalid date-time value. SQL 8426 8426 Incorrect format for a date-time or INTERVAL value. Cause. The date-time or INTERVAL value contained in the input parameter or the host variable had an incorrect format.
SQL Executor Messages (8000 to 8999) SQL 8429 8429 No entry is available in the DST Transition Table for the entered date-time value. Cause. The DST Transition Table was not updated with this date-time value. Effect. The input value is rejected and the statement fails. Recovery. Update the DST Transition Table with an entry covering this date-time value. The DST Transition Table can be updated by the super ID using the ADDDSTTRANSITION procedure.
SQL Executor Messages (8000 to 8999) SQL 8501 8501 Statement has open cursor. Cause. The statement that was being released, or for which a cursor name was being defined, held a cursor that was open. Effect. The statement fails. Recovery. Close the cursor and reissue the statement. SQL 8502 8502 Cursor name already declared in this procedure. Cause. The cursor name being declared was previously declared for another statement in the same procedure. Effect. The statement fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8511 8511 One of the item codes in the item code list passed to SQLCAGETINFOLIST is invalid. Cause. The item code was less than or equal to zero, or greater than the last valid item code. The ERRORITEM parameter indicates which item code was invalid. Effect. The call fails. Recovery. Replace the invalid item code with a valid code. SQL 8512 8512 The SQLCA passed to SQLCAGETINFOLIST is invalid. Cause. The SQLCA had one or more inconsistencies in its data structures.
SQL Executor Messages (8000 to 8999) SQL 8515 8515 The ERRORINDEX parameter passed to SQLCAGETINFOLIST is invalid. Cause. The value of ERRORINDEX was less than 0, or greater than the maximum number of errors that the SQLCA could hold. Effect. The call fails. Recovery. Pass an ERRORINDEX value in the correct range. SQL 8516 8516 The value of the NAMESMAX parameter passed to SQLCAGETINFOLIST is invalid. Cause. The value of NAMESMAX is less than or equal to zero. Effect. The call fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8601 8601 Incorrect number of request message bytes was received by the Executor Server Process (ESP). Cause. Either the requester executor process sent an incorrect message size while sending the message, or an incorrect number of message bytes was read by the ESP process from its $RECEIVE process. Effect. The statement fails. Recovery. Reissue the statement. A read problem might be intermittent.
SQL Executor Messages (8000 to 8999) SQL 8604 8604 A wrong version of message was exchanged between the requester and server executor processes. Cause. A message was exchanged between incompatible versions of the requester and server executor processes. If the version number of the request message sent to the server process is greater than the largest version number that the server can process, this error is returned.
SQL Executor Messages (8000 to 8999) SQL 8607 8607 A bad message was sent from one executor process to another. Cause. An incorrect number of message bytes was transferred to the receiving executor process, or the message tag was corrupted by the system. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8608 8608 Failed to send a message from one executor process to another. Cause. A call to the WRITEREADX procedure failed. Effect. The statement fails.
SQL Executor Messages (8000 to 8999) SQL 8610 8610 Incorrect return tag was returned with the reply message from the executor server process (ESP). Cause. Either the system corrupted the message tag or the requester process checked for an incorrect message tag. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8611 8611 A required executor server process (ESP) has ceased to exist. Cause. The ESP was no longer running.
SQL Executor Messages (8000 to 8999) SQL 8613 8613 A bad DEFINE: value-1 was set to recommend the initial size to be allocated for the extended segment for Executor Server Processes (ESPs). This DEFINE is not made available to users; it is only for internal testing. This error should not occur for user applications. Cause. A bad DEFINE was set. Effect. The statement fails. Recovery. None. Report the entire message to your service provider.
SQL Executor Messages (8000 to 8999) SQL 8620 8620 An internal error occurred during a hash join or hybrid join. Cause. The program was corrupted or an internal error occurred. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. SQL 8621 8621 The Tandem NonStop Kernel returned error value-1 during a hash join or hybrid join. Cause. An operating system resource could not be accessed or allocated. Effect. The statement fails. Recovery.
SQL Executor Messages (8000 to 8999) SQL 8624 8624 Tandem NonStop Kernel error value-1 occurred when multiple messages were buffered in an executor server process (ESP). Cause. A resource was unavailable or an internal error occurred. Effect. The statement fails. Recovery. Attempt to diagnose the problem, using the system error code. If the problem persists, report the entire message to your service provider. SQL 8625 8625 An error occurred while repartitioning with parallel sort processes.
SQL Executor Messages (8000 to 8999) SQL 8627 8627 An error occurred on the overflow file value-1 of a hybrid hash join operation. Cause. A file system error occurred while accessing a temporary file used as the overflow file for a hybrid hash join operation. See the SQLCA or the error display from SQLCI for the specific file system error. Effect. The statement fails. Recovery. Consult the documentation or contact your service provider for information on recovering from specific file system errors.
SQL Executor Messages (8000 to 8999) SQL 8630 8630 An error occurred while processing the GET statement. See the file system error for details. Cause. The file system error describes the cause of this error. Effect. The GET statement fails. Recovery. Correct the error and reissue the statement. SQL 8631 8631 The version of object being accessed is not understood by the local node. Cause. The version of the accessed object was changed to a later version after the query was compiled. Effect.
SQL Executor Messages (8000 to 8999) SQL 8634 8634 Overflow occurred while performing the value-1 operation. Cause. Rows did not fit in available memory, so an overflow occurred to disk. Effect. The performance of the query degrades. Recovery. Stop processes that are consuming memory. SQL 8635 8635 Unexpected end-of-file encountered while reading collation value-1. Cause. Internal error. The collation might be damaged. Effect. The statement fails. Recovery. Re-create the collation.
SQL Executor Messages (8000 to 8999) SQL 8638 8638 Collation value-1 uses features that are not supported by NonStop SQL/MP. Cause. Features used by the collation cannot be used by this release (or possibly any release) of SQL/MP software. Effect. The statement fails. Recovery. Remove the unsupported features from the collation source. SQL 8639 8639 An error occurred in the versioning procedures. error following this message for details. See the Cause.
SQL Executor Messages (8000 to 8999) SQL 8801 8801 MEASURE subsystem failed with error value-1 while accumulating SQL statement counters. Cause. Check Measure error codes in the Measure Reference Manual. Effect. If this message is reported as an error (a negative number in SQLCODE), the statement fails. If this is reported as a warning (a positive number in SQLCODE), the statement executes successfully, but the SQL statement counters (as reported by the Measure subsystem) might have incorrect values.
SQL Executor Messages (8000 to 8999) SQL 8995 8995 Internal error value-1: SQL executor array manager. Cause. Internal error: An internal error occurred in the SQL Executor or SQL ESP Manager (SQLESPMG) process. Effect. The statement fails. Recovery. None. Report the entire message to your service provider. Include the internal error number given in the message; this will aid in diagnosing the failure. SQL 8996 8996 Internal error value-1: process. SQL ESP Manager (SQLESPMG) Cause.
SQL Executor Messages (8000 to 8999) SQL 8998 8998 NonStop SQL/MP is not installed on system value-1. Cause. An attempt was made to execute an SQL statement on a node where SQL/MP was not installed. Effect. The statement fails. Recovery. Contact your system manager. SQL 8999 8999 Internal error: SQL executor. Cause. Internal error: Your program is corrupted, or an internal error occurred. Effect. The statement fails. Recovery. None. Report the entire message to your service provider.
SQL Executor Messages (8000 to 8999) HP NonStop SQL/MP Messages Manual—427720-006 10 -58
11 SQLCI Utility Processor Messages (9000 to 9999) SQL 9000 9000 The value of value-1 parameter is out of range. Cause. The indicated parameter had a value out of range for the specification. Effect. The statement fails. Recovery. Correct the parameter value and reissue the command. SQL 9001 9001 value-1 is not a valid file name. Cause. A valid file name was not specified where one was required. The form for a file name is: [\node.][$volume.][subvol.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9004 9004 Internal error: value-1 is not a valid token code. Cause. Internal error: Stated in the error message. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9005 9005 Internal error: is invalid. The list context of the token value-1 Cause. Internal error: Stated in the error message. Effect. The command fails. Recovery. None. Report the entire message to your service provider.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9008 9008 The specifications value-1 and value-2 of value-3 are incompatible. Cause. The indicated specifications are mutually exclusive. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 9009 9009 Duplicate specification of the value-1 parameter. Cause. The indicated parameter was specified more than once. Effect. The command fails. Recovery. Correct the syntax and reissue the command.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9012 9012 Error reading file label of value-1. Cause. The label information for the file listed in the error message could not be retrieved. For more information see the error message following this error. Effect. The command fails. Recovery. Correct the file system error condition. SQL 9013 9013 Error reading catalog information of value-1. Cause. Catalog information for the indicated SQL object could not be retrieved.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9015 9015 Source row number value-1 has a conversion error in column value-3.(Column value-3 starts at offset value-2.) Cause. The source row of the COPY, LOAD, APPEND, or APPENDRESTART operation had a column that could not be converted to its target column. See the message following this error for more information about the conversion error. Column names of the form copy of SQL-column-name are used for a non-SQL file when a DDL record is not specified.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9018 9018 Reference to the column value-1 is ambiguous. Cause. The DDL column name was not fully qualified, and another column had the same name. Effect. The COPY command fails. Recovery. Change the map to add more levels of qualification to the ambiguous name. SQL 9019 9019 Column name value-1 cannot be found. Cause. The DDL column name or SQL column name was not found.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9022 9022 Internal error: SQLUTIL internal error number value-1. Cause. Internal error: Programming error. Effect. SQLUTIL terminates abnormally. Recovery. None. Report the entire message to your service provider. SQL 9023 9023 The source column size is greater than the target column size. The source column name is value-1. The target column name is value-2. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9026 9026 The value-1 operation failed on value-2. An unexpected load error code was returned by the SQL loader. As a result, value-2 might be in an invalid state. Cause. The error code returned to LOAD, APPEND, APPENDRESTART, or APPENDCANCEL by the SQL loader was outside the range of valid error codes. Effect. The command fails. As a result, the target might be in an invalid state. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9029 9029 DUP command failed on value-1. Cause. An error occurred while attempting to DUP the named object. See the following message(s) for more information. Effect. The command fails. Recovery. See the accompanying message(s) to determine the appropriate corrective action. SQL 9030 9030 User specification of value-1 and DEFINE specification of value-2 are incompatible for DEFINE value-3. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9033 9033 Source row number value-1 ends in the middle of column value-4. The source row length is value-2. (Column value-4 starts at offset value-3.) Cause. The source row did not end on a column boundary. Column names of the form copy of SQL-column-name are used for a non-SQL file when a DDL record is not specified. Effect. The row is not written to the target SQL table. If the error limit in the ALLOWERRORS option is reached, the command is terminated.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9036 9036 The alternate key specifier value-1 is not defined for the file value-2. Cause. A copy operation through an alternate key access path was executed, but no index with the specified keytag existed. Effect. The command fails. Recovery. Correct the keytag and reissue the command. SQL 9037 9037 The value-1 operation failed on value-2. The load error code is value-3. The sort error code is value-4. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9040 9040 The value-1 command is not allowed in a user transaction. Cause. This command could not be performed within a user-defined TMF transaction. Effect. The command fails. Recovery. Consider entering a COMMIT WORK or ROLLBACK WORK command to end your transaction in progress, and reissue the command. Also, consider using the COPY command instead of LOAD. COPY can execute within a user-defined TMF transaction.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9043 9043 This operation cannot be applied to a catalog table, but value-1 is a catalog table. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the name to refer to a table that is not a catalog table, and reissue the command. SQL 9044 9044 No files found for user value-1,value-2. Cause. The user-specified file set does not contain any files owned by the indicated user. Effect. None. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9047 9047 Purging of value-1 has failed. Cause. The indicated file could not be purged, probably because of a security violation. See the error message following this error for more information. Effect. The PURGE command is not applied to this file. If the error limit in the ALLOWERRORS option is reached, the command is terminated. Recovery. Correct the file system error condition. SQL 9048 9048 The value-1 specification is not allowed for SQL objects.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9051 9051 The map names specification value-1 TO value-2 is not valid. Cause. An invalid Subsystem Programmatic Interface (SPI) token for name mapping was passed from SQLCI to SQLUTIL. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9052 9052 The CATALOG specification value-1 FOR value-2 is not valid. Cause. An invalid Subsystem Programmatic Interface (SPI) CATALOG token was passed from SQLCI to SQLUTIL.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9055 9055 The target fileset specification value-1 is not valid. Cause. An invalid Subsystem Programmatic Interface (SPI) token for a target file set was passed from SQLCI to SQLUTIL. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9056 9056 The value-1 command failed on value-2. The following message explains the failure in more detail. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9059 9059 Unable to find the names of protection views defined on the table value-1. See the message following this for more information. Cause. The SECURE function could not retrieve information about protection views defined on the table. Effect. If the error limit in the ALLOWERRORS option is reached, the command terminates. Recovery. See the message following this error for recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9062 9062 Ownership of the protection view value-1 cannot be changed without changing the ownership of the underlying table. The command must include both table and protection view. Cause. You attempted to change the ownership of a protection view without changing the ownership of the underlying table. Effect. If the error limit in the ALLOWERRORS option is reached, the command terminates. Recovery. Include the underlying table and reissue the command.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9065 9065 Unable to set the value-1 attribute for the target file value-2 (or one of its partitions). Cause. Some of the target file attributes (for example, AUDIT) could not be set. Effect. The target file will not be the exact image of the source file, but the data will be correct. Recovery. Informational message only; no corrective action is needed.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9069 9069 value-1 operation failed on value-2. Cause. An attempt to perform the specified operation on the named object failed and is explained in the following message. Effect. The command fails. Recovery. See the message following this error for recovery. If you think this is an internal error, report the entire message to your service provider.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9072 9072 Unable to value-1 because it would make the SQL protection view value-2 description be registered in a different catalog than the underlying table. Cause. The specified operation could not be performed because it would cause the protection view description to be registered in a different catalog than the underlying table. This error is probably the result of an incorrect CATALOG specification. Effect. The command fails. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9076 9076 Internal error: Unexpected error value-1. Cause. Internal error: An unexpected error was detected. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9077 9077 Internal error: Unable to MAP COLLATION NAMES because of a failure to parse the constraint text. Cause. Internal error: An error occurred while parsing the definition of a constraint text to perform collation name mapping. Effect.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9080 9080 Unable to duplicate value-1 because it is part of an SQL catalog. Cause. An object that is part of an SQL catalog could not be duplicated. Effect. The command fails. Recovery. Reissue the command without explicitly specifying any catalog objects. SQL 9081 9081 Unable to duplicate value-1 because it is marked corrupt. Cause. You cannot duplicate a corrupted object. Effect. The command fails. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9084 9084 Views or indexes were not duplicated because a target name map was not specified for them. Cause. An underlying table with views or indexes was duplicated, but no target name map was specified for them. Effect. The views and indexes are not duplicated. Recovery. If you want to duplicate the views and indexes, reissue the command, and specify a target name map for the views and indexes. SQL 9085 9085 Duplicating value-1 to value-2. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9088 9088 value-1 and dependent objects purged. Cause. An error occurred during an operation duplicating an underlying table and its dependent objects (protection views and indexes), so the duplicated base table was purged. See the message that follows this error for more information. Effect. Objects that were previously reported as duplicated are purged. Recovery. See the message following this error for recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9091 9091 Unable to end a transaction. command might be backed out. The work done by this Cause. A TMF transaction initiated by SQLUTIL could not successfully complete. The request might have been sent to the catalog manager, and the catalog manager aborted the transaction. There might have been problems related to the TMF subsystem; for example, the transaction exceeded the MINFILES limit.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9094 9094 Unable to set/reset corrupt flag of value-1. The operation cannot be successfully performed on this object. Cause. The corrupt bit could not be changed. You probably did not have sufficient authority to alter the label. See the file system error following this message for more information. Effect. The command is terminated. Recovery. Correct the file system error condition.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9097 9097 The value-1 operation failed on the partition value-2 of the index value-3 that is defined on the table value-4. Cause. The command failed on the partition of the index, possibly because of insufficient authority or file in use by another process. See the file system error following this error for more information. Effect. If the error limit in the ALLOWERRORS option is reached, the command terminates. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9100 9100 The DDL row (definition) value-1 information. Simplify the row. contains too much Cause. The DDL record definition is too complex for the COPY or LOAD command. Effect. The command fails. Recovery. Simplify the DDL record definition by using shorter item names and fewer qualification levels. SQL 9101 9101 The column moving specification is too long. Cause. The MOVE option is too complex. Effect. The command fails. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9104 9104 PROGID cannot be activated when changing the OWNER. Cause. Stated in the error message. Effect. The command fails. Recovery. Change the command to specify the new OWNER. Logon with a new owner ID, and then enter another SECURE command with the PROGID option. SQL 9105 9105 The PROGID attribute of the file value-1 was reset when the owner was changed. Cause. The file being secured had the PROGID flag on.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9107 9107 A PARTONLY or PARTOF option can be used only with a keysequenced target, and a PARTONLYIN option can be used only with a key-sequenced source. Cause. You attempted to use a PARTONLY or PARTOF option for writing data into, or a PARTONLYIN option for reading data from, a relative or entry-sequenced file. Effect. The command fails. Recovery. Remove the PARTONLY, PARTONLYIN, or PARTOF option, and reissue the command.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9110 9110 value-1 value-2 cannot be explicitly specified for this command. Cause. The command could not be applied to the objects of this type. For example, individual catalog tables cannot be purged or secured. Effect. The object is skipped, and the command continues. Recovery. No recovery is necessary. SQL 9111 9111 value-1 value-2 were skipped. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9113 9113 The source row number value-1 violates constraint value2 for the target table. Cause. For a COPY, LOAD, APPEND, or APPENDRESTART command, the source row violated constraints on the target SQL table. Effect. The row is not written to the output file. If the error limit in the ALLOWERRORS option is reached, the command terminates. Recovery. Correct the source data.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9116 9116 The base column name value-1 in the REDEFINE specification is ambiguous. Cause. The DDL name in the REDEFINE specification matched more than one name from the DDL dictionary. Effect. The command fails. Recovery. Add qualifications to the column name, and reissue the command. SQL 9117 9117 The redefining name value-1 in the REDEFINE specification cannot be found. Cause. Redefining name cannot be found in the DDL dictionary. Effect.
SQLCI Utility Processor Messages (9000 to 9999) table. If the error is related to source data, correct the source data and restart the command. SQL 9120 9120 A duplicate key encountered during a write operation to table value-1 has been ignored. Cause. During execution of a LOAD, APPEND, or APPENDRESTART command for a key-sequenced target table, a row that contained a duplicate primary-key value was rejected. This error can be caused by using different collations for the source and target columns. Effect.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9123 9123 Duplicated-key rows for table value-1 have been ignored during the LOAD or COPY operation. Cause. For the LOAD or COPY command, a row is rejected if a duplicate key is found. This can be caused by using different collations for the source and target columns. Effect. The LOAD or COPY operation continues. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9126 9126 Parity error encountered during read operation on value1. Record number [value-2] has been skipped by the LOAD or COPY operation. Cause. The COPY, LOAD, APPEND, or APPENDRESTART command encountered a record having a data parity error. Effect. The row is not written to the output file. If the error limit in the ALLOWERRORS option is reached, the command is terminated. Recovery. No recovery is necessary.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9129 9129 Row number value-1 has a key out of order. Cause. The row was not ordered by the value of the primary key. Effect. The statement fails. Recovery. Remove the SORTED option, or pass rows ordered by primary key value. SQL 9130 9130 All referential constraints must be dropped from table value-1 before performing the value-2 operation. Cause. The operation is not allowed if the table has referential constraints. Effect. The operation is terminated.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9132 9132 Version error. The version of object value-1 is value2, and the version of NonStop SQL/MP system software attempting to access the object is value-3. The version of the object cannot be greater than the version of NonStop SQL/MP system software that is attempting to access it. Cause. Stated in the error message. Effect. The operation fails. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9134 9134 Version error. The Program Catalog Version (PCV) of program file value-1 is value-2. The version of the NonStop SQL/MP system software on the target node is value-3. The PCV of the program file cannot be greater than the version of the NonStop SQL/MP system software on the target node. Cause. You attempted to duplicate an SQL program file and the PCV of the program file was greater than the version of SQL/MP software on the target node. Effect.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9136 9136 Version error. The Program Catalog Version (PCV) of program file value-1 is value-2. The version of NonStop SQL/MP system software on the node where the program file resides is value-3. The PCV of the program file cannot be greater than the version of NonStop SQL/MP system software on the node where the program file resides. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9139 9139 The version of the NonStop SQL/MP system software that is running could not be retrieved due to a file system error. Cause. See the file system error following this error for the cause. Effect. The operation fails. Recovery. For more information on the description of the file system error, refer to the Guardian Procedure Errors and Messages Manual. SQL 9141 9141 Version mismatch.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9144 9144 Version mismatch. The SQL index value-1 has a version number of value-2 in its disk label, which does not match the version number of value-3 in the object description in the value-4.INDEXES catalog table. Cause. The disk label or the INDEXES table was corrupted. Effect. The command continues. Recovery. None. Report the entire message to your service provider.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9148 9148 The PURGEDATA command using the PARTONLY option cannot operate on SQL table value-1 because the object is not the last partition of an entry-sequenced or relative table. Cause. PURGEDATA, PARTONLY option only applies to the last partition of an entrysequenced or relative table. Effect. The PURGEDATA command fails. Recovery. Correct the command.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9152 9152 Index value-1 does not belong to the target base table value-2. Cause. The index that was specified in a config-file FOR index-name clause for the parallel load index operation does exist as an SQL index, but it does not belong to the given target base table. Effect. The LOAD operation fails. Recovery. Reissue the command, specifying either an SQL index that belongs to the target base table or no index at all.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9155 9155 Indexes value-1 and value-2 are two partitions of the same index. An index cannot be specified more than once in the PARALLEL EXECUTION ON option. Cause. No more than one configuration file can be applied to an SQL index when loading index partitions in parallel. Effect. The LOAD operation fails. Recovery. Reissue the command, making sure that no index is specified more than once.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9158 9158 The referential constraint name specified in the MAKE RC QUERYcommand is not associated with table value-1 or the table is not the child table for the constraint. Cause. Stated in the error message. Effect. No query is generated for the table specified in the error message. Recovery. Use the FILEINFO command with the DETAIL option to determine the names of the referential constraints associated with the table.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9161 9161 The ENSCRIBE dictionary value-1 was moved from one subvolume to another, but its key files were not altered by the FUP ALTER command. Cause. You moved a DDL dictionary from one subvolume to another subvolume, but did not change the subvolume name of the alternate key file in the file label of each dictionary file that has alternate keys. Effect. The COPY, LOAD, APPEND, or APPENDRESTART command fails. The target is not modified. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9164 9164 The ENSCRIBE dictionary value-1 is full and no more objects can be added. The sequence number used in the dictionary has exceeded the unsigned 32-bit range. Cause. The NEXT-OBJ number in DICTDDF exceeded the unsigned 32-bit range. The dictionary is full and no more objects can be added. Effect. DDL closes the dictionary and output files and stops processing. Recovery. Delete some objects from the dictionary and recompile.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9168 9168 value-1 is not an APPEND recovery file. Cause. The file specified in the RECOVERYFILE parameter of an APPEND, APPENDRESTART, or APPENDCANCEL command does not contain the proper identifier characters at the beginning of the file. You may have made a mistake and named a different file than you intended. Or maybe you selected a name to use for a recovery file and there already was a file with that name. Effect. The command fails.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9171 9171 Recovery file has the wrong version. value-1; version needed is value-2. Version in file is Cause. The file named in the RECOVERYFILE parameter of the APPEND, APPENDRESTART, or APPENDCANCEL command was written by a different version of SQL than is currently installed. It is in a format not usable by the current SQL. Effect. The command fails. The target is not modified. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9174 9174 The target of an APPEND command cannot be in the corrupt state. If you are trying to recover from an earlier APPEND that was interrupted, use an APPENDRESTART or APPENDCANCEL command. Cause. You attempted to use the APPEND command to add data to a table or partition of a table that has its corrupt flag set. Effect. The command fails. No modification of the target table is done. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9176 9176 The error in the next message occurred when APPEND, APPENDRESTART, or APPENDCANCEL tried to restore value-1 to its initial state. As a result, value-1 might be in an invalid state. Cause. If an error causes APPEND to terminate, it attempts to restore the EOF of the target table to its original value and otherwise put the target table back to the way it was when the APPEND started.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9178 9178 The source file has been modified since the original APPEND started. Its original modification timestamp was value-1, its current modification timestamp is value-2. Cause. You entered an APPENDRESTART command to complete an APPEND that had been interrupted, but the contents of the source file were changed sometime after that original APPEND started.
SQLCI Utility Processor Messages (9000 to 9999) (APPEND will accept a recovery file that exists, but is incomplete — it will write fresh recovery information to the recovery file.) SQL 9181 9181 The recovery file specified in the APPEND already exists and contains recovery data. Cause. You entered an APPEND command that specifies a recovery file that already exists, indicating that an APPEND was already in progress and had been interrupted.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9200 9200 File value-1 not found. Cause. The named file was specified in a utility command, but the file could not be found. Effect. The file is skipped. Recovery. If you believe the file exists, verify the file name and make any necessary corrections before reissuing the command. SQL 9201 9201 Fileset value-1 not found. Cause. The named file set was specified in a utility command, but no files were found that matched it. Effect. The file set is skipped.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9204 9204 Unable to access volume value-1. Cause. Files on the named volume were specified in a utility command, but an error occurred during access to the volume. See the error message following this error for more information. Effect. The files are skipped. Recovery. See the error following this error for recovery. SQL 9205 9205 Undefined system value-1. Cause. Files on the named node were specified in a utility command, but the node does not exist.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9208 9208 Unable to value-1. DUP table value-2 failed because of mapping error. Cause. An error occurred in mapping names. The target and source might have the same name, or the table name was not specified in MAP NAMES. Effect. The table and its dependencies (indexes, views) are not duplicated. Recovery. Correct mapping errors and reissue the command. SQL 9209 9209 Unable to value-1.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9212 9212 Command fails because of version incompatibility between source and target systems or source and target objects. Cause. The error could be caused by SQL/MP software version incompatibility. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9213 9213 FILEINFO will lose some information due to version incompatibility between source and target systems or source and target objects. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9216 9216 Unable to value-1. DUP of collation object value-2 failed because of mapping error. Cause. An error occurred in mapping names. The target and source might have the same name, or the collation name was not specified in MAP NAMES. Effect. The collation object is not duplicated. Recovery. Correct the name mapping errors and reissue the request. SQL 9217 9217 The requested operation is not allowed on an OSS file. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9827 9827 value-1 CATALOG was unable to communicate with the catalog manager. Cause. A timeout occurred. Effect. The UPGRADE or DOWNGRADE CATALOG command fails. Recovery. None. Report the entire message to your service provider. SQL 9828 9828 value-1 CATALOG failed to start catalog manager process. Cause. Possible internal errors occurred. Effect. The UPGRADE or DOWNGRADE CATALOG command fails. Recovery. None.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9835 9835 CLEANUP does not purge single catalog table. Cause. The CLEANUP command does not purge single catalog table. Effect. The CLEANUP command terminates. Recovery. To purge a damaged catalog table, specify a wild-card character (*) in the qualified fileset list and a CATALOG option in the command. SQL 9836 9836 No user SQL object found. Cause. CLEANUP could not find any SQL tables, indexes, or views in the current subvolume. Effect.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9839 9839 CLEANUP does not purge catalog tables without CATALOG[S] option being specified. Cause. The CATALOG option was not specified. Effect. The CLEANUP command does not purge the catalog tables. Recovery. Reissue the CLEANUP command and include the CATALOG option. SQL 9840 9840 CLEANUP does not purge ENSCRIBE files. Cause. CLEANUP does not purge Enscribe files. Effect. The CLEANUP command does nothing. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9843 9843 Security violation. SUPER.SUPER is required for CLEANUP operation. Cause. CLEANUP requires SUPER.SUPER user security. Effect. The CLEANUP command fails. Recovery. Logon as SUPER.SUPER, and reissue the CLEANUP command. SQL 9844 9844 CLEANUP failed because operation cannot be done inside a user-defined TMF transaction. Cause. Stated in the error message. Effect. The CLEANUP command fails. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9847 9847 CLEANUP was unable to clean up catalog descriptions because the catalog is corrupted. Cause. The catalog was corrupted. Effect. Catalog descriptions are not cleaned up. Some catalog entries might have been cleaned up. Recovery. Enter the DROP CATALOG command first. If the drop operation fails, enter CLEANUP and specify the CATALOG option to remove the catalog tables. SQL 9848 9848 Security violation. shadow label operation.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9851 9851 VERIFY failed to obtain a disk label with a shared lock. Cause. Stated in the error message. Cause. The command fails. Recovery. Reissue the VERIFY command. SQL 9852 9852 A TMF transaction was not in effect, and BROWSE ACCESS is not allowed. Cause. Stated in the error message. Effect. The command fails. Recovery. Reissue the VERIFY command. SQL 9853 9853 Column value-1 in disk label does not match value-2 in catalog value-3. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9855 9855 Column value-1 in disk label does not match column value-2 and column value-3 in catalog value-4. Cause. Columns in the catalog table are corrupted. Effect. The command continues. Recovery. None. Report the entire message to your service provider. SQL 9856 9856 The local USAGES table has no entry for the primary key. Cause. The USAGES table is corrupted. Effect. The command continues. Recovery. None.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9859 9859 The number of partitions does not match the number of entries in the disk label. Cause. The FILES table is corrupted, or partitions are missing. Effect. The command continues, but no partitions are verified. Recovery. None. Report the entire message to your service provider. SQL 9860 9860 The partition column in FILES table is set incorrectly. Cause. The FILES table is corrupted. Effect. The command continues, but no partitions are verified.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9863 9863 The column of the TABLES table does not agree with the number of entries in the COLUMNS table for the shorthand view. Cause. The TABLES or COLUMNS table is corrupted. Effect. The command continues, but the columns are not verified. Recovery. None. Report the entire message to your service provider.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9867 9867 Unable to obtain catalog definition for the SQL index or index partition value-1. Cause. Another user locked an SQL index or a version error occurred. Effect. The command fails. Recovery. Check that no one is accessing the object, and then reissue the VERIFY command. If the command still fails, report the entire message to your service provider. SQL 9868 9868 Unable to obtain catalog definition for SQL protection view value-1. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9871 9871 The number of entries in the INDEXES table does not match the number of entries in the disk label. Cause. The INDEXES table was corrupted. Effect. The command continues, but verification for related indexes is not performed. Recovery. None. Report the entire message to your service provider. SQL 9872 9872 Shared lock is not allowed while reading catalog definition. It will continue with BROWSE ACCESS. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9875 9875 Column value-1 in disk label of the partition of this table is not correct. The name of the partition is value-2. Cause. The disk label of the partition might have been corrupted. Effect. The command continues. Recovery. None. Report the entire message to your service provider. SQL 9876 9876 Column value-1 in disk label of the index of this table is not correct. The name of the index is value-2. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9879 9879 VERIFY failed to read the protection view definition with a shared lock, and BROWSE ACCESS is not allowed. Cause. The protection view was locked by another user, and BROWSE ACCESS was not allowed. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9880 9880 VERIFY failed to read the shorthand view definition with a shared lock, and BROWSE ACCESS is not allowed. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9883 9883 VERIFY failed to verify partition value-1. Unable to read the disk label. Cause. See the disk process error preceding this error for the cause. Effect. VERIFY fails to verify this partition. Recovery. Correct the disk process error condition and reissue the request. SQL 9884 9884 The default value specified for column value-1 could not be verified due to an internal conversion error. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9886 9886 Value of value-1 is: value-2 Cause. VERIFY found that the CREATETIME or REDEFTIME value in the catalog did not match the CrTime^F or CatalogOptime^F value in the disk label. This can occur when a dropped table is recovered using ROLLFORWARD. Effect. VERIFY returns an error on the object being verified. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9890 9890 Data cannot be transferred due to character set incompatibility. Source column value-1 has character set value-2. Target column value-3 has character set value-4. Cause. The source column and target column character sets were incompatible. The target character set must be the same as the source character set. Effect. The COPY, LOAD, APPEND, or APPENDRESTART command fails. The target is not modified. Recovery.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9900 9900 The file name value-1 in the COLLATION specification is not valid. Cause. An invalid Subsystem Programmatic Interface (SPI) COLLATION token was passed from SQLCI to SQLUTIL. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 9901 9901 The collation object value-1 cannot be deleted because it has dependent objects. Cause.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9905 9905 The disk label contains invalid information. Cause. The collation or catalog table, or a protection view that points at a collation or catalog table, has an SQL label associated with it. This type of table should not have an SQL label associated with it. Effect. The command continues. Recovery. None. Report the entire message to your service provider. SQL 9906 9906 Column value-1 in catalog value-2 contains the value value-3.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9908 9908 The VALUE attribute for field value-1 was ignored because it contained a LOCALE specification. Cause. The VALUE attribute of the field listed in the message contained a LOCALE specification. SQL has not been enhanced to recognize and process LOCALE specifications. Effect. SQL ignores the VALUE attribute. The field is treated as if it did not have a VALUE attribute.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9912 9912 An error occurred during an attempt to translate the node name specified in the MODIFY DICTIONARY command into a node number. Cause. The name specified for a node could not be translated into a node number. Effect. The command fails. No modification is done. Recovery. Verify that the node name is correct and is specified correctly in the MODIFY DICTIONARY command.
SQLCI Utility Processor Messages (9000 to 9999) SQL 9915 9915 REPAIR can cause data inconsistency between tables and indexes. Cause. REPAIR creates an empty SQL object. This can cause data inconsistency between the repaired and the dependent object. For example, repair of a table object can make dependent indexes to be inconsistent because the table is empty and the index might have records. Effect. This might cause data inconsistency. Recovery. Re-create the inconsistent object.
SQLCI Utility Processor Messages (9000 to 9999) HP NonStop SQL/MP Messages Manual—427720-006 11 -82
12 SQLCI Messages (10000 to 10999) SQL 10001 10001 The OUT file cannot be the same as the IN file unless the IN file is a terminal or process. Cause. An IN and OUT file conflict occurred. Effect. The files are not opened. Recovery. Specify different file names for the IN and OUT files. If you want input to be taken from the terminal, do not specify the IN option in the RUN command. If you want output to go to the terminal, do not specify the OUT option in the RUN command.
SQLCI Messages (10000 to 10999) SQL 10005 10005 Unable to open file value-1. Cause. Another user opened the file, or the file did not exist. See the associated file system error. Effect. The file is not opened. Recovery. If the file is in use, wait until the file is released. If the file does not exist, correct the file identifier and reissue the command. SQL 10006 10006 Unable to open input file value-1. Cause. Another user opened the file, or the file did not exist. See the associated file system error.
SQLCI Messages (10000 to 10999) SQL 10009 10009 File value-1 cannot be opened because OBEY files can be nested only to a depth of four. Cause. The SQLCI limit for nested OBEY command files was exceeded. It cannot open more than four nested OBEY command files. Effect. The OBEY command fails. Recovery. Rearrange your OBEY command files so that there are no more than four nested OBEY command files and try again. SQL 10010 10010 Parameter string on the run command was truncated to 132 characters. Cause.
SQLCI Messages (10000 to 10999) SQL 10014 10014 The FC and ! commands can be entered only interactively. Cause. An FC or ! command was specified in an OBEY command file. Effect. The command fails. Recovery. Remove the FC or ! command from the OBEY command file. Enter these commands interactively if necessary. SQL 10015 10015 Command not found. Cause. The specified command was not found in the history buffer or the stored report commands. Effect. The command fails. Recovery. Enter the command explicitly.
SQLCI Messages (10000 to 10999) SQL 10021 10021 Syntax error. Cause. The command used invalid syntax. Effect. The command fails. Recovery. Check the syntax and reissue the command. To display the syntax, enter the SQLCI HELP command. SQL 10022 10022 This feature is not implemented yet. Cause. A command attempted to access an unavailable feature. Effect. The command fails. Recovery. Do not use this command. 10023 Internal error: SQLCI received a message with an invalid version number from SQLCI2. Cause.
SQLCI Messages (10000 to 10999) SQL 10025 10025 Internal error: SQLCI received an invalid message type from SQLCI2. Cause. Internal error: SQLCI and SQLCI2 are not compatible. Effect. The command fails. Recovery. Run VPROC on SQLCI and SQLCI2 to determine whether you are running compatible versions. If they are not compatible, install the compatible versions and reissue the command. If they are compatible, report the entire message to your service provider. SQL 10026 10026 Internal error: type from SQLCI.
SQLCI Messages (10000 to 10999) SQL 10028 10028 Internal error: SQLCI2 received a message out of order from SQLCI. Cause. Internal error: You might have incompatible versions of SQLCI and SQLCI2. Effect. The command fails. Recovery. Run VPROC on SQLCI and SQLCI2 to determine whether you are running compatible versions. If they are not compatible, install the compatible versions and reissue the command. If they are compatible, report the entire message to your service provider.
SQLCI Messages (10000 to 10999) SQL 10031 10031 Unable to communicate with SQLCI2 process. Enter the command again. Cause. The SQLCI2 process stopped because the BREAK key was pressed or because someone stopped the process. Effect. The command fails. Recovery. Enter the command again. SQL 10032 10032 Internal error: String overflow. Cause. Internal error: The input command length exceeded 32,767 characters. Effect. The command fails. Recovery. Reduce the command length and reissue the command.
SQLCI Messages (10000 to 10999) SQL 10035 10035 Unable to allocate extended memory (DEFINEPOOL error value-1). Cause. SQLCI failed to allocate a segment of memory to hold its data structures. Effect. The command fails. Recovery. Correct the problem indicated by the DEFINEPOOL error. SQL 10036 10036 Unable to allocate extended memory (GETPOOL error value-1). Cause. SQLCI failed to allocate a segment of memory to hold its data structures. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10039 10039 Numeric literal must contain 18 or fewer digits. When a numeric literal is in scientific notation, the mantissa and exponent must each have 18 or fewer digits. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the size of the numeric literal and reissue the command. SQL 10040 10040 String literal must be enclosed within identical quotation marks. Cause. Stated in the error message. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10043 10043 Statement name has not been successfully prepared. Cause. You tried to execute a statement that was not successfully prepared. Effect. The statement is not executed. Recovery. Prepare the statement before executing it. SQL 10044 10044 This value is not allowed for this option. Cause. An invalid value was specified for an option in the SET, SHOW, or RESET command. Effect. The command fails. Recovery. Use the correct value for the option.
SQLCI Messages (10000 to 10999) SQL 10048 10048 value-1 must be an SQL table, view, or index. Cause. An object other than a table, view, or index was specified in the DISPLAY USE OF command. Effect. The command fails. Recovery. Choose the correct object for the DISPLAY USE OF command and reissue the command. SQL 10049 10049 Unable to determine the underlying table name of the protection view. Cause. Stated in the error message. Effect.
SQLCI Messages (10000 to 10999) SQL 10052 10052 Unable to update =_DEFAULTS DEFINE (process defaults). Cause. The system was unable to set the process defaults or update the process defaults. Effect. The DEFINE is not altered. Recovery. If the DEFINEs are disabled, enable them and reissue the command. If the parameter values specified in the catalog or volume command are not valid, correct the parameter values and reissue the command. SQL 10053 10053 A logical name cannot be specified in this command.
SQLCI Messages (10000 to 10999) SQL 10056 10056 A system name is required. Cause. Stated in the error message. Effect. The command fails. Recovery. Specify a node name and reissue the command. SQL 10057 10057 File name value-1 contains a 7-character volume name. Cause. When used with SQLCI, volume names cannot exceed 6 characters. Effect. The command fails. Recovery. Correct the file name so that the volume name does not exceed 6 characters and reissue the command.
SQLCI Messages (10000 to 10999) SQL 10060 10060 Value must be period or comma. Cause. The SET STYLE value for DECIMAL_POINT option is not a period (.) or a comma (,). Effect. The command fails. Recovery. Enter the corrected command. SQL 10061 10061 Value must be between 1 and 255. Cause. The value specified for RIGHT_MARGIN is not in the range 1 through 255. Effect. The command fails. Recovery. Enter the corrected command. SQL 10062 10062 Value must be between 0 and 32767. Cause.
SQLCI Messages (10000 to 10999) SQL 10064 10064 Value must be between 1 and 32767 or ALL. Cause. The SET LAYOUT value for PAGE_LENGTH option is not in the valid range. Effect. The command fails. Recovery. Reissue the command with a correct value. SQL 10065 10065 Value must be between 0 and 255. Cause. The SET LAYOUT value for SPACE option is not in the valid range. Effect. The command fails. Recovery. Reissue the command with a correct value. SQL 10066 10066 Value must be from 0 to 255 characters. Cause.
SQLCI Messages (10000 to 10999) SQL 10069 10069 Section name cannot be specified twice. Cause. An OBEY command file had a duplicate section name. Effect. The command fails. Recovery. Remove the duplicate name and reissue the command. SQL 10070 10070 Section value-1 is not found in OBEY file. Cause. The section name was not found in the OBEY command file. Effect. The section did not execute. Recovery. Enter the OBEY command with the correct section name.
SQLCI Messages (10000 to 10999) SQL 10073 10073 The value for parameter value-1 has not been defined. Cause. The parameter specified in the error message was not named in the SET PARAM or EXECUTE. USING command. Effect. The command fails. Recovery. Set the missing parameter and reissue the command. SQL 10074 10074 Unnamed parameter number value-1 is not specified in the USING clause. Cause.
SQLCI Messages (10000 to 10999) SQL 10077 10077 Transaction is being ended because of outstanding I/Os. Cause. Outstanding I/Os caused the transaction to end. Effect. The transaction ends. Recovery. Wait and reissue the command later. SQL 10078 10078 A TMF transaction is in progress. Cause. The TMF subsystem determined that there was an active TMF transaction in your session. Effect. The new transaction is not started. Recovery. To continue in the current transaction, enter your next command.
SQLCI Messages (10000 to 10999) SQL 10081 10081 No TMF transaction is in progress. Cause. While attempting to abort or end the user-defined TMF transaction, the system determined that there is no active TMF transaction. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 10082 10082 The active transaction is aborted. Cause.
SQLCI Messages (10000 to 10999) SQL 10085 10085 AWAITIO on $RECEIVE failed. Cause. Stated in the error message. Effect. The command is terminated. Recovery. Retry the operation. If it still fails, report the problem to your system manager. SQL10086 10086 Internal error: Unable to transfer control of BREAK OWNERSHIP (SETMODE) in SQLCI. Cause. Internal error: Stated in the error message. Effect. You cannot interrupt any DDL, DML, or DCL statements. Recovery. Reissue the statement.
SQLCI Messages (10000 to 10999) SQL 10089 10089 Invalid system catalog name. Cause. You can only specify the local system catalog name for this command. Effect. The command fails. Recovery. Correct the catalog name and reissue the command. SQL 10090 10090 Your user ID is not authorized to execute this command. Cause. Your user ID is not authorized to execute the INITIALIZE SQL command. Only SUPER.SUPER can execute this command. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10093 10093 Value must be between 1 and 255. Cause. The value specified for VARCHAR_WIDTH was not in the range 1 through 255. Effect. The command fails. Recovery. Enter the corrected command. SQL 10094 10094 Catalog manager communication error. Cause. Either the catalog manager (SQLCAT) terminated abnormally or you ran the wrong version of the catalog manager. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10096 10096 This command is not allowed because a SELECT is in progress. Cause. When a SELECT operation is in progress, only certain SQLCI commands are allowed, such as report writer commands and the following commands: DISPLAY USE OF OBEY EDIT OUT ENV OUT_REPORT EXIT RESET LAYOUT | REPORT | SESSION | STYLE FC SAVE FUP SET LAYOUT | SESSION | STYLE HELP SHOW DEFINE | DEFMODE | LAYOUT | REPORT INFO DEFINE | PARAM | SESSION | STYLE LOG TEDIT Effect. The command fails.
SQLCI Messages (10000 to 10999) SQL 10098 10098 There are no more selected rows. Cause. The command tried to list rows when there were no more rows to select. Effect. No rows are displayed. Recovery. If you do not want to select any more data, use the CANCEL command to terminate the SELECT. If you want to see more data, use the LIST FIRST number command. SQL 10112 10112 (Some table statistics were lost) Cause. More than 16 tables were involved in the query. Effect. No table information is reported.
SQLCI Messages (10000 to 10999) SQL 10201 10201 value-1 has been updated as requested, but updating the define does not change the message file location for the current SQLCI session. Cause. Stated in the warning message. Effect. The INFO DEFINE request shows the new DEFINE values, but the message DEFINE was not changed for the SQLCI session. Messages are extracted from the message file specified at SQLCI initialization. Recovery.
SQLCI Messages (10000 to 10999) SQL 10302 10302 An error occurred during interprocess communication with the SQLUTIL process. The SQLUTIL process is stopped. Cause. An error occurred during interprocess communication between SQLCI and the SQLUTIL process. See the error following this error for the cause. Effect. The command fails. Recovery. Analyze the error. If you believe it is an intermittent error, enter the command again; otherwise, report the entire message to your service provider.
SQLCI Messages (10000 to 10999) SQL 10306 10306 Invalid user name. Cause. An invalid user name was specified. Effect. The command fails. Recovery. Reissue the command with a valid user name. SQL 10307 10307 Extents information is not applicable for views. Cause. The FILEINFO EXTENTS option was specified, but extent information was not applicable for views. Effect. None. The command continues. Recovery. Informational message only; no corrective action is needed.
SQLCI Messages (10000 to 10999) SQL 10310 10310 Restricted fileset required. Cause. A nonrestricted file set is specified where only a restricted file set was allowed. In a restricted file set, the only wild-card character allowed is an asterisk (*) in place of the node name, volume, subvolume, or file portion of a file set. Effect. The command fails. Recovery. Reissue the command with a restricted file set. SQL 10313 10313 The SAVEID and SAVEALL options conflict. Cause. Stated in the error message.
SQLCI Messages (10000 to 10999) SQL 10316 10316 An error occurred when accessing dictionary value-1. Cause. The dictionary file is inconsistent or corrupted. Effect. The command fails. Recovery. Correct the dictionary file and reissue the command. SQL 10317 10317 An error occurred when accessing record (definition) value-2. Cause. The DDL dictionary that contains this record is logically inconsistent, corrupted, or outdated. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10320 10320 Incorrect primary key length. invalid. The OBEY file value-1 is Cause. Stated in the error message. Effect. The command fails and the OBEY command file that was generated is invalid. Recovery. Change the DDL definition so that it matches the Enscribe file, or check that the DDL definition specifies the correct file, and then reissue the CONVERT command. SQL 10321 10321 The range of a binary number is from 1 to 18 digits. The OBEY file value-1 is invalid.
SQLCI Messages (10000 to 10999) SQL 10323 10323 The range of an ASCII character string is from 1 to 4064 characters. The OBEY file value-1 is invalid. Cause. The character string exceeded the maximum length of 4064 bytes accepted by SQL/MP software. Effect. The command fails, and the OBEY command file that was generated is invalid. Recovery. Modify the data size in the DDL definition of the Enscribe file so that the converted data type is compatible, and reissue the CONVERT command.
SQLCI Messages (10000 to 10999) SQL 10326 10326 An error occurred while reading an ENSCRIBE file or its partition value-1. The file might not exist in the dictionary. The OBEY file value-2 is invalid or was not created. Cause. An Enscribe error occurred while reading FILEINFO information from the Enscribe file or its partition file. The file might not exist. Effect. The command fails and the OBEY command file, if generated, is invalid. Recovery.
SQLCI Messages (10000 to 10999) SQL 10330 10330 Missing keyword, CATALOGS. Cause. The keyword CATALOGS was missing. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 10331 10331 The maximum number of SQL column names allowed in an OBEY file is 450. Cause. The request exceeded the limit of 450 column names in an OBEY command file. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10334 10334 The device names of a file must not exceed 6 characters. Cause. The Enscribe file and its associated alternate key files were network qualified; therefore, the volume and the device names cannot exceed 6 characters. Effect. The command fails. Recovery. Shorten the number of characters for the volume or the device names, or move the files to a place where both volume and device names do not exceed 6 characters.
SQLCI Messages (10000 to 10999) SQL 10337 10337 The range of a national language character string is from 1 to 2032 characters (2 to 4064 bytes). The OBEY file value-1 is invalid. Cause. The national language character string exceeded 4064 bytes, the maximum length accepted by SQL/MP. Effect. The command fails and the OBEY command file that was generated is invalid. Recovery.
SQLCI Messages (10000 to 10999) SQL 10400 10400 Unexpected end of line detected in the input line. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 10401 10401 The qualifier has occurred more than once in the command. Cause. Stated in the error message. Effect. The command fails. Recovery. You can enter each qualifier only once in the command. Remove extra qualifiers and reissue the command. SQL 10402 10402 Invalid keyword. Cause.
SQLCI Messages (10000 to 10999) SQL 10404 10404 Unexpected right parenthesis. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 10405 10405 A comma is expected, but is not found. Cause. A comma was missing. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 10406 10406 An unknown qualifier is detected. Cause. Stated in the error message. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10409 10409 The START fileset is not contained in the qualified fileset. Cause. The file set in the START option was not a subset of the qualified file set list. Effect. The command fails. Recovery. Use a file set that is in the qualified file set in the command and reissue the command. SQL 10410 10410 The keyword FROM is expected. Cause. The keyword FROM is missing. Effect. The command fails. Recovery. Correct the syntax and reissue the command.
SQLCI Messages (10000 to 10999) SQL 10413 10413 The keyword NAME[S] is expected. Cause. The keyword NAME[S] was missing. Effect. The command fails. Recovery. Correct the keyword and reissue the command. SQL 10414 10414 The keyword TO is expected. Cause. The keyword TO was missing. Effect. The command fails. Recovery. Correct the keyword and reissue the command. SQL 10415 10415 The keyword FOR is expected. Cause. The keyword FOR was missing. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10418 10418 The keyword VIEW is expected. Cause. The keyword VIEW was missing. Effect. The command fails. Recovery. Correct the keyword and reissue the command. SQL 10419 10419 The keyword PARTITION is expected. Cause. The keyword PARTITION is missing. Effect. The command fails. Recovery. Correct the keyword and reissue the command. SQL 10420 10420 The equal sign is expected. Cause. The equal sign was missing. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10423 10423 Invalid WHERE expression. Cause. Stated in the error message. Effect. The command fails. Recovery. Use the correct syntax for the WHERE expression and reissue the command. SQL 10424 10424 START has been specified twice in the command. Cause. Stated in the error message. Effect. The command fails. Recovery. Specify only one START option in your command and reissue the command. SQL 10425 10425 START can contain restricted wild-card characters only. Cause.
SQLCI Messages (10000 to 10999) SQL 10489 10489 Invalid catalog name or catalog set. Cause. You specified an invalid catalog name or catalog set. Effect. The command fails. Recovery. Reissue the command with a valid catalog name or catalog set. SQL 10490 10490 Invalid fileset. Cause. You specified an invalid file set. Effect. The command fails. Recovery. Reissue the command with a valid file set. SQL 10491 10491 Invalid fileset list. Cause. You specified an invalid file set list. Effect.
SQLCI Messages (10000 to 10999) SQL 10494 10494 Invalid MAP NAMES specification. Cause. You specified an invalid MAP NAMES specification. Effect. The command fails. Recovery. Reissue the command with a valid MAP NAMES specification. SQL 10495 10495 Invalid CATALOG specification. Cause. You specified an invalid CATALOG specification. Effect. The command fails. Recovery. Reissue the command with a valid CATALOG specification. SQL 10496 10496 The error limit was exceeded so the command aborted. Cause.
SQLCI Messages (10000 to 10999) SQL 10499 10499 Only one catalog list is allowed for this command. Cause. You specified more than one catalog list. Effect. The command fails. Recovery. Reissue the command, specifying one catalog list. To specify more than one catalog, use wild-card characters in the catalog list. SQL 10500 10500 Invalid DEFINE name value-1. Cause. The DEFINE name was not found or was not valid for the context. Effect. The DEFINE name is not added, altered, or deleted. Recovery.
SQLCI Messages (10000 to 10999) SQL 10503 10503 Unable to obtain file system buffer space. Cause. See the file system error for the cause. Effect. The indicated DEFINE was not updated or deleted. Recovery. Correct the file system error condition and reissue the command. SQL 10504 10504 Invalid value for value-1 Cause. You specified a value that is not valid for the attribute listed in the error message. Effect. The DEFINE is not added or altered. Recovery.
SQLCI Messages (10000 to 10999) SQL 10507 10507 Current attribute set is inconsistent; check number value-1. Cause. An inconsistency in attribute values occurred in a DEFINE of CLASS TAPE. Effect. The DEFINE is not added or altered. Recovery. Either alter the DEFINE to resolve the inconsistency, or add a DEFINE that resolves the inconsistency.
SQLCI Messages (10000 to 10999) SQL 10510 10510 A required attribute cannot be reset. Cause. The command tried to reset a mandatory attribute for the current DEFINE class. Effect. The DEFINE is not altered. Recovery. If you meant other attributes for the current DEFINE class, correct and reissue the command; otherwise, delete the DEFINE name and add the DEFINE with new attributes. SQL 10511 10511 Cannot convert DEFINE name to network form. Cause. Stated in the error message. Effect.
SQLCI Messages (10000 to 10999) SQL 10514 10514 DEFINE CLASS has not been set. Cause. The DEFINEs were not enabled on your node. Effect. The DEFINE is not added. Recovery. Contact your system manager to enable DEFINEs. SQL 10515 10515 Cannot alter CLASS attribute of DEFINE value-1. Cause. You tried to alter a mandatory attribute for a system DEFINE; for example, the CLASS attribute for the DEFINE =_DEFAULTS. Altering these is not allowed. Effect. The DEFINE is not altered. Recovery.
SQLCI Messages (10000 to 10999) SQL 10518 10518 SQLCI does not allow physical DEFINEs. Cause. Stated in the error message. Effect. The physical DEFINE is not added or altered. Recovery. Add a logical DEFINE, and specify the logical DEFINE. SQL 10519 10519 Internal error: SQLCI internal error. Cause. The internal error stated in the error message occurred. Effect. The command fails. Recovery. None. Report the entire message to your service provider. SQL 10520 10520 Invalid DEFINE attribute length.
SQLCI Messages (10000 to 10999) SQL 10523 10523 Invalid attribute value. Cause. The attribute value length exceeds 100, or the attribute name is not valid for an attribute value that is a file name or catalog. Effect. The DEFINE name is not added or altered. Recovery. Correct the attribute value and reissue the command. SQL 10524 10524 Internal error: Unable to get help text. Cause. Internal error: Help text could not be found for the requested topic. Effect. No help text is displayed. Recovery. None.
SQLCI Messages (10000 to 10999) SQL 10526 10526 Invalid option specified in HELP command. Cause. You specified an option other than SYNTAX, DETAIL, or EXAMPLE. Effect. The command fails. Recovery. Specify a valid option and reissue the command. 10527 The error number value-1 is not used in NonStop SQL/MP. Cause. You specified an error number that is not used in SQL/MP. Effect. The command fails. Recovery. Specify a valid error number and reissue the command.
SQLCI Messages (10000 to 10999) SQL 10532 10532 Invalid character set name value-1 is specified in the command. Cause. The character set name that was specified in the command was not supported by SQL/MP. Effect. The command fails. Recovery. Specify a character set name that is supported by SQL/MP and reissue the command. SQL 10533 10533 The value of parameter value-1 has invalid syntax.
SQLCI Messages (10000 to 10999) SQL 10535 10535 An invalid character set name is specified in the value of parameter value-1. Cause. The character set name in the parameter value was not supported by SQL/MP. Effect. The statement fails. Recovery. Use the SET PARAM command to specify a character set name that is supported by SQL/MP and reissue the command. SQL 10536 10536 The value of parameter value-1 has invalid syntax.
SQLCI Messages (10000 to 10999) SQL 10538 10538 The length of string literal for the value of parameter value-1 is invalid. The length of the string literal must be a multiple of the character set size. Cause. Stated in the error message. Effect. The command fails. Recovery. Correct the string literal for the parameter value and reissue the command. SQL 10600 10600 Internal error: value-1 has occurred at location value-2. Contact your service provider. Cause. Internal error: Stated in the error message.
SQLCI Messages (10000 to 10999) SQL 10603 10603 System is down or not in the network. Cause. Either the node name is invalid, or the node is down. Effect. The command fails. Recovery. If the node name is valid, reissue the command when the node is available. If the node name is invalid, correct the node name and reissue the command. SQL 10604 10604 Option conflicts with a previously specified option. Cause. Option conflicts occurred in the run options. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10608 10608 Invalid program name. Cause. The program name was invalid. The specified program is not supported through this interface. Effect. The command fails. Recovery. Enter a valid program name and reissue the command. SQL 10609 10609 Warning. Process has undefined externals, but was started successfully. Cause. The program contained calls to other programs that could not be resolved. The calls were mapped either to system routines or to DEBUG. Effect.
SQLCI Messages (10000 to 10999) SQL 10612 10612 Unable to allocate map. Cause. See the file system error following this error for the cause. Effect. The command fails. Recovery. Correct the file system error condition and reissue the command. SQL 10613 10613 File system error on swap file. Cause. See the file system error following this error for the cause. Effect. The command fails. Recovery. Correct the file system error condition and reissue the command. SQL 10614 10614 Invalid library file format.
SQLCI Messages (10000 to 10999) SQL 10617 10617 File system error on process name. Cause. See the file system error for the cause. Effect. The command fails. Recovery. Correct the file system error condition and reissue the command. SQL 10618 10618 Library conflict. Cause. Stated in the error message. Effect. The command fails. Recovery. Report the problem to your system manager. SQL 10619 10619 Unable to communicate with the system monitor process. Cause. Stated in the error message. Effect.
SQLCI Messages (10000 to 10999) SQL 10622 10622 File system error occurred during extended data segment initialization. Cause. Stated in the error message. Effect. The command fails. Recovery. Reissue the command. If the error persists, contact your system manager. SQL 10623 10623 File system error occurred on extended segment swap file. Cause. Stated in the error message. Effect. The command fails. Recovery. Reissue the command. If the error persists, contact your system manager.
SQLCI Messages (10000 to 10999) SQL 10626 10626 Process subtype is invalid. Cause. Stated in the error message. Effect. The command fails. Recovery. Reissue the command. If the error persists, contact your system manager. SQL 10627 10627 Unable to start SQL compiler value-1 during INITIALIZE SQL. Reissue the command. Cause. The system could not start or communicate with the SQL compiler (SQLCOMP). The SQLCOMP module might have been missing, or there was a security problem with SQLCOMP. Effect.
SQLCI Messages (10000 to 10999) SQL 10629 10629 Invalid SAVE option. Cause. The option for the SAVE command was invalid. Effect. The command fails. Recovery. Correct the SAVE command and reissue the command. SQL 10630 10630 Invalid command. Cause. You entered an invalid command. Effect. The command fails. Recovery. Correct the syntax and reissue the command. SQL 10631 10631 Invalid option. Cause. You entered an invalid option for the SET, RESET, SHOW, or SAVE command. Effect. The command fails. Recovery.
SQLCI Messages (10000 to 10999) SQL 10635 10635 The INITIALIZE SQL command does not support the PURGE option. Cause. The PURGE option in the INITIALIZE SQL command was not allowed. Effect. The system catalog is not purged. Recovery. Remove the SQL objects before you retry the INITIALIZE SQL command. SQL 10636 10636 Initialize CATALOG operation failed. Cause. The system catalog might have been previously created. For further details, see the associated file system error. Effect.
SQLCI Messages (10000 to 10999) SQL 10639 10639 -- SQLCOMPILE of SQLCI2 successful. Cause. SQLCI2 was successfully SQL compiled. Effect. The SQL compilation of SQLCI2 completed successfully. Recovery. Informational message only; no corrective action is needed. SQL 10640 10640 Right margin does not exceed left margin. Cause. The right margin value did not exceed the left margin value, so the line width was less than or equal to zero. Effect. The last margin value entered is ignored. Recovery.
SQLCI Messages (10000 to 10999) SQL 10643 10643 value-1 is an ambiguous column reference. Cause. The specified column name was not unique; it could not be identified. Effect. The command is ignored. Recovery. Specify the column name in a different form, providing enough information (such as table-name.column-name) to ensure that the name is unique among all columns in the tables that have been selected. SQL 10644 10644 value-1 not found in SELECT list. Cause.
SQLCI Messages (10000 to 10999) SQL 10647 10647 value-1 is nonnumeric. must be numeric. All total and subtotal items Cause. A nonnumeric column was specified in a TOTAL or SUBTOTAL command. Only numeric columns can be totaled or subtotaled. Effect. The command is ignored. Recovery. Reissue the command, using only numeric columns. SQL 10648 10648 You have specified subtotals or break title or break footing or line_number on value-1. You must specify a break on value-1 before the LIST command. Cause.
SQLCI Messages (10000 to 10999) SQL 10650 10650 Because of the new report definition command(s), the report is being started from the beginning. Cause. A BREAK, SUBTOTAL, or TOTAL command was specified after some rows were listed, and then a LIST NEXT command was specified, as in the following sequence: SELECT . . .; LIST FIRST n; BREAK ON . . .; LIST NEXT n; Effect. Instead of listing the next n rows, the report is started over from the first row. Recovery.
SQLCI Messages (10000 to 10999) SQL 10655 10655 Purge of SQLCI2 failed. Cause. See the file system error for the cause. Effect. You cannot execute the INITIALIZE SQL command successfully or install SQLCI2 on your system. Recovery. Correct the file system error condition. If you cannot correct the condition, contact your system manager. SQL 10656 10656 The command is not executed because the SQL application is not registered with NonStop SQL/MP Conversational Interface (SQLCI).
SQLCI Messages (10000 to 10999) SQL 10658 10658 Invalid syntax for DROP SYSTEM CATALOG. is required. Catalog name Cause. You must specify a catalog name in this command. Effect. The command fails. Recovery. Reissue the command with the catalog name. SQL 10659 10659 The DROP ALL SQL command failed. errors from the catalog manager. See the associated Cause. See the catalog manager errors for the cause. Effect. The DROP ALL SQL command fails. Recovery. Correct the catalog manager error.
SQLCI Messages (10000 to 10999) SQL 10662 10662 The CREATE SYSTEM CATALOG command failed. associated errors from the catalog manager. See the Cause. See the catalog manager errors for the cause. Effect. The CREATE SYSTEM CATALOG command fails. Recovery. Correct the catalog manager errors. SQL 10663 10663 The BREAK key was pressed when a DDL command was in progress. The SQLCI2 process was stopped, but the catalog manager (SQLCAT) might have completed the DDL command. Cause. Stated in the error message.
SQLCI Messages (10000 to 10999) SQL 10666 10666 Invalid year is entered as timestamp for COMPUTE_TIMESTAMP. Cause. You entered an invalid year as timestamp for COMPUTE_TIMESTAMP. The year value must be a number. Effect. The command fails. Recovery. Correct the year value and reissue the command. SQL 10667 10667 Invalid hour is entered as timestamp for COMPUTE_TIMESTAMP. Cause. You entered an invalid hour as timestamp for COMPUTE_TIMESTAMP. The hour value is not in the range 0 through 23. Effect.
SQLCI Messages (10000 to 10999) SQL 10670 10670 Invalid microsecond is entered as timestamp for COMPUTE_TIMESTAMP. Cause. You entered an invalid microsecond as timestamp for COMPUTE_TIMESTAMP. The microsecond value was not in the range 0 through 999. Effect. The command fails. Recovery. Correct the microsecond value and reissue the command. SQL 10671 10671 Invalid month is entered as timestamp for COMPUTE_TIMESTAMP. Cause. You entered an invalid month as timestamp for COMPUTE_TIMESTAMP.
SQLCI Messages (10000 to 10999) SQL 10675 10675 The value for TAB is out of range. The valid range is the set of values from left margin to right margin. Cause. The value for the TAB clause was less than the left margin or greater than the right margin. Effect. The DETAIL command fails. Recovery. Correct the value of TAB and reissue the command. SQL 10676 10676 The value for PAGE, NEED, or SKIP is out of range. valid range is 1 through 32767. The Cause.
SQLCI Messages (10000 to 10999) SQL 10679 10679 The INVOKE command does not currently support Ada, FORTRAN, and BASIC as a FORMAT option. Only COBOL85, C, Pascal, TAL, and SQL are supported. Cause. Stated in the error message. Effect. The command fails. Recovery. Informational message only; no corrective action is needed. SQL 10680 10680 value-1 is a duplicate item name. Cause. The name you specified has been specified previously. Each name must be unique. Effect. The command is rejected. Recovery.
SQLCI Messages (10000 to 10999) SQL 10683 10683 The PREFIX or SUFFIX clause cannot be specified with the NULLSTRUCTURE clause. Cause. The INVOKE command has a PREFIX or SUFFIX clause and a NULL STRUCTURE clause. Effect. The command fails. Recovery. Remove the incompatible clause and reissue the command. SQL 10684 10684 The PREFIX, SUFFIX, NULL STRUCTURE, and DATEFORMAT clauses cannot be specified with the FORMAT SQL option. Cause.
SQLCI Messages (10000 to 10999) SQL 10687 10687 An unnamed parameter cannot be used in this statement. Cause. You entered a command that included an unnamed parameter, and an unnamed parameter was not allowed. An unnamed parameter can be used only in a PREPARE command. Effect. The command fails. Recovery. Specify a named parameter and reissue the command. Alternatively, to use unnamed parameters in a SELECT statement, use the PREPARE statement to prepare the SELECT statement, and then use the EXECUTE...
SQLCI Messages (10000 to 10999) SQL 10690 10690 There is no current value-1 command to reset. Cause. The command displayed was specified in a RESET REPORT command; however, there is no command of that type currently in effect. Effect. The RESET REPORT command is ignored. Recovery. Informational message only; no corrective action is needed. SQL 10691 10691 The CHAR AS clause can be specified only with the FORMAT C option. Cause.
SQLCI Messages (10000 to 10999) SQL 10702 10702 Statement value-1 has not been prepared. Cause. Either the name of the prepared statement was incorrect, or the statement was not prepared before the EXPLAIN command was used. Effect. The execution plan for the SQL statement is not explained. Recovery. Prepare the statement, and then enter the correct statement name in the EXPLAIN command. SQL 10703 10703 Unable to use the compiler's extended segment in shared mode. Cause.
SQLCI Messages (10000 to 10999) SQL 10706 10706 Unnamed parameter number value-1 must have an integer value because it is used as a NULL indicator. Cause. An SQL statement contained a NULL indicator parameter. At the time the statement was entered or executed, the parameter value was not a signed integer. Effect. The SQL statement is not executed. Recovery. Correct the parameter value and reissue the statement. SQL 10707 10707 Arithmetic overflow or underflow in FLOAT literal. Cause.
SQLCI Messages (10000 to 10999) SQL 10710 10710 Invalid LOC option name. Cause. Invalid syntax was given for LOC option. Effect. The command fails. Recovery. Enter a valid LOC name. The LOC name must start with a number sign (#). The name can contain alphabetic or numeric characters in any combination, except that the character after the # must be alphabetic. SQL 10711 10711 The length of LOC name is too long. the first 8 characters from each name. SQLCI only uses Cause.
SQLCI Messages (10000 to 10999) SQL 10714 10714 SPOOL3 option can only be used on the spooler file. Cause. You tried to use the SPOOL3 option on a file that is not a spooler file. Effect. The command fails. Recovery. Correct the command by using the SPOOL3 option for a spooler file and reissue the command. SQL 10715 10715 Unable to open the specified output file. associated file-system error. See the Cause. See the associated file system error for the cause. Effect.
SQLCI Messages (10000 to 10999) SQL 10718 10718 Internal error on value-1, error number value-2. SQLCI did not handle this spooling operation correctly on the current output file. Cause. The internal error stated in the error message occurred. Effect. SQLCI does not do level 3 spooling on the current output file. Recovery. None. Report the entire message to your service provider. SQL 10719 10719 The SPOOL3 option will not change the attributes of the spooler job. Cause.
SQLCI Messages (10000 to 10999) SQL 10721 10721 Overflow occurred during arithmetic computation. inaccurate arithmetic result is expected. An Cause. An intermediate result was too large to be held in the internal buffers. Effect. An inaccurate arithmetic result is expected. Recovery. Check the data, simplify your arithmetic calculation and reissue the command. SQL 10722 10722 Overflow occurred during arithmetic computation. data cannot be formatted in date-time form. The Cause.
SQLCI Messages (10000 to 10999) SQL 10725 10725 The DOWNGRADE CATALOG and DOWNGRADE SYSTEM CATALOG commands are not allowed within a user defined transaction. Cause. You started a transaction before executing a DOWNGRADE CATALOG or DOWNGRADE SYSTEM CATALOG command. Effect. The DOWNGRADE CATALOG or DOWNGRADE SYSTEM CATALOG command fails. Recovery. Stop the TMF transaction and reissue the command. SQL 10726 10726 The MODIFY command failed. Cause. See associated error messages for more detail. Effect.
SQLCI Messages (10000 to 10999) SQL 10728 10728 The volumeset list contains too many elements. Cause. There were more than 10 volume names in the volumeset list. Effect. The file label is not modified. Recovery. Use wild-card characters as needed to reduce the number of elements in your volumeset list to a maximum of 10, including volumes to include and volumes to exclude. SQL 10729 10729 A volumeset name is invalid. Cause. Stated in the error message. Effect. The MODIFY DICTIONARY command is terminated.
SQLCI Messages (10000 to 10999) SQL 10999 10999 The message text is not available (file system error value-1). Cause. The message text could not be retrieved for the error number. Effect. You cannot display the error text. Recovery. None. Report the entire message to your service provider.
13 Preprocessor Messages (11000 to 11999) SQL 11001 11001 The SWAPVOL parameter value value-1 is not a valid volume name. Cause. Stated in the error message. Effect. Preprocessing terminates abnormally. Recovery. Correct the SWAPVOL parameter value. SQL 11002 11002 An SQL statement must not have more than 32767 characters, including blanks. Cause. The SQL statement contained more than 32767 characters. Effect. Preprocessing terminates abnormally. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11005 11005 Section name is missing. Cause. The SOURCE statement you entered probably included a left parenthesis after the file name, but did not specify a section name following the parenthesis. Effect. Syntax error: Preprocessing continues. Recovery. Remove the parenthesis or add the section name. SQL 11006 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11006 Host variable is too long.
Preprocessor Messages (11000 to 11999) names, one of the characters must be either a letter or a hyphen. The name cannot begin or end with a hyphen. A C or Pascal name can contain up to 31 characters: letters, digits, and the underscore (_). SQL 11008 11008 Invalid character. Cause. A character was invalid for COBOL. Effect. Syntax error: Preprocessing continues. Recovery. Remove the invalid character. SQL 11009 11009 SQLCA declaration is not allowed in this section of the program. Cause.
Preprocessor Messages (11000 to 11999) SQL 11011 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11011 WHENEVER directive is not allowed in this section of the COBOL program. This message is displayed when the COBOL85, NMCOBOL, C, and TAL programs with embedded SQL are preprocessed using SCI: 11011 WHENEVER directive is not allowed in this section of the program. Cause. Stated in the error message. Effect. Syntax error: The WHENEVER directive is ignored.
Preprocessor Messages (11000 to 11999) Recovery. Correct the command to include a valid output file name. SQL 11015 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11015 Undeclared host variable value-1. This message is displayed when the COBOL85, NMCOBOL, C, and TAL programs with embedded SQL are preprocessed using SCI: 11015 Undeclared or illegal host identifier. Cause.
Preprocessor Messages (11000 to 11999) SQL 11018 11018 The line numbers in this output file do not match the input source file's line numbers because renumbering was necessary. Cause. The preprocessor tried to keep the same line numbers in the generated output file as those in the input file, but preserving line numbers was not possible.
Preprocessor Messages (11000 to 11999) SQL 11022 11022 The directive must appear before the Data Division. Cause. The directive was after the Data Division. Effect. Syntax error: Preprocessing continues. Recovery. Move the directive before the Data Division. For a nested program, place the directive in the Identification Division. SQL 11023 11023 Undeclared cursor name value-1. Cause. A cursor name being used was not declared. Effect. Preprocessing continues, but no object code is generated. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11026 11026 COMPUTATIONAL clause requires numeric data type. Cause. The COMPUTATIONAL clause does not allow alphabetic or alphanumeric data type declaration. Effect. Preprocessing continues. Recovery. Remove the COMPUTATIONAL clause or change the PICTURE clause so that it describes a numeric item. SQL 11027 11027 SIGN clause requires signed numeric. Cause. The SIGN clause allows only a signed numeric data item.
Preprocessor Messages (11000 to 11999) SQL 11030 11030 SQLSA declaration is not permitted in this section of the program. Cause. The SQLSA declaration specified was in a section where it is not permitted. Effect. SQLSA is not declared. Recovery. Include the SQLSA directive in one of the allowed sections. For COBOL programs, the INCLUDE SQLSA directive must be only in the Working-Storage Section, Extended-Storage Section, or Linkage Section.
Preprocessor Messages (11000 to 11999) SQL 11032 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11032 BEGIN DECLARE SECTION and END DECLARE SECTION can appear only in the Data Division. Cause. The BEGIN DECLARE SECTION and END DECLARE SECTION directives were in a division other than the Data Division of a COBOL program. Effect. Preprocessing continues, but no object code is generated. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11034 11034 Invalid variable. Cause. A host variable was invalid. Effect. Preprocessing continues, but no object code is generated. Recovery. Specify a valid host variable. SQL 11035 11035 Invalid file name. Cause. The file name was invalid; the form must be: \node.$volume.subvol.file The volume name must not exceed 6 characters after the dollar sign ($). Effect. Preprocessing continues, but no object code is generated. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11038 11038 The INDEX clause is not allowed. Cause. The preprocessor does not allow the INDEX clause. Effect. Preprocessing continues, but no object code is generated. Recovery. Remove the INDEX clause. SQL 11039 11039 The RENAMES clause is ignored. Cause. The preprocessor does not allow the RENAMES clause. Effect. The host variable is still declared, but the RENAMES clause is ignored. Recovery. Remove the RENAMES clause.
Preprocessor Messages (11000 to 11999) SQL 11042 11042 Cannot create temporary file value-1. Cause. The volume did not have enough space to create the output file. Effect. Fatal error: Preprocessing terminates abnormally. Recovery. Choose a volume with more free space. SQL 11043 11043 Unable to write to file value-1. Cause. There might not have been enough disk space to allocate a primary or secondary extent. See the accompanying file system error. Effect. Fatal error: Preprocessing terminates abnormally.
Preprocessor Messages (11000 to 11999) SQL 11047 11047 SQLCA is declared more than once. Cause. Only one SQLCA declaration per procedure is allowed. Effect. The INCLUDE SQLCA directive is ignored. Recovery. Remove the duplicate INCLUDE SQLCA directive. SQL 11048 11048 SQLSA is declared more than once. Cause. The INCLUDE SQLSA directive occurred more than once in the program. Effect. The INCLUDE SQLSA directive is ignored. Recovery. Remove the duplicate SQLSA declaration.
Preprocessor Messages (11000 to 11999) SQL 11051 11051 Unable to open file value-1. Cause. Either the input file or the output file could not be opened. If this is an input file, the file probably did not exist, or another user opened it exclusively. If this is an output file, there was probably a security violation, or another user opened it explicitly. See the error following this error for the cause. Effect. An SIO error occurred. The file is not opened. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11056 11056 Only one DECLARE CURSOR statement per statement name is allowed. Cause. Stated in the error message. Effect. Preprocessing continues, but no object code is generated. Recovery. Remove the duplicate cursor declaration. SQL 11057 11057 GLOBAL or EXTERNAL clause is allowed only in a level 01 data description entry. Cause. You entered a GLOBAL or EXTERNAL clause in a data description level less than 01. Effect.
Preprocessor Messages (11000 to 11999) SQL 11059 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11059 SQLDA declaration must be in the Data Division of the COBOL program or in the areas where data declarations are allowed in a C or Pascal program. This message is displayed when the COBOL85, NMCOBOL, C, and TAL programs with embedded SQL are preprocessed using SCI: 11059 SQLDA declaration is not permitted in this section of the program Cause.
Preprocessor Messages (11000 to 11999) SQL 11061 11061 Conversational interface is not available. Cause. The input file was missing and the default input name was the home terminal or the user-specified terminal. Effect. Preprocessing terminates abnormally. Recovery. Supply an input file name. SQL 11062 11062 The preprocessor cannot include the SQLCA in the Working-Storage Section because the Working-Storage Section is missing in program value-1. Cause. The Working-Storage Section was missing. Effect.
Preprocessor Messages (11000 to 11999) SQL 11065 11065 Ambiguous reference to host variable value-1. Cause. The statement contained an ambiguous reference to a host variable; the name probably appeared in another record. Effect. The SQL statement fails. Recovery. Qualify the host variable name with the correct record name. SQL 11066 11066 Host variables cannot be longer than 30 characters. Cause. The specified host variable name was longer than 30 characters. Effect. Syntax error: Preprocessing continues.
Preprocessor Messages (11000 to 11999) SQL 11069 11069 Elementary data item was specified for group data item value-1. Cause. A situation like the following occurred: 01 EMP-RECORD. 02 NAMES PIC X(30). 03 EMP-NAME PIC X(30). NAMES must be a group data item. To correct this, declare EMP-RECORD as follows: 01 EMP-RECORD. 02 NAMES. 03 EMP-NAME PIC X(30). Effect. Syntax error: Preprocessing continues. Recovery. Correct the host variable declaration.
Preprocessor Messages (11000 to 11999) SQL 11072 11072 This END-EXEC does not have a corresponding EXEC SQL. Cause. Stated in the error message. Effect. Preprocessing continues. Recovery. An SQL statement must start with the delimiter EXEC SQL and must end with the delimiter END-EXEC. An END-EXEC was found without a corresponding EXEC SQL. Check that every SQL statement has balanced delimiters. SQL 11073 11073 An attempt was made to renumber with a line number increment of .
Preprocessor Messages (11000 to 11999) SQL 11077 11077 Only an SQL comment beginning with "--" can appear after END-EXEC. Cause. COBOL text or SQL statements followed an END-EXEC token. Only SQL comments can be after END-EXEC. Effect. Preprocessing continues. Recovery. Correct the syntax error. SQL 11078 11078 Invalid section name value-1. Cause. The section name specified in the SOURCE statement is not a valid COBOL section name. Section names must follow host variable rules. Effect.
Preprocessor Messages (11000 to 11999) SQL 11081 11081 Cursor names, procedure names, or statement names cannot be host variables. Cause. An attempt was made to preprocess an SQL statement that contains a cursor name, statement name, or procedure name that is a host variable. SQL COBOL does not support EXTENDED DYNAMIC SQL. Effect. The statement fails. Recovery. Specify a cursor name, procedure name, or statement name that is not a host variable.
Preprocessor Messages (11000 to 11999) SQL 11084 11084 There was an error in invoking this table. Cause. The INVOKE utility encountered an error while invoking this table. Effect. The statement fails. Recovery. Correct the INVOKE statement. SQL 11085 11085 Empty EXEC SQL statement delimiter not allowed. Cause. An EXEC SQL statement contained no text. Effect. The statement fails. Recovery. Remove the EXEC SQL statement and the terminating delimiter or add text to the SQL statement.
Preprocessor Messages (11000 to 11999) SQL 11088 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11088 Only a host variable of a fixed-length character type can be cast as a date-time or INTERVAL type. This message is displayed when the COBOL85, NMCOBOL, C, and TAL programs with embedded SQL are preprocessed using SCI: 11088 The variable is not a character type. Only a host variable of type character can be cast as a DATETIM or INTERVAL type. Cause.
Preprocessor Messages (11000 to 11999) SQL 11090 11090 An option cannot be specified more than once. Cause. You specified the same option more than once. Effect. The statement fails. Recovery. Remove the duplicate option. SQL 11091 11091 An extent size must be between 0 and 65,535 pages; 0 and 134,215,680 bytes; or 0 and 134 megabytes. Cause. You specified an extent size that was not within the valid range. Effect. The statement fails. Recovery. Correct the extent size.
Preprocessor Messages (11000 to 11999) SQL 11094 11094 Double byte host variable must be explicitly coerced with a multibyte character set, because the system procedure MBCS_DEFAULTCHARSET_ has not been configured to return a default multibyte character set which is supported by NonStop SQL. Cause. You specified a double byte host variable but no multibyte character set and the system is not configured to have a default multibyte character set. Effect.
Preprocessor Messages (11000 to 11999) SQL 11100 11100 Dynamic Declare Cursor not allowed here. Cause. You specified a global dynamically declared cursor when you were not inside a procedure. Effect. Compilation continues but, no object code is generated. Recovery. Specify a global statically declared cursor when not inside a procedure. SQL 11101 11101 This statement may only appear where executable code is allowed. Cause. You specified an executable SQL statement in an area where only data is allowed.
Preprocessor Messages (11000 to 11999) SQL 11105 11105 Extended Dynamic SQL cursor declarations must have both a cursor variable and a statement variable. Cause. You specified an Extended Dynamic SQL cursor declaration without both a cursor variable and a statement variable. Effect. Compilation continues, but no object code is generated. Recovery. Add either a cursor variable or a statement variable to the Extended Dynamic SQL cursor declaration.
Preprocessor Messages (11000 to 11999) SQL 11200 11200 BEGIN DECLARE/END DECLARE directives cannot be nested. Cause. You specified a BEGIN DECLARE and then another BEGIN DECLARE before ending the first BEGIN DECLARE section with an END DECLARE. Effect. Compilation continues after a warning is printed to the host listing file. Recovery. Remove the second BEGIN DECLARE to make one DECLARE section.
Preprocessor Messages (11000 to 11999) This message is displayed when the COBOL85, NMCOBOL, C, and TAL programs with embedded SQL are preprocessed using SCI: 11203 Version number specified a SQL system version that is not supported by this host complier. Cause. You specified a structure version that is not among the versions supported by this release of the preprocessor. Effect. Preprocessing continues, but no object code is generated. Recovery.
Preprocessor Messages (11000 to 11999) Recovery. Specify the version of the structure in the INCLUDE STRUCTURES directive. SQL 11206 11206 The RELEASE option on the INCLUDE SQLDA statement is not allowed when the INCLUDE STRUCTURES directive has been specified. Cause. You specified the RELEASE option on an INCLUDE SQLDA statement after the INCLUDE STRUCTURES directive was specified. Effect. Preprocessing continues, but no object code is generated. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11209 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11209 The statement must be placed in the Data Division. Cause. The SQL statement was not in the Data Division. Effect. Preprocessing continues, but no object code is generated. Recovery. Move the statement to the Data Division.
Preprocessor Messages (11000 to 11999) SQL 11212 11212 Unsupported character set. Cause. You specified an unsupported character set. Effect. Compilation continues, but no object code is generated. Recovery. Replace the unsupported character set specified with a valid character set. SQL 11213 11213 Current procedure name is being truncated for use as a SQL RTDU name. Cause.
Preprocessor Messages (11000 to 11999) SQL 11302 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11302 The specified character set name is invalid. Cause. You specified an invalid character set name in the CHARACTER SET IS clause. Effect. Preprocessing continues, but no object code is generated. Recovery. Correct the character set name.
Preprocessor Messages (11000 to 11999) Recovery. Contact your HP NonStop representative. SQL 11304 This message is displayed when the COBOL85 program with embedded SQL is preprocessed using SQLCOBOL: 11304 A PIC X variable declaration is expected. Cause. You specified the CHARACTER SET IS clause, but the variable declaration was not PIC X. Effect. Preprocessing continues, but no object code is generated. Recovery. Correct the variable declaration.
Preprocessor Messages (11000 to 11999) SQL 11400 11400 The filename specified to RW_Start was too large -report to Tandem Computers. Cause. If the filename is a Guardian name it cannot exceed 34 characters. If the filename is an OSS name it cannot exceed 1024 characters. If the filename is a PC name it cannot exceed 264 characters. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery. Use a file name that does not exceed the limit for the type of file.
Preprocessor Messages (11000 to 11999) SQL 11404 11404 RW_Readonly was specified to RW_Start, and then called RW_RTDU_Create -- report to Tandem computers. Cause. Internal error. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery. Contact your Tandem representative. SQL 11405 11405 The RTDU written exceeds the maximum size specified in RW_RTDU_Create -- report to Tandem computers. Cause. Internal error. Effect.
Preprocessor Messages (11000 to 11999) SQL 11408 11408 The work area of RW routines is corrupted -- report to Tandem Computers. Cause. Internal error. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery. Contact your Tandem representative.
Preprocessor Messages (11000 to 11999) SQL 11501 11501 The work area of the Data Block routines is not large enough -- report to Tandem Computers. Cause. Internal error. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery. Contact your Tandem representative. SQL 11502 11502 The block id specified in the DATA BLOCK routine was not defined before - report to Tandem Computers. Cause. Internal error. Effect.
Preprocessor Messages (11000 to 11999) SQL 11505 11505 The work area of RW routines is corrupted -- report to Tandem Computers. Cause. Internal error. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery. Contact your Tandem representative. SQL 11550 11550 An error occurred in the Data BLock Routine -- report to Tandem Computers. Cause. Internal error. Effect. Preprocessing aborts after the message is printed to the host listing file. Recovery.
Preprocessor Messages (11000 to 11999) SQL 11997 11997 File name cannot be converted to pre-D00 internal format. Cause. The file name contained both a system name and an eight- character volume name (counting the $). Effect. Compilation continues, but no object code is generated. Recovery. Do not use eight-character volume names. SQL 11998 11998 Embedded SQL memory exceeded during parsing. Cause. An internal error occurred. Effect.
14 SQL INVOKE messages (12000 to 12999) SQL 12001 12001 Invalid base level or increment specified in LEVEL clause. Cause. The INVOKE command had a LEVEL clause with an invalid base level number or increment. The base level must be an integer from 1 through 47. The increment must be an integer from 1 through 24. Effect. The command fails. Recovery. Specify the LEVEL clause with a valid base level and increment. SQL 12002 12002 LEVEL increment is too large for the base level specified. Cause.
SQL INVOKE messages (12000 to 12999) SQL 12004 12004 The host language does not support value-1 data type. Cause. You entered a data type that the host language does not support. Effect. The command fails. Recovery. Re-issue the command with a valid data type. SQL 12005 12005 Internal error: Either the user program was corrupted, or an internal error occurred. Cause. Internal error: Stated in the error message. Effect. The INVOKE statement fails. Recovery. None.
SQL INVOKE messages (12000 to 12999) SQL 12300 12300 The version of SQL object value-1 is not compatible with this version of NonStop SQL/MP software. Cause. An attempt was made to access an SQL object that was incompatible with this version of SQL/MP software. Effect. The command fails. Recovery. Upgrade your SQL/MP software. SQL 12300 12300 The version of SQL object value-1 is not compatible with this version of NonStop SQL/MP software. Cause.
SQL INVOKE messages (12000 to 12999) HP NonStop SQL/MP Messages Manual—427720-006 14- 4
15 Audit Fix-Up Messages (16000 to 16999) SQL 16001 16001 Unable to allocate an extended memory segment during the audit fix-up phase of the operation. (SEGMENT_ALLOCATE_ error value-2 in audit server process (value-1.) Cause. A process could not allocate a segment of memory to hold its data structures. Effect. The operation fails. Recovery. If possible, correct the problem indicated by the SEGMENT_ALLOCATE_ error code.
Audit Fix-Up Messages (16000 to 16999) SQL 16004 16004 A hardware trap occurred in an audit fix-up server process value-1. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 16005 16005 An audit fix-up request was made out of sequence. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
Audit Fix-Up Messages (16000 to 16999) SQL 16008 16008 An error occurred in audit fix-up server process (value-1) while processing a TMF audit record during the audit fix-up phase of the operation. Cause. The following file system error message indicates the cause. Effect. The operation fails. Recovery. Correct the error condition if possible and perform the operation again. If the error condition cannot be corrected, report the entire message to your service provider.
Audit Fix-Up Messages (16000 to 16999) SQL 16011 16011 An error occurred while reporting an event to the EMS collector during the audit fix-up phase of the operation, in process value-1. Cause. An EMS or SPI subsystem error occurred. Effect. The operation fails. Recovery. Check for an error condition in the reporting device. Correct the error condition if possible and perform the operation again. If the error condition cannot be corrected, report the entire message to your service provider.
Audit Fix-Up Messages (16000 to 16999) SQL 16015 16015 An audit fix-up server process could not be started from program file value-1. Error value-2 was returned from PROCESS_CREATE_. Cause. Refer to the Guardian Procedure Calls Reference Manual for an explanation of the PROCESS_CREATE_ error. Effect. The operation fails. Recovery. Correct the error condition if possible and perform the operation again. If the error condition cannot be corrected, report the entire message to your service provider.
Audit Fix-Up Messages (16000 to 16999) SQL 16018 16018 The version of an audit fix-up process' local audit trail could not be retrieved, is incompatible with the version of the audit fix-up process, or is incompatible with one of the disk processes involved in the operation. Audit fix-up server process value-1. Audit fix-up process valud-1. Audit volume value-2. Cause. An incompatible version of the AUDSERV program, or of TMF, or of DP2 was installed on the system. Effect. The operation fails. Recovery.
Audit Fix-Up Messages (16000 to 16999) SQL 16021 16021 An internal error occurred during the audit fix-up phase of the operation. An unknown exception class was encountered: (value-1), in process value-2. Cause. Internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 16022 16022 An audit fix-up server process could not be started from program file value-1 because $CMON denied permission to start the process. Cause.
Audit Fix-Up Messages (16000 to 16999) SQL 16024 16024 Audit fix-up process value-1 found a violation of the uniqueness constraint while working on the index for a CREATE UNIQUE INDEX operation. Cause. Another process inserted a record containing a duplicate key while performing a CREATE UNIQUE INDEX operation on the table. Effect. The operation fails. Recovery. Find the duplicate record, delete it, and reissue the request. SQL 16025 16025 An audit fix-up server detected an internal error. Cause.
16 File-System Messages This section describes file-system messages that are specific to NonStop SQL/MP. File-system messages that can be issued for NonStop SQL/MP in addition to other subsystems are not included here. SQL 035 035 Unable to obtain I/O process control block. Cause. Either you have requested more than 5000 locks, or the disk process for the accessed volume does not have space for more control blocks. Effect. The statement fails. Recovery.
File-System Messages SQL 197 197 An SQL error occurred. Cause. You attempted an operation that generated a call to a SQL/MP component, and an SQL error occurred in that component. The following situations are possible causes of this error: • • • • A startup error occurred during the initiation of a SQL/MP process. For example, the operation you attempted tried to start an SQLCAT process, but the initiation of the process failed. The SQLCAT object file on $SYSTEM.SYSTEM is not licensed.
File-System Messages SQL 579 579 The record size specified is too large for the given block size, file type and format. Cause. The record size specified is too large for the given block size, file type and format. Effect. The requested operation is not performed. Recovery. Increase the block size or reduce the record size specified on the file creation request. The largest supported record size in a format II file is slightly less than in a standard format file for a given block size.
File-System Messages SQL 582 582 Alternate key information could not be returned because it cannot be expressed in the superseded format of the parameter. Cause. For instance, if an alternate key field has an offset greater than 4095, this error will be returned if the alternate key information is requested via FILEINQUIRE, since the format from that procedure allows only 12 bits for an offset. Effect. The requested operation is not performed. Recovery.
File-System Messages SQL 590 590 A parameter value is invalid or inconsistent with another parameter. Cause. You entered an invalid or inconsistent parameter. Effect. The requested operation is not performed. Recovery. Check the syntax, correct it, and resubmit. SQL 597 597 A required item is missing from a parameter item list. Cause. You omitted a required item from a parameter list. Effect. The requested operation is not performed. Recovery. Correct the syntax and resubmit.
File-System Messages recompiling fails to correct the problem, report the entire message to your service provider. SQL 1025 1025 The supplied row or update value violates one of the constraints for the table. Cause. The row or update value that you specified is incompatible with one of the constraints for the table. Effect. The update or insert operation fails. Recovery. Correct the SQL statement and reissue the statement. SQL 1026 1026 The selection expression on an SQL view has been violated. Cause.
File-System Messages SQL 1028 1028 The disk process accessed a label of an unexpected type during an OPEN or during an SQL label operation. Cause. An attempt was made to perform an SQL operation on an Enscribe file. An SQL operation must be made on an SQL object, such as a table, view, catalog table, or index. Effect. The operation fails. Recovery. Correct the statement to perform the operation on an SQL object, and reissue the statement.
File-System Messages SQL 1031 1031 A supplied numeric value exceeds the declared precision of the column, some of the supplied values for DECIMAL or VARCHAR columns are invalid, or the supplied row is too long. Also, the disk process might have encountered a bad column in a stored row or a value in an update on a row that would change the length of a VARCHAR column in an entry-sequenced table. Cause. Stated in the error message. Effect. The operation fails. Recovery.
File-System Messages SQL 1034 1034 SQL internal error: The requested operation has failed because of an inconsistency in specifying the SQL catalog. Cause. SQL internal error: Stated in the error message. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1035 1035 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1036 1036 SQL internal error. Cause.
File-System Messages SQL 1039 1039 An SQL UPDATE statement was attempted, but update intent was not specified when the cursor was declared. Cause. The requested update through the cursor is not allowed because the cursor was declared without the FOR UPDATE clause. Effect. The update operation fails. Recovery. Add the FOR UPDATE clause to the DECLARE CURSOR statement; then preprocess (SQL COBOL programs only), host-language compile, SQL compile, and run the program again.
File-System Messages SQL 1042 1042 The operation required a default value for a column that was defined as NO DEFAULT. Cause. The INSERT statement did not supply values for all columns. One of the omitted values was for a column that had no default value defined. Effect. The insert operation fails. Recovery. Correct the INSERT statement by adding a value for the column that has no defined default value. Then preprocess (SQL COBOL programs only), hostlanguage compile, SQL compile, and run the program again.
File-System Messages SQL 1046 1046 SQL internal error. Cause. Stated in the error message. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1047 1047 The SQL index being used is marked invalid because the catalog manager has not successfully loaded it. Cause. The SQL statement used an index that was not successfully loaded. Effect. The SQL statement fails. Recovery. Re-create the index, and reissue the statement. SQL 1048 1048 SQL internal error. Cause.
File-System Messages SQL 1051 1051 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1052 1052 A row was encountered that resides in a block having a data parity error. The row does not satisfy the WHERE clause. Cause. Stated in the error message. Effect. If a cursor is being used, the cursor position following statement execution is after the potentially bad row but before the next row. Recovery.
File-System Messages SQL 1054 1054 Unable to access a nonaudited table or protection view that has been altered by an uncommitted DDL statement. Cause. Stated in the error message. Effect. The statement fails. Recovery. Wait until the DDL statement completes and reissue the statement. SQL 1055 1055 Unable to perform a utility operation while an uncommitted DDL operation from another transaction exists. Cause. Stated in the error message. Effect. The statement fails. Recovery.
File-System Messages SQL 1058 1058 Unable to access a table that is being dropped by another user. Cause. Access to the table was not allowed because the table was being dropped. Effect. The operation fails. Recovery. Check with your system manager to determine which table you should be using. SQL 1059 1059 Unable to access a protection view whose underlying table does not exist or is inconsistent. Cause.
File-System Messages SQL 1062 1062 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1063 1063 SQL internal error. Cause. SQL internal error. Effect. The SQL operation fails. Recovery. None. Report the entire message to your service provider. SQL 1064 1064 SQL internal error. Cause. SQL internal error. Effect. The SQL operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1066 1066 Internal error: Occurred in OPEN. Cause. Stated in the error message. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1067 1067 Internal error: Occurred in the file system or disk process OPEN protocol. Cause. Stated in the error message. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1068 1068 SQL internal error. Cause. SQL internal error. Effect.
File-System Messages SQL 1070 1070 The process's program file is not licensed. Cause. The operation can only be performed by a program that is licensed. Effect. The operation fails. Recovery. Refer to the SQL/MP Installation and Management Guide for a list of the SQL components that must be licensed by using the FUP LICENSE command. SQL 1071 1071 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1075 1075 A FETCH was attempted following a FETCH that failed. This left the cursor in an undefined position. Cause. Stated in the error message. Effect. The FETCH or SELECT operation fails. Recovery. Correct the problem that caused the previous FETCH to fail, and reissue the command. SQL 1076 1076 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1079 1079 The requested key compression option is inconsistent with the data type, offset in row, or descending flag of some of the key columns. Cause. The ICOMPRESS or DCOMPRESS option was not allowed because of the definition of the key. Effect. Creation of the table or index fails. Recovery. Either remove the compression option from the CREATE statement or redefine the key. Try the create operation again.
File-System Messages SQL 1083 1083 An internal input SQL structure has an invalid format, as indicated by an incorrect EYE^CATCHER data item value. The program might have corrupted the SQL region or SQL executor segment, or an SQL internal error might have occurred. Cause. Stated in the error message. Effect. The operation fails. Recovery. Recompile the SQL program and verify that the program is not corrupting the SQL EXS extended segment (segment 2000).
File-System Messages SQL 1086 1086 Unable to unlock an SQL table that has locks through either STABLE ACCESS or REPEATABLE ACCESS. Cause. An attempt was made to use the UNLOCK TABLE statement on a nonaudited table when cursors holding locks on the table were open. Effect. The UNLOCK TABLE statement fails. Recovery. Correct the program to close cursors on the table with either a FREE RESOURCES statement or CLOSE statements before issuing an UNLOCK TABLE statement.
File-System Messages SQL 1090 1090 The requested SQL operation cannot be completed because of current limitations on message sizes. Cause. Stated in the error message. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1091 1091 The table or related index cannot be dropped until the NOPURGEUNTIL date. Cause. The date and time set in the NOPURGEUNTIL attribute for the table or a related index prevented the table from being dropped at an earlier time.
File-System Messages SQL 1093 1093 The operation cannot be performed because the resulting row would exceed the RECLENGTH value defined for the relative table. Cause. The new column could not be added because it would have increased the row length beyond the limit set by the RECLENGTH attribute for the table. Effect. The operation fails. Recovery.
File-System Messages SQL 1096 1096 The BLOCKSIZE value for this table is too small for the row length of the table. Cause. Stated in the error message. Effect. The table or index creation fails. Recovery. Correct the CREATE statement by increasing the value of BLOCKSIZE, and reissue the statement. SQL 1097 1097 Unable to access an object that is off-line or has an inconsistent definition. Cause.
File-System Messages SQL 1099 1099 The definitions of the table and/or index partitions are inconsistent, or the index label and corresponding underlying table values are inconsistent. Cause. A DDL or utility operation involving the partitioned table or the index label and underlying table did not complete successfully and left the partitions in an inconsistent state. Effect. The operation fails. Recovery. Use the TMF subsystem to recover the partitions or the index label and underlying table.
File-System Messages SQL 1103 1103 An underflow occurred during expression evaluation. Cause. Stated in the error message. Effect. The operation fails. Recovery. Correct the SQL statement or column values. SQL 1104 1104 An SQL column of type DECIMAL contained values that are not digits. Cause. Stated in the error message. Effect. The operation fails. Recovery. Recover the table using the TMF subsystem or SQL/MP. Contact your service provider for assistance.
File-System Messages SQL 1107 1107 Division by zero occurred during expression evaluation. Cause. Stated in the error message. Effect. The operation fails. Recovery. Verify that the row producing the zero value is not used in this operation. SQL 1108 1108 Data type of column not supported by this release. Cause. The table contained a data type that is not supported by this release of SQL. Effect. The operation fails. Recovery.
File-System Messages SQL 1111 1111 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1112 1112 Arithmetic operation was requested in an unexpected unsigned data type. Cause. The program might have corrupted the SQL region or SQL executor segment, or an SQL internal error might have occurred. Effect. The operation fails. Recovery.
File-System Messages SQL 1115 1115 A specified SYSKEY value exceeds the current defined size of the relative SQL table. Cause. Stated in the error message. Effect. The INSERT statement fails. Recovery. Decrease the value specified for SYSKEY and reissue the statement. Alternatively, request that the owner of the table alter the table to increase its space so that the key value would be within the table, and reissue the request.
File-System Messages SQL 1118 1118 The specified view is not defined. Cause. The view cannot be altered or dropped because one of the indexes defined on the underlying table does not have a consistent description of the view. Effect. The DDL statement fails. Recovery. Use the VERIFY statement to identify the inconsistencies in the underlying table's definition. Contact your SQL/MP system manager about repairing the dictionary. For more information, refer to the SQL/MP Installation and Management Guide.
File-System Messages SQL 1121 1121 This error message has two possible causes. 1) A remote user specified local-only authority in the SECURE attribute for the object being created or altered. 2) The SECURE attribute did not grant read authority to all users being granted write authority. Cause. Stated in the error message. Effect. The CREATE or ALTER operation on the object fails. Recovery.
File-System Messages SQL 1125 1125 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1126 1126 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1127 1127 Unable to update an SQL catalog table from a process that is not licensed. Cause.
File-System Messages SQL 1129 1129 Scale truncation was needed but prohibited during expression evaluation. Cause. The scale of the target buffer is less than the scale of the source buffer. Effect. The operation fails. Recovery. Check your data and/or scale of your data buffers. SQL 1130 1130 Unable to use NonStop SQL/MP on a system where the product is not installed. Cause. Stated in the error message. Effect. The operation fails. Recovery. Install SQL/MP.
File-System Messages SQL 1137 1137 The supplied key for the new partition is already defined at the existing partitions. Cause. The FIRST KEY value duplicated the key value of a partition already defined for the table. Effect. The DDL statement fails. Recovery. Change the value of the FIRST KEY, and reissue the statement. SQL 1138 1138 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1141 1141 Incorrect syntax for date-time or INTERVAL value. Cause. The date-time or INTERVAL value contained in the expression has incorrect syntax. Effect. The operation fails. Recovery. Correct the syntax for the date-time or INTERVAL value in the expression that has incorrect syntax. SQL 1142 1142 Either the program needs to be recompiled using the latest SQL compiler or an SQL internal error has occurred. Cause. The error message states the cause. Effect. The operation fails.
File-System Messages SQL 1145 1145 SQL internal error. Cause. An SQL internal error occurred. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1146 1146 File system received an unexpected reply to an SQL open request. Cause. SQL internal error. An SQL file open request failed due to an unexpected response from the disk process. Effect. The open of the SQL file fails. Input and output operations directed against the file cannot be performed. Recovery.
File-System Messages SQL 1149 1149 The version of character processing rules object is no longer supported. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1150 1150 The encoded string will not fit in the supplied buffer. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1153 1153 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1154 1154 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1155 1155 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
File-System Messages SQL 1158 1158 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1159 1159 Attempted to add a new partition before the primary partition. Cause. Stated in the error message. Effect. The operation fails. Recovery. Change your DDL statement. SQL 1160 1160 SQL internal error. Cause. SQL internal error. Effect. The operation fails. Recovery. None.
File-System Messages SQL 1163 1163 Illegal operation attempted on a file having a system reserved filename. Cause. There are several system reserved filenames for internal use only. Any attempt to create, purge, rename, alter, or otherwise modify these files results in error 1163. Some of the reserved filename templates are (“*” is the wildcard): volume.subvolume.ZZIV* volume.ZTMFAT.filename volume.ZX0*.filename volume.ZYQ*.filename volume.ZYS*.filename volume.ZYTX*.
File-System Messages SQL 1166 1166 Bad aggregate composite expression. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1167 1167 The object SQL version is higher than the SQL version of the system where the request is issued. Cause. Access of an SQL object from an earlier version of SQL/MP was attempted and the object contains a feature that is not supported by the earlier version of SQL/MP. Effect. The operation fails.
File-System Messages SQL 1170 1170 HLSQLV of the SQL expression is not compatible with the system. Cause. SQL internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 1171 1171 The number of message bytes exchanged between the file system and the disk process has exceeded the highest limit (2147479551). Cause. Either an SQL internal error occurred or the referenced SQL object contains inconsistent data. Effect. The operation fails. Recovery.
File-System Messages SQL 1186 1186 An inconsistency is detected between the rows of the table and the index. Cause. The index has rows which are absent in the table causing the inconsistency. Effect. The execution plans which do an index scan followed by a table scan can fail during execution. Recovery. Correct the inconsistency, either by undoing the operation which caused the inconsistency, or by recreating the index if the table has the correct data.
17 EMS 512 Messages Event Management Service (EMS) messages issued with the number 512 indicate a message written to $0 as text, but not in EMS format. These messages can come from the following SQL/MP components: • • • • • • Conversational interface (SQLCI) Catalog manager Executor SQL COBOL85 preprocessor SQL compiler (SQLCOMP) SQL file system Some messages have file-system errors associated with them. Refer to Section 16, File-System Messages for a definition of the specified error.
SQL Conversational Interface (SQLCI) EMS 512 Messages is the program file name of the SQLCI process (usually $SYSTEM.SYSTEM.SQLCI). Cause. A trap occurred in the SQL conversational interface (SQLCI) process. Effect. If the write of the first (#1) message to $0 is successful and the SQLCI internal structures are not corrupted, SQLCI sends a second (#2) message to $0. If SQLCI cannot send the second message, it abends. Recovery. None.
SQL Conversational Interface (SQLCI) EMS 512 Messages SQLCI 3 512 SQLCI #3 Version: vv Type: tt Text: request vv is the two-digit SQL version number. tt is the two-digit SQL request type. request is the SQL request that SQLCI was processing. If the request is longer than 64 bytes, SQLCI truncates the value in request. Cause. After a trap occurred, SQLCI successfully sent the first (#1) and second (#2) messages to $0. Effect.
SQL Catalog Manager EMS 512 Messages • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a CPU dump if applicable • Your system number and the numbers and versions of all related products SQL Catalog Manager SQL Catalog Manager 1 512 SQL CAT #1 S: %ssssss P: %pppppp E: %eeeeee L: %llllll Trap # tt Running: program-name ssssss is the contents of the stack (S) register in octal. pppppp is the contents of the program (P) register in octal.
SQL Catalog Manager EMS 512 Messages • Your system number and the numbers and versions of all related products SQL Catalog Manager 2 512 SQL CAT #2 Location: symbolic-address symbolic-address is the symbolic representation of the address where the trap occurred. Cause. After a trap occurred, SQLCAT successfully sent the first (#1) message to $0. Effect.
SQL Executor EMS 512 Messages Recovery. None.
SQL Executor EMS 512 Messages ii is the two-digit octal index that specifies the segment in the code space represented by cc. program is the program file name of the executor process (usually $SYSTEM.SYSTEM.EXECUTOR). Cause. A trap occurred in the SQL executor process. Effect. If the write of the first (#1) message to $0 is successful and the executor internal structures are not corrupted, the executor sends a second (#2) message to $0. If the executor cannot send the second message, it abends. Recovery.
SQL Executor EMS 512 Messages dd is the type in decimal of the statement (for a Data Manipulation Language (DML) request only). Cause. After a trap occurred, the executor successfully sent the first (#1) message to $0. Effect. If the write of the second (#2) message to $0 is successful and the executor internal structures are not corrupted, the executor sends a third (#3) message to $0. If the executor cannot send the third message, it abends. Recovery. None.
SQL COBOL85 Preprocessor EMS 512 Messages vvvvvvvv is the value of the TNS/R virtual frame pointer (VFP) in hexadecimal at the time of the trap. ssssssss is the value of the stack pointer in hexadecimal at the time of the trap. Cause. After a trap occurred, the executor successfully sent the first (#1) and second (#2) messages to $0. Effect. The executor abends. Recovery. None.
SQL COBOL85 Preprocessor EMS 512 Messages eeeeee is the contents of the environment (E) register in octal. llllll is the contents of the local (L) register in octal. tt is the NonStop operating system trap number in decimal. program is the name of the source file that SQLCOBOL was processing. Cause. A trap occurred in the SQL COBOL preprocessor (SQLCOBOL). Effect.
SQL Compiler (SQLCOMP) EMS 512 Messages 06 Extended-Storage Section 07 Linkage Section 08 Procedure Division nn is the two-digit decimal value indicating the nesting level of the COBOL program. procedure is the name of the COBOL procedure that the preprocessor was processing. statement is the SQL source statement that the preprocessor was processing. If the source statement is longer than 70 bytes, the preprocessor truncates the value in statement. Cause.
SQL Compiler (SQLCOMP) EMS 512 Messages eeeeee is the contents of the environment (E) register in octal. llllll is the contents of the local (L) register in octal. tt is the NonStop operating system trap number in decimal. cc is the code space for the SQLCOMP process; cc can have these values: UC User code space UL User library code space SC System code space SL System library code space ii is the two-digit octal index that specifies the segment in the code space represented by cc.
SQL Compiler (SQLCOMP) EMS 512 Messages SQL Compiler 2 512 SQL COMP #2 ss mm iiii pppp statement ss is the two-digit decimal value indicating the current SQL compilation state or type; ss can have these values: 05 SQL compiler was compiling a static statement. 06 SQL compiler was compiling a dynamic statement. mm is the two-digit decimal value indicating the SQL compilation mode; mm can have these values: 10 SQL compiler was idle. 11 SQL compiler was compiling a statement.
SQL Compiler (SQLCOMP) EMS 512 Messages SQL Compiler 3 512 86 SQLCOMP event-type date-time [ program-name ] PID=pid [ E=sql-msg ] [ FS=file-system-msg ] event-type is the type of recompilation; event-type can have these values: PROG Automatic recompilation of an SQL program STMT Recompilation of a single SQL statement date-time is the date and time when the event message is generated. program-name is the name of the host language program that is recompiled.
SQL File System EMS 512 Messages SQL File System 512 SQL FILSYS TRAP %tt - P=%pppppp E=%eeeeee L=%llllll tt is the NonStop operating system trap number in octal (for example, 03 for a stack overflow). pppppp is the contents of the program (P) register in octal. eeeeee is the contents of the environment (E) register in octal. 111111 is the contents of the local (L) register in octal. Cause. A trap occurred in the SQL file system. Recovery. None.
SQL File System EMS 512 Messages ssssssss is the contents of the stack pointer in octal. Cause. A trap occurred in the SQL file system of a TNS/R system. Recovery. None. Report the entire message to your service provider, along with the following information: • • • • The values of each message field. The name of the application that abended and the SAVEABEND file, if one was created.
18 Audit Fix-Up EMS Messages Event Management Service (EMS) messages are issued by the audit fix-up (ZAUD) subsystem and are written to $0 or to a specified alternate collector. These messages can come from the following SQL/MP components: • • Catalog manager Audit fix-up processes These messages are informational messages. They report the progress of DDL statements invoked using the WITH SHARED ACCESS option.
Audit Fix-Up EMS Messages aud^recs^read is a running total of the number of audit records read during the audit fix-up operation. aud^recs^redo is a running total of the number of audit records queued for redo during the audit fix-up operation. aud^read^rate is the rate in bytes per second that audit records were read from the audit trail during the last reporting period. aud^redo^rate is the rate in bytes per second that audit records were queued for redo during the last reporting period.
Audit Fix-Up EMS Messages 3 Audit fix-up process aud-num started aud-num is the ordinal position of an audit fix-up request. Several audit fix-up requests can be made through the execution of an operation that uses WITH SHARED ACCESS. There are always at least two requests. Cause. An audit fix-up application request was made. Effect. The audit fix-up process has been started. Recovery. Informational message only; no corrective action is needed.
Audit Fix-Up EMS Messages 6 Cannot report events to collector collector is the name of the Event Management Service (EMS) collector that was unavailable. Cause. The local primary collector received a message that the requested remote primary collector or alternate collector is not available. Effect. Messages are no longer sent to the requested alternate collector. Recovery. Check to make sure the collector is functioning properly.
19 ZSQL EMS Messages Event Management Service (EMS) messages issued by the ZSQL subsystem are written to $0 or a specified alternate collector. These messages come from the SQL/MP Catalog Manager. These messages are informational messages and describe the progress of DDL statements invoked using the WITH SHARED ACCESS option. EMS 1 1 op^type command started op^type is the name of the operation as specified in the NAME option of the statement that started the operation. Effect.
ZSQL EMS Messages EMS 3 3 All target partitions have been created Time to create targets: interval secs interval is the interval since the last message for the request was processed. Cause. All target-partitions have been created. Effect. The newly created partitions can be loaded with data. Recovery. Informational message only; no corrective action is needed. EMS 4 4 Data Copy Started Cause. The data copy operation has started. Effect.
ZSQL EMS Messages EMS 6 6 Data Copy Completed Time since last status: interval secs [Total records copied : recs-read recs] interval is the interval since the last message for the request was processed. recs-read is a running count of the number of records read during the load phase. Cause. The data copy operation has finished. (Some SQL DDL requests, such as the CREATE INDEX statement, do not generate the optional portion of the message.) Effect.
ZSQL EMS Messages EMS 9 9 Commit phase has begun Cause. The commit phase for the SQL operation has started. Effect. The SQL DDL operation now requires exclusive access to all source and target partitions. Recovery. Informational message only; no corrective action is needed. EMS 10 10 File lock requested for partition: Time since last event interval secs source-file source-file is the name of the partition that requires the lock.
ZSQL EMS Messages EMS 12 12 All partition labels have been updated Time since last event interval secs interval is the interval since the last message for the request was processed. Cause. All partition labels affected by the operation have been updated. Effect. None. Recovery. Informational message only; no corrective action is needed. EMS 16 16 op^type command has completed op^type is the name of the operation as specified in the NAME option of the statement that started the operation. Cause.
ZSQL EMS Messages Effect. All resources in use have been freed. Recovery. Refer to the SQL/MP Messages Manual or use the ERROR command in SQLCI to determine the appropriate recovery for the SQLCODE value. Correct the SQL error and reissue the request. EMS 18 18 Cannot report events to collector collector is the name of the Event Management Service (EMS) collector that was unavailable. Cause. The specified alternate collector is not available. Effect.
20 Collation Compiler Messages This section describes the error messages that can be displayed by the collation compiler. The collation compiler is the component of SQL/MP evoked by the CREATE COLLATION command. Collation Compiler 11 11 Logic error number. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 12 12 Invalid command line parameters; semicolon expected after object file name.
Collation Compiler Messages Collation Compiler 14 14 Invalid command line parameter parameter. Cause. The indicated parameter entered on the command line is not recognized. Effect. The indicated parameter and any parameters following it are ignored. Recovery. This message appears at the bottom of the compile listing and documents the parameters used for the compile. Informational message only; no corrective action is needed.
Collation Compiler Messages Collation Compiler 19 19 The listing file is of an unsupported type. Cause. The listing file specified on the command line (the OUT parameter) must be either an Edit file or a nondisk file. This message is written to the STDERR file, which will be the operator's home terminal, unless output has been redirected by an ASSIGN statement to a destination other than STDERR. Effect. The compiler process terminates. Recovery.
Collation Compiler Messages Collation Compiler 30 30 Bad production number encountered during parse. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 31 31 Bad stack length encountered during parse. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider.
Collation Compiler Messages Collation Compiler 43 43 At least one illegal character encountered from above line. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 44 44 String not terminated before end-of-line. Cause. Strings must begin and end on the same line. Effect.
Collation Compiler Messages Collation Compiler 48 48 String too long; truncated to number characters. Cause. An unusually long string was encountered. This error might be caused by missing quotes. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Check the source file and rerun the collation compiler. Collation Compiler 49 49 Identifier too long; truncated to number characters. Cause. An unusually long identifier was encountered. Effect.
Collation Compiler Messages Collation Compiler 54 54 Duplicated definition of the 'escape_char' clause. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 55 55 A CHARNAME is expected for either a "comment_char" or a "escape_char" clause. Cause. You did not specify the escape or comment character in angle brackets as required. Effect.
Collation Compiler Messages Collation Compiler 58 58 Cannot redefine the default comment character to an escape character. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 59 59 Cannot redefine the default escape character to a comment character. Cause. Stated in the error message. Effect.
Collation Compiler Messages Collation Compiler 70 70 Too many character classes defined. Cause. The compiler supports up to 100 character classes, including the default 'alphas' and 'numerics' character classes. Effect. The compiler process terminates. Recovery. Remove some character classes and rerun. Collation Compiler 71 71 Too many character classes defined. Cause. The compiler supports up to 100 character classes, including the default 'alphas' and 'numerics' character classes. Effect.
Collation Compiler Messages Collation Compiler 74 74 Character processing rules definition too large - node resource exhausted. Cause. The compiler ran out of storage to store parse tree nodes. Effect. The compiler process terminates. Recovery. Reduce the number of items in the source and rerun the collation compiler. Collation Compiler 75 75 Bad node reference detected. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None.
Collation Compiler Messages Collation Compiler 78 78 Name reference error detected. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 79 79 Scope table overflow. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 80 80 Scope table underflow. Cause.
Collation Compiler Messages Collation Compiler 82 82 Logic error number detected during tree construction. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 83 83 Bad tree structure detected. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider.
Collation Compiler Messages Collation Compiler 87 87 SQL error number on describe of object table. Cause. An SQL error was encountered as specified by number. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. See the appropriate error section in this manual for more information. Collation Compiler 88 88 Structure in SQL object table is incorrect. Cause.
Collation Compiler Messages Collation Compiler 92 92 Object file name filename is invalid. Cause. The object file name is not a syntactically correct disk file name. This error can only occur when the collation compiler is evoked from outside the SQL environment. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the name and rerun the compiler. Collation Compiler 93 93 FILEINFO on object file failed with error code number. Cause.
Collation Compiler Messages Collation Compiler 95 95 Attempt to create object file failed with error code number. Cause. The compiler attempts to create the object file, but the operation fails with the Guardian error indicated by number. This error can only occur when the collation compiler is evoked from outside the SQL environment. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery.
Collation Compiler Messages Collation Compiler 2002 2002 Shift of character to itself ignored. Cause. A pair in the TOUPPER clause specified the same character as both the uppercase character and the lowercase character. Effect. This pair is ignored and processing continues. Recovery. Informational message only; no corrective action is needed. Collation Compiler 2003 2003 This character previously defined as lowercase. Cause.
Collation Compiler Messages Collation Compiler 2006 2006 This character previously occurs in the LC_COLLATE clause. Cause. A character can only appear once in the LC_COLLATE clause. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 2007 2007 This character previously occurs in the LC_COLLATE clause. Cause. A character can only appear once in the LC_COLLATE clause. Effect.
Collation Compiler Messages Collation Compiler 2010 2010 Only 1 or 2 characters allowed in this string. Cause. Strings appearing in the indicated context can only have one or two characters. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 2011 2011 This character appears twice in the LC_COLLATE clause. Cause. A character may appear only once in the LC_COLLATE clause.
Collation Compiler Messages Collation Compiler 2015 2015 The first character in this range is greater than the last. Cause. The beginning character of a range must have a lower character code than the ending character. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 2016 2016 This pair's weight is inconsistent with a preceding pair. Cause.
Collation Compiler Messages Collation Compiler 2018 2018 Unsupported character set. Cause. The given character set is not supported by this release of the collation compiler. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Specify a different character set in the source file and rerun the collation compiler. Collation Compiler 2019 2019 A pair may not be made equivalent to a single character. Cause.
Collation Compiler Messages Collation Compiler 2022 2022 A pair may not be less than every character. Cause. A collating element of two characters used in the LC_COLLATE clause precedes all single characters. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 2023 2023 A pair may not be greater than every character. Cause.
Collation Compiler Messages Collation Compiler 2081 2081 Bad string error number. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 3000 3000 The first character in this collating-element or string is equal to the space character. Cause. The space character (or a character equivalent to the space character) cannot appear as the first character in a two-character string. Effect.
Collation Compiler Messages Collation Compiler 4000 4000 Cannot produce encoding tables; too many elements in the LC_COLLATE clause. Cause. The source contains too many elements in the LC_COLLATE clause. The compiler is unable to generate a length-preserving encoding. The approximate limitation can be expressed algebraically. Consider these variables: • • • Let x equal the number of items in the LC_COLLATE clause that do not have weights specified or that have themselves specified as their weight.
Collation Compiler Messages Collation Compiler 5080 5080 Logic error number. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 5081 5081 Bad string error number. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider.
Collation Compiler Messages Collation Compiler 10020 10020 Bad string error number. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 10021 10021 Logic error 1. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 10022 10022 Logic error 2. Cause.
Collation Compiler Messages Collation Compiler 10025 10025 Logic error 5. Cause. Collation compiler internal error. Effect. The compiler process terminates. Recovery. None. Report the entire message to your service provider. Collation Compiler 10026 10026 The collation definition is too complex. size limit was exceeded. An internal Cause. Stated in the error message Effect. The compiler process terminates. Recovery. Correct the source file and rerun the collation compiler.
Collation Compiler Messages Collation Compiler 10051 10051 Duplicated "LC_COLLATE" definition. Cause. Only one LC_COLLATE definition is allowed. Effect. The compiler process terminates. Recovery. Remove the duplicate LC_COLLATE definition and rerun the collation compiler. Collation Compiler 10052 10052 Duplicated "LC_CTYPE" definition. Cause. Only one LC_CTYPE definition is allowed. Effect. The compiler process terminates. Recovery.
Collation Compiler Messages Collation Compiler 10102 10102 An ellipsis collation element must be specified in a pair of char_symbols. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 10103 10103 Elem-list cannot be specified with an ellipsis. Cause. You used an ellipsis in the collating element clause. Effect.
Collation Compiler Messages Collation Compiler 10106 10106 The weight symbol must be defined as a collation element before referenced. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 10107 10107 Duplicated collation element definition. Cause. Stated in the error message. Effect.
Collation Compiler Messages Collation Compiler 10110 10110 A COLLELEMENT must be defined in a "collating-element" clause before used. Cause. You referred to a collating element that has not been defined in a collating clause. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 10111 10111 UNDEFINED IGNORE must be specified at the end of collation definition. Cause.
Collation Compiler Messages Collation Compiler 10114 10114 Duplicated character class keyword. Cause. Stated in the error message. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 10115 10115 This keyword must be defined first in the "charclass" clause. Cause. Stated in the error message. Effect.
Collation Compiler Messages Collation Compiler 10121 10121 Each element for an elem-list must be a char_symbol. Cause. Each element that makes up a new element must be a “char” symbol. Effect. The compilation terminates after completing the phase in which the error is discovered. Recovery. Correct the source file and rerun the collation compiler. Collation Compiler 10122 10122 A COLLELEMENT must contain a stream of two or more characters (or integers). Cause.
21 FastSort Messages FastSort 1 1 The 'CTLBLOCK' parameter to SORTMERGESTART is required. Cause. The call to SORTMERGESTART did not specify a control block. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Specify the ctlblock parameter and reissue your request. FastSort 2 2 The 'KEYS' parameter to SORTMERGESTART is required. Cause. The call to SORTMERGESTART did not define any key fields. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages FastSort 4 4 An error has prevented creation of the sort process. Cause. The SORTPROG program name is incorrect, or some condition in the system caused the error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. If the SORTPROG program name is incorrect, change the SORT DEFINE PROGRAM attribute to specify the correct program name.
FastSort Messages FastSort 7 7 SORTMERGESEND has been called unexpectedly. Cause. The calling process called SORTMERGESEND at the wrong time. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Correct your program logic. For more information on the normal order of FastSort procedures, refer to the FastSort Manual. FastSort 8 8 SORTMERGERECEIVE has been called unexpectedly. Cause. The calling process called SORTMERGERECEIVE at the wrong time. Effect.
FastSort Messages FastSort 11 11 The free list file cannot be opened. Cause. SORTPROG could not open or create its free-list file, a second scratch file that FastSort sometimes creates for internal memory management. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code.
FastSort Messages FastSort 15 15 Files to be merged must be sorted. Cause. The data in one or more files specified for merging was not in sorted order. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Check your files to see which ones are not sorted, and specify sorting before merging for those files. FastSort 20 20 Communications with SORTPROG have broken down. Cause. Some condition in the system halted communications. Effect.
FastSort Messages FastSort 23 23 The FROM file could not be opened. Cause. SORTPROG could not open one of the input files. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code. FastSort 24 24 A temporary TO file is too small. Cause.
FastSort Messages FastSort 27 27 The TO file already exists and cannot be purged. Cause. The specified output file exists but is too small or has a wrong type. SORTPROG cannot purge the file and create a new one because of the file's security, current usage, or some other condition in the system. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages FastSort 30 30 A write has failed to a SCRATCH file. Cause. SORTPROG could not write to a scratch file, either because you underestimated the number of input records or because of a disk process or data flow problem. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Ensure that sufficient scratch space exists for the sort. SORTPROG might require more overflow scratch space. For more information on scratch files, refer to the FastSort Manual.
FastSort Messages FastSort 33 33 A CONTROL operation has failed. Cause. A control operation on the output file or on a scratch file failed. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code. FastSort 34 34 An EDITREAD has failed from the FROM file. Cause. FastSort could not read an EDIT input file. Effect.
FastSort Messages FastSort 37 37 Creation of the TO file has faileD. Cause. FastSort could not create the output file. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code. FastSort 38 38 The TO file could not be opened. Cause. FastSort could not open the output file. Effect.
FastSort Messages FastSort 41 41 CONFIGURATION PROBLEM: No SHORTPOOL. Cause. You did not specify SHORTPOOL. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Correct the syntax and resubmit. FastSort 42 42 The MEM size must be in the range 1 TO 64. Cause. The value of the memory parameter was incorrect in the call to SORTMERGESTART. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages FastSort 45 45 Invalid SCRATCH file block size. Cause. The SORT DEFINE BLOCK attribute specifies an invalid scratch file block size. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Change the SORT DEFINE BLOCK attribute to specify a block size in the range of 512 to 4096 for remote or partitioned scratch files or in the range of 512 to 30,720 for local nonpartitioned files. FastSort 46 46 Real number keys must be word aligned. Cause.
FastSort Messages FastSort 49 49 Invalid exclusion mode specified. Cause. An exclusion mode specified in the call to SORTMERGESTART was invalid. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Change the value of the in-file-exclusion-mode or out-file-exclusion-mode parameter. For more information on the descriptions of these parameters under the SORTMERGESTART procedure, refer to the FastSort Manual. FastSort 50 50 EDIT files may not be TO files. Cause.
FastSort Messages FastSort 53 53 A TO file may not be a file to be merged. Cause. The name of the output file is the same as the name of a merge file. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Change the output file name or the merge file name. FastSort 54 54 Invalid SCRATCH file name. Cause.
FastSort Messages FastSort 57 57 Collating sequence table must be present. Cause. The call to SORTMERGESTART specified translation, but the alternate collating sequence table was missing. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Set flags .10:10 to 0 or provide an alternate collating sequence table. For more information on the description of the flags parameter under the SORTMERGESTART procedure, refer to the FastSort Manual.
FastSort Messages • • When you run the program, specify 64 for the MEM option of the RUN command. If you run the program from another application, specify 64 for the PROCESS_CREATE_ or NEWPROCESS[NOWAIT] memory-pages parameter. Move user data from the user data segment to an extended data segment to free up more data stack space for the call to SORTMERGESTART. FastSort 61 61 Spare parameters may not be present. Cause.
FastSort Messages FastSort 64 64 Extended segment cannot be allocated. Cause. FastSort could not allocate an extended memory segment for a sort or subsort process. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code.
FastSort Messages FastSort 67 67 Invalid index SLACK specified. Cause. The data slack value in the call to SORTMERGESTART was outside the limits for the value. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Change the dslack parameter. For more information on the description of dslack under the SORTMERGESTART procedure, refer to the FastSort Manual. FastSort 68 68 Invalid new flag specified. Cause. The flags2 value in the call to SORTMERGESTART was not valid. Effect.
FastSort Messages FastSort 72 72 Invalid extended segment size. Cause. The extended segment size specified in the call to SORTMERGESTART was out of limits. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Correct the segment value in the process-start parameter. For more information on the description of process-start under the SORTMERGESTART procedure, refer to the FastSort Manual. FastSort 73 73 Invalid format of the process structure. Cause.
FastSort Messages FastSort 75 75 Invalid block length specified. Cause. The block buffer length specified in the call to SORTBUILDPARM was outside the limits. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Correct the value of the buffer-length parameter. For more information on the description of buffer-length under the SORTBUILDPARM procedure, refer to the FastSort Manual. FastSort 76 76 Start of subsort process has failed. Cause.
FastSort Messages FastSort 78 78 Communications with subsort process have failed. Cause. The distributor-collector process could not communicate with a subsort process. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Follow recovery recommendations in the Guardian Procedure Errors and Messages Manual for the operating system error code returned with this FastSort error code. FastSort 79 79 Parameters are mutually exclusive. Cause.
FastSort Messages FastSort 82 82 More than one SUBSORT should be specified. Cause. Only one subsort process was specified for a parallel sort run. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Specify at least two subsort processes. FastSort 83 83 SORTPROG and SORT library versions do not agree. Cause. Your system has components of both SORT and FastSort installed. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages FastSort 86 86 Invalid object specified as TO file. Cause. The output file is an SQL object. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. The TO file cannot be an SQL object. Specify a file other than an SQL object for the TO file. FastSort 87 87 Invalid object specified as FROM file. Cause. A FROM file is an SQL object. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. The FROM file cannot be an SQL object.
FastSort Messages FastSort 90 90 Unexpected return from LOADOPEN procedure. Cause. A programming error occurred on a call to an internal procedure. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Report the internal error number returned with this FastSort error code to your service provider. The high-order word of the error-code parameter returned by SORTERRORSUM and SORTERRORDETAIL contains the internal error number.
FastSort Messages FastSort 94 94 Unexpected return from SQL LOADOPEN procedure. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Report the entire message to your service provider. FastSort 95 95 Unexpected return from SQL LOADWRITE procedure. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Report the entire message to your service provider.
FastSort Messages FastSort 99 99 Default DEFINE is not of class SORT. Cause. A DEFINE with the reserved name = _SORT_DEFAULTS was created, but is not of class SORT. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Delete the DEFINE. If you want to specify default SORT DEFINE attributes, re-create the DEFINE as a SORT DEFINE. FastSort 100 100 SORTPROG must be SQL licensed. Cause. SORTPROG has not been SQL licensed. Effect.
FastSort Messages FastSort 103 103 User-specified DEFINE is not of class SORT. Cause. The DEFINE CLASS must be SORT. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Specify CLASS SORT in your SORT DEFINEs. FastSort 104 104 Error occurred while accessing a SORT DEFINE. Cause. An unacceptable DEFINE name was encountered, an attribute was missing, or an error was returned from a procedure call. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages FastSort 107 107 Error occurred while accessing a subsort define. Cause. An unacceptable DEFINE name was encountered, an attribute was missing, or an error was returned from a procedure call. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Ensure that a valid DEFINE name was specified. FastSort 108 108 Invalid DM block FORMAT for SORTMERGESQL. Cause. A programming error occurred on a call to an internal procedure. Effect.
FastSort Messages FastSort 111 111 SORTMERGESQL called unexpectedly. Cause. A programming error occurred on a call to an internal procedure. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 112 112 Error from SQL filesystem validations routines. Cause. A programming error occurred on a call to an internal procedure. Effect.
FastSort Messages FastSort 115 115 Error retrieving SQL file label. Cause. A programming error occurred on a call to an internal procedure. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 116 116 Only one file can be sorted via SORTMERGESQL. Cause. A programming error occurred on a call to an internal procedure. Effect.
FastSort Messages FastSort 119 119 Internal SQL null error. Cause. A programming error occurred on a call to an internal procedure. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 120 120 SQL Bulk IO not valid for specified input file. Cause. A programming error occurred on a call to an internal procedure. Effect.
FastSort Messages resolve the problem, generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 123 123 Datetime conversion field not found. Cause. A date-time field was specified as needing date-time conversion, but no datetime field was found. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. If you have written your own application, change the sort key values to valid field types.
FastSort Messages FastSort 126 126 Process already open and SORTPROC_OPEN_ called. Cause. A programming error occurred on a call to an internal procedure. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 127 127 Send message ID mismatch. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None.
FastSort Messages FastSort 130 130 Internal sort error. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 131 131 Missing or conflicting parameters in SORTLIB call. Cause. Stated in the error message. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages the Guardian Procedure Errors and Messages Manual for the file-system error code returned with the FastSort error code. FastSort 134 134 Invalid RECGEN startup message. Cause. Stated in the error message. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Check that the versions of RECGEN and SQLUTIL are compatible. If the base table was in use when FastSort returned this error, ensure that the base table is not in use and try to re-create the index.
FastSort Messages FastSort 137 137 RECGEN internal error: Keys out of order. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 138 138 Invalid to-file specified to RECGEN Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None.
FastSort Messages FastSort 141 141 Non-existent RECGEN TO-FILE specified. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 142 142 RECGEN unable to open base table. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery.
FastSort Messages save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 145 145 RECGEN error while packing record. Cause. Internal error. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. None. Generate and save a copy of your SAVEABEND file and report the entire message to your service provider. FastSort 146 146 RECGEN error while retrieving primary key. Cause. Internal error. Effect.
FastSort Messages FastSort 149 149 RECGEN calculates a bad multiple message address. Cause. Stated in the error message. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Check that the versions of RECGEN and SQLUTIL are compatible. If the base table was in use when FastSort returned this error, ensure that the base table is not in use and try to re-create the index. If this strategy fails to solve the problem, generate and save a copy of your SAVEABEND file.
FastSort Messages FastSort 153 153 UPS not supported in this environmenT. Cause. UPS cannot be used if subsorts are used, if the number of records to be sorted is greater than 32,767, or if the multiple openers feature is being used. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Check to see if any of the above conditions are true, and correct the condition. FastSort 154 154 UPS workspace bad. Cause. The eye-catcher field in the UPS workspace is corrupted. Effect.
FastSort Messages FastSort 161 161 Process create library file error. Cause. A PROCESS_CREATE_ error occurred on the library file parameter. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. For the programmatic interface, call the SORTERRORDETAIL or SORTERRORSUM procedure to determine the error code. For the interactive interface, the error parameter in the accompanying message identifies the error code.
FastSort Messages FastSort 164 164 Process create data segment error. Cause. A PROCESS_CREATE_ error occurred for the process file segment (PFS). Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. For the programmatic interface, call the SORTERRORDETAIL or SORTERRORSUM procedure to determine the error code. For the interactive interface, the error parameter in the accompanying message identifies the error code.
FastSort Messages FastSort 167 167 Process create library file format error. Cause. A PROCESS_CREATE_ error occurred because a library file has an invalid format. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. For the programmatic interface, call the SORTERRORDETAIL or SORTERRORSUM procedure to determine the error code. For the interactive interface, the error parameter in the accompanying message identifies the error code.
FastSort Messages FastSort 171 171 Extended segment cannot be deallocated. Cause. The SORTPROG process encountered an error while trying to deallocate its extended segment. Effect. None; the problem occurs at process termination time. Recovery. No recovery is necessary. However, service provider you should report this error to your service provider. FastSort 172 172 SORTPROG version too old; cannot support required new feature. Cause.
FastSort Messages FastSort 175 175 Invalid monitor message length. Cause. Your system’s version of SORTPROG is earlier than the FastSort system library procedures. Effect. The SQL DDL or DML operation in progress terminates abnormally. Recovery. Contact your system manager or service provider to have the correct version of FastSort or the operating system installed on your system. FastSort 176 176 SORTPROG version too old; cannot support optional openon-demand feature. Cause.
FastSort Messages HP NonStop SQL/MP Messages Manual—427720-006 21 -46
