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 Releases 2.0 and 2.1 Supported Release Version Updates (RVUs) This publication supports G06.23 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 524535-001 NonStop SQL/MX Release 1.8 November 2002 523730-001 NonStop SQL/MX Release 2.0 April 2004 523730-002 NonStop SQL/MX Release 2.0 August 2004 523730-003 NonStop SQL/MX Releases 2.0 and 2.1 June 2005 523730-004 NonStop SQL/MX Releases 2.0 and 2.
HP NonStop SQL/MX Messages Manual Tables What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Audience vii Related Documentation vii Notation Conventions xi 1.
2. General Messages (0 through 999) Contents 2. General Messages (0 through 999) 3. Privilege and Alias 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.
19. Rowsets Messages (30000 through 30999) Contents 19. Rowsets Messages (30000 through 30999) 20. SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE and SQLCODE Considerations SQLSTATE Values 20-1 20-1 A. Non-SQLCODE Error Messages InstallSQLmx script A-1 Metadata Migration Utility A-6 MXGNAMES Utility A-10 Tables Table 20-1.
Contents HP NonStop SQL/MX Messages Manual—523730-004 iv
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 Releases 2.0 and 2.1 Supported Release Version Updates (RVUs) This publication supports G06.23 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
What’s New in This Manual • • • • • • • Changes to the G06.27 Manual In Section 10, Executor Messages (8000 through 8999), added new and revised messages. In Section 12, Trigger, UDR Server, and Language Manager Messages (11000 through 11399), added new and revised messages. In Section 14, MXCI Messages (15000 through 15999), added new and revised messages. In Section 17, Utility Messages (20000 through 23099), added new and revised messages.
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 intended for NonStop SQL/MX database administrators and programmers who use the NonStop SQL/MX conversational or programmatic interface.
Related Documentation About This Manual Programming Manuals SQL/MX Programming Manual for C and COBOL Describes how to embed SQL/MX statements in ANSI C and COBOL programs. SQL/MX Programming Manual for Java Describes how to embed SQL/MX statements in Java programs according to the SQLJ standard. Specialized Guides SQL/MX Installation and Management Guide Describes how to plan for, install, create, and manage an SQL/MX database. Explains how to use installation and management commands and utilities.
Related Documentation About This 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. Visual Query Planner Help Context-sensitive help topics that describe how to use the Visual Query Planner graphical user interface. The NSM/web and Visual Query Planner help systems are accessible from their respective applications.
Related Documentation About This Manual This figure shows the manuals in the SQL/MX library: Programming Manuals Introductory Guides SQL/MX Comparison Guide for SQL/MP Users SQL/MX Quick Start SQL/MX Programming Manual for C and COBOL SQL/MX Programming Manual for Java Reference Manuals SQL/MX Reference Manual SQL/MX Messages Manual SQL/MX Glossary SQL/MX Connectivity Service Administrative Command Reference DataLoader/MX Reference Manual Specialized Guides SQL/MX Installation and Management G
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.
Change Bar Notation About This Manual HP NonStop SQL/MX Messages Manual—523730-004 xiv
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 • • Look up a message by its SQLCODE. Display information for a message, including its SQLCODE, the SQLSTATE values for the SQLCODE, and the message text. For further information about the ERROR command, see the SQL/MX Reference Manual. For detailed cause, effect, and recovery information for error messages, refer to 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 Messages Manual—523730-004 2 -2
3 Privilege and Alias 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.
Privilege and Alias Messages (1000 through 1999) Effect. The operation fails. Recovery. Check that a schema named schema does exist and resubmit. SQL 1004 1004 Table, view, or stored procedure object-name does not exist or object type is invalid for the current operation. Where object-name is the name of an SQL/MX object. Cause. You attempted an operation on an object that does not exist. Effect. The operation fails. Recovery. Check that an object named object-name does exist.
Privilege and Alias Messages (1000 through 1999) SQL 1008 1008 User name user-name does not exist. Where user-name is a Guardian user name. Cause. The user name specified in a GRANT or REVOKE statement, or the authorization ID in a CREATE SCHEMA statement, does not represent a valid Guardian user. Effect. The operation fails. Recovery. Correct the user name and resubmit. SQL 1009 1009 Column column-name does not exist in the specified table. Where column-name is an SQL identifier. Cause.
Privilege and Alias Messages (1000 through 1999) SQL 1013 1013 Not all privileges were granted. You lack grant option on some of the specified privileges. Cause. You attempted to grant privileges, but you do not have grant options for at least one of them. Effect. SQL/MX granted some privileges, but not all that you attempted to grant. Recovery. You must have grant options for privileges to grant them. SQL 1014 1014 Privileges were not revoked. Dependent privilege descriptors still exist. Cause.
Privilege and Alias Messages (1000 through 1999) Recovery. Correct the syntax and resubmit. SQL 1017 1017 You are not authorized to perform this operation. Cause. You attempted a replication operation without proper authorization. Effect. The operation fails. Recovery. In a replication context: Only the catalog owner and the local super ID can perform a replication operation for a catalog and for multiple schemas in a single catalog.
Privilege and Alias Messages (1000 through 1999) Recovery. None needed if SQL is operating normally. SQL 1022 1022 Schema schema-name already exists. Where schema-name is the name of an SQL/MX schema. Cause. You attempted to create a schema in a catalog that already contains a schema with that name. Effect. The operation fails. Recovery. If you did not use a fully qualified name, check that the default generates the correct catalog name. Retry the request, specifying a schema that does not already exist.
Privilege and Alias Messages (1000 through 1999) SQL 1025 1025 Request failed. One or more dependent objects exist. Cause. This error can occur when you drop a constraint, index, or table. These objects cannot be dropped if they have dependent objects and the drop-behavior is RESTRICT. Effect. SQL/MX does not perform the operation. Recovery. For DROP statements that support the CASCADE drop-behavior, you can reissue the statement specifying CASCADE.
Privilege and Alias Messages (1000 through 1999) Effect. The schema is not dropped. Recovery. Either drop all the objects in schema-name and resubmit the statement, or resubmit the drop statement using the CASCADE option. SQL 1029 1029 Object object-name could not be created. Where object-name is the name supplied in a CREATE statement. Cause. This error can result from various CREATE statements. See the accompanying error messages to determine the cause. Effect. The object is not created. Recovery.
Privilege and Alias Messages (1000 through 1999) SQL 1034 1034 SQL/MX was not able to initialize. Cause. See the accompanying error message for the cause. Effect. The operation fails. Recovery. Apply the recovery of the accompanying error message SQL 1035 1035 Catalog catalog-name already exists. Where catalog-name is the name of an SQL/MX catalog. Cause. You attempted to create a catalog using the name of an already existing catalog. Effect. The operation fails. Recovery.
Privilege and Alias Messages (1000 through 1999) SQL 1038 1038 Not all user catalogs have been dropped from the system. Cause. You attempted to drop SQL while one or more user-created catalogs existed. Effect. The operation fails. Recovery. You must drop all user-created catalogs before dropping SQL. SQL 1039 1039 The DROP SQL statement could not be executed. Cause. See the accompanying error message for the cause. Effect. SQL/MX does not drop SQL. Recovery.
Privilege and Alias Messages (1000 through 1999) Recovery. Reissue the statement with NOT NULL specified for all columns that are in the PRIMARY KEY and UNIQUE constraints. SQL 1043 1043 Constraint constraint-name already exists. Where constraint-name is the name of a column constraint or table constraint. Cause. You assigned the same constraint name to two constraints on the same table. Constraint names must be unique among all the constraints for a table. Effect. The operation fails. Recovery.
Privilege and Alias 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.
Privilege and Alias 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.
Privilege and Alias 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.
Privilege and Alias 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.
Privilege and Alias Messages (1000 through 1999) 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. Effect. The operation fails. Recovery. None. SQL 1063 1063 Dropping metadata index index-name is not allowed. Where index-name is the name of an SQL/MX index. Cause.
Privilege and Alias Messages (1000 through 1999) 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. You attempted to create an index on a metadata table, which is not allowed. Effect. The operation fails. Recovery. None. SQL 1069 1069 Schema schema-name could not be dropped. Where schema-name is the name of an SQL/MX schema. Cause.
Privilege and Alias Messages (1000 through 1999) 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. SQL 1072 1072 Unique constraint constraint-name-1 is disabled, so foreign key constraint constraint-name-2 could not be created.
Privilege and Alias Messages (1000 through 1999) 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. Where table-name is the name of the metadata table. Where view-name is the name of a view. Cause. SQL/MX required metadata information about object view-name and was unable to find it in table-name. Effect. The operation fails. Recovery. None.
Privilege and Alias Messages (1000 through 1999) SQL 1080 1080 The create 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 SQL/MX of a column named SYSKEY to ensure uniqueness for the clustering key. Effect. The operation fails. Recovery. Remove duplicate column names and resubmit.
Privilege and Alias 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. Where column-name is the specified column.
Privilege and Alias Messages (1000 through 1999) 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. SQL 1088 1088 The system generated column SYSKEY must be specified last or not specified at all in the STORE BY column list. Cause.
Privilege and Alias Messages (1000 through 1999) 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. A DROP TABLE specified an object that is not a base table, or a DROP VIEW specified an object that is not a view, or a DROP PROCEDURE specified an object that is not a procedure. Effect. The operation fails.
Privilege and Alias 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. The operation fails.
Privilege and Alias Messages (1000 through 1999) 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. The operation fails. Recovery. None. Contact your service provider. SQL 1104 1104 Default value string is too long for column column-name.
Privilege and Alias Messages (1000 through 1999) 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. SQL 1108 1108 The number of columns specified in the view column list, view-col-num, does not match the degree of the query expression, query-col-num. Where view-col-num is the number of columns in the view column list.
Privilege and Alias Messages (1000 through 1999) Effect. The operation fails. Recovery. Determine why the transaction failed and resubmit. SQL 1112 1112 An index column list cannot consist only of the systemgenerated column SYSKEY. Cause. The column list specified in a CREATE INDEX statement consisted only of the system-generated column SYSKEY. Effect. The operation fails. Recovery. Change the column list to include additional columns and reissue the statement.
Privilege and Alias Messages (1000 through 1999) SQL 1116 1116 The current partitioning scheme requires a userspecified clustering key on object table-name. Where table-name is the name of the table. Cause. The partitioning scheme requires a user-specified clustering key. Effect. The operation fails. Recovery. Specify a clustering key, either through a PRIMARY KEY, STORE BY, or PARTITION BY clause. SQL 1117 1117 Dropping the only partition of an object is not allowed.
Privilege and Alias Messages (1000 through 1999) SQL 1120 1120 Use of float datatype is a partitioning key is not allowed. Cause. You attempted an operation on a partitionable table that has float datatype in the partitioning key. Effect. The operation fails. Recovery. Enable the default ALLOW_FLOAT_DATATYPES_IN_PARTITIONING_KEY via a control query default statement and retry the operation. SQL 1121 1121 Partitions cannot be added or dropped on table tablename.
Privilege and Alias Messages (1000 through 1999) SQL 1123 1123 Not all of the partition key values (key) for object object-name could be processed. Please verify that the correct key value data types were specified. Where key is a list of the partition key values. Where object-name is the name of the object. Cause. You attempted to access a table using a first key value that contains an element that is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Privilege and Alias Messages (1000 through 1999) 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. Please verify that the correct table was specified. Where table-name is the name of the table. Cause. You attempted to perform an operation that can be performed only on a base table, and the specified object is not a base table. Effect. The operation fails. Recovery.
Privilege and Alias Messages (1000 through 1999) 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. The operation fails. Recovery. Log on as the super ID and then resubmit. SQL 1134 1134 A concurrent utility or DDL is being performed on object object-name, its parent, or one of its dependencies.
Privilege and Alias Messages (1000 through 1999) 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. Change the ALTER TABLE statement to specify DROPPABLE for the primary key. SQL 1137 1137 An internal error occurred: invalid index status. Details: description.
Privilege and Alias Messages (1000 through 1999) Cause. You attempted to create a check constraint that references a systemgenerated column. The column named SYSKEY is often system-generated. Effect. The operation fails. Recovery. Modify the statement so that no check constraints reference any systemgenerated column and resubmit. SQL 1140 1140 Row-length actual-row-length exceeds the maximum allowed row-length of maximum-row-length for table table-name.
Privilege and Alias Messages (1000 through 1999) Recovery. None. Contact your service provider. SQL 1143 1143 Validation for constraint constraint-name failed; incompatible data exists in referencing base table referencing-table-name and referenced base table referencedtable-name. To display the data violating the constraint, please use the following DML statement: statement-text. Where constraint-name is the name of a column constraint or table constraint.
Privilege and Alias Messages (1000 through 1999) SQL 1145 1145 The catalog name catalog-name is reserved for SQL/MX matadata. Where catalog-name is the name of an SQL/MX catalog. Cause. SQL/MX reserves certain catalog names for its own use. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for reserved names. Change catalog-name to a name that is not reserved and resubmit. SQL 1146 1146 Object object-name could not be altered because it is not a object-type.
Privilege and Alias Messages (1000 through 1999) SQL 1148 1148 System-generated column column-name of base table tablename cannot appear in a referential integrity constraint definition. Where column-name is the SYSKEY column. Where table-name is the name of the table. Cause. You tried to create a referential constraint on a table column that is the SYSKEY, which is not supported. Effect. The operation fails. Recovery. Do not use the SYSKEY as part of the referenced key.
Privilege and Alias Messages (1000 through 1999) SQL 1151 1151 POS (Partition Overlay Support) was not applied as volume names could not be generated for the partitions. So a simple table table-name was created without partitions. 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.
Privilege and Alias Messages (1000 through 1999) SQL 1180 1180 The required subvolume name for locations in schema schema-name is subvol-name. Where schema-name is the schema in which the object is being created. Where subvol-name is the designated subvolume name for that schema. Cause. One or more LOCATION clauses in the CREATE or MODIFY statement contained a Guardian location whose subvolume did not match the designated subvolume for the schema in which the object was being created. Effect.
Privilege and Alias Messages (1000 through 1999) SQL 1183 1183 Error error was returned by the file system on metadata table ANSI name (file name Guardian name). Where error is the error returned. Where ANSI name is the metadata table. Where Guardian name is the name of the file. Cause. See the Guardian Procedure Errors and Messages Manual for a description of file system error error. Effect. The operation fails. Recovery.
Privilege and Alias Messages (1000 through 1999) SQL 1186 1186 Column column-name is of type column-data-type which is not compatible with the default value’s type, value-datatype. Where column-name is the name of the column that has an error. Where column-data-type is the data type of column-name Where value-data-type is the value specified as the default value for the column. Cause. The value specified as the default for the column is incompatible with the type of the column. Effect. The operation fails.
Privilege and Alias Messages (1000 through 1999) Recovery. None. You cannot define a referential constraint that creates a circular dependency. 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.
Privilege and Alias Messages (1000 through 1999) SQL 1196 1196 The SQL/MP system catalog catalog-name could not be found due to an invalid SQL/MP location name. Where catalog-name is the name of the SQL/MP system catalog. Cause. An invalid SQL/MP system catalog location was specified or defaulted to. Effect. The operation fails. Recovery. Specify a correct SQL/MP system catalog location, or set the Guardian default system and volume to valid values.
Privilege and Alias Messages (1000 through 1999) Recovery. Specify a Guardian file name for the SQL/MP database object. SQL 1224 1224 An invalid data type was specified for routine parameter parameter-name. Where parameter-name is the name of the parameter. Cause. You specified a data type for this routine parameter that is not supported. Effect. SQL/MX is unable to complete the operation. Recovery. Specify a different data type. SQL 1225 1225 Mixing EXECUTE with other privileges is not allowed. Cause.
Privilege and Alias Messages (1000 through 1999) Recovery. Fix the error conditions identified in messages preceding this message and reissue the CREATE PROCEDURE statement. SQL 1232 1232 A file error occurred when saving dropped table DDL for table table-name to oss-pathname. Where table-name is the table being dropped whose DDL was to be saved. Where oss-pathname is the HP NonStop Kernel Open System Services (OSS) pathname of the file to which the DDL was to be saved. Cause.
Privilege and Alias Messages (1000 through 1999) Recovery. None. SQL 1235 1235 An invalid combination of EXTENT sizes and MAXEXTENTS was specified for table or index table-name. Cause. A CREATE or ALTER statement specified an invalid combination of EXTENT sizes and MAXEXTENTS. Effect. The operation fails. 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.
Privilege and Alias Messages (1000 through 1999) SQL 1238 1238 The character set for TRIGGER text must be ISO88591. Cause. You specified a literal with a character set other than ISO88591 in the text of a create trigger statement. Effect. The operation fails. Recovery. Specify only ISO88591 literals in the command. SQL 1239 1239 The character set for string literals in VIEW text must be ISO88591. Cause.
Privilege and Alias Messages (1000 through 1999) SQL 1242 1242 The character set for string literals in CONSTRAINT must be ISO88591. Cause. You specified a literal with a character set other than ISO88591 in the text of a constraint. Effect. The operation fails. Recovery. Specify only ISO88591 literals in constraints. 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.
Privilege and Alias Messages (1000 through 1999) Cause. A utility command specified an invalid key value. Effect. The operation fails. Recovery. Specify valid key values and resubmit. 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.
Privilege and Alias Messages (1000 through 1999) Where lock-name is the ANSI name of the DDL lock object that is associated with the utility operation. Cause. You attempted to drop an object that a utility command is using. Effect. The operation fails. Recovery. Wait until the utility operation has finished, and then retry the DROP operation. SQL 1251 1251 The extra insignificant digits of default value value are truncated to match the scale of the data type of column column-name.
Privilege and Alias Messages (1000 through 1999) Recovery. Change your query so that both unique and primary constraints or multiple unique constraints are not specified on the same set of columns. SQL 1261 1261 Error error-number was returned by the SQL/MX CLI while processing the UDR_JAVA_OPTIONS setting jvm-startup-options. Where error-number is the SQLCODE value. Where jvm-startup-options is a set of Java Virtual Machine startup options, specified in the application’s UDR_JAVA_OPTIONS default setting.
Privilege and Alias Messages (1000 through 1999) SQL 1264 1264 Duplicate privileges are not allowed in a GRANT or REVOKE statement. Cause. You specified duplicate privileges in a GRANT or REVOKE statement. Effect. The operation fails. Recovery. Reissue the GRANT or REVOKE statement, specifying a single privilege or a list of distinct privileges. SQL 1265 1265 Duplicate grantees not allowed in a GRANT or REVOKE statement. Cause. You specified duplicate grantees in a GRANT or REVOKE statement. Effect.
Privilege and Alias Messages (1000 through 1999) SQL 1268 1268 Duplicate columns are not allowed in a GRANT or REVOKE statement. Cause. You specified duplicate column names with the update or references privilege in a GRANT or REVOKE statement. Effect. The operation fails. Recovery. Correct the GRANT or REVOKE statement by specifying a single column name or a list of distinct column names. SQL 1270 1270 ALLOCATE or DEALLOCATE failed for object object-name due to file error error-number.
Privilege and Alias Messages (1000 through 1999) SQL 1272 1272 The system is not licensed for use of SQL/MX format tables. Cause. The site has not purchased DDL Licensing. Effect. The operation fails. Recovery. Purchase DDL Licensing (product number T0394). SQL 1273 1273 The specified MAXEXTENTS value must be greater than the number of extents allocated. Cause. The value that you specified to change MAXEXTENTS is less than or equal to the allocated extents. Effect. The operation fails. Recovery.
Privilege and Alias Messages (1000 through 1999) Recovery. To drop the constraint, you must remove the UNIQUE constraint or add an additional NOT NULL constraint to the columns that contain UNIQUE constraints and only one NOT NULL constraint for that column. SQL 1300 1300 Catman generated unknown Exception for procedure procedure-name. Where procedure-name is the ANSI name of a stored procedure. Cause. An unanticipated error occurred while reading metadata for a stored procedure. Effect.
Privilege and Alias 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.
Privilege and Alias 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. In a CREATE SCHEMA command, you specified subvolume in the LOCATION clause; however, this subvolume is already being used as schema subvolume by schema.
Privilege and Alias 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 ZSD are reserved for SQL/MX metadata schemas. Effect. The operation fails. Recovery.
Privilege and Alias Messages (1000 through 1999) SQL 1500 1500 The CATSYS - CAT_REFERENCES system schema relationship for catalog catalog may 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.
Privilege and Alias Messages (1000 through 1999) SQL 1503 1503 The OBJECTS - PARTITIONS definition schema relationship for type object may 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. Retry the operation.
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. 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. 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) Where number-1 is the error number. Where number-2 is the TPCError. Where text is the error message text. Cause. SQL/MX was unable to create server process name because of the process control procedure error number it received. More information appears in detail text. Effect. The operation fails. Recovery. Use the process control procedure error to diagnose and correct the problem.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2015 2015 Server process name could not be created - CPU is unavailable (NonStop Kernel error number). Where name is the server process name. Where number is the error number. Cause. SQL/MX was unable to create server process name because the CPU is unavailable or does not exist. Effect. The operation fails. Recovery. Use the process control procedure error to diagnose and correct the problem.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2018 2018 Server process name could not be created - library conflict. Where name is the server process name. Cause. SQL/MX was unable to create server process name because of a library conflict. The process you are trying to create has a different library than the one that is already running. Effect. The operation fails. Recovery. Check your process configuration. SQL 2019 2019 Server process name could not be created - unable to allocate virtual memory.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2021 2021 System error number occurred in procedure name from process name. Where number is the error number. Where procedure name is the name of the procedure. Where process name is the server process name. Cause. SQL/MX received an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 2022 2022 System error number occurred in procedure name from process name, detail text. Where number is the error number.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2025 2025 Server process name could not be created - CPU is unavailable; process id. Where name is the server process name. Where process id identifies the process. Cause. SQL/MX was unable to create server process name because the CPU is unavailable or does not exist. Effect. The operation fails. Recovery. Check the configuration and the CPU status. Use the messages that accompany this one to diagnose and correct the problem.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2029 2029 The new min value is greater than the current max value number. Where number is the current maximal value. Cause. The new minimal value is greater than the current maximal value. Effect. The new minimal value is not set. Recovery. Specify a new minimal value that is less than the current maximal value or specify a new maximal value that is greater than the new minimal value. SQL 2030 2030 The new max value is less than the current min value number.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2034 2034 process id: NonStop Kernel error number while communicating with server process name. Where process id identifies the process. Where number is the error number. Where name is the name of the server process. Cause. The SQL/MX process id received process control procedure error number while communicating with server process name. Effect. The SQL/MX process is not able to communicate with the server process. Recovery.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2038 2038 Character set name is not supported for SQLCI attribute TERMINAL_CHARSET. Where name is the name of the character set. Cause. You specified a non-ISO88591 character set name. Effect. The operation fails. Recovery. Specify an ISO88591 character set name. SQL 2050 2050 attribute is not the name of any DEFAULTS table attribute. Where attribute is the attribute name you specified. Cause. If the SQLSTATE is 42000, this is an error.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. None. Report the entire message to your service provider. SQL 2053 2053 Optimizer pass two assertion failure (failure-text) in file file-name at line line-num. Cause. This is an informational message that is a result of the two-pass mechanism of the optimizer. The optimizer created a simple plan, and then while refining that plan, an internal error occurred, so the simple plan was not improved. The simple plan is still valid and will work. Effect.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2056 2056 The value must be a number in the range value. Cause. You specified a value outside of the allowed range value. Effect. The operation fails. Recovery. Enter a valid value and resubmit. SQL 2057 2057 The value must be a multiple of value. Cause. You specified an invalid value for an attribute. It must be a multiple of value. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2060 2060 Procedure name has already been defined in this module. The previous definition is being retained and this latest one ignored. Where name is the procedure name. Cause. You defined procedure name twice in this module. Effect. SQL/MX uses the first definition. Recovery. This is an informational message only; no corrective action is needed. SQL 2061 2061 Static cursor name has already been defined in this module.
SQL/MX MXCMP Messages (2000 through 2999) Effect. SQL/MX uses the first static cursor definition. Recovery. This is an informational message only; no corrective action is needed. SQL 2064 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. Where name is the cursor name. Cause. You defined the dynamic cursor name twice in this module. Effect. SQL/MX uses the first dynamic cursor definition. Recovery.
SQL/MX MXCMP Messages (2000 through 2999) 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. You defined the descriptor name twice in this module. Effect. SQL/MX uses the first definition. Recovery. Informational message only; no corrective action is needed.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Correct the syntax and resubmit. SQL 2071 2071 The name name has already been declared or defined in this module. The previous definition, as a definition type, is being retained and this latest one ignored. Where name is the name of the module. Where definition type is the previous definition Cause. You defined name twice in this module in which it was defined as a type definition type. Effect. SQL/MX uses the previous definition. Recovery.
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 2075 2075 The -a application name option is not allowed for system module compilation Cause. You specified mxcmp -a application name system-module-definition-file, which is not supported. Effect. The operation fails. Recovery.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2081 2081 Error number while opening file name for read. Where number is the error number. Where name is the name of the file. Cause. SQL/MX received error number while opening file name for read. Effect. SQL/MX does not open the file. Recovery. Use the error number to diagnose and correct the problem. SQL 2082 2082 Error number while opening file name for write. Where number is the error number. Where name is the name of the file. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2085 2085 Error number was returned when closing file name. Where number is the error number. Where name is the name of the file. Cause. SQL/MX received error number when closing file name. Effect. SQL/MX does not close the file. Recovery. Use the error number to diagnose and correct the problem. SQL 2086 2086 The file name could not be purged. This file contains the results of a failed compilation and should be purged. Where name is the name of the file.
SQL/MX MXCMP Messages (2000 through 2999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 2092 2092 A module statement has already appeared in this file. The previous definition, name, is being retained and this latest one ignored. Where name is the name of the file. Cause. You included more than one module statement. name will be used. Effect. SQL/MX ignores the second module statement. Recovery. Informational message only; no corrective action is needed.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2095 2095 Module file name1, expected to contain module name2, instead contains name3. Where name1, name2, and name3 are module file names. Cause. SQL/MX expected to find the first module name1, but instead found the second module name2, in file name3. Effect. Only the second module is compiled. Recovery. None. SQL 2096 2096 A source file statement has already appeared in this module. The previous source file is being retained and this latest one ignored.
SQL/MX MXCMP Messages (2000 through 2999) Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 2099 2099 The compilation type compilation failed with value errors and value warnings. Cause. compilation type failed with the number of errors and warnings given as value. Effect. Any statement with an error is not compiled. Recovery. If this is a warning, this is an informational message. Otherwise, correct the syntax and resubmit. SQL 2100 2100 Break was received.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Resubmit the query with MEDIUM optimization level. Precede the statement with: CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM'; SQL 2103 2103 This query could not be compiled for one/both of the following reasons: a) Use of 'MINIMUM' optimization level, or b) incompatible Control Query Shape specifications. Cause.
SQL/MX MXCMP Messages (2000 through 2999) Effect. SQL/MX is unable to process this query. Recovery. Correct the CONTROL QUERY SHAPE specification and resubmit. SQL 2106 2106 This statement could not be compiled since it is too long. Break up large statements into smaller pieces. Cause. SQL/MX was unable to compile this query because it is too long. Effect. SQL/MX is unable to process this query. Recovery. Try breaking the statement into smaller pieces. SQL 2107 2107 This statement could not be compiled.
SQL/MX MXCMP Messages (2000 through 2999) Effect. The operation fails. Recovery. None. SQL 2201 2201 SQL compilation return code is mxcmp non-zero exit code. Cause. You invoked mxCompileUserModule on an application file that has an embedded module definition. An SQL compilation of an embedded module definition resulted in an MXCMP nonzero exit code, indicating a warning or error. Effect. The operation fails. Recovery. Review the MXCMP warning or error message.
SQL/MX MXCMP Messages (2000 through 2999) 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). The SQL compilation of the named embedded module definition produced an MXCMP warning or error. Effect. The operation fails. Recovery. Review the MXCMP warning or error. Trace the diagnostic back to the source file of the named module.
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 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) SQL 2217 2217 Temporary file file name does not exist or is not readable. Where file name is the name of the requested file. Cause. You invoked mxCompileUserModule on an SQLJ JAR or profile file to SQL compile its module definitions. This command tried but failed to create a temporary file or the temporary file created is not readable. Effect. The operation fails. Recovery. This is an internal error. Contact your service provider.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2220 2220 mxcmp path (MXCMP environment variable) does not exist or is not executable. Where mxcmp path is the MXCMP environment variable. Cause. You set your MXCMP environment variable to point to your own MXCMP and invoked mxCompileUserModule on an application file to DSQL compile its module definitions. Your MXCMP is not executable. Effect. The operation fails. Recovery. Verify that your MXCMP exists and is executable and retry the command.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2223 2223 Application file file name does not exist or is not readable. Where file name is the name of the application file. Cause. You invoked mxCompileUserModule on the named application file, which does not exist or is not readable. Effect. The operation fails. Recovery. Verify the spelling of the application file name and retry the command. SQL 2224 2224 An error occurred while opening temporary file that has the names of modules to be extracted. Cause.
SQL/MX MXCMP Messages (2000 through 2999) closing the temporary file that has the file names of the extracted module definition files. Effect. The operation fails. Recovery. This is an internal error. Contact your service provider. SQL 2227 2227 An error occurred while creating the module definition file for profile name. Where name is the name of the profile. Cause. You invoked mxCompileUserModule on an SQLJ JAR or profile file to SQL compile its module definitions.
SQL/MX MXCMP Messages (2000 through 2999) Recovery. Invoke the SQL/MX customizer on the translated SQLJ file and retry the command. SQL 2230 2230 There is no module statement in profile name. Where name is the name of the profile. Cause. You invoked mxCompileUserModule on an SQLJ JAR or profile file that has no SQL/MX module directive. Effect. The operation fails. Recovery. This is an internal error. Contact your service provider. SQL 2231 2231 Internal error error code error string. Cause.
SQL/MX MXCMP Messages (2000 through 2999) SQL 2233 2233 Query involves remote node nodename that is currently down. Compiler encountered a file system error error-num. It may produce a plan that is suboptimal or of incompatible version. Where nodename is the name of the node such as \system.$data_volume.$data_subvolume on which the failure occurred. Where error-num is the file system error number. Cause. The nodename you specified is not available. Effect.
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) 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. Enter at least one nonblank character and resubmit.
Parser and Compilation Messages (3000 through 3999) 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. Name the cursor and statement with string host variables and resubmit. SQL 3008 3008 Precision of type UNSIGNED data type, value, cannot exceed 9.
Parser and Compilation Messages (3000 through 3999) 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. SQL 3012 3012 COUNT is the only aggregate function that accepts (*) as an operand. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3015 3015 Scale value cannot exceed precision value. Cause. You defined a scale value with greater precision than 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. You gave a decimal item, value, with precision greater than 18, which is not supported. Effect. The operation fails. Recovery.
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. 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. SQL/MX requires an unsigned number. Effect.
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. 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. 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) 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. SQL 3058 3058 The BLOCKSIZE value must be 4096. Cause. You defined a BLOCKSIZE with an invalid value. It must be 4096. Effect.
Parser and Compilation Messages (3000 through 3999) 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. You specified duplicate EXTENT/MAXEXTENTS clauses in the PARTITION clause. Effect. The operation fails. Recovery.
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. 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) 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. Correct the syntax and resubmit. SQL 3077 3077 The [NO]ICOMPRESS clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause. You specified an ALTER INDEX...
Parser and Compilation Messages (3000 through 3999) 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. Cause. You specified duplicate ALLOCATE clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3082 3082 Duplicate [NO]AUDIT clauses were specified. Cause.
Parser and Compilation Messages (3000 through 3999) 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. Correct the syntax and resubmit. SQL 3086 3086 Duplicate [NO]CLEARONPURGE clauses were specified. Cause. You specified duplicate [NO]CLEARONPURGE clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3089 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause. You specified an ALTER TABLE...ATTRIBUTE(S) statement that includes the [NO]ICOMPRESS clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3090 3090 Duplicate LOCKLENGTH clauses were specified. Cause. You specified a statement with duplicate LOCKLENGTH clauses. Effect. The operation fails.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3094 3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements. Cause. You specified a CREATE INDEX statement that includes the DEALLOCATE clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3095 3095 Duplicate [NO]ICOMPRESS clauses were specified. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3098 3098 Duplicate LOCATION clauses were specified. Cause. You specified a statement with duplicate LOCATION clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3099 3099 Duplicate FILE ATTRIBUTE(S) clauses were specified. Cause. You specified a statement with duplicate FILE ATTRIBUTE(S) clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) SQL 3103 3103 Duplicate PARTITION clauses were specified. Cause. You specified a statement with duplicate PARTITION clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3104 3104 Only the ADD option is allowed in a PARTITION clause in a CREATE TABLE statement. Cause. You specified a CREATE TABLE statement with incorrect syntax. Only the ADD option is supported in a PARTITION clause. Effect. The operation fails. Recovery.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3108 3108 The LIKE clause and STORE BY clause cannot coexist in the same statement. Cause. You specified a statement with both LIKE and STORE BY clauses, which is not supported. Effect. The operation fails. Recovery. Correct the statement to include one of these clauses. SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3112 3112 The LIKE clause and PARTITION clause cannot coexist in the same statement. Cause. You specified a statement with both LIKE and PARTITION clauses, which is not supported. Effect. The operation fails. Recovery. Correct the statement to include one of these clauses. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3116 3116 Duplicate transaction access mode clauses were specified. Cause. You specified a statement with duplicate access mode clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the syntax and resubmit. SQL 3121 3121 Partitioned entry-sequenced tables are not yet supported. Cause. You specified an SQL/MP partitioned entry-sequenced table, which is not supported. Effect. The operation fails. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3128 3128 object name is a reserved word. It must be delimited by double-quotes to be used as an identifier. Where object name is the identifier. Cause. You used an identifier that is a reserved word. You must put it between double quotes (") to use it as an identifier. Effect. The operation fails. Recovery. Enclose the identifier in double quotes or select another name that is not a reserved word.
Parser and Compilation Messages (3000 through 3999) SQL 3132 3132 The HEADING for column name exceeds the maximum size of 128 characters. Where name is the name of the column. Cause. You specified a heading for column name that exceeds the maximum size of 128 characters. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3133 3133 PERFORM is valid only in COBOL programs. Cause. You specified a PERFORM statement, which is supported only in COBOL programs. Effect.
Parser and Compilation Messages (3000 through 3999) SQL 3136 3136 Only LEFT, RIGHT, and FULL OUTER JOIN are valid in {oj ...} Cause. You attempted to perform an invalid outer join. Only LEFT, RIGHT, and FULL OUTER JOIN are supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3140 3140 The isolation level cannot be READ UNCOMMITTED for an INSERT, UPDATE, DELETE, or DDL statement. Cause. You attempted to perform an INSERT, UPDATE, DELETE, or DDL statement with a READ UNCOMMITTED isolation level, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3141 3141 The transaction access mode cannot be READ ONLY for an INSERT, UPDATE, DELETE, or DDL statement. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3145 3145 Positioned UPDATE or DELETE is allowed only in embedded SQL. Cause. You attempted to perform a positioned UPDATE or DELETE, which is supported only in embedded SQL/MX. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3147 3147 In an IN predicate whose right operand is a value list, the left operand must be scalar (degree of one). Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3150 3150 Duplicate WITH HEADING phrases were specified in LIKE clause in CREATE TABLE statement. Cause. The WITH HEADINGS 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 HEADINGS phrases. SQL 3151 3151 Duplicate WITH HORIZONTAL PARTITIONS phrases were specified in LIKE clause in CREATE TABLE statement. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3157 3157 A catalog name is required. Cause. You attempted to create a catalog without specifying a catalog name. Effect. The operation fails. Recovery. Specify a catalog name and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3160 3160 host variable was declared more than once in the procedure parameter list. Cause. You declared host variable more than once in the procedure parameter list. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3164 3164 There is a data type mismatch between output host variable and selected value. Cause. A data type mismatch occurred between the output host variable and the selected value in the statement you specified. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3165 3165 The precision or exponent value specified in value was less than the minimum allowed or greater than the maximum allowed. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3168 3168 The FOR ... ACCESS clause is not allowed in a CREATE VIEW statement. Cause. You specified a CREATE VIEW statement with the FOR ... ACCESS clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3173 3173 UPDATE STATISTICS is not allowed in a compound statement. Cause. You specified a compound statement that contains an UPDATE STATISTICS command. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3177 3177 Character set name requires an even number of characters in the length declaration of the data type. Where name is the name of the character set. Cause. You specified a character set with an odd number of characters in the length declaration of the data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3181 3181 Specified name is not a valid three part ANSI name. Cause. You specified an invalid logical name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3185 3185 SIGNAL parameter 3 must be of type string. Cause. You attempted a SIGNAL statement with a third parameter that is not a quoted string. Effect. The operation fails. Recovery. Specify a parameter that is a quoted string and resubmit. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3189 3189 Setting a lock timeout is not allowed on a view. Cause. You attempted to set a lock timeout on a view, which is not supported. Effect. The operation fails. Recovery. None. SQL 3192 3192 Union operands table1 and table2 have different access/lock modes. Cause. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3196 3196 Only one access clause for may be specified for a single table SELECT. Cause. You specified two or more table-level access 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. SQL 3197 3197 Only one lock clause may be specified for a single table SELECT. Cause.
Parser and Compilation Messages (3000 through 3999) Recovery. Correct the syntax and resubmit. SQL 3202 3202 PARAMETER STYLE clause is required. Cause. In the CREATE PROCEDURE statement, you omitted the mandatory PARAMETER STYLE clause. Effect. The operation fails. 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.
Parser and Compilation Messages (3000 through 3999) SQL 3206 3206 The name for an object of this type must be fully qualified, or set NAMETYPE ANSI. Cause. In the CREATE PROCEDURE statement, you specified a partially qualified name when NAMETYPE was not set to ANSI. Effect. The operation fails. Recovery. Set NAMETYPE ANSI or fully qualify the name. SQL 3207 3207 Value for DYNAMIC RESULT SETS must be zero. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3210 3210 Minimum length of LONGWVARCHAR is value. Cause. You attempted a CREATE TABLE table name (columnname longwvarchar(N)) where N < current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery. Increase the CREATE TABLE statement’s longwvarchar column width N or decrease the current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting and resubmit. SQL 3211 3211 Maximum length of LONG VARBINARY is value. Cause.
Parser and Compilation Messages (3000 through 3999) SQL 3214 3214 Minimum length of LONG VARCHAR is value. Cause. You attempted a CREATE TABLE table name (columnname long varchar(N) where N < current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery. Decrease the CREATE TABLE statement’s long varchar column width N or increase the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit. SQL 3215 3215 Computed LONG VARCHAR length len1 is below minimum len2. Cause.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. Recovery. Do not use KANJI or KSC5601 character expressions in these functions. 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.
Parser and Compilation Messages (3000 through 3999) Recovery. Reissue the command with a valid location name. 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.
Parser and Compilation Messages (3000 through 3999) Effect. The operation fails. 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) Recovery. Remove the logical partition name syntax from the LOCATION clause and resubmit. 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. SQL/MX does not support arbitrary unicode characters. Effect. The operation fails. Recovery. Remove non-ISO88591 characters and resubmit.
Parser and Compilation Messages (3000 through 3999) HP NonStop SQL/MX Messages Manual—523730-004 5- 54
6 Binder and Compilation Messages (4000 through 4999) SQL 4000 4000 Internal error in the query binder. Cause. SQL/MX received an internal error in the query binder. Effect. 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 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 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. 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) 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. Correct the syntax and resubmit. SQL 4031 4031 Column name has an unknown data type, type. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4034 4034 The operation (data type operation data type) operation is not allowed. Cause. You attempted to perform an arithmetic operation on a DATETIME field using other DATETIME or INTERVAL expressions that do not have identical start and end fields. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4035 4035 Type specification1 cannot be cast to type specification2. Cause.
Binder and Compilation Messages (4000 through 4999) 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. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4039 4039 Column name is of type specification1, incompatible with the value's type, specification2. Cause.
Binder and Compilation Messages (4000 through 4999) 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. Correct the syntax and resubmit. SQL 4043 4043 The operand of function name must be character. Cause. You specified an operand for function name that is not a character, which is required. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) 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. SQL 4047 4047 The operands of function name must have a scale of 0. Cause. You specified operands of function name that do not have a scale of zero (0), which is required. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) 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. You specified predicate name, whose operands are required to be character, with invalid operands. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4051 4051 The first operand of function name must be character. Cause.
Binder and Compilation Messages (4000 through 4999) 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. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4056 4056 Exposed name name appears more than once. Cause. You specified a statement with an exposed table name that appears more than once. For example: SELECT * FROM tblx, tblx; Effect.
Binder and Compilation Messages (4000 through 4999) 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. You attempted to read from and insert, update, or delete within the same table name1, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4061 4061 Rows cannot be inserted into, or updated in, an individual table partition. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4064 4064 The operands of function name must be compatible character data types (that is, of the same character set). Cause. You specified operands for function name with incompatible character data types. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4066 4066 The operands of a UNION must be of equal degree. Cause. You specified operands of a UNION statement that are not of equal degree, which is required. Effect.
Binder and Compilation Messages (4000 through 4999) 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. Correct the syntax and resubmit. SQL 4070 4070 The operand of function name must be exact numeric. Cause. You specified an invalid operand for function name. It must be type exact numeric. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4073 4073 The COLLATE clause may appear only after an expression of character data type, not data type. Cause. You specified the COLLATE clause after an expression that is not a character data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4074 4074 CONTROL QUERY successful. Cause. The CONTROL QUERY statement completed successfully. Effect. None. Recovery. Informational message only; no corrective action is needed.
Binder and Compilation Messages (4000 through 4999) 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. The first argument must be numeric. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4079 4079 The operands of function name must be numeric. Cause. You specified an invalid operand in function name. The operands must be numeric. Effect. The operation fails.
Binder and Compilation Messages (4000 through 4999) SQL 4082 4082 Table, view or stored procedure name does not exist or is inaccessible. Cause. You referred to table 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. SQL 4083 4083 SQL/MP DDL operation failed. Cause. The SQL/MP Data Definition Language (DDL) operation you performed has failed. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) 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. Define the environment variable and resubmit. SQL 4087 4087 Prototype value 'value' is not a valid qualified name. Cause. You specified a prototype value that is not a valid qualified name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) SQL 4093 4093 The number of output dynamic parameters (value1) must equal the number of selected values (value2). Cause. SQL/MX requires that the number of output dynamic parameters, value1, match the number of selected values, value2. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4094 4094 The number of output host variables (value1) must equal the number of selected values (value2). Cause.
Binder and Compilation Messages (4000 through 4999) 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. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4098 4098 A NULL operand is not allowed in operation name. Cause. You included a NULL operand in operation name, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Binder and Compilation Messages (4000 through 4999) 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. A syntax error has caused SQL/MX to treat object name as an ambiguous entity. Effect. The operation fails. Recovery. Check the syntax for a missing parenthesis and resubmit.
Binder and Compilation Messages (4000 through 4999) Effect. Nothing is selected. Recovery. Replace the double quotes with single quotes. SQL 4105 4105 Translation name is not recognized. Cause. SQL/MX does not recognize the translation name. Effect. SQL/MX is unable to compile the statement. Recovery. Use one of the supported translation names. SQL 4106 4106 The character set for the operand of function name1 must be name2. Cause.
Binder and Compilation Messages (4000 through 4999) Recovery. Reword the query so that the expression inside the other sequence function does not contain references to the THIS function. SQL 4109 4109 Sequence functions are placed incorrectly: name. Cause. You specified a query that includes a SEQUENCE BY clause that contains an illegally placed sequence function name.
Binder and Compilation Messages (4000 through 4999) To correct the query, add a SEQUENCE BY clause: >>select runningsum(a) from t1 sequence by b; SQL 4111 4111 The query contains a SEQUENCE BY clause but no sequence functions. Cause. You specified a query that contained a SEQUENCE BY clause but no sequence functions, which is not supported. The purpose of the SEQUENCE BY clause is to specify an ordering for computing one or more sequence functions.
Binder and Compilation Messages (4000 through 4999) SQL 4114 4114 An absolute sample size must have a scale of zero. Cause. You specified an absolute sample size with a scale greater than zero, which is not supported. Effect. SQL/MX is unable to prepare the query. Recovery. Correct the syntax and resubmit. SQL 4115 4115 The sample size must be less than or equal to the sample period. Cause. You specified a sample size that is greater than the sample period.
Binder and Compilation Messages (4000 through 4999) Recovery. An updatable cursor query should specify the target update column in the select list of the query. Use the FOR UPDATE OF clause only if the cursor query is updatable. This example of a nonupdatable cursor join query does not select the target of the update and receives an error: >>SELECT A.PROD_CODE FROM EXPRODPARAMS A, MSRATES B +>WHERE CASE WHEN B.UPDATE_FLAG IS NULL THEN B.UPDATE_FLAG END = 'N' 'N' ELSE +>AND A.ACC_TYPE = B.ACC_TYPE AND A.
Binder and Compilation Messages (4000 through 4999) This example of a nonupdatable cursor join query selects the target of the update correctly and receives an error: >>SELECT A.PROD_CODE, B.UPDATE_FLAG FROM EXPRODPARAMS A, MSRATES B +>WHERE CASE WHEN B.UPDATE_FLAG IS NULL THEN B.UPDATE_FLAG END = 'N' 'N' ELSE +>AND A.ACC_TYPE = B.ACC_TYPE AND A.PROD_CODE = B.PROD_CODE +>FOR UPDATE OF UPDATE_FLAG ; *** ERROR[4118] The cursor query expression is not updatable.
Binder and Compilation Messages (4000 through 4999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4123 4123 NULL cannot be cast to a NOT NULL data type. Cause. You attempted to cast NULL to a NOT NULL data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4124 4124 More than one table will be locked: name. Where name is the name of the table. Cause. SQL/MX is preparing to lock more than one table. Effect. None. Recovery.
Binder and Compilation Messages (4000 through 4999) Recovery. Correct the syntax and resubmit. SQL 4127 4127 Type name1 cannot be assigned to type name2. Cause. You attempted to perform an assignment but specified incompatible data types. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Binder and Compilation Messages (4000 through 4999) SQL 4133 4133 Both trim character and source have to be CHARACTER type. Cause. The type of the trim source and trim character is not CHARACTER. Effect. The operation fails. Recovery. Make sure the type of the source and trim character is CHARACTER. SQL 4134 4134 The operation (name) is not allowed. instead. Try UNION ALL Cause. You attempted to perform an operation that SQL/MX does not allow. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the WHERE clause to use the primary key of the table expression. SQL 4151 4151 Stream access is supported only on updatable views. View: table name. Cause. You attempted to access a nonupdateable view using stream access mode. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4152 4152 Table name cannot be both read and updated. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4156 4156 Inner relation of left join cannot be embedded command name. Tables in scope: name. Cause. You attempted to perform a left join using the result set of an embedded UPDATE or DELETE as the inner relation. Effect. The operation fails. Recovery. Modify the statement and resubmit. SQL 4157 4157 Inner relation of left join cannot be stream expression. Tables in scope: name. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4160 4160 Intersection between embedded name1 expression and embedded name2 expression is not supported. Tables in scope: name3, name4. Cause. You attempted to perform an intersection between two embedded expressions. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4161 4161 Union between embedded name1 expression and embedded name2 expression not supported. Tables in scope: name3, name4. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4164 4164 Outer relation of right join cannot be embedded name expression. Tables in scope: name. Cause. You attempted to perform a right join using an embedded expression as the outer relation. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4165 4165 Outer relation of right join cannot be stream expression. Tables in scope: name. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4168 4168 Stream expressions are not supported in subqueries. Cause. You attempted to perform a subquery that included a stream expression. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. 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.
Binder and Compilation Messages (4000 through 4999) SQL 4173 4173 Stream expression is not supported for top level UPDATE statements. Cause. You attempted to perform a top-level UPDATE statement that included a stream expression. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4174 4174 JOIN_ORDER_BY_USER prevented compiler from reordering query tree. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4177 4177 Update of name1 column name2 is not permitted on rollback. Cause. You attempted to update clustering key components or columns associated with referential integrity constraints during a rollback. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4178 4178 Update of variable length column name is not permitted on rollback. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4183 4183 Embedded DELETE statements are not allowed on referenced tables. Cause. You attempted to perform an embedded DELETE statement on a table with a referential constraint. Effect. The operation fails. Recovery. Modify the statement and resubmit. SQL 4184 4184 Columns that are part of a referential constraint cannot be updated using embedded UPDATE statements. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4202 4202 SEQUENCE BY is not supported for embedded name expressions. Cause. You attempted to perform an embedded expression that included SEQUENCE BY. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4203 4203 Insert/Update/Delete operation on non-audited table name requires index maintenance which may cause the index(es) to become corrupt.
Binder and Compilation Messages (4000 through 4999) Recovery. Modify the statement and resubmit. SQL 4205 4205 Embedded name1 is supported for only key-sequenced tables. Table: name2. Cause. You attempted to perform an embedded action that is supported only for key-sequenced tables. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4206 4206 Embedded name is supported only for updatable views. View: name2. Cause.
Binder and Compilation Messages (4000 through 4999) SQL 4209 4209 Update of nullable column name is not permitted on rollback. Cause. You attempted to perform a rollback that included an update of a nullable column. Effect. SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. 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.
Binder and Compilation Messages (4000 through 4999) SQL 4214 4214 The SET ON ROLLBACK clause is not allowed on a nonaudited table. Table: name. Cause. You attempted to use a SET ON ROLLBACK clause to update a column in a nonaudited table. Effect. The operation fails. Recovery. Change the table’s AUDIT attribute and resubmit. 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.
Binder and Compilation Messages (4000 through 4999) SQL 4303 4303 The supplied type for parameter value of routine routine-name was type-name1 which is not compatible with the expected type type-name2. Cause. In the SQL/MX statement being compiled, you attempted to invoke a stored procedure with a type of parameter that is incompatible with the formal type of the parameter. Effect. The SQL/MX statement is not compiled. Recovery. Supply the correct parameter and type and retry the compilation.
Binder and Compilation Messages (4000 through 4999) SQL 4306 4306 A CALL statement is not allowed within a compound statement. Cause. In the SQL/MX statement being compiled, a CALL statement was present within a BEGIN...END block. Effect. The SQL/MX statement is not compiled. Recovery. Remove the CALL statement from the compound statement and retry the compilation. SQL 4307 4307 Rowset parameters are not allowed in a CALL statement. Cause.
Binder and Compilation Messages (4000 through 4999) Effect. The SQL/MX statement is not compiled. Recovery. Migrate to an SQL/MX version that supports stored procedure result sets. SQL 4310 4310 USER(x) is currently supported only in the outermost SELECT list. For example, it cannot be part of the subquery. Cause. You tried to use the USER(x) function somewhere other than the outermost SELECT clause. This function is not yet fully supported. Effect. The operation fails. Recovery.
Binder and Compilation Messages (4000 through 4999) HP NonStop SQL/MX Messages Manual—523730-004 6- 50
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.
Normalizer Messages (5000 through 5999) HP NonStop SQL/MX Messages Manual—523730-004 7 -2
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, then you should undo your changes using the CLEAR option in UPDATE STATISTICS. Cause. You have manually modified the metadata table, and now it contains an invalid boundary value. Effect. SQL/MX is unable to complete compilation. Recovery.
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 Messages Manual—523730-004 9 -2
10 Executor Messages (8000 through 8999) SQL 8001 8001 An internal executor error occurred. Cause. 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. 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) 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. Cause.
Executor Messages (8000 through 8999) 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. Where table name2 is the name of the table. Cause.
Executor Messages (8000 through 8999) 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. SQL 8104 8104 The operation is prevented by the check on view name1 cascaded from the check option on name2. Where view name1 is the name of the view. Where name2 is the name of the table. Cause.
Executor Messages (8000 through 8999) 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. SQL 8141 8141 An error was artificially injected, to test error handling. File name at line number. Cause.
Executor Messages (8000 through 8999) 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. Where type is the type of the affected object, such as table. Where object is the fully qualified ANSI name of the affected object. Cause. Late name resolution could not resolve the ANSI name to an available partition. Effect.
Executor Messages (8000 through 8999) Recovery. Determine why the two character types have different character sets and make them agree (for example, properly declare the character set of the host variable or use the SQL function TRANSLATE). SQL 8400 8400 Define name1 should have a name2 class attribute. Cause. The CLASS attribute of the DEFINE is not correct. For example, the CLASS attribute for an MP table name DEFINE should be MAP, not SORT. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8403 8403 The length argument of function SUBSTRING cannot be less than zero or greater than source string length. Cause. You specified a SUBSTRING function with an invalid length argument: less than zero or greater than the source string length. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8404 8404 The trim character argument of function TRIM must be one character in length. Cause.
Executor Messages (8000 through 8999) SQL 8409 8409 The escape character argument of a LIKE predicate must be one character in length. Cause. You specified a LIKE predicate with an invalid escape character argument, which must be one character in length. Effect. The operation fails. Recovery. Check your input data and resubmit. SQL 8410 8410 An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character. Cause.
Executor Messages (8000 through 8999) SQL 8413 8413 The string argument contains characters that cannot be converted. Cause. You provided a string argument for conversion that contains characters that cannot be converted. Effect. The operation fails. Recovery. Check your input data and resubmit. SQL 8414 8414 The attempted conversion is not supported on this platform. Cause. You attempted to perform a conversion that is not supported on this platform. Effect. The operation fails. Recovery. None.
Executor Messages (8000 through 8999) SQL 8417 8417 An error occurred during the evaluation of a USER function. Cause. SQL/MX has received an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8418 8418 The USER function is not supported on this platform. Cause. You attempted to perform the USER function, which is not supported on this platform. Effect. The operation fails. Recovery. None. SQL 8419 8419 An arithmetic expression attempted a division by zero.
Executor Messages (8000 through 8999) Recovery. Correct the syntax and resubmit. SQL 8422 8422 The provided INTERVAL is not valid and cannot be converted. Cause. You provided an INTERVAL that is not valid and that could not be converted. Effect. The operation fails. Recovery. Check your input and resubmit. SQL 8423 8423 The provided field number is not valid. Cause. You specified a field number that is not valid. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) SQL 8427 8427 detail text Cause. A sort error occurred. The error returned appears as detail text. Effect. The operation fails. Recovery. Use the information in the sort error to diagnose and correct the problem. SQL 8428 8428 The argument to function name is not valid. Where name is the name of the function. Cause. You specified an invalid argument for the function name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) SQL 8551 8551 Error NSK err was returned by the file system on objectname. Where NSK err is the HP NonStop Kernel error returned. Where object-name is the name of the object. Cause. The file system returned error NSK err on object-name. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 8552 8552 Error num was returned by the file system while fetching the version of the system name.
Executor Messages (8000 through 8999) Effect. The operation fails. An EMS event message for event number 5127 from the Disk subsystem has been generated to supply further diagnostic information. See the Operator Messages Manual for information on retrieving EMS event messages. Recovery. None. Contact your service provider. SQL 8570 8570 SQL/MX could not allocate sufficient memory to build query. Cause. The system does not have enough memory to build the query. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) Cause. You attempted to perform an operation on object name, for which you do not have a sufficient privilege level. Effect. The operation fails. Recovery. None. Have the system administrator change your privilege level, if appropriate. SQL 8574 8574 An OPEN was blown away on table name. Where name is the name of the table. Cause. While you had table name open, another operation such as DDL changed that table. Effect. The table is no longer open.
Executor Messages (8000 through 8999) Cause. SQL/MX could not find the object name. Effect. The operation fails. Recovery. Verify the location of the object and resubmit. SQL 8578 8578 Similarity check passed. Cause. The similarity check passed. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 8579 8579 Similarity check failed: name Cause. The similarity check failed. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) 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. The file system received process control procedure error number while performing a locking or unlocking operation. Effect. The operation fails. Recovery. Use the process control procedure error to diagnose and correct the problem.
Executor Messages (8000 through 8999) 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. SQL 8606 8606 Transaction subsystem name returned error number on a commit transaction. Where name is the name of the subsystem. Where number is the error number. Cause.
Executor Messages (8000 through 8999) 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. Correct the syntax so that the sequence of events is correct, and resubmit.
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 SQL/MX that SQL/MX could not commit or rollback. Effect. The operation fails. Recovery. The application that started the transaction must perform a commit or rollback. SQL/MX must start any transactions it will later commit or rollback. SQL 8614 8614 SQL cannot begin a transaction when multiple contexts exist. Cause.
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 8801 8801 Descriptor allocation failed because the descriptor already exists in the current context. Cause. This is an internal error.
Executor Messages (8000 through 8999) SQL 8804 8804 The provided input statement does not exist in the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8805 8805 Trying to action a descriptor that is not allocated with AllocDesc() call. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) Cause. SQL/MX has detected corrupted or invalid data in the module file name. Effect. SQL/MX could not execute the file. Recovery. Recompile the .mdf file, using the MXCMP compiler, to create a valid module file. See the subsection “Understanding and Avoiding Some Common Runtime Errors” in the SQL/MX Programming Manual for C and COBOL for more information. SQL 8809 8809 Open of the module file name failed with error number. Where name is the name of the file.
Executor Messages (8000 through 8999) SQL 8813 8813 Trying to fetch from a statement that is in the closed state. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8814 8814 The transaction mode at run time (value) differs from that specified at compile time (value). 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 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. The operation fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) 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. Effect. The operation fails. Recovery. None.
Executor Messages (8000 through 8999) 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. 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. SQL 8828 8828 Out-of-memory condition occurred while creating the name. Cause.
Executor Messages (8000 through 8999) 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. A transaction has not been started. Effect. The operation fails. Recovery. Verify that the transaction has been started or start it if it has not been.
Executor Messages (8000 through 8999) 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. Make sure the syntax is correct and that a valid descriptor item is being retrieved or set. SQL 8836 8836 Application specified an invalid update column for cursor. Cause. There is an error in the program that this code is embedded in.
Executor Messages (8000 through 8999) SQL 8839 8839 Transaction was aborted. Cause. A transaction failed during processing of an SQL/MX statement. SQL/MX might have aborted an AUTOCOMMIT transaction, or a transaction was aborted for some other reason (audit trail full, autoabort time limit reached, and so on). Effect. The operation fails. Recovery. Check the application event log for a detailed entry about this situation. SQL 8840 8840 Object name provided to CLI is not valid. Cause.
Executor Messages (8000 through 8999) SQL 8843 8843 Trying to retrieve an item, value, that is out of range. Where value is the entry number of the item. Cause. The item number of the requested descriptor item or the item number of the descriptor item being set is out of range. The value must be less than the maximum number of occurrences specified when the descriptor area was allocated. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8847 8847 An error occurred while trying to retrieve SQL/MP metadata information. Cause. SQL/MX received an error while trying to retrieve SQL/MP metadata information. Effect. The operation fails. Recovery. Use the errors that accompany this one to diagnose and correct the problem, and resubmit. SQL 8848 8848 Cancel on DDL statements or stored procedures is not supported. Cause.
Executor Messages (8000 through 8999) 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. SQL 8853 8853 Specified attribute definition is not valid. Cause. You specified an invalid attribute definition. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Executor Messages (8000 through 8999) 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. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8859 8859 There are pending insert, delete, or update operations. Cause. The current operation failed because there is a pending INSERT, DELETE, or UPDATE operation. Effect.
Executor Messages (8000 through 8999) 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. Rebuild the module file and resubmit. SQL 8863 8863 Module file name has an obsolete descriptor header. Where name is the file name. Cause. The module file name has an obsolete descriptor header. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) 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. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8867 8867 An error while reading from file name. Where name is the file name. Cause. SQL/MX encountered an error while reading the module file name. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) 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. The current operation fails. Recovery. None. Contact your service provider. SQL 8871 8871 The NOWAIT tag is not specified in the statement-id. Cause. A nowait tag was not specified. Effect. The operation fails. Recovery. None. Contact your service provider.
Executor Messages (8000 through 8999) 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. SQL 8880 8880 CLI applications are not allowed to remove the current context. Cause. A CLI application attempted to delete the current CLI context. Effect. The context is not removed. Recovery. None. Contact your service provider.
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) SQL 8892 8892 Buffer to return SQL/MP metadata information is too small. Cause. The buffer where SQL/MP metadata will be returned is too small. Effect. The operation fails. Recovery. Define the buffer with a larger size and resubmit. SQL 8893 8893 The statement argument count does not match the descriptor entry count. Cause. You specified a statement whose argument count does not match the descriptor entry count. Effect. The operation fails. Recovery.
Executor Messages (8000 through 8999) SQL 8896 8896 The character set name1 of a host variable does not match name2 of the corresponding descriptor item (entry number). Cause. The character set of a character host variable does not match the descriptor item. Effect. The operation fails. Recovery. Change the character set declaration of the host variable so that the character set name matches the descriptor item.
Executor Messages (8000 through 8999) SQL 8902 8902 An internal error occurred: MXUDR returned a UDR handle that is not valid. Cause. The SQL/MX UDR server generated an improperly formatted identifier when SQL/MX was executing a stored procedure. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8903 8903 An attempt was made by SQL/MX to kill the MXUDR server for this statement (process name). PROCESS_STOP_ returned value.
Executor Messages (8000 through 8999) SQL 8905 8905 The user does not have privilege-type privilege on user-defined routine routine-name. Cause. You do not have the required EXECUTE privilege on a stored procedure. Effect. The operation fails. Recovery. You must have the stored procedure’s owner or another authorized user grant you the required EXECUTE privilege, and then resubmit.
11 UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) 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 and Executor Sort Messages (9200 through 10049) • 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. SQL/MX is unable to continue processing. Recovery. Correct the syntax and resubmit. SQL 9204 9204 Invalid option option specified. Value must be range.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) 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. 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.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) 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 and Executor Sort Messages (9200 through 10049) Executor Sort Messages 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. None. This is an internal error. Contact your service provider. SQL 10004 10004 Sort failed while generating intermediate runs with sort error value1 and system error value2. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages 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. See the Guardian Procedure Calls Reference Manual to diagnose and correct the problem, or contact your service provider. SQL 10008 10008 Invalid sort algorithm selected. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages SQL 10012 10012 Sort failed during overflow with an invalid block number: $0~int0. Cause. The caller specified a block number that is out of range. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 10013 10013 Sort could not find any appropriate disks for overflow. Cause. The available disks on the system are not suitable for scratch usage. Effect.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) 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. See the Guardian Procedure Calls Reference Manual to diagnose and correct the problem, or contact your service provider. SQL 10017 10017 Sort failed while calling DEVICE_GETINFOBYLDEV_ with error number. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages SQL 10020 10020 Sort failed while calling FILENAME_FINDFINISH_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. See the Guardian Procedure Calls Reference Manual to diagnose and correct the problem, or contact your service provider. SQL 10021 10021 Sort failed while calling FILE_GETINFOLISTBYNAME_ with error number. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages SQL 10024 10024 Sort failed while calling SETMODE_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. See the Guardian Procedure Calls Reference Manual to diagnose and correct the problem, or contact your service provider. SQL 10026 10026 I/O to a scratch file failed while calling AWAITIOX with error number. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages SQL 10029 10029 Sort failed while calling FILE_GETINFO_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. See the Guardian Procedure Calls Reference Manual to diagnose and correct the problem, or contact your service provider. SQL 10044 10044 IO to a scratch file did not complete and reported error number. Cause.
UPDATE STATISTICS and Executor Sort Messages (9200 through 10049) Executor Sort Messages SQL 10049 10049 The block number was not found in any scratch file. Cause. The I/O operation failed because an expected scratch file that was created was not found. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
12 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 trigger can only be created if you drop and re-create the subject table with a name that is less than 123 characters. SQL 11006 11006 Use of rowsets with statements involving triggers is not supported. Note. As of the ABU SPR, this message is no longer generated. Cause. Rowsets were used in a statement that is a trigger event. Effect. The operation fails Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. You cannot use the OLD transition variable with an INSERT trigger because there is no old image for a row to be inserted. SQL 11013 11013 A DELETE trigger cannot reference NEW values. Cause. You attempted to create a DELETE trigger specifying a NEW transition variable. Effect. The operation fails. Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Add a REFERENCING NEW clause to the CREATE TRIGGER statement and resubmit. SQL 11017 11017 The left hand side of a SET assignment must be qualified with the name of the NEW transition variable. Cause. You specified a SET operation as an action for your BEFORE trigger, but the SET assignment is to an identifier. Effect. The operation fails. Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Cause. You attempted an INSERT/UPDATE/DELETE from the transition table during the operation of a trigger. Transition tables are read-only. Effect. The operation fails. Recovery. Correct the create trigger statement and resubmit. SQL 11021 11021 The subject table name cannot be used in the REFERENCING clause. Cause. You attempted to use the subject table name as a transition variable name. Effect. The operation fails. Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11024 11024 Specifying the same name, var-name, for both OLD and NEW is not allowed. Where var-name is the name you are attempting to assign to OLD and NEW transition variables. Cause. You attempted to create a trigger with a clause using the same name for both the NEW and OLD transition variables. Effect. The operation fails. Recovery. Specify different names for the OLD and NEW transition variables and resubmit.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Drop all UPDATE triggers whose subject columns match those columns in the SET ON ROLLBACK clause of the SET ON ROLLBACK statement. Matching is satisfied if at least one of the columns updated by the SET ON ROLLBACK clause is the same as one of the subject columns of the trigger.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Cause. You attempted to change a column of a particular row from a particular table to two different values at two different instances. You have designed a set of triggers that can result in nondeterministic behavior. Effect. The operation fails. Recovery. None. Redesign the triggers in such a way that this condition is not raised.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11035 11035 Metadata tables cannot have triggers! Cause. You attempted to create a trigger on a metadata table. Effect. The operation fails. Recovery. None. SQL 11036 11036 No triggers are defined on table table-name. Where table-name is the name of the specified table. Cause. You attempted to “alter trigger enable/disable all of” on a table that does not have triggers. Effect. This is a warning only. The operation succeeds.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11041 11041 Temporary table could not be created! Check default partitions. Cause. You attempted to create a trigger and one or more of the following conditions are true: • • The primary key length of the temporary table (which needs to be created when the first trigger is created) is longer than the allowed maximum length. The length of the temporary table name is longer than the maximum allowed user table name length. Effect.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The request message is rejected, and the SQL/MX statement fails. Recovery. None. Contact your service provider. SQL 11103 11103 MXUDR: Invalid routine handle: string. Cause. The SQL/MX UDR server encountered an internal error. Either an SQL/MX language manager operation failed or an SQL/MX UDR server data structure was determined to be invalid. Effect. The request message is rejected, and the SQL/MX statement fails. Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The request message is rejected, and the SQL/MX statement fails. Recovery. Stop and start the client process to restart a new SQL/MX UDR server, and retry the stored procedure call. SQL 11110 11110 MXUDR: Unexpected error during message processing: string. Cause. The SQL/MX UDR server encountered an internal error. Details appear in the message text. Effect. The operation fails. Recovery. None. Contact your service provider.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Cause. Initialization of the language manager failed because a required Java class could not be loaded or because a required Java method was not found. Effect. The operation fails. Recovery. Check the installation of the HP NonStop Server for Java product and the SQL/MX language manager. Verify the existence of the specified class. Stop and restart the session, and retry the SQL/MX statement.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Determine if the Java class file specified in the CREATE PROCEDURE statement exists. Determine if the Java method exists in the class file. The method must have the attributes public and static and must return void. Correct the class file or the method and resubmit. SQL 11205 11205 Java class class-file-name was not found in external path path-name. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Recovery. Verify that the Java method exists in the class file and that it has the public and static attributes, and then retry the SQL/MX statement. Use the NonStop Server for Java javap utility to determine which methods exist in a given class file. If this is a CALL statement, determine if the class file was removed or modified after the stored procedure was created. If so, you might need to drop and re-create the stored procedure.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11211 11211 Specified signature is invalid. Reason: Unknown parameter type used at position value. Cause. In a CREATE PROCEDURE statement, an unknown or unsupported parameter type was used at the specified parameter position in the SQL parameter list or in the EXTERNAL NAME clause. Effect. The operation fails. Recovery. Correct the parameters in the parameter list or in the EXTERNAL NAME clause, and resubmit.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) Effect. The operation fails. Recovery. Correct the EXTERNAL NAME clause and resubmit. SQL 11215 11215 Java execution: Invalid null input value at parameter position value. Cause. A null value was supplied as input to a stored procedure in Java and the corresponding Java data type is a primitive type that does not support null values. Effect. The operation fails. Recovery.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11218 11218 A Java method completed with an uncaught Java exception. Details: string. Cause. During execution of a CALL statement, a Java exception was thrown. Effect. The operation fails. Recovery. Review the Java method. Determine whether it is appropriate in your application for this exception to be thrown or whether it should be caught and handled by your user-defined routine. Retry the SQL/MX statement.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11221 11221 Language Manager is out of memory string. Cause. The language manager could not acquire enough memory to complete its work on the SQL/MX statement. Effect. The operation fails. Recovery. Stop and restart the session and retry the SQL/MX statement. SQL 11222 11222 The operation failed because the Java Virtual Machine ran out of memory. Cause.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11225 11225 Specified signature is invalid. Reason: The Java signature for a Java main method must be (java.lang.string[]). Cause. In a CREATE PROCEDURE statement, an invalid Java signature was used in the EXTERNAL NAME clause. Effect. The operation fails. 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.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) SQL 11228 11228 Floating point conversion error detail text. Cause. An error occurred in the language manager while converting an input value from the TNS to IEEE floating point format, or while converting an output value from the IEEE to TNS floating point format. More information appears in detail text. If the SQLSTATE is X0B6C, this is an error. If the SQLSTATE is 01N6C, this is a warning. Effect.
Trigger, UDR Server, and Language Manager Messages (11000 through 11399) HP NonStop SQL/MX Messages Manual—523730-004 12 -22
13 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) 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. SQL 13009 13009 The listing file argument is missing after the -l option. Cause. You specified the -l option without giving the listing file argument, which is required. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) 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. Correct the option and resubmit. SQL 13013 13013 Help for SQLC and SQLCO is available by typing SQLC or SQLCO on the command line. Cause. You did not enter any options. Effect. None. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) 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. Select a descriptor name that does not duplicate the SQLC default name, and resubmit. SQL 13017 13017 Descriptor name is multiply defined. Cause. You defined descriptor name more than once. Effect.
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. 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) 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. The preprocessor ignores the UNSIGNED NUMERIC item. Recovery. Correct the precision of the item and resubmit.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13065 13065 End of file was found after syntax-item1 when syntaxitem2 was expected, near line number. Cause. The compiler found end-of-file specified after syntax-item1 when it was expecting syntax-item2 near line number. For example, when the preprocessor parses host variables in an EXEC SQL/MX statement, they must be preceded with a: (colon).
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13069 13069 Module specification string argument is missing after -g option. Cause. The option you specified was incomplete. The -g option, specified on the mxsqlc or mxsqlo command line, was not followed by any other command line argument. Effect. The option is incomplete, and mxsqlc or mxsqlo returns this error message. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13072 13072 Module Version Specification string MVSS-string is not a regular identifier, or is longer than 31 characters. Cause. The Module Version Specification String (MVSS) you specified is not a regular identifier or is longer than 31 characters. Effect. The embedded SQL source file is not successfully preprocessed or the SQLJ profile is not customized. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13075 13075 Externally qualified module name module-name cannot be longer than 248 characters. Cause. The length of the three-part externally qualified module name exceeds 248 characters. Effect. It is not possible to the use the three-part externally qualified module name to name the OSS file in which the module will be stored. Also, the embedded SQL source file is not successfully preprocessed or the Java Profile is not customized. Recovery.
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 13501 13501 Specified command option name is not valid. Cause. You specified an invalid command option name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13502 13502 Source file name must be specified. Cause. You did not enter the source file name, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13503 13503 Filename for command option name is missing. Cause.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Recovery. Check the file's location, name and security, verify that no other process has it open, and resubmit. Check that the source and output file names are not the same, so that the preprocessor will not overwrite the source file. SQL 13506 13506 COBOL output source file name cannot be opened. Cause. SQL/MX could not open the COBOL output source file name. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13509 13509 Expecting keyword1 after keyword2, found keyword3. Cause. You did not enter the keyword that SQL/MX was expecting. When the preprocessor encounters certain keywords, it expects them to be followed by other specific keywords.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13511 13511 End of input file was reached while processing EXEC SQL. Cause. SQL/MX reached the end of the input file while processing EXEC SQL. The preprocessor was looking for the termination of the EXEC SQL/MX statement and reached the end of the file before detecting the end of the statement. There can be mismatched quote marks or parentheses. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13515 13515 Picture clause is not valid for a host variable. Cause. You specified an invalid PICTURE clause for a host variable. The PICTURE clause must be one of: PIC[TURE] X (length) PICTURE [S] { 9(integer) [V9(scale)] | V9(scale) } [USAGE [IS]] DISPLAY [SIGN [IS] LEADING SEPARATE [CHARACTER]] PICTURE [S] { 9(integer) [V9(scale)] | V9(scale) } [USAGE [IS]] { COMP[UTATIONAL] | COMP-5 | BINARY } Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13519 13519 Line number contains an unterminated character literal. Cause. The text in line number contains an unterminated character literal. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13520 13520 Line number does not correctly continue a character literal. Cause. The text in line number does not correctly continue a character literal. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13523 13523 END DECLARE SECTION encountered without a matching BEGIN DECLARE SECTION. Cause. You specified an END DECLARE SECTION without a matching BEGIN DECLARE SECTION. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13524 13524 DECLARE SECTION encountered in unexpected program section. Cause. You specified the DECLARE SECTION in a section where SQLCO did not expect it. Effect. The operation fails. Recovery.
SQLC and SQLCO Preprocessor Messages (13000 through 13999) SQL 13527 13527 The first declaration in a SQL DECLARE SECTION must have level 01 or 77. Cause. You specified an incorrect SQL DECLARE SECTION. Its first declaration must be level 01 or 77. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13528 13528 Line number: Variable name is not alphabetic and cannot have a CHARACTER SET clause. Cause.
14 MXCI Messages (15000 through 15999) SQL 15001 15001 A syntax error occurred at or before: string Cause. You specified a syntax error near string. 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. SQL 15003 15003 An incomplete statement was found in input: detail text Cause.
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. SQL/MX received error number while reading from a file. The error number depends on the operating system. Effect.
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. 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) 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. If the name is missing, add it to the file and resubmit. SQL 15015 15015 PARAM name (value value) cannot be converted to type data type. Cause. You tried to convert parameter name to data type. Effect. The operation fails.
MXCI Messages (15000 through 15999) 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) 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. Run RECOVER on the object that was being operated on, to ensure that it is returned to a consistent state.
MXCI Messages (15000 through 15999) SQL 15033 15033 Break was received. Cause. Break was received. Effect. The operation fails. Recovery. Informational message only; no corrective action is needed. SQL 15034 15034 Specified LOG file name is not valid. Cause. You specified an invalid LOG file name Effect. The operation fails. Recovery. Correct the file name and resubmit. SQL 15035 15035 Permission denied to access this file. Cause. SQL/MX was unable to access the file. Effect. The operation fails.
MXCI Messages (15000 through 15999) Recovery. Commit or abort the transaction and retry the MODE command. SQL 15202 15202 LOWLAYER seq-nbr: string1. Where seq-nbr is the error sequence number for this event, starting at 1. A number greater than 1 is rare. Where string1 is an error message from a lower level, often the file system or SQL compiler. See the Guardian Procedure Errors and Messages Manual.
MXCI Messages (15000 through 15999) Effect. A lower-level error might have been lost unless the connection just failed. Recovery. See the first error message displayed for the event (primary message) to determine the problem and the recovery action. SQL 15206 15206 SUBSYSTEM: Bad return code int1, library call function-name failed. Where int1 is the value of the return code from the library call. This code is provided for problem analysis by support or development personnel.
MXCI Messages (15000 through 15999) Recovery. Obtain proper authorization from the ODBC administrator. Then enter the command. SQL 15215 15215 SUBSYSTEM: SERVICE name used cannot supply this info, library call function-name failed. +++SUGG: SERVICE name was probably * and should be a specific SERVICE name. Where function-name is the name of the library function called. Cause. The service name is an asterisk (*). Effect. The command and subsequent subsystem call fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15218 15218 SUBSYSTEM: SERVER out of memory space, library call function-name failed. Where function-name is the name of the library function called. Cause. Out of memory space. Effect. The command and subsequent subsystem call fails. Recovery. See the ODBC server documentation for handling server memory problems. SQL 15219 15219 SUBSYSTEM: SERVICE is not in started state, library call function-name failed. +++SUGG: Start SERVICE and retry command.
MXCI Messages (15000 through 15999) SQL 15221 15221 SUBSYSTEM: User input data problem, library call function-name failed. +++SUGG: Invalid environment variable definitions for example. Where function-name is the name of the library function called. Cause. An attribute value entered on the command line is not valid for the command you issued. Effect. The command and subsequent subsystem call fails. Recovery. Enter the command with the correct attribute value.
MXCI Messages (15000 through 15999) Note. As of the ABU SPR, this message is no longer generated. Cause. You inserted a semicolon or comma in the wrong place. Effect. The operation fails. Recovery. Enter the command again with the correct characters and syntax. SQL 15227 15227 Command was missing the object type. Cause. The command is missing the second of its two required parameters. Effect. The operation fails. Recovery. The command displays valid object types in a second message.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Enter the command with a semicolon or comma after the object name. SQL 15230 15230 Opening quote unmatched in the command, command had: string1. Where string1 is a portion of the input showing the start of the problem. Cause. A string with single or double quotation mark (SQL identifier or literal) is missing the terminating mark. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15233 15233 Keywords can not be quoted, command had: string0. Where string0 displays the start of the error. Cause. A keyword contains a quotation character. Effect. The operation fails. Recovery. Enter the command without quotation marks for the keyword. SQL 15234 15234 Opening quote was matched but following separator not correct, command had: string1. Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated.
MXCI Messages (15000 through 15999) Recovery. Enter the complete command, including the command name. SQL 15238 15238 Empty command attribute found (extra comma) just before: string0. Where string0 is the portion of the input following the problem. Cause. You entered an extra comma instead of a value. Effect. The operation fails. Recovery. Enter the value instead of a comma and resubmit. SQL 15240 15240 No attributes supported by this command, command had: string1 ....
MXCI Messages (15000 through 15999) Recovery. Correct the attribute and retry the command. SQL 15244 15244 Command has a duplicate attribute "attribute-name". +++SUGG: Remove the duplicate keyword (and value). Where attribute-name is the name of the duplicate attribute. Cause. A duplicate attribute is in the command. Effect. The operation fails. Recovery. Enter the command without the duplicate attributes. SQL 15245 15245 This command attribute never has a value, command had: string0 string1.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Enter the command with correct the attribute value. SQL 15248 15248 This command has a non-numeric character invalid-char in a numeric field, command had: string1. Where invalid-char is the invalid character. Where string1 is the name and value of the attribute. Cause. The attribute value is invalid. Effect. The operation fails. Recovery. Enter the command with the correct attribute value.
MXCI Messages (15000 through 15999) SQL 15256 15256 A user name must have two components: groupname.membername. Cause. The user name field does not contain both the group and member name. Effect. The operation fails. Effect. Enter the command with a group and member name. SQL 15257 15257 A component name may not contain wild cards * or ? within the name. The wild card * alone is often permitted.
MXCI Messages (15000 through 15999) Where string2 is the component with too many characters. Cause. Too many characters are in the component. Effect. The operation fails. Recovery. Enter the command with a reduced number of characters in the component specified in the error. 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.
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) 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. 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.
MXCI Messages (15000 through 15999) SQL 15274 15274 Attribute value too large, limit 9,223,372,036,854,775,807, command had: string1. Where string1 is the attribute name and value. Cause. The attribute value entered is greater than the maximum allowed value. Effect. The operation fails. Recovery. Enter the command with the attribute value smaller or equal to the maximum allowed value. SQL 15275 15275 Concatenating strings of different quote types is not permitted, command had: string1.
MXCI Messages (15000 through 15999) Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated. Cause. A | character follows a string within quotes. Effect. The operation fails. Recovery. Retry the command, either specifying a valid concatenation operator || or removing the invalid character. SQL 15278 15278 Leading spaces are not allowed in SQL identifiers, command had: ‘string1’. Where string1 is a portion of the input showing the start of the problem.
MXCI Messages (15000 through 15999) Recovery. Enter the command with the correct syntax and resubmit. SQL 15281 15281 No separator found after quote, command had: ‘string0’. Where string0 is the text causing the error. Cause. A quoted string must always be followed by a dot, comma, or semicolon. A dot must not be preceded by white space. Effect. The operation fails. Recovery. Enter the separator after the quote (a comma might be missing), and then enter the remaining attributes.
MXCI Messages (15000 through 15999) Recovery. Select a valid object type from the list as the object type for this command. SQL 15287 15287 USAGE: "DELETE" 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 DELETE command objects when mode macl is set. Recovery.
MXCI Messages (15000 through 15999) Effect. The operation fails. A preceding message states the problem, and this message lists valid STOP command objects when mode macl is set. Recovery. Select a valid object type from the list as the object type for this command. SQL 15291 15291 USAGE: "VERSION" command supports object type: SERVICE. Cause. The input line contains either no second parameter, or an invalid command and object pair. Effect. The operation fails.
MXCI Messages (15000 through 15999) Recovery. Enter the command using the correct syntax. SQL 15297 15297 USAGE: [[system.]service] are the name components for a SERVICE 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 15298 15298 USAGE: [[system.]groupname.
MXCI Messages (15000 through 15999) SQL 15305 15305 SUBSYSTEM: DS still in use somewhere, library call function-name failed. Where function-name is the client library function name. Cause. The DS is in an active state with a service. Effect. The operation fails. Recovery. Enter the STOP DS * command. Use the wild card * for the service name. SQL 15307 15307 SUBSYSTEM: DS already exists, library call function-name failed. Where function-name is the client library function name. Cause.
MXCI Messages (15000 through 15999) SQL 15310 15310 SUBSYSTEM: SQL error from LowLayer, library call function-name failed. Where function-name is the client library function name. Cause. An SQL failure occurs in a lower client library. Effect. The operation fails. Recovery. Retry the command using the correct syntax. SQL 15311 15311 SUBSYSTEM: Association server not available, library call function-name failed. Where function-name is the client library function name. Cause.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual. SQL 15314 15314 SUBSYSTEM: SERVER not found here, library call function-name failed. Where function-name is the client library function name. Cause. The server is not found on the system. 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.
MXCI Messages (15000 through 15999) Cause. The data source is not currently available to make any changes. Effect. The operation fails. Recovery. Wait for the data source to fully transition to a stable state, then enter the command. 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.
MXCI Messages (15000 through 15999) SQL 15321 15321 SUBSYSTEM: Error enabling/disabling trace, library call function-name failed. Where function-name is the client library function name. Cause. The client library fails to enable or disable tracing. Effect. The operation fails. Recovery. Check your MXCS service process (MXOAS). It might not be responding. SQL 15322 15322 SUBSYSTEM: Busy, try again, library call function-name failed. Where function-name is the client library function name. Cause.
MXCI Messages (15000 through 15999) SQL 15324 15324 SUBSYSTEM: Error in Configuration server, library call function-name failed. Where function-name is the client library function name. Cause. This error comes from the client library call CFGStartService(). Effect. The operation fails. Recovery. Run the INFO command on the service to determine what state it is in; then stop and start the service.
MXCI Messages (15000 through 15999) Recovery. Verify that the service exists by using the INFO SERVICE * command. Then retry the failed command. SQL 15328 15328 Could not get the status for SERVICE service-name. Where service-name is the name of the service where the operation is to be performed. Cause. The lower level cannot return status for the service. The system could be busy. Effect. The operation fails. Recovery. Use the INFO SERVICE command to verify that the specific service is still operational.
MXCI Messages (15000 through 15999) SQL 15331 15331 CFG Trace file name is too long. Should be limited to 30 char. Cause. The file name given for the trace file is to long. Effect. The operation fails. Recovery. Enter the command, specifying a shorter trace file name. 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.
MXCI Messages (15000 through 15999) SQL 15351 15351 SERVER name must be * if DS selection attribute is specified. Cause. Server name is other than an asterisk (*) wild card to specify the DS selection attribute. Effect. The operation fails. Recovery. Run the INFO SERVER command using the asterisk (*) wild card for the server name when specifying the DS attribute. SQL 15352 15352 Could not get list of SERVERs on the SERVICE servicename. +++SUGG: Use INFO SERVICE to see if it still exists.
MXCI Messages (15000 through 15999) SQL 15354 15354 Could not get list of DSs names on SERVICE servicename. Where service-name is the name of the service. Cause. The lower-level fails to return a list of data source names on the service. The system might be busy. Effect. The operation fails. Recovery. Run the INFO SERVICE * command to verify that the service exists, and then retry the failed command. See the lower-level error messages issued with this message.
MXCI Messages (15000 through 15999) SQL 15357 15357 SERVER server-name was not found, looked at count. +++SUGG: Perhaps name is not valid or it already terminated. Where server-name is the name of the server. Where count is the number of servers scanned. Cause. A specific server is not found. The number of servers scanned is output. Effect. The operation fails. Recovery. Check the spelling of the server name and verify that it is a valid name. Enter the command with the correct server name.
MXCI Messages (15000 through 15999) SQL 15360 15360 SERVICE service-name cannot supply a list of SERVERS using DS datasource-name. +++SUGG: Use INFO SERVICE to see if it still exists. Where service-name is the name of the service. Where datasource-name is the name of the data source. Cause. The lower level returns a bad status when the server list is requested. The service is unavailable and does not return an error about finding the specified DS. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15366 15366 Could not get attribute info for DS “string0” from the database either. +++SUGG: The DS probably does not really exist. Where “string0” is the DS name. Cause. The lower levels returns a status indicating no ability to provide state information for this DS and also fails to get attribute information from the database. Either the name contains a type, needs double quotes, or the DS might not exist. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15369 15369 Could not set statistics 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 15370 15370 Could not set CPU list on 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 15373 15373 DS string1 creation failed, cleanup failed. DS may need to be deleted or repaired. +++SUGG: 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. Then remove the data source and re-create it. SQL 15374 15374 DS name AND SERVICE name can not both be a wild card.
MXCI Messages (15000 through 15999) SQL 15377 15377 Could not get process priority 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 15378 15378 Can not delete the default DS, string1. Where string1 is the data source name. Cause. Removing the TDM_Default_DataSource data source is not allowed. Effect. The operation fails. Recovery.
MXCI Messages (15000 through 15999) SQL 15381 15381 Can not delete a DS that is in use, string1. DS may need to be stopped on all services. +++SUGG: Where string1 is the system, service, and data source name. Cause. The data source is in the start state. Effect. The operation fails. Recovery. Stop the data source and rerun the command. SQL 15382 15382 Connection is lost to the service, string0. +++SUGG: The SERVICE may have died. Where string0 is the service name. Cause.
MXCI Messages (15000 through 15999) SQL 15385 15385 Reason text truncated, maximum characters allowed int1, int2 characters detected. Where int1 maximum allowable characters in a reason string. Where int2 is the number of reason text characters given in the command. Cause. Too many characters in the reason string. Effect. A warning message is displayed and the command is processed. Recovery. Enter the command using less than the maximum allowed characters in the reason string.
MXCI Messages (15000 through 15999) SQL 15389 15389 Idle server count int1 exceeds maximum server count int2, for DS string1. Where int1 is the idle 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. Idle server count is too large. Effect. The operation fails. Recovery. Either increase the maximum server count or decrease the idle server count of the data source.
MXCI Messages (15000 through 15999) SQL 15392 15392 Could not stop 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 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.
MXCI Messages (15000 through 15999) SQL 15396 15396 Could not get automatic start option 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 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.
MXCI Messages (15000 through 15999) SQL 15400 15400 No service active for tracing. Cause. No services are available to activate tracing for this DS. Effect. The trace operation is not processed. If this failure occurs during execution of an ADD DS command, it is possible the DS is successfully created in either the database or on a service before the service is terminated. Recovery. If the error occurs during execution of ADD DS, run INFO DS to verify that the DS is successfully created.
MXCI Messages (15000 through 15999) Cause. The attribute-name (for example, PREFIX, VALUE, LIMIT, ACTION) is not valid with the EVAR object for the command. Effect. The operation fails. Recovery. Either use a different EVAR attribute or delete the EVAR attribute from the command. 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.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Either specify an asterisk (*) wildcard for the EVAR name, or remove the type ALL from EVAR object for this command. 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.
MXCI Messages (15000 through 15999) Cause. More than one object type for the specified name is found. Effect. A warning message is displayed, and the command is processed. Recovery. Delete the duplicates. 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.
MXCI Messages (15000 through 15999) SQL 15416 15416 A define EVAR name must be 2 to 24 characters long. With the first character an equal sign and the second a letter. The remaining characters can be letters, numbers, hyphens, underscores or circumflexes (^). Cause. An invalid define EVAR name is entered in the command. Effect. The command fails. Recovery. Enter the command with a valid define EVAR name.
MXCI Messages (15000 through 15999) Recovery. Enter the command with a valid group or member name. SQL 15430 15430 Specified user user-name not found in existing list. Nothing changed. Where user-name is the user name. Cause. The user name was not found in the list of user names. Effect. The operation fails. 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.
MXCI Messages (15000 through 15999) SQL 15434 15434 Failed to write the USER changes in the output area to disk. New changes dropped. +++SUGG: Administrator must be super.super, and user name must be registered on this system to do this. Cause. A failure occurred in the lower-client library function. Effect. The operation fails. Recovery. See the lower-level error messages for details. SQL 15435 15435 Too many USERs for user-type list buffer size. New changes dropped.
MXCI Messages (15000 through 15999) SQL 15437 15437 Groupname group-name is not found in the system system-name user list. Where group-name is the group name. Where system-name is the name of the system. Cause. The group the operation was given against does not exist on the system. Effect. The operation fails. Recovery. Add the group to the system first, then reissue the command. SQL 15438 15438 This command does not permit * as the comp-name component when the membername is present.
MXCI Messages (15000 through 15999) Cause. The command is not available. Effect. The operation fails. Recovery. No recovery required. SQL 15453 15453 Unknown object type, string1. Where string1 is the object type. Cause. The object type is invalid. Effect. The operation fails. 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.
MXCI Messages (15000 through 15999) SQL 15457 15457 Could not open connection to SERVICE string1. +++SUGG: SERVICE name may be incorrect, system name was valid. Where string1 is the service name. Cause. The service name is incorrect. Effect. The operation fails. Recovery. Enter the command specifying a valid service name. Use the INFO SERVICE command to list the valid services. SQL 15458 15458 Could not open connection to system string1.
MXCI Messages (15000 through 15999) SQL 15502 15502 Invalid character in the command. Cause. The MXCI command scanner found an invalid character in the command. The character was not recognized in context. Effect. The operation fails. Recovery. Correct the syntax and reissue the command. 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.
MXCI Messages (15000 through 15999) SQL 15506 15506 The value must be a period or comma. Cause. The SET STYLE value that you specified for the DECIMAL_POINT option was not a period(.) or a comma (,). Effect. The operation fails. Recovery. Enter the corrected command. 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.
MXCI Messages (15000 through 15999) SQL 15510 15510 The value must be between 1 and 32767 or ALL. Cause. The SET LAYOUT value that you specified for the PAGE_LENGTH option was not in the value range. Effect. The operation fails. Recovery. Specify the correct value and resubmit. 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.
MXCI Messages (15000 through 15999) SQL 15514 15514 The value must be between 1 and 255 for the LIST command. Cause. The value that you specified in the LIST command was out of range. The value must be in the range 1 through 32767, or ALL. Effect. The operation fails. Recovery. Specify the correct value and resubmit. SQL 15515 15515 This command is not allowed because a SELECT is in progress. Cause.
MXCI Messages (15000 through 15999) Recovery. Use these commands only with SELECT. SQL 15517 15517 An invalid option was specified. Cause. You specified an invalid option for the SET, RESET, SHOW, or SAVE command. Effect. The operation fails. Recovery. Specify a valid option and resubmit. 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.
MXCI Messages (15000 through 15999) Recovery. Revise the TOTAL, SUBTOTAL, or DETAIL command so that all of the TOTAL items also appear in the DETAIL print list. SQL 15521 15521 You have a SUBTOTAL command but not a BREAK command. The SUBTOTAL command is being ignored. Cause. You specified a SUBTOTAL command, but there are no break columns to subtotal. Effect. The operation fails. Recovery. Enter a BREAK command or delete the SUBTOTAL command by using RESET.
MXCI Messages (15000 through 15999) Effect. The DETAIL command fails. Recovery. Correct the value of TAB and resubmit. SQL 15525 15525 The value for PAGE, NEED, or SKIP is out of range. The valid range is 1 through 32767. Cause. The value that you specified for the PAGE, NEED, or SKIP clause was not in the range 1 through 32767. Effect. The DETAIL command fails. Recovery. Correct the value of PAGE, NEED, or SKIP and resubmit.
MXCI Messages (15000 through 15999) Recovery. Remove the duplicate entry and resubmit. SQL 15529 15529 Alias OR detail-alias name cannot be used because a command-type command is using it. Cause. You attempted to reset an alias name or detail-alias name that was being used in another report command. The name cannot be deleted while another command is dependent upon it. Effect. The alias or detail-alias name is not reset. Recovery.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Use only unique names and resubmit. SQL 15533 15533 You have specified subtotal or break title or break footing or line_number on text1. You must specify a BREAK command on text2 before the LIST command. Cause. You specified a SUBTOTAL, BREAK TITLE, or BREAK FOOTING command or a LINE_NUMBER function for a column that is not a BREAK column. Effect. No report is generated. Recovery.
MXCI Messages (15000 through 15999) Effect. The operation fails. Recovery. Check that the operands belong to data type classes that can be operated upon in a binary arithmetic expression. 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.
MXCI Messages (15000 through 15999) Recovery. Correct the command and resubmit. 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.
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.
15 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. SQL/MX is unable to return or display a message. Recovery. Reinstall 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. Effect.
Messages Generated by the Message System (16000 through 16999) HP NonStop SQL/MX Messages Manual—523730-004 15- 2
16 Internal Stored Procedures Messages (19000 through 19999) SQL 19000 19000 An internal error occurred in internal stored procedure processing. Cause. Internal error. Effect. 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. SQL/MX is unable to process the request. Recovery. None. Report the entire message to your service provider.
Internal Stored Procedures Messages (19000 through 19999) SQL 19020 19020 Stored procedure name expects value input parameters. Cause. Internal error. Effect. SQL/MX is unable to process the request. Recovery. None. Report the entire message to your service provider. SQL 19021 19021 Stored procedure name returns with error: number. Cause. Internal error. Effect. SQL/MX is unable to process the request. Recovery. None. Report the entire message to your service provider.
17 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) Recovery. None. This is an internal error. Contact your service provider. SQL 20014 20014 File system error error number occurred while getting allocated extents for file. Cause. SQL was not able to obtain the number of allocated extents for 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.
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 20018 20018 An internal error occurred. There is an inconsistency between the data type (type) and default state (default) for column (name). Where type is the SQL_DATA_TYPE specified in the COLS metadata table. Where default is the DEFAULT_CLASS specified in the COLS metadata table.
Utility Messages (20000 through 23099) Where table2 is the name of the referencing table. Where const is the name of the constraint for the referencing table. Cause. SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20021 20021 An internal error occurred - invalid column data type. Cause.
Utility Messages (20000 through 23099) SQL 20024 20024 Object already exists. Cause. You tried to create a table that already exists. Effect. The operation fails. Recovery. Change the name of the table and resubmit. SQL 20025 20025 An internal error occurred - invalid object state. Cause. The utility subsystem that reads and maintains metadata performed a step out of sequence. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20028 20028 Specified an invalid partition physical size, should be BYTES, MBYTES, KBYTES, or GBYTES. Cause. You specified an invalid partition physical size, which must be expressed in bytes, megabytes, kilobytes, or gigabytes. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
Utility Messages (20000 through 23099) SQL 20032 20032 An internal problem was detected. 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 20033 20033 The partition must be empty before you drop it. Cause. You attempted to drop a nonempty range partition. Effect. The operation fails. Recovery. Make sure the range partition is empty before dropping it.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Check the spelling of the specified table name and resubmit. SQL 20037 20037 An invalid operation was specified - only ADD, DROP, and MOVE are supported. Cause. You specified a request that was not ADD, DROP, MOVE, or REUSE. Effect. The operation fails. Recovery. Check the spelling of your request and resubmit. SQL 20038 20038 The specified key value uses incorrect syntax. Cause. You specified a key value with incorrect syntax.
Utility Messages (20000 through 23099) SQL 20041 20041 File system error error number was encountered. Cause. The utility subsystem that retrieves data from the file system failed with an unexpected error. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20042 20042 Importing binary data to UCS2 character column $0~string0 is not allowed. Where $0~string0 is the corresponding column name. Cause.
Utility Messages (20000 through 23099) SQL 20045 20045 An internal error occurred - invalid sort order. Cause. The utility subsystem that reads and maintains metadata encountered an unexpected value for the sort order (ASC, DESC) on the primary key. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20046 20046 An internal error occurred - invalid size unit. Cause. The utility encountered an unexpected value for a size unit designation. Effect.
Utility Messages (20000 through 23099) SQL 20049 20049 File system error error occurred while retrieving the name of the local system. Where error is the returned file system error. Cause. An unexpected error occurred while decomposing a Guardian file name or template. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. SQL 20050 20050 The modify request failed. See subsequent errors for more details. Cause.
Utility Messages (20000 through 23099) Recovery. Use the messages that accompany this one to diagnose and correct the problem. SQL 20053 20053 Transaction Management subsystem could not begin a new transaction. Cause. The utility subsystem that performs transaction management operations failed while trying to begin a new transaction. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem.
Utility Messages (20000 through 23099) Recovery. None. This is an internal error. Contact your service provider. SQL 20057 20057 An internal error occurred - Transaction Management subsystem could not do GetRowsAffected on a statement. Cause. The utility subsystem that performs CLI requests to SQL failed trying to extract the number of rows affected from the previously executed request. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20061 20061 The -C command line option must have a value greater than zero. Cause. You specified the number of rows (or records) to be imported as a negative value. Effect. The operation fails. Recovery. Specify a positive num-rows value. SQL 20062 20062 The -T command-line option must have a value greater than zero. Cause. The transaction-size value that you specified is either negative or zero. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20066 20066 The specified error file does not exist or cannot be opened for write access. Cause. The error file that you specified cannot be opened because it was not created, or it has been corrupted. Effect. The operation fails. Recovery. Verify that the error file has been created. If it exists, check to see if the file is corrupted. SQL 20067 20067 A syntax error occurred at or before: string0. Where string0 is the value where the syntax error was detected.
Utility Messages (20000 through 23099) SQL 20070 20070 Columns in the datafile are not correct. Columns found so far: columnnumber Where columnnumber is the number of the column that IMPORT already processed in the current row. Cause. The specific field in the current row in the input file could not be processed. Effect. The operation fails. Recovery. Check the specified column in the current row for valid data. SQL 20071 20071 The row delimiter should not contain a qualifier character. Cause.
Utility Messages (20000 through 23099) SQL 20073 20073 Object objname does not exist. Where objname is the ANSI name of the target table. Cause. The object name that you specified was invalid or does not exist. Effect. The operation fails. Recovery. Specify a valid object name. Verify that the catalog name, schema name, and table name sections of the ANSI name are specified. SQL 20074 20074 IMPORT cannot open datafile - file name. Where file name is the input data file name. Cause.
Utility Messages (20000 through 23099) Recovery. Use the message that is shown before this one to diagnose and correct the problem. SQL 20081 20081 Row number rownum and column number columnnum could not be processed. Column Data: text. Where rownum is the row number that was processing when the error occurred. Cause. An internal error occurred in a stored procedure. Effect. The import was partially completed. It terminated while processing the row specified. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) SQL 20084 20084 The start position in the FIXED WIDTH FORMAT part of the format file is not valid. Cause. The start position for one of the columns that you specified in the FIXED WIDTH FORMAT part of the format file was invalid. Effect. The operation fails. Recovery. Verify and correct the column start position in the FIXED WIDTH FORMAT part of the format file and resubmit. SQL 20085 20085 The column size in FIXED WIDTH FORMAT part of the format file is not valid.
Utility Messages (20000 through 23099) SQL 20087 20087 One or more of the specified command-line arguments are not valid. Syntax: import catalog.schema.table -I input-file [-C number-of-rows] [-E error-file] [-F rows-to-skip] [-L max-errors] [-R multiple of trans-size] [-S] [-T trans-size] [-U format-file] [-W file-type] [-FD field-delimiter] [-QL field-qualifier] [-RD row-delimiter] [-Z character-set] Cause. One or more of the command line arguments that you specified were invalid. Effect.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. Contact your service provider SQL 20091 20091 The column size is not specified in compile time arguments. Key = columnsize Where columnsize is the column size specified in the FIXED WIDTH FORMAT part of the format file. Cause. The column size that you specified was missing from an internal message. Effect. The import operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) 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. The scale value that you specified was missing from an internal message. Effect. The operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) 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. Where columnname is the column name in the COLUMN FORMAT section of the format file. Cause.
Utility Messages (20000 through 23099) 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. SQL 20103 20103 The object name contains an invalid character: position in string pos, length of string len, value found char. Cause.
Utility Messages (20000 through 23099) 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. Contact your service provider. SQL 20108 20108 A qualifier is missing in the data file. Column Number = columnnumber. Where columnnumber is the column number in the data file. Cause.
Utility Messages (20000 through 23099) SQL 20111 20111 Source catalog catalog-name does not exist or cannot be accessed. Where catalog-name is the name of the catalog associated with the source table. Cause. You specified a source catalog name that does not exist or could not be accessed. Effect. The operation fails. Recovery. Correct the catalog name and resubmit. SQL 20112 20112 Source schema schema name does not exist or cannot be accessed.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Correct the catalog name and resubmit. SQL 20115 20115 Target schema schema name does not exist or cannot be accessed. Where schema name is the name of the schema associated with the target table. Cause. You specified a target schema name that does not exist or could not be accessed. Effect. The operation fails. Recovery. Correct the schema name and resubmit. SQL 20116 20116 Target table is the same as source. Operation failed.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Verify the schema name and resubmit. SQL 20119 20119 Table table name does not exist or cannot be accessed. Where table name is the name of the table to be purged. Cause. You specified a table name that does not exist or could not be accessed. Effect. The operation fails. Recovery. Verify the table name and resubmit. SQL 20120 20120 Partition does not exist or cannot be accessed. Cause.
Utility Messages (20000 through 23099) SQL 20123 20123 A user-defined transaction has been started. PURGEDATA cannot be performed. Cause. You attempted to perform a PURGEDATA operation after a user-defined transaction was started. Effect. The operation fails. Recovery. Commit or roll back the transaction and resubmit. SQL 20125 20125 table name is a metadata table. PURGEDATA cannot be performed on metadata tables. Where table name is the name of the table specified in the PURGEDATA operation. Cause.
Utility Messages (20000 through 23099) SQL 20129 20129 Internal error occurred while performing DUP. Cause. An internal error occurred while performing the DUP operation. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20130 20130 The Column IsNullable not present in compile time arguments. Key = keyval. Cause. The specified attribute was missing from an internal message. Effect. The operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) Effect. The DUP operation fails. Recovery. Commit or roll back the user-defined transaction and resubmit. SQL 20134 20134 IMPORT can not open errorfile - file name. Where file name is the name of the specified file. Cause. SQL was unable to open the file name that you specified with the -E command-line option. Effect. The IMPORT operation fails. Recovery. Specify a valid error file name and resubmit. SQL 20136 20136 The qualifier must be a single character. Cause.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Specify a valid column name. SQL 20139 20139 ABORTTRANSACTION failed with TMF error error number. Cause. The utility subsystem that performs CLI operations failed while trying to perform an ABORTTRANSACTION. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem. SQL 20140 20140 Wrong parameter name passed. Cause.
Utility Messages (20000 through 23099) SQL 20143 20143 Equal sign is missing. Cause. An equal sign is missing from an equation. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Utility Messages (20000 through 23099) SQL 20148 20148 Begin key same as end key. PURGEDATA cannot be performed. Cause. The list of partitions specified in the key range has the same begin and end key. There are no partitions to purge. Effect. The operation fails. Recovery. Specify a valid key range and resubmit. SQL 20149 20149 External indexes exist for this table. Since the source and target have the same catalog and schema, index map must be specified. DUP cannot be performed. Cause.
Utility Messages (20000 through 23099) SQL 20152 20152 The VARCHAR varying-length can support non-binary FIXED-WIDTH format file only. Cause. You specified VARCHAR for a format file that is binary FIXED-WIDTH. Effect. SQL is not able to perform the IMPORT operation. Recovery. Verify your format file and resubmit. 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.
Utility Messages (20000 through 23099) SQL 20157 20157 Assigning a DEFAULT value to the NO DEFAULT field. Column number = column number Cause. You attempted to assign a default value to a field, in column number, with NO DEFAULT. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Utility Messages (20000 through 23099) SQL 20163 20163 An internal error occurred - invalid include option of CREATE TABLE LIKE. Cause. SQL was unable to perform the requested operation. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. 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.
Utility Messages (20000 through 23099) SQL 20167 20167 The object name must contain at least one character. Cause. The object name that you specified is not valid.It must contain at least one character. Effect. The operation fails. Recovery. Correct the syntax and resubmit. 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.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Correct the format file and resubmit. 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. SQL 20173 20173 A transaction must be started before executing this request. Cause. SQL detected an internal error. Effect.
Utility Messages (20000 through 23099) SQL 20176 20176 A concurrent utility or DDL operation is being performed on table TableName. That operation must complete before the requested Import operation can run. Where TableName is the name of the table. Cause. The Import operation cannot be performed on a table while another utility operation is in progress on the same table. Effect. The operation fails. Recovery. Wait until the current utility operation is complete and resubmit.
Utility Messages (20000 through 23099) SQL 20180 20180 section name section of the format file is not valid. Cause. The specified section name in the format file was invalid. Effect. The operation fails. Recovery. Correct the format file and resubmit. 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.
Utility Messages (20000 through 23099) SQL 20184 20184 The syntax of the format file file name is not valid. Where file name is the name of the format file. Cause. The format file name that you specified was not a valid format file. Effect. The operation fails. Recovery. Correct the format file and resubmit. SQL 20185 20185 More than one partition resides on volume volume name. The MODIFY utility does not know which partition to move or drop.
Utility Messages (20000 through 23099) Recovery. Specify a value greater than or equal to zero and resubmit. SQL 20189 20189 Data in the primary partition (or subset) cannot be moved to the previous partition because no previous partition exists. Cause. You tried to move data in the first partition to a nonexisting previous partition. Effect. The operation fails. Recovery. Remove the TO PREVIOUS PARTITION phrase and resubmit.
Utility Messages (20000 through 23099) SQL 20193 20193 This operation cannot be performed under a user-defined transaction. Cause. You cannot perform a POPULATE INDEX operation under a user-defined transaction. Effect. The operation fails. Recovery. Commit or roll back the user-defined transaction and resubmit. 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.
Utility Messages (20000 through 23099) Cause. The index name specified by the caller should not contain data. Data was found to exist, most likely because a previous POPULATE INDEX command failed. Effect. The operation fails. Recovery. Execute the RECOVER command to clean up the previously failed command and resubmit. 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.
Utility Messages (20000 through 23099) SQL 20200 20200 Catalog does not exist. Cause. You specified a catalog name that is not defined or not visible on the system. Effect. The operation fails. 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.
Utility Messages (20000 through 23099) Cause. The index name could not be recovered with the given RECOVER command. Effect. The operation fails. Recovery. Use the correct RECOVER option and resubmit. 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) 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. Select the lock name from the DDL_LOCKS metadata table to determine which operation to recover and resubmit.
Utility Messages (20000 through 23099) 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. The RECOVER operation could not be performed on lock lock-name.
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) Cause. You tried to perform a MODIFY utility operation on a table with materialized views, which is not supported. Effect. The operation fails. Recovery. None. 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.
Utility Messages (20000 through 23099) SQL 20244 20244 The byte order mark in Unicode data file file is not valid. Where file is the name of the Unicode data file. Cause. The byte order mark bytes specified are invalid. Effect. The Unicode data import fails. 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.
Utility Messages (20000 through 23099) Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. 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.
Utility Messages (20000 through 23099) SQL 20255 20255 An invalid partition management operation was specified for an index. Only ADD, DROP, and MOVE requests are supported. Cause. You attempted a partition management request other than ADD, DROP, or MOVE on an index. Note that the REUSE request works only with range-partitioned requests. Effect. The operation fails. Recovery. None. SQL 20257 20257 This partition management operation is not supported for system-clustered base table table-name.
Utility Messages (20000 through 23099) SQL 20261 20261 The WHERE clause must be used with object-name because it has more than one partition. Where object-name is the name of the object. Cause. In the WHERE clause, you did not specify the partition in the request to move the partition to a new location. When the object has more than one partition, you must specify the partition. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) 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 20266 20266 Invalid message code code1 returned from SPI request, expecting code2. Where code1 is the code returned from SPI. Where code2 is the expected value. Cause.
Utility Messages (20000 through 23099) Effect. The IMPORT operation is complete. The table might remain in an unaudited state. Recovery. See the Guardian Procedure Errors and Messages Manual file system errors for possible recovery action and resubmit. SQL 20269 20269 The audit attribute of table table-name could not be turned off during import operation. Where table-name is the name of the target table. Cause.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20272 20272 Non-audited tables are not supported. Cannot perform DUP. Cause. The DUP operation does not support nonaudited tables. Effect. The operation fails. Recovery. Change the table to be audited using the FIXUP command, and resubmit. SQL 20273 20273 An internal error occurred. Cause.
Utility Messages (20000 through 23099) Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose the error and then resubmit. SQL 20276 20276 Reload operation failed, already in progress. Cause. SQL attempted to start a FUP RELOAD operation but an operation was already in progress. Effect. The operation fails. Recovery. Wait until the current RELOAD operation completes, and resubmit.
Utility Messages (20000 through 23099) SQL 20293 20293 The partition cannot be reused because the partition contains data and the specified table is referenced by another table. Cause. The partition that you specified in the partition management request contains data, and the specified base table is referenced by another base table via a referential integrity constraint. The REUSE operation is not allowed on such a partition. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20296 20296 The MODIFY request has completed successfully, but ORSERV might not have completed successfully. Please run FUP RELOAD manually to reclaim any free space on file-name-list. Where file-name-list is the list of Guardian file names of the partitions that might need reloading. The names are separated by blanks. Cause. The MODIFY utility encountered failures after it started all ORSERVs (the FUP RELOAD operation) successfully.
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 20324 20324 The table object does not exist. Cause. You attempted to perform a PARTONLY restore to a table that does not exist. Effect. The operation fails. Recovery. Check the location of the table. SQL 20325 20325 The job failed due to an internal error. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20330 20330 The specified parameter is not valid. Cause.
Utility Messages (20000 through 23099) Recovery. None. Contact your service provider. SQL 20333 20333 The audit file name is not valid. Cause. The DP2 file name of an audit object, passed by the transaction management process (TMP), is invalid. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20334 20334 The restore options do not match the backup options. Cause. The restore options you specified do not match the backup options. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. Contact your service provider. SQL 20338 20338 Master audit trail does not exist. Cause. In a snapshot restore, the master audit trail data was missing. Effect. The operation fails. Recovery. None. This an internal error. Contact your service provider. SQL 20350 20350 A syntax error was found near “string”, near character position int. Where string is the value where the syntax error was detected.
Utility Messages (20000 through 23099) 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. SQL 20354 20354 Only super ID can use MXTOOL operation operation. Where operation is the GOAWAY or FIXUP operation. Cause.
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 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. You can use GOAWAY only with SQL/MX objects. SQL 20358 20358 Catalog catalog does not exist.
Utility Messages (20000 through 23099) 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”. Where error is the error returned by the Guardian file system while searching for files. Where Guardian file is the template of Guardian files requested to be removed. Cause. MXTOOL generates a list of files to check as specified by a Guardian file template.
Utility Messages (20000 through 23099) 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. Correct the syntax and resubmit. SQL 20371 20371 The specified object object is not an SQL/MX table, view, or stored procedure. Where object is the name specified in the MXTOOL command. Cause. The object specified by the caller is not a table, view, or stored procedure. Effect.
Utility Messages (20000 through 23099) SQL 20374 20374 Option -s cannot be used in combination with any filtering option. Cause. A syntax error occurred while processing the GOAWAY operation. An invalid list of options was specified. Effect. The operation fails. Recovery. Please run “mytool help goaway” to get the list of correct options and retry request. SQL 20450 20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name).
Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. Run the GOAWAY operation on a local machine. SQL 20453 20453 Operation failed on name due to timeout. Where name is the name of the Guardian file requested to be removed. Cause. The GOAWAY operation failed because the label has a lock on it, and the operation timed out after 90 seconds. Effect. The operation fails. Recovery. Remove the lock on the label and retry the operation.
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 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.
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 20701 20701 Audit fix process process name was not able to allocate an extended memory segment. SEGMENT_ALLOCATE_ returned error error number.
Utility Messages (20000 through 23099) SQL 20703 20703 A heap allocation error occurred in process process name during the audit fixup phase of the operation. Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered a heap allocation error. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. SQL 20704 20704 A hardware trap occurred in audit fixup process process name.
Utility Messages (20000 through 23099) Recovery. None. Contact your service provider. SQL 20707 20707 A parameter was missing or not valid in an audit fixup request (process process name). Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process received an invalid request from the MODIFY code. Such an error might be caused by the use of incorrect versions of MXCMP or MXAUDSRV software. Effect. The MODIFY operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20710 20710 An error occurred while attempting to perform a REDO of a TMF audit record 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 applying TMF audit. Effect. The MODIFY operation fails. Recovery. Verify that TMF is up and running normally.
Utility Messages (20000 through 23099) SQL 20716 20716 The audit fixup phase of the operation was unable to retrieve information from the TMF subsystem. Cause. During an online partition management operation, the MXAUDSRV process was not able to retrieve information from TMF. Effect. The MODIFY operation fails. Recovery. Verify that TMF is up and running normally. If not, correct this problem and retry the operation. Otherwise, contact your service provider.
Utility Messages (20000 through 23099) Cause. During an online partition management operation, the MXAUDSRV process received a request from the MODIFY code with an incompatible version field. The probable cause is the use of incorrect product versions of MXCMP and MXAUDSRV. Effect. The MODIFY operation fails. Recovery. Verify that correct versions of MXCMP and MXAUDSRV are installed. If so, contact your service provider.
Utility Messages (20000 through 23099) SQL 20725 20725 Audit fixup process process name detected an internal error. Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered an internal error. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. SQL 20726 20726 An audit fixup process’s program file process name is not licensed. Where program file name is the MXAUDSRV process name. Cause.
Utility Messages (20000 through 23099) Cause. During an online partition management operation, the MXAUDSRV process encountered an error when attempting an SQL/MX statement. Effect. The MODIFY utility did not process the request. Recovery. Contact your service provider. SQL 20729 20729 File system error error code was returned from an MXARLIB call in audit fixup process process name. Where error code is the returned file system number. Where process name is the MXAUDSRV process name. Cause.
Utility Messages (20000 through 23099) Recovery. If the timestamp check failed at the beginning of the commit phase, perform a RECOVER command to undo partial processing. Then, retry the MODIFY operation with a timestamp sufficiently in the future. SQL 20732 20732 The time given in the AFTER clause is more than 30 days in the future. Cause. The MODIFY command includes a COMMIT AFTER timestamp clause, and the timestamp specifies a time that is more than 30 days in the future. Effect.
Utility Messages (20000 through 23099) SQL 20752 20752 The cmdname command cannot work on table table that has an object type of type. cmdname supports only tables that have an object type of BT. Where cmdname is the name of the utility. Where table is the table name specified. Where type is the object type of the table as found in the metadata. Cause. You possibly specified a utility operation on a view, stored procedure, or MP alias, which is not supported. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 20755 20755 VERIFY cannot work on object (name) because it is not part of the table (namespace) name space or the table does not exist. VERIFY supports only tables. Where name is the table name specified in the request. Cause. VERIFY failed because the object specified is not a table, possibly because of a misspelled name. Effect. The operation fails. Recovery. Specify the correct name and resubmit.
Utility Messages (20000 through 23099) 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. If a MODIFY operation is currently in progress, this error can be ignored. If a MODIFY operation is not in progress, the offline partition needs to be recovered.
Utility Messages (20000 through 23099) 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. Please use FIXUP to change the corrupt bit to correct the inconsistency. SQL 20762 20762 The primary extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file).
Utility Messages (20000 through 23099) 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. SQL 20765 20765 The audit flag (flag1) defined on the label does not match the audit flag (flag2) defined in the metadata for Guardian file (file). Where flag1 is the value of the flag stored in the label.
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) Recovery. Contact your service provider. SQL 20774 20774 The constraint text in the resource fork does not match the constraint text in the metadata for constraint (name) while processing the Guardian file (file). Where name is the constraint name described 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 20777 20777 The constraint map 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 20778 20778 The constraint information is missing from the metadata for object (name). Where name is the name of the table. Cause.
Utility Messages (20000 through 23099) SQL 20780 20780 Index (name) is defined in the metadata but missing from the resource fork for Guardian file (file). Where name is the name of the index that should exist in the index map in the resource fork. 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) Where file is the name of the Guardian file. Where string2 is the Guardian name of the partition as it is defined in the metadata (PARTITIONS or REPLICAS tables). Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. SQL 20784 20784 Partition map entry (file1) is defined in the metadata but is missing from the resource fork for Guardian file (file2).
Utility Messages (20000 through 23099) Recovery. Contact your service provider. 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.
Utility Messages (20000 through 23099) SQL 20790 20790 The partition name (rname) defined in the resource fork does not match the partition name (mname) defined in the metadata for Guardian file (file). Where rname is the partition name defined in the resource fork. 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.
Utility Messages (20000 through 23099) SQL 20795 20795 VERIFY cannot work on Guardian file (file) that has an object type of (type1). VERIFY supports only base tables that have an object type of type2. Where file is the Guardian file being verified. Where type1 is the object type found in the label information. Where type2 is the supported object type. Cause. You attempted to verify a Guardian file with an unsupported object type. Effect. The operation fails. Recovery. None.
Utility Messages (20000 through 23099) SQL 20852 20852 Broken bit was not changed for file file-name. Already set to the correct value of value. Where file-name is the Guardian file-name of the SQL/MX object. Where value is always 0 to indicate the broken bit is already cleared. Cause. The ‘-rb” option was used with the FIXUP utility to reset the broken bit on a file where the broken bit is not currently set. Effect. None. This is a warning. Recovery. No recovery is necessary.
Utility Messages (20000 through 23099) Where value is always 0 to indicate the corrupt bit is cleared. Cause. The “-rc” option was used with the FIXUP utility to reset the corrupt bit on a file where the corrupt bit is not currently set. Effect. None. This is a warning. Recovery. No recovery is necessary. 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.
Utility Messages (20000 through 23099) SQL 20860 20860 file-name is not a datafork/label. Only changes to datafork/label are supported. Where file-name is the Guardian file specified as an argument to FIXUP. Cause. You specified a file other than an SQL/MX data fork. 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.
Utility Messages (20000 through 23099) Effect. A resource cannot be allocated and the program fails. Recovery. Resubmit on another processor. SQL 23003 23003 servername: File error encountered: description. Where servername is the name of the server program that issued the error. Where description gives more detail about the file error. Cause. See details in description description. Effect. The operation fails. Recovery. Correct the problem and resubmit.
Utility Messages (20000 through 23099) Cause. The DML Layer reported an SQL error. See description for the reason. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 23008 23008 servername: Assertion failed. Where servername is the name of the server program that issued the error. Cause. Internal program ASSERT failed, indicating an invalid program state. Effect. The operation fails. Recovery. None. Contact your service provider.
Utility Messages (20000 through 23099) Where xml_tag is the XML tag which could not be identified. Cause. servername discovered an XML tag that is not supported or is invalid. This error could indicate a problem with mxemportddl XML file generation. It could also indicate a version problem of a downrev mximportddl running on input from an uprev mxexportddl. Effect. The operation fails. Recovery. Correct the input XML file and resubmit.
Utility Messages (20000 through 23099) 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. Where description contains details about the missing information in the DDL buffer. Cause. Expected DDL command not found in the XML input file. This might indicate a problem with mxexportddl XML file generation. Effect. The operation fails. Recovery.
Utility Messages (20000 through 23099) SQL 23018 23018 servername: Expected map entry is missing: description. Where servername is the name of the server program that issued the error. Where description contains detailed information about the missing mapping file section name. Cause. When processing a mapping file, an expected section or attribute was not found. Effect. The operation fails. Recovery. Correct the mapping file and resubmit.
Utility Messages (20000 through 23099) Where description contains detailed information about the argument in error. Cause. You did not specify a needed value for a specific run-time argument. This error could indicate a problem with the mxemportddl SML file generation. Effect. The operation fails. Recovery. Determine the problem with the input file and resubmit. SQL 23022 23022 Error occurred for partition file name when attempting to set the statistics metadata.
18 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. Where 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) Cause. You attempted to access an object in a schema that is currently being upgraded to an incompatible version. The affected object either does not exist, or has been upgraded to the incompatible version. Effect. The operation fails. Recovery. Retry the affected operation, with software that is compatible with a version version2 schema, to determine if the object exists.
Versioning and Distribution Messages (25000 through 25399) SQL 25101 25101 Remote node node1 is not running a compatible version of SQL/MX software. The SQL/MX software version (MXV) of node2 is MXV1, the local node supports only MXV MXV2. Where node1 is the name of the affected remote node. Where node2 is the name of the local node. Where MXV1 is the MXV of the affected remote node. Where MXV2 is the local node’s MXV. Cause.
Versioning and Distribution Messages (25000 through 25399) Cause. The remote node node runs a non-General Availability (non-GA) release of SQL/MX and cannot access remote nodes that have an MXV different from its own (MXV1). Effect. The operation fails. Recovery. Migrate the remote node to a supported GA release. Or, conversely, migrate the local node to the same non-GA release as the remote node.
Versioning and Distribution Messages (25000 through 25399) SQL 25201 25201 Table or view object cannot be accessed because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2. Where object is the name of the affected database object. Where version1 is the schema version of that database object’s schema. Where node is the name of the node that detects the incompatibility. Where version2 is that node’s MXV. Cause.
Versioning and Distribution Messages (25000 through 25399) SQL 25203 25203 Table or view object cannot be accessed on node because of a version incompatibility. Its schema has version version1; node does not support schema version higher than version2. Where object is the name of the affected database object. Where node is the name of the node where object is present. Where version1 is the schema version of object’s schema. Where version2 is that node’s MXV. Cause.
Versioning and Distribution Messages (25000 through 25399) SQL 25205 25205 Schema schema has schema version version1; this is incompatible with the version of the compiler that executes the operation. The compiler version is version2. Where schema is the name of a schema that is referenced by a DDL or utility operation. Where version1 is the schema version of schema. Where version2 is the compiler version of the compiler that executes the DDL or utility operation. Cause.
Versioning and Distribution Messages (25000 through 25399) • There is a need to access the system schema on a remote uprev node, and the system schema version of that system schema is later than the current compiler version. Effect. The operation fails. Recovery. Downgrade the system schema on the affected node to a version that is compatible with the required compiler version, or upgrade the compiler.
Versioning and Distribution Messages (25000 through 25399) SQL 25210 25210 Schema schema has schema version version1; node does not support schema versions lower than version2. Where schema is the name of the schema referenced by a DDL or utility operation. Where version1 is the schema version of schema. Where node is the node where the operation is executed or the node where metadata for the schema resides. Where version2 is the earliest supported schema version of node. Cause.
Versioning and Distribution Messages (25000 through 25399) SQL 25212 25212 Table or view object has schema version version1, the local SQL/MX software version (MXV) can access only database objects with schema version (MXV1). Where object is the affected table or view. Where version1 is the schema version of object’s schema. 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 release of SQL/MX and is compatible only with system 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 system schema version. Or, conversely, correct the system schema and reinitialize SQL on the affected node.
Versioning and Distribution Messages (25000 through 25399) SQL 25218 25218 Schema schema has schema version version1; node cannot access or represent schemas with versions higher than MXV1. Where schema is a schema that is accessed by a DDL or utility operation. Where version1 is the schema version of that schema. Where node is the node that encounters the incompatibility or the node where metadata for the schema is stored. Where MXV1 is the MXV of that node. Cause.
Versioning and Distribution Messages (25000 through 25399) Cause. You attempted to load a module with a module version (version1) that is earlier than the executing node’s earliest supported plan version (version2). Effect. The operation fails. 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.
Versioning and Distribution Messages (25000 through 25399) SQL 25303 25303 The query plan version is version1; node node does not support query plan versions higher than version2. Where version1 is the plan version of the affected query. Where node is the name of the node that detects the incompatibility. Where version2 is the MXV of the node that detects the incompatibility. Cause.
Versioning and Distribution Messages (25000 through 25399) • • For static compilations, the compiler automatically starts a compiler process of the required version. That compiler process compiles the entire module, and the result of that compilation is returned to the user. If a compiler of the required version cannot be found, error message 25103 is returned. Recovery. Recovery depends on the actual failure.
Versioning and Distribution Messages (25000 through 25399) 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 non-GA release of SQL/MX and is compatible only with modules generated by its own version Effect. The operation fails. Recovery. Compile the module with a compiler version that is compatible with the MXV.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) 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. The query affects one or more nodes with an MXV lower than the current compiler version. Effect. The operation fails. Recovery. Explicitly use a compiler of the specified version.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) 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. When the message is issued as a error, correct the error and retry the operation. If the message is issued as a warning, SQL/MX attempts to recover automatically.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) SQL 25404 25404 Catalogs catalog1 and catalog2 must have identical visibility. Where catalog1 and catalog2 are ANSI catalog names. Cause. You attempted to establish a relationship between catalog1 and catalog2, which have different visibility. Effect. The operation fails. Recovery. Correct the error and retry the operation.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) or 25403, and late name resolution or automatic recompilation is attempted. If that succeeds, the query executes. If not, the query fails and additional errors are issued. Recovery. If the message is issued as an error, correct the error and resubmit. SQL 25407 25407 File system error error was encountered on access to the system schema on node. Where error is a Guardian file system error number.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) Recovery. None. Replicas of the specified schema already exist on the node. SQL 25422 25422 Catalog catalog cannot be unregistered from node node because database objects in the catalog are present on the node. 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) Distribution Messages (25400-25499) SQL 25425 25425 Node node contains the only automatic catalog reference of catalog catalog. Schema replicas cannot be removed. Where node is the node where the single automatic replica of the target catalog resides. Where catalog is the ANSI name of the target catalog. Cause. The target node of an UNREPLICATE SCHEMA operation holds the only automatic reference for the affected schema catalog. Effect.
Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) related to one or more other catalogs that are visible on the target node. This error is issued once per related catalog. Effect. The operation fails. Recovery. Use the CASCADE option on UNREGISTER CATALOG. SQL 25428 25428 Catalog catalog1 cannot be registered on node node because it is related to catalog2 which has no reference on the target node.
Versioning and Distribution Messages (25000 through 25399) JDBC Driver Error Messages (29000-29999) SQL 25430 25430 The system catalog cannot be the target of a REGISTER CATALOG or UNREGISTER CATALOG command. Cause. A REGISTER CATALOG or UNREGISTER CATALOG operation was attempted for the system catalog. Effect. The operation fails. Recovery. None. SQL 25431 25431 Node node runs a release of SLQ/MX that supports only SQL/MP tables.
19 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. 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. 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) HP NonStop SQL/MX Messages Manual—523730-004 19- 5
Rowsets Messages (30000 through 30999) HP NonStop SQL/MX Messages Manual—523730-004 19- 6
20 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 Table 20-1. SQLSTATE Values (page 1 of 85) SQLSTATE SQLCODE Error Text 00000 0 Successful completion 01001 8106 The last row fetched by this cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT... of statements. 01004 8402 A string overflow occurred during the evaluation of a character expression. 01006 1015 Some of the specified privileges could not be revoked. 01007 1012 No privileges were granted.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 2 of 85) SQLSTATE SQLCODE Error Text 0150P 1025 Request failed. One or more dependent objects exist. 0150Q 1026 Only the schema owner or super ID user can drop a schema. 0150R 1027 The definition schema-name is dropped when its catalog is dropped. 0150S 1028 The schema must be empty. It contains at least one object object-name. 0150T 1029 Object object-name could not be created.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 3 of 85) SQLSTATE SQLCODE Error Text 0151I 1054 Index table name already exists. 0151J 1055 Table, view, or stored procedure table name already exists. 0151L 1057 The DAM volume specified (name) is not available or is not audit protected. 0151M 1058 Lock table name already exists. 0151N 1059 Request failed. Dependent constraint name exists. 0151P 1061 Cannot drop metadata catalog name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 4 of 85) SQLSTATE SQLCODE Error Text 0152N 1095 The partition by column name should also be part of the clustering/storage key. 0152Q 1098 Duplicate partition key (name) specified for object name. 0152R 1099 Column num is unnamed. You must specify an AS clause for that column expression, or name all the columns by specifying a view column list. 0152S 1100 Unable to select table.schema.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 5 of 85) SQLSTATE SQLCODE Error Text 0153G 1124 Schema name is an unknown version. 0153H 1125 API request version number mismatch. 0153I 1126 Referential integrity is not yet supported. Constraint name will not be enforced. 0153J 1127 The specified table name is not a base table. Please verify that the correct table was specified. 0153K 1128 Invalid API request. Details: text.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 6 of 85) SQLSTATE SQLCODE Error Text 01544 1148 System-generated column name of base table name cannot appear in a referential integrity constraint definition. 01551 1181 Unable to drop object name (file error num). 01552 1182 Cannot instantiate constraint name, conflicting lock exists. 01553 1183 Cannot instantiate module name, conflicting lock exists. 01554 1184 Insufficient privilege on name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 7 of 85) SQLSTATE SQLCODE Error Text 01606 2006 Internal error: assertion failure (name) in file name at line num. 01608 2008 Internal error: out of virtual memory. 01609 2009 The user transaction must be rolled back (or committed, if that makes sense in the application) before MXCMP can be restarted and proceed. 0160A 2010 Internal IPC error. 0160B 2011 Unable to create server process.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 8 of 85) SQLSTATE SQLCODE Error Text 0160Y 2034 text: NonStop Kernel error num while communicating with server process name. 0160Z 2035 text: Unable to open process name (err no = num). 01611 2037 receiving process: A message from process sending process was incorrectly formatted and could not be processed. 0161E 2050 name is not the name of any DEFAULTS table attribute.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 9 of 85) SQLSTATE SQLCODE Error Text 0161X 2069 A static cursor declaration might appear only in the body of a procedure. 0161Y 2070 Invalid statement type in this context. 0161Z 2071 The name name has already been declared or defined in this module. The previous definition, as a name, is being retained and this latest one ignored.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 10 of 85) SQLSTATE SQLCODE Error Text 0162V 2103 Unable to compile this query for one/both of the following reasons: a) Use of 'MINIMUM' optimization level, or b) Incompatible Control Query Shape specifications.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 11 of 85) SQLSTATE SQLCODE Error Text 0170A 3010 Character set name is not yet supported. 0170B 3011 name is not a valid qualified name; it has more than 3 name parts. 0170C 3012 COUNT is the only aggregate function that accepts (*) as an operand. 0170D 3013 Subtraction is the only operation allowed in the parenthesized expression preceding an interval qualifier.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 12 of 85) SQLSTATE SQLCODE Error Text 0170Y 3034 The PARTITION clause in the ALTER TABLE statement is not yet supported. 0170Z 3035 The RENAME clause in the ALTER TABLE statement is not yet supported. 01710 3036 The SET CONSTRAINT clause in the ALTER TABLE statement is not yet supported. 01711 3037 Precision of type data type cannot exceed 18.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 13 of 85) SQLSTATE SQLCODE Error Text 0171R 3063 Duplicate DSLACK clauses in the PARTITION clause. 0171S 3064 Duplicate ISLACK clauses in the PARTITION clause. 0171T 3065 The primary key constraint cannot be droppable when the STORE BY PRIMARY KEY clause appears in a table definition. 0171V 3067 ALTER TABLE ADD CONSTRAINT allows only DROPPABLE constraints.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 14 of 85) SQLSTATE SQLCODE Error Text 0172J 3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. 0172K 3092 Duplicate BLOCKSIZE clauses. 0172L 3093 Duplicate DCOMPRESS clauses. 0172M 3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements. 0172N 3095 Duplicate [NO]ICOMPRESS clauses. 0172O 3096 Duplicate [NO]SERIALWRITES clauses.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 15 of 85) SQLSTATE SQLCODE Error Text 0173A 3118 Identifier too long. 0173B 3119 The WITH LOCAL CHECK OPTION clause is not supported. 0173C 3120 The CREATE ASSERTION statement is not yet supported. 0173D 3121 Partitioned entry-sequenced tables are not yet supported. 0173E 3122 The format of the system name part in the specified location name name is invalid.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 16 of 85) SQLSTATE SQLCODE Error Text 01744 3148 Environment variable name is being ignored because this version of the code is Release, not Debug. Actual query results will likely not match expected results. 01745 3149 Duplicate WITH CONSTRAINTS phrases in LIKE clause in CREATE TABLE statement. 01746 3150 Duplicate WITH HEADING phrases in LIKE clause in CREATE TABLE statement.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 17 of 85) SQLSTATE SQLCODE Error Text 0174V 3175 Dynamic SQL statements are not allowed in compound statements. 0174W 3176 Subqueries are not allowed in the IF Condition. 0174X 3177 Character set name requires an even number of characters in the length declaration of the data type.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 18 of 85) SQLSTATE SQLCODE Error Text 01806 4006 Within an aggregate, all column references must come from the same scope. 01807 4007 The select list index num is out of range. It must be between 1 and the number of select expressions, which in this case is num. 01808 4008 A subquery is not allowed inside an aggregate function. 01809 4009 An aggregate is not allowed inside an aggregate function.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 19 of 85) SQLSTATE SQLCODE Error Text 0180V 4031 Column name is an unknown data type, num. 0180W 4032 Column name is an unknown class, num. It is neither a system column nor a user column. 0180X 4033 Column name is a primary or clustering key column and cannot be updated. 0180Y 4034 The operation (name name name) name is not allowed. 0180Z 4035 Type name cannot be cast to type type.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 20 of 85) SQLSTATE SQLCODE Error Text 0181L 4057 Correlation name name conflicts with qualified identifier of table name. 0181N 4059 The first operand of function name must be numeric. 0181O 4060 Reading from and inserting into, or updating in, or deleting from the same table, name, is not currently supported. name is contained by view(s) name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 21 of 85) SQLSTATE SQLCODE Error Text 0182F 4087 Prototype value 'name' is not a valid qualified name. 0182G 4088 The number of values in each TRANSPOSE item of a TRANSPOSE set must be equal. 0182H 4089 Check constraint name contains a subquery, which is not yet supported. 0182L 4093 The number of output dynamic parameters (num) must equal the number of selected values (num).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 22 of 85) SQLSTATE SQLCODE Error Text 01836 4114 An absolute sample size must have a scale of zero. 01837 4115 The sample size must be less than or equal to the sample period. 01838 4116 The second operand of function name is invalid. 01839 4117 The cursor query expression might be nonupdateable. 0183A 4118 The cursor query expression is not updateable.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 23 of 85) SQLSTATE SQLCODE Error Text 0184F 4159 Intersection of stream expressions not supported. Tables in scope: name. 0184G 4160 Intersection between embedded name expression and embedded name expression not supported. Tables in scope: name, name. 0184H 4161 Union between embedded name expression and embedded name expression not supported. Tables in scope: name, name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 24 of 85) SQLSTATE SQLCODE Error Text 0185L 4201 Embedded type expression not supported for compound statements. 0185M 4202 SEQUENCE BY not supported for embedded type expressions. 0185N 4203 INSERT/UPDATE/DELETE operation on nonaudited table name requires index maintenance which might cause the index(es) to become corrupt. 0185O 4204 Stream access only supported for key-sequenced tables.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 25 of 85) SQLSTATE SQLCODE Error Text 0188G 4304 Host variable or dynamic parameter parameter-name is used in more than one OUT or INOUT parameter for routine routine-name. Results might be unpredictable. 0188H 4305 Parameter value for used defined routine routine-name is an OUT or INOUT parameter and must be a host variable or a dynamic parameter.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 26 of 85) SQLSTATE SQLCODE Error Text 01K09 8009 Schema name name is invalid. 01K0A 8010 Default catalog name: name. Default schema name: name. 01K0B 8011 SELECT statement inside compound (BEGIN ... END) statement returns more than one row. 01K0C 8012 Encoding of CONTROL QUERY DEFAULTs: name. 01K0D 8013 Trying to update or delete from a cursor that is not in the fetched state.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 27 of 85) SQLSTATE SQLCODE Error Text 01KBB 8407 The operand of function JULIANTIMESTAMP is out of range. 01KBD 8409 The escape character argument of a LIKE predicate must be one character in length. 01KBE 8410 An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 28 of 85) SQLSTATE SQLCODE Error Text 01KFW 8572 The statement has incurred a fatal error and must be deallocated. 01KFX 8573 The user does not have name privilege on table or view name. 01KFY 8574 An OPEN was blown away on table name. 01KFZ 8575 Timestamp mismatch on table name. 01KG0 8576 Statement was recompiled. 01KG1 8577 Table, index, or view name not found.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 29 of 85) SQLSTATE SQLCODE Error Text 01KMC 8804 The input statement provided does not exist in the current context. 01KMD 8805 Trying to action a descriptor that is not allocated with AllocDesc() call. 01KME 8806 Trying to action a statement that is not allocated with AllocStmt() call. 01KMF 8807 Trying to allocate more than num entries for a descriptor.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 30 of 85) SQLSTATE SQLCODE Error Text 01KN4 8832 Transaction has not been started. 01KN5 8833 The input parameter is an invalid SQL transaction command. 01KN6 8834 Unable to find NonStop SQL installation directory. Operating system error num. 01KN7 8835 Invalid SQL descriptor information requested. 01KN8 8836 Invalid update column for cursor. 01KN9 8837 Invalid user id.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 31 of 85) SQLSTATE SQLCODE Error Text 01KNU 8858 The value:(num) passed in through input a host variable/parameter is an invalid SQL identifier 01KNV 8859 There are pending insert, delete, or update operations. 01KNW 8860 Module file name has obsolete module header. 01KNX 8861 Module file name has obsolete descriptor location table header.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 32 of 85) SQLSTATE SQLCODE Error Text 01KOX 8897 RPC exception in CLI request from non-trusted shadow client to trusted shadow server. 01KOY 8898 Internal error in CLI. 01KP1 8901 The MXUDR server for this statement is no longer running. The statement will be assigned a new MXUDR server if it is executed again. 01KP2 8902 Internal error: MXUDR returned an invalid UDR handle.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 33 of 85) SQLSTATE SQLCODE Error Text 01L5X 9213 If you intend to update histogram statistics for columns, you must specify a column group list in the statement. 01L5Y 9214 Unable to CREATE object name. 01L5Z 9215 UPDATE STATISTICS encountered an internal error (location).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 34 of 85) SQLSTATE SQLCODE Error Text 01N2V 11103 MXUDR: Invalid routine handle: string. 01N2W 11104 MXUDR: CLI Error: error-text. 01N2X 11105 MXUDR: Invalid Language Manager param mode. Parameter parameter-value. 01N30 11108 MXUDR: Unable to allocate memory for object object-name. 01N32 11110 MXUDR: Unexpected error during message processing: string. 01N33 11111 MXUDR: Internal error: value.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 35 of 85) SQLSTATE SQLCODE Error Text 01N61 11217 Java execution: Data overflow occurred while retrieving data at parameter position parameter number. Value is truncated. 01N62 11218 A Java method completed with an uncaught Java exception. Details: string. 01N63 11219 A Java method completed with an uncaught java.sql.SQLException. Details: string.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 36 of 85) SQLSTATE SQLCODE Error Text 01P0F 13015 Unable to open the module definition file name. 01P0G 13016 Descriptor name name conflicts with SQLC default name name. 01P0H 13017 Descriptor name is multiply defined. 01P0I 13018 Descriptor name name is invalid. 01P0J 13019 Statement name name uses name, a reserved name SQLC generates. 01P0K 13020 Statement name name is multiply defined.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 37 of 85) SQLSTATE SQLCODE Error Text 01P18 13044 Type specification type is not a recognized type near line num. 01P19 13045 Unexpected class declaration near line num ignored. 01P1A 13046 Expecting “}” to end member declaration near line num. 01P1B 13047 Undefined tag name near line num. 01P1C 13048 Tag name redefined near line num. 01P1D 13049 Input file not good near line num.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 38 of 85) SQLSTATE SQLCODE Error Text 01P22 13074 One or more of the first three parts of the externally qualified module name module-name is longer than 128 characters. 01P23 13075 Externally qualified module name module-name is not a Regular Identifier, or is longer than 248 characters. 01P24 13076 Catalog name catalog-name is not a valid OSS file name, or is longer than 128 characters.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 39 of 85) SQLSTATE SQLCODE Error Text 01PEK 13524 DECLARE SECTION encountered in unexpected program section. 01PEL 13525 Variable name might not be allocated correctly for a host variable. 01PEM 13526 Line num, name: name clause is not valid for a host variable. 01PEN 13527 The first declaration in an SQL DECLARE SECTION must have level 01 or 77.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 40 of 85) SQLSTATE SQLCODE Error Text 01R0N 15023 The USING list value name exceeds the SQLCI limit of num characters. 01R0O 15024 The USING list quoted literal name must be followed by either a comma or a semicolon. 01R0P 15025 Cursor operations are not supported by SQLCI. 01R0Q 15026 Break rejected. 01R0S 15028 Break error. 01R0U 15030 The specified define already exists.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 41 of 85) SQLSTATE SQLCODE Error Text 01U09 30009 Internal error. Trying to add more elements than maximum rowset size. 01U0A 30010 Internal error. Rowset is corrupted. 01U0B 30011 More than one INTO statement in the same query is not supported. 01U0C 30012 Rowset index name must be specified last in the derived column list of name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 42 of 85) SQLSTATE SQLCODE Error Text 01Z8L 25309 Module module can be executed only by a node with SQL/MX software version (MXV) version1, the MXV of node is MXV1. 01Z8M 25310 Module module has module version version1, the local SQL/MX software version (MXV) can only execute modules with module version MXV1. 01Z8N 25311 System module module has a wrong module version.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 43 of 85) SQLSTATE SQLCODE Error Text 0A000 -1126 Referential integrity is not yet supported. Constraint name will not be enforced. 0A000 -1142 Attempting to add a column with a NULL, UNIQUE, CHECK, PRIMARY KEY, or FOREIGN KEY constraint defined. This is not supported for a nonaudited table. 0A000 -13003 This feature is unsupported. 0A000 -13034 Character set name is not yet supported.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 44 of 85) SQLSTATE SQLCODE Error Text 0A000 -3105 Currently only range, hash and system partitioning are supported. 0A000 -3119 The WITH LOCAL CHECK OPTION clause is not supported. 0A000 -3120 The CREATE ASSERTION statement is not yet supported. 0A000 -3121 Partitioned entry-sequenced tables are not yet supported. 0A000 -3130 UNSIGNED option is not supported for LARGEINT type.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 45 of 85) SQLSTATE SQLCODE Error Text 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. 22007 -8415 The provided DATE, TIME, or TIMESTAMP is not valid and cannot be converted.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 46 of 85) SQLSTATE SQLCODE Error Text 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 20-1. SQLSTATE Values (page 47 of 85) SQLSTATE SQLCODE Error Text 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. 26000 -8804 The input statement provided does not exist in the current context. 26000 -8806 Trying to action a statement that is not allocated with AllocStmt() call.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 48 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3201 EXTERNAL PATH clause is required. 42000 -3202 PARAMETER STYLE clause is required. 42000 -3203 LANGUAGE clause is required.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 49 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -2056 The value must be a number in the range num.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 50 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -2093 A module timestamp statement was not found in file name. 42000 -2094 A module timestamp statement has already appeared in this module.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 51 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3015 Scale value cannot exceed precision value.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 52 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3057 Invalid size value in the ALLOCATE clause. 42000 -3058 The BLOCKSIZE value must be 4096. 42000 -3059 Invalid size value in the MAXSIZE clause.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 53 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. 42000 -3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ...
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 54 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3117 Duplicate DIAGNOSTICS SIZE specified. 42000 -3118 Identifier too long.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 55 of 85) SQLSTATE SQLCODE Error Text 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. 42000 -3157 Catalog name is required.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 56 of 85) SQLSTATE SQLCODE Error Text 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. Default schema: name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 57 of 85) 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 20-1. SQLSTATE Values (page 58 of 85) 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 20-1. SQLSTATE Values (page 59 of 85) 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 20-1. SQLSTATE Values (page 60 of 85) 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 20-1. SQLSTATE Values (page 61 of 85) SQLSTATE SQLCODE Error Text Condition: SQLJ-specific error. Subcondition: (no subclass). For information about the corresponding SQLJ 46000 run-time error messages, see the SQL/MX Programming Manual for Java. 46007 -11208 Specified signature is invalid. Reason: The list of parameter types must be enclosed in parentheses. 46007 -11209 Specified signature is invalid.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 62 of 85) SQLSTATE SQLCODE Error Text HY011 -8857 Statement attribute cannot be set now. INPUT_ARRAY_MAXSIZE must be set before compiling the statement. HY024 -8854 Invalid attribute value. HY024 -8856 Invalid attribute value. INPUT_ARRAY_MAXSIZE must be positive. HY092 -8853 Invalid attribute definition. X0101 -1001 An internal error occurred in module name on line num. DETAILS(text).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 63 of 85) SQLSTATE SQLCODE Error Text X010Z -1035 Catalog name already exists. X0110 -1036 Only the super ID can execute DROP SQL. X0111 -1037 SQL is not installed on system name. X0112 -1038 All catalogs have not been dropped from the system. X0113 -1039 Unable to drop SQL. X0114 -1040 Cannot alter metadata table. X0115 -1041 The primary key has already been defined.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 64 of 85) SQLSTATE SQLCODE Error Text X011Y -1070 Unable to create object name (file error num). X011Z -1071 Unable to access object name (file error num). X0120 -1072 Unique constraint name is disabled; cannot create foreign key constraint name. X0121 -1073 Only the super ID user can execute INITIALIZE SQL. X0123 -1075 Catalog name contains at least one schema. The catalog must be empty.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 65 of 85) SQLSTATE SQLCODE Error Text X0130 -1108 The number of columns specified in the view column list, num, does not match the degree of the query expression, num. X0131 -1109 The WITH CHECK OPTION clause appears in the definition of view name, but the view is not updateable. X0136 -1114 Unable to create catalog name metadata tables on name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 66 of 85) SQLSTATE SQLCODE Error Text X013Z -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: name X0140 -1144 Expected a quoted string in first key clause for column name on table name, value detected is (name).
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 67 of 85) SQLSTATE SQLCODE Error Text X0201 -2001 Error or warning num occurred while opening or reading from DEFAULTS table name. Using name values. X0202 -2002 Internal error: cannot create MXCMP server. X0203 -2003 Internal error: cannot establish connection with MXCMP server. X0204 -2004 Internal error: error from MXCMP; cannot work on this query.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 68 of 85) SQLSTATE SQLCODE Error Text X020S -2028 Unable to create OSS server process name. Insufficient resources. X020T -2029 Unable to create OSS server process name. OSS is not running. X020U -2030 Unable to create server process name via inetd (err no = num). X020X -2033 text: NonStop Kernel error num while communicating with process name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 69 of 85) SQLSTATE SQLCODE Error Text X022U -2102 Unable to compile this query with 'MINIMUM' optimization level. Suggestion: Retry with 'MEDIUM' optimization level. X022V -2103 Unable to compile this query for one/both of the following reasons: a) Use of 'MINIMUM' optimization level, or b) Incompatible Control Query Shape specifications.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 70 of 85) SQLSTATE SQLCODE Error Text X0449 -4153 Statement might not compile due to an order requirement on stream expression. X044A -4154 Statement might not compile due to an order requirement on embedded name expression. X044B -4155 Secondary indexes don't support order requirement. Table: name. X044D -4157 Inner relation of left join cannot be stream expression. Tables in scope: name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 71 of 85) SQLSTATE SQLCODE Error Text X044W -4176 Join between stream expression and embedded name expression not supported. Tables in scope: name. X044X -4177 Update of name column name not permitted on rollback. X044Y -4178 Update of variable length column name not permitted on rollback. X044Z -4179 SEQUENCE BY not supported for stream expressions.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 72 of 85) SQLSTATE SQLCODE Error Text X045Z -4215 Stream access is not allowed on a nonaudited table. Table: name. X0460 -4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded DELETE statement. X0461 -4217 X048C -4300 Invalid usage of procedure procedure-name - A UDR was invoked within a trigger.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 73 of 85) SQLSTATE SQLCODE Error Text X0803 -8003 The descriptor is locked by another nowaited operation. X0806 -8006 The stream timed out, but the cursor is still open. X0807 -8007 The operation has been canceled. X080A -8010 Default catalog name: name. Default schema name: name. X080B -8011 SELECT statement inside compound (BEGIN ... END) statement returns more than one row.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 74 of 85) SQLSTATE SQLCODE Error Text X08OI -8882 Containing SQL not permitted. X08OJ -8883 The current context has violation checking functions disabled. Use SQL_EXEC_SetUdrAttributes_Internal() to enable it. X08OU -8894 Argument argument-name of CLI function function-name is reserved for future use and must be set to string when calling the function. X083W -8140 Prohibited SQL statement attempted.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 75 of 85) SQLSTATE SQLCODE Error Text X08GQ -8602 The file system reported error num on a lock/unlock operation. X08JG -8700 An assertion failure or out-of-memory condition occurred during parallel execution. X08JQ -8710 Error num returned by Measure when attempting to update SQL counters. X08MG -8808 Module file name contains corrupted or invalid data.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 76 of 85) SQLSTATE SQLCODE Error Text X08NN -8851 CLI Parameter bound check error. X08NO -8852 Holdable cursors are only supported for streaming cursors and embedded UPDATE/DELETE cursors. X08NU -8858 The value: (num) passed in through input a host variable/parameter is an invalid SQL identifier X08NV -8859 There are pending insert, delete, or update operations.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 77 of 85) SQLSTATE SQLCODE Error Text X095R -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. X095S -9208 Unable to access column definitions. X095T -9209 Column name name does not exist in the table.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 79 of 85) SQLSTATE SQLCODE Error Text X0B66 -11222 Specified signature is invalid. Reason: Unknown parameter type used at position value. X0B67 -11223 Language Manager encountered internal error detail text. X0B68 -11224 JVM raised an exception. Details: detail text. X0B69 -11225 Specified signature is invalid. Reason: Unknown or unsupported type used as a return type.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 80 of 85) SQLSTATE SQLCODE Error Text X0D0J -13019 Statement name name uses name, a reserved name SQLC generates. X0D0K -13020 Statement name name is multiply defined. X0D0L -13021 name is already defined. X0D0M -13022 Cursor name is already defined. X0D0N -13023 name is already defined as a dynamic cursor. X0D0O -13024 Cursor name was not declared.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 81 of 85) SQLSTATE SQLCODE Error Text X0D1H -13053 Cursor name not opened or closed. X0D1I -13054 Cursor name not fetched or closed. X0D1J -13055 Cursor name not opened or fetched. X0D1K -13056 Cursor name not used. X0D1L -13057 End-of-file processing generated unexpected cursor status of num for cursor name. X0D1M -13058 Unable to open SQL CLI header file name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 82 of 85) SQLSTATE SQLCODE Error Text X0DDZ -13503 Missing filename for command option name. X0DE0 -13504 Missing timestamp command option. X0DE1 -13505 Source input file name cannot be opened. X0DE2 -13506 COBOL output source file name cannot be opened. X0DE3 -13507 Error while parsing source: name. X0DE4 -13508 Expecting name, found name. X0DE5 -13509 Expecting name after name, found name.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 83 of 85) SQLSTATE SQLCODE Error Text X0F04 -15004 Error num on change directory attempt to name. X0F06 -15006 Error num while reading from file. X0F07 -15007 Error num while opening file name. X0F08 -15008 The specified statement does not exist in the history buffer. X0F09 -15009 The requested help topic is too long. X0F0A -15010 The help file could not be opened.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 84 of 85) SQLSTATE SQLCODE Error Text X0P01 -25001 Program executable, executing on node, has encountered a version error. X0P2S -25100 Remote node node runs an incompatible version of SQL/MX software. The SQL/MX software version (MXV) of node is MXV1, the local node does not support MXVs older than MXV2. X0P2T -25101 Remote node node runs an incompatible version of SQL/MX software.
SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 20-1. SQLSTATE Values (page 85 of 85) SQLSTATE SQLCODE Error Text X0U0D -30013 Hostvar used to set input size of rowset has zero or negative value. X0U0E -30014 Hostvar used to set input size of rowset is not of type short, int, or long. X0U0K -30020 Embedded UPDATE/DELETE cannot be used with SELECT...INTO and rowset. XW02S -100 The “no data” completion condition (SQLCODE = +100). XW10C -1012 No privileges were granted.
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 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. SQL/MX is installed on the system, but it is the wrong version. Effect. The operation fails. Recovery. Install 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 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. (Verify that this is correct.) Recovery. None. This message is a warning.
Non-SQLCODE Error Messages MXGNAMES Utility migr0022 migr0022: The ERROR_LOG option was chosen without a specified filename. The filename has defaulted to error_log.out. Cause. A file name was not specified in the SHOW SCRIPT option. Effect. None. The file name defaults to script.out. Recovery. None. This message is a warning. migr0023 migr0023: The SHOW SCRIPT option was chosen without a specified filename. The filename has defaulted to script.out. Cause.
Non-SQLCODE Error Messages • • • • MXGNAMES Utility MXGNAMES0000: Program errors MXGNAMES0002: File errors MXGNAMES0003: SQL errors MXGNAMES0004: Command-line errors MXGNAMES0000 MXGNAMES0000: Program error: Insufficient memory to allocate object object. Program terminating. Cause. MXGNAMES failed to allocate memory needed for execution. Effect. The operation fails. Recovery. Determine the memory usage on the system and, if necessary, contact your service provider.
Non-SQLCODE Error Messages MXGNAMES Utility MXGNAMES0003 MXGNAMES0003: SQL error: Prepare statement error occurred: 15001. Cause. MXGNAMES was unable to prepare the query necessary to retrieve the table information. Effect. MXGNAMES proceeds to the next table, if any. Recovery. Make sure that the input list of table names specified for the SQLNames option is properly formatted. If this does not correct the problem, contact your service provider.
Non-SQLCODE Error Messages MXGNAMES Utility 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. Remove the duplicate option and resubmit. MXGNAMES0004 MXGNAMES0004: Command line error: Missing or invalid value for option option. Cause. Either you omitted a value or specified an invalid value for an option that requires a value. Effect. The operation fails. Recovery.
Non-SQLCODE Error Messages HP NonStop SQL/MX Messages Manual—523730-004 A -14 MXGNAMES Utility
