HP Neoview Messages Manual (Volume 1) HP Part Number: 611472-001 Published: August 2010 Edition: HP Neoview Release 2.
© Copyright 2010 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.........................................................................................................5 This Manual Has Two Volumes..............................................................................................................5 Supported Releases.................................................................................................................................5 Audience........................................................................
12 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399).............................................................................................................................239 13 Materialized Views Messages (12000 Through 12329)......................................251 14 Messages Generated by the Message System (16000 Through 16999)...........267 15 Internal Stored Procedures Messages (19000 Through 19999).........................269 16 Utility Messages (20000 Through 23099)....
About This Document The Neoview SQL database is the HP relational database management system (RDBMS) 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.
Chapter Title Chapter 10 (page 225) “UPDATE STATISTICS Messages (9200 Through 9218)” Chapter 11 (page 229) “Executor Sort and Scratch File I/O Messages (10000 Through 10199)” Chapter 12 (page 239) “Trigger, UDR Server, and Language Manager Messages (11000 Through 11399)” Chapter 13 (page 251) “Materialized Views Messages (12000 Through 12329)” Chapter 14 (page 267) “Messages Generated by the Message System (16000 Through 16999)” Chapter 15 (page 269) “Internal Stored Procedures Messages (19000
Chapter (page) Description Messages Added or Changed Chapter 17 (page 333) Chapter 17 (page 333) This chapter is new.
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.
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 Guide to Stored Procedures in Java Information about how to use stored procedures that are written in Java within a Neoview database. Neoview Query Guide Information about reviewing query execution plans and investigating query performance of Neoview databases. Neoview Transporter User Guide Information about processes and commands for loading data into your Neoview platform or extracting data from it.
• ODBC Client Administrator Online Help Context-sensitive help topics that describe how to use the ODBC Data Source Administrator. README files for installing Connectivity client products — — — — — README for the HP Neoview Windows Client Package README for the HP Neoview JDBC Type 4 Driver README for the HP Neoview ODBC Driver for Windows README for the HP Neoview ODBC Drivers for UNIX README for the HP Neoview ADO.
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” in Volume 2 of this manual 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 is the name of the module. num is the line number. details are the details of the error. 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.
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 a file-system error number. error Cause Effect See the accompanying error message for the cause. The operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385). 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. Recovery Apply the recovery of the accompanying error message.
Recovery You must drop all user-created catalogs before dropping SQL. SQL 1039 1039 The DROP SQL statement could not be executed. Cause Effect See the accompanying error message for the cause. The HP Neoview database software does not drop SQL. Recovery Apply the recovery of the accompanying error message. SQL 1040 1040 The use of ALTER on metadata tables is not permitted. Cause An ALTER TABLE statement was issued naming a table that is part of the HP Neoview database metadata.
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 is the name of the HP Neoview database object. error-number is the file-system error number.
Effect The catalog is not dropped. None of its schemas are dropped. Recovery Drop all schemas in the catalog and resubmit. SQL 1077 1077 Metadata table table-name does not contain information for view view-name. table-name is the name of the metadata table. view-name 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. Effect The operation fails. Recovery Do not attempt recovery.
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 The operation fails. Recovery 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. key is a partition key. object-name is the name of the table being created or changed. 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 This is an internal error. Effect 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 The MODIFY utility did not process the request. Recovery 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.
Recovery Specify a valid base table and resubmit. 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.
Effect The operation fails. Recovery Specify that the column-name is NOT NULL NOT DROPPABLE and resubmit. SQL 1136 1136 For an added column, the PRIMARY KEY clause cannot specify NOT DROPPABLE. Cause You used the ALTER TABLE statement to add a column specifying a primary key that is not droppable. A primary key added through ALTER TABLE must be droppable. Effect The operation fails. Recovery Change the ALTER TABLE statement to specify DROPPABLE for the primary key.
Effect The operation fails. 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 is the HP Neoview platform file name of a partition of object. error-number is a Neoview platform file-system error. Cause Effect An ALTER TABLE or ALTER INDEX operation encountered a file-system error. The operation fails.
first-key-string is the erroneous value used in the FIRST KEY clause for column-name. Cause In a CREATE TABLE statement, a value specified as first key is not a quoted string, but the type of the column for which this value is specified is one of the character data types. Effect 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.
SQL 1150 1150 Table table-name was not created because Partition Overlay Support could not generate volume names for the partitions to reside on. table-name is the name of the table. 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.
Effect The operation fails. Recovery Correct the syntax so that the correct object name is used. SQL 1156 1156 Synonym name does not exist or object type is invalid for the current operation. Cause view. Effect You specified a create or alter of synonym name on an object that is not a table or The operation fails. Recovery Correct the syntax so that the correct name is used. SQL 1157 1157 Synonym object name is the same as previous mapping.
SQL 1161 1161 System generated column SYSKEY cannot be specified as part of the PARTITION BY clause. 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 is the target of the GIVE operation.
Effect The label create, drop, or alter operation that is part of the DDL statement is performed serially, rather than in parallel. The serial method decreases performance compared to the parallel method. Recovery No corrective action is necessary. This message is a warning. SQL 1167 1167 Cannot change ownership of object name because authid is not the super id or service ID. object is the SYSTEM CATALOG. name is the name of the system catalog. authid is the target of the GIVE operation.
Recovery Retry the SQL statement either by using valid disk pool number or by ignoring the DISK POOL clause so that the Neoview software will place the table on a random disk pool. SQL 1175 1175 Since table table-name does not contain an IDENTIFIER column, the sequence generator object was not recreated. table-name is the name of the table. Cause You attempted to update sequence generator information for a table that does not contain an IDENTITY column.
name space is the name space of the object. create time is the time the object was created. owner is the role that created the object. operation info provides details about what actually happened. Cause Effect An unexpected error occurred during statement execution. The operation fails. Recovery Contact HP support to analyze the failure. SQL 1180 1180 The required subvolume name for locations in schema schema-name is subvol-name. schema-name is the schema in which the object is being created.
Cause File-system error. Effect The operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385). SQL 1184 1184 You do not have the required privilege(s) on column-name. column-name is the name of a column specified in the references part of a referential integrity constraint. Cause You attempted to establish a referential integrity constraint on a column for which the executing user ID has no REFERENCES privileges. Effect The operation fails.
dependency-information is a list of unique constraints that cause the circular dependency. Cause You tried to define a referential constraint that is creating a circular dependency, where one of the columns of the table is referencing a column that belongs to the same table, either directly or indirectly. Effect The operation fails. Recovery None. You cannot define a referential constraint that creates a circular dependency. SQL 1194 1194 Label could not be dropped (file error ).
table-name is the table being dropped whose DDL was to be saved. platform-pathname is the pathname of the file to which the DDL was to be saved. Cause are: • • • A file-system error occurred when you attempted to save a table DDL. Possible reasons The directory /usr/tandem/sqlmx/ddl did not exist or could not be created. The system did not have write access to /usr/tandem/sqlmx/ddl Insufficient file space was available. Effect The table is not dropped.
Cause You specified a literal with a character set other than ISO88591 in the text of a create view statement. Effect The operation fails. Recovery Specify only ISO88591 literals in the command. SQL 1240 1240 The character set for a PARTITION KEY column must be ISO88591. Cause Effect You specified a literal with a character set other than ISO88591 as a partition key. The operation fails. Recovery Specify only ISO88591 literals as partition keys.
column-name is the column of object-name that corresponds to the invalid key value. object-name is the name of the affected object. Cause A utility command specified a key value that is inconsistent with the data type of the column that corresponds to the key value. Effect The operation fails. Recovery Specify valid key values and resubmit. SQL 1248 1248 Partition name partition-name has already been used. Each partition in an object should have a unique name.
Recovery None. This is a warning message only. SQL 1252 1252 The existing index index-name to be used by a unique or primary constraint has not been populated. Please populate the index and then try to add the constraint again. is the name of an existing unpopulated index. index-name Cause An existing index that is not populated has been chosen for a unique or primary constraint, which is not allowed. Effect The operation fails. Recovery Populate the index and resubmit.
Recovery See the Neoview SQL Reference Manual for the list of reserved object names. Choose a name that is not reserved and reissue the CREATE statement. SQL 1264 1264 Duplicate privileges are not allowed in a GRANT or REVOKE statement. Cause Effect You specified duplicate privileges in a GRANT or REVOKE statement. The operation fails. Recovery Reissue the GRANT or REVOKE statement, specifying a single privilege or a list of distinct privileges.
Effect The operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385). SQL 1271 1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object. object-name is the ANSI name of the affected database object. number is the specified number of extents.
Recovery To drop the constraint, you must remove the UNIQUE constraint or add an additional NOT NULL constraint to the columns that contain UNIQUE constraints and only one NOT NULL constraint for that column. SQL 1276 1276 The PARTITION clause cannot be specified for an SQL/MP Table, SQL/MP view or SQL/MX view. The partition partition-name was specified for object table-name.
SQL 1284 1284 Table table-name cannot be dropped because it was specified to be NOT DROPPABLE. table-name Cause Effect is the name of an HP Neoview database table. An attempt was made to drop a table that is not droppable. The operation fails. Recovery Ensure that the table could be dropped, and issue SQL command ALTER TABLE table-name DROPPABLE to make the table droppable. SQL 1285 1285 Schema schema-name cannot be dropped because it contains NOT DROPPABLE table table-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 1301 1301 NO ACTION referential action for referential-triggered-action clause is not yet supported as specified by ANSI SQL99 standard. To alter the behavior, set an appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default. referential-triggered-action can either be ON DELETE or ON UPDATE.
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. The warning can be issued repeatedly for a single CREATE SCHEMA command if multiple schemas already exist with subvolume as the schema subvolume.
SQL 1311 1311 Unable to action-text constraint constraint-name due to the above errors. action-text is create. constraint-name is a constraint name. Cause An error occurs during the creation of the constraint. The error that described the cause of the failure already appears. This error message provides clarification. Effect The operation fails. Recovery No recovery is necessary. SQL 1312 1312 Unable to action-text object-name due to the above errors.
Effect Effect You cannot grant the WITH GRANT OPTION to objects at schema level. Recovery None. Contact HP Support if you require changes to system defaults. SQL 1400 1400 The default value of column column-name contains characters that cannot be converted to ISO_MAPPING 'character-set'. column-name is the column name. character-set is { ISO88591 | SJIS | UTF8 }.
SQL 1502 1502 The OBJECTS - REPLICAS definition schema relationship for type object may be corrupt. type is the type of the affected object. object is the fully qualified ANSI name of the affected object. Cause A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected REPLICAS definition schema table. Effect The operation fails. Recovery Do not attempt recovery.
column-name Cause Effect is the name of the IDENTITY column. An unsupported data type has been specified for the IDENTITY column. The statement fails. Recovery Specify a data type that the HP Neoview database supports for IDENTITY columns, and resubmit the statement. SQL 1511 1511 There can only be one IDENTITY column for a table. Cause Effect More than one IDENTITY column has been defined for the table. The operation failed. Recovery Define only one IDENTITY column for a table.
Cause The index required by the constraint is disabled, so the constraint cannot be enabled. Effect The operation failed. Recovery Populate index and retry the request. SQL 1519 1519 Constraint constraint on table table cannot be disabled because it is a foreign key constraint. constraint is the name of the constraint. table is the name of the table. Cause The specified constraint is defined as a foreign key constraint and cannot be disabled. Effect The operation failed.
SQL 1572 1572 The seq-gen-option value cannot be a negative number for identity-col-name. seq-gen-option is the name of the sequence generator option. identity-col-name is the name of the identity column. Cause Effect You specified a negative value for the sequence generator option. The statement fails. Recovery Specify a positive value for the sequence generator option, and resubmit the statement.
Effect The statement fails. Recovery Specify a value for the sequence generator option that is not greater than the maximum value that is allowed for the data type, and resubmit the statement. Note If the data type is a LARGEINT, the SQL 1576 message does not contain the column name. This error is caught, but the column name is not known. For this example . . .
Effect The statement fails. Recovery Specify either the MAXVALUE or INCREMENT BY sequence generator option to be altered for the IDENTITY column. SQL 1594 1594 An error occurred trying to access the current value of the IDENTITY column col-name. is the name of the IDENTITY column. col-name Cause An internal error occurred when the platform tried to access the current value of the IDENTITY column internal sequence generator. Effect The statement fails.
If the IDENTITY column's default specification type is GENERATED ALWAYS AS IDENTITY, recalibrate the CURRENT_VALUE of the internal sequence generator by using the ALTER TABLE ALTER COLUMN SET INCREMENT BY statement and manual calibration instructions. SQL 1598 1598 The new CURRENT_VALUE, current-value, for the IDENTITY column, column-name, for the table, table-name, will be greater than the maximum allowed, maximum-value. current-value is the CURRENT_VALUE of the IDENTITY column.
Recovery Correct the recalibration value and resubmit the statement. SQL 1600 1600 Unable to lock table, table-name, for the IDENTITY column, column-name, during recalibration. table-name is the name of the table that contains the IDENTITY column. column-name is the name of the IDENTITY column. Cause The table containing the IDENTITY column could not be locked in SHARED MODE because there is a locking contention on the table. Effect The statement fails to execute.
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 is the error number. name is the DEFAULTS table name. values 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 is information about the error. name is the name of the file. number 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 is the name of the server process. number-1 is the error number. number-2 is the TPCError. text 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.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. 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.
Cause The HP Neoview database software was unable to create server process name because it is an unlicensed privileged program. The server process was configured incorrectly at installation. Effect The operation fails. Recovery The server process must be a licensed privileged program. Check your configuration. SQL 2021 2021 System error number occurred in procedure name from process name. number is the error number. procedure name is the name of the procedure.
Recovery Check why the RTS server process identified in the error message is not running, fix any condition indicated by the returned operating system error, and try to restart the process. SQL 2025 2025 Server process name could not be created - CPU is unavailable; process id. name is the server process name. process id 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.
Cause Effect The new maximal value is smaller than the current minimal value. The new maximal value is not set. Recovery Specify a new maximal value that is greater than the current minimal value. SQL 2033 2033 process id: Operating system error number while communicating with process name. process id identifies the process. number is the error number. name is the name of the server process.
SQL 2038 2038 Character set name is not supported for SQLCI attribute TERMINAL_CHARSET. name is the name of the character set. Cause You specified a non-ISO88591 character set name. Effect The operation fails. Recovery Specify an ISO88591 character set name. SQL 2050 2050 attribute is not the name of any DEFAULTS table attribute. attribute is the attribute name you specified. Cause If the SQLSTATE is 42000, this is an error.
This additional information will also be helpful: the DDL for the tables involved, the query that produced this warning, and any CONTROL QUERY SHAPE and CONTROL QUERY DEFAULT settings in effect when the error occurred. SQL 2054 2054 HIST_NO_STATS_ROWCOUNT should always be greater than or equal to CQD HIST_NO_STATS_UEC. Present value of HIST_NO_STATS_UEC is 'value'. Cause You attempted to set the CQD HIST_NO_STATS_ROWCOUNT value as less than the current value of CQD HIST_NO_STATS_UEC.
name is the name of the table. Cause You received an error on the DEFAULTS table name. A previous error message has appeared with specific information. Effect The operation fails. Recovery None. SQL 2060 2060 Procedure name has already been defined in this module. 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.
Effect The HP Neoview database software uses the first dynamic cursor definition. Recovery This is an informational message only; no corrective action is needed. SQL 2065 2065 Statement name was not found in module name. name is the statement name. 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.
Cause In a module definition file, you specified a query statement such as SELECT, INSERT, UPDATE, DELETE, or a DDL statement. These statements must be embedded in procedures. Effect The HP Neoview database software is unable to compile the module. Recovery Correct the syntax and resubmit. SQL 2071 2071 The name name has already been declared or defined in this module. The previous definition, as a definition type, is being retained and this latest one ignored. name is the name of the module.
SQL 2076 2076 HIST_NO_STATS_UEC should always be less than or equal to CQD HIST_NO_STATS_ROWCOUNT. Present value of HIST_NO_STATS_ROWCOUNT is 'value'. Cause You attempted to set the CQD HIST_NO_STATS_UEC value as greater than the current value of CQD HIST_NO_STATS_ROWCOUNT. 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.
Recovery Use the error to diagnose and correct the problem. SQL 2084 2084 Error number while writing value bytes to file name. Cause HP Neoview database software received error number while writing to file name. value shows the number of bytes being written. 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. number is the error number. name is the name of the file.
name is the name of the file. Cause You included more than one module statement. name will be used. Effect The HP Neoview database software ignores the second module statement. Recovery Informational message only; no corrective action is needed. 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.
SQL 2098 2098 The compilation type compilation completed with value warnings. Cause Effect compilation type completed with the number of warnings given as value. None. Recovery Informational message only; no corrective action is needed. SQL 2099 2099 The compilation type compilation failed with value errors and value warnings. Cause compilation type failed with the number of errors and warnings given as value. Effect Any statement with an error is not compiled.
CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM'; Correct the CONTROL QUERY SHAPE specification and resubmit. 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.
Recovery This is an informational message. To prevent this warning, turn off query caching before query preparation. SQL 2109 2109 Invalid Character error converting SQL statement from character set from character set to character set to character set. from character set may be any of the supported character sets. One of the “from” or “to” character set is always UCS2. to character set may be any of the supported character sets. One of the “from” or “to” character set is always UCS2.
Cause You invoked mxCompileUserModule on an application file that is not an HP Neoview platform ELF object file. Effect The operation fails. 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.
-option Cause Effect is the command-line option. You invoked mxCompileUserModule with an unrecognized command-line option. The operation fails. Recovery Review the allowable command-line options by invoking mxCompileUserModule. Verify that the desired command-line options are spelled correctly and retry the command. SQL 2208 2208 mxCompileUserModule requires an application file name. Cause Effect You invoked mxCompileUserModule without supplying an application file. The operation fails.
SQL 2213 2213 A syntax error was encountered: expecting an identifier instead of string. 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.
SQL 2222 2222 SQL module module name was not found in application file name. module name is the requested module name. application file 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.
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 Declare a cursor name, or use the name of a previously prepared statement, and resubmit. 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 The operation fails. Recovery 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 The operation fails. Recovery 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 The operation fails. Recovery 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 The operation fails.
Effect The operation fails. Recovery 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 The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit.
SQL 3038 3038 PIC X types cannot have leading signs, or any signs at all. Cause Effect You specified a PIC X type with a sign, which is not supported. The operation fails. Recovery Remove the sign, or redefine the type, and resubmit. SQL 3039 3039 PIC X types do not have any COMP representation. Cause Effect You specified a PIC X type with COMP, which is not supported. The operation fails. Recovery Remove the COMP, or redefine the type, and resubmit. SQL 3040 3040 Precision zero is not valid.
SQL 3045 3045 The date ‘value’ is not valid. Cause Effect You specified an invalid date value. The operation fails. Recovery Change the date value and resubmit. SQL 3046 3046 The time ‘value’ is not valid. Cause Effect You specified an invalid time value. The operation fails. Recovery Correct the time value and resubmit. SQL 3047 3047 The timestamp ‘value’ is not valid. Cause Effect You specified an invalid timestamp value. The operation fails.
SQL 3052 3052 Duplicate NOT NULL clauses were specified in column definition name. Cause Effect You defined column name with more than one NOT NULL clause. The operation fails. Recovery Define the column with only one NOT NULL clause and resubmit. SQL 3053 3053 Duplicate PRIMARY KEY clauses were specified in column definition name. Cause Effect You defined column name with more than one PRIMARY KEY clause. The operation fails. Recovery Define the column with only one PRIMARY KEY clause and resubmit.
SQL 3059 3059 The specified size value (in the MAXSIZE clause or EXTENT size clause) is not valid. Cause Effect You provided an invalid size value in the MAXSIZE clause. The operation fails. Recovery 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. Cause Effect You provided an invalid percentage value in the DSLACK clause. The operation fails.
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 3068 3068 The ALLOCATE and DEALLOCATE clauses cannot coexist in the same ALTER INDEX statement. Cause You specified an ALTER INDEX statement with both an ALLOCATE and a DEALLOCATE clause, which is not supported.
SQL 3074 3074 The SEPARATE BY clause is not supported. Cause Effect You specified the SEPARATE BY clause, which is not supported. The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 3081 3081 Duplicate ALLOCATE clauses were specified. Cause Effect You specified duplicate ALLOCATE clauses. The operation fails. Recovery Correct the syntax and resubmit. SQL 3082 3082 Duplicate [NO]AUDIT clauses were specified. Cause Effect You specified duplicate [NO]AUDIT clauses. The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 3095 3095 Duplicate [NO]ICOMPRESS clauses were specified. Cause Effect You specified a statement with duplicate [NO]ICOMPRESS clauses. The operation fails. Recovery 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 You specified a statement with duplicate PARALLEL EXECUTION clauses. The operation fails. Recovery Correct the syntax and resubmit. SQL 3103 3103 Duplicate PARTITION clauses were specified. Cause Effect You specified a statement with duplicate PARTITION clauses. The operation fails. Recovery Correct the syntax and resubmit.
Effect The operation fails. Recovery Correct the statement to include one of these clauses. SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause Effect You specified a statement with duplicate STORE BY clauses. The operation fails. Recovery Correct the syntax and resubmit. SQL 3110 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. Cause You specified a statement with both LIKE and ATTRIBUTE(S) clauses, which is not supported. Effect The operation fails.
SQL 3115 3115 Duplicate ISOLATION LEVEL clauses were specified. Cause Effect You specified a statement with duplicate ISOLATION LEVEL clauses. The operation fails. Recovery Correct the syntax and resubmit. SQL 3116 3116 Duplicate transaction access mode clauses were specified. Cause Effect You specified a statement with duplicate access mode clauses. 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 3133 3133 PERFORM is valid only in COBOL programs. Cause You specified a PERFORM statement, which is supported only in COBOL programs. Effect The operation fails. Recovery Correct the syntax and resubmit.
Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3139 3139 A range partitioned index requires a FIRST KEY clause. Cause You attempted to create a range-partitioned index without a required FIRST KEY clause. Effect The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 3148 3148 Environment variable value is being ignored because this version of the code is Release, not Debug. 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 Effect You attempted to create a catalog without specifying a catalog name. 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 3169 3169 name is not a known collation. Cause Effect You attempted to use a collation that is not a known collation. The operation fails. Recovery Correct the syntax and resubmit.
SQL 3176 3176 Subqueries are not allowed in the IF Condition. Cause Effect You specified an IF statement that contains a subquery. 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. Effect The operation fails.
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 The operation fails. Recovery 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 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 The statement does not compile. Recovery Do not use DELETE or UPDATE in a CREATE VIEW statement. SQL 3219 3219 The value for DYNAMIC RESULT SETS must be between 0 and 255.
Effect SHOWLABEL does not display output. Recovery 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.
Cause The DDL statement coded in unicode contains non-ISO88591 characters. The HP Neoview database software does not support arbitrary unicode characters. Effect The operation fails. Recovery Remove non-ISO88591 characters and resubmit. SQL 3409 3409 Declaring a cursor on an embedded INSERT statement is not yet supported. Cause Effect You attempted to declare a cursor on an embedded INSERT statement. The operation fails. Recovery Modify the statement and resubmit.
Recovery Specify values for all the tuples in the list, or specify DEFAULT for all the tuples in the list. 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. SQL 3416 3416 The last operand of function name must not be NULL. name is the name of the function.
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. SQL 3420 3420 Illegal size value num for the number of disk pools in the DISK POOL OF clause. num is the specified disk pool number.
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. Effect The statement fails to execute and the transaction options do not take affect. Recovery Use MULTI COMMIT ON only with non-embedded DELETE statement.
Recovery Supply the input values for the IDENTITY column.
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 The operation fails. Recovery Correct the syntax and resubmit. SQL 4017 4017 Derived column name name was specified more than once. Cause Effect 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 You attempted to update table name, which is not updatable. The operation fails. Recovery None. SQL 4030 4030 Column name has an invalid combination of datetime fields (internal field number, internal field number, internal field number). Cause Effect You specified column name, which is an invalid combination of datetime fields. The operation fails. Recovery Correct the syntax and resubmit.
Effect The operation fails. Recovery 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 The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 4043 4043 The operand of function name must be character. Cause You specified an operand for function name that is not a character, which is required. Effect The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 4050 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation).
SQL 4055 4055 The select lists or tuples must have comparable data types. and type2 are not comparable. Cause Effect type1 You specified select lists or tuples with incompatible data types. The operation fails. Recovery Correct the syntax and resubmit. SQL 4056 4056 Exposed name name appears more than once. Cause You specified a statement with an exposed table name that appears more than once. For example: SELECT * FROM tblx, tblx; Effect The operation fails.
Effect The operation fails. Recovery 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 The operation fails. Recovery Correct the function and resubmit.
SQL 4069 4069 Column name uses an unsupported collation. Cause Effect You specified a column name that uses an unsupported collation. The operation fails. Recovery Correct the syntax and resubmit. SQL 4070 4070 The operand of function name must be exact numeric. Cause Effect You specified an invalid operand for function name. It must be type exact numeric. 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 There is an overflow in constant expression name. The operation fails. Recovery Correct the syntax and resubmit. SQL 4077 4077 Function name accepts only one or two operands. Cause You specified an invalid argument in function name. This function accepts only one or two arguments, both numeric. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4078 4078 Function name does not accept a weight operand.
SQL 4086 4086 Environment variable or define value does not exist. Cause Effect You specified an environment variable or define value that does not exist. The operation fails. Recovery Define the environment variable and resubmit. SQL 4087 4087 Prototype value 'value' is not a valid qualified name. Cause Effect You specified a prototype value that is not a valid qualified name. The operation fails. Recovery Correct the syntax and resubmit.
Effect The operation fails. Recovery 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 The operation fails. Recovery Correct the syntax and resubmit. SQL 4097 4097 A NULL operand is not allowed in function name. Cause Effect You attempted to use a NULL operand in function name, which is not supported.
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 The operation fails. Recovery 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 Effect You attempted to assign NULL to a NOT NULL column name. The operation fails. Recovery Correct the syntax and resubmit. SQL 4123 4123 NULL cannot be cast to a NOT NULL data type. Cause Effect You attempted to cast NULL to a NOT NULL data type. 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. Cause The HP Neoview database software is preparing to lock more than one table. Effect None.
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 The operation fails. Recovery 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 4139 4139 Use of a subquery in the WHERE clause of a Long Running Update statement is not supported.
SQL 4154 4154 Statement may not compile due to an order requirement on embedded name expression. Cause You attempted to compile an embedded DELETE or embedded UPDATE expression using an ORDER BY without using a clustering key or a secondary index. Effect The HP Neoview database software is unable to compile the statement. Recovery Create a secondary index materializing the order and resubmit. SQL 4156 4156 Inner relation of left join cannot be embedded command name. Tables in scope: name.
table-names1 and table-names2 are names of HP Neoview database tables that are in scope. Cause You attempted to perform a union operation that has an embedded INSERT, UPDATE, or DELETE statement. Effect The operation failed. Recovery Modify the statement and resubmit. 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.
Effect The operation failed. Recovery Modify the statement and resubmit. SQL 4168 4168 Stream expressions are not supported in subqueries. Cause Effect You attempted to perform a subquery that included a stream expression. 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...
SQL 4175 4175 Join between embedded name1 expression and embedded name2 expression is not supported. Tables in scope: name3. Cause You attempted to perform a join between two embedded expressions. 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.
Recovery Modify the statement and resubmit. SQL 4184 4184 Columns that are part of a referential constraint cannot be updated using embedded UPDATE statements. Cause You attempted to perform an embedded UPDATE statement on columns that are part of a referential constraint. Effect The operation fails. Recovery Modify the statement and resubmit. SQL 4189 4189 ORDER BY clause in an embedded INSERT, UPDATE, or DELETE statement is not supported.
SQL 4193 4193 The schema name prefix volatile-schema-prefix is reserved and cannot be used. volatile-schema-prefix is a reserved schema prefix used internally to manage volatile tables. Cause The volatile schema managed by the system uses a reserved schema prefix. This prefix is a reserved word and cannot be used in an SQL statement. Effect None. 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.
Cause You attempted to run a compound statement that contains an embedded INSERT statement. Effect The operation fails. Recovery Modify the statement and resubmit. SQL 4202 4202 SEQUENCE BY is not supported for embedded name expressions. Cause Effect You attempted to perform an embedded expression that included SEQUENCE BY. The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit.
Cause You attempted to use an index for stream access that does not cover all output columns of the base table. Effect The HP Neoview database software is unable to compile the statement. Recovery Restrict the select list or add the missing columns to the index. SQL 4208 4208 Index name and other indexes covering a subset of columns do not cover all columns referenced in WHERE clause of stream.
Recovery Change the table’s AUDIT attribute and resubmit. SQL 4215 4215 Stream access is not allowed on a non-audited table. Table: name. Cause Effect You attempted to use stream access on a nonaudited table. The operation fails. Recovery Change the table’s AUDIT attribute and resubmit. SQL 4216 4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded delete statement. Cause You attempted to use either a FIRST n or an ANY n clause in an embedded UPDATE or DELETE statement.
Effect This is a warning message only. Results will be unpredictable. The host variable could have any one of the actual OUT values. Recovery Use different host variables for each of the OUT or INOUT parameters. SQL 4305 4305 Parameter value for user-defined routine routine-name is an OUT or INOUT parameter and must be a host variable or a dynamic parameter.
Effect The operation fails. Recovery Correct the query and retry the request. SQL 4313 4313 Function rand()is not supported. Cause Effect You attempted to use the random function, which is not supported. The operation fails. Recovery Correct the syntax and resubmit. SQL 4320 4320 Stream access not allowed on multi-partitioned table, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set to OFF. Table in scope: table-name.
Effect The operation failed. Recovery In the left operand of the PARTITIONING_KEY clause of the KEY_RANGE_COMPARE function, specify columns that match the partitioning columns of table table-name. SQL 4336 4336 Embedded operation statements are not allowed in a join operation. Table in scope: table-names. operation is an INSERT operation. table-names are the names of HP Neoview database tables that are in scope. Cause Effect You attempted a join operation using an embedded INSERT statement.
SQL 4342 4342 The specified window frame clause is not valid. Cause Effect The window frame clause specified was not valid. The operation fails. Recovery Rewrite the query and use a valid window frame clause. SQL 4343 4343 A Window Frame Clause cannot contain a FOLLOWING term, either explicitly or implicitly. 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.
Cause A MIN/MAX window function that has UNBOUNDED FOLLOWING in its frame clause is used in the same query with RANK, DENSE_RANK, ROW_NUMBER or other MIN/MAX window functions that have UNBOUNDED PRECEDING in their frame clause on one end of the window frame and bounded PRECEDING or FOLLOWING on the other end. Effect The operation fails.
Cause Effect Multiple RANK functions with different expressions were specified. The statement fails. Recovery Rewrite the query so that it does not contain multiple RANK functions with different expressions. SQL 4362 4362 Using ASC/DESC with sequence functions is not supported. Cause Effect ASC/DESC was specified in the expression of the RANK sequence function. The statement fails to prepare. Recovery Rewrite the query so that it does not contain ASC/DESC in the argument of the RANK sequence function.
Recovery Rewrite the query so that it does not contain the RANK non-sequence function and sequence functions in the same scope. SQL 4368 4368 Nesting rank functions is not supported. Cause Effect The query contains nested RANK functions. The statement fails to prepare. Recovery Rewrite the query so that it does not contain nested RANK functions. SQL 4369 4369 Parameters and outer references are not supported with rank function.
Cause The compiler was attempting to end a transaction. The compiler, executor and TMF transaction identifiers did not match. Effect The operation fails. Recovery The transaction IDs can be used to help determine how the transaction was started and why the transaction identifiers didn't match.
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 column-names from table table-name were not available. The columns were being used by op-name operator. As a result, the access path chosen might not be the best possible. column-names is a list of column names of the affected columns. table-name is the name of the HP Neoview database table to which the columns belong.
• • Could not create directory dirname, a component of the path is not a directory. Could not create directory dirname, errno is errnum. filename is the specified file name. dirname is the specified directory name. errnum is the returned file-system error number. Cause The operation was attempted either in an invalid mode or by specifying an invalid directory. Effect The operation failed with the indicated error message.
Recovery None necessary; however, you can: • Generate new statistics now by using UPDATE STATISTICS FOR TABLE table-name ON NECESSARY COLUMNS. SQL 6012 6012 Statistics for column column-name from table table-name were generated with small sample. As a result, the access path chosen might not be the best possible. column-name is the name of the affected column for which statistics are missing. table-name is the name of the HP Neoview database table to which the column belongs.
Recovery If the Error code is 0, no action is required by the User. If the Error code is 33 or 35, Users should refer to Chapter 21 (page 385) for information about recovering from file-system error codes 33 and 35.
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 The command fails. Recovery Check the syntax rules for the command and reenter it accordingly. SQL 7112 7112 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 Check the syntax rules and then reenter the command, specifying at least 1 character. SQL 7343 7343 An internal SqlMX structure is invalid. Cause Effect An internal structure is not valid. The command fails.
Recovery Rewrite your query to prevent the join from overflowing its memory to disk. Contact HP Support for assistance.
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 Effect You pressed the break key. 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.
n1 is the time limit of the processor in seconds. pp is the disk process where the problem was detected. Cause The CPU time accumulated in an SQL disk process exceeded the limit n1 for which the query is configured. This problem was detected in disk process pp. Effect The operation fails. Recovery If possible, rewrite the query so that it can complete within the configured limit, or increase the limit. SQL 8026 8026 Server declined cancel request. The query ID of the targeted query was not found.
SQL 8100 8100 Define name does not exist Cause Effect You attempted to reference a define that does not exist. 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 8101 8101 The operation is prevented by check constraint name1 on table name2. name1 is the name of the constraint. name2 is the name of the table.
SQL 8105 8105 The operation is prevented by the check option on view name. is the name of the view. name Cause You attempted to perform an operation on table name that is prevented by the check option on view name. Effect The operation fails. Recovery Insert into the base table rather than this view. SQL 8106 8106 The last row fetched by this cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT... of statements.
Effect The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8301 8301 File system error error occurred on anchor file name. error is the HP Neoview platform file-system error code. name is the fully qualified Neoview platform file name of an SQL anchor file.
Cause The CLASS attribute of the DEFINE is not correct. For example, the CLASS attribute for an MP table name DEFINE should be MAP, not SORT. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8401 8401 A row subquery or SELECT...INTO statement cannot return more than one row. Cause The table or tables had more than one row that satisfied the query.
Cause You specified a TRIM function with an invalid trim 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 8405 8405 The operand of function CONVERTTIMESTAMP is out of range. Cause You attempted to reference the operand of a CONVERTTIMESTAMP function that is out of range. Effect The operation fails.
SQL 8412 8412 An input character host variable is missing its null terminator. Cause Effect You specified an input character host variable that is missing its null terminator. 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 8413 8413 The string argument contains characters that cannot be converted.
Cause You attempted to perform the USER function, which is not supported on this platform. 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 8419 8419 An arithmetic expression attempted a division by zero. Cause Effect An expression attempted to divide by zero, which is invalid. 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 8425 8425 NULL cannot be assigned to a DEFAULT NULL NOT NULL column. Cause Effect You attempted to assign a null value to a column that is defined as NOT NULL. 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.
object-name Cause Effect is the name of the object. The file system returned error NSK err on object-name. 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 8552 8552 Error number was returned by the file system while fetching the version of the system name. number is the error number returned. name is the name of the system.
SQL 8572 8572 The statement has incurred a fatal error and must be deallocated. 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 8573 8573 The user does not have level privilege on table or view name. level is the user privilege level. name is the name of the object.
Recovery Verify the location of the object and resubmit. SQL 8578 8578 Similarity check passed. Cause Effect The similarity check passed. None. Recovery Informational message only; no corrective action is needed. SQL 8579 8579 Similarity check failed: name name Provides the reason the similarity check failed. Cause The similarity check failed. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 8580 8580 No partitions of table name could be accessed.
Cause Failed to raise ESP priority at the beginning of query execution. The reason the query failed is indicated by the Guardian error number. The failure is likely because the ESP no longer exists. Effect The query operation fails. Recovery Execute the query again. The failure is likely temporary and the re-executed query may pass. SQL 8597 8597 Statement was automatically retried retry-value time(s). Delay before each retry was delay-value seconds. See next entry for the error that caused this retry.
Cause Transaction subsystem name has returned error number while starting a transaction. Effect The operation fails. Recovery Contact the GMCSC. SQL 8605 8605 Committing a transaction which has not started. Cause Effect You attempted to commit a transaction that has not been started. The operation fails. Recovery Correct the syntax so that the transaction is started before it is committed, and resubmit. SQL 8606 8606 Transaction subsystem name returned error number on a commit transaction.
name is the name of the subsystem. number is the error number. Cause Transaction subsystem name has returned error number while performing a waited rollback transaction. Effect The operation fails. Recovery Contact the GMCSC. SQL 8612 8612 Transaction mode cannot be set if the transaction is already running. Cause Effect You attempted to set the transaction mode, but the transaction is already running. The operation fails. Recovery Abort and restart the transaction if you must change its mode.
Effect The operation may fail or succeed. Recovery Recreate the target table with the same definition as the source table. SQL 8652 8652 Version($0~int0) of source($0~string0) must be the same as the version($1~int1) of target($1~string1). $0~int0 is the version of the source object. $0~string0 is the source object name. $1~int1 is the version of the target object. $1~string1 is the target object name. Cause Effect The version of the source object and the target object are different.
Recovery Cleanup the environment and retry the query. SQL 8657 8657 Could not recover the specified object. Reason: $0~string0 $0~string0 Cause Effect is the reason why replicate could not recover the object. See the reason, $0~string0, to determine the cause. The operation fails. Recovery See the reason, $0~string0, to determine how to recover from the error. SQL 8658 8658 Invalid ipAddr and/or portNum values returned after communication with BDR Service process.
Recovery Delete all data from target table or add purgedata target option in replicate command. SQL 8665 8665 Execution of replicate_schema_ddl stored procedure failed. Details: $0~string0 $0~string0 Cause is the error detail. This is an internal error. Effect The operation fails. Recovery None. Report the entire message to HP Support. SQL 8666 8666 A concurrent replicate operation is in progress for $0~string0 $1~string1. That operation must complete before this one can proceed.
Cause The HP Measure utility encountered an error while attempting to update HP Neoview database counters. Effect Measure fails to update the database counters. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8801 8801 Descriptor allocation failed because the descriptor already exists in the current context. Cause Effect This is an internal error. The operation fails.
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 8807 8807 Trying to allocate more than value entries for a descriptor. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery.
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 8814 8814 The transaction mode at run time (value) differs from that specified at compile time (value). Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery.
SQL 8820 8820 Transaction commit failed while closing the statement. Cause Effect This is an internal error. The operation fails. Recovery None. Contact the GMCSC. SQL 8821 8821 Rollback transaction failed during the process of fetching the statement. Cause Effect This is an internal error. The operation fails. 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.
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 8829 8829 Trying to set descriptor item for an entry that is either invalid or greater than the maximum entry count for that descriptor. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery.
Recovery Locate the Neoview database installation directory, correct your syntax, and resubmit. SQL 8835 8835 Invalid SQL descriptor information requested. Cause The descriptor item requested from the descriptor area or being set in the descriptor area is not valid. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
SQL 8841 8841 User application committed or aborted a transaction started by SQL. This transaction needs to be committed or aborted by calling SQL COMMIT or ROLLBACK WORK. Cause The HP Neoview database software started a transaction that was committed or aborted by an embedded program, rather than by the Neoview database software. Effect The operation fails. Recovery Commit or abort the transaction by calling SQL COMMIT or ROLLBACKWORK.
Recovery Correct the syntax and resubmit. SQL 8851 8851 A CLI Parameter bound check error occurred. Cause The HP Neoview database software received a call-level interface (CLI) parameter bound check 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 8852 8852 Holdable cursors are supported for only streaming cursors and embedded update/delete cursors.
SQL 8857 8857 Local authentication : User: $0~string0. $0~string0 Cause Effect is the name of the user on the platform. The password has expired for this platform user, but is within the grace period. The operation fails. Recovery Change the password for the user using NCI or HPDM, and try to logon again. SQL 8858 8858 The value (value) is not a valid SQL identifier. Cause Effect You attempted to reference an invalid SQL identifier, displayed in the message. The operation fails.
name is the file name. Cause The module file name has an obsolete descriptor header. Effect The operation fails. Recovery Rebuild the module file and resubmit. SQL 8864 8864 Module file name has an obsolete descriptor entry. name is the file name. Cause The module file name has an obsolete descriptor entry. Effect The operation fails. Recovery Rebuild the module file and resubmit. SQL 8865 8865 Module file name has an obsolete procedure location table header. name is the file name.
Cause Effect The file number does not refer to a quasi file object (QFO). 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 8870 8870 The current statement is not associated with any QFO. Cause Effect No quasi file object (QFO) file number is associated with the current statement. The current operation fails. Recovery Do not attempt recovery.
Cause Effect The rollback savepoint operation completed successfully. The statement has been rolled back without aborting the current transaction. Recovery Use the errors that accompany this one to diagnose and correct the problem before retrying the underlying INSERT, UPDATE, or DELETE operation. SQL 8879 8879 The buffer to return the Query ID is too small.
Effect back. The cursor was closed but all rows affected by opening this cursor have been rolled Recovery OPEN the cursor again and FETCH all rows until SQLCODE = 100 is returned. SQL 8889 8889 The provided buffer to retrieve Result Set proxy syntax is either null or not big enough. Cause An HP Neoview database call-level interface (CLI) function was unable to provide proxy syntax for a stored procedure result set because the provided target buffer is either null or not big enough.
SQL 8895 8895 The character set name for the descriptor item SQLDESC_CHAR_SET is not valid. Cause You specified an invalid character set name for the SQLDESC_CHAR_SET descriptor. Effect The SET DESCRIPTOR 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 8896 8896 The character set name1 of a host variable does not match name2 of the corresponding descriptor item (entry number).
Recovery Verify that the Neoview database UDR server is running. If not, the Neoview database software statement will acquire a new Neoview database UDR server when it is next executed. SQL 8905 8905 The user does not have privilege-type privilege on user-defined routine routine-name. Cause You do not have the required EXECUTE privilege on a stored procedure. The user-defined routine might be used by a trigger. Effect The operation fails.
name is the table, index, or materialized view where the Reorg operation fails. reason is why the operation fails. Cause Effect The reorganization failed because of the reported reason. 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. Consider searching the log for the keyword reorg to find other errors that report problems.
SQL 8916 8916 The request to allocate a stored procedure result set at position index failed because the position is out of range. Valid positions range from one up to the maximum number of result sets that can be returned from the specified CALL statement, which in this case is max-result-sets. is an integer specifying a position in the ordered set of result sets returned from a CALL statement.
variable_info from table(statistics(module-name,stmt-name));". (CPU is an HP Neoview processing node.) Effect The runtime statistics information is not retrieved, and the command fails. Recovery Issue the command with valid values for the CPU or PID. SQL 8921 8921 The request to obtain runtime statistics for qid-string timed out. Timeout period specified is number seconds.
SQL 8935 8935 The sequence generator update failed, see additional diagnostics for failure details. Cause Effect The update to the internal sequence generator failed. The statement fails. Recovery Additional error codes are returned for the update failure. Proceed with the recovery procedures recommended by the additional error codes.
10 UPDATE STATISTICS Messages (9200 Through 9218) SQL 9200 9200 UPDATE STATISTICS for table catalog-name.schema-name.table-name encountered an error (error-num) from statement-name. catalog-name is the name of the catalog for the table that was the subject of the UPDATE STATISTICS operation. schema-name is the name of the schema for the table that was the subject of the UPDATE STATISTICS operation. table-name is the name of the table that was the subject of the UPDATE STATISTICS operation.
Recovery Correct the syntax and resubmit. SQL 9204 9204 Invalid option option specified. Value must be range. Cause You specified an invalid option for UPDATE STATISTICS. The value range specifies the valid range for this option. Effect The HP Neoview database software is unable to continue processing. Recovery Correct the syntax and resubmit. SQL 9205 9205 UPDATE STATISTICS is not supported for object name. Cause Effect You attempted to run UPDATE STATISTICS against an object that is not supported.
SQL 9210 9210 One of the column data types is not supported by UPDATE STATISTICS. You must exclude this column from the column list in UPDATE STATISTICS. Cause You attempted to perform UPDATE STATISTICS on a column whose data type does not support this operation. Effect The operation fails. Recovery Exclude this column from the column list and resubmit. SQL 9212 9212 Cardinality statistics will be more accurate if you use the SET ROWCOUNT option in the SAMPLE clause.
SQL 9217 9217 The statement will have no effect because no histograms are currently maintained for the table. Cause The ON EXISTING COLUMNS option was used with update statistics, but there are no existing histograms for the table specified. Effect No histograms have been generated by update statistics. Recovery Informational message only; no corrective action is needed. SQL 9218 9218 The statement will have no effect because no histograms need to be updated.
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 229) “Scratch File I/O Messages (10101–10199)” (page 233) 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.
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. The operation fails.
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.
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. SQL 10047 10047 Sort Error: Wrong length read. Cause Effect The length of the data returned was not what was expected. The operation fails. Recovery None.
Cause Effect 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. operator is the HP Neoview query operator that encountered the error; for example: merge join. number is a Neoview platform internal procedure-error number. Cause Effect The query operator was unable to close a scratch file. The operation fails.
SQL 10111 10111 operator could not wait for a scratch file I/O to complete. AWAITIOX returned error number. operator is the HP Neoview query operator that encountered the error; for example: merge join. number is a Neoview platform internal procedure-error number. Cause Effect The query operator failed to complete a scratch file asynchronous I/O operation. The operation fails. Recovery None. This is an internal error. Do not attempt recovery.
operator is the HP Neoview query operator that encountered the error; for example: merge join. number is a Neoview platform internal procedure-error number. Cause Effect An invocation of FILE_GETINFOLISTBYNAME_ failed. 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. SQL 10116 10116 operator failed to create a disk pool.
Cause Effect An invocation of FILENAME_FINDNEXT_ failed. 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. SQL 10150 10150 operator failed to find an appropriate disk for overflow data. operator Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. The query operator could not find an appropriate scratch disk.
12 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399) SQL 11005 11005 Table table-name or one of its triggers is inaccessible. table-name Cause Effect is the name of the table. The object metadata is not accessible. The operation fails. Recovery Make sure that no concurrent DDL operations are accessing the table. If concurrent DDL operations are accessing the table, wait until these operations are completed, and then retry the operation.
SQL 11041 11041 Temporary table could not be created! Check default partitions. Cause failed. Effect During a create trigger DDL statement, the creation of the triggers temporary table The DDL statement fails. Recovery None. This is an internal error. Contact your HP support representative. SQL 11045 11045 FIRST N UPDATE or DELETE is not supported on a table that is the subject table of BEFORE triggers or AFTER STATEMENT triggers. Trigger trigger-name has table table-name as its subject table.
SQL 11050 11050 NOT ATOMIC is not allowed on compound triggered action statements. Cause A specified triggered action statement is a non-atomic compound statement (BEGIN NOT ATOMIC ... END), and triggered action statements can have only atomic compound statement(s) (BEGIN ATOMIC ... END) as part of a trigger definition. Effect The trigger definition can not compile or be prepared. Recovery Change BEGIN NOT ATOMIC to BEGIN ATOMIC. SQL 11051 11051 Materialized views cannot be updated in a trigger action.
SQL 11105 11105 MXUDR: Invalid Language Manager parameter mode. Parameter: parameter-value. Cause The UDR server encountered an internal error. An unexpected parameter mode value appeared in a request 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 11108 11108 MXUDR: Unable to allocate memory for object object-name. object-name is the name of the 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 11114 11114 MXUDR: Internal error: A stored procedure result set message-type request arrived containing an invalid result set handle: handle. message-type is a message that is sent to the UDR server. handle is an internal identifier generated by the database software and used in messages to and from the UDR server.
SQL 11118 11118 MXUDR: A stored procedure result set was encountered with an output column count of value. All stored procedure result sets are expected to have at least one output column. is output column count of the result set. value Cause Effect The result set output column count is not valid. 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.
Effect The operation fails. Recovery Correct the EXTERNAL NAME clause and resubmit. SQL 11212 11212 Specified signature is invalid. Reason: Java signature size is bigger than the maximum supported size. Cause In a CREATE PROCEDURE request, the Java signature size exceeded the maximum supported size. The currently supported maximum Java signature size is 8192 characters.
SQL 11217 11217 Java execution: Data overflow occurred while retrieving data at parameter position parameter number. Value is truncated. Cause During execution of a CALL statement, numeric or string overflow occurred while processing the stored procedure output value returned in parameter parameter number. Effect None. This is a warning message. Recovery Increase the field size of the SQL data type for the specified parameter. SQL 11218 11218 A Java method completed with an uncaught Java exception.
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 Stop and restart the session and retry the SQL statement. SQL 11223 11223 Language Manager encountered an internal error.
SQL 11232 11232 The Java method method-name in Java class class-name is not defined as static. method-name is the Java method name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. class-name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. Cause During the execution of a CREATE PROCEDURE statement, a method named method-name was found in the specified Java class, but the method did not have the static attribute.
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. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
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[]. is the ordinal position of the parameter specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement. index Cause Effect The parameter at position index is not java.
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.
table-name is the name of the table being altered. actual-row-length is the row length of the MV source or the trigger base table. max-row-length is the maximum row length of the MV source table or trigger base table for which it is guaranteed that the compile error will not occur. Cause Triggers and ON STATEMENT materialized views require the presence of an internal table to help maintain them.
Recovery None. SQL 12081 12081 Audit type not allowed for materialized view refresh type. Cause Effect The specified audit type is not allowed for the specified refresh type. The creation of the materialized view fails. Recovery Correct the syntax and resubmit. SQL 12087 12087 Operation failed since table log is not empty. Cause Effect This operation can be performed only when the table log is empty. The operation fails. Recovery Refresh all the materialized views that use this table and try again.
SQL 12109 12109 To ensure optimal Refresh performance, the STORE BY clause should include the following GROUP BY columns: col-names. are the group by columns that should be included in the STORE BY clause. col-names Cause To improve the materialized view refresh performance, the specified columns should have been included in the STORE BY clause. Effect This is an informational message. The materialized view is created successfully.
Recovery None. SQL 12115 12115 The IGNORE CHANGES clause of materialized view mv-name cannot be altered when the logs of the tables referred to in the IGNORE CHANGES clause are not empty. Refresh the materialized view and try the ALTER statement again. mv-name is a materialized view. Cause An attempt was made to ALTER IGNORE CHANGES on a base table of the materialized view and the insert/update/delete logs for the materialized view are not empty. Effect The operation fails.
Cause Effect You used the name of an MVGroup that does not exist. The operation failed. Recovery Correct the syntax and resubmit. SQL 12202 12202 Materialized view mv-name does not exist. Cause Effect You specified a name of a materialized view that does not exist. The operation failed. Recovery Correct the syntax and resubmit. SQL 12203 12203 Materialized view mv-name already exists in MVGroup. mv-name Cause Effect is a materialized view.
Recovery None. SQL 12209 12209 Some materialized views used by this materialized view must appear in the MVGroup as well.. Cause An attempt was made to add a dependent materialized view to a materialized view group. All materialized views this materialize view depends on must already be in the materialized view group. Effect The operation failed. Recovery Add the materialized views that this materialized view depends on to the materialized view group and resubmit.
Cause An attempt was made to add a materialized view to a materialized view group through automatic materialized view group creation. The owner of the table used by the materialized view is different from the owner of the materialized view. Effect The operation failed. Recovery Try to add the materialized view to the materialized view group manually. SQL 12301 12301 Materialized view mv-name is not initialized. mv-name Cause Effect is a materialized view.
Effect The DML operation on the materialized view fails. Recovery Contact the GMCSC. SQL 12316 12316 No corresponding context row was found in the context log. Cause This is an internal error used by the refresh utility to determine when the context log is empty and the work is done. Effect The operation fails. Recovery None. SQL 12318 12318 FIRST/ANY is not allowed in a query expression of a materialized view. Cause Effect You specified FIRST or ANY in a query expression of a materialized view.
Cause You attempted to create a materialized view by using the same table more than once. This operation is not allowed. Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12323 12323 Creation failed. The selection predicate includes a nonrepeatable expression. The materialized view cannot be maintainedincrementally.
Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12329 12329 Creation failed. Join predicates must have only one column instance at each side of the equal sign. The materialized view cannot be maintained incrementally. Cause Your CREATE MV statement includes a join predicate with multiple column instances on one side of the equal sign.
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 is a user-specified input value to a versioning built-in function. input-type 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 21 (page 385). SQL 20001 20001 File system error error number occurred during file read.
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 21 (page 385). 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. Cause SQL could not enable a large transfer to the requested file and received error number. Effect The operation fails.
SQL 20011 20011 An internal error occurred while performing a command on file file. Statement is out of sequence. command is the operation that can be: • FILE OPEN • FILE READ • FILE WRITE • FILE CLOSE • SET LARGE TRANSFER • FILE ALLOCATE/DEALLOCATE • FILE SET EOF TO 0 file is the name of the file being processed. Cause The utility subsystem that performs a file request received a request out of sequence. Effect The operation fails. Recovery Do not attempt recovery. Notify HP support.
SQL 20016 20016 File system error error number occurred while getting block size for file. error number is the HP Neoview platform file-system error. 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 21 (page 385). SQL 20017 20017 File system error error number occurred while getting partition length for file.
table1 is the name of the referenced table. num2 is the number of columns associated with the referencing table constraint. table2 is the name of the referencing table. const is the name of the constraint for the referencing table. 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.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20028 20028 Specified an invalid partition physical size, should be BYTES, MBYTES, KBYTES, or GBYTES. Cause You specified an invalid partition physical size, which must be expressed in bytes, megabytes, kilobytes, or gigabytes. Effect The operation fails. Recovery Correct the syntax and resubmit.
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. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20045 20045 An internal error occurred - invalid sort order.
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. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20052 20052 Transaction Management subsystem could not set the AutoCommit.
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 20057 20057 An internal error occurred - Transaction Management subsystem could not do GetRowsAffected on a statement. Cause The utility subsystem that sends CLI requests to SQL failed trying to extract the number of rows affected from the previously executed request. Effect The operation fails.
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.
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 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.
SQL 20163 20163 An internal error occurred - invalid include option of CREATE TABLE LIKE. Cause Effect SQL was unable to perform the requested 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 20164 20164 The search condition for the specified check constraint has a syntax error.
Cause You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object, its parent, or its dependent. Effect The operation fails. Recovery Wait until the concurrent operation has finished and then resubmit. 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.
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 20205 20205 Index index is online. Cannot perform POPULATE INDEX. is the index's ANSI name. index Cause Effect You requested to populate an index that is already populated. None. Recovery This is an information message. No corrective action is needed.
operation is recovery or DDL lock fixup. name is the name of a table, materialized view, or index. Cause Effect There is nothing to recover or fixup. None. Recovery None. This message is informational. SQL 20222 20222 Error occurred for partition file file name when attempting to set the number of index levels. file-name is the partition being accessed. Cause An unexpected error occurred on an attempt to complete a data movement operation for the request. Effect The operation fails.
SQL 20229 20229 A request to update the index status for index index-name failed. DUP could not be performed. index-name is the name of the index specified in the update request. Cause An unexpected error is returned during the final phase of duplicating indexes to the target table. Effect The operation fails. Recovery Use the messages that accompany this one to diagnose and correct the problem. SQL 20232 20232 This operation cannot be done on a nonaudited table that contains data.
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 20241 20241 The MODIFY utility cannot perform a DROP HASH operation on the object object-name because the target partition partition-name does not have enough space for the redistribution of data.
SQL 20266 20266 Invalid message code code1 returned from SPI request, expecting code2. code1 is the code returned from SPI. code2 is the expected value. Cause An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation. Effect The operation fails. Recovery None. This is an internal error. Contact your HP service provider. SQL 20267 20267 Returned buffer from SPI request has a length of len1, expected a value less than or equal to len2.
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 20275 20275 Reload operation failed, file system error error returned from ORSERV for file file. error is the error returned by the file system. file is the HP Neoview platform file. Cause Effect An unexpected error occurred while performing a FUP RELOAD. The operation fails.
Recovery Run FUP RELOAD manually to reclaim free space on the specified partitions if the D or F flag is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set. SQL 20296 20296 The MODIFY request has completed successfully, but ORSERV might not have completed successfully. Please run FUP RELOAD manually to reclaim any free space on file-name-list. file-name-list is the list of HP Neoview platform file names of the partitions that might need reloading.
Effect The operation fails. Recovery Contact your HP service provider to check if the Synonym metadata is corrupt. SQL 20317 20317 Internal Error: invalid referenced object’s type for the Synonym. Cause This is an internal error. The Synonym metadata is in an inconsistent state. The referenced object type is invalid. Effect The operation fails. Recovery Contact your HP service provider to check if the Synonym metadata is corrupt.
SQL 20351 20351 An internal error occurred. Cause Effect An unexpected error occurred on an MXTOOL 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 20352 20352 Syntax error. No arguments were provided. Try ‘mxtool help’. Cause Effect You specified MXTOOL without any arguments. The operation fails.
Recovery For information about file-system errors, see Chapter 21 (page 385). SQL 20357 20357 File name is not an SQL/MX object. name is the name of the HP Neoview platform file requested to be removed. Cause GOAWAY could not drop the specified Neoview platform file. Effect The operation fails. Recovery Specify the correct file name and resubmit. SQL 20358 20358 Catalog catalog does not exist. is the name of the catalog specified in the request.
Cause MXTOOL generates a list of files to check as specified by an HP Neoview platform file template. An error was returned during the processing of this list. Effect The operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385). SQL 20364 20364 An internal error occurred while getting the Guardian file name. Cause An unexpected error was returned while reading the file label for an HP Neoview platform file. Effect The operation fails.
Cause Effect You specified invalid options for the GOAWAY command. The operation fails. Recovery Do not use the DATA/RESOURCE FORK option, and resubmit. 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 is the HP Neoview platform file of the resource fork. data fork name is the Neoview platform file of the data fork. Cause Effect You specified invalid options for the GOAWAY command. The operation fails.
file is the name of the existing data or resource fork. Cause The GOAWAY operation failed because only the data fork or resource fork exists, and the -both option was specified. Effect The operation fails. Recovery If the file ends in 00, rerun the request with the -df option. If the file ends in 01, rerun the request with the -rf option. SQL 20460 20460 You specified -both for GOAWAY request of resource fork name You must specify data fork name to GOAWAY the label.
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. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20506 20506 Catalog catalog-name does not exist.
SQL 20511 20511 ON STATEMENT materialized view mv-name cannot be refreshed with CASCADE option. is a materialized view. mv-name Cause Effect 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 your HP service provider. 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.
Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If this problem persists, contact your HP service provider. SQL 20531 20531 An internal error occurred while extracting data type information from an internal data buffer. Cause Effect An internal error occurred. The operation fails. Recovery Do not attempt recovery.
SQL 20537 20537 Failed to change the index's status during the recompute of a materialized view. 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 text. Effect 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 21 (page 385). 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.
SQL 20550 20550 Unable to compile statement : string. is the statement that failed to compile. string 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 your HP service provider.
SQL 20556 20556 Materialized view mv-name cannot be refreshed standalone (the used materialized view(s) and table(s) are not coordinated). mv-name 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.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20563 20563 TMF error error-number occurred while trying to begin a transaction. 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.
Cause During the refresh operation, an error originating from the transaction management facility occurred on an operation to get the transaction identifier. 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 20576 20576 File system error error-number occurred during FILE_OPEN_ on process process-name. error-number is an error originating from the file system.
SQL 20587 20587 The object internal-object is an internal object. This object should only exist during certain maintenance operations. internal-object Cause Effect is the name of the internal object. VERIFY discovered that the schema being verified contains an internal object. None. This is an informational message. Recovery Do not attempt recovery. Contact your HP service provider. SQL 20701 20701 Audit fix process process name was not able to allocate an extended memory segment.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20705 20705 An audit fixup request was made out of sequence. Cause During an online partition management operation, the MXAUDSRV process received an unexpected request from the MODIFY code. Effect The MODIFY operation fails. Recovery Do not attempt recovery.
Cause During an online partition management operation, the MXAUDSRV process encountered an error while reading a transaction-log record. 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 20710 20710 An error occurred while attempting to perform a REDO of a TMF audit record during the audit fixup phase of the operation, in audit fixup process process name.
SQL 20717 20717 Audit fixup process (process name) could not begin or commit a TMF transaction. Cause During an online partition management operation, the MXAUDSRV process encountered an error when attempting to begin or commit a transaction. The probable cause is that transaction services are down or have transactions disabled. Effect The MODIFY utility did not process the request. Recovery Do not attempt recovery.
Cause During an online partition management operation, the MXAUDSRV process encountered an internal error. 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 20723 20723 An audit fixup process found a label change audit record during fixup work.
Cause During an online partition management operation, the MXAUDSRV process reported an unknown error code. Effect The POPULATE INDEX or MODIFY operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385). SQL 20728 20728 An SQL/MX error error code occurred in audit fixup process process name. error code is returned file system number.
SQL 20735 20735 An unexpected index transform error error-code occurred in audit fixup process process. error-code is the SQL error code. process is the file-system process identifier. Cause An unexpected error occurred when the Neoview database software tried to find audit records to apply to the index. 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 For information about file-system errors, see Chapter 21 (page 385). SQL 20755 20755 VERIFY cannot work on object (object-name) either because the object is not a table, view, stored procedure, or MV, or because the specified table, view, stored procedure, or MV does not exist. object-name is the name of the specified table, view, materialized view (MV), or stored procedure. Cause VERIFY failed because the specified object is not a table, view, materialized view, or stored procedure.
Recovery At some point, the POPULATE INDEX command should be performed to make the index available for queries. SQL 20760 20760 The redefinition timestamp (time1) defined on the label does not match the time (time2) defined in the metadata for Guardian file (file). time1 is the Julian timestamp found on the label. time2 is the Julian timestamp found in the metadata. file is the name of the HP Neoview platform file. Cause Effect An inconsistency was found during the VERIFY operation. None.
size1 is the maxextent size defined on the label. size2 is the maxextent size defined in the metadata. file is the name of the HP Neoview platform file. Cause Effect An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Contact your HP service provider to use the MXTOOL FIXUP utility to fix this inconsistency.
Cause VERIFY was unable to find metadata associated with the Neoview platform file, possibly because the Neoview platform file is orphaned or the metadata is wrong. Effect The operation fails. Recovery If the Neoview platform file is no longer needed, use GOAWAY to remove it. If the Neoview platform file should be part of an ANSI name, the metadata tables might need to be recovered.
Recovery Contact your HP service provider. SQL 20774 20774 The constraint text in the resource fork does not match the constraint text in the metadata for constraint (name) while processing the Guardian file (file). name is the constraint name described in the metadata. file 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 Contact your HP service provider.
Effect None. This is an informational message. Recovery Contact your HP service provider. SQL 20779 20779 The number of indexes (num1) in the index map array on the resource fork does not match the number of indexes (num2) in the metadata for Guardian file (file). num1 is the number of indexes in the index map in the resource fork. num2 is the number of populated indexes found in the metadata. file is the name of the HP Neoview platform file.
string2 Cause Effect is the Neoview platform name of the partition as it is defined in the metadata (PARTITIONS or REPLICAS tables). An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Contact your HP service provider. SQL 20784 20784 Partition map entry (file1) is defined in the metadata but is missing from the resource fork for Guardian file (file2). file1 is the HP Neoview platform name of the partition.
Cause Effect The requestor does not have the privileges to perform the VERIFY operation. The operation fails. Recovery Fix the problem and resubmit. SQL 20789 20789 The object schema version in resource fork (rversion) does not match version (mversion) in the metadata for Guardian file (file). rversion is the object schema version stored in the resource fork. mversion is the object schema version stored in the HP Neoview platform file.
SQL 20794 20794 Error (number) was returned when trying to extract the catalog, schema, table, or MV from the ANSI name defined in the resource fork for Guardian file (file). number is the file-system error number. file is the HP Neoview platform file being verified. Cause An unexpected error returned on an attempt to extract the catalog name, schema, table, or materialized view (MV) from the resource fork. Effect The operation fails.
SQL 20799 20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name). object-type is the type of object, which can be CATALOG, SCHEMA, TABLE, or INDEX. ruid is the UID value of the object stored in the resource fork. muid is the UID value of the object stored in the metadata. file-name is the name of the HP Neoview platform file. Cause An inconsistency was found.
Cause state. The table object's metadata flag is set up incorrectly, and its flag value is in an unknown Effect The caller cannot determine whether the table is a system metadata table or a user metadata table. Recovery The application developer should ensure that the table object's metadata flag is set up correctly. SQL 20816 20816 The current_epoch defined on the label does not match the current_epoch defined in the metadata for Guardian file (file).
Cause Effect MXTOOL VERIFY found a constraint that is disabled. This is an informational message. Recovery Contact your HP service provider to enable the constraint. 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.
SQL 20877 20877 The input file name contains invalid header information. name is the input file name specified in the request. 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.
option-name Cause Effect is one of these: DROP DEPENDENT, CASCADE DEPENDENT, or RECREATE DEPENDENT. You specified an option that is not implemented. 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.
Recovery Check whether the table or index exists or if a DDL lock is present, and fix the problem accordingly. 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.
SQL 23003 23003 servername: File error encountered: description. servername is the name of the server program that issued the error. description gives more detail about the file error. Cause Effect 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. servername is the name of the server program that issued the error.
SQL 23013 23013 servername: Error code: nnn. No error text available for this code. servername is the name of the server program that issued the error. nnn is the unknown error code. Cause Effect An exception occurred for an unexpected error. The operation fails. Recovery None. Contact your HP service provider. 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 is the name of the server program that issued the error. description contains detailed information about the missing mapping file section name. Cause Effect When processing a mapping file, an expected section or attribute was not found. The operation fails. Recovery Correct the mapping file and resubmit. SQL 23020 23020 servername: SQL/MX object was not found: object-name.
17 Authentication and User Management Messages (24000 Through 24999) The following errors can occur in the context of user authentication or user management actions. 24001 24001 The LDAP host name or IP address is not allowed to be null. Cause You specified a NULL value for the Host attribute when configuring the interface with an external directory server. Effect The operation fails. Recovery Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. 24007 24007 The configuration text exceeds the maximum length of 26624 characters. Cause The configuration description file contains more than the maximum number of characters allowed. Effect The operation fails. Recovery Remove any superfluous spaces or comments, and resubmit the command with a configuration description file that does not exceed the maximum length. 24008 24008 The alter config option is invalid.
24013 24013 The LDAP search password exceeds the maximum length of 128 characters. Cause You specified a value exceeding the maximum length for the SearchUserPwd attribute when configuring the interface with an external directory server. Effect The operation fails. Recovery Correct the syntax and resubmit. 24014 24014 The role name must start with an alphabetic letter. Cause You entered a role name beginning with a non-alphabetic character. For example, you specified a user's role as “007”.
Recovery Check the validity of the certificate. 24021 24021 The LDAP CA certificate is not allowed to be null with SSL enabled, and CA certificate required. Cause You specified SSL or TLS as the encryption option, but you did not provide a certificate. Effect The operation fails. Recovery Specify a valid CA certificate or set the encryption option to None. 24022 24022 Failed to check the remote user.
Recovery Retry the command. If the problem persists, report it to HP Support. 24029 24029 Failed to alter the Neoview policy. Cause The Neoview security policy could not be altered, because the specification was invalid. Effect The operation fails. Recovery Correct the specification, and resubmit the request. 24030 24030 Failed to get the Neoview role ID. Cause The role ID could not be retrieved because of an operating system problem.
Recovery Correct the syntax and resubmit. 24038 24038 The number of maximum logon attempts must be a value from 0 through 60. Cause Effect This message is currently not used. This message is currently not used. Recovery This message is currently not used. 24039 24039 The number of seconds to wait before a logon timeout failure occurs must be a value from 0 through 86400. Cause Effect This message is currently not used. This message is currently not used. Recovery This message is currently not used.
Effect This message is currently not used. Recovery This message is currently not used. 24045 24045 The minimum number of quality criteria that must be met when changing passwords must be a value from 0 through 4. Cause Effect This message is currently not used. This message is currently not used. Recovery This message is currently not used. 24046 24046 The user name is not allowed to be null. Cause Effect The user management operation failed because of an internal error. The operation fails.
24052 24052 Failed to alter the LDAP configuration entry. The entry does not exist. Cause You tried to delete an LDAP server configuration, but no server having the specified DomainName and UsagePri is currently configured. Effect The operation fails. Recovery Display a list of LDAP servers, make any necessary changes in your request, and resubmit. 24053 24052 Failed to get the LDAP configuration entry. The entry does not exist.
Cause The password you assigned to a platform user does not meet the configured criteria for password quality. Effect The operation fails. Recovery Choose a password consistent with password quality criteria. 24069 24069 The minimum quality required of password cannot be greater than the number of quality attributes set to on. Cause Effect This message is currently not used. This message is currently not used. Recovery This message is currently not used.
24079 24079 Failed to set the default role. The role must already associate with the database user. Cause You tried to set a role as the user's default role, but the role was not yet assigned to the user. Effect The operation fails. Recovery Assign the role to the user before making it the default role. 24081 24081 Not authorized to perform this operation. Cause You tried to take a user management action (such as adding or deleting a user, granting or revoking a role) but were not logged on as ROLE.
Recovery Correct your syntax, and resubmit the request. 24087 24087 The parameter parameter value is too long. Cause In the configuration description file, the value you entered for the specified parameter exceeded the permissible length. Effect The operation fails. Recovery Correct your syntax, and resubmit the request. 24088 24088 Invalid parameter name parameter specified in the configuration text.
Recovery Correct your syntax, and resubmit the request. 24094 24094 Failed to authenticate the requester. Cause You attempted to manage the directory server configuration and the role you are logged on with does not have the authority. Effect The operation fails. Recovery Logon as a user with role ROLE.SECMGR or request a user with the role to make the update for you. 24095 24095 Can not add the LDAP default configuration. Cause You tried to add an LDAP server with the DomainName default.
Effect The operation fails. Recovery None. This operation is not permitted. 24100 24100 Invalid usage priority. Cause The value you specified as the usage priority of an external directory server was not in the range of 0 through 32767. Effect The operation fails. Recovery Give the command again, specifying a usage priority within the expected range. 24101 24101 Invalid date, expecting a legal Neoview date in format MMM DD YYYY. Cause Effect The operation fails.
Recovery Check the parameter specified, and try again with any necessary corrections. If the problem persists, contact HP Support. 24110 24110 Current password required to change the password for this role. Cause You tried to reset the password for a role, but the security policy requires you to provide the current password in order to change the password. Effect The password is not changed. Recovery Try again, but this time provide the current password.
Recovery Contact HP Support 24119 24119 Alter User failed. Cause Effect Internal error. Internal error. Recovery Contact HP Support 24120 24120 Change Password failed. Cause Effect Internal error. Internal error. Recovery Contact HP Support 24121 24121 Delete Role failed. Cause Effect Internal error. Internal error. Recovery Contact HP Support 24122 24122 Delete User failed. Cause Effect Internal error. Internal error. Recovery Contact HP Support 24123 24123 Grant Role failed.
Cause Effect Internal error. Internal error. Recovery Contact HP Support 24127 24127 Username not found. Cause Effect You specified a username that is not registered on Neoview. Operation is not successful. Recovery Verify correct username and resubmit the command. 24128 24128 You are not authorized to perform this command. Cause Effect You attempted an operation that your current role is not authorized to perform. Operation is not successful.
Recovery Resubmit the command with the correct current password. If you do not know the correct current password, ask an administrator to reset your password. 24137 24137 Platform role not allowed. Cause Effect You attempted to grant a platform role to a database user. The role is not granted. Recovery Resubmit the command using a database role. 24139 24139 New role cannot be added. ROLES table failed consistency check. Cause Effect Internal error. Internal error. Recovery Contact HP Support.
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 351) “Distribution Messages (25400–25499)” (page 361) “JDBC Driver Error Messages (29000–29399)” (page 366) Versioning Messages (25000–25399) SQL 25002 25002 A versioning internal error occurred: missing compatibility check. Cause Effect This is a versioning internal error. The operation fails.
MXV1 is the MXV of the affected remote node. 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.
Cause You attempted to access a table or view in a schema with a schema version that is earlier than the accessing node’s earliest supported schema version. This message can be issued from the local node or from an ESP on a remote node. This message is accompanied by message 25001, which explains what actual software component reported the error. 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.
version2 is that node’s MXV. Cause You attempted to access a database object with an object schema version that is incompatible with one or more nodes where the object (or a partition or index of the object) resides. 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.
version2 is the compiler version of the compiler that compiles the query or executes the DDL or utility operation. Cause The affected query compilation, DDL, or utility operation attempted to access system schema tables with a system schema version that is incompatible with the version of the compiler that compiles the query and executes the operation. This can happen if: • • The local system schema version is later than the MXV of a node that is involved in the affected query.
Effect The request fails. Recovery Ensure that the affected schemas have the same version. SQL 25210 25210 Schema schema has schema version version1; node does not support schema versions lower than version2. schema is the name of the schema referenced by a DDL or utility operation. version1 is the schema version of schema. node is the node where the operation is executed or the node where metadata for the schema resides. version2 is the earliest supported schema version of node.
SQL 25213 25213 The system schema on node1 can be accessed only by a node with SQL/MX software version (MXV) version1, the MXV of node is MXV1. node1 is the node whose system schema is accessed. version1 is the schema version of object’s schema. node is the node that attempts to access the system schema on node1. MXV1 is the MXV of node1. 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.
is the MXV of the node that executes the query. MXV1 Cause The accessing node runs a non-GA release of the HP Neoview database software and is compatible only with schemas created by its own version. Effect The operation fails. Recovery Upgrade or downgrade the accessing node to a Neoview database software release that is compatible with the affected schema’s version. SQL 25218 25218 Schema schema has schema version version1; node cannot access or represent schemas with versions higher than MXV1.
SQL 25301 25301 Module module has module version version1; the local node does not support module versions higher than version2. module is the name of the affected module. version1 is the module version of the affected module. version2 is the MXV of the local node. Cause You attempted to load a module with a module version (version1) that is later than the local node’s MXV (version2). Effect The operation fails. Recovery Recompile the module with a supported version compiler.
node is the node that attempts to execute the query. MXV1 is the MXV of the affected node. Cause The affected node runs a GA release of the HP Neoview database software and is incompatible with a query plan generated by a non-GA release. Effect The operation fails. Recovery Compile the query with a compiler version that is compatible with the MXV. SQL 25308 25308 The query plan has plan version version1. The local SQL/MX software version (MXV) can execute query plans with plan version MXV1 only.
version2 is the actual module version of module. Cause The system module was manually renamed to indicate a version other than the actual version. Effect The operation fails. Recovery Reinstall the system module. SQL 25312 25312 A version version1 compiler is required to compile the query. The current compiler version is version2. version1 is the required compiler version. version2 is the actual compiler version.
Cause You attempted to register catalog catalog on node node, but a reference to catalog already exists on that node. Effect The operation fails. Recovery Correct the error and retry the operation. SQL 25403 25403 Catalog catalog already exists on node node1, but it is unrelated to the catalog of the same name on the local node node2. catalog is the ANSI name of the target catalog. node1 is a remote node where an independent catalog with the desired ANSI name already exists.
Cause When the DML query was compiled, the affected database object had partitions on a remote node, and the database object’s catalog was visible on both the remote node and the local node. When the query was executed, the visibility of the object’s catalog changed. See accompanying messages 1002, 25401, or 25403 for more details about the visibility of the change. Effect If the message is issued as an error, it is accompanied by error 1002, and the query fails.
Recovery Correct the error and retry the operation. SQL 25423 25423 Schema schema has no replica on node node. schema is the ANSI name of the affected schema. node is the remote node with no replica of the affected schema. Cause The target node of an UNREPLICATE SCHEMA operation does not have a replica of the affected schema. Effect The operation fails. Recovery None. The affected schema has no replica on the target node. SQL 25424 25424 A replica of schema schema already exists on node node.
Cause An UNREGISTER CATALOG operation using the RESTRICT option attempted to remove a catalog reference from a node. However, the target catalog is related to one or more other catalogs that are visible on the target node. This error is issued once per related catalog. Effect The operation fails. Recovery Use the CASCADE option on UNREGISTER CATALOG. SQL 25428 25428 Catalog catalog1 cannot be registered on node node because it is related to catalog2 which has no reference on the target node.
JDBC Driver Error Messages (29000–29399) This range of numbers is reserved for JDBC driver error messages. For complete information about JDBC driver error messages, see the Neoview JDBC Type 4 Driver Programmer's Reference.
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 An Input Output Exception was received while initializing the Input Stream. Unable to launch the Neoview Command Interface. Recovery 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 Effect The classpath for Neoview JDBC Type 4 Driver JAR file has not been set. 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 None. Recovery 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 None. Recovery Not applicable. 29430 Spooling is already OFF.
29435 Invalid ListCount value. The value must be in the range 0-2147483647." Cause range. Effect The value specified for the SET LISTCOUNT command is not within the acceptable The command fails to execute. Recovery 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 The command fails to execute. Recovery Retry the command by specifying a valid section name in the OBEY command. 29442 Could not create the specified file. Cause Effect Failed to create the file specified in the SAVEHIST command. The command fails to execute.
Effect 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 You specified an incorrect syntax for the PRUN command. The PRUN command fails to execute. Recovery Retry the PRUN command by specifying the valid options. 29457 NWMS not started on this server. Cause Effect You tried to execute a WMS command when WMS is not running on the server. All the WMS commands fail to execute. Recovery 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 The conditional statement fails. Recovery N/A. 29473 Unable to compare a string with an integer. Cause Effect The left side of a conditional statement is a string and the right side is a integer. The conditional statement fails. Recovery N/A. 29474 Unable to compare strings using the operator. Cause Effect An operator other than =, ==, <>, !=, ~=, ^= was used to compare strings. The conditional statement fails. Recovery 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. num1 is the size of the rowset. num2 is the smallest dimension of the rowset arrays. Cause You specified a rowset size larger than the smallest dimension, num2, of the rowset arrays. Effect 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 is the name of the BEFORE trigger. table-name 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.
materialized-view is the name of the materialized view. 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 is the name of the AFTER trigger.
21 File-System Errors Some file-system errors are new or changed for the Neoview platform and are not documented, see “New or Changed File-System Errors for the Neoview Platform” (page 398). 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. This section lists all file-system error codes and provides the corresponding error text for each code number.
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 0764 Unable to allocate space from the revive pool. 0765 Unable to allocate space from the SQL data area pool (SQLMXBuffer space). 0766 The maximum number of opens for a file has been reached. 0770 Neoview SQL tried to roll back a savepoint that had already been discarded. This can happen if Neoview SQL tries to roll back a savepoint twice, or if the savepoint exceeds its memory limit. Neoview SQL aborts the encompassing transaction for this error.
Error Number File-System Error Text 1053 An ECC error or a checksum error occurred indicating that it is impossible to process the accessed block. No data is returned. 1054 Unable to access a non-protected table or protection view that has been altered by an uncommitted DDL statement. 1055 Unable to perform a utility operation while an uncommitted DDL operation from another transaction exists. 1056 Unable to access a table that is being recovered by Transaction Services.
Error Number File-System Error Text 1086 Unable to unlock an SQL table that has locks through either STABLE ACCESS or REPEATABLE ACCESS. 1087 The SQL file system detected an internal disk process error. 1088 SQL internal error. 1089 SQL internal error. 1090 The requested SQL operation cannot be completed because of current limitations on message sizes. 1091 The file or table cannot be purged until the NOPURGEUNTIL date.
Error Number File-System Error Text 1122 The supplied KEYTAG value is already defined for this table. 1123 SQL internal error. 1124 SQL internal error. 1125 SQL internal error. 1126 SQL internal error. 1127 Unable to update an SQL catalog table from a process that is not licensed. 1128 An operand was scale truncated during expression evaluation. 1129 Scale truncation was needed but prohibited during expression evaluation.
Error Number File-System Error Text 4028 No space left on device. 4029 Illegal seek. 4030 Read only file system. 4031 Too many links. 4032 Broken pipe or no reader on socket. 4033 Argument out of range. 4034 Value out of range. 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.
Error Number File-System Error Text 4131 File name too long. 4132 Directory not empty. 4180 Invalid data in buffer. 4181 No reply in buffer. 4182 Partial buffer received. 4183 Interface error from SPI. 4184 Version mismatch. 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.
757 Transaction type mismatch. Cause This error is returned due to a transaction type mismatch. Typically this happens when a read-only transaction is in effect and an insert, update, delete, DDL or utility statement is executed within the same transaction and the mismatch is not detected by the SQL compiler. Effect The query aborts. Recovery Commit the read-only transaction before attempting to start a read-write transaction. Clients should also check their auto commit settings.
