HP NonStop SQL/MX Release 3.1 Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MX relational database management system and its associated subsystems. Product Version NonStop SQL/MX Release 3.1 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.23 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications.
Document History Part Number Product Version Published 640324-001 NonStop SQL/MX Release 3.0 February 2011 663849-001 NonStop SQL/MX Release 3.
Legal Notices Copyright 2011 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop SQL/MX Release 3.1 Messages Manual Tables Legal Notices What’s New in This Manual v Manual Information v New and Changed Information About This Manual xi Audience xi Related Documentation xi Notation Conventions xiv HP Encourages Your Comments v xvi 1.
2. General Messages (0 through 999) Contents 2. General Messages (0 through 999) 3. Data Definition Language (DDL) Messages (1000 through 1999) 4. SQL/MX MXCMP Messages (2000 through 2999) 5. Parser and Compilation Messages (3000 through 3999) 6. Binder and Compilation Messages (4000 through 4999) 7. Normalizer Messages (5000 through 5999) 8. Optimizer Messages (6000 through 6999) 9. Generator Messages (7000 through 7999) 10. Executor Messages (8000 through 8999) 11.
13. Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Contents 13. Trigger, UDR Server, and Language Manager Messages (11000 through 11399) 14. SQLC and SQLCO Preprocessor Messages (13000 through 13999) 15. MXCI Messages (15000 through 15999) 16. Messages Generated by the Message System (16000 through 16999) 17. Internal Stored Procedures Messages (19000 through 19999) 18. Utility Messages (20000 through 23099) 19.
Contents HP NonStop SQL/MX Release 3.
What’s New in This Manual Manual Information HP NonStop SQL/MX Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MX relational database management system and its associated subsystems. Product Version NonStop SQL/MX Release 3.1 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.23 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications.
What’s New in This Manual New and Changed Information SQL 3431 SQL 4231 and SQL 4232 SQL 8445, SQL 8875, SQL 8934 and SQL 8935 SQL 13083 through SQL 13089 SQL 20680 through SQL 20686 SQL 21074 SQL 25223 and SQL 25269 HP NonStop SQL/MX Release 3.
About This Manual NonStop SQL/MX is the HP relational database management system based on ANSI SQL-92. It uses the industry standard Structured Query Language (SQL) to define and manipulate data. This manual lists messages produced by NonStop SQL/MX and related subsystems. Audience This manual is for NonStop SQL/MX database administrators and programmers who use the NonStop SQL/MX conversational or programmatic interface.
Related Documentation About This Manual Connectivity Manuals SQL/MX Connectivity Service Manual Describes how to install and manage the HP NonStop SQL/MX Connectivity Service (MXCS), which enables applications developed for the Microsoft Open Database Connectivity (ODBC) application programming interface (API) and other connectivity APIs to use NonStop SQL/MX.
Related Documentation About This Manual Online Help SQL/MX Reference Online Help Overview and reference entries from the SQL/MX Reference Manual. SQL/MX Messages Online Help Individual messages grouped by source from the SQL/MX Messages Manual. SQL/MX Glossary Online Help Terms and definitions from the SQL/MX Glossary. NSM/web Help Context-sensitive help topics that describe how to use the NSM/web management tool.
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.
Notation for Messages About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
Change Bar Notation About This Manual either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
1 Message Handling NonStop SQL/MX reports exception condition messages at the SQL/MX conversational interface (MXCI) window, in SQL preprocessor and compiler listings, and during the execution of embedded SQL programs. You obtain the error messages that result from the execution of an SQL statement within an embedded program in C or COBOL by using the GET DIAGNOSTICS statement to access the SQL diagnostics area.
Non-SQLCODE Error Messages Message Handling Display information for a message, including its SQLCODE, the SQLSTATE values for the SQLCODE, and the message text. For more information about the ERROR command, see the SQL/MX Reference Manual. For detailed cause, effect, and recovery information for error messages, see this manual.
SQLSTATE and SQLCODE Message Handling SQLSTATE and SQLCODE SQLSTATE and SQLCODE status codes are returned to indicate either that an SQL statement completed successfully or that an exception condition was raised during execution of an SQL statement. The ANSI SQL-92 SQLSTATE variable is a five-character string with a two-character class code followed by a three-character subclass code. An SQLSTATE value of 00000 indicates successful completion.
Message Handling Process Control Procedure Errors Process Control Procedure Errors HP NonStop Process Services process control procedure errors are numeric codes that indicate errors and other conditions encountered by the process control procedures that are supported by NonStop Process Services. The process control procedures return these codes to callers. Many programs that are part of NonStop systems make calls to these procedures and, in some cases, must report procedure errors to the user.
2 General Messages (0 through 999) SQL 100 100 The "no data" completion condition (SQLCODE = +100). Cause. You have reached the end of a cursor, and there is no more data to be returned. When you enter a noncursor query (SELECT * FROM t WHERE...; DELETE FROM t WHERE...;), SQL/MX returns warning 100 to indicate that zero rows satisfied the predicate, and zero rows were affected. In embedded SQL/MX, on a cursor FETCH, SQL/MX returns this warning to indicate that it has reached the end of rows. Effect.
General Messages (0 through 999) HP NonStop SQL/MX Release 3.
3 Data Definition Language (DDL) Messages (1000 through 1999) SQL 1001 1001 An internal error occurred in module name on line num. DETAILS(details). Where name is the name of the module. Where num is the line number. Where details are the details of the error. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. See Contacting Your Service Provider on page 1-3. SQL 1002 1002 Catalog catalog does not exist or has not been registered on node node.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1003 1003 Schema schema does not exist. Where schema is the ANSI name of the affected schema. Cause. In a replication context: a REPLICATION SCHEMA operation specified a schema that does not exist. The specified schema must exist to complete the operation. Effect. The operation fails. Recovery. Check that a schema named schema does exist and resubmit the statement.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1006 1006 Index index-name does not exist. Where index-name is an SQL/MX object name. Cause. The operation you attempted requires the existence of an index named index-name. Effect. The operation fails. Recovery. Check that an index named index-name does exist. If you did not fully qualify the name, check that the defaults generate the correct qualified name. SQL 1008 1008 User name user-name does not exist.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Do not attempt to use this SQL/MX statement. SQL 1012 1012 No privileges were granted. You lack grant option on the specified privileges. Cause. You attempted to grant privileges for which you do not have grant options. Effect. No privileges are granted. Recovery. You must have grant options for privileges to grant them. SQL 1013 1013 Not all privileges were granted. You lack grant option on some of the specified privileges. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. NonStop SQL/MX did not revoke the privileges. Recovery. Re-issue the statement with proper authorization. SQL 1016 1016 Redundant references to column column-name were specified in the constraint or trigger definition. Where column-name is an SQL identifier. Cause. You created a constraint with multiple references to column-name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 1020 1020 Privilege settings on metadata tables cannot be changed. Cause. You attempted to change the privilege settings on a metadata schema or table, which cannot be changed. Effect. NonStop SQL/MX does not change the settings. Recovery. None. SQL 1021 1021 SQL is already initialized on system node-name.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1023 1023 Only super ID can name an authorization ID other than the current user name. Cause. You attempted to create a schema with the authorization ID of another user. Only the super ID can do this. Effect. The operation fails. Recovery. Log on as the super user to create a schema with another owner. SQL 1024 1024 File system error error-number occurred on text-string1. text-string-2.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. No SQL objects are dropped. Recovery. The owner of the schema (or super ID) needs to issue the DROP SCHEMA statement. SQL 1027 1027 The definition schema definition-schema-name is dropped when its catalog is dropped. Where definition-schema-name is the name of the definition schema specified. Cause. You attempted to drop the schema containing the metadata tables for the catalog. Effect. No SQL objects are dropped. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1030 1030 File label Guardian name could not be accessed. File system error error. Where Guardian name is the name of an SQL/MX file. Where error is a file system error number. Cause. A file system error occurred while accessing the file label for Guardian name and the stored row count could not be retrieved. Effect. The operation fails. Recovery. Apply the recovery of the accompanying error message.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1036 1036 Only super ID can execute DROP SQL. Cause. An attempt was made to drop SQL by a user who is not the super ID. Effect. The operation fails. Recovery. The super ID needs to issue the DROP SCHEMA statement. SQL 1037 1037 SQL/MX is not installed on system node. Where node is the name of the node referenced by the operation. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1040 1040 The use of ALTER on metdata tables is not permitted. Cause. An ALTER TABLE statement was issued naming a table that is part of the SQL/MX metadata. Such tables cannot be altered. Effect. The operation fails. Recovery. None. SQL 1041 1041 The primary key has already been defined. Cause. You attempted to add a primary key to a table that already has a primary key. Effect. The operation fails. Recovery. None.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1044 1044 Constraint constraint-name could not be created because the referenced columns in the referenced table are not part of a unique constraint. Where constraint-name is the name of a column constraint or table constraint. Cause. The columns that constraint-name references in the referenced table are not part of a unique constraint. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1046 1046 Referenced and referencing column lists do not match for constraint constraint-name. Where constraint-name is the name of a column constraint or table constraint. Cause. The list of referencing columns in constraint-name does not match the list of unique key columns that it is referencing. Effect. The operation fails. Recovery. Check that the constraint-name list of referencing columns matches the list of referenced columns.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1049 1049 Constraint cannot be dropped because it was specified to be NOT DROPPABLE. Cause. You attempted to drop a constraint that is NOT DROPPABLE. Effect. The operation fails. Recovery. None. SQL 1050 1050 Constraint cannot be dropped because it is used as a referenced object for a foreign key. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Either correct the table name or the constraint name and reissue the statement.You can use the SHOWDDL statement to display the names of constraints on the table. SQL 1053 1053 Unique index index-name could not be created because the specified column(s) contain duplicate data. Where index-name is the name specified for the index to create. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1057 1057 SQL/MX objects cannot be created on volume-name: File system error error-number. Where volume-name is the name of a volume. Where error-number is the file system error number. Cause. An attempt to create a file on volume volume-name resulted in file system error error-number. Effect. The operation fails. Recovery. Apply the recovery of the accompanying error message. SQL 1058 1058 Lock lock-name already exists.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1061 1061 Dropping metadata catalog catalog-name is not allowed. Where catalog-name is the name of an SQL/MX catalog. Cause. You attempted to drop a catalog that is part of the SQL/MX metadata. Effect. The operation fails. Recovery. None. SQL 1062 1062 Dropping metadata schema schema-name is not allowed. Where schema-name is the name of an SQL/MX metadata schema. Cause. You attempted to drop a schema that is part of the SQL/MX metadata.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1065 1065 Creating constraint constraint-name in metadata schema is not allowed. Where constraint-name is the name of the constraint. Cause. You attempted to create a constraint on a metadata table, which is not allowed. Effect. The operation fails. Recovery. None. SQL 1066 1066 Creating index index-name in metadata schema is not allowed. Where index-name is the name specified for the index. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Apply the recovery of the accompanying error message. SQL 1071 1071 Object ANSI name could not be accessed. Where ANSI name is the name of the SQL/MX object. Cause. The statement issued required access to the Guardian file underlying object ANSI name. Effect. The operation fails. Recovery. Apply the recovery action from the accompanying error message.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1075 1075 The catalog must be empty. It contains at least one schema schema-name. Where schema-name is the name of a schema in the specified catalog. Cause. An attempt was made to drop a catalog that is not empty. Effect. The catalog is not dropped. None of its schemas are dropped. Recovery. Drop all schemas in the catalog and resubmit. SQL 1077 1077 Metadata table table-name does not contain information for view view-name.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Apply the recovery of the accompanying error message. SQL 1080 1080 The DDL request has duplicate references to column column-name. Where column-name is the name of a column of a table. Cause. You attempted to create a table that has two columns with the same name. If you name a column “SYSKEY,” duplication can result from the implicit creation by NonStop SQL/MX of a column named SYSKEY to ensure uniqueness for the clustering key.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1083 1083 Validation for constraint constraint-name failed; incompatible data exists in table. Where constraint-name is the name of a column or table constraint. Cause. Data in the table violates the check constraint. Effect. The constraint operation fails. Recovery. Remove data that violates the constraint from the table and resubmit. SQL 1084 1084 An invalid default value was specified for column column-name.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Create a lock lock-name or specify a valid lock name and resubmit. SQL 1087 1087 DDL lock cannot be granted; invalid operation has been specified. Cause. An invalid utility operation requested a DDL lock. Effect. The lock request fails. Recovery. Specify a valid utility operation, or check to see if invalid utilities are being run, and resubmit.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Remove the self-reference and resubmit. SQL 1094 1094 Object object-name could not be dropped because it is not of type object-type. Where object-name is the ANSI name of the object stated in the DROP command. Where object-type is the type of object that was stated in the DROP command. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Change the statement so that it does not define two partitions to have the same first key, and resubmit. SQL 1099 1099 Column column-number is unnamed. You must specify an AS clause for that column expression, or name all the columns by specifying a view column list. Where column-number is the specified column. Cause. You attempted to create a view by using a query expression in which column-number was unnamed. Effect.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1102 1102 Rows could not be inserted into table table-name. Where table-name is the ANSI name of the metadata table. Cause. See the accompanying error message for clarification. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 1103 1103 Rows could not be deleted from table table-name. Where table-name is the ANSI name of the metadata table. Cause. See the accompanying error message for clarification. Effect.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1106 1106 The specified partition partition-location of object table-name does not exist. Where partition-location is the location of the specified partition. Where table-name is the name of the table. Cause. The location name partition-location specified in the partition operation does not exist. Effect. The partition operation fails. Recovery. Specify a valid partition location name and resubmit.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1111 1111 An error occurred while starting a transaction on object table-name. Where table-name is the name of the object. Cause. The transaction could not be started, possibly due to another transaction being active on the object. Effect. The operation fails. Recovery. Determine why the transaction failed and resubmit. SQL 1112 1112 An index column list cannot contain only the systemgenerated column SYSKEY. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1115 1115 Label Guardian name could not be created for ANSI name (file error error). Where Guardian name is the name of the Guardian file for the label creation that failed. Where ANSI name is the name of the table. Where error is the error number returned. Cause. A file system error occurred on the attempt to create the label. Effect. The table is not created. Recovery. Correct the file system error and reissue the CREATE statement.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Specify a different schema and resubmit. SQL 1119 1119 Dropping metadata object table-name is not allowed. Where table-name is the name of an SQL/MX metadata table. Cause. You attempted to use the DROP TABLE statement to drop a table that is part of SQL/MX metadata. Effect. The table is not dropped. Recovery. Metadata tables can be dropped only by using the DROP SQL statement or the MXTOOL GOAWAY utility.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1122 1122 The number of specified partition key values (partitionkey-value-list) for object object-name exceeds the number of user defined key columns, key-col-number. Where partition-key-value-list is a list of the partition key values. Where object-name is the name of the object. Where key-col-number is the number of columns in the user-defined key. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1126 1126 Operation cannot be performed because object is not an SQL/MP alias. Where object is the ANSI name of the object. Cause. You attempted to perform an operation that is specific to MP aliases on an object that is not an MP alias. Effect. The operation fails. Recovery. Specify an object that is an SQL/MP alias and resubmit. SQL 1127 1127 The specified table table-name is not a base table.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1132 1132 An added column cannot have DEFAULT NULL and NOT NULL at the same time. Cause. You attempted to add a column that is both DEFAULT NULL and NOT NULL. Effect. The operation fails. Recovery. Determine whether the column should be DEFAULT NULL or NOT NULL and resubmit. SQL 1133 1133 Only super ID can perform this operation. Cause. You attempted to perform an operation that can be performed only by the super ID. Effect.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Specify that the column-name is NOT NULL NOT DROPPABLE and resubmit. SQL 1136 1136 For an added column, the PRIMARY KEY clause cannot specify NOT DROPPABLE. Cause. You used the ALTER TABLE statement to add a column specifying a primary key that is not droppable. A primary key added through ALTER TABLE must be droppable. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1138 1138 An internal error occurred: invalid input parameter(s). Object name and status are required. Cause. This is an internal error in the interface between utilities and the catalog manager. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 1139 1139 System-generated column column-name of base table tablename cannot appear in the search condition of a check constraint definition.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1141 1141 Label file-name for object could not be accessed. File system error error-number. Where file-name is the Guardian file name of a partition of object. Where error-number is a Guardian file system error. Cause. An ALTER TABLE or ALTER INDEX operation encountered a file system error. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Run the query statement-text to see the rows that violate the referential constraint. Either change those rows or change the referential constraint definition and resubmit. SQL 1144 1144 A quoted string was expected in first key clause for column column-name on table table-name, but the value detected is (first-key-string). Where column-name is the column in table-name. Where table-name is the name of the table.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. The type of the object specified in the command is inconsistent with the DDL command being used. For example, this occurs if DROP TABLE is used, and the object you specify is an INDEX. Effect. The operation fails. Recovery. Check that the correct object name was specified and execute a statement that is consistent with that type of object.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1150 1150 Table table-name was not created because Partition Overlay Support could not generate volume names for the partitions to reside on. Where table-name is the name of the table. Cause. When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1154 1154 Cannot create object object-name as the table size is too big to fit on the system. Where object-name is the name of the object. Cause. NonStop SQL/MX could not create the object because the requested table size is bigger than the total amount of disk space available on the cluster. Effect. The SQL operation fails. Recovery. Check that the table size requested fits the cluster, and then retry the statement.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. If you want the STORE BY column list that specifies the clustering key to be different than the PRIMARY KEY, specify a DROPPABLE PRIMARY KEY. If you want the PRIMARY KEY to be the same as the STORE BY key, do not specify a STORE BY clause. Correct the syntax and resubmit. SQL 1162 1162 User user-name already owns object-type object-name. Operation ignored. Where user-name is a valid Guardian user name.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. Object not found by the specified UID. Effect. The operation fails. Recovery. Contact your service provider. SQL 1174 1174 An invalid data type was specified for column $0~String0. Where $0~String0 is the column name. Cause. The data type specification for a column is missing. Effect. The command fails. Recovery. Specify a data type for the column.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. See previous messages in this SQL/MX operation to determine the necessary corrective actions. Also, use the file system error error-number to analyze the cause. Fix the error and resubmit. SQL 1182 1182 Error error was returned by the file system on resource fork Guardian name. Where error is the error returned. Where Guardian name is the name of the file. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1184 1184 You do not have the required privilege(s) on columnname. Where column-name is the name of a column specified in the references part of a referential integrity constraint. Cause. You attempted to establish a referential integrity constraint on a column for which the executing user ID has no REFERENCES privileges. Effect. The operation fails. Recovery. Establish correct column privileges and resubmit.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1187 1187 The schema name schema-name is reserved for SQL/MX metadata. Where schema-name is the name of an SQL/MX schema. Cause. NonStop SQL/MX reserves certain schema names for its own use. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for reserved schema names. Choose a name that is not reserved and reissue the CREATE statement.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1190 1190 SQL/MP system catalog catalog-location could not be found - error error-number. Where catalog-location is a name of the form $vol.sql.catalogs. Where error-number identifies the error encountered. Cause. Unable to locate the device for the SQL/MP system catalog or the label of $vol.sql.catalogs. Effect. The operation fails. Recovery. Check that the device for the SQL/MP system catalog and the file $vol.sql.catalogs exist.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1193 1193 Internal first key size is size bytes; it exceeds the maximum of limit bytes. Cause. The internal form of a first key specification for a partition is larger than the metadata can accommodate. Effect. The operation fails. Recovery. Reduce the size of the first key specification and then resubmit. SQL 1195 1195 The number of columns for table-or-index exceeds the maximum limit of max-no-of-columns. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1197 1197 SQL/MP object name $0~string0 is not valid. Cause. You specified an invalid SQL/MP object name. Effect. The operation fails. Recovery. Specify a correct SQL/MP object name and resubmit. SQL 1221 1221 SQL/MP alias for file file-name could not be created. File system error: error-number. Where file-name is the Guardian file name specified in the CREATE SQL/MP ALIAS command. Where error-number is the Guardian file system error number.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1225 1225 Mixing EXECUTE privilege with other privileges is not allowed. Cause. EXECUTE and another privilege were specified in the same GRANT or REVOKE statement, which is not allowed. Effect. The operation fails. Recovery. Use separate GRANT or REVOKE statements for EXECUTE and other privileges. SQL 1226 1226 No valid combination of privileges was specified. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. An OSS file system error occurred when you attempted to save a table DDL. Possible reasons are: The directory /usr/tandem/sqlmx/ddl did not exist or could not be created. The system did not have write access to /usr/tandem/sqlmx/ddl. Insufficient OSS file space was available. Effect. The table is not dropped. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Correct the error and retry the operation. SQL 1236 1236 The schema name specified for SQL object object-name is not valid. The schema name must be the same as the schema being created. Where object-name is the name of the SQL object. Cause. You specified a schema name for an object that is different from the name of the schema being created. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1239 1239 The character set used for string literals in VIEW must be ISO88591. Cause. You specified a literal with a character set other than ISO88591 in the text of a create view statement. Effect. The operation fails. Recovery. Specify only ISO88591 literals in the command. SQL 1240 1240 The character set for a PARTITION KEY column must be ISO88591. Cause. You specified a literal with a character set other than ISO88591 as a partition key.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1243 1243 The hexadecimal form of string literals is not allowed in this context. Cause. You specified a hexadecimal literal in the text of the statement, which is not allowed. Effect. The operation fails. Recovery. Do not specify hexadecimals in this type of command. SQL 1244 1244 This operation is not allowed because object name is a SQL/MP object. Where object-name is the specified object. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1246 1246 The supplied partition key value (key-value) is inconsistent with the data type of column column-name of object object-name. Where key-value is the specified first key value. Where column-name is the column of object-name that corresponds to the invalid key value. Where object-name is the name of the affected object. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1250 1250 DROP cannot be performed on object object-name because a utility operation (operation-type) associated with DDL_LOCK lock-name is currently running. Where object-name is the ANSI name of the object named in the DROP command. Where operation-type is the type of utility operation. Where lock-name is the ANSI name of the DDL lock object that is associated with the utility operation. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1254 1254 Duplicate unique constraints are not allowed with same set of columns. Cause. You attempted to specify both the unique and primary key constraints or multiple unique constraints on the same set of columns, which is not allowed. Effect. The operation fails. Recovery. Change your query so that both unique and primary constraints or multiple unique constraints are not specified on the same set of columns.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1263 1263 Object names that start with text are reserved for SQL/MX metadata. Where text is the disallowed name that was specified. Cause. You specified an SQL/MX reserved object name. Effect. The object is not created. Recovery. See the SQL/MX Reference Manual for the list of reserved object names. Choose a name that is not reserved and reissue the CREATE statement.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1267 1267 EXECUTE privilege is incompatible with this object type. Cause. You specified a privilege that is not supported for the object type in a GRANT statement. Effect. The operation fails. Recovery. Reissue the GRANT statement specifying the valid privilege for the object type. SQL 1268 1268 Duplicate columns are not allowed in a GRANT or REVOKE statement. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Where number is the specified number of extents. Cause. A CREATE or ALTER operation specified an ALLOCATE attribute value that was greater than the MAXEXTENTS value for the affected database object, which is not allowed. Effect. The operation fails. Recovery. If possible, alter the MAXEXTENTS attribute value to be greater than the desired number of extents to be allocated. The current maximum value for MAXEXTENTS is 768.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1275 1275 Constraint constraint1 cannot be dropped because it is needed by unique constraint constraint2. Where constraint1 is the constraint you are trying to drop. Where constraint2 is the UNIQUE constraint. Cause. You attempted to drop a constraint that is needed by a UNIQUE constraint, which is not allowed because it would leave a UNIQUE constraint on a column, but without a NOT NULL constraint for that column. Effect. The operation fails.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1278 1278 The command cannot be executed because operation is in progress for all schemas in catalog catalog. Where operation is UPGRADE or DOWNGRADE. Where catalog is a catalog name that is affected by operation. Cause. You attempted to execute a DDL or utility operation that affected catalog or a schema in that catalog. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Retry the operation. If it continues to fail, report the error to your service provider. SQL 1301 1301 NO ACTION referential action for referential-triggeredaction clause is not yet supported as specified by ANSI SQL99 standard. To alter the behavior, set an appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default. Where referential-triggered-action can either be ON DELETE or ON UPDATE.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1302 1302 NO ACTION referential action for referential-triggeredaction clause behaves like RESTRICT referential action. To alter the behavior, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default. Where referential-triggered-action can either be ON DELETE or ON UPDATE. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1305 1305 The specified schema location subvolume is already in use by schema schema. Where subvolume is the Guardian subvolume name specified in the LOCATION clause of the CREATE SCHEMA command. Where schema is the ANSI name of an existing schema that already uses subvolume as a schema subvolume. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1307 1307 The schema location subvolume is reserved for SQL/MX metadata. Where subvolume is the Guardian subvolume name specified in the LOCATION clause of the CREATE SCHEMA command. Cause. In a CREATE SCHEMA command, you specified subvolume in the LOCATION clause, however subvolume names with the format ZSDdigit>anything> are reserved for SQL/MX metadata schemas. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) Where constraint-name is a constraint name. Cause. An error occurs during the creation of the constraint. The error that described the cause of the failure already appears. This error message provides clarification. Effect. The operation fails. Recovery. No recovery is necessary. SQL 1312 1312 Unable to action-text object-name due to the above errors. Where action-text is either create table or create index.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1500 1500 The CATSYS - CAT_REFERENCES system schema relationship for catalog catalog might be corrupt. Where catalog is the ANSI name of the affected catalog. Cause. A row for catalog was found in the CATSYS system schema table, but no corresponding row could be found in the CAT_REFERENCES system schema table. Effect. The operation fails. Recovery. Retry the operation. If the error persists, contact your service provider.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1503 1503 The OBJECTS - PARTITIONS definition schema relationship for type object might be corrupt. Where type is the type of the affected object. Where object is the fully qualified ANSI name of the affected object. Cause. A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected PARTITIONS definition schema table. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1510 1510 Identity column col-name can be of the following data types only: LARGEINT, unsigned INTEGER and unsigned SMALLINT. Where col-name is the IDENTITY column name. Cause. An unsupported data type is specified for IDENTITY column. Effect. The operation fails. Recovery. Modify the IDENTITY column data type to LARGEINT, unsigned INTEGER or unsigned SMALLINT, and resubmit the statement.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Specify a positive value for the internal sequence generator option, and resubmit the statement. SQL 1573 1573 The START WITH value must be greater than or equal to the MINVALUE and less than or equal to the MAXVALUE for col-name. Where col-name is the IDENTITY column name. Cause. For the IDENTITY column, START WITH option value is not in the range between MINVALUE and MAXVALUE. Effect. The operation fails.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1576 1576 The seq-gen-option value is greater than the maximum allowed for col-name data type. Where seq-gen-option is the internal sequence generator option. Where col-name is the IDENTITY column name. Cause. The internal sequence generator option (seq-gen-option) value is greater than the maximum value allowed for the IDENTITY column data type. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) Where seq-gen-value is the current numeric value of internal sequence generator. Cause. The specified MAXVALUE was less than current value of internal sequence generator. Effect. The operation fails. Recovery. Specify MAXVALUE equal to or greater than the current value of internal sequence generator and resubmit the statement. SQL 1592 1592 Only the MAXVALUE or INCREMENT BY option can be altered for the col-name.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. For details, see the additional diagnostics messages. Correct the cause, and resubmit the statement. SQL 1595 1595 The MAXVALUE option for the IDENTITY column col-name must be a valid numeric value. NO MAXVALUE is not allowed. Where col-name is the IDENTITY column name. Cause. An unsupported option (NO MAXVALUE) is specified for ALTER operation. Effect. The operation fails. Recovery.
Data Definition Language (DDL) Messages (1000 through 1999) If the IDENTITY column default specification type is GENERATED BY DEFAULT, recalibrate the CURRENT_VALUE of the internal sequence generator using the following command: ALTER TABLE table-name ALTER COLUMN column-name RECALIBRATE TO value NO SELECT Where table-name is the table that contains the IDENTITY column. Where column-name is the IDENTITY column name. Where value is the CURRENT_VALUE of the IDENTITY column.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1599 1599 The recalibration value is greater-or-less-than-an-option value, recalibration-value, of the IDENTITY column, col-name, for the table, table-name.
Data Definition Language (DDL) Messages (1000 through 1999) Effect. The operation fails. Recovery. Resubmit the statement when the locking contention has cleared. SQL 1601 1601 Recalibration of the GENERATED ALWAYS AS IDENTITY column, col-name, for the table, table-name, is not allowed with NO SELECT. Where col-name is the IDENTITY column name. Where table-name is the table that contains the IDENTITY column. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) SQL 1612 1612 Constraint $0~constraintName could not be created as it is a duplicate of $1~constraintName. Cause. You attempted to create a column list and the referential actions of a referential integrity constraint, which matches the column list and referential action of another referential integrity constraint in the table. Effect. The operation fails. Recovery. None.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. The NOT NULL constraint cannot be created on a referencing column with the SET NULL referential action on it. (OR) The primary key constraint cannot be created on the referencing column with the referential action specified because the primary key cannot be updated. Effect. The operation fails. Recovery. Drop the referential integrity constraint. SQL 1750 1750 WITH GRANT OPTION not allowed for security administrators. Cause.
Data Definition Language (DDL) Messages (1000 through 1999) Cause. An attempt was made to revoke the security administrator designation from a user name or user id specified by user which had not previously been designated as a security administrator. Effect. The operation fails. Recovery. Reissue the command, specifying a current security administrator. SQL 1753 1753 You must be a security administrator to perform this operation. Cause. An attempt was made by super.
Data Definition Language (DDL) Messages (1000 through 1999) Recovery. Remove PUBLIC from the grantee list and retry the operation. SQL 1756 1756 No GIVE SCHEMA operation is in progress. There is nothing to recover. Cause. An attempt was made to perform the RECOVER SCHEMA operation after a successful GIVE SCHEMA operation. Effect. The operation fails. Recovery. None.
4 SQL/MX MXCMP Messages (2000 through 2999) This section includes process creation errors, IPC errors, static compilation errors, and miscellaneous errors from the optimizer. SQL 2001 2001 Error or warning number occurred while opening or reading from DEFAULTS table name. Using values. Where number is the error number. Where name is the DEFAULTS table name. Where values is the default values file. Cause. NonStop SQL/MX was unable to open system defaults table name because of error number. Effect.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. This error might be a communication error. Check the configuration. If it seems correct, report the entire message to your service provider. SQL 2004 2004 Internal error: error from MXCMP; cannot work on this query. Cause. NonStop SQL/MX received an internal error from the MX compiler (MXCMP). Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. None. Report the entire message to your service provider. SQL 2009 2009 The user transaction must be rolled back (or committed, if that makes sense in the application) before MXCMP can be restarted and proceed. Cause. An outstanding transaction must be resolved before the MX compiler (MXCMP) can be restarted. Effect. The operation fails. Recovery. None. SQL 2010 2010 Internal IPC error. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2012 2012 Server process name could not be created on node Operating system error number-1, TPCError = number-2, error detail = text. (See Operating system procedure PROCESS_LAUNCH_ for details). Where name is the name of the server process. Where number-1 is the error number. Where number-2 is the TPCError. Where text is the error message text. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2014 2014 Server process name could not be created on node Operating system error number on swap file. Where name is the server process name. Where number is the error number. Cause. NonStop SQL/MX was unable to create server process name because of the process control procedure error number it received on the swap file. Effect. NonStop SQL/MX does not create the server process. Recovery.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2017 2017 Server process name could not be created on node - no more processes (PCBs) available. Where name is the server process name. Cause. NonStop SQL/MX was unable to create server process name, because no more process control blocks (PCBs) were available. Effect. NonStop SQL/MX does not create the server process because too many processes are running to allow more to be created. Recovery. Do not attempt recovery. Contact your service provider.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2020 2020 Server process name could not be created on node unlicensed privileged program. Where name is the server process name. Cause. NonStop SQL/MX was unable to create server process name because it is an unlicensed privileged program. The server process was configured incorrectly at installation. Effect. The operation fails. Recovery. The server process must be a licensed privileged program. Check your configuration.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2023 2023 Server process name could not be created - process id. Where name is the server process name. Where process id identifies the process. Cause. NonStop SQL/MX was unable to create server process name. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem. SQL 2025 2025 Server process name could not be created - CPU is unavailable; process id. Where name is the server process name.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2028 2028 OSS server process name could not be created on node insufficient resources. Where name is the server process name. Cause. NonStop SQL/MX was unable to create the OSS server process name because there is not enough memory to create this process. Effect. The operation fails. Recovery. Rebalance the system. SQL 2029 2029 The new min value is greater than the current max value number. Where number is the current maximal value. Cause.
SQL/MX MXCMP Messages (2000 through 2999) Cause. The NonStop SQL/MX process id received process control procedure error number while communicating with the server process name. Effect. NonStop SQL/MX is not able to communicate with the process. Recovery. Use the process control procedure error to diagnose and correct the problem. SQL 2034 2034 process id: Operating system error number while communicating with server process name. Where process id identifies the process. Where number is the error number.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2037 2037 receiving process: A message from process sending process was incorrectly formatted and could not be processed. Cause. The NonStop SQL/MX process receiving process received a message from process sending process that was unreadable in some way. Either the message was corrupted by sending process, or an internal error occurred within receiving process. Effect. The SQL/MX statement fails. Recovery. None. Contact your service provider.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2051 2051 Either control option option name or value 'value'is not valid. Cause. You specified an invalid control option name or a valid option with an invalid value. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 2052 2052 Optimizer internal counters: value value value value. Cause. This error should appear only if you are running in debug mode. Effect. None. Recovery. None. Report the entire message to your service provider.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2055 2055 The specified value 'value' for DEFAULTS attribute name is not valid. text-string. Where text-string contains the additional details about the error. This is an optional text. Cause. You specified an invalid value for the DEFAULTS attribute listed in the message. Effect. The operation fails. Recovery. Correct the syntax and resubmit. For valid values that are allowed in the specified DEFAULTS attribute, see the SQL/MX Reference Manual.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Specify the value using the expected type, if appropriate. SQL 2059 2059 Errors or warnings occurred while reading values from DEFAULTS table name. Where name is the name of the table. Cause. You received an error on the DEFAULTS table name. A previous error message has appeared with specific information. Effect. The operation fails. Recovery. None. SQL 2060 2060 Procedure name has already been defined in this module.
SQL/MX MXCMP Messages (2000 through 2999) Cause. You defined the static cursor name twice in this module. Effect. NonStop SQL/MX uses the first dynamic cursor definition. Recovery. This is an informational message only; no corrective action is needed. SQL 2063 2063 Dynamic cursor name has already been defined in this module. The previous definition, as a static cursor, is being retained and this latest one ignored. Where name is the cursor name. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2066 2066 Cursor name was not found in module name. Where name is the cursor name. Where name is the module name. Cause. NonStop SQL/MX could not find cursor name in module name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 2067 2067 Descriptor name has already been defined in this module. The previous definition is being retained and this latest one ignored. Where name is the descriptor name. Cause.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Correct the syntax and resubmit. SQL 2070 2070 Statement is not valid in this context. Cause. In a module definition file, you specified a query statement such as SELECT, INSERT, UPDATE, DELETE, or a DDL statement. These statements must be embedded in procedures. Effect. NonStop SQL/MX is unable to compile the module. Recovery. Correct the syntax and resubmit. SQL 2071 2071 The name name has already been declared or defined in this module.
SQL/MX MXCMP Messages (2000 through 2999) Effect. The operation fails and is unable to compile the entire module correctly. Recovery. None. Use a different name for your module and recompile. SQL 2074 2074 The name name is reserved for future system modules. Where name is the name of the module. Cause. You attempted to use a name that is reserved for future system modules. Effect. The operation fails and is unable to compile the entire module correctly. Recovery. None.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2080 2080 Error number while reading file: value bytes were read from text when value were expected in module name. Cause. NonStop SQL/MX received error number while reading module name. value shows the number of bytes read from text. The module file is unusable. Either it has been corrupted or overwritten. Effect. The operation fails. Recovery. Recompile the module definition file, using the MXCMP compiler, to create a valid module file.
SQL/MX MXCMP Messages (2000 through 2999) Effect. NonStop SQL/MX does not name or locate the file. Recovery. Use the error to diagnose and correct the problem. SQL 2084 2084 Error number while writing value bytes to file name. Cause. NonStop SQL/MX received error number while writing to file name. value shows the number of bytes being written. Effect. NonStop SQL/MX does not open the file. Recovery. Use the error to diagnose and correct the problem.
SQL/MX MXCMP Messages (2000 through 2999) Cause. NonStop SQL/MX ignored the command line argument for module name1. Instead, it used the second module name2 in file name3. Effect. None. Recovery. None. SQL 2091 2091 The required module statement was not found in file name. Where name is the name of the file. Cause. NonStop SQL/MX could not find the required module statement in file name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2094 2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored. Cause. You specified a timestamp statement twice in this module. Effect. NonStop SQL/MX uses the first timestamp. Recovery. Informational message only; no corrective action is needed. SQL 2095 2095 Module file name1, expected to contain module name2, instead contains name3.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Edit the module definition file so that its SOURCE_FILE statement’s source path name is no more than 1024 characters long. Rerun MXCMP on the module definition file. SQL 2098 2098 The compilation type compilation completed with value warnings. Cause. compilation type completed with the number of warnings given as value. Effect. None. Recovery. Informational message only; no corrective action is needed.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2102 2102 This query could not be compiled with 'MINIMUM' optimization level. Suggestion: Retry with 'MEDIUM' optimization level. Cause. NonStop SQL/MX was unable to compile this query using the MINIMUM optimization level. Effect. NonStop SQL/MX is unable to process this query. Recovery. Resubmit the query with MEDIUM optimization level.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. If applicable, use the MAXIMUM optimization level, correct the CONTROL QUERY SHAPE specification, and resubmit. SQL 2105 2105 This query could not be compiled because of incompatible Control Query Shape (CQS) specifications. Inspect the CQS in effect. Cause. NonStop SQL/MX was unable to compile this query because you used an incompatible CONTROL QUERY SHAPE specification. Effect. NonStop SQL/MX is unable to process this query. Recovery.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. This is an informational message. To prevent this warning, turn off query caching before query preparation. SQL 2200 2200 DEFAULTS attribute attribute is read-only. Where attribute is the DEFAULTS attribute. Cause. You attempted to change the DEFAULTS attribute, which is read-only. Effect. The operation fails. Recovery. None. SQL 2201 2201 SQL compilation return code is mxcmp non-zero exit code. Cause.
SQL/MX MXCMP Messages (2000 through 2999) Effect. The operation fails. Recovery. Verify that application pathname exists and is readable by the user. Verify that application pathname is spelled correctly, and retry the command. SQL 2204 2204 SQL compilation of module name failed. Where module name is the name of the module. Cause. You invoked mxCompileUserModule on an application file that has embedded module definition(s).
SQL/MX MXCMP Messages (2000 through 2999) SQL 2207 2207 -option is an unknown command line option. Where -option is the command-line option. Cause. You invoked mxCompileUserModule with an unrecognized command-line option. Effect. The operation fails. Recovery. Review the allowable command-line options by invoking mxCompileUserModule. Verify that the desired command-line options are spelled correctly and retry the command. SQL 2208 2208 mxCompileUserModule requires an application file name. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2211 2211 Lexical error: unknown symbol character. Cause. You invoked mxCompileUserModule on an application file, possibly intending to SQL compile only a subset of its embedded module definitions, but you specified an unknown character in the module name list. Effect. The operation fails. Recovery. Review the module name list syntax. Verify that the module names are specified correctly and retry the command.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2214 2214 Internal error in mxCompileUserModule in file filename at line linenumber: error message. Cause. You invoked mxCompileUserModule on an application file to SQL compile its embedded module definitions. An internal error occurred during the operation. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 2215 2215 identifier is not a valid regular identifier. Cause.
SQL/MX MXCMP Messages (2000 through 2999) Cause. You invoked mxCompileUserModule on an application file to SQL compile its module definitions. This command invoked MXCMP, which returned error code, indicating an abnormal termination. Effect. The operation fails. Recovery. If the system is heavily loaded, retry the command later. If the problem persists under normal system load, report it as an internal error and contact your service provider.
SQL/MX MXCMP Messages (2000 through 2999) Where error-num is the file system error number. Cause. The nodename you specified is not available. Effect. The compiler tried to produce a plan without using that node. This might result in a suboptimal plan. Recovery. See the Guardian Procedures Errors and Messages to diagnose and correct the problem. SQL 2235 2235 MXCMP Internal Error: detail-text, originated from file name at line number. Where, detail-text is information about the error.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Specify a valid Guardian or OSS directory. HP NonStop SQL/MX Release 3.
SQL/MX MXCMP Messages (2000 through 2999) HP NonStop SQL/MX Release 3.
5 Parser and Compilation Messages (3000 through 3999) SQL 3000 3000 An internal error occurred in module name on line number. DETAILS(detailed text). Cause. An internal error has occurred in module name on line number. Details are displayed in detailed text. Effect. The operation fails. Recovery. Use the information in the detailed text to diagnose and correct the problem and resubmit. SQL 3001 3001 Syntax error at or before SQL text. Cause. There is a syntax error near the text SQL text. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3003 3003 Length or precision must be greater than zero. Cause. You defined length or precision as zero. You must enter a value greater than zero. Effect. The operation fails. Recovery. Enter a value greater than zero and resubmit. SQL 3004 3004 A delimited identifier must contain at least one nonblank character. Cause. You defined a delimited identifier as blanks. You must enter at least one nonblank character. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) Recovery. Declare the cursor in a way that matches the statement and resubmit. SQL 3007 3007 In an ALLOCATE CURSOR statement, both the cursor and the statement must be named using string host variables. Cause. You specified an ALLOCATE CURSOR statement with invalid syntax. Both the cursor and the statement must be named using string host variables. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. Recovery. Specify a valid character set and resubmit. SQL 3011 3011 name is not a valid qualified name; it has more than 3 name parts. Where name is the name specified in the operation. Cause. You specified an invalid name name, which must have three or fewer parts. catalog.schema.table is valid. catalog.schema.table.name is invalid. Effect. The operation fails. Recovery. Correct the name and resubmit.
Parser and Compilation Messages (3000 through 3999) Recovery. Redefine the item with a precision value of 18 or less. SQL 3015 3015 Scale value cannot exceed precision value. Cause. You defined a scale value with greater precision than NonStop SQL/MX allows. Effect. The operation fails. Recovery. Redefine the scale with a precision value less than or equal to the allowable value. SQL 3016 3016 Precision of decimal, value, cannot exceed 18. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3019 3019 An unsigned number was expected within the parentheses, not value. Cause. You specified an unexpected value, value. NonStop SQL/MX requires an unsigned number. Effect. The operation fails. Recovery. Replace the value with an unsigned number and resubmit. SQL 3020 3020 An unsigned number was expected as the first operand within parentheses, not value. Cause. You specified an unexpected value, value.
Parser and Compilation Messages (3000 through 3999) SQL 3023 3023 The COLLATE clause in a sort specification is not yet supported. Cause. You attempted to perform a COLLATE clause in a sort specification, which is not supported. Effect. NonStop SQL/MX ignores the COLLATE clause. Recovery. Remove the COLLATE clause and resubmit. SQL 3024 3024 The MATCH PARTIAL clause is not yet supported. Cause. You attempted to use a MATCH PARTIAL clause, which is not supported. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3027 3027 name is not a valid simple name; it has more than one name part. Cause. You specified an invalid name name, which must have only one name part. Effect. NonStop SQL/MX could not prepare the statement. Recovery. Correct the name and resubmit. SQL 3028 3028 Specifying a privilege column list in the INSERT clause is not yet supported. Cause. You attempted to specify a privilege column list in an INSERT clause, which is not supported. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3031 3031 CASCADE drop behavior is not yet supported. Cause. You attempted to drop an object with the CASCADE option, which is not supported. Effect. The operation fails. Recovery. Drop the item without CASCADE. SQL 3032 3032 The COLUMN clause in the ALTER TABLE statement is not yet supported. Cause. You used the COLUMN clause in the ALTER TABLE statement, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3035 3035 The RENAME clause in the ALTER TABLE statement is not yet supported. Cause. You used the RENAME clause in the ALTER TABLE statement, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3036 3036 The SET CONSTRAINT clause in the ALTER TABLE statement is not yet supported. Cause. You used the SET CONSTRAINT clause in the ALTER TABLE statement, which is not supported. Effect. The operation fails.
Parser and Compilation Messages (3000 through 3999) SQL 3039 3039 PIC X types do not have any COMP representation. Cause. You specified a PIC X type with COMP, which is not supported. Effect. The operation fails. Recovery. Remove the COMP, or redefine the type, and resubmit. SQL 3040 3040 Precision zero is not valid. Add a '9' to the PICTURE clause. Cause. You specified an item with precision zero. You must add the number nine to the PICTURE clause. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3043 3043 Precision greater than 18 for a COMP numeric type is not valid. Cause. You specified a precision value greater than 18 for a COMP numeric type, which is not supported. Effect. The operation fails. Recovery. Change the precision to a value of 18 or less and resubmit. SQL 3044 3044 The interval value is not valid. Cause. You specified an invalid interval value. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the timestamp value to a valid one and resubmit. SQL 3048 3048 Dynamic parameters, such as name, are not allowed in a static compilation. Cause. You attempted to use parameters in a static compilation, which is not supported. Effect. The operation fails. Recovery. Remove the parameters and resubmit. SQL 3049 3049 Host variables, such as name, are not allowed in a dynamic compilation. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3052 3052 Duplicate NOT NULL clauses were specified in column definition name. Cause. You defined column name with more than one NOT NULL clause. Effect. The operation fails. Recovery. Define the column with only one NOT NULL clause and resubmit. SQL 3053 3053 Duplicate PRIMARY KEY clauses were specified in column definition name. Cause. You defined column name with more than one PRIMARY KEY clause. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3056 3056 Duplicate UPDATE rules were specified. Cause. You defined duplicate UPDATE rules. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3057 3057 The ALLOCATE value must be between 1 and number. Cause. You provided an invalid size value in the ALLOCATE clause. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for correct size values, and resubmit.
Parser and Compilation Messages (3000 through 3999) Recovery. See the SQL/MX Reference Manual for correct percentage values, and resubmit. SQL 3061 3061 The format of the specified location name name is not valid. Cause. You provided a location name with an invalid format. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for correct name format, and resubmit. SQL 3062 3062 Duplicate EXTENT/MAXEXTENTS clauses were specified in the PARTITION clause. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3065 3065 The primary key constraint cannot be droppable when the STORE BY PRIMARY KEY clause appears in a table definition. Cause. You defined a primary key as droppable in a table that includes STORE BY PRIMARY KEY in its definition, which is not supported. Effect. NonStop SQL/MX is unable to process this definition. Recovery. Change the definition of the primary key constraint so that it is NOT DROPPABLE.
Parser and Compilation Messages (3000 through 3999) SQL 3071 3071 Duplicate [NO]AUDITCOMPRESS clauses were specified. Cause. You specified duplicate [NO]AUDITCOMPRESS clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3072 3072 The BLOCKSIZE clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause. You specified an ALTER INDEX...ATTRIBUTE(S) statement that includes a BLOCKSIZE clause, which is not supported. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3075 3075 The [NO]COMPRESS clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause. You specified an ALTER INDEX...ATTRIBUTE(S) statement that includes a [NO]COMPRESS clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3076 3076 Duplicate DEALLOCATE clauses were specified. Cause. You specified duplicate DEALLOCATE clauses. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3079 3079 Duplicate EXTENT/MAXEXTENTS clauses were specified. Cause. You specified duplicate EXTENT/MAXEXTENT clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3080 3080 The [NO]SERIALWRITES clause is not supported. Cause. You specified the [NO]SERIALWRITES clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3081 3081 Duplicate ALLOCATE clauses were specified.
Parser and Compilation Messages (3000 through 3999) SQL 3084 3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause. You specified an ALTER TABLE...ATTRIBUTE(S) statement that includes the BLOCKSIZE clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3085 3085 Duplicate [NO]BUFFERED clauses were specified. Cause. You specified duplicate [NO]BUFFERED clauses. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3088 3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. Cause. You specified an ALTER TABLE statement with both ALLOCATE and DEALLOCATE clauses, which is not supported. Effect. The operation fails. Recovery. Correct the ALTER TABLE statement to include either ALLOCATE or DEALLOCATE. SQL 3089 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause. You specified an ALTER TABLE..
Parser and Compilation Messages (3000 through 3999) SQL 3092 3092 Duplicate BLOCKSIZE clauses were specified. Cause. You specified a statement with duplicate BLOCKSIZE clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3093 3093 Duplicate DCOMPRESS clauses were specified. Cause. You specified a statement with duplicate DCOMPRESS clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the syntax and resubmit. SQL 3097 3097 The DEALLOCATE clause is not allowed in the CREATE TABLE statements. Cause. You specified a CREATE TABLE statement that includes the DEALLOCATE clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3098 3098 Duplicate LOCATION clauses were specified. Cause. You specified a statement with duplicate LOCATION clauses. Effect. The operation fails.
Parser and Compilation Messages (3000 through 3999) SQL 3101 3101 Duplicate ISLACK clauses were specified. Cause. You specified a statement with duplicate ISLACK clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3102 3102 Duplicate PARALLEL EXECUTION clauses were specified. Cause. You specified a statement with duplicate PARALLEL EXECUTION clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3105 3105 Only range, hash, and system partitioning are currently supported. Cause. You attempted to specify an invalid partitioning method. Currently only range, hash, and system partitioning are supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3106 3106 Duplicate PRIMARY KEY clauses were specified. Cause. You specified a statement with duplicate PRIMARY KEY clauses. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause. You specified a statement with duplicate STORE BY clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3110 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. Cause. You specified a statement with both LIKE and ATTRIBUTE(S) clauses, which is not supported. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3113 3113 Error in CONTROL statement: number Where number is the error number. Cause. There is an error number in the CONTROL statement you specified. Effect. The operation fails. Recovery. Correct the CONTROL statement and resubmit. SQL 3114 3114 Transaction access mode READ WRITE is incompatible with isolation level READ UNCOMMITTED. Cause. You specified a statement with both READ WRITE and READ UNCOMMITTED clauses, which is not supported. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3117 3117 Duplicate DIAGNOSTICS SIZE clauses were specified. Cause. You specified a statement with duplicate DIAGNOSTICS SIZE clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3118 3118 Specified identifier is too long. Cause. You specified an identifier that is too long. Effect. The operation fails. Recovery. Shorten the identifier and resubmit. SQL 3119 3119 The WITH LOCAL CHECK OPTION clause is not supported.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the syntax and resubmit. SQL 3122 3122 The system specified in the location clause name is not accessible. Where name is the system name. Cause. You specified an invalid name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3123 3123 The format of the file name part in the specified location name name is not valid. The file name part must be eight characters long and end with the digits 00.
Parser and Compilation Messages (3000 through 3999) Recovery. Enclose the identifier in double quotes or select another name that is not a reserved word. SQL 3129 3129 Function name accepts exactly one operand. Where name is the name of the function. Cause. You specified two operands for an aggregate function that accepts exactly one operand. Only VARIANCE and STDDEV support two operands. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3133 3133 PERFORM is valid only in COBOL programs. Cause. You specified a PERFORM statement, which is supported only in COBOL programs. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3134 3134 The precision of time or timestamp, value, cannot exceed 6. Cause. You specified a time or timestamp precision value that exceeds six, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3137 3137 UNION JOIN is not yet supported. Cause. You attempted to perform a UNION JOIN, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3138 3138 A key-sequenced table with range partitioning requires a FIRST KEY clause. Cause. You attempted to create a key-sequenced table with range partitioning without a FIRST KEY clause. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3141 3141 The transaction access mode cannot be READ ONLY for an INSERT, UPDATE, DELETE, or DDL statement. Cause. You attempted to perform an INSERT, UPDATE, DELETE, or DDL statement with a transaction access mode of READ ONLY, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3142 3142 INTO clause host variables not allowed in a static cursor. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3147 3147 In an IN predicate whose right operand is a value list, the left operand must be scalar (degree of one). Cause. You specified an IN predicate whose right operand is a value list but whose left operand is not scalar, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3148 3148 Environment variable value is being ignored because this version of the code is Release, not Debug.
Parser and Compilation Messages (3000 through 3999) SQL 3151 3151 Duplicate WITH HORIZONTAL PARTITIONS phrases were specified in LIKE clause in CREATE TABLE statement. Cause. The WITH HORIZONTAL PARTITIONS phrase appears multiple times within the LIKE clause of the CREATE TABLE statement, which is not supported. Effect. The operation fails. Recovery. Remove the duplicate WITH HORIZONTAL PARTITIONS phrases. SQL 3153 3153 The FIRST KEY clause is not allowed with hash partitioning. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3158 3158 The DATETIME value value is not valid. Cause. You specified an invalid DATETIME literal. Either the DATETIME qualifier has an invalid combination of start and end fields or the DATETIME literal string is invalid. Effect. The operation fails. Recovery. Specify a valid DATETIME literal and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3161 3161 procedure parameter was not declared in the procedure parameter list. Cause. You did not declare procedure parameter in the parameter list, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3162 3162 Procedure parameter name was not used. Where name is the name of the procedure parameter. Cause. NonStop SQL/MX did not use procedure parameter name. Effect. None. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3165 3165 The precision or exponent value specified in value was less than the minimum allowed or greater than the maximum allowed. Cause. You specified a statement in which you exceed the min or max precision or the exponent value. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3166 3166 The value specified in the float or double value was less than the minimum allowed or greater than the maximum allowed. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3169 3169 name is not a known collation. Cause. You attempted to use a collation that is not a known collation. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3171 3171 Transaction statements are not allowed in compound statements. Cause. You specified a compound statement that contains transaction statements, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3174 3174 DDL statements are not allowed in compound statements. Cause. You specified a compound statement that contains DDL statements. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3175 3175 Dynamic SQL statements are not allowed in compound statements. Cause. You specified a compound statement that contains dynamic SQL/MX statements. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3178 3178 One or more of the following external (host-language) data types incorrectly appears within the SQL query or operation: name. Cause. You specified an SQL/MX query or attempted to perform an operation with an incorrect data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3179 3179 Collation name1 is not defined on the character set name2. Where name1 is the name of the collation.
Parser and Compilation Messages (3000 through 3999) SQL 3182 3182 Extra semicolon(;) in a compound statement. Cause. You specified an extra semicolon in a compound statement. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3183 3183 Duplicate clause-name clauses were specified. Where clause-name is the clause specified. Cause. You specified a CREATE PROCEDURE containing multiple occurrences of the clause-name clause. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) SQL 3186 3186 string: Dynamic parameters and host variables are currently not allowed in DDL. Where string is the dynamic parameter or host variable that was specified. Cause. NonStop SQL/MX does not support the use of dynamic parameters or host variables in DDL statements. Effect. The operation fails. Recovery. Remove occurrences of dynamic parameters or host variables and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3192 3192 Union operands table1 and table2 have different access/lock modes. Cause. NonStop SQL/MX attempted to compile a UNION query that has an access/lock mode that can be applied to both branches of the access/lock mode or only to the second branch of the UNION. Effect. The access/lock mode is applied only to the second branch of the UNION. Recovery. Specify that the access/lock mode apply to both branches and resubmit.
Parser and Compilation Messages (3000 through 3999) Recovery. Remove all but one of the table-level access options for each table reference. SQL 3197 3197 Only one lock clause may be specified for a single table SELECT. Cause. You specified two or more table-level lock options for the same table reference. Effect. The offending SQL statement is rejected with an error. Recovery. Remove all but one of the table-level access options for each table reference.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the syntax and resubmit. SQL 3203 3203 LANGUAGE clause is required. Cause. In the CREATE PROCEDURE statement, you omitted this mandatory LANGUAGE clause. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3204 3204 EXTERNAL NAME clause is badly formed. Cause. In the CREATE PROCEDURE statement, the EXTERNAL NAME clause you specified does not conform to the required syntax. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3207 3207 Value for DYNAMIC RESULT SETS must be zero. Cause. In the CREATE PROCEDURE statement, you specified the optional DYNAMIC RESULT SETS clause with nonzero value. Effect. The operation fails. Recovery. Remove the clause or use the value zero, and then resubmit. SQL 3208 3208 UNSIGNED numeric is not allowed for routine parameter. Cause. In the CREATE PROCEDURE statement, one of the parameters you specified is an unsigned numeric. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3211 3211 Maximum length of LONG VARBINARY is value. Cause. You attempted a CREATE TABLE table name (columnname long varbinary(N)) where N > current MAX_LONG_VARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery. Decrease the CREATE TABLE statement’s long varbinary column width N or increase the current MAX_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit. SQL 3212 3212 Minimum length of LONG VARBINARY is value. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3215 3215 Computed LONG VARCHAR length len1 is below minimum len2. Cause. You attempted a CREATE TABLE table name (c1 longvarchar, c2 long varchar,...cn long varchar) and the computed long varchar columns’ width is below the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) Effect. The statement does not compile. Recovery. Do not use DELETE or UPDATE in a CREATE VIEW statement. SQL 3219 3219 The value for DYNAMIC RESULT SETS must be between 0 and 255. Cause. In a CREATE PROCEDURE statement, you specified the optional DYNAMIC RESULT SETS clause with an invalid value. Effect. The operation fails. Recovery. Remove the clause or use a value between zero and 255 and resubmit. HP NonStop SQL/MX Release 3.
Parser and Compilation Messages (3000 through 3999) SQL 3220 3220 SHOWDDL failed for object object-name because an SQL/MP display option was used on a SQL/MX object. Where object-name specifies the ANSI name of a table, view, or SQL/MP ALIAS. Cause. SHOWDDL was given the SQL/MP display option with an SQL/MX table given as an argument. Effect. SHOWDDL does not display output. Recovery. Reissue the command without the SQL/MP display option or specify an SQL/MP object.
Parser and Compilation Messages (3000 through 3999) SQL 3227 3227 SHOWLABEL failed for object object-name. SHOWLABEL does not support SQL/MP objects or SQL/MP aliases. Where object-name specifies the ANSI name of an object. Cause. SHOWLABEL was unable to find the object in the specified namespace, or the object is unsupported. Effect. SHOWLABEL does not display output. Recovery. Reissue the command with a valid, supported object name and corresponding namespace.
Parser and Compilation Messages (3000 through 3999) Recovery. Do not use a hexadecimal format for the character set you specified. SQL 3402 3402 The format of the value hexadecimal string literal is not valid. Cause. You either used illegal hexadecimal digits, supplied an odd number of hexadecimal digits, or misplaced space separators. Effect. The operation fails. Recovery. Specify the string in the correct hexadecimal format and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3406 3406 A DDL statement could not be translated into a statement consisting of single-byte characters for processing. Cause. The DDL statement coded in unicode contains non-ISO88591 characters. NonStop SQL/MX does not support arbitrary unicode characters. Effect. The operation fails. Recovery. Remove non-ISO88591 characters and resubmit. SQL 3409 3409 Declaring a cursor on an embedded INSERT statement is not yet supported. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3415 3415 The first operand of function name is not valid. Where name is the name of the function. Cause. The first operand you supplied for function name is not an allowed value. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3416 3416 The last operand of function name must not be NULL. Where name is the function name. Cause. A NULL value is specified as last operand for function name . Effect. The operation fails.
Parser and Compilation Messages (3000 through 3999) Recovery. For GENERATED ALWAYS AS IDENTITY type IDENTITY column, value is generated for the IDENTITY column. Resubmit the INSERT statement to allow the default characteristics of the column to generate the value internally. SQL 3431 3431 For a table with a single column that is an IDENTITY column, col-name, the tuple list cannot have only DEFAULT values. Specify values for all. Where col-name is the IDENTITY column name. Cause.
Parser and Compilation Messages (3000 through 3999) HP NonStop SQL/MX Release 3.
6 Binder and Compilation Messages (4000 through 4999) SQL 4000 4000 Internal error in the query binder. Cause. NonStop SQL/MX received an internal error in the query binder. Effect. NonStop SQL/MX is unable to process this query. Recovery. None. Report the entire message to your service provider. SQL 4001 4001 Column name1 is not found. Default schema: name3. Tables in scope: name2. Cause. You referenced column name1, which NonStop SQL/MX could not find.
Binder and Compilation Messages (4000 through 4999) SQL 4002 4002 Column name1 is not found. Table name2 not exposed. Tables in scope: name3. Default schema: name4. Cause. You referenced column name1, which NonStop SQL/MX could not find. Table name2 is not exposed. The table name3 or tables in the scope of the column reference and the default schema name4 appear. Effect. The operation fails. Recovery. Correct the syntax so that the table and column can be found, and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4005 4005 Column reference name must be a grouping column or be specified within an aggregate. Cause. You referenced column name, which is not a grouping column or is not specified within an aggregate, which is not supported. Effect. The operation fails. Recovery. Correct the column reference and resubmit. SQL 4006 4006 Within an aggregate, all column references must come from the same scope. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4009 4009 An aggregate is not allowed inside an aggregate function. Cause. You specified an aggregate inside an aggregate function. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4010 4010 There are no columns with the correlation name table name. Cause. You specified columns with the table name qualifier, which does not exist or is not in scope at this point in the query. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4013 4013 Column name is a system column and cannot be updated or inserted into. Cause. You attempted to update or insert into a system column name, which is not supported. Effect. The operation fails. Recovery. Correct the syntax to refer to a nonsystem column. SQL 4014 4014 The operands of an INTERSECT must be of equal degree. Cause. You created an INTERSECT with operands of unequal degree. They must be equal. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4017 4017 Derived column name name was specified more than once. Cause. You specified column name more than once. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4018 4018 Rows cannot be deleted from an entry-sequenced table. Cause. You attempted to delete rows from an entry-sequenced table, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4021 4021 The select list contains a nongrouping non-aggregated column, name. Cause. You specified a select list that contains a nongrouping, nonaggregated column name, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4022 4022 Target column name was specified more than once. Cause. You specified column name more than once. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4025 4025 Error while preparing constraint name on table table name. Where table name is the name of the table. Cause. NonStop SQL/MX received an error while preparing constraint name on table name. See accompanying error messages. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4028 4028 Table or view name is not updatable. Cause. You attempted to update table name, which is not updatable. Effect. The operation fails. Recovery. None. SQL 4030 4030 Column name has an invalid combination of datetime fields (internal field number, internal field number, internal field number). Cause. You specified column name, which is an invalid combination of datetime fields. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4033 4033 Column name is a primary or clustering key column and cannot be updated. Cause. You attempted to update column name, which is a primary or clustering key column that cannot be updated. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4034 4034 The operation (data type operation data type) operation is not allowed. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4037 4037 Field name cannot be extracted from a source of type specification. Cause. You attempted to extract field name from a source whose type specification does not support this. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4038 4038 The operand of an AVG or SUM function must be numeric or interval. Cause. You attempted to perform an AVG or SUM function with an invalid operand. It must be numeric or interval.
Binder and Compilation Messages (4000 through 4999) SQL 4041 4041 Type specification1 cannot be compared with type specification2. Cause. You attempted to compare two type specifications that cannot be compared. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4042 4042 The operands of a comparison predicate must be of equal degree. Cause. You specified a comparison predicate with operands that are not of equal degree, which is required. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4045 4045 The operand of function name must be numeric. Cause. You specified operands for function name that are not numeric, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4046 4046 The operands of function name must be exact numeric. Cause. You specified operands of function name that are not type exact numeric, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4049 4049 A CASE expression cannot have a result data type of both type1 and type2. Cause. You specified a CASE expression with a result data type of two data types. It must be one of data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4050 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation). Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4053 4053 The third operand of function name must be numeric. Cause. You specified the third operand of a function name with a type other than numeric, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4055 4055 The select lists or tuples must have comparable data types. type1 and type2 are not comparable. Cause. You specified select lists or tuples with incompatible data types. Effect.
Binder and Compilation Messages (4000 through 4999) SQL 4059 4059 The first operand of function name must be numeric. Cause. You specified the first operand of function name with a type other than numeric, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4060 4060 Reading from and inserting, or updating in, or deleting from the same table, name1, is not currently supported. name1 is contained by view(s) name2. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4063 4063 The operands of function name must be comparable character data types (that is, of the same character set and collation). Cause. You specified operands for function name with noncomparable character data types. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4064 4064 The operands of function name must be compatible character data types (that is, of the same character set). Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4068 4068 The operand of function name must contain an even number of characters. Cause. You specified invalid operands for function name. They must contain an even number of characters. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4069 4069 Column name uses an unsupported collation. Cause. You specified a column name that uses an unsupported collation. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4072 4072 The operand of function name must be a datetime containing a name. Cause. You specified an invalid operand for function name. It must be a datetime operand containing the variable listed in the message. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4073 4073 The COLLATE clause may appear only after an expression of character data type, not data type. Cause.
Binder and Compilation Messages (4000 through 4999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4077 4077 Function name accepts only one or two operands. Cause. You specified an invalid argument in function name. This function accepts only one or two arguments, both numeric. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4078 4078 Function name does not accept a weight operand. Cause. You specified an invalid argument in function name.
Binder and Compilation Messages (4000 through 4999) SQL 4081 4081 SQL/MP error: number Cause. NonStop SQL/MX has received error number from SQL/MP. Effect. The operation fails. Recovery. Use the error number to determine the problem. SQL 4082 4082 Object name does not exist or is inaccessible. Cause. You referred to object name, which does not exist or is inaccessible (for example, on a downed disk volume). Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4085 4085 File organization name1 of object name2 is not supported. Cause. You specified an invalid file organization name1 (for example, "R" for Relative) for table name2. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4086 4086 Environment variable or define value does not exist. Cause. You specified an environment variable or define value that does not exist. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4089 4089 Check constraint name contains a subquery. This is not yet supported. Cause. You specified a constraint name that contains a subquery, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4093 4093 The number of output dynamic parameters (value1) must equal the number of selected values (value2). Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4096 4096 A DEFAULT specification is currently allowed only when simply contained in the VALUES list of an INSERT. Cause. You specified a DEFAULT value that was not contained in the VALUES list of an INSERT. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4097 4097 A NULL operand is not allowed in function name. Cause. You attempted to use a NULL operand in function name, which is not supported. Effect.
Binder and Compilation Messages (4000 through 4999) SQL 4100 4100 A NULL value is not allowed in a select list unless it is CAST to some data type. Cause. You specified a NULL value in a select list that is not cast to a data type, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4101 4101 If name is intended to be a further table reference in the FROM clause, the preceding join search condition must be enclosed in parentheses. Cause.
Binder and Compilation Messages (4000 through 4999) Recovery. See the Operator Messages Manual for information on EMS event messages. SQL 4104 4104 If a character literal was intended, you must use the single quote delimiter: ‘literal’. The use of double quotes causes SQL/MX to interpret column name as a delimited identifier column name. Where column name is a delimited ANSI identifier, such as MYCOL. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4107 4107 Column name has no default value, so DEFAULT cannot be specified. Cause. In the source value list of INSERT, you specified DEFAULT for column name, but there is no default value for that column. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4108 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. Cause.
Binder and Compilation Messages (4000 through 4999) Recovery. Correct the syntax and resubmit. For example: >>select a from T1 where runningcount(b) > 10 sequence by a; *** ERROR[4109] Sequence functions placed incorrectly: RUNNINGCOUNT(CAT.SCH.HPPARTEST1.B). *** ERROR[8822] Unable to prepare the statement. SQL 4110 4110 The query contains sequence functions but no SEQUENCE BY clause: name. Cause.
Binder and Compilation Messages (4000 through 4999) Correct the syntax with one of these: >>select a, runningavg(c) from T1 sequence by a; >>select a from T1 order by a; SQL 4112 4112 Absolute and relative sampling cannot occur in the same BALANCE expression. Cause. You attempted to perform absolute and relative sampling in the same balance expression, which is not supported. Effect. NonStop SQL/MX is unable to prepare the query. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4116 4116 The second operand of function name is not valid. Cause. You specified an invalid operand for the second operand of function name. For example, a numeric literal operand (for example, 9999999999999999999) cannot be represented as a valid compile-time constant value. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4118 4118 The cursor query expression is not updatable. Cause. You specified a join or a nonupdatable query in an updatable cursor query (that is, one with an optional FOR UPDATE OF clause). A join query is not updatable. Effect. The operation fails. Recovery. An updatable cursor query should not specify a join or a nonupdatable query. An SQL/MX statement cursor is updatable if all the following are true: It is a SELECT statement.
Binder and Compilation Messages (4000 through 4999) SQL 4120 4120 In a query with a GROUP BY, DISTINCT, or aggregate function, each column in the ORDER BY clause must be one of the columns explicitly SELECTed by the query. Column in error: name. Cause. You attempted to perform a query with an aggregate function, a GROUP BY clause, or a DISTINCT clause. A column in the ORDER BY clause, name, is not one of the columns explicitly selected by the query. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) SQL 4124 4124 More than one table will be locked: name. Where name is the name of the table. Cause. NonStop SQL/MX is preparing to lock more than one table. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 4125 4125 The select list of a subquery in a row value constructor must be scalar (degree of one) if the subquery is one of several expressions rather than the only expression in the constructor. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4128 4128 Default volume and subvolume information could not be retrieved from =_DEFAULTS define - DEFINEINFO error number. Where number is the error message. Cause. NonStop SQL/MX was not able to retrieve default volume and subvolume information using the =_DEFAULTS define. Effect. The operation fails. Recovery. Check the =_DEFAULTS define and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4134 4134 The operation (name) is not allowed. instead. Try UNION ALL Cause. You attempted to perform an operation that NonStop SQL/MX does not allow. Effect. The operation fails. Recovery. Try a UNION ALL operation and resubmit. SQL 4135 4135 In an INSERT-SELECT, each column in the ORDER BY clause must be one of the columns in the selected list of the query. Column in error: B. Cause.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the statement and resubmit. SQL 4152 4152 Table name cannot be both read and updated. Cause. You attempted to read from and update the same table. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4153 4153 Statement may not compile due to an order requirement on stream expression. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4157 4157 Inner relation of left join cannot be stream expression. Tables in scope: name. Cause. You attempted to perform a left join using the result set of a stream expression as the inner relation. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4158 4158 Join of stream expressions is not supported. Tables in scope: name. Cause. You attempted to perform a join of stream expressions.
Binder and Compilation Messages (4000 through 4999) SQL 4161 4161 Embedded INSERT, UPDATE, or DELETE statement is not allowed in a UNION operation. Tables in scope: table-names1, table-names2. Where table-names1 and table-names2 are names of NonStop SQL/MX tables that are in scope. Cause. You attempted to perform a UNION operation that has embedded an INSERT, UPDATE, or DELETE statement. Effect. The operation failed. Recovery. Modify the statement and resubmit.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the statement and resubmit. SQL 4165 4165 Outer relation of right join cannot be stream expression. Tables in scope: name. Cause. You attempted to perform a right join using a stream expression as the outer relation. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4166 4166 ORDER BY clause is not supported in UNION of two streams. Tables in scope: name1, name2. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4169 4169 Embedded delete statements are not allowed when using DECLARE ... FOR UPDATE clause. Cause. You attempted to perform a DECLARE... FOR UPDATE clause that included an embedded DELETE statement. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4170 4170 Stream expressions are not supported for insert statements. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4174 4174 JOIN_ORDER_BY_USER prevented compiler from reordering query tree. Cause. The SQL/MX compiler could not reorder the join tree because the JOIN_ORDER_BY_USER directive is in effect. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Disable the JOIN_ORDER_BY_USER directive and resubmit. SQL 4175 4175 Join between embedded name1 expression and embedded name2 expression is not supported. Tables in scope: name3. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4178 4178 Update of variable length column name is not permitted on rollback. Cause. You attempted to perform a rollback that included an update of a variable length column. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4179 4179 SEQUENCE BY is not supported for stream expressions. Cause. You included a SEQUENCE BY statement in a stream expression. Effect.
Binder and Compilation Messages (4000 through 4999) SQL 4184 4184 Columns that are part of a referential constraint cannot be updated using embedded UPDATE statements. Cause. You attempted to perform an embedded UPDATE statement on columns that are part of a referential constraint. Effect. The operation fails. Recovery. Modify the statement and resubmit. SQL 4193 4193 The schema name prefix volatile-schema-prefix is reserved and cannot be used.
Binder and Compilation Messages (4000 through 4999) SQL 4198 4198 Clustering key columns cannot be specified in the SET clause of an embedded UPDATE statement. Cause. Clustering key columns were specified in the SET clause of an embedded UPDATE statement. Effect. The statement does not compile. Recovery. Remove the clustering key columns from the SET clause and compile the statement again. SQL 4200 4200 Stream expressions are not supported for compound statements. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4203 4203 Insert/Update/Delete operation on non-audited table name requires index maintenance which may cause the index(es) to become corrupt. Performing INSERT, UPDATE, or DELETE operations on a nonaudited table could corrupt the index if the operation is interrupted. Use the IUD_NONAUDITED_INDEX_MAINT attribute value to control if these operations create an error condition, are allowed with a warning, or are allowed with no warning.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the statement and resubmit. SQL 4206 4206 Embedded name is supported only for updatable views. View: name2. Cause. You attempted to perform an embedded action that is supported only for updatable views. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4207 4207 Index name and other indexes covering a subset of columns do not cover all output values of stream. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4210 4210 Embedded update/delete statements not supported within an IF statement. Cause. You attempted to embed UPDATE/DELETE statements within an IF statement. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4212 4212 table name cannot be used to satisfy order requirement on the stream because it is partitioned. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4215 4215 Stream access is not allowed on a non-audited table. Table: name. Cause. You attempted to use stream access on a nonaudited table. Effect. The operation fails. Recovery. Change the table’s AUDIT attribute and resubmit. SQL 4216 4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded delete statement. Cause. You attempted to use either a FIRST n or an ANY n clause in an embedded UPDATE or DELETE statement. Effect.
Binder and Compilation Messages (4000 through 4999) SQL 4302 4302 Procedure procedure-name expects value1 parameters but was called with value2 parameters. Cause. In the SQL/MX statement being compiled, a stored procedure invocation contains an incorrect number of parameters. Effect. The SQL/MX statement is not compiled. Recovery. Correct the SQL/MX statement and retry the compilation.
Binder and Compilation Messages (4000 through 4999) SQL 4305 4305 Parameter value for user-defined routine routine-name is an OUT or INOUT parameter and must be a host variable or a dynamic parameter. Cause. In the SQL/MX statement being compiled, you attempted to invoke a stored procedure that has an OUT or INOUT parameter that is neither a host variable nor a dynamic parameter. Effect. The SQL/MX statement is not compiled. Recovery. Correct the SQL/MX statement.
Binder and Compilation Messages (4000 through 4999) SQL 4307 4307 Rowset parameters are not allowed in a CALL statement. Cause. In the SQL/MX statement being compiled, you attempted to use a rowset as a parameter in a stored procedure invocation. Effect. The SQL/MX statement is not compiled. Recovery. Alter the data type of the relevant variable, or use a different nonrowset host variable. Retry the compilation.
Binder and Compilation Messages (4000 through 4999) Recovery. Correct the query and retry the request. SQL 4313 4313 Function rand()is not supported. Cause. You attempted to use the random function, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4320 4320 Stream access not allowed on multi-partitioned table, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set to OFF. Table in scope: table-name. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4335 4335 The degree num1 specified for the left operand of the PARTITIONING KEY clause does not match the number of columns num2 in the partitioning key for table tablename. Where, num1 is the number of columns specified for the left operand of PARTITIONING_KEY option in the KEY_RANGE_COMPARE function. num2 is the number of columns in the partitioning key of the table tablename.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the statement and resubmit. SQL 4338 4338 Procedure label $0~String0 could not be accessed. File system error: $1~NSKCode. Cause. The procedure label or surrogate label of the procedure, which stores privilege information, cannot be accessed because it is corrupted or accidentally deleted. Effect. You cannot use the user-defined procedure associated with that label. Recovery. Retry the operation.
7 Normalizer Messages (5000 through 5999) SQL 5000 5000 Internal error in the query normalizer. Cause. The optimizer received an internal error during query normalization. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Release 3.
Normalizer Messages (5000 through 5999) HP NonStop SQL/MX Release 3.
8 Optimizer Messages (6000 through 6999) SQL 6000 6000 Internal error in the query optimizer. Cause. The optimizer received an internal error during query optimization. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 6001 6001 DISTINCT aggregates can be computed for only one column per table expression. Cause. You attempted to compute DISTINCT aggregates for more than one column. Effect. DISTINCT aggregates can be computed only for one column per table expression. Recovery.
Optimizer Messages (6000 through 6999) SQL 6003 6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name. If you have manually modified the metadata table, you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics. Cause. You have manually modified the metadata table, and now it contains an invalid boundary value. Effect. NonStop SQL/MX uses default histograms to compile the query.
Optimizer Messages (6000 through 6999) Recovery. None. SQL 6008 6008 Statistics for column column-name from table table-name were not available. As a result, the access path chosen might not be the best possible. Where column-name is the name of the affected column. Where table-name is the name of the SQL/MX table to which the columns belong. Cause. Statistics for the column were not generated. Effect. None. The plan generated by the optimizer might not be optimal. This is a warning message. Recovery.
Optimizer Messages (6000 through 6999) HP NonStop SQL/MX Release 3.
9 Generator Messages (7000 through 7999) SQL 7000 7000 An internal error occurred in the code generator in file name at line number: text. Cause. The code generator received an internal error in file name at line number. Additional information appears in text. Effect. The operation fails. Recovery. Contact your service provider. SQL 7001 7001 Default value value is not valid for column name. Cause. You attempted to create a table with an invalid default value for column name. Effect. The operation fails.
Generator Messages (7000 through 7999) HP NonStop SQL/MX Release 3.
10 Executor Messages (8000 through 8999) SQL 8001 8001 An internal executor error occurred. Cause. NonStop SQL/MX has received an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8002 8002 The current nowaited operation is not complete. Cause. A nowait CLI operation was started. Effect. The operation is not complete. Recovery. Ignore this message if the SQL/MX statement completes successfully.
Executor Messages (8000 through 8999) SQL 8005 8005 Trying to fetch from a cursor that is not in the open state. Cause. You attempted to fetch from a cursor that is not open. Effect. The operation fails. Recovery. Open the cursor before trying to fetch. SQL 8006 8006 The stream timed out, but the cursor is still open. Cause. A cursor is still open although its stream timed out. Effect. The operation fails. Recovery. Close the cursor before trying to open it. SQL 8007 8007 The operation has been canceled.
Executor Messages (8000 through 8999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8010 8010 Default catalog name: name1. name2. Default schema name: Where catalog name1 is the name of the catalog. Where schema name2 is the name of the schema. Cause. NonStop SQL/MX displays the default catalog and schema names. Effect. None. Recovery. This is an informational message only; no corrective action is needed. SQL 8011 8011 SELECT statement inside compound (BEGIN ...
Executor Messages (8000 through 8999) Recovery. Fetch the cursor and resubmit. SQL 8014 8014 A SELECT statement within compound statement did not return any row. Cause. You specified a SELECT statement inside a compound statement that did not return any rows. Effect. None. Recovery. This is an informational message only; no corrective action is needed. SQL 8015 8015 Aborting transaction because a compound statement performed an update operation followed by a SELECT statement that did not return any row.
Executor Messages (8000 through 8999) Recovery. Turn the explain default on for this query. SQL 8018 8018 Partition name1 of table name2 could not be accessed due to file system error number. It is skipped because the default SKIP_UNAVAILABLE_PARTITION was set. Where name1 is the name of the partition. Where name2 is the name of the table. Where number is the file system error returned. Cause. Attempt to open partition name1 of the table name2 failed, returning the file system error code number. Effect.
Executor Messages (8000 through 8999) table will then have a valid row count although the row count for the source table will remain invalid. SQL 8100 8100 Define name does not exist. Cause. You attempted to reference a define that does not exist. Effect. The operation fails. Recovery. Define the item, or use the correct define name. SQL 8101 8101 The operation is prevented by check constraint name1 on table name2. Where constraint name1 is the name of the constraint.
Executor Messages (8000 through 8999) Cause. You attempted to perform an operation on table name1 that is prevented by referential integrity constraint name2. Effect. The operation fails. Recovery. Change the data you are attempting to enter to be consistent with the constraint. The data must exist in another table. For example, if you are trying to enter a department number for an employee, the department number must exist in a department number table.
Executor Messages (8000 through 8999) Effect. The UPDATE/DELETE WHERE CURRENT statement is invalid. Recovery. Perform another FETCH then an UPDATE/DELETE. SQL 8140 8140 The statement was canceled, to test cancel processing. File name at line number. Where name is the name of the file. Where number is the line number. Cause. You set an environmental variable to test cancel processing. Effect. The statement was canceled. Recovery. Execute the statement again after first resetting the environmental variable.
Executor Messages (8000 through 8999) SQL 8301 8301 File system error error occurred on anchor file name. Where error is the Guardian file system error code. Where name is the fully qualified Guardian file name of an SQL/MX anchor file. Cause. Access to the specified anchor file failed and returned a Guardian file system error code. Effect. Late name resolution fails. Recovery. Correct the error and resubmit. SQL 8302 8302 All partitions of type object are unavailable.
Executor Messages (8000 through 8999) SQL 8350 8350 Character set set1 and set2 are not assignment compatible. Where set1 and set2 are the character sets of two character types. Cause. The two character sets are different. As a result, an assignment between the two character types cannot be made. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8402 8402 22001 A string overflow occurred during the evaluation of a character expression. Conversion of Source Type: source-data-type(internal-type) Source Value:string-value to Target Type:target-data-type(internal-type). Where source-data-type(internal-type) is the character string data type (and an internal representation of the data type) of the column to which the SQL statement refers.
Executor Messages (8000 through 8999) Recovery. Correct the syntax and resubmit. SQL 8405 8405 The operand of function CONVERTTIMESTAMP is out of range. Cause. You attempted to reference the operand of a CONVERTTIMESTAMP function that is out of range. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8407 8407 The operand of function JULIANTIMESTAMP is out of range. Cause. A statement attempted to reference the operand of a JULIANTIMESTAMP function that is out of range. Effect.
Executor Messages (8000 through 8999) SQL 8411 8411 A numeric overflow occurred during an arithmetic computation or data conversion. Cause. A computation has resulted in an item that overflows its field. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 8412 8412 An input character host variable is missing its null terminator. Cause. You specified an input character host variable that is missing its null terminator. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8415 8415 The provided DATE, TIME or TIMESTAMP is not valid and cannot be converted. Cause. You provided an invalid DATE, TIME or TIMESTAMP, which could not be converted. Effect. The operation fails. Recovery. Check your input data and resubmit. SQL 8416 8416 A datetime expression evaluated to an invalid datetime value. Cause. NonStop SQL/MX has encountered a datetime expression that, when evaluated, is invalid. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8419 8419 An arithmetic expression attempted a division by zero. Cause. An expression attempted to divide by zero, which is invalid. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 8420 8420 Missing indicator parameter for a NULL value. Cause. You specified a NULL value that is missing an indicator parameter. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) SQL 8424 8424 Function name is not yet supported. Where name is the name of the function. Cause. You attempted to perform function name, which is not supported. Effect. The operation fails. Recovery. None. SQL 8425 8425 NULL cannot be assigned to a DEFAULT NULL NOT NULL column. Cause. You attempted to assign a null value to a column that is defined as NOT NULL. Effect. The operation fails. Recovery. Correct the syntax and resubmit, without a null value.
Executor Messages (8000 through 8999) SQL 8429 8429 The preceding error actually occurred in function name. Cause. NonStop SQL/MX detected an error in the function name. Errors will appear before this one that refer to low-level computations that this function uses. Effect. The operation fails. Recovery. Correct the function and resubmit. SQL 8432 8432 A negative value cannot be converted to an unsigned numeric datatype.$0~string0 Cause.
Executor Messages (8000 through 8999) SQL 8550 8550 Error NSK err was returned by the Data Access Manager. Where NSK err is the HP NonStop Kernel error returned. Cause. The HP NonStop Data Access Manager returned error NSK err. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 8551 8551 Error NSK err was returned by the file system on objectname. Where NSK err is the HP NonStop Kernel error returned.
Executor Messages (8000 through 8999) SQL 8553 8553 Stream overflow; subscription rate has fallen too far behind publishing rate. Cause. The table used by the streaming cursor has overflowed. Effect. The cursor or statement is closed. Recovery. Reopen the statement or cursor and resume subscribing. For more details, see “Run-Time Limits on Streams” in SQL/MX Queueing and Publish/Subscribe Services. SQL 8555 8555 An internal error occurred in the SQL/MX executor in the disk process. Cause.
Executor Messages (8000 through 8999) Recovery. Try to reduce the system's load by entering fewer statements. You can try restarting NonStop SQL/MX. If this does not correct the problem, contact your service provider. SQL 8572 8572 The statement has incurred a fatal error and must be deallocated. Cause. NonStop SQL/MX has received an internal error. Effect. The operation fails. Recovery. Reexecute the statement and resubmit it. If this does not correct the problem, stop and restart NonStop SQL/MX.
Executor Messages (8000 through 8999) SQL 8575 8575 Timestamp mismatch on table name. Where name is the name of the table. Cause. Table name has been changed, and NonStop SQL/MX was not able to recompile this statement. Effect. The operation fails. Recovery. Verify what has changed in the file and recompile this program. SQL 8576 8576 Statement was recompiled. Cause. NonStop SQL/MX recompiled the statement. Effect. The operation fails. Recovery. Recompile the program.
Executor Messages (8000 through 8999) SQL 8579 8579 Similarity check failed: name Cause. The similarity check failed. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8580 8580 No partitions of table name could be accessed. File system error number was returned. Where name is the name of the specified table. Where number is the error code returned. Cause. Attempts to open any partition of table name failed, returning file system error code number. Effect. The operation fails.
Executor Messages (8000 through 8999) SQL 8601 8601 Error returned from file system while locking/unlocking. Cause. The file system received an error while locking or unlocking. Effect. The operation fails. Recovery. If errors accompany this one, use them to diagnose and correct the problem. SQL 8602 8602 The file system reported error number on a lock/unlock operation. Where number is the error number. Cause.
Executor Messages (8000 through 8999) Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 8605 8605 Committing a transaction which has not started. Cause. You attempted to commit a transaction that has not been started. Effect. The operation fails. Recovery. Correct the syntax so that the transaction is started before it is committed, and resubmit.
Executor Messages (8000 through 8999) Where number is the error number. Cause. Transaction subsystem name has returned error number while rolling back a transaction. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 8609 8609 Waited rollback performed without starting a transaction. Cause. You attempted to perform a waited rollback on a transaction that has not started. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8613 8613 SQL cannot commit or rollback a transaction that was started by application. Cause. An application started a transaction outside of NonStop SQL/MX that NonStop SQL/MX could not commit or rollback. Effect. The operation fails. Recovery. The application that started the transaction must perform a commit or rollback. NonStop SQL/MX must start any transactions it will later commit or rollback.
Executor Messages (8000 through 8999) SQL 8710 8710 Error num returned by Measure when attempting to update SQL counters. Where num is the error number returned. Cause. Measure encountered an error while attempting to update SQL/MX counters. Effect. Measure fails to update the SQL/MX counters. Recovery. Use the error in the message to diagnose and correct the problem. SQL 8750 8750 A module cannot be unloaded when a transaction is in progress. End the transaction and retry the operation. Cause.
Executor Messages (8000 through 8999) SQL 8802 8802 Statement allocation failed because the statement already exists in the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8803 8803 The provided input descriptor does not exist in the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8807 8807 Trying to allocate more than value entries for a descriptor. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8808 8808 Module file name contains corrupted or invalid data. Where name is the name of the file. Cause. NonStop SQL/MX has detected corrupted or invalid data in the module file name. Effect.
Executor Messages (8000 through 8999) SQL 8811 8811 Trying to close a statement that is either not in the open state or has not reached EOF. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8812 8812 Trying to execute a statement that is not in the closed state. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8816 8816 An internal error occurred while executing the TCB tree. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Release 3.
Executor Messages (8000 through 8999) SQL 8817 8817 An internal error occurred while fetching from the TCB tree. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8818 8818 An internal error occurred in root_tdb describe. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8819 8819 Begin transaction failed while preparing the statement. Cause. This is an internal error. Effect.
Executor Messages (8000 through 8999) Recovery. None. Contact your service provider. SQL 8822 8822 The statement was not prepared. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8823 8823 An internal error occurred: IO requests are waiting for description message in the IpcMessageStream. Where description is the description message. Cause. I/O requests are waiting for messages shown in message description from the IpcMessage Stream.
Executor Messages (8000 through 8999) SQL 8826 8826 The module could not be added. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8827 8827 The request name could not be sent. Where name is the name of the request. Cause. NonStop SQL/MX was unable to send request name. Effect. The operation fails. Recovery. Use the errors that accompany this one to diagnose and correct the problem.
Executor Messages (8000 through 8999) SQL 8830 8830 There is no current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8831 8831 Either no current context or the module to which the statement belongs is not added to the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8832 8832 Transaction has not been started. Cause.
Executor Messages (8000 through 8999) Cause. NonStop SQL/MX was unable to find the SQL/MX installation directory and received an operating system error number. Effect. The operation fails. Recovery. Locate the SQL/MX installation directory, correct your syntax, and resubmit. SQL 8835 8835 Invalid SQL descriptor information requested. Cause. The descriptor item requested from the descriptor area or being set in the descriptor area is not valid. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8838 8838 Unable to receive reply from MXCMP, possibly caused by internal errors when compiling SQL statements, processing DDL statements, or executing the builtin stored procedures. Cause. NonStop SQL/MX did not receive a reply it expected from MXCMP. Effect. The operation fails. Recovery. Verify that MXCMP is running. SQL 8839 8839 Transaction was aborted. Cause. A transaction failed during processing of an SQL/MX statement.
Executor Messages (8000 through 8999) SQL 8842 8842 The cursor, name, referenced by this statement is not found or is not updatable. Where name is the name of the cursor. Cause. There is an error in the program that this code is embedded in. The build might not have completed successfully. Effect. The operation fails. Recovery. Verify that the build was successful and resubmit. SQL 8843 8843 Trying to retrieve an item, value, that is out of range. Where value is the entry number of the item. Cause.
Executor Messages (8000 through 8999) Recovery. None. Contact your service provider. SQL 8846 8846 An empty SQL statement was passed in. Cause. The SQL source statement passed to the compiler to do the prepare was empty. Effect. The operation fails. Recovery. You must pass in a valid SQL source statement. SQL 8847 8847 An error occurred while trying to retrieve SQL/MP metadata information. Cause. NonStop SQL/MX received an error while trying to retrieve SQL/MP metadata information. Effect.
Executor Messages (8000 through 8999) SQL 8851 8851 A CLI Parameter bound check error occurred. Cause. NonStop SQL/MX received a CLI parameter bound check error. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8852 8852 Holdable cursors are supported for only streaming cursors and embedded update/delete cursors. Cause. You attempted to use a holdable cursor in a situation where it is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) Recovery. Correct the syntax and resubmit. SQL 8856 8856 Specified attribute value is not valid. INPUT_ARRAY_MAXSIZE must be positive. Cause. You specified an invalid attribute value. INPUT_ARRAY_MAXSIZE must be positive. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8858 8858 The value (value) is not a valid SQL identifier. Cause. You attempted to reference an invalid SQL identifier, displayed in the message. Effect.
Executor Messages (8000 through 8999) SQL 8861 8861 Module file name has an obsolete descriptor location table header. Where name is the file name. Cause. The module file name has an obsolete table header. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8862 8862 Module file name has an obsolete descriptor location table entry. Where name is the file name. Cause. The module file name has an obsolete descriptor location table entry. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8865 8865 Module file name has an obsolete procedure location table header. Where name is the file name. Cause. The module file name has an obsolete procedure location table header. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8866 8866 Module file name has an obsolete procedure location table entry. Where name is the file name. Cause. The module file name has an obsolete procedure location table entry. Effect.
Executor Messages (8000 through 8999) SQL 8869 8869 The specified file number in not a QFO, or the file number is not internally associated with a QFO object (CLI internal error). Cause. The file number does not refer to a quasi file object (QFO). Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8870 8870 The current statement is not associated with any QFO. Cause. No quasi file object (QFO) file number is associated with the current statement. Effect.
Executor Messages (8000 through 8999) SQL 8873 8873 The current statement is already associated with a QFO. Cause. An existing quasi file object (QFO) is already associated with the current statement. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8874 8874 An error in an insert, update or delete statement caused that statement to be rolled back but statement rollback failed. Cause. DP2 limits on savepoints is exceeded. Effect. The operation fails. Recovery. None.
Executor Messages (8000 through 8999) Recovery. Either start a transaction or set transaction attribute AUTOBEGIN to ON and rerun the statement. SQL 8878 8878 Transaction has been doomed. The user should explicitly roll back the transaction before proceeding. Cause. The CONTROL QUERY DEFAULT value for DOOM_USERTRANSACTION is ON, and NonStop SQL/MX encountered an unrecoverable error. Effect. The transaction is in a doomed state. Users are unable to continue work on this transaction. Recovery.
Executor Messages (8000 through 8999) SQL 8883 8883 URD violation checking is currently disabled. Cause. The server failed to enable UDR violation checking prior to issuing an SQL/MX CLI function call to check or clear the UDR violation flags. Effect. The operation fails. Recovery. This is an internal error in the SQL/MX UDR server. Contact your service provider. SQL 8884 8884 Prohibited SQL statement attempted. Cause. A stored procedure attempted to execute a transaction-related SQL/MX statement. Effect.
Executor Messages (8000 through 8999) Recovery. Make the CLI call again and use a buffer big enough to hold the proxy syntax. Consider using the len_of_item output parameter from the first CLI call to obtain the actual size of the buffer needed to return the proxy syntax. SQL 8890 8890 The SQL compiler failed to initialize properly. Query results may differ from what is expected, due to different compiler defaults. Cause. The SQL/MX compiler failed to correctly initialize. Effect.
Executor Messages (8000 through 8999) Recovery. Correct the syntax and resubmit. SQL 8894 8894 Argument argument-name of CLI function function-name is reserved for future use and must be set to string when calling the function. Cause. A value that was passed into an SQL/MX CLI function containing a reserved parameter was not the value expected by NonStop SQL/MX. Effect. The CLI function fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) Recovery. None. Contact your service provider. SQL 8898 8898 An internal error occurred in CLI. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8900 8900 Only ISO88591 and UCS2 host variables can be used to retrieve SQL error or warning messages. Cause. Host variable used to retrieve error message is not ISO88591 or UCS2 data type. Effect. The error message cannot be retrieved. Recovery.
Executor Messages (8000 through 8999) SQL 8903 8903 An attempt was made by SQL/MX to kill the MXUDR server for this statement (process name). PROCESS_STOP_ returned value. Where process name is the name of an SQL/MX UDR server process. Cause. NonStop SQL/MX received an interrupt signal, possibly caused by an MXCI user pressing Ctrl-C while the SQL/MX UDR server was executing a stored procedure. Effect.
Executor Messages (8000 through 8999) SQL 8906 8906 An invalid or corrupt MXUDR reply could not be processed, possibly due to memory corruption in MXUDR while executing user-defined routines or an internal error in SQL/MX. Cause. During execution of an SQL/MX statement, the SQL/MX executor received a message from the SQL/MX UDR server that was unreadable in some way. Either the message was corrupted by the SQL/MX UDR server, or an internal error occurred within the SQL/MX executor. Effect.
Executor Messages (8000 through 8999) SQL 8912 8912 The request to allocate a stored procedure result set failed. An unexpected internal error was encountered. Cause. An internal error was detected within the SQL/MX executor during allocation of a stored procedure result set. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8913 8913 The PREPARE operation is not allowed on a stored procedure result set. Cause.
Executor Messages (8000 through 8999) Cause. A CLI application attempted to access a stored procedure result set at position index, but the number of result sets returned from the CALL statement was less than index. Effect. The operation fails. Recovery. None. Contact the GMCSC and report this condition. SQL 8916 8916 The request to allocate a stored procedure result set at position index failed because the position is out of range.
Executor Messages (8000 through 8999) SQL 8934 8934 The MAXVALUE for the sequence generator has been exceeded Cause. The internal sequence generator table has reached either the maximum value for IDENTITY column data type or the MAXVALUE. Effect. The operation fails. Recovery. There is no recovery when IDENTITY column data type maximum is reached. If MAXVALUE is reached, define a new MAXVALUE using ALTER TABLE ALTER COLUMN statement, and resubmit the statement.
Executor Messages (8000 through 8999) HP NonStop SQL/MX Release 3.
11 UPDATE STATISTICS Messages (9200 through 9221) SQL 9200 9200 UPDATE STATISTICS encountered an error from statement name. Cause. UPDATE STATISTICS encountered an error from the SQL/MX statement name. Effect. The operation fails. Recovery. Other error messages will appear with this one, depending on what statement caused the error. Use them to diagnose and correct the problem. SQL 9201 9201 Unable to DROP object name. Cause. UPDATE STATISTICS encountered an error during a DROP of the object name. Effect.
UPDATE STATISTICS Messages (9200 through 9221) Perform UPDATE STATISTICS FOR the table. Then reexecute UPDATE STATISTICS with the column lists in which you are interested. SQL 9203 9203 Column names must be unique when specified in column list: (name). Cause. You specified a nonunique column name in the specified column list. Effect. NonStop SQL/MX is unable to continue processing. Recovery. Correct the syntax and resubmit. SQL 9204 9204 Invalid option option specified. Value must be range. Cause.
UPDATE STATISTICS Messages (9200 through 9221) SQL 9207 9207 The specified SAMPLE option generated an empty sample set. Modify the SAMPLE option and resubmit. Cause. The SAMPLE option you specified generated an empty sample set. Effect. NonStop SQL/MX is unable to continue processing. Recovery. Modify the SAMPLE option and resubmit. SQL 9208 9208 Column definitions could not be accessed. Cause. An UPDATE STATISTICS statement was unable to access column definitions. Effect. The operation fails. Recovery.
UPDATE STATISTICS Messages (9200 through 9221) SQL 9212 9212 Cardinality statistics will be more accurate if you use the SET ROWCOUNT option in the SAMPLE clause. Cause. The SET ROWCOUNT option was not used in the SAMPLE clause. Effect. Processing continues without interruption. Recovery. Provide SET ROWCOUNT option and resubmit for more accurate statistics. SQL 9213 9213 If you intend to update histogram statistics for columns, you must specify a column list in the statement. Cause.
UPDATE STATISTICS Messages (9200 through 9221) SQL 9217 9217 Unable to change the audit attribute for table-name. where, table-name is the name of a SQL/MX table. Cause. The audit attribute of the sample table could not be turned off during the UPDATE STATISTICS operation. The attribute is turned off when the table is empty and contains no indexes. This enables UPDATE STATISTICS to use Side-tree inserts for better performance.
UPDATE STATISTICS Messages (9200 through 9221) Effect. The operation fails. Recovery. Execute either a DELETE statement or a PURGEDATA command on the table and resubmit. SQL 9220 9220 Sample table table-name cannot have index or trigger on it. where, table-name is the name of a SQL/MX table. Cause. The user-specified sample table has either an index or a trigger or both. An index on the sample table might prevent the use of Side-tree inserts for populating the sample table and degrade performance.
12 Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10003 10003 Sort unexpectedly encountered an EOF during a read operation. Cause. This error occurs when a scratch file read operation unexpectedly reaches an EOF. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 10004 10004 Sort failed while generating intermediate runs with sort error value1 and system error value2. Cause.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10006 10006 A previous IO to a scratch file failed. Cause. A previous I/O failed during a nowaited scratch file I/O operation. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 10007 10007 Sort failed while writing to a scratch file with error system error. Cause. An I/O error occurred during a scratch file I/O operation. Effect. The operation fails. Recovery.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages Effect. The operation fails. Recovery. Contact your service provider. SQL 10012 10012 Sort failed during overflow with an invalid block number: number. Cause. The caller specified a block number that is out of range. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 10013 10013 Sort could not find any appropriate disks for overflow. Cause.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10016 10016 Sort failed while calling PROCESSHANDLE_DECOMPOSE_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. Contact your service provider. SQL 10017 10017 Sort failed while calling DEVICE_GETINFOBYLDEV_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages Effect. The operation fails. Recovery. Contact your service provider. SQL 10021 10021 Sort failed while calling FILE_GETINFOLISTBYNAME_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. Contact your service provider. SQL 10022 10022 Sort failed while calling FILE_CREATE with error number. Cause. An error occurred while calling a system level call.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10025 10025 Sort Error: FileClose failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10026 10026 I/O to a scratch file failed while calling AWAITIOX with error number. Cause. An I/O to a scratch file failed with a low level system error. Effect. The operation fails. Recovery. Do not attempt recovery.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages Recovery. Contact your service provider. SQL 10030 10030 Sort Error: GetTempPath error :path name too long. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. Contact your service provider. SQL 10031 10031 Sort Error: GetVolumeInformation failed, check root path. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10035 10035 Sort Error: CreateEvent failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10036 10036 Sort Error: CloseHandle failed. Cause. An error occurred while calling a system level call. Effect.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10040 10040 Sort Error: SetFilePointer failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10041 10041 Sort Error: _chdir failed. Cause. An error occurred while calling a system level call. Effect.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10044 10044 IO to a scratch file did not complete and reported error number. Cause. After several calls to the completion routine, the IO to a scratch file did not complete and returned a low level system error. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 10045 10045 Sort Error: WaitForMultipleObjects failed. Cause.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages SQL 10048 10048 IO to a scratch file failed because the free space threshold was reached on all available disks. Cause. The threshold, specified by the default SCRATCH_FREESPACE_THRESHOLD_PERCENT was reached on all available disks. Effect. The operation fails. Recovery. Reduce the threshold percentage and retry the query or specify a particular disk with adequate free space specifically for scratch use.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Scratch File I/O Messages SQL 10101 10101 operator failed to create a scratch file. FILE_CREATE_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause. The query operator was unable to create a scratch file. Effect. The operation fails. Recovery.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Cause. The query operator was unable to close a scratch file. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 10104 10104 operator scratch file write failed. WRITEX returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause. The query operator was unable to alter a scratch file's attributes. Effect. The operation fails. Recovery. Contact your service provider to diagnose the cause of the SETMODE returned error and correct the problem.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages SQL 10113 10113 operator could not get the last error for a scratch file. FILE_GETINFO_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause. The query operator failed to get the last error for a scratch file. Effect. The operation fails. Recovery. None. This is an internal error.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Recovery. None. This is an internal error. Do not attempt recovery. Contact your service provider. SQL 10116 10116 operator failed to create a disk pool. PROCESSHANDLE_GETMINE_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause. An invocation of PROCESSHANDLE_GETMINE_ failed.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Cause. An invocation of FILENAME_FINDSTART_ failed. Effect. The operation fails. Recovery. None. This is an internal error. Do not attempt recovery. Contact your service provider. SQL 10119 10119 operator encountered an error while searching for a scratch disk. FILENAME_FINDNEXT_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10133 10133 Scratch I/O Error: CloseHandle failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10134 10134 Scratch I/O Error: WriteFile failed. Cause. An error occurred while calling a system level call.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10138 10138 Scratch I/O Error: WaitForSingleObject failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10139 10139 Scratch I/O Error: GetOverlappedResult failed. Cause.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages SQL 10150 10150 operator failed to find an appropriate disk for overflow data. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. Cause. The query operator could not find an appropriate scratch disk. Effect. The operation fails. Recovery. None. Ensure that the disks for scratch file use are appropriate and have enough space.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages Recovery. None. This is an internal error. Do not attempt recovery. Contact your service provider. SQL 10153 10153 operator attempted to read data using a block number that was not mapped to a scratch file. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. Cause. The mapping of data blocks to scratch files is incomplete. Effect. The operation fails. Recovery. None.
Executor Sort and Scratch File I/O Messages (10000 through 10199) Scratch File I/O Messages HP NonStop SQL/MX Release 3.
13 Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11001 11001 There are more than 256 triggers in this statement. Cause. More than 256 triggers were encountered during the statement compilation, which is not supported. Effect. The operation fails. Recovery. Either rewrite the statement so that fewer triggers are generated, or redesign the triggers so that the triggering graph is not as deep.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. The threshold of 16 is hard-coded and cannot be changed. You can either rewrite your statement or redesign your triggers for less trigger recursion by adding conditions to your trigger actions. SQL 11004 11004 Triggers cannot be created on tables with names longer than 122 characters. Cause. You attempted to create a trigger on a subject table whose name length exceeds 122 characters.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11011 11011 Only an UPDATE trigger may specify explicit columns. Cause. You attempted to create an INSERT or DELETE trigger that has an explicit column list. Effect. The operation fails. Recovery. Specify a trigger without the explicit column list. SQL 11012 11012 An INSERT trigger cannot reference OLD values. Cause. You attempted to create an INSERT trigger specifying an OLD transition variable. Effect. The operation fails.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11015 11015 An AFTER trigger does not support the SET operation. Cause. You attempted to use the SET operation as an action for an after trigger. Effect. The operation fails. Recovery. You cannot modify the transition name in an AFTER trigger. Use the UPDATE statement instead as an action for the trigger. SQL 11016 11016 A BEFORE trigger that uses SET must have REFERENCING NEW clause. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11019 11019 Only statement triggers can scan the transition table. Cause. You attempted to create a row trigger that has a scan of the transition table either in its action or in its condition. Effect. The operation fails. Recovery. Depending on your application, you can either re-create the trigger as a statement trigger, or scan from the subject table. SQL 11020 11020 Ambiguous or invalid use of transition name name.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. None. SQL 11023 11023 Subqueries are currently not supported in the WHEN clause of AFTER triggers. Cause. You attempted to create a trigger that has a subquery in the WHEN clause of its action. Effect. The operation fails. Recovery. If the trigger action is an UPDATE or DELETE, you can move the condition to the action predicate. SQL 11024 11024 Specifying the same name, var-name, for both OLD and NEW is not allowed.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) DELETE statement target table. If the triggers cannot be dropped, avoid performing compound statement operations on the subject tables (or columns). SQL 11026 11026 SET ON ROLLBACK clause of Update or Delete statement is not allowed to update columns on which triggers are defined. Cause: The target columns of the SET ON ROLLBACK clause of a SET ON ROLLBACK UPDATE statement are the subject columns of an UPDATE trigger.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11028 11028 Action statement of trigger trigger-name on table subject-table-name has failed. Cause. The execution of a trigger action statement failed. Effect. The operation fails. Recovery. This error message will appear with another error message that states what statement has failed, why it failed, and how to recover.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11033 11033 Object name1 cannot be dropped because it is being used by trigger name2. Where name1 is the object name you are attempting to drop. Where name2 is the trigger name. Cause. You attempted to drop an object name that is being used by a trigger. Effect. The operation fails. Recovery. If possible, drop the trigger first, and then drop the object.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11037 11037 A trigger cannot be defined on a view! Cause. You attempted to create a trigger on a view. Effect. The operation fails. Recovery. Abandon the operation or create a trigger on one of the view-based tables, if this is applicable to your application. SQL 11038 11038 A trigger can be defined on base tables only! Cause. You attempted to create a trigger on an object other than a user base table. Effect.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Specify a different trigger name and resubmit. SQL 11046 11046 Host variables and dynamic parameters are not allowed in the action of a trigger. Cause. You attempted to create a trigger that includes host variables or dynamic parameters in its action. This can happen when you specify CALL statements or compound actions as triggered actions. Effect.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11060 11060 Trigger $0~triggerName for table $1~tableName could not be created due to circular dependency: $2~String0. Cause. You attempted to create a trigger, which resulted in a circular dependency. Effect. The operation fails. Recovery. None. You cannot create a trigger that creates a circular dependency. SQL 11101 11101 MXUDR: Unknown message type: value. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11104 11104 MXUDR: CLI Error: text. Cause. The SQL/MX UDR server encountered an unexpected error during an internal SQL/MX operation. The message text includes the name of the SQL/MX operation and the error code that was returned. Effect. At completion, the stored procedure might display unexpected results or side effects. Recovery. Contact your service provider. SQL 11105 11105 MXUDR: Invalid Language Manager parameter mode.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. Do not attempt recovery. Contact your service provider. SQL 11111 11111 MXUDR: Internal error: value. Cause. The SQL/MX UDR server received an incorrectly formatted message. Effect. The request message is rejected, and the SQL/MX statement fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 11113 11113 MXUDR: Internal error: An unexpected UNLOAD request arrived for UDR handle handle.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Check the installation of the NonStop Server for Java product. Stop and restart the session, and retry the SQL/MX statement. SQL 11203 11203 The Language Manager failed to create its class loader, possibly due to corrupt mxlangman.jar file. Cause. Initialization of the language manager failed during creation of an internal LmClassLoader object.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. Determine if the class file exists in the directory. If the SQL/MX statement is a CALL statement, determine if the class file was moved from the directory that was specified when the procedure was created. If the class file has been moved, either restore it to the original location, or drop the procedure and re-create it with the new location of the class file.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. Correct the EXTERNAL NAME clause and retry the SQL/MX statement. SQL 11209 11209 Specified signature is invalid. Reason: the number of SQL parameters value must match the number of parameters in the specified signature. Where value is number of SQL parameters in the SPJ definition. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11212 11212 Specified signature is invalid. Reason: Java signature size is more than supported. Cause. In a CREATE PROCEDURE statement, the Java signature size exceeded the maximum supported size. The currently supported maximum Java signature size is 8192 characters. Possible causes include an incorrect signature specified in the EXTERNAL NAME clause or a very large number of parameters in the Java method. Effect.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. Either correct the CALL statement so that the null value is not used, or change the Java data type of the parameter to the corresponding Java wrapper type. For example, if the Java data type is integer, change it to java.lang.Integer. Note that to change the Java data type, the procedure must be dropped and re-created.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11219 11219 A Java method completed with an uncaught java.sql.SQLException. The uncaught exception had a of value1 and SQLSTATE of value2. Details: string. SQLCODE Cause. During execution of a CALL statement, an SQL error occurred and a Java exception was thrown. Effect. The operation fails. Recovery. Review the Java method.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11222 11222 The operation failed because the Java Virtual Machine ran out of memory. Cause. The Java Virtual Machine, hosted by an SQL/MX UDR server, did not have enough memory to execute a Java method. This error condition will be accompanied by another condition that shows when the Java Virtual Machine encountered the error. Effect. The operation fails. Recovery. Stop and restart the session and retry the SQL/MX statement.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. The Java signature for a Java main() method must be (java.lang.String[]). Correct the EXTERNAL NAME clause, and retry the SQL/MX statement. SQL 11226 11226 All SQL parameters associated with a Java main method must have a parameter mode of IN. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11229 11229 The Java Virtual Machine produced the following output: jvm-terminal-output. Where jvm-terminal-output is diagnostic information generated by the Java Virtual Machine (JVM) and written to the terminal of an SQL/MX UDR server process. Cause. The JVM in the SQL/MX UDR server could be successfully started and the jvm-terminal-output text was captured. See also the errors that accompany this message for more information.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Where class-name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. Cause. During the execution of a CREATE PROCEDURE statement, the SPJ method could not be found in the specified Java class. The SPJ method must be named class-name.method-name and must have a Java type signature matching the declared SQL parameter types.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11234 11234 The method method-name(signature) was not found in Java class class-name. Where method-name is the Java method name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. Where signature is a Java type signature. Where class-name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Where max-results is the maximum number of result sets that the procedure can return. Where attempted-results is the actual number of result sets that the SPJ method attempted to return. Cause. During the execution of a CALL statement, the number of result sets returned from an SPJ method exceeds the procedure's declared maximum. The declared maximum was specified in the DYNAMIC RESULT SETS clause of the CREATE PROCEDURE statement.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11239 11239 No compatible methods method-name were found in Java class class-name. Where method-name is the Java method name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. class-name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Cause. The SPJRS version returned by the JDBC/MX driver to the language manager is not less than or equal to the version specified in the language manager. The incorrect stored procedure result sets interface throws an error 11241. This is an internal check to ensure that there is no version mismatch with JDBC/MX driver interface. Effect. The operation fails. Recovery. None. Contact your service provider.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Cause. While processing a stored procedure result set, the language manager was unable to process a DECIMAL value at the specified column position because the value contained a character other than a digit. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Release 3.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) HP NonStop SQL/MX Release 3.
14 SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13001 13001 An internal error occurred. The SQL statement could not be translated. Cause. An unanticipated error was detected. Effect. The issued command fails. Recovery. Retry the operation. If the problem persists, contact your service provider. SQL 13002 13002 A syntax error was found near line number. Cause. There is a syntax error near line number. Effect. The preprocessor ignores the line. Recovery. Correct the error and resubmit.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13005 13005 A general programming error occurred in file name at line number. Cause. The preprocessor has received a general programming error in file name near line number. Effect. The preprocessor could not continue. Recovery. Internal error. Contact your service provider. SQL 13006 13006 Switch has bad value, value, for its expression at line number in file name. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13008 13008 The module definition file argument is missing after the -m option. Cause. You specified the -m option without giving the module definition file argument, which is required. Effect. The operation fails. Recovery. Provide the module definition file argument and resubmit. The syntax is: -m mod-def-file where mod-def-file is the name of the module definition file that is to be the input file for the SQL/MX compiler.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13011 13011 option is an unknown command line option. Cause. You specified an option that SQLC does not recognize or support. Effect. The preprocessor ignores the option. Recovery. Correct the option and resubmit. SQL 13012 13012 argument is an invalid or undefined command line argument. Cause. You specified an argument that SQLC does not recognize or support. Effect. The preprocessor ignores the argument. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. Verify that the file can be opened, created, or written to, depending upon the action you are attempting, and resubmit. SQL 13016 13016 Descriptor name name1 conflicts with SQLC default name name2. Cause. In a START statement you specified descriptor name1, which duplicates the SQLC default name2. Effect. The preprocessor ignores the duplicate descriptor name. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13020 13020 Statement name name is multiply defined. Cause. You defined statement name more than once. Effect. The preprocessor ignores the duplicate definition. Recovery. Remove the duplicate definition and resubmit. SQL 13021 13021 name is already defined. Cause. The host variable name, which you attempted to define, has already been defined. Effect. The preprocessor ignores the duplicate definition. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. Declare the cursor and resubmit. SQL 13025 13025 Warning(s) near line number. Cause. NonStop SQL/MX received warnings near line number. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 13026 13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13029 13029 line number detail text Cause. This is a generic error. Effect. The preprocessor could not prepare the statement. Recovery. Use the detail text to determine the problem. SQL 13030 13030 line number detail text Cause. This generic error is displayed when the preprocessor detects a syntax error. Effect. The preprocessor could not prepare the statement. Recovery. Use the detail text to determine the problem.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13033 13033 Host variable name1 is in different scope than when cursor name2 was declared. Cause. You specified a host variable name name1, which is out of scope with cursor name. Effect. The preprocessor ignores the host variable you specified. Recovery. Find where the variable is declared and put it in the correct scope. SQL 13034 13034 Character set name is not yet supported. Cause. You specified character set name, which is not supported.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13037 13037 Function header syntax error was found near line number. Cause. There is a function header syntax error near line number. Effect. The preprocessor ignores the function header syntax. The syntax error is not allowed. Recovery. Correct the syntax and resubmit. SQL 13038 13038 Array size size was expected to be an unsigned integer near line number. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13041 13041 Typedef encountered near line number, and typedefs are not supported. Cause. You specified a typedef near line number, which is not supported. Effect. The preprocessor ignores the typedef. Recovery. Remove the typedef and resubmit. SQL 13042 13042 Unnamed declaration was found near line number. Cause. You specified an unnamed declaration near line number, which is not supported. Effect. The preprocessor ignores the declaration.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13045 13045 An unexpected class declaration was found near line number; it will be ignored. Cause. An unexpected class declaration occurred near line number. Effect. The class declaration is ignored, and the preprocessor continues. Recovery. Move the class declaration to its correct location and resubmit. SQL 13046 13046 "}" was expected to end member declaration - near line number. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. Correct the file problem and resubmit. SQL 13050 13050 Cursor name is not closed. Cause. Cursor name was not closed. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 13051 13051 Cursor name is not opened. Cause. Cursor name was not opened. Effect. The cursor could not be used. Recovery. Open the cursor. SQL 13052 13052 Cursor name is not fetched. Cause. Cursor name was not fetched. Effect. None.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. None. This is a warning message. SQL 13055 13055 Cursor name is not opened or fetched. Cause. Cursor name was not opened or fetched. Effect. None. Recovery. None. This is a warning message. SQL 13056 13056 Cursor name is not used. Cause. Cursor name was not used. Effect. None. Recovery. None. This is a warning message. SQL 13057 13057 End-of-file processing generated unexpected cursor status of status for cursor name. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13060 13060 The listing file name could not be opened. Cause. The preprocessor was unable to open the listing file name. Effect. The preprocessor ignores the listing file. Recovery. Verify that the SQL CLI header file or device exists and is readable, and resubmit. SQL 13061 13061 An invalid NUMERIC precision was specified - near line number. Cause. You specified a data item with invalid NUMERIC precision near line number. Effect.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13064 13064 Identifier name1 is not a member of struct name2 - near line number. Cause. Identifier name1 is not a member of the structure name2 near line number. Effect. The preprocessor ignores the identifier. Recovery. Correct the syntax and resubmit. SQL 13065 13065 End of file was found after syntax-item1 when syntaxitem2 was expected, near line number. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13067 13067 Source file name could not be opened. Cause. The preprocessor was unable to open file name. Effect. The preprocessor ignores the referenced file. Recovery. Verify that the file exists and is readable and resubmit. SQL 13068 13068 A C/C++ syntax error was found - near line number. Cause. NonStop SQL/MX detected a C/C++ syntax error near the line number listed in the message. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13071 13071 Module Tableset Specification string MTSS-string is not a regular identifier, or is longer than 31 characters. Cause. The Module Tableset Specification String (MTSS) you specified is not a regular identifier or is longer than 31 characters. Effect. The embedded SQL source file is not successfully preprocessed. Recovery. Reinvoke the preprocessor, this time specifying a regular identifier for the MTSS.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) (because of adding MGSS, MTSS, or MVSS) or if the catalog or schema is longer than 128 characters, this error message is generated. Effect. The embedded SQL source file is not successfully preprocessed. Recovery. Reinvoke the preprocessor, this time supplying a shorter value for any or all of the MGSS, MTSS, MVSS, or for the one-part module name coded in the embedded SQL source file’s MODULE directive.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13078 13078 Module catalog catalog name is not a valid identifier or is longer than 128 characters. Cause. You invoked an SQL preprocessor or mxCompileUserModule with a modulecatalog=catalog name option where catalog name is not a valid SQL identifier. Effect. The operation fails. Recovery. Verify that catalog name is a valid SQL identifier and retry the command.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13083 13083 Only INVOKED structures or VARCHAR compatible structures or records(without the NULL structure option) can be standalone host variables. Cause. An incompatible structure was specified to hold VARCHAR data in the embedded SQL application. Effect. Preprocessor fails to process the application. Module and cpp files are not generated. Recovery. Specify a structure compatible with VARCHAR data, and preprocess the application.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13086 13086 variable is not declared of type inside the declare section Where is the host variable to hold either SQLCODE or SQLSTATE. Where is the variable data type, either long or char[6]. Cause. The data type of a variable declared in the SQL declare section to hold either SQLCODE or SQLSTATE or both was not correct.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13089 13089 The include file file-name includes itself at linenumber. Where file-name is the file name in the #include statement. Where line-number is the line number of the #include statement. Cause. Include file includes itself in a circular manner in the embedded SQL application. Effect. None. This message is a warning. Preprocessor ignores the #include directive, and processes the subsequent statements. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13504 13504 Timestamp command option is missing. Cause. You did not enter the timestamp command option. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13505 13505 Source input file name cannot be opened. Cause. NonStop SQL/MX could not open the source input file name. Effect. The operation fails. Recovery. Check the file's location, name and security, verify that no other process has it open, and resubmit.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13508 13508 Expecting keyword, found keyword. Cause. You did not enter the keyword or character that NonStop SQL/MX required.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) This error is issued if the preprocessor does not find the keyword SECTION immediately after any of these keywords: FILE LINKAGE ***ERROR[13509] Expecting SECTION after FILE, found EXEC. This error is issued if the preprocessor does not find the picture representation immediately after the keyword PICTURE: ***ERROR[13509] Expecting picture specification after PICTURE, found EXEC. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. Use the errors that accompany this one to diagnose and correct the problem. SQL 13513 13513 The BIT data type is not implemented in SQL/MX. Cause. You specified the BIT data type, which is not supported in NonStop SQL/MX. Effect. The operation fails. Recovery. Specify a data type that NonStop SQL/MX supports. SQL 13514 13514 The CHARACTER SET attribute is not implemented in SQL/MX. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13516 13516 Unexpected end of input file encountered after line number. Cause. NonStop SQL/MX reached the end of the input file while processing EXEC SQL. Effect. The operation fails. Recovery. Correct the input file and resubmit. SQL 13517 13517 Line number is too long to process and has been truncated. Cause. The text in line number is longer than the buffer and has been truncated. Effect.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13521 13521 Line number: DISPLAY host variables must be SIGN LEADING SEPARATE. Cause. You attempted to define a DISPLAY host variable other than as a SIGN LEADING SEPARATE data type at line number. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13522 13522 DECLARE SECTION cannot be nested. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13525 13525 Variable name may not be allocated correctly for a host variable. Cause. Variable name might not be allocated correctly for a host variable. Effect. Check that you declared the variable correctly. An incorrect variable can result in incorrect data from the COBOL compiler. Recovery. Informational message only; no corrective action is needed.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13529 13529 Missing END DECLARE SECTION detected at line number. Cause. The END DECLARE SECTION statement is missing near line number. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13800 13800 Line number: name is not a valid character set name. Cause. You specified an invalid character set name at line number. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Release 3.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) HP NonStop SQL/MX Release 3.
15 MXCI Messages (15000 through 15999) SQL 15001 15001 A syntax error occurred at or before: statement info Cause. A syntax error was detected in statement .info indicates the location of the error in characters from the start of the SQL statement. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15002 15002 Internal parser error: detail text Cause. This is an internal error. Effect. The operation fails. Recovery. None. Report the entire message to your service provider.
MXCI Messages (15000 through 15999) SQL 15005 15005 Unmatched quote in input (unterminated string): text Cause. You specified text input with unbalanced quotation marks. Quoted text, whether literals or delimited identifiers, must not contain carriage returns. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15006 15006 Error number while reading from file. Cause. NonStop SQL/MX received error number while reading from a file. The error number depends on the operating system.
MXCI Messages (15000 through 15999) SQL 15009 15009 The requested help topic is too long. Cause. You entered more than 31 characters in your request for a help topic. Effect. The operation fails. Recovery. See the documentation for the topic. SQL 15010 15010 The help file could not be opened. Cause. NonStop SQL/MX was unable to open the help file. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem.
MXCI Messages (15000 through 15999) SQL 15013 15013 This command is not supported by the SQLCI OLE server. Cause. You specified a command that is not supported by the SQL/MX Conversational Interface (SQLCI) OLE server. Effect. The operation fails. Recovery. None. SQL 15014 15014 Section name not found in file name. Cause. You specified section name, which is not found in file name. Cause. The operation fails. Recovery. Check the spelling of the section name.
MXCI Messages (15000 through 15999) Recovery. Correct the syntax and resubmit. SQL 15018 15018 Break was received. The last statement may be lost. Cause. You pressed Break to stop processing of your most recent MXCI command. Effect. The last statement might be lost. Recovery. Informational message only; no corrective action is needed. SQL 15019 15019 value values were supplied in the USING list while the statement contains value unnamed parameters. Cause.
MXCI Messages (15000 through 15999) SQL 15023 15023 The USING list value value1 exceeds the MXCI limit of value2 characters. Cause. You specified an EXECUTE command with a USING clause, but the value1 item exceeds the number of characters, value2, that MXCI allows. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15024 15024 The USING list quoted literal name must be followed by either a comma or a semicolon. Cause.
MXCI Messages (15000 through 15999) SQL 15028 15028 Break error. Cause. A break that you specified to cancel an SQL/MX statement failed. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. SQL 15029 15029 Break was received. Please run RECOVER to recover any incomplete operations. Cause. A break was received while running a utility operation such as PURGEDATA, DUP, or MODIFY. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15032 1503 An error occurred while adding, altering or deleting this define. Cause. An error occurred while adding, altering, or deleting a define. Effect. The operation fails. Recovery. Use the file system errors that accompany this one to diagnose and correct the problem. SQL 15033 15033 Break was received. Cause. Break was received. Effect. The operation fails. Recovery. Informational message only; no corrective action is needed.
MXCI Messages (15000 through 15999) Recovery. Correct the file code or function argument. SQL 15038 15038 A SQL/MX transaction is already in progress. The mode cannot be changed at this time. Cause. You attempted to change the mode while a transaction was in progress. Effect. The operation fails. Recovery. Commit or abort the transaction and retry the MODE command. SQL 15039 15039 DISPLAY_EXPLAIN is not supported any more, use EXPLAIN instead. Cause. You attempted to run the DISPLAY_EXPLAIN command.
MXCI Messages (15000 through 15999) SQL 15203 15203 Maximum of int1 error messages exceeded, dropping the rest. Where int1 gives the maximum number of errors permitted for one command. Cause. Excessive error messages are issued, and at least one is dropped. Effect. The command fails with errors previously reported. This message is always the last one reported for a given error. Recovery. Correct the problem defined by the first error, which is normally the most meaningful.
MXCI Messages (15000 through 15999) SQL 15212 15212 SUBSYSTEM: Wrong length input parameter, library call function-name failed. Where function-name is the name of the library function called. Cause. A field in the command is too long. Effect. The operation fails. Recovery. Look for one or more input strings that exceed the character limit. Then enter the command with the correct length field(s). SQL 15214 15214 SUBSYSTEM: User not authorized for this action, library call function-name failed.
MXCI Messages (15000 through 15999) Cause. You issued an ADD EVAR command and the EVAR name supplied already exists. Effect. The command and subsequent subsystem call fails. Recovery. Specify a different EVAR name. View a list of known EVARs using the INFO EVAR command. SQL 15217 15217 Guardian file system error encountered, library call function-name failed. +++SUGG: Use "gtacl -c 'error errno" to decode. Where function-name is the name of the library function called.
MXCI Messages (15000 through 15999) SQL 15220 15220 SUBSYSTEM: Configuration server on SERVICE is not operational, library call function-name failed. +++SUGG: Configuration server should soon be restarted by SERVICE, if not stop (kill) SERVICE and restart from Guardian TACL prompt. Where function-name is the name of the library function called. Cause. The configuration server is not operational. Effect. The command and subsequent subsystem call fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15224 15224 SUBSYSTEM: SERVICE did not respond within the 5 second timeout, library call function-name failed. Where function-name is the name of the subsystem routine called. Cause. Call to a subsystem timed out. Effect. The requested action fails. Recovery. The CPU running the SERVICE or the SERVICE is busy. Retry the request. If it fails again, wait until the target CPU is less busy and retry the action.
MXCI Messages (15000 through 15999) SQL 15228 15228 Command contained a invalid-char before the end, command had: string1. ++++SUGG: Surround the string containing this character with quotes. Where invalid-char is the invalid character in the command. Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated. Cause. The MXCI lower level did not break the command apart on a semicolon or quotes did not enclose the character. Effect. The operation fails.
MXCI Messages (15000 through 15999) SQL 15231 15231 Command had a 'invalid-char' character where an attribute was expected, command had: string1. Where invalid-char is either a semicolon or a comma. Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated. Cause. You entered a comma followed by either another comma or a semicolon. Effect. The operation fails. Recovery. Enter the command with the correct comma or semicolon.
MXCI Messages (15000 through 15999) Cause. A token separator is incorrect, likely in the object name Effect. The operation fails. Recovery. Enter the command using the correct separator value. SQL 15235 15235 Attribute value not terminated with a comma or semicolon, command had: string0 string1 string2. +++SUGG: Command could be missing a comma or the whole value may need quotes. Only one token permitted for an attribute value. Where string0 string1 string2 is the remaining string. Cause.
MXCI Messages (15000 through 15999) SQL 15240 15240 No attributes supported by this command, command had: string1 .... Where string1 displays the start of the error. Cause. The command does not support attributes. Effect. The operation fails. Recovery. Enter the command without the attribute. SQL 15241 15241 Command is missing the required attribute "attributename". Where attribute-name is the name of the missing attribute. Cause. The required attribute is missing from the command. Effect.
MXCI Messages (15000 through 15999) SQL 15245 15245 This command attribute never has a value, command had: string0 string1. +++SUGG: Check syntax for missing comma after keyword. Where string0 and string1 are the name and value of the attributes. Cause. A value is associated with an attribute. Effect. The operation fails. Recovery. Enter the command without the attribute value. SQL 15246 15246 This command attribute has an invalid value, command had: string0 string1.
MXCI Messages (15000 through 15999) Recovery. Enter the command with the correct attribute value. SQL 15249 15249 Command has a quoted string not followed by a comma, semicolon, or the concat operator ||, command had: string1. Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated. Cause. A comma, semicolon, or concatenation operator does not follow the string inclosed in quotation marks. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15257 15257 A component name may not contain wild cards * or ? within the name. The wild card * alone is often permitted. Use double quotes to protect these characters in DS and EVAR names when they are normal characters, command had: string0. Where string0 is the component as entered in the command. Cause. The component name is not quoted. Effect. The operation fails. Recovery. Enter the command with the component name enclosed in quotation marks.
MXCI Messages (15000 through 15999) SQL 15260 15260 name name component must be * or start with $, command had string1. +++SUGG: Last component of name may be missing. Where string1 is the component of the object name as entered in the command. Cause. The service name is incorrect. The service name can be either an asterisk (*) or a ‘$’ followed by a service name. Effect. The operation fails. Recovery. Enter the command with a valid service name.
MXCI Messages (15000 through 15999) SQL 15263 15263 Single quote at start of component name not permitted, command had: ‘string1’. +++SUGG: Identifiers use double quotes when needed to prevent upcasing. Some name components are not identifiers and should not be quoted at all. Where string1 is the component name enclosed in single quotes. Cause. The component name is enclosed in single quotes. Effect. The operation fails. Recovery. Enter the command without the single quotes around component name.
MXCI Messages (15000 through 15999) SQL 15266 15266 Object name component has invalid character char, command has name. Where char is the invalid character. Where name is the component of the object name as entered in the input. Cause. The component name is incorrect; the name contained a nonalphanumeric character. Only system, service and server component names are validated this way and they must not contain special characters. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15269 15269 Attribute value is negative or 0, must be positive, command had: string1. Where string1 is the attribute name and value. Cause. The attribute value is negative or zero. Effect. The operation fails. Recovery. Enter the command with the attribute value as a positive, nonzero number. SQL 15271 15271 Attribute value too small, limit minimum, command had: string1. Where minimum is the minimum value allowed for the attribute value.
MXCI Messages (15000 through 15999) SQL 15273 15273 Attribute value too small, limit -9,223,372,036,854,775,808, command had: string1. Where string1 is the attribute name and value. Cause. The attribute value entered is less than the minimum allowed value. Effect. The operation fails. Recovery. Enter the command with the attribute value equal to or larger than the minimum allowed value. SQL 15274 15274 Attribute value too large, limit 9,223,372,036,854,775,807, command had: string1.
MXCI Messages (15000 through 15999) SQL 15276 15276 SERVICE name component * not permitted when accessing a SERVER. Cause. The service name is an asterisk (*), which is invalid when trying to access a server. Effect. The operation fails. Recovery. Retry the command specifying a valid service name. To list valid service names, use the INFO SERVICE command. SQL 15277 15277 Extra token invalid-char was found, command had: string1. Where invalid-char displays the invalid character.
MXCI Messages (15000 through 15999) SQL 15279 15279 Trailing spaces are not allowed in SQL identifiers, command had: ‘string1’. Where string1 displays the start of the error. Cause. A component of the object name ends with a blank or tab character. Effect. The operation fails. Recovery. Enter the command without a space at the end of the component name, or use underscores. Names ending with a space are invalid.
MXCI Messages (15000 through 15999) Recovery. Select a valid entry from the list as the first token of the input. SQL 15285 15285 USAGE: "ADD" command supports object types: DS, EVAR, USER. Cause. The input line contains either no second parameter or an invalid command and object pair. Effect. The operation fails. A preceding message states the problem, and this message lists valid ADD command objects when mode macl is set. Recovery.
MXCI Messages (15000 through 15999) SQL 15288 15288 USAGE: "INFO" command supports object types: DS, EVAR, SERVER, SERVICE, USER. Cause. The input line contains either no second parameter or an invalid command and object pair. Effect. The operation fails. A preceding message states the problem, and this message lists valid INFO command objects when mode macl is set. Recovery. Select a valid object type from the list as the object type for this command.
MXCI Messages (15000 through 15999) SQL 15294 15294 USAGE: [[[system.]service.]ds] are the name components for a DS object. Cause. The object name did not have the correct format. Effect. The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name. Recovery. Enter the command using the correct syntax. SQL 15295 15295 USAGE: [[[[system.]service.]ds.]evar] are the name components for an EVAR object. Cause.
MXCI Messages (15000 through 15999) SQL 15298 15298 USAGE: [[system.]groupname.membername] are the name components for a USER object. Cause. The object name or some component of it did not have the correct format. Effect. The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name. Recovery. Enter the command using the correct name syntax. SQL 15299 15299 USAGE: command obj-type [obj-name][, attribute]...; Cause.
MXCI Messages (15000 through 15999) SQL 15307 15307 SUBSYSTEM: DS already exists, library call function-name failed. Where function-name is the client library function name. Cause. The data source currently exists. Effect. The operation fails. Recovery. Enter the command specifying a different data source name. SQL 15308 15308 SUBSYSTEM: Parameter error on call to MXCS, library call string1 failed. Where string1 is the client library call. Cause. Lower- level client library function call fails. Effect.
MXCI Messages (15000 through 15999) SQL 15311 15311 SUBSYSTEM: Association server not available, library call function-name failed. Where function-name is the client library function name. Cause. The association server is not available. Effect. The operation fails. Recovery. Make sure an association server is available, and then enter the command. SQL 15312 15312 SUBSYSTEM: Cannot change DS state, (failed to start/stop a server), library call function-name failed.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Use the INFO SERVER command to list the servers on the system. Then enter the command with a valid server. SQL 15315 15315 SUBSYSTEM: DS is stopped, trace cannot be changed, library call function-name failed. Where function-name is the client library function name. Cause. The data source is in a stopped state. Effect. The operation fails. Recovery. Start the data source and then change the trace status.
MXCI Messages (15000 through 15999) SQL 15318 15318 SUBSYSTEM: SERVER is in use by another client, library call function-name failed. Where function-name is the client library function name. Cause. The server is accessed by another client process. Effect. The operation fails. Recovery. Wait until the other client process stops accessing the server, then enter the command. SQL 15319 15319 SUBSYSTEM: Trace already enabled, library call function-name failed.
MXCI Messages (15000 through 15999) SQL 15322 15322 SUBSYSTEM: Busy, try again, library call function-name failed. Where function-name is the client library function name. Cause. MXCS service is too busy so it cannot respond to the current request. Effect. The operation fails. Recovery. Try the command at a later time. SQL 15323 15323 SUBSYSTEM: Cannot create SERVER, library call functionname failed. Where function-name is the client library function name. Cause. Cause.
MXCI Messages (15000 through 15999) SQL 15325 15325 Could not get the list of SERVICES on the system. Cause. The lower-level could not return a list of services on the system to the MACL layer. Effect. The operation fails. Recovery. See information about this error in the EMS collector for MXCS service event messages, which is specified on the mxoas start command with $0 as the default. SQL 15326 15326 Could not get the next SERVICE name from the list. Cause.
MXCI Messages (15000 through 15999) Recovery. Use the INFO SERVICE command to verify that the specific service is still operational. See lower-level error messages issued with this message. Also, see information about this error in the EMS collector for MXCS service event messages, which is specified on the mxoas start command with $0 as the default. SQL 15329 15329 Could not get the status for all DSs on the SERVICE. Cause. The lower level cannot return status for all the data sources on the service.
MXCI Messages (15000 through 15999) SQL 15332 15332 USAGE: FILE option is supported only with TCFG. TMACL displays to the screen. Cause. You entered the command string version service, tmacl, file xxx: MACL trace does not support the file option. Instead, the command output goes to the screen, and you cannot specify these two attributes together. Effect. The operation fails. Recovery. Enter the command without the file option. For example, enter the command string version service, tcfg:.
MXCI Messages (15000 through 15999) SQL 15352 15352 Could not get list of SERVERs on the SERVICE servicename. +++SUGG: Use INFO SERVICE to see if it still exists. Where service-name is the name of the service. Cause. The lower level fails to return a list of servers for a service. The system might be busy. Effect. The operation fails. Recovery. Verify that the service exists via an INFO SERVICE * command and then retry the failed command. See the lower-level error messages issued with this message.
MXCI Messages (15000 through 15999) SQL 15355 15355 Could not get name of next DS on the SERVICE servicename. Where service-name is the name of the service. Cause. The lower-level fails to return the next data source name on the service. The system might be busy. Effect. The operation fails. Recovery. Use the INFO SERVICE * command to verify that the service exists, then retry the failed command. See the lower-level error messages issued with this message.
MXCI Messages (15000 through 15999) SQL 15358 15358 SERVER server-name is not the type that can be stopped this way. +++SUGG: Perhaps name is the association or configuration server, use STOP SERVICE on them. Where server-name is the name of the server. Cause. The lower level could not stop the server. Effect. The operation fails. Recovery. See the lower-level error messages. Check for an attempt to stop the association or configuration servers.
MXCI Messages (15000 through 15999) SQL 15363 15363 SERVICE service-name has no SERVERs. INFO SERVICE to see if it is stopped. +++SUGG: Use Where service-name is the name of the service. Cause. The lower level detects no servers associated with this service. Service might be in a stopped state. Effect. The operation fails. Recovery. Run the INFO SERVICE command to verify the status of the service. If service is stopped, issue the START SERVICE command.
MXCI Messages (15000 through 15999) SQL 15367 15367 Could not get state info for DS “string0” from the service and not trying for any other DSs. +++SUGG: The service may never have been started and so may not know about any DS. Where string0 is the DS name. Cause. The lower levels returned a status indicating no ability to provide state information for this DS (or any other). The most likely cause is that the service has never been started.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. SQL 15371 15371 Could not set process priority on DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. SQL 15372 15372 DS string1 creation failed. Where string1 is the data source name. Cause.
MXCI Messages (15000 through 15999) Recovery. Enter the command specifying either a data source or service name. SQL 15375 15375 Could not get statistics from DS string1 Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. SQL 15376 15376 Could not get CPU list from DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect.
MXCI Messages (15000 through 15999) SQL 15379 15379 DS creation failed, new DS name string1 already exists. Where string1 is the data source name. Cause. The specified data source already exists. Effect. The operation fails. Recovery. Enter the command specifying a different data source name. SQL 15380 15380 DS not found, string1. Where string1 is the data source name. Cause. The data source is not found on the system. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15383 15383 Unable to obtain all or part of the ENV variables on string1. Where string1 is the data source name. Cause. A failure in the client library. Effect. The command is partially processed. Recovery. See the lower-level error messages that precede this message. SQL 15384 15384 ALLSTAT keyword must preceed all other statistical keywords on the command line. Cause. ALLSTAT keyword is not in front of all other statistical keywords. Effect. The operation fails.
MXCI Messages (15000 through 15999) SQL 15387 15387 Could not disable trace for DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. SQL 15388 15388 Could not set the attributes of DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15390 15390 Initial server count int1 exceeds maximum server count int2 (or 200, whichever is smaller) for DS string1. Where int1 is the initial server count specified in the command. Where int2 is the maximum server count for the data source specified in the command. Where string1 is the data source name. Cause. Initial server count is too large. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15393 15393 The ACTIVE attribute requires SERVICE name be specific and started, also DS name must be a wildcard. Cause. The ACTIVE attribute is specified in the command, but the service name is not known. Effect. The operation fails. Recovery. Enter the command specifying the service name. SQL 15394 15394 Must specify at least one attribute on the ALTER DS command line. Cause. No attributes are specified in the alter command. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15397 15397 DS name can not be *. the command. +++SUGG: Specify a DS name on Cause. The data source in the command is an asterisk (*). Effect. The operation fails. Recovery. Enter the command again, specifying the data source name. An INFO DS command will list known data source names. SQL 15398 15398 Could not get attribute info for DS “string0” from database. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect.
MXCI Messages (15000 through 15999) error occurs during ALTER DS, run INFO SERVICE to list known services. Enter the ALTER command, specifying the trace attribute. Specify a valid service name or wild card to set trace on one or all operational services. SQL 15401 15401 EVAR type evar-name can not be used with the EVAR command evar-cmd. Where evar-name is the name of the EVAR type and evar-cmd is the EVAR command. Cause. The EVAR type ALL is not valid for EVAR object in the command. Effect.
MXCI Messages (15000 through 15999) SQL 15405 15405 DS name can not be * on an EVAR command. +++SUGG: Use a specific DS name on the command. Cause. EVAR belongs to a specific DS. The DS name must be specified. A DS name of * is not permitted on any EVAR command. Effect. The operation fails. Recovery. Use a specific DS name on the command. SQL 15407 15407 evar-name does not exist in EVAR type evar-type. Where evar-name is name of the EVAR specified in the command.
MXCI Messages (15000 through 15999) SQL 15410 15410 Copying EVARs from source-ds data source to target-ds data source failed. Where source-ds is the old data source where the EVARs will be copied from. Where source-ds is the existing DS that defines the EVARs to be copied. Where target-ds is the new data source where the EVARs will be copied to. Where target-ds is the new data source being created. Cause. A problem occurred in support routines during reading or writing to existing EVARs.
MXCI Messages (15000 through 15999) SQL 15413 15413 Duplicate object-type name found, add failed. Where object-type is the object type specified on the command line. Cause. More than one object-type for the specified name is found. Effect. The operation fails. Recovery. Delete the duplicates. SQL 15414 15414 The first object-type with this name was altered, but count more were found. +++SUGG: Delete all except last, it is the only one used.
MXCI Messages (15000 through 15999) SQL 15425 15425 Failed in scan of USERs on the SYSTEM system-name before end, number-users were scanned before failure. Where system-name is the name of the system. Where number-users is the number of users that were scanned in before failure. Cause. A failure occurs in the lower-client library function. Effect. The operation fails. Recovery. See the lower-level error messages for details.
MXCI Messages (15000 through 15999) Recovery. Run the info user command to see a list of users. SQL 15431 15431 The permissions for SUPER.SUPER may not be changed or deleted. Cause. The command was trying to change the SUPER.SUPER user. Effect. The operation fails. Recovery. None. SQL 15432 15432 Failed to set up an output area for outputing USERs. New changes dropped. Cause. A failure in the lower client library function. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15435 15435 Too many USERs for user-type list buffer size. New changes dropped. Max characters is char-max, failed user is number user-number of this type, user-name. Where user-type is either operator or user. Where char-max is the maximum number of characters in the user buffer. Where user-number is count of what user that exceeded buffer size. Where user-name is the user name. Cause. A set buffer limit holds all user names.
MXCI Messages (15000 through 15999) SQL 15438 15438 This command does not permit * as the comp-name component when the membername is present. Where comp-name is the name of the component. Cause. An invalid wild card is used on the command. Effect. The operation fails. Recovery. Reenter the command again, using a valid component name. SQL 15451 15451 DS string1 was not found, looked at int1. Where string1 is the command and object type.
MXCI Messages (15000 through 15999) Recovery. See the lower-level warning message that follows this message for a list of known object types. SQL 15454 15454 Unknown command in MXCS mode, string1. Where string1 is the command. Cause. The command is invalid. Effect. The operation fails. Recovery. See the lower-level warning message that follows this message for a list of known commands. SQL 15455 15455 Invalid command and object type combination, string1. Where string1 is the command and object type.
MXCI Messages (15000 through 15999) SQL 15458 15458 Could not open connection to system string1. +++SUGG: Check spelling, check connectivity, check that SQL/MX is operational there. Where string1 is the system name. Cause. The system name is incorrect. Effect. The operation fails. Recovery. Enter the command, specifying a valid system name. SQL 15459 15459 Could not open connection to DB of the local system, string1. +++SUGG: Verify SQL/MX is operational. Where string1 is the system name. Cause.
MXCI Messages (15000 through 15999) SQL 15503 15503 String literal must be enclosed within identical quotes. Cause. You specified a string literal that was not enclosed within identical quotation marks, as required. Effect. The operation fails. Recovery. Correct the command, verifying that quotation marks are balanced and reissue the command. Use two quotation marks for each quotation mark that you want to appear in the string. SQL 15504 15504 Ampersand must be followed by another quoted string. Cause.
MXCI Messages (15000 through 15999) SQL 15507 15507 The value must be between 1 and 255. Cause. The value that you specified for RIGHT_MARGIN was not in the range 1 through 255. Effect. The operation fails. Recovery. Specify the correct command and resubmit. SQL 15508 15508 The value must be between 0 and 32767. Cause. The value that you specified in the SET LIST_COUNT command was out of range. The value must be from 0 through 32767. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15511 15511 The value must be between 0 and 255. Cause. The SET LAYOUT value that you specified for the SPACE option was not in the valid range. Effect. The operation fails. Recovery. Specify the correct value and resubmit. SQL 15512 15512 The value must be between 0 to 255 characters for the SET LAYOUT value for SUBTOTAL option. Cause. The SET LAYOUT value that you specified for the SUBTOTAL option was not in the valid range. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15515 15515 This command is not allowed because a SELECT is in progress. Cause. When a SELECT operation is in progress, you can enter only certain MXCI commands, such as report writer commands and: ENV EXIT| RESET LAYOUT|REPORT|SESSION|STYLE FC SET LAYOUT|SESSION|STYLE HELP SHOW DEFINE|DEFMODE|LAYOUT|REPORT INFO DEFINE|PARAM|SESSION|STYLE LOG Effect. The operation fails. Recovery. If you specified the command by mistake, enter the correct command.
MXCI Messages (15000 through 15999) SQL 15518 15518 The value must be between 1 and 32767for LINE_SPACING option. Cause. The value that you specified for the LINE_SPACING option was not in the valid range. Effect. The operation fails. Recovery. Specify the correct LINE_SPACING value and resubmit. SQL 15519 15519 The current PAGE_LENGTH length1 value is insufficient for the report. The PAGE_LENGTH should be length2. Cause.
MXCI Messages (15000 through 15999) Recovery. Enter a BREAK command or delete the SUBTOTAL command by using RESET. SQL 15522 15522 Because of the new report definition command(s), the report is being regenerated from the start. 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.
MXCI Messages (15000 through 15999) Recovery. Correct the value of PAGE, NEED, or SKIP and resubmit. SQL 15526 15526 AS DATE or AS TIME format specified on an incompatible item type or on a value that is out of range. Cause. You specified the AS DATE or AS TIME clause for an item whose type is not compatible with the format. These formats are valid only with numeric items with scale 0. The item value must be within the range 48731278400000000 through 274927291200000000.
MXCI Messages (15000 through 15999) Recovery. Remove all instances of this alias or detail-alias name from the current report commands and resubmit. SQL 15530 15530 column-name not found in SELECT list. Cause. The column name that you specified in the message could not be found in the list of columns specified in the SELECT statement. Effect. The operation fails. Recovery. Verify that the column is specified in the SELECT statement and that the name is spelled correctly, and resubmit.
MXCI Messages (15000 through 15999) Effect. No report is generated. Recovery. Enter a BREAK command for the specified column, or reissue the command that treats the column as a BREAK column. SQL 15535 15535 The operand of JULTIME or DATEFORMAT function must have a DATETIME data type. Cause. You used a JULIANTIMESTAMP or DATEFORMAT function with a column name having a data type other than DATETIME. Effect. The operation fails. Recovery. Reissue the command after connecting it.
MXCI Messages (15000 through 15999) SQL 15538 15538 An operand of the LIKE operator does not have a CHARACTER type. Cause. You specified a column, pattern, or escape character in a LIKE predicate that does not have a character data type. The LIKE predicate can be used only on character data with type CHARACTER or VARCHAR. Effect. The operation fails. Recovery. Check the data types specified in the LIKE predicate and remove any numeric operands. SQL 15539 15539 A literal string is required here. Cause.
MXCI Messages (15000 through 15999) SQL 15542 15542 Unknown output device specified. Cause. The report writer does not support the current output device. Effect. The report writer output could show unexpected results. Recovery. Set a valid output device by using the LOG command and resubmit. SQL 15543 15543 Invalid hexadecimal characters were found in input. Cause. A character other than a-z, A-Z, or 0-9 was found in the hexadecimal input. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15546 15546 Headings cannot span more than 15 lines. Cause. You specified a heading clause that resulted in an item heading spanning more than 15 lines. Effect. Although the command is accepted at parser level, it will fail at build time. Recovery. Specify the heading clause with fewer “newline” characters. SQL 15547 15547 name is a detail-alias-name. It not allowed in this command. Cause. The column ID that you specified was a detail-alias name.
MXCI Messages (15000 through 15999) SQL 15550 15550 Format specification is not valid. Cause. You specified an invalid format. Effect. The operation fails. Recovery. Correct the format and resubmit. SQL 15551 15551 Numeric expression which was evaluated caused division by zero. Cause. A numeric expression that you specified caused division by zero, which is not supported. Effect. The operation fails. Recovery. Correct the command and resubmit.
MXCI Messages (15000 through 15999) SQL 15554 15554 The operand for name must have a type datatype. Cause. The operand for the function you specified does not have the correct data type. Effect. The operation fails. Recovery. Change the operand so that it has the specified data type. SQL 15555 15555 Numeric literal has too many digits. A maximum of 17 digits can be specified with an integral number. Cause.
MXCI Messages (15000 through 15999) SQL 15576 15576 There is no current name 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. This is an informational message; no recovery is necessary. SQL 15577 15577 There are no more selected rows. Cause. The command tried to list rows when there were no more rows to select. Effect. None. Recovery.
MXCI Messages (15000 through 15999) Effect. None. Recovery. Please specify a valid mode. SQL 15806 1558 The conversion failed. Cause. You attempted to perform a conversion that is invalid. Effect. The operation fails. Recovery. None. SQL 15807 15807 NULL cannot be assigned to a NOT NULL column. Cause. You assigned NULL to a column for which NOT NULL was specified. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15808 15808 An invalid column numberwas specified. Cause.
MXCI Messages (15000 through 15999) SQL 15810 15810 The buffer allocated must be on an even boundary. Cause. A computation occurred that resulted in an item overflowing its field. Effect. The operation fails. Recovery. The field size of the receiving field must be validated to be on an even boundary. SQL 15811 15811 Unable to get a valid Report Writer Constructor. Cause. MXCI was unable to connect to the Report Writer component. Effect. Cannot switch to mode report in this session. Recovery.
MXCI Messages (15000 through 15999) Recovery. Retry the operation. SQL 15816 15816 An internal error occurred - unable to get a valid MXCS Destructor. Cause. MXCI was unable to disconnect from the MXCS server. Effect. The operation fails. Recovery. Retry the operation. SQL 15817 15817 The current mode is MXCS. Cause. You tried to change the mode to MXCS while already in MXCS. Effect. None. Recovery. None. This is an informational message only.
MXCI Messages (15000 through 15999) SQL 15992 15992 Usage information not found or could not be displayed. Cause. The usage information for this module could not be found or could not be displayed. Effect. No usage information is displayed. Recovery. None. SQL 15999 15999 An MXCI internal error occurred. Cause. MXCI has received an internal error. Effect. The operation fails. Recovery. Report the entire message to your service provider. HP NonStop SQL/MX Release 3.
16 Messages Generated by the Message System (16000 through 16999) SQL 16000 16000 Error message file not found. Cause. The message file might not have been installed correctly. Effect. NonStop SQL/MX is unable to return or display a message. Recovery. Reinstall NonStop SQL/MX. See the SQL/MX Installation and Management Guide. If that does not resolve the problem, report the entire message to your service provider. SQL 16001 16001 The error number err-num is not used in SQL/MX. Cause. Internal error.
Messages Generated by the Message System (16000 through 16999) HP NonStop SQL/MX Release 3.
17 Internal Stored Procedures Messages (19000 through 19999) SQL 19000 19000 An internal error occurred in internal stored procedure processing. Cause. Internal error. Effect. NonStop SQL/MX is unable to process the request. Recovery. None. Report the entire message to your service provider. SQL 19001 19001 An error was found in field description of internal stored procedure. Cause. Internal error. Effect. NonStop SQL/MX is unable to process the request. Recovery. None.
Internal Stored Procedures Messages (19000 through 19999) SQL 19016 19016: Stored procedure name expects a type1 type value for parameter number. The data type of the actual parameter value is type2. where, name is the name of the built-in function. type1 is the data type of a formal parameter to the built-in function. number is the number of the formal parameter, starting with 1. type2 is the data type of the actual parameter to the built-in function. Cause.
Internal Stored Procedures Messages (19000 through 19999) SQL 19019 19019 Input type value is not defined for stored procedure built-in function. where, value is a user specified input value to a versioning built-in function. built-in function is the name of one of the versioning built-in functions (VERSION_INFO, RELATEDNESS). Cause. An attempt is made to access the named built-in function with an input-type that is not supported by that function. Effect. The request fails. Recovery. None.
Internal Stored Procedures Messages (19000 through 19999) Cause. An invalid feature version value is specified. Effect. The operation fails. Recovery. Specify a valid feature version value as input to the FEATURE_VERSION_INFO built-in function. SQL 19030 19030 Version of these modules is incompatible for this command. Cause. The specified module file is compiled with old compiler and does not have the source name section and object name section. Effect. The operation fails. Recovery.
18 Utility Messages (20000 through 23099) SQL 20000 20000 open. File system error error number occurred during file Where error number is the Guardian file system error. Cause. SQL was not able to open the requested file and received error error number. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20001 20001 File system error error number occurred during file read.
Utility Messages (20000 through 23099) SQL 20003 20003 File system error error number occurred during file close. Where error number is the Guardian file system error. Cause. SQL was not able to close the requested file and received error error number. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20004 20004 File system error error number occurred while trying to set EOF to zero for file.
Utility Messages (20000 through 23099) SQL 20006 20006 File system error error number occurred while enabling large transfers for file. Where error number is the Guardian file system error. Cause. SQL could not enable a large transfer to the requested file and received error number. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20007 20007 Transaction Management subsystem could not commit the current transaction.
Utility Messages (20000 through 23099) Recovery. None. This is an internal error. Contact your service provider. SQL 20010 20010 Previous read in file failed. Cause. The utilities subsystem that performs fast data transfer received an error when attempting to read data from the file. This error possibly results from retrying a previously failed read operation. Effect. The operation fails. Recovery. Use the errors that accompany this one to diagnose and correct the problem with the previous file read.
Utility Messages (20000 through 23099) Effect. SQL is unable to complete the command. Recovery. Determine what caused the previous command to fail and correct the problem. SQL 20013 20013 An internal error occurred - did not enable large transfer for file. Cause. The utility subsystem that performs fast data transfer performed steps out of sequence. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20017 20017 File system error error number occurred while getting partition length for file. Where error number is the Guardian file system error. Cause. SQL was not able to obtain the partition length (EOF) for the requested file and received error error number. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Recovery. None. Contact your service provider. SQL 20020 20020 An internal error occurred. The number of columns (num1) defined for the referenced table table1 does not match the number of columns (num2) defined on the referencing table table2 for constraint const. Where num1 is the number of columns associated with the referenced table constraint. Where table1 is the name of the referenced table.
Utility Messages (20000 through 23099) Recovery. Correct the field length in the format file and resubmit. SQL 20023 20023 Object does not exist. Cause. The utility subsystem that reads and maintains metadata could not find the requested SQL/MX object. A possible cause is that the catalog, schema, or object name is misspelled in the request. SQL/MX objects can be catalogs, schemas, tables, trigger temporary tables, stored procedures, indexes, or MP aliases. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20026 20026 An internal error occurred - invalid privilege type. Cause. The utility subsystem that reads and maintains metadata encountered an unexpected privilege type. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20027 20027 The specified begin key is greater than the end key for an ADD, MOVE, or DROP data request. Cause.
Utility Messages (20000 through 23099) SQL 20030 20030 The specified start key cannot be HIGH_VALUES. Cause. You specified a start key as HIGH_VALUES, which is not supported. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20031 20031 The specified end key cannot be LOW_VALUES. Cause. You specified an end key as LOW_VALUES, which is not supported. Effect. The operation fails. Recovery. None. This is an internal error.
Utility Messages (20000 through 23099) Recovery. Verify the location of the catalog and resubmit. SQL 20035 20035 Schema does not exist. Cause. You specified a modify request without a valid schema name. Effect. The operation fails. Recovery. Verify the location of the schema and resubmit. SQL 20036 20036 Table table-name does not exist. Where table-name is the ANSI SQL name of the specified table. Cause. The MODIFY utility could not find the specified table. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20039 20039 For the MOVE, DROP, and REUSE requests, the key range must specify an exact partition range. Cause. You used the add-move-boundary-range syntax instead of partitionidentification to identify a partition to be moved, dropped, or reused, but you did not specify the exact partition range. Effect. The operation fails. Recovery. Reissue the request with the correct partition range. Consider using the partition-identification syntax instead.
Utility Messages (20000 through 23099) SQL 20043 20043 The specified attribute cannot be modified for the existing object. Cause. You attempted to modify a nonmodifiable attribute of a table. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20044 20044 An internal error occurred - invalid file attribute. Cause. The utility subsystem that reads and maintains metadata encountered an unexpected value for a file attribute. Effect. The operation fails.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20048 20048 Range requested for the operation does not specify a subset of a single partition. Cause. You attempted to add a new partition or move a boundary of an existing partition with an invalid key range. The key range specified must be a subset of an existing partition, either the prefix or the suffix. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20051 20051 Transaction Management subsystem could not rollback the current transaction. Cause. The utility subsystem that performs transaction management operations failed while trying to roll back the current transaction. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem. SQL 20052 20052 Transaction Management subsystem could not set the AutoCommit. Cause.
Utility Messages (20000 through 23099) SQL 20055 20055 An internal error occurred - Transaction Management subsystem could not prepare a dynamic SQL statement. Cause. The utility subsystem that performs CLI requests to SQL failed trying to prepare a dynamic SQL statement as part of the current request. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20059 20059 The specified format file does not exist or cannot be opened for READ access. Cause. The format file specified as the command-line option for IMPORT does not exist or could not be opened. Effect. The operation fails. Recovery. Verify that the format file exists and is in a valid state. SQL 20060 20060 The -F command-line option cannot have a negative value. Cause. You specified the first row (or record) to be imported as a negative value.
Utility Messages (20000 through 23099) SQL 20064 20064 The file type specified in the command line is not valid. Only DELIM or FIXED (case insensitive) can be specified. Cause. You specified an invalid file type for the -W attribute. Effect. The operation fails. Recovery. Specify a valid file type attribute: DELIM or FIXED. SQL 20065 20065 The target table name is not specified. Cause. You did not specify a table name as a parameter to the IMPORT command. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20068 20068 An internal error or exception occurred. Cause. SQL detected an internal error. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20069 20069 The field delimiter should not contain a qualifier character. Cause. The field delimiter string that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, contains a field qualifier character. Effect.
Utility Messages (20000 through 23099) SQL 20072 20072 First character of the field delimiter must be different than the first character of the row delimiter. Cause. The field delimiter and row delimiter strings that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, start with the same character.
Utility Messages (20000 through 23099) SQL 20079 20079 User does not have INSERT privilege to perform import operation for object object-name. Cause. You do not have the minimum required privileges to perform the IMPORT operation. Effect. The operation fails. Recovery. Obtain the required INSERT privileges and resubmit. SQL 20080 20080 Last row processed was rownum. Where rownum is the number of the last row that was processed before this failure. Cause.
Utility Messages (20000 through 23099) Recovery. Append more data to the end of the data file. SQL 20083 20083 The column name in the FIXED WIDTH FORMAT part of the format file is not valid. Cause. The column name that you specified in the FIXED WIDTH FORMAT part of the format file was invalid. Effect. The operation fails. Recovery. Correct the column name in the FIXED WIDTH FORMAT part of the format file and resubmit.
Utility Messages (20000 through 23099) Where keyval is the column key value specified in the FIXED WIDTH FORMAT part of the format file. Cause. You specified an invalid column name for one of the columns in the FIXED WIDTH FORMAT part of the format file. Effect. The operation fails. Recovery. Verify and correct the column name in the FIXED WIDTH FORMAT part of the format file and resubmit. SQL 20087 20087 One or more of the specified command-line arguments are not valid. Syntax: import catalog.schema.
Utility Messages (20000 through 23099) SQL 20090 20090 The column type is not present in compile time arguments. Key = columntype Where columntype is the column name specified in the FIXED WIDTH FORMAT part of the format file. Cause. The column name that you specified was missing from an internal message. Effect. The operation fails. Recovery. None. Contact your service provider SQL 20091 20091 The column size is not specified in compile time arguments.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Release 3.
Utility Messages (20000 through 23099) SQL 20094 20094 Column first precision not present in compile time arguments. Key = precision. Cause. The specified attribute value is missing from an internal message. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20095 20095 The column last precision is not present in compile time arguments. Key = lastprecision Where lastprecision is the last precision for column scale for the specified table. Cause.
Utility Messages (20000 through 23099) SQL 20098 20098 The column name is not specified in the COLUMN FORMAT section of the format file. Cause. The column name was missing from the COLUMN FORMAT section of the format file. Effect. The operation fails. Recovery. Verify that the column names specified in the COLUMN FORMAT section of the format file are correct and add names that are missing. SQL 20099 20099 Column columnname defined as NOT NULL NO DEFAULT cannot be skipped.
Utility Messages (20000 through 23099) SQL 20101 20101 detail text. Cause. SQL has received an error as shown in the detail text. Effect. The operation fails. Recovery. Use the detail text to diagnose and correct the problem. SQL 20102 20102 The object name should not have a trailing blank. Cause. The utility subsystem that reads and maintains metadata discovered an unexpected blank in an object name. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) Recovery. None. Contact your service provider. SQL 20106 20106 An internal error occurred - invalid lock mode. Cause. SQL detected an internal error while performing a utility operation. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20107 20107 An internal error occurred - invalid access option. Cause. SQL detected an internal error while performing a utility operation. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20110 20110 IMPORT cannot insert data into a populated table that is not audited. Delete the data or have an administrator make the table audited. Cause. You tried to import into a destination file that was populated with data and was not audited, which is invalid. Effect. The operation fails. Recovery. Either delete the data or make the table audited. SQL 20111 20111 Source catalog catalog-name does not exist or cannot be accessed.
Utility Messages (20000 through 23099) Recovery. The operation fails. Effect. Correct the table name and resubmit. SQL 20114 20114 Target catalog catalog name does not exist or cannot be accessed. Where catalog name is the name of the catalog associated with the target table. Cause. You specified a target catalog name that does not exist or could not be accessed. Effect. The operation fails. Recovery. Correct the catalog name and resubmit.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Verify the catalog name and resubmit. SQL 20118 20118 Schema schema name does not exist or cannot be accessed. Where schema name is the name of the schema associated with the table to be purged. Cause. You specified a schema name that does not exist or could not be accessed. Effect. The operation fails. Recovery. Verify the schema name and resubmit. SQL 20119 20119 Table table name does not exist or cannot be accessed.
Utility Messages (20000 through 23099) SQL 20122 20122 Table has indexes. Cannot purge data from partition. Cause. You attempted to perform a partial PURGEDATA operation, which is supported only on tables that do not have dependent indexes. The table you requested has dependent indexes. Effect. The operation fails. Recovery. Remove any associated indexes and resubmit. If this is not possible, perform a DELETE request in the range of the specified partition.
Utility Messages (20000 through 23099) Recovery. Specify TARGET PURGE for an existing target object and resubmit. SQL 20128 20128 table name is a metadata table. DUP cannot be performed on metadata tables. Where table name is the name of the table currently being duplicated. Cause. The table name that you specified was a metadata table. You cannot perform the DUP operation on metadata tables. Effect. The operation fails. Recovery. Specify a different table and resubmit.
Utility Messages (20000 through 23099) SQL 20132 20132 A NULL value cannot be assigned to a NOT NULL NO DEFAULT field. Column number = column number Where column number is the column specified in the request. Cause. You attempted to import data that would assign a NULL to a NOT NULL field. Effect. The IMPORT operation fails. Recovery. Either change the data or change the field to accept NULL. SQL 20133 20133 A user defined transaction has been started. DUP cannot be performed. Cause.
Utility Messages (20000 through 23099) SQL 20137 20137 table has features that require schema version version1 or higher. The version of schema is version2. Cannot perform DUP. Where table is the source table for the DUP operation. Where version1 is the object feature version (OFV) of table. This is the lowest schema version that can store the features of the source table. Where schema is the target schema for the DUP operation. Where version2 is the version of schema. Cause.
Utility Messages (20000 through 23099) SQL 20140 20140 Wrong parameter name passed. Cause. The utility subsystem responsible for performing CLI operations failed while trying to get information from the returned statement. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20141 20141 Wrong parameter index passed. Cause. The utility subsystem that performs CLI operations failed while trying to get information from the returned statement. Effect.
Utility Messages (20000 through 23099) SQL 20145 20145 Key range specified for a table that is not a keysequenced table. PURGEDATA cannot be performed. Cause. You attempted to perform a PURGEDATA operation on a table by specifying a key range. The table is not a key-sequenced table and therefore there are no key ranges to specify. Effect. The operation fails. Recovery. Perform the PURGEDATA request without specifying key ranges. SQL 20146 20146 Key does not exist. Cannot perform PURGEDATA. Cause.
Utility Messages (20000 through 23099) SQL 20149 20149 External indexes exist for this object-type. Since the source and target have the same catalog and schema, index-map must be specified. DUP cannot be performed. Where object-type is table. Cause. You failed to define all the indexes of the index-map. Effect. The operation fails. Recovery. Specify the target indexes through the index-map clause and resubmit.
Utility Messages (20000 through 23099) SQL 20153 20153 The VARCHAR varying-length can support VARCHAR data type only. Cause. You specified VARCHAR for a column that is not a VARCHAR data type. Effect. The operation fails. Recovery. Verify your data file and resubmit. SQL 20154 20154 Column Null or Default flag is not present in COMPILE TIME ARGS. Key = key value Cause. SQL encountered an internal error in the stored procedure interface. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20160 20160 Error occurred while encoding key value key value for catalog.schema.table. Cause. You specified an invalid key value for the first key of a partition. Effect. The operation fails. Recovery. Correct input data and resubmit. SQL 20161 20161 Resume option of RECOVER command for DUP is possible only if DUP finished the data transfer between the source and target objects. RECOVER cannot be performed. Cause.
Utility Messages (20000 through 23099) SQL 20164 20164 The search condition for the specified check constraint has a syntax error. Cause. You attempted to create a check constraint, but a syntax error was found in the search condition. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 20165 20165 The number of key columns (value1) defined on the table or index is less than the number of key columns (value2) defined in the request. Cause.
Utility Messages (20000 through 23099) SQL 20168 20168 The partition key value cannot be specified when adding a partition to a hash-partitioned table or index. Cause. You specified partitioning key values in an “Add a new hash partition” request. You can specify the partitioning key values only when adding a new range partition. Effect. The operation fails. Recovery. Remove the WHERE clause and resubmit. SQL 20169 20169 Only the last partition of a hash-partitioned table or index can be dropped. Cause.
Utility Messages (20000 through 23099) SQL 20172 20172 RecordLength is missing in the FIXED WIDTH FORMAT section of the format file. Cause. The record length value is missing in the FIXED WIDTH FORMAT section of the format file. Effect. The operation fails. Recovery. Correct the format file and resubmit. HP NonStop SQL/MX Release 3.
Utility Messages (20000 through 23099) SQL 20173 20173 A transaction must be started before executing this request. Cause. SQL detected an internal error. Effect. SQL is unable to process the statement. Recovery. None This is an internal error. Contact your service provider. SQL 20174 20174 An internal error occurred - A valid SQLNode is expected. Cause. SQL detected an internal error. Effect. The operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Wait until the concurrent operation has finished and then resubmit. SQL 20177 20177 Resume option of RECOVER command for Import is possible only if Import finished inserting the data in the target table. RECOVER cannot be performed. Cause. The resume option is not allowed for the failed IMPORT operation because the data insertion part was not finished. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20181 20181 Begin key is greater than end key. PURGEDATA cannot be performed. Cause. The list of partitions specified in the key range specified an invalid range. There are no partitions to purge. Effect. The operation fails. Recovery. Specify a valid key range and resubmit. SQL 20182 20182 An internal error was encountered: OPEN of Import Stored Procedure failed. Cause. SQL encountered an internal error in the stored procedure interface. Effect.
Utility Messages (20000 through 23099) SQL 20185 20185 More than one partition resides on volume volume name. The MODIFY utility does not know which partition to move or drop. Where volume-name is the name of the volume containing the specified partition. Cause. You specified only the volume name in the LOCATION clause, but the object has more than one partition in the specified volume. Effect. The operation fails. Recovery. Correct the sections in the format file and resubmit.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Remove the TO PREVIOUS PARTITION phrase and resubmit. SQL 20190 20190 Data in the last partition (or subset) cannot be moved to the next partition because no next partition exists. Cause. You tried to move data in the last partition to a nonexisting next partition. Effect. The operation fails. Recovery. Remove the TO NEXT PARTITION phrase and resubmit. SQL 20191 20191 This operation is not supported on nonaudited tables. Cause.
Utility Messages (20000 through 23099) SQL 20194 20194 Loading of index index-name failed. Where index-name is the index to be populated as specified by the POPULATE INDEX command. Cause. The index load failed because of some problem. Effect. The operation fails. Recovery. If the problem was caused by a uniqueness violation, remove duplicate rows, and resubmit. If the problem occurred for some other reason, use the messages that accompany this one to diagnose and fix the problem.
Utility Messages (20000 through 23099) SQL 20197 20197 The specified index index-name is not available. Where index-name is the index to be populated as specified by the POPULATE INDEX command. Cause. The index name specified by the caller is not valid. The caller qualifying the index name with a catalog or schema is the probable cause. Catalog and schema names are not supported. Effect. The operation fails. Recovery. Specify a valid name, and resubmit.
Utility Messages (20000 through 23099) Recovery. Specify a valid catalog name and resubmit. SQL 20201 20201 Schema does not exist. Cause. The schema name specified by the caller is not valid. Effect. The operation fails. Recovery. Specify a valid schema name and resubmit. SQL 20202 20202 Table does not exist. Cause. The specified table does not exist. Effect. The operation fails. Recovery. Specify the correct object name and resubmit. SQL 20203 20203 Index index-name does not exist.
Utility Messages (20000 through 23099) SQL 20205 20205 Index index-name is online. Cannot perform POPULATE INDEX. Cause. An attempt to populate the index that is already populated. Effect. None. Recovery. None. SQL 20206 20206 Data type conversion failed while converting key value (column-value[,column-value]...)to data type(s) (datatype[,date-type]...) for object-name. Where column-value is a column value in the specified partitioning key value.
Utility Messages (20000 through 23099) Recovery. If object-name was not incorrectly added, no recovery is required. SQL 20210 20210 A DDL_LOCKS name must be specified for object-name. Where object-name is the name of the object to recover. Cause. RECOVER found multiple entries for the current table or index that needs to be recovered and cannot determine which operation to recover. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Recovery. None. Contact your service provider. SQL 20214 20214 No recover is defined for DDL_LOCKS name lock-name. Where lock-name identifies the name of the operation to recover. Cause. A request was made to recover an operation which is not specified correctly in the metadata. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20215 20215 Recovery failed for DDL_LOCKS name lock-name. Cause.
Utility Messages (20000 through 23099) SQL 20218 20218 Schema does not exist. Cause. The schema name specified by the caller is not defined or not visible on the current system. Effect. The operation fails. Recovery. Specify a valid schema name and resubmit. SQL 20219 20219 Table table-name does not exist. Where table-name is the name of the table to recover. Cause. The table name specified by the caller is not defined or not visible on the current system. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Recovery. Correct the syntax and resubmit. SQL 20222 20222 Error occurred for partition file file name when attempting to set the number of index levels. Where file-name is the partition being accessed. Cause. An unexpected error occurred while completing a data movement operation for the request. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) Recovery. Either purge the entire file or use a DELETE statement (DML statement) to remove the required rows. SQL 20226 20226 An internal error occurred - trigger parameter is not set. Cause. The utility subsystem that reads and maintains the metadata could not find all the information for a trigger. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) Recovery. Use the messages that accompany this one to diagnose and correct the problem. SQL 20230 20230 You cannot drop all partitions of the table or index. At least one partition must remain. Cause. You tried to drop the only remaining partition of a table or index. Effect. The operation fails. Recovery. If you want to drop the last remaining partition, use the DROP TABLE or INDEX statement.
Utility Messages (20000 through 23099) Recovery. None. SQL 20234 20234 Partition partition could not be found. Where partition is the physical name of the partition, in Guardian file name format. Cause. The MODIFY utility could not locate the specified partition. Effect. The operation fails. Recovery. None. SQL 20235 20235 Error returned from USER_GETINFO_ while converting userid to user name, status: status, userid: userid. Where status is the status returned from USER_GETINFO_.
Utility Messages (20000 through 23099) SQL 20237 20237 An internal error occurred: invalid username specified, username: username. Where username is the name of the current user. Cause. The user name is not valid. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20238 20238 A user-defined transaction has been started. The MODIFY utility cannot perform the partition management operation. Cause.
Utility Messages (20000 through 23099) SQL 20241 20241 The MODIFY utility cannot perform a DROP HASH operation on the object object-name because the target partition partition-name does not have enough space for the redistribution of data. Cause. The MODIFY DROP HASH operation failed because the remaining partitions do not have enough space for the redistribution of the dropped partition data. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Recovery. Re-create the Unicode data file. Specify the standard byte order mark sequence: 0xFF 0xFE, for the little- endian byte order, and 0xFE 0xFF, for the beginendian byte order. SQL 20245 20245 An invalid character set was specified. Column columnname is part of the partitioning key and must be defined with the character set ISO88591. Where column-name is the name of the column that corresponds to the invalid character set value. Cause.
Utility Messages (20000 through 23099) SQL 20252 20252 Only a single ADD, MOVE, DROP, or REUSE request is allowed. Cause. You included more than one request to the MODIFY command. Note that the REUSE request works only with range-partitioned tables. Effect. The operation fails. Recovery. None. SQL 20253 20253 The new key range must be empty before you can reuse a partition. Cause. The table already has data in the key range specified in the WITH clause of the REUSE request. Effect. The operation fails.
Utility Messages (20000 through 23099) SQL 20257 20257 This partition management operation is not supported for system-clustered base table table-name. Where table-name is the name of the table specified in the MODIFY command. Cause. You attempted a partition management operation other than moving an entire partition to a new location. Effect. The operation fails. Recovery. None. SQL 20258 20258 The WHERE clause cannot be used with table-name because it is a system-clustered base table.
Utility Messages (20000 through 23099) Recovery. None. SQL 20263 20263 An invalid DUP operation was specified; The INDEX ON option is required for duplicating unique and/or nonclustering primary key constraints. Cause. The INDEX ON option is required for duplicating a source table with unique or nonclustering primary key constraints. Effect. The operation fails. Recovery. Specify the INDEX ON option and resubmit. SQL 20264 20264 Invalid index names were specified in index-map. Cannot perform DUP. Cause.
Utility Messages (20000 through 23099) Where code2 is the expected value. Cause. An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20267 20267 Returned buffer from SPI request has a length of len1, expected a value less than or equal to len2. Where len1 is the length returned from the SPI request.
Utility Messages (20000 through 23099) Cause. The audit attribute of the table could not be turned off during the IMPORT operation due to an internal failure. The attribute is turned off when the table is empty and contains no indexes. This enables IMPORT to make use of Side Tree inserts for better performance. The attribute is turned back on after the IMPORT operation is complete. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Recovery. Change the table to be audited using the FIXUP command, and resubmit. SQL 20273 20273 An internal error occurred. Cause. An unexpected error was returned while attempting to perform a SPI operation. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20274 20274 Decoding the signature for a ROUTINE object failed. Cause. An unexpected error occurred while decoding the signature for a ROUTINE object.
Utility Messages (20000 through 23099) SQL 20290 20290 The current operation on partition partition for the object object failed because a utility operation on the same partition is already in progress or has failed. Where partition is the Guardian location of the partition involved in another utility operation. Cause. The specified partition partition is already involved in another utility operation, or a previous utility operation on the specified partition failed. Effect.
Utility Messages (20000 through 23099) SQL 20294 20294 The partition cannot be reused because the partition contains data and the table has an enabled DELETE trigger. Cause. The partition that you specified in the partition management request contains data, and the specified base table has an enabled DELETE trigger. The REUSE operation is not allowed on such a partition. Effect. The MODIFY utility operation fails. Recovery. Disable all triggers on the table and retry the REUSE operation.
Utility Messages (20000 through 23099) Recovery. Run FUP RELOAD manually to reclaim any free space on the specified partitions if the D flag (INCOMPLETE SQLDDL OPERATION), or F flag (UNRECLAIMED FREE SPACE) is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set. SQL 20297 20297 The MODIFY request has completed successfully, but was directed not to start ORSERV. Please run FUP RELOAD to reclaim free space. Cause.
Utility Messages (20000 through 23099) SQL 20302 20302 The IO buffer is not large enough to hold the object's metadata. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20303 20303 CANCEL cannot be used as an option for this RECOVER operation. Cause. You attempted to recover a failed PURGEDATA request by specifying CANCEL. However, PURGEDATA has progressed too far, and only RESUME can be specified. Effect.
Utility Messages (20000 through 23099) SQL 20307 20307 The catalog object already exists. Cause. You are trying to restore a catalog object that already exists. Effect. The operation fails. Recovery. Check the location of the catalog. SQL 20308 20308 The schema object already exists. Cause. You are trying to restore a schema object that already exists. Effect. The backup or restore operation fails. Recovery. Check the location of the schema.
Utility Messages (20000 through 23099) SQL 20312 20312 The index object already exists. Cause. You are trying to restore an index object that already exists. Effect. The operation fails. Recovery. Check the location of the index. SQL 20318 20318 The partition object was not found. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20319 20319 The table object already exists. Cause. You are trying to restore a table object that already exists.
Utility Messages (20000 through 23099) SQL 20320 20320 The view object already exists. Cause. You are trying to restore a view object that already exists. Effect. The operation fails. Recovery. Check the location of the view. SQL 20321 20321 An internal error was encountered: invalid catalog or schema object. Cause. SQL could not find the catalog or schema referenced by a view. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20331 20331 The specified parent object is not valid. Cause. You tried to perform an online restore, but the audit object has an invalid SQL node object. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20332 20332 The audit metadata is not valid. Cause. You tried to perform an online restore, but the audit trail data (the metadata of the audit object) on the tape is invalid. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) Effect. The backup or restore could not be performed. Recovery. None. This is an internal error. Contact your service provider. SQL 20336 20336 TMF function call failed, error code = error number. Cause. Internal error during online backup or restore. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20337 20337 Feature not supported by the online option. Cause.
Utility Messages (20000 through 23099) SQL 20340 20340 Indexes index-list on table table were successfully populated. Where index-list is a comma-separated list of indexes. Where table is the name of the table. Cause. One or more indexes successfully populated. Effect. The operation partially succeeded. Recovery. This is an informational message that indicates indexes that were successfully populated. This message appears with error 20339, which lists the indexes that failed to populate.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Enter MXTOOL HELP to get correct syntax, and resubmit. SQL 20353 20353 Syntax error. An invalid operation operation was requested. Try ‘mxtool help’. Where operation is the operation specified in the request. Cause. You specified MXTOOL but did not specify FIXUP, VERIFY, GOAWAY, or INFO as a valid operation. Effect. The operation fails. Recovery. Enter MXTOOL HELP to get correct syntax, and resubmit.
Utility Messages (20000 through 23099) Where error is the error returned by the file system. Cause. GOAWAY could not drop the specified Guardian file. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20357 20357 File name is not an SQL/MX object. Where name is the name of the Guardian file requested to be removed. Cause. GOAWAY could not drop the specified Guardian file. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20360 20360 Object object does not exist or the Object is not valid for the current operation. Where, object is the name of the table, index, or view specified in the MXTOOL request. Cause. You specified an incorrect table, index, or view name. Effect. The operation fails. Recovery. Enter the correct object name and resubmit. SQL 20362 20362 Error error was returned while validating the file set list specified by “Guardian file”.
Utility Messages (20000 through 23099) SQL 20364 20364 An internal error occurred while getting the Guardian file name. Cause. An unexpected error was returned while reading the file label for a Guardian file. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20370 20370 Invalid flag provided for the operation. Try ‘mxtool help’ for the operation. Cause. The syntax you specified was invalid. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20373 20373 The specified system does not exist in the network. Cause. The system name specified in the file template for Guardian files does not exist in the current network, possibly because of a misspelling. Effect. The operation fails. Recovery. Correct the spelling and resubmit. SQL 20374 20374 Option -s cannot be used in combination with any filtering option. Cause. A syntax error occurred while processing the GOAWAY operation.
Utility Messages (20000 through 23099) SQL 20450 20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name). Where data fork name is the Guardian file of the data fork. Where resource fork name is the Guardian file of the resource fork. Cause. You specified invalid options for the GOAWAY command. Effect. The operation fails. Recovery. Do not use the DATA/RESOURCE FORK option, and resubmit.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Remove the lock on the label and retry the operation. SQL 20454 20454 Only Super.Super user can perform the GOAWAY operation. Cause. User error. Only the SUPER ID user can run the GOAWAY utility. Effect. The operation fails. Recovery. Have the SUPER ID user run the GOAWAY utility. SQL 20456 20456 The following file will be removed name.
Utility Messages (20000 through 23099) Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20459 20459 You specified -both for the GOAWAY request. However, only file exists. You must use -df or -rf option to GOAWAY the label. Where file is the name of the existing data or resource fork. Cause. The GOAWAY operation failed because only the data fork or resource fork exists, and the -both option was specified. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20462 20462 Option -rf does not match label data fork name. Use -df to GOAWAY the label. Where data fork name is the name of the data fork. Cause. The GOAWAY operation failed because you specified data fork name with the -rf option. Effect. The operation fails. Recovery. Retry with the -df option. SQL 20520 20520 Object object cannot participate in refresh; a utility operation associated with a DDL lock on it is currently running.
Utility Messages (20000 through 23099) SQL 20525 20525 Task task-name cannot be executed remotely. Where task-name is the name of a refresh task. Cause. The refresh operation cannot be executed remotely because the buffer is full. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 20531 20531 An internal error occurred while extracting data type information from an internal data buffer. Cause. An internal error occurred. Effect. The operation fails.
Utility Messages (20000 through 23099) SQL 20588 20588 Invalid Character error converting string from character set $0~string0 to character set $1~string1. Cause. You specified an invalid character set. Effect. The operation fails. Recovery. Specify an ISO88591 character set. SQL 20589 Buffer Overrun error converting string from character set $0~string0 to character set $1~string1. Cause. You specified an invalid character set. Effect. The operation fails. Recovery. Specify an ISO88591 character set.
Utility Messages (20000 through 23099) SQL 20682 20682 Duplicate target location location was specified. Where location is an explicity specified target location for renaming a table or index. Cause. Duplicate target locations are specified. Effect. Rename operation fails and partitions are not renamed. Recovery. Specify unique set of target locations, and retry rename operation using MODIFY command.
Utility Messages (20000 through 23099) SQL 20685 20685 Existing location location matches multiple patterns. Where location is an existing location that matches more than one file name pattern. Cause. Multiple Guardian File Name patterns are specified and an existing location matches more than one of these patterns. Effect. Rename operation fails and partitions are not renamed. Recovery.
Utility Messages (20000 through 23099) SQL 20702 20702 A file system error occurred during the audit fixup phase of the operation, on file Guardian file name. Where Guardian file name is the name of the partition being processed. Cause. During the online partition management operation, the MXAUDSRV process encountered a file system error on the partition named by Guardian file name during redo processing. Effect. The MODIFY operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20705 20705 An audit fixup request was made out of sequence. Cause. During an online partition management operation, the MXAUDSRV process received an unexpected request from the MODIFY code. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. SQL 20706 20706 An audit fixup process received a request with an invalid type for an audit fixup operation. Cause.
Utility Messages (20000 through 23099) Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. SQL 20709 20709 A TMF audit read error occurred during the audit fixup phase of the operation, in audit fixup process process name. Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered an error while reading a TMF audit record. Effect. The MODIFY operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20712 20712 An internal error occurred during the audit fixup phase of the operation. The maximum size for a request message to the audit fixup server was exceeded. Cause. During an online partition management operation, the MXAUDSRV process received a request of an invalid size from the MODIFY code. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) Cause. During an online partition management operation, the MXAUDSRV process encountered an audit trail versioning error while processing audit records. Effect. The MODIFY operation fails. Recovery. Correct the TMF problem and resubmit. SQL 20719 20719 A request with an incompatible version was made to audit fixup process process name. Where process name is the MXAUDSRV process name. Cause.
Utility Messages (20000 through 23099) SQL 20723 20723 An audit fixup process found a label change audit record during fixup work. These audit records are most likely caused by another process performing a concurrent DDL operation, which is not allowed. Cause. During an online partition management operation, the MXAUDSRV process encountered a file label change audit record. Effect. The MODIFY operation fails. Recovery. Resubmit the request.
Utility Messages (20000 through 23099) Recovery. License the MXAUDSRV program file and retry the operation. SQL 20727 20727 An unexpected error code error code was returned by the audit fixup process process name. Where error code is the returned file system number. Where process name is the MXAUDSRV process name Cause. During an online partition management operation, the MXAUDSRV process. reported an unknown error code. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20730 20730 An unexpected key transform error error code occurred in audit fixup process process name. Where error code is the returned file system number. Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered an error when attempting to examine data fields extracted from a TMF audit record. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20733 20733 The times given in ONCOMMITERROR clauses are not in ascending order. Cause. The MODIFY command includes multiple COMMIT BEFORE and/or COMMIT AFTER clauses, and a time given in one such clause is earlier than one given in some preceding clause. Effect. The MODIFY utility did not process the request. Recovery. Correct the COMMIT clauses so that they are in ascending order in time, and retry the operation.
Utility Messages (20000 through 23099) SQL 20751 20751 A user-defined transaction has been started. VERIFY cannot be performed. Cause. A TMF transaction is currently active. The VERIFY process does not allow active transactions. Effect. The operation fails. Recovery. Commit or terminate the current transaction and resubmit. SQL 20752 20752 The cmdname command cannot work on object object-name that has an object type of type. cmdname supports only objects that have an object type of BT.
Utility Messages (20000 through 23099) Where object is the information being retrieved, such as the ANSI name. Cause. An unexpected error occurred while you were retrieving ANSI name information. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual topic FileSystem Errors for possible recovery action and resubmit.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. VERIFY does not allow resource fork names to be specified. SQL 20758 20758 Partition name is offline. Where filename is the Guardian file name of the partition that is offline. Cause. VERIFY discovered that the table being verified has a partition that is offline. This is a partition that is currently part of an active MODIFY request or a failed MODIFY request. Effect. None. This is an informational message. Recovery.
Utility Messages (20000 through 23099) SQL 20761 20761 The corrupt flag (flag1) defined on the label does not match the corrupt flag (flag2) defined in the metadata for Guardian file (fname). Where flag1 is the value of the corrupt flag on the label. Where flag2 is the value of the corrupt flag found in the metadata. Where fname is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery.
Utility Messages (20000 through 23099) SQL 20764 20764 The max extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file). Where size1 is the maxextent size defined on the label. Where size2 is the maxextent size defined in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20767 20767 The key size (size1) defined on the label does not match the key size (size2) defined in the metadata for Guardian file (file). Where size1 is the key size stored in the file label. Where size2 is the key size found in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider.
Utility Messages (20000 through 23099) Recovery. Contact your service provider. SQL 20770 20770 The ANSI name namespace (space1) in resource fork does not match the ANSI namespace (space2) defined in the metadata for Guardian file (file). Where space1 is the ANSI namespace found in the resource fork. Where space2 is the ANSI namespace found in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None.
Utility Messages (20000 through 23099) SQL 20775 20775 The number of droppable check constraints in resource fork (num1) does not match the number of droppable check constraints (num2) in the metadata for Guardian file (file). Where num1 is the number of constraints described in the constraint map in the resource fork. Where num2 is the number of constraints described in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None.
Utility Messages (20000 through 23099) SQL 20778 20778 The constraint information is missing from the metadata for object (name). Where name is the name of the table. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20779 20779 The number of indexes (num1) in the index map array on the resource fork does not match the number of indexes (num2) in the metadata for Guardian file (file).
Utility Messages (20000 through 23099) SQL 20781 20781 The index map array is missing from the resource fork for Guardian file (file). Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20782 20782 The index information is missing from the metadata for index (name). Where name is the name of the table. Cause.
Utility Messages (20000 through 23099) SQL 20784 20784 Partition map entry (file1) is defined in the metadata but is missing from the resource fork for Guardian file (file2). Where file1 is the Guardian name of the partition. Where file2 is the Guardian file where there was no partition map. The metadata indicates that there should be a partition map. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20787 20787 The partition (name1) defined in the metadata for index (index) does not match the partition (name2) defined in the resource fork for Guardian file (file). Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20788 20788 User does not have authority to perform operation for object object. Where object is the name of the table being verified. Cause.
Utility Messages (20000 through 23099) Where mname is the partition name defined in the metadata. Where file is the file being verified. Cause. An inconsistency was found between the partition name stored in the resource fork and the partition name found in the metadata. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20791 20791 An internal error occurred - the partition list is missing from the metadata for object (name).
Utility Messages (20000 through 23099) Cause. An unexpected error returned on an attempt to extract the catalog name, schema, or table from the resource fork. Effect. The operation fails. Recovery. Correct the problem and resubmit. If the problem persists, contact your service provider about this condition. SQL 20795 20795 VERIFY cannot work on Guardian file (file) that has an object type of (type1). VERIFY supports only objects that have an object type of type2.
Utility Messages (20000 through 23099) Where object name is the ANSI fully qualified name of the table or view. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. For an inactive DDL lock, contact your service provider. For an active DDL lock, wait for the operation holding the lock to complete. SQL 20799 20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name).
Utility Messages (20000 through 23099) SQL 20801 20801 There is currently an activity row hiding predicate for file-name. Where activity indicates an active row hiding a predicate. Where file-name is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Another utility operation on the same partition is already in progress or has failed. Effect. None. This is an informational message. Recovery.
Utility Messages (20000 through 23099) SQL 20804 20804 The object type in resource fork (robject-type) does not match the object type (mobject-type) defined in the metadata for Guardian file (file-name). Where robject-type is the object type in the resource fork. Where mobject-type is the object type in the metadata. Where file-name is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery.
Utility Messages (20000 through 23099) SQL 20807 20807 File code (code value) is incorrect for Guardian file ( file-name). Where code value is the value of file code. Where file-name is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20816 20816 The current_epoch defined on the label does not match the current_epoch defined in the metadata for Guardian file (file).
Utility Messages (20000 through 23099) SQL 20821 20821 Constraint constraint is disabled. Where constraint is the name of the constraint. Cause. MXTOOL VERIFY found a constraint that is disabled. Effect. This is an informational message. Recovery. Contact your service provider to enable the constraint. SQL 20822 20822 The DML privileges in the file label do not match the privileges defined in the metadata. Cause. An inconsistency was found during the VERIFY operation. Effect. None.
Utility Messages (20000 through 23099) Effect. None. This is a warning. Recovery. No recovery is necessary. SQL 20853 20853 name is not an SQL/MX object that is supported by FIXUP. Only TABLES and INDEXES are supported. Where name is the SQL/MX object. Cause. You attempted to run the FIXUP utility on an SQL/MX object that was not a table or index. Effect. The operation fails. Recovery. Do not attempt to run the FIXUP utility on objects other than tables and indexes. Enter a valid name and resubmit.
Utility Messages (20000 through 23099) SQL 20857 20857 FIXUP did not change the redefinition timestamp for file file-name. It is already set to the correct value of time. Where file-name is the Guardian file-name of the SQL/MX object. Where time is the current redefinition timestamp associated with the SQL/MX object. Cause.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Enter the correct SQL/MX file-name and resubmit. SQL 20861 20861 The corrupt bit has been reset for only local partitions of file-name. Please execute the command on the remote nodes to update respective remote partitions. Where file-name is the full name of the SQL/MX object. Cause. This message is displayed whenever FIXUP is used with the “-rc” option on a table or index with partitions on a remote node. Effect.
Utility Messages (20000 through 23099) Recovery. None. SQL 21052 21052 Tables source-table and target-table have incompatible clustering key specifications. Where source-table is the three-part ANSI name of the source table of a FASTCOPY command. target-table is the three-part ANSI name of the target table of a FASTCOPY command. Cause. The FASTCOPY TABLE or FASTCOPY INDEX command is executed.
Utility Messages (20000 through 23099) Effect. The fastcopy operation fails. The availability of source and target indexes and their tables is not affected. Recovery. None. SQL 21054 21054 Index target-index has no matching index from table source-table. Where source-table is the three-part ANSI name of the source table of a FASTCOPY command. target-index is the three-part ANSI name of an index on the target table of a FASTCOPY command. Cause.
Utility Messages (20000 through 23099) SQL 21056 21056 Index index is offline. Where index is the three-part ANSI name of the source or target index of the FASTCOPY INDEX command. Cause. The FASTCOPY INDEX command is executed and the source or target index is offline. Effect. The fastcopy operation fails. The availability of source and target indexes and their tables is not affected. Recovery.
Utility Messages (20000 through 23099) SQL 21059 21059 Object cannot participate in a FASTCOPY command. Where object is the three-part ANSI name of an SQL/MX object. Cause. The specified object, which is mentioned as either source or target object, is not allowed. The following types of objects are not allowed to participate in the fastcopy operation: metadata tables views SQL/MP aliases stored procedures Effect. The fastcopy operation fails; involved objects are left unchanged. Recovery. None.
Utility Messages (20000 through 23099) SQL 21062 21062 Schema schema does not exist or cannot be accessed. Where schema is the two-part ANSI name of an SQL/MX schema. Cause. A FASTCOPY command referenced an object from schema. However, the schema does not exist. Effect. The fastcopy operation fails; involved objects are left unchanged. Recovery. None. SQL 21063 21063 Object object does not exist or cannot be accessed. Where object is the three-part ANSI name of an SQL/MX table or index. Cause.
Utility Messages (20000 through 23099) SQL 21065 21065 source and target already participate in different fastcopy operations. Where source-object is the three-part ANSI name of a source table or index for a FASTCOPY command. target-object is the three-part ANSI name of a target table or index for a FASTCOPY command. Cause.
Utility Messages (20000 through 23099) SQL 21068 21068 The FASTCOPY of target-object has been canceled. Where target-object is the three-part ANSI name of a target table or index for a FASTCOPY or RECOVER...RESUME command. Cause. The RECOVER...CANCEL operation is in progress for the target object. Effect. The operation fails; involved objects are left unchanged. Recovery. None. SQL 21069 21069 FASTCOPY already is in progress for target-table.
Utility Messages (20000 through 23099) SQL 21071 21071 target-table has DELETE triggers enabled. Where target-table is the three-part ANSI name of the target table for a FASTCOPY command. Cause. The target table for an initial FASTCOPY command is non-empty; is the subject table for a DELETE trigger that is enabled. Effect. The operation fails; involved objects are left unchanged. Recovery. Disable DELETE triggers on the target table, retry the FASTCOPY command, and then enable the triggers again.
Utility Messages (20000 through 23099) SQL 21074 21074 IDENTITY column on target table has IDENTITY specifications that are incompatible with corresponding IDENTITY column on source table. Cause. The sequence generator specifications of source and target tables do not match. Effect. The FASTCOPY operation fails to execute. Recovery. This error is returned when the following conditions are not met. Ensure these conditions are met, and retry FASTCOPY operation.
Utility Messages (20000 through 23099) SQL 23001 23001 servername: An error occurred while instantiating class-name. Where servername is the name of the server program that issued the error. Where class-name is the name of the class that could not be instantiated. Cause. An error occurred while instantiating the class_name. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. SQL 23002 23002 servername: An error occurred while allocating heap.
Utility Messages (20000 through 23099) SQL 23004 23004 Specified argument is not valid: argument_name optional_argument_value. Where argument-name is the given invalid argument name. Where optional-argument-value is an invalid value given for the argument. Cause. A run-time argument is invalid. Effect. The operation fails. Recovery. Correct the run-time argument and resubmit. SQL 23005 23005 Required argument missing - argument_type. Where argument_type indicates the missing argument. Cause.
Utility Messages (20000 through 23099) SQL 23011 23011 servername: An unexpected XML tag found: xml_tag. Where servername is the name of the server program that issued the error. Where xml_tag is the XML tag that could not be identified. Cause. servername discovered an XML tag that is not supported or is invalid. This error could indicate a problem with the mxexportddl XML file generation. It could also indicate a version problem of a downrev mximportddl running on input from an uprev mxexportddl. Effect.
Utility Messages (20000 through 23099) SQL 23014 23014 servername: An internal error occurred - unhandled exception; cannot proceed. Where servername is the name of the server program that issued the error. Cause. An unexpected exception occurred. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 23015 23015 servername: DDL command could not be found in buffer: description. Where servername is the name of the server program that issued the error.
Utility Messages (20000 through 23099) SQL 23017 23017 servername: Expected XML tag is missing: description. Where servername is the name of the server program that issued the error. Where description contains detailed information about the missing XML tag. Cause. When processing an XML input file, an expected tag or tag attribute was not found. This might indicate a problem with the mxexportddl generated output XML file. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Where object-name is the name of the missing SQL/MX object. Cause. An expected SQL/MX object is not on the target system. Effect. The operation fails. Recovery. Correct the target system and resubmit. SQL 23021 23021 An argument requires a corresponding value description. Where description contains detailed information about the argument in error. Cause. You did not specify a needed value for a specific run-time argument. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Effect. None. Recovery. None. SQL 23025 23025 object-type object-name is skipped. Where object-name is the name of the SQL/MX object. Where object-type is the type of the SQL/MX object. Cause. An unexpected error has occurred. Effect. The reported SQL/MX object is skipped. Recovery. None. Contact your service provider. SQL 23026 23026 object-type object-name is dropped and recreated. Where object-name is the name of the SQL/MX object.
Utility Messages (20000 through 23099) Cause. The target table already contains statistics and KEEPSTATS option is set to OFF. Effect. The target table's statistics will be cleared. Recovery. To avoid statistics from being cleared, set KEEPSTATS option to ON. SQL 23029 23029 option-name argument is provided and so SQL/MX objects are not imported. Where option-name is either LISTONLY ON or PREPAREMAP. Cause. None. Effect. SQL/MX objects will not be imported. Recovery. None.
19 Versioning and Distribution Messages (25000 through 25399) SQL 25001 25001 Program executable, executing on node, has encountered a version error. where, executable is the OSS path name or Guardian file name of the program file for the process that encounters the version error. node is the node where the process executes. Cause. An SQL/MX system process, for example, an ESP or the compiler, encountered a versioning error.
Versioning and Distribution Messages (25000 through 25399) SQL 25004 25004 object does not exist or cannot be accessed because of a version incompatibility. Its schema is currently being upgraded to version version1; the component cannot access schemas with versions higher than version2. where, object is the type and name of the affected database object. version1 is the target version of the upgrade schema operation. component is the software component that detects the situation.
Versioning and Distribution Messages (25000 through 25399) SQL 25006 25006 The following feature is only available for schemas with version feature-version and higher: string. Schema schema has schema version schema-version. Where, feature-version is the minimum version schema that can accommodate the features used by the object. string is a short text description of the maximum version feature used by the object. schema is the affected schema of the object. schema-version is the schema version of schema.
Versioning and Distribution Messages (25000 through 25399) Cause. The remote node nodehas an MXV MXV1earlier than the local node’s earliest supported MXV MXV2, which is not supported. Effect. The operation fails. Recovery. Migrate the remote node to an MXV that is later than or equal to the local node’s oldest supported MXV. Or, conversely, fallback the local node to an MXV with a corresponding oldest supported MXV that is lower than or equal to the remote node’s MXV.
Versioning and Distribution Messages (25000 through 25399) SQL 25103 25103 A SQL/MX compiler of version version is required but cannot be found at the expected location (filename). where, version is the compiler version of a required compiler program.. filename is the expected Guardian file name of the required compiler program file. Cause. The compiler of the specified, supported version is required to compile the query or module; however, that compiler does not exist in the default compiler location.
Versioning and Distribution Messages (25000 through 25399) version1 is the schema version of that database object schema. node is the name of the node that detects the incompatibility. version2 is that node’s MXV. Cause. An attempt is made to access a table or view in a schema with a schema version that is higher than the accessing node’s MXV. This error can be issued from the local node or from an ESP on a remote node. Effect. The request fails. Recovery.
Versioning and Distribution Messages (25000 through 25399) object is the name of the affected database object. node is the name of the node where object is present. version1 is the schema version of object schema. version2 is that node’s MXV. Cause. An attempt is made to access a database object with an object schema version that is incompatible with one or more nodes where the object (or a partition or an index of the object) resides.
Versioning and Distribution Messages (25000 through 25399) version2 is the compiler version of the compiler that executes the DDL or utility operation. Cause. The affected DDL or utility operation references a database object in a schema with a schema version that is higher than the compiler version of the compiler that executes the operation. This can happen if one of these is true: A downrev compiler is explicitly being used to execute the operation.
Versioning and Distribution Messages (25000 through 25399) SQL 25207 25207 The system schema on node node1 has system schema version version1; node node2 does not support system schema versions lower than version2. where, node1 is the name of the node with an incompatible version system schema. version1 is the system schema version of node1. node2 is the name of the node where the incompatibility is detected. version2 is the earliest supported system schema version for node2. Cause.
Versioning and Distribution Messages (25000 through 25399) Where version1 and version2 are schema versions of schema1 and schema2, respectively. Cause. An attempt was made to create a view, trigger, or referential integrity constraint that refers to tables or views in schemas of different versions. Effect. The request fails. Recovery. Ensure that the affected schemas have the same version. SQL 25210 25210 Schema schema has schema version version1; node does not support schema version lower than version2.
Versioning and Distribution Messages (25000 through 25399) Cause. The affected node runs a General Availability (GA) release of SQL/MX and is incompatible with the database objects created by a non-GA version. Effect. The request fails. Recovery. Migrate the node to a SQL/MX version that has an MXV that is compatible with the affected schema version.
Versioning and Distribution Messages (25000 through 25399) SQL 25214 25214 The system schema on node1 has system schema version version1. The local SQL/MX software version (MXV) can access only system schemas of version MXV1. Where node1 is the node whose system schema is accessed. Where version1 is the schema version of the system schema on node1. Where MXV1 is the MXV of the node that executes the query. Cause.
Versioning and Distribution Messages (25000 through 25399) Where MXV1 is the MXV of the node that executes the query. Cause. The accessing node runs a non-GA version of SQL/MX and is compatible only with schemas created by its own version. Effect. The operation fails. Recovery. Upgrade or downgrade the accessing node to an SQL/MX release that is compatible with the affected schema’s version.
Versioning and Distribution Messages (25000 through 25399) SQL 25220 25220 Schema schema cannot be created with a version lower than version. Where schema is the fully qualified ANSI name of the target of a CREATE SCHEMA command. Where version is the local system schema version. Cause. The CREATE_DEFINITION_SCHEMA_VERSION CQD is set to a schema version that is lower than the local system schema version. This setting is not permitted for CREATE SCHEMA. Effect. The operation fails. Recovery.
Versioning and Distribution Messages (25000 through 25399) Cause. A CREATE SCHEMA command created a schema with a value that is not a valid schema version. Effect. The operation fails. Recovery. Use a valid schema version value for the CREATE_DEFINITION_SCHEMA_VERSION CQD. For SQL/MX R3.0, these values are valid: 1200 and 3000. Or, allow the system to select the schema version: CONTROL QUERY DEFAULT CREATE_DEFINITION_SCHEMA_VERSION 'SYSTEM'.
Versioning and Distribution Messages (25000 through 25399) SQL 25251 25251 The operation operation involves node node which does not support schema versions lower than version. Where operation is the actual operation: UPGRADE or DOWNGRADE. Where node is the Expand node name of an involved node. Where version is the oldest supported schema version of the node. Cause.
Versioning and Distribution Messages (25000 through 25399) Where version1 is the schema version of schema prior to the DOWNGRADE operation. Where version2 is the target version of the DOWNGRADE operation. It is higher than version1. Cause. A DOWNGRADE operation affects a schema with a schema version that is lower than the target version of the operation. Effect. The operation fails. Recovery.
Versioning and Distribution Messages (25000 through 25399) SQL 25261 25261 The original operation operation is active and cannot be recovered. Where operation is the UPGRADE or DOWNGRADE operation that you specified. Cause. A RECOVER command was issued and the original UPGRADE or DOWNGRADE operation is still being actively processed. Effect. The RECOVER command fails. Recovery. Terminate the processing of the original command and then re-issue the RECOVER command.
Versioning and Distribution Messages (25000 through 25399) SQL 25264 25264 Definition schema schema cannot be dropped because user schemas of the same version exist in its catalog. Where schema is a definition schema name. Cause. You attempted to drop the definition schema but user schemas of the same version exists in the catalog. Effect. The operation fails. Recovery. This is an internal error. Contact your service provider. SQL 25265 25265 An internal error occurred during operation: text.
Versioning and Distribution Messages (25000 through 25399) SQL 25268 25268: The DOWNGRADE command cannot complete because the version of the system schema on remote_node is higher than 1200. Where remote_node is the Expand node name of a remote node that is related to the node where the DOWNGRADE command is executed. Cause.
Versioning and Distribution Messages (25000 through 25399) Recovery. Recompile the module with a supported version compiler. SQL 25301 25301 Module module has module version version1; the local node does not support module versions higher than version2. Where module is the name of the affected module. Where version1 is the module version of the affected module. Where version2 is the MXV of the local node. Cause. An attempt is made to load a module with a module version that is higher than the MXV. Effect.
Versioning and Distribution Messages (25000 through 25399) Where version2 is the MXV of the node that detects the incompatibility. Cause. You attempted to execute a query plan fragment with a plan version that is later than the MXV of the node that executes the plan or plan fragment. Effect. There are two possibilities: Automatic recompilation is attempted (if allowed) with a downrev compiler that produces plans with a plan version that is compatible with version2.
Versioning and Distribution Messages (25000 through 25399) SQL 25309 25309 MModule module can only be executed by a node with SQL/MX Software Version (MXV) version1, the MXV of node is MXV1. Where module is the name of the affected module. Where version1 is the module version of module. Where node is the node that attempts to load the module. Where MXV1 is the MXV of the affected node. Cause. The affected node runs a GA version of SQL/MX and is incompatible with a module generated by a non-GA version.
Versioning and Distribution Messages (25000 through 25399) Cause. The system module was manually renamed to indicate a version other than the actual version. Effect. The request fails. Recovery. Reinstall the system module. SQL 25312 25312 A version version1 compiler is required to compile the query. The current compiler version is version2. Where version1 is the required compiler version. Where version2 is the actual compiler version. Cause.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) Distribution Messages (25400-25499) SQL 25401 25401 Catalog catalog has not been registered on node node. Where catalog is the ANSI name of the target catalog. It must be visible on the local node. Where node is a remote node where catalog visibility is required. Cause. You attempted to access or create a database object in catalog catalog on node node, but catalog has not been registered on that node. Effect.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) Cause. You attempted to access catalog catalog on node node1, but an independent catalog with the same name already exists on that node. Effect. If the message is issued as an error, the operation fails. If the message is issued as a warning (accompanying warning 25406), a late name resolution or automatic recompilation is attempted. Recovery.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) Where node is the expand node name of a remote node where one or more partitions of object resided when the DML query was compiled. Cause. When the DML query was compiled, the affected database object had partitions on a remote node, and the database object’s catalog was visible on both the remote node and the local node. When the query was executed, the visibility of the object’s catalog changed.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) SQL 25421 25421 An automatic catalog reference for catalog already exists on node node. Where catalog is the ANSI name of the target catalog. Where node is a remote node where an automatic reference of the target catalog exists. Cause. The target node of a REPLICATE SCHEMA operation already has an automatic reference for the specified schema catalog. Effect. The operation fails. Recovery. None.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) SQL 25424 25424 A replica of schema schema already exists on node node. Where schema is the ANSI name of the affected schema. Where node is the remote node where a replica of the affected schema exists. Cause. The target node of a REPLICATE SCHEMA operation already has a replica of the affected schema. Effect. The operation fails. Recovery. None.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) SQL 25427 25427 Catalog catalog1 cannot be unregistered from node node because it is related to catalog2 which has a reference on the target node. Where catalog1 is the ANSI name of the target node for the UNREGISTER CATALOG command. Where node is the name of the target node for the UNREGISTER CATALOG command. Where catalog2 is the ANSI name of a catalog that is related to the target catalog. Cause.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) SQL 25429 25429.Catalog catalog cannot be unregistered from node node because it is the only catalog reference that has an automatic replication rule. Where catalog is the ANSI name of the target catalog for the UNREGISTER CATALOG command. Where node is the name of the target node for the UNREGISTER CATALOG command. Cause.
Versioning and Distribution Messages (25000 through 25399) JDBC Driver Error Messages (29000-29999) SQL 25490 25490 DDB Debug Warning: text. Where text is explanatory text for debugging purposes. Cause. A test condition was encountered by debug mode software. The explanatory text contains the details. Effect. The affected operation succeeds. Recovery. None. This message is issued as a warning.
20 Rowsets Messages (30000 through 30999) SQL 30001 30001 A rowset must be composed of host variable arrays. Cause. You attempted to create a rowset that is not composed of host variable arrays. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 30002 30002 The given rowset size (num1) must be smaller or equal to the smallest dimension (num2) of the arrays composing the rowset. Where num1 is the size of the rowset. Where num2 is the smallest dimension of the rowset arrays. Cause.
Rowsets Messages (30000 through 30999) SQL 30004 30004 The dimension of the arrays composing the rowset must be greater than zero. A value of num was given. Where num is the rowset size. Cause. You specified a value for rowset arrays that is invalid. It must be greater than zero. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 30005 30005 The dimensions of the arrays composing the rowset are different. The smallest dimension is assumed. Cause.
Rowsets Messages (30000 through 30999) SQL 30008 30008 Rowset index is out of range. Cause. NonStop SQL/MX received an internal error from a rowset. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 30009 30009 Trying to add more elements than maximum rowset size. Cause. NonStop SQL/MX received an internal error from a rowset. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 30010 30010 An internal error occurred. Rowset is corrupted. Cause.
Rowsets Messages (30000 through 30999) Recovery. Correct the syntax and resubmit. SQL 30013 30013 Host variable used to set input size of rowset has zero or negative value. Cause. You specified a hostvar with a zero or negative value for the input size of the rowset. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 30014 30014 Host variable used to set input size of rowset is not of type short, int, or long. Cause.
Rowsets Messages (30000 through 30999) SQL 30026 30026 NOT ATOMIC rowset INSERT is not supported on a table that has dependent indexes that are not offline. Dependent index index-name exists for table table-name. Where, index-name is the name of the dependent index. table-name is the name of the table containing the dependent index. Cause. You attempted to use NOT ATOMIC inserts on a table that has at least one dependent index.
Rowsets Messages (30000 through 30999) Cause. You attempted to use NOT ATOMIC inserts on a table that is the referencing table of referential integrity constraints. Effect. The operation fails. Recovery. Contact your service provider. SQL 30029 30029 NOT ATOMIC INSERT is not supported on a table that is the subject table of enabled AFTER triggers. Cause. You attempted to use NOT ATOMIC inserts on a table that is subject table of at least one enabled AFTER trigger. Effect. The operation fails. Recovery.
21 SQLSTATE Values Returned by NonStop SQL/MX NonStop SQL/MX returns SQLSTATE values that are defined in the ISO/ANSI SQL standard and implementation-defined SQLSTATE values. See Subclause 22, “Status Codes” in the ISO/ANSI SQL92 Standard “Database Language SQL.” SQLSTATE and SQLCODE Considerations Using SQLSTATE causes performance overhead because of the representation of SQLSTATE as five characters. The overhead is most noticeable with short SQL statements and in error situations.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values SQLSTATE Values For information about equivalent SQLCODE and SQLSTATE values for key messages returned by NonStop SQL/MX and NonStop SQL/MP, see the section “Error Codes” in the SQL/MX Comparison Guide for SQL/MP Users. Table 21-1 is a list of returned SQLSTATE values ordered by SQLSTATE. SQLSTATE values are provided for both warning messages (positive SQLCODE numbers) and error messages (negative SQLCODE numbers). Table 21-1.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 2 of 84) SQLSTATE SQLCODE Error Text 0150K 1020 Privilege settings on metadata tables cannot be changed. 0150L 1021 SQL is already initialized on system node-name. 0150M 1022 Schema schema-name already exists. 0150N 1023 Only the super ID can name an authorization ID other than the current user name. 0150O 1024 File system error error-number occurred on module textstring-1. text-string-2.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 3 of 84) SQLSTATE SQLCODE Error Text 0151E 1050 Cannot drop constraint used as a referenced object for a foreign key. 0151F 1051 Insufficient privilege on table name. 0151G 1052 Trying to drop a constraint that does not belong to requested table. 0151H 1053 Unique index table name could not be created because the column(s) specified contain duplicate data.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 4 of 84) SQLSTATE SQLCODE Error Text 0152D 1085 The calculated key length is greater than 255 bytes. 0152E 1086 Lock table name does not exist. 0152F 1087 Lock cannot be granted, conflicting operation is in progress. 0152G 1088 Cannot instantiate object table name, conflicting lock exists. 0152I 1090 Self-referencing constraints are currently not supported.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 5 of 84) SQLSTATE SQLCODE Error Text 0153D 1121 Attempting to perform a partition add, move, or drop on table name. Partition operations are not allowed on tables with vertical partitions, entry sequenced operations, and SYSKEYonly partitioned tables. 0153E 1122 The number of specified partition key values (name) for object name exceeds the number of key columns used, num.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 6 of 84) SQLSTATE SQLCODE Error Text 0153Z 1143 Validation for constraint name failed; incompatible data exists in referencing base table name and referenced base table name. To display the data violating the constraint, please use the following DML statement: text 01540 1144 Expected a quoted string in first key clause for column name on table name, value detected is (num).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 7 of 84) SQLSTATE SQLCODE Error Text 01600 2000 Error messages for compiler main, IPC, and DEFAULTS table; assertions for optimizer. 01601 2001 Error or warning num occurred while opening or reading from DEFAULTS table name. Using name values. 01602 2002 Internal error: cannot create MXCMP server. 01603 2003 Internal error: cannot establish connection with MXCMP server.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 8 of 84) SQLSTATE SQLCODE Error Text 0160P 2025 Unable to create server process name. CPU is unavailable; text. 0160R 2027 NonStop Kernel error num while sending a startup message to process name. 0160S 2028 Unable to create OSS server process name. Insufficient resources. 0160T 2029 Unable to create OSS server process name. OSS is not running.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 9 of 84) SQLSTATE SQLCODE Error Text 0161S 2064 Dynamic cursor name has already been defined in this module. The previous definition, as a dynamic cursor, is being retained and this latest one ignored. 0161T 2065 Statement name was not found in module name. 0161U 2066 Cursor name was not found in module name. 0161V 2067 Descriptor name has already been defined in this module.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 10 of 84) SQLSTATE SQLCODE Error Text 0162M 2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored. 0162N 2095 Module file name, expected to contain module name, instead contains name. 0162Q 2098 The name compilation completed with num warnings. 0162R 2099 The name compilation failed with num errors and num warnings.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 11 of 84) SQLSTATE SQLCODE Error Text 01705 3005 A DECLARE CURSOR statement cannot dynamically get its cursor name from a host variable while also statically declaring a cursor specification. A dynamic cursor requires the name of a previously prepared statement, or a host variable containing such a name; a static cursor requires a fixed, static name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 12 of 84) SQLSTATE SQLCODE Error Text 0170R 3027 name is not a valid simple name; it has more than one name part. 0170S 3028 Specifying a privilege column list in the INSERT clause is not yet supported. 0170T 3029 name is not yet supported in referential integrity constraint definition. 0170U 3030 The PARALLEL EXECUTION clause is not yet supported.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 13 of 84) SQLSTATE SQLCODE Error Text 0171H 3053 Duplicate PRIMARY KEY clauses in column definition name. 0171I 3054 The NOT DROPPABLE clause is allowed only in PRIMARY KEY and NOT NULL constraint definitions. 0171J 3055 Duplicate DELETE rules specified. 0171K 3056 Duplicate UPDATE rules specified. 0171L 3057 Invalid size value in the ALLOCATE clause.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 14 of 84) SQLSTATE SQLCODE Error Text 0172B 3083 Duplicate [NO]AUDITCOMPRESS clauses. 0172C 3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. 0172D 3085 Duplicate [NO]BUFFERED clauses. 0172E 3086 Duplicate [NO]CLEARONPURGE clauses. 0172F 3087 The [NO]COMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 15 of 84) SQLSTATE SQLCODE Error Text 01732 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. 01733 3111 The LIKE clause and LOCATION clause cannot coexist in the same statement. 01734 3112 The LIKE clause and PARTITION clause cannot coexist in the same statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 16 of 84) SQLSTATE SQLCODE Error Text 0173V 3139 A range-partitioned index requires a FIRST KEY clause. 0173W 3140 The isolation level cannot be READ UNCOMMITTED for an INSERT, UPDATE, DELETE, or DDL statement. 0173X 3141 The transaction access mode cannot be READ ONLY for an INSERT, UPDATE, DELETE, or DDL statement. 0173Y 3142 INTO clause host variables are not allowed in a static cursor.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 17 of 84) SQLSTATE SQLCODE Error Text 0174N 3167 Duplicate [ NOT ] DROPPABLE clauses. 0174O 3168 The FOR ... ACCESS clause is not allowed in a CREATE VIEW statement. 0174P 3169 name is not a known collation. 0174R 3171 Transaction statements are not allowed in compound statements. 0174S 3172 EXIT is not allowed in a compound statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 18 of 84) SQLSTATE SQLCODE Error Text 01801 4001 Column name is not found. Tables in scope: name. Default schema: name. 01802 4002 Column name is not found. Table name not exposed. Tables in scope: name. Default schema: name. 01803 4003 Column name is not a column in table name, or, after a NATURAL JOIN or JOIN USING, is no longer allowed to be specified with a table correlation name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 19 of 84) SQLSTATE SQLCODE Error Text 0180N 4023 The degree of each row value constructor (num) must equal the degree of the target table column list (num). 0180O 4024 Column name has no default value, so must be explicitly specified in the insert column list. 0180P 4025 Error while preparing constraint name on table name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 20 of 84) SQLSTATE SQLCODE Error Text 0181D 4049 A CASE expression cannot have a result data type of both type and type. 0181E 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation). 0181F 4051 The first operand of function name must be character. 0181G 4052 The second operand of function name must be numeric.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 21 of 84) SQLSTATE SQLCODE Error Text 01825 4077 Function name accepts only one or two operands. 01826 4078 Function name does not accept a weight operand. 01827 4079 The operands of function name must be numeric. 01828 4080 SQL/MP error: num num. 01829 4081 SQL/MP error: error 0182A 4082 Table name does not exist or is inaccessible. 0182B 4083 SQL/MP DDL operation failed.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 22 of 84) SQLSTATE SQLCODE Error Text 0182Z 4107 Column name has no default value, so DEFAULT cannot be specified. 01830 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. 01831 4109 Sequence functions placed incorrectly: name. 01832 4110 The query contains sequence functions but no SEQUENCE BY clause: name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 23 of 84) SQLSTATE SQLCODE Error Text 01846 4150 Primary key of table expression name must be used for join with embedded name expression. Tables in scope: name. 01847 4151 Stream access only supported on updateable views name. 01848 4152 Table name cannot be both read and updated. 01849 4153 Statement might not compile due to an order requirement on stream expression.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 24 of 84) SQLSTATE SQLCODE Error Text 0184U 4174 JOIN_ORDER_BY_USER prevented compiler from reordering query tree. 0184V 4175 Join between embedded name expression and embedded name expression not supported. Tables in scope: name. 0184W 4176 Join between stream expression and embedded name expression not supported. Tables in scope: name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 25 of 84) SQLSTATE SQLCODE Error Text 0185Z 4215 Stream access is not allowed on a nonaudited table. Table: name. 01860 4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded DELETE statement. 01861 4217 text 0188C 4300 Invalid usage of procedure procedure-name - A UDR was invoked within a trigger.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 26 of 84) SQLSTATE SQLCODE Error Text 01J03 7003 A plan using cluster sampling could not be produced for this query. 01K01 8001 Internal executor error. 01K02 8002 The current nowaited operation is not complete. 01K03 8003 The descriptor is locked by another nowaited operation. 01K04 8004 Trying to open a statement or cursor that is not in the closed state.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 27 of 84) SQLSTATE SQLCODE Error Text 01K3X 8141 An error was artificially injected, to test error handling. File name at line num. 01K8C 8300 Late name resolution failed. 01K8D 8301 Late name resolution failed. File system error num on file name. 01K8E 8302 Late name resolution failed. SQLCODE error num from name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 28 of 84) SQLSTATE SQLCODE Error Text 01KBW 8428 The argument to function name is not valid. 01KBX 8429 The preceding error actually occurred in function name. 01KFA 8550 Error num was returned by the Data Access Manager. 01KFB 8551 Error num was returned by the Distribution Service on name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 29 of 84) SQLSTATE SQLCODE Error Text 01KH2 8614 SQL cannot begin a transaction when multiple contexts exist. 01KJG 8700 An assertion failure or out-of-memory condition occurred during parallel execution. 01KJQ 8710 Error num returned by Measure when attempting to update SQL counters. 01KM9 8801 Trying to allocate a descriptor that already exists in the current context.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 30 of 84) SQLSTATE SQLCODE Error Text 01KMW 8824 The input module_id does not have a module name. 01KMX 8825 Module is already added into the current context. 01KMY 8826 Unable to add the module. 01KMZ 8827 Unable to send the request name. 01KN0 8828 Out of memory while creating the name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 31 of 84) SQLSTATE SQLCODE Error Text 01KNM 8850 The table specified in this cursor update or DELETE statement is different than the table specified in the declare cursor statement. 01KNN 8851 CLI Parameter bound check error. 01KNO 8852 Holdable cursors are only supported for streaming cursors and embedded UPDATE/DELETE cursors. 01KNP 8853 Invalid attribute definition.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 32 of 84) SQLSTATE SQLCODE Error Text 01KOJ 8883 The current context has violation checking functions disabled. Use SQL_EXEC_SetUdrAttributes_Internal() to enable it. 01KOK 8884 Prohibited SQL statement attempted. 01KOQ 8890 The SQL compiler failed to initialize properly. Query results might differ from what is expected, due to different compiler defaults.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 33 of 84) SQLSTATE SQLCODE Error Text 01L5Q 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. 01L5R 9207 You are not allowed to generate histogram statistics on an ISO88591 CHARACTER SET column which contains a null terminator character. You need to exclude this column from the column group list in UPDATE STATISTICS.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 35 of 84) SQLSTATE SQLCODE Error Text 01N5U 11210 Specified signature is invalid. Reason: Missing [ ] for OUT/INOUT parameter at position value. 01N5V 11211 Specified signature is invalid. Reason: Unknown parameter type used at position value. 01N5W 11212 Specified signature is invalid. Reason: Java signature size is more than supported. 01N5X 11213 Specified signature is invalid.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 36 of 84) SQLSTATE SQLCODE Error Text 01P06 13006 Switch has bad value, num, for its expression at line num in file name. 01P07 13007 Missing output file argument after the -c option. 01P08 13008 Missing module definition file argument after the -m option. 01P09 13009 Missing listing file argument after the -l option. 01P0A 13010 Missing timestamp argument after the -t option.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 37 of 84) SQLSTATE SQLCODE Error Text 01P0Z 13035 Invalid line number num for line pragma; ignoring the rest. 01P10 13036 C/C++ syntax error in switch/for/while condition near line num. 01P11 13037 Function header syntax error near line num. 01P12 13038 Array size num expected to be an unsigned integer near line num.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 38 of 84) SQLSTATE SQLCODE Error Text 01P1U 13066 Identifier name was expected to be a structure type near line num. 01P1V 13067 Unable to open source file name. 01P1W 13068 C/C++ syntax error near line num. 01P1X 13069 Missing module specification string argument after -g option.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 39 of 84) SQLSTATE SQLCODE Error Text 01PEA 13514 The CHARACTER SET attribute is not implemented in SQL/MX. 01PEB 13515 Picture name is not valid for a host variable. 01PEC 13516 Unexpected end of input file encountered after line num. 01PED 13517 Line num is too long to process and has been truncated. 01PEE 13518 Line num cannot be interpreted as a COBOL line type.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 40 of 84) SQLSTATE SQLCODE Error Text 01R0C 15012 File read error on the help file. 01R0D 15013 This command is not supported by the SQLCI OLE server. 01R0E 15014 Section name not found in file name. 01R0F 15015 PARAM name (value num) cannot be converted to type type. 01R0G 15016 PARAM name not found. 01R0H 15017 Statement name not found. 01R0I 15018 Break was received.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 41 of 84) SQLSTATE SQLCODE Error Text 01T31 20109 text 01U01 30001 A rowset must be composed of host variable arrays. 01U02 30002 The given rowset size (num) must be smaller or equal to the smallest dimension (num) of the arrays composing the rowset. 01U03 30003 Rowset size must be an integer host variable or constant.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 42 of 84) SQLSTATE SQLCODE Error Text 01Z8C 25300 Module module has module version version1; node node does not support module versions lower than version2. 01Z8D 25301 Module module has module version version1; the local node does not support module versions higher than version2.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 43 of 84) SQLSTATE SQLCODE Error Text 0A000 -1120 Attempting to change the audit flags for a table in an unsupported way. 0A000 -1121 Attempting to perform a partition add, move, or drop on table name. Partition operations are not allowed on tables with vertical partitions, entry sequenced operations, and SYSKEYonly partitioned tables. 0A000 -1126 Referential integrity is not yet supported.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 44 of 84) SQLSTATE SQLCODE Error Text 0A000 -3036 The SET CONSTRAINT clause in the ALTER TABLE statement is not yet supported. 0A000 -3070 The [NO]AUDIT clause is not supported. 0A000 -3080 The [NO]SERIALWRITES clause is not supported. 0A000 -3105 Currently only range, hash and system partitioning are supported. 0A000 -3119 The WITH LOCAL CHECK OPTION clause is not supported.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 45 of 84) SQLSTATE SQLCODE Error Text 22003 -8411 A numeric overflow occurred during an arithmetic computation or data conversion. 22007 -3045 Invalid date 'date'. 22007 -3046 Invalid time 'time'. 22007 -3047 Invalid timestamp 'timestamp'. 22007 -3158 Invalid DATETIME datetime. 22007 -8413 The string argument contains characters that cannot be converted.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 46 of 84) SQLSTATE SQLCODE Error Text 24000 -8013 Trying to update or delete from a cursor that is not in the fetched state. 24000 -8811 Trying to close a statement that is either not in the open state or has not reached EOF. 24000 -8812 Trying to execute a statement that is not in the closed state. 24000 -8813 Trying to fetch from a statement that is in the closed state.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 47 of 84) SQLSTATE SQLCODE Error Text 25000 -8844 A transaction started by SQL that was committed or aborted by user application from outside of SQL, has now been cleaned up. 26000 -15017 Statement name not found. 26000 -2065 Statement name was not found in module name. 26000 -8802 Trying to allocate a statement that already exists in the current context.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 48 of 84) SQLSTATE SQLCODE Error Text 40000 -8821 Rollback transaction failed during the process of fetching the statement. 40000 -8839 Transaction was aborted. 40003 -8608 Transaction subsystem name returned error num on rollback transaction. 40003 -8610 Transaction subsystem name reported error num on a waited rollback transaction. 42000 -1000 A syntax error occurred.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 49 of 84) SQLSTATE SQLCODE Error Text 42000 -15023 The USING list value num exceeds the SQLCI limit of num characters. 42000 -15024 The USING list quoted literal name must be followed by either a comma or a semicolon. 42000 -2050 name is not the name of any DEFAULTS table attribute. 42000 -2051 Invalid name option name or value 'num'. 42000 -2055 Invalid value 'num' for DEFAULTS attribute name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 50 of 84) SQLSTATE SQLCODE Error Text 42000 -2092 A module statement has already appeared in this file. The previous definition, name, is being retained and this latest one ignored. 42000 -2093 A module timestamp statement was not found in file name. 42000 -2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 51 of 84) SQLSTATE SQLCODE Error Text 42000 -3011 name is not a valid qualified name; it has more than 3 name parts. 42000 -3012 COUNT is the only aggregate function that accepts (*) as an operand. 42000 -3013 Subtraction is the only operation allowed in the parenthesized expression preceding an interval qualifier. 42000 -3014 Precision of numeric, value, cannot exceed 18.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 52 of 84) SQLSTATE SQLCODE Error Text 42000 -3052 Duplicate NOT NULL clauses in column definition name. 42000 -3053 Duplicate PRIMARY KEY clauses in column definition name. 42000 -3054 The NOT DROPPABLE clause is allowed only in PRIMARY KEY and NOT NULL constraint definitions. 42000 -3055 Duplicate DELETE rules specified. 42000 -3056 Duplicate UPDATE rules specified.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 53 of 84) SQLSTATE SQLCODE Error Text 42000 -3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. 42000 -3085 Duplicate [NO]BUFFERED clauses. 42000 -3086 Duplicate [NO]CLEARONPURGE clauses. 42000 -3087 The [NO]COMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 54 of 84) SQLSTATE SQLCODE Error Text 42000 -3111 The LIKE clause and LOCATION clause cannot coexist in the same statement. 42000 -3112 The LIKE clause and PARTITION clause cannot coexist in the same statement. 42000 -3113 Error in CONTROL statement: name 42000 -3115 Duplicate ISOLATION LEVEL clause specified. 42000 -3116 Duplicate transaction access mode clause specified.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 55 of 84) SQLSTATE SQLCODE Error Text 42000 -3150 Duplicate WITH HEADING phrases in LIKE clause in CREATE TABLE statement. 42000 -3151 Duplicate WITH HORIZONTAL PARTITIONS phrases in LIKE clause in CREATE TABLE statement. 42000 -3153 The FIRST KEY clause is not allowed with hash partitioning. 42000 -3155 The POPULATE and NO POPULATE clauses cannot coexist in the same CREATE INDEX statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 56 of 84) SQLSTATE SQLCODE Error Text 42000 -3181 Invalid logical name, a three part logical name is required. 42000 -3187 Not supported: SET STREAM TIMEOUT per a specific stream. 42000 -3189 cannot set lock timeout on a view. 42000 -4001 Column name is not found. Tables in scope: name. Default schema: name. 42000 -4002 Column name is not found. Table name not exposed. Tables in scope: name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 57 of 84) SQLSTATE SQLCODE Error Text 42000 -4016 The number of derived columns (num) must equal the degree of the derived table (num). 42000 -4017 Derived column name name was specified more than once. 42000 -4018 Rows cannot be deleted from an entry-sequenced table. 42000 -4019 The select list of a subquery in a select list must be scalar (degree of one).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 58 of 84) SQLSTATE SQLCODE Error Text 42000 -4042 The operands of a comparison predicate must be of equal degree. 42000 -4043 The operand of function name must be character. 42000 -4044 Collation name does not support the name predicate or function. 42000 -4045 The operand of function name must be numeric. 42000 -4046 The operands of function name must be exact numeric.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 59 of 84) SQLSTATE SQLCODE Error Text 42000 -4072 The operand of function name must be a datetime containing a name. 42000 -4073 The COLLATE clause might appear only after an expression of character data type, not type. 42000 -4076 Overflow in constant expression name. 42000 -4077 Function name accepts only one or two operands. 42000 -4078 Function name does not accept a weight operand.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 60 of 84) SQLSTATE SQLCODE Error Text 42000 -4109 Sequence functions placed incorrectly: name. 42000 -4110 The query contains sequence functions but no SEQUENCE BY clause: name. 42000 -4111 The query contains a SEQUENCE BY clause but no sequence functions. 42000 -4112 Absolute and relative sampling cannot occur in the same BALANCE expression.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 61 of 84) SQLSTATE SQLCODE Error Text 46007 -11208 Specified signature is invalid. Reason: The list of parameter types must be enclosed in parentheses. 46007 -11209 Specified signature is invalid. Reason: the number of parameters value must match the number of parameters in Java method. 46007 -11210 Specified signature is invalid. Reason: Missing [ ] for OUT/INOUT parameter at position value.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 62 of 84) SQLSTATE SQLCODE Error Text X010L -1021 SQL is already initialized on system name. X010M -1022 Schema name already exists. X010N -1023 Only the super ID user can name an authorization ID other than the current user name. X010O -1024 Distribution Service/Data Access Manager error num occurred in module name on line num. DETAILS(text). X010P -1025 Request failed.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 63 of 84) SQLSTATE SQLCODE Error Text X011G -1052 Trying to drop a constraint that does not belong to requested table. X011H -1053 Unique index name could not be created because the column(s) specified contain duplicate data. X011I -1054 Index name already exists. X011J -1055 Table, view, or stored procedure name already exists.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 64 of 84) SQLSTATE SQLCODE Error Text X012F -1087 Lock cannot be granted, conflicting operation is in progress. X012G -1088 Cannot instantiate object name, conflicting lock exists. X012M -1094 Unable to drop object name because it is not a name. X012N -1095 The partition by column name should also be part of the clustering/storage key.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 65 of 84) SQLSTATE SQLCODE Error Text X013O -1132 An added column cannot have both DEFAULT NULL and NOT NULL. X013P -1133 Only the super ID can perform this operation. X013Q -1134 Concurrent DDL operations are being performed on the given object. The current operation cannot be performed. X013R -1135 Clustering key column name must be assigned a NOT NULL NOT DROPPABLE constraint.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 66 of 84) SQLSTATE SQLCODE Error Text X015B -1191 Cannot find SQL/MP system catalog name, DEVICE_GETINFOBYLDEV error num. X015C -1192 Cannot find SQL/MP system catalog name, FILE_GETINFOBYNAME_ error num. X015G -1196 Unable to find SQL/MP system catalog name, invalid SQL/MP location name. X015H -1197 Invalid SQL/MP object name name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 67 of 84) SQLSTATE SQLCODE Error Text X020G -2016 Server process name was started but had undefined externals. X020H -2017 Unable to create server process name. No more processes (PCBs) available. X020I -2018 Unable to create server process name. Library conflict. X020J -2019 Unable to create server process name. Unable to allocate virtual memory. X020K -2020 Unable to create server process name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 68 of 84) SQLSTATE SQLCODE Error Text X022B -2083 Error num while naming or locating file name. X022C -2084 Error num while writing num bytes to file name. X022D -2085 Error num while closing file name. X022E -2086 Unable to purge the file name. This file contains the results of a failed compilation and should be purged.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 69 of 84) SQLSTATE SQLCODE Error Text X034I -3162 Procedure parameter name was not used. X034J -3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. X0352 -3182 Extra semicolon(;) in a compound statement. X0400 -4000 Internal error in the query binder. X0422 -4074 CONTROL QUERY successful. X042B -4083 SQL/MP DDL operation failed.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 70 of 84) SQLSTATE SQLCODE Error Text X044M -4166 ORDER BY clause not supported in UNION of two streams. Tables in scope: name, name. X044N -4167 Embedded name statements not supported in subqueries. X044O -4168 Stream expressions not supported in subqueries. X044P -4169 Embedded DELETE statements not allowed when using DECLARE ... FOR UPDATE clause.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 71 of 84) SQLSTATE SQLCODE Error Text X045Q -4206 Embedded name only supported for updateable views. View: name. X045R -4207 Index name and other indexes covering a subset of columns do not cover all output values of stream. X045S -4208 Index name and other indexes covering a subset of columns do not cover all columns referenced in where clause of stream.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 72 of 84) SQLSTATE SQLCODE Error Text X0600 -6000 Internal error in the query optimizer. X0602 -6002 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid values. If you have manually modified the metadata table, then you should undo your changes using the CLEAR option in UPDATE STATISTICS.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 73 of 84) SQLSTATE SQLCODE Error Text X08P6 -8906 An invalid or corrupt MXUDR reply could not be processed, possibly due to memory corruption in MXUDR while executing friendly user-defined routines or an internal error in SQL/MX. X082S -8100 Define name does not exist X08O4 -8868 Unable to create context when current transaction is implicitly started by SQL.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 74 of 84) SQLSTATE SQLCODE Error Text X08FC -8552 Error num was returned by the Distribution Service while fetching the version of the system name. X08FD -8553 Stream overflow; subscription rate has fallen too far behind publishing rate. X08FU -8570 Insufficient memory to build query. X08FV -8571 Insufficient memory to execute query.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 75 of 84) SQLSTATE SQLCODE Error Text X08N3 -8831 Either no current context or the module to which the statement belongs is not added to the current context. X08N6 -8834 Unable to find NonStop SQL installation directory. Operating system error num. X08N7 -8835 Invalid SQL descriptor information requested. X08N8 -8836 Invalid update column for cursor. X08N9 -8837 Invalid user id.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 76 of 84) SQLSTATE SQLCODE Error Text X08OX -8897 RPC exception in CLI request from non-trusted shadow client to trusted shadow server. X08OY -8898 Internal error in CLI. X095K -9200 UPDATE STATISTICS encountered an error from name. X095L -9201 Unable to DROP object name. X095M -9202 UPDATE STATISTICS has located previously generate histogram that are not being regenerated.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 78 of 84) SQLSTATE SQLCODE Error Text X0B5M -11202 Language Manager initialization failed. Details: Unable to initialize JVM. X0B5N -11203 The Language Manager failed to create its class loader, possibly due to corrupt LmClassLoader.class file. X0B5Q -11206 Java class class-file-name was not found in external path path-name. X0B5R -11207 Java class class-file-name failed to initialize.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 79 of 84) SQLSTATE SQLCODE Error Text X0D09 -13009 Language Manager encountered internal error string. X0D0A -13010 JVM raised an exception. Details: string. X0D0B -13011 Specified signature is invalid. Reason: The Java signature for a Java main method must be (java.lang.string[ ]). X0D0C -13012 All SQL parameters associated with a Java main method must have a parameter mode of IN.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 80 of 84) SQLSTATE SQLCODE Error Text X0D14 -13040 Expecting “)” near line num. X0D16 -13042 Unnamed declaration near line num. X0D17 -13043 Expecting name near line num. X0D18 -13044 Type specification type is not a recognized type near line num. X0D19 -13045 Unexpected class declaration near line num ignored. X0D1A -13046 Expecting “}” to end member declaration near line num.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 81 of 84) SQLSTATE SQLCODE Error Text X0D20 -13072 Module Version Specification String MVSS-string is not a Regular Identifier, or is longer than 31 characters. X0D21 -13073 Module name module-name is not a value OSS file name, or is longer than 128 characters. X0D22 -13074 One or more of the first three parts of the externally qualified module name module-name is longer than 128 characters.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 82 of 84) SQLSTATE SQLCODE Error Text X0DEI -13522 DECLARE SECTION cannot be nested. X0DEJ -13523 END DECLARE SECTION without a matching BEGIN DECLARE SECTION. X0DEK -13524 DECLARE SECTION encountered in unexpected program section. X0DEL -13525 Variable name might not be allocated correctly for a host variable. X0DEM -13526 Line num, name: name clause is not valid for a host variable.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 83 of 84) SQLSTATE SQLCODE Error Text X0F10 -15036 Invalid filecode OR invalid function argument X0FRR -15999 SQLCI internal error. X0G00 -16000 Error message file not found. X0G01 -16001 No message found for error or warning sqlcode. X0J00 -19000 Internal error in internal stored procedure processing. X0J01 -19001 Error in field description of internal stored procedure.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 84 of 84) SQLSTATE SQLCODE Error Text X0P8M -25310 Module module has module version version1, the local SQL/MX software version (MXV) can execute modules only with module version MXV1. X0P8N -25311 System module module has a wrong module version. The expected module version is version1. The actual module version is version2. X0U08 -30008 Internal error. Rowset index is out of range.
SQLSTATE Values Returned by NonStop SQL/MX HP NonStop SQL/MX Release 3.
A Non-SQLCODE Error Messages This appendix contains SQL/MX utility messages that do not have SQLCODE values. Each message is identified by the name of the script or utility, followed by a four-digit sequence, such as Install0001. InstallSqlmx script This subsection describes the informational messages that the InstallSqlmx script generates: Errors Install0001 through Install0011 are generated when the InstallSqlmx script sets up the anchor file.
Non-SQLCODE Error Messages InstallSqlmx script Install0003 Install0003: Multiple instances of metadata exist on this system. You cannot use the rebuild option. Cause. You attempted to use the Rebuild (-b) option while multiple instances of the system metadata exist on the system. Effect. The operation fails. Recovery. Multiple instances of system metadata are not allowed on the same system. Contact your service provider. Install0004 Install0004: SQL/MX is already installed in volume. Cause.
Non-SQLCODE Error Messages InstallSqlmx script Recovery. Remove duplicate entries for the Location (-l) option and retry the request. Install0007 Install0007: A volume name for the metadata must be specified along with the -l option. Cause. You did not specify a system metadata location. Effect. The operation fails. Recovery. Rerun the InstallSqlmx script and use the Location (-l) option to specify a volume name. Install0008 Install0008: The -nofcheck option must be specified after the -l option. Cause.
Non-SQLCODE Error Messages InstallSqlmx script Install0011 Install0011: Invalid character set specified with the -n option. Valid character sets are ISO88591,UCS2,KANJI or KSC5601. Cause. You specified an invalid character set. Effect. The operation fails. Recovery. Specify a valid character set and retry the request. Install0012 Install0012: The SQL/MX initialization failed. Check /usr/tandem/sqlmx/bin/initlog for details. Phase 3 failed. Cause. The initialization operation failed because of an error.
Non-SQLCODE Error Messages InstallSqlmx script Install0015 Install0015: Missing file: filename. Not all metadata tables and MXCS tables were created and initialized properly. Cause. The process of creating the metadata tables or MXCS tables has failed. Effect. The operation fails. Recovery. Check other errors that are returned to determine the cause of the failure. After the failure has been fixed, retry the request. Install0016 Install0016: Could not create directory-name directory. Cause.
Non-SQLCODE Error Messages Metadata Migration Utility Install0019 Install0019: File file-name was not found, but is present only if the DDL licensing product was not installed. If the DDL licensing product was installed, refer to the SQL/MX Messages Manual for recovery details. Cause. The SQL/MX file file-name is not present. Effect. The installation of NonStop SQL/MX continues. This warning can be ignored if the DDL licensing product (T0394) was not installed.
Non-SQLCODE Error Messages Metadata Migration Utility Recovery. Use the correct input command and resubmit. migr0003 migr0003: Invalid input command. When using PRELIMINARY_REPORT, it must be the only command chosen. Cause. PRELIMINARY_REPORT must be the only command specified. A SHOW or EXECUTE command cannot be performed at the same time as the PRELIMINARY_REPORT. Effect. The operation fails, and valid syntax options are displayed. Recovery. Use the correct input command and resubmit.
Non-SQLCODE Error Messages Metadata Migration Utility migr0007 migr0007: Incorrect version of SQL/MX is installed for migrate. Cause. NonStop SQL/MX is installed on the system, but it is the wrong version. Effect. The operation fails. Recovery. Install NonStop SQL/MX Release 2.x. migr0008 migr0008: Environment variable NSK_VOL or NSK_SUBVOL or SQLMX_NAMETYPE=NSK not specified prior to use of migrate utility. Cause. The environment variable is not present. Effect. The operation fails. Recovery.
Non-SQLCODE Error Messages Metadata Migration Utility migr0017 migr0017: SQL/MP system catalog does not contain MPALIAS. Cause. SQL/MP is installed, but it does not have an MPALIAS table. Effect. There are no MPALIAS entries to migrate. (Verify that this is correct.) Recovery. None. This message is a warning. migr0018 migr0018: SQL/MP system catalog does not contain DEFAULTS. Cause. SQL/MP is installed, but does not have a DEFAULTS table. Effect. There are no DEFAULTS entries to migrate.
Non-SQLCODE Error Messages Metadata Migration Utility migr0021 migr0021: The SCRIPT OSS-filename> option was chosen without the CLEAR and the specified OSS-filename> already exists. The filename has defaulted to script.out. Cause. A file name specified in the SCRIPT option already exists and CLEAR is not used. Effect. None. The file name defaults to script.out. Recovery. None. This message is a warning. migr0022 migr0022: The ERROR_LOG option was chosen without a specified filename.
Non-SQLCODE Error Messages MXGNAMES Utility migr0025 migr0025: SQL/MP system catalog does not contain ZONAM2ID, ZOAS2DS, ZODS, ZOENV and/or ZORES. Cause. SQL/MP is installed, but it does not have the correct ODBC tables. Effect. There are no ODBC entries to migrate. (Verify that this is correct.) Recovery. None. This message is a warning. MXGNAMES Utility This subsection describes the messages generated by the MXGNAMES utility.
Non-SQLCODE Error Messages MXGNAMES Utility MXGNAMES0002 MXGNAMES0002: File error: Output file already exists: filename. Cause. The output file you specified, or a continuation file whose name was automatically generated by MXGNAMES, already exists. Effect. The operation fails. Recovery. Make sure that explicitly named files, or potential continuation files, do not already exist. MXGNAMES0003 MXGNAMES0003: SQL error: Prepare statement error occurred: 15001. Cause.
Non-SQLCODE Error Messages MXGNAMES Utility MXGNAMES0004 MXGNAMES0004: Command line error: -node option required with -BR2. Cause. You specified the -BR2 output format but did not specify the -node option for the target node. Effect. The operation fails. Recovery. Add the -node option and resubmit. MXGNAMES0004 MXGNAMES0004: Command line error: option option can only be specified once. Cause. You specified a given option more than once. Effect. The operation fails. Recovery.
Non-SQLCODE Error Messages HP NonStop SQL/MX Release 3.
