HP Neoview Messages Manual HP Part Number: 544563-001 Published: August 2007 Edition: HP Neoview Release 2.
© Copyright 2007 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.........................................................................................................9 Supported Releases.................................................................................................................................9 Audience.................................................................................................................................................9 ODBC and JDBC Messages..........................................
12 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399).............................................................................................................................215 13 Materialized Views Messages (12000 Through 12329)......................................221 14 Messages Generated by the Message System (16000 Through 16999)...........231 15 Internal Stored Procedures Messages (19000 Through 19999).........................233 16 Utility Messages (20000 Through 23099)....
22 SQLSTATE Values Returned by the Neoview Database.......................................397 SQLSTATE and SQLCODE Considerations........................................................................................397 SQLSTATE Values...............................................................................................................................397 23 File-System Errors.....................................................................................................
List of Tables 22-1 22-2 22-3 22-4 22-5 22-6 22-7 22-8 22-9 22-10 SQLSTATE Values Beginning 00000............................................................................................398 SQLSTATE Values Beginning 01700............................................................................................405 SQLSTATE Values Beginning 01800............................................................................................411 SQLSTATE Values Beginning 01I01.................................
About This Document HP Neoview database is the HP relational database management system based on ANSI SQL-92. It uses the industry standard Structured Query Language (SQL) to define and manipulate data. This manual describes messages produced by the HP Neoview data warehousing platform and its associated subsystems. Supported Releases This manual supports Neoview Release 2.2 and subsequent Neoview releases until otherwise indicated in a replacement publication.
Chapter (page) Description Messages Added and Changed Chapter 11 (page 205) “Executor Sort and Scratch File I/O Messages (10000 Through 10199)” 10101–10105, 10110–101119, 10150–10153 Chapter 12 (page 215) “Trigger, UDR Server, and Language 11223 Manager Messages (11000 Through 11399)” Chapter 13 (page 221) “Materialized Views Messages (12000 Through 12329)” Chapter 16 (page 235) “Utility Messages (20000 Through 23099)” 20205, 20339, 20340, 20520, 20521, 20523, 20542, 20543, 20545, 20546, 20547, 2
Chapter Title Chapter 17 (page 289) “Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29999)” Chapter 18 (page 309) “Rowsets Messages (30000 Through 30999)” The last chapters of this manual list messages of these Neoview components: Chapter Title — Use Chapter 19 (page 315) “Neoview Data Warehouse Manager Messages” — Look up these messages in numeric order.
Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: DAY (datetime-expression) @script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "{" module-name [, module-name]... "}" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Related Documentation This manual is part of the HP Neoview customer library. Neoview Customer Library • Administration Neoview Database Administrator’s Guide Information about how to load and manage the Neoview database by using the Neoview DB Admin and other tools. Neoview DB Admin Online Help Context-sensitive help topics that describe how to use the HP Neoview DB Admin management interface.
Publishing History Part Number Product Version Publication Date 543440–002 HP Neoview Release 1.0 August 2006 543643–001 HP Neoview Release 1.2 November 2006 543766–001 HP Neoview Release 2.0 March 2007 544563–001 HP Neoview Release 2.2 August 2007 You can find this manual or its replacement on line with the HP Business Intelligence Solutions technical documentation at: http://www.docs.hp.com/en/busintellsol.
1 Message Handling The Neoview database software reports exception condition messages at the HP Neoview Database Connectivity Service conversational interface (NDCS) window, in SQL preprocessor and compiler listings, and during the execution of embedded SQL programs. You obtain the error messages that result from the execution of an SQL statement within an embedded program in C or COBOL by using the GET DIAGNOSTICS statement to access the SQL diagnostics area.
positive numbers other than 0 (successful completion) or 100 (no data was found) signify warning messages. The Neoview database software identifies all messages by their unsigned SQLCODE value and their calculated SQLSTATE value. The SQLCODE is used to calculate the SQLSTATE value for all Neoview database software messages other than those for which an ANSI SQL-92 SQLSTATE value exists.
2 Data Definition Language (DDL) Messages (1000 Through 1999) SQL 1001 1001 An internal error occurred in module name on line num. DETAILS(details). name num details Cause Effect is the name of the module. is the line number. are the details of the error. This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
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. Cause The operation you attempted requires the existence of an index named index-name.
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 You attempted to revoke a privilege for a user who has granted privileges to another user.
SQL 1019 1019 No valid primary partition for table-name could be found. table-name Cause Effect is the name of an HP Neoview SQL table. 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.
Cause Effect Recovery Look up this error number in the file system manual to determine the cause. The operation fails. For information about file-system errors, see Chapter 23 (page 463). 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.
SQL 1030 1030 File label file name could not be accessed. File system error error. is the name of an HP Neoview database file. is a file-system error number. file name error Cause Effect See the accompanying error message for the cause. The operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463). 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.
SQL 1038 1038 Not all user catalogs have been dropped from the system. Cause Effect Recovery You attempted to drop SQL while one or more user-created catalogs existed. The operation fails. You must drop all user-created catalogs before dropping SQL. SQL 1039 1039 The DROP SQL statement could not be executed. Cause Effect Recovery See the accompanying error message for the cause. The HP Neoview database software does not drop SQL. Apply the recovery of the accompanying error message.
constraint-name is the name of a column constraint or table constraint. Cause The columns that constraint-name references in the referenced table are not part of a unique constraint. Effect The operation fails. Recovery Check that constraint-name references a unique or primary constraint in the referenced table. SQL 1045 1045 The unique constraint cannot be used because it is deferrable. Cause The referential constraint is referencing the unique constraint that is declared as deferrable.
Effect The operation fails. Recovery None. SQL 1050 1050 Constraint cannot be dropped because it is used as a referenced object for a foreign key. Cause You attempted to drop a unique or primary constraint, with dependent referential constraints, using the RESTRICT option, which does not remove such constraints. Effect The drop command fails. Recovery If you want to drop the dependent referential constraints, use the CASCADE option for the DROP CONSTRAINT command.
SQL 1059 1059 Request failed. Dependent constraint constraint-name exists. constraint-name is the name of a column constraint or table constraint. Cause You attempted to drop a table that has a referential constraint or a check constraint that refers to another table. Effect The HP Neoview database software does not drop the table. Recovery Either drop all constraints that refer to other tables and then drop the table, or reissue the DROP TABLE statement, specifying the CASCADE option.
SQL 1066 1066 Creating index index-name in metadata schema is not allowed. is the name specified for the index. index-name Cause Effect You attempted to create an index on a metadata table, which is not allowed. The operation fails. Recovery None. 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.
Effect Recovery The operation fails. Log on as the services ID before executing this command. SQL 1075 1075 The catalog must be empty. It contains at least one schema schema-name. is the name of a schema in the specified catalog. schema-name Cause Effect Recovery An attempt was made to drop a catalog that is not empty. The catalog is not dropped. None of its schemas are dropped. Drop all schemas in the catalog and resubmit.
SQL 1081 1081 Loading of index index-name failed unexpectedly. index-name is the name of the index being populated. Cause Population of the index failed, either because another concurrent operation was being performed on the base table or because data could not be loaded into the index by the call-level interface (CLI). Effect The operation fails. Recovery Determine the cause of the CLI failure and resubmit. SQL 1082 1082 Validation for constraint constraint-name failed unexpectedly.
Recovery Create a lock lock-name or specify a valid lock name and resubmit. SQL 1087 1087 DDL lock cannot be granted; invalid operation has been specified. Cause Effect An invalid utility operation requested a DDL lock. The lock request fails. Recovery Specify a valid utility operation, or check to see if invalid utilities are being run, and resubmit. SQL 1088 1088 The system generated column SYSKEY must be specified last or not specified at all in the STORE BY column list.
Cause This error is reported if a column specified in the partitioning key of the PARTITION BY (partitioning_columns) clause of a CREATE TABLE or CREATE INDEX statement is not also a member of the clustering key. Effect The table or index is not created.
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 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.
Cause The number of columns in the query do not equal the number of columns specified for the view. Effect The operation fails. Recovery Specify a query statement that has a degree that matches the number of columns in the view column list, and resubmit. 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.
Recovery For recovery action, see the accompanying error messages. SQL 1115 1115 Unable to create label for catalog.schema.object-name (file error 14). Cause The MODIFY utility could not create the target partition because the specified volume in the LOCATION clause does not exist. Effect Recovery The MODIFY utility did not process the request. None. SQL 1116 1116 The current partitioning scheme requires a user-specified clustering key on object table-name.
Recovery Enable the default ALLOW_FLOAT_DATATYPES_IN_PARTITIONING_KEY by using a control query default statement and retry the operation. 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.
Cause You attempted to perform an operation that can be performed only on a base table, and the specified object is not a base table. Effect The operation fails. Recovery 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.
column-name is the name of the column in the clustering key. Cause You attempted to make a column that is not NOT NULL NOT DROPPABLE a part of the clustering key of a table. Effect Recovery The operation fails. 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.
is the largest row size allowed. is the name of the table. maximum-row-length table-name Cause On a CREATE or ALTER TABLE statement, the size of the row exceeds the maximum allowed row size. 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.
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 Recovery The operation fails. 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 Recovery You specified a create or alter of synonym name on an object that is not a table or The operation fails. Correct the syntax so that the correct name is used. SQL 1157 1157 Synonym object name is the same as previous mapping.
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.
Cause An attempt was made to change the system catalog to an unauthorized person. The system catalog can only belong to the super ID or services ID. Effect The GIVE operation fails. Recovery Change the ownership to the super ID or the services ID. SQL 1168 1168 Internal error: unable to find object associated with UID uid. uid is the unique ID assigned to the object in metadata. Cause Effect Object not found by the specified UID. The operation fails.
is the returned file-system error number. error Cause Effect The object you attempted to drop resulted in file-system error error. The DDL DROP operation fails. Recovery See previous messages in this HP Neoview database software operation to determine the necessary corrective actions. Also, use the file-system error error-number to analyze the cause. For information about file-system errors, see Chapter 23 (page 463). Fix the error and resubmit.
value-data-type is the value specified as the default value for the column. Cause The value specified as the default for the column is incompatible with the type of the column. Effect The operation fails. Recovery Change either the column data type or the value for the default to be compatible types and resubmit. SQL 1187 1187 The schema name schema-name is reserved for SQL/MX metadata. schema-name Cause Effect is the name of an HP Neoview database schema.
Effect Recovery The operation fails. Specify a valid combination of privileges in the GRANT or REVOKE statement. SQL 1231 1231 User-defined routine procedure-name could not be created. procedure-name is the stored procedure’s ANSI name. Cause The stored procedure could not be created. Effect The CREATE PROCEDURE statement fails. Recovery Fix the error conditions identified in messages preceding this message and reissue the CREATE PROCEDURE statement.
Effect Recovery created. The operation fails. Specify a schema name for the object that matches the name of the schema being SQL 1238 1238 The character set used in TRIGGER text must be ISO88591. Cause You specified a literal with a character set other than ISO88591 in the text of a create trigger statement. Effect Recovery The operation fails. Specify only ISO88591 literals in the command. SQL 1239 1239 The character set used for string literals in VIEW must be ISO88591.
SQL 1245 1245 The supplied partition key value (key-value) for column column-name of object object-name is not valid. key-value column-name object-name Cause Effect Recovery is the specified first key value. is the column of object-name that corresponds to the invalid key value. is the name of the affected object. A utility command specified an invalid key value. The operation fails. Specify valid key values and resubmit.
Cause A CREATE TABLE or ALTER TABLE...ADD COLUMN specified a default value with a scale greater than the scale of the column. Effect The scale of the default value is set to that of the column; extra digits to the right are discarded. 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.
text is the disallowed name that was specified. Cause Effect You specified an HP Neoview database reserved object name. The object is not created. Recovery 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.
file-system error-number is an HP Neoview platform file-system error code. Cause A CREATE or ALTER operation encountered a file-system error error-number during processing of the ALLOCATE or DEALLOCATE attribute. Effect Recovery The operation fails. For information about file-system errors, see Chapter 23 (page 463). 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.
Cause You attempted to drop a constraint that is needed by a UNIQUE constraint, which is not allowed because it would leave a UNIQUE constraint on a column, but without a NOT NULL constraint for that column. Effect The operation fails. 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.
Cause Effect Recovery Cannot create a regular index on a volatile object. None. Either create a volatile index or make sure that the base object is not volatile. SQL 1284 1284 Table table-name cannot be dropped because it was specified to be NOT DROPPABLE. 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.
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. Cause NO ACTION referential action is specified in the referential integrity definition, and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is ‘OFF.
SCHEMA command if multiple schemas already exist with subvolume as the schema subvolume. Recovery Only schemas that are RDF replicated to another segment should have the same subvolume names as their corresponding schemas on the other segment. To create these, use the optional REUSE clause in the CREATE SCHEMA statement. All other schemas should have unique subvolume names.
SQL 1311 1311 Unable to action-text constraint constraint-name due to the above errors. action-text constraint-name is create. is a constraint name. Cause An error occurs during the creation of the constraint. The error that described the cause of the failure already appears. This error message provides clarification. Effect The operation fails. Recovery No recovery is necessary. SQL 1312 1312 Unable to action-text object-name due to the above errors.
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. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1503 1503 The OBJECTS - PARTITIONS definition schema relationship for type object may be corrupt. type object is the type of the affected object.
Cause Effect Recovery More than one IDENTITY column has been defined for the table. The operation failed. Define only one IDENTITY column for a table. SQL 1512 1512 ZZZZZ 99999 BEGINNER MAJOR DBADMIN IDENTITY column must be defined as a NOT NULL NOT DROPPABLE column. Cause Effect Recovery The IDENTITY column is not defined as a NOT NULL NOT DROPPABLE column. The operation failed. Define NOT NULL NOT DROPPABLE on the IDENTITY column.
constraint table is the name of the constraint. 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. Recovery No recovery is available.
3 Neoview Compiler Messages (2000 Through 2999) This section includes process creation errors, IPC errors, static compilation errors, and miscellaneous errors from the optimizer. SQL 2001 2001 Error or warning number occurred while opening or reading from DEFAULTS table name. Using values. number name values is the error number. is the DEFAULTS table name. is the default values file. Cause The HP Neoview database software was unable to open system defaults table name because of error number.
SQL 2006 2006 Internal error: assertion failure (detail text) in file name at line number. detail text name number is information about the error. is the name of the file. is the line number. Cause The HP Neoview database software received an internal error in file name at line number. More information is in detail text. Effect The operation fails. Recovery Do not attempt recovery.
SQL 2012 2012 Server process name could not be created - Operating system error number-1, TPCError = number-2, error detail = text. (See Operating system procedure PROCESS_LAUNCH_ for details). name number-1 number-2 text is the name of the server process. is the error number. is the TPCError. is the error message text. Cause The HP Neoview database software was unable to create server process name because of the process control procedure error number it received. More information appears in detail text.
name is the server process name. Cause The HP Neoview database software started server process name, but it had undefined externals. Effect None. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 2017 2017 Server process name could not be created - no more processes (PCBs) available. name is the server process name.
SQL 2021 2021 System error number occurred in procedure name from process name. number procedure name process name Cause Effect is the error number. is the name of the procedure. is the server process name. The HP Neoview database software received an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
process id identifies the process. Cause The HP Neoview database software was unable to create server process name because the CPU is unavailable or does not exist. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 2027 2027 Operating system error number while sending a startup message to process name. is the error number. is the server process name.
is the error number. is the name of the server process. number name Cause The HP Neoview database process id received process control procedure error number while communicating with the server process name. Effect The Neoview database software is not able to communicate with the process. Recovery Use the process control procedure error to diagnose and correct the problem. SQL 2034 2034 process id: Operating system error number while communicating with server process name.
SQL 2050 2050 attribute is not the name of any DEFAULTS table attribute. is the attribute name you specified. attribute Cause If the SQLSTATE is 42000, this is an error. You attempted to set a CONTROL QUERY DEFAULT setting, but the attribute name you specified is not valid. If the SQLSTATE is 01000, this is a warning. In an earlier HP Neoview database session, you inserted a row into a DEFAULTS table whose attribute column value is invalid. Effect If this is an error, the operation fails.
Recovery Set the value of CQD HIST_NO_STATS_ROWCOUNT greater than or equal to the value of HIST_NO_STATS_UEC. If you want to use a smaller value, reduce the value of CQD HIST_NO_STATS_UEC first. Note that any change in either of the two values can have an effect on the plan quality. SQL 2055 2055 The specified value 'value' for DEFAULTS attribute name is not valid. Cause You specified an invalid value for the DEFAULTS attribute listed in the message. Effect The operation fails.
Cause You defined procedure name twice in this module. Effect The HP Neoview database software uses the first definition. Recovery This is an informational message only; no corrective action is needed. SQL 2061 2061 Static cursor name has already been defined in this module. The previous definition, as a static cursor, is being retained and this latest one ignored. name is the cursor name. Cause You defined the static cursor name twice in this module.
Recovery Correct the syntax and resubmit. SQL 2066 2066 Cursor cursor-name was not found in module module-name. cursor-name module-name is the cursor name. is the module name. Cause The HP Neoview database software could not find cursor cursor-name in module module-name. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 2067 2067 Descriptor name has already been defined in this module. The previous definition is being retained and this latest one ignored.
definition type is the previous definition Cause type. You defined name twice in this module in which it was defined as a type definition Effect The HP Neoview database software uses the previous definition. Recovery Specify a new name for the item and resubmit, if necessary. SQL 2072 2072 A simple value specification that is a literal is not yet supported. Cause You specified a simple value as a literal, which is not supported. Effect The operation fails.
SQL 2080 2080 Error number while reading file: value bytes were read from text when value were expected in modul name. Cause The HP Neoview database software received error number while reading module name. value shows the number of bytes read from text. The module file is unusable. Either it has been corrupted or overwritten. Effect The operation fails. Recovery Recompile the module definition file, using the HP Neoview compiler, to create a valid module file.
is the error number. is the name of the file. number name Cause The HP Neoview database software received error number when closing file name. Effect The Neoview database software does not close the file. Recovery Use the error number to diagnose and correct the problem. SQL 2086 2086 The file name could not be purged. This file contains the results of a failed compilation and should be purged. name is the name of the file.
Recovery Supply a timestamp and resubmit. SQL 2094 2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored. Cause You specified a timestamp statement twice in this module. Effect The HP Neoview database software uses the first timestamp. Recovery Informational message only; no corrective action is needed. SQL 2095 2095 Module file name1, expected to contain module name2, instead contains name3.
Effect Any statement with an error is not compiled. Recovery If this is a warning, this is an informational message. Otherwise, correct the syntax and resubmit. SQL 2100 2100 Break was received. The compilation has been aborted. Cause Effect Recovery The HP Neoview database software received a break and aborted the compilation. The Neoview database software does not continue compilation. Informational message only; no corrective action is needed. SQL 2101 2101 Compilation failure due to internal error.
Cause The HP Neoview database software was unable to compile this query, either because it was not able to use the MEDIUM optimization level or because you used an incompatible CONTROL QUERY SHAPE specification. Effect The Neoview database software is unable to process this query. Recovery If applicable, use the MAXIMUM optimization level, correct the CONTROL QUERY SHAPE specification, and resubmit.
SQL 2201 2201 SQL compilation return code is mxcmp non-zero exit code. Cause You invoked mxCompileUserModule on an application file that has an embedded module definition. An SQL compilation of an embedded module definition resulted in an HP Neoview compiler nonzero exit code, indicating a warning or error. Effect The operation fails. Recovery Review the Neoview compiler warning or error message. Trace the diagnostic back to the module source file and correct the offending source statement.
SQL 2206 2206 Temporary file temp filename could not be created. temp filename is the name of the temporary file. Cause You invoked mxCompileUserModule on an application file that has many embedded module definitions. The tool cannot create another temporary file to hold the contents of an embedded module definition. Effect The operation fails. Recovery Verify that you have write access to TMPDIR (the directory where temporary files are created) and that TMPDIR has free space.
Recovery Review the module name list syntax. Verify that the module names are specified correctly and retry the command. SQL 2212 2212 A syntax error was encountered: expecting string1 instead of string2. Cause You invoked mxCompileUserModule on an application file, 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.
Effect Recovery The operation fails. Verify that your Neoview compiler exists and is executable and retry the command. SQL 2221 2221 SQL compiler invocation failed with return code error code. is the error message code. error code Cause You invoked mxCompileUserModule on an application file to SQL compile its module definitions. This command invoked the HP Neoview compiler, which returned error code, indicating an abnormal termination. Effect The operation fails.
number Cause Effect is the line number. An error occurred in file name at line number. Compilation failed because of a syntax error. Recovery This is a general error that is issued before a more specific error. Use the error that follows this one to diagnose and correct the problem.
4 Parser and Compilation Messages (3000 Through 3999) SQL 3000 3000 An internal error occurred in module name on line number. DETAILS(detailed text). Cause An internal error has occurred in module name on line number. Details are displayed in detailed text. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 3001 3001 Syntax error at or before SQL text.
Effect The operation fails. Recovery resubmit. Declare a cursor name, or use the name of a previously prepared statement, and SQL 3006 3006 In a dynamic cursor declaration, both the cursor and the statement must be named in the same way: both must be literals or both must be string host variable expressions. Cause You attempted to declare a dynamic cursor in a way that does not match the statement. Both must be literals or both must be string host variable expressions. Effect The operation fails.
Cause You specified an invalid name name, which must have three or fewer parts. catalog.schema.table is valid. catalog.schema.table.name is invalid. Effect Recovery The operation fails. Correct the name and resubmit. SQL 3012 3012 COUNT is the only aggregate function that accepts (*) as an operand. Cause You submitted an AVG or other aggregate function that does not allow (*) as an operand. Only COUNT allows you to use (*). Effect Recovery The operation fails. Remove the (*) operand and resubmit.
SQL 3018 3018 An unsigned smallint was expected, not value. Cause You specified an unexpected value, value. The HP Neoview database software requires an unsigned smallint. Effect Recovery The operation fails. Replace the value with an unsigned smallint and resubmit. SQL 3019 3019 An unsigned number was expected within the parentheses, not value. Cause You specified an unexpected value, value. The HP Neoview database software requires an unsigned number. Effect Recovery The operation fails.
Effect Recovery The operation fails. Remove the MATCH PARTIAL clause and resubmit. SQL 3025 3025 The format of the subvolume name part in the specified location name name is not valid. The subvolume name part must be eight characters long and begin with the letters ZSD. Cause You used an invalid location name for a subvolume that must be eight characters long and begin with the letters ZSD. Effect Recovery The operation fails. Correct the name and resubmit.
SQL 3031 3031 CASCADE drop behavior is not yet supported. Cause You attempted to drop an object with the CASCADE option, which is not supported. Effect The operation fails. Recovery Drop the item without CASCADE. SQL 3032 3032 The COLUMN clause in the ALTER TABLE statement is not yet supported. Cause You used the COLUMN clause in the ALTER TABLE statement, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3038 3038 PIC X types cannot have leading signs, or any signs at all. Cause Effect Recovery You specified a PIC X type with a sign, which is not supported. The operation fails. Remove the sign, or redefine the type, and resubmit. SQL 3039 3039 PIC X types do not have any COMP representation. Cause Effect Recovery You specified a PIC X type with COMP, which is not supported. The operation fails.
Effect Recovery The operation fails. Correct the interval value to a valid one and resubmit. SQL 3045 3045 The date ‘value’ is not valid. Cause Effect Recovery You specified an invalid date value. The operation fails. Change the date value and resubmit. SQL 3046 3046 The time ‘value’ is not valid. Cause Effect Recovery You specified an invalid time value. The operation fails. Correct the time value and resubmit. SQL 3047 3047 The timestamp ‘value’ is not valid.
Effect Recovery The operation fails. Define the column with only one HEADING clause and resubmit. SQL 3052 3052 Duplicate NOT NULL clauses were specified in column definition name. Cause Effect Recovery You defined column name with more than one NOT NULL clause. The operation fails. Define the column with only one NOT NULL clause and resubmit. SQL 3053 3053 Duplicate PRIMARY KEY clauses were specified in column definition name.
Effect Recovery The operation fails. Correct the BLOCKSIZE value and resubmit. SQL 3059 3059 The specified size value (in the MAXSIZE clause or EXTENT size clause) is not valid. Cause Effect Recovery You provided an invalid size value in the MAXSIZE clause. The operation fails. See the Neoview SQL Reference Manual for correct size values, and resubmit. SQL 3060 3060 The specified percentage value in the DSLACK clause is not valid.
Effect Recovery The HP Neoview database software is unable to process this definition. Change the definition of the primary key constraint so that it is NOT DROPPABLE. SQL 3067 3067 ALTER TABLE ADD CONSTRAINT allows only DROPPABLE constraints. Cause You specified an ALTER TABLE ADD CONSTRAINT statement with NOT DROPPABLE constraints. Only DROPPABLE constraints are allowed. Effect The operation fails. Recovery Correct the syntax and resubmit.
SQL 3074 3074 The SEPARATE BY clause is not supported. Cause Effect Recovery You specified the SEPARATE BY clause, which is not supported. The operation fails. Correct the syntax and resubmit. SQL 3075 3075 The [NO]COMPRESS clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause You specified an ALTER INDEX...ATTRIBUTE(S) statement that includes a [NO]COMPRESS clause, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 3081 3081 Duplicate ALLOCATE clauses were specified. Cause Effect Recovery You specified duplicate ALLOCATE clauses. The operation fails. Correct the syntax and resubmit. SQL 3082 3082 Duplicate [NO]AUDIT clauses were specified. Cause Effect Recovery You specified duplicate [NO]AUDIT clauses. The operation fails. Correct the syntax and resubmit. SQL 3083 3083 Duplicate [NO]AUDITCOMPRESS clauses were specified.
Recovery Correct the syntax and resubmit. SQL 3088 3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. Cause You specified an ALTER TABLE statement with both ALLOCATE and DEALLOCATE clauses, which is not supported. Effect The operation fails. Recovery Correct the ALTER TABLE statement to include either ALLOCATE or DEALLOCATE. SQL 3089 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause You specified an ALTER TABLE...
Cause You specified a CREATE INDEX statement that includes the DEALLOCATE clause, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3095 3095 Duplicate [NO]ICOMPRESS clauses were specified. Cause Effect Recovery You specified a statement with duplicate [NO]ICOMPRESS clauses. The operation fails. Correct the syntax and resubmit. SQL 3096 3096 Duplicate [NO]SERIALWRITES clauses were specified.
Recovery Correct the syntax and resubmit. SQL 3102 3102 Duplicate PARALLEL EXECUTION clauses were specified. Cause Effect Recovery You specified a statement with duplicate PARALLEL EXECUTION clauses. The operation fails. Correct the syntax and resubmit. SQL 3103 3103 Duplicate PARTITION clauses were specified. Cause Effect Recovery You specified a statement with duplicate PARTITION clauses. The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the statement to include one of these clauses. SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause Effect Recovery You specified a statement with duplicate STORE BY clauses. The operation fails. Correct the syntax and resubmit. SQL 3110 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. Cause You specified a statement with both LIKE and ATTRIBUTE(S) clauses, which is not supported.
SQL 3115 3115 Duplicate ISOLATION LEVEL clauses were specified. Cause You specified a statement with duplicate ISOLATION LEVEL clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3116 3116 Duplicate transaction access mode clauses were specified. Cause You specified a statement with duplicate access mode clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3117 3117 Duplicate DIAGNOSTICS SIZE clauses were specified.
SQL 3123 3123 The format of the file name part in the specified location name name is not valid. The file name part must be eight characters long and end with the digits 00. name is the name of the file. Cause You specified an invalid file name. The file name must be eight characters long and end with the digits 00 (zero zero). Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3127 3127 An invalid character was found in identifier name.
SQL 3132 3132 The HEADING for column name exceeds the maximum size of 128 characters. name is the name of the column. Cause You specified a heading for column name that exceeds the maximum size of 128 characters. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3133 3133 PERFORM is valid only in COBOL programs. Cause You specified a PERFORM statement, which is supported only in COBOL programs. Effect The operation fails. Recovery Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3139 3139 A range partitioned index requires a FIRST KEY clause. Cause clause. Effect Recovery You attempted to create a range-partitioned index without a required FIRST KEY The operation fails. Correct the syntax and resubmit. SQL 3140 3140 The isolation level cannot be READ UNCOMMITTED for an INSERT, UPDATE, DELETE, or DDL statement.
SQL 3147 3147 In an IN predicate whose right operand is a value list, the left operand must be scalar (degree of one). Cause You specified an IN predicate whose right operand is a value list but whose left operand is not scalar, which is required. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3148 3148 Environment variable value is being ignored because this version of the code is Release, not Debug. Actual query results will likely not match expected results.
Recovery Correct the syntax and resubmit. SQL 3155 3155 The POPULATE and NO POPULATE clauses cannot coexist in the same CREATE INDEX statement. Cause You specified a CREATE INDEX statement using both the POPULATE or NO POPULATE clauses, which is not supported. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3157 3157 A catalog name is required. Cause You attempted to create a catalog without specifying a catalog name. Effect The operation fails.
Recovery Correct the syntax and resubmit. SQL 3162 3162 Procedure parameter name was not used. name is the name of the procedure parameter. Cause The HP Neoview database software did not use procedure parameter name. Effect None. Recovery Informational message only; no corrective action is needed. SQL 3163 3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. name is the host variable.
Recovery Correct the syntax and resubmit. SQL 3168 3168 The FOR ... ACCESS clause is not allowed in a CREATE VIEW statement. Cause You specified a CREATE VIEW statement with the FOR ... ACCESS clause, which is not supported. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 3169 3169 name is not a known collation. Cause Effect Recovery You attempted to use a collation that is not a known collation. The operation fails. Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 3176 3176 Subqueries are not allowed in the IF Condition. Cause You specified an IF statement that contains a subquery. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3177 3177 Character set name requires an even number of characters in the length declaration of the data type. name is the name of the character set. Cause You specified a character set with an odd number of characters in the length declaration of the data type.
SQL 3182 3182 Extra semicolon(;) in a compound statement. Cause Effect You specified an extra semicolon in a compound statement. The operation fails. Recovery Correct the syntax and resubmit. SQL 3183 3183 Duplicate Row FORMAT clauses were specified. Cause You specified a CREATE TABLE statement containing multiple occurrences of the Row FORMAT clause. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3184 3184 An invalid SQLSTATE value string1 was found.
Cause You specified a STORE BY primary key but did not define a NOT DROPPABLE primary key. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3189 3189 Setting a lock timeout is not allowed on a view. Cause Effect You attempted to set a lock timeout on a view, which is not supported. The operation fails. Recovery None. SQL 3192 3192 Union operands table1 and table2 have different access/lock modes.
Recovery Remove all but one of the table-level access options for each table reference. SQL 3199 3199 Column col-name is incorrectly specified. Keywords ASCENDING and DESCENDING are not allowed in the partitioning key list. col-name is the name of the column. Cause You cannot specify ordering for columns of a partitioning key clause. Effect The operation fails.
SQL 3206 3206 The name for an object of this type must be fully qualified, or set NAMETYPE ANSI. Cause In the CREATE PROCEDURE statement, you specified a partially qualified name when NAMETYPE was not set to ANSI. Effect Recovery The operation fails. Set NAMETYPE ANSI or fully qualify the name. SQL 3207 3207 Value for DYNAMIC RESULT SETS must be zero. Cause In the CREATE PROCEDURE statement, you specified the optional DYNAMIC RESULT SETS clause with nonzero value. Effect Recovery The operation fails.
SQL 3212 3212 Minimum length of LONG VARBINARY is value. Cause You attempted a CREATE TABLE table name (columnname long varbinary(N)) where N < current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect The operation fails. Recovery Increase the CREATE TABLE statement’s long varbinary column width N or decrease the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit. SQL 3213 3213 Maximum length of LONG VARCHAR is value.
Recovery Do not use KANJI or KSC5601 character expressions in these functions. SQL 3218 3218 A table reference cannot contain DELETE or UPDATE in a CREATE VIEW statement. Cause A CREATE VIEW statement was issued with a DELETE or UPDATE operation as a table reference. Effect Recovery The statement does not compile. Do not use DELETE or UPDATE in a CREATE VIEW statement. SQL 3219 3219 The value for DYNAMIC RESULT SETS must be between 0 and 255.
Effect Recovery SHOWLABEL does not display output. Reissue the command with a valid location name. SQL 3228 3228 SHOWLABEL failed for physical location name location-name. SHOWLABEL supports only the data forks of SQL/MX tables, views, and indexes. location-name specifies the physical location name of an HP Neoview database software object. Cause SHOWLABEL supports only the physical names of data forks of the HP Neoview database software objects (physical location names that end in “00”).
dependent-object is the name of a dependent object of the target table, such as an index, after trigger, materialized view, or referential integrity constraint. Cause An INSERT, UPDATE, or DELETE operation into a table with dependent objects was attempted when the NO ROLLBACK transaction setting is ON. Effect Compilation of the statement fails. Recovery If you intend to use NO ROLLBACK, drop the dependent object.
SQL 3237 3237 Duplicate NO ROLLBACK clauses were specified. Cause Duplicate NO ROLLBACK clauses were specified in a SET TRANSACTION statement. Effect SET TRANSACTION statement fails, and the existing transaction state remains unaffected. Recovery Remove the duplicate NO ROLLBACK clause and issue the SET TRANSACTION statement again. SQL 3238 3238 Duplicate AUTOABORT clauses were specified. Cause Duplicate AUTOABORT clauses were specified in a SET TRANSACTION statement.
SQL 3402 3402 The format of the value hexadecimal string literal is not valid. Cause You either used illegal hexadecimal digits, supplied an odd number of hexadecimal digits, or misplaced space separators. Effect The operation fails. Recovery Specify the string in the correct hexadecimal format and resubmit. SQL 3403 3403 Function name1 does not take an operand with character set name2. Cause You specified a character operand with a character set that the function does not support.
SQL 3411 3411 Expressions are not allowed as IDENTITY column values. Specify DEFAULT or supply a largeint value. Cause You tried to specify an expression in place of a constant largeint value or DEFAULT. Effect The operation failed. Recovery Specify DEFAULT or supply a largeint value. SQL 3412 3412 IDENTITY column column-name must be the primary key or must have a unique index on it. column-name is the name of the IDENTITY column.
is the name of the function. name Cause The last operand you supplied for function name is NULL, which is not allowed. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3417 3417 Invalid DISK POOL num1 as the maximum number of disk pools allowed is num2. is the specified disk pool number. is the maximum number of disk pools set either through the DDL or through the default POS_NUM_DISK_POOLS.
Recovery Retry the query and use a valid number of disk pools. The number of disk pools must be greater than 0 and a multiple of 2 power times the number of disks per node and less than or equal to the number of disks on the cluster. Alternatively, to pick the default number of disk pools, ignore the DISK POOL OF clause. SQL 3421 3421 Duplicate NO PARTITION clauses were specified. Cause Effect Recovery The NO PARTITION clause was specified more than once. The operation fails.
5 Binder and Compilation Messages (4000 Through 4999) SQL 4000 4000 Internal error in the query binder. Cause Effect The HP Neoview database software received an internal error in the query binder. The Neoview database software is unable to process this query. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 4001 4001 Column name1 is not found. Tables in scope: name2. Default schema: name3.
If a column is part of a JOIN operation, you no longer qualify its name with its original table name2. Effect The operation fails. Recovery Correct the syntax and resubmit. If the column is part of a JOIN, remove the table qualifier and use only the column name. SQL 4004 4004 Column name name1 is ambiguous. Tables in scope: names. Default schema: name2. Cause You referenced column name1, whose parent table is ambiguous.
Recovery Correct the syntax and resubmit. SQL 4010 4010 There are no columns with the correlation name table name. Cause You specified columns with the table name qualifier, which does not exist or is not in scope at this point in the query. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4011 4011 Reference made to column name via star (*) is ambiguous. name is the name of the column. Cause You referred to column name using the SELECT * or SELECT TBL.
SQL 4016 4016 The number of derived columns (value1) must equal the degree of the derived table (value2). Cause You specified a statement in which the number of derived columns (value1) does not equal the degree of the derived table (value2). They must be equal. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4017 4017 Derived column name name was specified more than once. Cause Effect Recovery You specified column name more than once. The operation fails.
SQL 4023 4023 The degree of each row value constructor (value) must equal the degree of the target table column list (value). Cause You specified a statement, such as INSERT, in which a row value constructor does not equal the degree of the target table column list. For example: INSERT INTO table (acol, bcol) VALUES (1, 2, 3); is wrong because the number of columns does not match the number of values. Effect The operation fails. Recovery Correct the syntax and resubmit.
SQL 4028 4028 Table or view name is not updatable. Cause Effect Recovery You attempted to update table name, which is not updatable. The operation fails. None. SQL 4030 4030 Column name has an invalid combination of datetime fields (internal field number, internal field number, internal field number). Cause Effect Recovery You specified column name, which is an invalid combination of datetime fields. The operation fails. Correct the syntax and resubmit.
Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4036 4036 The source field of the EXTRACT function must be of DateTime or Interval type. Cause You specified a source field of the EXTRACT function that is not a DATETIME or INTERVAL data type. Effect Recovery The operation fails. Correct the source field type and resubmit. SQL 4037 4037 Field name cannot be extracted from a source of type specification.
SQL 4042 4042 The operands of a comparison predicate must be of equal degree. Cause You specified a comparison predicate with operands that are not of equal degree, which is required. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4043 4043 The operand of function name must be character. Cause You specified an operand for function name that is not a character, which is required. Effect The operation fails. Recovery Correct the syntax and resubmit.
Recovery Correct the syntax and resubmit. SQL 4049 4049 A CASE expression cannot have a result data type of both type1 and type2. Cause You specified a CASE expression with a result data type of two data types. It must be one of data type. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4050 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation).
SQL 4056 4056 Exposed name name appears more than once. Cause You specified a statement with an exposed table name that appears more than once. For example: SELECT * FROM tblx, tblx; Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4057 4057 Correlation name name1 conflicts with qualified identifier of table name2. Cause You specified correlation name1, which conflicts with a qualified identifier of table name2.
Effect Recovery The operation fails. Correct the function and resubmit. SQL 4063 4063 The operands of function name must be comparable character data types (that is, of the same character set and collation). Cause You specified operands for function name with noncomparable character data types. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4064 4064 The operands of function name must be compatible character data types (that is, of the same character set).
Cause You specified an invalid operand for function name. It must be type exact numeric. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4071 4071 The first operand of function name must be a datetime. Cause Effect Recovery You specified an invalid operand for function name. It must be datetime. The operation fails. Correct the syntax and resubmit. SQL 4072 4072 The operand of function name must be a datetime containing a name.
Cause You specified an invalid argument in function name. This function accepts only one or two arguments, both numeric. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4078 4078 Function name does not accept a weight operand. Cause You specified an invalid argument in function name. The first argument must be numeric. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4079 4079 The operands of function name must be numeric.
Cause Effect Recovery You specified a prototype value that is not a valid qualified name. The operation fails. Correct the syntax and resubmit. SQL 4088 4088 The number of values in each TRANSPOSE item of a TRANSPOSE set must be equal. Cause You specified a TRANSPOSE set with an unequal number of values in each TRANSPOSE item. Effect Recovery The operation fails. Correct the syntax and resubmit. SQL 4089 4089 Check constraint name contains a subquery. This is not yet supported.
Recovery Correct the syntax and resubmit. SQL 4097 4097 A NULL operand is not allowed in function name. Cause Effect Recovery You attempted to use a NULL operand in function name, which is not supported. The operation fails. Correct the syntax and resubmit. SQL 4098 4098 A NULL operand is not allowed in operation name. Cause Effect Recovery You included a NULL operand in operation name, which is not supported. The operation fails. Correct the syntax and resubmit.
SQL 4104 4104 If a character literal was intended, you must use the single quote delimiter: ‘literal’. The use of double quotes causes SQL/MX to interpret column name as a delimited identifier column name. column name is a delimited ANSI identifier, such as MYCOL. Cause You attempted to select from a table using a character literal, but you used double quotes as the delimiter instead of single quotes.
SQL 4109 4109 Sequence functions are placed incorrectly: name. Cause You specified a query that includes a SEQUENCE BY clause that contains an illegally placed sequence function name. Sequence functions (such as RUNNINGSUM, MOVINGSUM, LASTNOTNULL) are supported only in the select list or the HAVING clause of the query expression containing the SEQUENCE BY clause.
*** ERROR[4111] The query contains a SEQUENCE BY clause but no sequence functions. *** ERROR[8822] Unable to prepare the statement. Correct the syntax with one of these: >>select a, runningavg(c) from T1 sequence by a; >>select a from T1 order by a; SQL 4112 4112 Absolute and relative sampling cannot occur in the same BALANCE expression. Cause You attempted to perform absolute and relative sampling in the same balance expression, which is not supported.
SQL 4117 4117 The cursor query expression might be nonupdatable. Cause You specified a join or a nonupdatable query in an updatable cursor query (that is, one with an optional FOR UPDATE OF clause). That cursor's select list did not select the target column of the update. Effect The operation fails. Recovery An updatable cursor query should specify the target update column in the select list of the query. Use the FOR UPDATE OF clause only if the cursor query is updatable.
+>FOR UPDATE OF UPDATE_FLAG ; *** ERROR[4118] The cursor query expression is not updatable. *** ERROR[8822] Unable to prepare the statement. SQL 4119 4119 The requested number of parallel extract streams must be greater than one and cannot exceed the number of configured CPUs, number. number is the number of configured Neoview processing nodes. Cause HP Neoview database software was unable to compile a parallel extract producer query because the number of requested streams was either too low or too high.
SQL 4124 4124 More than one table will be locked: name. name is the name of the table. Cause Effect Recovery The HP Neoview database software is preparing to lock more than one table. None. Informational message only; no corrective action is needed. SQL 4125 4125 The select list of a subquery in a row value constructor must be scalar (degree of one) if the subquery is one of several expressions rather than the only expression in the constructor.
SQL 4130 4130 SIGNAL parameter 3 must be of type string Cause Effect Recovery You specified a SIGNAL parameter of an incorrect type. The operation fails. Correct the syntax and resubmit. SQL 4133 4133 Both trim character and source have to be CHARACTER type. Cause Effect Recovery The type of the trim source and trim character is not CHARACTER. The operation fails. Ensure that the type of the source and trim character is CHARACTER. SQL 4134 4134 The operation (name) is not allowed. Try UNION ALL instead.
SQL 4150 4150 Primary key of table expression name must be used for join with embedded operation expression. Tables in scope: name. Cause You performed an embedded DELETE or UPDATE and are now attempting to join the result set of whatever that operation was with the result set of another expression. You did not use the primary key of the second expression for your join. You must use the primary key to prevent returning multiple rows being returned for a single deleted or updated row.
SQL 4157 4157 Inner relation of left join cannot be stream expression. Tables in scope: name. Cause You attempted to perform a left join using the result set of a stream expression as the inner relation. Effect Recovery The HP Neoview database software is unable to compile the statement. Modify the statement and resubmit. SQL 4158 4158 Join of stream expressions is not supported. Tables in scope: name. Cause Effect Recovery You attempted to perform a join of stream expressions.
SQL 4163 4163 GROUP BY is not supported for embedded name1 expression. Tables in scope: name2. Cause You attempted to perform a GROUP BY in conjunction with an embedded expression. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4164 4164 Outer relation of right join cannot be embedded name expression. Tables in scope: name. Cause You attempted to perform a right join using an embedded expression as the outer relation.
Cause You attempted to perform a DECLARE... FOR UPDATE clause that included an embedded DELETE statement. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4170 4170 Stream expressions are not supported for insert statements. Cause Effect You attempted to perform an insert statement that includes a stream expression. The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit.
Recovery Modify the statement and resubmit. SQL 4177 4177 Update of name1 column name2 is not permitted on rollback. Cause You attempted to update clustering key components or columns associated with referential integrity constraints during a rollback. Effect Recovery The HP Neoview database software is unable to compile the statement. Modify the statement and resubmit. SQL 4178 4178 Update of variable length column name is not permitted on rollback.
Effect Recovery The statement does not compile. Do not use ORDER BY with an embedded INSERT, UPDATE, or DELETE statement. SQL 4190 4190 Table table-name is not a volatile table. table-name Cause exist. Effect is the user-specified table name in the statement. The volatile table name specified in the VOLATILE TABLE SQL statement does not None. Recovery Ensure that the volatile table with the specified table-name is created before issuing the SQL statement.
Effect None. Recovery Either remove the volatile table name from the SQL statement, or ensure that the table name is fully qualified. SQL 4200 4200 Stream expressions are not supported for compound statements. Cause You attempted to use a stream expression for a compound statement. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4201 4201 Embedded operation expression is not supported for compound statements.
Cause You attempted to perform an embedded action that is supported only for key-sequenced tables. Effect Recovery The HP Neoview database software is unable to compile the statement. Modify the statement and resubmit. SQL 4206 4206 Embedded name is supported only for updatable views. View: name2. Cause views. You attempted to perform an embedded action that is supported only for updatable Effect The HP Neoview database software is unable to compile the statement.
SQL 4213 4213 Use of rowsets in a predicate with embedded update/delete is not supported. Cause delete. You attempted to use a rowset as a predicate with an embedded update or embedded Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4214 4214 The SET ON ROLLBACK clause is not allowed on a non-audited table. Table: name. Cause You attempted to use a SET ON ROLLBACK clause to update a column in a nonaudited table.
SQL 4304 4304 Host variable or dynamic parameter parameter-name is used in more than one OUT or INOUT parameter for routine routine-name. Results may be unpredictable. Cause In the HP Neoview database software statement being compiled, you attempted to invoke a stored procedure that contains the same host variable or dynamic parameter in more than one OUT or INOUT parameter. Effect This is a warning message only. Results will be unpredictable. The host variable could have any one of the actual OUT values.
Recovery Migrate to an HP Neoview database software version that supports stored procedure result sets. SQL 4310 4310 USER(x) is currently supported only in the outermost SELECT list. For example, it cannot be part of the subquery. Cause You tried to use the USER(x) function somewhere other than the outermost SELECT clause. This function is not yet fully supported. Effect Recovery The operation fails. Correct the query and retry the request. SQL 4313 4313 Function rand()is not supported.
num1 num2 table-name is the number of columns specified for the left operand of PARTITIONING_KEY option in the KEY_RANGE_COMPARE function. is the number of columns in the partitioning key of the table table-name. is the name of the table on which the KEY_RANGE_COMPARE function is used. Cause You did not specify the correct number of columns in the left operand of the PARTITIONING_KEY clause of the KEY_RANGE_COMPARE function so that the clause matches the partitioning columns of table table-name.
6 Normalizer Messages (5000 Through 5999) SQL 5000 5000 Internal error in the query normalizer. Cause Effect The optimizer received an internal error during query normalization. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
7 Optimizer Messages (6000 Through 6999) SQL 6000 6000 Internal error in the query optimizer. Cause Effect The optimizer received an internal error during query optimization. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 6001 6001 DISTINCT aggregates can be computed for only one column per table expression.
Recovery Undo your changes by using the CLEAR option in UPDATE STATISTICS and regenerate the statistics. SQL 6007 6007 Multi-column statistics for columns names from table name were not available; as a result, the access path chosen might not be the best possible. Cause Statistics are not available for the multicolumn join you are performing.
filename dirname errnum is the specified file name. is the specified directory name. is the returned file-system error number. Cause The operation was attempted either in an invalid mode or by specifying an invalid directory. Effect Recovery The operation failed with the indicated error message. Correct the condition reported by the error message, and retry the operation.
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.
9 Executor Messages (8000 Through 8999) SQL 8001 8001 An internal executor error occurred. Cause Effect The HP Neoview database software has received an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8002 8002 The current nowaited operation is not complete. Cause Effect A nowait call-level interface (CLI) operation was started.
SQL 8007 8007 The operation has been canceled. Cause You pressed the break key. Effect The operation stops. Recovery None. SQL 8008 8008 Catalog name name is not valid. name is the name of the catalog. Cause You specified an invalid catalog name. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8009 8009 Schema name name is not valid.
SQL 8014 8014 A SELECT statement within compound statement did not return any row. Cause You specified a SELECT statement inside a compound statement that did not return any rows. Effect None. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8015 8015 Aborting transaction because a compound statement performed an update operation followed by a SELECT statement that did not return any row.
Cause You attempted to perform an operation on table name1 that is prevented by check constraint name2. Effect The operation fails. Recovery Change the data you are attempting to enter to be consistent with the constraint. SQL 8102 8102 The operation is prevented by a unique constraint. Cause You attempted to perform an operation that is prevented by a unique constraint. Effect The HP Neoview database software could not perform the operation.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8107 8107 Self-referencing INSERT statement without blocking operator is not allowed with AUTOCOMMIT OFF.
SQL 8302 8302 All partitions of type object are unavailable. is the type of the affected object, such as table. is the fully qualified ANSI name of the affected object. type object Cause Late name resolution could not resolve the ANSI name to an available partition. Effect The operation fails. Recovery resubmit. Determine why none of the partitions were available, then correct the error and SQL 8303 8303 Anchor file name contains invalid data.
SQL 8402 8402 22001 A string overflow occurred during the evaluation of a character expression. Cause If the SQLSTATE is 22001, this is an error. You attempted to use a character expression whose length caused a string overflow. If the SQLSTATE is 01004, this is a warning. You attempted to use a character expression whose length caused a string overflow. Effect If this is an error, the operation fails. If this is a warning, your string is truncated. Recovery Do not attempt recovery.
Cause You specified a LIKE predicate with an invalid escape character argument, which must be one character in length. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8410 8410 An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character. Cause You specified a LIKE pattern whose syntax is incorrect.
SQL 8415 8415 The provided DATE, TIME or TIMESTAMP is not valid and cannot be converted. Cause You provided an invalid DATE, TIME or TIMESTAMP, which could not be converted. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8416 8416 A datetime expression evaluated to an invalid datetime value.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8422 8422 The provided INTERVAL is not valid and cannot be converted. Cause You provided an INTERVAL that is not valid and that could not be converted. Effect The operation fails. Recovery Do not attempt recovery.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8551 8551 Error NSK err was returned by the file system on object-name. NSK err object-name Cause Effect is the file-system error returned. is the name of the object. The file system returned error NSK err on object-name. The operation fails. Recovery Do not attempt recovery.
SQL 8571 8571 SQL/MX could not allocate sufficient memory to execute query. Cause The system does not have enough memory to execute the query. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8572 8572 The statement has incurred a fatal error and must be deallocated. Cause The HP Neoview database software has received an internal error.
Recovery Recompile the program. SQL 8577 8577 Table, index or view name was not found. name is the name of the object. Cause Effect Recovery The HP Neoview database software could not find the object name. The operation fails. Verify the location of the object and resubmit. SQL 8578 8578 Similarity check passed. Cause Effect Recovery The similarity check passed. None. Informational message only; no corrective action is needed.
SQL 8602 8602 The file system reported error number on a lock/unlock operation. is the error number. number Cause The file system received process control procedure error number while performing a locking or unlocking operation. Effect The operation fails. Recovery Use the process control procedure error to diagnose and correct the problem. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Effect Recovery The operation fails. Correct the syntax so that the sequence of events is correct, and resubmit. SQL 8608 8608 Transaction subsystem name returned error number on rollback transaction. name number is the name of the subsystem. is the error number. Cause Transaction subsystem name has returned error number while rolling back a transaction. Effect Recovery The operation fails. Contact the GMCSC. SQL 8609 8609 Waited rollback performed without starting a transaction.
Cause The HP Neoview database software cannot start a transaction when multiple contexts are present. Effect The transaction is unable to start. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8690 8690 An invalid character value encountered in TRANSLATE function. Cause The source contains a character that cannot be translated to the target. Effect The operation fails.
SQL 8803 8803 The provided input descriptor does not exist in the current context. Cause This is an internal error. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8804 8804 The provided input statement does not exist in the current context. Cause This is an internal error. Effect The operation fails. Recovery Do not attempt recovery.
SQL 8809 8809 Open of the module file name failed with error number. name number Cause Effect Recovery is the name of the file. is the error number returned. The HP Neoview database software was unable to open module file name. The operation fails. Check the location of the module file and retry the operation. SQL 8811 8811 Trying to close a statement that is either not in the open state or has not reached EOF. Cause Effect This is an internal error. The operation fails.
SQL 8816 8816 An internal error occurred while executing the TCB tree. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8817 8817 An internal error occurred while fetching from the TCB tree. Cause Effect This is an internal error. 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 8824 8824 The input module_id does not have a module name. Cause A module name was not passed into the module ID structure that was passed in. Effect The operation fails. Recovery Ensure that a module name is passed into the module ID structure. SQL 8826 8826 The module could not be added.
SQL 8831 8831 Either no current context or the module to which the statement belongs is not added to the current context. Cause Effect This is an internal error. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8832 8832 Transaction has not been started. Cause Effect A transaction has not been started. The operation fails.
SQL 8837 8837 Authorization failure: Error number1 with status number2 was returned by proc-call. number1 number2 proc-call Cause is the file-system error returned by proc-call. is the status code returned by proc-call. is the name of the file-system procedure call returning the error. The value of the user ID passed in is not valid. Effect The operation fails. Recovery Ensure that the user ID of the form group id | name, user id | user name, password is valid and exists on the current system.
SQL 8843 8843 Trying to retrieve an item, value, that is out of range. value is the entry number of the item. Cause The item number of the requested descriptor item or the item number of the descriptor item being set is out of range. The value must be less than the maximum number of occurrences specified when the descriptor area was allocated. Effect The operation fails. Recovery Do not attempt recovery.
SQL 8853 8853 Specified attribute definition is not valid. Cause Effect You specified an invalid attribute definition. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8854 8854 Specified attribute value is not valid. Cause Effect You specified an invalid attribute value. The operation fails. Recovery Do not attempt recovery.
name is the file name. Cause The module file name has an obsolete module header. Effect The operation fails. Recovery Rebuild the module file and resubmit. SQL 8861 8861 Module file name has an obsolete descriptor location table header. name is the file name. Cause The module file name has an obsolete table header. Effect The operation fails. Recovery Rebuild the module file and resubmit. SQL 8862 8862 Module file name has an obsolete descriptor location table entry. name is the file name.
Recovery Rebuild the module file and resubmit. SQL 8867 8867 An error while reading from file name. name is the file name. Cause The HP Neoview database software encountered an error while reading the module file name. Effect Recovery The operation fails. Rebuild the module file and resubmit. SQL 8868 8868 SQL cannot create a new context when current transaction is implicitly started by SQL. Cause The application did not start its own transaction.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8873 8873 The current statement is already associated with a QFO. Cause Effect An existing quasi file object (QFO) is already associated with the current statement. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Effect The corresponding SQL request is rejected. Recovery Either change the definition of the stored procedure to allow SQL access, or determine why the stored procedure contains HP Neoview database statements that might be called while the stored procedure is executing. SQL 8888 8888 The underlying insert, update, or delete operation of cursor cursor-name is still in progress. Since the cursor is being closed before the operation is complete, all affected rows will be rolled back.
Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8894 8894 Argument argument-name of CLI function function-name is reserved for future use and must be set to string when calling the function. Cause A value that was passed into an HP Neoview database CLI function containing a reserved parameter was not the value expected by the database software.
Cause The HP Neoview database UDR server generated an improperly formatted identifier when the Neoview database software was executing a stored procedure. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8904 8904 SQL/MX did not receive a reply from MXUDR, possibly caused by internal errors while executing user-defined routines.
SQL 8912 8912 The request to allocate a stored procedure result set failed. An unexpected internal error was encountered. Cause An internal error was detected within the HP Neoview SQL executor during allocation of a stored procedure result set. Effect Recovery The operation fails. None. Contact the GMCSC and report this condition. SQL 8913 8913 The PREPARE operation is not allowed on a stored procedure result set.
Cause A call-level interface (CLI) application specified an invalid index in a request to bind a stored procedure result set to a specific result set index. A valid index range can be from 1 to the maximum number of result sets that can be returned from the CALL statement. Effect Recovery The operation fails. None. Contact the GMCSC and report this condition. SQL 8917 8917 The request to allocate a stored procedure result set at position index failed because a result set at positionindex already exists.
Cause The DISPLAY STATISTICS FOR CPU or PID or QID command timed out because the HP Neoview database software is unable to obtain the statistics from runtime statistics (RTS) components within the specified time-out period. Effect The runtime statistics information is not retrieved, and the command fails. Recovery Try increasing the time-out period by using SET SESSION DEFAULT RTS_TIMEOUT 'n' command. If problem persists, check if all RTS processes are running or if the system is very busy.
10 UPDATE STATISTICS Messages (9200 Through 9217) SQL 9200 9200 UPDATE STATISTICS encountered an error from statement name. Cause name. UPDATE STATISTICS encountered an error from the HP Neoview database statement Effect The operation fails. Recovery Other error messages will appear with this one, depending on what statement caused the error. Use them to diagnose and correct the problem. SQL 9201 9201 Unable to DROP object name.
Cause You attempted to run UPDATE STATISTICS against an object that is not supported. Effect The HP Neoview database software is unable to continue processing. Recovery Correct the syntax and resubmit. SQL 9206 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. Cause The HP Neoview database software could not perform an UPDATE STATISTICS statement because you are not authorized to perform this operation against this table.
Recovery Provide SET ROWCOUNT option and resubmit for more accurate statistics. SQL 9213 9213 If you intend to update histogram statistics for columns, you must specify a column list in the statement. Cause Effect Recovery You attempted to perform UPDATE STATISTICS and did not specify a column list. Processing continues without interruption. Correct your syntax to specify the column list and resubmit. SQL 9214 9214 Object name could not be created.
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 205) “Scratch File I/O Messages (10101–10199)” (page 209) 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 number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number. The query operator was unable to 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 number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number. The query operator 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 number Cause Effect is the HP Neoview query operator that encountered the error; for example: merge join. is a Neoview platform internal procedure-error number. An invocation of 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 11014 11014 A BEFORE trigger allows only SIGNAL, SET and CALL statements. Cause You attempted to create a BEFORE trigger with a trigger action other than SIGNAL, SET, or CALL. Consider that the dependent descriptor might be for a trigger. Effect The operation fails. Recovery If SET, SIGNAL, or CALL does not work, determine whether an AFTER trigger is more appropriate for your application.
SQL 11046 11046 Host variables and dynamic parameters are not allowed in the action of a trigger. Cause You attempted to create a trigger that includes host variables or dynamic parameters in its action. This can happen when you specify CALL statements or compound actions as triggered actions. Effect The operation fails, and the trigger is not created. Recovery Rewrite the trigger so that host variables and dynamic parameters do not appear in the trigger action. Then retry the operation.
SQL 11102 11102 MXUDR: Invalid UDR handle: string. Cause The HP Neoview database UDR server received a request for a stored procedure that is no longer present in the Neoview database UDR server context. Effect The request message is rejected, and the HP Neoview SQL statement fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 11103 11103 MXUDR: Invalid routine handle: string.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 11111 11111 MXUDR: Internal error: value. Cause Effect The HP Neoview database UDR server received an incorrectly formatted message. The request message is rejected, and the HP Neoview SQL statement fails. Recovery Do not attempt recovery.
SQL 11212 11212 Specified signature is invalid. Reason: Java signature size is bigger than the maximum supported size. Cause In a CREATE PROCEDURE statement, the Java signature size exceeded the maximum supported size. The currently supported maximum Java signature size is 8192 characters. Possible causes include an incorrect signature specified in the EXTERNAL NAME clause or a very large number of parameters in the Java method. Effect The operation fails.
13 Materialized Views Messages (12000 Through 12329) SQL 12001 12001 Creation failed. The materialized view cannot be incrementally maintained. 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 12006 12006 Incremental materialized views must have a simple query.
Recovery ON STATEMENT MVs and RECOMPUTE MVs do not have the IGNORE CHANGES clause, so these materialized views cannot be altered. SQL 12014 12014 Can not initialize; locking of name failed. name is a table used by a materialized view being initialized. Cause A table used by the materialized view cannot be locked, possibly because it is being used by other applications. Effect The materialized view cannot be initialized. Recovery Resubmit the create statement. If the issue persists, contact the GMCSC.
SQL 12029 12029 An attribute reserved for materialized views cannot be used for table creation. Cause views. In creating a table, you specified an attribute that is supported only for materialized Effect The creation of the table fails. Recovery Correct the syntax and resubmit. 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 Remove the attribute from the materialized view definition. SQL 12048 12048 ATTRIBUTE LOCK LENGTH not supported for materialized views. Cause Effect The LOCK LENGTH attribute is not supported for materialized views. The creation of the materialized view fails. Recovery Remove the attribute from the materialized view definition. SQL 12050 12050 ATTRIBUTE AUDIT not supported for materialized views.
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 12092 12092 Group by columns cannot exceed 255 characters. Cause The total size of all the materialized view Group By columns exceeds 255 characters. Effect The creation of the materialized view fails.
Effect This is an informational message. The materialized view is created successfully. Recovery None, but you can drop and recreate the materialized view with the recommended STORE BY clause to improve refresh performance. SQL 12110 12110 The materialized view mv-name and its dependents were dropped due to insufficient privileges. mv-name is the name of the dropped materialized view. Cause Privileges on the materialized view base table were revoked from the materialized view owner.
Cause You specified a name of a materialized view that does not exist. Effect The operation failed. Recovery Correct the syntax and resubmit. SQL 12204 12204 Materialized view or group do not exist. Cause You specified a name of a materialized view or MVGroup that do not exist. Effect The operation failed. Recovery Correct the syntax and resubmit. SQL 12205 12205 Group mvgroup not empty. Must be empty before drop. mvgroup Cause is an MVGroup. An MVGroup must be empty in order to drop it.
SQL 12318 12318 FIRST/ANY is not allowed in query expression of a materialized view. Cause You specified FIRST or ANY in a query expression of a materialized view. Effect The creation of the materialized view fails. Recovery Correct the syntax and resubmit. SQL 12320 12320 Creation failed. Materialized views on views are not supported. The materialized view cannot be incrementally maintained. Cause You attempted to create a materialized view on a view. This operation is not allowed.
SQL 12325 12325 Creation failed. The statement includes a HAVING clause. The materialized view cannot be incrementally maintained. Cause Effect Your CREATE MV statement includes the HAVING clause. The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12326 12326 Creation failed. Cross joins without equal join predicates are not supported. The materialized view cannot be incrementally maintained.
14 Messages Generated by the Message System (16000 Through 16999) SQL 16001 16001 The error number err-num is not used in SQL/MX. Cause Internal error. Effect The Neoview software is unable to return or display a message with the specified number. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
15 Internal Stored Procedures Messages (19000 Through 19999) SQL 19000 19000 An internal error occurred in internal stored procedure processing. Cause Effect Internal error. The HP Neoview database software is unable to process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 19001 19001 An error was found in field description of internal stored procedure.
SQL 19017 19017 The format of input value 'value' is invalid for input type input-type. value input-type is a user-specified input value to a versioning built-in function. is a valid input type to one of the versioning built-in functions, VERSION_INFO or RELATEDNESS. Cause A request attempts to access a built-in function with an input value that is invalid for the specified input type. Effect The request fails. Recovery None.
16 Utility Messages (20000 Through 23099) SQL 20000 20000 File system error error number occurred during file open. error number Cause Effect is the HP Neoview platform file-system error. SQL was not able to open the requested file and received error error number. The operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463). 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 23 (page 463). 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 - file is not open. Cause The utility subsystem that performs fast data transfer received a request out of sequence. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20012 20012 Previous write in file failed. Cause The utility subsystem that performs fast data transfer could not successfully write data into the file.
Recovery For information about file-system errors, Chapter 23 (page 463). SQL 20017 20017 File system error error number occurred while getting partition length for file. error number is the HP Neoview platform file-system error. Cause SQL was not able to obtain the partition length (EOF) for the requested file and received error error number. Effect The operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463). SQL 20018 20018 An internal error occurred.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20021 20021 An internal error occurred - invalid column data type. Cause The utility subsystem that reads and maintains metadata encountered an unexpected data type for a column. Effect The operation fails. Recovery Do not attempt recovery.
Cause Effect SQL detected an internal error. SQL is unable to process the statement. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20037 20037 An invalid operation was specified - only ADD, DROP, and MOVE are supported. Cause Effect You specified a request that was not ADD, DROP, MOVE, or REUSE. The operation fails. Recovery Do not attempt recovery.
Cause The utility subsystem that reads and maintains metadata encountered an unexpected value for the sort order (ASC, DESC) on the primary key. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20046 20046 An internal error occurred - invalid size unit. Cause Effect The utility encountered an unexpected value for a size unit designation. The operation fails.
SQL 20052 20052 Transaction Management subsystem could not set the AutoCommit. Cause The utility subsystem that performs transaction management operations failed while trying to set the auto commit 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 20053 20053 Transaction Management subsystem could not begin a new 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 20068 20068 An internal error or exception occurred. Cause Effect SQL detected 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.
Recovery Specify TARGET PURGE for an existing target object and resubmit. SQL 20129 20129 Internal error occurred while performing DUP. Cause Effect An internal error occurred while performing the DUP 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 20133 20133 A user defined transaction has been started. DUP cannot be performed.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20149 20149 External indexes exist for this object-type. Since the source and target have the same catalog and schema, index-map must be specified. DUP cannot be performed. object-type Cause Effect is table or materialized view. You failed to define all the indexes of the index-map. The operation fails.
Cause Effect SQL detected an internal error. SQL is unable to process the statement. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20174 20174 An internal error occurred - A valid SQLNode is expected. Cause Effect SQL detected an internal error. The operation fails. Recovery Do not attempt recovery.
Recovery If the MODIFY operation is required, alter the table to audited, perform the MODIFY, and then alter the table back to nonaudited. SQL 20194 20194 Loading of index index-name failed. is the index to be populated as specified by the POPULATE INDEX command. index-name Cause Effect The index load failed because of some problem. The operation fails. Recovery If the problem was caused by a uniqueness violation, remove duplicate rows, and resubmit.
SQL 20213 20213 An internal error occurred during RECOVER. Cause Effect An unknown error occurred in an attempt to recover a utility operation. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20215 20215 Recovery failed for DDL_LOCKS name lock-name. Cause Effect The RECOVER operation could not be performed on lock lock-name. The operation fails.
SQL 20227 20227 The specified syntax is not supported for a hash or hash2 partitioned table or index. Cause You issued a request that is not supported for a hash or hash2 partitioned table or index. Hash partitioned objects support ADD, DROP, and MOVE requests. ADD and DROP requests must refer to the last partition and MOVE requests must be from one location to another. Hash2 partitioned objects support MOVE requests from location to location. Effect The operation fails.
SQL 20236 20236 Error returned from USER_GETINFO_ while converting username to userid, status: status, username: username. status username Cause ID. Effect is the status returned from USER_GETINFO_. is the user name being converted. An unexpected error was returned while converting the current user name to user 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 20259 20259 An internal PURGEDATA error occurred. Cause An unexpected error was detected. 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 20265 20265 Error error number returned during a call to SPI command command. error number command is the error returned from the SPI interface. is the SPI command being processed.
SQL 20272 20272 Non-audited tables are not supported. Cannot perform DUP. Cause Effect The DUP operation does not support nonaudited tables. The operation fails. Recovery Change the table to be audited using the FIXUP command, and resubmit. SQL 20273 20273 An internal error occurred. Cause Effect An unexpected error was returned while attempting to perform a SPI operation. The operation fails. Recovery Do not attempt recovery.
Recovery Wait until the other utility operation completes and retry the MODIFY request. If another utility operation is not running, perform a RECOVER operation on the table or index that owns the partition to clean up the failed operation. Then resubmit. SQL 20295 20295 The MODIFY request has completed successfully, but ORSERV failed. Please run FUP RELOAD manually to reclaim any free space on file-name-list.
Cause This is an internal error. The Synonym metadata is in an inconsistent state. It has a referenced object, but the object’s UID cannot be mapped. Effect The operation fails. Recovery Contact the GMCSC to check if the Synonym metadata is corrupt. SQL 20315 20315 Internal Error: failed to retrieve the referenced object name of the Synonym. Cause This is an internal error. The Synonym metadata is in an inconsistent state. It has a referenced object, but the object’s name cannot be mapped.
SQL 20340 20340 Indexes index-list on table table were successfully populated. index-list table Cause Effect is a comma separated list of indexes. is the name of the table. One or more indexes successfully populated. The operation partially succeeded. Recovery This is an informational message that indicates which indexes were successfully populated. This message appears with associated error 20339, which lists the indexes that failed to populate.
operation is the FIXUP operation. Cause The FIXUP operation failed because you either do not own that schema or do not have services ID privilege. Effect The operation fails. Recovery Log on as the services ID or make sure that you are the owner of that schema. Then resubmit. SQL 20355 20355 File name was not found. name is the HP Neoview platform file specified in the GOAWAY request. Cause The Neoview platform file that you specified does not exist. Possibly you misspelled the name.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20360 20360 Object object does not exist or the Object is not valid for the current operation. is the name of the table, index, view, or materialized view specified in the MXTOOL request. object Cause Effect You specified an incorrect table, index, view, or materialized view name. The operation fails.
SQL 20371 20371 The specified object object is not an SQL/MX table, view, or stored procedure. is the name specified in the MXTOOL command. object Cause Effect The object specified by the caller is not a table, view, or stored procedure. 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 20372 20372 The resource fork is not accessible.
Cause You tried to remove a Neoview platform object on a remote system. 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 20453 20453 Operation failed on name due to timeout. name is the name of the HP Neoview platform file requested to be removed. Cause The GOAWAY operation failed because the label has a lock on it, and the operation timed out after 90 seconds.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20461 20461 Option -df does not match label resource fork name. Use -rf to GOAWAY the label. resource fork name is the name of the resource fork. Cause The GOAWAY operation failed because you specified resource fork name with the -df option. Effect The operation fails. Recovery Do not attempt recovery.
Effect This refresh operation fails. Recovery After the concurrent operation that holds the DDL lock finishes, run refresh again. If no concurrent operations are running, the DDL lock has to be removed. In this situation, contact HP support to remove the lock. SQL 20523 20523 Object object-name cannot participate in refresh, there are multiple DDL locks associated with it. object-name Cause Effect is the name of an object participating in the REFRESH operation.
SQL 20547 20547 File system error error-number occurred while executing REPLY. error-number Cause text. Effect is an error originating from the file system. To determine the cause, look up the reported error number for its associated error The operation fails. Recovery For more information about file-system errors, see Chapter 23 (page 463). SQL 20548 20548 Process create error error-number occurred while creating a new process. error-number is the operating system error.
SQL 20559 20559 The current user does not have the select privilege for materialized view mv-name, and cannot populate its index(es). mv-name is a materialized view name. Cause You do not have the correct privileges to perform the requested operation. Probably, you attempted to perform a REFRESH operation on a materialized view that was not initialized. Effect The operation fails. Recovery Acquire the needed privileges and retry the refresh operation.
SQL 20578 20578 File system error error-number occurred during WRITEREADX on process process-name. error-number process-name Cause text. Effect is an error originating from the file system. is the name of the process. To determine the cause, look up the reported error number for its associated error The operation fails. Recovery For more information about file-system errors, see Chapter 23 (page 463). SQL 20579 20579 File system error error-number occurred during READX on process process-name.
Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20704 20704 A hardware trap occurred in audit fixup process process name. process name is the MXAUDSRV process name. Cause During an online partition management operation, the MXAUDSRV process encountered a hardware trap. Such traps might be caused by programming errors in the MXAUDSRV process itself. Effect The MODIFY operation fails.
Cause During an online partition management operation, the MXAUDSRV process encountered an error while processing 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 20709 20709 A TMF audit read error occurred during the audit fixup phase of the operation, in audit fixup process process name. process name is the MXAUDSRV process name.
SQL 20716 20716 The audit fixup phase of the operation was unable to retrieve information from the TMF subsystem. Cause During an online partition management operation, the MXAUDSRV process was not able to retrieve information from transaction services. 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.
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 20721 20721 An internal error (unknown exception class) occurred in audit fixup process process name. process name is the MXAUDSRV process name. Cause During an online partition management operation, the MXAUDSRV process encountered an internal error. Effect The MODIFY operation fails.
Recovery License the MXAUDSRV program file and retry the operation. SQL 20727 20727 An unexpected error code error code was returned by the audit fixup process process name. error code process name is the returned file system number. is the MXAUDSRV process name. Cause During an online partition management operation, the MXAUDSRV process reported an unknown error code. Effect The POPULATE INDEX or MODIFY operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463).
error number is the returned file-system number. Cause When processing COMMIT BEFORE or COMMIT AFTER clauses, the MODIFY command encountered an error number from the CONVERTTIMESTAMP HP Neoview platform procedure when converting the current time to local civil time. Effect The POPULATE INDEX or MODIFY operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463). SQL 20735 20735 An unexpected index transform error error-code occurred in audit fixup process process.
SQL 20754 20754 File system error (error) was returned while retrieving the object from the resource fork. is the error returned by the file system. is the information being retrieved, such as the ANSI name. error object Cause An unexpected error occurred while you were retrieving ANSI name information. Effect The operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463).
Effect None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20759 20759 Index name is unpopulated. name is the index that is not populated. Cause Effect The POPULATE INDEX command has not been run. None. This is an informational message. Recovery Do not attempt recovery.
SQL 20763 20763 The secondary extent size (size1) defined on the label does not match the value (size2) defined in the metadata for Guardian file (file). size1 size2 file is the secondary extent size defined on the label. is the secondary extent size defined in the metadata. is the name of the HP Neoview platform file. Cause An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Do not attempt recovery.
size1 size2 file is the key size stored in the file label. is the key size found in the metadata. is the name of the HP Neoview platform file. Cause An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
version2 file Cause Effect is the object schema version found in the metadata. is the name of the HP Neoview platform file. An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Cause Effect An inconsistency was found during the VERIFY operation. This is an informational message. VERIFY found a problem that needs attention. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20777 20777 The constraint map is missing from the resource fork for Guardian file (file). file Cause Effect is the name of the HP Neoview platform file.
SQL 20781 20781 The index map array is missing from the resource fork for Guardian file (file). file Cause Effect is the name of the HP Neoview platform file. An inconsistency was found during the VERIFY operation. None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20782 20782 The index information is missing from the metadata for index (name).
Cause An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20786 20786 The partition map is missing from the resource fork for Guardian file (file). file is the name of the HP Neoview platform file. Cause Effect An inconsistency was found during the VERIFY operation. None.
is the partition name defined in the resource fork. is the partition name defined in the metadata. is the file being verified. rname mname file Cause An inconsistency was found between the partition name stored in the resource fork and the partition name found in the metadata. Effect None. This is an informational message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Cause Effect You attempted to verify a Neoview platform file with an unsupported object type. 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 20797 20797 The partition list for index (name) found in the index map array for table (table) does not match the partition information stored in the metadata. is the name of the index in the index map array being verified.
Cause VERIFY compared flag values in the file label and the metadata, and discovered that the information does not match. Effect The object's data might be misinterpreted. Recovery Run MXTOOL FIXUP on the object. SQL 20806 20806 The problem-name flag is set for Guardian file file-name. problem-name file-name Cause is the name of the problem reported. is the HP Neoview platform file name. VERIFY found that the file label reported the indicated problem.
Recovery Contact the GMCSC. SQL 20818 20818 The refreshed_at defined on the label does not match the refreshed_at defined in the metadata for Guardian file (file). file is the HP Neoview platform file being verified. Cause An inconsistency was found during the VERIFY operation. Effect This is an informational message. VERIFY found a problem that needs attention. Recovery Contact the GMCSC. SQL 20821 20821 Constraint constraint is disabled. constraint Cause is the name of the constraint.
file-name is the full name of the HP Neoview database object. Cause This message is displayed whenever FIXUP is used with the -rc option on a table or index with partitions on a remote node (Neoview segment). Effect The corrupt bit is reset only on the local segment. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
Cause The list-of-partitions option you specified is not support by PURGEDATA for a materialized view. Effect The operation fails. Recovery Remove the list-of-partitions option and resubmit. SQL 20993 20993 Materialized View name does not exist. name is the materialized view name. Cause The materialized view name specified by the caller is either not defined or not visible on the current system. Effect The operation fails. Recovery Specify a valid name and resubmit.
SQL 23008 23008 servername: Assertion failed. servername Cause Effect is the name of the server program that issued the error. Internal program ASSERT failed, indicating an invalid program state. 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 23011 23011 servername: An unexpected XML tag was found: xml_tag.
SQL 23015 23015 servername: DDL command could not be found in buffer: description. servername description is the name of the server program that issued the error. contains details about the missing information in the DDL buffer. Cause Expected DDL command not found in the XML input file. This might indicate a problem with mxexportddl XML file generation. Effect The operation fails. Recovery Determine the problem with the input file and resubmit.
SQL 23022 23022 Error occurred for partition file name when attempting to set the statistics metadata. name Cause Effect is the name of the partition in error. The program was unable to update the partition metadata. 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.
17 Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29999) The messages described in this section are: • • • “Versioning Messages (25000-25399)” (page 289) “Distribution Messages (25400-25499)” (page 304) “JDBC Driver Error Messages (29000-29999)” (page 308) Versioning Messages (25000-25399) SQL 25002 25002 A versioning internal error occurred: missing compatibility check. Cause This is a versioning internal error. Effect The operation fails.
MXV2 is the local node’s earliest supported MXV. Cause The remote node node has an MXV (MXV1) earlier than the local node’s earliest supported MXV (MXV2), which is not supported. Effect The operation fails. Recovery Upgrade the remote node to an MXV that is later than or equal to the local node’s earliest supported MXV. Or, conversely, downgrade the local node to an MXV that is earlier than or equal to the remote node’s MXV.
Effect The operation fails. Recovery Upgrade the affected schema to a version that is compatible with the MXV of the nodes that need to access the schema. SQL 25201 25201 Table or view object cannot be accessed because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2. object version1 node version2 is the name of the affected database object. is the schema version of that database object’s schema.
This message indicates a downgrade that has been performed without removing database objects of the later version. Effect The operation fails. The object (and all other objects in the affected schema) is inaccessible. Recovery Migrate the software on the affected node to a version that supports the database objects that are present on the node. SQL 25204 25204 Table or view object1 has schema version version1; this is incompatible with the version of the compiler that compiles the query.
• • The local system schema version is later than the MXV of a node that is involved in the affected query. Compilation of such a query requires a downrev compiler. There is a need to access the system schema on a remote uprev node, and the system schema version of that system schema is later than the current compiler version. Effect The operation fails. Recovery Downgrade the system schema on the affected node to a version that is compatible with the required compiler version, or upgrade the compiler.
schema version1 node version2 is the name of the schema referenced by a DDL or utility operation. is the schema version of schema. is the node where the operation is executed or the node where metadata for the schema resides. is the earliest supported schema version of node. Cause The affected DDL or utility operation references a database object in a schema with a schema version that is earlier than the earliest supported schema version of the node where the operation was executed.
Cause The accessing node runs a GA release of the HP Neoview database software and is incompatible with a system schema created by a non-GA release. Effect The operation fails. Recovery Upgrade or downgrade the accessing node to an HP Neoview database software release that is compatible with the affected system schema version. Or, conversely, correct the system schema and reinstalled the Neoview database software on the affected node.
SQL 25218 25218 Schema schema has schema version version1; node cannot access or represent schemas with versions higher than MXV1. schema version1 node MXV1 is a schema that is accessed by a DDL or utility operation. is the schema version of that schema. is the node that encounters the incompatibility or the node where metadata for the schema is stored. is the MXV of that node. Cause A DDL or utility operation attempted to access a schema with a version later than the local node’s MXV.
node version is the cluster segment name of an involved segment. is the oldest supported schema version of node. Cause The target version of an UPGRADE or DOWNGRADE operation is lower than the oldest supported schema version of one or more of the segments where an involved schema is visible. Effect The operation fails. Recovery (1) Use the VERSION_INFO built-in function to obtain the names and SQL/MX software versions (MXVs) of all segments where a schema is visible.
Recovery Use the CASCADE option. The GET NAMES OF RELATED CATALOGS command and the RELATEDNESS built-in function return the names of all catalogs related to a named catalog. SQL 25255 25255 The schema version of schema is version1; it cannot be upgraded to version2. schema version1 version2 is the schema name of a schema that is affected by an UPGRADE operation. is the schema version of schema before the UPGRADE operation. is the target version of the UPGRADE operation.
SQL 25260 25260 No UPGRADE or DOWNGRADE operation is in progress for catalog. There is nothing to recover. is the user-specified catalog of a RECOVER command. catalog Cause A RECOVER command was issued specifying a catalog name that was not specified as the target of an active UPGRADE or DOWNGRADE operation. Effect The RECOVER operation fails. Recovery Use the same specification on the RECOVER command as was originally used on the UPGRADE or DOWNGRADE command.
Cause An attempt was made to drop the definition schema, but user schemas of the same version exist in the catalog. Effect The operation fails. Recovery This is an internal error. Contact the GMCSC. SQL 25265 25265 An internal error occurred during operation: text. is the UPGRADE, DOWNGRADE, or RECOVER operation specified by the user. is an abbreviated reason for the internal error. operation text Cause Effect A programming error was detected internally. The operation fails.
Cause You attempted to load a module with a module version (version1) that is earlier than the executing node’s earliest supported plan version (version2). Effect The operation fails. Recovery Recompile the module with a supported version compiler. SQL 25301 25301 Module module has module version version1; the local node does not support module versions higher than version2. module version1 version2 is the name of the affected module. is the module version of the affected module.
SQL 25304 25304 A compiler of version version1 was automatically started on node to recompile the query. The current compiler version is version2. version1 node version2 is the version of the required compiler. is the node on which the compiler was started. is the version of the compiler that returns the message. NOTE: As of the ABU SPR, this message is no longer generated. Cause The query references one or more remote nodes with an MXV earlier than the current compiler’s current plan version.
is the MXV of the affected node. MXV1 Cause The affected node runs a non-GA release of the HP Neoview database software and is compatible only with modules generated by its own version Effect The operation fails. Recovery Compile the module with a compiler version that is compatible with the MXV. SQL 25310 25310 Module module has module version version1. The local SQL/MX software version (MXV) can execute modules with module version MXV1 only. module version1 MXV1 is the name of the affected module.
Cause The query affects one or more nodes with an MXV earlier than the current compiler version. Effect The operation fails. Recovery Explicitly use a compiler with a version in the specified interval. Distribution Messages (25400-25499) SQL 25401 25401 Catalog catalog has not been registered on node node. catalog node is the ANSI name of the target catalog. It must be visible on the local node. is a remote node where catalog visibility is required.
Cause You attempted to establish a relationship between catalog1 and catalog2, which have different visibility. Effect The operation fails. Recovery Correct the error and retry the operation. SQL 25405 25405 Catalog catalog cannot be created because location location is a remote node. catalog location is the ANSI name of the target catalog. is the location from a CREATE CATALOG operation.
Effect The operation fails. Recovery For information about file-system errors, see Chapter 23 (page 463). SQL 25421 25421 An automatic catalog reference for catalog already exists on node node. catalog node is the ANSI name of the target catalog. is a remote node where an automatic reference of the target catalog exists. Cause The target node of a REPLICATE SCHEMA operation already has an automatic reference for the specified schema catalog. Effect The operation fails. Recovery None.
Cause The target node of an UNREPLICATE SCHEMA operation holds the only automatic reference for the affected schema catalog. Effect The operation fails. Recovery Correct the error and resubmit. SQL 25426 25426 Volume volume could not be accessed. File system error number. is the name of a volume that is required, implicitly or explicitly, by the operation. The volume name is fully qualified (for example, \NODEX.$VOLY). is the file-system error that resulted from the attempt to access volume.
Recovery Correct the error and retry the operation. SQL 25430 25430 The system catalog cannot be the target of a REGISTER CATALOG or UNREGISTER CATALOG command. Cause A REGISTER CATALOG or UNREGISTER CATALOG operation was attempted for the system catalog. Effect The operation fails. Recovery None. SQL 25490 25490 DDB Debug Warning: text. text is explanatory text for debugging purposes. Cause A test condition was encountered by debug mode software. The explanatory text contains the details.
18 Rowsets Messages (30000 Through 30999) SQL 30002 30002 The given rowset size (num1) must be smaller or equal to the smallest dimension (num2) of the arrays composing the rowset. is the size of the rowset. is the smallest dimension of the rowset arrays. num1 num2 Cause arrays. Effect You specified a rowset size larger than the smallest dimension, num2, of the rowset The operation fails. Recovery Do not attempt recovery.
SQL 30009 30009 Trying to add more elements than maximum rowset size. Cause Effect The HP Neoview database software received an internal error from a rowset. The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 30010 30010 An internal error occurred. Rowset is corrupted. Cause Effect The HP Neoview database software received an internal error from a rowset.
Effect The rows that raised the error have not been inserted, and all other rows in the input rowsets have been inserted. Recovery Contact the GMCSC. SQL 30023 30023 Variable used to retrieve ROWSET_ROW_COUNT is either a scalar or an array that is smaller than the size of the rowset used in the previous statement. Cause The variable you used to retrieve ROWSET_ROW_COUNT is either a scalar or an array that is smaller than the size of the rowset used in the previous statement.
SQL 30027 30027 NOT ATOMIC INSERT is not supported on a table that is the subject table of BEFORE triggers. BEFORE trigger trigger-name has table table-name as its subject table. trigger-name table-name is the name of the BEFORE trigger. is the name of the subject table. Cause You attempted to use NOT ATOMIC inserts on a table that is the subject table of at least one BEFORE trigger. Effect The operation fails. Recovery Contact the GMCSC.
Cause You attempted to use NOT ATOMIC inserts on a table that is the subject table of a materialized view. Effect Compilation of the INSERT statement fails. Recovery Contact the GMCSC. SQL 30034 30034 NOT ATOMIC INSERT is not supported on a table that is the subject table of AFTER triggers. AFTER trigger trigger-name has table table-name as its subject table. trigger-name table-name is the name of the AFTER trigger. is the name of the subject table.
19 Neoview Data Warehouse Manager Messages The Data Warehouse Manager messages are: • • • • “Update Statistics Server (2101-2301)” (page 315) “Table Smarts Server (3101-3301)” (page 316) “Defrag Server (4101-4610)” (page 317) “Aging Server (5101-6206)” (page 319) Update Statistics Server (2101-2301) 2101 Environment variable NSMWEB_OPERATION_UID missing. Cause Failed to get the ENV variable NSMWEB_OPERATION_ID from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC.
2201 SQL prepare failed. Cause Recovery GMCSC. Failed to prepare an SQL statement. Analyze the SQL errors and warnings associated with this error. Contact the 2202 SQL execute failed. Cause Recovery GMCSC. Failed to execute an SQL statement. Analyze the SQL errors and warnings associated with this error. Contact the 2301 Pathsend Failed. Cause The Pathsend process failed during a call to the HP Neoview DB Admin scheduler framework. Recovery GMCSC.
Recovery Analyze the associated errors or warnings. Contact the GMCSC. 3205 Invalid Group mode encountered Cause An invalid Group mode was encountered in the input XML. Valid groups are any of the following: • • • • Large Medium Small Tiny Recovery Analyze the associated errors or warnings. Contact the GMCSC. 3301 XML root element name invalidated during DOM traversal. Cause Recovery An unexpected XML root element name was received. Analyze the associated errors or warnings. Contact the GMCSC.
4106 Stdin data stream is empty. Cause Received empty data stream over stdin from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 4201 Create pipe failed. Cause Recovery Failed to create pipes required for FUP service. Analyze the associated errors or warnings. Contact the GMCSC. 4202 Fork process failed. Cause Recovery Failed to fork a FUP service child process. Analyze the associated errors or warnings. Contact the GMCSC. 4203 Exec call failed.
4501 Create pipe failed. Cause Recovery Failed to create the pipes required for the Shell service. Analyze the associated errors or warnings. Contact the GMCSC. 4502 Fork process failed. Cause Recovery Failed to fork a Shell service child process. Analyze the associated errors or warnings. Contact the GMCSC. 4503 Exec call failed. Cause Recovery Failed during exec() call to get Shell service. Analyze the associated errors or warnings. Contact the GMCSC. 4504 Wait on child process failed.
Cause Failed to get the ENV variable NSMWEB_OPERATION_SESSIONID from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 5105 Environment variable NSMWEB_OPERATION_RECURRENCE missing. Cause Failed to get the ENV variable NSMWEB_OPERATION_RECURRENCE from the HP Neoview DB Admin scheduler framework. Recovery Contact the GMCSC. 5106 Environment variable DBM_DIR_NAME missing. Cause Recovery ENV variable DBM_DIR_NAME missing. Contact the GMCSC. 5107 Stdin data stream is empty.
5301 Pathsend Failed. Cause Received empty data stream over stdin from the HP Neoview DB Admin scheduler framework. Recovery Analyze accompanying errors and warnings. Contact the GMCSC. 5401 Invalid or nonexisting ansi table name. Cause Recovery Received invalid or nonexisting ANSI table name as input. Analyze accompanying errors and warnings. Contact the GMCSC. 5402 Guardian name could not be found for given ansi-name. Cause Failed to get the name for the input ANSI table name.
Recovery Analyze accompanying errors and warnings. Contact the GMCSC. 6203 SQL Allocate SQLDA failed. Cause Recovery Failed to allocate SQLDA. Analyze accompanying errors and warnings. Contact the GMCSC. 6204 SQL Describe using SQLDA failed. Cause Recovery Failed to describe using SQLDA. Analyze accompanying errors and warnings. Contact the GMCSC. 6205 SQL Execute failed for MTS Delete Statement 1. Cause Recovery Failed to execute MTS Delete Statement 1. Analyze accompanying errors and warnings.
20 Neoview Loader The Neoview Loader messages are organized into these categories: • • • • • • • • “Repository Library Messages on Neoview (10001-15025)” (page 323) “Distributor Messages (20001-20203)” (page 331) “Neoview Cmserver Messages (30001-32504)” (page 333) “Linux Cmserver Messages (35001-36013)” (page 342) “Repository Server Messages (40001-47001)” (page 347) “Gcmd Messages (50001-50097)” (page 351) “Neoview Gelserver Messages (60001-60774)” (page 363) “Linux Gelserver Messages” (page 374) Reposi
Cause Failed to insert task input/output attributes in the GEL_TASK_IO_ATTRIBUTE_INFO repository table. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 10008 Task updating failed. Cause Recovery Failed to update a task in the GEL_TASK_INFO repository table. Contact the GMCSC for analysis of accompanying error and warning messages. 10009 Deletion of task attribute failed. Cause table.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 10016 Failed while getting all server params. Cause Recovery Failed to get server parameters for a particular server from the repository table. Contact the GMCSC for analysis of accompanying error and warning messages. 10017 Task instance insertion failed. Cause table.
10024 Failure in getting task output attributes. Cause Failed to get task output attribute information from the GEL_TASK_ IO_ATTRIBUTE_INFO repository table. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 10025 Failure in getting count of the active processes for a task instance. Cause Failed to get information about a task from the GEL_TASK_ INSTANCE_STATS repository table. Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
10032 Failure while updating task instance status. Cause Failed to insert statistical information about a running task in the GEL_TASK_INSTANCE_STATS table. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 10033 Self-validation for last child process check failure. Cause Recovery Failed to validate the last active process. Contact the GMCSC for analysis of accompanying error and warning messages. 10034 Failure while deleting a task.
10040 Failure while getting all server names. Effect table. Recovery Failed to get all server names configured in the GEL_SYSTEM_CONFIG repository Contact the GMCSC for analysis of accompanying error and warning messages. 10041 Failure in Begin Work. Cause Recovery A failure occurred during a begin transaction operation. Contact the GMCSC for analysis of accompanying error and warning messages. 10042 Failure Rollback Work. Cause Recovery A failure occurred during a rollback transaction operation.
Cause The given source server name (-sn) or target server name (-gn) does not exist in the GEL_SYSTEM_CONFIG repository table. Recovery Check that the server names were spelled correctly (the names are case sensitive). If you are unable to determine the cause of the error, contact the GMCSC to check the server names in the GEL_SYSTEM_CONFIG repository table. 10049 Task Name does not exist. Cause Recovery An attempt was made to reference a task name that does not exist.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 10057 Failure while inserting the recovery information. Cause table. Recovery Error while attempting to insert into the GEL_TASK_INSTANCE_RCVY repository Contact the GMCSC for analysis of accompanying error and warning messages. 10058 Failure while deleting the recovery information. Cause table.
Cause table. Recovery Error while attempting to update the GEL_TASK_INSTANCE_RCVY repository Contact the GMCSC for analysis of accompanying error and warning messages. 10065 Failure while getting the input param value from the attribute_info table. Cause Error occurred on an attempt to access the extract input query from the repository. For more details, see the associated error text. Recovery Contact the GMCSC for further assistance. 10066 Failure while validating the extract query.
Cause Duplicate input options were encountered. Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure. The only option expected by this server is the path to the configuration file. 20003 Configuration file name has not been provided. Cause The input options did not provide the path to the configuration file name (distributor.config.xml). Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure.
20106 Failed to de-register one of the servers. Cause The server failed to de-register one of the services in the repository server (registration server). Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure and that the repository server is running. 20107 SERVERCLASS_SEND_ failed to communicate with server. Cause SERVERCLASS_SEND_ failed to communicate with the requested server. A detailed message is appended.
Recovery Retry the operation. If the problem persists, contact the GMCSC. 30004 First READUPDATEX failed on $RECEIVE. Cause Recovery A call to file system procedure READUPDATEX failed. Retry the operation. If the problem persists, contact the GMCSC. 30005 Call to FILE_GETINFO_ failed. Cause Recovery A call to file system procedure FILE_GETINFO_ failed. Retry the operation. If the problem persists, contact the GMCSC. 30006 Received unknown file system error.
Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure. The configuration for the Cmserver process must contain information for the environment variable named GEL_SERVER_PATH. 30502 Failed to find environment variable for Gelserver configuration file location. Cause Cmserver failed to find the environment variable for the Gelserver configuration file location (gelserver.config.xml) at startup time.
Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure. The configuration for the Cmserver process must contain information for the environment variable named GEL_MEDIUM_PRIORITY. 30508 Failed to find environment variable for Gelserver high priority value. Cause Cmserver failed to find the environment variable for the low priority value to be used for the Gelserver process. Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure.
Cause Cmserver failed to initialize an execution group for the relational target. The execution group is the module used by the Cmserver process to start the Gelserver processes in parallel. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. 30515 Failed to get the terminal path name. Cause Cmserver failed to get the terminal path name from itself. Recovery Retry the operation.
30522 Peer process failed to start Gelserver process. Cause A peer Cmserver process failed to start the Gelserver process on the system where the peer Cmserver process is running. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. 30523 Failed to get address and port number from Gelserver process. Cause Gelserver failed to provide its IP address and listener port to the Cmserver process. Recovery Retry the operation.
31003 Received error during select of list of active processes. Cause Cmserver failed to retrieve a list of processes running for a particular task. Recovery Retry the operation. If the problem persists, contact the GMCSC to check if the task name exists in the repository table GEL_TASK_INFO. If yes, have the GMCSC check the repository table GEL_TASK_INSTANCE_INFO for any instance with the status RUNNING for that particular task. 31004 Received error during select of task related information.
31010 Received error while selecting the max run-id. Cause Recovery Error while accessing the GEL_TASK_INSTANCE_INFO repository table. Contact the GMCSC center for further assistance. 31011 Received error while selecting row counts from stats table. Cause Recovery Error while accessing the GEL_TASK_INSTANCE_STATS repository table. Contact the GMCSC for analysis of accompanying error and warning messages. 31012 Received error while validating the input query.
Cause Cmserver failed to process the start task request because the SQL object name supplied during task configuration is not in ANSI format. Recovery Reconfigure the task using the overwrite flag option, and provide the name of the SQL object to be loaded in ANSI format. After that, reissue the start task command using Gcmd. 32001 Type of request not found. Cause Cmserver failed to determine the request type information in the request message received from the repository server.
Cause Cmserver failed to receive data from a peer Cmserver process. This error occurs when connectivity with a peer system is lost or the peer Cmserver process has stopped running. Recovery Check the network connectivity between the source Linux system and the HP Neoview platform. Check that the Cmserver process is running on the Linux Loader platform, and if not contact the system administrator to restart the Linux Cmserver process and then resubmit the request.
35006 Server is already running as a daemon process. Cause A copy of the Cmserver process is already running. Recovery No action is required because this is not an error condition. However, if you want to run a new copy of Cmserver, you must first stop the currently running copy of the Cmserver process. 35007 Failed to create a child process. Cause Cmserver failed to create a child process. Recovery See the Cmserver.log file for detailed error information.
Cause Cmserver was not able to start the Gelserver process. Recovery See the Cmserver.log file for detailed error information. Attempt to correct the problem and retry the operation. If the problem persists, contact the GMCSC. 35013 Failed to create a unnamed pipe. Cause Cmserver failed to create an unnamed pipe required for communicating with a child process (for example the Gelserver process). Recovery See the Cmserver.log file for detailed error information.
Cause Cmserver received a request with an unknown request type from a peer Cmserver process. This is a fatal error. Recovery See the Cmserver.log file for detailed error information. Attempt to correct the problem and retry the operation. If the problem persists, contact the GMCSC. 35020 Received error response for status update operation. Cause Cmserver received an error response when it attempted to deregister its information in the repository table. Recovery See the Cmserver.
• • The listener socket number specified for Cmserver in the gelserver.config.xml file is already in use by another program. The system has an unknown TCP/IP problem. Recovery See the Cmserver.log file for detailed error information. If the port is being used by another application then either shut down that application or change the listener port for the Cmserver process in the gelserver.config.xml configuration file. Retry the operation. If the problem persists, contact the GMCSC.
• • The system has an unknown TCP/IP problem. TCP/IP connectivity with the remote system during the send is lost. Recovery See the cmserver.log file for detailed error information. Retry the operation. If the problem persists, contact the GMCSC. 36010 Failed to receive data from repository server. Bytes received is less than or equal to 0. Cause Cmserver failed to receive data from a repository server on the remote system. The number of bytes received is less than or equal to 0 (zero).
40002 Failed to get catalog name. Cause A failure occurred while finding the catalog name. Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure. Check the environment for the GEL_CATALOG variable. 40003 Failed to get schema name. Cause A failure occurred while finding the schema name. Recovery Contact the GMCSC to check the configuration of the provisioning infrastructure. Check the environment for the GEL_SCHEMA variable.
40010 Received unknown operation type. Cause The server received an unknown operation type. Recovery Retry the operation. If the problem persists, contact the GMCSC to check error messages in the repserver.log file on the HP Neoview platform. 41001 Received an error during insert of server configuration. Cause A failure occurred while inserting a server configuration. Recovery Contact the GMCSC to check error and warning messages in the repserver.log file on the HP Neoview platform.
41007 Received an error during starting the task instance. Cause A failure occurred while starting a task instance. A second error message is issued with details about the specific cause of the failure. Recovery Correct the cause of the failure and resubmit the start task request. 41008 Received an error during stopping the task instance. Cause A failure occurred while stopping a task instance. A second error message is issued with details about the specific cause of the failure.
• • There is no instance of that task running. The user submitting the STOP_TASK request does not have permission to stop that task. Recovery Check the name of the task specified in the STOP_TASK request. If the task name is not correct, fix the task name and retry the STOP_TASK request. If the user does not have permission to stop the task, check with the local system administrator. 41015 Received error while fetching task instance id from recovery information.
Cause Missing request type parameter. Recovery Provide the request type. Valid values are CONFIG_TASK_LOAD, CONFIG_TASK_EXTRACT, START_TASK, and STOP_TASK. 50002 Task Name is missing Cause Recovery Missing task name parameter. Provide the task name. 50003 Task type is missing Cause Recovery Missing task type parameter. Provide the task type. 50004 Source system name is missing Cause Recovery Missing source system name parameter. Provide the source system name.
Recovery Provide the compression information. Valid values are Y or N. 50011 Error logging severity is missing Cause Missing error logging severity parameter. Recovery Provide the error logging severity. Valid values are ERROR, WARNING, INFO, and TRACE. 50012 Execution method is missing Cause Recovery Missing execution method parameter. Provide the missing execution method. Valid values are PARTITION or CPU. 50013 Output type is missing Cause Recovery Missing output type parameter.
50020 Transaction size is missing Cause Recovery Missing transaction size parameter. Provide the transaction size. 50021 Buffer size is missing Cause Recovery Missing buffer size parameter. Provide the buffer size. 50022 Format file is missing Cause Recovery Missing format file parameter. Provide the format file. 50023 Overwrite flag is missing Cause Recovery Missing overwrite flag parameter. Provide the overwrite flag. 50024 Input item is missing Cause Recovery Missing input item parameter.
50029 Error in validating task instance name Cause Recovery Task instance name validation failed. Verify the task instance name; maximum length is 32 characters. 50030 Error in validating source system Cause Recovery Source system validation failed. Verify the source system name; maximum length is 32 characters. 50031 Error in validating source server Cause Recovery Source server name validation failed. Verify the source server name; maximum length is 32 characters.
Recovery Verify the error-logging severity. Valid values are ERROR, WARNING, TRACE, DEBUG, and INFO. Check whether the error-logging severity default value is specified in gelserver.config.xml. 50038 Error in validating execution method Cause Execution method validation failed. Recovery Verify the execution method. Valid values are PARTITION and CPU. Check whether the execution method default value is specified in gelserver.config.xml.
Recovery Verify the input type. Valid values are TABLE, FILE, QUEUE, SAS, and PIPE. Check whether the input type default value is specified in gelserver.config.xml. 50046 Error in validating transaction size Cause Transaction size validation failed. Recovery Verify the transaction size; maximum size is less than 100000. Check whether the transaction size default value is specified in gelserver.config.xml. 50047 Error in validating buffer size Cause Buffer size validation failed.
Cause Recovery A DOM error occurred during parsing. Contact the GMCSC. 50055 Unexpected exception during parsing Cause Recovery An unexpected error occurred during parsing. Contact the GMCSC. 50058 Date format is missing. Cause The date format is missing. Effect Cannot process the request. Recovery Pass the date format in CONFIG_TASK_LOAD -dt option, or provide the default value in the gelserver.config.xml file and resubmit the CONFIG command. 50059 Date separator is missing.
50064 Error in validating field delimiter, value should be between 0x01 and 0x7F. Cause Recovery Invalid delimiter. Provide a valid delimiter and resubmit the command. 50065 Failed to create client socket, ERROR: nnn Cause There was a failure in the creation of the client socket. Recovery nnn is the error number returned by the socket call. For more information, see the Linux man page for socket. 50066 Failed to send data to Distributor server.
50071 QUEUE is required as Input Type for REAL time operations. Cause Effect Recovery Invalid Input Type for REAL time operations. Cannot process the request. Set the inputType (-it) to QUEUE if taskType (-tt) is REAL. 50072 QUEUE is Invalid Input Type for BATCH operations. Cause Effect Recovery Invalid Input Type for BATCH time operations. Cannot process the request. Set the inputType (-it) to FILE/PIPE if taskType (-tt) is BATCH. 50073 Error in validating Message Count Limit.
50079 Recovery flag can only be used with FILE as input type. Cause The recovery flag value (-rf) is specified when the input type is not FILE. Recovery Remove the recovery flag or change the input type to FILE and resubmit the config command. 50080 Mismatch between Gcmd version version-number and GEL version version-number on Loader. Cause A system version mismatch between the Loader and HP Neoview platforms.
50088 Right trim option is missing. Cause Recovery Right trim option is missing. Provide the right trim option (-tm) and resubmit the command. 50089 Concatenate output files option is missing. Cause Recovery Concatenate output files option is missing. Provide the concatenate output files option (-cf) and resubmit the command. 50090 Error in validating the partitioning table. Cause Invalid partitioning table option (-pt).
Recovery Correct the task type option and resubmit the command. 50097 Concatenate output files option is permitted only for 'FILE' output type. Cause The concatenate output files option was given for a 'PIPE' output type, which is not allowed. Recovery Correct the concatenate output files option and resubmit the command. Neoview Gelserver Messages (60001-60774) 60001 Required argument missing. One of the input option expects an argument, which is not provided.
60103 READUPDATE failed on $receive. Cause The server failed to perform a READUPDATE on $RECEIVE. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. 60104 Unable to get RECEIVEINFO_. Cause The server failed to perform FILE_ RECEIVEINFO_ to retrieve information about a message on $RECEIVE. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages.
Recovery Contact the GMCSC. 60110 Unable to insert status information in repository. Cause The server failed to insert server status information into the repository. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. One possible cause of the problem is that the security of the repository tables on the HP Neoview platform has not been set correctly. 60111 Unable to update status information in repository.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. One possible cause of the problem is that the security of the repository tables on the HP Neoview platform has not been set correctly. 60117 Failed to insert recovery record. Cause The server failed to insert recovery information into the GEL_TASK_INSTANCE_RCVY repository table. Underlying SQL error is appended.
60402 Required metadata could not be fetched. Column information unavailable. Cause The server was unable to find column information in the HP Neoview database metadata tables. Recovery Contact the GMCSC to check if the metadata tables are accessible and the user has permission to perform queries. 60403 Required metadata could not be fetched. Clustering key information unavailable. Cause The server was unable to find clustering key information in the HP Neoview database metadata tables.
• • • • The HP Neoview database catalog name of the specified table does not exist. The Neoview database schema name of the specified table does not exist. The user name or password is incorrect. An internal ODBC driver error occurred. Recovery Corrective action depends on the information in the detailed ODBC driver message. 60504 Failure in enabling/disabling auto-commit for connection. Cause The server failed to enable or disable AUTO_COMMIT for the HP ODBC driver.
60510 Failure in setting rowset size. Cause The server failed to set the rowset size. A detailed HP ODBC driver message is appended. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. 60511 Failure in setting binding type. Cause The server failed to set data binding type. A detailed HP ODBC driver message is appended. Recovery Retry the operation.
60517 Transaction could not be rolled back. Cause The server failed to rollback the transaction. A detailed HP ODBC driver message is appended. Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. 60518 Failure in retrieving row count. Cause The HP ODBC driver failed to retrieve the rows affected count. A detailed ODBC driver message is appended. Recovery Retry the operation.
Recovery Retry the operation. If the problem persists, contact the GMCSC to check the time-out value in the Gelserver configuration file on the HP Neoview platform, and possibly increase that value. 60602 Failed to read data. failure-details failure-details can be one of these: 1. Failed to receive or send data on socket. Timeout occurred. File System Error#: FS-error. Socket state at the time of failure: Socket-Connection-State. Socket-Connection-State can be one of these: a. b. c. 2.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. 60704 LoadServer completed with success. Cause Recovery The server successfully completed the task. This is an informational message only. No corrective action is needed. 60705 LoadServer completed with error(s). Cause The server encountered a problem during execution. Previous errors in the log provide details about the error. Recovery Corrective action depends on the previous errors in the log.
Recovery Check whether transaction services are function correctly. Contact the GMCSC for further diagnosis. 60772 Failed to end transaction. Cause The server failed to commit a user transaction. Errors from the underlying subsystem are appended. This error can appear because: • • Transaction services encountered problems. An internal software problem occurred. Recovery Check whether transaction services are function correctly. Contact the GMCSC for further diagnosis. 60773 Failed to abort transaction.
Linux Gelserver Messages The messages from the Linux gelserver are grouped into these three groups: NOTE: The messages from the gelserver process on the source system do not contain error numbers.
Common Messages From Linux Gelserver Master Thread Execution Started. Cause Recovery The server initialization completed successfully, and execution has started. This is an informational message only. No corrective action is needed. Reader DLL could not be loaded. Cause The server was unable to load the reader shared library. Recovery Ensure that your installation directory contains these files: libgelfilerdr.so, libgeljmsrdr.so for a load task or libgeltcpiprdr.so for an extract task.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Failed to initialize partition driver(s). Cause Various reasons can cause failure of the initialization of partition drivers. Previous errors in the log provide details about the error. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Failed to delete recovery file. Cause • • The gelserver failed to delete the recovery file.
Both files are in the load directory /opt/tandem/genus/gel/log/load. Execution completed with warnings. Bad records rejected on source. Cause The task completed with warnings—records were rejected at the source when the data was being read from either a file, name pipe, or JMS queue. Recovery This is an informational message only. No corrective action is needed. The rejected records are in a file with a name in this format: task_name.task_instance_name.input.
Master Thread, Load Task-Specific Messages SESSION PARAMETERS Cause This message displays the inputs provided for the task currently executing.
Recovery Check the task instance log for the specific error that caused the problem. Thread creation failure. [ERROR=error]. is the error returned by the thread library at the time of thread creation. error Cause Failed to create a thread for the target connection group initialization. This error occurs because of resource issues on the Linux system. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Waiting for initialization threads to complete.
File Reader Thread, Load Task-Specific Messages Error opening file [file-name]. Check if file exists and user has permission to read it. Cause Recovery The reader thread was unable to open an input data file for reading. Check that the file exists and that the user has read-access permission. More fields present in record than expected. Extra fields ignored. Cause Recovery The input data contains more fields than expected. The additional fields are discarded. This is an informational message only.
Record number Bad Row number is the number of the record in the input file. This field is omitted for a recovered task. is the record number in the “.input” bad file. Cause The input data contains fixed-width data that does not match the specifications of the format file. Recovery Check the format file, correct the input data if required, and retry the task. NULL input cannot be set for a NOT NULL column [bad-field-name].
JMS Reader Thread, Load Task-Specific Messages Error creating first pipe to Java service. "[Error=errno]" Cause This message indicates that either no more file descriptors are available for this process or the system has insufficient resources. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Error creating second pipe to Java service.
TCP/IP Writer Thread, Load Task-Specific Messages Invalid port for connection Cause An invalid (negative) port number was supplied by the gelserver on the Neoview platform. Recovery This is an internal error. Retry the load task. If the problem persists, contact the GMCSC for analysis of accompanying error and warning messages. Invalid connection parameters Cause An invalid port number was supplied by the gelserver on the Neoview platform. Recovery This is an internal error. Retry the load task.
error is the value of the errno variable returned by TCP/IP. Cause Failed to receive reply from a gelserver on the Neoview platform. Possibly: • • The gelserver process on the Neoview platform terminated before sending the reply. In this event, check the gelserver Neoview task instance log. Problems occurred in the network between the Neoview and Linux systems. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Control Message could not be sent to the loader.
field-name Cause Recovery is the name of the column. The refExp option was set in the format file for a nonnumeric field. Remove the refExp option for this field from the format file. Reflexive update cannot be applied to key field (key-field-name). key-field-name is the name of the indexed column. Cause The refExp option was set in the format file for a primary key field, and a primary key field cannot be changed. Recovery Remove the refExp option for this field from the format file.
Master Thread, Extract Task-Specific Messages SESSION PARAMETERS Cause This message displays the inputs provided for the task currently executing.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Failed to initialize transformation partition driver. Cause Various reasons can cause this failure. Previous errors in the log provide details about the error. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. Thread creation failure. [ERROR=error] error is the error returned by thread library at the time of thread creation.
Cause This message displays the task execution statistics. For example: PNo. Requested Applied Rejected Affected 0 6000 0 0 6000 1 6000 0 0 6000 2 6100 0 0 6100 3 6100 0 0 6100 4 6000 0 0 6000 Tot. 30200 0 0 30200 CTot. 30200 0 0 30200 Recovery 388 Neoview Loader This is an informational message only. No corrective action is needed.
TCP/IP Reader, Extract Task-Specific Messages Invalid port for connection. Cause An invalid (negative) port number was supplied by the gelserver on the Neoview platform. Recovery GMCSC. This is an internal error. Retry the load task. If the problem persists, contact the Invalid connection parameters. Cause Invalid connection parameters were supplied by the gelserver on the Neoview platform. Recovery GMCSC. This is an internal error. Retry the load task.
Cause Failed to receive the first data block from the gelserver on the Neoview platform. Possibly: • • The gelserver process on the Neoview platform terminated before sending the first data block. In this case, check the gelserver Neoview task instance log. Problems occurred in the network between the Neoview platform and the Linux system. The error number value indicates the exact cause of error. Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
Cause • • Failed to send message to the gelserver on the Neoview platform. Possibly: The gelserver process on the Neoview platform has already terminated. Problems occurred in the network between the Neoview platform and the Linux system. Recovery Contact the GMCSC for analysis of accompanying error and warning messages. ODBC/MX FastPath has been enabled. Cause Recovery The gelserver is configured to use the FastPath interface for the HP ODBC driver. This is an informational message only.
File Writer, Extract Task-Specific Messages file-name1 is renamed to file-name2 Cause The gelserver determines that the output file already exists and therefore renames the current output file. Recovery This is an informational message only. No corrective action is needed. Error opening file [file-name] for fstat. ERROR=errno Cause The gelserver writer thread is unable to open an output data file for writing.
File Writer Transformation, Extract Task-Specific Messages Error opening file [file-name]. Check if user has permission to create files in the directory. Cause The transformation thread was unable to open the output data file (as specified for the outputItem [-oi] argument in the extract request) for writing. Recovery Check that the file exists and that the user has write-access or create-access permission. Error opening file [file-name] for fstat.
21 Neoview Script Messages This section describes Neoview Script error messages. ERROR: SET command must have an option specified. Cause Effect You did not specify an option for the SET command. The SET command fails to execute. Recovery Retry the SET command with an appropriate option. For more information, see the Neoview Script Guide. ERROR: A syntax error occurred at or before: Cause Effect You used incorrect syntax in the Neoview Script interface command.
22 SQLSTATE Values Returned by the Neoview Database The HP Neoview database software returns SQLSTATE values that are defined in the ISO/ANSI SQL standard and implementation-defined SQLSTATE values. See Subclause 22, “Status Codes” in the ISO/ANSI SQL92 Standard “Database Language SQL.” SQLSTATE and SQLCODE Considerations • • • Using SQLSTATE causes performance overhead because of the representation of SQLSTATE as five characters.
Table 22-1 SQLSTATE Values Beginning 00000 398 SQLSTATE SQLCODE Error Text 00000 0 Successful completion. 01000 6008 Statistics for column name were not available; as a result, the access path chosen might not be the best possible. 01001 8106 The last row fetched by this cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT... of statements. 01004 8402 A string overflow occurred during the evaluation of a character expression.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0150Y 1034 The Neoview database software was not able to initialize. 0150Z 1035 Catalog catalog-name already exists 01510 1036 Only super ID can execute DROP SQL. 01511 1037 The Neoview database software is not installed on system node. 01512 1038 Not all catalogs have been dropped from the system. 01513 1039 The drop SQL statement could not be executed.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) 400 SQLSTATE SQLCODE Error Text 01521 1073 Only the super ID user can execute INITIALIZE SQL. 01523 1075 Catalog name contains at least one schema. The catalog must be empty. 01525 1077 Metadata table name does not contain information for view name. 01526 1078 The format of the specified location name name is invalid. 01527 1079 Unable to prepare the statement. 01528 1080 Duplicate references to column name in the create request.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0153A 1118 Cannot create object name in metadata schema. 0153B 1119 Cannot drop metadata object name. 0153C 1120 Attempting to change the audit flags for a table in an unsupported way. 0153D 1121 Attempting to perform a partition add, move, or drop on table name. Partition operations are not allowed on tables with vertical partitions, entry sequenced operations, and SYSKEY-only partitioned tables.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) 402 SQLSTATE SQLCODE Error Text 01544 1148 System-generated column name of base table name cannot appear in a referential integrity constraint definition. 01551 1181 Unable to drop object name (file error num). 01552 1182 Cannot instantiate constraint name, conflicting lock exists. 01553 1183 Cannot instantiate module name, conflicting lock exists. 01554 1184 Insufficient privilege on name.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0160H 2017 Unable to create server process name. No more processes (PCBs) available. 0160I 2018 Unable to create server process name. Library conflict. 0160J 2019 Unable to create server process name. Unable to allocate virtual memory. 0160K 2020 Unable to create server process name. Unlicensed privileged program. 0160L 2021 System error num in name from name.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) 404 SQLSTATE SQLCODE Error Text 0161V 2067 Descriptor name has already been defined in this module. The previous definition is being retained and this latest one ignored. 0161W 2068 A procedure body must be a SELECT, INSERT, UPDATE, DELETE, DECLARE CATALOG, DECLARE SCHEMA, or a static DECLARE CURSOR. 0161X 2069 A static cursor declaration might appear only in the body of a procedure. 0161Y 2070 Invalid statement type in this context.
Table 22-1 SQLSTATE Values Beginning 00000 (continued) SQLSTATE SQLCODE Error Text 0162X 2105 Unable to compile this query because of incompatible Control Query Shape (CQS) specifications. Suggestion: Inspect the CQS in effect. 0162Y 2106 Unable to compile this statement since it is too long. Suggestion: Break up large statements into smaller pieces. 0162Z 2107 Unable to compile this statement. Suggestion: Address the issue(s) raised in the reported warning(s).
Table 22-2 SQLSTATE Values Beginning 01700 (continued) 406 SQLSTATE SQLCODE Error Text 0170L 3021 Expected an unsigned number as the second operand within the parentheses, not value. 0170M 3022 The name operator is not yet supported. 0170N 3023 The COLLATE clause in a sort specification is not yet supported. 0170O 3024 The MATCH PARTIAL clause is not yet supported. 0170P 3025 The format of the subvolume name part in the specified location name name is invalid.
Table 22-2 SQLSTATE Values Beginning 01700 (continued) SQLSTATE SQLCODE Error Text 0171J 3055 Duplicate DELETE rules specified. 0171K 3056 Duplicate UPDATE rules specified. 0171L 3057 Invalid size value in the ALLOCATE clause. 0171M 3058 The BLOCKSIZE value must be 4096. 0171N 3059 Invalid size value in the MAXSIZE clause. 0171O 3060 Invalid percentage value in the DSLACK clause. 0171P 3061 The format of the specified location name name is invalid.
Table 22-2 SQLSTATE Values Beginning 01700 (continued) 408 SQLSTATE SQLCODE Error Text 0172G 3088 The ALLOCATE AND DEALLOCATE cannot coexist in the same ALTER TABLE statement. 0172H 3089 The [NO]ICOMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. 0172I 3090 Duplicate LOCKLENGTH clauses. 0172J 3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. 0172K 3092 Duplicate BLOCKSIZE clauses. 0172L 3093 Duplicate DCOMPRESS clauses.
Table 22-2 SQLSTATE Values Beginning 01700 (continued) SQLSTATE SQLCODE Error Text 0173E 3122 The format of the system name part in the specified location name name is invalid. Currently the system name part must be \NSK or /E/NSK. 0173F 3123 The format of the file name part in the specified location name name is invalid. The file name part must be eight characters long and end with the digits 00. 0173J 3127 Invalid character in identifier name. 0173K 3128 object name is a reserved word.
Table 22-2 SQLSTATE Values Beginning 01700 (continued) 410 SQLSTATE SQLCODE Error Text 0174H 3161 name was not declared in the procedure parameter list. 0174I 3162 Procedure parameter name was not used. 0174J 3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. 0174K 3164 Data type mismatch between output host variable and selected value. 0174L 3165 Min or max precision or exponent value exceeded, num.
Table 22-3 SQLSTATE Values Beginning 01800 SQLSTATE SQLCODE Error Text 01800 4000 Internal error in the query binder. 01801 4001 Column name is not found. Tables in scope: name. Default schema: name. 01802 4002 Column name is not found. Table name not exposed. Tables in scope: name. Default schema: name. 01803 4003 Column name is not a column in table name, or, after a NATURAL JOIN or JOIN USING, is no longer allowed to be specified with a table correlation name.
Table 22-3 SQLSTATE Values Beginning 01800 (continued) 412 SQLSTATE SQLCODE Error Text 0180W 4032 Column name is an unknown class, num. It is neither a system column nor a user column. 0180X 4033 Column name is a primary or clustering key column and cannot be updated. 0180Y 4034 The operation (namenamename) name is not allowed. 0180Z 4035 Type name cannot be cast to type type. 01810 4036 The source field of the EXTRACT function must be of DateTime or Interval type.
Table 22-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 0181V 4067 The operands of function name must be character data types. 0181W 4068 The operand of function name must contain an even number of characters. 0181X 4069 Column name uses an unsupported collation, name. 0181Y 4070 The operand of function name must be exact numeric. 0181Z 4071 The first operand of function name must be a datetime.
Table 22-3 SQLSTATE Values Beginning 01800 (continued) 414 SQLSTATE SQLCODE Error Text 0182Z 4107 Column name has no default value, so DEFAULT cannot be specified. 01830 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. 01831 4109 Sequence functions placed incorrectly: name. 01832 4110 The query contains sequence functions but no SEQUENCE BY clause: name. 01833 4111 The query contains a SEQUENCE BY clause but no sequence functions.
Table 22-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 0184G 4160 Intersection between embedded name expression and embedded name expression not supported. Tables in scope: name, name. 0184H 4161 Union between embedded name expression and embedded name expression not supported. Tables in scope: name, name. 0184I 4162 Groupby not supported for stream expression. Tables in scope: name. 0184J 4163 Groupby not supported for embedded name expression.
Table 22-3 SQLSTATE Values Beginning 01800 (continued) SQLSTATE SQLCODE Error Text 0185U 4210 Embedded UPDATE/DELETE statements are not supported within an IF statement. 0185W 4212 table name cannot be used to satisfy order requirement on the stream because it is partitioned. 0185X 4213 Use of rowsets in a predicate with embedded UPDATE/DELETE not supported. 0185Y 4214 The SET ON ROLLBACK clause is not allowed on a non-audited table. Table: name.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01K06 8006 The stream timed out, but the cursor is still open. 01K07 8007 The operation has been canceled. 01K08 8008 Catalog name name is invalid. 01K09 8009 Schema name name is invalid. 01K0A 8010 Default catalog name: name. Default schema name: name. 01K0B 8011 SELECT statement inside compound (BEGIN ... END) statement returns more than one row. 01K0C 8012 Encoding of CONTROL QUERY DEFAULTs: name.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) 418 SQLSTATE SQLCODE Error Text 01KBJ 8415 The provided DATE, TIME, or TIMESTAMP is not valid and cannot be converted. 01KBK 8416 A datetime expression evaluated to an invalid datetime value. 01KBL 8417 An error occurred during the evaluation of a USER function. 01KBM 8418 The USER function is not supported on this platform. 01KBN 8419 An arithmetic expression attempted a division by zero.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01KGX 8609 Waited rollback performed without starting a transaction. 01KGY 8610 Transaction subsystem name reported error num on a waited rollback transaction. 01KH0 8612 Transaction mode cannot be set if the transaction is already running. 01KH1 8613 SQL cannot commit or rollback a transaction that was started by application. 01KH2 8614 SQL cannot begin a transaction when multiple contexts exist.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) 420 SQLSTATE SQLCODE Error Text 01KN2 8830 There is no current context. 01KN3 8831 Either no current context or the module to which the statement belongs is not added to the current context. 01KN4 8832 Transaction has not been started. 01KN5 8833 The input parameter is an invalid SQL transaction command. 01KN6 8834 The SQL installation directory could not be found. Operating system error number.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01KO1 8865 Module file name has obsolete procedure location table header. 01KO2 8866 Module file name has obsolete procedure location table entry. 01KO3 8867 Error while reading from file name. 01KO4 8868 Unable to create context when current transaction is implicitly started by SQL.
Table 22-4 SQLSTATE Values Beginning 01I01 (continued) SQLSTATE SQLCODE Error Text 01L5O 9204 Invalid option option specified. Value must be range. 01L5P 9205 UPDATE STATISTICS for object name is not supported. 01L5Q 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. 01L5R 9207 You are not allowed to generate histogram statistics on an ISO88591 CHARACTER SET column which contains a null terminator character.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01M0M 10022 Sort Error: FILE_CREATE failed 01M0N 10023 Sort Error: FILE_OPEN_ failed 01M0O 10024 Sort Error: SetMode failed 01M0O 10024 Sort Error: SetMode failed 01M0Q 10026 Sort Error: AWAITIOX failed 01M0R 10027 Sort Error: FILE_GETINFOLIST failed 01M0S 10028 Sort Error: POSITION failed 01M0T 10029 Sort Error: FILE_GETINFO_ failed 01M18 10044 Sort Error: IO did not complete 01M1B 10047 Sort
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) 424 SQLSTATE SQLCODE Error Text 01N61 11217 Java execution: Data overflow occurred while retrieving data at parameter position parameter number. Value is truncated. 01N62 11218 A Java method completed with an uncaught Java exception. Details: string. 01N63 11219 A Java method completed with an uncaught java.sql.SQLException. Details: string. 01N64 11220 A Java method completed with an uncaught java.sql.SQLException with invalid SQLSTATE.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01P0L 13021 name is already defined. 01P0M 13022 Cursor name is already defined. 01P0N 13023 name is already defined as a dynamic cursor. 01P0O 13024 Cursor name was not declared. 01P0P 13025 Warning(s) near line num. 01P0Q 13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements. 01P0R 13027 Only one EXEC SQL MODULE statement is allowed.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) 426 SQLSTATE SQLCODE Error Text 01P1L 13057 End-of-file processing generated unexpected cursor status of num for cursor name. 01P1M 13058 Unable to open SQL CLI header file name. 01P1O 13060 Unable to open the listing file name. 01P1P 13061 Invalid NUMERIC precision specified near line num. 01P1Q 13062 Unsigned long long type not allowed near line num. 01P1R 13063 Identifier name not defined near line num.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01PE8 13512 Input file error while processing EXEC SQL. 01PE9 13513 The BIT data type is not implemented in the Neoview database software. 01PEA 13514 The CHARACTER SET attribute is not implemented in the Neoview database software. 01PEB 13515 Picture name is not valid for a host variable. 01PEC 13516 Unexpected end of input file encountered after line num.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) 428 SQLSTATE SQLCODE Error Text 01R0H 15017 Statement name not found. 01R0I 15018 Break was received. The last statement might be lost. 01R0J 15019 num values were supplied in the USING list while the statement contains num unnamed parameters. 01R0K 15020 The USING list must contain at least one parameter value. 01R0L 15021 The USING list cannot contain more than num parameter values.
Table 22-5 SQLSTATE Values Beginning 01M01 (continued) SQLSTATE SQLCODE Error Text 01U09 30009 Internal error. Trying to add more elements than maximum rowset size. 01U0A 30010 Internal error. Rowset is corrupted. 01U0B 30011 More than one INTO statement in the same query is not supported. 01U0C 30012 Rowset index name must be specified last in the derived column list of name. 01U0D 30013 Hostvar used to set input size of rowset has zero or negative value.
Table 22-6 SQLSTATE Values Beginning 07001 (continued) 430 SQLSTATE SQLCODE Error Text 07008 -8807 Trying to allocate more than num entries for a descriptor. 07008 -8893 The statement argument count does not match the descriptor entry count. 07009 -8829 Trying to set descriptor item for an entry that is either invalid or greater than the maximum entry count for that descriptor. 07009 -8843 Trying to retrieve an item, num, that is out of range.
Table 22-6 SQLSTATE Values Beginning 07001 (continued) SQLSTATE SQLCODE Error Text 0A000 -3080 The [NO]SERIALWRITES clause is not supported. 0A000 -3105 Currently only range, hash and system partitioning are supported. 0A000 -3119 The WITH LOCAL CHECK OPTION clause is not supported. 0A000 -3120 The CREATE ASSERTION statement is not yet supported. 0A000 -3121 Partitioned entry-sequenced tables are not yet supported. 0A000 -3130 UNSIGNED option is not supported for LARGEINT type.
Table 22-6 SQLSTATE Values Beginning 07001 (continued) 432 SQLSTATE SQLCODE Error Text 22011 -8403 The length argument of function SUBSTRING cannot be less than zero or greater than source string length. 22012 -4075 Division by zero in constant expression name. 22012 -8419 An arithmetic expression attempted a division by zero. 22015 -3044 Invalid interval num. 22019 -8409 The escape character argument of a LIKE predicate must be one character in length.
Table 22-6 SQLSTATE Values Beginning 07001 (continued) SQLSTATE SQLCODE Error Text 25000 -8819 Begin transaction failed while preparing the statement. 25000 -8820 Transaction commit failed while closing the statement. 25000 -8832 Transaction has not been started. 25000 -8833 The input parameter is an invalid SQL transaction command. 25000 -8841 User application committed or aborted a transaction started by SQL.
Table 22-7 SQLSTATE Values Beginning 42000 434 SQLSTATE SQLCODE Error Text 42000 -1000 A syntax error occurred. 42000 -3201 EXTERNAL PATH clause is required. 42000 -3202 PARAMETER STYLE clause is required. 42000 -3203 LANGUAGE clause is required. 42000 -3204 EXTERNAL NAME clause is badly formed. 42000 -3205 EXTERNAL NAME clause is required. 42000 -3206 The name for an object of this type must be fully qualified, or set NAMETYPE ANSI.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -2062 Static cursor name has already been defined in this module. The previous definition, as a dynamic cursor, is being retained and this latest one ignored. 42000 -2063 Dynamic cursor name has already been defined in this module. The previous definition, as a static cursor, is being retained and this latest one ignored. 42000 -2064 Dynamic cursor name has already been defined in this module.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) 436 SQLSTATE SQLCODE Error Text 42000 -3006 In a dynamic cursor declaration both the cursor and the statement must be named in the same way: both must be literals or both must be string host variable expressions. 42000 -3007 In an ALLOCATE CURSOR statement both the cursor and the statement must be named using string host variables. 42000 -3008 Precision of name UNSIGNED data type, value, cannot exceed 9.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -3056 Duplicate UPDATE rules specified. 42000 -3057 Invalid size value in the ALLOCATE clause. 42000 -3058 The BLOCKSIZE value must be 4096. 42000 -3059 Invalid size value in the MAXSIZE clause. 42000 -3060 Invalid percentage value in the DSLACK clause. 42000 -3061 The format of the specified location name name is invalid. 42000 -3062 Duplicate MAXSIZE clauses in the PARTITION clause.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) 438 SQLSTATE SQLCODE Error Text 42000 -3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. 42000 -3092 Duplicate BLOCKSIZE clauses. 42000 -3093 Duplicate DCOMPRESS clauses. 42000 -3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements. 42000 -3095 Duplicate [NO]ICOMPRESS clauses. 42000 -3096 Duplicate [NO]SERIALWRITES clauses.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -3135 Precision of float, value, cannot exceed 54. 42000 -3136 Only LEFT, RIGHT, and FULL OUTER JOIN are valid in {oj ...} 42000 -3138 A key-sequenced table with range partitioning requires a FIRST KEY clause. 42000 -3139 A range-partitioned index requires a FIRST KEY clause. 42000 -3142 INTO clause host variables are not allowed in a static cursor.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) 440 SQLSTATE SQLCODE Error Text 42000 -3187 Not supported: SET STREAM TIMEOUT per a specific stream. 42000 -3189 cannot set lock timeout on a view. 42000 -4001 Column name is not found. Tables in scope: name. Default schema: name. 42000 -4002 Column name is not found. Table name not exposed. Tables in scope: name. Default schema: name.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -4025 Error while preparing constraint name on table name. 42000 -4027 Table name is not insertable. 42000 -4028 Table name is not updateable. 42000 -4030 Column name is an invalid combination of datetime fields (num, num, num). 42000 -4031 Column name is an unknown data type, num. 42000 -4032 Column name is an unknown class, num. It is neither a system column nor a user column.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) 442 SQLSTATE SQLCODE Error Text 42000 -4063 The operands of function name must be comparable character data types (that is, of the same character set and collation). 42000 -4064 The operands of function name must be compatible character data types (that is, of the same character set). 42000 -4066 The operands of a UNION must be of equal degree. 42000 -4067 The operands of function name must be character data types.
Table 22-7 SQLSTATE Values Beginning 42000 (continued) SQLSTATE SQLCODE Error Text 42000 -4110 The query contains sequence functions but no SEQUENCE BY clause: name. 42000 -4111 The query contains a SEQUENCE BY clause but no sequence functions. 42000 -4112 Absolute and relative sampling cannot occur in the same BALANCE expression. 42000 -4113 The sample size for name Sampling must be num. 42000 -4114 An absolute sample size must have a scale of zero.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) 444 SQLSTATE SQLCODE Error Text 46007 -11213 Specified signature is invalid. Reason: A return type must not be specified. 46101 -11215 Java execution: Invalid null input value at parameter position value. 46103 -11205 Java class class-file-name was not found in external path path-name. HY011 -8855 Statement attribute cannot be set now. HY011 -8857 Statement attribute cannot be set now.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X0111 -1037 SQL is not installed on system name. X0112 -1038 All catalogs have not been dropped from the system. X0113 -1039 Unable to drop SQL. X0114 -1040 Cannot alter metadata table. X0115 -1041 The primary key has already been defined. X0116 -1042 All PRIMARY KEY or UNIQUE constraint columns must be NOT NULL. X0118 -1044 Unable to create constraint name.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) 446 SQLSTATE SQLCODE Error Text X0128 -1080 Duplicate references to column name in the create request. X0129 -1081 Loading of index name failed unexpectedly. X012A -1082 Validation for constraint name failed unexpectedly. X012B -1083 Validation for constraint name failed; incompatible data exists in table. X012C -1084 Invalid default value for column name. X012D -1085 The calculated key length is greater than 255 bytes.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X013K -1128 Invalid API request. Details: text. X013M -1130 The column requires a default value. X013O -1132 An added column cannot have both DEFAULT NULL and NOT NULL. X013P -1133 Only the super ID can perform this operation. X013Q -1134 Concurrent DDL operations are being performed on the given object. The current operation cannot be performed.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) 448 SQLSTATE SQLCODE Error Text X0201 -2001 Error or warning num occurred while opening or reading from DEFAULTS table name. Using name values. X0202 -2002 Internal error: cannot create MXCMP server. X0203 -2003 Internal error: cannot establish connection with MXCMP server. X0204 -2004 Internal error: error from MXCMP; cannot work on this query.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X021G -2052 Optimizer internal counters: namenamenamename. X021H -2053 ASSERTION FAILURE CAUGHT BY OPTIMIZER! Attempting to recover and produce a plan. X021N -2059 Warnings while reading values from DEFAULTS table name. X0221 -2073 Only the super ID user can compile system module name. X0222 -2074 The name name is reserved for future system modules.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) 450 SQLSTATE SQLCODE Error Text X034I -3162 Procedure parameter name was not used. X034J -3163 Host variable name appears more than once in the INTO list. Execution results will be undefined. X0352 -3182 Extra semicolon(;) in a compound statement. X0400 -4000 Internal error in the query binder. X0422 -4074 CONTROL QUERY successful. X042U -4102 The FIRST/ANY n syntax cannot be used with in an outermost SELECT statement.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X044W -4176 Join between stream expression and embedded name expression not supported. Tables in scope: name. X044X -4177 Update of name column name not permitted on rollback. X044Y -4178 Update of variable length column name not permitted on rollback. X044Z -4179 SEQUENCE BY not supported for stream expressions. X0450 -4180 Stream expression not supported for top level DELETE statement.
Table 22-8 SQLSTATE Values Beginning 44000 (continued) SQLSTATE SQLCODE Error Text X048J -4307 Rowset parameters are not allowed in a CALL statement. X048K -4308 Internal error: unsupported SQL data type value specified for a CALL statement parameter. X0500 -5000 Internal error in the query normalizer. X0600 -6000 Internal error in the query optimizer. X0602 -6002 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid values.
Table 22-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X08O4 -8868 Unable to create context when current transaction is implicitly started by SQL. X08O5 -8869 The specified file number is not a QFO, or the file number is not internally associated with a QFO object (CLI internal error). X08O6 -8870 The current statement is not associated with any QFO. X08O7 -8871 Nowait tag is not specified in the statement-id.
Table 22-9 SQLSTATE Values Beginning X0700 (continued) 454 SQLSTATE SQLCODE Error Text X08G3 -8579 Similarity check failed: name X08GP -8601 Error returned from file system while locking/unlocking. X08GQ -8602 The file system reported error num on a lock/unlock operation. X08JG -8700 An assertion failure or out-of-memory condition occurred during parallel execution. X08JQ -8710 Error num returned by Measure when attempting to update SQL counters.
Table 22-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X08NW -8860 Module file name has obsolete module header. X08NX -8861 Module file name has obsolete descriptor location table header. X08NY -8862 Module file name has obsolete descriptor location table entry. X08NZ -8863 Module file name has obsolete descriptor header. X08O0 -8864 Module file name has obsolete descriptor entry. X08O1 -8865 Module file name has obsolete procedure location table header.
Table 22-9 SQLSTATE Values Beginning X0700 (continued) 456 SQLSTATE SQLCODE Error Text X0A05 -10005 Sort Error: Unexpected error value.
Table 22-9 SQLSTATE Values Beginning X0700 (continued) SQLSTATE SQLCODE Error Text X0B5M -11202 Language Manager initialization failed. Details: Unable to initialize JVM. X0B5N -11203 The Language Manager failed to create its class loader, possibly due to corrupt LmClassLoader.class file. X0B5Q -11206 Java class class-file-name was not found in external path path-name. X0B5R -11207 Java class class-file-name failed to initialize.
Table 22-10 SQLSTATE Values Beginning X0D01 (continued) 458 SQLSTATE SQLCODE Error Text X0D0E -13014 Unable to open the output source file name. X0D0F -13015 Unable to open the module definition file name. X0D0G -13016 Descriptor name name conflicts with SQLC default name name. X0D0H -13017 Descriptor name is multiply defined. X0D0I -13018 Descriptor name name is invalid. X0D0J -13019 Statement name name uses name, a reserved name SQLC generates.
Table 22-10 SQLSTATE Values Beginning X0D01 (continued) SQLSTATE SQLCODE Error Text X0D1I -13054 Cursor name not fetched or closed. X0D1J -13055 Cursor name not opened or fetched. X0D1K -13056 Cursor name not used. X0D1L -13057 End-of-file processing generated unexpected cursor status of num for cursor name. X0D1M -13058 Unable to open SQL CLI header file name. X0D1O -13060 Unable to open the listing file name. X0D1P -13061 Invalid NUMERIC precision specified near line num.
Table 22-10 SQLSTATE Values Beginning X0D01 (continued) 460 SQLSTATE SQLCODE Error Text X0DE6 -13510 The SQL declare section might not contain COPY or REPLACE. X0DE7 -13511 End of input file while processing EXEC SQL. X0DE8 -13512 Input file error while processing EXEC SQL. X0DE9 -13513 The BIT data type is not implemented in SQL/MX. X0DEA -13514 The CHARACTER SET attribute is not implemented in SQL/MX. X0DEB -13515 Picture name is not valid for a host variable.
Table 22-10 SQLSTATE Values Beginning X0D01 (continued) SQLSTATE SQLCODE Error Text X0F0U -15030 The specified define already exists. Use alter or delete and add. X0F0V -15031 The specified define does not exist. X0F0W -15032 An error occurred while adding, altering or deleting this define. X0F0X -15033 Break was received. X0F0Y -15034 Invalid LOG file name.
Table 22-10 SQLSTATE Values Beginning X0D01 (continued) 462 SQLSTATE SQLCODE Error Text X0P8N -25311 System module module has a wrong module version. The expected module version is version1. The actual module version is version2. X0U08 -30008 Internal error. Rowset index is out of range. X0U09 -30009 Internal error. Trying to add more elements than maximum rowset size. X0U0A -30010 Internal error. Rowset is corrupted.
23 File-System Errors 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. The error text can sometimes help you troubleshoot a problem.
Error Number File-System Error Text 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 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. 0061 No more file opens are permitted on this disk or device; the system administrator issued a STOPOPENS command or the number of open files reached the maximum allowed. 0062 The disk was mounted but no mount order was given, so the file open is not permitted.
Error Number File-System Error Text 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. 0103 Disk not ready due to power failure. 0104 No response from printer.
Error Number File-System Error Text 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 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). 0215 I/O attempted to absent memory page (hardware path error). 0216 Memory breakpoint encountered during this I/O operation. 0217 Memory parity error during this I/O (hardware path error).
Error Number File-System Error Text 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. 0530 The program called WRITE^FILE for the receiving file before calling READ^FILE.
Error Number File-System Error Text 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. 0633 Operation is invalid because a performance measurement utility is running. 0634 A logical device number exceeded 16 bits.
Error Number File-System Error Text 1025 The supplied row or update value violates one of the constraints for the table. 1026 The selection expression on an SQL view has been violated. 1027 The Data Access Manager process encountered a bad SQL label or tree of labels. 1028 The Data Access Manager process accessed a label of an unexpected type during an OPEN or during an SQL label operation. 1029 A request to share an existing SQL open failed because no matching open was found.
Error Number File-System Error Text 1059 Unable to access a protection view whose underlying table does not exist or is inconsistent. 1060 SQL internal error. 1061 The cursor is no longer defined in the Data Access Manager process. 1062 SQL internal error. 1063 SQL internal error. 1064 The table cannot be dropped because protection views are still defined for the table. 1065 This error message has two possible causes: 1) Either an SQL internal error has occurred.
Error Number File-System Error Text 1093 The operation cannot be performed because the resulting row would exceed the RECLENGTH value defined for the relative table. 1094 The limit on the number of columns that can make up a key has been exceeded for indexes or key-sequenced tables. 1095 An invalid value has been supplied for the BLOCKSIZE attribute. 1096 The BLOCKSIZE value for this table is too small for the row length of the table.
Error Number File-System Error Text 3501 More control information was received than this dialect allows. 3502 Server does not have sufficient available storage for this request. 3503 Server does not support this dialect. 3504 Server does not support this request type. 3505 Server version is not current. 4001 Operation not permitted. Process does not have the appropriate privileges or permissions to perform the requested operation. 4002 No such file or directory.
Error Number File-System Error Text 4046 No record locks available. 4061 No data sent or received. 4099 Function not implemented. 4101 Operation would block. 4102 Operation now in progress. 4103 Operation already in progress. 4104 Socket operation on nonsocket. 4105 Destination address required. 4106 Message too long. 4107 Protocol wrong type for socket. 4108 Protocol not available. 4109 Protocol not supported. 4110 Socket type not supported.
Error Number File-System Error Text 4196 Invalid socket call. 4197 File type not supported. 4198 C file (code 180) not odd unstructured. 4199 Insufficient internal memory. 4200 Too many symbolic links during path name resolution. 4201 File-set catalog internal consistency error. 4202 Root file set is not mounted. 4203 POSIX not running or not installed. 4204 Illegal byte sequence.
