manualshive.com logo in svg

HP Neoview Messages, Manual

Share
Download
HP Neoview Messages Manual Download Page 114

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.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 3178

3178 One or more of the following external (host-language) data types

incorrectly appears within the SQL query or operation: name.

Cause

You specified an HP Neoview database software query or attempted to perform an

operation with an incorrect data type.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 3179

3179 Collation name1 is not defined on the character set name2.

name1

is the name of the collation.

name2

is the character set name.

Cause

You attempted to used a collation name that is not defined on the character set. A

valid collation name is required.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 3180

3180 STREAM statements are not allowed in compound statements.

Cause

You specified a compound statement that contains a STREAM statement, which is

not supported.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 3181

3181 Specified name is not a valid three part ANSI name.

Cause

You specified an invalid logical name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

114

Parser and Compilation Messages (3000 Through 3999)

Summary of Contents for Neoview Messages

Page 1: ...HP Neoview Messages Manual Volume 1 HP Part Number 61 1472 001 Published August 2010 Edition HP Neoview Release 2 5 ...

Page 2: ...f are trademarks of the Open Software Foundation Inc OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing performance or use of this mate...

Page 3: ... 13 Contacting Your Service Provider 14 2 Data Definition Language DDL Messages 1000 Through 1999 15 3 Neoview Compiler Messages 2000 Through 2999 67 4 Parser and Compilation Messages 3000 Through 3999 89 5 Binder and Compilation Messages 4000 Through 4999 131 6 Normalizer Messages 5000 Through 5999 171 7 Optimizer Messages 6000 Through 6999 173 8 Generator Messages 7000 Through 7999 179 9 Executo...

Page 4: ... 271 17 Authentication and User Management Messages 24000 Through 24999 333 18 Versioning Distribution and JDBC Messages 25000 Through 25499 and 29000 Through 29399 351 Versioning Messages 25000 25399 351 Distribution Messages 25400 25499 361 JDBC Driver Error Messages 29000 29399 366 19 Neoview Command Interface NCI Messages 29400 Through 29599 367 20 Rowsets Messages 30000 Through 30999 379 21 F...

Page 5: ... JDBC Messages ODBC messages are contained in the Neoview ODBC Drivers Manual JDBC messages are contained in the Neoview JDBC Type 4 Driver Programmer s Reference Additional JDBC messages appear in the README for HP Neoview Release 2 5 Document Organization Chapter 1 page 13 is an introduction to Neoview software message handling The remaining chapters list SQL messages or file system errors in nu...

Page 6: ... new and changed messages The chapters that have new or changed messages are listed together with the added or changed message numbers Messages Added or Changed Description Chapter page 1085 1143 1168 1176 1177 1178 1179 1194 1277 1299 1314 1315 1324 1325 1596 1597 1598 1599 1600 1601 Data Definition Language DDL Messages 1000 Through 1999 Chapter 2 page 15 4347 4348 4349 4381 4382 4390 4419 Binde...

Page 7: ...underline is used to indicate a hypertext link within text By clicking a passage of text with a blue underline you are taken to the location described For example Rowset errors are listed in Chapter 20 page 379 General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words Type th...

Page 8: ...ee spaces and is separated from the preceding line by a blank line This spacing distinguishes items in a continuation line from items in a vertical list of selections For example match value NOT LIKE pattern ESCAPE esc char expression Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual Bold Text Bold text in an example indic...

Page 9: ... not in decimal notation The notation precedes an octal number The B notation precedes a binary number The H notation precedes a hexadecimal number For example 005400 B101111 H2F P p register E e register Related Documentation This manual is part of the HP Neoview library which includes Neoview Customer Library The manuals in the Neoview customer library are listed here for your convenience Admini...

Page 10: ...Neoview Performance Analysis Tools Online Help Information about how to use the Neoview Performance Analysis Tools to analyze and troubleshoot query related issues on the Neoview data warehousing platform Neoview Performance Analysis Tools User Guide Information about using the Repository including descriptions of Repository views and guidelines for writing Neoview SQL queries against the views Ne...

Page 11: ...r messages Neoview Messages Manual Information about new features for the current release including where to download software and obtain documentation README for HP Neoview Release 2 5 Publishing History Publication Date Product Version Part Number March 2007 HP Neoview Release 2 0 543766 001 August 2007 HP Neoview Release 2 2 544563 001 April 2008 HP Neoview Release 2 3 544796 001 May 2009 HP Ne...

Page 12: ...12 ...

Page 13: ...ue without the sign In this manual you will find the following message information for ERROR 1000 SQL 1000 1000 A syntax error occurred Cause You specified a statement with incorrect syntax Effect The HP Neoview database software statement fails Recovery Correct the syntax and resubmit SQLSTATE and SQLCODE SQLSTATE and SQLCODE status codes are returned to indicate either that an SQL statement comp...

Page 14: ...ility with earlier versions of the American standard Tables in SQLSTATE Values in Volume 2 of this manual identify the equivalent SQLSTATE and SQLCODE values for Neoview database software warning and error messages Contacting Your Service Provider Some messages have no recovery information and you will be instructed to contact the Global Mission Critical Solution Center GMCSC 14 Message Handling ...

Page 15: ...d on the local segment Effect The operation fails Recovery Enter a valid catalog name or register the catalog on the segment indicated and resubmit SQL 1003 1003 Schema schema does not exist schema is the ANSI name of the affected schema Cause The specified schema does not exist Effect The operation fails Recovery Check that a schema named schema does exist and resubmit SQL 1004 1004 Object object...

Page 16: ...in a GRANT or REVOKE statement or the authorization ID in a CREATE SCHEMA statement does not represent a valid Neoview platform user Effect The operation fails Recovery Correct the user name and resubmit SQL 1009 1009 Column column name does not exist in the specified table column name is an SQL identifier Cause The table that is referenced does not have a column with this name Effect The operatio...

Page 17: ...first or use the CASCADE option see error 1025 that discusses RESTRICT CASCADE as it applies to drop SQL 1015 1015 Some of the specified privileges could not be revoked Cause You attempted to revoke a privilege that either does not exist or you do not have authority to revoke Effect The HP Neoview database did not revoke the privileges Recovery The user who granted the privileges must revoke them ...

Page 18: ...chema Cause You attempted to create a schema in a catalog that already contains a schema with that name Effect The operation fails Recovery If you did not use a fully qualified name check that the default generates the correct catalog name Retry the request specifying a schema that does not already exist SQL 1023 1023 Only services ID can name an authorization ID different from the current user na...

Page 19: ...ed to drop the schema containing the metadata tables for the catalog Effect No SQL objects are dropped Recovery Use DROP SCHEMA statements to drop all the user created schemas in the catalog Then use the DROP CATALOG statement to drop the catalog The schema definition schema name is dropped when you drop its catalog SQL 1028 1028 The schema must be empty It contains at least one object object name...

Page 20: ...a catalog using the name of an already existing catalog Effect The operation fails Recovery None if this is the desired catalog Otherwise correct the catalog name and resubmit SQL 1036 1036 Only services ID can execute DROP SQL Cause An attempt was made to drop SQL by a user who is not the services ID Effect The operation fails Recovery The services ID needs to issue the DROP SCHEMA statement SQL ...

Page 21: ...ecify NOT NULL on one or more columns that are included in a UNIQUE or PRIMARY KEY constraint Effect The operation fails Recovery Reissue the statement with NOT NULL specified for all columns that are in the PRIMARY KEY and UNIQUE constraints SQL 1043 1043 Constraint constraint name already exists constraint name is the name of a column constraint or table constraint Cause You assigned the same co...

Page 22: ...ndividual DROP statements before dropping the object itself or use the CASCADE clause on the DROP statement for the object SQL 1048 1048 The statement currently supports only RESTRICT drop behavior Cause Drop behavior CASCADE was specified on a DROP statement that supports only RESTRICT drop behavior Effect The operation fails Recovery Reissue the DROP statement specifying RESTRICT or omitting the...

Page 23: ... on volume name File system error error number volume name is the name of a volume error number is the file system error number Cause An attempt to create a file on volume volume name resulted in file system error error number Effect The operation fails Recovery For information about file system errors see Chapter 21 page 385 SQL 1058 1058 Lock lock name already exists lock name is the name of the...

Page 24: ...ffect The operation fails Recovery None SQL 1064 1064 Dropping metadata view tablename is not allowed tablename is the name of an HP Neoview database table Cause An attempt was made to drop a view that is a metadata object Metadata views and their creation are not currently supported so this error should not be encountered Effect The operation fails Recovery None SQL 1065 1065 Creating constraint ...

Page 25: ...on fails Recovery Apply the recovery action from the accompanying error message SQL 1072 1072 Unique constraint constraint name 1 is disabled so foreign key constraint constraint name 2 could not be created constraint name 1 is the name of the disabled constraint constraint name 2 is the name of the foreign key constraint Cause You created a referential constraint that references a unique constrai...

Page 26: ...d resubmit SQL 1079 1079 SQL MX was not able to prepare the statement Cause See the accompanying error message for the cause Effect The operation fails Recovery Apply the recovery of the accompanying error message SQL 1080 1080 The DDL request has duplicate references to column column name column name is the name of a column of a table Cause You attempted to create a table that has two columns wit...

Page 27: ...n column name column name is the specified column Cause An invalid default value was specified in the column definition for column name Effect Creation of the table or addition of the column fails Recovery Specify a valid default value for the column and resubmit SQL 1085 1085 The calculated key length is greater than value value Maximum key length Will be 255 or 2048 bytes depending on the type o...

Page 28: ... it is not of type object type object name is the ANSI name of the object stated in the DROP command object type is the type of object that was stated in the DROP command Cause A DROP TABLE specified an object that is not a base table or a DROP VIEW specified an object that is not a view or a DROP PROCEDURE specified an object that is not a procedure Effect The operation fails Recovery Reissue the...

Page 29: ...ble table name could not be selected table name is the ANSI name of the metadata table Cause For clarification see the accompanying error message Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 1 101 1101 Table table name could not be updated table name is the...

Page 30: ...s not allowed Effect The operation fails Recovery Correct the error and resubmit SQL 1 106 1106 The specified partition partition location of object table name does not exist partition location is the location of the specified partition table name is the name of the table Cause The location name partition location specified in the partition operation does not exist Effect The partition operation f...

Page 31: ... 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 1 1 12 1112 An index column list cannot contain only the system generated column SYSKEY Cause The column list specified in a CREATE INDEX statement consisted only of the system generated column SYSKEY Effect The...

Page 32: ... name is not allowed in metadata schema table name is the name of the object Cause You attempted to create an object in the metadata schema Effect The operation fails Recovery Specify a different schema and resubmit SQL 1 1 19 1119 Dropping metadata object table name is not allowed table name is the name of an HP Neoview database metadata table Cause You attempted to use the DROP TABLE statement t...

Page 33: ...ls Recovery Fix the statement and resubmit SQL 1 123 1123 Not all of the partition key values key for object object name could be processed Please verify that the correct key value data types were specified key is a list of the partition key values object name is the name of the object Cause You attempted to access a table using a first key value that contains an element that is not supported Effe...

Page 34: ...hould be DEFAULT NULL or NOT NULL and resubmit SQL 1 133 1133 Only super ID can perform this operation Cause You attempted to perform an operation that can be performed only by the super ID Effect The operation fails Recovery Log on as the super ID and then resubmit SQL 1 134 1134 A concurrent utility or DDL is being performed on object object name its parent or one of its dependencies That operat...

Page 35: ...re required Cause This is an internal error in the interface between utilities and the catalog manager 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 1 139 1139 System generated column column name of base table table name cannot appear in the search condition...

Page 36: ...me To display the data that violates the constraint please use the following DML statement statement text constraint name is the name of a column constraint or table constraint referencing table name is the table on which the constraint is being added referenced table name is the table specified in the FOREIGN KEY clause statement text is a query Cause You attempted to add a referential integrity ...

Page 37: ...bject required for the DDL statement issued Cause The type of the object specified in the command is inconsistent with the DDL command being used For example this occurs if DROP TABLE is used and the object you specify is an INDEX Effect The operation fails Recovery Check that the correct object name was specified and execute a statement that is consistent with that type of object SQL 1 147 1147 S...

Page 38: ...enabled without setting volume names through POS_LOCATIONS for table partitions to reside on location names are generated automatically However the HP Neoview database software could not generate the location names automatically and because the POS_RAISE_ERROR is not set the given table is created as a simple table without partitions as it would be if the POS feature was not enabled Effect The POS...

Page 39: ...ied an alter or drop of synonym name but a synonym of that name does not exist Effect The operation fails Recovery Correct the syntax so that the correct name is used SQL 1 160 1160 A mismatch between the NOT DROPPABLE PRIMARY KEY constraint and the STORE BY clause was detected When both clauses are specified the STORE BY key column list must be the same as or a prefix of the PRIMARY KEY column li...

Page 40: ...ect whose ownership is changing name is the name of the object authid is the target of the GIVE operation Cause An attempt was made to change the catalog owner by someone who does not have the authorization to change the owner Effect The GIVE operation fails Recovery None SQL 1 164 1164 An unexpected error was returned while processing the statement stmt Error returned is int stmt is a Neoview SQL...

Page 41: ...the identifier for the object uid2 is the identifier for the schema create time is the time the object was created role is the role that is trying to access the object lock mode provides details about the access requested Cause Object not found by the specified UID Effect The operation fails Recovery Contact the GMCSC to help in determining why the internal error occurred SQL 1 169 1169 Schema pri...

Page 42: ...fails Recovery Set MAX_TABLE_SIZE to be less than or equal to ABSOLUTE_MAX_TABLE_SIZE SQL 1 177 1177 Internal error trying to create an object with a qualified name type of name type This qualified name type is not supported name type is the object type being created Cause An internal error was encountered Effect The operation fails Recovery Contact HP support to analyze the failure SQL 1 178 1178...

Page 43: ... generate the Neoview platform locations SQL 1 181 1181 Label file name could not be dropped file error error file name is the name of the table index view or routine being dropped error is the returned file system error number Cause The object you attempted to drop resulted in file system error error Effect The DDL DROP operation fails Recovery See previous messages in this HP Neoview database so...

Page 44: ...of the column that has an error column data type is the data type of column name 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 1 18...

Page 45: ...upported Effect The HP Neoview database software is unable to complete the operation Recovery Specify a different data type SQL 1225 1225 Mixing EXECUTE privilege with other privileges is not allowed Cause EXECUTE and another privilege were specified in the same GRANT or REVOKE statement which is not allowed Effect The operation fails Recovery Use separate GRANT or REVOKE statements for EXECUTE an...

Page 46: ...nt SQL 1235 1235 An invalid combination of EXTENT sizes and MAXEXTENTS was specified for table or index table name Cause A CREATE or ALTER statement specified an invalid combination of EXTENT sizes and MAXEXTENTS Effect The operation fails Recovery Correct the error and retry the operation For information about EXTENT and MAXEXTENTS see the Neoview SQL Reference Manual SQL 1236 1236 The schema nam...

Page 47: ...ter set other than ISO88591 in the text of a constraint Effect The operation fails Recovery Specify only ISO88591 literals in constraints SQL 1243 1243 The hexadecimal form of string literals is not allowed in this context Cause You specified a hexadecimal literal in the text of the statement which is not allowed Effect The operation fails Recovery Do not specify hexadecimal numbers in this type o...

Page 48: ... used to recover from the UPGRADE operation failure Before attempting the UPGRADE operation again the failure of insert into log table name has to be corrected SQL 1250 1250 DROP cannot be performed on object object name because a utility operation operation type associated with DDL_LOCK lock name is currently running object name is the ANSI name of the object named in the DROP command operation t...

Page 49: ...le processing the UDR_JAVA_OPTIONS setting jvm startup options error number is the SQLCODE value jvm startup options is a set of Java Virtual Machine startup options specified in the application s UDR_JAVA_OPTIONS default setting Cause An unanticipated error occurred during a CREATE PROCEDURE operation Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery ope...

Page 50: ...atement specifying the valid privilege for the procedure or routine SQL 1267 1267 EXECUTE privilege is incompatible with this object type Cause You specified a privilege that is not supported for the object type in a GRANT statement Effect The operation fails Recovery Reissue the GRANT statement specifying the valid privilege for the object type SQL 1268 1268 Duplicate columns are not allowed in a...

Page 51: ...ery operations in response to an automatically generated dial out message about this condition SQL 1273 1273 The specified MAXEXTENTS value must be greater than the number of extents allocated Cause The value that you specified to change MAXEXTENTS is less than or equal to the allocated extents Effect The operation fails Recovery Use a MAXEXTENTS value greater than the allocated extents SQL 1274 1...

Page 52: ... response to an automatically generated dial out message about this condition Consider running the VERIFY operation on the named object to check for inconsistencies in the metadata with respect to the partitioning scheme SQL 1278 1278 The command cannot be executed because operation is in progress for all schemas in catalog catalog operation is a schema level operation UPGRADE or DOWNGRADE that us...

Page 53: ...olatile tables Cause A CREATE VOLATILE TABLE statement specifies the NOT DROPPABLE clause which is not allowed Effect The operation fails Recovery Correct the error and resubmit the statement SQL 1289 1289 The use of ALTER on definition schemas and metadata schemas is not permitted Cause An attempt was made to alter a definition schema or metadata schema Effect The operation fails Recovery None SQ...

Page 54: ...is specified in the referential definition and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is SYSTEM Effect The NO ACTION referential action has RESTRICT referential action semantics It is recorded as NO ACTION in the metadata table Recovery To alter the behavior of the NO ACTION referential action set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTR...

Page 55: ...ed by existing schemas 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 1307 1307 The schema location subvolume is reserved for SQL MX metadata subvolume is the HP Neoview platform subvolume name specified in the LOCATION clause of the CREATE SCHEMA command Cau...

Page 56: ...me of the object Cause The create privilege for the catalog has been disabled Effect The operation fails Recovery Contact HP services to reinstate the create operation SQL 1315 1315 Catalog name does not have an associated definition schema The ALTER CATALOG operation fails name is the name of the catalog Cause An ALTER CATALOG catalog DISABLE CREATE or ALTER ALL CATALOGS DISABLE CREATE operation ...

Page 57: ...a DDL command Effect The operation fails Recovery None SQL 1500 1500 The CATSYS CAT_REFERENCES system schema relationship for catalog catalog may be corrupt catalog is the ANSI name of the affected catalog Cause A row for catalog was found in the CATSYS system schema table but no corresponding row could be found in the CAT_REFERENCES system schema table Effect The operation fails Recovery Do not a...

Page 58: ... dial out message about this condition SQL 1504 1504 table has no OBJECTS entry in definition schema table is the fully qualified ANSI name of a table in definition schema definition schema is the fully qualified ANSI name of the affected definition schema Cause A row for table could not be found in the OBJECTS table in definition schema Effect The operation fails Recovery Do not attempt recovery ...

Page 59: ...s Cause Tables with an IDENTITY column are not partitioned using either the hash or hash2 partitioning scheme Effect The operation failed Recovery Partition using only the hash or hash2 scheme for tables with an IDENTITY column SQL 1514 1514 Cannot add an IDENTITY column using ALTER TABLE command Cause You tried to add an IDENTITY column by using the ALTER TABLE command Effect The operation failed...

Page 60: ...s not work with a volatile index Therefore the CREATE INDEX NO POPULATE syntax is not supported for volatile indexes Effect The operation fails and the volatile index is not created Recovery Remove the NO POPULATE clause from the CREATE INDEX statement and try recreating the index SQL 1570 1570 The MAXVALUE for the sequence generator must be greater than the MINVALUE for col name col name is the n...

Page 61: ...tion and less than or equal to the MAXVALUE sequence generator option and resubmit the statement SQL 1574 1574 The CYCLE option is currently not supported for col name col name is the name of the IDENTITY column Cause You specified the CYCLE option for the sequence generator Only the NO CYCLE option is currently supported Effect The statement fails Recovery Specify a NO CYCLE option and resubmit t...

Page 62: ...ator option to be altered for a column that is an IDENTITY column SQL 1591 1591 The MAXVALUE option for the col name must be greater than the current value of seq gen value col name is the name of the IDENTITY column seq gen value is the numeric value of the sequence generator Cause You specified a MAXVALUE option that is less than the current value of the sequence generator Effect The statement f...

Page 63: ...or failed Please see additional messages for details Cause The recalibration of the CURRENT_VALUE column in the internal sequence generator table failed Effect The statement fails to execute Recovery Review the additional messages provided with this error for the internal UPDATE statement failure The additional messages will help you determine why the update to the CURRENT_VALUE column failed SQL ...

Page 64: ...his is possible alter the internal sequence generator options and then resubmit the RECALIBRATE command If the user specified value fails resubmit the RECALIBRATE command using a value less than the maximum value that is causing the failure SQL 1599 1599 The recalibration value is greater or less than an option value recalibration value of the IDENTITY column column name for the table table name g...

Page 65: ...n the table Effect The statement fails to execute Recovery Resubmit the statement when the locking contention has cleared SQL 1601 1601 Recalibration of the GENERATED ALWAYS AS IDENTITY column column name for the table table name is not allowed with NO SELECT column name is the name of the IDENTITY column table name is the name of the table that contains the IDENTITY column Cause You specified the...

Page 66: ...66 ...

Page 67: ...pt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 2003 2003 Internal error cannot establish connection with MXCMP server Cause The HP Neoview database software was unable to establish a connection with the Neoview database compiler MXCMP server Effect The operation fails Recovery Do not attempt recovery HP su...

Page 68: ...ck or committed if that makes sense in the application before MXCMP can be restarted and proceed Cause An outstanding transaction must be resolved before the HP Neoview compiler can be restarted Effect The operation fails Recovery None SQL 2010 2010 Internal IPC error Cause The HP Neoview database software received an internal interprocess communication error Effect The operation fails Recovery Do...

Page 69: ...process name on segment because of the process control procedure error number it received on the program file Effect The operation fails Recovery Use the process control procedure error to diagnose and correct the problem SQL 2014 2014 Server process name could not be created on node Operating system error number on swap file name is the server process name number is the error number Cause The HP ...

Page 70: ...sponse to an automatically generated dial out message about this condition SQL 2018 2018 Server process name could not be created on node library conflict name is the server process name Cause The HP Neoview database software was unable to create server process name because of a library conflict The process you are trying to create has a different library than the one that is already running Effec...

Page 71: ... process name text is more information about the error Cause The HP Neoview database software received 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 2023 2023 Server process name could not be created process id name is the server process na...

Page 72: ...r process does not 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 2028 2028 OSS server process name could not be created on node insufficient resources name is the server process name Cause The HP Neoview database software was unable to create the OSS server process name because ...

Page 73: ...icating with server process name Effect The Neoview database process is not able to communicate with the server process Recovery Use the process control procedure error to diagnose and correct the problem SQL 2035 2035 process id Open of process name failed error number process id identifies the process name is the name of the server process number is the error number Cause The HP Neoview database...

Page 74: ... name or a valid option with an invalid value Effect The operation fails Recovery Correct the syntax and resubmit SQL 2052 2052 Optimizer internal counters value value value value Cause This error should appear only if you are running in debug mode Effect None Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message abo...

Page 75: ...Cause You specified an invalid value for the DEFAULTS attribute listed in the message Effect The operation fails Recovery Correct the syntax and resubmit SQL 2056 2056 The value must be a number in the range value Cause You specified a value outside of the allowed range value Effect The operation fails Recovery Enter a valid value and resubmit SQL 2057 2057 The value must be a multiple of value Ca...

Page 76: ...ective action is needed SQL 2062 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 name is the cursor name Cause You defined the static cursor name twice in this module Effect The HP Neoview database software uses the first dynamic cursor definition Recovery This is an informational message only...

Page 77: ...e The previous definition is being retained and this latest one ignored name is the descriptor name Cause You defined the descriptor name twice in this module Effect The HP Neoview database software uses the first definition Recovery Informational message only no corrective action is needed SQL 2068 2068 A procedure body must be a SELECT INSERT UPDATE DELETE DECLARE CATALOG DECLARE SCHEMA or a sta...

Page 78: ...ich is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 2073 2073 Only super ID user can compile system module name name is the name of the module Cause You attempted to compile a system module that can be compiled only by the super ID Effect The operation fails and is unable to compile the entire module correctly Recovery None Use a different name for your mod...

Page 79: ...rrupted or overwritten Effect The operation fails Recovery Recompile the module definition file using the HP Neoview compiler to create a valid module file SQL 2081 2081 Error number while opening file name for read number is the error number name is the name of the file Cause The HP Neoview database software received error number while opening file name for read Effect The Neoview database softwa...

Page 80: ...the name of the file Cause A compilation failed and for some reason HP Neoview database software was not able to purge the module file Effect The module file is not valid and should not be used Recovery Purge the file from the HP Neoview platform SQL 2090 2090 The command line argument for module name name1 is being ignored in favor of module name name2 in file name3 name1 name2 and name3 are modu...

Page 81: ...name2 and name3 are module file names Cause The HP Neoview database software expected to find the first module name1 but instead found the second module name2 in file name3 Effect Only the second module is compiled Recovery None SQL 2096 2096 A source file statement has already appeared in this module The previous source file is being retained and this latest one ignored Cause The HP Neoview compi...

Page 82: ...ess 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 2102 2102 This query could not be compiled with MINIMUM optimization level Suggestion Retry with MEDIUM optimization level Cause The HP Neoview database software was unable to compile this query using the MINIMUM optimizatio...

Page 83: ...s query because you used an incompatible CONTROL QUERY SHAPE specification Effect The Neoview database software is unable to process this query Recovery Correct the CONTROL QUERY SHAPE specification and resubmit SQL 2106 2106 This statement could not be compiled since it is too long Break up large statements into smaller pieces Cause The HP Neoview database software was unable to compile this quer...

Page 84: ...he from or to character set is always UCS2 to character set may be any of the supported character sets One of the from or to character set is always UCS2 Cause Not enough space was allocated to translate between the character sets Effect The operation fails Recovery Contact your HP service provider about this problem SQL 2200 2200 DEFAULTS attribute attribute is read only attribute is the DEFAULTS...

Page 85: ...ic back to the source file of the named module Correct offending source statements Retry preprocessing translating compiling and SQL compiling the application file SQL 2205 2205 A temporary filename could not be created Cause You invoked mxCompileUserModule on an application file that has many embedded module definitions The tool cannot create another temporary file name to hold the contents of an...

Page 86: ...g quote Cause You invoked mxCompileUserModule using a command line option allowing a delimited identifier but the delimited identifier has no closing quote Effect The operation fails Recovery Ensure that the delimited identifier has a closing quote and retry the command SQL 221 1 2211 Lexical error unknown symbol character Cause You invoked mxCompileUserModule on an application file possibly inten...

Page 87: ... but you specified an invalid regular identifier in the module name list Effect The operation fails Recovery Review the module name list syntax especially where an identifier is expected Verify that the list of module names is specified correctly Verify that regular identifiers used are not SQL reserved words and retry the command SQL 2220 2220 mxcmp path MXCMP environment variable does not exist ...

Page 88: ...233 Query involves remote node segment name that is currently down Compiler encountered a file system error error num It may produce a plan that is suboptimal or of incompatible version segment name is the name of the segment such as system data_volume data_subvolume on which the failure occurred error num is the file system error number Cause The segment name you specified is not available Effect...

Page 89: ... fewer parts Effect The operation fails Recovery Correct the syntax and resubmit SQL 3003 3003 Length or precision must be greater than zero Cause You defined length or precision as zero You must enter a value greater than zero Effect The operation fails Recovery Enter a value greater than zero and resubmit SQL 3004 3004 A delimited identifier must contain at least one nonblank character Cause You...

Page 90: ...or and statement with string host variables and resubmit SQL 3008 3008 Precision of type UNSIGNED data type value cannot exceed 9 Cause You specified a CREATE TABLE statement with a precision value greater than nine for the PRECISION field which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3009 3009 DROP ASSERTION statement is not yet supported Cause You...

Page 91: ...SQL 3014 3014 Precision of numeric value cannot exceed 18 Cause You defined a numeric item value with precision greater than 18 which is not supported Effect The operation fails Recovery Redefine the item with a precision value of 18 or less SQL 3015 3015 Scale value cannot exceed precision value Cause You defined a scale value with greater precision than the HP Neoview database software allows Ef...

Page 92: ...Replace the value with an unsigned number and resubmit SQL 3021 3021 An unsigned number was expected as the second operand within parentheses not value Cause You specified an unexpected value value The HP Neoview database software requires an unsigned number Effect The operation fails Recovery Replace the value with an unsigned number and resubmit SQL 3022 3022 The name operator is not yet support...

Page 93: ...part Cause You specified an invalid name name which must have only one name part Effect The HP Neoview database software could not prepare the statement Recovery Correct the name and resubmit SQL 3028 3028 Specifying a privilege column list in the INSERT clause is not yet supported Cause You attempted to specify a privilege column list in an INSERT clause which is not supported Effect The operatio...

Page 94: ...upported Cause You used the PARTITION clause in the ALTER TABLE statement which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3035 3035 The RENAME clause in the ALTER TABLE statement is not yet supported Cause You used the RENAME clause in the ALTER TABLE statement which is not supported Effect The operation fails Recovery Correct the syntax and resubmit ...

Page 95: ... for a numeric or decimal type with a scale greater than 9 Cause You specified UNSIGNED for a numeric or decimal type that has a scale greater than nine which is not supported Effect The operation fails Recovery Change the specification to SIGNED and resubmit SQL 3042 3042 UPSHIFT for a numeric type is not valid Cause You specified UPSHIFT for a numeric type which is not supported Effect The opera...

Page 96: ...fails Recovery Remove the parameters and resubmit SQL 3049 3049 Host variables such as name are not allowed in a dynamic compilation Cause You attempted to use host variables in dynamic compilation which is not supported Effect The operation fails Recovery Remove the host variables and resubmit SQL 3050 3050 The constraint must have the same catalog and schema as the specified table Cause You spec...

Page 97: ... appear only in PRIMARY KEY and NOT NULL constraint definitions Effect The operation fails Recovery Correct the syntax and resubmit SQL 3055 3055 Duplicate DELETE rules were specified Cause You defined duplicate DELETE rules Effect The operation fails Recovery Correct the syntax and resubmit SQL 3056 3056 Duplicate UPDATE rules were specified Cause You defined duplicate UPDATE rules Effect The ope...

Page 98: ...use Cause You specified duplicate EXTENT MAXEXTENTS clauses in the PARTITION clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3063 3063 Duplicate DSLACK clauses were specified in the PARTITION clause Cause You specified duplicate DSLACK clauses in the PARTITION clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3064 3064 Duplicate ISLACK cl...

Page 99: ...DIT clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3071 3071 Duplicate NO AUDITCOMPRESS clauses were specified Cause You specified duplicate NO AUDITCOMPRESS clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3072 3072 The attribute clause is not allowed in the ALTER object ATTRIBUTE S statement attribute is either...

Page 100: ...the ALTER INDEX ATTRIBUTE S statement Cause You specified an ALTER INDEX ATTRIBUTE S statement that includes the NO ICOMPRESS clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3078 3078 The LOCKLENGTH clause is not allowed in the ALTER INDEX ATTRIBUTE S statement Cause You specified an ALTER INDEX ATTRIBUTE S statement that includes the LOCKLENGT...

Page 101: ... the ALTER TABLE ATTRIBUTE S statement Cause You specified an ALTER TABLE ATTRIBUTE S statement that includes the BLOCKSIZE clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3085 3085 Duplicate NO BUFFERED clauses were specified Cause You specified duplicate NO BUFFERED clauses Effect The operation fails Recovery Correct the syntax and resubmit S...

Page 102: ...tatement with duplicate LOCKLENGTH clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3091 3091 The NO AUDIT clause is not allowed in the CREATE INDEX statements Cause You specified a CREATE INDEX statement with the NO AUDIT clause which is not supported Effect The HP Neoview database software ignores the CREATE INDEX statement Recovery Correct the syntax and resubmit ...

Page 103: ...a CREATE TABLE statement that includes the DEALLOCATE clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3098 3098 Duplicate LOCATION clauses were specified Cause You specified a statement with duplicate LOCATION clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3099 3099 Duplicate FILE ATTRIBUTE S clauses were specif...

Page 104: ...ntax and resubmit SQL 3105 3105 Only range hash hash2 and system partitioning are currently supported Cause You attempted to specify an invalid partitioning method Currently only range hash hash2 and system partitioning are supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3106 3106 Duplicate PRIMARY KEY clauses were specified Cause You specified a statement with du...

Page 105: ...which is not supported Effect The operation fails Recovery Correct the statement to include one of these clauses SQL 31 12 3112 The LIKE clause and PARTITION clause cannot coexist in the same statement Cause You specified a statement with both LIKE and PARTITION clauses which is not supported Effect The operation fails Recovery Correct the statement to include one of these clauses SQL 31 13 3113 E...

Page 106: ...g Cause You specified an identifier that is too long Effect The operation fails Recovery Shorten the identifier and resubmit SQL 31 19 3119 The WITH LOCAL CHECK OPTION clause is not supported Cause You attempted to create a constraint with the WITH LOCAL CHECK OPTION clause which is not supported Effect The operation fails Recovery Eliminate the WITH LOCAL CHECK OPTION clause and resubmit SQL 3120...

Page 107: ...d an identifier that is a reserved word You must put it between double quotes to use it as an identifier Effect The operation fails Recovery Enclose the identifier in double quotes or select another name that is not a reserved word SQL 3129 3129 Function name accepts exactly one operand name is the name of the function Cause You specified two operands for an aggregate function that accepts exactly...

Page 108: ... syntax and resubmit SQL 3135 3135 The precision of float value cannot exceed 54 Cause You specified a value for float precision that exceeds 54 which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3136 3136 Only LEFT RIGHT and FULL OUTER JOIN are valid in oj Cause You attempted to perform an invalid outer join Only LEFT RIGHT and FULL OUTER JOIN are suppo...

Page 109: ...ATE DELETE or DDL statement with a transaction access mode of READ ONLY which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3142 3142 INTO clause host variables not allowed in a static cursor Cause You attempted to create a static cursor with INTO clause host variables which is not supported Effect The operation fails Recovery Correct the syntax and resub...

Page 110: ...ultiple times within the LIKE clause of the CREATE TABLE statement which is not supported Effect The operation fails Recovery Remove the duplicate WITH CONSTRAINTS phrases SQL 3150 3150 Duplicate WITH HEADING phrases were specified in LIKE clause in CREATE TABLE statement Cause The WITH HEADINGS phrase appears multiple times within the LIKE clause of the CREATE TABLE statement which is not support...

Page 111: ...cify a valid DATETIME literal and resubmit SQL 3159 3159 If you intended name to be a character set specifier for a character string literal you must remove the spaces in front of the single quote delimiter name is the character set specifier Cause You apparently specified name as a character set specifier for example KANJI but you placed a space in front of the single quote delimiter which is not...

Page 112: ...e mismatch occurred between the output host variable and the selected value in the statement you specified Effect The operation fails Recovery Correct the syntax and resubmit SQL 3165 3165 The precision or exponent value specified in value was less than the minimum allowed or greater than the maximum allowed Cause You specified a statement in which you exceed the min or max precision or the expone...

Page 113: ...ax and resubmit SQL 3172 3172 EXIT is not allowed in a compound statement Cause You specified a compound statement that contains an EXIT command Effect The operation fails Recovery Correct the syntax and resubmit SQL 3173 3173 UPDATE STATISTICS is not allowed in a compound statement Cause You specified a compound statement that contains an UPDATE STATISTICS command Effect The operation fails Recov...

Page 114: ...tempted to perform an operation with an incorrect data type Effect The operation fails Recovery Correct the syntax and resubmit SQL 3179 3179 Collation name1 is not defined on the character set name2 name1 is the name of the collation name2 is the character set name Cause You attempted to used a collation name that is not defined on the character set A valid collation name is required Effect The o...

Page 115: ...e and resubmit SQL 3185 3185 SIGNAL parameter 3 must be of type string Cause You attempted a SIGNAL statement with a third parameter that is not a quoted string Effect The operation fails Recovery Specify a parameter that is a quoted string and resubmit SQL 3186 3186 string Dynamic parameters and host variables are currently not allowed in DDL string is the dynamic parameter or host variable that ...

Page 116: ... the SIGNAL text message Cause You attempted a SIGNAL statement SIGNAL statements are commonly used as an action for a trigger in a compound statement or in a user application Effect The operation fails Recovery None SQL 3195 3195 Table creation with data type dtype is not supported dtype is a data type specified for a column Cause The data type specified for a column in a CREATE TABLE statement i...

Page 117: ...ubmit SQL 3202 3202 PARAMETER STYLE clause is required Cause In the CREATE PROCEDURE statement you omitted the mandatory PARAMETER STYLE clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3203 3203 LANGUAGE clause is required Cause In the CREATE PROCEDURE statement you omitted this mandatory LANGUAGE clause Effect The operation fails Recovery Correct the syntax and resu...

Page 118: ...tempted a CREATE TABLE table name columnname longwvarchar N where N current MAX_LONG_WVARCHAR_DEFAULT_SIZE setting Effect The operation fails Recovery Decrease the CREATE TABLE statement s longwvarchar column width N or increase the current MAX_LONG_WVARCHAR_DEFAULT_SIZE setting and resubmit SQL 3210 3210 Minimum length of LONGWVARCHAR is value Cause You attempted a CREATE TABLE table name columnn...

Page 119: ...rease the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit SQL 3215 3215 Computed LONG VARCHAR length len1 is below minimum len2 Cause You attempted a CREATE TABLE table name c1 longvarchar c2 long varchar cn long varchar and the computed long varchar columns width is below the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting Effect The operation fails Recovery Decrease the number of long v...

Page 120: ...lay output Recovery Reissue the command without the display option or specify an object SQL 3225 3225 SHOWLABEL failed for object object name The object does not exist in the given namespace namespace the object is not accessible or the object type is not supported SHOWLABEL supports only SQL MX tables views and indexes object name is the specified name of an object namespace is either the TABLE o...

Page 121: ...as the specified table or view Cause You specified a synonym that has a different catalog than the object Effect The operation fails Recovery Correct the syntax so that the synonym and the object have the same catalog and schema values SQL 3231 3231 WITH NO ROLLBACK clause was used in an INSERT UPDATE or DELETE statement when AUTOCOMMIT is OFF Cause An INSERT UPDATE or DELETE statement is used the...

Page 122: ...OLLBACK transaction setting is in effect Cause On a positioned DELETE or an embedded DELETE statement a DELETE operation that included the STREAM clause and SET ON ROLLBACK clause was attempted when the NO ROLLBACK transaction setting is ON Effect Compilation of the statement fails Recovery If you intend to use NO ROLLBACK remove the conflicting clause Otherwise either turn OFF the NO ROLLBACK tra...

Page 123: ...ement SQL 3240 3240 The commit size value must be an unsigned integer value greater than zero Cause A commit size option was specified that is zero or negative Effect The statement fails to execute Recovery Specify a valid commit size and resubmit the statement SQL 3241 3241 This MERGE statement is not supported Reason reason text reason text is the reason for the error Cause The MERGE statement c...

Page 124: ...nd with character set name2 Cause You specified a character operand with a character set that the function does not support Effect The operation fails Recovery Do not use the character operand with that character set in the function SQL 3404 3404 Character set name to which SQL_TEXT is aliased is not allowed for a SQL module Cause You specified SQL_TEXT as the module character name set SQL_TEXT is...

Page 125: ...ue index on it column name is the name of the IDENTITY column Cause You tried to INSERT a system generated value for the IDENTITY column that does not have a unique index on it Effect The operation failed Recovery Create a unique index on the IDENTITY column Note that the unique index must be only on the IDENTITY column SQL 3413 3413 The NOT NULL constraint on IDENTITY column column name must be N...

Page 126: ...ified either through the DDL or through the default POS_NUM_DISK_POOLS Effect The operation fails Recovery Retry the query by specifying a disk pool number that is less than or equal to the number of disk pools specified in the DDL or through the default POS_NUM_DISK_POOLS SQL 3418 3418 Local Number of Partitions clause is not allowed with DISK POOL clause Cause Using the DISK POOL clause with LOC...

Page 127: ...Effect The operation fails Recovery Retry the query by specifying only a single NO PARTITION clause SQL 3422 3422 Duplicate DISK POOL clauses were specified Cause The DISK POOL clause was specified more than once Effect The operation fails Recovery Retry the query by specifying only a single DISK POOL clause SQL 3423 3423 Duplicate NUMBER OF PARTITIONS clause specified or NO PARTITION and NUMBER O...

Page 128: ...option A second START WITH MINVALUE MAXVALUE INCREMENT BY or NO CYCLE sequence generator option has been specified Effect The statement fails Recovery Specify a single START WITH MINVALUE MAXVALUE INCREMENT BY or NO CYCLE sequence generator option and resubmit the statement SQL 3428 3428 Identity column col name defined as GENERATED ALWAYS cannot accept values specified by the user col name is the...

Page 129: ...Recovery Supply the input values for the IDENTITY column 129 ...

Page 130: ...130 ...

Page 131: ...e the user specified double quotes which indicate a delimited identifier rather than single quotes which indicate an alpha literal The user probably intended select from tb where b b alpha literal or select from tb where b v table tb a int b char v char Effect The operation fails Recovery Correct the syntax so that the table and column can be found and resubmit SQL 4002 4002 Column name1 is not fo...

Page 132: ...peration fails Recovery Correct the column reference and resubmit SQL 4006 4006 Within an aggregate all column references must come from the same scope Cause You referred to columns that do not come from the same scope Effect The operation fails Recovery Correct the column references and resubmit SQL 4007 4007 The select list index value1 is out of range It must be between 1 and the number of sele...

Page 133: ... to column name with a SELECT or SELECT TBL reference Column name must be a grouping column or be specified within an aggregate Effect The operation fails Recovery Correct the syntax and resubmit SQL 4013 4013 Column name is a system column and cannot be updated or inserted into Cause You attempted to update or insert into a system column name which is not supported Effect The operation fails Reco...

Page 134: ...19 The select list of a subquery in a select list must be scalar degree of one Cause You specified a select list that is not scalar Effect The operation fails Recovery Correct the syntax and resubmit SQL 4020 4020 Arithmetic operations on row value constructors are not allowed Cause You attempted to perform an arithmetic operation on row value constructors which is not supported Effect The operati...

Page 135: ...but if you use it you must explicitly specify values for columns that do not have default values Effect The operation fails Recovery Correct the syntax and resubmit SQL 4025 4025 Error while preparing constraint name on table table name table name is the name of the table Cause The HP Neoview database software received an error while preparing constraint name on table name See accompanying error m...

Page 136: ... Cause You specified column name with an unknown class Effect The operation fails Recovery Correct the syntax and resubmit SQL 4033 4033 Column name is a primary or clustering key column and cannot be updated Cause You attempted to update column name which is a primary or clustering key column that cannot be updated Effect The operation fails Recovery Correct the syntax and resubmit SQL 4034 4034 ...

Page 137: ... function with an invalid operand It must be numeric or interval Effect The operation fails Recovery Correct the syntax and resubmit SQL 4039 4039 Column name is of type specification1 incompatible with the value s type specification2 Cause You specified column name with type specification1 which is incompatible with the type of the value Effect The operation fails Recovery Correct the syntax and ...

Page 138: ...d of function name must be numeric Cause You specified operands for function name that are not numeric which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4046 4046 The operands of function name must be exact numeric Cause You specified operands of function name that are not type exact numeric which is required Effect The operation fails Recovery Correct the s...

Page 139: ...ils Recovery Correct the syntax and resubmit SQL 4052 4052 The second operand of function name must be numeric Cause You specified the first operand of function name with a type other than numeric which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4053 4053 The third operand of function name must be numeric Cause You specified the third operand of a function ...

Page 140: ...OM tblx tblz tblx Effect The operation fails Recovery Correct the syntax and resubmit SQL 4059 4059 The first operand of function name must be numeric Cause You specified the first operand of function name with a type other than numeric which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4060 4060 Reading from and inserting or updating in or deleting from the ...

Page 141: ...haracter data types that is of the same character set Cause You specified operands for function name with incompatible character data types Effect The operation fails Recovery Correct the syntax and resubmit SQL 4066 4066 The operands of a UNION must be of equal degree Cause You specified operands of a UNION statement that are not of equal degree which is required Effect The operation fails Recove...

Page 142: ...name Cause You specified an invalid operand for function name It must be a datetime operand containing the variable listed in the message Effect The operation fails Recovery Correct the syntax and resubmit SQL 4073 4073 The COLLATE clause may appear only after an expression of character data type not data type Cause You specified the COLLATE clause after an expression that is not a character data ...

Page 143: ...u specified an invalid operand in function name The operands must be numeric Effect The operation fails Recovery Correct the syntax and resubmit SQL 4082 4082 Object name does not exist or is inaccessible Cause You referred to table name which does not exist or is inaccessible for example on a downed disk volume Effect The operation fails Recovery Correct the syntax and resubmit SQL 4084 4084 SQL ...

Page 144: ...u specified a constraint name that contains a subquery which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 4093 4093 The number of output dynamic parameters value1 must equal the number of selected values value2 Cause The HP Neoview database software requires that the number of output dynamic parameters value1 match the number of selected values value2 Ef...

Page 145: ...LL operand is not allowed in predicate name Cause You included a NULL operand in predicate name which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 4100 4100 A NULL value is not allowed in a select list unless it is CAST to some data type Cause You specified a NULL value in a select list that is not cast to a data type which is required Effect The operati...

Page 146: ...bles in scope CAT SCH T050A Default schema CAT SCH ERROR 4104 If a character literal was intended you must use the single quote delimiter instead of the double Lower instead of Lower Effect Nothing is selected Recovery Replace the double quotes with single quotes SQL 4105 4105 Translation name is not recognized Cause The HP Neoview database software does not recognize the translation name Effect T...

Page 147: ... select x from select a runningcount b from T1 sequence by a T2 x y where y 10 select count from t1 sequence by b group by a having runningsum a count Effect The operation fails Recovery Correct the syntax and resubmit For example select a from T1 where runningcount b 10 sequence by a ERROR 4109 Sequence functions placed incorrectly RUNNINGCOUNT CAT SCH HPPARTEST1 B ERROR 8822 Unable to prepare th...

Page 148: ... to perform absolute and relative sampling in the same balance expression which is not supported Effect The HP Neoview database software is unable to prepare the query Recovery Correct the syntax and resubmit SQL 41 13 4113 The sample size for type Sampling must be size type Cause You specified an invalid combination of sample type and sample size type Effect The HP Neoview database software is un...

Page 149: ...updatable cursor join query does not select the target of the update and receives an error SELECT A PROD_CODE FROM EXPRODPARAMS A MSRATES B WHERE CASE WHEN B UPDATE_FLAG IS NULL THEN N ELSE B UPDATE_FLAG END N AND A ACC_TYPE B ACC_TYPE AND A PROD_CODE B PROD_CODE FOR UPDATE OF UPDATE_FLAG ERROR 4001 Column UPDATE_FLAG is not found Tables in scope A Default schema CAT SCH ERROR 4117 The cursor quer...

Page 150: ...exceed the number of HP Neoview processing nodes Effect The operation fails Recovery Resubmit with an appropriate number of requested streams SQL 4120 4120 In a query with a GROUP BY DISTINCT or aggregate function each column in the ORDER BY clause must be one of the columns explicitly SELECTed by the query Column in error name Cause You attempted to perform a query with an aggregate function a GR...

Page 151: ...ry consisting of several expressions whose select list is not scalar If the subquery is not the only expression in the constructor it must be scalar Effect The operation fails Recovery Correct the syntax and resubmit SQL 4126 4126 The row value constructors in a VALUES clause must be of equal degree Cause You specified a VALUES clause whose row value constructors are not of equal degree Effect The...

Page 152: ...cter is CHARACTER SQL 4134 4134 The operation name is not allowed Try UNION ALL instead Cause You attempted to perform an operation that the HP Neoview database software does not allow Effect The operation fails Recovery Try a UNION ALL operation and resubmit SQL 4135 4135 In an INSERT SELECT each column in the ORDER BY clause must be one of the columns in the selected list of the query Column in ...

Page 153: ...or your join You must use the primary key to prevent returning multiple rows being returned for a single deleted or updated row Effect The HP Neoview database software is unable to compile the statement Recovery Modify the WHERE clause to use the primary key of the table expression SQL 4151 4151 Stream access is supported only on updatable views View table name Cause You attempted to access a nonu...

Page 154: ...le to compile the statement Recovery Modify the statement and resubmit SQL 4158 4158 Join of stream expressions is not supported Tables in scope name Cause You attempted to perform a join of stream expressions Effect The HP Neoview database software is unable to compile the statement Recovery Modify the statement and resubmit SQL 4159 4159 Intersection of stream expressions is not supported Tables...

Page 155: ...f right join cannot be embedded name expression Tables in scope name Cause You attempted to perform a right join using an embedded expression as the outer relation Effect The HP Neoview database software is unable to compile the statement Recovery Modify the statement and resubmit SQL 4165 4165 Outer relation of right join cannot be stream expression Tables in scope name Cause You attempted to per...

Page 156: ...is unable to compile the statement Recovery Modify the statement and resubmit SQL 4171 4171 Embedded operation statements are not supported in INSERT statements operation is an INSERT operation Cause You attempted to perform an INSERT that included an embedded INSERT statement Effect The operation failed Recovery Modify the statement and resubmit SQL 4173 4173 Stream expression is not supported fo...

Page 157: ...to compile the statement Recovery Modify the statement and resubmit SQL 4178 4178 Update of variable length column name is not permitted on rollback Cause You attempted to perform a rollback that included an update of a variable length column Effect The HP Neoview database software is unable to compile the statement Recovery Modify the statement and resubmit SQL 4179 4179 SEQUENCE BY is not suppor...

Page 158: ...BLE SQL statement does not exist Effect None Recovery Ensure that the volatile table with the specified table name is created before issuing the SQL statement SQL 4191 4191 Username schema name specified as part of the volatile table or index must be the same as the current username user name schema name is the user specified schema name in the SQL statement user name is the current default SQL us...

Page 159: ...SQL 4198 4198 Clustering key columns cannot be specified in the SET clause of an embedded UPDATE statement Cause Clustering key columns were specified in the SET clause of an embedded UPDATE statement Effect The statement does not compile Recovery Remove the clustering key columns from the SET clause and compile the statement again SQL 4199 4199 The SET ON ROLLBACK clause cannot be specified when ...

Page 160: ... Recovery Informational message only no corrective action is needed SQL 4204 4204 Stream access is supported for only key sequenced tables Table name Cause You attempted to use stream access on a table that is not key sequenced which is required Effect The HP Neoview database software is unable to compile the statement Recovery Modify the statement and resubmit SQL 4205 4205 Embedded name1 is supp...

Page 161: ...submit SQL 4210 4210 Embedded update delete statements not supported within an IF statement Cause You attempted to embed UPDATE DELETE statements within an IF statement Effect The HP Neoview database software is unable to compile the statement Recovery Modify the statement and resubmit SQL 4212 4212 table name cannot be used to satisfy order requirement on the stream because it is partitioned Caus...

Page 162: ...ew database software statement being compiled a stored procedure invocation contains an incorrect number of parameters Effect The Neoview database software statement is not compiled Recovery Correct the Neoview database software statement and retry the compilation SQL 4303 4303 The supplied type for parameter value of routine routine name was type name1 which is not compatible with the expected ty...

Page 163: ...4308 4308 Internal error Unsupported SQL data type value specified for a CALL statement parameter Cause In the HP Neoview database software statement being compiled a parameter in a stored procedure invocation had an unsupported SQL data type Effect The Neoview database software statement is not compiled Recovery This error should never occur Drop the stored procedure and recreate it with an appro...

Page 164: ...able specified in the PARTITIONING_KEY option of the KEY_RANGE_COMPARE function Effect The operation failed Recovery Specify a column that is part of the partitioning key in the PARTITIONING_KEY clause of the KEY_RANGE_COMPARE function SQL 4334 4334 KEY_RANGE_COMPARE is not allowed on views Cause KEY_RANGE_COMPARE function cannot be used on views Effect The operation failed Recovery Use the KEY_RA...

Page 165: ...ubmit SQL 4339 4339 Subqueries are not supported in the join predicate of Full Outer Join Cause A subquery is specified in the join predicate of FULL OUTER JOIN Effect The query failed to compile Recovery Specify a join predicate for FULL OUTER JOIN that does not contain a subquery and resubmit SQL 4340 4340 All Window Functions within a select clause must have the same window partition clause and...

Page 166: ...on fails Recovery Rewrite the query so that windows functions are placed only in the select list SQL 4347 4347 Maximum Window frame size of n1 rows exceeded n1 is the maximum number of rows Cause The window frame specified is larger than the maximum window frame allowed Effect The operation fails Recovery Rewrite the query so that window frame size does not exceed the maximum window frame allowed ...

Page 167: ...a regular delete on the view SQL 4351 4351 Set Transaction MULTI COMMIT option is only supported for DELETE statements Cause MULTI COMMIT was specified on a statement other than DELETE Effect The statement fails to execute Recovery Use MULTI COMMIT ON with DELETE statement only SQL 4352 4352 SET TRANSACTION MULTI COMMIT ON is not compatible with the following options a READ UNCOMMITTED isolation l...

Page 168: ... or the qualify clause Cause The RANK function can be placed only in the SELECT list or the QUALIFY clause Effect The statement fails to prepare Recovery Rewrite the query so that the RANK function is placed only in the SELECT list or the QUALIFY clause SQL 4365 4365 Using rank function and aggregate functions in the same scope is not supported Cause You used the RANK function with aggregate funct...

Page 169: ...not set the holdable cursor attribute for this SQL statement SQL 4382 4382 Holdable cursor attribute cannot be set for a CALL statement Cause A holdable cursor attribute is set for a CALL statement Effect The CALL statement fails to compile Recovery Do not set the holdable cursor attribute for the CALL statement SQL 4390 4390 The OLAP History row size exceeds the limit of bytes bytes bytes is the ...

Page 170: ...cutor and TMF transaction identifiers did not match Effect The operation fails Recovery The transaction IDs can be used to help determine how the transaction was started and why the transaction identifiers didn t match 170 Binder and Compilation Messages 4000 Through 4999 ...

Page 171: ...query normalizer Cause The optimizer received an internal error during query normalization 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 171 ...

Page 172: ...172 ...

Page 173: ...ation Recovery Undo your changes using the CLEAR option in UPDATE STATISTICS SQL 6003 6003 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value value for column name If you have manually modified the metadata table then you should undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics Cause You have manually modified the metadata...

Page 174: ...lt the access path chosen might not be the best possible column name is the name of the affected column table name is the name of the HP Neoview database table to which the columns belong Cause Statistics for the column were not generated Effect None The plan generated by the optimizer may not be optimal This is a warning message Recovery Generate the statistics for the column identified in the wa...

Page 175: ...elong op_name is the operator that was being processed when the warning was issued Cause Statistics for the set of columns were not generated The warning is issued only for multi column statistics Effect The plan generated by the optimizer may not be optimal Statistics for the columns identified in the warning will be automatically generated at the next available scheduled time window Recovery Non...

Page 176: ...s the name of the HP Neoview database table to which the column belongs Cause Statistics for the Column were not generated Effect Statistics were generated while the query was being compiled with small sample the plan generated by the optimizer may not be optimal Statistics for the column identified in the warning will be automatically generated at the next available scheduled time window Recovery...

Page 177: ...ry If the Error code is 0 no action is required by the User If the Error code is 33 or 35 Users should refer to Chapter 21 page 385 for information about recovering from file system error codes 33 and 35 177 ...

Page 178: ...178 ...

Page 179: ...pling is performed on a base table with no WHERE clause predicate SQL 7004 7004 A parallel extract plan could not be produced Possible causes include an incompatible Control Query Shape CQS specification use of rowset expressions or use of SQL features that cannot be parallelized such as FIRST LAST N table valued functions stream access to tables and embedded updates or deletes Cause HP Neoview da...

Page 180: ...or the command and reenter it with the required right parenthesis SQL 71 14 7114 Expecting Cause The command did not specify a delimiting comma where TMFCOM expected one Effect The command fails Recovery Check the syntax rules for the command and reenter it accordingly SQL 7334 7334 Expecting a MX Catalog or Schema ANSI Name Cause The SET ANSIDEFAULT command specified one of the CATALOG SYSTEM USE...

Page 181: ...mand specifying a valid SQL identifier SQL 7339 7339 A newer version of SQL MX is needed on this system Cause There is a version mismatch between the caller TMF and the SQL MX parser This can occur for the DUMP FILES INFO DUMPS RECOVER FILES and SET ANSIDEFAULT commands Effect The command fails Recovery Check the version of SQL MX and install a newer version of SQL MX if necessary SQL 7340 7340 Ex...

Page 182: ...tch the current defaults specified Effect The command fails Recovery This message should not appear contact the GMCSC or your support provider SQL 7350 7350 Incompatible consistency level of consistency num for DP2 Halloween protection Cause The compiler encountered a problem while producing a plan that would be incompatible with the chosen isolation level Effect The compiler reports the problem a...

Page 183: ...Recovery Rewrite your query to prevent the join from overflowing its memory to disk Contact HP Support for assistance 183 ...

Page 184: ...184 ...

Page 185: ...ry Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 8004 8004 Trying to open a statement or cursor that is not in the closed state Cause You attempted to open a statement or cursor that is not in the closed state It must be in the closed state to be opened Effect The operation fails Recovery Do n...

Page 186: ...und BEGIN END statement returns more than one row Cause You specified a SELECT statement inside a compound statement that returns more than one row 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 8012 8012 Encoding of CONTROL QUERY DEFAULTs encoding Cause The ...

Page 187: ...he accessing software Cause You attempted to access a system version that is incompatible with the version of the accessing software Effect The operation fails Recovery The system you are trying to access must be on a system version that is compatible with your accessing software Upgrade that system SQL 8017 8017 Explain information is not available for this query Cause The explain default has bee...

Page 188: ...rease the time out period by using SET SESSION DEFAULT RTS_TIMEOUT n command If the problem persists check to see if the system is very busy SQL 8028 8028 Server declined cancel request The pp process was not found pp is the name of the process Cause The MXSSMP process which is used to process cancel requests is not running Effect The query is not canceled Recovery Correct any problem that causes ...

Page 189: ...ration Recovery Make the data you enter unique to be consistent with the constraint SQL 8103 8103 The operation is prevented by referential integrity constraint name1 on table name2 name1 is the name of the constraint name2 is the name of the table Cause You attempted to perform an operation on table name1 that is prevented by referential integrity constraint name2 Effect The operation fails Recov...

Page 190: ... a self referencing INSERT statement that was compiled without a blocking operator either 1 while the AUTOCOMMIT option was set to OFF or 2 in a user defined transaction following a BEGIN WORK statement Effect The operation fails Recovery For cause 1 set the AUTOCOMMIT option to ON and execute the statement For cause 2 terminate the transaction and then execute the statement SQL 8108 8108 The oper...

Page 191: ...ition Effect The operation fails Recovery Determine why none of the partitions were available then correct the error and resubmit SQL 8303 8303 Anchor file name contains invalid data name is the fully qualified HP Neoview platform file name of a Neoview database anchor file Cause The named anchor file contains invalid data Effect The HP Neoview database software uses data from the anchor file to l...

Page 192: ... character string literal that you specified in the SQL statement target data type internal type is the character string data type and an internal representation of the data type to which the character string is being converted 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...

Page 193: ...scape character argument of a LIKE predicate must be one character in length Cause You specified a LIKE predicate with an invalid escape character argument which must be one character in length Effect The operation fails Recovery 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 escap...

Page 194: ...ally generated dial out message about this condition 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 cond...

Page 195: ...1 8421 NULL cannot be assigned to a NOT NULL column Cause You assigned NULL to a column for which NOT NULL was specified Effect The operation fails Recovery 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 ...

Page 196: ...e The table or the statement has invalid SJIS or UTF8 characters Effect The operation fails Recovery Remove the invalid characters from the table or the statement and resubmit SQL 8440 8440 The size of the history buffer is too small to execute one or more of the Window Functions in the query Cause You attempted to run a window function that requires a larger history buffer Effect The operation fa...

Page 197: ...dition SQL 8555 8555 An internal error occurred in the SQL MX executor in the disk process Cause An HP Neoview database procedure in the disk process detected an internal error Effect The operation fails An Event Management Services EMS event message for event number 5127 from the Disk subsystem has been generated to supply further diagnostic information For information on retrieving EMS messages ...

Page 198: ...anged that table Effect The table is no longer open You will see this message if the HP Neoview database software was unable to recompile your 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 8575 8575 Timestamp mismatch on table name name is the name of the table Cause Table n...

Page 199: ...operation fails Recovery Contact the GMCSC SQL 8581 8581 The in memory Join operation could not complete due to insufficient memory Cause Insufficient memory was available to perform the join operation Effect The operation fails Recovery Contact HP support for assistance in recompiling the query with Unique In Memory Hash Joins turned off control query default UNIQUE_HASH_JOINS OFF and re execute ...

Page 200: ...om file system while locking unlocking Cause The file system received an error while locking or unlocking 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 8602 8602 The file system reported error number on a lock unlock operation number is the error number Caus...

Page 201: ...8607 8607 Rolling back a transaction that has not started Cause You attempted to roll back a transaction that has not started Effect The operation fails Recovery 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 is the name of the subsystem number is the error number Cause Transactio...

Page 202: ...s it will later commit or rollback SQL 8614 8614 SQL cannot begin a transaction when multiple contexts exist 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 c...

Page 203: ... Service or server name 1 string1 is the function that returned the error For example READX 1 READX 2 WRITEX or PROCESSNAME_CREATE_ 0 int0 is error code 1 1 int1 is error code 2 2 string2 is the error detail Cause See the accompanying error messages to determine the cause Effect The operation may fail or succeed Recovery Apply the recovery for the indicated error SQL 8654 8654 Query Id was not fou...

Page 204: ...Listener process received an error from CLI Effect The operation fails Recovery Apply the recovery of the CLI error SQL 8660 8660 Could not read BDR configuration table Cause BDR processes cannot read from configuration table manageability replicate_schema replicate_config Effect The operation fails Recovery Check the environment TMF OSS and retry the operation SQL 8661 8661 Specified target syste...

Page 205: ... example role SUPER SERVICES is not authorized to perform this command on object NEO SCH CUSTOMER Cause The user is not authorized to replicate the object Effect The operation fails Recovery Request the owner of the object to run replicate 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 ...

Page 206: ...o an automatically generated dial out message about this condition 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 st...

Page 207: ...er to create a valid module file SQL 8809 8809 Open of the module file name failed with error number name is the name of the file number is the error number returned Cause The HP Neoview database software was unable to open module file name Effect The operation fails Recovery Check the location of the module file and retry the operation SQL 881 1 8811 Trying to close a statement that is either not...

Page 208: ...QL 8816 8816 An internal error occurred while executing the TCB tree 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 8817 8817 An internal error occurred while fetching from the TCB tree Cause This is an internal error Effect Th...

Page 209: ... 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 Cause This is an internal error ...

Page 210: ...er no current context or the module to which the statement belongs is not added to the current context Cause This is an internal error Effect The operation fails Recovery 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 A transaction has not been s...

Page 211: ...entication but logging failed Effect The authentication failed Recovery Correct the logging issue and then try to logon again SQL 8838 8838 Unable to receive reply from MXCMP possibly caused by internal errors when compiling SQL statements processing DDL statements or executing the builtin stored procedures Cause The HP Neoview database software did not receive a reply it expected from MXCMP Effec...

Page 212: ...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 HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 8845 8845 An internal error occurred root_tcb is null Cause This is an inte...

Page 213: ...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 8854 8854 Specified attribute value is not valid Cause You specified an invalid attribute value Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response ...

Page 214: ... 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 8860 8860 Module file name has an obsolete module header name is the file name Cause The module file name has an obsolete module header Effect The operation fails Recovery Rebuild the module file and resubmit SQ...

Page 215: ...ame has an obsolete procedure location table entry Effect The operation fails Recovery Rebuild the module file and resubmit SQL 8867 8867 An error while reading from file name name is the file name Cause The HP Neoview database software encountered an error while reading the module file name Effect The operation fails Recovery Rebuild the module file and resubmit SQL 8868 8868 SQL cannot create a ...

Page 216: ...ect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 8873 8873 The current statement is already associated with a QFO Cause An existing quasi file object QFO is already associated with the current statement Effect The operation fails Recovery Do not attempt recovery H...

Page 217: ...he current CLI context Effect The context is not removed Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 8881 8881 The specified CLI context handle could not be found Cause A call level interface CLI application specified a context handle that does not exist Effect The specified operati...

Page 218: ... SQL 8891 8891 Non ASCII character host variable type was specified for name field name is the name of the field Cause The host variable type for the field name must be ASCII 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 8893 8893 The statement argument coun...

Page 219: ...ically generated dial out message about this condition SQL 8901 8901 The MXUDR server for this statement is no longer running The statement will be assigned a new MXUDR server if it is executed again Cause During execution of an HP Neoview database software statement an attempt was made to contact a nonexistent Neoview database UDR server Effect The operation fails Recovery Retry the Neoview datab...

Page 220: ...urred within the Neoview database executor 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 8909 8909 The request to allocate a stored procedure result set failed because the provided input statement is not a CALL statement Cause A call level interface CLI appl...

Page 221: ...e an SQL statement and the statement identifier is associated with a stored procedure result set Effect The operation fails Recovery None Contact the GMCSC and report this condition SQL 8914 8914 An attempt to open a stored procedure result set at position index failed because multiple open attempts on the same result set are not allowed index is an integer specifying a position in the ordered set...

Page 222: ... bind multiple stored procedure result set statements to the same result set index Effect The operation fails Recovery None Contact the GMCSC and report this condition SQL 8918 8918 The Runtime Statistics infrastructure is not running Unable to return Runtime Statistics Cause The user issued a command to retrieve runtime statistics but the runtime statistics infrastructure the SSCP and SSMP proces...

Page 223: ... nodes Effect The runtime statistics information returned might be devoid of statistics from one or more nodes If the node is involved in the query the statistics might not be accurate Recovery Retry the command If the problem persists contact the GMCSC SQL 8923 8923 The given Query Id 0 string0 is not found Cause The command to obtain the runtime statistics for a given QID did not find the query ...

Page 224: ...ilure details Cause The update to the internal sequence generator failed Effect The statement fails Recovery Additional error codes are returned for the update failure Proceed with the recovery procedures recommended by the additional error codes 224 Executor Messages 8000 Through 8999 ...

Page 225: ... Unable to DROP object name Cause UPDATE STATISTICS encountered an error during a DROP of the object name Effect The HP Neoview database software is unable to continue processing Recovery Resubmit the statement If this does not correct the problem stop and restart the Neoview database If this does not correct the problem contact the GMCSC SQL 9202 9202 UPDATE STATISTICS has located previously gene...

Page 226: ...ither own the object name or be the super ID Effect The HP Neoview database software is unable to continue processing Recovery Resubmit after checking the table location and access privileges SQL 9207 9207 The specified SAMPLE option generated an empty sample set Modify the SAMPLE option and resubmit Cause The SAMPLE option you specified generated an empty sample set Effect The HP Neoview database...

Page 227: ...tax to specify the column list and resubmit SQL 9214 9214 Object name could not be created Cause UPDATE STATISTICS encountered an error during a CREATE of the object name Effect The HP Neoview database software is unable to continue processing Recovery Resubmit the statement If this does not correct the problem stop and restart the HP Neoview database software If this does not correct the problem ...

Page 228: ... generated by update statistics Recovery Informational message only no corrective action is needed SQL 9218 9218 The statement will have no effect because no histograms need to be updated Cause The HP Neoview database software determined that no histograms needed to be created or updated for the table Effect The operation does not fail but has no effect Recovery Informational message only no corre...

Page 229: ...ystem error if any would indicate the low level system error If the cause is only a sort error the system error might be 0 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 10005 10005 Sort encountered an unexpected error Cause An unknown sort error occurred Eff...

Page 230: ...rflow with an invalid block number number Cause The caller specified a block number that is out of range Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 10013 10013 Sort could not find any appropriate disks for overflow Cause The available disks on the system ...

Page 231: ...8 Sort failed while calling FILENAME_FILESTART_ with error number Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact the GMCSC SQL 10019 10019 Sort failed while calling FILENAME_FILENEXT_ with error error number Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact the GMCSC SQL 10020 10020 Sort fail...

Page 232: ...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 10027 10027 Sort failed while calling FILE_GETINFOLIST with error number Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact the GMCSC SQL 10028 1002...

Page 233: ...ch use SQL 10049 10049 The block number was not found in any scratch file Cause The I O operation failed because an expected scratch file that was created was not found Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition Scratch File I O Messages 10101 10199 SQL 10101...

Page 234: ...rite to a scratch file Effect The operation fails Recovery Contact the GMCSC to diagnose the cause of the WRITEX returned error and correct the problem SQL 10105 10105 operator scratch file read failed READX returned error number operator is the HP Neoview query operator that encountered the error for example merge join number is a Neoview platform internal procedure error number Cause The query o...

Page 235: ...omatically generated dial out message SQL 101 13 10113 operator could not get the last error for a scratch file FILE_GETINFO_ returned error number operator is the HP Neoview query operator that encountered the error for example merge join number is a Neoview platform internal procedure error number Cause The query operator failed to get the last error for a scratch file Effect The operation fails...

Page 236: ...HP Neoview query operator that encountered the error for example merge join number is a Neoview platform internal procedure error number Cause The operation fails Effect 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 101 18 10118 operator encountered an er...

Page 237: ...ESHOLD_PERCENT was reached on all available scratch disks Effect The operation fails Effect The operation fails Recovery Either reduce the threshold percentage and retry the query or specify a scratch disk with adequate free space SQL 10152 10152 operator attempted to read data using an invalid block number operator is the HP Neoview query operator that encountered the error for example merge join...

Page 238: ...238 ...

Page 239: ...is that of a trigger the recovery options are Drop the trigger or triggers first and reattempt the operation Abandon the revoke operation Use the cascade drop behavior option for revoke and reattempt the operation The cascade drop behavior if successful will also drop all the triggers by using the target object SQL 1 1018 11018 An empty or unsupported trigger action was specified Cause An attempt ...

Page 240: ...ic parameters do not appear in the trigger action Then retry the operation SQL 1 1047 11047 SELECT statements are not allowed in the compound action of a trigger Cause You attempted to create a trigger that includes a SELECT statement in its compound action Effect The operation fails and the trigger is not created Recovery Rewrite the trigger so that the SELECT statement is not present in the trig...

Page 241: ...R Invalid UDR handle string Cause The UDR server received a request for a stored procedure that is no longer present in the UDR server context Effect The request message is rejected and the SQL statement fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 1 1 103 11103 MXUDR Invalid r...

Page 242: ... an automatically generated dial out message about this condition SQL 1 1 1 1 1 11111 MXUDR Internal error value Cause The UDR server received an incorrectly formatted message Effect The request message is rejected and the SQL statement fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition ...

Page 243: ...ations in response to an automatically generated dial out message about this condition SQL 1 1 1 16 11116 MXUDR Internal error A stored procedure result set message type request arrived containing an invalid result set index index message type type is a message that is sent to the UDR server index is an internal identifier generated by the database software and used in messages to and from the UDR...

Page 244: ...s Unable to initialize the Java virtual machine Cause Initialization of the language manager failed during creation of the Java Virtual Machine Effect The operation fails Recovery Check the installation of the NSJ product Stop and restart the session and retry the SQL statement HP support will perform recovery operations SQL 1 1203 11203 The Language Manager failed to create its class loader possi...

Page 245: ...n type Cause In a CREATE PROCEDURE statement an unknown or unsupported return type was given in the EXTERNAL NAME clause Effect The operation fails Recovery Correct the EXTERNAL NAME and resubmit SQL 1 1215 11215 Java execution Invalid null input value at parameter position parameter number Cause A null value was supplied as input to a stored procedure in Java and the corresponding Java data type ...

Page 246: ...se During execution of a CALL statement an SQL error occurred and a Java exception was thrown Effect The operation fails Recovery Review the Java method Determine whether it is appropriate in your application for this exception to be thrown or whether it should be caught and handled by your user defined routine Retry the SQL statement SQL 1 1220 11220 A Java method completed with an uncaught java ...

Page 247: ...atement Cause During the execution of a CREATE PROCEDURE statement multiple SPJ methods were found in the specified Java class Each SPJ method was named class name method name and had a Java type signature matching the declared SQL parameter types If the DYNAMIC RESULT SETS clause specified a value greater than 0 zero each method also had one or more trailing java sql ResultSet parameters Effect T...

Page 248: ...n fails Recovery Correct the signature of the SPJ method and resubmit SQL 1 1234 11234 The Java method method name signature was not found in Java class class name method name is the Java method name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement signature is a Java type signature class name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE s...

Page 249: ...ing To reduce occurrences of this message you can change the SPJ method to return fewer result sets or recreate the procedure with a higher value for DYNAMIC RESULT SETS SQL 1 1238 11238 Stored procedure procedure name attempted to return one or more result sets containing large object data procedure name is the ANSI name of a stored procedure Cause During the execution of a CALL statement an SPJ ...

Page 250: ...essage about this condition SQL 1 1243 11243 The Language Manager encountered a java sql SQLException while retrieving the value of column column number from a java sql ResultSet row column number is the column number in the result set row Cause While processing a stored procedure result set the language manager was unable to access the specified column value in a row retrieved from the Neoview JD...

Page 251: ...y name name is an object Cause The materialized view query expression is not valid Effect The creation of the materialized view fails Recovery Rewrite the materialized view query expression and resubmit the statement SQL 12008 12008 Creation of the table holding the materialized view failed Cause The physical table that will hold the materialized view data could not be created Effect The creation ...

Page 252: ... by other applications Effect The materialized view cannot be initialized Recovery Resubmit the create statement If the issue persists contact the GMCSC SQL 12015 12015 Creation of an MVlog table for name failed name is a table used by a materialized view Cause When a materialized view is created log tables for its base tables are created as well The creation of such log tables failed Effect The c...

Page 253: ...name name is an existing materialized view Cause You attempted to initialize a materialized view that is using a second materialized view which is not yet initialized Effect The materialized view cannot be initialized Recovery Initialize the second materialized view first SQL 12027 12027 Materialized views cannot be created on metadata table name name is a metadata table Cause Materialized views a...

Page 254: ...d views Cause A STORE BY PRIMARY KEY is not supported in a Create Materialized View statement Effect The creation of the materialized view fails Recovery Change the STORE BY clause and resubmit the Create Materialized View statement SQL 12046 12046 Fatal Error in attribute table lists list type unknown Cause Some of the attributes specified in the CREATE Materialized View statement are not allowed...

Page 255: ... materialized views table name is the name of the trigger or materialized view source table actual row length is the row length of the MV source table or the trigger base table max row length is the maximum row length of the MV source table or trigger base table for which it is guaranteed that the compile error will not occur Cause Triggers and ON STATEMENT materialized views require the presence ...

Page 256: ...he creation of the materialized view fails Recovery None SQL 12070 12070 UPDATE Triggers and or incremental materialized views exist on table table name and the record length is larger than the recommended length of max row length If you are updating multiple columns in the same update statement try splitting your update statement into multiple update statements where less columns are updated per ...

Page 257: ...L 12106 12106 The index was created with NO POPULATE clause It will be populated during first refresh Cause A newly created index will not be populated until the materialized view is initialized Effect The is an informational message The index cannot be used until the materialized view is refreshed Recovery None SQL 12107 12107 The STORE BY clause is illegal The specified columns are aggregated co...

Page 258: ...f you need to recover the dropped materialized view the revoked privileges need to be acquired and the materialized view recreated SQL 121 1 1 12111 NO AUDIT materialized views are not supported Cause You specified a materialized view that is not audited Effect The creation of the materialized view fails Recovery Correct the syntax and resubmit SQL 121 12 12112 A secondary index index name was cre...

Page 259: ...terialized view can only track changes on a single table Effect The operation fails Recovery Try altering the materialized view and remove the COMMIT REFRESH EACH attribute and resubmit or only track changes on a single table SQL 121 18 12118 Embedded Insert Update or Delete is not allowed on a table used by an ON STATEMENT Materialized View Cause You attempted to execute an embedded insert update...

Page 260: ... 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 is an MVGroup Cause An MVGroup must be empty in order to drop it Effect The operation failed Recovery Remove all the materialized views from the MVGroup and try again SQL 12206 12206 Materialized view mv name is not in MVGroup mv name is a materi...

Page 261: ...ws from the materialized view group before removing the dependent materialized view SQL 1221 1 12211 The MVGroup already exists Cause An attempt was made to create a materialized view group with a name that already exists Effect The operation failed Recovery Change the materialized view group name and resubmit SQL 12212 12212 The materialized view mv name and all of its dependents were removed fro...

Page 262: ...04 An additional phase is needed to complete the refresh Cause The refresh operation did not complete This is an internal warning used by the refresh utility to complete the refresh operation with an addition phase Effect The operation fails Recovery None SQL 12308 12308 Internal refresh error MIN MAX values are compromised Cause The MIN MAX values have been compromised due to an incomplete refres...

Page 263: ...ew that have changed Cause The materialized view is tracking changes on too many changed base tables Effect The operation fails Recovery Refresh the materialized view with RECOMPUTE 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 a...

Page 264: ... a HAVING clause The materialized view cannot be maintained incrementally Cause Your CREATE MV statement includes the HAVING clause Effect 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 maintained ...

Page 265: ... Distinct aggregate functions were used in an incremental materialized view Effect The materialized view is not created Recovery Change the materialized view query to avoid using DISTINCT or change the materialized view to RECOMPUTE SQL 12333 12333 Creation failed INITIALIZE clause must be provided Cause There is a syntax error in the CREATE MV statement Effect The materialized view is not created...

Page 266: ...266 ...

Page 267: ...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 267 ...

Page 268: ...268 ...

Page 269: ...he 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 19003 19003 Internal stored procedure failed without any error information returned Cause Internal error Effect The HP Neoview database software is unable to process the request Recovery Do not attempt recovery HP support will p...

Page 270: ...ause Internal error Effect 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 19021 19021 Stored procedure name returns with error number Cause Internal error Effect The HP Neoview database software is unable to process the ...

Page 271: ...uested file and received error error number 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 20003 20003 File system error error number occurred during file close error number is the HP Neoview platform file system error Cause SQL was not able to close the requ...

Page 272: ...d buffer size is not a multiple of the block size for file Cause The utility subsystem that performs fast data transfer was sent an invalid buffer size 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 20009 20009 An internal error occurred buffer size is larger...

Page 273: ...dial out message about this condition SQL 20013 20013 An internal error occurred did not enable large transfer for file Cause The utility subsystem that performs fast data transfer performed steps out of sequence Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL...

Page 274: ...Neoview database software found a discrepancy while reading metadata information The information returned is inconsistent 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 20019 20019 An internal error occurred An invalid default state ...

Page 275: ...ist Cause The utility subsystem that reads and maintains metadata could not find the requested HP Neoview database object A possible cause is that the catalog schema or object name is misspelled in the request Neoview database objects can be catalogs schemas tables trigger temporary tables stored procedures indexes or MP aliases Effect The operation fails Recovery Enter the correct name and retry ...

Page 276: ...ils Recovery Check the spelling in the request and resubmit SQL 20040 20040 An internal error occurred file name not specified while getting file label information Cause The utility subsystem that retrieves data from the file system failed because no file name was specified to the subsystem Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in r...

Page 277: ...ery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 20047 20047 An internal error occurred invalid store option Cause The utility subsystem that reads and maintains metadata encountered an unexpected value for the STORE BY option for the table Effect The operation fails Recovery Do not attempt r...

Page 278: ...pt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 20054 20054 An internal error occurred Transaction Management subsystem could not do Close on a transaction Cause The utility subsystem that sends CLI requests to SQL failed trying to clean up memory upon completion of a request Effect The operation fails Reco...

Page 279: ...invalid character position in string position length of string length value found value position is the position in the statement where the invalid character was found length is the length of the string value is the value of the invalid character Cause An invalid character was specified in a Neoview SQL identifier Effect The request fails Recovery Fix the syntax and resubmit SQL 20105 20105 An int...

Page 280: ...n internal error occurred while performing the DUP operation Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 20133 20133 A user defined transaction has been started DUP cannot be performed Cause You cannot perform the DUP operation under a user defined transac...

Page 281: ...al 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 is table or materialized view Cause You failed to define all the indexes of the index map Effect The operation fails Recovery Specify the target indexes through the index map clau...

Page 282: ...20174 An internal error occurred A valid SQLNode is expected Cause SQL detected 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 20175 20175 An internal error occurred trying to commit or rollback a transaction that does not exist Cause SQL de...

Page 283: ...QL 20182 20182 An internal error was encountered OPEN of Import Stored Procedure failed Cause SQL encountered an internal error in the stored procedure interface Effect 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 20191 20191 This operation is not supported on non...

Page 284: ...eration 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 20212 20212 Utility process is still running for DDL_LOCKS name lock name lock name identifies the name of the operation to recover Cause You attempted to recover an operation that is still running Effect The operation fails ...

Page 285: ...lity subsystem that reads and maintains the metadata could not find all the information for a trigger 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 20227 20227 The specified syntax is not supported for a hash or hash2 partitioned table or index Cause You iss...

Page 286: ...representing the user ID being converted Cause An unexpected error was returned while converting the current user ID to a user name Effect The operation fails Recovery Try adding the user name back to the system by issuing user management commands to first drop and then re create the user For more information see the Neoview User Management and Security Administration Guide If those commands do no...

Page 287: ...on fails Recovery Correct the syntax and resubmit SQL 20255 20255 An invalid partition management operation was specified for an index Only ADD DROP and MOVE requests are supported Cause You attempted a partition management request other than ADD DROP or MOVE on an index Note that the REUSE request works only with range partitioned requests Effect The operation fails Recovery Correct the syntax an...

Page 288: ...20271 SPI Error error returned from subsystem while performing an online reload operation error is the error returned subsystem is the name of the subsystem returning the error Cause An unexpected error was returned while attempting to perform a SPI operation Effect The operation fails Recovery None This is an internal error Contact your HP service provider SQL 20272 20272 Non audited tables are n...

Page 289: ...ady involved in another utility operation or a previous utility operation on the specified partition failed Effect The MODIFY utility did not process the request 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 ...

Page 290: ... is present for the partitions Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set SQL 20298 20298 The program file progname is not licensed progname is the name of the program file Cause You specified a program file that is not licensed Effect The operation fails Recovery License the specified program and resubmit SQL 20314 20314 Internal Error failed to retrieve the referenced...

Page 291: ...ness violations when loading unique indexes Effect The operation fails Recovery For unique indexes remove conflicting records from the base table and retry the populate operation For non unique indexes do not attempt recovery SQL 20340 20340 Indexes index list on table table were successfully populated index list is a comma separated list of indexes table is the name of the table Cause One or more...

Page 292: ...ut message about this condition Recovery Consult the MXTOOL HELP to get the correct syntax and resubmit SQL 20354 20354 Only a Services ID or Schema owner can use the MXTOOL operation 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 s...

Page 293: ...ct schema name and resubmit SQL 20360 20360 Object object does not exist or the Object is not valid for the current operation object is the name of the table index view or materialized view specified in the MXTOOL request Cause You specified an incorrect table index view or materialized view name Effect The operation fails Recovery Enter the correct object name and resubmit SQL 20362 20362 Error e...

Page 294: ...it SQL 20371 20371 The specified object object is not an SQL MX table view or stored procedure object is the name specified in the MXTOOL command Cause The object specified by the caller is not a table view or stored procedure Effect The operation fails Recovery Specify the correct object name and resubmit SQL 20372 20372 The resource fork is not accessible Cause The resource fork is either broken...

Page 295: ...QL 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 Effect The operation fails Recovery Remove the lock on the label and retry the operation SQL 20454 20454 Only Super Super user can perform the GOAWAY operatio...

Page 296: ...me 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 Retry with the rf option SQL 20462 20462 Option rf does not match label data fork name Use df to GOAWAY the label data fork name is the name of the data fork Cause The GOAWAY operation failed because you specified data fork name with ...

Page 297: ...e it does not exist Effect The operation fails Recovery Enter a valid schema name and resubmit the command SQL 20508 20508 Materialized view mv name does not exist mv name is a materialized view Cause The materialized view is not visible because it does not exist Effect The operation fails Recovery Enter a valid materialized view name and resubmit the command SQL 20509 20509 MVGROUP mvgroup name d...

Page 298: ...t attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 20514 20514 MVLog cleanup is not possible because no ON REQUEST materialized view is being refreshed Cause The materialized views being refreshed do not include an ON REQUEST materialized view which is a candidate for log cleanup Effect The operation fa...

Page 299: ...ent operations are running the DDL lock has to be removed Contact your HP service provider to remove the lock SQL 20522 20522 A DDL lock on materialized view mv name cannot be canceled Try to perform Refresh again or restore the materialized view mv name is the materialized view name Cause A DDL lock on the materialized view cannot be released Effect The operation fails Recovery Resubmit the REFRE...

Page 300: ...ts contact your HP service provider SQL 20527 20527 Failed to complete the task task name correctly task name is the name of a refresh task Cause The refresh operation cannot complete due to a task failure Effect The operation fails Recovery REFRESH the materialized view again first use the CANCEL option to clean up and then retry the REFRESH command If this problem persists contact your HP servic...

Page 301: ...ge about this condition SQL 20533 20533 The datatype is not supported yet Cause The refresh operation cannot complete because a failure occurred on a required internal task The clustering key for the materialized view includes a data type that is not supported Effect The operation fails Recovery Change the materialized view definition so the data type is not in the clustering key and resubmit the ...

Page 302: ...fect The operation fails Recovery REFRESH the materialized view again first use the CANCEL option to clean up and then retry the REFRESH command If the error persists contact your HP service provider SQL 20541 20541 Assertion failed in file file name at line number line number file name is the name of the source file where the assertion occurred line number is the line number in the source file wh...

Page 303: ... 385 SQL 20547 20547 File system error error number occurred while executing REPLY error number is an error originating from the file system Cause To determine the cause look up the reported error number for its associated error text Effect The operation fails Recovery For more information about file system errors see Chapter 21 page 385 SQL 20548 20548 Process create error error number occurred w...

Page 304: ...ave the correct privileges to perform the requested operation You need the insert privilege on the materialized view to refresh the materialized view To initialize the materialized view you additionally need select and delete privileges Effect The operation fails Recovery Acquire the needed privileges and retry the refresh operation If the needed privileges are unavailable ask the owner of the mat...

Page 305: ...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 privil...

Page 306: ...e to an automatically generated dial out message about this condition SQL 20566 20566 TMF error error number occurred while trying to abort a transaction error number is an error originating from the transaction management facility TMF Cause During the refresh operation an error originating from the transaction management facility occurred on an abort transaction operation Effect The operation fai...

Page 307: ...originating from the file system process name is the name of the process Cause To determine the cause look up the reported error number for its associated error text Effect The operation fails Recovery For more information about file system errors see Chapter 21 page 385 SQL 20578 20578 File system error error number occurred during WRITEREADX on process process name error number is an error origi...

Page 308: ...tion on file file name file name is the name of the partition being processed Cause During the online partition management operation the MXAUDSRV process encountered a file system error on the partition named by file name during redo processing Effect The POPULATE INDEX or MODIFY operation fails Recovery For information about file system errors see Chapter 21 page 385 SQL 20703 20703 A heap alloca...

Page 309: ...tion SQL 20707 20707 A parameter was missing or not valid in an audit fixup request process process name process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process received an invalid request from the MODIFY code This error might be caused by the use of incorrect versions of MXCMP or MXAUDSRV software Effect The MODIFY operation fails Recov...

Page 310: ...line partition management operation the MXAUDSRV process encountered an error while attempting to report an EMS event to 0 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 20712 20712 An internal error occurred during the audit fixup phase of the operati...

Page 311: ...ated dial out message about this condition SQL 20719 20719 A request with an incompatible version was made to audit fixup process process name process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process received a request from the MODIFY code with an incompatible version field The probable cause is the use of incorrect product versions of MX...

Page 312: ...ocess identifier Cause A uniqueness violation was detected during the populate index operation Effect The populate operation failed Recovery Recover the index file remove conflicting records from base table and retry the operation SQL 20725 20725 Audit fixup process process name detected an internal error process name is the MXAUDSRV process name Cause During an online partition management operati...

Page 313: ...elds from a transaction services log record Effect The POPULATE INDEX or MODIFY operation fails Recovery None For information about file system errors see Chapter 21 page 385 SQL 20730 20730 An unexpected key transform error error code occurred in audit fixup process process name error code is the returned file system number process name is the MXAUDSRV process name Cause During an online partitio...

Page 314: ...ave an object type of BT or MV cmdname is the name of the utility object name is the name of the specified object type is the object s type as found in the metadata base table BT or materialized view MV Cause You possibly specified a utility operation on a view a stored procedure or an alias for an SQL MP object The utility operation on these objects is not allowed Effect The operation fails Recov...

Page 315: ...ct The operation fails Recovery Correct the condition and resubmit SQL 20757 20757 The file specified filename is a resource fork Verify does not support operations on resource forks filename is the HP Neoview platform file name specified Cause VERIFY failed because the name of the file is a resource fork Effect The operation fails Recovery None Informational only SQL 20758 20758 Partition name is...

Page 316: ...n informational message Recovery Use FIXUP to change the corrupt bit to correct the inconsistency SQL 20762 20762 The primary extent size size1 defined on the label does not match the value size2 defined in the metadata for Guardian file file size1 is the primary extent size defined on the label size2 is the primary extent size defined in the metadata file is the name of the HP Neoview platform fi...

Page 317: ...bel does not match the record size size2 defined in the metadata for Guardian file file size1 is the record size stored in the file label size2 is the record size found in the metadata file is the name of the HP Neoview platform file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP service provider SQL 20767 20767 Th...

Page 318: ...und in the resource fork space2 is the ANSI namespace found in the metadata file is the name of the HP Neoview platform file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP service provider SQL 20771 20771 The object feature version in resource fork version1 does not match version version2 in the metadata for Guardi...

Page 319: ...ency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP service provider SQL 20776 20776 Check constraint constraint is defined in the metadata but missing from the resource fork for object object name constraint is the name of the constraint that should exist in the constraint map in the resource fork object name is the name of the object C...

Page 320: ...s found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP service provider SQL 20781 20781 The index map array is missing from the resource fork for Guardian file file file is the name of the HP Neoview platform file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP serv...

Page 321: ...me of the HP Neoview platform file name is the name of the table Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your HP service provider to perform an MXTOOL CLEANUP operation on the object 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...

Page 322: ...s the partition name defined in the metadata file is the file being verified Cause An inconsistency was found between the partition name stored in the resource fork and the partition name found in the metadata Effect None This is an informational message Recovery Contact your HP service provider SQL 20791 20791 An internal error occurred the partition list is missing from the metadata for object n...

Page 323: ...ted object type Effect The operation fails Recovery Correct the syntax and resubmit 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 name is the name of the index in the index map array being verified table is the name of the table being verified Cause VERIFY compared the list of indexes d...

Page 324: ...oview platform file name 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 Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message about this condition SQL 20806 20806 The problem name flag is set for ...

Page 325: ...essage VERIFY found a problem that needs attention Recovery Contact your HP service provider 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 proble...

Page 326: ...e FIXUP utility on the remote segment SQL 20859 20859 An internal FIXUP error occurred Cause An internal error occurred 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 20861 20861 The corrupt bit has been reset for only local partitions of file name Please exe...

Page 327: ...DATA on a materialized view that has a refresh type other than ON REQUEST Only the refresh type ON REQUEST is allowed by PURGEDATA for a materialized view Effect The operation fails Recovery None The PURGEDATA utility cannot purge the specified materialized view specified SQL 20992 20992 Materialized View name is a hash2 partitioned object PURGEDATA does not allow individual or sets partitions to ...

Page 328: ...is the specified table name Cause The specified table does not exist Effect The operation fails Recovery Specify an existing table and resubmit the command SQL 21007 21007 A user defined transaction has been started TRANSFORM cannot be performed Cause You already started a user defined transaction Effect The operation fails Recovery Close the user defined transaction SQL 21008 21008 An internal pr...

Page 329: ...covery Specify an existing materialized view and resubmit the command SQL 21013 21013 TRANSFORM cannot be performed on a range partitioned object Cause The specified table materialized view or index is range partitioned Effect The operation fails Recovery Specify an object which is not range partitioned SQL 23001 23001 servername An error occurred while instantiating class name servername is the n...

Page 330: ...peration 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 2301 1 23011 servername An unexpected XML tag was found xml_tag servername is the name of the server program that issued the error xml_tag is the XML tag that could not be identified Cause servername discovered an XML tag th...

Page 331: ... 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 23016 23016 servername Formatted file error was encountered description servername is the name of the server program that issued the error description contains detailed information about the formatted file in error Cause The formatt...

Page 332: ...server program that issued the error object name is the name of the missing HP Neoview database object Cause An expected Neoview database object is not on the target system Effect The operation fails Recovery Correct the target system and resubmit SQL 23022 23022 Error occurred for partition file name when attempting to set the statistics metadata name is the name of the partition in error Cause T...

Page 333: ...DAP port number Cause You specified a negative number as the port number when configuring the interface with an external directory server Effect The operation fails Recovery Correct the syntax and resubmit 24004 24004 Invalid LDAP version Cause You specified an invalid LDAP version when configuring the interface with an external directory server Permissible values are 2 and 3 Effect The operation ...

Page 334: ...ed Effect This message is currently not used Recovery This message is currently not used 24010 24010 The LDAP search Distinguished Name is not allowed to be null Cause You specified a NULL value for the SearchUserDN attribute when configuring the interface with an external directory server Effect The operation fails Recovery Correct the syntax and resubmit 2401 1 24011 The LDAP search Distinguishe...

Page 335: ...not possible to delete the specified role 24016 24016 The LDAP port number exceeds the maximum port number Cause You specified a port number greater than 65535 Effect The operation fails Recovery Correct the syntax and resubmit 24017 24017 Failed to delete the Neoview role The role does not exist Cause You tried to delete a role but no such role was defined on Neoview Effect The operation does not...

Page 336: ...contact HP Support for help in determining whether an internal software error occurred 24023 24023 Failed to grant the Neoview role to the database user The user does not exist Cause You tried to register a remote database user on the Neoview platform but that user does not exist on the external directory server Effect The operation fails Recovery Verify that the name you supplied to the ADDUSER c...

Page 337: ...users or owns objects in the database Effect The operation fails Recovery Revoke the role from all users who currently have it drop all objects owned by the role then delete the role 24033 24033 Failed to get a list of Neoview roles Cause The operating system returned an unexpected error Effect The operation fails Recovery Please report this error to HP Support 24034 24034 Internal Error Failed to...

Page 338: ...ssage is currently not used 24041 24041 The number of passwords to be remembered must be a value from 0 through 60 Cause This message is currently not used Effect This message is currently not used Recovery This message is currently not used 24042 24042 The maximum password length must be a value from 8 through 64 characters Cause This message is currently not used Effect This message is currently...

Page 339: ...ery Choose a shorter name 24049 24049 The user name exceeds maximum length of 128 characters Cause You specified a database username that is too long The maximum length is 128 characters Effect The operation fails Recovery Choose a shorter name 24050 24050 Failed to add the LDAP configuration entry The entry exists already Cause You tried to add a new LDAP server configuration but a server having ...

Page 340: ...to list the roles assigned to a user but no such user is registered on the Neoview platform Effect The operation fails Recovery Check your typing of the user name Reissue the command specifying an existing user 24056 24056 Failed to delete the user entry The entry does not exist Cause You tried to remove a user from the Neoview platform but no such user is registered Effect The operation fails Rec...

Page 341: ...n fails Recovery Specify a different role name 24073 24073 Failed to add the user The user already exists Cause You tried to add a user on the Neoview platform but the user already exists Effect The user is already registered so the command has no effect Recovery If you meant to specify a different user change the user name and resubmit the command 24074 24074 Failed to add the Neoview role The ro...

Page 342: ...configuration entry Cause The operation failed because of an internal error Effect The operation fails Recovery Please report this error to HP Support 24083 24083 Failed to delete the LDAP configuration entry Cause The operation failed because of an internal error Effect The operation fails Recovery Please report this error to HP Support 24084 24084 Failed to alter the LDAP configuration entry Cau...

Page 343: ...Effect The operation fails Recovery Correct your syntax and resubmit the request 24090 24090 Mandatory parameter parameter was not defined Cause You omitted a mandatory parameter in the configuration description file Effect The operation fails Recovery Correct your syntax and resubmit the request 24091 24091 Cannot specify both UserIdentifier and UniqueIdentifier Cause You included these two mutua...

Page 344: ... Support 24097 24097 Cannot delete the LDAP default configuration Cause You tried to delete the LDAP server configuration called default It is not permissible to delete this configuration entry Effect The operation fails Recovery None This operation is not permitted 24098 24098 Configuration parameter string string must be defined in the default configuration Cause You attempted to define in the c...

Page 345: ...at the request might have failed You were not authorized to give the command No such user or role exists A parameter in the command was invalid A server side problem prevented the request from being completed Effect The operation fails Recovery Check your typing and resubmit the request 24103 24103 Role name is missing ROLE prefix Cause You specified an unqualified role name to a command that requ...

Page 346: ...re special users that can only have one role Effect The role is not granted Recovery Create another database user and grant the role combination desired 241 14 24114 Invalid object name Cause Internal error Effect Internal error Recovery Contact HP Support 241 15 24115 Internal error user role management request when no transaction was active Cause Internal error Effect Internal error Recovery Con...

Page 347: ...fect Internal error Recovery Contact HP Support 24122 24122 Delete User failed Cause Internal error Effect Internal error Recovery Contact HP Support 24123 24123 Grant Role failed Cause Internal error Effect Internal error Recovery Contact HP Support 24124 24124 Revoke Role failed Cause Internal error Effect Internal error Recovery Contact HP Support 24125 24125 Set Role failed Cause Internal erro...

Page 348: ...mit command 24130 24130 Invalid option for this user Cause You specified an option that is not relevant for the user provided Effect Operation is not successful Recovery Determine correct user or operation and resubmit command 24131 24131 Role cannot be altered Cause You specified a role that cannot be altered Only platform roles and the database roles ROLE DBA ROLE MGR and ROLE SECMGR may be alte...

Page 349: ...ur password 24137 24137 Platform role not allowed Cause You attempted to grant a platform role to a database user Effect The role is not granted Recovery Resubmit the command using a database role 24139 24139 New role cannot be added ROLES table failed consistency check Cause Internal error Effect Internal error Recovery Contact HP Support 349 ...

Page 350: ...350 ...

Page 351: ...started by the default compiler encounters an error Effect The CLI suppresses the generation of message 8839 Recovery Not applicable SQL 25006 25006 The following feature is only available for schemas with version feature version and higher string schema has schema version schema version feature version is the minimum version schema that can accommodate the features used by the object string is a ...

Page 352: ...e to the same non GA release as the local node Or conversely migrate the local node to a GA release that is compatible with the remote node s MXV SQL 25102 25102 Remote node node is not running a version of SQL MX software which can interoperate with other versions The SQL MX software version MXV of node is MXV1 node is the name of the affected remote node remote HP Neoview database segment MXV1 i...

Page 353: ...e nodes that need to access the schema SQL 25202 25202 Table or view object cannot be accessed on node because of a version incompatibility Its schema has version version1 node does not support schema versions lower than version2 object is the name of the affected database object node is the name of the node that detects the incompatibility version1 is the schema version of object s schema version...

Page 354: ...t The operation fails Recovery Do not explicitly use a downrev compiler to compile the query or module SQL 25205 25205 Schema schema has schema version version1 this is incompatible with the version of the compiler that executes the operation The compiler version is version2 schema is the name of a schema that is referenced by a DDL or utility operation version1 is the schema version of schema ver...

Page 355: ...ported system schema version for node2 Cause The affected operation needs to access system schema tables with a downrev system schema version This error can be reported for any type of operation query compilation query execution or DDL and utility operations Effect The operation fails Recovery Upgrade the system schema on the affected node to a compatible version SQL 25208 25208 The system schema ...

Page 356: ...accessed only by a node with SQL MX software version MXV version1 the MXV of node is MXV1 object is the affected table or view version1 is the schema version of object s schema node is the node that executes the query MXV1 is the MXV of the node that executes the query Cause The affected node runs a General Availability GA release of the HP Neoview database software and is incompatible with the af...

Page 357: ...cessing node runs a non GA release of the HP Neoview database software and is compatible only with system schemas created by its own version Effect The operation fails Recovery Upgrade or downgrade the accessing node to a Neoview database software release that is compatible with the affected system schema version Or conversely correct the system schema and reinitialize SQL on the affected node SQL...

Page 358: ...est schema version of the involved tables or views is higher than the lowest SQL MX software version MXV of the involved nodes Cause A mixed version query was detected by the compiler for example a query where the MXV of one or more of the involved nodes is earlier than the MXV of one or more of the involved database objects Such a query cannot be compiled Effect The operation fails Recovery Inves...

Page 359: ...The operation fails Recovery Recompile the module with a supported version compiler SQL 25303 25303 The query plan version is version1 node node does not support query plan versions higher than version2 version1 is the plan version of the affected query node is the name of the node that detects the incompatibility version2 is the MXV of the node that detects the incompatibility Cause You attempted...

Page 360: ...the module version of module node is the node that attempts to load the module MXV1 is the MXV of the affected node 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 mod...

Page 361: ...XV 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 is the ANSI name of the target catalog It must be visible on the local node node is a remote node where catalog visibility is required Cause ...

Page 362: ...ware attempts to recover automatically SQL 25404 25404 Catalogs catalog1 and catalog2 must have identical visibility catalog1 and catalog2 are ANSI catalog names Cause You attempted to establish a relationship between catalog1 and catalog2 which have different visibility Effect The operation fails Recovery Correct the error and retry the operation SQL 25405 25405 Catalog catalog cannot be created ...

Page 363: ...5420 Node node could not be accessed File system error number node is the remote node that is required implicitly or explicitly by a replication operation number is the file system error that resulted from the attempt to access node Cause A replication operation required access to a remote node that cannot be accessed because of the reported file system error Effect The operation fails Recovery Fo...

Page 364: ... is the ANSI name of the target catalog Cause The target node of an UNREPLICATE SCHEMA operation holds the only automatic reference for the affected schema catalog Effect The operation fails Recovery Correct the error and resubmit SQL 25426 25426 Volume volume could not be accessed File system error number volume is the name of a volume that is required implicitly or explicitly by the operation Th...

Page 365: ...very Use the CASCADE option on REGISTER CATALOG SQL 25429 25429 Catalog catalog cannot be unregistered from node node because it is the only catalog reference that has an automatic replication rule catalog is the ANSI name of the target catalog for the UNREGISTER CATALOG command node is the name of the target node for the UNREGISTER CATALOG command Cause An UNREGISTER CATALOG operation attempted t...

Page 366: ...umbers is reserved for JDBC driver error messages For complete information about JDBC driver error messages see the Neoview JDBC Type 4 Driver Programmer s Reference 366 Versioning Distribution and JDBC Messages 25000 Through 25499 and 29000 Through 29399 ...

Page 367: ...specified incorrect number of command line options when launching Neoview Command Interface Effect Unable to login to the Neoview Command Interface Recovery Retry launching the Neoview Command Interface with the correct options Issue hpnci help to see the list of valid options 29403 Could not find the script file specified Cause You specified an invalid non existing file in the script option while...

Page 368: ... see the Neoview Command Interface Guide 29409 SHOW command must have an option specified Cause You did not specify an option for the SHOW command Effect The SHOW command fails to execute Recovery Retry the SHOW command with an appropriate option For more information see the Neoview Command Interface Guide 29410 Could not find the file specified Cause You specified an invalid non existing filename...

Page 369: ...tables found Cause There are no tables present in the current schema If you specified a pattern there are no tables matching the specified pattern Effect None Recovery Verify if you are in the correct schema by issuing an ENV or a SHOW SCHEMA command 29418 No schemas found Cause There are no schemas present in the catalog If you specified a pattern there are no schemas matching the specified patte...

Page 370: ...dures matching the specified pattern Effect None Recovery Verify if you are in the correct schema by issuing an ENV or a SHOW SCHEMA command 29424 No indexes present for object name Cause object name refers to a table or a materialized view name There are no indexes present on the specified table or the materialized view Effect None Recovery Not applicable 29425 No materialized views present for o...

Page 371: ...ration fails Recovery To view the list of the prepared statements in the current session execute the SHOW PREPARED command 29432 Invalid number of parameters for prepared statement t stmt name Cause stmt name refers to the statement name used in the PREPARE statement You specified an incorrect number of parameters for executing a prepared statement Effect Executing the prepared statement fails Rec...

Page 372: ...d commands is greater than 100 or the total number of commands if the number of entered commands is less than or equal to 100 in the history buffer of the current session Recovery Retry the command by using a value that does not exceed 100 29438 The history buffer is empty Cause You executed history as the first command in the Neoview Command Interface and there are no previously executed commands...

Page 373: ... operation has been cancelled and the connection to the database has been lost Please connect to the database by using connect reconnect command Cause You cancelled a query by pressing Ctrl C on the console when a query was still executing Effect Connection to the database is lost Recovery Establish a new connection to the Neoview Platform by issuing a CONNECT RECONNECT command 29446 Number of con...

Page 374: ...plicable Effect Not applicable Recovery Please contact support personnel 29452 Invalid value specified for property hpnci prun maxconn Cause You specified an invalid value for the property hpnci prun maxconn Effect The PRUN command does not use the value you specified for the maximum number of connections Recovery Retry launching Neoview Command Interface by specifying a valid value for the proper...

Page 375: ...ns Cause You specified an invalid directory for the logs directory in PRUN command Effect The PRUN command fails to execute Recovery Retry the PRUN command by specifying a valid directory 29460 A syntax error occurred at or before Cause You used incorrect syntax in the interface command Effect The interface command fails to execute Recovery Correct the syntax and retry the interface command For mo...

Page 376: ...to the session prompt Recovery Retry executing the script file by reducing the depth of nested obey Ensure that there are no loops in your nested obey calls For example if you have files A sql B sql and C sql if you obey file A which obeys file B which obeys file C be sure that file C doesn t obey file A 29469 Unable to align display for multibyte characters Try relaunching NCI with Djava awt head...

Page 377: ...em that is misconfigured Effect The allow and deny operations on access to dump files fails Recovery Please contact the support personnel to fix this problem 29551 Missing Core File Pattern Cause You tried to execute ALLOW DENY ACCESS TO DUMPFILEScommand on a Neoview system that is misconfigured Effect The allow and deny operations on access to dump files fails Recovery Please contact the support ...

Page 378: ...378 ...

Page 379: ...0004 The dimension of the arrays composing the rowset must be greater than zero A value of num was given num is the rowset size Cause You specified a value for rowset arrays that is invalid It must be greater than 0 zero 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 condi...

Page 380: ...ed dial out message about this condition SQL 30014 30014 Host variable used to set input size of rowset is not of type short int or long Cause You specified a hostvar for the input size of the rowset that is not of type short int or long Effect The operation fails Recovery Do not attempt recovery HP support will perform recovery operations in response to an automatically generated dial out message...

Page 381: ...s set to OFF Effect The GET DIAGNOSTICS statement fails The variable used to retrieve ROWSET_ROW_COUNT is not altered from its input state If other diagnostic statement information items are being retrieved in the same GET DIAGNOSTICS statement their output variables must also be considered invalid Recovery Do not attempt recovery HP support will perform recovery operations in response to an autom...

Page 382: ...0 Atomicity clause is not allowed on an INSERT statement from either ODBC MX or JDBC MX Cause You attempted to use a NOT ATOMIC or ATOMIC clause on an INSERT statement from either ODBC MX or JDBC MX Effect The PREPARE of the INSERT 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 3...

Page 383: ...You attempted to use NOT ATOMIC inserts on a table that is the subject table of at least one AFTER trigger Effect Compilation of the INSERT operation fails Recovery Contact the GMCSC SQL 30035 30035 All rows in the NOT ATOMIC INSERT raised an error No rows have been inserted Cause All rows in the NOT ATOMIC inserts raised nonfatal errors Effect No rows are inserted This is a warning message only R...

Page 384: ...384 ...

Page 385: ...s process cannot accept a command because the receiving file is not opened correctly 0007 The operation was successful examine message control word for additional status 0008 A read through a locked record was successful 0009 The new record or file could not be created because a file by that name or a record with that key already exists 0010 The file is not in the directory or the record is not in...

Page 386: ...e transaction or open lock unit limit has been reached 0035 Unable to lock physical memory not enough memory available 0036 Attempt to perform operation on wrong type of system 0038 The server process received a request with a sync ID older than the set of saved replies 0039 The operation timed out A command did not complete within the time specified by its time limit parameter 0040 A checksum err...

Page 387: ...g 0076 Transaction identifier is invalid or obsolete 0078 A transaction attempted to update or delete a record which it has not previously locked 0079 Invalid operation on protected file or non protected disk 0080 Operation is not valid for a transaction which still has non blocking I Os outstanding on a disk or process file 0081 Transaction Services not running on this segment or on the remote se...

Page 388: ...rrun error hardware problem 0121 Request aborted due to possible data loss caused by reset of circuit bus sequence error or Data Access Manager process takeover 0122 Subdevice is busy 0123 A line reset is in progress loss of data is possible 0124 Illegal disk address requested or formatting error occurred 0130 Write check error from disk internal circuitry fault 0131 Seek incomplete from disk cyli...

Page 389: ... allowable NAKs received transmission error invalid message control word on WRITE or invalid request ID 0173 WACK received or bus frame aborted 0174 Incorrect alternating ACK received or command rejected 0175 Poll sequence ended with no responder 0176 Text overrun insufficient buffer space for data transfer 0177 No address list specified 0178 Application buffer is incorrect control request pending...

Page 390: ... the same unit number path error 0225 Node power failed then restored 0230 Controller power failed then restored 0231 Access is denied due to error in communication with the security monitor 0232 Error in call to SERVERCLASS_SEND_ 0233 Network line handler error operation not started Ownership switch was performed 0240 Network error operation not started 0241 External cluster bypass error operatio...

Page 391: ...d 0561 The size of an output buffer was too small 0563 The operation is not supported for this file type 0564 A malformed request was denied 0565 This reply is malformed or not appropriate 0566 The define used is incompatible for use with target system s TOS version 0567 An out of sequence message was received 0570 A duplicate message was received 0571 Message cannot be accepted because sequence n...

Page 392: ... Number of the data block on disk 0704 Generated by the Data Access Manager process when it receives a Transaction Services Transaction Log Disk request type message and the Data Access Manager process is not an transaction log disk 0705 Generated by the Data Access Manager process when it receives a request message that is inappropriate for a Transaction Log Data Access Manager Process 0706 Gener...

Page 393: ...supplied row is too long Also the disk process might have encountered a bad column in a stored row or a value in an update on a row that would change the length of a VARCHAR column in an entry sequenced table 1031 The SQL row description is inconsistent 1032 The SQL key column description is inconsistent or the specified key is too long 1033 SQL internal error The requested operation has failed be...

Page 394: ...66 Internal error Occurred in the file system or Data Access Manager process OPEN protocol 1067 SQL internal error 1068 SQL internal error 1069 The process s program file is not licensed 1070 SQL internal error 1071 SQL internal error 1072 SQL internal error 1073 Internal error SQL file system procedure 1074 A FETCH was attempted following a FETCH that failed This left the cursor in an undefined p...

Page 395: ...ding underlying table values are inconsistent 1099 An operand was truncated during assignment of character data 1100 Truncation was needed but prohibited during assignment of character data 1101 An overflow occurred during expression evaluation 1102 An underflow occurred during expression evaluation 1103 An SQL column of type DECIMAL contained values that are not digits 1104 Unable to assign a neg...

Page 396: ...02 Server does not support this dialect 3503 Server does not support this request type 3504 Server version is not current 3505 Operation not permitted Process does not have the appropriate privileges or permissions to perform the requested operation 4001 No such file or directory 4002 No such process or table entry 4003 Interrupted system call 4004 I O error 4005 No such device or address 4006 Arg...

Page 397: ...on address required 4105 Message too long 4106 Protocol wrong type for socket 4107 Protocol not available 4108 Protocol not supported 4109 Socket type not supported 4110 Operation not supported on socket 4111 Protocol family not supported 4112 Address family not supported 4113 Address already in use 4114 Can t assign requested address 4115 Network is down 4116 Network is unreachable 4117 Network d...

Page 398: ...stem error occurred 4208 Illegal operation attempted on file descriptor 4209 Logic error 4210 Current working directory or filename longer than PATH_MAX 4211 An error occurred during invocation of a DEFINE procedure 4212 A cross node exec has been attempted while holding a semaphore 4213 An invalid message tag had been encountered when setlocale_from_msg function was called There was no correspond...

Page 399: ...ction Clients should also check their auto commit settings 766 1376 The maximum number of opens for a single file or partition has been reached device type 3 Cause A file or partition open request would exceed the maximum number of opens for a single file or partition on a volume Effect The procedure sets the error code and returns without performing the requested operation Recovery Wait then try ...

Page 400: ......

Reviews:

No comments

Brands by name

Popular brands

Load more brands