1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Neoview Messages
  6. Manual

HP Neoview Messages Manual

Hide thumbs
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
Table of Contents

Advertisement

Quick Links

Download this manual
HP Neoview Messages Manual (Volume 1)
HP Part Number: 61 1472-001
Published: August 2010
Edition: HP Neoview Release 2.5

Advertisement

Table of Contents
loading

Related Manuals for HP Neoview Messages

Summary of Contents for HP Neoview Messages

  • Page 1 HP Neoview Messages Manual (Volume 1) HP Part Number: 61 1472-001 Published: August 2010 Edition: HP Neoview Release 2.5...
  • Page 2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    General Syntax Notation........................7 Notation for Messages........................8 Related Documentation..........................9 Neoview Customer Library.......................9 Publishing History..........................11 HP Encourages Your Comments......................11 1 Message Handling......................13 Viewing Neoview Database Messages....................13 SQLSTATE and SQLCODE........................13 Contacting Your Service Provider......................14 2 Data Definition Language (DDL) Messages (1000 Through 1999)......15 3 Neoview Compiler Messages (2000 Through 2999)..........67...
  • Page 4 12 Trigger, UDR Server, and Language Manager Messages (1 1000 Through 1 1399)..........................239 13 Materialized Views Messages (12000 Through 12329)........251 14 Messages Generated by the Message System (16000 Through 16999)...267 15 Internal Stored Procedures Messages (19000 Through 19999)......269 16 Utility Messages (20000 Through 23099)............271 17 Authentication and User Management Messages (24000 Through 24999)..333 18 Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29399)....................351...

  • Page 5: About This Document

    About This Document The Neoview SQL database is the HP relational database management system (RDBMS) based on ANSI SQL-92. It uses the industry standard Structured Query Language (SQL) to define and manipulate data. This manual describes messages produced by the HP Neoview data warehousing platform and its associated subsystems.

  • Page 6: New And Changed Information

    Chapter Title Chapter 10 (page 225) “UPDATE STATISTICS Messages (9200 Through 9218)” Chapter 11 (page 229) “Executor Sort and Scratch File I/O Messages (10000 Through 10199)” Chapter 12 (page 239) “Trigger, UDR Server, and Language Manager Messages (11000 Through 11399)” Chapter 13 (page 251) “Materialized Views Messages (12000 Through 12329)”...

  • Page 7: Notation Conventions

    Chapter (page) Description Messages Added or Changed Chapter 17 (page 333) Chapter 17 (page 333) This chapter is new. 24001, 24002, 24003, 24004, 24005, 24006, 24007, 24008, 24009, 24010, 24011, 24012, 24013, 24014, 24015, 24016, 24017, 24019, 24020, 24021, 24022, 24023, 24026, 24027, 24028, 24029, 24030, 24031, 24033, 24034, 24036, 24037, 24039, 24040, 24041, 24042, 24043, 24044, 24045,...

  • Page 8: Notation For Messages

    Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: DAY (datetime-expression) @script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "{"...

  • Page 9: Related Documentation

    %005400 %B101111 %H2F P=%p-register E=%e-register Related Documentation This manual is part of the HP Neoview library, which includes: Neoview Customer Library The manuals in the Neoview customer library are listed here for your convenience. • Administration Neoview User Management and...
  • Page 10 — README for the HP Neoview Transporter Java Client • Management HP Database Manager (HPDM) Help topics that describe how to use the HP Database Manager client to monitor Online Help and manage a Neoview data warehousing platform. HP Database Manager (HPDM)

  • Page 11: Publishing History

    You can find this manual or its replacement at http://www.hp.com/go/neoviewdocs. HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or comments to docsfeedback@hp.com.

  • Page 13: Message Handling

    1 Message Handling The Neoview database software reports exception condition messages at the HP Neoview Database Connectivity Service conversational interface (NDCS) window. Most Neoview database software exception condition messages describe error conditions for which recovery action is required. Some messages are warnings that provide information for which no action is required.

  • Page 14: Contacting Your Service Provider

    value for all Neoview database software messages other than those for which an ANSI SQL-92 SQLSTATE value exists. The SQLCODE parameter is a deprecated feature that is supported to maintain compatibility with earlier versions of the American standard. Tables in “SQLSTATE Values” in Volume 2 of this manual identify the equivalent SQLSTATE and SQLCODE values for Neoview database software warning and error messages.

  • Page 15: Data Definition Language (Ddl) Messages (1000 Through 1999)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1002 1002 Catalog catalog does not exist or has not been registered on node segment.
  • Page 16 The statement that you specified is not available for use. Effect The operation fails. Recovery Do not attempt to use this HP Neoview database statement. SQL 1012 1012 No privileges were granted. You lack grant option on the specified privileges.
  • Page 17 You attempted to grant privileges, but you do not have grant options for at least one of them. Effect The HP Neoview database granted some privileges, but not all that you attempted to grant. Recovery You must have grant options for privileges to grant them.
  • Page 18 Recovery None. SQL 1021 1021 SQL is already initialized on system segment. is the name of the HP Neoview platform segment on which the INITIALIZE SQL segment statement was executed. Cause The HP Neoview platform has already been initialized on this segment.
  • Page 19 SQL 1028 1028 The schema must be empty. It contains at least one object object-name. is the name of an HP Neoview database object existing in the schema. object-name Cause You attempted to drop a schema that contains one or more objects.
  • Page 20 Cause In a replication or distribution context: An operation attempted to create a catalog reference or a partition on a segment where the HP Neoview database has not been installed. Effect The operation fails. Recovery Either reissue the statement specifying a different segment, or install the HP Neoview database on segment and resubmit.
  • Page 21 SQL 1040 1040 The use of ALTER on metadata tables is not permitted. Cause An ALTER TABLE statement was issued naming a table that is part of the HP Neoview database metadata. Such tables cannot be altered. Effect The operation fails.
  • Page 22 Recovery Check that constraint-name references a unique or primary constraint in the referenced table. SQL 1046 1046 Referenced and referencing column lists do not match for constraint constraint-name. is the name of a column constraint or table constraint. constraint-name Cause The list of referencing columns in constraint-name does not match the list of unique key columns that it is referencing.
  • Page 23 You attempted to drop a table that has a referential constraint or a check constraint that refers to another table. Effect The HP Neoview database software does not drop the table. Recovery Either drop all constraints that refer to other tables and then drop the table, or...
  • Page 24 1061 Dropping metadata catalog catalog-name is not allowed. is the name of an HP Neoview database catalog. catalog-name Cause You attempted to drop a catalog that is part of the HP Neoview database metadata. Effect The operation fails. Recovery None.
  • Page 25 SQL 1073 1073 Only services ID can execute INITIALIZE SQL. Cause You attempted to initialize the HP Neoview database, but you are not the services ID. Only the services ID can perform this function. Effect The operation fails.
  • Page 26 You attempted to create a table that has two columns with the same name. If you name a column “SYSKEY,” duplication can result from the implicit creation by the HP Neoview database software of a column named SYSKEY to ensure uniqueness for the clustering key.
  • Page 27 SQL 1082 1082 Validation for constraint constraint-name failed unexpectedly. is the name of a column or table constraint. constraint-name Cause The constraint validation failed, either because a concurrent operation was being performed on the table or on the referenced table (for a referential integrity constraint), or data in the table violates the constraint.
  • Page 28 SQL 1088 1088 The system generated column SYSKEY must be specified last or not specified at all in the STORE BY column list. Cause If the system-generated column SYSKEY is specified in the STORE BY list of columns, it must be specified last. Effect The operation fails.
  • Page 29 For clarification, see the accompanying error message. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 101 1101 Table table-name could not be updated.
  • Page 30 For clarification, see the accompanying error message. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 104 1104 Default value string is too long for column column-name.
  • Page 31 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1 1 1 1111 An error occurred while starting a transaction on object table-name.
  • Page 32 Specify a different schema and resubmit. SQL 1 1 19 1119 Dropping metadata object table-name is not allowed. is the name of an HP Neoview database metadata table. table-name Cause You attempted to use the DROP TABLE statement to drop a table that is part of the HP Neoview database metadata.
  • Page 33 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 127 1127 The specified table table-name is not a base table. Please verify that the correct table was specified.
  • Page 34 Effect HP Neoview database software is unable to perform the requested operation. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 130 1130 The column requires a default value.
  • Page 35 This is an internal error in the interface between utilities and the catalog manager. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 138 1138 An internal error occurred: invalid input parameter(s). Object name and status are required.
  • Page 36 SQL 1 141 1141 Label file-name for object could not be accessed. File system error error-number. is the HP Neoview platform file name of a partition of object. file-name is a Neoview platform file-system error. error-number Cause An ALTER TABLE or ALTER INDEX operation encountered a file-system error.
  • Page 37 SQL 1 145 1145 The catalog name catalog-name is reserved for SQL/MX metadata. is the name of an HP Neoview database catalog. catalog-name Cause The Neoview database software reserves certain catalog names for its own use.
  • Page 38 Cause The HP Neoview database software could not create the object because the requested table size is bigger than the total amount of disk space available on the cluster. Effect The SQL operation fails.
  • Page 39 Effect The operation fails. Recovery Correct the syntax so that the correct object name is used. SQL 1 156 1156 Synonym name does not exist or object type is invalid for the current operation. Cause You specified a create or alter of synonym name on an object that is not a table or view.
  • Page 40 1161 System generated column SYSKEY cannot be specified as part of the PARTITION BY clause. Cause The HP Neoview database software could not create the object because system-generated column SYSKEY is not allowed as part of the PARTITION BY clause. Effect The DDL operation fails.
  • Page 41 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 1 167 1167 Cannot change ownership of object name because authid is not the super id or service ID.
  • Page 42 An internal error was encountered. Effect The operation fails. Recovery Contact HP support to analyze the failure. SQL 1 178 1178 Internal error: unable to find catalog associated with uid uid. This catalog was created on create time and is being accessed by role role.
  • Page 43 Cause One or more LOCATION clauses in the CREATE or MODIFY statement contained an HP Neoview platform location whose subvolume did not match the designated subvolume for the schema in which the object was being created. Effect The object was not created.
  • Page 44 Change either the column data type or the value for the default to be compatible types and resubmit. SQL 1 187 1187 The schema name schema-name is reserved for SQL/MX metadata. is the name of an HP Neoview database schema. schema-name Cause The Neoview database software reserves certain schema names for its own use.
  • Page 45 Cause You specified a data type for this routine parameter that is not supported. Effect The HP Neoview database software is unable to complete the operation. Recovery Specify a different data type. SQL 1225 1225 Mixing EXECUTE privilege with other privileges is not allowed.
  • Page 46 For information about file-system errors, see Chapter 21 (page 385). SQL 1233 1233 Creating schema in SQL/MX system catalog catalog-name is prohibited. is the name of the HP Neoview database catalog. catalog-name Cause You attempted to create a schema in the system catalog. Effect The operation fails.
  • Page 47 Cause You specified a literal with a character set other than ISO88591 in the text of a create view statement. Effect The operation fails. Recovery Specify only ISO88591 literals in the command. SQL 1240 1240 The character set for a PARTITION KEY column must be ISO88591. Cause You specified a literal with a character set other than ISO88591 as a partition key.
  • Page 48 is the column of object-name that corresponds to the invalid key value. column-name is the name of the affected object. object-name Cause A utility command specified a key value that is inconsistent with the data type of the column that corresponds to the key value. Effect The operation fails.
  • Page 49 An unanticipated error occurred during a CREATE PROCEDURE operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1262 1262 The command cannot be executed because operation is in progress for schema.
  • Page 50 1270 ALLOCATE or DEALLOCATE failed for object sql object-name due to file error file-system error-number on filename. is the ANSI name of the affected SQL database object. sql object-name is an HP Neoview platform file-system error code. file-system error-number Cause A CREATE or ALTER operation encountered a file-system error error-number during processing of the ALLOCATE or DEALLOCATE attribute.
  • Page 51 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1273 1273 The specified MAXEXTENTS value must be greater than the number of extents allocated.
  • Page 52 SQL object (table or index). object-name Cause The HP Neoview database does not recognize the partitioning scheme stored in the metadata for the named object. Effect The named object is considered corrupt and is inaccessible.
  • Page 53 SQL 1284 1284 Table table-name cannot be dropped because it was specified to be NOT DROPPABLE. is the name of an HP Neoview database table. table-name Cause An attempt was made to drop a table that is not droppable. Effect The operation fails.
  • Page 54 SQL 1304 1304 SQL/MX could not obtain the location of the system schema tables. Cause The HP Neoview platform location of the system schema tables could not be obtained from the anchor file. Effect The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure.
  • Page 55 Cause In a CREATE SCHEMA command, you did not specify a LOCATION clause, so the HP Neoview database software was unable to generate a schema subvolume name that is not already being used by existing schemas. Effect The operation fails.
  • Page 56 The create privilege for the catalog has been disabled. Effect The operation fails. Recovery Contact HP services to reinstate the create operation. SQL 1315 1315 Catalog name does not have an associated definition schema. The ALTER CATALOG operation fails is the name of the catalog.
  • Page 57 CAT_REFERENCES system schema table. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1501 1501 The OBJECTS - MP_PARTITIONS definition schema relationship for type object may be corrupt.
  • Page 58 REPLICAS definition schema table. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1503 1503 The OBJECTS - PARTITIONS definition schema relationship for type object may be corrupt.
  • Page 59 An unsupported data type has been specified for the IDENTITY column. Effect The statement fails. Recovery Specify a data type that the HP Neoview database supports for IDENTITY columns, and resubmit the statement. SQL 151 1 1511 There can only be one IDENTITY column for a table.
  • Page 60 Cause The index required by the constraint is disabled, so the constraint cannot be enabled. Effect The operation failed. Recovery Populate index and retry the request. SQL 1519 1519 Constraint constraint on table table cannot be disabled because it is a foreign key constraint. is the name of the constraint.
  • Page 61 SQL 1572 1572 The seq-gen-option value cannot be a negative number for identity-col-name. is the name of the sequence generator option. seq-gen-option is the name of the identity column. identity-col-name Cause You specified a negative value for the sequence generator option. Effect The statement fails.
  • Page 62 Effect The statement fails. Recovery Specify a value for the sequence generator option that is not greater than the maximum value that is allowed for the data type, and resubmit the statement. Note If the data type is a LARGEINT, the SQL 1576 message does not contain the column name.
  • Page 63 Effect The statement fails. Recovery Specify either the MAXVALUE or INCREMENT BY sequence generator option to be altered for the IDENTITY column. SQL 1594 1594 An error occurred trying to access the current value of the IDENTITY column col-name. is the name of the IDENTITY column. col-name Cause An internal error occurred when the platform tried to access the current value of the...
  • Page 64 If the IDENTITY column's default specification type is GENERATED ALWAYS AS IDENTITY, recalibrate the CURRENT_VALUE of the internal sequence generator by using the ALTER TABLE ALTER COLUMN SET INCREMENT BY statement and manual calibration instructions. SQL 1598 1598 The new CURRENT_VALUE, current-value, for the IDENTITY column, column-name, for the table, table-name, will be greater than the maximum allowed, maximum-value.
  • Page 65 Recovery Correct the recalibration value and resubmit the statement. SQL 1600 1600 Unable to lock table, table-name, for the IDENTITY column, column-name, during recalibration. is the name of the table that contains the IDENTITY column. table-name is the name of the IDENTITY column. column-name Cause The table containing the IDENTITY column could not be locked in SHARED MODE...

  • Page 67: Neoview Compiler Messages (2000 Through 2999)

    DEFAULTS table name. name is the default values file. values Cause The HP Neoview database software was unable to open system defaults table name because of error number. Effect The Neoview database software uses either another file or values instead. Recovery Do not attempt recovery.
  • Page 68 Cause The HP Neoview database software received an internal error in file name at line number. More information is in detail text. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 69 Cause The HP Neoview database software was unable to create server process name because of the process control procedure error number it received. More information appears in detail text. Effect The operation fails.
  • Page 70 SQL 2016 2016 Server process name was started but had undefined externals. is the server process name. name Cause The HP Neoview database software started server process name, but it had undefined externals. Effect None. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 71 Cause The HP Neoview database software was unable to create server process name because it is an unlicensed privileged program. The server process was configured incorrectly at installation. Effect The operation fails. Recovery The server process must be a licensed privileged program. Check your configuration.
  • Page 72 2028 OSS server process name could not be created on node - insufficient resources. is the server process name. name Cause The HP Neoview database software was unable to create the OSS server process name because there is not enough memory to create this process. Effect The operation fails. Recovery Do not attempt recovery.
  • Page 73 Cause The HP Neoview database process id was unable to open server process name because of the operating system error number it received. Effect The operation fails. Recovery Use the operating system error to diagnose and correct the problem.
  • Page 74 DEFAULT setting, but the attribute name you specified is not valid. If the SQLSTATE is 01000, this is a warning. In an earlier HP Neoview database session, you inserted a row into a DEFAULTS table whose attribute column value is invalid.
  • Page 75 This additional information will also be helpful: the DDL for the tables involved, the query that produced this warning, and any CONTROL QUERY SHAPE and CONTROL QUERY DEFAULT settings in effect when the error occurred. SQL 2054 2054 HIST_NO_STATS_ROWCOUNT should always be greater than or equal to CQD HIST_NO_STATS_UEC.
  • Page 76 Cause You defined the static cursor name twice in this module. Effect The HP Neoview database software uses the first static cursor definition. Recovery This is an informational message only; no corrective action is needed. SQL 2062 2062 Static cursor name has already been defined in this module. The previous definition, as a dynamic cursor, is being retained and this latest one ignored.
  • Page 77 2065 Statement name was not found in module name. is the statement name. name is the module name. name Cause The HP Neoview database software could not find statement name in module name. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 2066 2066 Cursor cursor-name was not found in module module-name.
  • Page 78 In a module definition file, you specified a query statement such as SELECT, INSERT, UPDATE, DELETE, or a DDL statement. These statements must be embedded in procedures. Effect The HP Neoview database software is unable to compile the module. Recovery Correct the syntax and resubmit.
  • Page 79 Effect The operation fails. Recovery Recompile the module definition file, using the HP Neoview compiler, to create a valid module file. SQL 2081 2081 Error number while opening file name for read. is the error number.
  • Page 80 Cause A compilation failed, and for some reason HP Neoview database software was not able to purge the module file. Effect The module file is not valid and should not be used.
  • Page 81 SQL 2097 2097 Source file name is over 1024 characters long. Cause The HP Neoview compiler was invoked on a module definition file that contains a SOURCE_FILE statement whose source path name has over 1024 characters. Effect The operation fails.
  • Page 82 2102 This query could not be compiled with 'MINIMUM' optimization level. Suggestion: Retry with 'MEDIUM' optimization level. Cause The HP Neoview database software was unable to compile this query using the MINIMUM optimization level. Effect The Neoview database software is unable to process this query.
  • Page 83 2106 This statement could not be compiled since it is too long. Break up large statements into smaller pieces. Cause The HP Neoview database software was unable to compile this query because it is too long. Effect The Neoview database software is unable to process this query.
  • Page 84 2201 SQL compilation return code is mxcmp non-zero exit code. Cause You invoked mxCompileUserModule on an application file that has an embedded module definition. An SQL compilation of an embedded module definition resulted in an HP Neoview compiler nonzero exit code, indicating a warning or error. Effect The operation fails.
  • Page 85 Cause You invoked mxCompileUserModule on an application file that is not an HP Neoview platform ELF object file. Effect The operation fails. Recovery Verify that the name application file is an ELF object file. Verify that the name of application file is spelled correctly, and retry the command.
  • Page 86 Cause You invoked mxCompileUserModule without supplying an application file. Effect The operation fails. Recovery Invoke mxCompileUserModule on an application file, such as an HP Neoview platform ELF object file. SQL 2209 2209 string is not a valid delimited identifier. 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.
  • Page 87 An internal error occurred during the operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 2215 2215 identifier is not a valid regular identifier.
  • Page 88 SQL 2222 2222 SQL module module name was not found in application file name. is the requested module name. module name is the requested application file. application file name Cause You invoked mxCompileUserModule on an application file with a list of module names to SQL compile.

  • Page 89: Parser And Compilation Messages (3000 Through 3999)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 3001 3001 Syntax error at or before SQL text. Cause There is a syntax error near the text SQL text.
  • Page 90 Cause You specified character set name that is not supported for use in an HP Neoview database software object, such as a table or module. Examples include creating a KANJI or KSC5601 column in a Neoview database software table.
  • Page 91 Redefine the item with a precision value of 18 or less. SQL 3015 3015 Scale value cannot exceed precision value. Cause You defined a scale value with greater precision than the HP Neoview database software allows. Effect The operation fails.
  • Page 92 SQL 3018 3018 An unsigned smallint was expected, not value. Cause You specified an unexpected value, value. The HP Neoview database software requires an unsigned smallint. Effect The operation fails. Recovery Replace the value with an unsigned smallint and resubmit.
  • Page 93 3027 name is not a valid simple name; it has more than one name part. Cause You specified an invalid name name, which must have only one name part. Effect The HP Neoview database software could not prepare the statement. Recovery Correct the name and resubmit. SQL 3028 3028 Specifying a privilege column list in the INSERT clause is not yet supported.
  • Page 94 SQL 3031 3031 CASCADE drop behavior is not yet supported. Cause You attempted to drop an object with the CASCADE option, which is not supported. Effect The operation fails. Recovery Drop the item without CASCADE. SQL 3032 3032 The COLUMN clause in the ALTER TABLE statement is not yet supported. Cause You used the COLUMN clause in the ALTER TABLE statement, which is not supported.
  • Page 95 SQL 3038 3038 PIC X types cannot have leading signs, or any signs at all. 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. SQL 3039 3039 PIC X types do not have any COMP representation.
  • Page 96 SQL 3045 3045 The date value is not valid. Cause You specified an invalid date value. Effect The operation fails. Recovery Change the date value and resubmit. SQL 3046 3046 The time value is not valid. Cause You specified an invalid time value. Effect The operation fails.
  • Page 97 SQL 3052 3052 Duplicate NOT NULL clauses were specified in column definition name. Cause You defined column name with more than one NOT NULL clause. Effect The operation fails. Recovery Define the column with only one NOT NULL clause and resubmit. SQL 3053 3053 Duplicate PRIMARY KEY clauses were specified in column definition name.
  • Page 98 You defined a primary key as droppable in a table that includes STORE BY PRIMARY KEY in its definition, which is not supported. Effect The HP Neoview database software is unable to process this definition. Recovery Change the definition of the primary key constraint so that it is NOT DROPPABLE.
  • Page 99 You specified an ALTER INDEX statement with both an ALLOCATE and a DEALLOCATE clause, which is not supported. Effect The HP Neoview database software ignores the ALTER INDEX statement. Recovery Correct the ALTER INDEX statement to include either ALLOCATE or DEALLOCATE.
  • Page 100 SQL 3074 3074 The SEPARATE BY clause is not supported. Cause You specified the SEPARATE BY clause, which is not supported. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3075 3075 The [NO]COMPRESS clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement.
  • Page 101 Recovery Correct the syntax and resubmit. SQL 3081 3081 Duplicate ALLOCATE clauses were specified. Cause You specified duplicate ALLOCATE clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3082 3082 Duplicate [NO]AUDIT clauses were specified. Cause You specified duplicate [NO]AUDIT clauses. Effect The operation fails.
  • Page 102 Cause You specified a CREATE INDEX statement with the [NO]AUDIT clause, which is not supported. Effect The HP Neoview database software ignores the CREATE INDEX statement. Recovery Correct the syntax and resubmit. SQL 3092 3092 Duplicate BLOCKSIZE clauses were specified.
  • Page 103 Cause You specified a CREATE INDEX statement that includes the DEALLOCATE clause, which is not supported. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3095 3095 Duplicate [NO]ICOMPRESS clauses were specified. Cause You specified a statement with duplicate [NO]ICOMPRESS clauses. Effect The operation fails.
  • Page 104 Recovery Correct the syntax and resubmit. SQL 3102 3102 Duplicate PARALLEL EXECUTION clauses were specified. Cause You specified a statement with duplicate PARALLEL EXECUTION clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 3103 3103 Duplicate PARTITION clauses were specified. Cause You specified a statement with duplicate PARTITION clauses.
  • Page 105 Effect The operation fails. Recovery Correct the statement to include one of these clauses. SQL 3109 3109 Duplicate STORE BY clauses were specified. Cause You specified a statement with duplicate STORE BY clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 31 10 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement.
  • Page 106 SQL 31 15 3115 Duplicate ISOLATION LEVEL clauses were specified. Cause You specified a statement with duplicate ISOLATION LEVEL clauses. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 31 16 3116 Duplicate transaction access mode clauses were specified. Cause You specified a statement with duplicate access mode clauses.
  • Page 107 The operation fails. Recovery Correct the syntax and resubmit. SQL 3131 3131 The statement just entered is currently not supported. Cause You specified a statement that is not supported by the HP Neoview database software. Effect The operation fails. Recovery None.
  • Page 108 SQL 3132 3132 The HEADING for column name exceeds the maximum size of 128 characters. is the name of the column. name Cause You specified a heading for column name that exceeds the maximum size of 128 characters. Effect The operation fails. Recovery Correct the syntax and resubmit.
  • Page 109 SQL 3145 3145 Positioned UPDATE or DELETE is allowed only in embedded SQL. Cause You attempted to perform a positioned UPDATE or DELETE, which is supported only in embedded the HP Neoview database software. Effect The operation fails. Recovery Correct the syntax and resubmit.
  • Page 110 Release, not Debug. Actual query results will likely not match expected results. is the environment variable value specified. value Cause The HP Neoview database software is ignoring the environment variable you specified. Query results might not match expected results. Effect None. Recovery Informational message only;...
  • Page 111 Recovery Correct the syntax and resubmit. SQL 3155 3155 The POPULATE and NO POPULATE clauses cannot coexist in the same CREATE INDEX statement. Cause You specified a CREATE INDEX statement using both the POPULATE or NO POPULATE clauses, which is not supported. Effect The operation fails.
  • Page 112 SQL 3162 3162 Procedure parameter name was not used. is the name of the procedure parameter. name Cause The HP Neoview database software did not use procedure parameter name. Effect None. Recovery Informational message only; no corrective action is needed.
  • Page 113 Recovery Correct the syntax and resubmit. SQL 3175 3175 Dynamic SQL statements are not allowed in compound statements. Cause You specified a compound statement that contains dynamic HP Neoview database software statements. Effect The operation fails. Recovery Correct the syntax and resubmit.
  • Page 114 3178 One or more of the following external (host-language) data types incorrectly appears within the SQL query or operation: name. Cause You specified an HP Neoview database software query or attempted to perform an operation with an incorrect data type. Effect The operation fails.
  • Page 115 3186 string: Dynamic parameters and host variables are currently not allowed in DDL. is the dynamic parameter or host variable that was specified. string Cause The HP Neoview database software does not support the use of dynamic parameters or host variables in DDL statements. Effect The operation fails. Recovery Remove occurrences of dynamic parameters or host variables and resubmit.
  • Page 116 3192 Union operands table1 and table2 have different access/lock modes. Cause The HP Neoview database software attempted to compile a UNION query that has an access/lock mode that can be applied to both branches of the access/lock mode or only to the second branch of the UNION.
  • Page 117 Cause In the CREATE PROCEDURE statement, the EXTERNAL NAME clause you specified does not conform to the required syntax. Effect The HP Neoview database software is unable to create the procedure. Recovery Correct the syntax and resubmit. SQL 3205 3205 EXTERNAL NAME clause is required.
  • Page 118 SQL 3206 3206 The name for an object of this type must be fully qualified, or set NAMETYPE ANSI. Cause In the CREATE PROCEDURE statement, you specified a partially qualified name when NAMETYPE was not set to ANSI. Effect The operation fails. Recovery Set NAMETYPE ANSI or fully qualify the name.
  • Page 119 SQL 3212 3212 Minimum length of LONG VARBINARY is value. Cause You attempted a CREATE TABLE table name (columnname long varbinary(N)) where N < current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect The operation fails. Recovery Increase the CREATE TABLE statement’s long varbinary column width N or decrease the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit.
  • Page 120 SQL/MX object. specifies the ANSI name of a table, view, or ALIAS. object-name Cause SHOWDDL was given the display option with an HP Neoview database software table given as an argument. Effect SHOWDDL does not display output.
  • Page 121 HP Neoview database software location-name object. Cause SHOWLABEL supports only the physical names of data forks of the HP Neoview database software objects (physical location names that end in “00”). SHOWLABEL does not support resource forks. Effect SHOWLABEL does not display output.
  • Page 122 is the name of a dependent object of the target table, such as an index, dependent-object after trigger, materialized view, or referential integrity constraint. Cause An INSERT, UPDATE, or DELETE operation into a table with dependent objects was attempted when the NO ROLLBACK transaction setting is ON. Effect Compilation of the statement fails.
  • Page 123 SQL 3237 3237 Duplicate NO ROLLBACK clauses were specified. Cause Duplicate NO ROLLBACK clauses were specified in a SET TRANSACTION statement. Effect SET TRANSACTION statement fails, and the existing transaction state remains unaffected. Recovery Remove the duplicate NO ROLLBACK clause and issue the SET TRANSACTION statement again.
  • Page 124 3401 Hexadecimal representation of string literals associated with character set name is not supported. Cause You used a hexadecimal format to represent a character string that is not supported by the HP Neoview database software. Effect The operation fails. Recovery Do not use a hexadecimal format for the character set you specified.
  • Page 125 Cause The DDL statement coded in unicode contains non-ISO88591 characters. The HP Neoview database software does not support arbitrary unicode characters. Effect The operation fails. Recovery Remove non-ISO88591 characters and resubmit. SQL 3409 3409 Declaring a cursor on an embedded INSERT statement is not yet supported.
  • Page 126 Recovery Specify values for all the tuples in the list, or specify DEFAULT for all the tuples in the list. SQL 3415 3415 The first operand of function name is not valid. is the name of the function. name Cause The first operand you supplied for function name is not an allowed value.
  • Page 127 Effect The operation fails. Recovery Retry the query and use a valid disk pool number. The disk pool number must be greater than 0 and less than or equal to the number of disk pools set through the DDL. Alternatively, to pick a random disk pool, ignore the DISK POOL clause so that the table will be placed on a random disk pool.
  • Page 128 SQL 3425 3425 Embedded embedded-operation expression is not supported with Long Running Updates. is an embedded INSERT, UPDATE or DELETE. statement. embedded-operation Cause A MULTI COMMIT option has been specified on an embedded statement. Effect The statement fails to execute and the transaction options do not take affect. Recovery Use MULTI COMMIT ON only with non-embedded DELETE statement.
  • Page 129 Recovery Supply the input values for the IDENTITY column.

  • Page 131: Binder And Compilation Messages (4000 Through 4999)

    5 Binder and Compilation Messages (4000 Through 4999) SQL 4000 4000 Internal error in the query binder. Cause The HP Neoview database software received an internal error in the query binder. Effect The Neoview database software is unable to process this query. Recovery Do not attempt recovery.
  • Page 132 If a column is part of a JOIN operation, you no longer qualify its name with its original table name2. Effect The operation fails. Recovery Correct the syntax and resubmit. If the column is part of a JOIN, remove the table qualifier and use only the column name.
  • Page 133 Cause You referred to column name using the SELECT * or SELECT TBL.* reference, and the HP Neoview database software could not locate the column because the reference is ambiguous. Effect The operation fails.
  • Page 134 SQL 4016 4016 The number of derived columns (value1) must equal the degree of the derived table (value2). Cause You specified a statement in which the number of derived columns (value1) does not equal the degree of the derived table (value2). They must be equal. Effect The operation fails.
  • Page 135 4025 Error while preparing constraint name on table table name. is the name of the table. table name Cause The HP Neoview database software received an error while preparing constraint name on table name. See accompanying error messages. Effect The operation fails.
  • Page 136 SQL 4028 4028 Table or view name is not updatable. Cause You attempted to update table name, which is not updatable. Effect The operation fails. Recovery None. SQL 4030 4030 Column name has an invalid combination of datetime fields (internal field number, internal field number, internal field number).
  • Page 137 Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4036 4036 The source field of the EXTRACT function must be of DateTime or Interval type. Cause You specified a source field of the EXTRACT function that is not a DATETIME or INTERVAL data type.
  • Page 138 SQL 4042 4042 The operands of a comparison predicate must be of equal degree. Cause You specified a comparison predicate with operands that are not of equal degree, which is required. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4043 4043 The operand of function name must be character.
  • Page 139 The status of the corresponding MAINTAIN command task could not be determined and was not executed. The MAINTAIN task is considered to be disabled. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 140 SQL 4055 4055 The select lists or tuples must have comparable data types. type1 and type2 are not comparable. Cause You specified select lists or tuples with incompatible data types. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4056 4056 Exposed name name appears more than once.
  • Page 141 SQL 4062 4062 The preceding error actually occurred in function name. Cause The HP Neoview database software detected an error in function name. Errors that appear before this one refer to the low level computations that this function uses. Effect The operation fails.
  • Page 142 SQL 4069 4069 Column name uses an unsupported collation. Cause You specified a column name that uses an unsupported collation. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4070 4070 The operand of function name must be exact numeric. Cause You specified an invalid operand for function name.
  • Page 143 You attempted to perform an action on a object name that is corrupt. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 4085 4085 File organization name1 of object name2 is not supported.
  • Page 144 4094 The number of output host variables (value1) must equal the number of selected values (value2). Cause The HP Neoview database software requires that the number of output host variables, value1, match the number of selected values, value2. Effect The operation fails.
  • Page 145 4101 If name is intended to be a further table reference in the FROM clause, the preceding join search condition must be enclosed in parentheses. Cause A syntax error has caused the HP Neoview database software to treat object name as an ambiguous entity. Effect The operation fails.
  • Page 146 Replace the double quotes with single quotes. SQL 4105 4105 Translation name is not recognized. Cause The HP Neoview database software does not recognize the translation name. Effect The Neoview database software is unable to compile the statement. Recovery Use one of the supported translation names.
  • Page 147 SQL 4108 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function. Cause A ROWS SINCE function in your statement contained another sequence function that, in turn, contained an invalid reference to the THIS function. Inside ROWS SINCE, the THIS function must not appear inside any other sequence function.
  • Page 148 Cause You attempted to perform absolute and relative sampling in the same balance expression, which is not supported. Effect The HP Neoview database software is unable to prepare the query. Recovery Correct the syntax and resubmit. SQL 41 13 4113 The sample size for type Sampling must be size type.
  • Page 149 Effect The operation fails. Recovery An updatable cursor query should not specify a join or a nonupdatable query. An HP Neoview database software statement cursor is updatable if all the following are true: • It is a SELECT statement. •...
  • Page 150 HP Neoview database software was unable to compile a parallel extract producer query because the number of requested streams was either too low or too high. The number of streams must be greater than 1 and cannot exceed the number of HP Neoview processing nodes.
  • Page 151 4124 More than one table will be locked: name. is the name of the table. name Cause The HP Neoview database software is preparing to lock more than one table. Effect None. Recovery Informational message only; no corrective action is needed.
  • Page 152 Ensure that the type of the source and trim character is CHARACTER. SQL 4134 4134 The operation (name) is not allowed. Try UNION ALL instead. Cause You attempted to perform an operation that the HP Neoview database software does not allow. Effect The operation fails.
  • Page 153 Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the WHERE clause to use the primary key of the table expression.
  • Page 154 You attempted to compile an embedded DELETE or embedded UPDATE expression using an ORDER BY without using a clustering key or a secondary index. Effect The HP Neoview database software is unable to compile the statement. Recovery Create a secondary index materializing the order and resubmit.
  • Page 155 Cause You attempted to perform a GROUP BY in conjunction with a stream expression. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4163 4163 GROUP BY is not supported for embedded name1 expression. Tables in scope: name2.
  • Page 156 SQL 4174 4174 JOIN_ORDER_BY_USER prevented compiler from reordering query tree. Cause The HP Neoview database software compiler could not reorder the join tree because the JOIN_ORDER_BY_USER directive is in effect. Effect The Neoview database software is unable to compile the statement.
  • Page 157 Tables in scope: name3. Cause You attempted to perform a join between two embedded expressions. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4176 4176 Join between stream expression and embedded name1 expression is not supported.
  • Page 158 Recovery Modify the statement and resubmit. SQL 4184 4184 Columns that are part of a referential constraint cannot be updated using embedded UPDATE statements. Cause You attempted to perform an embedded UPDATE statement on columns that are part of a referential constraint. Effect The operation fails.
  • Page 159 4200 Stream expressions are not supported for compound statements. Cause You attempted to use a stream expression for a compound statement. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4201 4201 Embedded operation expression is not supported for compound statements.
  • Page 160 4202 SEQUENCE BY is not supported for embedded name expressions. Cause You attempted to perform an embedded expression that included SEQUENCE BY. Effect The HP Neoview database software is unable to compile the statement. Recovery Modify the statement and resubmit. SQL 4203 4203 Insert/Update/Delete operation on non-audited table name requires index maintenance which may cause the index(es) to become corrupt.
  • Page 161 You attempted to use an index for stream access that does not cover all output columns of the base table. Effect The HP Neoview database software is unable to compile the statement. Recovery Restrict the select list or add the missing columns to the index.
  • Page 162 4302 Procedure procedure-name expects value1 parameters but was called with value2 parameters. Cause In the HP Neoview database software statement being compiled, a stored procedure invocation contains an incorrect number of parameters. Effect The Neoview database software statement is not compiled.
  • Page 163 4308 Internal error: Unsupported SQL data type value specified for a CALL statement parameter. Cause In the HP Neoview database software statement being compiled, a parameter in a stored procedure invocation had an unsupported SQL data type. Effect The Neoview database software statement is not compiled.
  • Page 164 Effect The operation fails. Recovery Correct the query and retry the request. SQL 4313 4313 Function rand()is not supported. Cause You attempted to use the random function, which is not supported. Effect The operation fails. Recovery Correct the syntax and resubmit. SQL 4320 4320 Stream access not allowed on multi-partitioned table, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set to OFF.
  • Page 165 4336 Embedded operation statements are not allowed in a join operation. Table in scope: table-names. is an INSERT operation. operation are the names of HP Neoview database tables that are in scope. table-names Cause You attempted a join operation using an embedded INSERT statement.
  • Page 166 SQL 4342 4342 The specified window frame clause is not valid. Cause The window frame clause specified was not valid. Effect The operation fails. Recovery Rewrite the query and use a valid window frame clause. SQL 4343 4343 A Window Frame Clause cannot contain a FOLLOWING term, either explicitly or implicitly.
  • Page 167 Cause A MIN/MAX window function that has UNBOUNDED FOLLOWING in its frame clause is used in the same query with RANK, DENSE_RANK, ROW_NUMBER or other MIN/MAX window functions that have UNBOUNDED PRECEDING in their frame clause on one end of the window frame and bounded PRECEDING or FOLLOWING on the other end. Effect The operation fails.
  • Page 168 Cause Multiple RANK functions with different expressions were specified. Effect The statement fails. Recovery Rewrite the query so that it does not contain multiple RANK functions with different expressions. SQL 4362 4362 Using ASC/DESC with sequence functions is not supported. Cause ASC/DESC was specified in the expression of the RANK sequence function.
  • Page 169 Recovery Rewrite the query so that it does not contain the RANK non-sequence function and sequence functions in the same scope. SQL 4368 4368 Nesting rank functions is not supported. Cause The query contains nested RANK functions. Effect The statement fails to prepare. Recovery Rewrite the query so that it does not contain nested RANK functions.
  • Page 170 Cause The compiler was attempting to end a transaction. The compiler, executor and TMF transaction identifiers did not match. Effect The operation fails. Recovery The transaction IDs can be used to help determine how the transaction was started and why the transaction identifiers didn't match. Binder and Compilation Messages (4000 Through 4999)

  • Page 171: Normalizer Messages (5000 Through 5999)

    5000 Internal error in the query normalizer. Cause The optimizer received an internal error during query normalization. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.

  • Page 173: Optimizer Messages (6000 Through 6999)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 6001 6001 DISTINCT aggregates can be computed for only one column per table expression.
  • Page 174 HP Neoview database table to which the columns belong. table-name is the operator that was being processed when the warning was issued. op-name Cause Statistics for the set of columns was not generated.
  • Page 175 STATISTICS FOR TABLE table-name ON NECESSARY COLUMNS. is a list of column names of the affected columns. column-list is the name of the HP Neoview database table to which the columns belong. table-name is the operator that was being processed when the warning was issued.
  • Page 176 HP Neoview database table to which the column belongs. table-name Cause Statistics for the Column were not generated.
  • Page 177 Recovery If the Error code is 0, no action is required by the User. If the Error code is 33 or 35, Users should refer to Chapter 21 (page 385) for information about recovering from file-system error codes 33 and 35.

  • Page 179: Generator Messages (7000 Through 7999)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 7001 7001 Default value value is not valid for column name.
  • Page 180 SQL 71 1 1 7111 Expecting return or “;”. Cause The command did not include a delimiting carriage return or semicolon (;) where TMFCOM expected one. Effect The command fails. Recovery Check the syntax rules for the command and reenter it accordingly. SQL 71 12 7112 Expecting “(”.
  • Page 181 Cause The command (DUMP FILES, INFO DUMPS, or RECOVER FILES) was entered without specifying an ANSI Name keyword. Effect The command fails. The same error is returned if you do not specify anything after the first single quote. Recovery Check the syntax rules for the command and then reenter the command, specifying a valid ANSI Name keyword.
  • Page 182 Effect The compiler reports the problem and exits. Recovery None. Contact HP Support. SQL 7352 7352 A Hash-Join that may overflow its memory to disk can not accept input rows longer than 57344 bytes. Cause The length of inner or outer input rows to a hash-join operator exceeded the overflow buffer size, which is 57344 bytes by default.
  • Page 183 Recovery Rewrite your query to prevent the join from overflowing its memory to disk. Contact HP Support for assistance.

  • Page 185: Executor Messages (8000 Through 8999)

    The HP Neoview database software has received an internal error. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8002 8002 The current nowaited operation is not complete.
  • Page 186 You specified an invalid catalog name. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8009 8009 Schema name name is not valid.
  • Page 187 Effect None. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8015 8015 Aborting transaction because a compound statement performed an update operation followed by a SELECT statement that did not return any row.
  • Page 188 is the time limit of the processor in seconds. is the disk process where the problem was detected. Cause The CPU time accumulated in an SQL disk process exceeded the limit n1 for which the query is configured. This problem was detected in disk process pp. Effect The operation fails.
  • Page 189 You attempted to reference a define that does not exist. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8101 8101 The operation is prevented by check constraint name1 on table name2.
  • Page 190 Effect The UPDATE/DELETE WHERE CURRENT statement is invalid. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8107 8107 Self-referencing INSERT statement without blocking operator is not allowed with AUTOCOMMIT OFF.
  • Page 191 The named anchor file contains invalid data. Effect The HP Neoview database software uses data from the anchor file to locate the system schema tables on a node. Without a valid anchor file, it is not possible to compile or execute queries that use Neoview database metadata on the anchor file’s segment.
  • Page 192 MP table name DEFINE should be MAP, not SORT. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8401 8401 A row subquery or SELECT...INTO statement cannot return more than one row.
  • Page 193 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8405 8405 The operand of function CONVERTTIMESTAMP is out of range.
  • Page 194 You specified an input character host variable that is missing its null terminator. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8413 8413 The string argument contains characters that cannot be converted.
  • Page 195 You attempted to perform the USER function, which is not supported on this platform. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8419 8419 An arithmetic expression attempted a division by zero.
  • Page 196 Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8425 8425 NULL cannot be assigned to a DEFAULT NULL NOT NULL column. Cause You attempted to assign a null value to a column that is defined as NOT NULL.
  • Page 197 8555 An internal error occurred in the SQL/MX executor in the disk process. Cause An HP Neoview database procedure in the disk process detected an internal error. Effect The operation fails. An Event Management Services (EMS) event message for event number 5127 from the Disk subsystem has been generated to supply further diagnostic information.
  • Page 198 While you had table name open, another operation such as a DDL operation changed that table. Effect The table is no longer open. You will see this message if the HP Neoview database software was unable to recompile your statement. Recovery Do not attempt recovery.
  • Page 199 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 8595 8595 Key values specified in the INSERT part of a MERGE statement must be the same as those specified in the ON clause.
  • Page 200 The file system received an error while locking or unlocking. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8602 8602 The file system reported error number on a lock/unlock operation.
  • Page 201 Cause Transaction subsystem name has returned error number while starting a transaction. Effect The operation fails. Recovery Contact the GMCSC. SQL 8605 8605 Committing a transaction which has not started. Cause You attempted to commit a transaction that has not been started. Effect The operation fails.
  • Page 202 8613 SQL cannot commit or rollback a transaction that was started by application. Cause An application started a transaction outside of the HP Neoview database software that the Neoview database software could not commit or rollback. Effect The operation fails.
  • Page 203 Effect The operation may fail or succeed. Recovery Recreate the target table with the same definition as the source table. SQL 8652 8652 Version($0~int0) of source($0~string0) must be the same as the version($1~int1) of target($1~string1). is the version of the source object. $0~int0 is the source object name.
  • Page 204 Recovery Cleanup the environment and retry the query. SQL 8657 8657 Could not recover the specified object. Reason: $0~string0 is the reason why replicate could not recover the object. $0~string0 Cause See the reason, $0~string0, to determine the cause. Effect The operation fails.
  • Page 205 The source contains a character that cannot be translated to the target. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8700 8700 An assertion failure or out-of-memory condition occurred during parallel execution.
  • Page 206 Cause The HP Measure utility encountered an error while attempting to update HP Neoview database counters. Effect Measure fails to update the database counters. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 207 Effect The Neoview database software could not execute the file. Recovery Recompile the .mdf file, using the HP Neoview compiler, to create a valid module file. SQL 8809 8809 Open of the module file name failed with error number.
  • Page 208 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8814 8814 The transaction mode at run time (value) differs from that specified at compile time (value).
  • Page 209 Recovery Use the errors that accompany this one to diagnose and correct the problem. SQL 8828 8828 Out-of-memory condition occurred while creating the name. Cause The HP Neoview database software ran out of memory while creating the internal structure name.
  • Page 210 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8829 8829 Trying to set descriptor item for an entry that is either invalid or greater than the maximum entry count for that descriptor.
  • Page 211 8838 Unable to receive reply from MXCMP, possibly caused by internal errors when compiling SQL statements, processing DDL statements, or executing the builtin stored procedures. Cause The HP Neoview database software did not receive a reply it expected from MXCMP. Effect The operation fails. Recovery Do not attempt recovery.
  • Page 212 SQL. This transaction needs to be committed or aborted by calling SQL COMMIT or ROLLBACK WORK. Cause The HP Neoview database software started a transaction that was committed or aborted by an embedded program, rather than by the Neoview database software. Effect The operation fails.
  • Page 213 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8852 8852 Holdable cursors are supported for only streaming cursors and embedded update/delete cursors.
  • Page 214 You attempted to reference an invalid SQL identifier, displayed in the message. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8859 8859 There are pending insert, delete, or update operations.
  • Page 215 SQL 8867 8867 An error while reading from file name. is the file name. name Cause The HP Neoview database software encountered an error while reading the module file name. Effect The operation fails. Recovery Rebuild the module file and resubmit.
  • Page 216 SQL 8872 8872 New operations cannot be executed while another NOWAIT operation is pending. Cause Only one nowait operation at a time is allowed on an HP Neoview SQL statement. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 217 SQL 8882 8882 Containing SQL is not permitted. Cause A stored procedure registered with the NO SQL attribute attempted to access the HP Neoview database software. Effect The corresponding SQL request is rejected.
  • Page 218 Cause A value that was passed into an HP Neoview database CLI function containing a reserved parameter was not the value expected by the database software. Effect The CLI function fails.
  • Page 219 Effect The SET DESCRIPTOR fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 8896 8896 The character set name1 of a host variable does not match name2 of the corresponding descriptor item (entry number).
  • Page 220 SQL/MX. Cause During execution of an HP Neoview SQL statement, the Neoview database executor received a message from the Neoview database UDR server that was unreadable in some way. Either the message was corrupted by the Neoview database UDR server, or an internal error occurred within the Neoview database executor.
  • Page 221 8912 The request to allocate a stored procedure result set failed. An unexpected internal error was encountered. Cause An internal error was detected within the HP Neoview SQL executor during allocation of a stored procedure result set. Effect The operation fails.
  • Page 222 SQL 8916 8916 The request to allocate a stored procedure result set at position index failed because the position is out of range. Valid positions range from one up to the maximum number of result sets that can be returned from the specified CALL statement, which in this case is max-result-sets.
  • Page 223 Timeout period specified is number seconds. Cause The DISPLAY STATISTICS FOR CPU or PID or QID command timed out because the HP Neoview database software is unable to obtain the statistics from runtime statistics (RTS) components within the specified time-out period. Effect The runtime statistics information is not retrieved, and the command fails.
  • Page 224 SQL 8935 8935 The sequence generator update failed, see additional diagnostics for failure details. Cause The update to the internal sequence generator failed. Effect The statement fails. Recovery Additional error codes are returned for the update failure. Proceed with the recovery procedures recommended by the additional error codes.

  • Page 225: Update Statistics Messages (9200 Through 9218)

    Cause UPDATE STATISTICS encountered an error during a DROP of the object name. Effect The HP Neoview database software is unable to continue processing. Recovery Resubmit the statement. If this does not correct the problem, stop and restart the Neoview database. If this does not correct the problem, contact the GMCSC.
  • Page 226 The operation fails. Recovery Resubmit the statement. If this does not correct the problem, stop and restart the HP Neoview database software. If this does not correct the problem, report the entire message to HP support. SQL 9209 9209 Column name does not exist in object name.
  • Page 227 The HP Neoview database software is unable to continue processing. Recovery Resubmit the statement. If this does not correct the problem, stop and restart the HP Neoview database software. If this does not correct the problem, report the entire message to HP support. SQL 9215 9215 UPDATE STATISTICS encountered an internal error (location).
  • Page 228 9218 The statement will have no effect because no histograms need to be updated. Cause The HP Neoview database software determined that no histograms needed to be created or updated for the table. Effect The operation does not fail but has no effect.

  • Page 229: 1 Executor Sort And Scratch File I/O Messages (10000 Through 10199)

    This error occurs when a scratch file read operation unexpectedly reaches an EOF. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 10004 10004 Sort failed while generating intermediate runs with sort error value1 and system error value2.
  • Page 230 The caller of sort specified an invalid sort algorithm. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 10010 10010 Sort run number is invalid.
  • Page 231 SQL 10015 10015 Sort failed while calling PROCESSHANDLE_GETMINE_ with error number. Cause An error occurred while calling a system level call. Effect The operation fails. Recovery Contact the GMCSC. SQL 10016 10016 Sort failed while calling PROCESSHANDLE_DECOMPOSE_ with error number. Cause An error occurred while calling a system level call.
  • Page 232 An I/O operation to a scratch file failed with a low-level system error. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 10027 10027 Sort failed while calling FILE_GETINFOLIST with error number.

  • Page 233: Scratch File I/O Messages (10101-10199)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 10047 10047 Sort Error: Wrong length read.
  • Page 234 None. This is an internal error. Contact the GMCSC. SQL 10103 10103 operator failed to close a scratch file. FILE_CLOSE_ returned error number. is the HP Neoview query operator that encountered the error; for example: operator merge join. is a Neoview platform internal procedure-error number.
  • Page 235 Effect The operation fails. Recovery None. This is an internal error. Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message. SQL 101 12 10112 operator failed to set the current position in a scratch file.
  • Page 236 Effect The operation fails. Recovery None. This is an internal error. Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message. SQL 101 16 10116 operator failed to create a disk pool. PROCESSHANDLE_GETMINE_ returned error number.
  • Page 237 Effect The operation fails. Recovery None. This is an internal error. Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message. SQL 10150 10150 operator failed to find an appropriate disk for overflow data.

  • Page 239: Trigger, Udr Server, And Language Manager Messages (1 1000 Through 1 1399)

    12 Trigger, UDR Server, and Language Manager Messages (1 1000 Through 1 1399) SQL 1 1005 11005 Table table-name or one of its triggers is inaccessible. is the name of the table. table-name Cause The object metadata is not accessible. Effect The operation fails.
  • Page 240 Effect The DDL statement fails. Recovery None. This is an internal error. Contact your HP support representative. SQL 1 1045 11045 FIRST N UPDATE or DELETE is not supported on a table that is the subject table of BEFORE triggers or AFTER STATEMENT triggers. Trigger trigger-name has table table-name as its subject table.
  • Page 241 Effect The request message is rejected, and the SQL statement fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1 102 11102 MXUDR: Invalid UDR handle: string.
  • Page 242 The UDR server encountered an internal error. An unexpected parameter mode value appeared in a request message. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1 108 11108 MXUDR: Unable to allocate memory for object object-name.
  • Page 243 Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1 1 14 11114 MXUDR: Internal error: A stored procedure result set message-type request arrived containing an invalid result set handle: handle.
  • Page 244 The operation fails. Recovery Check the installation of the NSJ product and the language manager. Verify the existence of the specified class. Stop and restart the session, and retry the SQL statement. HP support will perform recovery operations. SQL 1 1202 11202 Language Manager initialization failed.
  • Page 245 Effect The operation fails. Recovery Correct the EXTERNAL NAME clause and resubmit. SQL 1 1212 11212 Specified signature is invalid. Reason: Java signature size is bigger than the maximum supported size. Cause In a CREATE PROCEDURE request, the Java signature size exceeded the maximum supported size.
  • Page 246 SQL 1 1217 11217 Java execution: Data overflow occurred while retrieving data at parameter position parameter number. Value is truncated. Cause During execution of a CALL statement, numeric or string overflow occurred while processing the stored procedure output value returned in parameter parameter number. Effect None.
  • Page 247 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1230 11230 Multiple compatible Java methods named method-name were found in Java class class-name.
  • Page 248 SQL 1 1232 11232 The Java method method-name in Java class class-name is not defined as static. is the Java method name specified in the EXTERNAL NAME clause of a method-name CREATE PROCEDURE statement. is the Java class name specified in the EXTERNAL NAME clause of a class-name CREATE PROCEDURE statement.
  • Page 249 Java method signature. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1236 11236 Stored procedure procedure-name attempted to return too many result sets.
  • Page 250 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 1 1243 11243 The Language Manager encountered a java.sql.SQLException while retrieving the value of column column-number from a java.sql.ResultSet...

  • Page 251: Materialized Views Messages (12000 Through 12329)

    Cause The HP Neoview database software found a discrepancy while reading metadata information. The information returned is inconsistent. This is an internal error. Effect The operation fails. Recovery Contact HP support.
  • Page 252 is an unaudited table. name Cause Materialized views that use unaudited tables are not supported. Effect The creation of the materialized view fails. Recovery Correct the syntax and resubmit. SQL 1201 1 12011 The materialized view cannot be altered. ON STATEMENT and RECOMPUTE materialized views do not contain an IGNORE CHANGES clause.
  • Page 253 This is an internal configuration error resulting from an incorrect object type. Effect The operation fails. Recovery Contact HP support. SQL 12024 12024 A materialized view cannot be initialized when it is using other materialized views that are not initialized: name.
  • Page 254 SQL 12033 12033 An underlying materialized view has an incompatible refresh type. Cause You attempted to create a materialized view on top of another materialized view with an incompatible refresh type. Effect The creation of the materialized view fails. Recovery The two materialized views must have compatible refresh types.
  • Page 255 SQL 12050 12050 ATTRIBUTE AUDIT not supported for materialized views. Cause The AUDIT attribute is not supported for materialized views. Effect The creation of the materialized view fails. Recovery Remove the attribute from the materialized view definition. SQL 12051 12051 ATTRIBUTE DEALLOCATE not supported for materialized views. Cause The DEALLOCATE attribute is not supported for materialized views.
  • Page 256 is the name of the table being altered. table-name is the row length of the MV source or the trigger base table. actual-row-length is the maximum row length of the MV source table or trigger base max-row-length table for which it is guaranteed that the compile error will not occur.
  • Page 257 Recovery None. SQL 12081 12081 Audit type not allowed for materialized view refresh type. Cause The specified audit type is not allowed for the specified refresh type. Effect The creation of the materialized view fails. Recovery Correct the syntax and resubmit. SQL 12087 12087 Operation failed since table log is not empty.
  • Page 258 SQL 12109 12109 To ensure optimal Refresh performance, the STORE BY clause should include the following GROUP BY columns: col-names. are the group by columns that should be included in the STORE BY clause. col-names Cause To improve the materialized view refresh performance, the specified columns should have been included in the STORE BY clause.
  • Page 259 Recovery None. SQL 121 15 12115 The IGNORE CHANGES clause of materialized view mv-name cannot be altered when the logs of the tables referred to in the IGNORE CHANGES clause are not empty. Refresh the materialized view and try the ALTER statement again.
  • Page 260 Cause You used the name of an MVGroup that does not exist. Effect The operation failed. Recovery Correct the syntax and resubmit. SQL 12202 12202 Materialized view mv-name does not exist. Cause You specified a name of a materialized view that does not exist. Effect The operation failed.
  • Page 261 Recovery None. SQL 12209 12209 Some materialized views used by this materialized view must appear in the MVGroup as well.. Cause An attempt was made to add a dependent materialized view to a materialized view group. All materialized views this materialize view depends on must already be in the materialized view group.
  • Page 262 Cause An attempt was made to add a materialized view to a materialized view group through automatic materialized view group creation. The owner of the table used by the materialized view is different from the owner of the materialized view. Effect The operation failed.
  • Page 263 Effect The DML operation on the materialized view fails. Recovery Contact the GMCSC. SQL 12316 12316 No corresponding context row was found in the context log. Cause This is an internal error used by the refresh utility to determine when the context log is empty and the work is done.
  • Page 264 Cause You attempted to create a materialized view by using the same table more than once. This operation is not allowed. Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12323 12323 Creation failed.
  • Page 265 Effect The operation fails because the materialized view cannot be incrementally maintained. Recovery Correct the syntax and resubmit. SQL 12329 12329 Creation failed. Join predicates must have only one column instance at each side of the equal sign. The materialized view cannot be maintained incrementally.

  • Page 267: Messages Generated By The Message System (16000 Through 16999)

    Internal error. Effect The Neoview software is unable to return or display a message with the specified number. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.

  • Page 269: Internal Stored Procedures Messages (19000 Through 19999)

    Effect The HP Neoview database software is unable to process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 19001 19001 An error was found in field description of internal stored procedure.
  • Page 270 Effect The HP Neoview database software is unable to process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 19021 19021 Stored procedure name returns with error: number.

  • Page 271: Utility Messages (20000 Through 23099)

    SQL was not able to write to the requested file and received error error number. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20003 20003 File system error error number occurred during file close.
  • Page 272 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20008 20008 An internal error occurred - buffer size is not a multiple of the block size for file.
  • Page 273 Effect SQL is unable to complete the command. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20013 20013 An internal error occurred - did not enable large transfer for file.
  • Page 274 The information returned is inconsistent. This is an internal error. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20019 20019 An internal error occurred. An invalid default state (state) exists in the COLS metadata table for column (name).
  • Page 275 The utility subsystem that reads and maintains metadata could not find the requested HP Neoview database object. A possible cause is that the catalog, schema, or object name is misspelled in the request. Neoview database objects can be catalogs, schemas, tables, trigger temporary tables, stored procedures, indexes, or MP aliases.
  • Page 276 Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20028 20028 Specified an invalid partition physical size, should be BYTES, MBYTES, KBYTES, or GBYTES. Cause You specified an invalid partition physical size, which must be expressed in bytes, megabytes, kilobytes, or gigabytes.
  • Page 277 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20045 20045 An internal error occurred - invalid sort order.
  • Page 278 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20052 20052 Transaction Management subsystem could not set the AutoCommit.
  • Page 279 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20057 20057 An internal error occurred - Transaction Management subsystem could not do GetRowsAffected on a statement.
  • Page 280 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20109 20109 details. describe the returned error information from the file system. details...
  • Page 281 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20141 20141 Wrong parameter index passed. Cause The utility subsystem that performs CLI operations failed while trying to get information from the returned statement.
  • Page 282 SQL was unable to perform the requested operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20164 20164 The search condition for the specified check constraint has a syntax error.
  • Page 283 An unspecified internal error occurred during the IMPORT utility operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20179 20179 An unexpected error condition was encountered.
  • Page 284 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20205 20205 Index index is online. Cannot perform POPULATE INDEX. is the index's ANSI name.
  • Page 285 An invalid character set designation was encountered. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20226 20226 An internal error occurred - trigger parameter is not set.
  • Page 286 For more information, see the Neoview User Management and Security Administration Guide. If those commands do not solve the problem or if the status value returned by the error is not 11, please contact HP Support for assistance. SQL 20236 20236 Error returned from USER_GETINFO_ while converting username to userid, status: status, username: username.
  • Page 287 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20241 20241 The MODIFY utility cannot perform a DROP HASH operation on the object object-name because the target partition partition-name does not have enough space for the redistribution of data.
  • Page 288 ORSERV process to perform a FUP RELOAD operation. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20271 20271 SPI Error error returned from subsystem while performing an online reload operation.
  • Page 289 20290 The current operation on partition partition for the object object failed because a utility operation on the same partition is already in progress or has failed. is the HP Neoview platform location of the partition involved in another utility partition operation.
  • Page 290 20296 The MODIFY request has completed successfully, but ORSERV might not have completed successfully. Please run FUP RELOAD manually to reclaim any free space on file-name-list. is the list of HP Neoview platform file names of the partitions that might file-name-list need reloading. The names are separated by blanks.
  • Page 291 Effect The operation fails. Recovery Contact your HP service provider to check if the Synonym metadata is corrupt. SQL 20317 20317 Internal Error: invalid referenced object’s type for the Synonym. Cause This is an internal error. The Synonym metadata is in an inconsistent state. The referenced object type is invalid.
  • Page 292 Specify the correct file name and resubmit. SQL 20356 20356 File name could not be accessed. Error error was returned. is the name of the HP Neoview platform file requested to be removed. name is the error returned by the file system.
  • Page 293 SQL 20362 20362 Error error was returned while validating the file set list specified by “file”. is the error returned by the HP Neoview platform file system while searching for error files. is the template of Neoview platform files requested to be removed.
  • Page 294 Cause MXTOOL generates a list of files to check as specified by an HP Neoview platform file template. An error was returned during the processing of this list. Effect The operation fails. Recovery For information about file-system errors, see Chapter 21 (page 385).
  • Page 295 SQL 20452 20452 GOAWAY cannot be used to remove a Guardian file on a remote system (system). is the name of the system where the HP Neoview platform object resides. system Cause You tried to remove a Neoview platform object on a remote system.
  • Page 296 An unanticipated error occurred on an attempt to refresh the materialized view. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20504 20504 A user-defined transaction has been started. REFRESH cannot be performed.
  • Page 297 This is an internal error between utilities and the catalog manager. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20506 20506 Catalog catalog-name does not exist.
  • Page 298 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20514 20514 MVLog cleanup is not possible because no ON REQUEST materialized view is being refreshed.
  • Page 299 This refresh operation fails. Recovery After the concurrent operation that holds the DDL lock finishes, run refresh again. If no concurrent operations are running, the DDL lock has to be removed. Contact your HP service provider to remove the lock. SQL 20522 20522 A DDL lock on materialized view mv-name cannot be canceled.
  • Page 300 The operation fails. Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If this problem persists, contact your HP service provider. SQL 20528 20528 Failed to increment the current epoch of table table-name.
  • Page 301 Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If the error persists, contact your HP service provider. SQL 20536 20536 Failed to populate the index(es) during the recompute of a materialized view.
  • Page 302 The operation fails. Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If the error persists, contact your HP service provider. SQL 20539 20539 Failed to execute : string.
  • Page 303 The refresh operation was unable to complete log cleanup correctly. Effect The operation fails. Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If the error persists, contact your HP service provider.
  • Page 304 Recovery REFRESH the materialized view again: first use the CANCEL option to clean up, and then retry the REFRESH command. If the error persists, contact your HP service provider. SQL 20551 20551 The materialized view mv-name cannot be refreshed (not all of the used materialized views are initialized).
  • Page 305 SQL 20556 20556 Materialized view mv-name cannot be refreshed standalone (the used materialized view(s) and table(s) are not coordinated). is a materialized view name. mv-name Cause The materialized view might be based other materialized views and tables that are not up to date. Effect The operation fails.
  • Page 306 Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20563 20563 TMF error error-number occurred while trying to begin a transaction. is an error originating from the transaction management facility (TMF).
  • Page 307 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20576 20576 File system error error-number occurred during FILE_OPEN_ on process process-name.
  • Page 308 Effect The MODIFY operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20704 20704 A hardware trap occurred in audit fixup process process name.
  • Page 309 Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20705 20705 An audit fixup request was made out of sequence. Cause During an online partition management operation, the MXAUDSRV process received an unexpected request from the MODIFY code.
  • Page 310 Effect The MODIFY operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20710 20710 An error occurred while attempting to perform a REDO of a TMF audit record during the audit fixup phase of the operation, in audit fixup process process name.
  • Page 311 Effect The MODIFY utility did not process the request. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20718 20718 An audit trail version incompatibility on audit volume volume name was encountered in audit fixup process process name.
  • Page 312 Effect The MODIFY operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20723 20723 An audit fixup process found a label change audit record during fixup work.
  • Page 313 Effect The MODIFY operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20734 20734 Error error number was returned by CONVERTTIMESTAMP while trying to obtain local civil time.
  • Page 314 Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20751 20751 A user-defined transaction has been started. VERIFY cannot be performed.
  • Page 315 Recovery None. Informational only. SQL 20758 20758 Partition name is offline. is the HP Neoview platform file name of the partition that is offline. name Cause VERIFY discovered that the table being verified has a partition that is offline. This partition is currently part of an active MODIFY request or a failed MODIFY request.
  • Page 316 (time2) defined in the metadata for Guardian file (file). is the Julian timestamp found on the label. time1 is the Julian timestamp found in the metadata. time2 is the name of the HP Neoview platform file. file Cause An inconsistency was found during the VERIFY operation. Effect None.
  • Page 317 An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Contact your HP service provider to use the MXTOOL FIXUP utility to fix this inconsistency. SQL 20765 20765 The audit flag (flag1) defined on the label does not match the audit flag (flag2) defined in the metadata for Guardian file (file).
  • Page 318 (name2) defined in the metadata for Guardian file (file). is the ANSI name found in the resource fork. name1 is the ANSI name found in the metadata. name2 is the name of the HP Neoview platform file. file Cause An inconsistency was found during the VERIFY operation. Effect None.
  • Page 319 (name) while processing the Guardian file (file). is the constraint name described in the metadata. name is the name of the HP Neoview platform file. file Cause An inconsistency was found during the VERIFY operation.
  • Page 320 20783 The location (string1) defined in the partition map for Guardian file (file) does not match the location (string2) defined in metadata. is the HP Neoview platform name of the partition that is defined in the partition string1 map on the resource fork that does not exist in the metadata.
  • Page 321 An inconsistency was found during the VERIFY operation. Effect None. This is an informational message. Recovery Contact your HP service provider to perform an MXTOOL CLEANUP operation on the object. SQL 20786 20786 The partition map is missing from the resource fork for Guardian file (file).
  • Page 322 (mversion) in the metadata for Guardian file (file). is the object schema version stored in the resource fork. rversion is the object schema version stored in the HP Neoview platform file. mversion is the Neoview platform file where an inconsistency is detected.
  • Page 323 For information about file-system errors, see Chapter 21 (page 385). Correct the problem and resubmit. If the problem persists, contact your HP service provider about this condition. SQL 20795 20795 VERIFY cannot work on Guardian file (file) that has an object type of (type1).
  • Page 324 Effect This mismatch causes operations that depend on these values to be the same to fail. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 20805...
  • Page 325 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 after the SELECT operation, contact your HP service provider. SQL 20821 20821 Constraint constraint is disabled.
  • Page 326 TABLES, INDEXES and Materialized views are supported. is the HP Neoview database object. name Cause You attempted to run the FIXUP utility on an HP Neoview database object that was not a table, index, or materialized view. Effect The operation fails.
  • Page 327 20990 PURGEDATA requires NOLOG option because name has Materialized View defined. PURGEDATA cannot be performed. is the materialized view name. name Cause The HP Neoview database object you specified has materialized views created on it, but you omitted the NOLOG option. Effect The operation fails. Recovery Specify the NOLOG option and resubmit.
  • Page 328 is one of these: DROP DEPENDENT, CASCADE DEPENDENT, or option-name RECREATE DEPENDENT. Cause You specified an option that is not implemented. Effect The operation fails. Recovery Remove the option that is not implemented, and resubmit the command. SQL 21004 21004 Catalog does not exist or has not been registered on the local segment.
  • Page 329 An error occurred while instantiating the class_name. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 23002 23002 servername: An error occurred while allocating heap.
  • Page 330 The DML Layer reported an SQL error. See description for the reason. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 23008 23008 servername: Assertion failed.
  • Page 331 An unexpected exception occurred. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 23015 23015 servername: DDL command could not be found in buffer: description.
  • Page 332 The program was unable to update the partition metadata. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. Utility Messages (20000 Through 23099)

  • Page 333: Authentication And User Management Messages (24000 Through 24999)

    17 Authentication and User Management Messages (24000 Through 24999) The following errors can occur in the context of user authentication or user management actions. 24001 24001 The LDAP host name or IP address is not allowed to be null. Cause You specified a NULL value for the Host attribute when configuring the interface with an external directory server.
  • Page 334 Recovery Correct the syntax and resubmit. 24007 24007 The configuration text exceeds the maximum length of 26624 characters. Cause The configuration description file contains more than the maximum number of characters allowed. Effect The operation fails. Recovery Remove any superfluous spaces or comments, and resubmit the command with a configuration description file that does not exceed the maximum length.
  • Page 335 24013 24013 The LDAP search password exceeds the maximum length of 128 characters. Cause You specified a value exceeding the maximum length for the SearchUserPwd attribute when configuring the interface with an external directory server. Effect The operation fails. Recovery Correct the syntax and resubmit.
  • Page 336 If the error persists, check the server configuration. If the configuration appears to be valid (and consistent with the requirements of the external server), contact HP Support for help in determining whether an internal software error occurred.
  • Page 337 Cause The role ID could not be retrieved because of an operating system problem. Effect The operation fails, and the failure is logged as a system event that HP Support can use to help identify the problem. Recovery Please report this error to HP Support.
  • Page 338 Recovery Correct the syntax and resubmit. 24038 24038 The number of maximum logon attempts must be a value from 0 through Cause This message is currently not used. Effect This message is currently not used. Recovery This message is currently not used. 24039 24039 The number of seconds to wait before a logon timeout failure occurs must be a value from 0 through 86400.
  • Page 339 The user management operation failed because of an internal error. Effect The operation fails. Recovery Report this error to HP Support. 24047 24047 The user name exceeds the maximum length of 32 characters. Cause You specified a platform username that is too long. The maximum length is 32 characters.
  • Page 340 You tried to add a user but the operation failed because of an internal error. Effect The operation fails. Recovery Please report this error to HP Support. 24059 24059 Unable to acquire lock. Cause The operation failed because of an internal error.
  • Page 341 Cause The password you assigned to a platform user does not meet the configured criteria for password quality. Effect The operation fails. Recovery Choose a password consistent with password quality criteria. 24069 24069 The minimum quality required of password cannot be greater than the number of quality attributes set to on.
  • Page 342 Cause The operation failed because of an internal error. Effect The operation fails. Recovery Please report this error to HP Support. 24083 24083 Failed to delete the LDAP configuration entry. Cause The operation failed because of an internal error. Effect The operation fails.
  • Page 343 Recovery Correct your syntax, and resubmit the request. 24087 24087 The parameter parameter value is too long. Cause In the configuration description file, the value you entered for the specified parameter exceeded the permissible length. Effect The operation fails. Recovery Correct your syntax, and resubmit the request.
  • Page 344 The operation failed because of an internal error. Effect The operation fails. Recovery Please report this error to HP Support. 24097 24097 Cannot delete the LDAP default configuration. Cause You tried to delete the LDAP server configuration called “default.” It is not permissible to delete this configuration entry.
  • Page 345 Effect The operation fails. Recovery None. This operation is not permitted. 24100 24100 Invalid usage priority. Cause The value you specified as the usage priority of an external directory server was not in the range of 0 through 32767. Effect The operation fails.
  • Page 346 Recovery Check the parameter specified, and try again with any necessary corrections. If the problem persists, contact HP Support. 241 10 24110 Current password required to change the password for this role. Cause You tried to reset the password for a role, but the security policy requires you to provide the current password in order to change the password.
  • Page 347 Recovery Contact HP Support 241 19 24119 Alter User failed. Cause Internal error. Effect Internal error. Recovery Contact HP Support 24120 24120 Change Password failed. Cause Internal error. Effect Internal error. Recovery Contact HP Support 24121 24121 Delete Role failed.
  • Page 348 Cause Internal error. Effect Internal error. Recovery Contact HP Support 24127 24127 Username not found. Cause You specified a username that is not registered on Neoview. Effect Operation is not successful. Recovery Verify correct username and resubmit the command. 24128 24128 You are not authorized to perform this command.
  • Page 349 You attempted to grant a platform role to a database user. Effect The role is not granted. Recovery Resubmit the command using a database role. 24139 24139 New role cannot be added. ROLES table failed consistency check. Cause Internal error. Effect Internal error. Recovery Contact HP Support.

  • Page 351: Versioning, Distribution, And Jdbc Messages (25000 Through 25499 And 29000 Through 29399)

    25100 Remote node node is not running a compatible version of SQL/MX software. The SQL/MX software version (MXV) of node is MXV1, the local node does not support MXVs older than MXV2. is the name of the affected remote node (remote HP Neoview database segment). node Versioning Messages (25000–25399)
  • Page 352 The SQL/MX software version (MXV) of node2 is MXV1, the local node supports only MXV MXV2. is the name of the affected remote node (remote HP Neoview database segment). node1 is the name of the local node (local Neoview database segment).
  • Page 353 Cause You attempted to access a table or view in a schema with a schema version that is earlier than the accessing node’s earliest supported schema version. This message can be issued from the local node or from an ESP on a remote node. This message is accompanied by message 25001, which explains what actual software component reported the error.
  • Page 354 is that node’s MXV. version2 Cause You attempted to access a database object with an object schema version that is incompatible with one or more nodes where the object (or a partition or index of the object) resides. This message indicates a downgrade that has been performed without removing database objects of the later version.
  • Page 355 is the compiler version of the compiler that compiles the query or executes the version2 DDL or utility operation. Cause The affected query compilation, DDL, or utility operation attempted to access system schema tables with a system schema version that is incompatible with the version of the compiler that compiles the query and executes the operation.
  • Page 356 MXV of the node that executes the query. MXV1 Cause The affected node runs a General Availability (GA) release of the HP Neoview database software and is incompatible with the affected schema. Effect The operation fails. Recovery Upgrade or downgrade the node to a Neoview database software release that is compatible with the affected schema’s version.
  • Page 357 MXV of node1. MXV1 Cause The accessing node runs a GA release of the HP Neoview database software and is incompatible with a system schema created by a non-GA release. Effect The operation fails. Recovery Upgrade or downgrade the accessing node to an HP Neoview database software release that is compatible with the affected system schema version.
  • Page 358 MXV of the node that executes the query. MXV1 Cause The accessing node runs a non-GA release of the HP Neoview database software and is compatible only with schemas created by its own version. Effect The operation fails.
  • Page 359 SQL 25301 25301 Module module has module version version1; the local node does not support module versions higher than version2. is the name of the affected module. module is the module version of the affected module. version1 is the MXV of the local node. version2 Cause You attempted to load a module with a module version (version1) that is later than...
  • Page 360 MXV of the affected node. MXV1 Cause The affected node runs a GA release of the HP Neoview database software and is incompatible with a query plan generated by a non-GA release. Effect The operation fails. Recovery Compile the query with a compiler version that is compatible with the MXV.

  • Page 361: Distribution Messages (25400-25499)

    Recovery When the message is issued as a error, correct the error and retry the operation. If the message is issued as a warning, the HP Neoview database software attempts to recover automatically. SQL 25402 25402 Catalog catalog has previously been registered on node node.
  • Page 362 Recovery If the message is issued as a error, correct the error and retry the operation. If the message is issued as a warning, the HP Neoview database software attempts to recover automatically. SQL 25404 25404 Catalogs catalog1 and catalog2 must have identical visibility.
  • Page 363 Cause When the DML query was compiled, the affected database object had partitions on a remote node, and the database object’s catalog was visible on both the remote node and the local node. When the query was executed, the visibility of the object’s catalog changed. See accompanying messages 1002, 25401, or 25403 for more details about the visibility of the change.
  • Page 364 Recovery Correct the error and retry the operation. SQL 25423 25423 Schema schema has no replica on node node. is the ANSI name of the affected schema. schema is the remote node with no replica of the affected schema. node Cause The target node of an UNREPLICATE SCHEMA operation does not have a replica of the affected schema.
  • Page 365 A test condition was encountered by debug mode software. The explanatory text contains the details. Effect The affected operation succeeds. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. Distribution Messages (25400–25499)

  • Page 366: Jdbc Driver Error Messages (29000-29399)

    JDBC Driver Error Messages (29000–29399) This range of numbers is reserved for JDBC driver error messages. For complete information about JDBC driver error messages, see the Neoview JDBC Type 4 Driver Programmer's Reference. Versioning, Distribution, and JDBC Messages (25000 Through 25499 and 29000 Through 29399)

  • Page 367: Neoview Command Interface (Nci) Messages (29400 Through (29599)

    19 Neoview Command Interface (NCI) Messages (29400 Through (29599) This section describes Neoview Command Interface (NCI) error messages. 29400 Could not initialize the console reader. Cause An Input Output Exception was received while initializing the Input Stream. Effect Unable to launch the Neoview Command Interface. Recovery Retry launching the Neoview Command Interface.
  • Page 368 29406 Could not find the HP Neoview Type 4 driver in the classpath. Cause The classpath for Neoview JDBC Type 4 Driver JAR file has not been set. Effect Unable to launch the Neoview Command Interface. Recovery Reinstall the Neoview Command Interface by selecting a valid Neoview JDBC Type 4 Driver.
  • Page 369 Recovery Retry the command by switching to the appropriate mode. Issue the help command for more information on the list of supported commands in current mode. 29414 This command is not supported in SQL mode. Cause You specified an interface command that is not supported in SQL mode. Effect The command fails to execute.
  • Page 370 29421 No materialized views found. Cause There are no materialized views present in the current schema. If you specified a pattern, there are no tables matching the specified pattern. Effect None. Recovery Verify if you are in the correct schema by issuing an ENV or a SHOW SCHEMA command.
  • Page 371 Cause There are no prepared statements present in the current schema. If you specified a pattern for the statement name, there are no prepared statements matching the specified statement name pattern. Effect None. Recovery Not applicable. 29428 No parameters found. Cause There are no parameters set in the current session.
  • Page 372 29435 Invalid ListCount value. The value must be in the range 0-2147483647." Cause The value specified for the SET LISTCOUNT command is not within the acceptable range. Effect The command fails to execute. Recovery Retry the command by specifying a value within the specified range. 29436 The specified statement does not exist in the history buffer.
  • Page 373 Cause <section-name>is the name of a section within the filename to execute. <filename> refers to a script file containing commands to be executed by the OBEY command. You specified an invalid section name in the OBEY command. Effect The command fails to execute. Recovery Retry the command by specifying a valid section name in the OBEY command.
  • Page 374 Effect The command fails to execute. Recovery Reconnect to the Neoview Platform by specifying the appropriate login credentials and execute the command. 29449 Server product may not be installed or an internal error has occurred. Please contact support. Cause The Neoview Command Interface Server product has not been installed on the Neoview Platform Effect The command fails to execute.
  • Page 375 29456 -d|defaults option cannot be specified with any other options. Cause You specified an incorrect syntax for the PRUN command. Effect The PRUN command fails to execute. Recovery Retry the PRUN command by specifying the valid options. 29457 NWMS not started on this server. Cause You tried to execute a WMS command when WMS is not running on the server.
  • Page 376 Cause <paramname> refers to the parameter name. You specified an invalid parameter name in the SQL statement Effect The statement fails to execute. Recovery Retry the SQL statement by specifying a valid parameter or use the SET PARAM command to set a parameter value. 29465 Obey commands inside of files are executed in non-interactive mode and require a filename or wildcard.
  • Page 377 Effect The conditional statement fails. Recovery N/A. 29473 Unable to compare a string with an integer. Cause The left side of a conditional statement is a string and the right side is a integer. Effect The conditional statement fails. Recovery N/A.

  • Page 379: Rowsets Messages (30000 Through 30999)

    Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 30003 30003 Rowset size must be an integer host variable or constant.
  • Page 380 SQL 30009 30009 Trying to add more elements than maximum rowset size. Cause The HP Neoview database software received an internal error from a rowset. Effect The operation fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition.
  • Page 381 GET DIAGNOSTICS statement, their output variables must also be considered invalid. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 30024 30024 ROWSET_ROW_COUNT is not available for this statement.
  • Page 382 Effect The PREPARE of the INSERT fails. Recovery Do not attempt recovery. HP support will perform recovery operations in response to an automatically generated dial-out message about this condition. SQL 30031 30031 The number of error conditions raised during the NOT ATOMIC INSERT statement has exceeded the user specified value of max-num for the capacity of the diagnostic area.
  • Page 383 is the name of the materialized view. materialized-view Cause You attempted to use NOT ATOMIC inserts on a table that is the subject table of a materialized view. Effect Compilation of the INSERT statement fails. Recovery Contact the GMCSC. SQL 30034 30034 NOT ATOMIC INSERT is not supported on a table that is the subject table of AFTER triggers.

  • Page 385: 21 File-System Errors

    21 File-System Errors Some file-system errors are new or changed for the Neoview platform and are not documented, “New or Changed File-System Errors for the Neoview Platform” (page 398). Some error messages generated by the Neoview platform include file-system error codes. For example: SQL 1024 1024 File system error error-number occurred on text-string-1.
  • Page 386 Error Number File-System Error Text 0023 The disk address is out of bounds, or the maximum number of blocks in an alternate-key file is exceeded. 0024 Privileged mode is required for this operation. 0025 AWAITIO[X] or CANCEL attempted on file opened for waited I/O. 0026 AWAITIO[X] or CANCEL or CONTROL 22 attempted on a file with no outstanding I/O requests.
  • Page 387 Error Number File-System Error Text 0059 The disk file is bad; there is a mismatch in the internal file control block, or the file structure in a structured file is inconsistent. 0060 The file resides on a removed disk, the device is stopped or not open, or a server has failed and a process has been replaced by a different process with the same name since the server was opened.
  • Page 388 Error Number File-System Error Text 0097 Transaction aborted by call to ABORTTRANSACTION. 0098 Allocation of a Transaction Control Block failed because the local table is full, or the table on a remote segment is full. 0099 Process attempted to use features of a microcode option that is not installed on this segment. 0100 Device is not ready or the controller is not operational.
  • Page 389 Error Number File-System Error Text 0156 Tape command rejected. 0157 I/O process internal system error. 0160 Request is invalid for device state; protocol error. 0161 Impossible event occurred for line state. 0162 Operation timed out. 0163 EOT received or power at autocall unit is off. 0164 Disconnect received or data line is occupied (busy).
  • Page 390 Error Number File-System Error Text 0201 The current path to the device is down, an attempt was made to write to a nonexistent process, the message-system request was incorrectly formatted, or an error was found in the message system interface. 0210 Device ownership changed during operation.
  • Page 391 Error Number File-System Error Text 0522 Either the SET^FILE or CHECK^FILE operation is not valid on an open file or OPEN^FILE was called for a file already open. 0523 An EDITREAD or EDITREADINIT error occurred. 0524 The specified file was not open. 0525 The requested operation was inconsistent with the access mode.
  • Page 392 Error Number File-System Error Text 0590 The parameter value is invalid or inconsistent with another. 0593 The request was cancelled. 0594 A tape-catalog error was returned to Tape Services. Refer to the event log for detailed information. 0595 An error was returned to Tape Services. Refer to the event log for detailed information. 0597 A required item is missing from an item list.
  • Page 393 Error Number File-System Error Text 0764 Unable to allocate space from the revive pool. 0765 Unable to allocate space from the SQL data area pool (SQLMXBuffer space). 0766 The maximum number of opens for a file has been reached. 0770 Neoview SQL tried to roll back a savepoint that had already been discarded.
  • Page 394 Error Number File-System Error Text 1053 An ECC error or a checksum error occurred indicating that it is impossible to process the accessed block. No data is returned. 1054 Unable to access a non-protected table or protection view that has been altered by an uncommitted DDL statement.
  • Page 395 Error Number File-System Error Text 1086 Unable to unlock an SQL table that has locks through either STABLE ACCESS or REPEATABLE ACCESS. 1087 The SQL file system detected an internal disk process error. 1088 SQL internal error. 1089 SQL internal error. 1090 The requested SQL operation cannot be completed because of current limitations on message sizes.
  • Page 396 Error Number File-System Error Text 1122 The supplied KEYTAG value is already defined for this table. 1123 SQL internal error. 1124 SQL internal error. 1125 SQL internal error. 1126 SQL internal error. 1127 Unable to update an SQL catalog table from a process that is not licensed. 1128 An operand was scale truncated during expression evaluation.
  • Page 397 Error Number File-System Error Text 4028 No space left on device. 4029 Illegal seek. 4030 Read only file system. 4031 Too many links. 4032 Broken pipe or no reader on socket. 4033 Argument out of range. 4034 Value out of range. 4035 No message of desired type.

  • Page 398: New Or Changed File-System Errors For The Neoview Platform

    Error Number File-System Error Text 4131 File name too long. 4132 Directory not empty. 4180 Invalid data in buffer. 4181 No reply in buffer. 4182 Partial buffer received. 4183 Interface error from SPI. 4184 Version mismatch. 4185 XDR encoding error. 4186 XDR decoding error.
  • Page 399 Transaction type mismatch. Cause This error is returned due to a transaction type mismatch. Typically this happens when a read-only transaction is in effect and an insert, update, delete, DDL or utility statement is executed within the same transaction and the mismatch is not detected by the SQL compiler. Effect The query aborts.

Table of Contents