HP NonStop SQL/MX, NonStop SQL/MX 3.0 Messages Manual

HP NonStop SQL/MX Messag es 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 Published

640324-001 February 2011

Document History

Part Number Product Version Published

640324- 001 NonStop SQL/M X R elease 3.0 February 2011

Legal Notices

Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Techn ical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its

subsidiaries in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The

Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the

Open Software Foundation, Inc.

OSF MAKES NO WAR R ANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANT IES OF MERCHANT ABILITY AND FITNESS FOR A PARTICUL AR PURPOS E.

OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material.

© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation. © 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute of Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.

This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.

Printed in the US

Hewlett-Packard Company—640324-001

HP NonStop SQL/MX Messages Manual

Glossary Figures

Legal Notices What’s New in This Manual v

Manual Information v New and Changed Information v

About This Manual xi

Audience xi Related Documentation xi Notation Conventions xiv HP Encourages Your Comments xvi

1. Message Handling

Viewing SQL/MX Messages 1-1

Non-SQLCODE Error Messages 1-2

Messages That Report a Guardian File System Error 1-2 SQLSTATE and SQLCODE 1-3 Contacting Your Service Provider 1-3 Process Control Procedure Errors 1-4

Contents

HP NonStop SQL/MX Messages Manual—640324-001

2. General Messages (0 through 999)

3. Data Definition Language (DDL) Messages (1000 through

1999)

4. SQL/MX MXCMP Messages (2000 through 2999)

5. Parser and Compilation Messages (3000 through 3999)

6. Binder and Compilation Messages (4000 through 4999)

7. Normalizer Messages (5000 through 5999)

8. Optimizer Messages (6000 through 6999)

9. Generator Messages (7000 through 7999)

10. Executor Messages (8000 through 8999)

11. UP DATE 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

Contents

HP NonStop SQL/MX Messages Manual—640324-001

iii

13. Trigger, UDR Server, and Language Manager Messages (11000 through 11399)

14. SQLC and SQLCO Preprocessor Messages (13000 through

13999)

15. MXCI Messages (15000 through 15999)

16. Messages Generated by the Message System (16000 through 16999)

17. Internal Stored Procedures Messages (19000 through 19999)

18. Utility Messages (20000 through 23099)

19. Versioning and Distribution Messages (25000 through

25399)

Distribution Messages (25400-25499) 19-25 JDBC Driver Error Messages (29000-29999) 19-32

20. Rowsets Messages (30000 through 30999)

21. SQLSTATE Values Returned by NonStop SQL/MX

SQLSTATE and SQLCODE Considerations 21- 1 SQLSTATE Values 21-2

A. Non-SQLCODE Error Messages

InstallSqlmx script A-1 Metadata Migration Utility A-6 MXGNAMES Utility A-11

Tables

Table 21-1. SQLSTATE Values 21-2

Contents

HP NonStop SQL/MX Messages Manual—640324-001

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 subsequent H-series RVUs, until otherwise indicated by its replacement publications.

Document History

New and Changed Information

Changes to the 640324-001 manual:

•

Updated the following error messages:

SQL 1004

SQL 1020

SQL 1055

SQL 1080

SQL 1085

SQL 1087

SQL 1098

SQL 1112

SQL 1132

SQL 1140

Part Number Published

640324- 001 February 2011

Part Number Product Ve rsion Published

640324- 001 NonStop SQL/M X R elease 3.0 February 2011

What’s New in This Manual

HP NonStop SQL/MX Messages Manual—640324-001

New and Changed Information

SQL 1143

SQL 1150 and SQL 1151

SQL 1225

SQL 1238

SQL 1239

SQL 1263

SQL 1270 and SQL 1271

SQL 1500 through SQL 1503

SQL 2011 through SQL 2020

SQL 2027 and SQL 2028

SQL 2033 and SQL 2034

SQL 2055

SQL 2984

SQL 3008

SQL 3014

SQL 4082

SQL 4129

SQL 4161

SQL 4320

SQL 6003

SQL 6008

SQL 8402

SQL 8411

SQL 8419

SQL 8834

SQL 8837

SQL 9215

SQL 10003 through SQL 10013

SQL 10015 through SQL 10024

SQL 10026 through SQL 10029

What’s New in This Manual

HP NonStop SQL/MX Messages Manual—640324-001

vii

New and Changed Information

SQL 10049

SQL 11041

SQL 11022

SQL 11027

SQL 11101 through SQL 11111

SQL 11209

SQL 11242 through SQL 11244

SQL 19020

SQL 20011

SQL 20025

SQL 20037

SQL 20123

SQL 20127

SQL 20137

SQL 20142

SQL 20149

SQL 20154 and SQL 20155

SQL 20176

SQL 20354

SQL 20360

SQL 20371

SQL 20733

SQL 20752

SQL 20755

SQL 20759

SQL 20779

SQL 20795

SQL 23001 through SQL 23003

SQL 23007

SQL 23011 through SQL 23020

What’s New in This Manual

HP NonStop SQL/MX Messages Manual—640324-001

viii

New and Changed Information

SQL 25208

SQL 25214

SQL 25216

SQL 25302 and SQL 25303

SQL 25308

SQL 25310

•

Added the following error messages:

SQL 1154

SQL 1158

SQL 1159

SQL 1165

SQL 1168

SQL 1174

SQL 1189

SQL 1193 and SQL 1195

SQL 1249

SQL 1276

SQL 1277

SQL 1278

SQL 1289

SQL 1295

SQL 1311 and SQL 1312

SQL 1401

SQL 1506

SQL 2235

SQL 3218

SQL 3409

SQL 3415

SQL 4193

SQL 4195 and SQL 4196

What’s New in This Manual

HP NonStop SQL/MX Messages Manual—640324-001

New and Changed Information

SQL 4198

SQL 4220

SQL 4336 through SQL 4338

SQL 4353

SQL 4362

SQL 6004

SQL 8019

SQL 8022

SQL 8401

SQL 8432 and SQL 8433

SQL 8581

SQL 8598

SQL 8887

SQL 8889

SQL 8900

SQL 8916 and SQL 8917

SQL 10025

SQL 10030 through SQL 10043

SQL 10045 and SQL 10046

SQL 10051

SQL 10101 through SQL 10119

SQL 10130 through SQL 10141

SQL 10150 through SQL 10153

SQL 11002

SQL 11046

SQL 11049

SQL 15001

SQL 15039

SQL 19022

SQL 20339 and SQL 20340

What’s New in This Manual

HP NonStop SQL/MX Messages Manual—640324-001

New and Changed Information

SQL 20376 and SQL 20377

SQL 20454

SQL 20520 through SQL 20532

SQL 20562

SQL 20588 and SQL 20589

SQL 20794

SQL 20816

SQL 20820 through SQL 20822

SQL 20877

SQL 25003

SQL 25006

SQL 25007

SQL 25209

SQL 25220 through SQL 25222

SQL 25250 through SQL 25268

SQL 30026 through SQL 30029

SQL 30035

SQL 30037

•

Added SQLSTATE 21000 on page 21-45.

•

Removed SQL message 2054.

•

Changed SQL message 8910 to 8916 and updated its description on page 10-53.

•

Changed SQL message 8911 to 8917 and updated its description on page 10-54.

•

Removed SQL message 20240.

•

Removed SQL messages from 20278 through 20289.

•

Removed SQL message 25105.

•

Removed SQL message 25304.

HP NonStop SQL/MX Messages Manual—640324-001

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.

Audience

This manual is for NonStop SQL/MX database administrators and programmers who use the NonStop SQL/MX conversational or programmatic interface.

Readers of this manual must know the:

•

fundamenta ls of NonSt op SQL/MX

•

fundamentals of the HP NonStop operating system

•

fundamentals of the SQL/MX conversational interface (MXCI)

Other Related Documentation

Guard ian Proc edure Err ors and Messages Manual

Describes the Guardian messages for HP NonStop systems that use HP NonStop Kernel operating system.

Guard ian Proc edure Calls Refere nc e M anual

Describes t he syntax of Guardian procedure calls.

About This Manual

HP NonStop SQL/MX Messages Manual—640324-001

xiv

Notation Conventions

Hypertext Links

Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example:

This requirement is described under Backup DAM Volumes and Physical Disk

Drives on page 3-2.

General Syntax Notation

This list summarizes the notation conventions for syntax presentation in this manual.

UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type

these items exactly as shown. Items not enclosed in brackets are required. For example:

MAXATTACH

lowercase italic letters. Lowercase italic letters indicate variable items that you supply.

Items not enclosed in brackets are required. For example:

file-name

Punctuation. Parentheses, commas, semicolons, and other symbols not previously

described must be typed as shown. For example:

error := NEXTFILENAME ( file-name ) ;

LISTOPENS SU $process-name.#su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example:

"[" repetition-constant-list "]"

Item Sp aci ng. Spaces shown between items are required unless one of the items is a

punctuation symbol such as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items:

$process-name.#su-name

Line Sp acing. 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

About This Manual

HP NonStop SQL/MX Messages Manual—640324-001

Notation for Messages

a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] LINE

[ , attribute-spec ]…

Notation for Messages

This list summarizes the notation conventions for the presentation of displayed messages in this manual.

Bold Text. Bold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE

?123

CODE RECEIVED: 123.00

The user must press the Return key after typing the input.

Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or

returned exactly as shown. For example:

Backup Up.

lowercase italic letters. Lowercase italic letters indicate variable items whose values are

displayed or returned. For example:

p-register

process-name

[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For

example:

Event number = number [ Subject = first-subject-value ]

A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example:

proc-name trapped [ in SQL | in SQL file system ]

{ } 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

About This Manual

HP NonStop SQL/MX Messages Manual—640324-001

xvi

Change Bar Notation

either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example:

obj-type obj-name state changed to state, caused by { Object | Operator | Service }

process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in

brackets or braces. For example:

Transfer status: { OK | Failed }

% Percent Sign. A percent sign precedes a number that is not in decimal notation. The

% notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example:

%005400

%B101111

%H2F

P=%p-register E=%e-register

Change Bar Notat ion

Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example:

The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).

The CRE has many new message types and some new message type codes for old message types. In the C RE, the messa ge type S Y STEM incl udes all me ssages 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.

Include the document title, part number, and any comment, error found, or suggestion for improvement concerning this document.

HP NonStop SQL/MX Messages Manual—640324-001

1-1

1 Message Handling

NonS top SQL/MX reports exception condi tion messages at the SQL/MX conve rsational interface (MXCI) window, in SQL preprocessor and compiler listings, and during the execution of embedded SQL programs.

You obtain the error messages that result from the execution of an SQL statement within an embedded program in C or COBOL by using the GET DIAGNOSTICS statement to access the SQL diagnostics area. For detailed information about accessing SQL/MX messages in a programmatic environment, see the SQL/MP Programming Manual for C.

Most SQL/MX exception condition messages describe error conditions for which recovery action is required. Some messages are warnings that provide information for which no action is required.

Error messages that appear in response to SQL/MX commands are logged to the MXCI application's log file if you have used the LOG command to request them.

The format of an SQL/MX error is “*** ERROR” followed by the error number in brackets, and the descriptive text. Use the error number shown to find information about a par ticul ar erro r in thi s m anual. F or e xampl e , inform ati on f or S QL/M X error 1125 can be found under “SQL 1125.”

Messages and events are listed in this manual in numeric order, broken down by the component that produced them.

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.

This message number is the SQLCODE value (without the sign). In this manual, you will find this message information for ERROR[1000]:

SQL 1000

Cause. You specified a statement with incorrect syntax. Effect. The SQL/MX statement fails. Recovery. Correct the syntax and resubmit.

From MXCI, use the ERROR command to:

•

Look up a message by its SQLCODE.

1000 A syntax error occurred.

Message Handling

HP NonStop SQL/MX Messages Manual—640324-001

1-2

Non-SQLCODE Error Messages

•

Display information for a message, including its SQLCODE, the SQLSTATE values for the SQLCODE, and the message text.

For more information about the ERROR command, see the SQL/MX Reference Manual. For detailed cause, effect, and recovery information for error messages, see this manual.

Non-SQLCODE Error Messages

Non-SQLCODE error messages are listed in Appendix A of this manual and include messages generated by the InstallSqlmx script, Metadata Migration utility, and the MXGNAMES utility. The format for these messages ar e: th e pro cess that gene rates the error, followed by an error number and a descriptive text:

Messages That Report a Guardian File System Error

For more information about messages that report a Guardian file system error, see the Guardian Procedure Errors and Messages Manual. Information about the error can also be found using the TACL “error” command. This command can be either used directly from TACL, for example:

$DATA14 HANLON 10> error 73

0073 [EGUARDIAN LOCKED] The disk file or record is locked.

or invoked from an OSS prompt:

/usr/mhanlon: gtacl -c 'error 73'

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.

Install0018: A processor on the system does not meet the hardware requirements for SQL/MX.

Message Handling

HP NonStop SQL/MX Messages Manual—640324-001

1-3

SQLSTATE and SQLCODE

SQLSTATE and SQLCODE status codes are returned to indicate either that an SQL statement completed successfully or that an exception condition was raised during execution of an SQL statement.

The ANSI SQL-92 SQLSTATE variable is a five-character string with a two-character class code followed by a three-character subclass code. An SQLSTATE value of 00000 indicates successful completion.

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.

NonStop SQL/MX also returns a numeric SQLCODE value after SQL statement execution. SQLCODE values with negative numbers signify errors. SQLCODE values with positive numbers other than 0 (successful completion) or 100 (no data was found) signify warning messages. NonStop SQL/MX identifies all messages by their unsigned SQLCODE value and their calculated SQLSTATE value. The SQLCODE is used to calculate the SQLS TAT E valu e for all SQL/MX messag es other than tho se for w hich an ANSI SQL-92 SQLSTATE value exists.

The SQLCODE parameter is a deprecated feature that is supported to maintain compatibility with earlier versions of the American standard.

Table 21-1, SQLSTATE Values, on page 21-2 identifies the equivalent SQLSTATE and

SQLCODE values for SQL/MX warning and error messages.

Contacting Your Service Provider

Some messages have no recovery, and you will be instructed to contact your service provider. If you cannot solve a problem, go to the Cluster Support Manager and open a problem report. The Cluster Support Manager collects, saves, and manages all information needed by your service provider to solve the problem.

For more information, see the NonStop Support Toolkit Help.

Message Handling

HP NonStop SQL/MX Messages Manual—640324-001

1-4

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. Many programs that are part of NonStop systems make calls to these procedures and, in some cases, must report procedure errors to the user.

When a process control procedure error is reported as part of a message (such as a message to the Application log), the name of the procedure is normally included in the message. An exception is when a PROCESS_CREATE_ error might be referred to as a process creation error.

See the Guardian Procedure Calls Reference Manual for the meaning of values returned by these and other types of process control errors:

•

PROCESS_GETNFO_Errors

•

PROCESS_GETPAIRINFO _Errors

•

Process Creation Errors (returned by the PROCESS_CREATE_procedure)

HP NonStop SQL/MX Messages Manual—640324-001

2-1

General Messages (0 through 999)

SQL 100

Cause. You have reached the end of a cursor, and there is no more data to be

returned. When you enter a noncursor query (SELECT * FROM t WHERE...; DELETE FROM t

WHERE...;), SQL/MX returns warning 100 to indicate that zero rows satisfied the predicate, and zero rows were affected. In embedded SQL/MX, on a cursor FETCH, SQL/MX returns this warning to indicate that it has reached the end of rows.

Effect. You will not be able to get any more rows from this cursor or SELECT statement.

Recovery. This is an informational message. Start a new cursor for a new read.

100 The "no data" completion condition (SQLCODE = +100).

General Messages (0 through 999)

HP NonStop SQL/MX Messages Manual—640324-001

2-2

HP NonStop SQL/MX Messages Manual—640324-001

3-1

Data Definition Language (DDL) Messages (1000 through 1999)

SQL 1001

Where name is the name of the module. Where num is the line number. Where details are the details of the error.

Cause. This is an internal error. Effect. The operation fails. Recovery. None. Contact your service provider.

See Contacting Your Service Provider on page 1-3.

SQL 1002

Where catalog is the ANSI name of the target catalog. Where node is the node where the process executes. Cause. The catalog is not visible on the local node, either because it does not exist or

because it exists elsewhere on the network but has not been registered on the local node.

Effect. The operation fails. Recovery. Enter a valid catalog name (or register the catalog on the node indicated)

and resubmit.

1001 An internal error occurred in module name on line num. DETAILS(details).

1002 Catalog catalog does not exist or has not been registered on node node.

Data Definition Language (DDL) Messages (1000 through 1999)

HP NonStop SQL/MX Messages Manual—640324-001

3-2

SQL 1003

Where schema is the ANSI name of the affected schema. Cause. In a replication context: a REPLICATION SCHEMA operation specified a

schema that does not exist.

Effect. The operation fails. Recovery. Check that a schema named schema does exist and resubmit.

SQL 1004

Where object-name is the name of an SQL/MX object. Cause. You attempted an operation on an object that does not exist or attempted an

operation on an object with the wrong type. For example, you tried to drop a view but specified a table name.

Effect. The operation fails. Recovery. Check that an object object-name exists. If you did not fully qualify the

name, check that the defaults generate the correct fully qualified name and resubmit.

SQL 1005

Where constraint-name is the name of a column constraint or table constraint. Cause. The ALTER TABLE statement you attempted requires the existence of a

constraint named constraint-name.

Effect. The operation fails. Recovery. Check that a constraint named constraint-name exists for the table

specified. You can use the SHOWDDL command to find the names of the constraints that exist on a table.

1003 Schema schema does not exist.

1004 Object object-name does not exist or object type is invalid for the current operation.

1005 Constraint constraint-name does not exist.

Data Definition Language (DDL) Messages (1000 through 1999)

HP NonStop SQL/MX Messages Manual—640324-001

3-3

SQL 1006

Where index-name is an SQL/MX object name. Cause. The operation you attempted requires the existence of an index named

index-name.

Effect. The operation fails. Recovery. Check that an index named index-name does exist. If you did not fully

qualify the name, check that the defaults generate the correct qualified name.

SQL 1008

Where user-name is a Guardian user name. Cause. The user name specified in a GRANT or REVOKE statement, or the

authorization ID in a CREATE SCHEMA statement, does not represent a valid Guardian user.

Effect. The operation fails. Recovery. Correct the user name and resubmit.

SQL 1009

Where column-name is an SQL identifier.

Cause. The table that is referenced does not have a column with this name. Effect. The operation fails. Recovery. Replace either the name of the table or the name of the column (whichever

is incorrect) and resubmit.

SQL 1010

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.

1006 Index index-name does not exist.

1008 User name user-name does not exist.

1009 Column column-name does not exist in the specified table.

1010 The statement just specified is currently not supported.

Data Definition Language (DDL) Messages (1000 through 1999)

HP NonStop SQL/MX Messages Manual—640324-001

3-4

SQL 1012

Cause. You attempted to grant privileges for which you do not have grant options. Effect. No privileges are granted. Recovery. You must have grant options for privileges to grant them.

SQL 1013

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.

SQL 1014

Cause. You attempted to revoke a privilege for a user who has granted privileges to

another user. Privileges must be revoked in reverse order from how they were granted. If you perform a grant to another user who then performs a grant to a third user, you cannot revoke privileges to the second user until that user revokes their privileges to the third user.

Effect. NonStop SQL/MX did not revoke the privileges. Recovery. Make sure that the dependent privileges from the user whose privileges

you want to revoke are revoked first.

SQL 1015

Cause. You attempted to revoke a privilege that does not exist or that was granted by

another user.

Effect. NonStop SQL/MX did not revoke the privileges. Recovery. The user who granted the privileges must revoke them.

1012 No privileges were granted. You lack grant option on the specified privileges.

1013 Not all privileges were granted. You lack grant option on some of the specified privileges.

1014 Privileges were not revoked. Dependent privilege descriptors still exist.

1015 Some of the specified privileges could not be revoked.

+ 722 hidden pages

HP NonStop SQL/MX, NonStop SQL/MX 3.0 Messages Manual

Specifications and Main Features

Frequently Asked Questions

User Manual