1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. NonStop SQL/MX
  6. Messages manual

HP NonStop SQL/MX Messages Manual

Hide thumbs
1
2
3
4
5
Table Of Contents
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
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
Table of Contents

Advertisement

Quick Links

HP NonStop SQL/MX
Messages Manual
Abstract
This manual describes messages produced by the HP NonStop™ SQL/MX relational
database management system and its associated subsystems.
Product Version
NonStop SQL/MX Release 3.0
Supported Release Version Updates (RVUs)
This publication supports J06.11 and all subsequent J-series RVUs and H06.22 and all
subsequent H-series RVUs, until otherwise indicated by its replacement publications.
Part Number
640324-001
Published
February 2011

Advertisement

Table of Contents
loading

Related Manuals for HP NonStop SQL/MX

Summary of Contents for HP NonStop SQL/MX

  • Page 1 HP NonStop SQL/MX Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MX relational database management system and its associated subsystems. Product Version NonStop SQL/MX Release 3.0 Supported Release Version Updates (RVUs) This publication supports J06.11 and all subsequent J-series RVUs and H06.22 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications.
  • Page 2 Document History Part Number Product Version Published 640324-001 NonStop SQL/MX Release 3.0 February 2011...

  • Page 3: Legal Notices

    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 5: Message Handling

    HP NonStop SQL/MX Messages Manual Glossary Figures Legal Notices What’s New in This Manual Manual Information New and Changed Information About This Manual Audience Related Documentation Notation Conventions HP Encourages Your Comments 1. Message Handling Viewing SQL/MX Messages Non-SQLCODE Error Messages...

  • Page 6: Table Of Contents

    9. Generator Messages (7000 through 7999) 10. Executor Messages (8000 through 8999) 11. UPDATE STATISTICS Messages (9200 through 9221) 12. Executor Sort and Scratch File I/O Messages (10000 through 10199) Executor Sort Messages 12-1 Scratch File I/O Messages 12-12 HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 7 19. Versioning and Distribution Messages (25000 through 25399) Distribution Messages (25400-25499) 19-25 JDBC Driver Error Messages (29000-29999) 19-32 20. Rowsets Messages (30000 through 30999) 21. SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE and SQLCODE Considerations 21-1 SQLSTATE Values 21-2 A. Non-SQLCODE Error Messages InstallSqlmx script...
  • Page 8 Contents HP NonStop SQL/MX Messages Manual—640324-001...

  • Page 9: Manual Information

    What’s New in This Manual Manual Information HP NonStop SQL/MX Messages Manual Abstract This manual describes messages produced by the HP NonStop™ SQL/MX relational database management system and its associated subsystems. Product Version NonStop SQL/MX Release 3.0 Supported Release Version Updates (RVUs) This publication supports J06.11 and all subsequent J-series RVUs and H06.22 and all...
  • Page 10 SQL 8402 ° SQL 8411 ° SQL 8419 ° SQL 8834 ° SQL 8837 ° SQL 9215 ° SQL 10003 through SQL 10013 ° SQL 10015 through SQL 10024 ° SQL 10026 through SQL 10029 HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 11 SQL 20371 ° SQL 20733 ° SQL 20752 ° SQL 20755 ° SQL 20759 ° SQL 20779 ° SQL 20795 ° SQL 23001 through SQL 23003 ° SQL 23007 ° SQL 23011 through SQL 23020 HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 12 ° SQL 1295 ° SQL 1311 SQL 1312 ° SQL 1401 ° SQL 1506 ° SQL 2235 ° SQL 3218 ° SQL 3409 ° SQL 3415 ° SQL 4193 ° SQL 4195 SQL 4196 HP NonStop SQL/MX Messages Manual—640324-001 viii...
  • Page 13 ° SQL 10130 through SQL 10141 ° SQL 10150 through SQL 10153 ° SQL 11002 ° SQL 11046 ° SQL 11049 ° SQL 15001 ° SQL 15039 ° SQL 19022 ° SQL 20339 SQL 20340 HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 14 Changed SQL message 8911 to 8917 and updated its description on page 10-54. • Removed SQL message 20240. • Removed SQL messages from 20278 through 20289. • Removed SQL message 25105. • Removed SQL message 25304. HP NonStop SQL/MX Messages Manual—640324-001...

  • Page 15: About This Manual

    About This Manual NonStop SQL/MX is the HP relational database management system based on ANSI SQL-92. It uses the industry standard Structured Query Language (SQL) to define and manipulate data. This manual lists messages produced by NonStop SQL/MX and related subsystems.
  • Page 16 Service Administrative library (MACL) available with the SQL/MX Command Reference conversational interface (MXCI). ODBC/MX Driver for Describes how to install and configure HP NonStop Windows ODBC/MX for Microsoft Windows, which enables applications developed for the ODBC API to use NonStop SQL/MX.
  • Page 17 You can download the Reference, Messages, and Glossary online help by following the instructions mentioned under the SQL/MX Online Help and Sample Programs document. This document can be accessed from the following documentation links available at the HP Business Support Center (BSC), http://www.hp.com/go/nonstop-docs: •...

  • Page 18: Notation Conventions

    $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by HP NonStop SQL/MX Messages Manual—640324-001...

  • Page 19: Notation For Messages

    { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list can be arranged HP NonStop SQL/MX Messages Manual—640324-001...

  • Page 20: Change Bar Notation

    In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. 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 compliments to docsfeedback@hp.com.
  • Page 21 Viewing SQL/MX Messages The message key is a sequential SQL/MX message number that is returned automatically by NonStop SQL/MX when an exception condition occurs. For example, this message might be displayed within your application development tool while you prepare an embedded SQL program: *** ERROR[1000] A syntax error occurred.
  • Page 22 0073 [EGUARDIAN LOCKED] The disk file or record is locked. or invoked using mxci, with the “sh” command and gtacl: >>sh gtacl -c 'error 73'; 0073 [EGUARDIAN LOCKED] The disk file or record is locked. HP NonStop SQL/MX Messages Manual—640324-001 1 -2...

  • Page 23: Contacting Your Service Provider

    NonStop SQL/MX extends the ANSI SQL-92 SQLSTATE values to include other situations not described by the ANSI values. If an ANSI SQL-92 SQLSTATE value exists for an error condition, NonStop SQL/MX returns that value. Otherwise, NonStop SQL/MX returns an SQLSTATE value that is defined by NonStop SQL/MX.
  • Page 24 Process Control Procedure Errors Process Control Procedure Errors HP NonStop Process Services process control procedure errors are numeric codes that indicate errors and other conditions encountered by the process control procedures that are supported by NonStop Process Services. The process control procedures return these codes to callers.

  • Page 25: General Messages (0 Through

    SQL/MX returns this warning to indicate that it has reached the end of rows. Effect. You will not be able to get any more rows from this cursor or SELECT statement. Recovery. This is an informational message. Start a new cursor for a new read. HP NonStop SQL/MX Messages Manual—640324-001 2 -1...
  • Page 26 General Messages (0 through 999) HP NonStop SQL/MX Messages Manual—640324-001 2 -2...
  • Page 27 Effect. The operation fails. Recovery. Enter a valid catalog name (or register the catalog on the node indicated) and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3 -1...
  • Page 28 Effect. The operation fails. Recovery. Check that a constraint named constraint-name exists for the table specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table. HP NonStop SQL/MX Messages Manual—640324-001 3 -2...
  • Page 29 1010 The statement just specified is currently not supported. Cause. The statement that you specified is not available for use. Effect. The operation fails. Recovery. Do not attempt to use this SQL/MX statement. HP NonStop SQL/MX Messages Manual—640324-001 3 -3...
  • Page 30 Cause. You attempted to grant privileges, but you do not have grant options for at least one of them. Effect. NonStop SQL/MX granted some privileges, but not all that you attempted to grant. Recovery. You must have grant options for privileges to grant them.
  • Page 31 1019 No valid primary partition for table-name could be found. Where table-name is the name of an SQL/MX table. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3 -5...
  • Page 32 1021 SQL is already initialized on system node-name. Where node-name is the name of the system on which the INITIALIZE SQL statement was executed. Cause. NonStop SQL/MX has already been initialized on this node. Effect. No operation is performed. Recovery. None needed if SQL is operating normally.
  • Page 33 RESTRICT. Effect. NonStop SQL/MX does not perform the operation. Recovery. For DROP statements that support the CASCADE drop-behavior, you can reissue the statement specifying CASCADE. For other DROP statements, you must first drop each of the dependent objects, then drop the object.
  • Page 34 Cause. A file system error occurred while accessing the file label for Guardian name and the stored row count could not be retrieved. Effect. The operation fails. Recovery. Apply the recovery of the accompanying error message. HP NonStop SQL/MX Messages Manual—640324-001 3 -8...
  • Page 35 1031 Object object-name could not be dropped. Where object-name is the SQL object. Cause. See the accompanying error message for the cause. Effect. NonStop SQL/MX does not drop the object. Recovery. Apply the recovery of the accompanying error message. SQL 1034 1034 SQL/MX was not able to initialize.
  • Page 36 Where node is the name of the node referenced by the operation. Cause. In a replication or distribution context: An operation attempted to create a catalog reference or a partition on a node where NonStop SQL/MX has not been installed.
  • Page 37 Where constraint-name is the name of a column constraint or table constraint. Cause. The columns that constraint-name references in the referenced table are not part of a unique constraint. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 11...
  • Page 38 Cause. The referential constraint is referencing the unique constraint that is declared as deferrable. This is an internal error. Effect. The operation fails. Recovery. Check that the referential constraint references a unique constraint that is not declared deferrable. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 12...
  • Page 39 Cause. Drop behavior CASCADE was specified on a DROP statement that supports only RESTRICT drop behavior. Effect. The operation fails. Recovery. Reissue the DROP statement, specifying RESTRICT or omitting the drop behavior (which will default to RESTRICT). HP NonStop SQL/MX Messages Manual—640324-001 3- 13...
  • Page 40 1052 Constraint cannot be dropped because it does not belong to the specified table. Cause. An ALTER TABLE statement with DROP CONSTRAINT specified a name that is not the name of a constraint on this table. Effect. No constraint is dropped. HP NonStop SQL/MX Messages Manual—640324-001 3- 14...
  • Page 41 Recovery. Check that the object name is correct. If the name is not fully qualified, check that the current schema is set correctly. You can choose a different name, or drop the existing object with this name and then reissue the statement. HP NonStop SQL/MX Messages Manual—640324-001 3- 15...
  • Page 42 Cause. You attempted to drop a table that has a referential constraint or a check constraint that refers to another table. Effect. NonStop SQL/MX does not drop the table. Recovery. Either drop all constraints that refer to other tables and then drop the table, or reissue the DROP TABLE statement, specifying the CASCADE option.
  • Page 43 Cause. An attempt was made to drop a view that is a metadata object. Metadata views and their creation are not currently supported, so this error should not be encountered. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 3- 17...
  • Page 44 1070 Object object-name could not be created. File error: error-number. Where object-name is the name of the SQL/MX object. Where error-number is the file system error number. Cause. An attempt to create object object-name resulted in file system error error-number. HP NonStop SQL/MX Messages Manual—640324-001 3- 18...
  • Page 45 SQL 1073 1073 Only super ID can execute INITIALIZE SQL. Cause. You attempted to initialize NonStop SQL/MX, but you are not the super ID. Only the super ID can perform this function. Effect. The operation fails.
  • Page 46 Where table-name is the name of the metadata table. Where view-name is the name of a view. Cause. NonStop SQL/MX required metadata information about object view-name and was unable to find it in table-name. Effect. The operation fails.
  • Page 47 Cause. 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 NonStop SQL/MX of a column named SYSKEY to ensure uniqueness for the clustering key.
  • Page 48 1085 and error 1041 are returned. SQL 1086 1086 Lock lock-name does not exist. Where lock-name is the name of the specified lock. Cause. Lock lock-name was specified, but does not exist. HP NonStop SQL/MX Messages Manual—640324-001 3- 22...
  • Page 49 1090 Self-referencing constraints are currently not supported. Cause. You attempted to create a self-referencing constraint. A referential constraint is self-referencing if the foreign key is referencing the primary key of the same table. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 23...
  • Page 50 Where object-name is the name of the table being created or changed. Cause. You attempted to create or change a table so that more than one partition has the same first key. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 24...
  • Page 51 1101 Table table-name could not be updated. Where table-name is the ANSI name of the metadata table. Cause. See the accompanying error message for clarification. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 25...
  • Page 52 HORIZONTAL PARTITIONS and STORE BY clauses. Cause. A CREATE TABLE...LIKE statement specifies both the WITH PARTITIONS and STORE BY clause, which is not allowed. Effect. The operation fails. Recovery. Correct the error and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 26...
  • Page 53 Cause. You used WITH CHECK OPTION in the definition of a view that is not updatable. Effect. The operation fails. Recovery. Either make the view updatable or omit the WITH CHECK OPTION and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 27...
  • Page 54 Cause. This error can result from various CREATE statements issued to create the metadata. See the accompanying error messages to determine the cause. Effect. One or more objects are not created. Recovery. See the accompanying error messages for recovery action. HP NonStop SQL/MX Messages Manual—640324-001 3- 28...
  • Page 55 Recovery. None. SQL 1118 1118 Creating object table-name is not allowed in metadata schema. Where table-name is the name of the object. Cause. You attempted to create an object in the metadata schema. HP NonStop SQL/MX Messages Manual—640324-001 3- 29...
  • Page 56 SYSKEY. Where table-name is the name of the table. Cause. You attempted to do an invalid ADD, DROP, or MODIFY of a partition. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 3- 30...
  • Page 57 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 1125 1125 API request version number mismatch. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 31...
  • Page 58 Where description is text further explaining the problem. Cause. Internal error. Effect. NonStop SQL/MX is unable to perform the requested operation. Recovery. None. Report the entire message to your service provider. SQL 1130 1130 The column requires a default value.
  • Page 59 Where column-name is the name of the column in the clustering key. Cause. You attempted to make a column that is not NOT NULL NOT DROPPABLE a part of the clustering key of a table. HP NonStop SQL/MX Messages Manual—640324-001 3- 33...
  • Page 60 Where description is an explanation of the acceptable status values. Cause. This is an internal error in the interface between utilities and the catalog manager. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 34...
  • Page 61 Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for row size limit calculations. Change the column definitions and reissue the statement. HP NonStop SQL/MX Messages Manual—640324-001 3- 35...
  • Page 62 NOT NULL, or has a CHECK, UNIQUE, PRIMARY KEY, or FOREIGN KEY constraint. Cause. Internal error. Effect. NonStop SQL/MX is unable to perform the requested operation. Recovery. None. Contact your service provider. SQL 1143 1143 Validation for constraint constraint-name failed;...
  • Page 63 1145 The catalog name catalog-name is reserved for SQL/MX matadata. Where catalog-name is the name of an SQL/MX catalog. Cause. NonStop SQL/MX reserves certain catalog names for its own use. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for reserved names. Change catalog-name to a name that is not reserved and resubmit.
  • Page 64 Cause. You tried to create a referential constraint on a table column that is the SYSKEY, which is not supported. Effect. The operation fails. Recovery. Do not use the SYSKEY as part of the referenced key. HP NonStop SQL/MX Messages Manual—640324-001 3- 38...
  • Page 65 Cause. When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, NonStop SQL/MX could not generate the location names automatically and, because the CQD POS_RAISE_ERROR is set, the table is not created.
  • Page 66 Where object-name is the name of the object. Cause. NonStop SQL/MX could not create the object because the requested table size is bigger than the total amount of disk space available on the cluster.
  • Page 67 Recovery. Contact your service provider. SQL 1174 1174 An invalid data type was specified for column $0~String0. Where, $0~String0 is the column name. Cause. The data type specification for a column is missing. Effect. The command fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 41...
  • Page 68 Where error is the error returned. Where Guardian name is the name of the file. Cause. See the Guardian Procedure Errors and Messages Manual for a description of file system error error. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 42...
  • Page 69 Cause. See the Guardian Procedure Errors and Messages Manual for a description of file system error error. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 3- 43...
  • Page 70 Cause. The value specified as the default for the column is incompatible with the type of the column. Effect. The operation fails. Recovery. Change either the column data type or the value for the default to be compatible types and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 44...
  • Page 71 1187 The schema name schema-name is reserved for SQL/MX metadata. Where schema-name is the name of an SQL/MX schema. Cause. NonStop SQL/MX reserves certain schema names for its own use. Effect. The operation fails. Recovery. See the SQL/MX Reference Manual for reserved schema names. Choose a name that is not reserved and reissue the CREATE statement.
  • Page 72 Where error-number identifies the error encountered. Cause. Unable to find SQL/MP system catalog table $vol.sql.catalogs. Effect. The operation fails. Recovery. Check that the SQL/MP system catalog table $vol.sql.catalogs exists. If it does, contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 46...
  • Page 73 Cause. An invalid SQL/MP system catalog location was specified or defaulted to. Effect. The operation fails. Recovery. Specify a correct SQL/MP system catalog location, or set the Guardian default system and volume to valid values. HP NonStop SQL/MX Messages Manual—640324-001 3- 47...
  • Page 74 Where file-name is the Guardian file name specified in the CREATE SQL/MP ALIAS command. Where error-number is the Guardian file system error number. Cause. NonStop SQL/MX was unable to obtain file information about file-name. Effect. The operation fails. Recovery. Use the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
  • Page 75 Where table-name is the table being dropped whose DDL was to be saved. Where oss-pathname is the HP NonStop Kernel Open System Services (OSS) pathname of the file to which the DDL was to be saved.
  • Page 76 1235 An invalid combination of EXTENT sizes and MAXEXTENTS was specified for table or index table-name. Cause. A CREATE or ALTER statement specified an invalid combination of EXTENT sizes and MAXEXTENTS. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 3- 50...
  • Page 77 Where file-name is the Guardian file name specified in the ALTER SQL/MP ALIAS command. Where error-number is the Guardian file system error number. Cause. NonStop SQL/MX was unable to obtain file information about file-name. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.
  • Page 78 1242 The character set for string literals in CONSTRAINT must be ISO88591. Cause. You specified a literal with a character set other than ISO88591 in the text of a constraint. Effect. The operation fails. Recovery. Specify only ISO88591 literals in constraints. HP NonStop SQL/MX Messages Manual—640324-001 3- 52...
  • Page 79 Where column-name is the column of object-name that corresponds to the invalid key value. Where object-name is the name of the affected object. Cause. A utility command specified an invalid key value. Effect. The operation fails. Recovery. Specify valid key values and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 53...
  • Page 80 Effect. The UPGRADE operation failed. Recovery. RECOVER must be used to recover from the UPGRADE operation failure. Before attempting the UPGRADE operation again, the failure of insert into log-table-name has to be corrected. HP NonStop SQL/MX Messages Manual—640324-001 3- 54...
  • Page 81 Where index-name is the name of an existing unpopulated index. Cause. An existing index that is not populated has been chosen for a unique or primary constraint, which is not allowed. Effect. The operation fails. Recovery. Populate the index and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 55...
  • Page 82 Cause. You attempted a DDL or utility operation on a database object while operation was in progress for that object’s schema. Effect. The DDL or utility operation fails. Recovery. Wait until the operation has finished, and then retry the DDL or utility operation. HP NonStop SQL/MX Messages Manual—640324-001 3- 56...
  • Page 83 Cause. You specified an unsupported privilege on a procedure or routine in a GRANT statement. Effect. The operation fails. Recovery. Reissue the GRANT statement specifying the valid privilege for the procedure or routine. HP NonStop SQL/MX Messages Manual—640324-001 3- 57...
  • Page 84 1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object. Where object-name is the ANSI name of the affected database object. HP NonStop SQL/MX Messages Manual—640324-001 3- 58...
  • Page 85 $1~Int0 for the file $0~String0. Cause. You specified an insufficient MAXEXTENTS value while creating an index. Effect. The SQL operation completed with a warning. Recovery. This is a warning only. HP NonStop SQL/MX Messages Manual—640324-001 3- 59...
  • Page 86 1277 Unrecognized partitioning scheme for object object-name. Where object-name is the name of the SQL object (table or index). Cause. NonStop SQL/MX does not recognize the partitioning scheme stored in the metadata for the named object. Effect. The named object is considered corrupt and is inaccessible.
  • Page 87 Cause. The data type of the specified default value for the column does not match the column data type. Effect. The command fails. Recovery. Specify a default value of a matching data type for the column. HP NonStop SQL/MX Messages Manual—640324-001 3- 61...
  • Page 88 CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT is ‘OFF.’ Effect. The NO ACTION referential action cannot be defined. Recovery. To alter the behavior of NO ACTION referential action, set the appropriate value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default. HP NonStop SQL/MX Messages Manual—640324-001 3- 62...
  • Page 89 Effect. The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure. Recovery. Correct the error, as reported in the accompanying messages, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 3- 63...
  • Page 90 Where schema is the ANSI name of the schema specified in the CREATE SCHEMA command. Cause. In a CREATE SCHEMA command, you did not specify a LOCATION clause, but NonStop SQL/MX was unable to generate a schema subvolume name that is not already being used by existing schemas. Effect. The operation fails.
  • Page 91 Effect. The operation fails. Recovery. Remove the creation of triggers from the CREATE SCHEMA statement and resubmit. Create triggers in separate statements. SQL 1311 1311 Unable to action-text constraint constraint-name due to the above errors. Where, HP NonStop SQL/MX Messages Manual—640324-001 3- 65...
  • Page 92 Cause. Unable to convert the default value of column column-name from UCS2 to the ISO_MAPPING character-set during the generation of an internal query while processing a DDL command. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 3- 66...
  • Page 93 Cause. A row for object was found in the affected OBJECTS definition schema table, but no corresponding row could be found in the affected REPLICAS definition schema table. Effect. The operation fails. Recovery. Retry the operation. If the error persists, contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 67...
  • Page 94 Where node1 and node2 are the Expand nodes on which schema is visible. Cause. A SCHEMATA row for schema is expected to exist on node1 and node2. However, the SCHEMATA row is not found on node2. Effect. The operation fails. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 3- 68...
  • Page 95 Cause. You attempted to create a column list of referential integrity constraint, which matches the column list of another referential integrity constraint in the table. However, the referential action differs for these two constraints. HP NonStop SQL/MX Messages Manual—640324-001 3- 69...
  • Page 96 SET NULL referential action on it. (OR) The primary key constraint cannot be created on the referencing column with the referential action specified because the primary key cannot be updated. Effect. The operation fails. Recovery. Drop the referential integrity constraint. HP NonStop SQL/MX Messages Manual—640324-001 3- 70...

  • Page 97: Sql/Mx Mxcmp Messages (2000 Through

    Where number is the error number. Where name is the DEFAULTS table name. Where values is the default values file. Cause. NonStop SQL/MX was unable to open system defaults table name because of error number. Effect. NonStop SQL/MX uses either another file or values instead.
  • Page 98 Where detail text is information about the error. Where name is the name of the file. Where number is the line number. Cause. NonStop SQL/MX received an internal error in file name at line number. More information is in detail text. Effect. The operation fails.
  • Page 99 Where number is the error number. Where name is the name of the program file. Cause. NonStop SQL/MX was unable to create a server process because of the process control procedure error number it received while resolving the program file name.
  • Page 100 Where number-1 is the error number. Where number-2 is the TPCError. Where text is the error message text. Cause. NonStop SQL/MX was unable to create server process name because of the process control procedure error number it received. More information appears in detail text.
  • Page 101 Where name is the server process name. Where number is the error number. Cause. NonStop SQL/MX was unable to create server process name because of the process control procedure error number it received on the swap file. Effect. NonStop SQL/MX does not create the server process.
  • Page 102 Where name is the server process name. Cause. NonStop SQL/MX was unable to create server process name because of a library conflict. The process you are trying to create has a different library than the one that is already running.
  • Page 103 2020 Server process name could not be created on node - unlicensed privileged program. Where name is the server process name. Cause. NonStop SQL/MX was unable to create server process name because it is an unlicensed privileged program. The server process was configured incorrectly at installation.
  • Page 104 Where name is the server process name. Where process id identifies the process. Cause. NonStop SQL/MX was unable to create server process name because the CPU is unavailable or does not exist. Effect. The operation fails. Recovery. Check the configuration and the CPU status. Use the messages that accompany this one to diagnose and correct the problem.
  • Page 105 2028 OSS server process name could not be created on node - insufficient resources. Where name is the server process name. Cause. NonStop SQL/MX was unable to create the OSS server process name because there is not enough memory to create this process. Effect. The operation fails.
  • Page 106 Cause. The NonStop SQL/MX process id received process control procedure error number while communicating with server process name. Effect. The NonStop SQL/MX process is not able to communicate with the server process. Recovery. Use the process control procedure error to diagnose and correct the problem.
  • Page 107 2037 receiving process: A message from process sending process was incorrectly formatted and could not be processed. Cause. The NonStop SQL/MX process receiving process received a message from process sending process that was unreadable in some way. Either the message was corrupted by sending process, or an internal error occurred within receiving process.
  • Page 108 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. HP NonStop SQL/MX Messages Manual—640324-001 4- 12...
  • Page 109 Cause. You specified a DEFAULTS attribute name value of data type, which is not supported. The item is being converted to data type, which is supported. Effect. Because of the conversion, the actual value used might be truncated or rounded. HP NonStop SQL/MX Messages Manual—640324-001 4- 13...
  • Page 110 Where name is the cursor name. Cause. You defined the static cursor name twice in this module. Effect. NonStop SQL/MX uses the first static cursor definition. Recovery. This is an informational message only; no corrective action is needed. SQL 2062...
  • Page 111 2065 Statement name was not found in module name. Where name is the statement name. Where name is the module name. Cause. NonStop SQL/MX could not find statement name in module name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
  • Page 112 2066 Cursor name was not found in module name. Where name is the cursor name. Where name is the module name. Cause. NonStop SQL/MX could not find cursor name in module name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
  • Page 113 Cause. In a module definition file, you specified a query statement such as SELECT, INSERT, UPDATE, DELETE, or a DDL statement. These statements must be embedded in procedures. Effect. NonStop SQL/MX is unable to compile the module. Recovery. Correct the syntax and resubmit. SQL 2071...
  • Page 114 HIST_NO_STATS_ROWCOUNT. If you want to use a larger value, increase the value of CQD HIST_NO_STATS_ROWCOUNT first. Note that any change in either of the two values can have an effect on the plan quality. HP NonStop SQL/MX Messages Manual—640324-001 4- 18...
  • Page 115 Where number is the error number. Where name is the name of the file. Cause. NonStop SQL/MX received error number while opening file name for read. Effect. NonStop SQL/MX does not open the file. Recovery. Use the error number to diagnose and correct the problem.
  • Page 116 Where name is the name of the file. Cause. A compilation failed, and for some reason NonStop SQL/MX was not able to purge the module file. Effect. The module file is not valid and should not be used.
  • Page 117 2091 The required module statement was not found in file name. Where name is the name of the file. Cause. NonStop SQL/MX could not find the required module statement in file name. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
  • Page 118 2095 Module file name1, expected to contain module name2, instead contains name3. Where name1, name2, and name3 are module file names. Cause. NonStop SQL/MX expected to find the first module name1, but instead found the second module name2, in file name3. Effect. Only the second module is compiled.
  • Page 119 SQL 2100 2100 Break was received. The compilation has been aborted. Cause. NonStop SQL/MX received a break and aborted the compilation. Effect. NonStop SQL/MX does not continue compilation. Recovery. Informational message only; no corrective action is needed. SQL 2101 2101 Compilation failure due to internal error.
  • Page 120 Use of 'MINIMUM' optimization level, or b) incompatible Control Query Shape specifications. Cause. NonStop SQL/MX was unable to compile this query, either because it was not able to use the MINIMUM optimization level or because you used an incompatible CONTROL QUERY SHAPE specification.
  • Page 121 2106 This statement could not be compiled since it is too long. Break up large statements into smaller pieces. Cause. NonStop SQL/MX was unable to compile this query because it is too long. Effect. NonStop SQL/MX is unable to process this query.
  • Page 122 SQL 2203 2203 Application file application pathname cannot be opened. Cause. You invoked mxCompileUserModule (or mxcmp -a application pathname mdf) on an application that does not exist or is inaccessible to the user. HP NonStop SQL/MX Messages Manual—640324-001 4- 26...
  • Page 123 Effect. The operation fails. Recovery. Verify that you have write access to TMPDIR (the directory where temporary files are created) and that TMPDIR has free space. Delete unused temporary files from TMPDIR and retry the command. HP NonStop SQL/MX Messages Manual—640324-001 4- 27...
  • Page 124 Cause. You invoked mxCompileUserModule using a command-line option allowing a delimited identifier, but the delimited identifier has no closing quote. Effect. The operation fails. Recovery. Make sure that the delimited identifier has a closing quote and retry the command. HP NonStop SQL/MX Messages Manual—640324-001 4- 28...
  • Page 125 Effect. The operation fails. Recovery. Review the module name list syntax, especially where an identifier is expected. Verify that the list of module names are specified correctly and retry the command. HP NonStop SQL/MX Messages Manual—640324-001 4- 29...
  • Page 126 Recovery. Verify that your MXCMP exists and is executable and retry the command. SQL 2221 2221 SQL compiler invocation failed with return code error code. Where error code is the error message code. HP NonStop SQL/MX Messages Manual—640324-001 4- 30...
  • Page 127 Compiler encountered a file system error error-num. It may produce a plan that is suboptimal or of incompatible version. Where nodename is the name of the node such as \system.$data_volume.$data_subvolume on which the failure occurred. HP NonStop SQL/MX Messages Manual—640324-001 4- 31...
  • Page 128 2984 -g moduleLocal may not specify an OSS or Guardian directory. Where moduleLocal is a Guardian or OSS directory. Cause. The user as specified an Expand directory. Effect. Compilation failed because of a syntax error. HP NonStop SQL/MX Messages Manual—640324-001 4- 32...
  • Page 129 SQL/MX MXCMP Messages (2000 through 2999) Recovery. Specify a valid Guardian or OSS directory. HP NonStop SQL/MX Messages Manual—640324-001 4- 33...
  • Page 130 SQL/MX MXCMP Messages (2000 through 2999) HP NonStop SQL/MX Messages Manual—640324-001 4- 34...

  • Page 131: Parser And Compilation Messages (3000 Through

    3002 column name is not a valid column reference; it has more than 4 name parts. Cause. You specified an invalid column reference, which must have four or fewer parts. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5 -1...
  • Page 132 Cause. You attempted to declare a dynamic cursor in a way that does not match the statement. Both must be literals or both must be string host variable expressions. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5 -2...
  • Page 133 Cause. You specified character set name that is not supported for use in an SQL/MX object, such as a table or module. Examples include creating a KANJI or KSC5601 column in an SQL/MX table. HP NonStop SQL/MX Messages Manual—640324-001 5 -3...
  • Page 134 Recovery. Correct the syntax and resubmit. SQL 3014 3014 Precision of numeric, value, cannot exceed 18. Cause. You defined a numeric item, value, with precision greater than 18, which is not supported. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5 -4...
  • Page 135 Recovery. Redefine the item with a precision value of 18 or less. SQL 3015 3015 Scale value cannot exceed precision value. Cause. You defined a scale value with greater precision than NonStop SQL/MX allows. Effect. The operation fails. Recovery. Redefine the scale with a precision value less than or equal to the allowable value.
  • Page 136 SQL 3019 3019 An unsigned number was expected within the parentheses, not value. Cause. You specified an unexpected value, value. NonStop SQL/MX requires an unsigned number. Effect. The operation fails. Recovery. Replace the value with an unsigned number and resubmit.
  • Page 137 Cause. You attempted to perform a COLLATE clause in a sort specification, which is not supported. Effect. NonStop SQL/MX ignores the COLLATE clause. Recovery. Remove the COLLATE clause and resubmit. SQL 3024 3024 The MATCH PARTIAL clause is not yet supported.
  • Page 138 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. NonStop SQL/MX 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 139 3034 The PARTITION clause in the ALTER TABLE statement is not yet supported. Cause. You used the PARTITION clause in the ALTER TABLE statement, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5 -9...
  • Page 140 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. HP NonStop SQL/MX Messages Manual—640324-001 5- 10...
  • Page 141 SQL 3042 3042 UPSHIFT for a numeric type is not valid. Cause. You specified UPSHIFT for a numeric type, which is not supported. Effect. The operation fails. Recovery. Change the specification and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 11...
  • Page 142 Cause. You specified an invalid time value. Effect. The operation fails. Recovery. Correct the time value and resubmit. SQL 3047 3047 The timestamp ‘value’ is not valid. Cause. You specified an invalid timestamp value. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 12...
  • Page 143 3051 Duplicate HEADING clauses were specified in column definition name. Cause. You defined column name with more than one HEADING clause. Effect. The operation fails. Recovery. Define the column with only one HEADING clause and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 13...
  • Page 144 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3055 3055 Duplicate DELETE rules were specified. Cause. You defined duplicate DELETE rules. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 14...
  • Page 145 Recovery. See the SQL/MX Reference Manual for correct size values, and resubmit. SQL 3060 3060 The specified percentage value in the DSLACK clause is not valid. Cause. You provided an invalid percentage value in the DSLACK clause. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 15...
  • Page 146 Recovery. Correct the syntax and resubmit. SQL 3064 3064 Duplicate ISLACK clauses were specified in the PARTITION clause. Cause. You specified duplicate ISLACK clauses in the PARTITION clause. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 16...
  • Page 147 Cause. You defined a primary key as droppable in a table that includes STORE BY PRIMARY KEY in its definition, which is not supported. Effect. NonStop SQL/MX is unable to process this definition. Recovery. Change the definition of the primary key constraint so that it is NOT DROPPABLE.
  • Page 148 Recovery. Correct the syntax and resubmit. 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. HP NonStop SQL/MX Messages Manual—640324-001 5- 18...
  • Page 149 3078 The LOCKLENGTH clause is not allowed in the ALTER INDEX ... ATTRIBUTE(S) statement. Cause. You specified an ALTER INDEX...ATTRIBUTE(S) statement that includes the LOCKLENGTH clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 19...
  • Page 150 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3083 3083 Duplicate [NO]AUDITCOMPRESS clauses were specified. Cause. You specified duplicate [NO]AUDITCOMPRESS clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 20...
  • Page 151 3087 The [NO]COMPRESS clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. Cause. You specified an ALTER TABLE...ATTRIBUTE(S) statement that includes the [NO]COMPRESS clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 21...
  • Page 152 3091 The [NO]AUDIT clause is not allowed in the CREATE INDEX statements. Cause. You specified a CREATE INDEX statement with the [NO]AUDIT clause, which is not supported. Effect. NonStop SQL/MX ignores the CREATE INDEX statement. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 22...
  • Page 153 Cause. You specified a statement with duplicate [NO]ICOMPRESS clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3096 3096 Duplicate [NO]SERIALWRITES clauses were specified. Cause. You specified a statement with duplicate [NO]SERIALWRITES clauses. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 23...
  • Page 154 Recovery. Correct the syntax and resubmit. SQL 3100 3100 Duplicate DSLACK clauses were specified. Cause. You specified a statement with duplicate DSLACK clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 24...
  • Page 155 CREATE TABLE statement. Cause. You specified a CREATE TABLE statement with incorrect syntax. Only the ADD option is supported in a PARTITION clause. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 25...
  • Page 156 Cause. You specified a statement with both LIKE and STORE BY clauses, which is not supported. Effect. The operation fails. Recovery. Correct the statement to include one of these clauses. HP NonStop SQL/MX Messages Manual—640324-001 5- 26...
  • Page 157 3112 The LIKE clause and PARTITION clause cannot coexist in the same statement. Cause. You specified a statement with both LIKE and PARTITION clauses, which is not supported. Effect. The operation fails. Recovery. Correct the statement to include one of these clauses. HP NonStop SQL/MX Messages Manual—640324-001 5- 27...
  • Page 158 Recovery. Correct the syntax and resubmit. SQL 3116 3116 Duplicate transaction access mode clauses were specified. Cause. You specified a statement with duplicate access mode clauses. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 28...
  • Page 159 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3121 3121 Partitioned entry-sequenced tables are not yet supported. Cause. You specified an SQL/MP partitioned entry-sequenced table, which is not supported. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 29...
  • Page 160 Where object name is the identifier. Cause. You used an identifier that is a reserved word. You must put it between double quotes (") to use it as an identifier. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 30...
  • Page 161 Effect. 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 NonStop SQL/MX. Effect. The operation fails. Recovery. None. SQL 3132 3132 The HEADING for column name exceeds the maximum size of 128 characters.
  • Page 162 3136 Only LEFT, RIGHT, and FULL OUTER JOIN are valid in {oj ...} Cause. You attempted to perform an invalid outer join. Only LEFT, RIGHT, and FULL OUTER JOIN are supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 32...
  • Page 163 DDL statement. Cause. You attempted to perform an INSERT, UPDATE, DELETE, or DDL statement with a READ UNCOMMITTED isolation level, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 33...
  • Page 164 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 NonStop SQL/MX. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 165 Actual query results will likely not match expected results. Where value is the environment variable value specified. Cause. NonStop SQL/MX is ignoring the environment variable you specified. Query results might not match expected results. Effect. None. Recovery. Informational message only; no corrective action is needed.
  • Page 166 Recovery. Correct the syntax and resubmit. SQL 3157 3157 A catalog name is required. Cause. You attempted to create a catalog without specifying a catalog name. Effect. The operation fails. Recovery. Specify a catalog name and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 36...
  • Page 167 Cause. You declared host variable more than once in the procedure parameter list. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 37...
  • Page 168 SQL 3162 3162 Procedure parameter name was not used. Where name is the name of the procedure parameter. Cause. NonStop SQL/MX did not use procedure parameter name. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 3163 3163 Host variable name appears more than once in the INTO list.
  • Page 169 3168 The FOR ... ACCESS clause is not allowed in a CREATE VIEW statement. Cause. You specified a CREATE VIEW statement with the FOR ... ACCESS clause, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 39...
  • Page 170 SQL 3173 3173 UPDATE STATISTICS is not allowed in a compound statement. Cause. You specified a compound statement that contains an UPDATE STATISTICS command. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 40...
  • Page 171 Where name is the name of the character set. Cause. You specified a character set with an odd number of characters in the length declaration of the data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 41...
  • Page 172 Recovery. Correct the syntax and resubmit. SQL 3181 3181 Specified name is not a valid three part ANSI name. Cause. You specified an invalid logical name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 42...
  • Page 173 3185 SIGNAL parameter 3 must be of type string. Cause. You attempted a SIGNAL statement with a third parameter that is not a quoted string. Effect. The operation fails. Recovery. Specify a parameter that is a quoted string and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 43...
  • Page 174 3186 string: Dynamic parameters and host variables are currently not allowed in DDL. Where string is the dynamic parameter or host variable that was specified. Cause. NonStop SQL/MX does not support the use of dynamic parameters or host variables in DDL statements. Effect. The operation fails.
  • Page 175 3192 Union operands table1 and table2 have different access/lock modes. Cause. NonStop SQL/MX 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 176 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 3202 3202 PARAMETER STYLE clause is required. Cause. In the CREATE PROCEDURE statement, you omitted the mandatory PARAMETER STYLE clause. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 46...
  • Page 177 3204 EXTERNAL NAME clause is badly formed. Cause. In the CREATE PROCEDURE statement, the EXTERNAL NAME clause you specified does not conform to the required syntax. Effect. NonStop SQL/MX is unable to create the procedure. Recovery. Correct the syntax and resubmit. SQL 3205 3205 EXTERNAL NAME clause is required.
  • Page 178 Cause. You attempted a CREATE TABLE table name (columnname longwvarchar(N)) where N current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery. Increase the CREATE TABLE statement’s longwvarchar column width N or decrease the current MIN_LONG_WVARCHAR_DEFAULT_SIZE setting and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 48...
  • Page 179 Cause. You attempted a CREATE TABLE table name (columnname long varchar(N) where N current MIN_LONG_VARCHAR_DEFAULT_SIZE setting. Effect. The operation fails. Recovery. Decrease the CREATE TABLE statement’s long varchar column width N or increase the current MIN_LONG_VARCHAR_DEFAULT_SIZE setting and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 49...
  • Page 180 SQL 3218 3218 A table reference cannot contain DELETE or UPDATE in a CREATE VIEW statement. Cause. A CREATE VIEW statement was issued with a DELETE or UPDATE operation as a table reference. HP NonStop SQL/MX Messages Manual—640324-001 5- 50...
  • Page 181 Cause. In a CREATE PROCEDURE statement, you specified the optional DYNAMIC RESULT SETS clause with an invalid value. Effect. The operation fails. Recovery. Remove the clause or use a value between zero and 255 and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 51...
  • Page 182 Where location-name specifies the physical location name of an SQL/MX object. Cause. SHOWLABEL was given an invalid physical location as an argument. Effect. SHOWLABEL does not display output. Recovery. Reissue the command with a valid location name. HP NonStop SQL/MX Messages Manual—640324-001 5- 52...
  • Page 183 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 NonStop SQL/MX. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 5- 53...
  • Page 184 Cause. You cannot specify the logical partition name in the LOCATION clause of the create statement of catalog, procedure, view and materialized view object types. Effect. The operation fails. Recovery. Remove the logical partition name syntax from the LOCATION clause and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 5- 54...
  • Page 185 3406 A DDL statement could not be translated into a statement consisting of single-byte characters for processing. Cause. The DDL statement coded in unicode contains non-ISO88591 characters. NonStop SQL/MX does not support arbitrary unicode characters. Effect. The operation fails. Recovery. Remove non-ISO88591 characters and resubmit.
  • Page 186 Parser and Compilation Messages (3000 through 3999) HP NonStop SQL/MX Messages Manual—640324-001 5- 56...

  • Page 187: Binder And Compilation Messages (4000 Through

    4001 Column name1 is not found. Tables in scope: name2. Default schema: name3. Cause. You referenced column name1, which NonStop SQL/MX could not find. The table name2 or tables in the scope of the column reference and the default schema name3 appear.
  • Page 188 Table name2 not exposed. Tables in scope: name3. Default schema: name4. Cause. You referenced column name1, which NonStop SQL/MX could not find. Table name2 is not exposed. The table name3 or tables in the scope of the column reference and the default schema name4 appear.
  • Page 189 4008 A subquery is not allowed inside an aggregate function. Cause. You specified a subquery within an aggregate function, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6 -3...
  • Page 190 4011 Reference made to column name via star (*) is ambiguous. Where name is the name of the column. Cause. You referred to column name using the SELECT * or SELECT TBL.* reference, and NonStop SQL/MX could not locate the column because the reference is ambiguous. Effect. The operation fails.
  • Page 191 Cause. You specified a statement in which the number of derived columns (value1) does not equal the degree of the derived table (value2). They must be equal. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6 -5...
  • Page 192 Arithmetic operations on row value constructors are not allowed. Cause. You attempted to perform an arithmetic operation on row value constructors, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6 -6...
  • Page 193 The column list is optional, but if you use it, you must explicitly specify values for columns that do not have default values. HP NonStop SQL/MX Messages Manual—640324-001 6 -7...
  • Page 194 4025 Error while preparing constraint name on table table name. Where table name is the name of the table. Cause. NonStop SQL/MX received an error while preparing constraint name on table name. See accompanying error messages. Effect. The operation fails.
  • Page 195 4032 Column name has an unknown class, class. It is neither a system column nor a user column. Cause. You specified column name with an unknown class. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6 -9...
  • Page 196 DateTime or Interval type. Cause. You specified a source field of the EXTRACT function that is not a DATETIME or INTERVAL data type. Effect. The operation fails. Recovery. Correct the source field type and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 10...
  • Page 197 Cause. You specified operands for a BETWEEN predicate that are not of equal degree, which is required. Effect. The operation fails. Recovery. Correct the syntax so that the operands are of equal degree and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 11...
  • Page 198 4044 Collation name1 does not support the name2 predicate or function. Cause. You specified collation name1, which does not support the predicate or function listed in the message. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 12...
  • Page 199 BOOLEAN, not type. Cause. You specified the third operand of a ternary comparison argument with an invalid type. The type must be boolean. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 13...
  • Page 200 4052 The second operand of function name must be numeric. Cause. You specified the first operand of function name with a type other than numeric, which is required. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 14...
  • Page 201 Cause. You specified correlation name1, which conflicts with a qualified identifier of table name2. For example: SELECT * FROM tblx, tblz, tblx; Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 15...
  • Page 202 SQL 4062 4062 The preceding error actually occurred in function name. Cause. NonStop SQL/MX detected an error in function name. Errors that appear before this one refer to the low level computations that this function uses. Effect. The operation fails.
  • Page 203 4067 The operands of function name must be character data types. Cause. You specified invalid operands for function name. They must be operands of type character. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 17...
  • Page 204 4071 The first operand of function name must be a datetime. Cause. You specified an invalid operand for function name. It must be datetime. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 18...
  • Page 205 Cause. You attempted to divide by zero in constant expression name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 4076 4076 Overflow occurred in constant expression name. Cause. There is an overflow in constant expression name. HP NonStop SQL/MX Messages Manual—640324-001 6- 19...
  • Page 206 Recovery. Correct the syntax and resubmit. SQL 4080 4080 SQL/MP error: number text. Cause. NonStop SQL/MX has received error number from SQL/MP. Effect. The operation fails. Recovery. Use the error number and text to determine the problem. HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 207 Binder and Compilation Messages (4000 through 4999) SQL 4081 4081 SQL/MP error: number Cause. NonStop SQL/MX has received error number from SQL/MP. Effect. The operation fails. Recovery. Use the error number to determine the problem. SQL 4082 4082 Object name does not exist or is inaccessible.
  • Page 208 4088 The number of values in each TRANSPOSE item of a TRANSPOSE set must be equal. Cause. You specified a TRANSPOSE set with an unequal number of values in each TRANSPOSE item. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 22...
  • Page 209 SQL 4094 4094 The number of output host variables (value1) must equal the number of selected values (value2). Cause. NonStop SQL/MX requires that the number of output host variables, value1, match the number of selected values, value2. Effect. The operation fails.
  • Page 210 4099 A NULL operand is not allowed in predicate name. Cause. You included a NULL operand in predicate name, which is not supported. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 24...
  • Page 211 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 NonStop SQL/MX to treat object name as an ambiguous entity. Effect. The operation fails.
  • Page 212 Recovery. Replace the double quotes with single quotes. SQL 4105 4105 Translation name is not recognized. Cause. NonStop SQL/MX does not recognize the translation name. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Use one of the supported translation names.
  • Page 213 >>select x from (select a, runningcount(b) from T1 sequence by a) T2(x,y) where y > 10; >>select count(*) from t1 sequence by b group by a having runningsum(a) > count(*); Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 6- 27...
  • Page 214 ORDER BY (if you intend to order the result set.) For example: >>select a from T1 sequence by a; *** ERROR[4111] The query contains a SEQUENCE BY clause but no sequence functions. *** ERROR[8822] Unable to prepare the statement. HP NonStop SQL/MX Messages Manual—640324-001 6- 28...
  • Page 215 Absolute and relative sampling cannot occur in the same BALANCE expression. Cause. You attempted to perform absolute and relative sampling in the same balance expression, which is not supported. Effect. NonStop SQL/MX is unable to prepare the query. Recovery. Correct the syntax and resubmit. SQL 4113 4113 The sample size for type Sampling must be size type.
  • Page 216 +>FOR UPDATE OF UPDATE_FLAG ; *** ERROR[4001] Column UPDATE_FLAG is not found. Tables in scope: A. Default schema: CAT.SCH. *** ERROR[4117] The cursor query expression may be nonupdatable. *** ERROR[8822] Unable to prepare the statement. HP NonStop SQL/MX Messages Manual—640324-001 6- 30...
  • Page 217 B.UPDATE_FLAG END = 'N' +>AND A.ACC_TYPE = B.ACC_TYPE AND A.PROD_CODE = B.PROD_CODE +>FOR UPDATE OF UPDATE_FLAG ; *** ERROR[4118] The cursor query expression is not updatable. *** ERROR[8822] Unable to prepare the statement. HP NonStop SQL/MX Messages Manual—640324-001 6- 31...
  • Page 218 4123 NULL cannot be cast to a NOT NULL data type. Cause. You attempted to cast NULL to a NOT NULL data type. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 6- 32...
  • Page 219 SQL 4124 4124 More than one table will be locked: name. Where name is the name of the table. Cause. NonStop SQL/MX is preparing to lock more than one table. Effect. None. Recovery. Informational message only; no corrective action is needed.
  • Page 220 4128 Default volume and subvolume information could not be retrieved from =_DEFAULTS define - DEFINEINFO error number. Where number is the error message. Cause. NonStop SQL/MX was not able to retrieve default volume and subvolume information using the =_DEFAULTS define. Effect. The operation fails.
  • Page 221 SQL 4134 4134 The operation (name) is not allowed. Try UNION ALL instead. Cause. You attempted to perform an operation that NonStop SQL/MX does not allow. Effect. The operation fails. Recovery. Try a UNION ALL operation and resubmit. SQL 4135 4135 In an INSERT-SELECT, each column in the ORDER BY clause must be one of the columns in the selected list of the query.
  • Page 222 SQL 4152 4152 Table name cannot be both read and updated. Cause. You attempted to read from and update the same table. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4153 4153 Statement may not compile due to an order requirement on stream expression.
  • Page 223 Tables in scope: name. Cause. You attempted to perform a left join using the result set of a stream expression as the inner relation. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4158 4158 Join of stream expressions is not supported.
  • Page 224 4161 Embedded INSERT, UPDATE, or DELETE statement is not allowed in a UNION operation. Tables in scope: table-names1, table-names2. Where table-names1 and table-names2 are names of NonStop SQL/MX tables that are in scope. Cause. You attempted to perform a UNION operation that has embedded an INSERT, UPDATE, or DELETE statement.
  • Page 225 Tables in scope: name. Cause. You attempted to perform a right join using a stream expression as the outer relation. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4166 4166 ORDER BY clause is not supported in UNION of two streams.
  • Page 226 DECLARE ... FOR UPDATE clause. Cause. You attempted to perform a DECLARE... FOR UPDATE clause that included an embedded DELETE statement. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4170 4170 Stream expressions are not supported for insert statements.
  • Page 227 Cause. The SQL/MX compiler could not reorder the join tree because the JOIN_ORDER_BY_USER directive is in effect. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Disable the JOIN_ORDER_BY_USER directive and resubmit. SQL 4175 4175 Join between embedded name1 expression and embedded name2 expression is not supported.
  • Page 228 Cause. You attempted to perform a rollback that included an update of a variable length column. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4179 4179 SEQUENCE BY is not supported for stream expressions.
  • Page 229 Cause. The HAVING predicate refers to a renamed column in the select list. Effect. The statement does not compile. Recovery. Correct the column name in the HAVING predicate. HP NonStop SQL/MX Messages Manual—640324-001 6- 43...
  • Page 230 4200 Stream expressions are not supported for compound statements. Cause. You attempted to use a stream expression for a compound statement. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4201 4201 Embedded name expression is not supported for compound statements.
  • Page 231 IUD_NONAUDITED_INDEX_MAINT is set to WARN. This message appears as an warning. Effect. NonStop SQL/MX performs the INSERT, UPDATE, or DELETE operation. If the operation encounters an error, you will see other messages about that condition. Recovery. Informational message only; no corrective action is needed.
  • Page 232 View: name2. Cause. You attempted to perform an embedded action that is supported only for updatable views. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4207 4207 Index name and other indexes covering a subset of columns do not cover all output values of stream.
  • Page 233 IF statement. Cause. You attempted to embed UPDATE/DELETE statements within an IF statement. Effect. NonStop SQL/MX is unable to compile the statement. Recovery. Modify the statement and resubmit. SQL 4212 4212 table name cannot be used to satisfy order requirement on the stream because it is partitioned.
  • Page 234 Cause. You attempted to use the THIS function in context other than inside a ROWS SINCE function. Effect. The operation fails. Recovery. Correct the NonStop SQL/MX statement and resubmit. SQL 4302 4302 Procedure procedure-name expects value1 parameters but was called with value2 parameters.
  • Page 235 OUT or INOUT parameter that is neither a host variable nor a dynamic parameter. Effect. The SQL/MX statement is not compiled. Recovery. Correct the SQL/MX statement. Supply a host variable or a dynamic parameter for OUT or INOUT parameters, and retry the compilation. HP NonStop SQL/MX Messages Manual—640324-001 6- 49...
  • Page 236 Cause. In the SQL/MX statement being compiled, a CALL statement was present within a BEGIN...END block. Effect. The SQL/MX statement is not compiled. Recovery. Remove the CALL statement from the compound statement and retry the compilation. HP NonStop SQL/MX Messages Manual—640324-001 6- 50...
  • Page 237 SELECT list. For example, it cannot be part of the subquery. Cause. You tried to use the USER(x) function somewhere other than the outermost SELECT clause. This function is not yet fully supported. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 6- 51...
  • Page 238 PARTITIONING_KEY clause of KEY_RANGE_COMPATRE function. SQL 4334 4334 KEY_RANGE_COMPARE is not allowed on views. Cause. KEY_RANGE_COMPARE function cannot be used on views. Effect. The operation failed. Recovery. Use KEY_RANGE_COMPARE function on tables or indexes. HP NonStop SQL/MX Messages Manual—640324-001 6- 52...
  • Page 239 Table in scope: table-names. Where, operation is an INSERT operation. table-names are the names of the NonStop SQL/MX tables that are in scope. Cause. You attempted a join operation using an embedded INSERT statement. Effect. The operation failed. Recovery. Modify the statement and resubmit.
  • Page 240 Cause. ASC/DESC was specified in the expression of the RANK sequence function. Effect. The statement fails to prepare. Recovery. Rewrite the query so that it does not contain ASC/DESC in the argument of the RANK sequence function. HP NonStop SQL/MX Messages Manual—640324-001 6- 54...

  • Page 241: Normalizer Messages (5000 Through

    Normalizer Messages (5000 through 5999) SQL 5000 5000 Internal error in the query normalizer. Cause. The optimizer received an internal error during query normalization. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 7 -1...
  • Page 242 Normalizer Messages (5000 through 5999) HP NonStop SQL/MX Messages Manual—640324-001 7 -2...

  • Page 243: Optimizer Messages (6000 Through

    CLEAR option in UPDATE STATISTICS. Cause. You have manually modified the metadata table, and now it contains invalid values. Effect. NonStop SQL/MX is unable to complete compilation. Recovery. Undo your changes using the CLEAR option in UPDATE STATISTICS. HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 244 Cause. You have manually modified the metadata table, and now it contains an invalid boundary value. Effect. NonStop SQL/MX uses default histograms to compile the query. Therefore, these might not be the best plans generated. Recovery. Undo your changes using the CLEAR option in UPDATE STATISTICS and regenerate the statistics.
  • Page 245 Effect. This is a warning message. SQL/MX optimizer has reached the set threshold and the query plan generated might be sub-optimal. As a result, there may be a slow execution of the query. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 8 -3...
  • Page 246 Optimizer Messages (6000 through 6999) HP NonStop SQL/MX Messages Manual—640324-001 8 -4...

  • Page 247: Generator Messages (7000 Through

    WHERE clause in the SELECT statement. This query does not satisfy these conditions. Effect. NonStop SQL/MX is unable to compile the query. Recovery. Rewrite the query (for example, using nested queries) so that cluster sampling is performed on a base table with no WHERE-clause predicate.
  • Page 248 Generator Messages (7000 through 7999) HP NonStop SQL/MX Messages Manual—640324-001 9 -2...

  • Page 249: Executor Messages (8000 Through

    Executor Messages (8000 through 8999) SQL 8001 8001 An internal executor error occurred. Cause. NonStop SQL/MX has received an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8002 8002 The current nowaited operation is not complete.
  • Page 250 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 8009 8009 Schema name name is not valid. Where name is the name of the schema. Cause. You specified an invalid schema name. HP NonStop SQL/MX Messages Manual—640324-001 10- 2...
  • Page 251 Where catalog name1 is the name of the catalog. Where schema name2 is the name of the schema. Cause. NonStop SQL/MX displays the default catalog and schema names. Effect. None. Recovery. This is an informational message only; no corrective action is needed.
  • Page 252 Upgrade that system. SQL 8017 8017 Explain information is not available for this query. Cause. The explain default has been turned off for this query. Effect. NonStop SQL/MX is not able to display explain information. HP NonStop SQL/MX Messages Manual—640324-001 10- 4...
  • Page 253 Recovery. In the SQL/MX R3.0, the only way to reset the row count is to delete all the rows from the table. Alternatively, the INSERT…SELECT statements can be used to move the data from the table with the invalid row count to another table. The target HP NonStop SQL/MX Messages Manual—640324-001 10- 5...
  • Page 254 8102 The operation is prevented by a unique constraint. Cause. You attempted to perform an operation that is prevented by a unique constraint. Effect. NonStop SQL/MX could not perform the operation. Recovery. Make the data you enter unique to be consistent with the constraint. SQL 8103 8103 The operation is prevented by referential integrity constraint name1 on table name2.
  • Page 255 FETCH and UPDATE/DELETE...WHERE CURRENT... of statements. Cause. The last row fetched by the cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT statements and is no longer available. HP NonStop SQL/MX Messages Manual—640324-001 10- 7...
  • Page 256 Effect. The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure. Recovery. Correct the error, as reported in the accompanying messages, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10- 8...
  • Page 257 Where name is the fully qualified Guardian file name of an SQL/MX anchor file. Cause. The named anchor file contains invalid data. Effect. NonStop SQL/MX uses data from the anchor file to locate the system schema tables on a node. Without a valid anchor file, it is not possible to compile or execute queries that use SQL/MX metadata on the anchor file’s Expand node.
  • Page 258 If the INTO clause is incorrect, use a cursor to select and fetch the data. Use an INTO clause only when you expect one row to satisfy the SELECT statement. If the subquery is incorrect, rewrite the SELECT query. HP NonStop SQL/MX Messages Manual—640324-001 10 -10...
  • Page 259 8404 The trim character argument of function TRIM must be one character in length. Cause. You specified a TRIM function with an invalid trim character argument, which must be one character in length. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 10 -11...
  • Page 260 Cause. You specified a LIKE pattern whose syntax is incorrect. An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character. Effect. The operation fails. Recovery. Check your input data and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10 -12...
  • Page 261 Recovery. Check your input data and resubmit. SQL 8414 8414 The attempted conversion is not supported on this platform. Cause. You attempted to perform a conversion that is not supported on this platform. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 10 -13...
  • Page 262 Recovery. Check your input data and resubmit. SQL 8416 8416 A datetime expression evaluated to an invalid datetime value. Cause. NonStop SQL/MX has encountered a datetime expression that, when evaluated, is invalid. Effect. The operation fails. Recovery. Check your input data and resubmit.
  • Page 263 Recovery. Check your input and resubmit. SQL 8423 8423 The provided field number is not valid. Cause. You specified a field number that is not valid. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10 -15...
  • Page 264 8428 The argument to function name is not valid. Where name is the name of the function. Cause. You specified an invalid argument for the function name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10 -16...
  • Page 265 SQL 8429 8429 The preceding error actually occurred in function name. Cause. NonStop SQL/MX detected an error in the function name. Errors will appear before this one that refer to low-level computations that this function uses. Effect. The operation fails.
  • Page 266 8551 Error NSK err was returned by the file system on object- name. Where NSK err is the HP NonStop Kernel error returned. Where object-name is the name of the object. Cause. The file system returned error NSK err on object-name.
  • Page 267 Cause. The system does not have enough memory to build the query. Effect. The operation fails. Recovery. Try to reduce the system's load by entering fewer statements. You can try restarting NonStop SQL/MX. If this does not correct the problem, contact your service provider. SQL 8571 8571 SQL/MX could not allocate sufficient memory to execute query.
  • Page 268 Cause. While you had table name open, another operation such as DDL changed that table. Effect. The table is no longer open. You will see this message if NonStop SQL/MX was unable to recompile your statement. Recovery. Reopen the table and start again.
  • Page 269 SQL 8575 8575 Timestamp mismatch on table name. Where name is the name of the table. Cause. Table name has been changed, and NonStop SQL/MX was not able to recompile this statement. Effect. The operation fails. Recovery. Verify what has changed in the file and recompile this program.
  • Page 270 Cause. Insufficient memory was available to perform the join operation. Effect. The operation fails. Recovery. Contact HP support for assistance in recompiling the query with Unique In-Memory Hash Joins turned off (control query default UNIQUE_HASH_JOINS 'OFF'), and re-execute.
  • Page 271 8604 Transaction subsystem name returned error number while starting a transaction. Where name is the subsystem name. Where number is the error number. Cause. Transaction subsystem name has returned error number while starting a transaction. HP NonStop SQL/MX Messages Manual—640324-001 10 -23...
  • Page 272 Recovery. Correct the syntax so that the sequence of events is correct, and resubmit. SQL 8608 8608 Transaction subsystem name returned error number on rollback transaction. Where name is the name of the subsystem. HP NonStop SQL/MX Messages Manual—640324-001 10 -24...
  • Page 273 8612 Transaction mode cannot be set if the transaction is already running. Cause. You attempted to set the transaction mode, but the transaction is already running. Effect. The operation fails. Recovery. Abort and restart the transaction if you must change its mode. HP NonStop SQL/MX Messages Manual—640324-001 10 -25...
  • Page 274 Effect. The operation fails. Recovery. The application that started the transaction must perform a commit or rollback. NonStop SQL/MX must start any transactions it will later commit or rollback. SQL 8614 8614 SQL cannot begin a transaction when multiple contexts exist.
  • Page 275 Recovery. Change the module-name to refer to the correct user module and retry the operation. SQL 8801 8801 Descriptor allocation failed because the descriptor already exists in the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -27...
  • Page 276 Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8806 8806 Trying to action a statement that is not allocated with AllocStmt() call. Cause. This is an internal error. HP NonStop SQL/MX Messages Manual—640324-001 10 -28...
  • Page 277 SQL 8808 8808 Module file name contains corrupted or invalid data. Where name is the name of the file. Cause. NonStop SQL/MX has detected corrupted or invalid data in the module file name. Effect. NonStop SQL/MX could not execute the file.
  • Page 278 Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8815 8815 An internal error occurred while building the TCB tree when executing the statement. Cause. This is an internal error. HP NonStop SQL/MX Messages Manual—640324-001 10 -30...
  • Page 279 Recovery. None. Contact your service provider. SQL 8816 8816 An internal error occurred while executing the TCB tree. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -31...
  • Page 280 Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8821 8821 Rollback transaction failed during the process of fetching the statement. Cause. This is an internal error. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 10 -32...
  • Page 281 Recovery. Make sure a module name is passed into the module ID structure. SQL 8825 8825 Module is already added into the current context. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -33...
  • Page 282 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. NonStop SQL/MX ran out of memory while creating the internal structure name. Effect. The operation fails. Recovery. Increase NonStop SQL/MX's memory and resubmit. SQL 8829...
  • Page 283 Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8834 8834 The SQL installation directory could not be found. Operating system error number. Where number is the error number. HP NonStop SQL/MX Messages Manual—640324-001 10 -35...
  • Page 284 Executor Messages (8000 through 8999) Cause. NonStop SQL/MX was unable to find the SQL/MX installation directory and received an operating system error number. Effect. The operation fails. Recovery. Locate the SQL/MX installation directory, correct your syntax, and resubmit. SQL 8835 8835 Invalid SQL descriptor information requested.
  • Page 285 SQL. This transaction needs to be committed or aborted by calling SQL COMMIT or ROLLBACK WORK. Cause. NonStop SQL/MX started a transaction that was committed or aborted by an embedded program, rather than by NonStop SQL/MX. Effect. The operation fails.
  • Page 286 SQL, has now been cleaned up. Cause. After NonStop SQL/MX started a transaction that was committed or aborted by an embedded program, rather than from NonStop SQL/MX, you used SQL COMMIT or ROLLBACKWORK to properly finish the transaction.
  • Page 287 SQL 8847 8847 An error occurred while trying to retrieve SQL/MP metadata information. Cause. NonStop SQL/MX received an error while trying to retrieve SQL/MP metadata information. Effect. The operation fails. Recovery. Use the errors that accompany this one to diagnose and correct the problem, and resubmit.
  • Page 288 Executor Messages (8000 through 8999) SQL 8851 8851 A CLI Parameter bound check error occurred. Cause. NonStop SQL/MX received a CLI parameter bound check error. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8852 8852 Holdable cursors are supported for only streaming cursors and embedded update/delete cursors.
  • Page 289 8860 Module file name has an obsolete module header. Where name is the file name. Cause. The module file name has an obsolete module header. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10 -41...
  • Page 290 8864 Module file name has an obsolete descriptor entry. Where name is the file name. Cause. The module file name has an obsolete descriptor entry. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 10 -42...
  • Page 291 SQL 8867 8867 An error while reading from file name. Where name is the file name. Cause. NonStop SQL/MX encountered an error while reading the module file name. Effect. The operation fails. Recovery. Rebuild the module file and resubmit. SQL 8868 8868 SQL cannot create a new context when current transaction is implicitly started by SQL.
  • Page 292 8872 New operations cannot be executed while another NOWAIT operation is pending. Cause. Only one nowait operation at a time is allowed on an SQL/MX statement. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -44...
  • Page 293 Cause. The CONTROL QUERY DEFAULT value for DOOM_USERTRANSACTION is ON, and NonStop SQL/MX encountered an unrecoverable error. Effect. The transaction is in a doomed state. Users are unable to continue work on this transaction.
  • Page 294 Cause. The server failed to enable UDR violation checking prior to issuing an SQL/MX CLI function call to check or clear the UDR violation flags. Effect. The operation fails. Recovery. This is an internal error in the SQL/MX UDR server. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -46...
  • Page 295 8889 The provided buffer to retrieve Result Set proxy syntax is either null or not big enough. Cause. The NonStop SQL/MX call-level interface (CLI) function was unable to provide a proxy syntax for a stored procedure result set because the provided target buffer is either null or not big enough.
  • Page 296 Cause. A value that was passed into an SQL/MX CLI function containing a reserved parameter was not the value expected by NonStop SQL/MX. Effect. The CLI function fails. Recovery. None. Contact your service provider.
  • Page 297 Effect. The operation fails. Recovery. None. Contact your service provider. SQL 8898 8898 An internal error occurred in CLI. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 10 -49...
  • Page 298 Where process name is the name of an SQL/MX UDR server process. Cause. NonStop SQL/MX received an interrupt signal, possibly caused by an MXCI user pressing Ctrl-C while the SQL/MX UDR server was executing a stored procedure. Effect. The operation fails, and if PROCESS_STOP_ was successful (as indicated by a return value of 0), the SQL/MX UDR server is stopped.
  • Page 299 8904 SQL/MX did not receive a reply from MXUDR, possibly caused by internal errors while executing user-defined routines. Cause. During execution of an SQL/MX statement, NonStop SQL/MX did not receive an expected reply from the SQL/MX UDR server. Effect. The operation fails.
  • Page 300 8913 The PREPARE operation is not allowed on a stored procedure result set. Cause. A CLI application attempted to dynamically prepare an SQL statement, and the statement identifier is associated with a stored procedure result set. HP NonStop SQL/MX Messages Manual—640324-001 10 -52...
  • Page 301 CALL statement. max-result-sets is the maximum number of result sets that can be returned from the associated CALL statement. HP NonStop SQL/MX Messages Manual—640324-001 10 -53...
  • Page 302 Cause. A call-level interface (CLI) application attempted to bind multiple stored procedure result set statements to the same result set index. Effect. The operation fails. Recovery. None. Contact GMCSC and report this condition. HP NonStop SQL/MX Messages Manual—640324-001 10 -54...

  • Page 303: Update Statistics Messages (9200 Through

    Effect. NonStop SQL/MX is unable to continue processing. Recovery. Resubmit the statement. If this does not correct the problem, stop and restart NonStop SQL/MX. If this does not correct the problem, report the entire message to your service provider. SQL 9202 9202 UPDATE STATISTICS has located previously generated histograms that are not being regenerated.
  • Page 304 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. Cause. NonStop SQL/MX could not perform an UPDATE STATISTICS statement because you are not authorized to perform this operation against this table. You must either own the object name or be the super ID.
  • Page 305 Cause. An UPDATE STATISTICS statement was unable to access column definitions. Effect. The operation fails. Recovery. Resubmit the statement. If this does not correct the problem, stop and restart NonStop SQL/MX. If this does not correct the problem, report the entire message to your service provider. SQL 9209 9209 Column name does not exist in object name.
  • Page 306 Effect. NonStop SQL/MX is unable to continue processing. Recovery. Resubmit the statement. If this does not correct the problem, stop and restart NonStop SQL/MX. If this does not correct the problem, report the entire message to your service provider. SQL 9215 9215 UPDATE STATISTICS encountered an internal error (from location with return value=errorcode).
  • Page 307 Cause. The user-specified sample table has some data records in it and is not empty. If the sample table is not empty, the UPDATE STATISTICS command might not be able to populate it. This could also corrupt the statistics collected by the command. HP NonStop SQL/MX Messages Manual—640324-001 11- 5...
  • Page 308 The USING SAMPLE TABLE clause is supported for SQL/MX tables only. Effect. The operation fails. Recovery. Specify a SQL/MX table name. For running the UPDATE STATISTICS command on a SQL/MP table, do not use the USING SAMPLE TABLE clause. HP NonStop SQL/MX Messages Manual—640324-001 11- 6...

  • Page 309: Executor Sort And Scratch File I/O Messages (10000 Through

    Recovery. Do not attempt recovery. Contact your service provider. SQL 10005 10005 Sort encountered an unexpected error. Cause. An unknown sort error occurred. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12- 1...
  • Page 310 Recovery. Do not attempt recovery. Contact your service provider. SQL 10011 10011 Sort failed while reading a scratch file with error system error. Where system error is the error returned. Cause. An I/O error occurred during a scratch file I/O operation. HP NonStop SQL/MX Messages Manual—640324-001 12- 2...
  • Page 311 Recovery. None. This is an internal error. Contact your service provider. 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 your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12- 3...
  • Page 312 Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. Contact your service provider. SQL 10020 10020 Sort failed while calling FILENAME_FINDFINISH_ with error number. Cause. An error occurred while calling a system level call. HP NonStop SQL/MX Messages Manual—640324-001 12- 4...
  • Page 313 Recovery. Contact your service provider. SQL 10024 10024 Sort failed while calling SETMODE_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12- 5...
  • Page 314 Effect. The operation fails. Recovery. Contact your service provider. SQL 10029 10029 Sort failed while calling FILE_GETINFO_ with error number. Cause. An error occurred while calling a system level call. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 12- 6...
  • Page 315 Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10034 10034 Sort Error: Create File failed. Cause. An error occurred while calling a system level call. HP NonStop SQL/MX Messages Manual—640324-001 12- 7...
  • Page 316 Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10039 10039 Sort Error: Sort Error:ResetEvent failed. Cause. An error occurred while calling a system level call. HP NonStop SQL/MX Messages Manual—640324-001 12- 8...
  • Page 317 Recovery. No recovery possible. Contact your service provider. SQL 10043 10043 Sort Error: Write Failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12- 9...
  • Page 318 10047 Sort Error: Wrong length read. Cause. The length of the data returned was not what was expected. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12 -10...
  • Page 319 10051 Io to scratch file failed while calling CONTROL with error $0~int0. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12 -11...
  • Page 320 10103 operator failed to close a scratch file. FILE_CLOSE_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is a SQL/MX platform internal procedure-error number. HP NonStop SQL/MX Messages Manual—640324-001 12 -12...
  • Page 321 Recovery. Contact your service provider to diagnose the cause of the READX returned error and correct the problem. SQL 10110 10110 operator failed to alter a scratch file. SETMODE returned error number. Where, HP NonStop SQL/MX Messages Manual—640324-001 12 -13...
  • Page 322 Cause. The query operator failed to set the current position in a scratch file. Effect. The operation fails. Recovery. None. This is an internal error. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12 -14...
  • Page 323 Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. Cause. An invocation of FILE_GETINFOLISTBYNAME_ failed. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 12 -15...
  • Page 324 10118 operator encountered an error while searching for a scratch disk. FILENAME_FINDSTART_ returned error number. Where, operator is the SQL/MX query operator that encountered the error; for example: merge join. number is an SQL/MX platform internal procedure-error number. HP NonStop SQL/MX Messages Manual—640324-001 12 -16...
  • Page 325 Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10132 10132 Scratch I/O Error: GetTempFileName failed. Cause. An error occurred while calling a system level call. HP NonStop SQL/MX Messages Manual—640324-001 12 -17...
  • Page 326 Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. SQL 10137 10137 Scratch I/O Error: WaitForMultipleObjects failed. Cause. An error occurred while calling a system level call. HP NonStop SQL/MX Messages Manual—640324-001 12 -18...
  • Page 327 Recovery. No recovery possible. Contact your service provider. SQL 10141 10141 Scratch I/O Error: GetDiskFreeSpace failed. Cause. An error occurred while calling a system level call. Effect. The operation fails. Recovery. No recovery possible. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12 -19...
  • Page 328 SQL/MX query operator that encountered the error; for example: merge join. Cause. The query operator attempted to read a nonexistent block of data from a scratch file. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 12 -20...
  • Page 329 SQL/MX query operator that encountered the error; for example: merge join. Cause. The mapping of data blocks to scratch files is incomplete. Effect. The operation fails. Recovery. None. This is an internal error. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 12 -21...
  • Page 330 Executor Sort and Scratch File I/O Messages (10000 Scratch File I/O Messages through 10199) HP NonStop SQL/MX Messages Manual—640324-001 12 -22...

  • Page 331: Messages (11000 Through

    Where TriggerName is the name of one of the triggers in the triggering cycle. Where TableName is the subject table name of trigger TriggerName. Cause. During execution, a trigger was generated recursively more than 16 times. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13- 1...
  • Page 332 Cause. You attempted to specify a statement granularity for a BEFORE trigger, which is not supported. Effect. The operation fails. Recovery. Either specify a row granularity or do not specify a granularity. Row granularity is the default for BEFORE triggers. HP NonStop SQL/MX Messages Manual—640324-001 13- 2...
  • Page 333 Recovery. If SET or SIGNAL does not work, determine whether an AFTER trigger is more appropriate for your application. If an AFTER trigger cannot be used, you will need to implement the action in your application. HP NonStop SQL/MX Messages Manual—640324-001 13- 3...
  • Page 334 Recovery. Add an action to the trigger statement and use a supported action for the trigger. Before triggers support only SET and SIGNAL operations, while AFTER triggers support INSERT, UPDATE, DELETE, and SIGNAL operations. HP NonStop SQL/MX Messages Manual—640324-001 13- 4...
  • Page 335 Cause. You attempted to create a trigger that had a triggered action with a SET operation that attempted to update or access a column that is not part of the subject table table-name. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13- 5...
  • Page 336 Effect. The operation fails. Recovery. Drop all triggers defined on the table and operation that caused the error. For example, if the operation is a DELETE, drop all DELETE triggers defined on the HP NonStop SQL/MX Messages Manual—640324-001 13- 6...
  • Page 337 Recovery. Drop all the triggers defined on the table and operation that caused the error. For example, if the operation is a DELETE, drop all DELETE triggers defined on the DELETE statement target table. If the triggers cannot be dropped, do not attempt these operations. HP NonStop SQL/MX Messages Manual—640324-001 13- 7...
  • Page 338 Cause. You attempted to drop or alter a trigger that does not exist. Effect. The operation fails. Recovery. None, if the name of the trigger was entered correctly. Otherwise, correct the trigger name and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 13- 8...
  • Page 339 Where table-name is the name of the specified table. Cause. You attempted to “alter trigger enable/disable all of” on a table that does not have triggers. Effect. This is a warning only. The operation succeeds. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 13- 9...
  • Page 340 SQL 11042 11042 Trigger name already exists. Where name is the name of the trigger you are trying to create. Cause. You attempted to create a trigger that already exists. HP NonStop SQL/MX Messages Manual—640324-001 13 -10...
  • Page 341 Cause. You attempted to create a trigger, which resulted in circular dependency. Effect. The operation fails. Recovery. None. You cannot create a trigger that creates a circular dependency. HP NonStop SQL/MX Messages Manual—640324-001 13 -11...
  • Page 342 SQL/MX UDR server data structure was determined to be invalid. Effect. The request message is rejected and the SQL/MX statement fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 13 -12...
  • Page 343 SQL 11110 11110 MXUDR: Unexpected error during message processing: string. Cause. The SQL/MX UDR server encountered an internal error. Details appear in the message text. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13 -13...
  • Page 344 11113 MXUDR: Internal error: An unexpected UNLOAD request arrived for UDR handle handle. Where handle is an internal identifier generated by NonStop SQL/MX and used in messages to and from the SQL/MX UDR server. Cause. The SQL/MX UDR server received a request out of sequence.
  • Page 345 Correct the class file or the method and resubmit. SQL 11205 11205 Java class class-file-name was not found in external path path-name. Cause. The class file did not exist in the given directory. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13 -15...
  • Page 346 Cause. In a CREATE PROCEDURE statement, the list of parameter types specified in the EXTERNAL NAME clause was not enclosed in parentheses. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13 -16...
  • Page 347 SQL parameter list or in the EXTERNAL NAME clause. Effect. The operation fails. Recovery. Correct the parameters in the parameter list or in the EXTERNAL NAME clause, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 13 -17...
  • Page 348 Cause. A null value was supplied as input to a stored procedure in Java and the corresponding Java data type is a primitive type that does not support null values. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13 -18...
  • Page 349 Recovery. Review the Java method. Determine whether it is appropriate in your application for this exception to be thrown or whether it should be caught and handled by your user-defined routine. Retry the SQL/MX statement. HP NonStop SQL/MX Messages Manual—640324-001 13 -19...
  • Page 350 11221 Language Manager is out of memory string. Cause. The language manager could not acquire enough memory to complete its work on the SQL/MX statement. Effect. The operation fails. Recovery. Stop and restart the session and retry the SQL/MX statement. HP NonStop SQL/MX Messages Manual—640324-001 13 -20...
  • Page 351 11225 Specified signature is invalid. Reason: The Java signature for a Java main method must be (java.lang.string[]). Cause. In a CREATE PROCEDURE statement, an invalid Java signature was used in the EXTERNAL NAME clause. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 13 -21...
  • Page 352 Effect. If this is an error, the SQL/MX statement fails. If this is a warning, floating-point data is truncated or floating-point precision is reduced. Recovery. Increase the field size of the receiving field. HP NonStop SQL/MX Messages Manual—640324-001 13 -22...
  • Page 353 SPJ method by specifying that method's Java type signature in the EXTERNAL NAME clause, and then resubmit. SQL 11231 11231 The method method-name(signature) was not found in or is not a public method of class-name. Where signature is a Java type signature. HP NonStop SQL/MX Messages Manual—640324-001 13 -23...
  • Page 354 Java class, but the method had a return type other than void. Effect. The operation fails. Recovery. Correct the signature of the SPJ method, and then resubmit. HP NonStop SQL/MX Messages Manual—640324-001 13 -24...
  • Page 355 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 11236 11236 Stored procedure procedure-name attempted to return too many result sets.
  • Page 356 BLOB and CLOB, are not native data types in SQL/MX and are not supported as stored procedure result set column types. Effect. The operation fails. Recovery. Change the SPJ method, which will not return result sets containing large object data. HP NonStop SQL/MX Messages Manual—640324-001 13 -26...
  • Page 357 The JDBC/MX driver's interface version is ver2 and the expected version is ver1 or lower. Where procedure-name is the ANSI name of a stored procedure. Where ver1 and ver2 are the SPJ RS interface version numbers of the JDBC/MX driver. HP NonStop SQL/MX Messages Manual—640324-001 13 -27...
  • Page 358 Recovery. Do not attempt recovery. Contact your service provider. SQL 11244 11244 The Language Manager encountered invalid character data in column column-number of a java.sql.ResultSet row. Where column-number is the column number in the result set row. HP NonStop SQL/MX Messages Manual—640324-001 13 -28...
  • Page 359 DECIMAL value at the specified column position because the value contained a character other than a digit. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 13 -29...
  • Page 360 Trigger, UDR Server, and Language Manager Messages (11000 through 11399) HP NonStop SQL/MX Messages Manual—640324-001 13 -30...

  • Page 361: Sqlc And Sqlco Preprocessor Messages (13000 Through

    Effect. The operation fails. Recovery. None. If the problem persists, contact your service provider. SQL 13004 13004 No error. Cause. The preprocessor has executed successfully. Effect. None. Recovery. Informational message only; no corrective action is needed. HP NonStop SQL/MX Messages Manual—640324-001 14- 1...
  • Page 362 -c out-file where out-file specifies the name of the preprocessed output source file containing the translated embedded SQL/MX statements. If you are preparing a C++ application, specify the name with the .cpp extension. HP NonStop SQL/MX Messages Manual—640324-001 14- 2...
  • Page 363 C/C++ source file and the SQL/MX module definition file. timestamp overrides the default operating system timestamp. HP NonStop SQL/MX Messages Manual—640324-001 14- 3...
  • Page 364 SQL 13015 13015 The module definition file name could not be opened. Cause. The preprocessor was unable to open the module definition file name. Effect. The preprocessor ignores the referenced module definition file. HP NonStop SQL/MX Messages Manual—640324-001 14- 4...
  • Page 365 Cause. You specified the statement name, which is a reserved name in SQLC. Effect. The preprocessor ignores the statement name. Recovery. Change the name to one that does not conflict with SQLC's reserved names. See the SQL/MX Reference Manual for a list of reserved names. HP NonStop SQL/MX Messages Manual—640324-001 14- 5...
  • Page 366 Recovery. Remove the duplicate definition and resubmit. SQL 13024 13024 Cursor name was not declared. Cause. The cursor name, which you attempted to use, has not been declared. Effect. The preprocessor ignores the cursor. HP NonStop SQL/MX Messages Manual—640324-001 14- 6...
  • Page 367 13999) Recovery. Declare the cursor and resubmit. SQL 13025 13025 Warning(s) near line number. Cause. NonStop SQL/MX received warnings near line number. Effect. None. Recovery. Informational message only; no corrective action is needed. SQL 13026 13026 The EXEC SQL MODULE statement must precede any cursor definitions or executable SQL statements.
  • Page 368 Cause. You specified input host variables for cursor name. An open cursor does not need host variables. Effect. The preprocessor ignores the host variables you specified for this cursor. Recovery. Remove the host variables and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14- 8...
  • Page 369 13036 C/C++ syntax error in switch/for/while condition near line number. Cause. The preprocessor encountered a C/C++ syntax error near line number. Effect. The preprocessor ignores the switch/for/while condition. Recovery. Correct the syntax error and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14- 9...
  • Page 370 13040 A ")" was expected near line number. Cause. The preprocessor requires a right parenthesis near line number. Effect. The preprocessor ignores the parenthetical statement. Recovery. Correct the syntax by adding a right parenthesis or removing an extra left parenthesis. HP NonStop SQL/MX Messages Manual—640324-001 14 -10...
  • Page 371 13044 Type specification syntax name is not a recognized type near - line number. Cause. You specified an unrecognized type specification near line number. Effect. The preprocessor ignores the type specification. Recovery. Replace this type specification with one that is recognized. HP NonStop SQL/MX Messages Manual—640324-001 14 -11...
  • Page 372 Recovery. Remove the redefinition and resubmit. SQL 13049 13049 Input file is not good near line number. Cause. The preprocessor could not read the input file. Effect. The preprocessor ignores the input file. HP NonStop SQL/MX Messages Manual—640324-001 14 -12...
  • Page 373 Cause. Cursor name was not opened or closed. Effect. The cursor could not be used. Recovery. Open the cursor. SQL 13054 13054 Cursor name is not fetched or closed. Cause. Cursor name was not fetched or closed. Effect. None. HP NonStop SQL/MX Messages Manual—640324-001 14 -13...
  • Page 374 Cause. The preprocessor was unable to open the SQL CLI header file name. Effect. The preprocessor ignores the SQL CLI header file. Recovery. Verify that the SQL CLI header file exists and is readable, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -14...
  • Page 375 SQL 13063 13063 Identifier name is not defined - near line number. Cause. Identifier name was not defined near line number. Effect. The preprocessor ignores the identifier. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -15...
  • Page 376 13066 Identifier name was expected to be a structure type - near line number. Cause. The identifier name you specified was expected to be a structure type near line number. Effect. The preprocessor ignores the identifier. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -16...
  • Page 377 Recovery. Verify that the file exists and is readable and resubmit. SQL 13068 13068 A C/C++ syntax error was found - near line number. Cause. NonStop SQL/MX detected a C/C++ syntax error near the line number listed in the message. Effect. The operation fails.
  • Page 378 Module Group Specification String (MGSS), Module TableSet Specification String (MTSS), or Module Version Specification String (MVSS). If module name is longer than 128 characters HP NonStop SQL/MX Messages Manual—640324-001 14 -18...
  • Page 379 Effect. The schema name is invalid, and this error is generated. Recovery. Reinvoke the preprocessor, this time supplying an embedded SQL source file that has a valid schema name in its MODULE directive. HP NonStop SQL/MX Messages Manual—640324-001 14 -19...
  • Page 380 -g moduleCatalog=module catalog name>. • -g moduleSchema = module schema name>. • -g moduleGroup = module group specification string>. • -g moduleTableSet = module tableset specification string>. • -g moduleVersion= module version specification string>. HP NonStop SQL/MX Messages Manual—640324-001 14 -20...
  • Page 381 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 13505 13505 Source input file name cannot be opened. Cause. NonStop SQL/MX could not open the source input file name. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 14 -21...
  • Page 382 SQL 13508 13508 Expecting keyword, found keyword. Cause. You did not enter the keyword or character that NonStop SQL/MX required. When the preprocessor is processing the code within a control block such as IF, WHILE, DO, or is at the end of one, it looks for the keyword that ends that block and...
  • Page 383 Recovery. Correct the syntax and resubmit. SQL 13509 13509 Expecting keyword1 after keyword2, found keyword3. Cause. You did not enter the keyword that NonStop SQL/MX was expecting. When the preprocessor encounters certain keywords, it expects them to be followed by other specific keywords. For example:...
  • Page 384 SQL 13513 13513 The BIT data type is not implemented in SQL/MX. Cause. You specified the BIT data type, which is not supported in NonStop SQL/MX. Effect. The operation fails. Recovery. Specify a data type that NonStop SQL/MX supports.
  • Page 385 Recovery. Correct the syntax and resubmit. SQL 13516 13516 Unexpected end of input file encountered after line number. Cause. NonStop SQL/MX reached the end of the input file while processing EXEC SQL. Effect. The operation fails. Recovery. Correct the input file and resubmit.
  • Page 386 Recovery. Correct the syntax and resubmit. SQL 13522 13522 DECLARE SECTION cannot be nested. Cause. You specified the DECLARE SECTION as nested code. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -26...
  • Page 387 13526 Line number, variable name: clause type clause is not valid for a host variable, Cause. You specified a clause type JUST or OCCURS clause for variable name on line number. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -27...
  • Page 388 SQL 13800 13800 Line number: name is not a valid character set name. Cause. You specified an invalid character set name at line number. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 14 -28...

  • Page 389: Mxci Messages (15000 Through 15999)

    Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15004 15004 Error number on change directory attempt to directory. Cause. NonStop SQL/MX has received error number while attempting to change directory. Effect. The operation fails. Recovery. Correct the error and resubmit.
  • Page 390 Recovery. Correct the syntax and resubmit. SQL 15006 15006 Error number while reading from file. Cause. NonStop SQL/MX received error number while reading from a file. The error number depends on the operating system. Effect. The operation fails. Recovery. Use the error number to diagnose and correct the problem.
  • Page 391 Recovery. See the documentation for the topic. SQL 15010 15010 The help file could not be opened. Cause. NonStop SQL/MX was unable to open the help file. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem.
  • Page 392 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15016 15016 PARAM name not found. Cause. NonStop SQL/MX did not find parameter name. Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 15017 15017 Statement name not found.
  • Page 393 15020 The USING list must contain at least one parameter value. Cause. You specified an EXECUTE command with a USING clause, but you did not specify parameter values. NonStop SQL/MX requires at least one parameter value. Effect. The operation fails. Recovery. Correct the syntax and resubmit.
  • Page 394 Recovery. Correct the syntax and resubmit. SQL 15026 15026 Break rejected. Cause. A break you specified to cancel an SQL/MX statement failed. Effect. The operation fails. Recovery. None. Report the entire message to your service provider. HP NonStop SQL/MX Messages Manual—640324-001 15- 6...
  • Page 395 SQL 15031 15031 The specified define does not exist. Cause. You attempted to use a define that does not exist. Effect. The operation fails. Recovery. Correct the define name or add it, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15- 7...
  • Page 396 Recovery. Correct the file name and resubmit. SQL 15035 15035 Permission denied to access this file. Cause. NonStop SQL/MX was unable to access the file. Effect. The operation fails. Recovery. Check the file permissions and reset them if necessary. SQL 15036 15036 Specified file has an inappropriate filecode or an invalid function argument was specified.
  • Page 397 Effect. The action fails, and this message provides information about the failure. Recovery. Correct the problem defined by the first error message displayed for the event; which is usually the most meaningful for recovery action. HP NonStop SQL/MX Messages Manual—640324-001 15- 9...
  • Page 398 If provided, also see lower-level error messages for additional information. Using an appropriate MACL INFO command, check the status of the target object or related object for indication of a problem. HP NonStop SQL/MX Messages Manual—640324-001 15 -10...
  • Page 399 SQL 15216 15216 SUBSYSTEM: EVAR already defined, library call function- name failed. +++SUGG: Look at existing EVARs with \"INFO EVAR *, TYPE xxx>\". Where function-name is the name of the library function called. HP NonStop SQL/MX Messages Manual—640324-001 15 -11...
  • Page 400 Where function-name is the name of the library function called. Cause. The service is not in the started state. Effect. The command and subsequent subsystem call fails. Recovery. Start the service and enter the command again. HP NonStop SQL/MX Messages Manual—640324-001 15 -12...
  • Page 401 15222 SUBSYSTEM: Unspecified problem, library call function- name failed. Where function-name is the name of the library function called. Cause. Unknown. Effect. The command and subsequent subsystem call fails. Recovery. See the lower-level error messages issued with this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -13...
  • Page 402 Cause. The command is missing the second of its two required parameters. Effect. The operation fails. Recovery. The command displays valid object types in a second message. Enter the command again providing the second parameter. HP NonStop SQL/MX Messages Manual—640324-001 15 -14...
  • Page 403 Cause. A string with single or double quotation mark (SQL identifier or literal) is missing the terminating mark. Effect. The operation fails. Recovery. Enter the command with the correct terminating single or double quotation mark. HP NonStop SQL/MX Messages Manual—640324-001 15 -15...
  • Page 404 15234 Opening quote was matched but following separator not correct, command had: string1. Where string1 displays the start of the error. Note. As of the ABU SPR, this message is no longer generated. HP NonStop SQL/MX Messages Manual—640324-001 15 -16...
  • Page 405 Where string0 is the portion of the input following the problem. Cause. You entered an extra comma instead of a value. Effect. The operation fails. Recovery. Enter the value instead of a comma and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -17...
  • Page 406 +++SUGG: Remove the duplicate keyword (and value). Where attribute-name is the name of the duplicate attribute. Cause. A duplicate attribute is in the command. Effect. The operation fails. Recovery. Enter the command without the duplicate attributes. HP NonStop SQL/MX Messages Manual—640324-001 15 -18...
  • Page 407 Where invalid-char is the invalid character. Where string1 is the name and value of the attribute. Cause. The attribute value is invalid. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -19...
  • Page 408 15256 A user name must have two components: groupname.membername. Cause. The user name field does not contain both the group and member name. Effect. The operation fails. Effect. Enter the command with a group and member name. HP NonStop SQL/MX Messages Manual—640324-001 15 -20...
  • Page 409 Where string2 is the component with too many characters. Cause. Too many characters are in the component. Effect. The operation fails. Recovery. Enter the command with a reduced number of characters in the component specified in the error. HP NonStop SQL/MX Messages Manual—640324-001 15 -21...
  • Page 410 Where string1 is the missing component name. Cause. The component is not specified in a previous command. Effect. The operation fails. Recovery. Enter the command with the proper component name. Do not use an asterisk (*) wild card. HP NonStop SQL/MX Messages Manual—640324-001 15 -22...
  • Page 411 Where fname is the file name. Where string1 is the name component as entered. Cause. The component name is not valid. Effect. The operation fails. Recovery. Enter the command with the correct component name for the command issued. HP NonStop SQL/MX Messages Manual—640324-001 15 -23...
  • Page 412 +++SUGG: Omit key value or look for missing comma. Where string1 is the attribute name and value. Cause. The attribute value is not specified as OFF. Effect. The operation fails. Recovery. Enter the command with the attribute value off. HP NonStop SQL/MX Messages Manual—640324-001 15 -24...
  • Page 413 Where string1 is the attribute name and value. Cause. The attribute value entered is greater than the maximum allowed value. Effect. The operation fails. Recovery. Enter the command with the attribute value smaller or equal to the maximum allowed value. HP NonStop SQL/MX Messages Manual—640324-001 15 -25...
  • Page 414 Cause. A quoted string is concatenated with a different type of quoted string; for example, a single quoted string with a double quoted string. Effect. The operation fails. Recovery. Retry the command using the same type of quote characters for concatenation. HP NonStop SQL/MX Messages Manual—640324-001 15 -26...
  • Page 415 Cause. A component of the object name starts with a blank or tab character. Names with a leading space are not valid. Effect. The operation fails. Recovery. Enter the command without a space at the start of the component name, or use an underscore character. HP NonStop SQL/MX Messages Manual—640324-001 15 -27...
  • Page 416 15284 USAGE: Valid commands are: ADD, ALTER, DELETE, INFO, START, STOP, VERSION. Cause. The command contains an invalid first parameter. Effect. The operation fails. A preceding message states the problem, and this message lists valid parameters when mode macl is set. HP NonStop SQL/MX Messages Manual—640324-001 15 -28...
  • Page 417 Effect. The operation fails. A preceding message states the problem, and this message lists valid DELETE command objects when mode macl is set. Recovery. Select a valid object type from the list as the object type for this command. HP NonStop SQL/MX Messages Manual—640324-001 15 -29...
  • Page 418 Effect. The operation fails. A preceding message states the problem, and this message lists valid VERSION command objects when mode macl is set. Recovery. Select “service” as the object type for this command. HP NonStop SQL/MX Messages Manual—640324-001 15 -30...
  • Page 419 Cause. The object name did not have the correct format. Effect. The operation fails. A preceding message states the problem, and this message shows the valid syntax for an object name. Recovery. Enter the command using the correct syntax. HP NonStop SQL/MX Messages Manual—640324-001 15 -31...
  • Page 420 Where function-name is the client library function name. Cause. The DS is in an active state with a service. Effect. The operation fails. Recovery. Enter the STOP DS * command. Use the wild card * for the service name. HP NonStop SQL/MX Messages Manual—640324-001 15 -32...
  • Page 421 15310 SUBSYSTEM: SQL error from LowLayer, library call function-name failed. Where function-name is the client library function name. Cause. An SQL failure occurs in a lower client library. Effect. The operation fails. Recovery. Retry the command using the correct syntax. HP NonStop SQL/MX Messages Manual—640324-001 15 -33...
  • Page 422 Recovery. See the Guardian Procedure Errors and Messages Manual. SQL 15314 15314 SUBSYSTEM: SERVER not found here, library call function-name failed. Where function-name is the client library function name. Cause. The server is not found on the system. HP NonStop SQL/MX Messages Manual—640324-001 15 -34...
  • Page 423 Cause. The data source is not currently available to make any changes. Effect. The operation fails. Recovery. Wait for the data source to fully transition to a stable state, then enter the command. HP NonStop SQL/MX Messages Manual—640324-001 15 -35...
  • Page 424 Where function-name is the client library function name. Cause. The client library fails to enable or disable tracing. Effect. The operation fails. Recovery. Check your MXCS service process (MXOAS). It might not be responding. HP NonStop SQL/MX Messages Manual—640324-001 15 -36...
  • Page 425 See information about this error in the EMS collector for MXCS service event messages, which is specified on the mxoas start command with $0 as the default. HP NonStop SQL/MX Messages Manual—640324-001 15 -37...
  • Page 426 Where service-name is the name of the service where the operation is to be performed. Cause. The lower level cannot return status for the service. The system could be busy. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -38...
  • Page 427 15331 CFG Trace file name is too long. Should be limited to 30 char. Cause. The file name given for the trace file is to long. Effect. The operation fails. Recovery. Enter the command, specifying a shorter trace file name. HP NonStop SQL/MX Messages Manual—640324-001 15 -39...
  • Page 428 Cause. Server name is other than an asterisk (*) wild card to specify the DS selection attribute. Effect. The operation fails. Recovery. Run the INFO SERVER command using the asterisk (*) wild card for the server name when specifying the DS attribute. HP NonStop SQL/MX Messages Manual—640324-001 15 -40...
  • Page 429 Effect. The operation fails. Recovery. Run the INFO SERVICE * command to verify that the service exists, and then retry the failed command. See the lower-level error messages issued with this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -41...
  • Page 430 Recovery. Check the spelling of the server name and verify that it is a valid name. Enter the command with the correct server name. If the error persists, verify that the server is operational. HP NonStop SQL/MX Messages Manual—640324-001 15 -42...
  • Page 431 DS. Effect. The operation fails. Recovery. Check the status of the service. See the lower-level error messages issued with this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -43...
  • Page 432 DS and also fails to get attribute information from the database. Either the name contains a type, needs double quotes, or the DS might not exist. Effect. The operation fails. Recovery. Issue the INFO DS* command to determine if the DS exists. HP NonStop SQL/MX Messages Manual—640324-001 15 -44...
  • Page 433 Recovery. See the lower-level error messages that follow this message. SQL 15370 15370 Could not set CPU list on DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. HP NonStop SQL/MX Messages Manual—640324-001 15 -45...
  • Page 434 15374 DS name AND SERVICE name can not both be a wild card. +++SUGG: Specify either a DS name or a SERVICE name on command line. Cause. Both the data source and service names are asterisks. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -46...
  • Page 435 15378 Can not delete the default DS, string1. Where string1 is the data source name. Cause. Removing the TDM_Default_DataSource data source is not allowed. Effect. The operation fails. Recovery. Recovery is not required. HP NonStop SQL/MX Messages Manual—640324-001 15 -47...
  • Page 436 Effect. The operation fails. Recovery. Use the INFO SERVICE* command to see the existing service. If the specific service does not exist, create a service or try a different service that is in a started state. HP NonStop SQL/MX Messages Manual—640324-001 15 -48...
  • Page 437 15386 Could not enable trace for DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -49...
  • Page 438 Where string1 is the data source name. Cause. Idle server count is too large. Effect. The operation fails. Recovery. Either increase the maximum server count or decrease the idle server count of the data source. HP NonStop SQL/MX Messages Manual—640324-001 15 -50...
  • Page 439 15392 Could not stop DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -51...
  • Page 440 15396 Could not get automatic start option for DS string1. Where string1 is the data source name. Cause. A failure occurs in the client library. Effect. The operation fails. Recovery. See the lower-level error messages that follow this message. HP NonStop SQL/MX Messages Manual—640324-001 15 -52...
  • Page 441 Recovery. If the error occurs during execution of ADD DS, run INFO DS to verify that the DS is successfully created. Then run INFO SERVICE to list known services. If the HP NonStop SQL/MX Messages Manual—640324-001 15 -53...
  • Page 442 Cause. The attribute-name (for example, PREFIX, VALUE, LIMIT, ACTION) is not valid with the EVAR object for the command. Effect. The operation fails. Recovery. Either use a different EVAR attribute or delete the EVAR attribute from the command. HP NonStop SQL/MX Messages Manual—640324-001 15 -54...
  • Page 443 15409 The EVAR name must be * when the TYPE is ALL. Cause. Incorrect command entry. Effect. The operation fails. Recovery. Either specify an asterisk (*) wildcard for the EVAR name, or remove the type ALL from EVAR object for this command. HP NonStop SQL/MX Messages Manual—640324-001 15 -55...
  • Page 444 Where duplicate-count is the number of duplicates found. Cause. More than one object type for the specified name is found. Effect. A warning message is displayed, and the command is processed. Recovery. Delete the duplicates. HP NonStop SQL/MX Messages Manual—640324-001 15 -56...
  • Page 445 The remaining characters can be letters, numbers, hyphens, underscores or circumflexes (^). Cause. An invalid define EVAR name is entered in the command. Effect. The command fails. Recovery. Enter the command with a valid define EVAR name. HP NonStop SQL/MX Messages Manual—640324-001 15 -57...
  • Page 446 15430 Specified user user-name not found in existing list. Nothing changed. Where user-name is the user name. Cause. The user name was not found in the list of user names. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -58...
  • Page 447 Cause. A failure occurred in the lower-client library function. Effect. The operation fails. Recovery. See the lower-level error messages for details. HP NonStop SQL/MX Messages Manual—640324-001 15 -59...
  • Page 448 Where system-name is the name of the system. Cause. The group the operation was given against does not exist on the system. Effect. The operation fails. Recovery. Add the group to the system first, then reissue the command. HP NonStop SQL/MX Messages Manual—640324-001 15 -60...
  • Page 449 Cause. The command is not available. Effect. The operation fails. Recovery. No recovery required. SQL 15453 15453 Unknown object type, string1. Where string1 is the object type. Cause. The object type is invalid. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -61...
  • Page 450 Where string1 is the service name. Cause. The service name is incorrect. Effect. The operation fails. Recovery. Enter the command specifying a valid service name. Use the INFO SERVICE command to list the valid services. HP NonStop SQL/MX Messages Manual—640324-001 15 -62...
  • Page 451 Where string1 is the system name. Cause. The database on the system is not installed or is not operational. Effect. The operation fails. Recovery. Verify that NonStop SQL/MX is installed and operational. SQL 15501 15501 A syntax error was found.
  • Page 452 15506 The value must be a period or comma. Cause. The SET STYLE value that you specified for the DECIMAL_POINT option was not a period(.) or a comma (,). Effect. The operation fails. Recovery. Enter the corrected command. HP NonStop SQL/MX Messages Manual—640324-001 15 -64...
  • Page 453 15510 The value must be between 1 and 32767 or ALL. Cause. The SET LAYOUT value that you specified for the PAGE_LENGTH option was not in the value range. Effect. The operation fails. Recovery. Specify the correct value and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -65...
  • Page 454 Cause. The value that you specified in the LIST command was out of range. The value must be in the range 1 through 32767, or ALL. Effect. The operation fails. Recovery. Specify the correct value and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -66...
  • Page 455 SQL 15517 15517 An invalid option was specified. Cause. You specified an invalid option for the SET, RESET, SHOW, or SAVE command. Effect. The operation fails. Recovery. Specify a valid option and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -67...
  • Page 456 15521 You have a SUBTOTAL command but not a BREAK command. The SUBTOTAL command is being ignored. Cause. You specified a SUBTOTAL command, but there are no break columns to subtotal. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -68...
  • Page 457 15525 The value for PAGE, NEED, or SKIP is out of range. The valid range is 1 through 32767. Cause. The value that you specified for the PAGE, NEED, or SKIP clause was not in the range 1 through 32767. Effect. The DETAIL command fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -69...
  • Page 458 Cause. You attempted to reset an alias name or detail-alias name that was being used in another report command. The name cannot be deleted while another command is dependent upon it. Effect. The alias or detail-alias name is not reset. HP NonStop SQL/MX Messages Manual—640324-001 15 -70...
  • Page 459 You must specify a BREAK command on text2 before the LIST command. Cause. You specified a SUBTOTAL, BREAK TITLE, or BREAK FOOTING command or a LINE_NUMBER function for a column that is not a BREAK column. HP NonStop SQL/MX Messages Manual—640324-001 15 -71...
  • Page 460 Cause. The two operands of the binary arithmetic operator did not belong to data type classes that can be operated upon. Effect. The operation fails. Recovery. Check that the operands belong to data type classes that can be operated upon in a binary arithmetic expression. HP NonStop SQL/MX Messages Manual—640324-001 15 -72...
  • Page 461 Cause. You specified an AS DATE or AS TIME format on an incompatible item type. AS DATE or AS TIME can be specified only on an item having a LARGEINT data type. Effect. The operation fails. Recovery. Correct the command and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -73...
  • Page 462 Cause. You attempted a comparison between incompatible data types in a relational, LIKE IN, or BETWEEN predicate. Effect. The operation fails. Recovery. Check the character sets of the operands of the predicate, and correct those that are incompatible. HP NonStop SQL/MX Messages Manual—640324-001 15 -74...
  • Page 463 Cause. You specified a nonnumeric column in a TOTAL or SUBTOTAL command. Only numeric columns can be totaled or subtotaled. Effect. The command is ignored. Recovery. Reissue the command, using only numeric columns. HP NonStop SQL/MX Messages Manual—640324-001 15 -75...
  • Page 464 Cause. The current command requires an alias name, but the name that you specified was not an alias. Effect. The command is ignored. Recovery. Reissue the command, using a valid alias name. To display current alias names, use the SHOW REPORT NAME command. HP NonStop SQL/MX Messages Manual—640324-001 15 -76...
  • Page 465 However, that column ID is not currently set by the corresponding report command. Effect. The column ID is ignored by the RESET REPORT command. Recovery. This is an informational message; no recovery is necessary. HP NonStop SQL/MX Messages Manual—640324-001 15 -77...
  • Page 466 Cause. You tried to change the mode to SQL while already in SQL mode. Effect. The operation fails. Recovery. None. This is an informational message only. SQL 15805 15805 The specified mode is not valid. Cause. You tried to change the mode to an invalid mode. HP NonStop SQL/MX Messages Manual—640324-001 15 -78...
  • Page 467 15809 A string overflow occurred during the evaluation of a character expression. Cause. A string overflow occurred during the evaluation of a character expression. Effect. The operation fails. Recovery. Increase the field size of the receiving field and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 15 -79...
  • Page 468 SQL 15815 15815 An internal error occurred - unable to get a valid MXCS Constructor. Cause. MXCI was unable to connect to the MXCS server and get a valid constructor. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 15 -80...
  • Page 469 Cause. A new report definition command(s) has been specified. The report is being started from the beginning. Effect. A new report is being generated. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 15 -81...
  • Page 470 Effect. No usage information is displayed. Recovery. None. SQL 15999 15999 An MXCI internal error occurred. Cause. MXCI has received an internal error. Effect. The operation fails. Recovery. Report the entire message to your service provider. HP NonStop SQL/MX Messages Manual—640324-001 15 -82...

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

    SQL 16001 16001 The error number err-num is not used in SQL/MX. Cause. Internal error. Effect. NonStop SQL/MX is unable to return or display a message with the specified number. Recovery. None. Report the entire message to your service provider.
  • Page 472 Messages Generated by the Message System (16000 through 16999) HP NonStop SQL/MX Messages Manual—640324-001 16- 2...

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

    19000 An internal error occurred in internal stored procedure processing. Cause. Internal error. Effect. NonStop SQL/MX is unable to process the request. Recovery. None. Report the entire message to your service provider. SQL 19001 19001 An error was found in field description of internal stored procedure.
  • Page 474 (VERSION_INFO, RELATEDNESS). Cause. An attempt is made to access a built-in function with an input value that is invalid for the specified input type. Effect. The request fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 17- 2...
  • Page 475 19020 Stored procedure name expects value input parameters. Cause. A wrong number of input parameters are entered for the stored procedure. Effect. NonStop SQL/MX is unable to process the request. Recovery. If the message is returned from an explicit invocation of the stored procedure, re-enter the request with the correct number of input parameters.
  • Page 476 Cause. Searching in Guardian path (i.e. starting with /G/ on osh) is not supported, and user has specified this location with module_dir option. Effect. The operation fails. Recovery. Don’t use Guardian location in module_dir option. HP NonStop SQL/MX Messages Manual—640324-001 17- 4...

  • Page 477: Utility Messages (20000 Through 23099)

    Cause. SQL was not able to write to the requested file and received error error number. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18- 1...
  • Page 478 Cause. SQL was not able to retrieve information for the requested file and received error error number. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18- 2...
  • Page 479 20009 An internal error occurred - buffer size is larger than maximum transfer size for file. Cause. The utility subsystem responsible for performing fast data transfer was sent an invalid buffer size. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18- 3...
  • Page 480 20012 Previous write in file failed. Cause. The utility subsystem that performs fast data transfer could not successfully write data into the file. This error possibly results from a previous failed write to the same partition. HP NonStop SQL/MX Messages Manual—640324-001 18- 4...
  • Page 481 20016 File system error error number occurred while getting block size for file. Where error number is the Guardian file system error. Cause. SQL was not able to obtain the blocksize for the requested file and received error error number. HP NonStop SQL/MX Messages Manual—640324-001 18- 5...
  • Page 482 Where default is the DEFAULT_CLASS specified in the COLS metadata table. Where name is the COLUMN_NAME specified in the COLS metadata table. Cause. NonStop SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent. This is an internal error.
  • Page 483 Where table2 is the name of the referencing table. Where const is the name of the constraint for the referencing table. Cause. NonStop SQL/MX found a discrepancy while reading metadata information. The information returned is inconsistent. Effect. The operation fails.
  • Page 484 [not] opened, • [not] closed, • [not] modified, • [not] created Cause. Illegal sequence of operations performed by a utility. Effect. The operation fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 8...
  • Page 485 Cause. You specified an invalid key range, possibly because you specified the begin key as noninclusive (>) or specified the end key as inclusive (=). Effect. The operation fails. Recovery. Correct the first key value and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18- 9...
  • Page 486 Cause. The catalog is not visible on the local node, either because it does not exist or because it exists elsewhere in the network and has not been registered on the local node. This utility message corresponds to message 1002. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -10...
  • Page 487 20038 The specified key value uses incorrect syntax. Cause. You specified a key value with incorrect syntax. Effect. The operation fails. Recovery. Check the syntax of the specified partitioning key value and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -11...
  • Page 488 Where $0~string0 is the corresponding column name. Cause. You attempted to import UCS2 character data in binary mode. Effect. The operation fails. Recovery. Prepare the UCS2 data in a UCS2 data file and import it in delimited mode. HP NonStop SQL/MX Messages Manual—640324-001 18 -12...
  • Page 489 Recovery. None. This is an internal error. Contact your service provider. SQL 20047 20047 An internal error occurred - invalid store option. Cause. The utility subsystem that reads and maintains metadata encountered an unexpected value for the STORE BY option for the table. HP NonStop SQL/MX Messages Manual—640324-001 18 -13...
  • Page 490 20050 The modify request failed. See subsequent errors for more details. Cause. You attempted to perform a modify request, which failed. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18 -14...
  • Page 491 Cause. The utility subsystem that performs CLI requests to SQL failed trying to clean up memory upon completion of a request. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -15...
  • Page 492 Cause. The input file specified as the command-line option for IMPORT does not exist or could not be opened. Effect. The operation fails. Recovery. Verify that the input data file exists and is in a valid state. HP NonStop SQL/MX Messages Manual—640324-001 18 -16...
  • Page 493 20062 The -T command-line option must have a value greater than zero. Cause. The transaction-size value that you specified is either negative or zero. Effect. The operation fails. Recovery. Specify a positive transaction-size value. HP NonStop SQL/MX Messages Manual—640324-001 18 -17...
  • Page 494 20067 A syntax error occurred at or before: string0. Where string0 is the value where the syntax error was detected. Cause. You specified the wrong syntax. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -18...
  • Page 495 Cause. The row delimiter string that you specified, either at the command line or in the DELIMITED FORMAT section of the format file, contains a field qualifier character. Effect. The operation fails. Recovery. Specify a row delimiter string that does not contain a field qualifier character and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -19...
  • Page 496 Effect. The operation fails. Recovery. Check the validity of the input file. If the input file is a valid remote file, verify that the remote password for the system is set. HP NonStop SQL/MX Messages Manual—640324-001 18 -20...
  • Page 497 Cause. The fixed-width data file is incomplete and does not provide enough data at the end of the file for importing. Effect. The last transaction of the import is aborted, and all rows in that transaction are not imported. HP NonStop SQL/MX Messages Manual—640324-001 18 -21...
  • Page 498 20086 Column columname in the FIXED WIDTH FORMAT part of the format file is not found in the target table. Key = keyval Where columnname is the column name specified in the FIXED WIDTH FORMAT part of the format file. HP NonStop SQL/MX Messages Manual—640324-001 18 -22...
  • Page 499 Where columnname is the column name specified in the FIXED WIDTH FORMAT part of the format file. Cause. The column name that you specified was missing from an internal message. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -23...
  • Page 500 20093 The column scale is not present in compile time arguments. Key = scale Where scale is the column scale for the specified table. Cause. The scale value that you specified was missing from an internal message. HP NonStop SQL/MX Messages Manual—640324-001 18 -24...
  • Page 501 Utility Messages (20000 through 23099) Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -25...
  • Page 502 Cause. The date order that you specified was invalid. Effect. The operation fails. Recovery. Valid date order values are MDY, MYD, DMY, DYM, YMD, and YDM. Correct the date order in the DATE FORMAT section of the format file. HP NonStop SQL/MX Messages Manual—640324-001 18 -26...
  • Page 503 Cause. The skip flag was missing for this column from the COLUMN FORMAT section of the format file. Effect. The operation fails. Recovery. Set the skip flag to Y or N in the COLUMN FORMAT section of the format file. HP NonStop SQL/MX Messages Manual—640324-001 18 -27...
  • Page 504 Effect. The operation fails. Recovery. Correct the syntax and resubmit. SQL 20105 20105 An internal error occurred - invalid object type. Cause. SQL detected an internal error while performing a utility operation. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -28...
  • Page 505 Where details describe the returned error information from the file system. Cause. An unexpected error was returned from the CLI while accessing file system information. Effect. The operation fails. Recovery. Use the accompanying error messages to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18 -29...
  • Page 506 20113 Source table table name does not exist or cannot be accessed. Where table name is the name of the table to duplicate. Cause. You specified a source table name that does not exist or could not be accessed. HP NonStop SQL/MX Messages Manual—640324-001 18 -30...
  • Page 507 20117 Catalog catalog name does not exist or cannot be accessed. Where catalog name is the name of the catalog associated with the table to be purged. Cause. You specified a catalog name that does not exist or could not be accessed. HP NonStop SQL/MX Messages Manual—640324-001 18 -31...
  • Page 508 Cause. The table being purged has multiple partitions and is not key-sequenced. This type of table is not supported. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -32...
  • Page 509 SQL 20127 20127 Target option was specified as NEW but object-type exists. DUP operation failed. Where object-type is a table. Cause. The target name you specified was not valid. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -33...
  • Page 510 20131 The row delimiter is missing from the data file. Cause. The row delimiter was missing from the delimited input data file. Effect. The operation fails. Recovery. Add a row delimiter and run the import again. HP NonStop SQL/MX Messages Manual—640324-001 18 -34...
  • Page 511 DELIMITED FORMAT section of the format file, is more than one character long. Effect. The operation fails. Recovery. Specify a single character qualifier at the command line or in the DELIMITED FORMAT section of the format file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -35...
  • Page 512 Cause. The utility subsystem that performs CLI operations failed while trying to perform an ABORTTRANSACTION. Effect. The operation fails. Recovery. Use the messages that accompany this one to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18 -36...
  • Page 513 Recovery. None. This is an internal error. Contact your service provider. SQL 20143 20143 Equal sign is missing. Cause. An equal sign is missing from an equation. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -37...
  • Page 514 Cause. The list of partitions specified in the key range has the same begin and end key. There are no partitions to purge. Effect. The operation fails. Recovery. Specify a valid key range and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -38...
  • Page 515 20151 IMPORT does not currently support binary data files. Cause. The format file has a line that specifies FileIsBinary=Y.This option is not supported in the current release of NonStop SQL/MX. Effect. The operation fails. Recovery. Change the format file to specify FileIsBinary=N and resubmit.
  • Page 516 20157 Assigning a DEFAULT value to the NO DEFAULT field. Column number = column number Cause. You attempted to assign a default value to a field, in column number, with NO DEFAULT. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -40...
  • Page 517 20163 An internal error occurred - invalid include option of CREATE TABLE LIKE. Cause. SQL was unable to perform the requested operation. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -41...
  • Page 518 20167 The object name must contain at least one character. Cause. The object name that you specified is not valid.It must contain at least one character. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -42...
  • Page 519 SQL 20171 20171 section name section is missing in the format file. Cause. The section name is missing from the format file. Effect. The operation fails. Recovery. Correct the format file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -43...
  • Page 520 Cause. The record length value is missing in the FIXED WIDTH FORMAT section of the format file. Effect. The operation fails. Recovery. Correct the format file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -44...
  • Page 521 “RF”—Refresh, “VA”—Validate, “TR”—Transform. Cause. You attempted to execute a utility or alter the DDL of an object while a concurrent utility or DDL operation was being performed on the object, its parent, or its dependent. HP NonStop SQL/MX Messages Manual—640324-001 18 -45...
  • Page 522 20180 section name section of the format file is not valid. Cause. The specified section name in the format file was invalid. Effect. The operation fails. Recovery. Correct the format file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -46...
  • Page 523 Where file name is the name of the format file. Cause. The format file name that you specified was not a valid format file. Effect. The operation fails. Recovery. Correct the format file and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -47...
  • Page 524 20189 Data in the primary partition (or subset) cannot be moved to the previous partition because no previous partition exists. Cause. You tried to move data in the first partition to a nonexisting previous partition. HP NonStop SQL/MX Messages Manual—640324-001 18 -48...
  • Page 525 20193 This operation cannot be performed under a user-defined transaction. Cause. You cannot perform a POPULATE INDEX operation under a user-defined transaction. Effect. The operation fails. Recovery. Commit or roll back the user-defined transaction and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -49...
  • Page 526 Cause. The index name specified by the caller should not contain data. Data was found to exist, most likely because a previous POPULATE INDEX command failed. Effect. The operation fails. Recovery. Execute the RECOVER command to clean up the previously failed command and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -50...
  • Page 527 Recovery. None. Contact your service provider. SQL 20200 20200 Catalog does not exist. Cause. You specified a catalog name that is not defined or not visible on the system. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -51...
  • Page 528 Where object-name is the index to be recovered as specified by the POPULATE INDEX command. Cause. The index name could not be recovered with the given RECOVER command. Effect. The operation fails. Recovery. Use the correct RECOVER option and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -52...
  • Page 529 Recovery. Commit or roll back the user-defined transaction, and resubmit. SQL 20209 20209 Nothing remains to be recovered on object-name. Where object-name is the name of the object to recover. Cause. Recovery is not needed for object-name. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -53...
  • Page 530 Recovery. Determine the operation that is currently running, wait until it completes, and then resubmit. SQL 20213 20213 An internal error occurred during RECOVER. Cause. An unknown error occurred while recovering a utility operation. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -54...
  • Page 531 20217 Catalog does not exist. Cause. The catalog name specified by the caller is not defined or not visible on the current system. Effect. The operation fails. Recovery. Specify a valid catalog name and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -55...
  • Page 532 Where int is the byte location in the string where the error occurred. Note. As of this ABU SPR, this message is no longer generated. Cause. You specified the wrong syntax. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -56...
  • Page 533 PURGEDATA does not allow individual or sets of partitions to be purged, only the entire table can be purged. Cause. You attempted to purge individual partitions of a hash-partitioned table, which is not supported. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -57...
  • Page 534 Where index-name is the name of the index specified in the update request. Cause. An unexpected error is returned during the final phase of duplicating indexes to the target table. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -58...
  • Page 535 20233 No partition could be found in volume volume name for the specified object. Where volume-name is the name of the volume. Cause. The MODIFY utility could not find, in volume volume-name, partitions that belong to the specified object. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -59...
  • Page 536 Cause. An unexpected error was returned while converting the current user name to user ID. Effect. The operation fails. Recovery. Diagnose the returned status described in the Guardian Procedure Errors and Messages Manual to determine the problem and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -60...
  • Page 537 Cause. You specified an invalid attribute value for attribute PM_ONLINE_TRANSACTION_GRANULARITY for online operation and attribute PM_OFFLINE_TRANSACTION_GRANULARITY for offline operation. Effect. The operation fails. Recovery. Commit or roll back the transaction (using the COMMIT WORK or ROLLBACK WORK command) and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -61...
  • Page 538 20244 The byte order mark in Unicode data file file is not valid. Where file is the name of the Unicode data file. Cause. The byte order mark bytes specified are invalid. Effect. The Unicode data import fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -62...
  • Page 539 Where operation is the type of MODIFY operation including ADD, MOVE, or DROP. Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -63...
  • Page 540 Cause. You attempted a partition management request other than ADD, DROP, or MOVE on an index. Note that the REUSE request works only with range-partitioned requests. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18 -64...
  • Page 541 Cause. In the WHERE clause, you did not specify the partition in the request to move the partition to a new location. When the object has more than one partition, you must specify the partition. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -65...
  • Page 542 Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20266 20266 Invalid message code code1 returned from SPI request, expecting code2. Where code1 is the code returned from SPI. HP NonStop SQL/MX Messages Manual—640324-001 18 -66...
  • Page 543 SQL 20269 20269 The audit attribute of table table-name could not be turned off during import operation. Where table-name is the name of the target table. HP NonStop SQL/MX Messages Manual—640324-001 18 -67...
  • Page 544 Recovery. None. This is an internal error. Contact your service provider. SQL 20272 20272 Non-audited tables are not supported. Cannot perform DUP. Cause. The DUP operation does not support nonaudited tables. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -68...
  • Page 545 20276 Reload operation failed, already in progress. Cause. SQL attempted to start a FUP RELOAD operation but an operation was already in progress. Effect. The operation fails. Recovery. Wait until the current RELOAD operation completes, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -69...
  • Page 546 The REUSE operation is not allowed on such a partition. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18 -70...
  • Page 547 If the failures were caused by the MODIFY process being killed inadvertently, the warning message is issued by the RECOVER utility during the recovery. Effect. The MODIFY utility completed the request, but the FUP RELOAD operation might not have finished successfully. HP NonStop SQL/MX Messages Manual—640324-001 18 -71...
  • Page 548 20300 The object type object is not currently supported. Where object type is the object type specified. Cause. You attempted to perform a backup or a restore on object type, which is not supported. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18 -72...
  • Page 549 Recovery. Use CANCEL to retry the operation. SQL 20306 20306 There is no data associated with the object name object. Cause. Internal error. Effect. The backup or restore could not be performed. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -73...
  • Page 550 20311 The column data type is not supported. Cause. You are trying to create a column of a data type that is not supported. Effect. The backup or restore operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18 -74...
  • Page 551 SQL 20319 20319 The table object already exists. Cause. You are trying to restore a table object that already exists. Effect. The operation fails. Recovery. Check the location of the table and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -75...
  • Page 552 SQL 20330 20330 The specified parameter is not valid. Cause. An internal function has specified the wrong parameters. Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -76...
  • Page 553 Cause. The restore options you specified do not match the backup options. Effect. The operation fails. Recovery. Correct the restore options and resubmit. SQL 20335 20335 Selected run time option is not valid. Cause. The restore session mode is unknown. HP NonStop SQL/MX Messages Manual—640324-001 18 -77...
  • Page 554 Effect. The operation fails. Recovery. For unique indexes, remove conflicting records from the base table and retry the populate operation. For non-unique indexes, do not attempt recovery. HP NonStop SQL/MX Messages Manual—640324-001 18 -78...
  • Page 555 Effect. The operation fails. Recovery. None. This is an internal error. Contact your service provider. SQL 20352 20352 Syntax error. No arguments were provided. Try ‘mxtool help’. Cause. You specified MXTOOL without any arguments. HP NonStop SQL/MX Messages Manual—640324-001 18 -79...
  • Page 556 Recovery. Specify the Guardian file correctly and resubmit. SQL 20356 20356 File name could not be accessed. Error error was returned. Where name is the name of the Guardian file requested to be removed. HP NonStop SQL/MX Messages Manual—640324-001 18 -80...
  • Page 557 20359 Schema schema does not exist. Where schema is the name of the schema specified in the request. Cause. You specified an invalid schema name. Effect. The operation fails. Recovery. Enter the correct schema name and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -81...
  • Page 558 Cause. MXTOOL generates a list of files to check as specified by a Guardian file template. An error was returned during the processing of this list. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 18 -82...
  • Page 559 Recovery. Specify the correct object name and resubmit. SQL 20372 20372 The resource fork is not accessible. Cause. The resource fork is either broken or does not exist. Effect. None. Recovery. None. This is an informational message. HP NonStop SQL/MX Messages Manual—640324-001 18 -83...
  • Page 560 Recovery. Specify an ISO88591 character set name. SQL 20377 20377 An error occurred while doing a conversion between TERMINAL_CHARSET & ISO_MAPPING CQD. Cause. You specified an invalid character set. Effect. The operation fails. Recovery. Specify an ISO88591 character set. HP NonStop SQL/MX Messages Manual—640324-001 18 -84...
  • Page 561 Where name is the name of the Guardian file requested to be removed. Cause. The GOAWAY operation failed because the label has a lock on it, and the operation timed out after 90 seconds. HP NonStop SQL/MX Messages Manual—640324-001 18 -85...
  • Page 562 Where file is the name of the Guardian file. Where error is the file system error returned while trying to remove a Guardian file. Cause. The GOAWAY operation failed because of an unexpected error. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -86...
  • Page 563 Where resource fork name is the name of the resource fork. Cause. The GOAWAY operation failed because you specified resource fork name with the -df option. Effect. The operation fails. Recovery. Retry with the -rf option. HP NonStop SQL/MX Messages Manual—640324-001 18 -87...
  • Page 564 Recovery. After the concurrent operation that holds the DDL lock finishes, run refresh again. If no concurrent operations are running, the DDL lock must be removed. Contact your service provider to remove the lock. HP NonStop SQL/MX Messages Manual—640324-001 18 -88...
  • Page 565 Cause. Refresh reached a transaction management facility (TMF) limit on the number of transactions that the facility can start. Effect. The refresh operation fails. Recovery. Do not attempt recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -89...
  • Page 566 SQL 20702 20702 A file system error occurred during the audit fixup phase of the operation, on file Guardian file name. Where Guardian file name is the name of the partition being processed. HP NonStop SQL/MX Messages Manual—640324-001 18 -90...
  • Page 567 20705 An audit fixup request was made out of sequence. Cause. During an online partition management operation, the MXAUDSRV process received an unexpected request from the MODIFY code. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -91...
  • Page 568 Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered an error while processing an HP NonStop Transaction Management Facility (TMF) audit record. Effect. The MODIFY operation fails.
  • Page 569 The maximum size for a request message to the audit fixup server was exceeded. Cause. During an online partition management operation, the MXAUDSRV process received a request of an invalid size from the MODIFY code. Effect. The MODIFY operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -93...
  • Page 570 Where process name is the name of the MXAUDSRV process. Cause. During an online partition management operation, the MXAUDSRV process encountered an audit trail versioning error while processing audit records. Effect. The MODIFY operation fails. Recovery. Correct the TMF problem and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -94...
  • Page 571 Where process name is the MXAUDSRV process name. Cause. During an online partition management operation, the MXAUDSRV process encountered an internal error. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -95...
  • Page 572 20726 An audit fixup process’s program file process name is not licensed. Where program file name is the MXAUDSRV process name. Cause. The MXAUDSRV program file is not licensed. Effect. The MODIFY operation fails. HP NonStop SQL/MX Messages Manual—640324-001 18 -96...
  • Page 573 Cause. During an online partition management operation, the MXAUDSRV process encountered an error when attempting to extract data fields from a TMF audit record. Effect. The MODIFY operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18 -97...
  • Page 574 30 days in the future. Effect. The MODIFY operation fails. Recovery. Correct the COMMIT AFTER clause to use a time within 30 days of the present, and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18 -98...
  • Page 575 Cause. An unexpected error occurred when trying to find audit records to apply to index. Effect. Populate is not done. Recovery. Recover the index file, check environment and retry. HP NonStop SQL/MX Messages Manual—640324-001 18 -99...
  • Page 576 Recovery. None. Contact your service provider. SQL 20754 20754 File system error (error) was returned while retrieving the object from the resource fork. Where error is the error returned by the file system. HP NonStop SQL/MX Messages Manual—640324-001 18- 100...
  • Page 577 20757 The file specified (filename) is a resource fork. Verify does not support operations on resource forks. Where file is the Guardian file name specified. Cause. VERIFY failed because the name of the file is a resource fork. HP NonStop SQL/MX Messages Manual—640324-001 18- 101...
  • Page 578 Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Please use FIXUP to change the redefinition timestamp to correct the inconsistency. HP NonStop SQL/MX Messages Manual—640324-001 18- 102...
  • Page 579 Where size2 is the secondary extent size defined in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 103...
  • Page 580 Where size2 is the record size found in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 104...
  • Page 581 Where name2 is the ANSI name found in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. HP NonStop SQL/MX Messages Manual—640324-001 18- 105...
  • Page 582 Where name is the constraint name described in the metadata. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 106...
  • Page 583 Guardian file (file). Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 107...
  • Page 584 Where name is the name of the index that should exist in the index map in the resource fork. Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 108...
  • Page 585 Where string2 is the Guardian name of the partition as it is defined in the metadata (PARTITIONS or REPLICAS tables). Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 109...
  • Page 586 Guardian file (file). Where file is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 110...
  • Page 587 20790 The partition name (rname) defined in the resource fork does not match the partition name (mname) defined in the metadata for Guardian file (file). Where rname is the partition name defined in the resource fork. HP NonStop SQL/MX Messages Manual—640324-001 18 -111...
  • Page 588 20794 Error (number) was returned when trying to extract the catalog, schema, or table from the ANSI name defined in the resource fork for Guardian file (file). Where, number is the file-system error number. file is the SQL/MX file being verified. HP NonStop SQL/MX Messages Manual—640324-001 18- 112...
  • Page 589 20798 There is currently an active/inactive DDL lock for object (object name). Where active/inactive specifies whether the lock is active or inactive. Where object specifies whether the object is a table or view. HP NonStop SQL/MX Messages Manual—640324-001 18- 113...
  • Page 590 Where mscheme is the partitioning scheme of the object stored in the metadata. Where file-name is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 114...
  • Page 591 Effect. None. This is an informational message. Recovery. Check if another utility operation is using the same partition and is in progress. If it is not, contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 115...
  • Page 592 Where flag value various flag values on label. Where file-name is the name of the Guardian file. Cause. An inconsistency was found during the VERIFY operation. Effect. None. This is an informational message. Recovery. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 116...
  • Page 593 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 service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 117...
  • Page 594 Where value is always 0 to indicate the broken bit is already cleared. Cause. The ‘-rb” option was used with the FIXUP utility to reset the broken bit on a file where the broken bit is not currently set. HP NonStop SQL/MX Messages Manual—640324-001 18- 118...
  • Page 595 Cause. The “-rc” option was used with the FIXUP utility to reset the corrupt bit on a file where the corrupt bit is not currently set. Effect. None. This is a warning. Recovery. No recovery is necessary. HP NonStop SQL/MX Messages Manual—640324-001 18- 119...
  • Page 596 20860 file-name is not a datafork/label. Only changes to datafork/label are supported. Where file-name is the Guardian file specified as an argument to FIXUP. Cause. You specified a file other than an SQL/MX data fork. HP NonStop SQL/MX Messages Manual—640324-001 18- 120...
  • Page 597 Cause. The FASTCOPY TABLE or FASTCOPY INDEX command is executed with incompatible source and target objects. The accompanying error messages are displayed with detailed incompatibility information. Effect. The fastcopy operation fails. The source and target tables are available to other operations. HP NonStop SQL/MX Messages Manual—640324-001 18- 121...
  • Page 598 • indexes have the same number of index columns • each source-target pair of index columns, in key sequence order, have the same column number in the tables HP NonStop SQL/MX Messages Manual—640324-001 18- 122...
  • Page 599 Cause. A FASTCOPY command is executed and all the rows from the source objects are already copied to the specified target object or they are being copied by previous FASTCOPY command. Effect. None. This is an informational command. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 123...
  • Page 600 Effect. The FASTCOPY operation fails; target objects are left in an incomplete state. Recovery. Use the RECOVER operation to either CANCEL or RESUME the fastcopy operation depending on the actual error. HP NonStop SQL/MX Messages Manual—640324-001 18- 124...
  • Page 601 Cause. A FASTCOPY command referenced an object from catalog. However, the catalog does not exist or is not registered on the system where the command is executed. Effect. The fastcopy operation fails; involved objects are left unchanged. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 125...
  • Page 602 Cause. One of the objects for continuation FASTCOPY command does not participate in any fastcopy operation, whereas the other object participates in a fastcopy operation. Effect. The operation fails; involved objects are left unchanged. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 126...
  • Page 603 21067 Source and target index belong to the same base table. Cause. For the FASTCOPY INDEX command, source and target specify indexes from the same base table. Effect. The operation fails; involved objects are left unchanged. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 127...
  • Page 604 Cause. The FASTCOPY is a continuation of a previous command and the source object is modified because the previous command was issued. Effect. The entire fastcopy operation is canceled. Involved target objects are left empty and available. Recovery. Initiate a new fastcopy operation. HP NonStop SQL/MX Messages Manual—640324-001 18- 128...
  • Page 605 Cause. The target table for a FASTCOPY command has an ANSI name part that is longer than 122 characters. This is not supported by FASTCOPY. Effect. The operation fails; involved objects are left unchanged. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 129...
  • Page 606 Where servername is the name of the server program that issued the error. Where description provides more details about the file error. Cause. See details in description description. Effect. The operation fails. Recovery. Correct the problem and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 18- 130...
  • Page 607 Recovery. Do not attempt recovery. Contact your service provider. SQL 23008 23008 Assertion failed. Cause. Internal program ASSERT failed, indicating an invalid program state. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 131...
  • Page 608 Where servername is the name of the server program that issued the error. Where nnn is the unknown error code. Cause. An exception occurred for an unexpected error. Effect. The operation fails. Recovery. None. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 132...
  • Page 609 If the file is damaged or not a valid format, it might indicate a problem with the mxexportddl program. Effect. The operation fails. Recovery. Determine the problem with the formatted file and resubmit. If the problem persists, contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 18- 133...
  • Page 610 Recovery. Specify a valid set of run-time arguments and resubmit. SQL 23020 23020 servername: SQL/MX object was not found: object-name. Where servername is the name of the server program that issued the error. HP NonStop SQL/MX Messages Manual—640324-001 18- 134...
  • Page 611 Recovery. None. SQL 23024 23024 object-type object-name already exists. Where object-name is the name of the SQL/MX object. Where object-type is the type of the SQL/MX object. Cause. The target SQL/MX object already exists. HP NonStop SQL/MX Messages Manual—640324-001 18- 135...
  • Page 612 Where table-name is the name of the SQL/MX table. Cause. The target table already contains statistics. Effect. None. Recovery. None. SQL 23028 23028 Statistics of the table table-name is cleared. Where table-name is the name of the SQL/MX table. HP NonStop SQL/MX Messages Manual—640324-001 18- 136...
  • Page 613 23030 Only schema owner or super.super can perform the operation. Where operation is either the export or import. Cause. The mxexportddl or mximportddl operation is started by non-schema owner or non super ID user. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 18- 137...
  • Page 614 Utility Messages (20000 through 23099) HP NonStop SQL/MX Messages Manual—640324-001 18- 138...

  • Page 615: Versioning And Distribution Messages

    Recovery. Not Applicable. SQL 25002 25002 A versioning internal error occurred: missing compatibility check. Cause. This is a versioning internal error, please contact the HP GCSC. Effect. The operation fails. Recovery. None. SQL 25003 25003 A versioning internal error occurred: abort transaction message cleanup.
  • Page 616 The affected object either does not exist or has not yet been downgraded from the incompatible version. Effect. The operation fails. Recovery. Wait until the downgrade schema operation is finished and retry the affected operation. HP NonStop SQL/MX Messages Manual—640324-001 19- 2...
  • Page 617 MXVs older than MXV2. where, node is the name of the affected remote node. MXV1 is the MXV of the affected remote node. MXV2 is the local node’s earliest supported MXV. HP NonStop SQL/MX Messages Manual—640324-001 19- 3...
  • Page 618 MXV different from its own. Effect. The request fails. Recovery. Migrate the remote node to a supported GA release. Or, conversely, migrate the local node to the same non-GA release as the remote node. HP NonStop SQL/MX Messages Manual—640324-001 19- 4...
  • Page 619 25201 Table or view object cannot be accessed because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2. where, object is the name of the affected database object. HP NonStop SQL/MX Messages Manual—640324-001 19- 5...
  • Page 620 SQL 25203 25203 Table or view object cannot be accessed on node because of a version incompatibility. Its schema has version version1; node does not support schema versions higher than version2. where, HP NonStop SQL/MX Messages Manual—640324-001 19- 6...
  • Page 621 The compiler version is version2. where, schema1 is the name of a schema that is referenced by a DDL or utility operation. version1 is the schema version of schema. HP NonStop SQL/MX Messages Manual—640324-001 19- 7...
  • Page 622 Effect. The request fails. Recovery. Downgrade the system schema on the affected node to a version that is compatible with the required compiler version. HP NonStop SQL/MX Messages Manual—640324-001 19- 8...
  • Page 623 25209 Related schemas must have identical schema version. Schema schema1 has version version1; schema schema2 has version version2. Where schema1 and schema2 are schemas that would be related as the result of the affected DDL or utility operation. HP NonStop SQL/MX Messages Manual—640324-001 19- 9...
  • Page 624 Where object is the affected table or view. Where version1 is the schema version of object schema. Where node is the node that executes the query. Where MXV1 is the MXV of the node that executes the query. HP NonStop SQL/MX Messages Manual—640324-001 19 -10...
  • Page 625 Recovery. Migrate the accessing node to a SQL/MX version that has an MXV that is compatible with the affected system schema version. Or, conversely, cleanup the system schema and re-initialize sql on the affected node. HP NonStop SQL/MX Messages Manual—640324-001 19 -11...
  • Page 626 SQL/MX software version (MXV) can access only schemas of version MXV1. Where schema is a schema that is accessed by a DDL or utility operation. Where version1 is the schema version of that schema. HP NonStop SQL/MX Messages Manual—640324-001 19 -12...
  • Page 627 Recovery. Investigate and resolve the situation. Note that the message text does not specify which node(s) or database object(s) are involved the reason being that an unknown number of nodes and database objects may be affected. HP NonStop SQL/MX Messages Manual—640324-001 19 -13...
  • Page 628 Recovery. Allow the system to select the schema version for the new schema: CONTROL QUERY DEFAULT CREATE_DEFINITION_SCHEMA_VERSION 'SYSTEM' SQL 25222 25222 version is not a valid schema version. Where version is the value that is in effect for the CREATE_DEFINITION_SCHEMA_VERSION CQD. HP NonStop SQL/MX Messages Manual—640324-001 19 -14...
  • Page 629 Cause. The target version of an UPGRADE or DOWNGRADE operation is lower than the oldest supported schema version of one or more nodes where an involved schema is visible. Effect. The operation fails. HP NonStop SQL/MX Messages Manual—640324-001 19 -15...
  • Page 630 Effect. The operation fails. Recovery. Execute a corresponding UPGRADE operation to upgrade the affected schema to the current version and then re-execute the DOWNGRADE operation. HP NonStop SQL/MX Messages Manual—640324-001 19 -16...
  • Page 631 Where operation is the UPGRADE or DOWNGRADE operation that you specified. Cause. A RECOVER command was issued and the original UPGRADE or DOWNGRADE operation is still being actively processed. Effect. The RECOVER command fails. HP NonStop SQL/MX Messages Manual—640324-001 19 -17...
  • Page 632 Cause. You attempted to drop the definition schema but user schemas of the same version exists in the catalog. Effect. The operation fails. Recovery. This is an internal error. Contact your service provider. HP NonStop SQL/MX Messages Manual—640324-001 19 -18...
  • Page 633 Cause. The DOWNGRADE command was executed in a distributed environment where one or more affected catalogs were originally created on remote_node and where the system schema version on that node is higher than 1200. Effect. The DOWNGRADE command fails. HP NonStop SQL/MX Messages Manual—640324-001 19 -19...
  • Page 634 Recovery. Recompile the module with a supported version compiler. SQL 25302 25302 The query plan version is version1; node node does not support query plan versions lower than version2. Where version1 is the plan version of the affected query. HP NonStop SQL/MX Messages Manual—640324-001 19 -20...
  • Page 635 SQL/MX Software Version (MXV) version1, the MXV of node is MXV1. Where version1 is the plan version of the affected query plan. Where node is the node that attempts to execute the query. HP NonStop SQL/MX Messages Manual—640324-001 19 -21...
  • Page 636 Cause. The affected node runs a GA version of SQL/MX and is incompatible with a module generated by a non-GA version. Effect. The request fails. Recovery. Compile the module with a compiler version that is compatible with the MXV. HP NonStop SQL/MX Messages Manual—640324-001 19 -22...
  • Page 637 Where version1 is the required compiler version. Where version2 is the actual compiler version. Cause. The query affects one or more nodes with an MXV lower than the current compiler version. Effect. The request fails. HP NonStop SQL/MX Messages Manual—640324-001 19 -23...
  • Page 638 Where version3 is the actual compiler version. Cause. The query affects one or more nodes with an MXV lower than the current compiler version. Effect. The request fails. Recovery. Explicitly use a compiler with version in the specified interval. HP NonStop SQL/MX Messages Manual—640324-001 19 -24...

  • Page 639: Distribution Messages (25400-25499)

    (accompanying warning 25406), a late name resolution or automatic recompilation is attempted. Recovery. When the message is issued as a error, correct the error and retry the operation. If the message is issued as a warning, NonStop SQL/MX attempts to recover automatically. SQL 25402 25402 Catalog catalog has previously been registered on node node.
  • Page 640 (accompanying warning 25406), a late name resolution or automatic recompilation is attempted. Recovery. If the message is issued as a error, correct the error and retry the operation. If the message is issued as a warning, NonStop SQL/MX attempts to recover automatically. SQL 25404 25404 Catalogs catalog1 and catalog2 must have identical visibility.
  • Page 641 Cause. A replication operation required access to a remote node that cannot be accessed because of the reported file system error. Effect. The operation fails. Recovery. Correct the error and retry the operation. HP NonStop SQL/MX Messages Manual—640324-001 19 -27...
  • Page 642 Cause. The target node of an UNREPLICATE SCHEMA operation does not have a replica of the affected schema. Effect. The operation fails. Recovery. None. The affected schema has no replica on the target node. HP NonStop SQL/MX Messages Manual—640324-001 19 -28...
  • Page 643 Cause. The operation required access to a volume, local or remote, that cannot be accessed because of the reported file system error. Effect. The operation fails. Recovery. Correct the error and retry the operation. HP NonStop SQL/MX Messages Manual—640324-001 19 -29...
  • Page 644 However the target catalog is related to one or more other catalogs that are not visible on the target node. This error is issued once per related catalog. Effect. The operation fails. Recovery. Use the CASCADE option on REGISTER CATALOG. HP NonStop SQL/MX Messages Manual—640324-001 19 -30...
  • Page 645 Where node is the name of the target node for the REGISTER CATALOG command. Cause. A REGISTER CATALOG operation attempted to register the catalog on a Release 1.8 node. Effect. The operation fails. Recovery. None. HP NonStop SQL/MX Messages Manual—640324-001 19 -31...

  • Page 646: Jdbc Driver Error Messages (29000-29999)

    Recovery. None. This message is issued as a warning. JDBC Driver Error Messages (29000-29999) This range of numbers is reserved for JDBC Driver error messages and are documented in the JDBC documentation. For complete information, see the applicable JDBC Driver manual. HP NonStop SQL/MX Messages Manual—640324-001 19 -32...

  • Page 647: Rowsets Messages (30000 Through 30999)

    30003 Rowset size must be an integer host variable or constant. Cause. You specified a rowset size with a value other than an integer host variable or constant. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 20- 1...
  • Page 648 The smallest dimension is assumed. Cause. You specified different values for the dimensions of a rowset array. Effect. NonStop SQL/MX uses the smallest dimension for the array. Recovery. If this is not the value you want to use, correct the syntax and resubmit.
  • Page 649 Rowsets Messages (30000 through 30999) SQL 30008 30008 Rowset index is out of range. Cause. NonStop SQL/MX received an internal error from a rowset. Effect. The operation fails. Recovery. None. Contact your service provider. SQL 30009 30009 Trying to add more elements than maximum rowset size.
  • Page 650 Cause. You attempted to use a rowset in the SET clause of an UPDATE statement when a corresponding rowset is not present in the WHERE clause. Effect. The operation fails. Recovery. Correct the syntax and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 20- 4...
  • Page 651 Referential integrity constraint constraint-name has table table-name as its referencing table. Where, constraint-name is the name of the referential integrity constraint. table-name is the name of the referencing table. HP NonStop SQL/MX Messages Manual—640324-001 20- 5...
  • Page 652 30037 The search-condition for a DELETE [FIRST N] statement contains a rowset. Cause. The search-condition for a DELETE [FIRST N] statement contains a rowset. Effect. The statement does not compile. Recovery. Remove the rowset host variable or parameter from the search-condition. HP NonStop SQL/MX Messages Manual—640324-001 20- 6...

  • Page 653: Sqlstate Values Returned By Nonstop Sql/Mx

    SQLSTATE Values Returned by NonStop SQL/MX NonStop SQL/MX returns SQLSTATE values that are defined in the ISO/ANSI SQL standard and implementation-defined SQLSTATE values. See Subclause 22, “Status Codes” in the ISO/ANSI SQL92 Standard “Database Language SQL.” SQLSTATE and SQLCODE Considerations •...

  • Page 654: Sqlstate Values

    SQLSTATE Values SQLSTATE Values For information about equivalent SQLCODE and SQLSTATE values for key messages returned by NonStop SQL/MX and NonStop SQL/MP, see the section “Error Codes” in the SQL/MX Comparison Guide for SQL/MP Users. Table 21-1 is a list of returned SQLSTATE values ordered by SQLSTATE. SQLSTATE values are provided for both warning messages (positive SQLCODE numbers) and error messages (negative SQLCODE numbers).
  • Page 655 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 2 of 84) SQLSTATE SQLCODE Error Text 0150K 1020 Privilege settings on metadata tables cannot be changed. 0150L 1021 SQL is already initialized on system node-name. 0150M 1022 Schema schema-name already exists.
  • Page 656 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 3 of 84) SQLSTATE SQLCODE Error Text 0151E 1050 Cannot drop constraint used as a referenced object for a foreign key. 0151F 1051 Insufficient privilege on table name.
  • Page 657 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 4 of 84) SQLSTATE SQLCODE Error Text 0152D 1085 The calculated key length is greater than 255 bytes. 0152E 1086 Lock table name does not exist. 0152F 1087 Lock cannot be granted, conflicting operation is in progress.
  • Page 658 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 5 of 84) SQLSTATE SQLCODE Error Text 0153D 1121 Attempting to perform a partition add, move, or drop on table name. Partition operations are not allowed on tables with vertical partitions, entry sequenced operations, and SYSKEY- only partitioned tables.
  • Page 659 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 6 of 84) SQLSTATE SQLCODE Error Text 0153Z 1143 Validation for constraint name failed; incompatible data exists in referencing base table name and referenced base table name. To display the data violating the constraint, please use...
  • Page 660 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 7 of 84) SQLSTATE SQLCODE Error Text 01600 2000 Error messages for compiler main, IPC, and DEFAULTS table; assertions for optimizer. 01601 2001 Error or warning num occurred while opening or reading from DEFAULTS table name.
  • Page 661 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 8 of 84) SQLSTATE SQLCODE Error Text 0160P 2025 Unable to create server process name. CPU is unavailable; text. 0160R 2027 NonStop Kernel error num while sending a startup message to process name.
  • Page 662 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 9 of 84) SQLSTATE SQLCODE Error Text 0161S 2064 Dynamic 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 663 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 10 of 84) SQLSTATE SQLCODE Error Text 0162M 2094 A module timestamp statement has already appeared in this module. The previous timestamp is being retained and this latest one ignored.
  • Page 664 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 11 of 84) SQLSTATE SQLCODE Error Text 01705 3005 A DECLARE CURSOR statement cannot dynamically get its cursor name from a host variable while also statically declaring a cursor specification.
  • Page 665 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 12 of 84) SQLSTATE SQLCODE Error Text 0170R 3027 name is not a valid simple name; it has more than one name part. 0170S 3028 Specifying a privilege column list in the INSERT clause is not yet supported.
  • Page 666 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 13 of 84) SQLSTATE SQLCODE Error Text 0171H 3053 Duplicate PRIMARY KEY clauses in column definition name. 0171I 3054 The NOT DROPPABLE clause is allowed only in PRIMARY KEY and NOT NULL constraint definitions.
  • Page 667 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 14 of 84) SQLSTATE SQLCODE Error Text 0172B 3083 Duplicate [NO]AUDITCOMPRESS clauses. 0172C 3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement.
  • Page 668 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 15 of 84) SQLSTATE SQLCODE Error Text 01732 3110 The LIKE clause and ATTRIBUTE(S) clause cannot coexist in the same statement. 01733 3111 The LIKE clause and LOCATION clause cannot coexist in the same statement.
  • Page 669 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 16 of 84) SQLSTATE SQLCODE Error Text 0173V 3139 A range-partitioned index requires a FIRST KEY clause. 0173W 3140 The isolation level cannot be READ UNCOMMITTED for an INSERT, UPDATE, DELETE, or DDL statement.
  • Page 670 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 17 of 84) SQLSTATE SQLCODE Error Text 0174N 3167 Duplicate [ NOT ] DROPPABLE clauses. 0174O 3168 The FOR ... ACCESS clause is not allowed in a CREATE VIEW statement.
  • Page 671 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 18 of 84) SQLSTATE SQLCODE Error Text 01801 4001 Column name is not found. Tables in scope: name. Default schema: name. 01802 4002 Column name is not found. Table name not exposed. Tables in scope: name.
  • Page 672 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 19 of 84) SQLSTATE SQLCODE Error Text 0180N 4023 The degree of each row value constructor (num) must equal the degree of the target table column list (num).
  • Page 673 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 20 of 84) SQLSTATE SQLCODE Error Text 0181D 4049 A CASE expression cannot have a result data type of both type and type. 0181E 4050 The operands of the name predicate must be comparable character data types (that is, of the same character set and collation).
  • Page 674 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 21 of 84) SQLSTATE SQLCODE Error Text 01825 4077 Function name accepts only one or two operands. 01826 4078 Function name does not accept a weight operand.
  • Page 675 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 22 of 84) SQLSTATE SQLCODE Error Text 0182Z 4107 Column name has no default value, so DEFAULT cannot be specified. 01830 4108 Inside a ROWS SINCE, another sequence function contained an invalid reference to the THIS function.
  • Page 676 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 23 of 84) SQLSTATE SQLCODE Error Text 01846 4150 Primary key of table expression name must be used for join with embedded name expression. Tables in scope: name.
  • Page 677 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 24 of 84) SQLSTATE SQLCODE Error Text 0184U 4174 JOIN_ORDER_BY_USER prevented compiler from reordering query tree. 0184V 4175 Join between embedded name expression and embedded name expression not supported. Tables in scope: name.
  • Page 678 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 25 of 84) SQLSTATE SQLCODE Error Text 0185Z 4215 Stream access is not allowed on a nonaudited table. Table: name. 01860 4216 The FIRST/ANY n syntax cannot be used with an embedded update or embedded DELETE statement.
  • Page 679 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 26 of 84) SQLSTATE SQLCODE Error Text 01J03 7003 A plan using cluster sampling could not be produced for this query. 01K01 8001 Internal executor error. 01K02 8002 The current nowaited operation is not complete.
  • Page 680 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 27 of 84) SQLSTATE SQLCODE Error Text 01K3X 8141 An error was artificially injected, to test error handling. File name at line num. 01K8C 8300 Late name resolution failed.
  • Page 681 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 28 of 84) SQLSTATE SQLCODE Error Text 01KBW 8428 The argument to function name is not valid. 01KBX 8429 The preceding error actually occurred in function name.
  • Page 682 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 29 of 84) SQLSTATE SQLCODE Error Text 01KH2 8614 SQL cannot begin a transaction when multiple contexts exist. 01KJG 8700 An assertion failure or out-of-memory condition occurred during parallel execution.
  • Page 683 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 30 of 84) SQLSTATE SQLCODE Error Text 01KMW 8824 The input module_id does not have a module name. 01KMX 8825 Module is already added into the current context.
  • Page 684 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 31 of 84) SQLSTATE SQLCODE Error Text 01KNM 8850 The table specified in this cursor update or DELETE statement is different than the table specified in the declare cursor statement.
  • Page 685 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 32 of 84) SQLSTATE SQLCODE Error Text 01KOJ 8883 The current context has violation checking functions disabled. Use SQL_EXEC_SetUdrAttributes_Internal() to enable it. 01KOK 8884 Prohibited SQL statement attempted.
  • Page 686 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 33 of 84) SQLSTATE SQLCODE Error Text 01L5Q 9206 You are not authorized to read/write object name. Verify that you have the necessary access privileges. 01L5R 9207...
  • Page 687 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 34 of 84) SQLSTATE SQLCODE Error Text 01M0M 10022 Sort Error: FILE_CREATE failed 01M0N 10023 Sort Error: FILE_OPEN_ failed 01M0O 10024 Sort Error: SetMode failed 01M0O 10024...
  • Page 688 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 35 of 84) SQLSTATE SQLCODE Error Text 01N5U 11210 Specified signature is invalid. Reason: Missing [ ] for OUT/INOUT parameter at position value. 01N5V 11211 Specified signature is invalid. Reason: Unknown parameter type used at position value.
  • Page 689 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 36 of 84) SQLSTATE SQLCODE Error Text 01P06 13006 Switch has bad value, num, for its expression at line num in file name. 01P07 13007 Missing output file argument after the -c option.
  • Page 690 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 37 of 84) SQLSTATE SQLCODE Error Text 01P0Z 13035 Invalid line number num for line pragma; ignoring the rest. 01P10 13036 C/C++ syntax error in switch/for/while condition near line num.
  • Page 691 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 38 of 84) SQLSTATE SQLCODE Error Text 01P1U 13066 Identifier name was expected to be a structure type near line num. 01P1V 13067 Unable to open source file name.
  • Page 692 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 39 of 84) SQLSTATE SQLCODE Error Text 01PEA 13514 The CHARACTER SET attribute is not implemented in SQL/MX. 01PEB 13515 Picture name is not valid for a host variable.
  • Page 693 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 40 of 84) SQLSTATE SQLCODE Error Text 01R0C 15012 File read error on the help file. 01R0D 15013 This command is not supported by the SQLCI OLE server.
  • Page 694 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 41 of 84) SQLSTATE SQLCODE Error Text 01T31 20109 text 01U01 30001 A rowset must be composed of host variable arrays. 01U02 30002 The given rowset size (num) must be smaller or equal to the smallest dimension (num) of the arrays composing the rowset.
  • Page 695 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 42 of 84) SQLSTATE SQLCODE Error Text 01Z8C 25300 Module module has module version version1; node node does not support module versions lower than version2. 01Z8D 25301 Module module has module version version1;...
  • Page 696 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 43 of 84) SQLSTATE SQLCODE Error Text 0A000 -1120 Attempting to change the audit flags for a table in an unsupported way. 0A000 -1121 Attempting to perform a partition add, move, or drop on table name.
  • Page 697 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 44 of 84) SQLSTATE SQLCODE Error Text 0A000 -3036 The SET CONSTRAINT clause in the ALTER TABLE statement is not yet supported. 0A000 -3070 The [NO]AUDIT clause is not supported.
  • Page 698 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 45 of 84) SQLSTATE SQLCODE Error Text 22003 -8411 A numeric overflow occurred during an arithmetic computation or data conversion. 22007 -3045 Invalid date 'date'. 22007 -3046 Invalid time 'time'.
  • Page 699 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 46 of 84) SQLSTATE SQLCODE Error Text 24000 -8013 Trying to update or delete from a cursor that is not in the fetched state. 24000 -8811 Trying to close a statement that is either not in the open state or has not reached EOF.
  • Page 700 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 47 of 84) SQLSTATE SQLCODE Error Text 25000 -8844 A transaction started by SQL that was committed or aborted by user application from outside of SQL, has now been cleaned up.
  • Page 701 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 48 of 84) SQLSTATE SQLCODE Error Text 40000 -8821 Rollback transaction failed during the process of fetching the statement. 40000 -8839 Transaction was aborted. 40003 -8608 Transaction subsystem name returned error num on rollback transaction.
  • Page 702 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 49 of 84) SQLSTATE SQLCODE Error Text 42000 -15023 The USING list value num exceeds the SQLCI limit of num characters. 42000 -15024 The USING list quoted literal name must be followed by either a comma or a semicolon.
  • Page 703 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 50 of 84) SQLSTATE SQLCODE Error Text 42000 -2092 A module statement has already appeared in this file. The previous definition, name, is being retained and this latest one ignored.
  • Page 704 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 51 of 84) SQLSTATE SQLCODE Error Text 42000 -3011 name is not a valid qualified name; it has more than 3 name parts. 42000 -3012 COUNT is the only aggregate function that accepts (*) as an operand.
  • Page 705 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 52 of 84) SQLSTATE SQLCODE Error Text 42000 -3052 Duplicate NOT NULL clauses in column definition name. 42000 -3053 Duplicate PRIMARY KEY clauses in column definition name.
  • Page 706 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 53 of 84) SQLSTATE SQLCODE Error Text 42000 -3084 The BLOCKSIZE clause is not allowed in the ALTER TABLE ... ATTRIBUTE(S) statement. 42000 -3085 Duplicate [NO]BUFFERED clauses.
  • Page 707 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 54 of 84) SQLSTATE SQLCODE Error Text 42000 -3111 The LIKE clause and LOCATION clause cannot coexist in the same statement. 42000 -3112 The LIKE clause and PARTITION clause cannot coexist in the same statement.
  • Page 708 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 55 of 84) SQLSTATE SQLCODE Error Text 42000 -3150 Duplicate WITH HEADING phrases in LIKE clause in CREATE TABLE statement. 42000 -3151 Duplicate WITH HORIZONTAL PARTITIONS phrases in LIKE clause in CREATE TABLE statement.
  • Page 709 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 56 of 84) SQLSTATE SQLCODE Error Text 42000 -3181 Invalid logical name, a three part logical name is required. 42000 -3187 Not supported: SET STREAM TIMEOUT per a specific stream.
  • Page 710 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 57 of 84) SQLSTATE SQLCODE Error Text 42000 -4016 The number of derived columns (num) must equal the degree of the derived table (num). 42000 -4017 Derived column name name was specified more than once.
  • Page 711 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 58 of 84) SQLSTATE SQLCODE Error Text 42000 -4042 The operands of a comparison predicate must be of equal degree. 42000 -4043 The operand of function name must be character.
  • Page 712 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 59 of 84) SQLSTATE SQLCODE Error Text 42000 -4072 The operand of function name must be a datetime containing a name. 42000 -4073 The COLLATE clause might appear only after an expression of character data type, not type.
  • Page 713 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 60 of 84) SQLSTATE SQLCODE Error Text 42000 -4109 Sequence functions placed incorrectly: name. 42000 -4110 The query contains sequence functions but no SEQUENCE BY clause: name.
  • Page 714 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 61 of 84) SQLSTATE SQLCODE Error Text 46007 -11208 Specified signature is invalid. Reason: The list of parameter types must be enclosed in parentheses. 46007 -11209 Specified signature is invalid. Reason: the number of parameters value must match the number of parameters in Java method.
  • Page 715 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 62 of 84) SQLSTATE SQLCODE Error Text X010L -1021 SQL is already initialized on system name. X010M -1022 Schema name already exists. X010N -1023 Only the super ID user can name an authorization ID other than the current user name.
  • Page 716 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 63 of 84) SQLSTATE SQLCODE Error Text X011G -1052 Trying to drop a constraint that does not belong to requested table. X011H -1053 Unique index name could not be created because the column(s) specified contain duplicate data.
  • Page 717 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 64 of 84) SQLSTATE SQLCODE Error Text X012F -1087 Lock cannot be granted, conflicting operation is in progress. X012G -1088 Cannot instantiate object name, conflicting lock exists.
  • Page 718 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 65 of 84) SQLSTATE SQLCODE Error Text X013O -1132 An added column cannot have both DEFAULT NULL and NOT NULL. X013P -1133 Only the super ID can perform this operation.
  • Page 719 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 66 of 84) SQLSTATE SQLCODE Error Text X015B -1191 Cannot find SQL/MP system catalog name, DEVICE_GETINFOBYLDEV error num. X015C -1192 Cannot find SQL/MP system catalog name, FILE_GETINFOBYNAME_ error num.
  • Page 720 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 67 of 84) SQLSTATE SQLCODE Error Text X020G -2016 Server process name was started but had undefined externals. X020H -2017 Unable to create server process name. No more processes (PCBs) available.
  • Page 721 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 68 of 84) SQLSTATE SQLCODE Error Text X022B -2083 Error num while naming or locating file name. X022C -2084 Error num while writing num bytes to file name.
  • Page 722 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 69 of 84) SQLSTATE SQLCODE Error Text X034I -3162 Procedure parameter name was not used. X034J -3163 Host variable name appears more than once in the INTO list.
  • Page 723 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 70 of 84) SQLSTATE SQLCODE Error Text X044M -4166 ORDER BY clause not supported in UNION of two streams. Tables in scope: name, name. X044N -4167 Embedded name statements not supported in subqueries.
  • Page 724 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 71 of 84) SQLSTATE SQLCODE Error Text X045Q -4206 Embedded name only supported for updateable views. View: name. X045R -4207 Index name and other indexes covering a subset of columns do not cover all output values of stream.
  • Page 725 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 72 of 84) SQLSTATE SQLCODE Error Text X0600 -6000 Internal error in the query optimizer. X0602 -6002 The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid values. If you...
  • Page 726 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 73 of 84) SQLSTATE SQLCODE Error Text X08P6 -8906 An invalid or corrupt MXUDR reply could not be processed, possibly due to memory corruption in MXUDR while executing friendly user-defined routines or an internal error in SQL/MX.
  • Page 727 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 74 of 84) SQLSTATE SQLCODE Error Text X08FC -8552 Error num was returned by the Distribution Service while fetching the version of the system name. X08FD -8553 Stream overflow;...
  • Page 728 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 75 of 84) SQLSTATE SQLCODE Error Text X08N3 -8831 Either no current context or the module to which the statement belongs is not added to the current context.
  • Page 729 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 76 of 84) SQLSTATE SQLCODE Error Text X08OX -8897 RPC exception in CLI request from non-trusted shadow client to trusted shadow server. X08OY -8898 Internal error in CLI.
  • Page 730 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 77 of 84) SQLSTATE SQLCODE Error Text X0A0A -10010 Sort Error: Run number is invalid X0A0B -10011 Sort Error: Error reading Scratch File X0A0C -10012 Sort Error: Scratch Block number is invalid...
  • Page 731 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 78 of 84) SQLSTATE SQLCODE Error Text X0B5M -11202 Language Manager initialization failed. Details: Unable to initialize JVM. X0B5N -11203 The Language Manager failed to create its class loader, possibly due to corrupt LmClassLoader.class file.
  • Page 732 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 79 of 84) SQLSTATE SQLCODE Error Text X0D09 -13009 Language Manager encountered internal error string. X0D0A -13010 JVM raised an exception. Details: string. X0D0B -13011 Specified signature is invalid. Reason: The Java signature for a Java main method must be (java.lang.string[ ]).
  • Page 733 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 80 of 84) SQLSTATE SQLCODE Error Text X0D14 -13040 Expecting “)” near line num. X0D16 -13042 Unnamed declaration near line num. X0D17 -13043 Expecting name near line num.
  • Page 734 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 81 of 84) SQLSTATE SQLCODE Error Text X0D20 -13072 Module Version Specification String MVSS-string is not a Regular Identifier, or is longer than 31 characters. X0D21 -13073 Module name module-name is not a value OSS file name, or is longer than 128 characters.
  • Page 735 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 82 of 84) SQLSTATE SQLCODE Error Text X0DEI -13522 DECLARE SECTION cannot be nested. X0DEJ -13523 END DECLARE SECTION without a matching BEGIN DECLARE SECTION. X0DEK -13524 DECLARE SECTION encountered in unexpected program section.
  • Page 736 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 83 of 84) SQLSTATE SQLCODE Error Text X0F10 -15036 Invalid filecode OR invalid function argument X0FRR -15999 SQLCI internal error. X0G00 -16000 Error message file not found.
  • Page 737 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values Table 21-1. SQLSTATE Values (page 84 of 84) SQLSTATE SQLCODE Error Text X0P8M -25310 Module module has module version version1, the local SQL/MX software version (MXV) can execute modules only with module version MXV1.
  • Page 738 SQLSTATE Values Returned by NonStop SQL/MX SQLSTATE Values HP NonStop SQL/MX Messages Manual—640324-001 21 -86...

  • Page 739: Non-Sqlcode Error Messages

    INITIALIZE SQL operation. Effect. The operation fails. Recovery. If you believe that the system metadata exists, contact your service provider. Otherwise, run the InstallSqlmx script without specifying the Rebuild (-b) option. HP NonStop SQL/MX Messages Manual—640324-001 A- 1...
  • Page 740 Recovery. Multiple instances of system metadata are not allowed on the same system. Contact your service provider. Install0004 Install0004: SQL/MX is already installed in volume. Cause. You cannot install NonStop SQL/MX at the volume volume. NonStop SQL/MX has already been installed. Effect. The operation fails. Recovery. None.
  • Page 741 Install0010: The command line argument argument is invalid. Cause. You specified an invalid argument with argument. Effect. The operation fails. Recovery. Enter one of these three options (-l, -b, or -help) and retry the request. HP NonStop SQL/MX Messages Manual—640324-001 A- 3...
  • Page 742 Reinstall the missing SQL/MX files from the SUT and restart the SQL/MX installation. Cause. SQL/MX files installed from the SUT are missing. Effect. The operation fails. Recovery. Reinstall the missing SQL/MX files from the SUT and restart installation. HP NonStop SQL/MX Messages Manual—640324-001 A- 4...
  • Page 743 Cause. One or more processors in the system do not meet the minimum hardware requirements for installing NonStop SQL/MX. All processors in a node on which NonStop SQL/MX Release 2.0 (or a superseding product) is installed must be Model 1954 (S72000) or newer.

  • Page 744: Metadata Migration Utility

    Messages Manual for recovery details. Cause. The SQL/MX file file-name is not present. Effect. The installation of NonStop SQL/MX continues. This warning can be ignored if the DDL licensing product (T0394) was not installed. If the DDL licensing product was installed, NonStop SQL/MX is not fully functional, and the steps described under Recovery must be performed.
  • Page 745 Effect. The operation fails. Recovery. None. migr0006 migr0006: SQL/MX is not installed. Cause. NonStop SQL/MX is not installed on the system, which is required. Effect. The operation fails. Recovery. Install NonStop SQL/MX prior to running the migrate utility. HP NonStop SQL/MX Messages Manual—640324-001...
  • Page 746 Metadata Migration Utility migr0007 migr0007: Incorrect version of SQL/MX is installed for migrate. Cause. NonStop SQL/MX is installed on the system, but it is the wrong version. Effect. The operation fails. Recovery. Install NonStop SQL/MX Release 2.x. migr0008 migr0008: Environment variable NSK_VOL or NSK_SUBVOL or SQLMX_NAMETYPE=NSK not specified prior to use of migrate utility.
  • Page 747 The filename has defaulted to error_log.out. Cause. A file name specified in the ERROR_LOG option already exists and CLEAR is not used. Effect. None. The file name will default to error_log.out. Recovery. None. This message is a warning. HP NonStop SQL/MX Messages Manual—640324-001 A- 9...
  • Page 748 ERROR_LOG has defaulted to error_log.out. Cause. The ERROR_LOG option was not chosen for the EXECUTE command. Effect. None. An ERROR_LOG is captured to the default file name error_log.out. Recovery. None. This message is a warning. HP NonStop SQL/MX Messages Manual—640324-001 A -10...

  • Page 749: Mxgnames Utility

    Cause. An error occurred during the reading or writing of the EDIT file. Effect. The operation fails. Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem. HP NonStop SQL/MX Messages Manual—640324-001 A -11...
  • Page 750 MXGNAMES0004: Command line error: output-format is required. Cause. You failed to specify either output format (-BR2 or -TMF) at the command line. Effect. The operation fails. Recovery. Specify the output format at the command line and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 A -12...
  • Page 751 Cause. You specified a value for an option that does not take a value, such as -TMF, -BR2, or -nocomment. Effect. The operation fails. Recovery. Remove the unnecessary values specified for the option and resubmit. HP NonStop SQL/MX Messages Manual—640324-001 A -13...
  • Page 752 Non-SQLCODE Error Messages MXGNAMES Utility HP NonStop SQL/MX Messages Manual—640324-001 A -14...

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents