HP Neoview Messages Manual HP Part Number: 544796-001 Published: April 2008 Edition: HP Neoview Release 2.
© Copyright 2008 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................7 Supported Releases.................................................................................................................................7 Audience.................................................................................................................................................7 ODBC and JDBC Messages..........................................
12 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399).............................................................................................................................217 13 Materialized Views Messages (12000 Through 12329)......................................229 14 Messages Generated by the Message System (16000 Through 16999)...........243 15 Internal Stored Procedures Messages (19000 Through 19999).........................245 16 Utility Messages (20000 Through 23099)....
List of Tables 24-1 24-2 24-3 24-4 24-5 24-6 24-7 24-8 24-9 24-10 SQLSTATE Values Beginning 00000............................................................................................416 SQLSTATE Values Beginning 01700............................................................................................423 SQLSTATE Values Beginning 01800............................................................................................429 SQLSTATE Values Beginning 01I01.................................
About This Document HP Neoview database 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 describes messages produced by the HP Neoview data warehousing platform and its associated subsystems. Supported Releases This manual supports Neoview Release 2.3 and subsequent Neoview releases until otherwise indicated in a replacement publication.
Chapter (page) Description Messages Added and Changed Chapter 16 (page 247) “Utility Messages (20000 Through 23099)” 20002, 20007, 20028, 20037, 20501, 20504–20514, 20517, 20519, 20522, 20524–20529, 20531–20533, 20535–20539, 20541, 20549, 20550, 20553, 20555, 20556, 20562, 20563, 20565–20568, 21001, 21004–21013 Chapter 17 (page 309) “Security Interface Messages (24000 Through 24000–24050 24499)” Chapter 18 (page 317) “Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Throug
Chapter Title Chapter 18 (page 317) “Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29399)” Chapter 19 (page 333) “Neoview Command Interface (NCI) Messages (29400 Through (29599)” Chapter 20 (page 345) “Rowsets Messages (30000 Through 30999)” The last chapters of this manual list messages of these Neoview components: Chapter Title — Use Chapter 21 (page 351) “Neoview Data Warehouse Manager Messages” — Look up these messages in numeric order.
pathname Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: DAY (datetime-expression) @script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "{" module-name [, module-name]... "}" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
[ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
Neoview Database Administrator’s Guide Information about how to load and manage the Neoview database by using the Neoview DB Admin and other tools. Neoview DB Admin Online Help Context-sensitive help topics that describe how to use the HP Neoview DB Admin management interface. Neoview Guide to Stored Procedures in Java Information about how to use stored procedures that are written in Java within a Neoview database.
ODBC Client Administrator Online Help Context-sensitive help topics that describe how to use the ODBC client interface.
Publishing History Part Number Product Version Publication Date 543440-002 HP Neoview Release 1.0 August 2006 543643-001 HP Neoview Release 1.2 November 2006 543766-001 HP Neoview Release 2.0 March 2007 544563-001 HP Neoview Release 2.2 August 2007 544796-001 HP Neoview Release 2.3 April 2008 You can find this manual or its replacement on line with the HP Business Intelligence Solutions technical documentation at: http://www.docs.hp.com/en/busintellsol.
1 Message Handling The Neoview database software reports exception condition messages at the HP Neoview Database Connectivity Service conversational interface (NDCS) window. Most Neoview database software exception condition messages describe error conditions for which recovery action is required. Some messages are warnings that provide information for which no action is required.
value for all Neoview database software messages other than those for which an ANSI SQL-92 SQLSTATE value exists. The SQLCODE parameter is a deprecated feature that is supported to maintain compatibility with earlier versions of the American standard. Tables in “SQLSTATE Values” (page 415) identify the equivalent SQLSTATE and SQLCODE values for Neoview database software warning and error messages.
2 Data Definition Language (DDL) Messages (1000 Through 1999) SQL 1001 1001 An internal error occurred in module name on line num. DETAILS(details). name num details Cause Effect is the name of the module. is the line number. are the details of the error. This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
constraint-name is the name of a column constraint or table constraint. Cause The ALTER TABLE statement you attempted requires the existence of a constraint named constraint-name. Effect The operation fails. Recovery Check that a constraint named constraint-name exists for the table specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table. SQL 1006 1006 Index index-name does not exist. index-name is an HP Neoview database object name.
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 The HP Neoview database 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 Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1020 1020 Privilege settings on metadata cannot be changed. Cause You attempted to change privilege settings on a metadata schema or table. They cannot be changed. Effect The HP Neoview database software does not change the settings. Recovery None.
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 The HP Neoview database software does not perform the operation. Recovery For DROP statements that support the CASCADE drop-behavior, you can reissue the statement specifying CASCADE.
is the name of an HP Neoview database file. is a file-system error number. file name error Cause Effect See the accompanying error message for the cause. The operation fails. Recovery For information about file-system errors, see Chapter 25 (page 481). SQL 1031 1031 Object object-name could not be dropped. object-name Cause Effect is the SQL object. See the accompanying error message for the cause. The HP Neoview database software does not drop the object.
Effect Recovery The operation fails. You must drop all user-created catalogs before dropping SQL. SQL 1039 1039 The DROP SQL statement could not be executed. Cause Effect Recovery See the accompanying error message for the cause. The HP Neoview database software does not drop SQL. Apply the recovery of the accompanying error message. SQL 1040 1040 The use of ALTER on metadata tables is not permitted.
Recovery Check that constraint-name references a unique or primary constraint in the referenced table. SQL 1046 1046 Referenced and referencing column lists do not match for constraint constraint-name. 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.
SQL 1051 1051 You do not have the required privilege(s) on object-name. is the name of the object for which you have insufficient privileges. object-name Cause Effect You have insufficient privileges to create a view or a trigger. The operation fails. Recovery See the Neoview SQL Reference Manual for the required security needed to create a view or trigger. SQL 1053 1053 Unique index index-name could not be created because the specified column(s) contain duplicate data.
SQL 1061 1061 Dropping metadata catalog catalog-name is not allowed. is the name of an HP Neoview database catalog. catalog-name Cause Effect You attempted to drop a catalog that is part of the HP Neoview database metadata. The operation fails. Recovery None. SQL 1062 1062 Dropping metadata schema schema-name is not allowed. is the name of an HP Neoview database metadata schema. schema-name Cause Effect You attempted to drop a schema that is part of the Neoview database metadata. The operation fails.
SQL 1069 1069 Schema schema-name could not be dropped. is the name of an HP Neoview database schema. schema-name Cause Effect See the accompanying error message for the cause of the problem. The operation fails. Recovery Apply the recovery action from the accompanying error message. SQL 1070 1070 Object object-name could not be created. File error: error-number. object-name error-number is the name of the HP Neoview database object. is the file-system error number.
Cause Effect Recovery An attempt was made to drop a catalog that is not empty. The catalog is not dropped. None of its schemas are dropped. Drop all schemas in the catalog and resubmit. SQL 1077 1077 Metadata table table-name does not contain information for view view-name. table-name view-name is the name of the metadata table. is the name of a view. Cause HP Neoview database software required metadata information about object view-name but was unable to find it in table-name.
SQL 1082 1082 Validation for constraint constraint-name failed unexpectedly. constraint-name is the name of a column or table constraint. Cause The constraint validation failed, either because a concurrent operation was being performed on the table or on the referenced table (for a referential integrity constraint), or data in the table violates the constraint. Effect The constraint operation fails.
SQL 1088 1088 The system generated column SYSKEY must be specified last or not specified at all in the STORE BY column list. Cause If the system-generated column SYSKEY is specified in the STORE BY list of columns, it must be specified last. Effect Recovery The operation fails. Correct the STORE BY clause and resubmit. SQL 1089 1089 The system generated column SYSKEY must be specified last or not specified at all in the index column list.
SQL 1098 1098 Partition key (key) already specified for object object-name. is a partition key. is the name of the table being created or changed. key object-name Cause You attempted to create or change a table so that more than one partition has the same first key. Effect The operation fails. 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.
SQL 1103 1103 Rows could not be deleted from table table-name. table-name Cause Effect is the ANSI name of the metadata table. For clarification, see the accompanying error message. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1104 1104 Default value string is too long for column column-name.
SQL 1109 1109 The WITH CHECK OPTION clause appears in the definition of view view-name, but the view is not updatable. is the name of the view being created. view-name Cause You used WITH CHECK OPTION in the definition of a view that is not updatable. Effect The operation fails. Recovery Either make the view updatable or omit the WITH CHECK OPTION and resubmit. SQL 1110 1110 text. text is the message text return about the error. Cause Effect This is an internal error. The operation fails.
Cause The MODIFY utility could not create the target partition because the specified volume in the LOCATION clause does not exist. Effect Recovery The MODIFY utility did not process the request. None. SQL 1116 1116 The current partitioning scheme requires a user-specified clustering key on object table-name. table-name Cause Effect is the name of the table. The partitioning scheme requires a user-specified clustering key. The operation fails.
SQL 1121 1121 Partitions cannot be added or dropped on table table-name. These partition operations are not allowed on tables whose clustering key consists only of the SYSKEY. table-name is the name of the table. Cause You attempted to do an invalid ADD, DROP, or MODIFY of a partition. Effect The operation fails. Recovery None. SQL 1122 1122 The number of specified partition key values (partition-key-value-list) for object object-name exceeds the number of user defined key columns, key-col-number.
SQL 1128 1128 An invalid API request was encountered. Details: description. description Cause Effect is text further explaining the problem. Internal error. HP Neoview database software is unable to perform the requested operation. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1130 1130 The column requires a default value.
Recovery Specify that the column-name is NOT NULL NOT DROPPABLE and resubmit. SQL 1136 1136 For an added column, the PRIMARY KEY clause cannot specify NOT DROPPABLE. Cause You used the ALTER TABLE statement to add a column specifying a primary key that is not droppable. A primary key added through ALTER TABLE must be droppable. Effect Recovery key. The operation fails. Change the ALTER TABLE statement to specify DROPPABLE for the primary SQL 1137 1137 An internal error occurred: invalid index status.
Recovery See the Neoview SQL Reference Manual for row size limit calculations. Change the column definitions and reissue the statement. SQL 1141 1141 Label file-name for object could not be accessed. File system error error-number. file-name error-number Cause Effect Recovery is the HP Neoview platform file name of a partition of object. is a Neoview platform file-system error. An ALTER TABLE or ALTER INDEX operation encountered a file-system error. The operation fails.
Recovery Correct the value first-key-string to be a type that is compatible with the type of column column-name and resubmit. SQL 1145 1145 The catalog name catalog-name is reserved for SQL/MX metadata. catalog-name Cause Effect is the name of an HP Neoview database catalog. The Neoview database software reserves certain catalog names for its own use. The operation fails. Recovery See the Neoview SQL Reference Manual for reserved names. Change catalog-name to a name that is not reserved and resubmit.
Cause When the Partition Overlay Support (POS) feature is enabled without setting volume names (through POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, the HP Neoview database software could not generate the location names automatically and, because the POS_RAISE_ERROR is set, the table is not created. Effect Recovery • • • The operation fails.
SQL 1156 1156 Synonym name does not exist or object type is invalid for the current operation. Cause view. Effect Recovery You specified a create or alter of synonym name on an object that is not a table or The operation fails. Correct the syntax so that the correct name is used. SQL 1157 1157 Synonym object name is the same as previous mapping. Cause You specified an alter of synonym on an object name, which is the same as its previous mapping. Effect Recovery The operation succeeds with a warning.
Cause The HP Neoview database software could not create the object because system-generated column SYSKEY is not allowed as part of the PARTITION BY clause. Effect The DDL operation fails. Recovery Remove the system added column SYSKEY from the PARTITION BY clause and retry the DDL statement. SQL 1162 1162 User authid already owns object. Operation ignored. authid object Cause Effect Recovery is the target of the GIVE operation. is the CATALOG whose ownership is changing.
SQL 1168 1168 Internal error: unable to find object associated with UID uid. uid is the unique ID assigned to the object in metadata. Cause Effect Object not found by the specified UID. The operation fails. Recovery Contact the GMCSC to help in determining why the internal error occurred. SQL 1169 1169 Schema privileges for schema schema have not been enabled. schema Cause Effect is the name of the schema. A GRANT or REVOKE of schema level privileges was requested. The operation fails.
Recovery See previous messages in this HP Neoview database software operation to determine the necessary corrective actions. Also, use the file-system error error-number to analyze the cause. For information about file-system errors, see Chapter 25 (page 481). Fix the error and resubmit. SQL 1182 1182 Error error was returned by the file system on resource fork file name. is the error returned. is the name of the file. error file name Cause File-system error. Effect The operation fails.
Effect The operation fails. Recovery Change either the column data type or the value for the default to be compatible types and resubmit. SQL 1187 1187 The schema name schema-name is reserved for SQL/MX metadata. schema-name Cause Effect is the name of an HP Neoview database schema. The Neoview database software reserves certain schema names for its own use. The operation fails. Recovery See the Neoview SQL Reference Manual for reserved schema names.
SQL 1231 1231 User-defined routine procedure-name could not be created. procedure-name is the stored procedure’s ANSI name. Cause The stored procedure could not be created. Effect The CREATE PROCEDURE statement fails. 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 platform-pathname.
Recovery created. Specify a schema name for the object that matches the name of the schema being SQL 1238 1238 The character set used in 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 Recovery The operation fails. Specify only ISO88591 literals in the command. SQL 1239 1239 The character set used for string literals in VIEW must be ISO88591.
key-value column-name object-name Cause Effect Recovery is the specified first key value. is the column of object-name that corresponds to the invalid key value. is the name of the affected object. A utility command specified an invalid key value. The operation fails. 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.
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. value column-name is the default value that was specified for column-name. is the name of the column in the table. Cause A CREATE TABLE or ALTER TABLE...ADD COLUMN specified a default value with a scale greater than the scale of the column.
Cause You attempted a DDL or utility operation on a database object while operation was in progress for that object’s schema. Effect The DDL or utility operation fails. Recovery Wait until the operation has finished, and then retry the DDL or utility operation. SQL 1263 1263 Object names that start with text are reserved for SQL/MX metadata. text is the disallowed name that was specified. Cause Effect You specified an HP Neoview database reserved object name. The object is not created.
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 sql object-name due to file error file-system error-number on filename. sql object-name file-system error-number is the ANSI name of the affected SQL database object. is an HP Neoview platform file-system error code.
SQL 1275 1275 Constraint constraint1 cannot be dropped because it is needed by unique constraint constraint2. constraint1 constraint2 is the constraint you are trying to drop. is the UNIQUE constraint. Cause You attempted to drop a constraint that is needed by a UNIQUE constraint, which is not allowed because it would leave a UNIQUE constraint on a column, but without a NOT NULL constraint for that column. Effect The operation fails.
Cause Effect Recovery Cannot create a volatile index on a regular nonvolatile object. None. Either create a nonvolatile index or make sure that the base object is volatile. SQL 1280 1280 A regular DDL statement cannot be used on volatile objects. Cause Effect Recovery Cannot create a regular index on a volatile object. None. Either create a volatile index or make sure that the base object is not volatile. SQL 1284 1284 Table table-name cannot be dropped because it was specified to be NOT DROPPABLE.
Cause An unanticipated error occurred on a metadata read operation for a stored procedure. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1301 1301 NO ACTION referential action for referential-triggered-action clause is not yet supported as specified by ANSI SQL99 standard.
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. Effect The statement fails unless it includes the optional REUSE clause to allow reuse of the same schema subvolume name. If the REUSE clause is used, this is a warning message and the schema is created successfully.
Recovery Remove the creation of triggers from the CREATE SCHEMA statement and resubmit. Create triggers in separate statements. SQL 1311 1311 Unable to action-text constraint constraint-name due to the above errors. action-text constraint-name is create. is a constraint name. Cause An error occurs during the creation of the constraint. The error that described the cause of the failure already appears. This error message provides clarification. Effect The operation fails.
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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1501 1501 The OBJECTS - MP_PARTITIONS definition schema relationship for type object may be corrupt. type object is the type of the affected object.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1506 1506 The system schema metadata for schema schema is inconsistent between nodes node1 and node2. schema node1 and node2 is the fully qualified schema name that is mentioned by the current DDL or utility operation. are two clusters on which schema is visible.
SQL 1517 1517 Constraint constraint on table table is NOT DROPPABLE. You cannot disable NOT DROPPABLE constraints. constraint table Cause Effect Recovery is the name of the constraint. is the name of the table. The specified constraint is defined as NOT DROPPABLE and cannot be disabled. The operation failed. No recovery is available. SQL 1518 1518 Constraint constraint was not enabled because it requires index index which is disabled. constraint index is the name of the constraint being enabled.
3 Neoview Compiler 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. number name values is the error number. is the DEFAULTS table name. is the default values file. Cause The HP Neoview database software was unable to open system defaults table name because of error number.
SQL 2006 2006 Internal error: assertion failure (detail text) in file name at line number. detail text name number is information about the error. is the name of the file. is the line number. Cause The HP Neoview database software received an internal error in file name at line number. More information is in detail text. Effect The operation fails. Recovery Do not attempt recovery.
SQL 2012 2012 Server process name could not be created on node - Operating system error number-1, TPCError = number-2, error detail = text. (See Operating system procedure PROCESS_LAUNCH_ for details). name number-1 number-2 text is the name of the server process. is the error number. is the TPCError. is the error message text. Cause The HP Neoview database software was unable to create server process name because of the process control procedure error number it received.
SQL 2016 2016 Server process name was started but had undefined externals. name is the server process name. Cause The HP Neoview database software started server process name, but it had undefined externals. Effect None. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 2017 2017 Server process name could not be created on node- no more processes (PCBs) available.
Effect The operation fails. Recovery The server process must be a licensed privileged program. Check your configuration. SQL 2021 2021 System error number occurred in procedure name from process name. number procedure name process name Cause Effect is the error number. is the name of the procedure. is the server process name. The HP Neoview database software received an internal error. The operation fails. Recovery Do not attempt recovery.
SQL 2025 2025 Server process name could not be created - CPU is unavailable; process id. name process id is the server process name. identifies the process. Cause The HP Neoview database software was unable to create server process name because the node is unavailable or does not exist. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 2033 2033 process id: Operating system error number while communicating with process name. process id number name identifies the process. is the error number. is the name of the server process. Cause The HP Neoview database process id received process control procedure error number while communicating with the server process name. Effect The Neoview database software is not able to communicate with the process. Recovery Use the process control procedure error to diagnose and correct the problem.
Effect The operation fails. Recovery Specify an ISO88591 character set name. SQL 2050 2050 attribute is not the name of any DEFAULTS table attribute. is the attribute name you specified. attribute Cause If the SQLSTATE is 42000, this is an error. You attempted to set a CONTROL QUERY DEFAULT setting, but the attribute name you specified is not valid. If the SQLSTATE is 01000, this is a warning.
Cause You attempted to set the CQD HIST_NO_STATS_ROWCOUNT value as less than the current value of CQD HIST_NO_STATS_UEC. Effect The current value of the HIST_NO_STATS_ROWCOUNT is retained. Recovery Set the value of CQD HIST_NO_STATS_ROWCOUNT greater than or equal to the value of HIST_NO_STATS_UEC. If you want to use a smaller value, reduce the value of CQD HIST_NO_STATS_UEC first. Note that any change in either of the two values can have an effect on the plan quality.
SQL 2060 2060 Procedure name has already been defined in this module. The previous definition is being retained and this latest one ignored. name is the procedure name. Cause You defined procedure name twice in this module. Effect The HP Neoview database software 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.
name name is the statement name. is the module name. Cause The HP Neoview database software could not find statement name in module name. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 2066 2066 Cursor cursor-name was not found in module module-name. cursor-name module-name is the cursor name. is the module name. Cause The HP Neoview database software could not find cursor cursor-name in module module-name. Effect The operation fails.
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. name definition type is the name of the module. is the previous definition Cause type. You defined name twice in this module in which it was defined as a type definition Effect The HP Neoview database software uses the previous definition. Recovery Specify a new name for the item and resubmit, if necessary.
Effect The current value of the HIST_NO_STATS_UEC is retained. Recovery Set the value of CQD HIST_NO_STATS_UEC less than or equal to the value of HIST_NO_STATS_ROWCOUNT. If you want to use a larger value, increase the value of CQD HIST_NO_STATS_ROWCOUNT first. Note that any change in either of the two values can have an effect on the plan quality. SQL 2080 2080 Error number while reading file: value bytes were read from text when value were expected in modul name.
Effect The Neoview database software does not open the file. Recovery Use the error to diagnose and correct the problem. SQL 2085 2085 Error number was returned when closing file name. is the error number. is the name of the file. number name Cause The HP Neoview database software received error number when closing file name. Effect The Neoview database software does not close the file. Recovery Use the error number to diagnose and correct the problem.
SQL 2093 2093 A module timestamp statement was not found in file name. name is the name of the file. Cause The HP Neoview database software did not find a module timestamp statement in the module definition file name. Effect Recovery The Neoview database software uses a default timestamp value of all zeros. Supply a timestamp and resubmit. SQL 2094 2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored.
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. The compilation has been aborted.
SQL 2104 2104 This query could not be compiled for one of two reasons: a) incompatible Control Query Shape (CQS) specifications, or b) 'MEDIUM' optimization level is not sufficient to satisfy the CQS in effect. Suggestion: a) inspect the CQS in effect; or b) raise the optimization level to 'MAXIMUM'. Note that for this query, 'MAXIMUM' optimization level may result in a long compile time.
SQL 2109 2109 Invalid Character error converting SQL statement from character set from character set to character set to character set. from character set to character set may be any of the supported character sets. One of the “from” or “to” character set is always UCS2. may be any of the supported character sets. One of the “from” or “to” character set is always UCS2. Cause The character translation routines failed in the translation between character sets.
Recovery Verify that the name application file is an ELF object file. Verify that the name of application file is spelled correctly, and retry the command. SQL 2203 2203 Application file application pathname cannot be opened. Cause You invoked mxCompileUserModule (or mxcmp -a application pathname mdf) on an application that does not exist or is inaccessible to the user. Effect The operation fails. Recovery Verify that application pathname exists and is readable by the user.
Recovery Review the allowable command-line options by invoking mxCompileUserModule. Verify that the desired command-line options are spelled correctly and retry the command. SQL 2208 2208 mxCompileUserModule requires an application file name. Cause Effect You invoked mxCompileUserModule without supplying an application file. The operation fails. Recovery Invoke mxCompileUserModule on an application file, such as an HP Neoview platform ELF object file.
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 unexpected string in the module name list. Effect The operation fails. Recovery Review the module name list syntax, especially where an identifier is expected. Verify that the list of module names are specified correctly and retry the command.
module name application file name is the requested module name. is the requested application file. Cause You invoked mxCompileUserModule on an application file with a list of module names to SQL compile. This list includes the named module, which cannot be found in the application file. Effect The operation fails. Recovery Verify the spelling of the module name and retry the command. SQL 2223 2223 Application file file name does not exist or is not readable.
4 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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 3001 3001 Syntax error at or before SQL text.
Effect The operation fails. Recovery resubmit. Declare a cursor name, or use the name of a previously prepared statement, and SQL 3006 3006 In a dynamic cursor declaration, both the cursor and the statement must be named in the same way: both must be literals or both must be string host variable expressions. Cause You attempted to declare a dynamic cursor in a way that does not match the statement. Both must be literals or both must be string host variable expressions. Effect The operation fails.
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 Recovery The operation fails. Correct the name and resubmit. SQL 3012 3012 COUNT is the only aggregate function that accepts (*) as an operand. Cause You submitted an AVG or other aggregate function that does not allow (*) as an operand. Only COUNT allows you to use (*). Effect Recovery The operation fails. Remove the (*) operand and resubmit.
SQL 3018 3018 An unsigned smallint was expected, not value. Cause You specified an unexpected value, value. The HP Neoview database software requires an unsigned smallint. Effect Recovery The operation fails. Replace the value with an unsigned smallint and resubmit. SQL 3019 3019 An unsigned number was expected within the parentheses, not value. Cause You specified an unexpected value, value. The HP Neoview database software requires an unsigned number. Effect Recovery The operation fails.
Effect Recovery The operation fails. Remove the MATCH PARTIAL clause and resubmit. SQL 3025 3025 The format of the subvolume name part in the specified location name name is not valid. The subvolume name part must be eight characters long and begin with the letters ZSD. Cause You used an invalid location name for a subvolume that must be eight characters long and begin with the letters ZSD. Effect Recovery The operation fails. Correct the name and resubmit.
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 Recovery The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3038 3038 PIC X types cannot have leading signs, or any signs at all. Cause Effect Recovery You specified a PIC X type with a sign, which is not supported. The operation fails. Remove the sign, or redefine the type, and resubmit. SQL 3039 3039 PIC X types do not have any COMP representation. Cause Effect Recovery You specified a PIC X type with COMP, which is not supported. The operation fails.
Effect Recovery The operation fails. Correct the interval value to a valid one and resubmit. SQL 3045 3045 The date ‘value’ is not valid. Cause Effect Recovery You specified an invalid date value. The operation fails. Change the date value and resubmit. SQL 3046 3046 The time ‘value’ is not valid. Cause Effect Recovery You specified an invalid time value. The operation fails. Correct the time value and resubmit. SQL 3047 3047 The timestamp ‘value’ is not valid.
Effect Recovery The operation fails. Define the column with only one HEADING clause and resubmit. SQL 3052 3052 Duplicate NOT NULL clauses were specified in column definition name. Cause Effect Recovery You defined column name with more than one NOT NULL clause. The operation fails. Define the column with only one NOT NULL clause and resubmit. SQL 3053 3053 Duplicate PRIMARY KEY clauses were specified in column definition name.
Effect Recovery The operation fails. Correct the BLOCKSIZE value and resubmit. SQL 3059 3059 The specified size value (in the MAXSIZE clause or EXTENT size clause) is not valid. Cause Effect Recovery You provided an invalid size value in the MAXSIZE clause. The operation fails. See the Neoview SQL Reference Manual for correct size values, and resubmit. SQL 3060 3060 The specified percentage value in the DSLACK clause is not valid.
Effect Recovery The HP Neoview database software is unable to process this definition. Change the definition of the primary key constraint so that it is NOT DROPPABLE. SQL 3067 3067 ALTER TABLE ADD CONSTRAINT allows only DROPPABLE constraints. Cause You specified an ALTER TABLE ADD CONSTRAINT statement with NOT DROPPABLE constraints. Only DROPPABLE constraints are allowed. Effect The operation fails. Recovery Correct the syntax and resubmit.
SQL 3074 3074 The SEPARATE BY clause is not supported. Cause Effect Recovery You specified the SEPARATE BY clause, which is not supported. The operation fails. Correct the syntax and resubmit. SQL 3075 3075 The [NO]COMPRESS clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause You specified an ALTER INDEX...ATTRIBUTE(S) statement that includes a [NO]COMPRESS clause, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 3081 3081 Duplicate ALLOCATE clauses were specified. Cause Effect Recovery You specified duplicate ALLOCATE clauses. The operation fails. Correct the syntax and resubmit. SQL 3082 3082 Duplicate [NO]AUDIT clauses were specified. Cause Effect Recovery You specified duplicate [NO]AUDIT clauses. The operation fails. Correct the syntax and resubmit. SQL 3083 3083 Duplicate [NO]AUDITCOMPRESS clauses were specified.
Recovery Correct the syntax and resubmit. SQL 3088 3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. Cause You specified an ALTER TABLE statement with both ALLOCATE and DEALLOCATE clauses, which is not supported. Effect The operation fails. Recovery Correct the ALTER TABLE statement to include either ALLOCATE or DEALLOCATE. SQL 3089 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause You specified an ALTER TABLE...
Cause You specified a CREATE INDEX statement that includes the DEALLOCATE clause, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3095 3095 Duplicate [NO]ICOMPRESS clauses were specified. Cause Effect Recovery You specified a statement with duplicate [NO]ICOMPRESS clauses. The operation fails. Correct the syntax and resubmit. SQL 3096 3096 Duplicate [NO]SERIALWRITES clauses were specified.
Recovery Correct the syntax and resubmit. SQL 3102 3102 Duplicate PARALLEL EXECUTION clauses were specified. Cause Effect Recovery You specified a statement with duplicate PARALLEL EXECUTION clauses. The operation fails. Correct the syntax and resubmit. SQL 3103 3103 Duplicate PARTITION clauses were specified. Cause Effect Recovery You specified a statement with duplicate PARTITION clauses. The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the statement to include one of these clauses. SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause Effect Recovery You specified a statement with duplicate STORE BY clauses. The operation fails. Correct the syntax and resubmit. SQL 3110 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. Cause You specified a statement with both LIKE and ATTRIBUTE(S) clauses, which is not supported.
SQL 3115 3115 Duplicate ISOLATION LEVEL clauses were specified. Cause You specified a statement with duplicate ISOLATION LEVEL clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. 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.
SQL 3123 3123 The format of the file name part in the specified location name name is not valid. The file name part must be eight characters long and end with the digits 00. name is the name of the file. Cause You specified an invalid file name. The file name must be eight characters long and end with the digits 00 (zero zero). Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3127 3127 An invalid character was found in identifier name.
SQL 3132 3132 The HEADING for column name exceeds the maximum size of 128 characters. name is the name of the column. Cause You specified a heading for column name that exceeds the maximum size of 128 characters. Effect Recovery The operation fails. 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 The operation fails. Recovery Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3139 3139 A range partitioned index requires a FIRST KEY clause. Cause clause. Effect Recovery You attempted to create a range-partitioned index without a required FIRST KEY The operation fails. Correct the syntax and resubmit. SQL 3140 3140 The isolation level cannot be READ UNCOMMITTED for an INSERT, UPDATE, DELETE, or DDL statement.
SQL 3147 3147 In an IN predicate whose right operand is a value list, the left operand must be scalar (degree of one). Cause You specified an IN predicate whose right operand is a value list but whose left operand is not scalar, which is required. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3148 3148 Environment variable value is being ignored because this version of the code is Release, not Debug. Actual query results will likely not match expected results.
Recovery Correct the syntax and resubmit. SQL 3155 3155 The POPULATE and NO POPULATE clauses cannot coexist in the same CREATE INDEX statement. Cause You specified a CREATE INDEX statement using both the POPULATE or NO POPULATE clauses, which is not supported. Effect The operation fails. Recovery Correct the syntax and resubmit. 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 Correct the syntax and resubmit. SQL 3162 3162 Procedure parameter name was not used. name is the name of the procedure parameter. Cause The HP Neoview database software did not use procedure parameter name. Effect None. Recovery Informational message only; no corrective action is needed. SQL 3163 3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. name is the host variable.
Recovery Correct the syntax and resubmit. 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 Recovery The operation fails. Correct the syntax and resubmit. SQL 3169 3169 name is not a known collation. Cause Effect Recovery You attempted to use a collation that is not a known collation. The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 3176 3176 Subqueries are not allowed in the IF Condition. Cause You specified an IF statement that contains a subquery. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3177 3177 Character set name requires an even number of characters in the length declaration of the data type. 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.
SQL 3182 3182 Extra semicolon(;) in a compound statement. Cause Effect You specified an extra semicolon in a compound statement. The operation fails. Recovery Correct the syntax and resubmit. SQL 3183 3183 Duplicate Row FORMAT clauses were specified. Cause You specified a CREATE TABLE statement containing multiple occurrences of the Row FORMAT clause. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3184 3184 An invalid SQLSTATE value string1 was found.
Cause You specified a STORE BY primary key but did not define a NOT DROPPABLE primary key. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3189 3189 Setting a lock timeout is not allowed on a view. Cause Effect You attempted to set a lock timeout on a view, which is not supported. The operation fails. Recovery None. SQL 3192 3192 Union operands table1 and table2 have different access/lock modes.
Recovery Remove all but one of the table-level access options for each table reference. SQL 3199 3199 Column col-name is incorrectly specified. Keywords ASCENDING and DESCENDING are not allowed in the partitioning key list. col-name is the name of the column. Cause You cannot specify ordering for columns of a partitioning key clause. Effect The operation fails.
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 Recovery The operation fails. Set NAMETYPE ANSI or fully qualify the name. SQL 3207 3207 Value for DYNAMIC RESULT SETS must be zero. Cause In the CREATE PROCEDURE statement, you specified the optional DYNAMIC RESULT SETS clause with nonzero value. Effect Recovery The operation fails.
SQL 3212 3212 Minimum length of LONG VARBINARY is value. Cause You attempted a CREATE TABLE table name (columnname long varbinary(N)) where N < current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect The operation fails. Recovery Increase the CREATE TABLE statement’s long varbinary column width N or decrease the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit. SQL 3213 3213 Maximum length of LONG VARCHAR is value.
Recovery Do not use KANJI or KSC5601 character expressions in these functions. SQL 3218 3218 A table reference cannot contain DELETE or UPDATE in a CREATE VIEW statement. Cause A CREATE VIEW statement was issued with a DELETE or UPDATE operation as a table reference. Effect Recovery The statement does not compile. Do not use DELETE or UPDATE in a CREATE VIEW statement. SQL 3219 3219 The value for DYNAMIC RESULT SETS must be between 0 and 255.
Effect Recovery SHOWLABEL does not display output. Reissue the command with a valid location name. SQL 3228 3228 SHOWLABEL failed for physical location name location-name. SHOWLABEL supports only the data forks of SQL/MX tables, views, and indexes. location-name specifies the physical location name of an HP Neoview database software object. Cause SHOWLABEL supports only the physical names of data forks of the HP Neoview database software objects (physical location names that end in “00”).
dependent-object is the name of a dependent object of the target table, such as an index, after trigger, materialized view, or referential integrity constraint. Cause An INSERT, UPDATE, or DELETE operation into a table with dependent objects was attempted when the NO ROLLBACK transaction setting is ON. Effect Compilation of the statement fails. Recovery If you intend to use NO ROLLBACK, drop the dependent object.
SQL 3237 3237 Duplicate NO ROLLBACK clauses were specified. Cause Duplicate NO ROLLBACK clauses were specified in a SET TRANSACTION statement. Effect SET TRANSACTION statement fails, and the existing transaction state remains unaffected. Recovery Remove the duplicate NO ROLLBACK clause and issue the SET TRANSACTION statement again. SQL 3238 3238 Duplicate AUTOABORT clauses were specified. Cause Duplicate AUTOABORT clauses were specified in a SET TRANSACTION statement.
SQL 3400 3400 Invalid code point value for character set name. Cause Effect There is an undefined character in the character set. The operation fails. Recovery Remove the invalid character and resubmit. SQL 3401 3401 Hexadecimal representation of string literals associated with character set name is not supported. Cause You used a hexadecimal format to represent a character string that is not supported by the HP Neoview database software. Effect The operation fails.
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. The HP Neoview database software does not support arbitrary unicode characters. Effect Recovery The operation fails. Remove non-ISO88591 characters and resubmit. SQL 3409 3409 Declaring a cursor on an embedded INSERT statement is not yet supported.
Cause You provided mixed user-specified values and DEFAULT values in a tuple list for the IDENTITY column. Effect The operation failed. Recovery in the list. Specify values for all the tuples in the list, or specify DEFAULT for all the tuples SQL 3415 3415 The first operand of function name is not valid. name is the name of the function. Cause The first operand you supplied for function name is not an allowed value. Effect The operation fails. Recovery Correct the syntax and resubmit.
num is the specified disk pool number. Cause The disk pool number specified in the DISK POOL clause must be greater than 0. Effect The operation fails. Recovery Retry the query and use a valid disk pool number. The disk pool number must be greater than 0 and less than or equal to the number of disk pools set through the DDL. Alternatively, to pick a random disk pool, ignore the DISK POOL clause so that the table will be placed on a random disk pool.
Recovery These clauses are not supported for materialized views. The materialized view is partitioned the same way as the underlying base table. Remove the clauses and retry the statement. SQL 3425 3425 Embedded embedded-operation expression is not supported with Long Running Updates. embedded-operation is an embedded INSERT, UPDATE or DELETE. statement. Cause A MULTI COMMIT option has been specified on an embedded statement.
5 Binder and Compilation Messages (4000 Through 4999) SQL 4000 4000 Internal error in the query binder. Cause Effect The HP Neoview database software received an internal error in the query binder. The Neoview database software is unable to process this query. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 4001 4001 Column name1 is not found. Tables in scope: name2. Default schema: name3.
If a column is part of a JOIN operation, you no longer qualify its name with its original table name2. Effect The operation fails. Recovery Correct the syntax and resubmit. If the column is part of a JOIN, remove the table qualifier and use only the column name. SQL 4004 4004 Column name name1 is ambiguous. Tables in scope: names. Default schema: name2. Cause You referenced column name1, whose parent table is ambiguous.
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 Correct the syntax and resubmit. SQL 4011 4011 Reference made to column name via star (*) is ambiguous. name is the name of the column. Cause You referred to column name using the SELECT * or SELECT TBL.
SQL 4016 4016 The number of derived columns (value1) must equal the degree of the derived table (value2). Cause You specified a statement in which the number of derived columns (value1) does not equal the degree of the derived table (value2). They must be equal. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4017 4017 Derived column name name was specified more than once. Cause Effect Recovery You specified column name more than once. The operation fails.
SQL 4023 4023 The degree of each row value constructor (value) must equal the degree of the target table column list (value). Cause You specified a statement, such as INSERT, in which a row value constructor does not equal the degree of the target table column list. For example: INSERT INTO table (acol, bcol) VALUES (1, 2, 3); is wrong because the number of columns does not match the number of values. Effect The operation fails. Recovery Correct the syntax and resubmit.
SQL 4028 4028 Table or view name is not updatable. Cause Effect Recovery You attempted to update table name, which is not updatable. The operation fails. None. SQL 4030 4030 Column name has an invalid combination of datetime fields (internal field number, internal field number, internal field number). Cause Effect Recovery You specified column name, which is an invalid combination of datetime fields. The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4036 4036 The source field of the EXTRACT function must be of DateTime or Interval type. Cause You specified a source field of the EXTRACT function that is not a DATETIME or INTERVAL data type. Effect Recovery The operation fails. Correct the source field type and resubmit. SQL 4037 4037 Field name cannot be extracted from a source of type specification.
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 Recovery The operation fails. 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 Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 4049 4049 A CASE expression cannot have a result data type of both type1 and type2. Cause You specified a CASE expression with a result data type of two data types. It must be one of data type. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4050 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation).
SQL 4055 4055 The select lists or tuples must have comparable data types. and type2 are not comparable. Cause Effect Recovery type1 You specified select lists or tuples with incompatible data types. The operation fails. 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 Recovery The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4062 4062 The preceding error actually occurred in function name. Cause The HP Neoview database software detected an error in function name. Errors that appear before this one refer to the low level computations that this function uses. Effect Recovery The operation fails. Correct the function and resubmit.
SQL 4069 4069 Column name uses an unsupported collation. Cause Effect Recovery You specified a column name that uses an unsupported collation. The operation fails. 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. SQL 4071 4071 The first operand of function name must be a datetime.
SQL 4076 4076 Overflow occurred in constant expression name. Cause Effect Recovery There is an overflow in constant expression name. The operation fails. Correct the syntax and resubmit. SQL 4077 4077 Function name accepts only one or two operands. Cause You specified an invalid argument in function name. This function accepts only one or two arguments, both numeric. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4078 4078 Function name does not accept a weight operand.
SQL 4086 4086 Environment variable or define value does not exist. Cause Effect Recovery You specified an environment variable or define value that does not exist. The operation fails. Define the environment variable and resubmit. SQL 4087 4087 Prototype value 'value' is not a valid qualified name. Cause Effect Recovery You specified a prototype value that is not a valid qualified name. The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4096 4096 A DEFAULT specification is currently allowed only when simply contained in the VALUES list of an INSERT. Cause You specified a DEFAULT value that was not contained in the VALUES list of an INSERT. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4097 4097 A NULL operand is not allowed in function name.
SQL 4102 4102 The [FIRST/ANY n] syntax can be used only in an outermost SELECT statement that is not contained in a UNION or INSERT. Cause You attempted to use either a FIRST n or an ANY n clause in other than an outermost SELECT statement. Effect Recovery The operation fails. Remove the FIRST n or ANY n clause and resubmit. SQL 4104 4104 If a character literal was intended, you must use the single quote delimiter: ‘literal’.
SQL 4108 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. Cause A ROWS SINCE function in your statement contained another sequence function that, in turn, contained an invalid reference to the THIS function. Inside ROWS SINCE, the THIS function must not appear inside any other sequence function. Effect The operation fails.
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. Without sequence functions, the SEQUENCE BY clause has no effect. Effect The operation fails.
SQL 4116 4116 The second operand of function name is not valid. Cause You specified an invalid operand for the second operand of function name. For example, a numeric literal operand (for example, 9999999999999999999) cannot be represented as a valid compile-time constant value. Effect The operation fails. Recovery Correct the syntax and resubmit. In this example, you would replace the numeric literal with a smaller numeric literal operand that can be represented as a valid compile-time constant value.
• • • There are no GROUP BY, DISTINCT, or ORDER BY clauses. All select_list columns are column references. No column reference occurs more than once in the select list. 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 ELSE B.UPDATE_FLAG END = 'N' 'N' +>AND A.ACC_TYPE = B.ACC_TYPE AND A.PROD_CODE = B.
Cause You attempted to assign NULL to a NOT NULL column name. 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. name is the name of the table.
Recovery Check the =_DEFAULTS define and resubmit. SQL 4129 4129 An IF statement should have the same set of output host variables on both sides of IF THEN statement list and the ELSE statement list. Cause You specified an IF statement that does not have the same set of output host variables on both sides of its IF THEN statement list and its ELSE statement list. Effect Recovery The operation fails. Correct the syntax and resubmit.
SQL 4138 4138 Use of a subquery in the WHERE clause of a DELETE [FIRST N] statement is not supported. Cause Effect A DELETE [FIRST N] statement has a subquery in the WHERE clause. The statement does not compile. Recovery Either rewrite the statement without using a subquery, or do not use a DELETE [FIRST N] type statement. SQL 4150 4150 Primary key of table expression name must be used for join with embedded operation expression. Tables in scope: name.
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 Recovery The operation fails. Modify the statement and resubmit. SQL 4157 4157 Inner relation of left join cannot be stream expression. Tables in scope: name. Cause You attempted to perform a left join using the result set of a stream expression as the inner relation.
SQL 4162 4162 GROUP BY is not supported for stream expression. Tables in scope: name. Cause Effect You attempted to perform a GROUP BY in conjunction with a stream expression. The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4163 4163 GROUP BY is not supported for embedded name1 expression. Tables in scope: name2. Cause You attempted to perform a GROUP BY in conjunction with an embedded expression.
Effect The HP Neoview database software 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 The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit.
SQL 4176 4176 Join between stream expression and embedded name1 expression is not supported. Tables in scope: name2. Cause You attempted to perform a join between a stream expression and an embedded expression. Effect Recovery The HP Neoview database software is unable to compile the statement. Modify the statement and resubmit. SQL 4177 4177 Update of name1 column name2 is not permitted on rollback.
Effect Recovery The operation fails. Modify the statement and resubmit. SQL 4189 4189 ORDER BY clause in an embedded INSERT, UPDATE, or DELETE statement is not supported. Cause Effect Recovery An embedded INSERT, UPDATE, or DELETE statement has an ORDER BY clause. The statement does not compile. Do not use ORDER BY with an embedded INSERT, UPDATE, or DELETE statement. SQL 4190 4190 Table table-name is not a volatile table. table-name Cause exist.
Recovery Change the schema name provided as part of the two-part name to anything other than volatile-schema-prefix and reissue the SQL statement. SQL 4194 4194 Table table-name is a volatile table and not allowed within this sql statement. table-name is the user-specified table name in the statement. Cause The table name specified is a volatile table that is not allowed in this SQL statement. Effect None.
Effect Recovery The HP Neoview database software is unable to compile the statement. 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. Cause You attempted to perform an INSERT, UPDATE, or DELETE operation on a nonaudited table and IUD_NONAUDITED_INDEX_MAINT is set to WARN. This message appears as an warning.
Cause You attempted to use an index for stream access that does not cover all base table columns referenced in the WHERE clause. Effect Recovery The HP Neoview database software is unable to compile the statement. Add the missing columns to the index. SQL 4209 4209 Update of nullable column name is not permitted on rollback. Cause Effect Recovery You attempted to perform a rollback that included an update of a nullable column. The HP Neoview database software is unable to compile the statement.
SQL 4216 4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded delete statement. Cause You attempted to use either a FIRST n or an ANY n clause in an embedded UPDATE or DELETE statement. Effect Recovery The operation fails. Remove the FIRST n or ANY n clause and resubmit. SQL 4220 4220 The THIS function can be used only inside a ROWS SINCE function. Cause You attempted to use the THIS function in context other than inside a ROWS SINCE function.
Cause In the HP Neoview database software statement being compiled, you attempted to invoke a stored procedure that has an OUT or INOUT parameter that is neither a host variable nor a dynamic parameter. Effect The Neoview database software statement is not compiled. Recovery Correct the Neoview database software statement. Supply a host variable or a dynamic parameter for OUT or INOUT parameters, and retry the compilation. SQL 4307 4307 Rowset parameters are not allowed in a CALL statement.
Recovery Correct the syntax and resubmit. SQL 4320 4320 Stream access not allowed on multi-partitioned table, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set to OFF. Table in scope: table-name. Cause You attempted a stream access on a multi-partitioned table when the flag ATTEMPT_ASYNCHRONOUS_ACCESS was set to OFF. Effect Recovery The operation fails. Set the ATTEMPT_ASYNCHRONOUS_ACCESS flag to ON and resubmit. SQL 4333 4333 Column column-name is not part of the partitioning key.
operation table-names Cause Effect Recovery is an INSERT operation. are the names of HP Neoview database tables that are in scope. You attempted a join operation using an embedded INSERT statement. The operation failed. Modify the statement and resubmit. SQL 4337 4337 Use of a subquery in the WHERE clause of an embedded INSERT statement is not supported. Cause You attempted to run an embedded INSERT statement that contains a subquery in its WHERE clause. Effect Recovery The operation failed.
Cause Effect The window frame clause of a window function contains a FOLLOWING term. The operation fails. Recovery Rewrite the query and exclude any FOLLOWING term. SQL 4345 4345 Window and Sequence functions cannot be used together. Cause Effect Both the window and sequence function syntax were used together. The operation fails. Recovery functions. Rewrite the query to contain either a valid window frame clause or sequence SQL 4346 4346 Window functions can be placed only in the select list.
6 Normalizer Messages (5000 Through 5999) SQL 5000 5000 Internal error in the query normalizer. Cause Effect The optimizer received an internal error during query normalization. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
7 Optimizer Messages (6000 Through 6999) SQL 6000 6000 Internal error in the query optimizer. Cause Effect The optimizer received an internal error during query optimization. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 6001 6001 DISTINCT aggregates can be computed for only one column per table expression.
Recovery Undo your changes by using the CLEAR option in UPDATE STATISTICS and regenerate the statistics. SQL 6007 6007 Multi-column statistics for columns names from table name were not available; as a result, the access path chosen might not be the best possible. names name is a list of column names of the affected columns. is the name of the HP Neoview database table. Cause Statistics are not available for the multicolumn join you are performing.
• • • filename dirname errnum Could not create directory dirname, read-only filesystem. Could not create directory dirname, a component of the path is not a directory. Could not create directory dirname, errno is errnum. is the specified file name. is the specified directory name. is the returned file-system error number. Cause The operation was attempted either in an invalid mode or by specifying an invalid directory. Effect Recovery The operation failed with the indicated error message.
• • 164 Generate new statistics now by using UPDATE STATISTICS FOR TABLE table-name ON NECESSARY COLUMNS. Suppress this message by setting the HIST_ROWCOUNT_REQUIRING_STATS value to a very large number so that this message appears only for tables with more rows than that value or when statistics are missing.
8 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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 7111 7111 Expecting return or “;”. Cause The command did not include a delimiting carriage return or semicolon (;) where TMFCOM expected one. Effect Recovery The command fails. Check the syntax rules for the command and reenter it accordingly. SQL 7112 7111 Expecting “(”. Cause An ALTER PROCESS command was entered with the CPUS option, but the cpu-list did not include a lead left-parenthesis. Effect The command fails.
Cause The command (DUMP FILES, INFO DUMPS, or RECOVER FILES) was entered without specifying an ANSI Name keyword. Effect The command fails. The same error is returned if you do not specify anything after the first single quote. Recovery Check the syntax rules for the command and then reenter the command, specifying a valid ANSI Name keyword. SQL 7337 7337 SQL/MX is not installed on the system. Cause TMFCOM has detected that SQL/MX is not installed on the system.
Cause The command was entered with a delimited SQL identifier containing no significant characters. This can occur for the DUMP FILES, INFO DUMPS, RECOVER FILES, and SET ANSIDEFAULT commands. Effect The command fails. Recovery character. Check the syntax rules and then reenter the command, specifying at least 1 SQL 7343 7343 An internal SqlMX structure is invalid. Cause Effect Recovery An internal structure is not valid. The command fails.
9 Executor Messages (8000 Through 8999) SQL 8001 8001 An internal executor error occurred. Cause Effect The HP Neoview database software has received an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8002 8002 The current nowaited operation is not complete. Cause Effect A nowait call-level interface (CLI) operation was started.
SQL 8007 8007 The operation has been canceled. Cause You pressed the break key. Effect The operation stops. Recovery None. SQL 8008 8008 Catalog name name is not valid. name is the name of the catalog. Cause You specified an invalid catalog name. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8009 8009 Schema name name is not valid.
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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. 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 You attempted to perform an operation on table name1 that is prevented by check constraint name2. Effect The operation fails. Recovery Change the data you are attempting to enter to be consistent with the constraint. SQL 8102 8102 The operation is prevented by a unique constraint. Cause You attempted to perform an operation that is prevented by a unique constraint. Effect The HP Neoview database software could not perform the operation.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8107 8107 Self-referencing INSERT statement without blocking operator is not allowed with AUTOCOMMIT OFF.
SQL 8302 8302 All partitions of type object are unavailable. is the type of the affected object, such as table. is the fully qualified ANSI name of the affected object. type object Cause Late name resolution could not resolve the ANSI name to an available partition. Effect The operation fails. Recovery resubmit. Determine why none of the partitions were available, then correct the error and SQL 8303 8303 Anchor file name contains invalid data.
SQL 8402 8402 22001 A string overflow occurred during the evaluation of a character expression. Cause If the SQLSTATE is 22001, this is an error. You attempted to use a character expression whose length caused a string overflow. If the SQLSTATE is 01004, this is a warning. You attempted to use a character expression whose length caused a string overflow. Effect If this is an error, the operation fails. If this is a warning, your string is truncated. Recovery Do not attempt recovery.
Cause You specified a LIKE predicate with an invalid escape character argument, which must be one character in length. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8410 8410 An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character. Cause You specified a LIKE pattern whose syntax is incorrect.
SQL 8415 8415 The provided DATE, TIME or TIMESTAMP is not valid and cannot be converted. Cause You provided an invalid DATE, TIME or TIMESTAMP, which could not be converted. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8416 8416 A datetime expression evaluated to an invalid datetime value.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. 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 Do not attempt recovery.
Recovery For information about the history buffer size, see num_history_rows in the Neoview Query Guide. If possible, rewrite the query to avoid exceeding the size of the history buffer. If you need the history buffer size increased, contact the GMCSC about resetting the maximum size. SQL 8550 8550 Error NSK err was returned by the Data Access Manager. NSK err Cause Effect is the file-system error returned. The Data Access Manager returned error NSK err. The operation fails.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. 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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Cause Table name has been changed, and the HP Neoview database software was not able to recompile this statement. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8576 8576 Statement was recompiled. Cause The HP Neoview database software recompiled the statement. Effect The operation fails. Recovery Recompile the program.
Effect The merge operation fails. Recovery Ensure that the unique ON clause key is the same key used in the INSERT statement, and reissue the query. SQL 8601 8601 Error returned from file system while locking/unlocking. Cause Effect The file system received an error while locking or unlocking. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
number is the error number. Cause Transaction subsystem name has returned error number while committing a transaction. Effect Recovery The operation fails. Contact the GMCSC. SQL 8607 8607 Rolling back a transaction that has not started. Cause Effect Recovery You attempted to roll back a transaction that has not started. The operation fails. Correct the syntax so that the sequence of events is correct, and resubmit.
SQL 8613 8613 SQL cannot commit or rollback a transaction that was started by application. Cause An application started a transaction outside of the HP Neoview database software that the Neoview database software could not commit or rollback. Effect The operation fails. Recovery The application that started the transaction must perform a commit or rollback. The Neoview database software must start any transactions it will later commit or rollback.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8802 8802 Statement allocation failed because the statement already exists in the current context. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 8808 8808 Module file name contains corrupted or invalid data. name is the name of the file. Cause The HP Neoview database software has detected corrupted or invalid data in the module file name. Effect Recovery file. The Neoview database software could not execute the file. Recompile the .mdf file, using the HP Neoview compiler, to create a valid module SQL 8809 8809 Open of the module file name failed with error number. name number Cause Effect Recovery is the name of the file.
SQL 8815 8815 An internal error occurred while building the TCB tree when executing the statement. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8816 8816 An internal error occurred while executing the TCB tree. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery.
Recovery None. Contact the GMCSC. SQL 8823 8823 An internal error occurred: IO requests are waiting for description message in the IpcMessageStream. description is the description message. Cause I/O requests are waiting for messages shown in message description from the IpcMessageStream. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 8830 8830 There is no current context. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8831 8831 Either no current context or the module to which the statement belongs is not added to the current context. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery.
Cause There is an error in the program that this code is embedded in. The build might not have completed correctly. Effect The operation fails. Recovery Verify that the build was successful and resubmit. SQL 8837 8837 Authorization failure: Error number1 with status number2 was returned by proc-call. number1 number2 proc-call Cause is the file-system error returned by proc-call. is the status code returned by proc-call. is the name of the file-system procedure call returning the error.
Effect Recovery The operation fails. Verify that the build was successful and resubmit. SQL 8843 8843 Trying to retrieve an item, value, that is out of range. 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 Do not attempt recovery.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8853 8853 Specified attribute definition is not valid. Cause Effect You specified an invalid attribute definition. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 8860 8860 Module file name has an obsolete module header. name is the file name. Cause The module file name has an obsolete module header. Effect The operation fails. Recovery Rebuild the module file and resubmit. SQL 8861 8861 Module file name has an obsolete descriptor location table header. name is the file name. Cause The module file name has an obsolete table header. Effect The operation fails. Recovery Rebuild the module file and resubmit.
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. name is the file name. Cause The HP Neoview database software encountered an error while reading the module file name. Effect Recovery The operation fails. Rebuild the module file and resubmit. SQL 8868 8868 SQL cannot create a new context when current transaction is implicitly started by SQL.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8873 8873 The current statement is already associated with a QFO. Cause Effect An existing quasi file object (QFO) is already associated with the current statement. The operation fails. Recovery Do not attempt recovery.
Cause A stored procedure registered with the NO SQL attribute attempted to access the HP Neoview database software. Effect The corresponding SQL request is rejected. Recovery Either change the definition of the stored procedure to allow SQL access, or determine why the stored procedure contains HP Neoview database statements that might be called while the stored procedure is executing. SQL 8888 8888 The underlying insert, update, or delete operation of cursor cursor-name is still in progress.
Cause count. You specified a statement whose argument count does not match the descriptor entry Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8894 8894 Argument argument-name of CLI function function-name is reserved for future use and must be set to string when calling the function.
SQL 8902 8902 An internal error occurred: MXUDR returned a UDR handle that is not valid. Cause The HP Neoview database UDR server generated an improperly formatted identifier when the Neoview database software was executing a stored procedure. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Recovery None. Contact the GMCSC and report this condition. SQL 8910 8910 Reorg command on name failed. name is the table, index, or materialized view where the Reorg operation fails. Cause The reorganization failed because of unavailable resources. Common causes are a resource being busy or a device being down. Effect The operation fails. Recovery To determine the cause of the problem, look in the EMS log for other messages that report additional errors and unavailable resources.
Effect Recovery The operation fails. None. Contact the GMCSC and report this condition. SQL 8915 8915 An attempt to access a stored procedure result set at position index failed because there is no result set currently available at that position. index is an integer specifying a position in the ordered set of result sets returned from a CALL statement.
SQL 8919 8919 Unable to retrieve Runtime Statistics for invalid Query Id string. string is the query ID specified. Cause You issued either a command to retrieve runtime statistics for a query ID that is not in a valid format or a "select variable_info from table(statistics(module-name,stmt-name));" command with the query ID, but the query ID is not in a valid format. Effect No runtime statistics information can be retrieved for the input query ID, and the command fails.
10 UPDATE STATISTICS Messages (9200 Through 9218) SQL 9200 9200 UPDATE STATISTICS encountered an error from statement name. Cause name. UPDATE STATISTICS encountered an error from the HP Neoview database statement 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 You attempted to run UPDATE STATISTICS against an object that is not supported. Effect The HP Neoview database software is unable to continue processing. Recovery Correct the syntax and resubmit. SQL 9206 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. Cause The HP Neoview database software could not perform an UPDATE STATISTICS statement because you are not authorized to perform this operation against this table.
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 Effect Recovery You attempted to perform UPDATE STATISTICS and did not specify a column list. Processing continues without interruption. Correct your syntax to specify the column list and resubmit. SQL 9214 9214 Object name could not be created.
Recovery 206 Informational message only; no corrective action is needed.
11 Executor Sort and Scratch File I/O Messages (10000 Through 10199) The messages described in this chapter are: • • “Executor Sort Messages (10000–10049)” (page 207) “Scratch File I/O Messages (10101–10199)” (page 211) Executor Sort Messages (10000–10049) SQL 10003 10003 Sort unexpectedly encountered an EOF during a read operation. Cause Effect This error occurs when a scratch file read operation unexpectedly reaches an EOF. The operation fails. Recovery Do not attempt recovery.
Effect The operation fails. Recovery Contact the GMCSC. SQL 10008 10008 Invalid sort algorithm selected. Cause Effect The caller of sort specified an invalid sort algorithm. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 10010 10010 Sort run number is invalid. Cause Effect The scratch run on the disk does not belong to any scratch block on the disk.
SQL 10015 10015 Sort failed while calling PROCESSHANDLE_GETMINE_ with error number. Cause Effect An error occurred while calling a system level call. The operation fails. Recovery Contact the GMCSC. SQL 10016 10016 Sort failed while calling PROCESSHANDLE_DECOMPOSE_ with error number. Cause Effect An error occurred while calling a system level call. The operation fails. Recovery Contact the GMCSC. SQL 10017 10017 Sort failed while calling DEVICE_GETINFOBYLDEV_ with error number.
SQL 10022 10022 Sort failed while calling FILE_CREATE with error number. Cause Effect An error occurred while calling a system level call. The operation fails. Recovery Contact the GMCSC. SQL 10023 10023 Sort failed while calling FILE_OPEN_ with error number. Cause Effect An error occurred while calling a system level call. The operation fails. Recovery Contact the GMCSC. SQL 10024 10024 Sort failed while calling SETMODE_ with error number.
SQL 10044 10044 IO to a scratch file did not complete and reported error number. Cause After several calls to the completion routine, the I/O operation to a scratch file did not complete and returned a low-level system error. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. Note for Support See the Guardian Procedure Calls Reference Manual to diagnose the problem.
SQL 10102 10102 operator failed to open a scratch file. FILE_OPEN_ returned error number. operator number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number. The query operator was unable to open a scratch file. The operation fails. Recovery None. This is an internal error. Contact the GMCSC. SQL 10103 10103 operator failed to close a scratch file. FILE_CLOSE_ returned error number.
Cause Effect The query operator was unable to alter a scratch file's attributes. The operation fails. Recovery Contact the GMCSC to diagnose the cause of the SETMODE returned error and correct the problem. SQL 10111 10111 operator could not wait for a scratch file I/O to complete. AWAITIOX returned error number. operator number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number.
Recovery None. This is an internal error. Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message. SQL 10115 10115 operator was unable to obtain disk volume free space information. FILE_GETINFOLISTBYNAME_ returned error number. operator number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number.
SQL 10119 10119 operator encountered an error while searching for a scratch disk. FILENAME_FINDNEXT_ returned error number. operator number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number. An invocation of FILENAME_FINDNEXT_ failed. The operation fails. Recovery None. This is an internal error. Do not attempt recovery.
Cause Effect The mapping of data blocks to scratch files is incomplete. The operation fails. Recovery None. This is an internal error. Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message.
12 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399) SQL 11014 11014 A BEFORE trigger allows only SIGNAL, SET and CALL statements. Cause You attempted to create a BEFORE trigger with a trigger action other than SIGNAL, SET, or CALL. Consider that the dependent descriptor might be for a trigger. Effect The operation fails. Recovery If SET, SIGNAL, or CALL does not work, determine whether an AFTER trigger is more appropriate for your application.
SQL 11046 11046 Host variables and dynamic parameters are not allowed in the action of a trigger. Cause You attempted to create a trigger that includes host variables or dynamic parameters in its action. This can happen when you specify CALL statements or compound actions as triggered actions. Effect The operation fails, and the trigger is not created. Recovery Rewrite the trigger so that host variables and dynamic parameters do not appear in the trigger action. Then retry the operation.
Cause Effect The UDR server received a request message with an unknown message type. The request message is rejected, and the SQL statement fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 11102 11102 MXUDR: Invalid UDR handle: string. Cause The UDR server received a request for a stored procedure that is no longer present in the UDR server context.
Cause Effect The UDR server encountered an internal error. Details appear in the message text. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 11111 11111 MXUDR: Internal error: value. Cause The UDR server received an incorrectly formatted message. Effect The request message is rejected, and the SQL statement fails. Recovery Do not attempt recovery.
Cause Effect An internal CLI operation failed. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 11116 11116 MXUDR: Internal error: A stored procedure result set message-type request arrived containing an invalid result set index: index. message-type index Cause Effect type is a message that is sent to the UDR server.
SQL 11202 11202 Language Manager initialization failed. Details: Unable to initialize the Java virtual machine. Cause Initialization of the language manager failed during creation of the Java Virtual Machine. Effect The operation fails. Recovery Check the installation of the NSJ product. Stop and restart the session, and retry the SQL statement. HP support will perform recovery operations SQL 11203 11203 The Language Manager failed to create its class loader, possibly due to corrupt mxlangman.jar file.
Effect The operation fails. Recovery Stop and restart the session and retry the SQL statement. SQL 11222 11222 The operation failed because the Java Virtual Machine ran out of memory. Cause The Java Virtual Machine, hosted by the UDR server, did not have enough memory to execute a Java method. This error condition will be accompanied by another condition that shows when the Java Virtual Machine encountered the error. Effect The operation fails.
Recovery Correct the signature of the SPJ method, and resubmit. SQL 11232 11232 The Java method method-name in Java class class-name is not defined as static. method-name class-name is the Java method name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement.
is the position of the result set parameter in the Java method signature. parameter-position Cause During the execution of a CALL statement, an SPJ method returned result sets but the result sets could not be processed because the language manager encountered an unexpected error trying to retrieve the information for the result set at position parameter-position in the Java method signature. Effect The operation fails. Recovery Do not attempt recovery.
the declared SQL parameter types. If the DYNAMIC RESULT SETS clause specifies a value greater than zero, the SPJ method must also have one or more trailing java.sql.ResultSet[] parameters. Effect The operation fails. Recovery Ensure that the SPJ method exists in the specified class file, and resubmit. SQL 11240 11240 Specified signature is invalid. Reason: Parameter at position index is not java.sql.ResultSet[].
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
13 Materialized Views Messages (12000 Through 12329) SQL 12001 12001 Creation failed. The materialized view cannot be maintained incrementally. Cause You specified an incremental materialized view and used a query expression that is not supported as incremental. Effect The creation of the materialized view fails. Recovery Change the materialized view definition and resubmit the create statement. SQL 12005 12005 Materialized view mv-name is not found in metadata table name.
name is an unaudited table. Cause Materialized views that use unaudited tables are not supported. Effect The creation of the materialized view fails. Recovery Correct the syntax and resubmit. SQL 12011 12011 The materialized view cannot be altered. ON STATEMENT and RECOMPUTE materialized views do not contain an IGNORE CHANGES clause. Cause The materialized view (MV) being altered is not an ON REQUEST MV to alter the IGNORE CHANGES clause. Effect The operation fails.
SQL 12021 12021 Table name is in the IGNORE CHANGES clause but is not a base table or is not in the FROM clause. name is a table. Cause An attempt was made to submit a statement with an IGNORE CHANGES clause which includes a table that is not a base table of the materialized view or is not in the FROM clause. Effect The operation fails. Recovery Resubmit and use a valid base table name in the IGNORE CHANGES clause. SQL 12023 12023 A configuration error occurred on an initialized materialized view.
SQL 12033 12033 An underlying materialized view has an incompatible refresh type. Cause You attempted to create a materialized view on top of another materialized view with an incompatible refresh type. Effect The creation of the materialized view fails. Recovery The two materialized views must have compatible refresh types. SQL 12038 12038 Cannot GRANT REFERENCES on materialized views.
SQL 12050 12050 ATTRIBUTE AUDIT not supported for materialized views. Cause Effect The AUDIT attribute is not supported for materialized views. The creation of the materialized view fails. Recovery Remove the attribute from the materialized view definition. SQL 12051 12051 ATTRIBUTE DEALLOCATE not supported for materialized views. Cause Effect The DEALLOCATE attribute is not supported for materialized views. The creation of the materialized view fails.
SQL 12092 12092 Group by columns cannot exceed 255 characters. Cause The total size of all the materialized view Group By columns exceeds 255 characters. Effect The creation of the materialized view fails. Recovery Rewrite the Create Materialized View statement so that the total size of all the Group BY columns does not exceed 255 characters, and resubmit the Create Materialized View statement. SQL 12106 12106 The index was created with NO POPULATE clause. It will be populated during first refresh.
Cause Privileges on the materialized view base table were revoked from the materialized view owner. Effect The materialized view and its dependent objects (such as views or other materialized views created on this materialized view) are dropped. Recovery None. If you need to recover the dropped materialized view, the revoked privileges need to be acquired and the materialized view recreated. SQL 12111 12111 NO AUDIT materialized views are not supported.
SQL 12116 12116 The IGNORE CHANGES clause of materialized view mv-name cannot be altered when the COMMIT REFRESH EACH mvattribute is specified and the alter causes the materialized view to change from tracking changes on one base table to multiple base tables. mv-name is a materialized view. Cause An attempt was made to alter a materialized view such that the materialized view is now tracking changes on more than one table.
SQL 12206 12206 Materialized view mv-name is not in MVGroup. mv-name is a materialized view. Cause An attempt was made to remove a non-existent materialized view from a materialized view group. Effect The operation failed. Recovery None. SQL 12208 12208 An MVGROUP cannot contain ON STATEMENT materialized views like mv-name. mv-name is a materialized view. Cause An attempt was made to add an ON STATEMENT materialized view to a materialized view group. This is not supported.
mv-name mvgroup-name is a materialized view. is a materialized view group. Cause The materialized view and its depends were removed from the materialized view group because the owner of the materialized view revoked the select privilege. Effect The operation failed. Recovery None. SQL 12213 12213 You are not the owner of table name. The materialized view mv-name was not added to the default MVGroup mvroup-name and will not be refreshed with the MVGroup. name mv-name mvgroup-name is a table.
SQL 12312 12312 Materialized view mv-name is unavailable. mv-name Cause state. is a materialized view. A DML operation is attempted against a materialized view that is in an unavailable Effect The DML operation fails. Recovery Contact the GMCSC to fix the materialized view state. SQL 12314 12314 Table name is not used by this materialized view. name is a table. Cause The materialized view is not available for any DML operation, mostly probably because of a preceding failing MAINTAIN.
Recovery Correct the syntax and resubmit. SQL 12321 12321 Creation failed. The select list must have at least one column. The materialized view cannot be maintained incrementally. Cause You attempted to create a materialized view without columns in the select list. This operation is not allowed. Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12322 12322 Creation failed. The same table is used more than once.
SQL 12327 12327 Creation failed. The select list contains a nongrouping, nonaggregated column. The materialized view cannot be maintained incrementally. Cause You attempted to create a materialized view that includes a select list with a nongrouping, nonaggregated column. Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12328 12328 Creation failed. Only equi-join predicates are allowed.
14 Messages Generated by the Message System (16000 Through 16999) SQL 16001 16001 The error number err-num is not used in SQL/MX. Cause Internal error. Effect The Neoview software is unable to return or display a message with the specified number. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
15 Internal Stored Procedures Messages (19000 Through 19999) SQL 19000 19000 An internal error occurred in internal stored procedure processing. Cause Effect Internal error. The HP Neoview database software is unable to process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 19001 19001 An error was found in field description of internal stored procedure.
SQL 19017 19017 The format of input value 'value' is invalid for input type input-type. value input-type is a user-specified input value to a versioning built-in function. is a valid input type to one of the versioning built-in functions, VERSION_INFO or RELATEDNESS. Cause A request attempts to access a built-in function with an input value that is invalid for the specified input type. Effect The request fails. Recovery None.
16 Utility Messages (20000 Through 23099) SQL 20000 20000 File system error error number occurred during file open. error number Cause Effect is the HP Neoview platform file-system error. SQL was not able to open the requested file and received error error number. The operation fails. Recovery For information about file-system errors, see Chapter 25 (page 481). SQL 20001 20001 File system error error number occurred during file read.
error number is the HP Neoview platform file-system error. Cause SQL was not able to retrieve information for the requested file and received error error number. Effect The operation fails. Recovery For information about file-system errors, see Chapter 25 (page 481). SQL 20006 20006 File system error error number occurred while enabling large transfers for file. error number is the HP Neoview platform file-system error.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20011 20011 An internal error occurred - file is not open. Cause The utility subsystem that performs fast data transfer received a request out of sequence. Effect The operation fails. Recovery Do not attempt recovery.
Cause SQL was not able to obtain the blocksize for the requested file and received error error number. Effect The operation fails. Recovery For information about file-system errors, Chapter 25 (page 481). SQL 20017 20017 File system error error number occurred while getting partition length for file. error number is the HP Neoview platform file-system error. Cause SQL was not able to obtain the partition length (EOF) for the requested file and received error error number. Effect The operation fails.
Cause The HP Neoview database software found a discrepancy while reading metadata information. The information returned is inconsistent. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20021 20021 An internal error occurred - invalid column data type. Cause The utility subsystem that reads and maintains metadata encountered an unexpected data type for a column.
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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. Note for Support Correct the syntax and resubmit.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20044 20044 An internal error occurred - invalid file attribute. Cause The utility subsystem that reads and maintains metadata encountered an unexpected value for a file attribute. Effect The operation fails. Recovery Do not attempt recovery.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20051 20051 Transaction Management subsystem could not rollback the current transaction. Cause The utility subsystem that performs transaction management operations failed while trying to roll back the current transaction. Effect The operation fails. Recovery Do not attempt recovery.
SQL 20056 20056 An internal error occurred - Transaction Management subsystem could not close a statement. Cause The utility subsystem that sends CLI requests to SQL failed trying to close a previously executed SQL statement. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 20109 20109 details. details describe the returned error information from the file system. Cause An unexpected error was returned from the CLI while accessing file system information. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20127 20127 Target option was specified as NEW but object-type exists. DUP operation failed.
SQL 20141 20141 Wrong parameter index passed. Cause The utility subsystem that performs CLI operations failed while trying to get information from the returned statement. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20142 20142 An internal error occurred - invalid datatype. Allowed datatypes are 'char' and 'varchar’.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20164 20164 The search condition for the specified check constraint has a syntax error. Cause You attempted to create a check constraint, but a syntax error was found in the search condition. Effect The operation fails. Recovery Do not attempt recovery.
SQL 20178 20178 Internal error occurred while performing Import. Cause Effect An unspecified internal error occurred during the IMPORT utility operation. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20179 20179 An unexpected error condition was encountered. Cause The MODIFY utility encountered an unexpected error condition.
SQL 20205 20205 Index index is online. Cannot perform POPULATE INDEX. index is the index's ANSI name. Cause You requested to populate an index that is already populated. Effect None. Recovery This is an information message. No corrective action is needed. SQL 20206 20206 Data type conversion failed while converting key value (column-value[,column-value]...)to data type(s) (data-type[,date-type]...) for object-name.
Cause An unexpected error occurred on an attempt to complete a data movement operation for the request. Effect The operation fails. Recovery None. This is an internal error. Contact the GMCSC. SQL 20223 20223 Internal error on unsupported character set conversion. Cause An invalid character set designation was encountered. Effect The operation fails. Recovery Do not attempt recovery.
SQL 20232 20232 This operation cannot be done on a nonaudited table that contains data. Cause Effect You tried to perform a MODIFY utility on a nonaudited table containing data. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20235 20235 Error returned from USER_GETINFO_ while converting userid to user name, status: status, userid: userid.
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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20255 20255 An invalid partition management operation was specified for an index.
len2 is the expected length. 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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20271 20271 SPI Error error returned from subsystem while performing an online reload operation. error subsystem Cause Effect is the error returned.
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. SQL 20290 20290 The current operation on partition partition for the object object failed because a utility operation on the same partition is already in progress or has failed.
Effect The MODIFY utility completed the request, but the FUP RELOAD operation might not have finished successfully. Recovery Run FUP RELOAD manually to reclaim any free space on the specified partitions if the D flag (INCOMPLETE SQLDDL OPERATION), or F flag (UNRECLAIMED FREE SPACE) is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set. SQL 20298 20298 The program file progname is not licensed. progname Cause Effect is the name of the program file.
Cause This is an internal error. The Synonym metadata is in an inconsistent state. It should have a referenced object, but it cannot be found. Effect The operation fails. Recovery Contact the GMCSC to check if the Synonym metadata is corrupt. SQL 20339 20339 Indexes index-list on table table did not populate successfully. index-list table is a comma separated list of indexes. is the name of the table.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20353 20353 Syntax error. An invalid operation operation was requested. Try ‘mxtool help’. 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. Recovery Do not attempt recovery.
SQL 20358 20358 Catalog catalog does not exist. is the name of the catalog specified in the request. catalog Cause Effect You specified a catalog name that is not defined or is not visible on the system. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20359 20359 Schema schema does not exist. is the name of the schema specified in the request.
Cause An unexpected error was returned while reading the file label for an HP Neoview platform file. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20370 20370 Invalid flag provided for the operation. Try ‘mxtool help’ for the operation. Cause Effect The syntax you specified was invalid. The operation fails. Recovery Do not attempt recovery.
SQL 20451 20451 You asked to drop only the resource fork resource fork name but a data fork exists (data fork name). resource fork name data fork name Cause is the HP Neoview platform file of the resource fork. is the Neoview platform file of the data fork. You specified invalid options for the GOAWAY command. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Cause The GOAWAY operation failed because only the data fork or resource fork exists, and the -both option was specified. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20460 20460 You specified -both for GOAWAY request of resource fork name You must specify data fork name to GOAWAY the label. resource fork name data fork name is the name of the resource fork.
Cause The refresh operation cannot complete because a transaction has already been started by a user. Effect The operation fails. Recovery End the open transaction, and resubmit the command. SQL 20505 20505 Failed to access the catalog data. REFRESH cannot be performed. Cause Effect This is an internal error between utilities and the catalog manager. The operation fails. Recovery Do not attempt recovery.
SQL 20511 20511 ON STATEMENT materialized view mv-name cannot be refreshed with CASCADE option. mv-name Cause Effect is a materialized view. The CASCADE option is not allowed with ON STATEMENT materialized views. The operation fails. Recovery Remove the CASCADE option, and resubmit the command. SQL 20512 20512 MVGROUP mvgroup-name does not contain materialized views. mvgroup-name Cause Effect is a materialized view group. An attempt was made to maintain an empty materialized view group.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20520 20520 Object object cannot participate in refresh; a utility operation associated with a DDL lock on it is currently running. is the name of the object. object Cause Effect Object object has a DDL lock on it. The refresh operation fails. Recovery After the concurrent operation that holds the DDL lock finishes, rerun refresh again.
Effect The operation fails. Recovery Try to REFRESH with the CANCEL option to release the DDL lock, and resubmit the original REFRESH statement. If the error persists, contact HP support. SQL 20525 20525 Task task-name cannot be executed remotely. task-name Cause Effect is the name of a refresh task. The refresh operation cannot be executed remotely because the buffer is full. The operation fails. Recovery Do not attempt recovery.
SQL 20531 20531 An internal error occurred while extracting data type information from an internal data buffer. Cause Effect TBD. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20532 20532 An internal error occurred while comparing data from internal data buffers.
Cause The refresh operation failed internally while attempting to change the index’s status during a recompute operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20538 20538 Failed to fetch data from the multi-transactional materialized view's context table. Cause The refresh operation cannot complete because a failure occurred on a required internal task.
Recovery For more information about file-system errors, see Chapter 25 (page 481). SQL 20545 20545 File system error error-number occurred while executing AWAITIO. error-number Cause text. Effect is an error originating from the file system. To determine the cause, look up the reported error number for its associated error The operation fails. Recovery For more information about file-system errors, see Chapter 25 (page 481).
Cause The refresh operation cannot complete because a failure occurred on a required internal task. Effect The operation fails. Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If the error persists, contact HP support. SQL 20551 20551 The materialized view mv-name cannot be refreshed (not all of the used materialized views are initialized). mv-name Cause Effect is a materialized view name.
Cause The materialized view might be based other materialized views and tables that are not up to date. Effect The operation fails. Recovery Put materialized views with common tables into a materialized view group, and refresh the MVGROUP. 20558 The current user does not have the select and delete privileges for materialized view mv-name, and cannot purge data from it. mv-name is a materialized view name. Cause You do not have the correct privileges to perform the requested operation.
error-number is an error originating from the transaction management facility (TMF). Cause During the refresh operation, an error originating from the transaction management facility occurred on a begin transaction operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20565 20565 TMF error error-number occurred while trying to commit a transaction.
SQL 20576 20576 File system error error-number occurred during FILE_OPEN_ on process process-name. error-number process-name Cause text. Effect is an error originating from the file system. is the name of the process. To determine the cause, look up the reported error number for its associated error The operation fails. Recovery For more information about file-system errors, see Chapter 25 (page 481). SQL 20577 20577 File system error error-number occurred during FILE_CLOSE_ on process process-name.
Cause During an online partition management operation, memory allocation errors prevented the MXAUDSRV process from initializing. The error number given is the return code MXAUDSRV received from a SEGMENT_ALLOCATE_ request. Effect The POPULATE INDEX or MODIFY operation fails. Recovery Contact the GMCSC. SQL 20702 20702 A file system error occurred during the audit fixup phase of the operation, on file file name. file name is the name of the partition being processed.
Cause During an online partition management operation, the MXAUDSRV process received an invalid request from the MODIFY code. The probable cause was incorrect versions of MXCMP or MXAUDSRV software. Effect The MODIFY utility did not process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20711 20711 An error occurred while reporting an event to the EMS collector during the audit fixup phase of the operation, in process process name. process name is the MXAUDSRV process name. Cause During an online partition management operation, the MXAUDSRV process encountered an error while attempting to report an EMS event to $0.
Cause During an online partition management operation, the MXAUDSRV process encountered an audit-trail versioning error while processing audit records. Effect The MODIFY operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20719 20719 A request with an incompatible version was made to audit fixup process process name. process name is the MXAUDSRV process name.
SQL 20724 20724 Audit fixup process process found a violation of the uniqueness constraint while populating a unique index. process Cause Effect is a file-system process identifier. A uniqueness violation was detected during the populate index operation. The populate operation failed. Recovery Recover the index file, remove conflicting records from base table, and retry the operation. SQL 20725 20725 Audit fixup process process name detected an internal error. process name is the MXAUDSRV process name.
SQL 20729 20729 File system error error code was returned from an MXARLIB call in audit fixup process process name. error code process name is the returned file system number. is the MXAUDSRV process name. Cause During an online partition management operation, the MXAUDSRV process encountered an error when attempting to extract data fields from a transaction-services log record. Effect The POPULATE INDEX or MODIFY operation fails. Recovery None.
Cause A transaction-services transaction is currently active. The VERIFY process does not allow active transactions. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20752 20752 The cmdname command cannot work on object object-name that has an object type of type. cmdname supports only objects that have an object type of BT or MV.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. HP support can specify the correct name and resubmit. SQL 20756 20756 VERIFY cannot work on Guardian file (file) because it belongs to the space name space. VERIFY supports only objects in the namespace name space. file space is the HP Neoview platform file name specified. is the ANSI name space for the file.
Cause Effect An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20761 20761 The corrupt flag (flag1) defined on the label does not match the corrupt flag (flag2) defined in the metadata for Guardian file (fname). flag1 flag2 fname is the value of the corrupt flag on the label.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. 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). flag1 flag2 file is the value of the flag stored in the label. is the value of the flag stored in the metadata. is the name of the HP Neoview platform file.
SQL 20769 20769 The ANSI name (name1) in resource fork does not match the ANSI name (name2) defined in the metadata for Guardian file (file). name1 name2 file is the ANSI name found in the resource fork. is the ANSI name found in the metadata. is the name of the HP Neoview platform file. Cause An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Do not attempt recovery.
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). name file Cause Effect is the constraint name described in the metadata. is the name of the HP Neoview platform file. An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Do not attempt recovery.
Cause Effect An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20779 20779 The number of indexes (num1) in the index map array on the resource fork does not match the number of indexes (num2) in the metadata for Guardian file (file).
SQL 20783 20783 The location (string1) defined in the partition map for Guardian file (file) does not match the location (string2) defined in metadata. string1 file string2 Cause Effect is the HP Neoview platform name of the partition that is defined in the partition map on the resource fork that does not exist in the metadata. is the name of the Neoview platform file. is the Neoview platform 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 Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20788 20788 User does not have authority to perform operation for object object. is the name of the table being verified. object Cause The requestor does not have the privileges to perform the VERIFY operation.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20792 20792 VERIFY is not able to read file label information for file file name. file name is the name of the HP Neoview platform file. Cause An unexpected error was returned while extracting parts of the ANSI name from the resource fork. Effect The operation fails. Recovery Contact the GMCSC.
SQL 20798 20798 There is currently an active/inactive DDL lock for object (object name). active/inactive object object name Cause Effect specifies whether the lock is active or inactive. specifies whether the object is a table or view. is the ANSI fully qualified name of the table or view. An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery For an inactive DDL lock, contact the GMCSC.
is the HP Neoview platform file name. file-name Cause An SQL file has a file code out of the correct range of 550 through 565. Effect The object might be inaccessible. Recovery Run MXTOOL FIXUP on the file. SQL 20812 20812 Internal Error: Unknown Object Security Class value found in an existing Table object. Cause The table object's metadata flag is set up incorrectly, and its flag value is in an unknown state.
SQL 20853 20853 name is not an SQL/MX object that is supported by FIXUP. Only TABLES, INDEXES and Materialized views are supported. name is the HP Neoview database object. Cause You attempted to run the FIXUP utility on an HP Neoview database object that was not a table, index, or materialized view. Effect The operation fails. Recovery Do not attempt to run the FIXUP utility on objects other than tables, indexes, and materialized views. Enter a valid name and resubmit.
Cause The header information of the input file did not match the header format. Effect The operation fails. Recovery Fix the header information and retry the request. SQL 20990 20990 PURGEDATA requires NOLOG option because name has Materialized View defined. PURGEDATA cannot be performed. name is the materialized view name. Cause The HP Neoview database object you specified has materialized views created on it, but you omitted the NOLOG option. Effect The operation fails.
Effect The operation fails. Recovery Remove the option that is not implemented, and resubmit the command. SQL 21004 21004 Catalog does not exist or has not been registered on the local segment. Cause Effect The specified catalog does not exist on the local segment. The operation fails. Recovery Specify an existing catalog, and resubmit the command. SQL 21005 21005 Schema does not exist. Cause Effect The specified schema does not exist. The operation fails.
SQL 21010 21010 Index index-name does not exist. index-name Cause Effect is the specified index name. The specified index does not exist. The operation fails. Recovery Specify an existing index, and resubmit the command. SQL 21011 21011 Can not open base table/MV for index index-name. index-name Cause Effect is the specified index name. The base table or materialized view does not exist for the specified index. The operation fails.
SQL 23003 23003 servername: File error encountered: description. servername description Cause Effect is the name of the server program that issued the error. gives more detail about the file error. See details in description description. The operation fails. Recovery Correct the problem and resubmit. Recovery Correct the run-time argument and resubmit. SQL 23007 23007 servername: An SQL Error occurred: description.
SQL 23013 23013 servername: Error code: nnn. No error text available for this code. servername nnn Cause Effect is the name of the server program that issued the error. is the unknown error code. An exception occurred for an unexpected error. The operation fails. Recovery None. Contact the GMCSC. SQL 23014 23014 servername: An internal error occurred - unhandled exception; cannot proceed. servername Cause Effect is the name of the server program that issued the error.
SQL 23018 23018 servername: Expected map entry is missing: description. servername description Cause is the name of the server program that issued the error. contains detailed information about the missing mapping file section name. When processing a mapping file, an expected section or attribute was not found. Effect The operation fails. Recovery Correct the mapping file and resubmit. SQL 23020 23020 servername: SQL/MX object was not found: object-name.
17 Security Interface Messages (24000 Through 24499) 24001 24001 The LDAP host name or IP address is not allowed to be null. Cause Effect Recovery You specified a NULL value, which is not allowed for the host name or IP address. The operation fails. Correct the syntax and resubmit. 24002 24002 The LDAP host name or IP address exceeds the maximum length of 128 characters. Cause Effect Recovery You specified a value that exceeds the maximum length. The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. 24008 24008 LDAP distinguished name (DN) suffix is not allowed to be null. Cause Effect Recovery You specified a NULL value. The operation fails. Correct the syntax and resubmit. 24009 24009 The LDAP distinguished name (DN) suffix exceeds the maximum length of 512 characters. Cause Effect Recovery You specified a value that exceeds the maximum length. The operation fails. Correct the syntax and resubmit.
24015 24015 The LDAP authorization group exceeds the maximum length of 512 characters. Cause Effect Recovery You specified a value that exceeds the maximum length. The operation fails. Correct the syntax and resubmit. 24016 24016 The LDAP group type is not allowed to be null. Cause Effect Recovery You specified a NULL value. The operation fails. Correct the syntax and resubmit. 24017 24017 The LDAP group type exceeds the maximum length of 32 characters.
24022 24022 Internal Error – Failed to check the LDAP user. Cause Effect Recovery Internal error. The operation fails. None. Contact the GMCSC. 24023 24023 Failed to add the Neoview user. The LDAP user does not exist. Cause Effect Recovery You tried to add a Neoview user before adding that user to the LDAP server. The operation fails. Add the LDAP user to the LDAP server, and resubmit the request. 24024 24024 No support for an add policy function.
Cause Effect Recovery Internal error. The operation fails. None. Contact the GMCSC. 24030 24030 Internal Error – Failed to get the Neoview role ID. Cause Effect Recovery Internal error. The operation fails. None. Contact the GMCSC. 24031 24031 Internal Error – Failed to delete the Neoview role. Cause Effect Recovery Internal error. The operation fails. None. Contact the GMCSC. 24032 24032 Internal Error – Failed to get the Neoview role. Cause Effect Recovery Internal error. The operation fails. None.
24037 24037 The role name exceeds the maximum length of 8 characters. Cause Effect Recovery You specified a value that exceeds the maximum length. The operation fails. Correct the syntax and resubmit. 24038 24038 The number of maximum logon attempts must be a value from 0 through 9999. Cause Effect Recovery You specified an invalid value. The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. 24044 24044 The maximum number of days before a password expires must be a value from 0 through 32767. Cause Effect Recovery You specified an invalid value. The operation fails. Correct the syntax and resubmit. 24045 24045 The minimum number of quality criteria that must be met when changing passwords must be a value from 0 through 5. Cause Effect Recovery You specified an invalid value. The operation fails. Correct the syntax and resubmit.
18 Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29399) The messages described in this section are: • • • “Versioning Messages (25000–25399)” (page 317) “Distribution Messages (25400–25499)” (page 327) “JDBC Driver Error Messages (29000–29399)” (page 332) Versioning Messages (25000–25399) SQL 25002 25002 A versioning internal error occurred: missing compatibility check. Cause This is a versioning internal error. Effect The operation fails.
MXV2 is the local node’s earliest supported MXV. Cause The remote node node has an MXV (MXV1) earlier than the local node’s earliest supported MXV (MXV2), which is not supported. Effect The operation fails. Recovery Upgrade the remote node to an MXV that is later than or equal to the local node’s earliest supported MXV. Or, conversely, downgrade the local node to an MXV that is earlier than or equal to the remote node’s MXV.
Effect The operation fails. Recovery Upgrade the affected schema to a version that is compatible with the MXV of the nodes that need to access the schema. 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. object version1 node version2 is the name of the affected database object. is the schema version of that database object’s schema.
This message indicates a downgrade that has been performed without removing database objects of the later version. Effect The operation fails. The object (and all other objects in the affected schema) is inaccessible. Recovery Migrate the software on the affected node to a version that supports the database objects that are present on the node. SQL 25204 25204 Table or view object1 has schema version version1; this is incompatible with the version of the compiler that compiles the query.
• • The local system schema version is later than the MXV of a node that is involved in the affected query. Compilation of such a query requires a downrev compiler. 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.
schema version1 node version2 is the name of the schema referenced by a DDL or utility operation. is the schema version of schema. is the node where the operation is executed or the node where metadata for the schema resides. is the earliest supported schema version of node. Cause The affected DDL or utility operation references a database object in a schema with a schema version that is earlier than the earliest supported schema version of the node where the operation was executed.
Cause The accessing node runs a GA release of the HP Neoview database software and is incompatible with a system schema created by a non-GA release. Effect The operation fails. Recovery Upgrade or downgrade the accessing node to an HP Neoview database software release that is compatible with the affected system schema version. Or, conversely, correct the system schema and reinstalled the Neoview database software on the affected node.
SQL 25218 25218 Schema schema has schema version version1; node cannot access or represent schemas with versions higher than MXV1. schema version1 node MXV1 is a schema that is accessed by a DDL or utility operation. is the schema version of that schema. is the node that encounters the incompatibility or the node where metadata for the schema is stored. is the MXV of that node. Cause A DDL or utility operation attempted to access a schema with a version later than the local node’s MXV.
Recovery Recompile the module with a supported version compiler. SQL 25302 25302 The query plan version is version1; node node does not support query plan versions lower than version2. version1 node version2 Cause • • is the plan version of the affected query. is the name of the node that detects the incompatibility. is the executing node’s oldest supported plan version. Either: Automatic recompilation is attempted (if allowed) with the current compiler.
• • • For automatic recompilations and dynamic SQL, the executor automatically starts a compiler process of the required version and retries the operation. If that strategy succeeds, this message is returned as a warning. If it does not succeed, the operation fails. 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.
is the MXV of the affected node. MXV1 Cause The affected node runs a non-GA version of the HP Neoview database software 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. SQL 25311 25311 System module module has a wrong module version. The expected module version is version1, the actual module version is version2.
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, the HP Neoview database software attempts to recover automatically. SQL 25402 25402 Catalog catalog has previously been registered on node node.
Recovery Correct the error and retry the operation. SQL 25406 25406 Runtime visibility check failed for type of object object trying to access node. type of object object node is the object type of object (for instance, index). is the ANSI name of a database object specified in the DML query. is the expand node name of a remote node where one or more partitions of object resided when the DML query was compiled.
SQL 25422 25422 Catalog catalog cannot be unregistered from node node because database objects in the catalog are present on the node. catalog node is the ANSI name of the target catalog for the UNREGISTER CATALOG command. is the name of the target node for the UNREGISTER CATALOG command. Cause An UNREGISTER CATALOG operation attempted to remove a catalog reference from a node where one or more database objects in that catalog are present. Effect The operation fails.
Recovery For information about file-system errors, see Chapter 25 (page 481). SQL 25427 25427 Catalog catalog1 cannot be unregistered from node node because it is related to catalog2 which has a reference on the target node. catalog1 node catalog2 is the ANSI name of the target node for the UNREGISTER CATALOG command. is the name of the target node for the UNREGISTER CATALOG command. is the ANSI name of a catalog that is related to the target catalog.
Cause A test condition was encountered by debug mode software. The explanatory text contains the details. Effect The affected operation succeeds. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. JDBC Driver Error Messages (29000–29399) This range of numbers is reserved for JDBC driver error messages.
19 Neoview Command Interface (NCI) Messages (29400 Through (29599) This section describes Neoview Command Interface (NCI) error messages. 29400 Could not initialize the console reader. Cause Effect Recovery An Input Output Exception was received while initializing the Input Stream. Unable to launch the Neoview Command Interface. Retry launching the Neoview Command Interface. 29401 Could not initialize the console writer.
29406 Could not find the HP Neoview Type 4 driver in the classpath. Cause The classpath for Neoview JDBC Type 4 Driver JAR file has not been set. Effect Unable to launch the Neoview Command Interface. Recovery Reinstall the Neoview Command Interface by selecting a valid Neoview JDBC Type 4 Driver. 29407 Failed to connect to the database. Connection limit exceeded. Cause Effect The available database connections are already being used.
Recovery Retry the command by switching to the appropriate mode. Issue the help command for more information on the list of supported commands in current mode. 29414 This command is not supported in SQL mode. Cause Effect You specified an interface command that is not supported in SQL mode. The command fails to execute. Recovery Retry the command by switching to the appropriate mode. Issue the help command for more information on the list of supported commands in current mode.
29421 No materialized views found. Cause There are no materialized views present in the current schema. If you specified a pattern, there are no tables matching the specified pattern. Effect None. Recovery Verify if you are in the correct schema by issuing an ENV or a SHOW SCHEMA command. 29422 No materialized view groups found. Cause There are no materialized view groups present in the current schema. If you specified a pattern, there are no materialized view groups matching the specified pattern.
Cause There are no prepared statements present in the current schema. If you specified a pattern for the statement name, there are no prepared statements matching the specified statement name pattern. Effect Recovery None. Not applicable. 29428 No parameters found. Cause There are no parameters set in the current session. If you specified a pattern, there are no parameters matching the specified the pattern name. Effect Recovery None. Not applicable. 29430 Spooling is already OFF.
29435 Invalid ListCount value. The value must be in the range 0-2147483647." Cause range. Effect Recovery The value specified for the SET LISTCOUNT command is not within the acceptable The command fails to execute. Retry the command by specifying a value within the specified range. 29436 The specified statement does not exist in the history buffer. Cause There were no recently executed commands in history matching the command pattern you specified in the FC or REPEAT command.
Cause is the name of a section within the filename to execute. refers to a script file containing commands to be executed by the OBEY command. You specified an invalid section name in the OBEY command. Effect Recovery The command fails to execute. Retry the command by specifying a valid section name in the OBEY command. 29442 Could not create the specified file. Cause Effect Recovery Failed to create the file specified in the SAVEHIST command. The command fails to execute.
Cause Effect You do not have permissions to execute the command. The command fails to execute. Recovery Reconnect to the Neoview Platform by specifying the appropriate login credentials and execute the command. 29449 Server product may not be installed or an internal error has occurred. Please contact support. Cause The Neoview Command Interface Server product has not been installed on the Neoview Platform Effect The command fails to execute. Recovery Contact support personnel to fix this problem.
29456 -d|defaults option cannot be specified with any other options. Cause Effect Recovery You specified an incorrect syntax for the PRUN command. The PRUN command fails to execute. Retry the PRUN command by specifying the valid options. 29457 NWMS not started on this server. Cause Effect Recovery You tried to execute a WMS command when WMS is not running on the server. All the WMS commands fail to execute. Please contact the support personnel to start the WMS process.
Cause refers to the parameter name. You specified an invalid parameter name in the SQL statement Effect The statement fails to execute. Recovery Retry the SQL statement by specifying a valid parameter or use the SET PARAM command to set a parameter value. 29465 Obey commands inside of files are executed in non-interactive mode and require a filename or wildcard. Cause You did not specify a filename or a directory name for the OBEY command within script files.
Effect Recovery The conditional statement fails. N/A. 29473 Unable to compare a string with an integer. Cause Effect Recovery The left side of a conditional statement is a string and the right side is a integer. The conditional statement fails. N/A. 29474 Unable to compare strings using the operator. Cause Effect Recovery An operator other than =, ==, <>, !=, ~=, ^= was used to compare strings. The conditional statement fails. N/A. 29550 Missing Node Dump Pattern.
20 Rowsets Messages (30000 Through 30999) SQL 30002 30002 The given rowset size (num1) must be smaller or equal to the smallest dimension (num2) of the arrays composing the rowset. is the size of the rowset. is the smallest dimension of the rowset arrays. num1 num2 Cause arrays. Effect You specified a rowset size larger than the smallest dimension, num2, of the rowset The operation fails. Recovery Do not attempt recovery.
SQL 30009 30009 Trying to add more elements than maximum rowset size. Cause Effect The HP Neoview database software received an internal error from a rowset. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 30010 30010 An internal error occurred. Rowset is corrupted. Cause Effect The HP Neoview database software received an internal error from a rowset.
Effect The rows that raised the error have not been inserted, and all other rows in the input rowsets have been inserted. Recovery Contact the GMCSC. SQL 30023 30023 Variable used to retrieve ROWSET_ROW_COUNT is either a scalar or an array that is smaller than the size of the rowset used in the previous statement. Cause The variable you used to retrieve ROWSET_ROW_COUNT is either a scalar or an array that is smaller than the size of the rowset used in the previous statement.
SQL 30027 30027 NOT ATOMIC INSERT is not supported on a table that is the subject table of BEFORE triggers. BEFORE trigger trigger-name has table table-name as its subject table. trigger-name table-name is the name of the BEFORE trigger. is the name of the subject table. Cause You attempted to use NOT ATOMIC inserts on a table that is the subject table of at least one BEFORE trigger. Effect The operation fails. Recovery Contact the GMCSC.
Cause You attempted to use NOT ATOMIC inserts on a table that is the subject table of a materialized view. Effect Compilation of the INSERT statement fails. Recovery Contact the GMCSC. SQL 30034 30034 NOT ATOMIC INSERT is not supported on a table that is the subject table of AFTER triggers. AFTER trigger trigger-name has table table-name as its subject table. trigger-name table-name is the name of the AFTER trigger. is the name of the subject table.
21 Neoview Data Warehouse Manager Messages The Data Warehouse Manager messages are: • • • • “Update Statistics Server (2101–2301)” (page 351) “Table Smarts Server (3101–3301)” (page 352) “Defrag Server (4101–4610)” (page 353) “Aging Server (5101–6206)” (page 355) Update Statistics Server (2101–2301) 2101 Environment variable NSMWEB_OPERATION_UID missing. Cause Failed to get the ENV variable NSMWEB_OPERATION_ID from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC.
2201 SQL prepare failed. Cause Recovery GMCSC. Failed to prepare an SQL statement. Analyze the SQL errors and warnings associated with this error. Contact the 2202 SQL execute failed. Cause Recovery GMCSC. Failed to execute an SQL statement. Analyze the SQL errors and warnings associated with this error. Contact the 2301 Pathsend Failed. Cause The Pathsend process failed during a call to the HP Neoview DB Admin scheduler framework. Recovery GMCSC.
Recovery Analyze the associated errors or warnings. Contact the GMCSC. 3205 Invalid Group mode encountered Cause An invalid Group mode was encountered in the input XML. Valid groups are any of the following: • • • • Large Medium Small Tiny Recovery Analyze the associated errors or warnings. Contact the GMCSC. 3301 XML root element name invalidated during DOM traversal. Cause Recovery An unexpected XML root element name was received. Analyze the associated errors or warnings. Contact the GMCSC.
4106 Stdin data stream is empty. Cause Received empty data stream over stdin from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 4201 Create pipe failed. Cause Recovery Failed to create pipes required for FUP service. Analyze the associated errors or warnings. Contact the GMCSC. 4202 Fork process failed. Cause Recovery Failed to fork a FUP service child process. Analyze the associated errors or warnings. Contact the GMCSC. 4203 Exec call failed.
4501 Create pipe failed. Cause Recovery Failed to create the pipes required for the Shell service. Analyze the associated errors or warnings. Contact the GMCSC. 4502 Fork process failed. Cause Recovery Failed to fork a Shell service child process. Analyze the associated errors or warnings. Contact the GMCSC. 4503 Exec call failed. Cause Recovery Failed during exec() call to get Shell service. Analyze the associated errors or warnings. Contact the GMCSC. 4504 Wait on child process failed.
Cause Failed to get the ENV variable NSMWEB_OPERATION_SESSIONID from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 5105 Environment variable NSMWEB_OPERATION_RECURRENCE missing. Cause Failed to get the ENV variable NSMWEB_OPERATION_RECURRENCE from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 5106 Environment variable DBM_DIR_NAME missing. Cause Recovery ENV variable DBM_DIR_NAME missing. Contact the GMCSC. 5107 Stdin data stream is empty.
5301 Pathsend Failed. Cause Received empty data stream over stdin from the HP Neoview DB Admin scheduler framework. Recovery Analyze accompanying errors and warnings. Contact the GMCSC. 5401 Invalid or nonexisting ansi table name. Cause Recovery Received invalid or nonexisting ANSI table name as input. Analyze accompanying errors and warnings. Contact the GMCSC. 5402 Guardian name could not be found for given ansi-name. Cause Failed to get the name for the input ANSI table name.
Recovery Analyze accompanying errors and warnings. Contact the GMCSC. 6203 SQL Allocate SQLDA failed. Cause Recovery Failed to allocate SQLDA. Analyze accompanying errors and warnings. Contact the GMCSC. 6204 SQL Describe using SQLDA failed. Cause Recovery Failed to describe using SQLDA. Analyze accompanying errors and warnings. Contact the GMCSC. 6205 SQL Execute failed for MTS Delete Statement 1. Cause Recovery Failed to execute MTS Delete Statement 1. Analyze accompanying errors and warnings.
22 Neoview Transporter Messages (Client Messages 10013 Through 49005, Server Messages 1000 Through 5302) This section describes the Neoview Transporter client and server error messages. 10013 Server transporter version does not match client version Cause Effect The server does not support the client version in use. Transporter services are not available. Recovery Contact HP to obtain compatible versions of the Transporter client/server components.
Recovery Dependent on the failure documented in the preceding message. 11008 Decryption of encrypted word for reference name failed Cause Effect Recovery Informational message. N/A. N/A. 11009 Entry with reference name is not present in file Cause The entry for reference name specified is not present in the files encctlprops.txt or ctlprops.txt. Effect The requested operation is not completed.
Recovery Specify reference name argument for option -r and plainText word argument for option -p while performing the add operation. 11014 Reference Name argument not specified for option -r in case of del operation Cause The reference name argument is not specified for option -r while performing a delete operation. Effect The delete operation fails. Recovery operation.
11020 Decoding of site key digest from base 64 failed Cause Effect Recovery Error 11033 or Error 11034 gives the cause for failure in decoding the string. Encryption tool exits without executing the requested operation. Retry and if the problem persists, contact your HP service provider. 11021 Decoding of site key from base 64 failed Cause Effect Recovery Error 11033 or Error 11034 gives the cause for failure in decoding the string. Encryption tool exits without executing the requested operation.
Cause Effect Error 11033 or Error 11034 gives the cause for failure in decoding the string. Encryption tool exits without executing the requested operation. Recovery provider. Correct the failure cause, and retry. If the problem persists, contact your HP service 11029 Entry with reference name already exists in file Cause Reference name argument specified for option -r (during add operation) is already present in the file encctlprops.txt.
Recovery Check spelling, option name, and location of option in the control file. Correct and resubmit the control file. 13003 Control file , PARSER ERROR = Cause Effect Recovery Parser found incorrect syntax in provided control file. The client stops processing the control file. Check spelling and area around the line number specified. 13004 Value specified for option =
Recovery Add the missing section in the control file and resubmit the control file. 13014 Element name exceeds maximum length of bytes Cause Effect Recovery A control file entity name has exceeded the maximum number of bytes. The client stops processing the control file. Shorten the name listed in the log and resubmit the control file. 13015 Control file not valid Cause Effect Recovery A section, part, or item of the control file provided is not valid.
Cause Error in element contained in this section. Effect The client stops processing the control file. Recovery Correct and resubmit the control file 13023 Job section errors Cause Error in element contained in this section. Effect The client stops processing the control file. Recovery Correct and resubmit the control file. 13024 Map section errors Cause Error in element contained in this section. Effect The client stops processing the control file.
20004 Version mismatch, Patch numbers are not compatible, control file = Cause Effect Recovery The client is not compatible with the patch version specified in the control file. The client stops processing the control file. Correct the patch version number in the control file and resubmit. 21002 Typeformat = is invalid, control file = Cause Effect Recovery Part of the typeformat is invalid. The client stops processing the control file. Correct and resubmit the control file.
21010 Character is not valid for use in Interval YearMonth format string Cause The format string specified for an interval yearmonth contains a non-supported character. Effect The client stops processing the control file. Recovery Remove the character or replace with a supported character and resubmit the control file. 21011 Character is not valid for use in Interval DateTime format string Cause Effect The format string specified for an interval contains a non-supported character.
21017 Format string contains AM/PM identifier with 24 hour identifier Cause Format string contains AM/PM definition with the character definition for defining 24 hour time format. Effect Recovery The client stops processing the control file. Correct the format string and resubmit the control file. 21018 Format string contains multiple secondformat identifiers Cause Effect Recovery Format string contains multiple second definitions. The client stops processing the control file.
22401 FixedWidth dataformat , number of positions should match number of fields, positions , fields Cause The number of fixed width offsets specified does not match the number of fields specified. Effect Recovery The client stops processing the control file. Correct the fixed width offsets and resubmit the control file. 22402 FixedWidth dataformat has invalid recordlength . Control file Cause Effect Recovery Recordlength is not valid.
22602 Field not valid Cause Effect Recovery One or more errors in a field definition. The client stops processing the control file. Correct the field definitions and resubmit the control file. 23001 Missing mapformat section from control file Cause Effect Recovery The map format section is missing. The client stops processing the control file. Add the missing map format section and resubmit the control file.
23028 Map
Effect Recovery The client stops processing the control file. Correct and resubmit the control file. 26013 Job = , Source and Target providers are not different. Source , target . Control file Cause Effect Recovery Source and Target are the same Source. The client stops processing the control file. Correct and resubmit the control file.
Cause Effect Recovery Multipart option was specified for job type load. The client stops processing the control file. Correct and resubmit the control file. 26022 More than one job is specified in Jobs section, in API mode, control file = Cause Effect A single job is allowed in API mode. The client stops processing the control file. Recovery Correct the control file to have no more than a single job. Move additional jobs to separate control files.
Effect Recovery The client stops processing the control file. Correct and resubmit the control file. 26034 Target provider not defined, target = Cause Effect Recovery JobEntry refers to a target that was not found. The client stops processing the control file. Correct and resubmit the control file. 26035 Map not defined, Map:
36006 File = : bad record = , record is empty or has fewer fields than expected Cause The record in the data file is empty or has less fields than the number of fields specified in the control file. Effect Recovery The record is not loaded. Correct the record in the data file according to the corresponding control file.
36012 File = : bad record = , data conversion error Cause Record field has an unrecognized data type. Effect The affected row is marked as a bad record in the bad records file, and processing will continue. Recovery Check the field mappings in the control file. 36020 Pipe open error, pipe = , error = Cause Effect Recovery There was a problem opening the pipe. The job fails. Examine the open error and take corrective action.
38012 ***Job finished*** Cause Job client statistics for a specified job have been printed, the job is finished (statistics are final). Effect Recovery N/A. This is an informational message. No corrective action is needed. 38013 Job elapsed time
Cause Effect Recovery Maximum discard limit has been reached for the job. The job is terminated. Clean up the data being loaded or increase the discard limit. 38028 Job stopped, error = , exceeded threshold = Cause Effect Recovery Maximum discard limit has been reached for the job. The job is terminated. Too many error occurred when inserting data. Consider removing duplicates. 38030 All job entries under job from control file cannot be run.
Cause Effect Recovery Transporter server component is not installed or the installation is corrupted. Transporter services are not available. Re-install the Transporter server module. 43002 Transporter Service error: . OS error: . SQL error . Error details: Cause Effect Requested service failed for internal errors or incorrect usage. One or more Transporter jobs may be terminated.
Effect The Transporter client does not automatically recover the job in question. Recovery Perform manual recovery of the failed job entries. Specifically, for each listed job entry, you need to determine which rows were not copied from the stage table to the target table and manually copy these rows. Once all job entries have been recovered, you must drop the specified stage table.
Recovery Verify that the Neoview connection information is correctly provided in the control file. Otherwise, contact your HP service provider for resolution. 46002 Encountered Control File persistence error on while processing control file . Execution cannot continue! Cause There was a problem accessing the NEO.HP_TRANSPORTER.CONTROL_FILES table or the NEO.HP_TRANSPORTERCONTROL_FILE_TEXT table. Effect table.
46008 SQL Exception persisting control file Cause There was a SQL exception while querying the Transporter metadata in the HP_TRANSPORTER schema. Effect The Transporter client terminates. Recovery If the SQL error is transient, correct the problem and recover the job, otherwise there is an internal error. Contact your HP service provider for analysis and problem resolution.
Effect The Transporter client terminates. Recovery If the SQL error is transient, correct the problem and recover the job, otherwise there is an internal error. Contact your HP service provider for analysis and problem resolution. 47001 ODBC is not a valid type of source. Use jdbc for source Cause Effect Recovery section. Java transporter client does not recognize odbc data sources. Job is aborted.
47009 Targets for job do not match source . Source should have targets Cause The Transporter client cannot run the identified job because all sources within the job do not have the same set of target/s. Effect The Transporter client terminates. Recovery Within a job all sources should load to the same set of targets. If a job has 2 sources src1 and src2 and if src1 loads to target tgt1 and tgt2 then src2 also should load to tgt1 and tgt2.
Effect The Transporter client terminates. Recovery Verify the data type matches with the table column type or else it should be VARCHAR. 47015 Default map entry for field in table does not have a default value, so a value must be provided for this column Cause The Transporter client cannot run the job because a field which maps to a column that does not have a default value is marked as default in the map section. Effect The Transporter client terminates.Cause An identity map entry is specified for a target column that is not an integral data type (not part of the INT data types). Effect Control file validation fails resulting in an aborted job. Recovery Modify the control file to specify identity map entries for only integral data types. 47021 Identity map entry field for table
cannot be a condition option Cause Effect An identity map entry contains a condition option. Control file validation fails resulting in an aborted job.47026 Reflexive update field on table does not allow update=false and condition=true when the target column does not have a default value Cause A reflexive update operation contains field mapping options "update=false" and "condition=true" on a target column that does not have a default value. Effect Control file validation fails resulting in an aborted job.Cause A field map entry contains both the update and condition options set to true. Condition fields are only updateable with reflexive update. Effect Control file validation fails, resulting in an aborted job. Recovery Modify the control file by not setting both the condition and option field mapping options to true, unless it is a reflexive update. 47033 Cannot get table metadata for SQL source Cause The Transporter client is unable to get table metadata information from an SQL query.
Effect This is a warning message. Recovery None. Option parallelstreams should be set to equal or less than the number of configured cpus. 47041 Duplicate job entry for job found with source and target Cause Effect Recovery The Transporter client finds duplicate job entry within the identified job. The Transporter client terminates. Remove the duplicate job entry and resubmit the control file.
48002 Committing a transaction for job on table ... Cause Effect Recovery Informational message only. N/A. N/A. 48003 Aborting a transaction for job on table ... Cause Effect Recovery Informational message only. N/A. N/A. 48004 Suspending a transaction for job on table ... Cause Effect Recovery Informational message only. N/A. N/A. 48005 Resuming a transaction for job on table ... Cause Effect Recovery Informational message only. N/A. N/A.48009 The job experienced a failure while committing the transaction on table . Job is being terminated! Cause Effect Transaction could not be committed. Job is terminated. Recovery Check the log to see if any TMF issues or Transaction Services prevented the transaction from committing. Retry job after correcting TMF issues. For transaction service related errors, contact your HP service provider for analysis and problem resolution.Cause Effect Unable to leave a transaction. Job is terminated. Recovery Check the log to see if any TMF issues or Transaction Services prevented the transaction from leaving. Retry job after correcting TMF issues. For transaction service related errors, contact your HP service provider for analysis and problem resolution. 49003 Statement for source from job could not be prepared. Error message: Cause Effect A statement prepare operation was executed as part the current job.
1001 Error during service DLL initialization. Transporter version info wasn't retrieved. (Svc Error: 102::) Cause Effect An internal error occurred while retrieving Transporter server version details. Connection is not validated, service request fails, and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. 1002 Error during service DLL initialization. Transporter version info query yielded no results.
Effect Recovery The Transporter server terminates immediately and may cause jobs to terminate. Temporary failure, try restarting the program. 3004 Internal buffer overflow. (Svc Error: 207::) Cause Effect Recovery Internal memory buffer corruption. Service request fails and Transporter jobs may terminate. Refer to the EMS messages for additional information. 3005 Error while beginning service transaction.
3010 Cannot resume service operation, Auto-commit is set to TRUE. (Svc Error: 214::) Cause Effect Recovery Requested service required Autocommit option to be set to FALSE. Service request fails and Transporter jobs may terminate. Refer to the EMS messages for additional information. 3011 Unable to retrieve object UID, query yielded no response. (Svc Error: 219::) Cause Effect Database object may not exist, or related metadata is not present.
Effect Recovery Service request fails andTransporter jobs may terminate. Refer to the EMS messages for additional information. 3205 SQL operation exception. Error while fetching output SQL descriptor details. (Svc Error: 204::) Cause Effect Recovery An internal error occurred while retrieving SQL column metadata. Service request fails and Transporter jobs may terminate. Refer to the EMS messages for additional information. 3206 SQL operation exception.
4001 Internal error. Error retrieving the node name. (Svc Error: GNI201::) Cause Effect Recovery An internal error occurred in retrieval of node names in Neo cluster. Service request fails andTransporter jobs may terminate. Refer to the EMS messages for additional information. 4101 Partition information not found for the table (Svc Error: GPM252::) Cause Effect Table partition information is not available, table may not exist.
Effect Recovery Service request fails andTransporter jobs may terminate. Refer to EMS messages for additional information. 4201 No sequence record found for the table/column. (Svc Error: GNS252::) Cause No identity metadata record found for the table/column pair, table may be non-existing. Effect Service request fails and Transporter jobs may terminate. Recovery Verify the table name is spelled correctly and with the appropriate case.
4401 File open error. (Svc Error: RF251:: ) Cause Effect Recovery Unable to open the requested file for reading. Service request fails and Transporter jobs may terminate. Refer to the EMS messages for additional information. 4402 File read error. (Svc Error: RF252:: ) Cause Effect Recovery An error occurred while trying to read from the requested file. Service request fails and Transporter jobs may terminate.
Cause Effect An internal error occurred while retrieving the current transaction identifier. Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 4506 Error suspending the current transaction.
4601 Error suspending the current transaction. (Svc Error: JT252:: ) Cause An error occurred suspending the current transaction while trying to join another transaction. Effect Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 4602 Cannot save more transaction contexts.
Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 4608 The transaction is already joined by the process. (Svc Error: JT257::) Cause A request was made to join a transaction, which is already joined by the server process. Effect Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information.
4702 Requesting process has no current transaction identifier. (Svc Error: AT252::) Cause A request was made to abort the current transaction, while the process currently has no active transaction. Effect Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 4703 Transaction is already aborted.
Effect Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 4901 Requesting process has no current transaction to suspend. (Svc Error: LT252::) Cause Suspension of current transaction has been requested while there is no active transaction for the process. Effect Service request fails and Transporter jobs may terminate.
5001 Requesting process has no current transaction identifier. (Svc Error: CT252::) Cause Attempt to commit the current transaction while the process has no active transaction. Effect Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 5002 Error committing the transaction.
Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 5102 Error resuming transaction. Transaction ending or aborting. (Svc Error: RT252::) Cause Effect Unable to resume a transaction as it is ending or aborting. Service request fails and Transporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider.
Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider. 5302 Error retrieving the SQL statement attributes. (Svc Error: CQI252::) Cause Effect An internal error occurred while trying to retrieve the SQL statement attributes. Service request fails andTransporter jobs may terminate. Recovery Refer to the EMS messages for additional information. If the problem persists, contact your HP service provider.
23 Neoview Workload Management Services (WMS) Messages This section describes Neoview Workload Management Services (WMS) error messages. Unexpected programming exception: error=14,error_detail=0,process=\segment-name.$ZWMGR,function=FILENAME_TO_PROCESSHANDLE_. Check the server event log on node IP-address for details. Cause Effect You tried to use WMS before starting WMS. The operation fails. Recovery Start WMS before using it.
Recovery Retry the operation with a percentage between 0 and 100. For more information, see the Neoview Workload Management Services Guide. Unexpected programming exception: ComExecDirect: exception detail = 0, error message = Invalid MAX_MEM_USAGE...must be between 0 and 100 Cause Effect You specified a percentage that is not between 0 and 100. The operation fails. Recovery Retry the operation with a percentage between 0 and 100. For more information, see the Neoview Workload Management Services Guide.
Effect The operation fails. Recovery Retry the operation with a comment that is 256 characters or less, including spaces. For more information, see the Neoview Workload Management Services Guide. Unexpected programming exception: ComExecDirect: exception detail = 0, error message = Invalid ACTIVE begin time...could not locate begin time Cause Effect You specified an invalid start time. The operation fails. Recovery Retry the operation with a valid start time from 00:00 to 23:58.
Effect The operation fails. Recovery Retry the operation with an end time that is earlier than the start time. For more information, see the Neoview Workload Management Services Guide. Unexpected programming exception: ComExecDirect: exception detail = 0, error message = Invalid EXEC_TIMEOUT...must be between 0 and 1440 Cause Effect You specified an execution timeout value that is not between 0 and 1440 minutes. The operation fails.
Cause Effect Recovery You tried to delete HP_DEFAULT_SERVICE, which is disallowed. The operation fails. You are prohibited from deleting HP_DEFAULT_SERVICE. Unexpected programming exception: ComExecDirect: exception detail = 0, error message = Cannot delete SYSTEM Cause Effect Recovery You tried to delete the SYSTEM service, which is disallowed. The operation fails. You are prohibited from deleting the SYSTEM service.
Cause You issued a WMS command, and the WMS ZQSDLL could not identify a WMS process on any of the segments during a FastExecDirect() call. Effect Recovery The command fails. Contact your HP service representative. Unexpected programming exception: ComExecDirect: exception detail = 0, error message = No valid connection with WMS Cause You issued a WMS command, and the WMS ZQSDLL could not identify a WMS process on any of the segments during a FastFetch() call. Effect Recovery 414 The command fails.
24 SQLSTATE Values Returned by the Neoview Database The HP Neoview database software 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.
Table 24-1 SQLSTATE Values Beginning 00000 416 SQLSTATE SQLCODE Error Text 00000 0 Successful completion. 01000 6008 Statistics for column name were not available; as a result, the access path chosen might not be the best possible. 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.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0150Y 1034 The Neoview database software was not able to initialize. 0150Z 1035 Catalog catalog-name already exists 01510 1036 Only super ID can execute DROP SQL. 01511 1037 The Neoview database software is not installed on system node. 01512 1038 Not all catalogs have been dropped from the system. 01513 1039 The drop SQL statement could not be executed.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) 418 SQLSTATE SQLCODE Error Text 01521 1073 Only the super ID user can execute INITIALIZE SQL. 01523 1075 Catalog name contains at least one schema. The catalog must be empty. 01525 1077 Metadata table name does not contain information for view name. 01526 1078 The format of the specified location name name is invalid. 01527 1079 Unable to prepare the statement. 01528 1080 Duplicate references to column name in the create request.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0153A 1118 Cannot create object name in metadata schema. 0153B 1119 Cannot drop metadata object name. 0153C 1120 Attempting to change the audit flags for a table in an unsupported way. 0153D 1121 Attempting to perform a partition add, move, or drop on table name. Partition operations are not allowed on tables with vertical partitions, entry sequenced operations, and SYSKEY-only partitioned tables.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) 420 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.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0160H 2017 Unable to create server process name. No more processes (PCBs) available. 0160I 2018 Unable to create server process name. Library conflict. 0160J 2019 Unable to create server process name. Unable to allocate virtual memory. 0160K 2020 Unable to create server process name. Unlicensed privileged program. 0160L 2021 System error num in name from name.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) 422 SQLSTATE SQLCODE Error Text 0161V 2067 Descriptor name has already been defined in this module. The previous definition is being retained and this latest one ignored. 0161W 2068 A procedure body must be a SELECT, INSERT, UPDATE, DELETE, DECLARE CATALOG, DECLARE SCHEMA, or a static DECLARE CURSOR. 0161X 2069 A static cursor declaration might appear only in the body of a procedure. 0161Y 2070 Invalid statement type in this context.
Table 24-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0162X 2105 Unable to compile this query because of incompatible Control Query Shape (CQS) specifications. Suggestion: Inspect the CQS in effect. 0162Y 2106 Unable to compile this statement since it is too long. Suggestion: Break up large statements into smaller pieces. 0162Z 2107 Unable to compile this statement. Suggestion: Address the issue(s) raised in the reported warning(s).
Table 24-2 SQLSTATE Values Beginning 01700 (continued) 424 SQLSTATE SQLCODE Error Text 0170L 3021 Expected an unsigned number as the second operand within the parentheses, not value. 0170M 3022 The name operator is not yet supported. 0170N 3023 The COLLATE clause in a sort specification is not yet supported. 0170O 3024 The MATCH PARTIAL clause is not yet supported. 0170P 3025 The format of the subvolume name part in the specified location name name is invalid.
Table 24-2 SQLSTATE Values Beginning 01700 (continued) SQLSTATE SQLCODE Error Text 0171J 3055 Duplicate DELETE rules specified. 0171K 3056 Duplicate UPDATE rules specified. 0171L 3057 Invalid size value in the ALLOCATE clause. 0171M 3058 The BLOCKSIZE value must be 4096. 0171N 3059 Invalid size value in the MAXSIZE clause. 0171O 3060 Invalid percentage value in the DSLACK clause. 0171P 3061 The format of the specified location name name is invalid.
Table 24-2 SQLSTATE Values Beginning 01700 (continued) 426 SQLSTATE SQLCODE Error Text 0172G 3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. 0172H 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. 0172I 3090 Duplicate LOCKLENGTH clauses. 0172J 3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. 0172K 3092 Duplicate BLOCKSIZE clauses. 0172L 3093 Duplicate DCOMPRESS clauses.
Table 24-2 SQLSTATE Values Beginning 01700 (continued) SQLSTATE SQLCODE Error Text 0173E 3122 The format of the system name part in the specified location name name is invalid. Currently the system name part must be \NSK or /E/NSK. 0173F 3123 The format of the file name part in the specified location name name is invalid. The file name part must be eight characters long and end with the digits 00. 0173J 3127 Invalid character in identifier name. 0173K 3128 object name is a reserved word.
Table 24-2 SQLSTATE Values Beginning 01700 (continued) 428 SQLSTATE SQLCODE Error Text 0174H 3161 name was not declared in the procedure parameter list. 0174I 3162 Procedure parameter name was not used. 0174J 3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. 0174K 3164 Data type mismatch between output host variable and selected value. 0174L 3165 Min or max precision or exponent value exceeded, num.
Table 24-3 SQLSTATE Values Beginning 01800 SQLSTATE SQLCODE Error Text 01800 4000 Internal error in the query binder. 01801 4001 Column name is not found. Tables in scope: name. Default schema: name. 01802 4002 Column name is not found. Table name not exposed. Tables in scope: name. Default schema: name. 01803 4003 Column name is not a column in table name, or, after a NATURAL JOIN or JOIN USING, is no longer allowed to be specified with a table correlation name.
Table 24-3 SQLSTATE Values Beginning 01800 (continued) 430 SQLSTATE SQLCODE Error Text 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 (namenamename) name is not allowed. 0180Z 4035 Type name cannot be cast to type type. 01810 4036 The source field of the EXTRACT function must be of DateTime or Interval type.
Table 24-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 0181V 4067 The operands of function name must be character data types. 0181W 4068 The operand of function name must contain an even number of characters. 0181X 4069 Column name uses an unsupported collation, name. 0181Y 4070 The operand of function name must be exact numeric. 0181Z 4071 The first operand of function name must be a datetime.
Table 24-3 SQLSTATE Values Beginning 01800 (continued) 432 SQLSTATE SQLCODE Error Text 0182Z 4107 Column name has no default value, so DEFAULT cannot be specified. 01830 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. 01831 4109 Sequence functions placed incorrectly: name. 01832 4110 The query contains sequence functions but no SEQUENCE BY clause: name. 01833 4111 The query contains a SEQUENCE BY clause but no sequence functions.
Table 24-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 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. 0184I 4162 Groupby not supported for stream expression. Tables in scope: name. 0184J 4163 Groupby not supported for embedded name expression.
Table 24-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 0185U 4210 Embedded UPDATE/DELETE statements are not supported within an IF statement. 0185W 4212 table name cannot be used to satisfy order requirement on the stream because it is partitioned. 0185X 4213 Use of rowsets in a predicate with embedded UPDATE/DELETE not supported. 0185Y 4214 The SET ON ROLLBACK clause is not allowed on a non-audited table. Table: name.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01K06 8006 The stream timed out, but the cursor is still open. 01K07 8007 The operation has been canceled. 01K08 8008 Catalog name name is invalid. 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.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) 436 SQLSTATE SQLCODE Error Text 01KBJ 8415 The provided DATE, TIME, or TIMESTAMP is not valid and cannot be converted. 01KBK 8416 A datetime expression evaluated to an invalid datetime value. 01KBL 8417 An error occurred during the evaluation of a USER function. 01KBM 8418 The USER function is not supported on this platform. 01KBN 8419 An arithmetic expression attempted a division by zero.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01KGX 8609 Waited rollback performed without starting a transaction. 01KGY 8610 Transaction subsystem name reported error num on a waited rollback transaction. 01KH0 8612 Transaction mode cannot be set if the transaction is already running. 01KH1 8613 SQL cannot commit or rollback a transaction that was started by application. 01KH2 8614 SQL cannot begin a transaction when multiple contexts exist.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) 438 SQLSTATE SQLCODE Error Text 01KN2 8830 There is no current context. 01KN3 8831 Either no current context or the module to which the statement belongs is not added to the current context. 01KN4 8832 Transaction has not been started. 01KN5 8833 The input parameter is an invalid SQL transaction command. 01KN6 8834 The SQL installation directory could not be found. Operating system error number.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01KO1 8865 Module file name has obsolete procedure location table header. 01KO2 8866 Module file name has obsolete procedure location table entry. 01KO3 8867 Error while reading from file name. 01KO4 8868 Unable to create context when current transaction is implicitly started by SQL.
Table 24-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01L5O 9204 Invalid option option specified. Value must be range. 01L5P 9205 UPDATE STATISTICS for object name is not supported. 01L5Q 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. 01L5R 9207 You are not allowed to generate histogram statistics on an ISO88591 CHARACTER SET column which contains a null terminator character.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01M0M 10022 Sort Error: FILE_CREATE failed 01M0N 10023 Sort Error: FILE_OPEN_ failed 01M0O 10024 Sort Error: SetMode failed 01M0O 10024 Sort Error: SetMode failed 01M0Q 10026 Sort Error: AWAITIOX failed 01M0R 10027 Sort Error: FILE_GETINFOLIST failed 01M0S 10028 Sort Error: POSITION failed 01M0T 10029 Sort Error: FILE_GETINFO_ failed 01M18 10044 Sort Error: IO did not complete 01M1B 10047 Sort
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) 442 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. 01N64 11220 A Java method completed with an uncaught java.sql.SQLException with invalid SQLSTATE.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01P0L 13021 name is already defined. 01P0M 13022 Cursor name is already defined. 01P0N 13023 name is already defined as a dynamic cursor. 01P0O 13024 Cursor name was not declared. 01P0P 13025 Warning(s) near line num. 01P0Q 13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements. 01P0R 13027 Only one EXEC SQL MODULE statement is allowed.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) 444 SQLSTATE SQLCODE Error Text 01P1L 13057 End-of-file processing generated unexpected cursor status of num for cursor name. 01P1M 13058 Unable to open SQL CLI header file name. 01P1O 13060 Unable to open the listing file name. 01P1P 13061 Invalid NUMERIC precision specified near line num. 01P1Q 13062 Unsigned long long type not allowed near line num. 01P1R 13063 Identifier name not defined near line num.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01PE8 13512 Input file error while processing EXEC SQL. 01PE9 13513 The BIT data type is not implemented in the Neoview database software. 01PEA 13514 The CHARACTER SET attribute is not implemented in the Neoview database software. 01PEB 13515 Picture name is not valid for a host variable. 01PEC 13516 Unexpected end of input file encountered after line num.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) 446 SQLSTATE SQLCODE Error Text 01R0H 15017 Statement name not found. 01R0I 15018 Break was received. The last statement might be lost. 01R0J 15019 num values were supplied in the USING list while the statement contains num unnamed parameters. 01R0K 15020 The USING list must contain at least one parameter value. 01R0L 15021 The USING list cannot contain more than num parameter values.
Table 24-5 SQLSTATE Values Beginning 01M01 (continued) 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. 01U0D 30013 Hostvar used to set input size of rowset has zero or negative value.
Table 24-6 SQLSTATE Values Beginning 07001 (continued) 448 SQLSTATE SQLCODE Error Text 07008 -8807 Trying to allocate more than num entries for a descriptor. 07008 -8893 The statement argument count does not match the descriptor entry count. 07009 -8829 Trying to set descriptor item for an entry that is either invalid or greater than the maximum entry count for that descriptor. 07009 -8843 Trying to retrieve an item, num, that is out of range.
Table 24-6 SQLSTATE Values Beginning 07001 (continued) SQLSTATE SQLCODE Error Text 0A000 -3080 The [NO]SERIALWRITES clause is not supported. 0A000 -3105 Currently only range, hash and system partitioning are supported. 0A000 -3119 The WITH LOCAL CHECK OPTION clause is not supported. 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.
Table 24-6 SQLSTATE Values Beginning 07001 (continued) 450 SQLSTATE SQLCODE Error Text 22011 -8403 The length argument of function SUBSTRING cannot be less than zero or greater than source string length. 22012 -4075 Division by zero in constant expression name. 22012 -8419 An arithmetic expression attempted a division by zero. 22015 -3044 Invalid interval num. 22019 -8409 The escape character argument of a LIKE predicate must be one character in length.
Table 24-6 SQLSTATE Values Beginning 07001 (continued) SQLSTATE SQLCODE Error Text 25000 -8819 Begin transaction failed while preparing the statement. 25000 -8820 Transaction commit failed while closing the statement. 25000 -8832 Transaction has not been started. 25000 -8833 The input parameter is an invalid SQL transaction command. 25000 -8841 User application committed or aborted a transaction started by SQL.
Table 24-7 SQLSTATE Values Beginning 42000 452 SQLSTATE SQLCODE Error Text 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. 42000 -3204 EXTERNAL NAME clause is badly formed. 42000 -3205 EXTERNAL NAME clause is required. 42000 -3206 The name for an object of this type must be fully qualified, or set NAMETYPE ANSI.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -2062 Static cursor name has already been defined in this module. The previous definition, as a dynamic cursor, is being retained and this latest one ignored. 42000 -2063 Dynamic cursor name has already been defined in this module. The previous definition, as a static cursor, is being retained and this latest one ignored. 42000 -2064 Dynamic cursor name has already been defined in this module.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) 454 SQLSTATE SQLCODE Error Text 42000 -3006 In a dynamic cursor declaration both the cursor and the statement must be named in the same way: both must be literals or both must be string host variable expressions. 42000 -3007 In an ALLOCATE CURSOR statement both the cursor and the statement must be named using string host variables. 42000 -3008 Precision of name UNSIGNED data type, value, cannot exceed 9.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 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. 42000 -3060 Invalid percentage value in the DSLACK clause. 42000 -3061 The format of the specified location name name is invalid. 42000 -3062 Duplicate MAXSIZE clauses in the PARTITION clause.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) 456 SQLSTATE SQLCODE Error Text 42000 -3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. 42000 -3092 Duplicate BLOCKSIZE clauses. 42000 -3093 Duplicate DCOMPRESS clauses. 42000 -3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements. 42000 -3095 Duplicate [NO]ICOMPRESS clauses. 42000 -3096 Duplicate [NO]SERIALWRITES clauses.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -3135 Precision of float, value, cannot exceed 54. 42000 -3136 Only LEFT, RIGHT, and FULL OUTER JOIN are valid in {oj ...} 42000 -3138 A key-sequenced table with range partitioning requires a FIRST KEY clause. 42000 -3139 A range-partitioned index requires a FIRST KEY clause. 42000 -3142 INTO clause host variables are not allowed in a static cursor.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) 458 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.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -4025 Error while preparing constraint name on table name. 42000 -4027 Table name is not insertable. 42000 -4028 Table name is not updateable. 42000 -4030 Column name is an invalid combination of datetime fields (num, num, num). 42000 -4031 Column name is an unknown data type, num. 42000 -4032 Column name is an unknown class, num. It is neither a system column nor a user column.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) 460 SQLSTATE SQLCODE Error Text 42000 -4063 The operands of function name must be comparable character data types (that is, of the same character set and collation). 42000 -4064 The operands of function name must be compatible character data types (that is, of the same character set). 42000 -4066 The operands of a UNION must be of equal degree. 42000 -4067 The operands of function name must be character data types.
Table 24-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 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. 42000 -4113 The sample size for name Sampling must be num. 42000 -4114 An absolute sample size must have a scale of zero.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) 462 SQLSTATE SQLCODE Error Text 46007 -11213 Specified signature is invalid. Reason: A return type must not be specified. 46101 -11215 Java execution: Invalid null input value at parameter position value. 46103 -11205 Java class class-file-name was not found in external path path-name. HY011 -8855 Statement attribute cannot be set now. HY011 -8857 Statement attribute cannot be set now.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text 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. X0116 -1042 All PRIMARY KEY or UNIQUE constraint columns must be NOT NULL. X0118 -1044 Unable to create constraint name.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) 464 SQLSTATE SQLCODE Error Text X0128 -1080 Duplicate references to column name in the create request. X0129 -1081 Loading of index name failed unexpectedly. X012A -1082 Validation for constraint name failed unexpectedly. X012B -1083 Validation for constraint name failed; incompatible data exists in table. X012C -1084 Invalid default value for column name. X012D -1085 The calculated key length is greater than 255 bytes.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X013K -1128 Invalid API request. Details: text. X013M -1130 The column requires a default value. X013O -1132 An added column cannot have both DEFAULT NULL and NOT NULL. X013P -1133 Only the super ID can perform this operation. X013Q -1134 Concurrent DDL operations are being performed on the given object. The current operation cannot be performed.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) 466 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.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X021G -2052 Optimizer internal counters: namenamenamename. X021H -2053 ASSERTION FAILURE CAUGHT BY OPTIMIZER! Attempting to recover and produce a plan. X021N -2059 Warnings while reading values from DEFAULTS table name. X0221 -2073 Only the super ID user can compile system module name. X0222 -2074 The name name is reserved for future system modules.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) 468 SQLSTATE SQLCODE Error Text X034I -3162 Procedure parameter name was not used. X034J -3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. X0352 -3182 Extra semicolon(;) in a compound statement. X0400 -4000 Internal error in the query binder. X0422 -4074 CONTROL QUERY successful. X042U -4102 The FIRST/ANY n syntax cannot be used with in an outermost SELECT statement.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) 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. X0450 -4180 Stream expression not supported for top level DELETE statement.
Table 24-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X048J -4307 Rowset parameters are not allowed in a CALL statement. X048K -4308 Internal error: unsupported SQL data type value specified for a CALL statement parameter. X0500 -5000 Internal error in the query normalizer. X0600 -6000 Internal error in the query optimizer. X0602 -6002 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid values.
Table 24-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X08O4 -8868 Unable to create context when current transaction is implicitly started by SQL. X08O5 -8869 The specified file number is not a QFO, or the file number is not internally associated with a QFO object (CLI internal error). X08O6 -8870 The current statement is not associated with any QFO. X08O7 -8871 Nowait tag is not specified in the statement-id.
Table 24-9 SQLSTATE Values Beginning X0700 (continued) 472 SQLSTATE SQLCODE Error Text X08G3 -8579 Similarity check failed: name X08GP -8601 Error returned from file system while locking/unlocking. 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.
Table 24-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X08NW -8860 Module file name has obsolete module header. X08NX -8861 Module file name has obsolete descriptor location table header. X08NY -8862 Module file name has obsolete descriptor location table entry. X08NZ -8863 Module file name has obsolete descriptor header. X08O0 -8864 Module file name has obsolete descriptor entry. X08O1 -8865 Module file name has obsolete procedure location table header.
Table 24-9 SQLSTATE Values Beginning X0700 (continued) 474 SQLSTATE SQLCODE Error Text X0A05 -10005 Sort Error: Unexpected error value.
Table 24-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X0B5M -11202 Language Manager initialization failed. Details: Unable to initialize JVM. X0B5N -11203 The Language Manager failed to create its class loader, possibly due to corrupt LmClassLoader.class file. X0B5Q -11206 Java class class-file-name was not found in external path path-name. X0B5R -11207 Java class class-file-name failed to initialize.
Table 24-10 SQLSTATE Values Beginning X0D01 (continued) 476 SQLSTATE SQLCODE Error Text X0D0E -13014 Unable to open the output source file name. X0D0F -13015 Unable to open the module definition file name. X0D0G -13016 Descriptor name name conflicts with SQLC default name name. X0D0H -13017 Descriptor name is multiply defined. X0D0I -13018 Descriptor name name is invalid. X0D0J -13019 Statement name name uses name, a reserved name SQLC generates.
Table 24-10 SQLSTATE Values Beginning X0D01 (continued) SQLSTATE SQLCODE Error Text 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. X0D1O -13060 Unable to open the listing file name. X0D1P -13061 Invalid NUMERIC precision specified near line num.
Table 24-10 SQLSTATE Values Beginning X0D01 (continued) 478 SQLSTATE SQLCODE Error Text X0DE6 -13510 The SQL declare section might not contain COPY or REPLACE. X0DE7 -13511 End of input file while processing EXEC SQL. X0DE8 -13512 Input file error while processing EXEC SQL. X0DE9 -13513 The BIT data type is not implemented in SQL/MX. X0DEA -13514 The CHARACTER SET attribute is not implemented in SQL/MX. X0DEB -13515 Picture name is not valid for a host variable.
Table 24-10 SQLSTATE Values Beginning X0D01 (continued) SQLSTATE SQLCODE Error Text X0F0U -15030 The specified define already exists. Use alter or delete and add. X0F0V -15031 The specified define does not exist. X0F0W -15032 An error occurred while adding, altering or deleting this define. X0F0X -15033 Break was received. X0F0Y -15034 Invalid LOG file name.
Table 24-10 SQLSTATE Values Beginning X0D01 (continued) 480 SQLSTATE SQLCODE Error Text X0P8N -25311 System module module has a wrong module version. The expected module version is version1. The actual module version is version2. X0U08 -30008 Internal error. Rowset index is out of range. X0U09 -30009 Internal error. Trying to add more elements than maximum rowset size. X0U0A -30010 Internal error. Rowset is corrupted.
25 File-System Errors Some file-system errors are new or changed for the Neoview platform and are not documented in the Guardian Procedure Errors and Messages Manual, see “New or Changed File-System Errors for the Neoview Platform” (page 494). Some error messages generated by the Neoview platform include file-system error codes. For example: SQL 1024 1024 File system error error-number occurred on text-string-1. text-string-2.
Error Number File-System Error Text 0023 The disk address is out of bounds, or the maximum number of blocks in an alternate-key file is exceeded. 0024 Privileged mode is required for this operation. 0025 AWAITIO[X] or CANCEL attempted on file opened for waited I/O. 0026 AWAITIO[X] or CANCEL or CONTROL 22 attempted on a file with no outstanding I/O requests. 0027 An operation was attempted with outstanding no-waited I/O requests pending.
Error Number File-System Error Text 0059 The disk file is bad; there is a mismatch in the internal file control block, or the file structure in a structured file is inconsistent. 0060 The file resides on a removed disk, the device is stopped or not open, or a server has failed and a process has been replaced by a different process with the same name since the server was opened.
Error Number File-System Error Text 0097 Transaction aborted by call to ABORTTRANSACTION. 0098 Allocation of a Transaction Control Block failed because the local table is full, or the table on a remote segment is full. 0099 Process attempted to use features of a microcode option that is not installed on this segment. 0100 Device is not ready or the controller is not operational. 0101 The tape is write protected. 0102 Printer paper out, bail open or end of ribbon.
Error Number File-System Error Text 0156 Tape command rejected. 0157 I/O process internal system error. 0160 Request is invalid for device state; protocol error. 0161 Impossible event occurred for line state. 0162 Operation timed out. 0163 EOT received or power at autocall unit is off. 0164 Disconnect received or data line is occupied (busy). 0165 RVI received or data line not occupied after setting call request. 0166 ENQ received or auto call unit failed to set present-next-digit.
Error Number File-System Error Text 0201 The current path to the device is down, an attempt was made to write to a nonexistent process, the message-system request was incorrectly formatted, or an error was found in the message system interface. 0210 Device ownership changed during operation. 0211 The node performing the operation failed during the operation. 0213 Channel data parity error (path error). 0214 Channel timeout (path error).
Error Number File-System Error Text 0522 Either the SET^FILE or CHECK^FILE operation is not valid on an open file or OPEN^FILE was called for a file already open. 0523 An EDITREAD or EDITREADINIT error occurred. 0524 The specified file was not open. 0525 The requested operation was inconsistent with the access mode. 0526 The required operation failed because of insufficient stack space. 0527 The temporary buffer required for a non-blocking WRITE^FILE operation was not provided.
Error Number File-System Error Text 0590 The parameter value is invalid or inconsistent with another. 0593 The request was cancelled. 0594 A tape-catalog error was returned to Tape Services. Refer to the event log for detailed information. 0595 An error was returned to Tape Services. Refer to the event log for detailed information. 0597 A required item is missing from an item list. 0632 Not enough stack space to complete request.
Error Number File-System Error Text 0899 An attempt to switch nodes failed. 1024 The specified SQL subset is not defined to the file system. 1025 The supplied row or update value violates one of the constraints for the table. 1026 The selection expression on an SQL view has been violated. 1027 The Data Access Manager process encountered a bad SQL label or tree of labels. 1028 The Data Access Manager process accessed a label of an unexpected type during an OPEN or during an SQL label operation.
Error Number File-System Error Text 1057 Unable to access a table that is being altered by another user. 1058 Unable to access a table that is being dropped by another user. 1059 Unable to access a protection view whose underlying table does not exist or is inconsistent. 1060 SQL internal error. 1061 The cursor is no longer defined in the Data Access Manager process. 1062 SQL internal error. 1063 SQL internal error.
Error Number File-System Error Text 1091 The file or table cannot be purged until the NOPURGEUNTIL date. 1092 The operation cannot be performed because the resulting disk directory entry would be too long. Too many columns, partitions, indexes, protection views, or constraints have been defined. 1093 The operation cannot be performed because the resulting row would exceed the RECLENGTH value defined for the relative table.
Error Number File-System Error Text 1128 An operand was scale truncated during expression evaluation. 1129 Scale truncation was needed but prohibited during expression evaluation. 1130 Unable to use SQL on a system where the product is not installed. 3501 More control information was received than this dialect allows. 3502 Server does not have sufficient available storage for this request. 3503 Server does not support this dialect. 3504 Server does not support this request type.
Error Number File-System Error Text 4035 No message of desired type. 4036 Identifier removed. 4045 Deadlock condition. 4046 No record locks available. 4061 No data sent or received. 4099 Function not implemented. 4101 Operation would block. 4102 Operation now in progress. 4103 Operation already in progress. 4104 Socket operation on nonsocket. 4105 Destination address required. 4106 Message too long. 4107 Protocol wrong type for socket. 4108 Protocol not available.
Error Number File-System Error Text 4185 XDR encoding error. 4186 XDR decoding error. 4195 Out-of-band data available. 4196 Invalid socket call. 4197 File type not supported. 4198 C file (code 180) not odd unstructured. 4199 Insufficient internal memory. 4200 Too many symbolic links during path name resolution. 4201 File-set catalog internal consistency error. 4202 Root file set is not mounted. 4203 POSIX not running or not installed. 4204 Illegal byte sequence.
Recovery Wait, then try again. Check the system for processes that are performing too many concurrent I/O operations, or rewrite the application to request fewer locks. If the problem persists, contact your service provider. 758 (%1366) Unable to allocate space from the control block pool or trying to open too many files or partitions on a volume.
Effect The procedure sets the error code and returns without performing the requested operation. Recovery This is a Data Access Manager internal error. Contact your service provider. 764 (%1374) Unable to allocate space from the revive pool.(device type: 3) Cause No space is available in the revive pool to allocate a new buffer. Effect The procedure sets the error code and returns without performing the requested operation. Recovery Wait, then try again.
