manualshive.com logo in svg

HP NonStop SQL/MX, Messages Manual

Share
Download
HP NonStop SQL/MX Messages Manual Download Page 616

Versioning and Distribution Messages (25000 
through 25399)

HP NonStop SQL/MX Messages Manual — 640324-001

19- 2

SQL 25004

where,

object

  is the type and name of the affected database object.

version1

  is the target version of the upgrade schema operation.

component 

is the software component that detects the situation. It is either 

compiler

 or 

local node

.

version2

  is the SQL/MX software version (MXV) of 

component

.

Cause. An operation attempted to access an object in a schema that is currently being 
upgraded to an incompatible version. The affected object either does not exist at all or 
has been upgraded to an incompatible version.

Effect. The operation fails.

Recovery. Retry the affected operation, with software that is compatible with a version 

version2

 

schema, to determine if the object exists or not

SQL 25005

where,

object

 is the type and name of the affected database object.

version1

  is the source version of the downgrade schema operation.

component 

is the software component that detects the situation. It is either 

“

compiler

” or 

“local node”

.

version2

  is the MXV of 

component

.

Cause. An operation attempted to access an object in a schema that is currently being 
downgraded from an incompatible version. The affected object either does not exist or 
has not yet been downgraded from the incompatible version.

Effect. The operation fails.

Recovery. Wait until the downgrade schema operation is finished and retry the 
affected operation.

25004 

object

 does not exist or cannot be accessed because of 

a version incompatibility. Its schema is currently being 
upgraded to version 

version1

; the 

component

 cannot access 

schemas with versions higher than 

version2

.

25005 

object

 does not exist or cannot be accessed because of 

a version incompatibility. Its schema is currently being 
downgraded from version 

version1

; the 

component

 cannot access 

schemas with versions higher than 

version2

.

Summary of Contents for NonStop SQL/MX

Page 1: ...ent system and its associated subsystems Product Version NonStop SQL MX Release 3 0 Supported Release Version Updates RVUs This publication supports J06 11 and all subsequent J series RVUs and H06 22 and all subsequent H series RVUs until otherwise indicated by its replacement publications Part Number Published 640324 001 February 2011 ...

Page 2: ...Document History Part Number Product Version Published 640324 001 NonStop SQL MX Release 3 0 February 2011 ...

Page 3: ...d Motif 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 thi...

Page 4: ......

Page 5: ...nged Information v About This Manual xi Audience xi Related Documentation xi Notation Conventions xiv HP Encourages Your Comments xvi 1 Message Handling Viewing SQL MX Messages 1 1 Non SQLCODE Error Messages 1 2 Messages That Report a Guardian File System Error 1 2 SQLSTATE and SQLCODE 1 3 Contacting Your Service Provider 1 3 Process Control Procedure Errors 1 4 ...

Page 6: ...ser and Compilation Messages 3000 through 3999 6 Binder and Compilation Messages 4000 through 4999 7 Normalizer Messages 5000 through 5999 8 Optimizer Messages 6000 through 6999 9 Generator Messages 7000 through 7999 10 Executor Messages 8000 through 8999 11 UPDATE STATISTICS Messages 9200 through 9221 12 Executor Sort and Scratch File I O Messages 10000 through 10199 Executor Sort Messages 12 1 S...

Page 7: ...through 16999 17 Internal Stored Procedures Messages 19000 through 19999 18 Utility Messages 20000 through 23099 19 Versioning and Distribution Messages 25000 through 25399 Distribution Messages 25400 25499 19 25 JDBC Driver Error Messages 29000 29999 19 32 20 Rowsets Messages 30000 through 30999 21 SQLSTATE Values Returned by NonStop SQL MX SQLSTATE and SQLCODE Considerations 21 1 SQLSTATE Values...

Page 8: ...Contents HP NonStop SQL MX Messages Manual 640324 001 iv ...

Page 9: ...Version Updates RVUs This publication supports J06 11 and all subsequent J series RVUs and H06 22 and all subsequent H series RVUs until otherwise indicated by its replacement publications Document History New and Changed Information Changes to the 640324 001 manual Updated the following error messages SQL 1004 SQL 1020 SQL 1055 SQL 1080 SQL 1085 SQL 1087 SQL 1098 SQL 1112 SQL 1132 SQL 1140 Part N...

Page 10: ...239 SQL 1263 SQL 1270 and SQL 1271 SQL 1500 through SQL 1503 SQL 2011 through SQL 2020 SQL 2027 and SQL 2028 SQL 2033 and SQL 2034 SQL 2055 SQL 2984 SQL 3008 SQL 3014 SQL 4082 SQL 4129 SQL 4161 SQL 4320 SQL 6003 SQL 6008 SQL 8402 SQL 8411 SQL 8419 SQL 8834 SQL 8837 SQL 9215 SQL 10003 through SQL 10013 SQL 10015 through SQL 10024 SQL 10026 through SQL 10029 ...

Page 11: ...SQL 11101 through SQL 11111 SQL 11209 SQL 11242 through SQL 11244 SQL 19020 SQL 20011 SQL 20025 SQL 20037 SQL 20123 SQL 20127 SQL 20137 SQL 20142 SQL 20149 SQL 20154 and SQL 20155 SQL 20176 SQL 20354 SQL 20360 SQL 20371 SQL 20733 SQL 20752 SQL 20755 SQL 20759 SQL 20779 SQL 20795 SQL 23001 through SQL 23003 SQL 23007 SQL 23011 through SQL 23020 ...

Page 12: ...25216 SQL 25302 and SQL 25303 SQL 25308 SQL 25310 Added the following error messages SQL 1154 SQL 1158 SQL 1159 SQL 1165 SQL 1168 SQL 1174 SQL 1189 SQL 1193 and SQL 1195 SQL 1249 SQL 1276 SQL 1277 SQL 1278 SQL 1289 SQL 1295 SQL 1311 and SQL 1312 SQL 1401 SQL 1506 SQL 2235 SQL 3218 SQL 3409 SQL 3415 SQL 4193 SQL 4195 and SQL 4196 ...

Page 13: ... SQL 6004 SQL 8019 SQL 8022 SQL 8401 SQL 8432 and SQL 8433 SQL 8581 SQL 8598 SQL 8887 SQL 8889 SQL 8900 SQL 8916 and SQL 8917 SQL 10025 SQL 10030 through SQL 10043 SQL 10045 and SQL 10046 SQL 10051 SQL 10101 through SQL 10119 SQL 10130 through SQL 10141 SQL 10150 through SQL 10153 SQL 11002 SQL 11046 SQL 11049 SQL 15001 SQL 15039 SQL 19022 SQL 20339 and SQL 20340 ...

Page 14: ...SQL 25006 SQL 25007 SQL 25209 SQL 25220 through SQL 25222 SQL 25250 through SQL 25268 SQL 30026 through SQL 30029 SQL 30035 SQL 30037 Added SQLSTATE 21000 on page 21 45 Removed SQL message 2054 Changed SQL message 8910 to 8916 and updated its description on page 10 53 Changed SQL message 8911 to 8917 and updated its description on page 10 54 Removed SQL message 20240 Removed SQL messages from 2027...

Page 15: ...part of the SQL MX library of manuals which includes Introductory Guides SQL MX Comparison Guide for SQL MP Users Describes SQL differences between NonStop SQL MP and NonStop SQL MX SQL MX Quick Start Describes basic techniques for using SQL in the SQL MX conversational interface MXCI Includes information about installing the sample database Reference Manuals SQL MX Reference Manual Describes the ...

Page 16: ...f NonStop SQL MX NonStop NS Series Database Migration Guide Describes how to migrate NonStop SQL MX NonStop SQL MP and Enscribe databases and applications to HP Integrity NonStop NS series systems Data Management Guides SQL MX Data Mining Guide Describes the SQL MX data structures and operations to carry out the knowledge discovery process SQL MX Report Writer Guide Describes how to produce format...

Page 17: ...rence Online Help Overview and reference entries from the SQL MX Reference Manual SQL MX Messages Online Help Individual messages grouped by source from the SQL MX Messages Manual SQL MX Glossary Online Help Terms and definitions from the SQL MX Glossary NSM web Help Context sensitive help topics that describe how to use the NSM web management tool Visual Query Planner Help Context sensitive help ...

Page 18: ...ems that you supply Items not enclosed in brackets are required For example file name Punctuation Parentheses commas semicolons and other symbols not previously described must be typed as shown For example error NEXTFILENAME file name LISTOPENS SU process name su name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown ...

Page 19: ...actly as shown For example Backup Up lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned For example p register process name Brackets Brackets enclose items that are sometimes but not always displayed For example Event number number Subject first subject value A group of items enclosed in brackets is a list of all possible items that can...

Page 20: ...register Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition Change bars are vertical rules placed in the right margin of changed portions of text figures tables examples and so on Change bars highlight new or revised information For example The message types specified in the REPORT clause are different in the CO...

Page 21: ...d the LOG command to request them The format of an SQL MX error is ERROR followed by the error number in brackets and the descriptive text Use the error number shown to find information about a particular error in this manual For example information for SQL MX error 1125 can be found under SQL 1125 Messages and events are listed in this manual in numeric order broken down by the component that pro...

Page 22: ...ocess that generates the error followed by an error number and a descriptive text Messages That Report a Guardian File System Error For more information about messages that report a Guardian file system error see the Guardian Procedure Errors and Messages Manual Information about the error can also be found using the TACL error command This command can be either used directly from TACL for example...

Page 23: ...DE values with negative numbers signify errors SQLCODE values with positive numbers other than 0 successful completion or 100 no data was found signify warning messages NonStop SQL MX identifies all messages by their unsigned SQLCODE value and their calculated SQLSTATE value The SQLCODE is used to calculate the SQLSTATE value for all SQL MX messages other than those for which an ANSI SQL 92 SQLSTA...

Page 24: ...part of NonStop systems make calls to these procedures and in some cases must report procedure errors to the user When a process control procedure error is reported as part of a message such as a message to the Application log the name of the procedure is normally included in the message An exception is when a PROCESS_CREATE_ error might be referred to as a process creation error See the Guardian ...

Page 25: ...M t WHERE SQL MX returns warning 100 to indicate that zero rows satisfied the predicate and zero rows were affected In embedded SQL MX on a cursor FETCH SQL MX returns this warning to indicate that it has reached the end of rows Effect You will not be able to get any more rows from this cursor or SELECT statement Recovery This is an informational message Start a new cursor for a new read 100 The n...

Page 26: ...General Messages 0 through 999 HP NonStop SQL MX Messages Manual 640324 001 2 2 ...

Page 27: ...page 1 3 SQL 1002 Where catalog is the ANSI name of the target catalog Where node is the node where the process executes Cause The catalog is not visible on the local node either because it does not exist or because it exists elsewhere on the network but has not been registered on the local node Effect The operation fails Recovery Enter a valid catalog name or register the catalog on the node indi...

Page 28: ...t specified a table name Effect The operation fails Recovery Check that an object object name exists If you did not fully qualify the name check that the defaults generate the correct fully qualified name and resubmit SQL 1005 Where constraint name is the name of a column constraint or table constraint Cause The ALTER TABLE statement you attempted requires the existence of a constraint named const...

Page 29: ...n ID in a CREATE SCHEMA statement does not represent a valid Guardian user Effect The operation fails Recovery Correct the user name and resubmit SQL 1009 Where column name is an SQL identifier Cause The table that is referenced does not have a column with this name Effect The operation fails Recovery Replace either the name of the table or the name of the column whichever is incorrect and resubmi...

Page 30: ...w they were granted If you perform a grant to another user who then performs a grant to a third user you cannot revoke privileges to the second user until that user revokes their privileges to the third user Effect NonStop SQL MX did not revoke the privileges Recovery Make sure that the dependent privileges from the user whose privileges you want to revoke are revoked first SQL 1015 Cause You atte...

Page 31: ...perations on a database schema are restricted to the schema owner only operations on a database object are restricted to the schema owner and the object owner In all cases the local super ID is authorized to perform DDL and utility operations Additionally invalid remote password for the user could trigger this error Verify the remote password for the user and resubmit SQL 1019 Where table name is ...

Page 32: ...e of an SQL MX schema Cause You attempted to create a schema in a catalog that already contains a schema with that name Effect The operation fails Recovery If you did not use a fully qualified name check that the default generates the correct catalog name Retry the request specifying a schema that does not already exist SQL 1023 Cause You attempted to create a schema with the authorization ID of a...

Page 33: ...RESTRICT Effect NonStop SQL MX does not perform the operation Recovery For DROP statements that support the CASCADE drop behavior you can reissue the statement specifying CASCADE For other DROP statements you must first drop each of the dependent objects then drop the object SQL 1026 Cause An attempt was made to drop a schema by someone other than its owner or the super ID Effect No SQL objects ar...

Page 34: ...d resubmit the statement or resubmit the drop statement using the CASCADE option SQL 1029 Where object name is the name supplied in a CREATE statement Cause This error can result from various CREATE statements See the accompanying error messages to determine the cause Effect The object is not created Recovery Apply the recovery of the accompanying error messages SQL 1030 Where Guardian name is the...

Page 35: ...f the accompanying error message SQL 1035 Where catalog name is the name of an SQL MX catalog Cause You attempted to create a catalog using the name of an already existing catalog Effect The operation fails Recovery None if this is the desired catalog Otherwise correct the catalog name and resubmit SQL 1036 Cause An attempt was made to drop SQL by a user who is not the super ID Effect The operatio...

Page 36: ...mpted to drop SQL while one or more user created catalogs existed Effect The operation fails Recovery You must drop all user created catalogs before dropping SQL SQL 1039 Cause See the accompanying error message for the cause Effect NonStop SQL MX does not drop SQL Recovery Apply the recovery of the accompanying error message SQL 1040 Cause An ALTER TABLE statement was issued naming a table that i...

Page 37: ... assigned the same constraint name to two constraints on the same table Constraint names must be unique among all the constraints for a table Effect The operation fails Recovery Make all the constraint names for the table unique Use SHOWDDL to see the names of existing constraints SQL 1044 Where constraint name is the name of a column constraint or table constraint Cause The columns that constrain...

Page 38: ...he referenced table SQL 1045 Cause The referential constraint is referencing the unique constraint that is declared as deferrable This is an internal error Effect The operation fails Recovery Check that the referential constraint references a unique constraint that is not declared deferrable Contact your service provider 1045 The unique constraint cannot be used because it is deferrable ...

Page 39: ...ed unless you use the CASCADE option on the DROP statement Effect The operation fails Recovery To drop the object and all its dependent objects you can either drop each of the dependent objects using individual DROP statements before dropping the object itself or use the CASCADE clause on the DROP statement for the object SQL 1048 Cause Drop behavior CASCADE was specified on a DROP statement that ...

Page 40: ... object name is the name of the object for which you have insufficient privileges Cause You have insufficient privileges to create a view or a trigger Effect The operation fails Recovery See the SQL MX Reference Manual for the required security needed to create a view or trigger SQL 1052 Cause An ALTER TABLE statement with DROP CONSTRAINT specified a name that is not the name of a constraint on th...

Page 41: ...specified for the index to create Cause You attempted to create an index with the name of an index that already exists on the specified table Effect The index is not created Recovery Choose a different name for the index and reissue the statement SQL 1055 Where object name is the name of an existing SQL MX object Cause You attempted to create an object with a name that is already in use for a tabl...

Page 42: ...unique lock name which was not generated Effect The operation fails Recovery Specify a unique lock name and resubmit SQL 1059 Where constraint name is the name of a column constraint or table constraint Cause You attempted to drop a table that has a referential constraint or a check constraint that refers to another table Effect NonStop SQL MX does not drop the table Recovery Either drop all const...

Page 43: ...SQL 1063 Where index name is the name of an SQL MX index Cause An attempt was made to drop an index that is part of the SQL MX metadata Effect The operation fails Recovery None SQL 1064 Where tablename is the name of an SQL MX 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 encountere...

Page 44: ...L 1069 Where schema name is the name of an SQL MX schema Cause See the accompanying error message for the cause of the problem Effect The operation fails Recovery Apply the recovery action from the accompanying error message SQL 1070 Where object name is the name of the SQL MX object Where error number is the file system error number Cause An attempt to create object object name resulted in file s...

Page 45: ...me 2 is the name of the foreign key constraint Cause You created a referential constraint that references a unique constraint that has been disabled This is an internal error Effect The operation fails Recovery Create the referential constraint that references a unique constraint that has not been disabled SQL 1073 Cause You attempted to initialize NonStop SQL MX but you are not the super ID Only ...

Page 46: ...ble to find it in table name Effect The operation fails Recovery None Contact your service provider SQL 1078 Where location name is a name specified in a LOCATION clause Cause An invalid name was supplied in a LOCATION clause Effect The operation fails Recovery See the SQL MX Reference Manual for limitations on names allowed in the LOCATION clause Correct the name and resubmit SQL 1079 Cause See t...

Page 47: ...being performed on the base table or because data could not be loaded into the index by the Call level interface CLI Effect The operation fails Recovery Determine the cause of the CLI failure and resubmit SQL 1082 Where constraint name is the name of a column or table constraint Cause The constraint validation failed either because a concurrent operation was being performed on the table or on the ...

Page 48: ...olumn and resubmit SQL 1085 Cause The length of the primary key which is calculated by the number of primary key columns and their data types exceeds the maximum length Effect The operation fails Recovery Ensure that the key length is less than the maximum bytes allowed and resubmit If a trigger is created on a table that has a primary key with a length greater than the maximum key length error 10...

Page 49: ... resubmit SQL 1089 Cause The system generated SYSKEY column was not the last column in a CREATE INDEX statement Effect The operation fails Recovery Change the column list to place SYSKEY at the end of the list and resubmit the statement SQL 1090 Cause You attempted to create a self referencing constraint A referential constraint is self referencing if the foreign key is referencing the primary key...

Page 50: ...ecified in the partitioning key of the PARTITION BY partitioning_columns clause of a CREATE TABLE or CREATE INDEX statement is not also a member of the clustering key Effect The table or index is not created Recovery Either remove the offending column from the partitioning key specification and possibly replace it with a column that is a member of the clustering key or add the offending column to ...

Page 51: ...ach unnamed column and resubmit SQL 1100 Where table name is the ANSI name of the metadata table Cause See the accompanying error message for clarification Effect The operation fails Recovery None Contact your service provider SQL 1101 Where table name is the ANSI name of the metadata table Cause See the accompanying error message for clarification Effect The operation fails Recovery None Contact ...

Page 52: ...here column name is the name of a character type column for which a default value is specified Cause The specified default value for column name is longer than the maximum of 239 characters Effect The operation fails Recovery Correct the error and resubmit SQL 1105 Cause A CREATE TABLE LIKE statement specifies both the WITH PARTITIONS and STORE BY clause which is not allowed Effect The operation f...

Page 53: ...of columns in the query do not equal the number of columns specified for the view Effect The operation fails Recovery Specify a query statement that has a degree that matches the number of columns in the view column list and resubmit SQL 1109 Where view name is the name of the view being created Cause You used WITH CHECK OPTION in the definition of a view that is not updatable Effect The operation...

Page 54: ... Change the column list to include additional columns and reissue the statement SQL 1114 Where catalog name is the name of an SQL MX catalog Where location info is the location where the tables could not be created Cause This error can result from various CREATE statements issued to create the metadata See the accompanying error messages to determine the cause Effect One or more objects are not cr...

Page 55: ...quires a user specified clustering key Effect The operation fails Recovery Specify a clustering key either through a PRIMARY KEY STORE BY or PARTITION BY clause SQL 1117 Cause You attempted to drop the only partition of the object Effect The operation fails Recovery None SQL 1118 Where table name is the name of the object Cause You attempted to create an object in the metadata schema 1115 Label Gu...

Page 56: ...y Both methods will irrevocably destroy the database SQL 1120 Cause You attempted an operation on a partitionable table that has float datatype in the partitioning key Effect The operation fails Recovery None Contact your service provider SQL 1121 Where table name is the name of the table Cause You attempted to do an invalid ADD DROP or MODIFY of a partition Effect The operation fails Recovery Non...

Page 57: ... Where key is a list of the partition key values Where object name is the name of the object Cause You attempted to access a table using a first key value that contains an element that is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 1125 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider 1122 The number of...

Page 58: ... fails Recovery Specify a valid base table and resubmit SQL 1128 Where description is text further explaining the problem Cause Internal error Effect NonStop SQL MX is unable to perform the requested operation Recovery None Report the entire message to your service provider SQL 1130 Cause You attempted to create a column that requires a default value without specifying a default value Effect The o...

Page 59: ...ject while a concurrent utility or DDL operation was being performed on the object its parent or its dependencies Effect The operation fails Recovery Wait until the concurrent operation has finished and then resubmit SQL 1135 Where column name is the name of the column in the clustering key Cause You attempted to make a column that is not NOT NULL NOT DROPPABLE a part of the clustering key of a ta...

Page 60: ...ded through ALTER TABLE must be droppable Effect The operation fails Recovery Change the ALTER TABLE statement to specify DROPPABLE for the primary key SQL 1137 Where description is an explanation of the acceptable status values Cause This is an internal error in the interface between utilities and the catalog manager Effect The operation fails Recovery None Contact your service provider 1136 For ...

Page 61: ...ystem generated column and resubmit SQL 1140 Where actual row length is the length of a row of the table or index maximum row length is the largest row size allowed name is the name of the table or index Cause On a CREATE or ALTER TABLE statement or a CREATE INDEX statement the size of the row exceeds the maximum allowed row size Effect The operation fails Recovery See the SQL MX Reference Manual ...

Page 62: ...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 constraint that is violated by rows already in the table Effect The operation fails 1141 Label file name for object could not be accessed File system error e...

Page 63: ...ffect The operation fails Recovery Correct the value first key string to be a type that is compatible with the type of column column name and resubmit SQL 1145 Where catalog name is the name of an SQL MX catalog Cause NonStop SQL MX reserves certain catalog names for its own use Effect The operation fails Recovery See the SQL MX Reference Manual for reserved names Change catalog name to a name tha...

Page 64: ...of the table Cause You tried to create a unique or primary key constraint on the SYSKEY column Effect The operation fails Recovery Do not use the SYSKEY as part of the unique or primary key SQL 1148 Where column name is the SYSKEY column Where table name is the name of the table Cause You tried to create a referential constraint on a table column that is the SYSKEY which is not supported Effect Th...

Page 65: ...s the name of the table Cause When the Partition Overlay Support feature is enabled without setting volume names through CQD POS_LOCATIONS for table partitions to reside on location names are generated automatically However NonStop SQL MX could not generate the location names automatically and because the CQD POS_RAISE_ERROR is not set the given table is created as a simple table without partition...

Page 66: ... 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 1160 Cause You attempted to create a table that contains both a NOT DROPPABLE PRIMARY KEY constraint and a STORE BY clause The syntax specified is not correct The STORE BY column list must be the same as or a prefix of the NOT DROPPABLE PRIMARY KEY column list...

Page 67: ...al method Effect The label create drop or alter operation that is part of the DDL statement is performed serially rather than in parallel The serial method decreases performance compared to the parallel method Recovery No corrective action is necessary This message is a warning SQL 1168 Where uid is the unique ID assigned to the object in metadata Cause Object not found by the specified UID Effect...

Page 68: ...uardian name is the name of the table index view or routine being dropped Where 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 SQL MX operation to determine the necessary corrective actions Also use the file system error error number to analyze the c...

Page 69: ...he error returned Where ANSI name is the metadata table Where Guardian name is the name of the file Cause See the Guardian Procedure Errors and Messages Manual for a description of file system error error Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem 1183 Error error was returned by the file system on metadata table AN...

Page 70: ...pecify the correct location for all partitions involved in the affected command SQL 1186 Where column name is the name of the column that has an error Where column data type is the data type of column name Where value data type is the value specified as the default value for the column Cause The value specified as the default for the column is incompatible with the type of the column Effect The op...

Page 71: ...y where one of the columns of the table is referencing a column that belongs to the same table either directly or indirectly Effect The operation fails Recovery None You cannot define a referential constraint that creates a circular dependency SQL 1189 Where maximum number key columns is the maximum number of key columns For SQL MX R 3 0 the value of is maximum number key columns 1024 Cause The nu...

Page 72: ...ind SQL MP system catalog table vol sql catalogs Effect The SQL MX operation fails with an error Recovery Check that the SQL MP system catalog table vol sql catalogs exists If it does contact your service provider SQL 1192 Where catalog location is a name of the form vol sql catalogs Where error number identifies the error encountered Cause Unable to find SQL MP system catalog table vol sql catalo...

Page 73: ...100 Effect The operation fails Recovery Reduce the number of columns and then resubmit SQL 1196 Where catalog name is the name of the SQL MP system catalog Cause An invalid SQL MP system catalog location was specified or defaulted to Effect The operation fails Recovery Specify a correct SQL MP system catalog location or set the Guardian default system and volume to valid values 1193 Internal first...

Page 74: ...Manual to diagnose and correct the problem SQL 1222 Where file name is the name of the file Cause You specified a Guardian file name that is not an SQL MP database object Effect The operation fails Recovery Specify a Guardian file name for the SQL MP database object SQL 1224 Where parameter name is the name of the parameter Cause You specified a data type for this routine parameter that is not sup...

Page 75: ...Where procedure name is the stored procedure s ANSI name Cause The stored procedure could not be created Effect The CREATE PROCEDURE statement fails Recovery Fix the error conditions identified in messages preceding this message and reissue the CREATE PROCEDURE statement SQL 1232 Where table name is the table being dropped whose DDL was to be saved Where oss pathname is the HP NonStop Kernel Open ...

Page 76: ...alog name is the name of the SQL MX catalog Cause You attempted to create a schema in the system catalog Effect The operation fails Recovery Choose a different catalog name and reissue the CREATE statement SQL 1234 Where object name is the name of the SQL MP object Cause An ALTER SQL MP ALIAS command specified the same SQL MP database object as was previously mapped Effect The operation succeeds T...

Page 77: ...Where error number is the Guardian file system error number Cause NonStop SQL MX was unable to obtain file information about file name Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 1238 Cause You specified a literal with a character set other than ISO88591 in the text of a create trigger statement Effect The operat...

Page 78: ...iterals as partition keys SQL 1241 Cause You specified a literal with a character set other than ISO88591 in a HEADING clause Effect The operation fails Recovery Specify only ISO88591 literals in HEADING clauses SQL 1242 Cause You specified a literal with a character set other than ISO88591 in the text of a constraint Effect The operation fails Recovery Specify only ISO88591 literals in constraint...

Page 79: ...peat the operation using a valid ANSI name or perform the operation in SQL MP using the Guardian type name SQL 1245 Where key value is the specified first key value Where column name is the column of object name that corresponds to the invalid key value Where object name is the name of the affected object Cause A utility command specified an invalid key value Effect The operation fails Recovery Sp...

Page 80: ...bject Effect The CREATE statement fails Recovery Choose a name that is not the same as any other partition name in this object and reissue the CREATE statement SQL 1249 Where log table name is the name of the log table Cause Insert into one of the translation log tables has failed The log table name specifies the translation log table where the insert failed Effect The UPGRADE operation failed Rec...

Page 81: ... default value with a scale greater than the scale of the column Effect The scale of the default value is set to that of the column extra digits to the right are discarded Recovery None This is an warning message only SQL 1252 Where index name is the name of an existing unpopulated index Cause An existing index that is not populated has been chosen for a unique or primary constraint which is not a...

Page 82: ...ause An unanticipated error occurred during a CREATE PROCEDURE operation Effect The operation fails Recovery Retry the operation If the operation continues to fail contact your service provider SQL 1262 Where operation is a schema level operation Where schema is the ANSI name of the affected schema Cause You attempted a DDL or utility operation on a database object while operation was in progress ...

Page 83: ... single privilege or a list of distinct privileges SQL 1265 Cause You specified duplicate grantees in a GRANT or REVOKE statement Effect The operation fails Recovery Reissue the GRANT or REVOKE statement specifying a single grantee or a list of distinct grantees SQL 1266 Cause You specified an unsupported privilege on a procedure or routine in a GRANT statement Effect The operation fails Recovery ...

Page 84: ...the affected SQL database object Where file system error number is a Guardian file system error code Cause A CREATE or ALTER operation encountered a file system error error number during processing of the ALLOCATE or DEALLOCATE attribute Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 1271 Where object name is the AN...

Page 85: ...sing Effect The operation fails Recovery Purchase DDL Licensing product number T0394 SQL 1273 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 Cause You specified an insufficient MAXEXTENTS value while creating an index Effect The SQL operatio...

Page 86: ...se was used with an SQL MX view Effect The statement does not compile Recovery Remove the PARTITION clause and compile the statement again SQL 1277 Where object name is the name of the SQL object table or index Cause NonStop SQL MX does not recognize the partitioning scheme stored in the metadata for the named object Effect The named object is considered corrupt and is inaccessible Recovery Do not...

Page 87: ...ity operation SQL 1289 Cause An attempt was made to alter a definition schema or metadata schema Effect The operation fails Recovery None SQL 1295 Where 0 ColumnName is the column name Cause The data type of the specified default value for the column does not match the column data type Effect The command fails Recovery Specify a default value of a matching data type for the column 1278 The command...

Page 88: ...O ACTION referential action is specified in the referential integrity definition and the CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is OFF Effect The NO ACTION referential action cannot be defined Recovery To alter the behavior of NO ACTION referential action set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default 1300 Catman generated unknown E...

Page 89: ... SQL MP table Cause An SQL MP database object was referenced in a create view or create trigger operation which is not allowed Effect The operation fails Recovery Specify only SQL MX native database objects in create view or create trigger operations SQL 1304 Cause The Guardian location of the system schema tables could not be obtained from the anchor file Effect The operation fails This message w...

Page 90: ...s the schema subvolume Recovery Only schemas that are RDF replicated to another node should have the same subvolume names as their corresponding schemas on the other node To create these use the optional REUSE clause in the CREATE SCHEMA statement All other schemas should have unique subvolume names Schemas that are or will be related as RDF primary and backup schemas must have identical schema na...

Page 91: ...name is the name of the object Cause You specified an object for an SQL operation that does not support its object type Effect The operation fails Recovery Specify an object of valid object type and retry the operation SQL 1310 Cause You specified creation of triggers in the CREATE SCHEMA statement Effect The operation fails Recovery Remove the creation of triggers from the CREATE SCHEMA statement...

Page 92: ...e An error occurs during the creation of the table or index The error that described the cause of the failure already appears This error message provides clarification Effect The operation fails Recovery No recovery is necessary SQL 1401 Where column name is the column name character set is ISO88591 SJIS UTF8 Cause Unable to convert the default value of column column name from UCS2 to the ISO_MAPP...

Page 93: ... could be found in the affected MP_PARTITIONS definition schema table Effect The operation fails Recovery Retry the operation If the error persists contact your service provider SQL 1502 Where type is the type of the affected object Where object is the fully qualified ANSI name of the affected object Cause A row for object was found in the affected OBJECTS definition schema table but no correspond...

Page 94: ...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 Retry the operation If the error persists contact your service provider SQL 1506 Where schema is the fully qualified schema name that is mentioned by the current DDL or utility operation Where node1 and node2 are the Expand nodes on whic...

Page 95: ...column on which you want to create the referential integrity constraint SQL 1612 Cause You attempted to create a column list and the referential actions of a referential integrity constraint which matches the column list and referential action of another referential integrity constraint in the table Effect The operation fails Recovery None SQL 1613 Cause You attempted to create a column list of re...

Page 96: ...ng1 Referential action Cause The NOT NULL constraint cannot be created on a referencing column with the SET NULL referential action on it OR The primary key constraint cannot be created on the referencing column with the referential action specified because the primary key cannot be updated Effect The operation fails Recovery Drop the referential integrity constraint 1614 Constraint 0 constraintNa...

Page 97: ... error Use it to diagnose and correct the problem SQL 2002 Cause NonStop SQL MX was unable to create the MXCMP server Effect NonStop SQL MX could not proceed Recovery Check the environment to make sure that the MXCMP server is set up correctly Also because this error might be caused by a communication error check the configuration If it seems correct report the entire message to your service provi...

Page 98: ...he entire message to your service provider SQL 2006 Where detail text is information about the error Where name is the name of the file Where number is the line number Cause NonStop SQL MX received an internal error in file name at line number More information is in detail text Effect The operation fails Recovery None Report the entire message to your service provider SQL 2008 Cause NonStop SQL MX...

Page 99: ...your service provider SQL 2011 Where number is the error number Where name is the name of the program file Cause NonStop SQL MX was unable to create a server process because of the process control procedure error number it received while resolving the program file name Effect The operation fails Recovery Use the process control procedure error to diagnose and correct the problem 2009 The user tran...

Page 100: ...rence Manual for information about process creation errors SQL 2013 Where name is the name of the server process Where segment is the segment where the error condition occurred Where number is the error number Cause NonStop SQL MX was unable to create server process name on segment because of the process control procedure error number it received on the program file Effect The operation fails Reco...

Page 101: ...or condition occurred Where number is the error number Cause NonStop SQL MX was unable to create server process name on segment because the node is unavailable or does not exist Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 2016 Where name is the server process name Cause NonStop SQL MX started server process name but it had undefined externals Effec...

Page 102: ...ss name because of a library conflict The process you are trying to create has a different library than the one that is already running Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 2019 Where name is the server process name Cause NonStop SQL MX was unable to create server process name because it was unable to allocate enough virtual memory to start ...

Page 103: ...cedure Where process name is the server process name Cause NonStop SQL MX received an internal error Effect The operation fails Recovery None Contact your service provider SQL 2022 Where number is the error number Where procedure name is the name of the procedure Where process name is the server process name Where text is more information about the error Cause NonStop SQL MX received an internal e...

Page 104: ... or does not exist Effect The operation fails Recovery Check the configuration and the CPU status Use the messages that accompany this one to diagnose and correct the problem SQL 2027 Where number is the error number Where name is the server process name Cause NonStop SQL MX received the process control procedure error number while sending a startup message to process name Effect Usually the serve...

Page 105: ...imal value or specify a new maximal value that is greater than the new minimal value SQL 2030 Where number is the current minimal value Cause The new maximal value is smaller than the current minimal value Effect The new maximal value is not set Recovery Specify a new maximal value that is greater than the current minimal value SQL 2033 Where process id identifies the process Where number is the e...

Page 106: ...control procedure error number while communicating with server process name Effect The NonStop SQL MX 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 Where process id identifies the process Where name is the name of the server process Where number is the error number Cause The NonStop SQL MX pr...

Page 107: ...cter set name SQL 2050 Where attribute is the attribute name you specified Cause If the SQLSTATE is 42000 this is an error You attempted to set a CONTROL QUERY DEFAULT setting but the attribute name you specified is not valid If the SQLSTATE is 01000 this is a warning In an earlier SQL MX session you inserted a row into a DEFAULTS table whose attribute column value is invalid Effect If this is an ...

Page 108: ...le plan was not improved The simple plan is still valid and will work Effect Your query will use the original simple plan Recovery Informational message only no corrective action is needed This message will be accompanied by an assertion failure message and possibly CONTROL QUERY SHAPE information However report the entire message and the preceding assertion failure message to your service provide...

Page 109: ...alue and resubmit SQL 2057 Cause You specified an invalid value for an attribute It must be a multiple of value Effect The operation fails Recovery Correct the syntax and resubmit SQL 2058 Where name is the DEFAULTS attribute name Where data type is the attribute name value Cause You specified a DEFAULTS attribute name value of data type which is not supported The item is being converted to data t...

Page 110: ...061 Where name is the cursor name Cause You defined the static cursor name twice in this module Effect NonStop SQL MX uses the first static cursor definition Recovery This is an informational message only no corrective action is needed SQL 2062 Where name is the cursor name 2059 Errors or warnings occurred while reading values from DEFAULTS table name 2060 Procedure name has already been defined i...

Page 111: ...ame Cause You defined the dynamic cursor name twice in this module Effect NonStop SQL MX uses the first dynamic cursor definition Recovery This is an informational message only no corrective action is needed SQL 2065 Where name is the statement name Where name is the module name Cause NonStop SQL MX could not find statement name in module name Effect The operation fails Recovery Correct the syntax...

Page 112: ...procedure whose body is invalid It must be a SELECT INSERT UPDATE DELETE DECLARE CATALOG DECLARE SCHEMA or static DECLARE CURSOR Effect The operation fails Recovery Correct the syntax and resubmit SQL 2069 Cause You specified a static cursor declaration that is outside the body of a procedure It should appear only in the body of a procedure Effect The operation fails 2066 Cursor name was not found...

Page 113: ...ned as a type definition type Effect NonStop SQL MX uses the previous definition Recovery Specify a new name for the item and resubmit if necessary SQL 2072 Cause You specified a simple value as a literal which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 2073 Where name is the name of the module Cause You attempted to compile a system module that can be...

Page 114: ...ery Delete the a application name and retry the mxcmp system module definition file command SQL 2076 Cause You attempted to set the CQD HIST_NO_STATS_UEC value as greater than the current value of CQD HIST_NO_STATS_ROWCOUNT Effect The current value of the HIST_NO_STATS_UEC is retained Recovery Set the value of CQD HIST_NO_STATS_UEC less than or equal to the value of HIST_NO_STATS_ROWCOUNT If you w...

Page 115: ...p SQL MX does not open the file Recovery Use the error number to diagnose and correct the problem SQL 2082 Where number is the error number Where name is the name of the file Cause NonStop SQL MX received error number while opening file name for write Effect NonStop SQL MX does not open the file Recovery Use the error number to diagnose and correct the problem SQL 2083 Where number is the error nu...

Page 116: ...Effect NonStop SQL MX does not close the file Recovery Use the error number to diagnose and correct the problem SQL 2086 Where name is the name of the file Cause A compilation failed and for some reason NonStop SQL MX 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 Open System Services OSS shell SQL 2090 Where name1 ...

Page 117: ... included more than one module statement name will be used Effect NonStop SQL MX ignores the second module statement Recovery Informational message only no corrective action is needed SQL 2093 Where name is the name of the file Cause NonStop SQL MX did not find a module timestamp statement in the module definition file name Effect NonStop SQL MX uses a default timestamp value of all zeros Recovery...

Page 118: ...tion can have only one SOURCE_FILE statement that specifies that module s SQL source file Effect The operation fails Recovery Edit the module definition file so that it contains no more than one SOURCE_FILE statement and rerun MXCMP on the module definition SQL 2097 Cause MXCMP was invoked on a module definition file that contains a SOURCE_FILE statement whose source path name has over 1024 charac...

Page 119: ...rror is not compiled Recovery If this is a warning this is an informational message Otherwise correct the syntax and resubmit SQL 2100 Cause NonStop SQL MX received a break and aborted the compilation Effect NonStop SQL MX does not continue compilation Recovery Informational message only no corrective action is needed SQL 2101 Cause A compilation failed with an internal error Effect NonStop SQL MX...

Page 120: ...LEVEL MEDIUM Correct the CONTROL QUERY SHAPE specification and resubmit SQL 2104 Cause NonStop SQL MX was unable to compile this query either because it was not able to use the MEDIUM optimization level or because you used an incompatible CONTROL QUERY SHAPE specification Effect NonStop SQL MX is unable to process this query 2102 This query could not be compiled with MINIMUM optimization level Sug...

Page 121: ... unable to compile the query Effect The operation fails Recovery Use the warning messages returned by the compiler to diagnose and correct the problem SQL 2108 Cause The SQL MX compiler attempted to compile this query with query caching on but failed It then successfully compiled this query with caching turned off Effect The SQL MX compiler has compiled the query as if query plan caching was turne...

Page 122: ...sage Trace the diagnostic back to the module source file and correct the offending source statement Retry preprocessing translating compiling and SQL compiling the application file SQL 2202 Cause You invoked mxCompileUserModule on an application file that is not a NonStop Open System Services OSS ELF object file Effect The operation fails Recovery Verify that the name application file is an ELF ob...

Page 123: ...that has many embedded module definitions The tool cannot create another temporary file name to hold the contents of an embedded module definition The tool used tmpnam to create a string that is not the name of an existing file which tmpnam could not do Effect The operation fails Recovery Clean up TMPDIR the directory where temporary files are created by deleting unused temporary files Retry the c...

Page 124: ...tem Services OSS ELF object file SQL 2209 Cause You invoked mxCompileUserModule using a command line option allowing a delimited identifier but the delimited identifier has an invalid character such as the sign Effect The operation fails Recovery Remove invalid characters such as the sign from the delimited identifier and retry the command SQL 2210 Cause You invoked mxCompileUserModule using a com...

Page 125: ...string in the module name list Effect The operation fails Recovery Review the module name list syntax especially where string1 is expected Verify that the list of module names are specified correctly and retry the command SQL 2213 Cause You invoked mxCompileUserModule on an application file possibly intending to SQL compile only a subset of its embedded module definitions but you specified an unex...

Page 126: ...s 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 Where mxcmp path is the MXCMP environment variable Cause You set your MXCMP environment variable to point to your own MXCMP and invoked mxCompileUserModule on an application file to SQL compile its module definitions Your MXCMP is not...

Page 127: ...compile This list includes the named module which cannot be found in the application file Effect The operation fails Recovery Verify the spelling of the module name and retry the command SQL 2223 Where file name is the name of the application file Cause You invoked mxCompileUserModule on the named application file which does not exist or is not readable Effect The operation fails Recovery Verify t...

Page 128: ...d in file name at line number Effect The operation fails Recovery None Contact your service provider SQL 2900 Where number is the line number Cause An error occurred in file name at line number Effect Compilation failed because of a syntax error Recovery This is a general error that is issued before a more specific error Use the error that follows this one to diagnose and correct the problem SQL 2...

Page 129: ...SQL MX MXCMP Messages 2000 through 2999 HP NonStop SQL MX Messages Manual 640324 001 4 33 Recovery Specify a valid Guardian or OSS directory ...

Page 130: ...SQL MX MXCMP Messages 2000 through 2999 HP NonStop SQL MX Messages Manual 640324 001 4 34 ...

Page 131: ...1 Cause There is a syntax error near the text SQL text Effect The operation fails Recovery See the errors that accompany this message for more information Correct the syntax and resubmit SQL 3002 Cause You specified an invalid column reference which must have four or fewer parts Effect The operation fails Recovery Correct the syntax and resubmit 3000 An internal error occurred in module name on li...

Page 132: ...or name or use the name of a previously prepared statement and resubmit SQL 3006 Cause You attempted to declare a dynamic cursor in a way that does not match the statement Both must be literals or both must be string host variable expressions Effect The operation fails 3003 Length or precision must be greater than zero 3004 A delimited identifier must contain at least one nonblank character 3005 A...

Page 133: ... UNSIGNED column which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3009 Cause You attempted to perform a DROP ASSERTION statement which is not supported Effect The operation fails Recovery None SQL 3010 Where name is the name of the character set Cause You specified character set name that is not supported for use in an SQL MX object such as a table or ...

Page 134: ...y COUNT allows you to use Effect The operation fails Recovery Remove the operand and resubmit SQL 3013 Cause You specified an expression with invalid syntax Only subtraction is supported in the parenthesized expression that precedes an interval qualifier Effect The operation fails Recovery Correct the syntax and resubmit SQL 3014 Cause You defined a numeric item value with precision greater than 1...

Page 135: ...ted Effect The operation fails Recovery Redefine the item with a precision value of 18 or less SQL 3017 Cause You specified an unexpected value value NonStop SQL MX requires an unsigned integer Effect The operation fails Recovery Replace the value with an unsigned integer and resubmit SQL 3018 Cause You specified an unexpected value value NonStop SQL MX requires an unsigned smallint Effect The ope...

Page 136: ...e value with an unsigned number and resubmit SQL 3021 Cause You specified an unexpected value value NonStop SQL MX requires an unsigned number Effect The operation fails Recovery Replace the value with an unsigned number and resubmit SQL 3022 Cause You attempted to use an operator that is not supported Effect The operation fails Recovery None 3019 An unsigned number was expected within the parenth...

Page 137: ... invalid location name for a subvolume that must be eight characters long and begin with the letters ZSD Effect The operation fails Recovery Correct the name and resubmit SQL 3026 Cause You made a syntax error in a list of file attributes which must be separated by commas Effect The operation fails Recovery Correct the syntax and resubmit 3023 The COLLATE clause in a sort specification is not yet ...

Page 138: ...st and resubmit SQL 3029 Cause You attempted to specify an option that is not supported in a referential integrity constraint definition Effect The operation fails Recovery Remove the option and resubmit SQL 3030 Cause You used the PARALLEL EXECUTION clause which is not supported Effect The operation fails Recovery Remove the PARALLEL EXECUTION clause and resubmit 3027 name is not a valid simple n...

Page 139: ...x and resubmit SQL 3033 Cause You used the MOVE clause in the ALTER TABLE statement which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3034 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 3031 CASCADE drop behavior is not yet supported 3032 The COL...

Page 140: ...it SQL 3037 Cause You specified a CREATE TABLE statement with a precision value greater than 18 for data type which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3038 Cause You specified a PIC X type with a sign which is not supported Effect The operation fails Recovery Remove the sign or redefine the type and resubmit 3035 The RENAME clause in the ALTER ...

Page 141: ...x and resubmit SQL 3041 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 Cause You specified UPSHIFT for a numeric type which is not supported Effect The operation fails Recovery Change the specification and resubmit 3039 PIC X types do no...

Page 142: ...ry Correct the interval value to a valid one and resubmit SQL 3045 Cause You specified an invalid date value Effect The operation fails Recovery Change the date value and resubmit SQL 3046 Cause You specified an invalid time value Effect The operation fails Recovery Correct the time value and resubmit SQL 3047 Cause You specified an invalid timestamp value Effect The operation fails 3043 Precision...

Page 143: ...bmit SQL 3050 Cause You specified a constraint whose catalog and schema do not match the specified table Effect The operation fails Recovery Correct the syntax so that the constraint and table have the same catalog and schema SQL 3051 Cause You defined column name with more than one HEADING clause Effect The operation fails Recovery Define the column with only one HEADING clause and resubmit 3048 ...

Page 144: ...nd resubmit SQL 3054 Cause You specified a constraint with an invalid NOT DROPPABLE clause which can appear only in PRIMARY KEY and NOT NULL constraint definitions Effect The operation fails Recovery Correct the syntax and resubmit SQL 3055 Cause You defined duplicate DELETE rules Effect The operation fails Recovery Correct the syntax and resubmit 3052 Duplicate NOT NULL clauses were specified in ...

Page 145: ...096 or 32768 Effect The operation fails Recovery Correct the BLOCKSIZE value and resubmit SQL 3059 Cause You provided an invalid size value in the MAXSIZE clause Effect The operation fails Recovery See the SQL MX Reference Manual for correct size values and resubmit SQL 3060 Cause You provided an invalid percentage value in the DSLACK clause Effect The operation fails 3056 Duplicate UPDATE rules w...

Page 146: ...e Effect The operation fails Recovery Correct the syntax and resubmit SQL 3063 Cause You specified duplicate DSLACK clauses in the PARTITION clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3064 Cause You specified duplicate ISLACK clauses in the PARTITION clause Effect The operation fails Recovery Correct the syntax and resubmit 3061 The format of the specified locat...

Page 147: ...covery Correct the syntax and resubmit SQL 3068 Cause You specified an ALTER INDEX statement with both an ALLOCATE and a DEALLOCATE clause which is not supported Effect NonStop SQL MX ignores the ALTER INDEX statement Recovery Correct the ALTER INDEX statement to include either ALLOCATE or DEALLOCATE SQL 3070 Cause You specified the NO AUDIT clause which is not supported Effect The operation fails...

Page 148: ...operation fails Recovery Correct the syntax and resubmit SQL 3073 Cause You specified a NO BUFFERED clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3074 Cause You specified the SEPARATE BY clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 3071 Duplicate NO AUDITCOMPRESS clauses were specified 3072...

Page 149: ...TER 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 Cause You specified an ALTER INDEX ATTRIBUTE S statement that includes the LOCKLENGTH clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 3075 The NO COMPRESS clause is not allowed in ...

Page 150: ...ed duplicate ALLOCATE clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3082 Cause You specified duplicate NO AUDIT clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3083 Cause You specified duplicate NO AUDITCOMPRESS clauses Effect The operation fails Recovery Correct the syntax and resubmit 3079 Duplicate EXTENT MAXEXTENTS clauses were ...

Page 151: ...and resubmit SQL 3086 Cause You specified duplicate NO CLEARONPURGE clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3087 Cause You specified an ALTER TABLE ATTRIBUTE S statement that includes the NO COMPRESS clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE AT...

Page 152: ...n fails Recovery Correct the syntax and resubmit SQL 3090 Cause You specified a statement with duplicate LOCKLENGTH clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3091 Cause You specified a CREATE INDEX statement with the NO AUDIT clause which is not supported Effect NonStop SQL MX ignores the CREATE INDEX statement Recovery Correct the syntax and resubmit 3088 The...

Page 153: ...ncludes the DEALLOCATE clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3095 Cause You specified a statement with duplicate NO ICOMPRESS clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3096 Cause You specified a statement with duplicate NO SERIALWRITES clauses Effect The operation fails 3092 Duplicate BLOCKSIZE cl...

Page 154: ...ON clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3099 Cause You specified a statement with duplicate FILE ATTRIBUTE S clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3100 Cause You specified a statement with duplicate DSLACK clauses Effect The operation fails Recovery Correct the syntax and resubmit 3097 The DEALLOCATE clause is not...

Page 155: ...esubmit SQL 3103 Cause You specified a statement with duplicate PARTITION clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3104 Cause You specified a CREATE TABLE statement with incorrect syntax Only the ADD option is supported in a PARTITION clause Effect The operation fails Recovery Correct the syntax and resubmit 3101 Duplicate ISLACK clauses were specified 3102 D...

Page 156: ...Recovery Correct the syntax and resubmit SQL 3107 Cause You specified a statement with duplicate LIKE clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3108 Cause You specified a statement with both LIKE and STORE BY clauses which is not supported Effect The operation fails Recovery Correct the statement to include one of these clauses 3105 Only range hash and system ...

Page 157: ...You specified a statement with both LIKE and LOCATION clauses which is not supported Effect The operation fails Recovery Correct the statement to include one of these clauses SQL 3112 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 3109 Duplicate STORE BY clauses we...

Page 158: ...peration fails Recovery Correct the statement to include one of these clauses SQL 3115 Cause You specified a statement with duplicate ISOLATION LEVEL clauses Effect The operation fails Recovery Correct the syntax and resubmit SQL 3116 Cause You specified a statement with duplicate access mode clauses Effect The operation fails Recovery Correct the syntax and resubmit 3113 Error in CONTROL statemen...

Page 159: ... clause which is not supported Effect The operation fails Recovery Eliminate the WITH LOCAL CHECK OPTION clause and resubmit SQL 3120 Cause You specified the CREATE ASSERTION statement which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3121 Cause You specified an SQL MP partitioned entry sequenced table which is not supported Effect The operation fails 3...

Page 160: ...e You specified an identifier that includes an invalid character Effect The operation fails Recovery Correct the syntax of the identifier and resubmit SQL 3128 Where object name is the identifier Cause You used an identifier that is a reserved word You must put it between double quotes to use it as an identifier Effect The operation fails 3122 The system specified in the location clause name is no...

Page 161: ...INT data item with the UNSIGNED option which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3131 Cause You specified a statement that is not supported by NonStop SQL MX Effect The operation fails Recovery None SQL 3132 Where name is the name of the column Cause You specified a heading for column name that exceeds the maximum size of 128 characters Effect T...

Page 162: ...overy Correct the syntax and resubmit SQL 3135 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 Cause You attempted to perform an invalid outer join Only LEFT RIGHT and FULL OUTER JOIN are supported Effect The operation fails Recovery Correct the syntax and resubmit 3133 PERFORM is va...

Page 163: ...e You attempted to create a range partitioned index without a required FIRST KEY clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3140 Cause You attempted to perform an INSERT UPDATE DELETE or DDL statement with a READ UNCOMMITTED isolation level which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 3137 UNION JOIN is not yet suppo...

Page 164: ...t SQL 3143 Cause You attempted to create a table value constructor with BROWSE or READ UNCOMMITTED access which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3145 Cause You attempted to perform a positioned UPDATE or DELETE which is supported only in embedded NonStop SQL MX Effect The operation fails Recovery Correct the syntax and resubmit 3141 The trans...

Page 165: ... 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 Cause The WITH HEADINGS phrase appears multiple times within the LIKE clause of the CREATE TABLE statement which is not supported Effect The operation fails Recovery Remove the duplicate WITH HEADINGS phrases 3147 In an IN predicate...

Page 166: ...overy Correct the syntax and resubmit SQL 3155 Cause You specified a CREATE INDEX statement using both the POPULATE or NO POPULATE clauses which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 3157 Cause You attempted to create a catalog without specifying a catalog name Effect The operation fails Recovery Specify a catalog name and resubmit 3151 Duplicate ...

Page 167: ...cifier for example KANJI but you placed a space in front of the single quote delimiter which is not supported For example _KANJI xyz causes this error _KANJI XYZ does not Effect The operation fails Recovery Correct the syntax and resubmit SQL 3160 Cause You declared host variable more than once in the procedure parameter list Effect The operation fails Recovery Correct the syntax and resubmit 3158...

Page 168: ...RT statement whose INTO list includes host variable name more than once Effect Execution results are undefined Recovery This is an informational message only No corrective action is needed but you might want to rewrite your query SQL 3164 Cause A data type mismatch occurred between the output host variable and the selected value in the statement you specified Effect The operation fails Recovery Co...

Page 169: ...ou specified a statement with more than one NOT DROPPABLE clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3168 Cause You specified a CREATE VIEW statement with the FOR ACCESS clause which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 3165 The precision or exponent value specified in value was less than the minimum allowed or gre...

Page 170: ...tion fails Recovery Correct the syntax and resubmit SQL 3172 Cause You specified a compound statement that contains an EXIT command Effect The operation fails Recovery Correct the syntax and resubmit SQL 3173 Cause You specified a compound statement that contains an UPDATE STATISTICS command Effect The operation fails Recovery Correct the syntax and resubmit 3169 name is not a known collation 3171...

Page 171: ...ified an IF statement that contains a subquery Effect The operation fails Recovery Correct the syntax and resubmit SQL 3177 Where name is the name of the character set Cause You specified a character set with an odd number of characters in the length declaration of the data type Effect The operation fails Recovery Correct the syntax and resubmit 3174 DDL statements are not allowed in compound stat...

Page 172: ...required Effect The operation fails Recovery Correct the syntax and resubmit SQL 3180 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 Cause You specified an invalid logical name Effect The operation fails Recovery Correct the syntax and resubmit 3178 One or more of the foll...

Page 173: ... is the illegal SQLSTATE value Cause You attempted to use an illegal SQLSTATE value A valid SQLSTATE value is a single quoted string value that begins with an S or an s followed by a four digit integer Effect The operation fails Recovery Specify a valid SQLSTATE value and resubmit SQL 3185 Cause You attempted a SIGNAL statement with a third parameter that is not a quoted string Effect The operatio...

Page 174: ...which is not supported Effect The operation fails Recovery None SQL 3188 Cause You specified a STORE BY primary key but did not define a NOT DROPPABLE primary key Effect The operation fails Recovery Correct the syntax and resubmit SQL 3189 Cause You attempted to set a lock timeout on a view which is not supported Effect The operation fails Recovery None 3186 string Dynamic parameters and host vari...

Page 175: ...atement 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 Where dtype is a data type specified for a column Cause The data type specified for a column in a CREATE TABLE statement is not supported Effect The operation fails Recovery Correct the data and resubmit SQL 3196 Cause You specifi...

Page 176: ...ing key clause Effect The operation fails Recovery Remove any of the following keywords from the columns specified in the PARTITION clause ASCENDING ASC DESCENDING DESC and resubmit SQL 3201 Cause In the CREATE PROCEDURE statement you omitted the mandatory EXTERNAL PATH clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3202 Cause In the CREATE PROCEDURE statement you o...

Page 177: ...QL MX is unable to create the procedure Recovery Correct the syntax and resubmit SQL 3205 Cause In the CREATE PROCEDURE statement you omitted the mandatory EXTERNAL NAME clause Effect The operation fails Recovery Correct the syntax and resubmit SQL 3206 Cause In the CREATE PROCEDURE statement you specified a partially qualified name when NAMETYPE was not set to ANSI Effect The operation fails Reco...

Page 178: ...mnname 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 Cause You attempted a CREATE TABLE table name columnname longwvarchar N where N current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting Effect Th...

Page 179: ...the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit SQL 3213 Cause You attempted a CREATE TABLE table name columnname long varchar N where N current MAX_LONG_VARCHAR_DEFAULT_SIZE setting Effect The operation fails Recovery Decrease the CREATE TABLE statement s long varchar column width N or increase the current MAX_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit SQL 3214 Cause You attemp...

Page 180: ...ns falls below the current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting Effect The operation fails Recovery Reduce the number of longwvarchar columns in the CREATE TABLE statement or increase the current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting and resubmit SQL 3217 Cause You specified KANJI or KSC5601 character expressions to function LOWER LCASE UPPER UPSHIFT or UCASE Effect The operation fails Recovery...

Page 181: ...y Do not use DELETE or UPDATE in a CREATE VIEW statement SQL 3219 Cause In a CREATE PROCEDURE statement you specified the optional DYNAMIC RESULT SETS clause with an invalid value Effect The operation fails Recovery Remove the clause or use a value between zero and 255 and resubmit 3219 The value for DYNAMIC RESULT SETS must be between 0 and 255 ...

Page 182: ...s the default Effect SHOWLABEL does not display output Recovery Reissue the command with an object name and corresponding namespace of a valid supported and accessible object SQL 3226 Where location name specifies the physical location name of an SQL MX object Cause SHOWLABEL was given an invalid physical location as an argument Effect SHOWLABEL does not display output Recovery Reissue the command...

Page 183: ...does not support resource forks Effect SHOWLABEL does not display output Recovery Reissue the command with a valid location name SQL 3400 Cause There is an undefined character in the character set Effect The operation fails Recovery Remove the invalid character and resubmit SQL 3401 Cause You used a hexadecimal format to represent a character string that is not supported by NonStop SQL MX Effect T...

Page 184: ... SQL 3404 Cause You specified SQL_TEXT as the module character name set SQL_TEXT is synonymous with UCS2 which is not supported Effect The operation fails Recovery Replace SQL_TEXT with ISO88591 and resubmit SQL 3405 Cause You cannot specify the logical partition name in the LOCATION clause of the create statement of catalog procedure view and materialized view object types Effect The operation fa...

Page 185: ...declare a cursor on an embedded INSERT statement Effect The operation fails Recovery Modify the statement and resubmit SQL 3415 Where name is the name of the function Cause The first operand you supplied for function name is not an allowed value Effect The operation fails Recovery Correct the syntax and resubmit 3406 A DDL statement could not be translated into a statement consisting of single byt...

Page 186: ...Parser and Compilation Messages 3000 through 3999 HP NonStop SQL MX Messages Manual 640324 001 5 56 ...

Page 187: ... error is that you have used double quotes instead of single quotes For example select from tb where b b result in this error ERROR 4001 Column b is not found Tables in scope CAT SCH TB Default schema CAT SCH In this example 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 wher...

Page 188: ...ion you no longer qualify its name with its original table name2 Effect The operation fails Recovery Correct the syntax and resubmit If the column is part of a JOIN remove the table qualifier and use only the column name SQL 4004 Cause You referenced column name1 whose parent table is ambiguous The table names or tables in the scope of the column reference and default schema name2 appear Effect Th...

Page 189: ...pecified an index value1 that is out of the range of between 1 and the value2 of SELECT expressions Effect The operation fails Recovery Correct the index and resubmit SQL 4008 Cause You specified a subquery within an aggregate function which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 4005 Column reference name must be a grouping column or be specified with...

Page 190: ...e SELECT or SELECT TBL reference and NonStop SQL MX could not locate the column because the reference is ambiguous Effect The operation fails Recovery Correct the syntax and resubmit SQL 4012 Cause You referred 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 res...

Page 191: ...ample you used an aggregate function in a predicate WHERE or HAVING but the aggregated columns come from the local scope instead of an outer scope Effect The operation fails Recovery Correct the syntax and resubmit SQL 4016 Cause You specified a statement in which the number of derived columns value1 does not equal the degree of the derived table value2 They must be equal Effect The operation fail...

Page 192: ...ubmit SQL 4019 Cause You specified a select list that is not scalar Effect The operation fails Recovery Correct the syntax and resubmit SQL 4020 Cause You attempted to perform an arithmetic operation on row value constructors which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 4017 Derived column name name was specified more than once 4018 Rows cannot be dele...

Page 193: ...use the number of columns does not match the number of values Effect The operation fails Recovery Correct the syntax and resubmit SQL 4024 Cause You attempted to insert column name into a table and the column has no default value For example INSERT INTO table acol bcol ccol VALUES 1 2 is wrong if ccol does not have a default value and you did not specify its value The column list is optional but i...

Page 194: ...26 Where name is the name of the table Cause You attempted to read from and insert update or delete within the same table name This feature is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 4027 Where name is the name of the table Cause You attempted to insert into table name which is not insertable Effect The operation fails Recovery None 4025 Error while pr...

Page 195: ...SQL 4031 Cause You specified column name with an unknown data type Effect The operation fails Recovery Correct the syntax and resubmit SQL 4032 Cause You specified column name with an unknown class Effect The operation fails Recovery Correct the syntax and resubmit 4028 Table or view name is not updatable 4030 Column name has an invalid combination of datetime fields internal field number internal...

Page 196: ...ry Correct the syntax and resubmit SQL 4035 Cause You attempted to cast type specification1 to another type specification2 that is not valid Effect The operation fails Recovery Correct the syntax and resubmit SQL 4036 Cause You specified a source field of the EXTRACT function that is not a DATETIME or INTERVAL data type Effect The operation fails Recovery Correct the source field type and resubmit...

Page 197: ...u specified column name with type specification1 which is incompatible with the type of the value Effect The operation fails Recovery Correct the syntax and resubmit SQL 4040 Cause You specified operands for a BETWEEN predicate that are not of equal degree which is required Effect The operation fails Recovery Correct the syntax so that the operands are of equal degree and resubmit 4037 Field name ...

Page 198: ... and resubmit SQL 4043 Cause You specified an operand for function name that is not a character which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4044 Cause You specified collation name1 which does not support the predicate or function listed in the message Effect The operation fails Recovery Correct the syntax and resubmit 4041 Type specification1 cannot be...

Page 199: ...submit SQL 4047 Cause You specified operands of function name that do not have a scale of zero 0 which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4048 Cause You specified the third operand of a ternary comparison argument with an invalid type The type must be boolean Effect The operation fails Recovery Correct the syntax and resubmit 4045 The operand of fun...

Page 200: ...ause You specified the first operand of function name with a type other than character which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4052 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 4049 A CASE expression cannot have a result da...

Page 201: ... a statement with an exposed table name that appears more than once For example SELECT FROM tblx tblx Effect The operation fails Recovery Correct the syntax and resubmit SQL 4057 Cause You specified correlation name1 which conflicts with a qualified identifier of table name2 For example SELECT FROM tblx tblz tblx Effect The operation fails Recovery Correct the syntax and resubmit 4053 The third op...

Page 202: ... or update rows in an individual table partition which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 4062 Cause NonStop SQL MX detected an error in function name Errors that appear before this one refer to the low level computations that this function uses Effect The operation fails Recovery Correct the function and resubmit 4059 The first operand of func...

Page 203: ...ands of a UNION statement that are not of equal degree which is required Effect The operation fails Recovery Correct the syntax and resubmit SQL 4067 Cause You specified invalid operands for function name They must be operands of type character Effect The operation fails Recovery Correct the syntax and resubmit 4063 The operands of function name must be comparable character data types that is of t...

Page 204: ...ery Correct the syntax and resubmit SQL 4070 Cause You specified an invalid operand for function name It must be type exact numeric Effect The operation fails Recovery Correct the syntax and resubmit SQL 4071 Cause You specified an invalid operand for function name It must be datetime Effect The operation fails Recovery Correct the syntax and resubmit 4068 The operand of function name must contain...

Page 205: ...d resubmit SQL 4074 Cause The CONTROL QUERY statement completed successfully Effect None Recovery Informational message only no corrective action is needed SQL 4075 Cause You attempted to divide by zero in constant expression name Effect The operation fails Recovery Correct the syntax and resubmit SQL 4076 Cause There is an overflow in constant expression name 4072 The operand of function name mus...

Page 206: ...ction name The first argument must be numeric Effect The operation fails Recovery Correct the syntax and resubmit SQL 4079 Cause You specified an invalid operand in function name The operands must be numeric Effect The operation fails Recovery Correct the syntax and resubmit SQL 4080 Cause NonStop SQL MX has received error number from SQL MP Effect The operation fails Recovery Use the error number...

Page 207: ...ume Effect The operation fails Recovery Correct the syntax and resubmit SQL 4083 Cause The SQL MP Data Definition Language DDL operation you performed has failed Effect The operation fails Recovery Correct the syntax and resubmit SQL 4084 Cause You attempted to perform an action on a object name that is corrupt Effect The operation fails Recovery See the SQL MX Reference Manual for procedures for ...

Page 208: ... environment variable and resubmit SQL 4087 Cause You specified a prototype value that is not a valid qualified name Effect The operation fails Recovery Correct the syntax and resubmit SQL 4088 Cause You specified a TRANSPOSE set with an unequal number of values in each TRANSPOSE item Effect The operation fails Recovery Correct the syntax and resubmit 4085 File organization name1 of object name2 i...

Page 209: ...4 Cause NonStop SQL MX requires that the number of output host variables value1 match the number of selected values value2 Effect The operation fails Recovery Correct the syntax and resubmit SQL 4095 Cause You included a NULL operand in object name which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 4089 Check constraint name contains a subquery This is not y...

Page 210: ...rect the syntax and resubmit SQL 4098 Cause You included a NULL operand in operation name which is not supported Effect The operation fails Recovery Correct the syntax and resubmit SQL 4099 Cause You included a NULL operand in predicate name which is not supported Effect The operation fails Recovery Correct the syntax and resubmit 4096 A DEFAULT specification is currently allowed only when simply ...

Page 211: ...m Correct the syntax and resubmit SQL 4102 Cause You attempted to use either a FIRST n or an ANY n clause in other than an outermost SELECT statement Effect The operation fails Recovery Remove the FIRST n or ANY n clause and resubmit SQL 4103 Cause An internal error occurred during retrieval of node numbers in SQL MX cluster Effect Service request fails and Transporter jobs may terminate 4100 A NU...

Page 212: ...eral 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 Cause NonStop SQL MX does not recognize the translation name Effect NonStop SQL MX is unable to compile the statement Recovery Use one of the supported translation names SQL 4106 Cause You specified an opera...

Page 213: ... function does not contain references to the THIS function SQL 4109 Cause You specified a query that includes a SEQUENCE BY clause that contains an illegally placed sequence function name Sequence functions such as RUNNINGSUM MOVINGSUM LASTNOTNULL are supported only in the select list or the HAVING clause of the query expression containing the SEQUENCE BY clause For example these queries are legal...

Page 214: ...select runningsum a from t1 ERROR 4110 The query contains sequence functions but no SEQUENCE BY clause RUNNINGSUM CAT SCH T1 A To correct the query add a SEQUENCE BY clause select runningsum a from t1 sequence by b SQL 4111 Cause You specified a query that contained a SEQUENCE BY clause but no sequence functions which is not supported The purpose of the SEQUENCE BY clause is to specify an ordering...

Page 215: ...to prepare the query Recovery Correct the syntax and resubmit SQL 4114 Cause You specified an absolute sample size with a scale greater than zero which is not supported Effect NonStop SQL MX is unable to prepare the query Recovery Correct the syntax and resubmit SQL 4115 Cause You specified a sample size that is greater than the sample period It must be less than or equal to the sample period Effe...

Page 216: ...e That cursor s select list did not select the target column of the update Effect The operation fails Recovery An updatable cursor query should specify the target update column in the select list of the query Use the FOR UPDATE OF clause only if the cursor query is updatable This example of a nonupdatable cursor join query does not select the target of the update and receives an error SELECT A PRO...

Page 217: ... table For example this query is updatable SELECT A FROM T This one is not SELECT A FROM T WHERE B SELECT C FROM U WHERE T I U I There are no aggregates There are no GROUP BY DISTINCT or ORDER BY clauses All select_list columns are column references No column reference occurs more than once in the select list This example of a nonupdatable cursor join query selects the target of the update correct...

Page 218: ...ation fails Recovery Correct the ORDER BY clause and resubmit SQL 4122 Cause You attempted to assign NULL to a NOT NULL column name Effect The operation fails Recovery Correct the syntax and resubmit SQL 4123 Cause You attempted to cast NULL to a NOT NULL data type Effect The operation fails Recovery Correct the syntax and resubmit 4120 In a query with a GROUP BY DISTINCT or aggregate function eac...

Page 219: ...rrect the syntax and resubmit SQL 4126 Cause You specified a VALUES clause whose row value constructors are not of equal degree Effect The operation fails Recovery Correct the syntax and resubmit SQL 4127 Cause You attempted to perform an assignment but specified incompatible data types Effect The operation fails Recovery Correct the syntax and resubmit 4124 More than one table will be locked name...

Page 220: ...n fails Recovery Correct the syntax and resubmit SQL 4130 Cause You specified a SIGNAL parameter of an incorrect type Effect The operation fails Recovery Correct the syntax and resubmit SQL 4133 Cause The type of the trim source and trim character is not CHARACTER Effect The operation fails Recovery Make sure the type of the source and trim character is CHARACTER 4128 Default volume and subvolume ...

Page 221: ... was with the result set of another expression You did not use the primary key of the second expression for your join You must use the primary key to prevent returning multiple rows being returned for a single deleted or updated row Effect NonStop SQL MX is unable to compile the statement Recovery Modify the WHERE clause to use the primary key of the table expression SQL 4151 Cause You attempted t...

Page 222: ...alizes the order and resubmit SQL 4154 Cause You attempted to compile an embedded DELETE or embedded UPDATE expression using an ORDER BY without using a clustering key or a secondary index Effect NonStop SQL MX is unable to compile the statement Recovery Create a secondary index materializing the order and resubmit SQL 4156 Cause You attempted to perform a left join using the result set of an embe...

Page 223: ...u attempted to perform an intersection of stream expressions Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4160 Cause You attempted to perform an intersection between two embedded expressions Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit 4157 Inner relation of left join cannot be stream ...

Page 224: ...ement and resubmit SQL 4163 Cause You attempted to perform a GROUP BY in conjunction with an embedded expression Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4164 Cause You attempted to perform a right join using an embedded expression as the outer relation Effect NonStop SQL MX is unable to compile the statement 4161 Embedded INSERT UPDAT...

Page 225: ...odify the statement and resubmit SQL 4167 Cause You attempted to perform a subquery that included an embedded statement Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4168 Cause You attempted to perform a subquery that included a stream expression Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resu...

Page 226: ... and resubmit SQL 4171 Cause You attempted to perform an INSERT that included an embedded statement Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4173 Cause You attempted to perform a top level UPDATE statement that included a stream expression Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubm...

Page 227: ...rm a join between a stream expression and an embedded expression Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4177 Cause You attempted to update clustering key components or columns associated with referential integrity constraints during a rollback Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and ...

Page 228: ...statement and resubmit SQL 4180 Cause You attempted to use a stream expression to perform a top level DELETE Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4183 Cause You attempted to perform an embedded DELETE statement on a table with a referential constraint Effect The operation fails Recovery Modify the statement and resubmit 4178 Update...

Page 229: ... the two part name to anything other than volatile schema prefix and reissue the SQL statement SQL 4195 Cause The GROUP BY expression contains a renamed column in the select list Effect The statement does not compile Recovery Correct the column name in the GROUP BY expression SQL 4196 Cause The HAVING predicate refers to a renamed column in the select list Effect The statement does not compile Rec...

Page 230: ... statement and resubmit SQL 4201 Cause You attempted to use an embedded expression for a compound statement Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4202 Cause You attempted to perform an embedded expression that included SEQUENCE BY Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit 419...

Page 231: ...SERT UPDATE or DELETE operation on a nonaudited table and IUD_NONAUDITED_INDEX_MAINT is set to WARN This message appears as an warning Effect NonStop SQL MX performs the INSERT UPDATE or DELETE operation If the operation encounters an error you will see other messages about that condition Recovery Informational message only no corrective action is needed SQL 4204 Cause You attempted to use stream ...

Page 232: ...SQL 4208 Cause You attempted to use an index for stream access that does not cover all base table columns referenced in the WHERE clause Effect NonStop SQL MX is unable to compile the statement Recovery Add the missing columns to the index SQL 4209 Cause You attempted to perform a rollback that included an update of a nullable column Effect NonStop SQL MX is unable to compile the statement Recover...

Page 233: ...ttempted to use a rowset as a predicate with an embedded update or embedded delete Effect NonStop SQL MX is unable to compile the statement Recovery Modify the statement and resubmit SQL 4214 Cause You attempted to use a SET ON ROLLBACK clause to update a column in a nonaudited table Effect The operation fails Recovery Change the table s AUDIT attribute and resubmit 4210 Embedded update delete sta...

Page 234: ...ction in context other than inside a ROWS SINCE function Effect The operation fails Recovery Correct the NonStop SQL MX statement and resubmit SQL 4302 Cause In the SQL MX statement being compiled a stored procedure invocation contains an incorrect number of parameters Effect The SQL MX statement is not compiled Recovery Correct the SQL MX statement and retry the compilation 4215 Stream access is ...

Page 235: ...he actual OUT values Recovery Use different host variables for each of the OUT or INOUT parameters SQL 4305 Cause In the SQL MX statement being compiled you attempted to invoke a stored procedure that has an OUT or INOUT parameter that is neither a host variable nor a dynamic parameter Effect The SQL MX statement is not compiled Recovery Correct the SQL MX statement Supply a host variable or a dyn...

Page 236: ...L 4306 Cause In the SQL MX statement being compiled a CALL statement was present within a BEGIN END block Effect The SQL MX statement is not compiled Recovery Remove the CALL statement from the compound statement and retry the compilation 4306 A CALL statement is not allowed within a compound statement ...

Page 237: ...d procedure Cause You are running an SQL MX version that does not support stored procedure result sets and attempted to compile a CALL statement for a stored procedure that returns result sets This message indicates a downgrade has been performed without removing stored procedures that return result sets Effect The SQL MX statement is not compiled Recovery Migrate to an SQL MX version that support...

Page 238: ...use The user has specified a column in the PARTITIONING_KEY clause that is not part of the partitioning key of the table specified in the PARTITIONING_KEY option of 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 KEY_RANGE_COMPATRE function SQL 4334 Cause KEY_RANGE_COMPARE function cannot be use...

Page 239: ...nd of the PARTITIONING_KEY clause of the KEY_RANGE_COMPARE function that matches the partitioning columns of table tablename SQL 4336 Where operation is an INSERT operation table names are the names of the NonStop SQL MX tables that are in scope Cause You attempted a join operation using an embedded INSERT statement Effect The operation failed Recovery Modify the statement and resubmit SQL 4337 Ca...

Page 240: ...ause The referential integrity constraint or unique constraint of the table is inaccessible because it is deleted Effect The operation fails Recovery Retry the operation If the error persists contact your service provider SQL 4362 Cause ASC DESC was specified in the expression of the RANK sequence function Effect The statement fails to prepare Recovery Rewrite the query so that it does not contain...

Page 241: ...01 7 1 7 Normalizer Messages 5000 through 5999 SQL 5000 Cause The optimizer received an internal error during query normalization Effect The operation fails Recovery None Contact your service provider 5000 Internal error in the query normalizer ...

Page 242: ...Normalizer Messages 5000 through 5999 HP NonStop SQL MX Messages Manual 640324 001 7 2 ...

Page 243: ...pression Recovery Correct syntax and resubmit SQL 6002 Cause You have manually modified the metadata table and now it contains invalid values Effect NonStop SQL MX is unable to complete compilation Recovery Undo your changes using the CLEAR option in UPDATE STATISTICS 6000 Internal error in the query optimizer 6001 DISTINCT aggregates can be computed for only one column per table expression 6002 T...

Page 244: ...statistics for column names and when the rowcount in table name is more than the value of the defaults table constant HIST_ROWCOUNT_REQUIRING_STATS If you want to suppress this message set that value to a very large number and you will see this message only for tables with more rows than that and for which there are no updated statistics Effect None This is a warning message 6003 The metadata tabl...

Page 245: ...e column identified in the warning and prepare the query again SQL 6020 Cause The defaults attribute MEMORY_USAGE_SAFETY_NET is set and the MXCMP process memory reached the set threshold Effect This is a warning message SQL MX optimizer has reached the set threshold and the query plan generated might be sub optimal As a result there may be a slow execution of the query Recovery None 6008 Statistic...

Page 246: ...Optimizer Messages 6000 through 6999 HP NonStop SQL MX Messages Manual 640324 001 8 4 ...

Page 247: ... syntax and resubmit SQL 7003 Cause You can use cluster sampling in a query only on a base table result set and only if there is no WHERE clause in the SELECT statement This query does not satisfy these conditions Effect NonStop SQL MX is unable to compile the query Recovery Rewrite the query for example using nested queries so that cluster sampling is performed on a base table with no WHERE claus...

Page 248: ...Generator Messages 7000 through 7999 HP NonStop SQL MX Messages Manual 640324 001 9 2 ...

Page 249: ...ld contact your service provider SQL 8003 Cause The descriptor is still being used by another nowait CLI operation Effect The new descriptor is locked Recovery None Contact your service provider SQL 8004 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 Close the cursor before trying to ...

Page 250: ...o open it SQL 8007 Cause You pressed the break key Effect The operation stops Recovery None SQL 8008 Where name is the name of the catalog Cause You specified an invalid catalog name Effect The operation fails Recovery Correct the syntax and resubmit SQL 8009 Where name is the name of the schema Cause You specified an invalid schema name 8005 Trying to fetch from a cursor that is not in the open s...

Page 251: ...tatement that returns more than one row Effect The operation fails Recovery Correct the syntax and resubmit SQL 8012 Cause NonStop SQL MX displays an internal CONTROL QUERY DEFAULT encoding Effect None Recovery This is an informational message only no corrective action is needed SQL 8013 Cause You are trying to update or delete from a cursor that is not in the fetched state Effect The operation fa...

Page 252: ...ed SQL 8016 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 Cause The explain default has been turned off for this query Effect NonStop SQL MX is not able to di...

Page 253: ...e provider SQL 8022 Cause The row count maintained by the disk process for one or more partitions of the table name is invalid because of the following reasons The table is created by an SQL release before R3 0 The table is created by an SQL DUP operation The table is reorganized Effect The operation fails Recovery In the SQL MX R3 0 the only way to reset the row count is to delete all the rows fr...

Page 254: ... prevented by check constraint name2 Effect The operation fails Recovery Change the data you are attempting to enter to be consistent with the constraint SQL 8102 Cause You attempted to perform an operation that is prevented by a unique constraint Effect NonStop SQL MX could not perform the operation Recovery Make the data you enter unique to be consistent with the constraint SQL 8103 Where name1 ...

Page 255: ...has been prevented by the check on view name2 cascaded from the check option on the table Effect The operation fails Recovery Change the view properties if appropriate SQL 8105 Where name is the name of the view Cause You attempted to perform an operation on table name that is prevented by the check option on view name Effect The operation fails Recovery Insert into the base table rather than this...

Page 256: ... The operation fails Recovery Recompile and reexecute the statement after first resetting the environmental variable SQL 8300 Where type is the type of the affected object such as table Where object is the fully qualified ANSI name of the affected object Cause Late name resolution failed for the affected object Effect The operation fails This message will be accompanied by one or more other messag...

Page 257: ... not resolve the ANSI name to an available partition Effect The operation fails Recovery Determine why none of the partitions were available then correct the error and resubmit SQL 8303 Where name is the fully qualified Guardian file name of an SQL MX anchor file Cause The named anchor file contains invalid data Effect NonStop SQL MX uses data from the anchor file to locate the system schema table...

Page 258: ...table name DEFINE should be MAP not SORT Effect The operation fails Recovery Use a correct CLASS attribute as specified in the SQL MX Programming Manual for C and COBOL SQL 8401 Cause The table or tables had more than one row that satisfied the query Only one row is allowed Effect The operation fails Recovery Determine if the statement or the data is incorrect If the data is incorrect correct the ...

Page 259: ...ength caused a string overflow Effect If this is an error the operation fails If this is a warning your string is truncated Recovery Do not attempt recovery Contact your service provider SQL 8403 Cause You specified a SUBSTRING function with an invalid length argument less than zero or greater than the source string length Effect The operation fails Recovery Correct the syntax and resubmit SQL 840...

Page 260: ...invalid escape character argument which must be one character in length Effect The operation fails Recovery Check your input data and resubmit SQL 8410 Cause You specified a LIKE pattern whose syntax is incorrect An escape character in a LIKE pattern must be followed by another escape character an underscore or a percent character Effect The operation fails Recovery Check your input data and resub...

Page 261: ...nd resubmit SQL 8413 Cause You provided a string argument for conversion that contains characters that cannot be converted Effect The operation fails Recovery Check your input data and resubmit SQL 8414 Cause You attempted to perform a conversion that is not supported on this platform Effect The operation fails Recovery None 8411 A numeric overflow occurred during an arithmetic computation or data...

Page 262: ...ecovery Check your input data and resubmit SQL 8417 Cause NonStop SQL MX has received an internal error Effect The operation fails Recovery None Contact your service provider SQL 8418 Cause You attempted to perform the USER function which is not supported on this platform Effect The operation fails Recovery None 8415 The provided DATE TIME or TIMESTAMP is not valid and cannot be converted 8416 A d...

Page 263: ... which NOT NULL was specified Effect The operation fails Recovery Correct the syntax and resubmit SQL 8422 Cause You provided an INTERVAL that is not valid and that could not be converted Effect The operation fails Recovery Check your input and resubmit SQL 8423 Cause You specified a field number that is not valid Effect The operation fails Recovery Correct the syntax and resubmit 8419 An arithmet...

Page 264: ... the syntax and resubmit without a null value SQL 8427 Cause A sort error occurred The error returned appears as detail text Effect The operation fails Recovery Use the information in the sort error to diagnose and correct the problem SQL 8428 Where name is the name of the function Cause You specified an invalid argument for the function name Effect The operation fails Recovery Correct the syntax ...

Page 265: ...ing assigned and retry the operation SQL 8433 Where char set is the name of the character set SJIS or UTF8 function is the function name Cause 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 8550 Where NSK err is the HP NonStop Kernel error returned Cause The HP NonStop...

Page 266: ...ect name Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 8552 Where num is the error number returned Where name is the name of the system Cause The file system returned error num Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem 8551 Error NS...

Page 267: ...ion See the Operator Messages Manual for information on retrieving EMS event messages Recovery None Contact your service provider SQL 8570 Cause The system does not have enough memory to build the query Effect The operation fails Recovery Try to reduce the system s load by entering fewer statements You can try restarting NonStop SQL MX If this does not correct the problem contact your service prov...

Page 268: ...ame is the name of the object Cause You attempted to perform an operation on object name for which you do not have a sufficient privilege level Effect The operation fails Recovery None Have the system administrator change your privilege level if appropriate SQL 8574 Where name is the name of the table Cause While you had table name open another operation such as DDL changed that table Effect The t...

Page 269: ...NonStop SQL MX recompiled the statement Effect The operation fails Recovery Recompile the program SQL 8577 Where name is the name of the object Cause NonStop SQL MX could not find the object name Effect The operation fails Recovery Verify the location of the object and resubmit SQL 8578 Cause The similarity check passed Effect None Recovery Informational message only no corrective action is needed...

Page 270: ...SQL 8581 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 SQL 8598 Cause An attempt was made to access a view that no longer exists Effect The query fails Recovery Verify that the v...

Page 271: ...iagnose and correct the problem See Process Control Procedure Errors on page 1 4 SQL 8603 Cause You attempted to begin a transaction that has already been started Effect The operation fails Recovery Correct the syntax so that the transaction is started only once and resubmit SQL 8604 Where name is the subsystem name Where number is the error number Cause Transaction subsystem name has returned err...

Page 272: ... Transaction subsystem name has returned error number while committing a transaction Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 8607 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 SQ...

Page 273: ...esubmit SQL 8610 Where name is the name of the subsystem Where number is the error number Cause Transaction subsystem name has returned error number while performing a waited rollback transaction Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 8612 Cause You attempted to set the transaction mode but the transaction i...

Page 274: ...use The source contains a character that cannot be translated to the target Effect The operation fails Recovery Make sure the source data is clean and translatable and resubmit SQL 8700 Cause An ESP encountered an error during a query Effect The query fails Recovery Use the EMS event log information in the event generated by this failure to diagnose and correct the problem You might need to alloca...

Page 275: ...Retry the UNLOAD MODULE command after ending the transaction by committing or aborting it SQL 8751 Cause The module name specified in the UNLOAD MODULE command refers to a system module file Effect None Recovery Change the module name to refer to the correct user module and retry the operation SQL 8801 Cause This is an internal error Effect The operation fails Recovery None Contact your service pr...

Page 276: ...overy None Contact your service provider SQL 8805 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 8806 Cause This is an internal error 8802 Statement allocation failed because the statement already exists in the current context 8803 The provided input descriptor does not exist in the current context 8804 The provided input statement does n...

Page 277: ... file See the subsection Understanding and Avoiding Some Common Run time Errors in the SQL MX Programming Manual for C and COBOL for more information SQL 8809 Where name is the name of the file Where number is the error number returned Cause NonStop SQL MX was unable to open module file name Effect The operation fails Recovery Check the location of the module file and retry the operation For more ...

Page 278: ...e Contact your service provider SQL 8814 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 8815 Cause This is an internal error 8811 Trying to close a statement that is either not in the open state or has not reached EOF 8812 Trying to execute a statement that is not in the closed state 8813 Trying to fetch from a statement that is in the cl...

Page 279: ...anual 640324 001 10 31 Effect The operation fails Recovery None Contact your service provider SQL 8816 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider 8816 An internal error occurred while executing the TCB tree ...

Page 280: ... The operation fails Recovery None Contact your service provider SQL 8820 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 8821 Cause This is an internal error Effect The operation fails 8817 An internal error occurred while fetching from the TCB tree 8818 An internal error occurred in root_tdb describe 8819 Begin transaction failed while p...

Page 281: ...operation fails Recovery None Contact your service provider SQL 8824 Cause A module name was not passed into the module ID structure that was passed in Effect The operation fails Recovery Make sure a module name is passed into the module ID structure SQL 8825 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider 8822 The statement was not prepared 8...

Page 282: ...gnose and correct the problem SQL 8828 Cause NonStop SQL MX ran out of memory while creating the internal structure name Effect The operation fails Recovery Increase NonStop SQL MX s memory and resubmit SQL 8829 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider 8826 The module could not be added 8827 The request name could not be sent 8828 Out o...

Page 283: ...ion fails Recovery Verify that the transaction has been started or start it if it has not been SQL 8833 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 8834 Where number is the error number 8830 There is no current context 8831 Either no current context or the module to which the statement belongs is not added to the current context 8832 T...

Page 284: ... this code is embedded in The build might not have completed correctly Effect The operation fails Recovery Verify that the build was successful and resubmit SQL 8837 Where number1 is the file system error returned by proc call Where number2 is the status code returned by proc call Where proc call is the name of the file system procedure call returning the error Cause The value of the user ID is no...

Page 285: ... SQL 8840 Cause The object named provided to CLI is invalid Effect The operation fails Recovery Correct the object name and resubmit SQL 8841 Cause NonStop SQL MX started a transaction that was committed or aborted by an embedded program rather than by NonStop SQL MX Effect The operation fails Recovery Commit or abort the transaction by calling SQL COMMIT or ROLLBACKWORK 8838 Unable to receive rep...

Page 286: ... allocated Effect The operation fails Recovery Specify a valid number between 1 and the maximum allocated item count of the descriptor SQL 8844 Cause After NonStop SQL MX started a transaction that was committed or aborted by an embedded program rather than from NonStop SQL MX you used SQL COMMIT or ROLLBACKWORK to properly finish the transaction Effect None Recovery Informational message only no ...

Page 287: ...blem and resubmit SQL 8848 Cause You attempted to enter a break while running DDL statements or internal table valued functions Effect The operation fails Recovery None SQL 8850 Cause The table specified in the update or DELETE statement is not the same as the one specified in the declare cursor statement as is required Effect The operation fails Recovery Correct the syntax and resubmit 8846 An em...

Page 288: ... definition Effect The operation fails Recovery Correct the syntax and resubmit SQL 8854 Cause You specified an invalid attribute value Effect The operation fails Recovery Correct the syntax and resubmit SQL 8855 Cause You attempted to set a statement attribute after a statement was compiled The attribute must be set before compilation Effect The operation fails 8851 A CLI Parameter bound check er...

Page 289: ...ct the syntax and resubmit SQL 8859 Cause The current operation failed because there is a pending INSERT DELETE or UPDATE operation Effect The operation fails Recovery Complete the outstanding operation and try again SQL 8860 Where 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 8856 Specified a...

Page 290: ...odule file and resubmit SQL 8863 Where name is the file name Cause The module file name has an obsolete descriptor header Effect The operation fails Recovery Rebuild the module file and resubmit SQL 8864 Where name is the file name Cause The module file name has an obsolete descriptor entry Effect The operation fails Recovery Rebuild the module file and resubmit 8861 Module file name has an obsole...

Page 291: ...ere name is the file name Cause NonStop SQL MX encountered an error while reading the module file name Effect The operation fails Recovery Rebuild the module file and resubmit SQL 8868 Cause The application did not start its own transaction Multiple contexts are not allowed when the transaction is started by NonStop SQL MX Effect The operation fails Recovery None Contact your service provider 8865...

Page 292: ...der SQL 8871 Cause A nowait tag was not specified Effect The operation fails Recovery None Contact your service provider SQL 8872 Cause Only one nowait operation at a time is allowed on an SQL MX statement Effect The operation fails Recovery None Contact your service provider 8869 The specified file number in not a QFO or the file number is not internally associated with a QFO object CLI internal ...

Page 293: ...ction attribute AUTOBEGIN to ON and rerun the statement SQL 8878 Cause The CONTROL QUERY DEFAULT value for DOOM_USERTRANSACTION is ON and NonStop SQL MX encountered an unrecoverable error Effect The transaction is in a doomed state Users are unable to continue work on this transaction Recovery Use the ROLLBACK WORK statement to undo the transaction explicitly 8873 The current statement is already ...

Page 294: ...sponding SQL request is rejected Recovery Either change the definition of the stored procedure to allow SQL access or determine why the stored procedure contains SQL MX statements that might be called while the stored procedure is executing SQL 8883 Cause The server failed to enable UDR violation checking prior to issuing an SQL MX CLI function call to check or clear the UDR violation flags Effect...

Page 295: ...n was unable to provide a proxy syntax for a stored procedure result set because the provided target buffer is either null or not big enough Effect The operation fails Recovery Make the CLI call again and use a buffer big enough to hold the proxy syntax Consider using the len_of_item output parameter from the first CLI call to obtain the actual size of the buffer needed to return the proxy syntax ...

Page 296: ...ent whose argument count does not match the descriptor entry count Effect The operation fails Recovery Correct the syntax and resubmit SQL 8894 Cause A value that was passed into an SQL MX CLI function containing a reserved parameter was not the value expected by NonStop SQL MX Effect The CLI function fails Recovery None Contact your service provider 8891 Non ASCII character host variable type was...

Page 297: ...of the host variable so that the character set name matches the descriptor item SQL 8897 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 8898 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider 8895 The character set name for the descriptor item SQLDESC_CHAR_SET is not valid 8896 The chara...

Page 298: ...Recovery None Contact your service provider SQL 8903 Where process name is the name of an SQL MX UDR server process Cause NonStop SQL MX received an interrupt signal possibly caused by an MXCI user pressing Ctrl C while the SQL MX UDR server was executing a stored procedure Effect The operation fails and if PROCESS_STOP_ was successful as indicated by a return value of 0 the SQL MX UDR server is s...

Page 299: ... have the stored procedure s owner or another authorized user grant you the required EXECUTE privilege and then resubmit SQL 8906 Cause During execution of an SQL MX statement the SQL MX executor received a message from the SQL MX UDR server that was unreadable in some way Either the message was corrupted by the SQL MX UDR server or an internal error occurred within the SQL MX executor Effect The ...

Page 300: ...ed procedure result sets cannot be allocated from statements other than CALL statements Effect The operation fails Recovery None Contact your service provider SQL 8912 Cause An internal error was detected within the SQL MX executor during allocation of a stored procedure result set Effect The operation fails Recovery None Contact your service provider SQL 8913 Cause A CLI application attempted to ...

Page 301: ... fails Recovery None Contact the GMCSC and report this condition SQL 8916 where index is an integer specifying a position in the ordered set of result sets returned from a CALL statement max result sets is the maximum number of result sets that can be returned from the associated CALL statement 8914 An attempt to open a stored procedure result set failed because multiple open operations on the sam...

Page 302: ...ct The operation fails Recovery None Contact GMCSC and report this condition SQL 8917 where index is an integer specifying a position in the ordered set of result sets returned from a CALL statement Cause A call level interface CLI application attempted to bind multiple stored procedure result set statements to the same result set index Effect The operation fails Recovery None Contact GMCSC and re...

Page 303: ...m stop and restart NonStop SQL MX If this does not correct the problem report the entire message to your service provider SQL 9202 Cause UPDATE STATISTICS has located previously generated histograms that are not being regenerated Effect Processing continues without interruption Recovery Remove or replace previously generated histograms by performing either one of these two recovery actions Reexecu...

Page 304: ...t SQL 9205 Cause You attempted to run UPDATE STATISTICS against an object that is not supported Effect NonStop SQL MX is unable to continue processing Recovery Correct the syntax and resubmit SQL 9206 Cause NonStop SQL MX could not perform an UPDATE STATISTICS statement because you are not authorized to perform this operation against this table You must either own the object name or be the super I...

Page 305: ...entire message to your service provider SQL 9209 Cause You tried to access column name which does not exist in object name Effect The operation fails Recovery Check the column name and resubmit SQL 9210 Cause You attempted to perform UPDATE STATISTICS on a column whose data type does not support this operation Effect The operation fails Recovery Exclude this column from the column list and resubmi...

Page 306: ...SQL MX is unable to continue processing Recovery Resubmit the statement If this does not correct the problem stop and restart NonStop SQL MX If this does not correct the problem report the entire message to your service provider SQL 9215 Cause UPDATE STATISTICS received an internal error at the location with error code errorcode implying otherdetails Effect The operation fails Recovery Do not atte...

Page 307: ... clause is specified the UPDATE STATISTICS command populates the sample table with some temporary records At the end of the operation these records are deleted Effect The sample table is not empty This has no effect on the statistics that have already been collected If the sample table is used again before all the records are deleted the UPDATE STATISTICS command will return an error 9219 Recovery...

Page 308: ... besides degrading performance Effect The operation fails Recovery Drop all the indexes and triggers on the sample table and resubmit SQL 9221 where table name is the name of a SQL MX table Cause Either the table for which the statistics have to be collected or the user specified sample table is not a SQL MX table it is either a SQL MP table or some other object such as index or a view The USING S...

Page 309: ...ring the merge phase of a sort The sort error would indicate any low level sort error and the system error if any would indicate the low level system error If the cause is only a sort error the system error may be 0 Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 10005 Cause An unknown sort error occurred Effect The operation fails Recovery Do not atte...

Page 310: ... specified an invalid sort algorithm Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 10010 Cause The scratch run on the disk does not belong to any scratch block on the disk Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 10011 Where system error is the error returned Cause An I O error occurred during a sc...

Page 311: ... disks and Storage Management Foundation SMF virtual disks are not considered suitable See the SQL MX Reference Manual for more information on how to influence the placement of scratch files SQL 10014 Cause An internal data structure could not be allocated because of an out of memory condition Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 1001...

Page 312: ...g a system level call Effect The operation fails Recovery Contact your service provider SQL 10019 Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact your service provider SQL 10020 Cause An error occurred while calling a system level call 10016 Sort failed while calling PROCESSHANDLE_DECOMPOSE_ with error number 10017 Sort failed while calling DEV...

Page 313: ...vel call Effect The operation fails Recovery Contact your service provider SQL 10023 Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact your service provider SQL 10024 Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact your service provider 10021 Sort failed while calling FILE_GETINFOLISTBYNAME_ w...

Page 314: ...SQL 10027 Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact your service provider SQL 10028 Cause An error occurred while calling a system level call Effect The operation fails Recovery Contact your service provider SQL 10029 Cause An error occurred while calling a system level call Effect The operation fails 10025 Sort Error FileClose failed 100...

Page 315: ... service provider SQL 10032 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10033 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10034 Cause An error occurred while calling a system level call 1003...

Page 316: ...t The operation fails Recovery No recovery possible Contact your service provider SQL 10037 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10038 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 1003...

Page 317: ...use An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10042 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10043 Cause An error occurred while calling a system level call Effect The operation fails Recover...

Page 318: ...stem level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10046 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10047 Cause The length of the data returned was not what was expected Effect The operation fails Recovery None This is an internal error C...

Page 319: ...pecifically for scratch use SQL 10049 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 Contact your service provider SQL 10051 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider 10048 IO to a scratch ...

Page 320: ... problem SQL 10102 Where operator is the SQL MX query operator that encountered the error for example merge join number is a SQL MX platform internal procedure error number Cause The query operator was unable to open a scratch file Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 10103 Where operator is the SQL MX query operator that encountered ...

Page 321: ...e operation fails Recovery Contact your service provider to diagnose the cause of the WRITEX returned error and correct the problem SQL 10105 Where operator is the SQL MX query operator that encountered the error for example merge join number is an SQL MX platform internal procedure error number Cause The query operator was unable to read from a scratch file Effect The operation fails Recovery Con...

Page 322: ... SQL MX platform internal procedure error number Cause The query operator failed to complete a scratch file asynchronous I O operation Effect The operation fails Recovery None This is an internal error Do not attempt recovery Contact your service provider SQL 10112 Where operator is the SQL MX query operator that encountered the error for example merge join number is an SQL MX platform internal pr...

Page 323: ...oin number is an SQL MX platform internal procedure error number Cause An invocation of FILE_GETINFOLIST_ failed Effect The operation fails Recovery None This is an internal error Do not attempt recovery Contact your service provider SQL 10115 Where operator is the SQL MX query operator that encountered the error for example merge join number is an SQL MX platform internal procedure error number C...

Page 324: ...er SQL 10117 Where operator is the SQL MX query operator that encountered the error for example merge join number is an SQL MX platform internal procedure error number Cause The operation fails Effect The operation fails Recovery None This is an internal error Do not attempt recovery Contact your service provider SQL 10118 Where operator is the SQL MX query operator that encountered the error for ...

Page 325: ... The operation fails Recovery None This is an internal error Do not attempt recovery Contact your service provider SQL 10130 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10131 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Conta...

Page 326: ...n fails Recovery No recovery possible Contact your service provider SQL 10135 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10136 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10137 Cause An err...

Page 327: ...ile calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10140 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible Contact your service provider SQL 10141 Cause An error occurred while calling a system level call Effect The operation fails Recovery No recovery possible C...

Page 328: ... operator that encountered the error for example merge join Cause The threshold specified by the default SCRATCH_FREESPACE_THRESHOLD_PERCENT was reached on all available scratch disks 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 Where operator is the SQL MX query operator that encountered...

Page 329: ...act your service provider SQL 10153 Where operator is the SQL MX query operator that encountered the error for example merge join Cause The mapping of data blocks to scratch files is incomplete Effect The operation fails Recovery None This is an internal error Do not attempt recovery Contact your service provider 10153 operator attempted to read data using a block number that was not mapped to a s...

Page 330: ...Executor Sort and Scratch File I O Messages 10000 through 10199 HP NonStop SQL MX Messages Manual 640324 001 12 22 Scratch File I O Messages ...

Page 331: ...TableName is the subject table name of trigger TriggerName Cause During execution a trigger was generated recursively more than 16 times Effect The operation succeeds Recovery None This is a warning only SQL 11003 Where TriggerName is the name of one of the triggers in the triggering cycle Where TableName is the subject table name of trigger TriggerName Cause During execution a trigger was generat...

Page 332: ...s than 123 characters SQL 11006 Cause Rowsets were used in a statement that is a trigger event Effect The operation fails Recovery Either remove the rowset from the statement or drop all triggers defined on the table and operation that caused the error For example if the operation is a delete you need to drop all delete triggers defined on the DELETE statement target table If the triggers cannot b...

Page 333: ...mpted to create a DELETE trigger specifying a NEW transition variable Effect The operation fails Recovery You cannot use the NEW transition variable with a DELETE trigger because there is no new image for a row to be deleted SQL 11014 Cause You attempted to create a BEFORE trigger with a trigger action other than SIGNAL or SET Effect The operation fails Recovery If SET or SIGNAL does not work dete...

Page 334: ...ssignment is to an identifier Effect The operation fails Recovery Prefix the assignment to the SET operation with the NEW transition variable name and resubmit SQL 11018 Cause An attempt was made during DDL to create an AFTER trigger with an unsupported action In particular this error is raised if the trigger action is a compound statement an embedded DELETE or an embedded UPDATE Effect The operat...

Page 335: ...very Correct the create trigger statement and resubmit SQL 11021 Cause You attempted to use the subject table name as a transition variable name Effect The operation fails Recovery Use a different name for the transition variable name and resubmit SQL 11022 Where column name is the column name Where table name is the trigger subject table name Cause You attempted to create a trigger that had a tri...

Page 336: ...transition variables and resubmit SQL 11025 Cause An INSERT statement in a compound statement has as its target a trigger subject table on which INSERT triggers are defined An UPDATE statement in a compound statement has as its target a trigger subject columns on which UPDATE triggers are defined A DELETE statement in a compound statement has as its target a trigger subject table on which DELETE t...

Page 337: ...T ON ROLLBACK clause is the same as one of the subject columns of the trigger If the triggers cannot be dropped you might want to avoid performing SET ON ROLLBACK statements on the subject columns SQL 11027 Cause The target table of an embedded DELETE statement is the subject table of a DELETE trigger The target columns of an embedded UPDATE statement are the subject columns of an UPDATE trigger T...

Page 338: ...ecovery None Redesign the triggers in such a way that this condition is not raised This usually involves following the cascading of triggers and identifying when the column is being modified more than once From error 11028 which was raised along with this error you can identify the trigger that made the second change to the same column of a given row SQL 11030 Cause You attempted to drop or alter ...

Page 339: ...ble name you are attempting to drop Cause You attempted a drop table cascade on a table that contains defined triggers Effect The operation succeeds Recovery None This is a warning only SQL 11035 Cause You attempted to create a trigger on a metadata table Effect The operation fails Recovery None SQL 11036 Where table name is the name of the specified table Cause You attempted to alter trigger enab...

Page 340: ...t trigger is created is longer than the allowed maximum length The length of the temporary table name is longer than the maximum allowed user table name length Effect The operation fails Recovery If the primary key length is too long re create your subject table with a primary key that is 12 bytes shorter than the maximum allowed primary key length If the table name is too long re create your subj...

Page 341: ...cifies the optional ROW keyword specified Effect The operation fails and the trigger is not created Recovery Correct the syntax so that a row trigger uses the ROW keyword in its referencing clause and a statement trigger uses the TABLE keyword in its referencing clause You can remove the optional keyword because it can be implied from the for each clause if specified If the optional keyword is not...

Page 342: ...received a request for a stored procedure that is no longer present in the SQL MX UDR server context Effect The request message is rejected and the SQL MX statement fails Recovery Do not attempt recovery Contact your service provider SQL 11103 Cause The SQL MX UDR server encountered an internal error Either an SQL MX language manager operation failed or an SQL MX UDR server data structure was dete...

Page 343: ... message is rejected and the SQL MX statement fails Recovery Do not attempt recovery Contact your service provider SQL 11108 Where object name is the name of the object Cause The SQL MX UDR server was not able to obtain enough memory to allocate the named object Effect The request message is rejected and the SQL MX statement fails Recovery Stop and start the client process to restart a new SQL MX ...

Page 344: ...This is a warning message only SQL 11201 Where class name is the name of the Java class Cause Initialization of the language manager failed because a required Java class could not be loaded or because a required Java method was not found Effect The operation fails Recovery Check the installation of the HP NonStop Server for Java product and the SQL MX language manager Verify the existence of the s...

Page 345: ...statement SQL 11204 Where method name is the name of a Java method Where description is text further explaining the problem Cause During a CREATE PROCEDURE operation the specified Java method could not be located for verification purposes Effect The operation fails Recovery Determine if the Java class file specified in the CREATE PROCEDURE statement exists Determine if the Java method exists in th...

Page 346: ...was not modified after it was generated with the NonStop Server for Java javac utility SQL 11207 Cause The Java method given in the CREATE PROCEDURE statement was not found in the class file or if this is a CALL statement the Java method corresponding to the stored procedure was not found in the class file Effect The operation fails Recovery Verify that the Java method exists in the class file and...

Page 347: ...ecified parameter position did not have opening and closing square brackets in the EXTERNAL NAME clause Effect The operation fails Recovery Correct the EXTERNAL NAME clause and resubmit SQL 11211 Cause In a CREATE PROCEDURE statement an unknown or unsupported parameter type was used at the specified parameter position in the SQL parameter list or in the EXTERNAL NAME clause Effect The operation fa...

Page 348: ...he EXTERNAL NAME clause Effect The operation fails Recovery Correct the EXTERNAL NAME clause and resubmit SQL 11214 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 clause and resubmit SQL 11215 Cause A null value was supplied as input to a stored procedure in Java and the...

Page 349: ... SQL 11217 Cause During execution of a CALL statement numeric or string overflow occurred while processing the stored procedure output value returned in parameter parameter number Effect None this is a warning message Recovery Increase the field size of the SQL data type for the specified parameter SQL 11218 Cause During execution of a CALL statement a Java exception was thrown Effect The operatio...

Page 350: ...ry Review the Java method Determine whether it is appropriate in your application for this exception to be thrown or whether it should be caught and handled by your user defined routine Retry the SQL MX statement SQL 11221 Cause The language manager could not acquire enough memory to complete its work on the SQL MX statement Effect The operation fails Recovery Stop and restart the session and retr...

Page 351: ... service provider SQL 11224 Cause The Java Virtual Machine encountered an internal error and raised an exception More information appears in detail text Also see the errors that accompany this message for more information Effect The operation fails Recovery Perform whatever corrective action is required to eliminate the Java exception Stop and restart the session and retry the SQL MX statement SQL...

Page 352: ... was used in SQL parameter list All SQL parameters associated with Java main methods must have a character data type Effect The operation fails Recovery Correct the SQL parameter list and retry the SQL MX statement SQL 11228 Cause An error occurred in the language manager while converting an input value from the TNS to IEEE floating point format or while converting an output value from the IEEE to...

Page 353: ... NAME clause of a CREATE PROCEDURE statement 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 zero each method also had one or more trailing jav...

Page 354: ...TE PROCEDURE statement Where class name is the Java class name specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement Cause During the execution of a CREATE PROCEDURE statement a method named method name was found in the specified Java class but the method did not have the static attribute Effect The operation fails Recovery Correct the signature of the SPJ method and then resubmit ...

Page 355: ...35 Where parameter position is the position of the result set parameter in the Java method signature Cause During the execution of a CALL statement an SPJ method returned result sets but the result sets could not be processed because the language manager encountered an unexpected error trying to retrieve the information for the result set at position parameter position in the Java method signature...

Page 356: ...a CALL statement an SPJ method returned result sets but the result sets could not be processed because the version of JDBC MX in the SPJ environment does not support stored procedure result sets Effect The operation fails Recovery Change the version of JDBC MX in the SPJ environment to one that supports stored procedure result sets SQL 11238 Where procedure name is the ANSI name of a stored proced...

Page 357: ...rameters Effect The operation fails Recovery Ensure that the SPJ method exists in the specified class file and resubmit SQL 11240 Where index is the ordinal position of the parameter specified in the EXTERNAL NAME clause of a CREATE PROCEDURE statement Cause The parameter at position index is not java sql ResultSet Effect The operation fails Recovery Ensure that the specified signature trailing pa...

Page 358: ... The operation fails Recovery Do not attempt recovery Contact your service provider SQL 11243 Where 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 JDBC Type driver server side because a java sql ResultSet getter method getLong getString and...

Page 359: ...324 001 13 29 Cause While processing a stored procedure result set the language manager was unable to process a DECIMAL value at the specified column position because the value contained a character other than a digit Effect The operation fails Recovery Do not attempt recovery Contact your service provider ...

Page 360: ...Trigger UDR Server and Language Manager Messages 11000 through 11399 HP NonStop SQL MX Messages Manual 640324 001 13 30 ...

Page 361: ...ocessor ignores the line Recovery Correct the error and resubmit SQL 13003 Cause You attempted to perform an SQLCO function that is not supported Effect The operation fails Recovery None If the problem persists contact your service provider SQL 13004 Cause The preprocessor has executed successfully Effect None Recovery Informational message only no corrective action is needed 13001 An internal err...

Page 362: ...to process with this value Recovery Internal error Contact your service provider SQL 13007 Cause You specified the c option without giving the output file argument which is required Effect The operation fails Recovery Provide the output file argument and resubmit The syntax is c out file where out file specifies the name of the preprocessed output source file containing the translated embedded SQL...

Page 363: ...ecovery Provide the listing file argument and resubmit The syntax is l list file where list file is the name of the SQL MX C C preprocessor error and warning message file SQL 13010 Cause You specified the t option without giving the timestamp argument which is required Effect The operation fails Recovery Provide the timestamp argument and resubmit The syntax is t timestamp where timestamp is a cre...

Page 364: ... only no corrective action is needed See online help for SQLC and SQLCO if necessary SQL 13014 Cause The preprocessor was unable to open file name Effect The preprocessor ignores the referenced file Recovery Verify that the file exists and is readable and resubmit SQL 13015 Cause The preprocessor was unable to open the module definition file name Effect The preprocessor ignores the referenced modu...

Page 365: ...y Remove the duplicate definition and resubmit SQL 13018 Cause You specified the descriptor name which is invalid Effect The preprocessor ignores the invalid descriptor name Recovery Correct the definition of this name and resubmit Descriptor name is a value specification a literal or host variable with character data type SQL 13019 Cause You specified the statement name which is a reserved name i...

Page 366: ...hich you attempted to define has already been defined Effect The preprocessor ignores the duplicate definition Recovery Remove the duplicate definition and resubmit SQL 13023 Cause The cursor name which you attempted to define has already been defined as a dynamic cursor Effect The preprocessor ignores the second definition of the cursor Recovery Remove the duplicate definition and resubmit SQL 13...

Page 367: ...Cause You specified more than one EXEC SQL MODULE statement when only one is supported Effect The preprocessor ignores the second EXEC SQL MODULE statement Recovery Remove the extra EXEC SQL MODULE statement and resubmit SQL 13028 Cause The host variable you specified in the declare cursor name could not be used because it was out of scope at the time you attempted to open it Effect The preprocess...

Page 368: ...EXECUTE IMMEDIATE statement The preprocessor found one of these errors You did not specified more than one host variable of this type The host variable that you specified is not character type STRING Effect The preprocessor ignores the host variable Recovery Correct the host variable and resubmit SQL 13032 Cause You specified input host variables for cursor name An open cursor does not need host v...

Page 369: ...haracter set name you specified with one that is supported See the SQL MX Reference Manual for information about character sets SQL 13035 Cause You specified an invalid line number Effect The preprocessor ignores the line Recovery Remove or correct the line number and resubmit SQL 13036 Cause The preprocessor encountered a C C syntax error near line number Effect The preprocessor ignores the switc...

Page 370: ...9 Cause You specified a function definition within an SQL MX declare section near line number which is not supported Effect The preprocessor ignores the function definition Recovery Move the function definition and resubmit SQL 13040 Cause The preprocessor requires a right parenthesis near line number Effect The preprocessor ignores the parenthetical statement Recovery Correct the syntax by adding...

Page 371: ...uired one of these items equal sign comma or right parenthesis and did not find it The missing syntax item is near line number Effect The preprocessor ignores the declaration list that contains this item Recovery Correct the syntax and resubmit SQL 13044 Cause You specified an unrecognized type specification near line number Effect The preprocessor ignores the type specification Recovery Replace t...

Page 372: ...ply the missing bracket SQL 13047 Cause You specified an undefined tag name near line number Effect The preprocessor ignores the tag Recovery Define the tag and resubmit SQL 13048 Cause You redefined tag name near line number Effect The preprocessor ignores the redefinition Recovery Remove the redefinition and resubmit SQL 13049 Cause The preprocessor could not read the input file Effect The prepr...

Page 373: ...ursor could not be used Recovery Open the cursor SQL 13052 Cause Cursor name was not fetched Effect None Recovery Informational message only no corrective action is needed SQL 13053 Cause Cursor name was not opened or closed Effect The cursor could not be used Recovery Open the cursor SQL 13054 Cause Cursor name was not fetched or closed Effect None 13050 Cursor name is not closed 13051 Cursor nam...

Page 374: ...sing the preprocessor received an unexpected cursor status for cursor name Effect The preprocessor fails Recovery Internal error Contact your service provider SQL 13058 Cause The preprocessor was unable to open the SQL CLI header file name Effect The preprocessor ignores the SQL CLI header file Recovery Verify that the SQL CLI header file exists and is readable and resubmit 13055 Cursor name is no...

Page 375: ...IC item Recovery Correct the precision of the item and resubmit SQL 13062 Cause You did not specify a corresponding SQL MX type for an UNSIGNED LONG LONG 8 byte integer item Effect The preprocessor ignores the integer item Recovery Specify a corresponding SQL MX type for this item SQL 13063 Cause Identifier name was not defined near line number Effect The preprocessor ignores the identifier Recove...

Page 376: ...ng until it reaches the end of file or finds a colon If it reaches end of file first and the very next thing the preprocessor finds before reaching the end of file is the name of a host variable the message would look like this ERROR 13065 End of file was found after host variable expression when was expected near line 54 Effect The preprocessor ignores the identifier Recovery Correct the syntax a...

Page 377: ... argument Effect The option is incomplete and mxsqlc or mxsqlo returns this error message Recovery Reinvoke the preprocessor either by totally omitting the g option or by supplying a complete g option g moduleGroup g moduleTableset or g moduleVersion SQL 13070 Cause The Module Group Specification String MGSS you specified is not a regular identifier or is longer than 31 characters Effect The embed...

Page 378: ...alid characters or has more than 128 characters Effect The module name is invalid and this error is generated Recovery Reinvoke the preprocessor this time supplying an embedded SQL source file that has a valid module name in its MODULE directive SQL 13074 Cause An externally qualified module name consists of three parts a catalog a schema and a one part module name that has been qualified with Mod...

Page 379: ...ter value for any or all of the MGSS MVSS MTSS for the one part module name coded in the embedded SQL source file s MODULE directive or the default catalog or schema if the MODULE directive is encoded as a one part name SQL 13076 Cause the four invalid characters or has more than 128 characters Effect The catalog name is invalid and this error is generated Recovery Reinvoke the preprocessor this t...

Page 380: ...se You invoked the COBOL preprocessor MXSLCO and the process of externally qualifying the input source file s MODULE directive resulted in a module file name that exceeds COBOL s maximum length for a nonnumeric literal Effect The command fails Recovery Shorten one or more of the following and reissue the COBOL preprocessing command The module name in the input source file s MODULE directive g modu...

Page 381: ...ause You did not enter the file name for the command option name Effect The operation fails Recovery Correct the syntax and resubmit SQL 13504 Cause You did not enter the timestamp command option Effect The operation fails Recovery Correct the syntax and resubmit SQL 13505 Cause NonStop SQL MX could not open the source input file name Effect The operation fails 13501 Specified command option name ...

Page 382: ...d an error while parsing the source detail text Effect The operation fails Recovery Correct the syntax and resubmit SQL 13508 Cause You did not enter the keyword or character that NonStop SQL MX required When the preprocessor is processing the code within a control block such as IF WHILE DO or is at the end of one it looks for the keyword that ends that block and then a semicolon and issues this m...

Page 383: ...OR 13509 Expecting DIVISION after DATA found EXEC This error is issued if the preprocessor does not find the keyword SECTION immediately after any of these keywords FILE LINKAGE ERROR 13509 Expecting SECTION after FILE found EXEC This error is issued if the preprocessor does not find the picture representation immediately after the keyword PICTURE ERROR 13509 Expecting picture specification after ...

Page 384: ...an input file error while processing EXEC SQL Effect The operation fails Recovery Use the errors that accompany this one to diagnose and correct the problem SQL 13513 Cause You specified the BIT data type which is not supported in NonStop SQL MX Effect The operation fails Recovery Specify a data type that NonStop SQL MX supports SQL 13514 Cause You specified the CHARACTER SET attribute which is no...

Page 385: ...SQL MX reached the end of the input file while processing EXEC SQL Effect The operation fails Recovery Correct the input file and resubmit SQL 13517 Cause The text in line number is longer than the buffer and has been truncated Effect NonStop SQL MX truncates the line which can affect compilation Recovery Correct the syntax and resubmit SQL 13518 Cause The text in line number could not be interpre...

Page 386: ...fails Recovery Correct the syntax and resubmit SQL 13521 Cause You attempted to define a DISPLAY host variable other than as a SIGN LEADING SEPARATE data type at line number Effect The operation fails Recovery Correct the syntax and resubmit SQL 13522 Cause You specified the DECLARE SECTION as nested code Effect The operation fails Recovery Correct the syntax and resubmit 13519 Line number contain...

Page 387: ...rrectly for a host variable Effect Check that you declared the variable correctly An incorrect variable can result in incorrect data from the COBOL compiler Recovery Informational message only no corrective active is needed SQL 13526 Cause You specified a clause type JUST or OCCURS clause for variable name on line number Effect The operation fails Recovery Correct the syntax and resubmit 13523 END...

Page 388: ...ails Recovery Correct the syntax and resubmit SQL 13529 Cause The END DECLARE SECTION statement is missing near line number Effect The operation fails Recovery Correct the syntax and resubmit SQL 13800 Cause You specified an invalid character set name at line number Effect The operation fails Recovery Correct the syntax and resubmit 13527 The first declaration in a SQL DECLARE SECTION must have le...

Page 389: ...r service provider SQL 15003 Cause You specified an incomplete statement which appears in detail text The most common error is a missing semicolon at the end of a statement Effect The operation fails Recovery Correct the syntax and resubmit SQL 15004 Cause NonStop SQL MX has received error number while attempting to change directory Effect The operation fails Recovery Correct the error and resubmi...

Page 390: ...received error number while reading from file name The error number depends on the operating system Effect The operation fails Recovery Use the error number to diagnose and correct the problem SQL 15008 Cause You attempted to reference a statement from the history buffer but the statement does not exist there Effect The operation fails Recovery Check your entry for x instead of s If you specified ...

Page 391: ...company this one to diagnose and correct the problem SQL 15011 Cause You requested help for a topic that does not have help available Effect The operation fails Recovery See the documentation for this topic SQL 15012 Cause NonStop SQL MX was unable to read the help file Effect The operation fails Recovery Use the messages that accompany this one to diagnose and correct the problem 15009 The reques...

Page 392: ...ssing add it to the file and resubmit SQL 15015 Cause You tried to convert parameter name to data type Effect The operation fails Recovery Correct the syntax and resubmit SQL 15016 Cause NonStop SQL MX did not find parameter name Effect The operation fails Recovery Correct the syntax and resubmit SQL 15017 Cause NonStop SQL MX did not find statement name Effect The operation fails 15013 This comma...

Page 393: ...covery Correct the syntax and resubmit SQL 15020 Cause You specified an EXECUTE command with a USING clause but you did not specify parameter values NonStop SQL MX requires at least one parameter value Effect The operation fails Recovery Correct the syntax and resubmit SQL 15021 Cause You specified an EXECUTE command with a USING clause that has more parameter values than are supported Effect The ...

Page 394: ...olon Effect The operation fails Recovery Correct the syntax and resubmit SQL 15025 Cause You attempted to perform a cursor operation which is not supported by MXCI Effect The operation fails Recovery Correct the syntax and resubmit SQL 15026 Cause A break you specified to cancel an SQL MX statement failed Effect The operation fails Recovery None Report the entire message to your service provider 1...

Page 395: ...R on the object that was being operated on to ensure that it is returned to a consistent state SQL 15030 Cause You attempted to add a define that already exists Effect The operation fails Recovery Alter the existing define or delete and add it SQL 15031 Cause You attempted to use a define that does not exist Effect The operation fails Recovery Correct the define name or add it and resubmit 15028 B...

Page 396: ...ified an invalid LOG file name Effect The operation fails Recovery Correct the file name and resubmit SQL 15035 Cause NonStop SQL MX was unable to access the file Effect The operation fails Recovery Check the file permissions and reset them if necessary SQL 15036 Cause You specified an invalid file code or invalid function argument Effect The operation fails 1503 An error occurred while adding alt...

Page 397: ...n Procedure Errors and Messages Manual If another error number in included in the message it likely refers to an SQL MX error message documented in this manual SQL MX Messages Manual Cause A lower level error is reported This message is usually intended for debug purposes but it also can give information relating to the problem It is the third in a string of three error messages with the primary e...

Page 398: ...he event primary message to determine the problem and the recovery action SQL 15206 Where int1 is the value of the return code from the library call This code is provided for problem analysis by support or development personnel Where function name is the name of the library function called Cause A subsystem error is not converted to a meaningful string The error number has meaning only to the libr...

Page 399: ...e ODBC administrator Then enter the command SQL 15215 Where function name is the name of the library function called Cause The service name is an asterisk Effect The command and subsequent subsystem call fails Recovery Enter the command with a specific service name SQL 15216 Where function name is the name of the library function called 15212 SUBSYSTEM Wrong length input parameter library call fun...

Page 400: ... provided SQL 15218 Where function name is the name of the library function called Cause Out of memory space Effect The command and subsequent subsystem call fails Recovery See the ODBC server documentation for handling server memory problems SQL 15219 Where function name is the name of the library function called Cause The service is not in the started state Effect The command and subsequent subs...

Page 401: ...e command and subsequent subsystem call fails Recovery Enter the command with the correct attribute value SQL 15222 Where function name is the name of the library function called Cause Unknown Effect The command and subsequent subsystem call fails Recovery See the lower level error messages issued with this message 15220 SUBSYSTEM Configuration server on SERVICE is not operational library call fun...

Page 402: ...Cause You inserted a semicolon or comma in the wrong place Effect The operation fails Recovery Enter the command again with the correct characters and syntax SQL 15227 Cause The command is missing the second of its two required parameters Effect The operation fails Recovery The command displays valid object types in a second message Enter the command again providing the second parameter 15224 SUBS...

Page 403: ...command with a semicolon or comma after the object name SQL 15230 Where string1 is a portion of the input showing the start of the problem Cause A string with single or double quotation mark SQL identifier or literal is missing the terminating mark Effect The operation fails Recovery Enter the command with the correct terminating single or double quotation mark 15228 Command contained a invalid ch...

Page 404: ...h characters inside the quoted string SQL 15233 Where string0 displays the start of the error Cause A keyword contains a quotation character Effect The operation fails Recovery Enter the command without quotation marks for the keyword SQL 15234 Where string1 displays the start of the error 15231 Command had a invalid char character where an attribute was expected command had string1 Note As of the...

Page 405: ...name which is the first token is missing possibly because the command starts with a comma Effect The operation fails Recovery Enter the complete command including the command name SQL 15238 Where string0 is the portion of the input following the problem Cause You entered an extra comma instead of a value Effect The operation fails Recovery Enter the value instead of a comma and resubmit 15235 Attr...

Page 406: ...te The error can be a misspelled attribute or a missing comma space character or attribute value in the preceding attribute Effect The operation fails Recovery Correct the attribute and retry the command SQL 15244 Where attribute name is the name of the duplicate attribute Cause A duplicate attribute is in the command Effect The operation fails Recovery Enter the command without the duplicate attr...

Page 407: ...0 is the name of the attribute Cause An attribute value is not associated with the attribute name Effect The operation fails Recovery Enter the command with correct the attribute value SQL 15248 Where invalid char is the invalid character Where string1 is the name and value of the attribute Cause The attribute value is invalid Effect The operation fails 15245 This command attribute never has a val...

Page 408: ... either entered unquoted white space in the object name or a comma was missing at the end of the name Effect The operation fails Effect Enter the command again with the correct object name syntax SQL 15256 Cause The user name field does not contain both the group and member name Effect The operation fails Effect Enter the command with a group and member name 15249 Command has a quoted string not f...

Page 409: ...nents for the object type SQL 15259 Where string1 is the object type Where int1 is the maximum number of characters allowed by the component Where string2 is the component with too many characters Cause Too many characters are in the component Effect The operation fails Recovery Enter the command with a reduced number of characters in the component specified in the error 15257 A component name may...

Page 410: ...the component with no backslash Cause The system name does not have a backslash preceding its name Effect The operation fails Recovery Enter the command with a backslash preceding the system name SQL 15262 Where string1 is the missing component name Cause The component is not specified in a previous command Effect The operation fails Recovery Enter the command with the proper component name Do not...

Page 411: ...t name for an SQL identifier SQL 15265 Where fname is the file name Where string1 is the name component as entered Cause The component name is not valid Effect The operation fails Recovery Enter the command with the correct component name for the command issued 15263 Single quote at start of component name not permitted command had string1 SUGG Identifiers use double quotes when needed to prevent ...

Page 412: ... an appropriate MACL INFO command with an asterisk wild card SQL 15267 Where string1 is the attribute name and value Cause The attribute value is not enclosed with single quotes Effect The operation fails Recovery Enter the command with the attribute value enclosed in single quotes SQL 15268 Where string1 is the attribute name and value Cause The attribute value is not specified as OFF Effect The ...

Page 413: ...m allowed value Effect The operation fails Recovery Enter the command with the attribute value equal to or larger than the minimum allowed value SQL 15272 Where maximum is the maximum value allowed for the attribute value Where string1 is the attribute name and value Cause The attribute value entered is greater than the maximum allowed value Effect The operation fails Recovery Enter the command wi...

Page 414: ...The operation fails Recovery Enter the command with the attribute value smaller or equal to the maximum allowed value SQL 15275 Where string1 displays the start of the error Cause A quoted string is concatenated with a different type of quoted string for example a single quoted string with a double quoted string Effect The operation fails Recovery Retry the command using the same type of quote cha...

Page 415: ... Recovery Retry the command either specifying a valid concatenation operator or removing the invalid character SQL 15278 Where string1 is a portion of the input showing the start of the problem Cause A component of the object name starts with a blank or tab character Names with a leading space are not valid Effect The operation fails Recovery Enter the command without a space at the start of the c...

Page 416: ... command with the correct syntax and resubmit SQL 15281 Where string0 is the text causing the error Cause A quoted string must always be followed by a dot comma or semicolon A dot must not be preceded by white space Effect The operation fails Recovery Enter the separator after the quote a comma might be missing and then enter the remaining attributes SQL 15284 Cause The command contains an invalid...

Page 417: ...invalid command and object pair Effect The operation fails A preceding message states the problem and this message lists valid ALTER command objects when mode macl is set Recovery Select a valid object type from the list as the object type for this command SQL 15287 Cause The input line contains either no second parameter or an invalid command and object pair Effect The operation fails A preceding...

Page 418: ...bject type for this command SQL 15290 Cause The input line contains either no second parameter or an invalid command and object pair Effect The operation fails A preceding message states the problem and this message lists valid STOP command objects when mode macl is set Recovery Select a valid object type from the list as the object type for this command SQL 15291 Cause The input line contains eit...

Page 419: ...5296 Cause The object name did not have the correct format Effect The operation fails A preceding message states the problem and this message shows the valid syntax for an object name Recovery Enter the command using the correct syntax SQL 15297 Cause The object name did not have the correct format Effect The operation fails A preceding message states the problem and this message shows the valid s...

Page 420: ...0 Where string0 is the DS name Cause The lower levels returned a status indicating no ability to provide state information for this DS There could be several reasons for this Look at additional lower level messages Effect The operation fails Recovery Issue the INFO DS command to determine if the DS exists SQL 15305 Where function name is the client library function name Cause The DS is in an activ...

Page 421: ...n name Cause You entered a data source name that does not exist on the system Effect The operation fails A preceding message states the problem and this message shows the valid syntax Recovery Retry the command using the correct syntax SQL 15310 Where function name is the client library function name Cause An SQL failure occurs in a lower client library Effect The operation fails Recovery Retry th...

Page 422: ...mmand SQL 15313 Where function name is the client library function name Cause This error is returned when a call to Guardian API PROCESS_STOP_ fails The system returns an error while trying to stop the server process The process might appear to be running but it might not be usable Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual SQL 15314 Where function na...

Page 423: ...rary function name Cause The port is used by another process or is not released from the operating system Effect The operation fails Recovery Wait for the port to clear then enter the command SQL 15317 Where function name is the client library function name Cause The data source is not currently available to make any changes Effect The operation fails Recovery Wait for the data source to fully tra...

Page 424: ...15320 Where function name is the client library function name Cause The trace status is already disabled Effect The operation fails Recovery Recovery not required SQL 15321 Where function name is the client library function name Cause The client library fails to enable or disable tracing Effect The operation fails Recovery Check your MXCS service process MXOAS It might not be responding 15318 SUBS...

Page 425: ... system state to determine why the new servers cannot start See information about this error in the EMS collector for MXCS service event messages which is specified on the mxoas start command with 0 as the default SQL 15324 Where function name is the client library function name Cause This error comes from the client library call CFGStartService Effect The operation fails Recovery Run the INFO com...

Page 426: ...blem SQL 15327 Where service name is the name of the service where the open is performed Cause Cannot open a connection to the service which might have recently terminated Effect The operation fails Recovery Verify that the service exists by using the INFO SERVICE command Then retry the failed command SQL 15328 Where service name is the name of the service where the operation is to be performed Ca...

Page 427: ...or MXCS service event messages which is specified on the mxoas start command with 0 as the default SQL 15330 Cause The lower level cannot return status for the next data source on the service The system could be busy Effect The operation fails Recovery Use the INFO SERVICE command to verify that the specific service is still operational or the INFO DS command to verify that the DS still exists See...

Page 428: ...e service A possible problem might exist in passing messages to the server Effect The operation fails Recovery See lower level error messages issued with this message Also see information about this error in the EMS collector for MXCS service event messages which is specified on the mxoas start command with 0 as the default SQL 15351 Cause Server name is other than an asterisk wild card to specify...

Page 429: ...eration fails Recovery Run the INFO DS command with the asterisk wild card specifying the data source Check the spelling and case of the data source name and if necessary use quotes to protect its case SQL 15354 Where service name is the name of the service Cause The lower level fails to return a list of data source names on the service The system might be busy Effect The operation fails Recovery ...

Page 430: ...utput The system might be busy Effect The operation fails Recovery Run the INFO SERVICE command to verify that the service exists and then retry the failed command See the lower level error messages issued with this message SQL 15357 Where server name is the name of the server Where count is the number of servers scanned Cause A specific server is not found The number of servers scanned is output ...

Page 431: ... the name of the service Where datasource name is the name of the data source Cause The lower level returns a bad status when the server list is requested The service is unavailable and does not return an error about finding the specified DS Effect The operation fails Recovery Check the status of the service See the lower level error messages issued with this message 15358 SERVER server name is no...

Page 432: ...ect The operation fails Recovery Issue the INFO SERVICE command to see if the service exists and is in a started state If service is stopped issue the START SERVICE command SQL 15366 Where string0 is the DS name Cause The lower levels returns a status indicating no ability to provide state information for this DS and also fails to get attribute information from the database Either the name contain...

Page 433: ...L 15368 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message SQL 15369 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message SQL 15370 Where string1 ...

Page 434: ...covery See the lower level error messages that follow this message SQL 15373 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message Then remove the data source and re create it SQL 15374 Cause Both the data source and service names are asterisks Effect The operation fails 153...

Page 435: ...ct The operation fails Recovery See the lower level error messages that follow this message SQL 15377 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message SQL 15378 Where string1 is the data source name Cause Removing the TDM_Default_DataSource data source is not allowed Ef...

Page 436: ...e and data source name Cause The data source is in the start state Effect The operation fails Recovery Stop the data source and rerun the command SQL 15382 Where string0 is the service name Cause The data source is not connected to the service Effect The operation fails Recovery Use the INFO SERVICE command to see the existing service If the specific service does not exist create a service or try ...

Page 437: ...e int2 is the number of reason text characters given in the command Cause Too many characters in the reason string Effect A warning message is displayed and the command is processed Recovery Enter the command using less than the maximum allowed characters in the reason string SQL 15386 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Rec...

Page 438: ...covery See the lower level error messages that follow this message SQL 15389 Where int1 is the idle server count specified in the command Where int2 is the maximum server count for the data source specified in the command Where string1 is the data source name Cause Idle server count is too large Effect The operation fails Recovery Either increase the maximum server count or decrease the idle serve...

Page 439: ...L 15391 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message SQL 15392 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message 15390 Initial server cou...

Page 440: ... 15395 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message SQL 15396 Where string1 is the data source name Cause A failure occurs in the client library Effect The operation fails Recovery See the lower level error messages that follow this message 15393 The ACTIVE attribut...

Page 441: ... name SQL 15400 Cause No services are available to activate tracing for this DS Effect The trace operation is not processed If this failure occurs during execution of an ADD DS command it is possible the DS is successfully created in either the database or on a service before the service is terminated Recovery If the error occurs during execution of ADD DS run INFO DS to verify that the DS is succ...

Page 442: ...QL 15402 Where attribute name is the name of the EVAR attribute Cause The required attribute name is missing from the EVAR object for the command Effect The operation fails Recovery Supply an EVAR attribute name for example LIMIT or VALUE with the command SQL 15403 Where attribute name is the name of the EVAR attribute Cause The attribute name for example PREFIX VALUE LIMIT ACTION is not valid wit...

Page 443: ...perly executed Recovery Use the INFO EVAR command to display a list of all existing EVARs of this type Use the asterisk wild card as the name SQL 15408 Cause Client library function fails Effect The operation fails Recovery See the lower level error messages below this message SQL 15409 Cause Incorrect command entry Effect The operation fails Recovery Either specify an asterisk wildcard for the EV...

Page 444: ... evar name is name of the EVAR specified in the command Where evar type is the EVAR type specified in the command Cause Incorrect command entry Effect The operation fails Recovery Check command input for EVAR type EVAR name or system SQL 15412 Where object type is the object type specified on the command line Where duplicate count is the number of duplicates found Cause More than one object type f...

Page 445: ...use No EVARs exist because the data source does not exist Effect The command fails Recovery Check the name of the data source specified in the command SQL 15416 Cause An invalid define EVAR name is entered in the command Effect The command fails Recovery Enter the command with a valid define EVAR name 15413 Duplicate object type name found add failed 15414 The first object type with this name was ...

Page 446: ...tails SQL 15429 Where string1 is either the group or member name Cause A wild card specifies either the group or member name Effect The operation fails Recovery Enter the command with a valid group or member name SQL 15430 Where user name is the user name Cause The user name was not found in the list of user names Effect The operation fails 15425 Failed in scan of USERs on the SYSTEM system name b...

Page 447: ...he lower client library function Effect The operation fails Recovery See the lower level error messages for details SQL 15434 Cause A failure occurred in the lower client library function Effect The operation fails Recovery See the lower level error messages for details 15431 The permissions for SUPER SUPER may not be changed or deleted 15432 Failed to set up an output area for outputing USERs New...

Page 448: ...s the name of the system Cause The user named for the operation does not exist on the system Effect The operation fails Recovery Add the user to the system and enter the command SQL 15437 Where group name is the group name Where system name is the name of the system Cause The group the operation was given against does not exist on the system Effect The operation fails Recovery Add the group to the...

Page 449: ...ata source name with the command Effect The operation fails Recovery Enter the correct data source name for the service or database SQL 15452 Where string1 is the command and object type Cause The command is not available Effect The operation fails Recovery No recovery required SQL 15453 Where string1 is the object type Cause The object type is invalid Effect The operation fails 15438 This command...

Page 450: ...ect type Cause The command is not valid with the specified object type Effect The operation fails Recovery See the lower level warning message that follows this message for a list of valid object types SQL 15457 Where string1 is the service name Cause The service name is incorrect Effect The operation fails Recovery Enter the command specifying a valid service name Use the INFO SERVICE command to ...

Page 451: ...rational SQL 15501 Cause You specified a command with invalid syntax Effect The command failed Recovery Check the syntax and reissue the command SQL 15502 Cause The MXCI command scanner found an invalid character in the command The character was not recognized in context Effect The operation fails Recovery Correct the syntax and reissue the command 15458 Could not open connection to system string1...

Page 452: ... an ampersand at the end of the previous line so that the new string in the next line is concatenated with the previous string or separate the fields with a comma and resubmit SQL 15505 Cause You specified an invalid value for an option in the SET SHOW or RESET command Effect The operation fails Recovery Use the correct value for the option SQL 15506 Cause The SET STYLE value that you specified fo...

Page 453: ...eration fails Recovery Specify the correct value and resubmit SQL 15509 Cause The SET STYLE value length that you specified for the NEWLINE_CHAR option was not 1 Effect The operation fails Recovery Specify the correct value and resubmit SQL 15510 Cause The SET LAYOUT value that you specified for the PAGE_LENGTH option was not in the value range Effect The operation fails Recovery Specify the corre...

Page 454: ... The SET LAYOUT value that you specified for the WINDOW option was not in the valid range Effect The operation fails Recovery Specify the correct value and resubmit SQL 15514 Cause The value that you specified in the LIST command was out of range The value must be in the range 1 through 32767 or ALL Effect The operation fails Recovery Specify the correct value and resubmit 15511 The value must be ...

Page 455: ...e command use the CANCEL command to terminate the SELECT statement and reissue the command SQL 15516 Cause You can enter these commands only when a SELECT is in progress BREAK DETAIL PAGE TITLE BREAK FOOTING LIST REPORT FOOTING BREAK TITLE NAME REPORT TITLE CANCEL PAGE FOOTING SUBTOTAL TOTAL Effect The operation fails Recovery Use these commands only with SELECT SQL 15517 Cause You specified an in...

Page 456: ...the report will fit within the given page length SQL 15520 Cause One of the columns in the TOTAL or SUBTOTAL command is not present in the current DETAIL command print list Effect The operation fails Recovery Revise the TOTAL SUBTOTAL or DETAIL command so that all of the TOTAL items also appear in the DETAIL print list SQL 15521 Cause You specified a SUBTOTAL command but there are no break columns...

Page 457: ...rough 255 Effect The DETAIL command fails Recovery Correct the value of SPACE and resubmit SQL 15524 Cause The value that you specified for the TAB clause was less than the left margin or greater than the right margin Effect The DETAIL command fails Recovery Correct the value of TAB and resubmit SQL 15525 Cause The value that you specified for the PAGE NEED or SKIP clause was not in the range 1 th...

Page 458: ...ror of the Report Writer module specified in the command Effect The operation fails Recovery None Contact your service provider SQL 15528 Cause You specified an option more than once in the command Effect The operation fails Recovery Remove the duplicate entry and resubmit SQL 15529 Cause You attempted to reset an alias name or detail alias name that was being used in another report command The na...

Page 459: ... greater than zero and less than or equal to the number of columns specified in the select list Effect The operation fails Recovery Use a valid column number and resubmit SQL 15532 Cause The name that you specified has been previously specified Each name must be unique Effect The operation fails Recovery Use only unique names and resubmit SQL 15533 Cause You specified a SUBTOTAL BREAK TITLE or BRE...

Page 460: ... name having a data type other than LARGEINT binary 64 with scale of zero Effect The operation fails Recovery Correct the problem and resubmit SQL 15537 Cause The two operands of the binary arithmetic operator did not belong to data type classes that can be operated upon Effect The operation fails Recovery Check that the operands belong to data type classes that can be operated upon in a binary ar...

Page 461: ...t The operation fails Recovery Specify a literal string and recompile SQL 15540 Cause You specified an invalid date and time to compute the timestamp Effect The operation fails Recovery Correct the syntax or values and resubmit SQL 15541 Cause You specified an AS DATE or AS TIME format on an incompatible item type AS DATE or AS TIME can be specified only on an item having a LARGEINT data type Effe...

Page 462: ... in a relational LIKE IN or BETWEEN predicate For example you cannot compare a numeric value and a character value Effect The operation fails Recovery Check the data types of the operands of the predicate and correct those that are incompatible SQL 15545 Cause You attempted a comparison between incompatible data types in a relational LIKE IN or BETWEEN predicate Effect The operation fails Recovery...

Page 463: ...mn name COL n or an alias name SQL 15548 Cause The right margin value that you specified did not exceed the left margin value so the line width was less than or equal to zero Effect The last margin value specified is ignored Recovery Specify values that result in a right margin greater than the left margin SQL 15549 Cause You specified a nonnumeric column in a TOTAL or SUBTOTAL command Only numeri...

Page 464: ...d a delimited identifier without a required nonblank character Effect The operation fails Recovery Correct the command and resubmit SQL 15553 Cause The current command requires an alias name but the name that you specified was not an alias Effect The command is ignored Recovery Reissue the command using a valid alias name To display current alias names use the SHOW REPORT NAME command 15550 Format...

Page 465: ...ur because of an arithmetic operation or an aggregation on large data values Effect The operation fails Recovery For an intermediate result overflow use simpler arithmetic expressions in your statements SQL 15575 Cause The column ID displayed was specified in a RESET REPORT command However that column ID is not currently set by the corresponding report command Effect The column ID is ignored by th...

Page 466: ...the CANCEL command to terminate the SELECT operation If you want to see more data use the LIST FIRST number command SQL 15803 Cause You tried to change the mode to report while already in report mode Effect The operation fails Recovery None This is an informational message only SQL 15804 Cause You tried to change the mode to SQL while already in SQL mode Effect The operation fails Recovery None Th...

Page 467: ...e syntax and resubmit SQL 15808 Cause The column number specified in the table was invalid Effect The operation fails Recovery Specify a valid column number in the table and resubmit SQL 15809 Cause A string overflow occurred during the evaluation of a character expression Effect The operation fails Recovery Increase the field size of the receiving field and resubmit 1558 The conversion failed 158...

Page 468: ...ble to connect to the Report Writer component Effect Cannot disconnect from the Report Writer module Recovery None SQL 15813 Cause The output device specified was invalid Effect Cannot switch to the output device specified Recovery Specify a valid output device and resubmit SQL 15815 Cause MXCI was unable to connect to the MXCS server and get a valid constructor Effect The operation fails 15810 Th...

Page 469: ...id character set name for SQLCI attribute TERMINAL_CHARSET in MXCI Effect None Recovery Specify a valid character set name for the TERMINAL_CHARSET attribute and resubmit SQL 15991 Cause A new report definition command s has been specified The report is being started from the beginning Effect A new report is being generated Recovery None 15816 An internal error occurred unable to get a valid MXCS ...

Page 470: ...e could not be found or could not be displayed Effect No usage information is displayed Recovery None SQL 15999 Cause MXCI has received an internal error Effect The operation fails Recovery Report the entire message to your service provider 15992 Usage information not found or could not be displayed 15999 An MXCI internal error occurred ...

Page 471: ...age Recovery Reinstall NonStop SQL MX See the SQL MX Installation and Management Guide If that does not resolve the problem report the entire message to your service provider SQL 16001 Cause Internal error Effect NonStop SQL MX is unable to return or display a message with the specified number Recovery None Report the entire message to your service provider 16000 Error message file not found 16001...

Page 472: ...Messages Generated by the Message System 16000 through 16999 HP NonStop SQL MX Messages Manual 640324 001 16 2 ...

Page 473: ...ervice provider SQL 19002 Cause Internal error Effect NonStop SQL MX is unable to process the request Recovery None Report the entire message to your service provider SQL 19003 Cause Internal error Effect NonStop SQL MX is unable to process the request Recovery None Report the entire message to your service provider 19000 An internal error occurred in internal stored procedure processing 19001 An ...

Page 474: ...s a data type which is incompatible with the formal parameter Effect The request fails Recovery None SQL 19017 where value is a user specified input value to a versioning built in function input type is a valid input type to one of the versioning built in functions VERSION_INFO RELATEDNESS Cause An attempt is made to access a built in function with an input value that is invalid for the specified ...

Page 475: ...overy If the message is returned from an explicit invocation of the stored procedure re enter the request with the correct number of input parameters Otherwise report the entire message to your service provider SQL 19021 Cause Internal error Effect NonStop SQL MX is unable to process the request Recovery None Report the entire message to your service provider SQL 19022 Where target_feature_version...

Page 476: ...is compiled with old compiler and does not have the source name section and object name section Effect The operation fails Recovery Compile the module with a newer compiler SQL 19031 Cause Searching in Guardian path i e starting with G on osh is not supported and user has specified this location with module_dir option Effect The operation fails Recovery Don t use Guardian location in module_dir op...

Page 477: ...to open the requested file and received error error number Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20002 Where error number is the Guardian file system error Cause SQL was not able to write to the requested file and received error error number Effect The operation fails Recovery See the Guardian Procedure Err...

Page 478: ...ed file and received error error number Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20005 Where error number is the Guardian file system error Cause SQL was not able to retrieve information for the requested file and received error error number Effect The operation fails Recovery See the Guardian Procedure Errors...

Page 479: ...Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20008 Cause The utility subsystem that performs fast data transfer was sent an invalid buffer size Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20009 Cause The utility subsystem responsible for performing fast data transfer was sent an invalid buffer size Effect The ...

Page 480: ... the operation that can be FILE OPEN FILE READ FILE WRITE FILE CLOSE SET LARGE TRANSFER FILE ALLOCATE DEALLOCATE FILE SET EOF TO 0 Where file is the name of the file being processed Cause The utility subsystem that performs a file request received a request out of sequence Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 20012 Cause The utility subsyste...

Page 481: ...ails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20015 Cause The utility subsystem that performs fast data transfer performed operations out of sequence Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20016 Where error number is the Guardian file system error Cause SQL was not able to ob...

Page 482: ... specified in the COLS metadata table Cause NonStop SQL MX found a discrepancy while reading metadata information The information returned is inconsistent This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 20019 Where state is the DEFAULT_CLASS specified in the COLS metadata table Where name is the COLUMN_NAME specified in the COLS metadata table C...

Page 483: ...se The utility subsystem that reads and maintains metadata encountered an unexpected data type for a column Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20022 Where 0 int0 is the value of the field length specified in the format file Where 1 string0 is the corresponding column name Where 2 int1 is the required value for the field length Cause...

Page 484: ...ls Recovery Check for misspellings and resubmit SQL 20024 Cause You tried to create a table that already exists Effect The operation fails Recovery Change the name of the table and resubmit SQL 20025 Where object name is the name of the table view synonym trigger and so on Where state1 state2 is not opened not closed not modified not created Cause Illegal sequence of operations performed by a util...

Page 485: ...ed an invalid partition physical size which must be expressed in bytes megabytes kilobytes or gigabytes Effect The operation fails Recovery Correct the syntax and resubmit SQL 20029 Cause You specified an invalid key range possibly because you specified the begin key as noninclusive or specified the end key as inclusive Effect The operation fails Recovery Correct the first key value and resubmit 2...

Page 486: ...ne This is an internal error Contact your service provider SQL 20033 Cause You attempted to drop a nonemtpy range partition Effect The operation fails Recovery Make sure the range partition is empty before dropping it SQL 20034 Cause The catalog is not visible on the local node either because it does not exist or because it exists elsewhere in the network and has not been registered on the local n...

Page 487: ...d table Effect The operation fails Recovery Check the spelling of the specified table name and resubmit SQL 20037 Cause You specified a request that was not ADD DROP MOVE or REUSE Effect The operation fails Recovery Check the spelling in the request and resubmit SQL 20038 Cause You specified a key value with incorrect syntax Effect The operation fails Recovery Check the syntax of the specified par...

Page 488: ...rnal error Contact your service provider SQL 20041 Cause The utility subsystem that retrieves data from the file system failed with an unexpected error Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20042 Where 0 string0 is the corresponding column name Cause You attempted to import UCS2 character data in binary mod...

Page 489: ...unexpected value for the sort order ASC DESC on the primary key Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20046 Cause The utility encountered an unexpected value for a size unit designation Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20047 Cause The utility subsystem that reads and m...

Page 490: ...Where error is the returned file system error Cause An unexpected error occurred while decomposing a Guardian file name or template Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20050 Cause You attempted to perform a modify request which failed Effect The operation fails Recovery Use the messages that accompany thi...

Page 491: ...L 20053 Cause The utility subsystem that performs transaction management operations failed while trying to begin a new transaction Effect The operation fails Recovery Use the messages that accompany this one to diagnose and correct the problem SQL 20054 Cause The utility subsystem that performs CLI requests to SQL failed trying to clean up memory upon completion of a request Effect The operation f...

Page 492: ...s CLI requests to SQL failed trying to extract the number of rows affected from the previously executed request Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20058 Cause The input file specified as the command line option for IMPORT does not exist or could not be opened Effect The operation fails Recovery Verify that the input data file exists...

Page 493: ... Recovery Specify a first row value of either 0 zero or a positive value SQL 20061 Cause You specified the number of rows or records to be imported as a negative value Effect The operation fails Recovery Specify a positive num rows value SQL 20062 Cause The transaction size value that you specified is either negative or zero Effect The operation fails Recovery Specify a positive transaction size v...

Page 494: ...annot be opened because it was not created or it has been corrupted Effect The operation fails Recovery Verify that the error file has been created If it exists check to see if the file is corrupted SQL 20067 Where string0 is the value where the syntax error was detected Cause You specified the wrong syntax Effect The operation fails Recovery Correct the syntax and resubmit 20064 The file type spe...

Page 495: ...mn that IMPORT already processed in the current row Cause The specific field in the current row in the input file could not be processed Effect The operation fails Recovery Check the specified column in the current row for valid data SQL 20071 Cause The row delimiter string that you specified either at the command line or in the DELIMITED FORMAT section of the format file contains a field qualifie...

Page 496: ... other delimiter SQL 20073 Where objname is the ANSI name of the target table Cause The object name that you specified was invalid or does not exist Effect The operation fails Recovery Specify a valid object name Verify that the catalog name schema name and table name sections of the ANSI name are specified SQL 20074 Where file name is the input data file name Cause SQL was unable to open the data...

Page 497: ... Where rownum is the row number that was processing when the error occurred Cause An internal error occurred in a stored procedure Effect The import was partially completed It terminated while processing the row specified Recovery None Contact your service provider SQL 20082 Cause The fixed width data file is incomplete and does not provide enough data at the end of the file for importing Effect T...

Page 498: ...TH FORMAT part of the format file and resubmit SQL 20085 Cause The column size that you specified for one of the columns in the FIXED WIDTH FORMAT part of the format file was invalid Effect The operation fails Recovery Correct the column size specified for one of the columns in the FIXED WIDTH FORMAT part of the format file and resubmit SQL 20086 Where columnname is the column name specified in th...

Page 499: ...use The format file name was missing from an internal message Effect The operation fails Recovery None Contact your service provider SQL 20089 Where columnname is the column name specified in the FIXED WIDTH FORMAT part of the format file Cause The column name that you specified was missing from an internal message Effect The operation fails Recovery None Contact your service provider 20087 One or...

Page 500: ...ecovery None Contact your service provider SQL 20092 Where precision is the column precision specified in the FIXED WIDTH FORMAT part of the format file Cause The precision value that you specified was missing from an internal message Effect The operation fails Recovery None Contact your service provider SQL 20093 Where scale is the column scale for the specified table Cause The scale value that y...

Page 501: ...Utility Messages 20000 through 23099 HP NonStop SQL MX Messages Manual 640324 001 18 25 Effect The operation fails Recovery None Contact your service provider ...

Page 502: ...ou specified was missing from an internal message Effect The operation fails Recovery None Contact your service provider SQL 20097 Where dateorder is the order of date specified in the DATE FORMAT section of the format file Cause The date order that you specified was invalid Effect The operation fails Recovery Valid date order values are MDY MYD DMY DYM YMD and YDM Correct the date order in the DA...

Page 503: ...column was defined as NOT NULL NO DEFAULT and therefore cannot be skipped Effect The operation fails Recovery Set the skip flag to Y or N in the COLUMN FORMAT section of the format file SQL 20100 Where columnname is the column name in the COLUMN FORMAT section of the format file Cause The skip flag was missing for this column from the COLUMN FORMAT section of the format file Effect The operation f...

Page 504: ...ause You specified an object name that contains an illegal character Effect The operation fails Recovery Correct the syntax and resubmit SQL 20104 Cause You specified an object name that exceeds the maximum length Effect The operation fails Recovery Correct the syntax and resubmit SQL 20105 Cause SQL detected an internal error while performing a utility operation Effect The operation fails 20101 d...

Page 505: ... column number in the data file Cause There is a missing or mismatched field qualifier for the column in the data file Effect The operation fails Recovery Verify the data and add the missing qualifier SQL 20109 Where details describe the returned error information from the file system Cause An unexpected error was returned from the CLI while accessing file system information Effect The operation f...

Page 506: ...bmit SQL 20112 Where schema name is the name of the schema associated with the source table Cause You specified a source schema name that does not exist or could not be accessed Effect The operation fails Recovery Correct the schema name and resubmit SQL 20113 Where table name is the name of the table to duplicate Cause You specified a source table name that does not exist or could not be accessed...

Page 507: ...ma name that does not exist or could not be accessed Effect The operation fails Recovery Correct the schema name and resubmit SQL 20116 Cause The target table name you specified was the same as the source table name Effect The operation fails Recovery Correct the target table name and resubmit SQL 20117 Where catalog name is the name of the catalog associated with the table to be purged Cause You ...

Page 508: ...e accessed Effect The operation fails Recovery Verify the table name and resubmit SQL 20120 Cause You specified a partition that does not exist or could not be accessed Effect The operation fails Recovery Verify the partition name and resubmit SQL 20121 Cause The table being purged has multiple partitions and is not key sequenced This type of table is not supported Effect The operation fails Recov...

Page 509: ...d Effect The operation fails Recovery Commit or roll back the transaction and resubmit SQL 20125 Where table name is the name of the table specified in the PURGEDATA operation Cause The table name that you specified was a metadata table You cannot perform the PURGEDATA operation on metadata tables Effect The operation fails Recovery Specify a different table and resubmit SQL 20127 Where object typ...

Page 510: ...while performing the DUP operation Effect The operation fails Recovery None Contact your service provider SQL 20130 Cause The specified attribute was missing from an internal message Effect The operation fails Recovery None Contact your service provider SQL 20131 Cause The row delimiter was missing from the delimited input data file Effect The operation fails Recovery Add a row delimiter and run t...

Page 511: ...ed file Cause SQL was unable to open the file name that you specified with the E command line option Effect The IMPORT operation fails Recovery Specify a valid error file name and resubmit SQL 20136 Cause The field qualifier that you specified either at the command line or in the DELIMITED FORMAT section of the format file is more than one character long Effect The operation fails Recovery Specify...

Page 512: ... source table Effect The DUP operation fails Recovery None Contact your service provider SQL 20138 Cause You specified an invalid column name in the COLUMN FORMAT section of the format file Effect The operation fails Recovery Specify a valid column name SQL 20139 Cause The utility subsystem that performs CLI operations failed while trying to perform an ABORTTRANSACTION Effect The operation fails R...

Page 513: ...s Recovery None This is an internal error Contact your service provider SQL 20142 Where invalid datatype is the data type specified by the user Cause The utility subsystem that performs CLI operations failed while trying to get information from the returned statement Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20143 Cause An equal sign is mi...

Page 514: ...ffect The operation fails Recovery Specify a valid partition map and resubmit SQL 20147 Cause The range that you specified is empty Effect The operation fails Recovery Verify the key range and resubmit SQL 20148 Cause The list of partitions specified in the key range has the same begin and end key There are no partitions to purge Effect The operation fails Recovery Specify a valid key range and re...

Page 515: ...urrent release of NonStop SQL MX Effect The operation fails Recovery Change the format file to specify FileIsBinary N and resubmit SQL 20152 Cause You specified VARCHAR for a format file that is binary FIXED WIDTH Effect SQL is not able to perform the IMPORT operation Recovery Verify your format file and resubmit 20149 External indexes exist for this object type Since the source and target have th...

Page 516: ...L encountered an internal error in the stored procedure interface Effect The operation fails Recovery None Contact your service provider SQL 20157 Cause You attempted to assign a default value to a field in column number with NO DEFAULT Effect The operation fails Recovery Correct the syntax and resubmit 20153 The VARCHAR varying length can support VARCHAR data type only 20154 Column Null or Defaul...

Page 517: ...lity subsystem that reads and maintains metadata could not successfully read information for catalog schema table Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20163 Cause SQL was unable to perform the requested operation Effect The operation fails Recovery None This is an internal error Contact your service provider 20160 Error occurred while...

Page 518: ...r of key columns in the table and resubmit SQL 20166 Cause You used an SQL reserved word as an object name Effect The operation fails Recovery Correct the syntax and resubmit SQL 20167 Cause The object name that you specified is not valid It must contain at least one character Effect The operation fails Recovery Correct the syntax and resubmit 20164 The search condition for the specified check con...

Page 519: ...the LAST PARTITION syntax and resubmit SQL 20170 Cause The partition that you specified in the LOCATION clause does not exist Effect The MODIFY utility did not process the request Recovery Check the location of the partition and resubmit SQL 20171 Cause The section name is missing from the format file Effect The operation fails Recovery Correct the format file and resubmit 20168 The partition key ...

Page 520: ...0324 001 18 44 SQL 20172 Cause The record length value is missing in the FIXED WIDTH FORMAT section of the format file Effect The operation fails Recovery Correct the format file and resubmit 20172 RecordLength is missing in the FIXED WIDTH FORMAT section of the format file ...

Page 521: ...e name of the table view synonym trigger and so on Where operation type of operation that is currently holding the DDL lock One of the following DP DUP PI Populate index PD Purgedata RC Recovery RF Refresh VA Validate TR Transform Cause You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object its parent or its de...

Page 522: ...Cause The MODIFY utility encountered an unexpected error condition Effect Depending on the severity of the problem the MODIFY utility might not process the request or it might partially process the request Recovery Execute the RECOVER command to undo the changes made by the aborted request If the recovery does not complete successfully contact your service provider SQL 20180 Cause The specified se...

Page 523: ...responding partitioning key column Cause The data type of the specified partitioning key value column value was incompatible with the character type of the corresponding partitioning key column Effect The operation fails Recovery Correct the partitioning key value and resubmit SQL 20184 Where file name is the name of the format file Cause The format file name that you specified was not a valid for...

Page 524: ...Recovery Correct the data in the input file and resubmit SQL 20188 Cause The command line options L and XL must specify a value greater than or equal to zero and less than or equal to 2147483646 Effect The operation fails Recovery Specify a value greater than or equal to zero and resubmit SQL 20189 Cause You tried to move data in the first partition to a nonexisting previous partition 20185 More t...

Page 525: ...rform the MODIFY and then alter the table back to nonaudited SQL 20192 Where table name is the name of the specified table Cause You tried to perform a modify request on a metadata table which is not supported Effect The operation fails Recovery None SQL 20193 Cause You cannot perform a POPULATE INDEX operation under a user defined transaction Effect The operation fails Recovery Commit or roll bac...

Page 526: ... command Where table name is the table or view being populated Cause The index name specified by the caller does not belong to the table or view being populated Effect The operation fails Recovery Specify a valid name and resubmit SQL 20196 Where index name is the index to be populated as specified by the POPULATE INDEX command Cause The index name specified by the caller should not contain data D...

Page 527: ...d Whereintisthebytelocationinthestringwheretheerroroccurred Cause You specified the wrong syntax Effect The operation fails Recovery Correct the syntax and resubmit SQL 20199 Cause An unknown error occurred while populating an index Effect The operation fails Recovery None Contact your service provider SQL 20200 Cause You specified a catalog name that is not defined or not visible on the system Ef...

Page 528: ...dex name is the name of the specified index in ANSI SQL name format Cause The MODIFY utility could not find the specified index Effect The operation fails Recovery Check the spelling of the specified index name and resubmit SQL 20204 Where object name is the index to be recovered as specified by the POPULATE INDEX command Cause The index name could not be recovered with the given RECOVER command E...

Page 529: ... with the data type of the corresponding partition key column Effect The operation fails Recovery None SQL 20208 Cause You cannot perform a RECOVER operation under a user defined transaction Effect The operation fails Recovery Commit or roll back the user defined transaction and resubmit SQL 20209 Where object name is the name of the object to recover Cause Recovery is not needed for object name E...

Page 530: ...ecover Cause A DDL_LOCKS lock name was specified but not found possibly because the wrong name was specified Effect The operation fails Recovery Specify the correct name and resubmit SQL 20212 Where 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 Recovery Determine the operation that is currently...

Page 531: ... Recovery Check for other messages to determine the cause of failure and resubmit SQL 20216 Where object name is the name of the object Cause A request was made to recover an operation which is not specified correctly in the metadata Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20217 Cause The catalog name specified by the caller is not defin...

Page 532: ...e name and resubmit SQL 20220 Where index name is the name of the index to recover Cause The index name specified by the caller is not defined or not visible on the current system Effect The operation fails Recovery Specify a valid name and resubmit SQL 20221 Where string is the value where the syntax error was detected Where int is the byte location in the string where the error occurred Cause Yo...

Page 533: ...tempted to purge data from a table that is being referenced by a referential integrity constraint which is not supported Effect The operation fails Recovery Remove the referential integrity constraint and resubmit SQL 20225 Cause You attempted to purge individual partitions of a hash partitioned table which is not supported Effect The operation fails 20222 Error occurred for partition file file na...

Page 534: ...very None This is an internal error Contact your service provider SQL 20228 Cause The DDL_LOCK specified was not defined in metadata Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20229 Where index name is the name of the index specified in the update request Cause An unexpected error is returned during the final phase of duplicating indexes to...

Page 535: ...ration fails Recovery Check the syntax and resubmit SQL 20232 Cause You tried to perform a MODIFY utility on a nonaudited table containing data Effect The operation fails Recovery None SQL 20233 Where volume name is the name of the volume Cause The MODIFY utility could not find in volume volume name partitions that belong to the specified object Effect The operation fails 20230 You cannot drop all...

Page 536: ...the returned status described in the Guardian Procedure Errors and Messages Manual to determine the problem and resubmit SQL 20236 Where status is the status returned from USER_GETINFO_ Where username is the user name being converted Cause An unexpected error was returned while converting the current user name to user ID Effect The operation fails Recovery Diagnose the returned status described in...

Page 537: ...ansaction using the COMMIT WORK or ROLLBACK WORK command and then resubmit SQL 20239 Where default attribute is the specified attribute value Cause You specified an invalid attribute value for attribute PM_ONLINE_TRANSACTION_GRANULARITY for online operation and attribute PM_OFFLINE_TRANSACTION_GRANULARITY for offline operation Effect The operation fails Recovery Commit or roll back the transaction...

Page 538: ... Where file is the name of the Unicode data file Cause Two byte order mark bytes cannot be found at the beginning of the Unicode data file Effect The Unicode data import fails Recovery Re create the Unicode data file and add the two byte order marks SQL 20244 Where file is the name of the Unicode data file Cause The byte order mark bytes specified are invalid Effect The Unicode data import fails 2...

Page 539: ...r set ISO88591 SQL 20250 Cause You tried to reuse the first partition but the new key range that you specified in the WITH clause overlaps the existing key range of the first partition Effect The operation fails Recovery None SQL 20251 Where operation is the type of MODIFY operation including ADD MOVE or DROP Cause This is an internal error Effect The operation fails Recovery None Contact your ser...

Page 540: ... not specify the PURGEDATA option in the REUSE request Effect The operation fails Recovery None SQL 20255 Cause You attempted a partition management request other than ADD DROP or MOVE on an index Note that the REUSE request works only with range partitioned requests Effect The operation fails Recovery None 20252 Only a single ADD MOVE DROP or REUSE request is allowed 20253 The new key range must ...

Page 541: ...ion fails Recovery None SQL 20259 Cause An unexpected error was detected Effect The operation fails Recovery None Contact your service provider SQL 20261 Where object name is the name of the object Cause In the WHERE clause you did not specify the partition in the request to move the partition to a new location When the object has more than one partition you must specify the partition Effect The o...

Page 542: ...mber is the error returned from the SPI interface Where command is the SPI command being processed Cause An unexpected error was returned from SPI when MODIFY attempted to start an ORSERV process to perform a FUP RELOAD operation Effect The operation fails Recovery None This is an internal error Contact your service provider SQL 20266 Where code1 is the code returned from SPI 20263 An invalid DUP ...

Page 543: ... the target table Cause The audit attribute of the table is turned off during the IMPORT operation if the table is empty and contains no indexes This enables IMPORT to make use of Side Tree inserts for better performance The audit attribute could not be turned back on after the IMPORT operation was complete because of an internal failure Effect The IMPORT operation is complete The table might rema...

Page 544: ...th the specified object have had their redefinition timestamps updated Effect The operation completes with warnings Recovery After completing this request the same request must be issued on all systems that contain a partition of the object SQL 20271 Where error is the error returned Where subsystem is the name of the subsystem returning the error Cause An unexpected error was returned while attem...

Page 545: ...vice provider SQL 20275 Where error is the error returned by the file system Where file is the Guardian file Cause An unexpected error occurred while performing a FUP RELOAD Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose the error and then resubmit SQL 20276 Cause SQL attempted to start a FUP RELOAD operation but an operation was already in pr...

Page 546: ...n object that has a decoupled partitioning key Only offline partition management operations are allowed on such an object Effect The MODIFY utility did not process the request Recovery Retry the operation without the WITH SHARED ACCESS clause SQL 20293 Cause The partition that you specified in the partition management request contains data and the specified base table is referenced by another base...

Page 547: ...or both flags might still be set and no subsequent DDL commands or utilities can operate on the partitions Recovery Run FUP RELOAD manually to reclaim free space on the specified partitions if the D or F flag is present for the partitions Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set SQL 20296 Cause The MODIFY utility encountered failures after it started all ORSERVs the F...

Page 548: ...n FUP RELOAD manually to reclaim any free space on any partitions of the object if the D INCOMPLETE SQLDDL OPERATION or F UNRECLAIMED FREE SPACE flag is present for the partition Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set SQL 20298 Where progname is the name of the program file Cause You specified a program file that is not licensed Effect The operation fails Recovery L...

Page 549: ...o recover a failed PURGEDATA request by specifying RESUME However PURGEDATA has progressed too far and only CANCEL can be specified Effect SQL is unable to recover the PURGEDATA command Recovery Use CANCEL to retry the operation SQL 20306 Cause Internal error Effect The backup or restore could not be performed Recovery None Contact your service provider 20302 The IO buffer is not large enough to h...

Page 550: ...ernal error Effect The backup or restore operation fails Recovery None Contact your service provider SQL 20310 Cause This is an internal error Effect The backup or restore operation fails Recovery None Contact your service provider SQL 20311 Cause You are trying to create a column of a data type that is not supported Effect The backup or restore operation fails Recovery None 20307 The catalog obje...

Page 551: ...e location of the index SQL 20318 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 20319 Cause You are trying to restore a table object that already exists Effect The operation fails Recovery Check the location of the table and resubmit 20312 The index object already exists 20318 The partition object was not found 20319 The table object alr...

Page 552: ...rform a PARTONLY restore to a table that does not exist Effect The operation fails Recovery Check the location of the table SQL 20325 Cause This is an internal error Effect The operation fails Recovery None Contact your service provider SQL 20330 Cause An internal function has specified the wrong parameters Effect The operation fails Recovery None This is an internal error Contact your service pro...

Page 553: ...tact your service provider SQL 20333 Cause The DP2 file name of an audit object passed by the transaction management process TMP is invalid Effect The operation fails Recovery None Contact your service provider SQL 20334 Cause The restore options you specified do not match the backup options Effect The operation fails Recovery Correct the restore options and resubmit SQL 20335 Cause The restore se...

Page 554: ...e master audit trail data was missing Effect The operation fails Recovery None This an internal error Contact your service provider SQL 20339 Where index list is a comma separated list of indexes Where table is the name of the table Cause One of more indexes did not populate correctly probably because of uniqueness violations when loading unique indexes Effect The operation fails Recovery For uniq...

Page 555: ... action are reported by error 20339 SQL 20350 Where string is the value where the syntax error was detected Where int is the byte location in the string where the error occurred Cause You specified the wrong syntax Effect The operation fails Recovery Enter MXTOOL HELP to get correct syntax and resubmit SQL 20351 Cause An unexpected error occurred while performing an MXTOOL operation Effect The ope...

Page 556: ...n failed because you do not have super ID or schema owner privilege Effect The operation fails Recovery Log on as the super ID and resubmit SQL 20355 Where name is the Guardian file specified in the GOAWAY request Cause The Guardian file that you specified does not exist possibly because of a spelling error Effect The operation fails Recovery Specify the Guardian file correctly and resubmit SQL 20...

Page 557: ...ardian file Effect The operation fails Recovery None You can use GOAWAY only with SQL MX objects SQL 20358 Where catalog is the name of the catalog specified in the request Cause You specified a catalog name that is not defined or is not visible on the system Effect The operation fails Recovery Enter the correct catalog name and resubmit SQL 20359 Where schema is the name of the schema specified i...

Page 558: ...e template An error was returned during this generation process Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem SQL 20363 Where error is the error returned from the file system Cause MXTOOL generates a list of files to check as specified by a Guardian file template An error was returned during the processing of this list...

Page 559: ...it SQL 20371 Where object name is the name specified in the MXTOOL command Cause The object specified by the caller is not an SQL MX object Effect The operation fails Recovery Specify the correct object name and resubmit SQL 20372 Cause The resource fork is either broken or does not exist Effect None Recovery None This is an informational message 20364 An internal error occurred while getting the ...

Page 560: ...ls Recovery Please run mytool help goaway to get the list of correct options and retry request SQL 20376 Cause You specified a non ISO88591 character set name Effect The operation fails Recovery Specify an ISO88591 character set name SQL 20377 Cause You specified an invalid character set Effect The operation fails Recovery Specify an ISO88591 character set 20373 The specified system does not exist...

Page 561: ...Do not use the DATA RESOURCE FORK option and resubmit SQL 20452 Where system is the name of the system where the Guardian object resides Cause You tried to remove a Guardian object on a remote system Effect The operation fails Recovery Run the GOAWAY operation on a local machine SQL 20453 Where name is the name of the Guardian file requested to be removed Cause The GOAWAY operation failed because ...

Page 562: ...ady to remove the requested files Effect GOAWAY is waiting for a response before continuing Recovery None SQL 20457 Cause The GOAWAY operation was terminated Effect None Recovery None This is an informational message SQL 20458 Where file is the name of the Guardian file Where error is the file system error returned while trying to remove a Guardian file Cause The GOAWAY operation failed because of...

Page 563: ... resource fork Where data fork name is the name of the data fork Cause The GOAWAY operation failed because you specified resource fork name with the both option Effect The operation fails Recovery Retry with data fork name label name SQL 20461 Where resource fork name is the name of the resource fork Cause The GOAWAY operation failed because you specified resource fork name with the df option Effe...

Page 564: ...ock must be removed Contact your service provider to remove the lock SQL 20521 Where object is the name of the object Cause Object object has a DDL lock on it by another concurrent refresh utility execution Effect This refresh operation fails Recovery After the concurrent operation that holds the DDL lock finishes run refresh again If no concurrent operations are running the DDL lock must be remov...

Page 565: ... which is a comparison of values attempted for SQL item data types that are not identical Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 20562 Cause Refresh reached a transaction management facility TMF limit on the number of transactions that the facility can start Effect The refresh operation fails Recovery Do not attempt recovery Contact your servi...

Page 566: ...error number given is the return code MXAUDSRV received from a SEGMENT_ALLOCATE_ request Effect The MODIFY operation fails Recovery See the Guardian Procedure Errors and Messages Manual topic SEGMENT_ALLOCATE_ for possible recovery actions for error number SQL 20702 Where Guardian file name is the name of the partition being processed 20588 Invalid Character error converting string from character ...

Page 567: ...ry None Contact your service provider SQL 20704 Where process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process encountered a hardware trap Such traps might be caused by programming errors in the MXAUDSRV process itself Effect The MODIFY operation fails Recovery None Contact your service provider SQL 20705 Cause During an online partition ...

Page 568: ...IFY operation fails Recovery None Contact your service provider SQL 20708 Where process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process encountered an error while processing an HP NonStop Transaction Management Facility TMF audit record Effect The MODIFY operation fails Recovery None Contact your service provider SQL 20709 Where process ...

Page 569: ...SRV process name Cause During an online partition management operation the MXAUDSRV process encountered an error while attempting to report an EMS event to 0 Effect The MODIFY operation fails Recovery Verify that EMS is up and running normally If not correct this problem and retry the operation Otherwise contact your service provider SQL 20712 Cause During an online partition management operation ...

Page 570: ...at the TMF subsystem is down or has transactions disabled Effect The MODIFY utility did not process the request Recovery Correct the TMF problem and resubmit SQL 20718 Where volume name is the volume where the audit trails resides Where process name is the name of the MXAUDSRV process Cause During an online partition management operation the MXAUDSRV process encountered an audit trail versioning e...

Page 571: ...stem name is the name of the system where the version incompatibility occurs Cause The wrong product version of MXAUDSRV is installed on the named system Effect The MODIFY operation fails Recovery Install the current product version of MXAUDSRV SQL 20721 Where process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process encountered an interna...

Page 572: ...n online partition management operation the MXAUDSRV process encountered an internal error Effect The MODIFY operation fails Recovery None Contact your service provider SQL 20726 Where program file name is the MXAUDSRV process name Cause The MXAUDSRV program file is not licensed Effect The MODIFY operation fails 20723 An audit fixup process found a label change audit record during fixup work These...

Page 573: ...eration the MXAUDSRV process encountered an error when attempting an SQL MX statement Effect The MODIFY utility did not process the request Recovery Contact your service provider SQL 20729 Where error code is the returned file system number Where process name is the MXAUDSRV process name Cause During an online partition management operation the MXAUDSRV process encountered an error when attempting...

Page 574: ...rocessing at the time the MODIFY command is first parsed and again when MODIFY is ready to begin commit phase Effect The MODIFY operation fails Recovery If the timestamp check failed at the beginning of the commit phase perform a RECOVER command to undo partial processing Then retry the MODIFY operation with a timestamp sufficiently in the future SQL 20732 Cause The MODIFY command includes a COMMI...

Page 575: ... encountered an error number from the CONVERTTIMESTAMP Guardian procedure when converting the current time to local civil time Effect The MODIFY operation fails Recovery See the Guardian Procedure Calls Reference Manual topic CONVERTTIMESTAMP Procedure for the meaning of error number and possible recovery actions SQL 20735 Cause An unexpected error occurred when trying to find audit records to app...

Page 576: ...ias for an SQL MP object The utility operation on these objects is not allowed Effect The operation fails Recovery Specify the name of a table and resubmit SQL 20753 Cause An unexpected error caused VERIFY to terminate Effect The operation fails Recovery None Contact your service provider SQL 20754 Where error is the error returned by the file system 20751 A user defined transaction has been start...

Page 577: ...command by specifying a valid object name SQL 20756 Where file is the Guardian file name specified Where space is the ANSI name space for the file Cause You specified a Guardian file that was not a base table Effect The operation fails Recovery None VERIFY supports only Guardian files that belong to the SQL MX table name space SQL 20757 Where file is the Guardian file name specified Cause VERIFY f...

Page 578: ...ration did not complete and perform a RECOVER operation and then resubmit SQL 20759 Where name is the index that is not populated Cause The POPULATE INDEX command has not been run Effect None This is an informational message Recovery At some point the POPULATE INDEX command should be performed to make the index available for queries SQL 20760 Where time1 is the Julian timestamp found on the label ...

Page 579: ... was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider SQL 20763 Where size1 is the secondary extent size defined on the label Where size2 is the secondary extent size defined in the metadata Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informationa...

Page 580: ... Effect None This is an informational message Recovery Please use VERIFY to change the audit attribute to correct the inconsistency SQL 20766 Where size1 is the record size stored in the file label Where size2 is the record size found in the metadata Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message...

Page 581: ...e metadata is wrong Effect The operation fails Recovery If the Guardian file is no longer needed use GOAWAY to remove it If the Guardian file should be part of an ANSI name the metadata tables might need to be recovered Contact your service provider about metadata recovery SQL 20769 Where name1 is the ANSI name found in the resource fork Where name2 is the ANSI name found in the metadata Where fil...

Page 582: ...le Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider SQL 20774 Where name is the constraint name described in the metadata Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service pr...

Page 583: ...e is the name of the object Cause An inconsistency was found during the VERIFY operation Effect This is an informational message VERIFY found a problem that needs attention Recovery Contact your service provider SQL 20777 Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your servic...

Page 584: ...FY operation Effect None This is an informational message Recovery Contact your service provider SQL 20780 Where name is the name of the index that should exist in the index map in the resource fork Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider 20778 The co...

Page 585: ...rdian name of the partition that is defined in the partition map on the resource fork that does not exist in the metadata Where file is the name of the Guardian file Where string2 is the Guardian name of the partition as it is defined in the metadata PARTITIONS or REPLICAS tables Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Cont...

Page 586: ...re 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 service provider SQL 20786 Where file is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider 20784 Partition map ent...

Page 587: ...e where an inconsistency is detected Cause An inconsistency was found between the object schema version stored in the resource fork and object schema version found in the metadata Effect None This is an informational message Recovery Contact your service provider SQL 20790 Where rname is the partition name defined in the resource fork 20787 The partition name1 defined in the metadata for index ind...

Page 588: ...t one entry for the object Effect VERIFY has detected a problem and reported an inconsistency Recovery Contact your service provider SQL 20792 Where file name is the name of the Guardian file Cause An unexpected error was returned while extracting parts of the ANSI name from the resource fork Effect The operation fails Recovery See the Guardian Procedure Errors and Messages Manual topic File Syste...

Page 589: ...ex map array being verified Where table is the name of the table being verified Cause VERIFY compared the list of indexes defined in the index map of the specified table with the list of indexes defined in the metadata and discovered that the information does not match Effect VERIFY has detected a problem and reported an inconsistency Recovery Contact your service provider SQL 20798 Where active i...

Page 590: ...e in the metadata tables does not match the UID value in the resource fork Effect This mismatch causes operations that depend on these values to be the same to fail Recovery Run the ru option of MXTOOL FIXUP to make the UID value in the resource fork match the UID value in the metadata SQL 20800 Where rscheme is the partitioning scheme of the object stored in the resource fork Where mscheme is the...

Page 591: ...ration on the same partition is already in progress or has failed Effect None This is an informational message Recovery Check if another utility operation is using the same partition and is in progress If it is not contact your service provider SQL 20803 Where object name is the name of the object Where file name is the name of the Guardian file Cause An inconsistency was found during the VERIFY o...

Page 592: ... was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider SQL 20806 Where flag value various flag values on label Where file name is the name of the Guardian file Cause An inconsistency was found during the VERIFY operation Effect None This is an informational message Recovery Contact your service provider 20804 The object type in re...

Page 593: ...file name is the name of the Guardian file Where object name is the name of the object being verified Cause An inconsistency was found during the VERIFY operation The object has not been updated since the system upgrade Effect None This is an informational message Recovery Perform a SELECT COUNT on the object being verified to perform a lazy update to fix the RCB version If the problem persists af...

Page 594: ... 1 indicates the file is currently audited Cause The a option was used with the FIXUP utility to change the audit bit on an SQL MX file to the currently set value Effect None This is a warning Recovery No recovery is necessary SQL 20852 Where file name is the Guardian file name of the SQL MX object Where value is always 0 to indicate the broken bit is already cleared Cause The rb option was used w...

Page 595: ...y on an SQL MP object Effect The operation fails Recovery See the SQL MP documentation for instructions on fixing SQL MP objects SQL 20856 Where file name is the Guardian file name of the SQL MX object Where value is always 0 to indicate the corrupt bit is cleared Cause The rc option was used with the FIXUP utility to reset the corrupt bit on a file where the corrupt bit is not currently set Effec...

Page 596: ...t Cause You attempted to specify the FIXUP utility on a file that exists on a remote node Effect The operation fails Recovery You must run the FIXUP utility on the remote node SQL 20859 Cause An internal error occurred Effect The operation fails Recovery None Contact your service provider SQL 20860 Where file name is the Guardian file specified as an argument to FIXUP Cause You specified a file ot...

Page 597: ...ffect The operation fails Recovery Fix the header information and retry the request SQL 21051 Where source table is the three part ANSI name of the source table of a FASTCOPY command target table is the three part ANSI name of the target table of a FASTCOPY command Cause The FASTCOPY TABLE or FASTCOPY INDEX command is executed with incompatible source and target objects The accompanying error mess...

Page 598: ...pair of clustering key columns in key sequence order have the same column number in the tables Effect The fastcopy operation fails The source and target tables are available to other operations Recovery None SQL 21053 Where source index is the three part ANSI name of the source index of a FASTCOPY command target index is the three part ANSI name of the target index of a FASTCOPY command Cause The ...

Page 599: ...me number of index columns each source target pair of index columns in key sequence order have the same column number in the tables Effect The fastcopy operation fails The source and target tables are available to other operations Recovery None SQL 21055 Where object type is a table or index you specified in the command syntax target object is the three part ANSI name of the target object for a FA...

Page 600: ...Y RI constraint on another table references the target table Effect The fastcopy operation fails The target table and its indexes are available to other operations Recovery Remove the RI constraint and retry if required SQL 21058 Where source object is the three part ANSI name of a source table or index for a FASTCOPY command target object is the three part ANSI name of a target table or index for...

Page 601: ...fined transaction is active when a FASTCOPY command is executed Effect The fastcopy operation fails involved objects are left unchanged Recovery Commit the user defined transaction and retry the FASTCOPY command SQL 21061 Where catalog is the ANSI name of an SQL MX catalog Cause A FASTCOPY command referenced an object from catalog However the catalog does not exist or is not registered on the syst...

Page 602: ...he fastcopy operation fails involved objects are left unchanged Recovery None SQL 21064 Where object 1 is the three part ANSI name of one of the two objects for a FASTCOPY command object 2 is the three part ANSI name of the other object for a FASTCOPY command Cause One of the objects for continuation FASTCOPY command does not participate in any fastcopy operation whereas the other object participa...

Page 603: ...PY command Effect The operation fails involved objects are left unchanged Recovery None SQL 21066 Where object type is table or index as specified in the command syntax Cause For a FASTCOPY command source and target specify the same object Effect The operation fails involved objects are left unchanged Recovery None SQL 21067 Cause For the FASTCOPY INDEX command source and target specify indexes fr...

Page 604: ...astcopy operation is already initiated for the target table or one of its indexes Effect The operation fails involved objects are left unchanged Recovery None SQL 21070 Where source object is the three part ANSI name of the source object for a FASTCOPY command Cause The FASTCOPY is a continuation of a previous command and the source object is modified because the previous command was issued Effect...

Page 605: ...PY command has a system defined SYSKEY column and is the subject table for one or more triggers A FASTCOPY command cannot operate on such a table Effect The operation fails involved objects are left unchanged Recovery Drop all triggers that have the target table as subject table retry the FASTCOPY command and then re create the triggers If necessary execute queries that will perform the trigger ac...

Page 606: ...f the server program that issued the error Cause An error occurred when allocating an object on the heap Effect A resource cannot be allocated and the program fails Recovery Resubmit on another processor SQL 23003 Where servername is the name of the server program that issued the error Where description provides more details about the file error Cause See details in description description Effect ...

Page 607: ...the run time argument and resubmit SQL 23007 Where servername is the name of the server program that issued the error Where description provides details about the file error Cause The DML Layer reported an SQL error See description for the reason Effect The operation fails Recovery Do not attempt recovery Contact your service provider SQL 23008 Cause Internal program ASSERT failed indicating an in...

Page 608: ...ere servername is the name of the server program that issued the error Where error_number is the file system error number returned Where proc_call is the name of the procedure call returning the error Cause The file system procedure proc_call returned an error error_number Effect The operation fails Recovery Correct the problem and resubmit SQL 23013 Where servername is the name of the server prog...

Page 609: ...ion fails Recovery Determine the problem with the input file and resubmit SQL 23016 Where servername is the name of the server program that issued the error Where description contains detailed information about the formatted file in error Cause The formatted XML file is invalid description indicates the nature of the problem If the file is damaged or not a valid format it might indicate a problem ...

Page 610: ...re description contains detailed information about the missing mapping file section name Cause When processing a mapping file an expected section or attribute was not found Effect The operation fails Recovery Correct the mapping file and resubmit SQL 23019 Where description contains detailed information about the error Cause An invalid set of run time arguments are provided Effect The operation fa...

Page 611: ...and resubmit SQL 23022 Where name is the name of the partition in error Cause The program was unable to update the partition metadata Effect The operation fails Recovery None Contact your service provider SQL 23023 Cause None Effect SQL MP tables and aliases will not be exported or imported Recovery None SQL 23024 Where object name is the name of the SQL MX object Where object type is the type of ...

Page 612: ...ject type is the type of the SQL MX object Cause The target SQL MX object already exists and KEEPDDL option is set to OFF Effect The target SQL MX object will be dropped and recreated Recovery None Contact your service provider SQL 23027 Where table name is the name of the SQL MX table Cause The target table already contains statistics Effect None Recovery None SQL 23028 Where table name is the na...

Page 613: ...ATS option to ON SQL 23029 Where option name is either LISTONLY ON or PREPAREMAP Cause None Effect SQL MX objects will not be imported Recovery None SQL 23030 Where operation is either the export or import Cause The mxexportddl or mximportddl operation is started by non schema owner or non super ID user Effect The operation fails Recovery None 23029 option name argument is provided and so SQL MX o...

Page 614: ...Utility Messages 20000 through 23099 HP NonStop SQL MX Messages Manual 640324 001 18 138 ...

Page 615: ...ning The actual error is described in an accompanying message Recovery Not Applicable SQL 25002 Cause This is a versioning internal error please contact the HP GCSC Effect The operation fails Recovery None SQL 25003 Cause This error signals to the call level interface CLI that although the active transaction has been aborted message 8839 should not be issued This error occurs when a downrev compil...

Page 616: ...and name of the affected database object version1 is the source version of the downgrade schema operation component is the software component that detects the situation It is either compiler or local node version2 is the MXV of component Cause An operation attempted to access an object in a schema that is currently being downgraded from an incompatible version The affected object either does not e...

Page 617: ...d feature version and retry SQL 25007 Where string is a short text description of the feature For example HASH2 Partitioning Cause An operation is performed to create or alter an object with a feature that is known but not supported Effect The operation fails Recovery None SQL 25100 where node is the name of the affected remote node MXV1 is the MXV of the affected remote node MXV2 is the local nod...

Page 618: ...ess remote nodes with a different MXV Effect The request fails Recovery Migrate the remote node 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 where node is the name of the affected remote node MXV1 is the MXV of the affected remote node Cause The remote node runs a non GA release of SQL MX a...

Page 619: ... made to access a table or view in a schema with a schema version that is lower than the accessing node s oldest supported schema version This error can be issued from the local node or from an ESP on a remote node Effect The request fails This message will be accompanied by message 25001 which explains what actual software component reported the error Recovery Upgrade the affected schema to a ver...

Page 620: ...de s oldest supported schema version Cause An attempt is made to access a database object with an object schema version that is incompatible with one or more nodes where the object or a partition or an index of the object resides This message indicates that a migration has been made without properly upgrading database objects of old schemas that are no longer supported on the new version Effect Th...

Page 621: ...L 25204 where object1 is the name of a database object that is referenced by the affected query version1 is the object schema version of object1 version2 is the compiler version of the compiler that compiles the query Cause The affected query references a database object with an object schema version that is higher than the compiler version of the compiler This can happen if a downrev compiler is ...

Page 622: ...ler that compiles the query or executes the DDL or utility operation Cause The affected query compilation DDL or utility operation need to access system schema tables with a system schema version that is incompatible with the version of the compiler that compiles the query and executes the operation This can happen if The local system schema version is later than the MXV of a node that is involved...

Page 623: ...e of the node with an incompatible version system schema Where version1 is the system schema version of node Where MXV1 is the MXV of the local node Cause During late name resolution for the affected query you attempted to access an uprev system schema Effect The request fails Recovery Downgrade the system schema on the affected node to a version that is compatible with the MXV of the local node S...

Page 624: ...nces a database object in a schema with a schema version that is lower than the oldest supported schema version of the node where the operation is executed Effect The request fails Recovery Depends on the circumstance If the schema is defined on remote downrev nodes only then an upgrade of the schema should be attempted from one of those nodes If the schema is defined on the local node then the sc...

Page 625: ...on that has an MXV that is compatible with the affected schema version SQL 25213 Where node1 is the node whose system schema is accessed Where version1 is the system schema version of node1 system schema Where node2 is the node that attempts to access the system schema on node1 Where MXV1 is the MXV of node2 Cause The accessing node runs a GA release of SQL MX and is incompatible with a system sch...

Page 626: ...ration Where version1 is the schema version of that schema Where node is the node that attempts to access the schema Where MXV1 is the MXV of node Cause The accessing node runs a GA version of SQL MX and is incompatible with a schema created by a non GA version Effect The request fails Recovery Migrate the accessing node to a SQL MX version that has an MXV that is compatible with the affected sche...

Page 627: ...ma with a version higher than the local node s MXV Effect The operation fails Recovery Migrate to an SQL MX version that has an MXV that is compatible with the affected schema version SQL 25219 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 lower than the OSV of one or more of the involved database objects Such a q...

Page 628: ... of the target of a CREATE SCHEMA command Where version1 is the attempted schema version Where version2 is the schema version of one or more existing schemas in the affected catalog Cause The CREATE_DEFINITION_SCHEMA_VERSION CQD is set to a schema version that is different from the schema version of existing schemas in the affected catalog Effect The operation fails Recovery Allow the system to se...

Page 629: ... associated with a base table Where OFV is the object feature version of object Cause A DOWNGRADE operation affects a schema containing one or more objects that use features that are not supported in the target version Effect The DOWNGRADE operation fails Recovery Use the FEATURE_VERSION_INFO built in function to obtain the objects names Drop the affected objects or alter them so that they no long...

Page 630: ...in the names and MXVs of all nodes where a schema is visible Migrate the specified node s and other involved nodes to a version that supports the target schema version Or specify a target version that is compatible with all involved nodes SQL 25256 Where schema is the schema name of a schema that is affected by a DOWNGRADE operation Where version1 is the schema version of schema prior to the DOWNG...

Page 631: ...cify a valid schema version SQL 25260 Cause A RECOVER command is issued with a catalog name that has not been specified as the target of an active UPGRADE or DOWNGRADE operation Effect The RECOVER command fails Recovery Use the same specification on the RECOVER command that was originally used on the UPGRADE or DOWNGRADE command SQL 25261 Where operation is the UPGRADE or DOWNGRADE operation that ...

Page 632: ...visable to save the view text so that the view can be recreated after the UPGRADE or DOWNGRADE operation SQL 25263 Where operation is UPGRADE or DOWNGRADE operation Cause The specified operation is executed in a user defined transaction Effect The operation fails Recovery Commit or abort the user defined transaction and then re issue the operation SQL 25264 Where schema is a definition schema name...

Page 633: ...ier than the one where the original UPGRADE or DOWNGRADE command was started Effect The operation fails Recovery Migrate the system to version 1 and retry the RECOVER operation SQL 25268 Where remote_node is the Expand node name of a remote node that is related to the node where the DOWNGRADE command is executed Cause The DOWNGRADE command was executed in a distributed environment where one or mor...

Page 634: ...rted plan version Effect The request fails Recovery Recompile the module with a supported version compiler SQL 25301 Where module is the name of the affected module Where version1 is the module version of the affected module Where version2 is the MXV of the local node Cause An attempt is made to load a module with a module version that is higher than the MXV Effect The request fails Recovery Recom...

Page 635: ...lity Cause You attempted to execute a query plan fragment with a plan version that is later than the MXV of the node that executes the plan or plan fragment Effect There are two possibilities Automatic recompilation is attempted if allowed with a downrev compiler that produces plans with a plan version that is compatible with version2 If the recompilation succeeds this message is returned as a war...

Page 636: ...s own version Effect The operation fails Recovery Compile the query with a compiler version that is compatible with the MXV SQL 25309 Where module is the name of the affected module Where version1 is the module version of module Where node is the node that attempts to load the module Where MXV1 is the MXV of the affected node Cause The affected node runs a GA version of SQL MX and is incompatible ...

Page 637: ...re version2 is the actual module version of module Cause The system module was manually renamed to indicate a version other than the actual version Effect The request fails Recovery Reinstall the system module SQL 25312 Where version1 is the required compiler version Where version2 is the actual compiler version Cause The query affects one or more nodes with an MXV lower than the current compiler ...

Page 638: ...is the lowest compiler version that can compile the query Where version3 is the actual compiler version Cause The query affects one or more nodes with an MXV lower than the current compiler version Effect The request fails Recovery Explicitly use a compiler with version in the specified interval 25313 AA compiler with version less than or equal to version1 and higher than or equal to version2 is r...

Page 639: ... retry the operation If the message is issued as a warning NonStop SQL MX attempts to recover automatically SQL 25402 Where catalog is the ANSI name of the target catalog It must be visible on the local node Where node is a remote node where a reference to the target catalog already exists Cause You attempted to register catalog catalog on node node but a reference to catalog already exists on tha...

Page 640: ...ip between catalog1 and catalog2 which have different visibility Effect The operation fails Recovery Correct the error and retry the operation SQL 25405 Where catalog is the ANSI name of the target catalog Where location is the location from a CREATE CATALOG operation Cause A CREATE CATALOG operation specified a remote location either explicitly or because the default volume is remote Effect The o...

Page 641: ... attempted If that succeeds the query executes If not the query fails and additional errors are issued Recovery If the message is issued as an error correct the error and resubmit SQL 25407 Where error is a Guardian file system error number Where node is the expand node name of a remote node Cause Late name resolution encountered the reported file system error when trying to access the system sche...

Page 642: ...node for the UNREGISTER CATALOG command Cause An UNREGISTER CATALOG operation attempted to remove a catalog reference from a node where one or more database objects in that catalog are present Effect The operation fails Recovery Correct the error and retry the operation SQL 25423 Where schema is the ANSI name of the affected schema Where node is the remote node with no replica of the affected sche...

Page 643: ...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 Where volume is the name of a volume that is required implicitly or explicitly by the operation The volume name is fully qualified for example NODEX VOLY Where number is the file system error that resulted from the attempt t...

Page 644: ...se the CASCADE option on UNREGISTER CATALOG SQL 25428 Where catalog1 is the ANSI name of the target catalog for the REGISTER CATALOG command Where node is the name of the target node for the REGISTER CATALOG command Where catalog2 is the ANSI name of a catalog that is related to the target catalog Cause A REGISTER CATALOG operation using the RESTRICT option attempted to register a catalog on a nod...

Page 645: ...ry the operation SQL 25430 Cause A REGISTER CATALOG or UNREGISTER CATALOG operation was attempted for the system catalog Effect The operation fails Recovery None SQL 25431 Where node is the name of the target node for the REGISTER CATALOG command Cause A REGISTER CATALOG operation attempted to register the catalog on a Release 1 8 node Effect The operation fails Recovery None 25429 Catalog catalog...

Page 646: ...st condition was encountered by debug mode software The explanatory text contains the details Effect The affected operation succeeds Recovery None This message is issued as a warning JDBC Driver Error Messages 29000 29999 This range of numbers is reserved for JDBC Driver error messages and are documented in the JDBC documentation For complete information see the applicable JDBC Driver manual 25490...

Page 647: ...specified a rowset size larger than the smallest dimension num2 of the rowset arrays Effect The operation fails Recovery Correct the syntax and resubmit SQL 30003 Cause You specified a rowset size with a value other than an integer host variable or constant Effect The operation fails Recovery Correct the syntax and resubmit 30001 A rowset must be composed of host variable arrays 30002 The given ro...

Page 648: ...resubmit SQL 30006 Cause Stated in the message Effect The operation fails Recovery Refine your SELECT statement and resubmit SQL 30007 Cause You attempted to perform an assign statement using incompatible types Effect The operation fails Recovery Correct the syntax and resubmit 30004 The dimension of the arrays composing the rowset must be greater than zero A value of num was given 30005 The dimen...

Page 649: ...t The operation fails Recovery None Contact your service provider SQL 30011 Cause You attempted to use more than one INTO statement in one query Effect The operation fails Recovery Correct the syntax and resubmit SQL 30012 Cause You did not specify the name of the rowset index in the derived column list given in the message Effect The operation fails 30008 Rowset index is out of range 30009 Trying...

Page 650: ...ttempted to use an embedded UPDATE or DELETE with SELECT INTO and rowset Effect The operation fails Recovery Correct the syntax and resubmit SQL 30021 Cause You attempted to use a rowset in the SET clause of an UPDATE statement when a corresponding rowset is not present in the WHERE clause Effect The operation fails Recovery Correct the syntax and resubmit 30013 Host variable used to set input siz...

Page 651: ... to use NOT ATOMIC inserts on a table that is the subject table of at least one BEFORE trigger Effect The operation fails Recovery Contact your service provider SQL 30028 Where constraint name is the name of the referential integrity constraint table name is the name of the referencing table 30026 NOT ATOMIC rowset INSERT is not supported on a table that has dependent indexes that are not offline ...

Page 652: ...service provider SQL 30035 Cause All rows in the NOT ATOMIC inserts raised nonfatal errors Effect No rows are inserted This is a warning message only Recovery Contact your service provider SQL 30037 Cause The search condition for a DELETE FIRST N statement contains a rowset Effect The statement does not compile Recovery Remove the rowset host variable or parameter from the search condition 30029 N...

Page 653: ...TATE values to SQLCODE values can result in ambiguous SQLCODE values SQLCODE values will often not map to a unique SQLSTATE value For example see the many SQLCODE values mapped to SQLSTATE 42000 in Table 21 1 SQLSTATE Values To deal with the problem of ambiguous SQLCODE values HP recommends retrieving the error message text or the SQLCODE value in addition to the SQLSTATE SQLSTATE values for some ...

Page 654: ...ges were granted You lack grant option on the specified privileges 01007 1013 Not all privileges were granted You lack grant option on some of the specified privileges 01500 1000 A syntax error occurred 01501 1001 An internal error occurred in module name on line num DETAILS details 01502 1002 Catalog catalog does not exist or has not been registered on node node 01503 1003 Schema schema does not ...

Page 655: ...d not be dropped 0150Y 1034 SQL MX was not able to initialize 0150Z 1035 Catalog catalog name already exists 01510 1036 Only super ID can execute DROP SQL 01511 1037 SQL MX is not installed on system node 01512 1038 Not all catalogs have been dropped from the system 01513 1039 The drop SQL statement could not be executed 01514 1040 The use of ALTER on metadata tables is not permitted 01515 1041 Th...

Page 656: ...w table name 0151T 1065 Cannot create constraint name in metadata schema 0151U 1066 Cannot create index table name in metadata schema 0151X 1069 Unable to drop schema name 0151Y 1070 Unable to create object table name file error num 0151Z 1071 Unable to access object table name file error num 01520 1072 Unique constraint name is disabled cannot create foreign key constraint name 01521 1073 Only th...

Page 657: ... to delete rows from table schema name 0152W 1104 Default value string too long for column name 0152X 1105 CREATE TABLE LIKE statement cannot contain both HORIZONTAL PARTITIONS and STORE BY clauses 0152Y 1106 The specified partition name of object name does not exist 01530 1108 The number of columns specified in the view column list num does not match the degree of the query expression num 01531 1...

Page 658: ...t 0153M 1130 The column requires a default value 0153O 1132 An added column cannot have both DEFAULT NULL and NOT NULL 0153P 1133 Only the super ID can perform this operation 0153Q 1134 Concurrent DDL operations are being performed on the given object The current operation cannot be performed 0153R 1135 Clustering key column name must be assigned a NOT NULL NOT DROPPABLE constraint 0153S 1136 For ...

Page 659: ...me conflicting lock exists 01554 1184 Insufficient privilege on name 01555 1185 The location name is either invalid or missing 01556 1186 Column name is of type type incompatible with the default value s type type 01557 1187 The schema name name is reserved for SQL MX metadata 01558 1188 Unable to create referential integrity constraint name for table name due to circular dependency name 0155A 119...

Page 660: ... create server process NonStop Kernel error num while resolving program file name name 0160C 2012 Unable to create server process name NonStop Kernel error num TPC error num error detail num See NonStop Kernel procedure PROCESS_LAUNCH_ for details 0160D 2013 Unable to create server process name NonStop Kernel error num on program file 0160E 2014 Unable to create server process name NonStop Kernel ...

Page 661: ...rs name name name name 0161H 2053 ASSERTION FAILURE CAUGHT BY OPTIMIZER Attempting to recover and produce a plan 0161J 2055 Invalid value num for DEFAULTS attribute name 0161K 2056 The value must be a number in the range num 0161L 2057 The value must be a multiple of num 0161M 2058 DEFAULTS attribute name is of type type but is being converted to type 0161N 2059 Warnings while reading values from ...

Page 662: ...simple value specification that is a literal is not yet supported 01621 2073 Only the super ID user can compile system module name 01622 2074 The name name is reserved for future system modules 01628 2080 Error num while reading file num bytes were read from name when num were expected in module name 01629 2081 Error num while opening file name for read 0162A 2082 Error num while opening file name...

Page 663: ...or b MEDIUM optimization level is not sufficient to satisfy the CQS in effect Suggestion a Inspect the CQS in effect or b Raise the optimization level to MAXIMUM Note that for this query MAXIMUM optimization level might result in a long compile time 0162X 2105 Unable to compile this query because of incompatible Control Query Shape CQS specifications Suggestion Inspect the CQS in effect 0162Y 2106...

Page 664: ...is the only aggregate function that accepts as an operand 0170D 3013 Subtraction is the only operation allowed in the parenthesized expression preceding an interval qualifier 0170E 3014 Precision of numeric value cannot exceed 18 0170F 3015 Scale value cannot exceed precision value 0170G 3016 Precision of decimal value cannot exceed 18 0170H 3017 Expected an unsigned integer not value 0170I 3018 E...

Page 665: ... not yet supported 01711 3037 Precision of type data type cannot exceed 18 01712 3038 PIC X types cannot have leading signs or any signs at all 01713 3039 PIC X types do not have any COMP representation 01714 3040 Precision zero is invalid Add a 9 to the PICTURE clause 01715 3041 UNSIGNED is invalid for a numeric or decimal type with a scale greater than 9 01716 3042 UPSHIFT for a numeric type is ...

Page 666: ...t cannot be droppable when the STORE BY PRIMARY KEY clause appears in a table definition 0171V 3067 ALTER TABLE ADD CONSTRAINT allows only DROPPABLE constraints 0171W 3068 The ALLOCATE and DEALLOCATE clauses cannot coexist in the same ALTER INDEX statement 0171Y 3070 The NO AUDIT clause is not supported 0171Z 3071 Duplicate NO AUDITCOMPRESS clauses 01720 3072 The BLOCKSIZE clause is not allowed in...

Page 667: ...172L 3093 Duplicate DCOMPRESS clauses 0172M 3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements 0172N 3095 Duplicate NO ICOMPRESS clauses 0172O 3096 Duplicate NO SERIALWRITES clauses 0172P 3097 The DEALLOCATE clause is not allowed in the CREATE TABLE statements 0172Q 3098 Duplicate LOCATION clauses 0172R 3099 Duplicate FILE ATTRIBUTE S clauses 0172S 3100 Duplicate DSLACK claus...

Page 668: ...system name part in the specified location name name is invalid Currently the system name part must be NSK or E NSK 0173F 3123 The format of the file name part in the specified location name name is invalid The file name part must be eight characters long and end with the digits 00 0173J 3127 Invalid character in identifier name 0173K 3128 object name is a reserved word It must be delimited by dou...

Page 669: ... TABLE statement 01746 3150 Duplicate WITH HEADING phrases in LIKE clause in CREATE TABLE statement 01747 3151 Duplicate WITH HORIZONTAL PARTITIONS phrases in LIKE clause in CREATE TABLE statement 01749 3153 The FIRST KEY clause is not allowed with hash partitioning 0174B 3155 The POPULATE and NO POPULATE clauses cannot coexist in the same CREATE INDEX statement 0174D 3157 Catalog name is required...

Page 670: ...ing external host language data types incorrectly appears within the SQL query or operation name 0174Z 3179 Collation name is not defined on the character set name 01750 3180 STREAM statements are not allowed in compound statements 01751 3181 Invalid logical name a three part logical name is required 01752 3182 Extra semicolon in a compound statement 01757 3187 Not supported SET STREAM TIMEOUT per...

Page 671: ...09 4009 An aggregate is not allowed inside an aggregate function 0180A 4010 There are no columns with the correlation name name 0180B 4011 Ambiguous star column reference name 0180C 4012 Column reference name must be a grouping column or be specified within an aggregate On this grouped table a star reference is not allowed 0180D 4013 Column name is a system column and cannot be updated or inserted...

Page 672: ...0180Y 4034 The operation name name name name is not allowed 0180Z 4035 Type name cannot be cast to type type 01810 4036 The source field of the EXTRACT function must be of DateTime or Interval type 01811 4037 Field name cannot be extracted from a source of type type 01812 4038 The operand of an AVG or SUM function must be numeric or interval 01813 4039 Column name is of type type incompatible with...

Page 673: ...81P 4061 Rows cannot be inserted into or updated in an individual table partition 0181Q 4062 The preceding error actually occurred in function name 0181R 4063 The operands of function name must be comparable character data types that is of the same character set and collation 0181S 4064 The operands of function name must be compatible character data types that is of the same character set 0181U 40...

Page 674: ...ber of selected values num 0182M 4094 The number of output host variables num must equal the number of selected values num 0182N 4095 A DEFAULT whose value is NULL is not allowed in name 0182O 4096 A DEFAULT specification is currently allowed only when simply contained in the VALUES list of an INSERT 0182P 4097 A NULL operand is not allowed in function name 0182Q 4098 A NULL operand is not allowed...

Page 675: ... not updateable 0183C 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 0183D 4121 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 Table in scope...

Page 676: ...ted Tables in scope name name 0184H 4161 Union between embedded name expression and embedded name expression not supported Tables in scope name name 0184I 4162 Groupby not supported for stream expression Tables in scope name 0184J 4163 Groupby not supported for embedded name expression Tables in scope name 0184K 4164 Outer relation of right join cannot be embedded name expression Tables in scope n...

Page 677: ...03 INSERT UPDATE DELETE operation on nonaudited table name requires index maintenance which might cause the index es to become corrupt 0185O 4204 Stream access only supported for key sequenced tables Table name 0185P 4205 Embedded type only supported for key sequenced tables Table name 0185Q 4206 Embedded type only supported for updateable views View name 0185R 4207 Index name and other indexes co...

Page 678: ...ynamic parameter 0188I 4306 A CALL statement is not allowed within a compound statement 0188J 4307 Rowset parameters are not allowed in a CALL statement 0188K 4308 Internal error unsupported SQL data type value specified for a CALL statement parameter 01900 5000 Internal error in the query normalizer 01I00 6000 Internal error in the query optimizer 01I01 6001 DISTINCT aggregates can be computed on...

Page 679: ...ing to update or delete from a cursor that is not in the fetched state 01K0E 8014 A SELECT statement within a compound statement did not return any row 01K0F 8015 Aborting transaction because a compound statement performed an update operation followed by a SELECT statement that did not return any row 01K0G 8016 An attempt was made to access name which has a system version that is incompatible with...

Page 680: ... or a percent character 01KBF 8411 A numeric overflow occurred during an arithmetic computation or data conversion 01KBG 8412 An input character host variable is missing its null terminator 01KBH 8413 The string argument contains characters that cannot be converted 01KBI 8414 The attempted conversion is not supported on this platform 01KBJ 8415 The provided DATE TIME or TIMESTAMP is not valid and ...

Page 681: ...nt was recompiled 01KG1 8577 Table index or view name not found 01KG2 8578 Similarity check passed 01KG3 8579 Similarity check failed name 01KGP 8601 Error returned from file system while locking unlocking 01KGQ 8602 The file system reported error num on a lock unlock operation 01KGR 8603 Trying to begin a transaction that has already been started 01KGS 8604 Transaction subsystem name returned err...

Page 682: ...ies for a descriptor 01KMG 8808 Module file name contains corrupted or invalid data 01KMH 8809 Unable to open the module file name 01KMJ 8811 Trying to close a statement that is either not in the open state or has not reached EOF 01KMK 8812 Trying to execute a statement that is not in the closed state 01KML 8813 Trying to fetch from a statement that is in the closed state 01KMM 8814 The transactio...

Page 683: ...ormation requested 01KN8 8836 Invalid update column for cursor 01KN9 8837 Invalid user id 01KNA 8838 Unable to receive reply from MXCMP possibly caused by internal errors when compiling SQL statements processing DDL statements or executing the built in stored procedures 01KNB 8839 Transaction was aborted 01KNC 8840 Object name provided to CLI is invalid 01KND 8841 User application committed or abo...

Page 684: ...NY 8862 Module file name has obsolete descriptor location table entry 01KNZ 8863 Module file name has obsolete descriptor header 01KO0 8864 Module file name has obsolete descriptor entry 01KO1 8865 Module file name has obsolete procedure location table header 01KO2 8866 Module file name has obsolete procedure location table entry 01KO3 8867 Error while reading from file name 01KO4 8868 Unable to c...

Page 685: ...s no longer running The statement will be assigned a new MXUDR server if it is executed again 01KP2 8902 Internal error MXUDR returned an invalid UDR handle 01KP3 8903 An attempt was made by SQL MX to kill the MXUDR server for this statement process name PROCESS_STOP_ returned value 01KP4 8904 Unable to receive reply from MXUDR possibly caused by internal errors while executing user defined routin...

Page 686: ...le to CREATE object name 01L5Z 9215 UPDATE STATISTICS encountered an internal error location 01M01 10001 Sort Error No error text is defined for this error 01M03 10003 Sort Error Warning Scratch File EOF 01M04 10004 Sort Error Merge is disallowed for Sort 01M05 10005 Sort Error Unexpected error value Check error 01M06 10006 Sort Error Previous IO failed 01M07 10007 Sort Error Error writing to Scra...

Page 687: ...pected error during message processing string 01N33 11111 MXUDR Internal error value 01N35 11113 MXUDR Internal error An unexpected UNLOAD request arrived for UDR handle string 01N5L 11201 Language Manager initialization failed Details Error occurred while loading Java System Class class name 01N5M 11202 Language Manager initialization failed Details Unable to initialize JVM 01N5N 11203 The Langua...

Page 688: ...ql SQLException Details string 01N64 11220 A Java method completed with an uncaught java sql SQLException with invalid SQLSTATE The uncaught exception had an SQLCODE of SQLCODE value and SQLSTATE of SQLSTATE value Details string 01N65 11221 Language Manager is out of memory string 01N66 11222 The operation failed because the Java Virtual Machine ran out of memory 01N67 11223 Language Manager encou...

Page 689: ... is multiply defined 01P0I 13018 Descriptor name name is invalid 01P0J 13019 Statement name name uses name a reserved name SQLC generates 01P0K 13020 Statement name name is multiply defined 01P0L 13021 name is already defined 01P0M 13022 Cursor name is already defined 01P0N 13023 name is already defined as a dynamic cursor 01P0O 13024 Cursor name was not declared 01P0P 13025 Warning s near line nu...

Page 690: ...end member declaration near line num 01P1B 13047 Undefined tag name near line num 01P1C 13048 Tag name redefined near line num 01P1D 13049 Input file not good near line num 01P1E 13050 Cursor name not closed 01P1F 13051 Cursor name not opened 01P1G 13052 Cursor name not fetched 01P1H 13053 Cursor name not opened or closed 01P1I 13054 Cursor name not fetched or closed 01P1J 13055 Cursor name not op...

Page 691: ...is longer than 128 characters 01P23 13075 Externally qualified module name module name is not a Regular Identifier or is longer than 248 characters 01P24 13076 Catalog name catalog name is not a valid OSS file name or is longer than 128 characters 01P25 13077 Schema name schema name is not a valid OSS file name or is longer than 128 characters 01PDW 13500 SQLCO errors 01PDX 13501 Invalid command o...

Page 692: ...ted correctly for a host variable 01PEM 13526 Line num name name clause is not valid for a host variable 01PEN 13527 The first declaration in an SQL DECLARE SECTION must have level 01 or 77 01PEO 13528 Line num Variable num is not alphabetic and cannot have a CHARACTER SET clause 01PEP 13529 Missing END DECLARE SECTION detected at line num 01PM8 13800 Line num name is not a valid character set nam...

Page 693: ...wed by either a comma or a semicolon 01R0P 15025 Cursor operations are not supported by SQLCI 01R0Q 15026 Break rejected 01R0S 15028 Break error 01R0U 15030 The specified define already exists Use alter or delete and add 01R0V 15031 The specified define does not exist 01R0W 15032 An error occurred while adding altering or deleting this define 01R0X 15033 Break was received 01R0Y 15034 Invalid LOG ...

Page 694: ... the same query is not supported 01U0C 30012 Rowset index name must be specified last in the derived column list of name 01U0D 30013 Hostvar used to set input size of rowset has zero or negative value 01U0E 30014 Hostvar used to set input size of rowset is not of type short int or long 01U0K 30020 Embedded UPDATE DELETE cannot be used with SELECT INTO and rowset 01Y00 16000 Error message file not ...

Page 695: ... with module version MXV1 01Z8N 25311 System module module has a wrong module version The expected module version is version1 the actual module version is version2 02000 100 The no data completion condition SQLCODE 100 07001 15015 PARAM name value num cannot be converted to type type 07001 15016 PARAM name not found 07001 15019 num values were supplied in the USING list while the statement contain...

Page 696: ...025 Cursor operations are not supported by SQLCI 0A000 2072 A simple value specification that is a literal is not yet supported 0A000 3009 DROP ASSERTION statement is not yet supported 0A000 3010 Character set name is not yet supported 0A000 3022 The name operator is not yet supported 0A000 3023 The COLLATE clause in a sort specification is not yet supported 0A000 3024 The MATCH PARTIAL clause is ...

Page 697: ...or deleting from the same table name is not currently supported name is contained by view s name 0A000 4069 Column name uses an unsupported collation name 0A000 4085 File organization name of object name is not supported 0A000 4089 Check constraint name contains a subquery which is not yet supported 0A000 4096 A DEFAULT specification is currently allowed only when simply contained in the VALUES li...

Page 698: ...source string length 22012 4075 Division by zero in constant expression name 22012 8419 An arithmetic expression attempted a division by zero 22015 3044 Invalid interval num 22019 8409 The escape character argument of a LIKE predicate must be one character in length 22024 8412 An input character host variable is missing its null terminator 22025 8410 An escape character in a LIKE pattern must be f...

Page 699: ... ONLY for an INSERT UPDATE DELETE or DDL statement 25000 8603 Trying to begin a transaction that has already been started 25000 8604 Transaction subsystem name returned error num while starting a transaction 25000 8605 Committing a transaction which has not started 25000 8606 Transaction subsystem name returned error num on a commit transaction 25000 8612 Transaction mode cannot be set if the tran...

Page 700: ...or that is not allocated with AllocDesc call 34000 2066 Cursor name was not found in module name 38000 11218 A Java method completed with an uncaught Java exception Details string 39001 11220 A Java method completed with an uncaught java sql SQLException with invalid SQLSTATE The uncaught exception had an SQLCODE of SQLCODE value and SQLSTATE of SQLSTATE value Details string 3D000 8008 Catalog nam...

Page 701: ... for routine parameter 42000 1123 Unable to process the partition key values num for object name Please verify that the correct key value data types were specified 42000 1136 For an added column the PRIMARY KEY clause cannot be NOT DROPPABLE 42000 1186 Column name is of type type incompatible with the default value s type type 42000 13002 Syntax error near line num 42000 13025 Warning s near line ...

Page 702: ...c cursor name has already been defined in this module The previous definition as a dynamic cursor is being retained and this latest one ignored 42000 2063 Dynamic cursor name has already been defined in this module The previous definition as a static cursor is being retained and this latest one ignored 42000 2064 Dynamic cursor name has already been defined in this module The previous definition a...

Page 703: ...value of num was given 42000 30005 The dimensions of the arrays composing the rowset are different The smallest dimension is assumed 42000 30006 Rowset and one dimensional variable are in output list 42000 30007 Incompatible assignment from type type to type type 42000 3001 Syntax error at or before SQL text 42000 3002 name is not a valid column reference it has more than 4 name parts 42000 3003 L...

Page 704: ...e subvolume name part in the specified location name name is invalid The subvolume name part must be eight characters long and begin with the letters ZSD 42000 3026 A comma must be used to separate file attributes 42000 3027 name is not a valid simple name it has more than one name part 42000 3037 Precision of type data type cannot exceed 18 42000 3038 PIC X types cannot have leading signs or any ...

Page 705: ...in the PARTITION clause 42000 3065 The primary key constraint cannot be droppable when the STORE BY PRIMARY KEY clause appears in a table definition 42000 3067 ALTER TABLE ADD CONSTRAINT allows only DROPPABLE constraints 42000 3068 The ALLOCATE and DEALLOCATE clauses cannot coexist in the same ALTER INDEX statement 42000 3071 Duplicate NO AUDITCOMPRESS clauses 42000 3072 The BLOCKSIZE clause is no...

Page 706: ... clauses 42000 3094 The DEALLOCATE clause is not allowed in the CREATE INDEX statements 42000 3095 Duplicate NO ICOMPRESS clauses 42000 3096 Duplicate NO SERIALWRITES clauses 42000 3097 The DEALLOCATE clause is not allowed in the CREATE TABLE statements 42000 3098 Duplicate LOCATION clauses 42000 3099 Duplicate FILE ATTRIBUTE S clauses 42000 3100 Duplicate DSLACK clauses 42000 3101 Duplicate ISLAC...

Page 707: ... a reserved word It must be delimited by double quotes to be used as an identifier 42000 3129 Function name accepts exactly one operand 42000 3132 The HEADING for column name exceeds the maximum size of 128 characters 42000 3133 PERFORM is valid only in COBOL programs 42000 3134 Precision of time or timeStamp num cannot exceed 6 42000 3135 Precision of float value cannot exceed 54 42000 3136 Only ...

Page 708: ...3165 Min or max precision or exponent value exceeded num 42000 3166 Min or max value for float or double value exceeded num 42000 3167 Duplicate NOT DROPPABLE clauses 42000 3168 The FOR ACCESS clause is not allowed in a CREATE VIEW statement 42000 3171 Transaction statements are not allowed in compound statements 42000 3172 EXIT is not allowed in a compound statement 42000 3173 UPDATE STATISTICS i...

Page 709: ...st be between 1 and the number of select expressions which in this case is num 42000 4008 A subquery is not allowed inside an aggregate function 42000 4009 An aggregate is not allowed inside an aggregate function 42000 4010 There are no columns with the correlation name name 42000 4011 Ambiguous star column reference name 42000 4012 Column reference name must be a grouping column or be specified w...

Page 710: ...Error while preparing constraint name on table name 42000 4027 Table name is not insertable 42000 4028 Table name is not updateable 42000 4030 Column name is an invalid combination of datetime fields num num num 42000 4031 Column name is an unknown data type num 42000 4032 Column name is an unknown class num It is neither a system column nor a user column 42000 4033 Column name is a primary or clu...

Page 711: ...he third operand of function name must be numeric 42000 4055 The select lists or tuples must have comparable data types type and type are not comparable 42000 4056 Exposed name name appears more than once 42000 4057 Correlation name name conflicts with qualified identifier of table name 42000 4059 The first operand of function name must be numeric 42000 4061 Rows cannot be inserted into or updated...

Page 712: ...rameters num must equal the number of selected values num 42000 4094 The number of output host variables num must equal the number of selected values num 42000 4095 A DEFAULT whose value is NULL is not allowed in name 42000 4097 A NULL operand is not allowed in function name 42000 4098 A NULL operand is not allowed in operation name 42000 4099 A NULL operand is not allowed in predicate name 42000 ...

Page 713: ...ROUP 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 Table in scope name 42000 4122 NULL cannot be assigned to NOT NULL column name 42000 4123 NULL cannot be cast to a NOT NULL data type 42000 4125 The select list of a subquery in a row value constructor if the subquery is one of several expressio...

Page 714: ...ound in external path path name HY011 8855 Statement attribute cannot be set now HY011 8857 Statement attribute cannot be set now INPUT_ARRAY_MAXSIZE must be set before compiling the statement HY024 8854 Invalid attribute value HY024 8856 Invalid attribute value INPUT_ARRAY_MAXSIZE must be positive HY092 8853 Invalid attribute definition X0101 1001 An internal error occurred in module name on line...

Page 715: ...ject name X010Y 1034 Unable to initialize SQL X010Z 1035 Catalog name already exists X0110 1036 Only the super ID can execute DROP SQL X0111 1037 SQL is not installed on system name X0112 1038 All catalogs have not been dropped from the system X0113 1039 Unable to drop SQL X0114 1040 Cannot alter metadata table X0115 1041 The primary key has already been defined X0116 1042 All PRIMARY KEY or UNIQU...

Page 716: ... schema X011X 1069 Unable to drop schema name X011Y 1070 Unable to create object name file error num X011Z 1071 Unable to access object name file error num X0120 1072 Unique constraint name is disabled cannot create foreign key constraint name X0121 1073 Only the super ID user can execute INITIALIZE SQL X0123 1075 Catalog name contains at least one schema The catalog must be empty X0125 1077 Metad...

Page 717: ...tition name of object name does not exist X0130 1108 The number of columns specified in the view column list num does not match the degree of the query expression num X0131 1109 The WITH CHECK OPTION clause appears in the definition of view name but the view is not updateable X0136 1114 Unable to create catalog name metadata tables on name X0137 1115 Unable to create label for name file error num ...

Page 718: ...ferenced base table name To display the data violating the constraint please use the following DML statement name X0140 1144 Expected a quoted string in first key clause for column name on table name value detected is name X0141 1145 The catalog name name is reserved for SQL MX metadata X0142 1146 Unable to alter object name because it is not a name X0143 1147 System generated column name of base ...

Page 719: ... while opening or reading from DEFAULTS table name Using name values X0202 2002 Internal error cannot create MXCMP server X0203 2003 Internal error cannot establish connection with MXCMP server X0204 2004 Internal error error from MXCMP cannot work on this query X0205 2005 Internal error from compilation no errors in diagnostics yet for statement name X0206 2006 Internal error assertion failure na...

Page 720: ...e to create OSS server process name OSS is not running X020U 2030 Unable to create server process name via inetd err no num X020X 2033 text NonStop Kernel error num while communicating with process name X020Y 2034 text NonStop Kernel error num while communicating with server process name X020Z 2035 text Unable to open process name err no num X0211 2037 receiving process A message from process send...

Page 721: ...of MINIMUM optimization level or b Incompatible Control Query Shape specifications X022W 2104 Unable to compile this query for one of two reasons a Incompatible Control Query Shape CQS specifications or b MEDIUM optimization level is not sufficient to satisfy the CQS in effect Suggestion a Inspect the CQS in effect or b Raise the optimization level to MAXIMUM Note that for this query MAXIMUM optim...

Page 722: ... stream expression X044A 4154 Statement might not compile due to an order requirement on embedded name expression X044B 4155 Secondary indexes don t support order requirement Table name X044D 4157 Inner relation of left join cannot be stream expression Tables in scope name X044E 4158 Join of stream expressions not supported Tables in scope name X044F 4159 Intersection of stream expressions not sup...

Page 723: ...xpression not supported Tables in scope name X044X 4177 Update of name column name not permitted on rollback X044Y 4178 Update of variable length column name not permitted on rollback X044Z 4179 SEQUENCE BY not supported for stream expressions X0450 4180 Stream expression not supported for top level DELETE statement X0451 4181 Join with embedded name expression is not supported X0452 4182 Selectio...

Page 724: ...le name X0460 4216 The FIRST ANY n syntax cannot be used with an embedded update or embedded DELETE statement X0461 4217 X048C 4300 Invalid usage of procedure procedure name A UDR was invoked within a trigger X048E 4302 Procedure procedure name expects value1 parameters but was called with value2 parameters X048F 4303 The supplied type for parameter value of routine routine name was type name1 whi...

Page 725: ...ed operation X0806 8006 The stream timed out but the cursor is still open X0807 8007 The operation has been canceled X080A 8010 Default catalog name name Default schema name name X080B 8011 SELECT statement inside compound BEGIN END statement returns more than one row X080C 8012 Encoding of CONTROL QUERY DEFAULTs name X080E 8014 A SELECT statement within compound statement did not return any row X...

Page 726: ...X08OI 8882 Containing SQL not permitted X08OJ 8883 The current context has violation checking functions disabled Use SQL_EXEC_SetUdrAttributes_Internal to enable it X08OU 8894 Argument argument name of CLI function function name is reserved for future use and must be set to string when calling the function X083W 8140 Prohibited SQL statement attempted X083X 8141 An error was artificially injected ...

Page 727: ...rted error num on a lock unlock operation X08JG 8700 An assertion failure or out of memory condition occurred during parallel execution X08JQ 8710 Error num returned by Measure when attempting to update SQL counters X08MG 8808 Module file name contains corrupted or invalid data X08MH 8809 Unable to open the module file name X08MN 8815 Error while building the TCB tree when executing the statement ...

Page 728: ...check error X08NO 8852 Holdable cursors are only supported for streaming cursors and embedded UPDATE DELETE cursors X08NU 8858 The value num passed in through input a host variable parameter is an invalid SQL identifier X08NV 8859 There are pending insert delete or update operations X08NW 8860 Module file name has obsolete module header X08NX 8861 Module file name has obsolete descriptor location ...

Page 729: ... a null terminator character You need to exclude this column from the column group list in UPDATE STATISTICS X095S 9208 Unable to access column definitions X095T 9209 Column name name does not exist in the table X095U 9210 One of the column data types is not supported by UPDATE STATISTICS You need to exclude this column from the column group list in UPDATE STATISTICS X095W 9212 Cardinality statist...

Page 730: ...EN_ failed X0A0O 10024 Sort Error SetMode failed X0A0P 10025 Sort Error FileClose failed X0A0Q 10026 Sort Error AWAITIOX failed X0A0R 10027 Sort Error FILE_GETINFOLIST failed X0A0S 10028 Sort Error POSITION failed X0A0T 10029 Sort Error FILE_GETINFO_ failed X0A18 10044 Sort Error IO did not complete X0A1B 10047 Sort Error Wrong length read X0B2T 11101 MXUDR Unknown message type value X0B2V 11103 M...

Page 731: ...eter type used at position value X0B67 11223 Language Manager encountered internal error detail text X0B68 11224 JVM raised an exception Details detail text X0B69 11225 Specified signature is invalid Reason Unknown or unsupported type used as a return type X0B6A 11226 Java execution Invalid null input value at parameter position value X0B6B 11227 Java execution Data overflow occurred while retriev...

Page 732: ...ates X0D0K 13020 Statement name name is multiply defined X0D0L 13021 name is already defined X0D0M 13022 Cursor name is already defined X0D0N 13023 name is already defined as a dynamic cursor X0D0O 13024 Cursor name was not declared X0D0Q 13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements X0D0R 13027 Only one EXEC SQL MODULE statement is allowed X0...

Page 733: ...not used X0D1L 13057 End of file processing generated unexpected cursor status of num for cursor name X0D1M 13058 Unable to open SQL CLI header file name X0D1O 13060 Unable to open the listing file name X0D1P 13061 Invalid NUMERIC precision specified near line num X0D1Q 13062 Unsigned long long type not allowed near line num X0D1R 13063 Identifier name not defined near line num X0D1S 13064 Identif...

Page 734: ...n name X0DE0 13504 Missing timestamp command option X0DE1 13505 Source input file name cannot be opened X0DE2 13506 COBOL output source file name cannot be opened X0DE3 13507 Error while parsing source name X0DE4 13508 Expecting name found name X0DE5 13509 Expecting name after name found name X0DE6 13510 The SQL declare section might not contain COPY or REPLACE X0DE7 13511 End of input file while ...

Page 735: ...pt to name X0F06 15006 Error num while reading from file X0F07 15007 Error num while opening file name X0F08 15008 The specified statement does not exist in the history buffer X0F09 15009 The requested help topic is too long X0F0A 15010 The help file could not be opened X0F0B 15011 No help is available for the requested topic X0F0C 15012 File read error on the help file X0F0E 15014 Section name no...

Page 736: ...MXVs older than MXV2 X0P2T 25101 Remote node node runs an incompatible version of SQL MX software The SQL MX software version MXV of node is MXV1 the local node only supports MXV MXV2 X0P2U 25102 Remote node node runs a version of SQL MX software which cannot interoperate with other versions The SQL MX software version MXV of node is MXV1 X0P8C 25300 Module module had module version version1 node ...

Page 737: ...ted X0U0C 30012 Rowset index name must be specified last in the derived column list of name X0U0D 30013 Hostvar used to set input size of rowset has zero or negative value X0U0E 30014 Hostvar used to set input size of rowset is not of type short int or long X0U0K 30020 Embedded UPDATE DELETE cannot be used with SELECT INTO and rowset XW02S 100 The no data completion condition SQLCODE 100 XW10C 101...

Page 738: ...SQLSTATE Values Returned by NonStop SQL MX HP NonStop SQL MX Messages Manual 640324 001 21 86 SQLSTATE Values ...

Page 739: ...e generated when InstallSqlmx initializes NonStop SQL MX Install0001 Cause The specified system volume was invalid Effect The operation fails Recovery Specify the correct syntax for the volume and retry the request Install0002 Cause You attempted to use the Rebuild b option on a system that has not performed an INITIALIZE SQL operation Effect The operation fails Recovery If you believe that the sy...

Page 740: ... a mismatch between the system metadata and the anchor file The anchor file no longer exists However the system metadata still exists at the volume volume Effect The operation fails Recovery Use the Rebuild Anchor File b option to re create the anchor file Install0006 Cause You specified the InstallSqlmx Location l option more than once Effect The operation fails Install0003 Multiple instances of ...

Page 741: ...ript and specify the nofcheck option after you specify the l option Install0009 Cause The n option must be specified after the l option You specified it before Effect The operation fails Recovery Rerun the InstallSqlmx script and specify the l option before you specify the n option Install0010 Cause You specified an invalid argument with argument Effect The operation fails Recovery Enter one of th...

Page 742: ...has failed Effect The operation fails Recovery Check other errors that are returned to determine the cause of the failure After the failure has been fixed retry the request Install0014 Cause SQL MX files installed from the SUT are missing Effect The operation fails Recovery Reinstall the missing SQL MX files from the SUT and restart installation Install0011 Invalid character set specified with the...

Page 743: ...perform this function Effect The operation fails Recovery Log on as the super ID before executing this command Install0018 Cause One or more processors in the system do not meet the minimum hardware requirements for installing NonStop SQL MX All processors in a node on which NonStop SQL MX Release 2 0 or a superseding product is installed must be Model 1954 S72000 or newer Effect The operation fai...

Page 744: ...ted an invalid combination of options If EXECUTE SCRIPT is to be chosen it must be the only option executed ALL MPALIAS DEFAULTS and PROCS are not valid when using SCRIPT Effect The operation fails and valid syntax options are displayed Recovery Remove the ALL MPALIAS DEFAULTS or PROCS option and resubmit migr0002 Cause The Metadata Migration tool has detected an invalid combination of options SHO...

Page 745: ...or this command Effect The operation fails and valid syntax options are displayed Recovery Use the correct file name and resubmit migr0005 Cause SQL MP is not installed on the system There is nothing to migrate Effect The operation fails Recovery None migr0006 Cause NonStop SQL MX is not installed on the system which is required Effect The operation fails Recovery Install NonStop SQL MX prior to r...

Page 746: ... SCRIPT option that does not exist Effect The operation fails Recovery Specify the correct file name and resubmit migr0016 Cause SQL MP is installed but it does not have a PARAMS table Effect There are no PARAMS entries to migrate Verify that this is correct Recovery None This message is a warning migr0007 Incorrect version of SQL MX is installed for migrate migr0008 Environment variable NSK_VOL o...

Page 747: ...installed but it does not have a PROCS or PARAMS table Effect There are no PROCS entries to migrate Verify that this is correct Recovery None This message is a warning migr0020 Cause A file name specified in the ERROR_LOG option already exists and CLEAR is not used Effect None The file name will default to error_log out Recovery None This message is a warning migr0017 SQL MP system catalog does no...

Page 748: ... name defaults to script out Recovery None This message is a warning migr0024 Cause The ERROR_LOG option was not chosen for the EXECUTE command Effect None An ERROR_LOG is captured to the default file name error_log out Recovery None This message is a warning migr0021 The SCRIPT OSS filename option was chosen without the CLEAR and the specified OSS filename already exists The filename has defaulte...

Page 749: ...S0002 File errors MXGNAMES0003 SQL errors MXGNAMES0004 Command line errors MXGNAMES0000 Cause MXGNAMES failed to allocate memory needed for execution Effect The operation fails Recovery Determine the memory usage on the system and if necessary contact your service provider MXGNAMES0002 Cause An error occurred during the reading or writing of the EDIT file Effect The operation fails Recovery See th...

Page 750: ...that the input list of table names specified for the SQLNames option is properly formatted If this does not correct the problem contact your service provider MXGNAMES0004 Cause You specified an unknown option on the MXGNAMES command line Effect The operation fails Recovery Remove the unknown option and resubmit MXGNAMES0004 Cause You failed to specify either output format BR2 or TMF at the command...

Page 751: ...a value or specified an invalid value for an option that requires a value Effect The operation fails Recovery Specify a correct value for the option and resubmit MXGNAMES0004 Cause You specified a value for an option that does not take a value such as TMF BR2 or nocomment Effect The operation fails Recovery Remove the unnecessary values specified for the option and resubmit MXGNAMES0004 Command li...

Page 752: ...Non SQLCODE Error Messages HP NonStop SQL MX Messages Manual 640324 001 A 14 MXGNAMES Utility ...

Reviews:

No comments

Brands by name

Popular brands

Load more brands