Copyright: Copyright (c) 1994, Oracle Corporation.


Entry Topic
Oracle7 Server Messages and Codes Manual

Oracle7™Server Messages and Codes Manual

PREFACE

CHAPTER 1. HOW TO USE MESSAGES

CHAPTER 2. ORACLE7 SERVER MESSAGES

CHAPTER 3. PL/SQL AND FIPS MESSAGES

CHAPTER 4. PRECOMPILER MESSAGES

CHAPTER 5. SQL*DBA MESSAGES

CHAPTER 6. IMPORT/EXPORT MESSAGES

CHAPTER 7. SQL*LOADER MESSAGES

CHAPTER 8. SQL*MODULE MESSAGES

APPENDIX A. MESSAGES ALPHABETICALLY

APPENDIX B. OPERATING SYSTEM- SPECIFIC INFORMATION


This help file created via:

Oracle Book to Microsoft Help Version 1.0p

© 1994 Oracle Corporation Inc.

Authored by KM .


Oracle7äServer Messages and Codes Manual
Oracle7™Server Messages and Codes Manual

Release 7.1

May, 1994

Part No. A12379-2 Second Edition

Oracle7™ Server Messages and Codes Manual,  Release 7.1

Part No. A12379-2

Copyright © Oracle Corporation 1992, 1993, 1994

Primary Authors:  Martin Gruber, Brian Quigley

Contributing Authors:  John Frazzini, Tom Portfolio, Tim Smith

This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law.  Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights Legend 	Use, duplication, or disclosure by the Government is subject to restrictions 	as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in 	Technical Data and Computer Software (October 1988).

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA  94065.

If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights," as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).

The information in this document is subject to change without notice.   If you find any problems in the documentation, please report them to us in writing.   Oracle Corporation does not warrant that this document is error-free.

Oracle, CASE*Dictionary, Pro*Ada, Pro*COBOL, Pro*FORTRAN, Pro*Pascal, Pro*PL/I, SQL*Connect, SQL*DBA, SQL*Forms, SQL*Loader, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.  CASE*Designer, CASE*Method, Oracle7, Oracle Parallel Server, Oracle*XA, PL/SQL, Pro*C, SQL*Module, and Trusted Oracle7 are trademarks of Oracle Corporation.

All other product or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners.


PREFACE

The purpose of this Manual is to provide complementary information about messages generated by the Oracle Server and its integral parts. The integral parts of an Oracle Server can include the following: the SQL processor, PL/SQL, SQL*DBA, pre-compilers, the Export and Import utilities, and SQL*Loader. Except for operating system-specific messages, all messages in this Manual are common to all Oracle products that interface with the Oracle Server.

Operating system-specific messages generated by the Oracle server are listed in the Oracle documentation set for each system. For convenience, this Manual indicates which document contains these specific messages.

Each message listing in this manual usually explains the probable cause of the message. If the message is a warning or indicates an error occurred, the message listing usually indicates a corrective action.

 ________________________________________

Audience

This Manual is intended for all Oracle7 users.

 ________________________________________

How This Manual Is Organized

This Manual contains seven chapters and an appendix. The following is a brief description of their contents:

 Chapter 1 Using Messages    This chapter describes how to gain the most information from this manual. It is important to read this chapter if you wish to report a problem to Oracle customer support.

 Chapter 2 Oracle7 Server Messages    This chapter lists messages generated by the Oracle7 Server.

 Chapter 3 PL/SQL and FIPS Messages    This chapter lists messages generated by PL/SQL. This chapter also warnings generated when FIPS flagging is set in an Oracle product and an Oracle extension to the SQL92 standard is used or a SQL92 feature is used in a non-conforming manner.

 Chapter 4   Precompiler Messages    This chapter lists messages generated by Oracle pre-compilers.

 Chapter 5 SQL*DBA Messages    This chapter lists messages generated by SQL*DBA.

 Chapter 6 Export/Import Messages    This chapter lists messages generated by the Export and Import utilities.

 Chapter 7 SQL*Loader Messages    This chapter lists messages generated by SQL*Loader.

 Chapter 8 SQL*Module Messages    This chapter lists messages generated by SQL*Module.

 ________________________________________

Related Publications

 Concepts

Often, a message in this Manual indicates a misunderstanding of a concept or administrative procedure when interacting with Oracle. In this case, refer to one of the following manuals:

•	Oracle7 Server Concepts Manual Part No. 6693-70-1292.

•	Oracle7 Server Administrator's Guide Part No. 6694-70-1292.

•	Oracle7 Server Application Developer's Guide Part No. 6695-70-1292.

•	Oracle7 Parallel Server Administrator's Guide Part No. 5990-70-1292.

•	Oracle7 Server Documentation Addendum Release 7.1 Part No. A12042-3. This manual contains information specific to the 7.1 release of Oracle7 that is not contained in the generic Oracle7 documentation.

 Trusted Oracle7

Generic messages for Trusted Oracle7 are listed in this Manual. If you see a Trusted Oracle7 message that differs from the text in this Manual, refer to the following manual:

•	Trusted Oracle7 Server Administrator's Guide, Part No. 6610-70-1292.

 Syntax Messages

A message in this Manual may indicates a syntax error in an Oracle command or programming statement, in which case refer to one of the following documents:

•	Oracle7 Server SQL Language Reference Manual, Part No. 778-70-1292.

•	PL/SQL User's Guide and Reference, Part No. 800-20-1292.

•	Oracle7 Server Utilities User's Guide, Part No. A12389.

•	Programmer's Guide to the Oracle Call Interface Part No. A14530-1.

•	SQL*Module User's Guide and Reference Part No. A14174-1.

•	PL/SQL 2.1 and Oracle Precompileres Release 1.6 Addendum Part No. A11828-3.

 Oracle Product Messages

Oracle products that are not listed earlier in this preface as integral to the server - such as SQL*Plus, SQL*Forms, CASE*Designer, Pro*C, and so forth - are not listed or referenced in this Manual. Please refer to the product specific documentation for the product messages.

 Operating system-specific, SQL*Net,and SQL*Connect Messages

Oracle runs on many different operating systems, communicates across many different network protocols, and interfaces with many different types of database systems. Operating system-specific messages generated by an Oracle Server are listed in the documentation for that operating system. In the unlikely event that a message is listed in your operating system-specific documentation and this Manual, use the operating specific documentation, but report the discrepancy using the Reader's Comment Form at the back of this Manual.

Messages not listed in this Manual are likely to be listed in one of the manuals in the following list. If you cannot find a message in a manual listed below, try the Oracle installation or user's guide for your product and platform.

 SQL*Net generic messages

Oracle Network Products Messages Manual Part No. A16263. Note that some product dependent SQL*Net messages may be listed in the installation or user's guide for your platform.

 AMDAHL

Oracle7 for Amdahl UTS Installation and Configuration Guide Part No. A11242.

 BULL

Oracle7 Bull DPX/2 Installation and User's Guide Part No. Z11665.

 DEC

Oracle7 for DEC Alpha AXP OSF/1 Installation and Configuration Guide Part No. A11052.

Oracle7 for Alpha AXP OpenVMS User's Guide  Part No. A11363.

Oracle7 for DEC RISC ULTRIX Installation and Configuration Guide Part No. A11051.

Trusted Oracle7 for DEC RISC ULTRIX MLS+ Installation and User's Guide Part No. A13953.

Trusted Oracle7 for VAX SEVMS Installation and Administrator's Guide Part No. A12015.

Oracle7 for VAX OpenVMS User's Guide Part No. A11062.

Oracle7 (7.1) for VAX OpenVMS User's Guide Part No. A13019.

 Hewlett Packard

Oracle7 Server for HP-UX 9000 Series 300/400 Installation and User's Guide Part No. 5092-70.

Oracle7 for HP 9000 Series 700/800 Installation and Configuration Guide Part No. A12270.

Trusted Oracle7 for HP-UX BLS Installation & Configuration Guide Part No. A12066.

Oracle7 Server for HP 3000/900 Installation and User's Guide Part No. A11616.

 ICL

Oracle7 For ICL DRS Systems ICL DRS6000 Installation and User's Guide Part No. 5767-70.

Oracle7 Server for ICL DRS 6000 Installation & User's Guide Part No. Z10469.

Oracle7 Server for ICL DRS6000 Installation and User's Guide Part No. Z11348.

 IBM

Oracle7 for IBM RISC System/6000 Installation and Configuration Guide Part No. A11366.

Oracle7 for MVS Messages Guide Part No. A10327.

Oracle7 for VM Messages Guide Part No. A10304.

 NCR

Oracle7 Server for NCR System 3000 Installation and User's Guide Part No. Z11342.

 Pyramid

Oracle7 for Pyramid DC/OS Installation and Configuration Guide Part No. A11795.

 Stratus

Oracle7 for Stratus FTX Installation and Configuration Guide Part No. A14289.

 UNIX generic

 ________________________________________

Your Comments Are Welcome

We value and appreciate your comments as an Oracle user and reader of the manuals. As we write, revise, and evaluate, your opinions are the most important input we receive. At the back of this manual is a Reader's Comment Form which we encourage you to use to tell us both what you like and what you dislike about this (or other) Oracle manuals. If the form has been used, or you would like to contact us in California, please use the following address.

Oracle7 Server Documentation Manager

Oracle Corporation

500 Oracle Parkway

Redwood Shores, CA  94065

U.S.A.


CHAPTER 1. HOW TO USE MESSAGES

This chapter gives you general information and helpful tips about messages. The following topics are covered:

•	locating message documentation

•	accuracy of messages

•	message format

•	recognizing variable text in messages

•	message stacks

•	message ranges

•	calling Customer Support

•	Oracle exception messages

•	trace files

•	the Alert file

 ________________________________________

Locating Message Documentation

 Oracle Server

These messages are generated by the Oracle Server when running any Oracle program. This Manual documents messages that are common across Oracle products and tools.

 Product Specific

These messages are specific to one product and are documented in manuals for that product. For example, if you work on a Macintosh and use SQL*Net you would need to refer to the messages contained in SQL*Net for Macintosh Manual.

 Operating System-Specific

These messages are specific to one operating system. A range of message code numbers is reserved for each operating system. For example, the range 7500 - 7999 is for DEC VAX/VMS messages; these messages are listed in the appropriate operating system-specific documentation.

The prefix of the message indicates where to find information about the message. For example, some messages in this manual have the prefix "ORA". If you encounter a message without a prefix, first check the manuals for the product you are using, then check this manual.

 ________________________________________

Accuracy of Messages

The accuracy of the messages in this manual is our primary concern. Occasionally, an enhancement to a message is not incorporated into the Oracle software. Should you encounter a message generated on your system that differs from the message in this book, be assured the improved message text is usually incorporated in the next release of the software. If you should encounter a discrepancy, please contact us using the information contained in the Reader Comment Form at the back of this Manual.

 Message Format

All messages you see displayed are prefixed by text that indicates which program issued the message. For example, the prefix "ORA" shows that the message was generated by the Oracle server. The location of messages in this book depends on the prefix of the message. The following table lists the prefixes of messages that you may encounter and the location of the message in this book.

All messages are listed in order by the message code number. To look up a message, use the message code number.

 Message Prefixes Listed in this Manual

The following messages per prefix are listed in this manual.

Prefix	Type of Message 	  Location

DBA	SQL*DBA 	 Chapter 5

EXP	Export utility 	Chapter 6

IMP	Import utility 	Chapter 6

LCC	Parameter file 	 Chapter 5

MOD	SQL*Module 	Chapter 8

ORA	Generic Oracle Server	Chapter 2

PCC	Precompiler 	Chapter 4

PLS	PL/SQL 	Chapter 3

SQL	Precompiler Run-time 	Chapter 4

SQL*Loader	SQL*Loader 	Chapter 7

 Message Prefixes of Oracle Products Not Listed in this Manual

The following message per prefix are not listed in this manual.

Prefix	Type of Product

ACF	File Access

ACG	Oracle Access

ACI	IAC Access

ACM	Mail Access

ACS	SQL Access

ACT	Text Retrieval Access

ADA	SQL*Connect to ADABAS

ADM	Office Administration

APP	Applications

ASY	SQL*Net Driver (Async Manager)

BLD	VM Install

BRW	Data Browser

CAL	SQL*Calc

CCC	CASE*Core

CIC	CICS Attach

CPR	CASE*Project

CRM	CASE*Repository

CPY	Oracle Tools

DBU	DBU

DIR	Directory Services

DLN	Datalens

FRM	SQL*Forms

GC*	Oracle Charting Library

GO*	Oracle Graphics

GWP	Oracle Procedural Gateway

GWT	Oracle Transparent Gateway Developer Kit

GTW	Gateway and Connect Kit

IAP	SQL*Forms

IDM	SQL*Connect to IDMS

IMP	IMPORT

IMS	SQL*Connect to IMS

INS	Install

KNT	SQL*Net Driver (Knet TCP/IP)

MAI	Oracle Mail

MGR	Server Manager

MBC	Multi-byte CASE Library

MOD	SQL*Module

MPA	SQL*Net Driver (LU6.2/APPC)

MPI	SQL*Net Driver (DECNet)

MPM	MPM

MPV	SQL*Net Driver (VTAM)

MST	VM Network Master (listener)

MTC	SQL*Net Driver (IBM TCP/IP)

NBD	VM net install

NSM	SQL*Net (VTAMaster)

NSS	VM-specific shared segment/memory Configurator

OAP	SQL*Net Driver (APPC/LU62 Manager)

OCL	ORAINST

ODM	Document Manager

OFC	Oracle Office

OFF	Oracle Office

OG*	Oracle Graphics

OIN	VM ORAINST

OIT	SQL*Net Driver (SNS TCP/IP)

ONS	SQL*Net Driver (VTAM)

ONT	SQL*Net Driver (NCR TCP/IP)

OPW	Oracle Password

OSN	SQL*Net Driver (VTAM)

OXA	Oracle XA Interface

OXQ	Office Automation Query Builder

PDE	PL/SQL Development Environment

RDB	SQL*Connect to RDB

RMS	SQL*Connect to RMS

RXS	Pro*Rexx

SCH	Office Scheduler

SDS	Source Control

SP1	Oracle Tools

SP2	Oracle Tools

SRV	VM server (child process)

TST	Ora*Tst

VG*	Virtual Graphics System

VSA	SQL*Connect to VSAM

 ________________________________________

Recognizing Variable Text in Messages

To help you find and fix errors, Oracle embeds object names, numbers, and character strings in some messages. These embedded variables are represented by name, num, str and so on. For example, the message:

ORA-00020: maximum number of processes (num) exceeded

might actually appear as:

ORA-00020: maximum number of processes (50) exceeded

 ________________________________________

Message Stacks

Occasionally, you may see a "message stack." This is simply a series of related messages issued at different levels of Oracle.

The following message stack is a generic example:

ORA-06502: PL/SQL: numeric or value error

ORA-06512: at "SCOTT.VALUE_ERR", line 1

ORA-06512: at line 1

The following message stack is a VAX/VMS example:

ORA-01034: Oracle not available

ORA-07625: smsget: $MGBLSC failure

%SYSTEM-W-NOSUCHSEC, no such (global) section

In this example, notice that the message at the bottom of the stack is issued by the VMS operating system. Seeing the messages at each level in the system may help you trace the originating event. For example, in this case, Oracle may not be available simply because it has not been started, and consequently there is no system global area (SGA). If you need the help of customer support, be sure to report all the messages in the stack.

 ________________________________________

Message Ranges

Oracle messages are grouped into specific ranges indicating the type or cause of event that generated the message. Most of these messages are listed in this Manual. Because Oracle runs on many different platforms, operating system-specific messages are listed in the appropriate Oracle manual for each platform.

The following sections list all current message ranges. Ranges highlighted in bold type are operating system-specific messages that are not listed in this Manual. Although this Manual does not list operating system-specific messages, it does list the message ranges and refers you to the "Related Publications" on page iii.

00000-00099: Oracle Server

00100-00150: Multi-Threaded Server

00150-00159: Oracle*XA

00200-00249: Control Files

00250-00299: Archiving and Recovery

00300-00379: Redo Log Files

00400-00420: Oracle Compatibility

00436-00437: Licensing

00440-00485: Background Processes

00486-00569: Interrupt Handlers

00570-00599: SQL*Connect Opening & Reading Files

00600-00639: Oracle Exceptions

00640-00699: SQL*Connect

00700-00709: Dictionary Cache

00816-00816: Message Translation

00900-00999: SQL Parsing

01000-01099: User Program Interface

01100-01250: Oracle Files

01400-01489: SQL Execution

01490-01499: Miscellaneous, ANALYZE, SQL Parsing, Execution

01500-01699: Oracle Commands

01700-01799: SQL Parsing

01800-01899: The Date Function

01900-02039: SQL Parsing

02040-02099: Distributed Transactions

02100-02139: Precompiler Runtime (SQLLIB)

02140-02299: SQL Parsing

02351-02375: Direct Loader

02376-02399: Oracle Resources

02400-02419: EXPLAIN PLAN Command

02420-02429: Schemas

02430-02449: Constraint Enabling & Disabling

02450-02479: Hash Cluster Commands

02500-02699: CTOS

02700-02757: UNIX Two Task

02875-02899: IBM RS/6000

03000-03099: Features Not Implemented

03100-03199: Two-Task Interface

03276-03289: Extent Allocation

03290-03295: TRUNCATE Command

03296-03299: Expandable Data Files

03500-03699: Macintosh

03700-03999: AOS/VS

04000-04109: Command Parameters

04020-04029: Library Object Locks

04030-04039: System Memory

04040-04069: Stored Procedures

04070-04099: Triggers

04500-04899: CMS

04900-09429: ICL DRS6000

05000-05899: OEM

06000-06429: SQL*Net

06430-06499: NCR System 3000

06500-06599: PL/SQL

06581-06591: European OEM Ports

06700-06899: SQL*Net TLI

06900-06939: CMX

06950-06999: SQL*Net AppleTalk

07000-07099: SQL*Connect/DB2

07100-07199: SQL*Connect/IMS

07200-07499: UNIX

07500-07999: VAX/VMS

08000-08174: Accessing Data

08175-08190: Discrete Transactions

08401-08410: European OEM Systems

08500-08799: SQL*Connect

08800-08899: SQL*Connect Tandem

09000-09099: SQL*Connect TERADATA

09100-09199: Oracle Gateways

09200-09499: OS/2 & MSDOS

09500-09699: MPE/XL

09700-09999: UNIX

10000-10999: Internal

11000-11999: SQL*Net MVS

12000-12014: Table Snapshots

12100-12299: SQL*Net

12300-12499: Trusted Oracle7

12500-12699: SQL*Net

12700-12799: National Language Support

19999-21000: User Defined

21100-21299: Internal

23300-24299: DBMS PL/SQL Packages

 ________________________________________

Calling Customer Support

Some messages recommend calling Oracle's customer support to report a problem. When you call customer support, please have the following information at hand:

•	the hardware, operating system, and release number of the operating system on which Oracle is running

•	the complete release number of the Oracle Server. For example, 7.0.16 or 7.1.3

•	all Oracle programs (with version numbers) in use when the error occurred. For example, SQL*Net V2.0 or SQL*Forms V3.0

•	if you encountered one or more error codes or messages, the exact code numbers and message texts, in the order they appeared

•	the problem severity, according to the following codes:

1 = Program not usable. Critical impact on operations.

2 = Program usable. Operations severely restricted.

3 = Program usable with limited functions. Not critical to overall operations.

4 = Problem circumvented by customer. Minimal effect, if any, on operations.

Also, you will be expected to give your:

•	name

•	company's name

•	company's Oracle Support ID Number

•	phone number

 ________________________________________

Oracle Exception Messages

Oracle's extensive self-checking helps detect internal errors. Rather than frustrate you with cryptic messages, Oracle uses the following catchall message for Oracle internal exceptions:

ORA-00600: internal error code, arguments: [num], [],[],[],[],[]

An actual message might appear as follows:

ORA-00600: internal error code, arguments: [1042],[3],[upilam], [], [],[]

Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.

In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.

If you receive an ORA-00600 message, report it as a software bug to customer support.

 ________________________________________

Trace Files

Each time an Oracle instance starts, or an unexpected event occurs in a user process or background process, a trace file is created. The name of the trace file includes the instance name, the process name, and the Oracle process number. The file extension or file type is usually TRC, and if different is noted your operating system-specific Oracle documentation. The contents of the trace file may include dumps of the system global area, process global area, supervisor stack, and registers.

Two initialization parameters specify where the trace files are stored:

BACKGROUND_DUMP_DESTINATION

Specifies the location for trace files created by the Oracle background processes PMON, DBWR, LGWR, and SMON.

USER_DUMP_DEST

Specifies the location for trace files created by user processes such as SQL*DBA, SQL*Plus, or Pro*C.

The Alert file also describes the location of trace files generated when internal errors occur. See the next section for a description of the Alert file.

You may need to format the trace file before using it to diagnose problems. To format a trace file, use the DUMPFMT utility, which is available on most systems and is described in your operating system-specific Oracle documentation. Customer support may ask you for a formatted trace file to help solve a problem.

For more information about trace files, see the Oracle7 Server Administrator's Guide.

 ________________________________________

The Alert File

The Alert file is a log file that records information about internal errors and administrative activities, such as backups. When an internal error occurs, the message is sent to the terminal screen as well as written to the Alert file. Oracle also writes additional information about internal errors to the Alert file, such as the location and name of any trace files generated because of the error and so forth.

The name of the Alert file is operating system-specific, and the location of the Alert file is the same as the location of the background process trace files. This location is specified by the BACKGROUND_DUMP_DEST initialization parameter. For more information, see your Oracle7 operating system-specific documentation.

If your system uses an operator's console, some messages from Oracle may appear on the console. All important messages are written to the Alert file as well as the operator's console. Because non-Oracle messages also appear on this console, the Alert file is a better record for tracing all Oracle administrative activity and errors than the console log.

The Alert file also records information about administrative activities, such as backups and archiving online redo log files. For more information about the Alert file, see the Oracle7 Server Database Administrator's Guide.


CHAPTER 2. ORACLE7 SERVER MESSAGES

This chapter lists the messages issued by the Oracle Server. Each message code has the format, ORA-nnnnn, where nnnnn is an integer.

Oracle Server messages specific to a particular operating system are not listed in this chapter, although the message range is listed. The "Related Publications" on page  iii of the "Preface" lists the appropriate Oracle documentation containing the Oracle Server messages specific to your operating system.

 ________________________________________

00000-00099: Oracle Server

This section lists the messages generated by the Oracle Server.

ORA-00000	normal, successful completion

 Cause:	An operation has completed normally, having met no exceptions.

 Action:	No action required.

ORA-00001	unique constraint (table.column) violated

 Cause:	An update or insert statement attempted to insert a duplicate key.

 Action:	Either remove the unique restriction or do not insert the key.

For Trusted Oracle7 configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.

ORA-00018	maximum number of sessions exceeded

 Cause:	An operation requested a resource that was unavailable. The maximum number of sessions is specified by the initialization parameter SESSIONS. When this maximum is reached, no more requests are processed.

 Action:	Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the SESSIONS parameter in the initialization parameter file, and restart Oracle.

ORA-00019	maximum number of session licenses exceeded

 Cause:	All licenses are in use.

 Action:	Call customer support before increasing the number of session licenses.

ORA-00020	maximum number of processes (num) exceeded

 Cause:	An operation requested a resource that was unavailable. The maximum number of processes is specified by the initialization parameter PROCESSES. When this maximum is reached, no more requests are processed.

 Action:	Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the PROCESSES parameter in the initialization parameter file, and restart Oracle.

ORA-00021	session attached to some other process; cannot switch session

 Cause:	The user session is currently being used by someone else.

 Action:	Do not execute calls in a user session concurrently.

ORA-00022	invalid session id; access denied

 Cause:	Either the session specified does not exist, or the caller does not have the privilege to access it.

 Action:	Specify a valid session ID. This requires ownership of the session id or the CHANGE_USER privilege.

ORA-00023	session references process' private memory; cannot detach session

 Cause:	An attempt was made to detach the current session, which contains references to the process' private memory.

 Action:	A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating-system privileges. To allow the detach, it may be necessary to close the session's database links or cursors. Detaching a session with operating-system privileges is always disallowed.

ORA-00024	logins from more than one process not allowed in single-process mode

 Cause:	An attempt was made to log in more than once from different processes after Oracle had been started in single-process mode.

 Action:	When Oracle is running in single-process mode, log off from the previous process before trying to log in from another one.

ORA-00025	failed to allocate num

 Cause:	An allocation failed because Oracle ran out of memory.

 Action:	Restart Oracle with a larger SGA heap.

ORA-00026	missing or invalid session id

 Cause:	The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified.

 Action:	Retry the command with a valid session ID.

ORA-00027	cannot kill current session

 Cause:	An attempt was made to kill the current session with the ALTER SYSTEM KILL SESSION command.

 Action:	If it is necessary to kill the current session, do so from another session.

ORA-00028	your session has been killed

 Cause:	A privileged user killed the session and it is no longer logged in to the database.

 Action:	Contact the database administrator. The administrator may be attempting to perform an operation that requires users to be logged out. When the database administrator announces that the database is available, log in and resume work.

ORA-00029	session is not a user session

 Cause:	The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started.

 Action:	Retry the command with a valid session ID.

ORA-00030	user session ID does not exist

 Cause:	The user session ID no longer exists, probably because the session was logged out.

 Action:	Use a valid session ID.

ORA-00031	session marked for kill

 Cause:	The session specified in the ALTER SYSTEM KILL SESSION command cannot be killed immediately because the session is involved in an non-interruptible operation (for example, rolling back a transaction or blocked by a network operation). The session has been marked to be killed as soon as possible after the current operation is done.

 Action:	No action required. The session will be killed when the operation is completed. Further executions of the ALTER SYSTEM KILL SESSION command may cause the session to be killed sooner.

ORA-00034	cannot <commit or rollback> in current PL/SQL session

 Cause:	An attempt was made to rollback from a PL/SQL object (procedure, function, package) in a session where commit and rollback are disabled by an ALTER SESSION DISABLE COMMIT IN PROCEDURE statement.

 Action:	Enable commits from PL/SQL in this session or do not attempt a commit or rollback when disabled.

ORA-00035	LICENSE_MAX_USERS cannot be less than current number of users

 Cause:	Specified value for LICENSE_MAX_USERS is less than current number of users.

 Action:	Check the license limit and drop extra users or purchase more licenses.

ORA-00050	O/S error occurred while obtaining an enqueue. See O/S error.

 Cause:	Could not obtain the operating-system resources necessary for an Oracle enqueue. This most often occurs when the user resource quota on the operating system is too low.

 Action:	Look up the operating system error in the operating system-specific Oracle documentation and perform the needed action.

ORA-00051	time-out occurred while waiting for resource

 Cause:	This message is usually caused by an instance that has terminated abnormally.

 Action:	Restart any non-recovered instances.

ORA-00052	maximum number of enqueue resources (num) exceeded

 Cause:	An operation requested a resource that was unavailable. The maximum number of enqueue resources is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests are processed.

 Action:	Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.

ORA-00053	maximum number of enqueues exceeded

 Cause:	An operation requested a resource that was unavailable and the enqueue list for the resource had reached its maximum length. If a request is made for a resource that is unavailable, the request is enqueued to wait for the resource. The number of requests that may be queued for a given resource is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests may be added to the enqueue list.

 Action:	Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.

ORA-00054	resource busy and acquire with NOWAIT specified

 Cause:	The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.

 Action:	Try the command after a few minutes or enter the command without the NOWAIT keyword.

ORA-00055	maximum number of DML locks exceeded

 Cause:	An operation requested a resource that was unavailable. The maximum number of DML locks is specified by the DML_LOCKS parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.

 Action:	Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the DML_LOCKS parameter in the initialization parameter file, and restart Oracle.

ORA-00056	DDL lock on object 'str.name' already held in an incompatible mode

 Cause:	The attempted lock is incompatible with the DDL lock already held on the object. This usually occurs when attempting to drop a table that has parse locks.

 Action:	Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation.

ORA-00057	maximum number of temporary table locks exceeded

 Cause:	The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.

 Action:	Increase TEMPORARY_TABLE_LOCKS parameter and warm start.

ORA-00058	DB_BLOCK_SIZE must be num to mount this database (not num)

 Cause:	The DB_BLOCK_SIZE parameter value in the initialization parameter file used to start a database does not match the value used when that database was created.

Potential reasons for this mismatch are:   1. mounting the wrong database   2. using the wrong initialization parameter file   3. the DB_BLOCK_SIZE value was changed

 Action:	For one of the above causes, either:   1. mount the correct database   2. use the correct initialization parameter file   3. correct the DB_BLOCK_SIZE parameter value

ORA-00059	maximum number of DB_FILES exceeded

 Cause:	An unavailable resource was requested. The maximum number of datafiles is specified by the DB_FILES parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.

 Action:	Try again when the resource is freed. If this message occurs often, Oracle must be shut down and restarted after increasing the DB_FILES parameter in the initialization parameter file. If the DB_FILES parameter cannot be changed because it is already set to the MAXDATAFILES parameter value (set at database creation), you must create a new control file.

ORA-00060	deadlock detected while waiting for resource

 Cause:	Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.

 Action:	Either:

•	Enter a ROLLBACK statement and re-execute all statements since the last commit.

•	Wait until the lock is released (possibly a few minutes) and re-execute the rolled back statements.

ORA-00061	another instance has a different DML_LOCKS setting

 Cause:	The shared instance being started is using DML locks and the running instances are not, or vice versa.

 Action:	Either:

•	Do not use DML_LOCKS by setting DML_LOCKS to zero at all instances.

•	Use DML_LOCKS by setting DML_LOCKS to a positive integer at all instances.

ORA-00062	DML full-table lock cannot be acquired; DML_LOCKS is 0

 Cause:	The instance was started with the initialization parameter DML_LOCKS set to zero, but the statement being executed needs a full-table lock (S, X, or SRX).

 Action:	Set DML_LOCKS to a nonzero value, restart the instance, and re-enter the statement.

ORA-00063	LOG_FILES initialization parameter exceeded

 Cause:	The value of the LOG_FILES initialization parameter was exceeded.

 Action:	Increase the value of LOG_FILES and warm start Oracle. The value needs to be as large as the highest number log that currently exists rather than just the count of the logs that exist. If this parameter cannot be increased because it would exceed the MAXLOGFILES set at database creation, you must create a new control file first.

ORA-00064	object is too large to allocate on this O/S ('num, num')

 Cause:	The initialization parameter DB_BLOCK_SIZE is set to a value that calls for more contiguous space than can be allocated on the operating system being used.

ORA-00065	initialization of FIXED_DATE failed

 Cause:	An attempt was made to enter a fixed date string that was not in the proper format.

 Action:	Enter the date string using the format YYYY-MM-DD:HH24:MI:SS.

ORA-00066	LOG_FILES is var but needs to be var to be compatible

 Cause:	The maximum number of redo log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

 Action:	Check that LOG_FILES initialization parameter is same for all instances.

ORA-00067	invalid value var for parameter var, must be at least var

 Cause:	The value for the initialization parameter is invalid.

 Action:	Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.

ORA-00068	invalid value var for parameter var, must be between var and var

 Cause:	The value for the initialization parameter is invalid.

 Action:	Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.

ORA-00097	use of Oracle SQL feature not in SQL92  compliance level

 Cause:	You tried to use an Oracle SQL feature that is not compliant with the SQL92 standard.

 Action:	Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance.

 ________________________________________

00100-00150: Multi-threaded Server

This section lists message generated by the multi-threaded server.

ORA-00100	idle public server terminating

 Cause:	There are too many idle shared servers waiting on the common dispatcher request queue.

 Action:	No action required.

ORA-00101	invalid specification for initialization parameter MTS_DISPATCHERS

 Cause:	The syntax for the MTS_DISPATCHERS parameter is incorrect.

 Action:	Enter the MTS_DISPATCHERS parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance.

ORA-00102	network protocol ('str') cannot be used by the dispatchers

 Cause:	The network specified in MTS_DISPATCHERS initialization parameter does not have the functionality required by the dispatchers.

 Action:	Refer to your Oracle7 operating system-specific documentation for network protocols supported by the dispatchers.

ORA-00103	invalid network protocol; reserved for use by dispatchers

 Cause:	The network specified in SQL*Net CONNECT string is reserved for use by the dispatchers.

 Action:	Specify other network protocols in the CONNECT string.

ORA-00104	deadlock detected; all public servers blocked waiting for resource

 Cause:	This message occurs when a client locks a resource and the maximum number of shared servers are taken by other clients who are requesting a locked resource. The original client is unable to get a shared server and cannot release the lock on the resource.

 Action:	The system automatically starts up new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_SERVERS. If this problem occurs frequently, ensure more shared servers will be available at the next restart of the instance by increasing the value of the initialization parameter MTS_SERVERS or MTS_MAX_SERVERS.

ORA-00105	dispatching mechanism not configured to support network protocol

 Cause:	The ALTER SYSTEM SET MTS_DISPATCHERS command was used to alter a set of dispatchers for a network protocol that is not specified in the initialization parameter file.

 Action:	Do either of the following:

•	Include the network protocol in the MTS_DISPATCHERS initialization parameter and restart the system.

•	Use the ALTER SYSTEM SET MTS_DISPATCHERS command with a network protocol that exists in the initialization parameter file.

ORA-00106	cannot startup/shutdown database when connected to a dispatcher

 Cause:	An attempt was made to start up or shut down an instance while connected to a shared server process via a dispatcher.

 Action:	Reconnect to the database using a dedicated server.

ORA-00107	failed to connect to network listener process

 Cause:	Usually caused by the fact that the network listener process has not been started.

 Action:	Check for the following:

•	The network configuration file is not set up correctly.

•	The client side address is not specified correctly.

•	The listener initialization parameter file is not set up correctly.

ORA-00108	failed to set up dispatcher to accept connection asynchronously

 Cause:	The network protocol used by the dispatcher does not support asynchronous operations.

 Action:	Contact customer support.

ORA-00111	Warning: maximum number of servers is only num; adding num servers

 Cause:	An attempt was made to start more shared server processes than the number allowed by the initialization parameter MTS_MAX_SERVERS. The actual number of shared servers started is specified in the message.

 Action:	If more shared server processes are required, increase the initialization parameter MTS_MAX_SERVERS and restart the instance.

ORA-00112	only created up to num (maximum specified) dispatchers

 Cause:	An attempt was made to start up more dispatchers than the maximum number specified by the initialization parameter MTS_MAX_DISPATCHERS.

 Action:	If more dispatchers are required, increase MTS_MAX_DISPATCHERS, restart the instance, and add dispatchers using the ALTER SYSTEM MTS_DISPATCHERS command.

ORA-00113	protocol name string is too long

 Cause:	A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long.

 Action:	Use a valid protocol name for the MTS_DISPATCHERS initialization parameter.

ORA-00114	missing value for initialization parameter MTS_SERVICE

 Cause:	There is no value for the MTS_SERVICE initialization parameter, nor for the DB_NAME parameter.

 Action:	Add an MTS_SERVICE or DB_NAME definition to the initialization parameter file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE is explicitly specified.

ORA-00115	connection refused; dispatcher connection table is full

 Cause:	A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.

 Action:	Connect to a different dispatcher or use a dedicated server.

ORA-00116	MTS_SERVICE name is too long

 Cause:	The service name specified in the MTS_SERVICE initialization parameter is too long.

 Action:	Use a shorter name for the MTS_SERVICE value (maximum is 255 characters).

ORA-00117	value out of range for the MTS_SERVERS system parameter

 Cause:	The value of the MTS_SERVERS parameter is incorrect.

 Action:	The MTS_SERVERS parameter must be from 0 to MTS_MAX_SERVERS.

ORA-00118	value out of range for MTS_DISPATCHERS system parameter

 Cause:	The value of the MTS_DISPATCHERS parameter is incorrect.

 Action:	The sum of all MTS_DISPATCHERS values must be from 0 to MTS_MAX_DISPATCHERS.

ORA-00119	invalid specification for system parameter MTS_LISTENER_ADDRESS

 Cause:	The syntax for the MTS_LISTENER_ADDRESS is incorrect.

 Action:	Refer to the Oracle7 Server Administrator's Guide for the correct syntax.

ORA-00120	dispatching mechanism not enabled or installed

 Cause:	Either the dispatching mechanism is not enabled or the Oracle executable image is not installed with the dispatching mechanism.

 Action:	Refer to the Oracle7 Server Administrator's Guide and your Oracle7 operating system-specific documentation for procedures for starting and configuring the dispatcher processes.

ORA-00121	MTS_SERVERS specified without MTS_DISPATCHERS

 Cause:	A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition for MTS_DISPATCHERS was specified. If no value is specified for MTS_DISPATCHERS, shared servers will not be used.

 Action:	Add a definition for MTS_DISPATCHERS in the INIT.ORA file. If you do not intend to use shared servers, remove the MTS_SERVERS definition.

ORA-00122	cannot initialize network configuration

 Cause:	Oracle could not initialize SQL*Net Version 2.

 Action:	See accompanying messages.

 ________________________________________

00150-00159: Oracle*XA

ORA-00150	duplicate transaction ID

 Cause:	Attempted to start a new transaction with an ID already in use by an existing transaction.

 Action:	Check that your application uses a valid transaction ID.

ORA-00151	invalid transaction ID

 Cause:	The specified transaction ID does not correspond to an existing valid transaction.

 Action:	Check that your application uses a valid transaction ID.

ORA-00152	current session does not match requested session

 Cause:	The current session is not the same as the session that was passed into a UPIXADO() call.

 Action:	Check that your application is coded correctly.

 ________________________________________

00200-00249: Control Files

ORA-00200	cannot create control file 'name'

 Cause:	The control file cannot be created, usually because of insufficient disk storage or filename conflicts.

 Action:	Check that there is sufficient disk and no conflicts in filenames and try to create the control file again.

ORA-00201	control file version num incompatible with Oracle version num

 Cause:	The control file was created by a different version of Oracle.

 Action:	Either:

•	Restart with version of Oracle used to create the control file.

•	Use the CREATE CONTROLFILE command to create a new control file that is compatible with this release.

ORA-00202	control file: 'name'

 Cause:	This message reports the name of the file involved in other messages.

 Action:	See the associated messages for a description of the problem.

ORA-00203	using the wrong control files

 Cause:	The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but are not the same files. The most likely cause is that one instance is using a backup of the control file. If you want to use a backed up control file, you can recover using the USING BACKUP CONTROLFILE option.

 Action:	Check that all instances are using the correct version of the control file.

ORA-00204	error in reading control file 'name' (block num, # blocks num)

 Cause:	A disk read-failure occurred while attempting to read the specified control file. The block location of the failure is given.

 Action:	Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating system reasons for Oracle's inability to read the disk or control file. Refer to the Oracle7 Server Administrator's Guide for information about recovering from the loss of a control file. See also your operating system-specific Oracle documentation.

ORA-00205	error in identifying control file 'name'

 Cause:	The system could not find a control file of the specified name and size.

 Action:	Either:

•	Check that the proper control filename is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again.

•	When using mirrored control files (that is, more than one control file is referenced in the initialization parameter file), remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new filename in the initialization parameter file.

ORA-00206	error in writing control file 'name' (block num, # blocks num)

 Cause:	A disk write-failure occurred while attempting to write to the specified control file. The block location of the failure is given.

 Action:	Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating-system reasons for Oracle's inability to write to the disk or control file. See the Oracle7 Server Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.

ORA-00207	control files are not for the same database

 Cause:	The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. The most likely cause is either that one of the mounts used the wrong control file or there are two databases with the same name.

 Action:	Check that the control file is for the correct database and not an old version. When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new filename in the initialization parameter file.

ORA-00208	number of control file names exceeds limit of num

 Cause:	An attempt was made to use more control files than Oracle supports. The limit is given in the message.

 Action:	Shut down Oracle, reduce the number of control filenames specified in the CONTROL_FILES parameter in the initialization parameter file and restart Oracle. Delete unused files.

ORA-00209	block size num exceeds limit of num bytes

 Cause:	A block size larger than that allowed by the operating system was specified.

 Action:	Reduce the block size to the amount specified in the message and try again.

ORA-00210	cannot open control file 'name'

 Cause:	The system was unable to open a control file.

 Action:	Check that the control file exists, that the storage device is online, and that the file is not locked by some other program and try again. Also, check to see that the operating-system limit on the number of open files per process has not been exceeded.

When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the parameter from the initialization parameter file referencing the control filename indicated in the message and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new filename in the initialization parameter file.

ORA-00211	control file 'name' does not match previous control files

 Cause:	The specified control file is from another database.

 Action:	Locate and specify the correct control file for this database, then retry the operation. When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file, create another copy of the control file, and include the new filename in the initialization parameter file.

ORA-00212	block size num below minimum required size of num bytes

 Cause:	The specified block size is too small. Additional space is needed for system overhead.

 Action:	Specify a larger block size and retry the operation.

ORA-00213	cannot reuse control file 'name'; old file size num, num required

 Cause:	To reuse a control file, it must be the same size as the previous one used.

 Action:	In the CREATE DATABASE statement, do not specify REUSE.

ORA-00214	control file 'name' version num inconsistent with file 'name' version num

 Cause:	An inconsistent set of control files, datafiles, and redo log files was used.

 Action:	Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period.

ORA-00215	must be at least one control file

 Cause:	No control file was specified, or the control file specified does not exist.

 Action:	Specify at least one valid control file and retry the operation.

ORA-00216	unable to determine physical block size for control file 'name'

 Cause:	An error occurred while determining the physical block size of the specified control file.

 Action:	Check the accompanying message stack for more detailed information.

ORA-00217	control file 'name' physical block size num inconsistent with num

 Cause:	The physical block size of the operating system is inconsistent with the block size of the control file.

 Action:	The system will not operate with invalid control files. Either restore a valid control file or recreate the database. When using multiplexed control files (that is, more than one control file is referenced in the initialization parameter file), remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new filename in the initialization parameter file.

ORA-00218	control file 'name' was created with physical size num now is num

 Cause:	The control file size specified in the file's header differs from the physical block size of the control file. This usually means that the control file has been corrupted.

 Action:	Recover the control file as described in the Oracle7 Server Administrator's Guide.

ORA-00219	required control file size num larger than maximum num

 Cause:	The CREATE DATABASE statement specified a combination of initialization parameters that results in the control file exceeding the internal maximum size.

 Action:	You must recreate the database. In the CREATE DATABASE statement, use lower for clauses such as MAXDATAFILES and MAXLOGFILES as described in the Oracle7 Server Administrator's Guide.

ORA-00220	control file 'name' not mounted by first instance

 Cause:	The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.

 Action:	Find and use the correct control file.

ORA-00221	error on write to control file

 Cause:	An error occurred when writing to one or more of the control files.

 Action:	More descriptive messages will follow this message.

ORA-00223	conversion data file is invalid or incorrect version

 Cause:	A Version 6 to Oracle7 conversion datafile contains invalid data or was created with an old version of the migration utility.

 Action:	Regenerate the conversion file with the correct version of the migration utility or use the correct file for converting the database.

ORA-00224	the specified file is not a control file

 Cause:	The file specified in the initialization parameter file is not a control file.

 Action:	Edit the initialization parameter file and specify the correct control filename.

 ________________________________________

00250-00299: Archiving and Recovery

This section lists the messages generated when archiving or recovery of the database is in progress.

ORA-00250	archiver not started

 Cause:	An attempt was made to stop automatic archiving, but the archiver process was not running.

 Action:	No action required.

ORA-00251	archiving/media recovery requires OS DBA or OPER privileges

 Cause:	An attempt was made to perform archiving or media recovery without having the required operating system DBA or OPER privileges.

 Action:	Ask the database administrator to perform the operation or grant the necessary privileges.

ORA-00252	log 'name' of thread num is empty, cannot archive

 Cause:	The specified redo log was not used since it was introduced to the database. It is also possible that the instance died during a log switch, and the log was left empty.

 Action:	Empty logs do not need to be archived. Do not attempt to archive the redo log file.

ORA-00253	limit of num exceeded by length num of archive string 'name'

 Cause:	The specified archive string is too long. The limit is given in the message.

 Action:	Use a shorter string, making sure not to exceed the given limit and try again.

ORA-00254	error in archive control string 'archive_log_location'

 Cause:	The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.

 Action:	Specify a valid location name.

ORA-00255	error archiving log 'name' of thread num, sequence # num

 Cause:	An error occurred during archiving.

 Action:	Check the accompanying message stack for more detailed information.

If the online log is corrupted then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but does allow redo to be generated.

ORA-00256	error occurred in translating archive text string 'str'

 Cause:	An error occurred while translating the archive control string.

 Action:	Check the accompanying message stack for more detailed information.

ORA-00257	archiver is stuck. Connect internal only, until freed.

 Cause:	The ARCH process received an error while trying to archive a redo log file. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is that the destination device is out of space to store the redo log file.

 Action:	Check the archiver trace file for a detailed description of the problem. Also, verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

ORA-00258	manual archiving in NOARCHIVELOG mode must identify log

 Cause:	An attempt was made to manually archive a redo log file without specifying the sequence number, group number, or filename while the database is in NOARCHIVELOG mode.

 Action:	The name, group number, or thread and sequence number of redo log files must be specified to manually archive redo log files while the database is in NOARCHIVELOG mode.

ORA-00259	log name of open thread num is the current log, cannot archive

 Cause:	An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for generation of redo entries.

 Action:	Force a log switch in the instance where the thread is open. If no instances are open, open the database so instance recovery can recover the thread.

ORA-00260	cannot find online log sequence num for thread num

 Cause:	The log sequence number specified in the ARCHIVE statement does not match any of the online logs for the specified thread.   This can result from any of the following situations:

•	This log may have been reused for another sequence number.

•	This log may have been dropped.

•	The sequence number may be greater than the current log sequence number.

•	The thread may not have any logs.

 Action:	Check the ARCHIVE statement; then specify a valid log sequence number.

ORA-00261	log name of thread num is being archived or modified

 Cause:	Either the log is being archived by another process or an administrative command is executing and modifying the log. Clearing, adding a member, dropping a member, renaming a member, and dropping the log are operations that modify a log.

 Action:	Wait for the current operation to complete and try again.

ORA-00262	current log name of closed thread num cannot switch

 Cause:	The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived or cleared and cannot be reused.

 Action:	Archive another log in the same thread first or complete the clearing. See attached errors for the reason the switch cannot be completed.

ORA-00263	there are no logs that need archiving for thread num

 Cause:	An attempt was made to manually archive the unarchived logs in this thread, but no logs need archiving.

 Action:	No action required.

ORA-00264	no recovery required

 Cause:	An attempt was made to perform media recovery on files which do not need any type of recovery.

 Action:	Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.

ORA-00265	instance recovery required, cannot set ARCHIVELOG mode

 Cause:	The database either crashed or was shut down with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the datafiles.

 Action:	Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE options.

ORA-00266	name of archived logfile needed

 Cause:	During media recovery, the name of an archived redo log file was requested, but no name was entered.

 Action:	Mount the correct redo log file and enter its name when it is requested.

ORA-00267	name of archived logfile not needed

 Cause:	During media recovery, the name of an archived redo log file was entered, but no name was requested.

 Action:	Continue media recovery, but do not enter a new log name.

ORA-00268	specified logfile does not exist name

 Cause:	The given redo log file does not exist.

 Action:	Check the spelling and capitalization of the filename and retry the command.

ORA-00269	specified logfile is part of thread num not num

 Cause:	The given redo log file is not part of the given thread

 Action:	Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.

ORA-00270	error creating archive log

 Cause:	An error was encountered when either creating or opening the destination file for archiving.

 Action:	Check that the archive destination is valid and that there is sufficient space on the destination device.

ORA-00271	there are no logs that need archiving

 Cause:	An attempt was made to manually archive the unarchived redo log files, but there are no files that need to be archived.

 Action:	No action required.

ORA-00272	error writing archive log

 Cause:	An I/O error occurred while archiving a redo log file.

 Action:	Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.

ORA-00273	media recovery of direct load data that was not logged

 Cause:	A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.

 Action:	The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.

ORA-00274	illegal recovery option str

 Cause:	An illegal option was specified for a recovery command.

 Action:	Correct the syntax and retry the command.

ORA-00275	media recovery has already been started

 Cause:	An attempt was made to start a second media recovery operation in the same session.

 Action:	Complete or cancel the first media recovery session or start another session to perform media recovery.

ORA-00276	CHANGE keyword specified but no change given

 Cause:	The CHANGE keyword was specified on the command line, but no change number was given.

 Action:	Retry the command using a valid change number after the CHANGE keyword.

ORA-00277	Illegal option to the UNTIL recovery flag str

 Cause:	Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.

 Action:	Correct the syntax.

ORA-00278	logfile 'name' no longer needed for this recovery

 Cause:	The specified redo log file is no longer needed for the current recovery.

 Action:	No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.

ORA-00279	change num generated at name needed for thread num

 Cause:	The requested log is required to proceed with recovery.

 Action:	Please specify the requested log in the command or cancel recovery.

ORA-00280	change num for thread num is in sequence #num

 Cause:	This message helps to locate the redo log file with the specified change number requested by other messages.

 Action:	Use the information provided in this message to specify the required archived redo log files for other errors.

ORA-00281	media recovery may not be performed using dispatcher

 Cause:	An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.

 Action:	Connect to the instance via a dedicated server process to perform media recovery.

ORA-00282	UPI name call not supported, use ALTER DATABASE RECOVER

 Cause:	The given UPI call is no longer supported.

 Action:	Use the ALTER DATABASE RECOVER command for all recovery actions.

ORA-00283	recovery session canceled due to errors.

 Cause:	An error during recovery was determined to be fatal enough to end the current recovery session.

 Action:	More specific messages will accompany this message. Refer to the other messages for the appropriate action.

ORA-00284	recovery session still in progress.

 Cause:	An error during recovery was determined to be minor enough to allow the current recovery session to continue.

 Action:	More specific messages will accompany this message. Refer to other messages for the appropriate action.

ORA-00285	TIME not given as a string constant

 Cause:	UNTIL TIME was not followed by a string constant for the time.

 Action:	Enter the time enclosed in single quotation marks.

ORA-00286	no members available, or no member contains valid data

 Cause:	None of the members of a redo log file group are available, or the available members do not contain complete data.

 Action:	If a member is temporarily off line, attempt to make it available. Check that the correct filenames are being used, especially if the redo log file is being accessed from a remote location.

ORA-00287	specified change number num not found in thread num

 Cause:	The given change number does not appear in any of the online redo logs for the given thread.

 Action:	Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.

ORA-00288	to continue recovery type ALTER DATABASE RECOVER CONTINUE

 Cause:	During media recovery, redo information from a new log is not required but the continuation command is necessary to do a checkpoint and report errors.

 Action:	Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.

ORA-00289	suggestion: str

 Cause:	This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.

 Action:	Consider using this filename for the next log needed for recovery.

ORA-00290	operating system archiving error occurred. See error below

 Cause:	While attempting to archive to a redo log file, the server encountered and unexpected operating system error.

 Action:	Correct the operating system error (given in the messages) and retry the operation. See also your operating system-specific Oracle documentation.

ORA-00291	numeric value required for PARALLEL option

 Cause:	A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.

 Action:	Re-enter the command with a numeric argument specifying the degree of parallelism desired.

 ________________________________________

00300-00379: Redo Log Files

This section lists messages generated when the Redo Log Files are being accessed.

ORA-00300	illegal redo log block size num specified -exceeds limit of num

 Cause:	The specified block size of the redo log file is greater than the maximum block size for the operating system.

 Action:	Create the redo log on a device with a smaller block size.

ORA-00301	error in adding logfile 'name' - file cannot be created

 Cause:	The creation of the redo log file failed.

 Action:	Check that there is enough storage space on the device, that the name of the file is valid, and that the device is online; then try again.

Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.

ORA-00302	limit of num logs exceeded

 Cause:	The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16).

 Action:	No action required.

ORA-00304	requested INSTANCE_NUMBER is busy

 Cause:	An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.

 Action:	Specify another value for INSTANCE_NUMBER in the initialization parameter file or wait for recovery to finish for that instance number. Then restart the instance.

ORA-00305	log name of thread num inconsistent; belongs to another database

 Cause:	The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.

 Action:	Specify the correct redo log file; then retry the operation.

ORA-00306	limit of num log writer instances in this database

 Cause:	Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only when attempting to start another instance in Parallel Server mode.

 Action:	It is not possible to start more than the given number of instances. The maximum is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.

ORA-00307	requested INSTANCE_NUMBER out of range, maximum is num

 Cause:	The initialization parameter INSTANCE_NUMBER specified a number that was out of range.

 Action:	Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.

ORA-00308	cannot open archived log 'name'

 Cause:	The system cannot access a required archived redo log file.

 Action:	Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.

ORA-00309	log belongs to wrong database

 Cause:	The system cannot access the archived redo log because it belongs to another database.

 Action:	Specify the correct redo log file; then retry the operation.

ORA-00310	archived log contains sequence num; sequence num required

 Cause:	The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified during recovery.

 Action:	Specify the correct redo log file; then retry the operation.

ORA-00311	cannot read header from archived log

 Cause:	An error occurred when attempting to read the file header from the archived redo log file.

 Action:	Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00312	online log name thread num: 'str'

 Cause:	This message reports the filename for details of another message.

 Action:	Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00313	open failed for members of log group var of thread var

 Cause:	The online log cannot be opened. The file may not be in the expected location.

 Action:	Specify the correct redo log file or make log available, if necessary. Also, see the following messages, if any.

ORA-00314	log name of thread num, expected sequence # num does not match num

 Cause:	The online log is out of sequence, probably because it is corrupted or an old version.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00315	log name of thread num, wrong thread # num in header

 Cause:	The online redo log file is corrupted or is an old version.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00316	log name of thread num, type str in header is not redo log file

 Cause:	The online redo log file is corrupted or is an old version.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00317	file type str in header is not logfile

 Cause:	This is not an archived redo log file.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00318	log name of thread num, expected file size num does not match num

 Cause:	The file size indicated in the control file did not match the file size contained in the redo log file.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00319	log name of thread num has incorrect log reset status

 Cause:	An online redo log file has log reset data that is different from the log reset data listed in the control file. The redo log file is probably an incorrectly restored backup.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00320	cannot read file header from log name of thread num

 Cause:	The system is unable to read the redo log file header because the file is not available or the file is corrupted.

 Action:	Specify the correct redo log file; then retry the operation.

ORA-00321	log name of thread num, cannot update logfile header

 Cause:	The system cannot write to the redo log file.

 Action:	Restore access to the redo log file; then retry the operation.

ORA-00322	log name of thread num is not current copy

 Cause:	An online redo log file appears to be an incorrectly restored backup, according to a check of the redo log file header.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00323	current log of thread num not usable and all others need archiving

 Cause:	An attempt to open a thread failed because it is necessary to switch to another online log, but all the other online redo logs need to be archived before they can be used.

 Action:	Archive the online redo logs for the thread; then retry the operation.

ORA-00324	logfile 'name' translated name 'name' too long, num characters exceeds num limit

 Cause:	The translated name for a redo log file is too long.

 Action:	Respecify a redo log filename that produces a shorter filename on translation.

ORA-00325	archived log for thread num, wrong thread # num in header

 Cause:	The archived redo log file is corrupted, or it belongs to another thread. This redo log file cannot be used.

 Action:	Find and use the correct archived redo log file; then retry the operation.

ORA-00326	log begins at change num, need earlier change num

 Cause:	The archived redo log file supplied for recovery was generated after the redo log file that is needed. Cannot use the log for applying redo information at this time.

 Action:	Find and install the correct archived redo log file; then retry the operation.

ORA-00327	log name of thread num, physical size num less than needed num

 Cause:	A redo log file has shrunk in size. This is usually caused by a computer operator's mistake or an operating system error.

 Action:	Restore the redo log file from backup. If the database was shut down cleanly, no further action should be required. Otherwise, manual recovery may be necessary.

ORA-00328	archived log ends at change num, need later change num

 Cause:	The archived redo log file supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo information at this time.

 Action:	Find and install the correct archived redo log file; then retry the operation.

ORA-00329	archived log begins at change num, need change num

 Cause:	The archived redo log file supplied for recovery is not the correct log. An earlier redo log file is needed.

 Action:	Find and install the correct archived redo log file; then retry the operation.

ORA-00330	archived log ends at change num, need change num

 Cause:	The archived redo log file supplied for recovery is not the correct log. A later redo log file is needed.

 Action:	Find and install the correct archived redo log file; then retry the operation.

ORA-00331	log version num incompatible with Oracle version num

 Cause:	The log was created under an older (incompatible) version of Oracle, or an attempt was made to use the wrong log.

 Action:	Specify the correct redo log file or recover the database with the old software. Then shut down and restart Oracle with the new software.

ORA-00332	archived log is too small - may be incompletely archived

 Cause:	The log occupies less space than is allocated to it. This may result from a shutdown abort while the archiver was writing it.

 Action:	Get a complete version of the file (either the online version or one that was successfully archived) and use that for recovery.

ORA-00333	redo log read error block num count num

 Cause:	An error occurred while reading the redo log file. Other messages will accompany this message and will give the name of the file.

 Action:	Restore access to the file or get another copy of the file.

ORA-00334	archived log: 'name'

 Cause:	This message reports the filename involved with other errors.

 Action:	See the associated messages for a description of the problem.

ORA-00335	online log name: No log with this number, log does not exist

 Cause:	This message reports the filename involved with other messages.

 Action:	Correct the underlying problems mentioned in the other messages.

ORA-00336	logfile size num blocks is less than minimum num blocks

 Cause:	The redo log file size specified in the CREATE DATABASE statement is too small.

 Action:	Increase the redo log file size and re-enter the statement.

ORA-00337	logfile 'name' does not exist and no size specified

 Cause:	The system could not add a redo log file because it could not find an existing file or a size for creating the file.

 Action:	Specify a size for the redo log file; then retry the operation.

ORA-00338	log name of thread num is more recent than control file

 Cause:	The control file change sequence number in the redo log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error to happen by reopening the database may cause the error to stop happening without correcting the problem. Every attempt to open the database advances the control file change sequence number.

 Action:	Use the correct control file or perform recovery using a backup of the control file.

ORA-00339	archived log does not contain any redo

 Cause:	The archived log being applied is not the correct log. The log being applied is possibly a copy of a log or was an online log being prepared to be used as the current log.

 Action:	Restore the correct redo log file.

ORA-00340	I/O error processing online log name of thread num

 Cause:	An I/O error occurred on the named online redo log file-probably because the file was not accessible or because it was corrupted.

 Action:	Restore access to the file or restore the file from a backup.

ORA-00341	log name of thread num, wrong log # num in header

 Cause:	The internal information in an online redo log file does not match the control file information.

 Action:	Refer to the Oracle7 Server Administrator's Guide for recovery procedures.

ORA-00342	archived log was created before last RESETLOGS

 Cause:	Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.

 Action:	Find and install the correct archived redo log file; then retry the operation.

ORA-00343	too many errors, log member closed

 Cause:	The maximum number of errors on this log member has been exceeded. Other messages will accompany this message.

 Action:	Correct the underlying problems mentioned in the other messages.

ORA-00344	unable to recreate online log 'name'

 Cause:	An I/O failure occurred when attempting to recreate an online log as part of either a ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.

 Action:	Check the accompanying messages. Check that the file is accessible.

ORA-00345	redo log write error block num count num

 Cause:	An I/O error has occurred while writing the log, probably because the file was not accessible, or a device failed.

 Action:	Make the file accessible or restore the device; then restart the system. If the log is lost, apply media or incomplete recovery.

ORA-00346	log member marked as STALE

 Cause:	A redo log file member is no longer complete. Other messages will accompany this message.

 Action:	Correct the underlying problem mentioned in the other messages.

ORA-00347	log name of thread num expected block size num does not match num

 Cause:	During online recovery, the block size specified in the control file did not match the block size indicated in the redo log file.

 Action:	Restore the correct redo log file from a backup or reset the online redo log files.

ORA-00348	single-process redo failure. Must abort instance

 Cause:	A failure occurred during a single-process redo log operation. This error does not occur during normal multiprocess operations.

 Action:	Shut down and restart the database.

ORA-00349	failure obtaining block size for 'name'

 Cause:	The operating system was unable to determine the block size for the named file.

 Action:	Check the accompanying messages; then restore the device or specify another file.

ORA-00350	log name of thread num needs to be archived

 Cause:	Media recovery is enabled and the specified log was not archived.

 Action:	Archive the redo log file or disable media recovery. If the command supports the UNARCHIVED option then it can be used. However, this may result in making backups unusable and forcing some offline files to be dropped.

ORA-00351	recover-to time invalid

 Cause:	The time specified in a RECOVER DATABASE... UNTIL is after January 1, 1988.

 Action:	Specify a time after January 1, 1988.

ORA-00352	all logs for thread num need to be archived - can not enable

 Cause:	An attempt was made to enable a thread when all of the online redo log files in the thread needed to be archived, and media recovery has been enabled. There is no online redo log file that can be made the new current log for the thread.

 Action:	Archive a redo log file for the thread.

ORA-00353	log corruption near block num time stamp str

 Cause:	Some type of redo log file corruption has been discovered. This message describes the location of the corruption. Other messages will accompany this message and describe the type of corruption.

 Action:	Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.

ORA-00354	corrupt redo log block header

 Cause:	The block header on the block in the redo log file is not valid. The block number and time-stamp are given in an accompanying message.

 Action:	Perform recovery with a good version of the redo log file or perform cancel-based recovery up to, but not including, the corrupted redo log file.

ORA-00355	change numbers out of order

 Cause:	A change number found in the redo log file is lower than a previously encountered change number. The redo log file is corrupted in some way. The corruption may be at the earlier change number or at this one. The block number and time-stamp are given in an accompanying message.

 Action:	Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.

ORA-00356	inconsistent lengths in change description

 Cause:	A change record in the redo log file contains lengths that do not add up to a consistent value. The redo log file is corrupted in some way.

 Action:	Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.

ORA-00357	too many members specified for logfile, the maximum is num

 Cause:	An attempt was made to add a redo log group or add a redo log group member that would result in a set of online redo logs with too many members. The maximum number of members is set when the database is created.

 Action:	Use fewer redo log group members.

ORA-00358	Too many file members specified, the maximum is num

 Cause:	A CREATE or ALTER statement specified too many members in the file list.

 Action:	Specify a number of files that is within the given limit.

ORA-00359	Logfile group num does not exist

 Cause:	An attempt to add or drop a redo log group member specified a redo log file group number that does not exist.

 Action:	Check the configuration of the redo log files and retry the command with a valid group number.

ORA-00360	not a logfile member:  name

 Cause:	An invalid filename was given to drop a redo log group member. Either the file is not a part of the database, or it is a datafile.

 Action:	Specify a valid member name and retry the command.

ORA-00361	cannot remove last logmember name group num

 Cause:	An attempt was made to remove the last member of a redo log group.

 Action:	If desired, delete the entire log by using the DROP LOGFILE command.

ORA-00362	member is required to form a valid logfile in group name

 Cause:	A request to drop a redo log group member was denied because it would remove data required to form a complete online redo log group.

 Action:	If desired, delete the entire log (after archiving, if required) using the DROP LOGFILE command.

ORA-00363	log is not the archived version

 Cause:	The log given for recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as the end of the thread. This message can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.

 Action:	Find the archived version of the log and specify its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.

ORA-00364	can not write header to new log member

 Cause:	An I/O error occurred when attempting to write the header to a redo log group member that is being added to an existing group.

 Action:	See accompanying messages. Fix the problem or use another file.

ORA-00365	the specified log is not the correct next log

 Cause:	The specified log failed to pass checks to ensure it corresponds to the log that was generated against a cold backup image of the database.

 Action:	Find the log that was generated by this copy of the database and give that filename to recover.

ORA-00369	Current log of thread %s not useable and other log being cleared

 Cause:	Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.

 Action:	If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise re-enter the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs.

ORA-00371	no free buffer handles available

 Cause:	The value of the initialization parameter DB_HANDLES is too small.

 Action:	Shut down the instance, increase the value of DB_HANDLES in the initialization parameter file, and then restart the instance. Under normal circumstances, let DB_HANDLES take its default value by omitting the parameter from the initialization parameter file.

ORA-00372	file name can not be modified at this time

 Cause:	An attempt was made to access a file being taken off line, or the database may be closing.

 Action:	Access the file after it is taken off line. Attempts will either succeed because the datafile is back online or fail with a message describing which file is off line. Repeat until successful.

ORA-00373	online log version ver incompatible with Oracle version ver

 Cause:	The online log was written by an incompatible version of Oracle. This can occur when the redo log file was created by either a newer or older version of Oracle.

 Action:	Recover the database using a compatible version, shut it down cleanly; then restart with the current software.

ORA-00374	parameter DB_BLOCK_SIZE = num invalid, valid range [num..num]

 Cause:	An invalid value has been used for the DB_BLOCK_SIZE initialization parameter.

 Action:	Adjust the parameter and restart the instance.

ORA-00375	unable to get default DB_BLOCK_SIZE

 Cause:	The system was unable to determine the default DB_BLOCK_SIZE.

 Action:	See the corresponding operating system-specific message. As a work-around, specify the block size with the parameter DB_BLOCK_SIZE in the initialization parameter file. See also your operating system-specific Oracle documentation.

ORA-00376	file name can not be read at this time

 Cause:	An attempt was made to read from a file that is not readable. The most likely cause is that the file is off line.

 Action:	Check the state of the file. Bring the file online, if necessary.

ORA-00390	log %s of thread %s is being cleared, cannot become current log

 Cause:	An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.

 Action:	If the clear command is still executing then wait for its completion. If it terminated then re-enter the clear command or drop the log.

ORA-00391	All threads must switch to new log format at the same time

 Cause:	An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.

 Action:	Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database.

ORA-00392	log %s of thread %s is being cleared, operation not allowed

 Cause:	An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.

 Action:	If the clear command is still executing then wait for its completion. If it terminated then reenter the clear command or drop the log.

ORA-00393	log %s of thread %s is needed for recovery of offline datafiles

 Cause:	Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped.

 Action:	Archive the log then repeat the clear command. If archiving is not possible and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.


CHAPTER 3. PL/SQL AND FIPS MESSAGES

This chapter lists messages generated by PL/SQL. For each PL/SQL message, the probable cause and corrective action are given.

To help you find and fix errors, PL/SQL inserts object names, numbers, and character strings into some error messages. These message inserts are represented by name, num, and str respectively. For example, the error message listed as

PLS-00388: undefined column 'name' in subquery

might actually appear as:

PLS-00388: undefined column 'AMPNO' in subquery

This chapter also lists the warnings that can be generated when the FIPS flagger is set in an Oracle product, and an Oracle extension to the SQL92 standard is used or a SQL92 feature is used in a nonconforming manner. FIPS warnings messages are listed for completeness. The cause and actions are described in the ANSI document ANSI X3.135-1992.

 ________________________________________

00000-01000: PL/SQL Messages

PLS-00101	reserved for future use

Not in Release 2.1.

PLS-00102	parser stack overflow because nesting is too deep

 Cause:	The parser, which checks the syntax of PL/SQL statements, uses a data structure called a stack. The number of levels of nesting in your PL/SQL block exceeded the stack capacity.

 Action:	Reorganize your block structure to avoid nesting at too deep a level. For example, move the lowest-level sub-block to a higher level.

PLS-00103	found 'str' but expected one of the following: 'str'

 Cause:	This error message is from the parser. It found a token (language element) that is inappropriate in this context.

 Action:	Check the previous tokens and the one given in the error message. The line and column numbers given in the error message refer to the end of the faulty language construct.

PLS-00104	empty argument list in call of procedure 'name' must be omitted

 Cause:	In a subprogram call, the name of the subprogram was followed by an empty parameter list. For example, procedure P was called as P(). This is not allowed.

 Action:	Remove the empty parameter list. In the example, change the procedure call to P.

PLS-00105	at most one forward declaration of type 'name' is permitted

Not in Release 2.1.

PLS-00108	declarative units must be a single variable declaration

 Cause:	While checking a declarative unit (a top-level declare block without the BEGIN...END), PL/SQL found that there was more than one item declared or that the item was not a variable declaration. A table is a common variable declaration at the unit level. To define a TABLE, you can compile a DECLARE compilation unit, but only one at a time is allowed.

 Action:	Declare variables in separate declarative units.

PLS-00109	unknown exception name 'name' in PRAGMA EXCEPTION_INIT

 Cause:	No declaration for the exception name was found within its scope.

 Action:	Check that the pragma follows the exception declaration and is within the same scope.

PLS-00110	bind variable 'name' not allowed in this context

 Cause:	A bind variable, that is, an identifier prefixed with a colon, was found in an inappropriate context.

 Action:	Remove the colon or replace the bind variable with the appropriate object.

PLS-00111	end-of-file in comment

 Cause:	A comment had a comment initiator (/*), but before the comment terminator (*/) was found, an end-of-file marker was encountered.

 Action:	Remove the comment initiator or add a comment terminator. The line and column numbers given in the error message refer to the beginning of the last legal token before the comment initiator.

PLS-00112	end-of-line in quoted identifier

 Cause:	A quoted identifier had a beginning quote ("), but before the ending quote (") was found, an end-of-line marker was encountered.

 Action:	Remove the beginning quote or add the ending quote. The line and column numbers given in the error message refer to the beginning of the quoted identifier.

PLS-00113	END identifier 'name1' must match 'name2' at line num, column num

 Cause:	Following the keyword END, which terminates some language constructs (such as loops, blocks, functions, and procedures), you can optionally place the name of that construct. For example, at the end of the definition of loop L, you might write END L.

This error occurs when the optional name does not match the name given to the language construct. It is usually caused by a misspelled identifier or by faulty block structure.

 Action:	Check that the spelling of the END identifier matches the name given to the language construct and that the block structure is correct.

PLS-00114	bind variable 'name' exceeds implementation length

 Cause:	The name of a PL/SQL variable is longer than 30 characters. Legal identifiers (including quoted identifiers) have a maximum length of 30 characters. You might have mistakenly enclosed a string literal in double quotes instead of single quotes. In which case PL/SQL considers it a quoted identifier.

 Action:	Shorten the name to 30 characters or less or if you are using a string literal, replace the double quotes with single quotes.

PLS-00115	this PRAGMA must follow the declaration of 'name'

 Cause:	The pragma refers to a PL/SQL object that was not declared or is not within the scope of the reference. Identifiers must be declared before they are used in a pragma. Forward references are not allowed.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00116	duplicate WHERE clause in table expression

 Cause:	Two or more WHERE clauses were found in a DELETE, SELECT, or UPDATE statement. The WHERE clause specifies a condition under which rows in a table are processed. The condition can contain several logical expressions connected by AND or OR, but a statement can contain only one WHERE clause.

 Action:	Remove one of the WHERE clauses and, if necessary, connect logical expressions by AND or OR.

PLS-00117	duplicate CONNECT BY clause in table expression

 Cause:	Two or more CONNECT BY clauses were found in a SELECT statement. The CONNECT BY clause defines a relationship used to return rows in a hierarchical order. The relationship can contain two expressions separated by a relational operator (such as = or !=), but a statement can contain only one CONNECT BY clause.

 Action:	Remove one of the CONNECT BY clauses. If necessary, separate expressions by a relational operator.

PLS-00118	duplicate GROUP BY clause in table expression

 Cause:	Two or more GROUP BY clauses were found in a SELECT statement. The GROUP BY clause lists column expressions used to form a summary row for each group of selected rows. The list can contain several column expressions separated by commas, but a statement can contain only one GROUP BY clause.

 Action:	Remove one of the GROUP BY clauses. If necessary, separate column expressions by commas.

PLS-00119	duplicate HAVING clause in table expression

 Cause:	Two or more HAVING clauses were found in a SELECT statement. The HAVING clause specifies a condition under which groups of rows (formed by the GROUP BY clause) are included in the result. The condition can include several logical expressions connected by AND or OR, but a statement can contain only one HAVING clause.

 Action:	Remove one of the HAVING clauses. If necessary, connect logical expressions by AND or OR.

PLS-00120	inappropriate argument in OPEN statement

 Cause:	The cursor_name parameter in an OPEN statement is misspelled or does not refer to a legally declared cursor.

 Action:	Check your spelling of the cursor_name parameter. Make sure the cursor was declared properly.

PLS-00121	only the set function COUNT may take * as an argument

 Cause:	You used the asterisk (*) option in the argument list of a SQL group function other than COUNT. For example, you might have coded:

 SELECT SUM(*) INTO emp_count FROM emp;  -- should be COUNT(*) 	Only COUNT lets you use the asterisk option, which returns the number of rows in a table.

 Action:	Remove the asterisk option from the argument list and replace it with an expression that refers to one or more database columns.

PLS-00123	program too large

 Cause:	PL/SQL was designed primarily for robust transaction processing. One consequence of the special-purpose design is that the PL/SQL compiler imposes a limit on block size. The limit depends on the mix of statements in your PL/SQL block. Blocks that exceed the limit cause this error.

 Action:	The best solution is to modularize your program by defining subprograms, which can be stored in an Oracle database. Another solution is to break your program into two sub-blocks. Have the first block INSERT any data the second block needs into a temporary database table. Then, have the second block SELECT the data from the table.

PLS-00124	name of exception expected for first argument in EXCEPTION_INIT pragma

 Cause:	The first argument passed to the EXCEPTION_INIT pragma was something other than an exception name. The first argument must be the name of a legally declared exception.

 Action:	Replace the first argument with the name of a legally declared exception.

PLS-00125	type name expected

 Cause:	When declaring a constant or variable, you failed to specify its datatype. For example, you might have coded:

 pi  CONSTANT := 3.14159;  -- should be CONSTANT REAL := 3.14159 	Every constant and variable must have a datatype, which specifies a storage format, constraints, and valid range of values.

 Action:	Supply the missing datatype specifier.

PLS-00201	identifier 'name' must be declared

 Cause:	You tried to reference an undefined variable, exception, procedure, function, or other object. Either you failed to declare the identifier or it is not within the scope of the reference.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00202	type 'name' must be declared

 Cause:	You tried to reference an undefined type. Either you failed to declare the type identifier or it is not within the scope of the reference.

 Action:	Check your spelling and declaration of the type identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00203	function DECODE must be called with at least 3 non-Boolean arguments

 Cause:	Less than three arguments were passed to the built-in function DECODE. Though DECODE takes a variable number of (non-Boolean) arguments, you must pass it at least three.

 Action:	Call DECODE with three or more arguments.

PLS-00204	function or pseudocolumn 'name' may be used inside a SQL statement only

 Cause:	A pseudocolumn or proscribed function was used in a procedural statement. The SQL pseudocolumns (CURRVAL, LEVEL, NEXTVAL, ROWID, ROWNUM) can be used only in SQL statements. Likewise, certain functions, such as DECODE and the SQL group functions (AVG, MIN, MAX, COUNT, SUM, STDDEV, VARIANCE), can be used only in SQL statements.

 Action:	Remove the pseudocolumn reference or function call from the procedural statement or replace the procedural statement with a SELECT INTO statement; for example, replace:

 bonus := DECODE(rating, 1, 5000, 2, 2500, ...); 	with the following statement:

 SELECT DECODE(rating, 1, 5000, 2, 2500, ...) INTO bonus FROM dual; 	PLS-00205	aggregate not allowed here

 Cause:	An aggregate, that is, a parenthesized list of values such as (7788, 'SCOTT', 20), was found in an inappropriate context.

 Action:	Remove or relocate the aggregate.

PLS-00206	%TYPE must be applied to a variable or column, not 'name'

 Cause:	The program object declared using the %TYPE datatype attribute is not of the appropriate class. It must be a variable, column, record component, subprogram formal parameter, or other object to which values can be assigned.

 Action:	Declare an object of the appropriate class or define the datatype in another way (for example, use %ROWTYPE).

PLS-00207	identifier 'name', applied to implicit cursor SQL, is not a legal cursor attribute

 Cause:	An identifier that is not a cursor attribute was applied to the identifier SQL. For example, this error occurs if the cursor attribute is misspelled.

 Action:	Check your spelling of the cursor attribute name. Check that the attribute is one of these: %NOTFOUND, %FOUND, %ROWCOUNT, %ISOPEN.

PLS-00208	identifier 'name' is not a legal cursor attribute

 Cause:	An identifier not declared as a cursor attribute was applied to an identifier declared as a cursor. For example, this error occurs if the cursor attribute is misspelled.

 Action:	Check your spelling of the cursor attribute name. Check that the attribute is one of these: %NOTFOUND, %FOUND, %ROWCOUNT, %ISOPEN.

PLS-00209	table 'name' is not in FROM clause

 Cause:	In a query, a table referenced by the select list is not named in the FROM clause.

 Action:	Check your spelling of the table names, check each column in the select list refers to a table in the FROM clause, then re-execute the query.

PLS-00210	an OTHERS clause is required in this CASE statement

Not in Release 2.1.

PLS-00211	CASE labels or ranges must not be duplicated in different WHEN clauses

Not in Release 2.1.

PLS-00212	could not obtain enough memory to compile CASE statement

Not in Release 2.1.

PLS-00213	package STANDARD not accessible

 Cause:	The PL/SQL compiler could not find package STANDARD in the current Oracle database. To compile a program, PL/SQL needs package STANDARD.

 Action:	Check that package STANDARD is available in the current Oracle database, then retry the operation.

PLS-00214	BEGIN...END block nesting is too deep

 Cause:	The number of levels of nesting in your PL/SQL block is too large. You can nest blocks up to 255 levels deep, depending on the availability of system resources such as memory.

 Action:	Reorganize your block structure to avoid nesting at too deep a level. For example, move the lowest-level sub-block to a higher level.

PLS-00215	string length constraints must be in range (1 .. 32767)

 Cause:	When declaring a character variable, you specified a length that is outside the legal range. For example, the following declarations are illegal:

 flag  CHAR(0);        -- illegal; zero lengthname  VARCHAR2(-10);  -- illegal; negative length  Action:	Change the length constraint, making sure that it lies in the range of 1 .. 32767.

PLS-00216	NUMBER precision constraint must be in range (1 .. 38)

 Cause:	You declared a NUMBER variable with a precision that is outside the legal range. Declarations such as N NUMBER(800) or N NUMBER(123,10) are not supported.

 Action:	Change the illegal NUMBER precision constraint, making sure that it lies in the range of 1 .. 38.

PLS-00217	NUMBER scale constraint must be in range (-84 .. 127)

 Cause:	You declared a NUMBER variable with a scale that is outside the legal range. Declarations such as N NUMBER(10,345) or N NUMBER(10,-100) are not supported.

 Action:	Change the illegal NUMBER scale constraint, making sure that it lies in the range of -84 .. 127.

PLS-00218	a variable declared NOT NULL must have an initialization assignment

 Cause:	In general, variables that have no initialization clause in their declaration are automatically initialized to NULL. This is illogical for NOT NULL variables, and therefore an initialization clause is required.

 Action:	Add an initialization clause to the variable declaration.

PLS-00219	label 'name' reference is out of scope

 Cause:	A block or loop label was used to qualify a variable (as in outer_block.date) that was not declared or is not within the scope of the label. The variable name might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the variable name. Also check that the declaration is placed correctly in the block structure.

PLS-00220	simple name required in this context

 Cause:	A qualified name such as A.B or A.B.C is not permitted here.

 Action:	Use a simple name such as A instead.

PLS-00221	'name' is not a procedure or is undefined

 Cause:	The named identifier is being referenced as a procedure, but the identifier was not declared or actually represents another object. For example, it might have been declared as a function.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00222	no function with name 'name' exists in this scope

 Cause:	The named identifier is being referenced as a function, but the identifier was not declared or actually represents another object. For example, it might have been declared as a procedure.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00223	parameterless procedure 'name' used as function

 Cause:	The named identifier is being referenced as a parameterless function, but the identifier actually represents a procedure.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure. If necessary, change the declaration of the identifier or change the reference so that it does not require a return value.

PLS-00224	object 'name' must be of type function or array to be used this way

 Cause:	The named identifier is being referenced as a function or an array, but the identifier actually represents an object (a number or date, for example) that cannot be referenced in this way.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00225	subprogram or cursor 'name' reference is out of scope

 Cause:	A subprogram or cursor references a variable that was not declared or is not within the scope of the subprogram or cursor. The variable name might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the variable name. Also check that the declaration is placed correctly in the block structure.

PLS-00226	package 'name' used as variable reference

 Cause:	A package was referenced in an expression, as if it were a variable or function. Either the name of the variable or function is misspelled or the reference is not fully qualified. For example, to call the function my_function, which is stored in package my_package, you must use dot notation as follows:

 ... my_package.my_function ...  Action:	Correct your spelling of the variable or function name or use dot notation to reference the packaged variable or function.

PLS-00227	IN formal parameter 'name' not allowed in this context

 Cause:	When declaring the formal parameters of a subprogram, you used one parameter to initialize another, as in:

 PROCEDURE my_proc (j NUMBER, k NUMBER := j) IS ... 	The first parameter has no value until run time, so it cannot be used to initialize another parameter.

 Action:	Remove the illegal formal parameter reference.

PLS-00229	attribute expression within SQL expression

 Cause:	You used an attribute expression such as SQL%NOTFOUND in a SQL statement, but attribute expressions are allowed only in procedural statements.

 Action:	To work around this limitation, assign the value of the attribute expression to a variable, then use the variable in the SQL statement. For example, replace the statement:

 INSERT INTO audits VALUES (c1%ROWCOUNT, ...); 	with the following statements:

 row_count := c1%ROWCOUNT;INSERT INTO audits VALUES (row_count, ...); 	PLS-00230	OUT and IN OUT formal parameters may not have default expressions

 Cause:	When declaring the formal parameters of a procedure, you initialized an OUT or IN OUT parameter to a default value, as in:

 PROCEDURE calc_bonus (bonus OUT REAL := 0, ...) IS ... 	However, only IN parameters can be initialized to default values.

 Action:	Remove the illegal default expression.

PLS-00231	function 'name' may not be used in SQL

 Cause:	You used a proscribed function in a SQL statement. Certain functions, such as SQLCODE and SQLERRM, can be used only in procedural statements.

 Action:	Remove the function call from the SQL statement, or replace the function call with a local variable. For example, the following statement is illegal:

 INSERT INTO errors VALUES (SQLCODE, SQLERRM); 	However, you can assign the values of SQLCODE and SQLERRM to local variables, then use the variables in the SQL statement, as follows:

 err_num := SQLCODE;err_msg := SQLERRM;INSERT INTO errors VALUES (err_num, err_msg); 	PLS-00232	nested packages not permitted

 Cause:	You declared a package inside another package, but package declarations are allowed only at the top level. In other words, you cannot nest packages.

 Action:	Move the package declaration outside the enclosing package.

PLS-00233	function name used as an exception name in WHEN clause

 Cause:	The WHEN clause in an exception handler contains a function call instead of an exception name. A valid exception handler consists of a WHEN clause, which must specify an exception, followed by a sequence of statements to be executed when that exception is raised.

 Action:	Check your spelling of the identifier in the WHEN clause, then replace the function call with an exception name.

PLS-00302	component 'name' must be declared

 Cause:	In a reference to a component (for example, in the name A.B, B is a component of A), the component was not declared. The component might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the component. Also check that the declaration is placed correctly in the block structure.

PLS-00303	qualifier 'name' must be declared

 Cause:	In a name such as A.B, A is a qualifier, and B is a component of the qualifier. This error occurs when no declaration for the qualifier is found. The qualifier might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the qualifier. Also check that the declaration is placed correctly in the block structure.

PLS-00304	cannot compile body of 'name' without its specification

 Cause:	The compiled package specification needed to compile a package body could not be found. Some possible causes follow:

 •	The package name is misspelled.•	The package specification was never compiled.•	The compiled package specification is not accessible. 	You must compile the package specification before compiling the package body, and the compiler must have access to the compiled specification.

 Action:	Check your spelling of the package name. Compile the package specification before compiling the package body. And, check that the compiler has access to the compiled specification.

PLS-00305	previous use of 'name' conflicts with this use

 Cause:	While looking for prior declarations of a cursor, procedure, function, or package, the compiler found another object with the same name in the same scope.

 Action:	Check your spelling of the cursor, procedure, function, or package name. Also check the names of all constants, variables, parameters, and exceptions declared in the same scope. Then, remove or rename the object with the duplicate name.

PLS-00306	wrong number or types of arguments in call to 'name'

 Cause:	This error occurs when the named subprogram call cannot be matched to any declaration for that subprogram name. The subprogram name might be misspelled, a parameter might be of the wrong datatype, the declaration might be faulty, or the declaration might be placed incorrectly in the block structure. For example, this error occurs if you call the built-in square root function SQRT with a misspelled name or with a parameter of the wrong datatype.

 Action:	Check your spelling and declaration of the subprogram name. Also check that its call is correct, its parameters are of the right datatype, and, if it is not a built-in function, that its declaration is placed correctly in the block structure.

PLS-00307 	too many declarations of 'name' match this call

 Cause:	The declaration of a subprogram name is ambiguous because there is no exact match between the declaration and the call. When implicit conversions of the parameter datatypes are used, more than one declaration matches the call. The subprogram name might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the subprogram name. Also check that its call is correct, its parameters are of the right datatype, and, if it is not a built-in function, that its declaration is placed correctly in the block structure.

PLS-00308	this construct is not allowed as the origin of an assignment

 Cause:	The construct or expression does not designate a value that can be assigned to a variable. For example, the datatype name NUMBER cannot appear on the right-hand side of an assignment statement as in X := NUMBER.

 Action:	Correct the illegal assignment statement.

PLS-00309	with %LAST attribute, 'name' must be a variable of an enumerated type

Not in Release 2.1.

PLS-00310	with %ROWTYPE attribute, 'name' must name a cursor or table

 Cause:	The %ROWTYPE attribute must be applied to an identifier declared as a cursor or table. This error occurs when %ROWTYPE follows some identifier that has not been so declared.

 Action:	Change the declaration or do not apply the %ROWTYPE attribute to the identifier.

PLS-00311	the declaration of the type of 'name' is incomplete or malformed

 Cause:	This occurrence of the identifier cannot be compiled because its datatype has not been properly defined.

 Action:	Correct the faulty datatype declaration.

PLS-00312	a positional parameter association may not follow a named association

 Cause:	When passing a list of parameters to a subprogram or cursor, if you use both positional and named associations, you must place all positional associations in their declared order and before all named associations, which can be in any order.

 Action:	Reorder the parameter list to meet the requirements or use named association only.

PLS-00313	'name' not declared in this scope

 Cause:	There is no declaration for the given identifier within the scope of reference. The identifier might be misspelled, its declaration might be faulty, or the declaration might be placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00314	TABLE declarations are not allowed as PL/SQL local variables

 Cause:	In a precompiled program, you mistakenly used the DECLARE TABLE statement inside an embedded PL/SQL block. If an embedded PL/SQL block refers to a database table that does not yet exist, you can use the DECLARE TABLE statement to tell the precompiler what the table will look like. But, DECLARE TABLE statements are allowed only in the host program.

 Action:	Move the DECLARE TABLE statement outside the embedded PL/SQL block. If you want a variable that can store an entire row of data selected from a database table or fetched by a cursor, use the %ROWTYPE attribute.

PLS-00315	PL/SQL TABLE declarations must currently use BINARY_INTEGER indexes

 Cause:	In the INDEX BY clause of a PL/SQL table declaration, you specified a datatype other than BINARY_INTEGER. PL/SQL tables can have one column and a primary key. The column can belong to any scalar type, but the primary key must belong to type BINARY_INTEGER.

 Action:	Change the datatype specifier to BINARY_INTEGER.

PLS-00316	PL/SQL TABLE declarations must currently use a single index

 Cause:	In the INDEX BY clause of a PL/SQL table declaration, you specified a composite primary key. PL/SQL tables must have a simple, unnamed primary key of type BINARY_INTEGER.

 Action:	Change the faulty clause to INDEX BY BINARY_INTEGER.

PLS-00319	subquery in an IN or NOT IN clause must contain exactly one column

 Cause:	You used an invalid expression such as:

 a IN (SELECT x, y, z FROM ... ) 	When a [NOT]IN clause is used with a subquery, it does not test for set membership. The number of expressions in the [NOT]IN clause and the subquery select list must match, so, in the example above, the subquery must specify at most one column.

 Action:	Change the subquery to select only one column.

PLS-00320	the declaration of the type of this expression is incomplete or malformed

 Cause:	In a declaration, the name of a variable or cursor is misspelled or the declaration makes a forward reference. Forward references are not allowed in PL/SQL. You must declare a variable or cursor before referencing it in other statements, including other declarative statements. For example, the following declaration of dept_rec raises this exception because it refers to a cursor not yet declared:

 DECLARE   dept_rec  dept_cur%ROWTYPE;   CURSOR dept_cur IS SELECT ...   ...  Action:	Check your spelling of all identifiers in the declaration. If necessary, move the declaration so that it makes no forward references.

PLS-00321	expression 'str' is inappropriate as the left hand side of an assignment statement

 Cause:	The expression does not designate a variable that can have a value assigned to it. For example, the function SYSDATE cannot appear on the left-hand side of an assignment statement such as:

 SYSDATE := '01-JAN-1990';  Action:	Correct the illegal assignment statement.

PLS-00322	declaration of a constant 'name' must contain an initialization assignment

 Cause:	A constant declaration is lacking the assignment of the constant value. For example, in the following declaration ":= 3.14159" is the initialization assignment:

 pi CONSTANT NUMBER := 3.14159;  Action:	Correct the constant declaration by supplying the missing initialization assignment.

PLS-00323	subprogram 'name' is declared in a package specification and must be defined in the package body

 Cause:	You placed a subprogram specification in a package specification, but neglected to place the corresponding subprogram body in the package body. The package body implements the package specification, so the package body must contain the definition of every subprogram declared in the package specification.

 Action:	Check your spelling of the subprogram name. If necessary, add the missing subprogram body to the package body.

PLS-00324	cursor attribute may not be applied to non-cursor 'name'

 Cause:	This error occurs when a cursor attribute (%FOUND, %NOTFOUND, %ROWCOUNT, or %ISOPEN) appears following an identifier not declared as a cursor. It occurs, for example, if the variable name my_cur in my_cur%FOUND was not properly declared as a cursor or if the variable declaration was placed incorrectly in the block structure.

 Action:	Check your spelling and declaration of the identifier. Also check that the declaration is placed correctly in the block structure.

PLS-00325	non-integral numeric literal num is inappropriate in this context

 Cause:	A non-integral numeric literal was used in a context that requires an integer (a number with no fractional part).

 Action:	Replace the inappropriate literal with an integral literal.

PLS-00326	IN clause must contain same number of expressions as subquery

 Cause:	The number of expressions in an IN clause did not equal the number of expressions in a corresponding subquery select list. For example, the following statement is invalid because the IN clause contains two expressions, but the subquery select list contains just one:

 ... WHERE (ename, sal) IN (SELECT sal FROM emp);  Action:	Check the number of expressions in each set, then change the statement to make the numbers equal.

PLS-00328	a subprogram body must be defined for the forward declaration of 'name'

 Cause:	You declared a subprogram specification, but failed to define the corresponding subprogram body. You can write the subprogram specification and body as a unit, or you can separate the specification from its body, which is necessary when you want to define mutually recursive subprograms or group subprograms in a package.

 Action:	Check your spelling of the subprogram name. If necessary, supply the missing subprogram body.

PLS-00330	invalid use of type name or subtype name

 Cause:	You mistakenly used a datatype or subtype specifier in place of a constant, variable, or expression. For example, you might have coded:

 IF emp_count > number THEN ... -- illegal; NUMBER is a datatype specifier  Action:	Replace the datatype or subtype specifier with a valid constant, variable, or expression.

PLS-00335	a package name conflicts with an existing object

 Cause:	When trying to create a package (which is a database object that groups logically related PL/SQL types, objects, and subprograms), you gave it the same name as an existing database object.

 Action:	Give the package a unique name.

PLS-00341	declaration of cursor 'name' is incomplete or malformed

 Cause:	A cursor declaration is improper or an identifier referenced in the cursor declaration was not properly declared. You might have specified a return type (%ROWTYPE) that does not refer to an existing database table or previously declared cursor. For example, the following cursor declaration is illegal because c1 is not yet fully defined:

 CURSOR c1 RETURN c1%ROWTYPE IS SELECT ...  -- illegal 	In this case, you need not specify a return type because it is implicit.

 Action:	Check your spelling and declaration of the cursor name and any identifiers referenced in the cursor declaration. Also check that the declaration is placed correctly in the block structure. If you specified a return type, check that it refers to an existing database table or previously declared cursor.

PLS-00351	not logged on to database 'name'

 Cause:	You tried to access an Oracle database without being logged on. Probably, an invalid username or password was entered.

 Action:	Log on to Oracle with a correctly-spelled username and password before trying to access the database.

PLS-00352	unable to access another database 'name'

 Cause:	You tried to reference an object in a database other than the current local or remote Oracle database.

 Action:	Correct your reference and check that the object is in the current Oracle database.

PLS-00353	'name' must name a user in the database

 Cause:	This error occurs when the username was misspelled or when the user does not exist in the database.

 Action:	Check your spelling of the username and check that the user exists.

PLS-00354	username must be a simple identifier

 Cause:	A qualified username such as scott.accts is not permitted in this context.

 Action:	Specify a simple username such as scott instead.

PLS-00355	use of PL/SQL table not allowed in this context

 Cause:	You referenced a PL/SQL table in the wrong context (for example, with a remote link).

 Action:	Remove the PL/SQL table reference or change the context.

PLS-00356	'name' must name a table to which the user has access

 Cause:	The named table is not accessible to the user. This error occurs when the table name or username was misspelled, the table and/or user does not exist in the database, the user was not granted the necessary privileges, or the table name duplicates the name of a local variable or loop counter.

 Action:	Check your spelling of the table name and username. Also check that the table and user exist, that the user has the necessary privileges, and that the table name does not duplicate the name of a local variable or loop counter.

PLS-00357	table, view or sequence reference 'name' not allowed in this context

 Cause:	A reference to a database table, view, or sequence was found in an inappropriate context. Such references can appear only in SQL statements or (excluding sequences) in %TYPE and %ROWTYPE declarations. Some valid examples follow:

 SELECT ename, emp.deptno, dname INTO my_ename, my_deptno, my_dept   FROM emp, dept WHERE emp.deptno = dept.deptno;DECLARE   last_name  emp.ename%TYPE;   dept_rec   dept%ROWTYPE;  Action:	Remove or relocate the illegal reference.

PLS-00358	column 'name' exists in more than one table; use qualifier

 Cause:	Your statement is ambiguous because it specifies two or more tables having the same column name. For example, the following statement is ambiguous because deptno is a column in both tables:

 SELECT deptno, loc INTO my_deptno, my_loc FROM emp, dept;  Action:	Precede the column name with the table name (as in emp.deptno) so that the column reference is unambiguous.

PLS-00359	assignment target in 'str' must have components

 Cause:	An assignment target was not declared to have the required components. For example, this error occurs if you try to assign a row of column values to a variable instead of a record, as follows:

 DECLARE   dept_rec   dept%ROWTYPE;   my_deptno  dept.deptno%TYPE;   ...BEGIN   SELECT deptno, dname, loc INTO my_deptno  -- invalid      FROM dept WHERE ...   ...  Action:	Check your spelling of the names of the assignment target and all its components. Check that the assignment target is declared with the required components and that the declaration is placed correctly in the block structure.

PLS-00360	cursor declaration without body needs return type

 Cause:	A cursor declaration lacks either a body (SELECT statement) or a return type (%ROWTYPE). If you want to separate a cursor specification from its body, you must supply a return type, as in:

 CURSOR c1 RETURN emp%ROWTYPE;  Action:	Add a SELECT statement or return type to the cursor declaration.

PLS-00363	expression 'str' cannot be used as an assignment target

 Cause:	You mistakenly used a literal, constant, IN parameter, loop counter, or function call as the target of an assignment. For example, the following statement is illegal because the assignment target, 30, is a literal:

 SELECT deptno INTO 30 FROM dept WHERE ...  -- illegal  Action:	Correct the statement by using a valid assignment target.

PLS-00364	loop index variable 'name' use is invalid

 Cause:	A reference to a loop counter was found in an inappropriate context. For example, the following statement is illegal because the loop counter is used as the terminal value in its own range expression:

 FOR j IN 1 .. j LOOP ...  -- illegal  Action:	Change the loop range expression so that it does not reference the loop counter. If you want to refer in the range expression to another variable with the same name as the loop counter, change one of the names or qualify the variable name with a label.

PLS-00365	'name' is an OUT parameter and cannot be read

 Cause:	You tried to assign the value of an OUT parameter to another parameter or variable. Inside a procedure, an OUT parameter acts like an uninitialized variable. Therefore, its value cannot be read. For example, the following assignments are illegal:

 PROCEDURE calc_bonus (bonus OUT REAL, ...) IS   rating  REAL;   wages   REAL;BEGIN   ...   IF rating > 90 THEN      bonus := bonus * 2;  -- illegal   END IF;   SELECT sal + bonus INTO wages FROM emp ...  -- illegal   ...END calc_bonus;  Action:	Use an IN OUT parameter instead of the OUT parameter. Inside a procedure, an IN OUT parameter acts like an initialized variable. Therefore, its value can be read.

PLS-00366	subtype of a NOT NULL type must also be NOT NULL

 Cause:	After defining a subtype as NOT NULL, you used it as the base type for another subtype defined as NULL. That is not allowed. For example, you might have coded:

 DECLARE   SUBTYPE Weekday IS INTEGER NOT NULL;   SUBTYPE Weekend IS Weekday NULL;  -- illegal 	instead of:

 DECLARE   SUBTYPE Weekday IS INTEGER NOT NULL;   SUBTYPE Weekend IS Weekday;  Action:	Revise the subtype definitions to eliminate the conflict.

PLS-00367	a RAISE statement with no exception name must be inside an exception handler

 Cause:	A RAISE statement not followed by an exception name was found outside an exception handler.

 Action:	Delete the RAISE statement, relocate it to an exception handler, or supply the missing exception name.

PLS-00368	in RAISE statement, 'name' must be an exception name

 Cause:	The identifier in a RAISE statement is not a valid exception name.

 Action:	Check that the identifier in the RAISE statement was declared as an exception and is correctly placed in the block structure. If you are using one of the PL/SQL predefined exception names, check its spelling.

PLS-00369	no choices may appear with choice OTHERS in an exception handler

 Cause:	A construct of the form:

 WHEN excep1 OR OTHERS => 	was encountered in the definition of an exception handler. OTHERS must appear by itself as the last exception handler in a block.

 Action:	Remove the identifier that appears with OTHERS or write a separate exception handler for that identifier.

PLS-00370	OTHERS handler must be last among the exception handlers of a block

 Cause:	One or more exception handlers appear after an OTHERS handler. However, the OTHERS handler must be the last handler in a block or subprogram because it acts as the handler for all exceptions not named specifically.

 Action:	Move the OTHERS handler so that it follows all specific exception handlers.

PLS-00371	at most one declaration for 'name' is permitted in the declaration section

 Cause:	A reference to an identifier is ambiguous because there are conflicting declarations for it in the declaration section of a block, procedure, or function. At most one declaration of the identifier is permitted in a declaration section.

 Action:	Check your spelling of the identifier. If necessary, remove all but one declaration of the identifier.

PLS-00372	in a procedure, RETURN statement cannot contain an expression

 Cause:	In a procedure, a RETURN statement contains an expression, which is not allowed. In functions, a RETURN statement must contain an expression because its value is assigned to the function identifier. However, in procedures, a RETURN statement simply lets you exit before the normal end of the procedure is reached.

 Action:	Remove the expression from the RETURN statement or redefine the procedure as a function.

PLS-00373	EXIT label 'name' must label a LOOP statement

 Cause:	The statement with the named label is not a loop. An EXIT statement does not require a label operand, but if you specify one (as in EXIT my_label), it must be the label of a loop statement.

 Action:	Check that the label name is spelled correctly and that it refers to a loop statement.

PLS-00374	illegal EXIT statement; it must appear inside the loop labeled 'name'

 Cause:	An EXIT statement does not require a label operand, but if you specify one (as in EXIT my_label), the EXIT statement must be inside the loop designated by that label.

 Action:	Check that the label name is spelled correctly, placed properly, and refers to the appropriate EXIT statement.

PLS-00375	illegal GOTO statement; this GOTO cannot branch to label 'name'

 Cause:	The line and column numbers accompanying the error message refer to a GOTO that branches from outside a construct (a loop or exception handler, for example) containing a sequence of statements to a label inside that sequence of statements. Such a branch is not allowed.

 Action:	Either move the GOTO statement inside the sequence of statements or move the labeled statement outside the sequence of statements.

PLS-00376	illegal EXIT statement; it must appear inside a loop

 Cause:	An EXIT statement was found outside of a loop construct. The EXIT statement is used to exit prematurely from a loop and so must always appear within a loop.

 Action:	Either remove the EXIT statement or place it inside a loop.

PLS-00377	internal type PLS_INTEGER is not included in this release of PL/SQL

 Cause:	In a declaration, you mistakenly specified the obsolete datatype PLS_INTEGER, which has been replaced by the datatype BINARY_INTEGER.

 Action:	Specify the datatype BINARY_INTEGER instead of PLS_INTEGER.

PLS-00378	invalid compilation unit for this release of PL/SQL

 Cause:	A compilation unit is a file containing PL/SQL source code that is passed to the compiler. Only compilation units containing blocks, declarations, statements, and subprograms are allowed. This error occurs when some other language construct is passed to the compiler.

 Action:	Check that the compilation unit contains only blocks, declarations, statements, and subprograms.

PLS-00379	CASE statements are not included in this release of PL/SQL

 Cause:	The unit being compiled contains a CASE statement. However, the current release of PL/SQL does not support CASE statements.

 Action:	Remove the CASE statement from the compilation unit.

PLS-00381	type mismatch found at 'name' between column and variable in subquery or INSERT

 Cause:	The datatypes of a column and a variable do not match. The variable was encountered in a subquery or INSERT statement.

 Action:	Change the variable datatype to match that of the column.

PLS-00382	expression is of wrong type

 Cause:	The given expression variable is of the wrong datatype for the context in which it was found.

 Action:	Change the datatype of the expression. You might want to use datatype conversion functions.

PLS-00383	type mismatch found at 'name' inside an IN or NOT IN clause

 Cause:	In a test for set membership such as X NOT IN (SELECT Y ... ), the expressions X and Y do not match in datatype, and it is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the select list.

PLS-00384	type mismatch found at 'name' in UPDATE's SET clause

 Cause:	The column to the left of the equal sign in the SET clause of an UPDATE statement does not match in datatype with the column, expression, or subquery to the right of the equal sign. It is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the SET clause.

PLS-00385	type mismatch found at 'name' in SELECT...INTO statement

 Cause:	The expressions to the left and right of the INTO clause in a SELECT...INTO statement do not match in datatype. It is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the select list.

PLS-00386	type mismatch found at 'name' between FETCH cursor and INTO variables

 Cause:	An assignment target in the INTO list of a FETCH statement does not match in datatype with the corresponding column in the select list of the cursor declaration. It is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the cursor declaration or the datatype of the assignment target. You might want to use datatype conversion functions in the select list of the query associated with the cursor.

PLS-00387	INTO variable cannot be a database object

 Cause:	An item in the INTO list of a FETCH or SELECT statement was found to be a database object. INTO introduces a list of user-defined variables to which output values are assigned. Therefore, database objects cannot appear in the INTO list.

 Action:	Check your spelling of the INTO list item. If necessary, remove the item from the INTO list or replace it with a user-defined output variable.

PLS-00388	undefined column 'name' in subquery

 Cause:	A subquery contains a column name that was not defined for the specified table.

 Action:	Change the expression to specify a column that was defined.

PLS-00389	undefined column 'name' in left-hand-side expression

 Cause:	A left-hand-side expression in a SQL statement refers to an undefined column.

 Action:	Check your spelling of the column name, then change the expression so that it refers only to defined columns.

PLS-00390	undefined column 'name' in INSERT statement

 Cause:	An INSERT statement refers to a column not defined for the table or view into which data is being INSERTed.

 Action:	Check your spelling of the column name, then change the statement so that it refers only to defined columns.

PLS-00391	undefined column 'name' in UPDATE statement

 Cause:	An UPDATE statement refers to a column not defined for the table or view being UPDATEd.

 Action:	Check your spelling of the column name, then change the statement so that it refers only to defined columns.

PLS-00392	type mismatch in arguments to BETWEEN

 Cause:	In a comparison such as X BETWEEN Y AND Z, the expressions X, Y, and Z do not match in datatype, and it is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the expressions so that their datatypes match. You might want to use datatype conversion functions.

PLS-00393	wrong number of columns in SELECT...INTO statement

 Cause:	The number of columns selected by a SELECT...INTO statement does not match the number of variables in the INTO clause.

 Action:	Change the number of columns in the select list or the number of variables in the INTO clause so that the numbers match.

PLS-00394	wrong number of values in the INTO list of a FETCH statement

 Cause:	The number of variables in the INTO clause of a FETCH statement does not match the number of columns in the cursor declaration.

 Action:	Change the number of variables in the INTO clause or the number of columns in the cursor declaration so that the numbers match.

PLS-00395	wrong number of values in VALUES clause of INSERT statement

 Cause:	The number of columns in an INSERT statement does not match the number of values in the VALUES clause. For example, the following statement is faulty because no column is specified for the value 20:

 INSERT INTO emp (empno, ename) VALUES (7788, 'SCOTT', 20);  Action:	Change the number of items in the column list or the number of items in the VALUES list so that the numbers match.

PLS-00396	INSERT statement's subquery yields wrong number of columns

 Cause:	The number of columns in an INSERT statement does not match the number of columns in a subquery select list. For example, the following statement is faulty because no corresponding column is specified for col3:

 INSERT INTO emp (ename, empno) SELECT col1, col2, col3 FROM ...  Action:	Change the number of items in the column list of the INSERT statement or the number of items the select list so that the numbers match.

PLS-00397	type mismatch in arguments to IN

 Cause:	In a test for set membership such as X IN (Y, Z), the expressions X, Y, and Z do not match in datatype, and it is unclear which implicit conversion is needed to correct the mismatch.

 Action:	Change the expressions so that their datatypes match. You might want to use datatype conversion functions.

PLS-00398	wrong number of columns in UNION, INTERSECT, or MINUS expression

 Cause:	The SELECT clauses to the left and right of a UNION, INTERSECT, or MINUS expression do not select the same number of columns. For example, the following statement is faulty because the select lists do not contain the same number of items:

 CURSOR my_cur IS SELECT ename FROM emp   INTERSECT SELECT ename, empno FROM emp;  Action:	Change the select lists so that they contain the same number of items.

PLS-00399	different types of columns in UNION, INTERSECT, or MINUS expression

 Cause:	The select lists to the left and right of a UNION, INTERSECT, or MINUS expression select at least one column that is mismatched in datatype. For example, the following statement is faulty because the constant 3 is of datatype NUMBER, whereas SYSDATE is of datatype DATE:

 CURSOR my_cur IS SELECT 3 FROM emp   INTERSECT SELECT SYSDATE FROM emp;  Action:	Change the select lists so that they match in datatype. You might want to use datatype conversion functions in the select list of one or more queries.

PLS-00400	different number of columns between cursor SELECT statement and return value

 Cause:	In a cursor declaration, you specified a return type (such as RETURN emp%ROWTYPE), but the number of returned column values does not match the number of select-list items.

 Action:	Change the cursor return type or the select list so that the number of returned column values matches the number of select-list items.

PLS-00401	different column types between cursor SELECT statement and return value found at 'name'

 Cause:	In a cursor declaration, you specified a return type (such as RETURN emp%ROWTYPE), but a returned column value and its corresponding select-list item belong to different datatypes.

 Action:	Change the cursor return type or the select list so that each returned column value and its corresponding select-list item belong to the same datatype.

PLS-00402	alias required in SELECT list of cursor to avoid duplicate column names

 Cause:	A cursor was declared with a SELECT statement that contains duplicate column names. Such references are ambiguous.

 Action:	Replace the duplicate column name in the select list with an alias.

PLS-00403	INTO list of FETCH statement contains illegal assignment target

 Cause:	A FETCH statement was unable to assign a value to an assignment target in its INTO list because the target is not a legally formed and declared variable. For example, the following assignment is illegal because 'Jones' is a character string, not a variable:

 FETCH my_cur INTO 'Jones';  Action:	Check your spelling and declaration of the assignment target. Check that you followed the rules for forming variable names.

PLS-00404	cursor 'name' must be declared with FOR UPDATE to use with CURRENT OF

 Cause:	The use of the CURRENT OF name clause is legal only if name was declared with a FOR UPDATE clause.

 Action:	Add a FOR UPDATE clause to the definition of the cursor or do not use the CURRENT OF 'name' clause.

PLS-00405	subquery not allowed in this context

 Cause:	A subquery was used in an inappropriate context, such as:

 if (SELECT deptno FROM emp WHERE ... ) = 20 then ... 	Subqueries are allowed only in SQL statements.

 Action:	You can get the same result by using a temporary variable, as in:

 SELECT deptno INTO temp_var FROM emp WHERE ...;IF temp_var = 20 THEN ... 	PLS-00406	length of SELECT list in subquery must match number of assignment targets

 Cause:	A query select list is not the same length as the list of targets that will receive the returned values. For example, the following statement is faulty because the subquery returns two values for one target:

 UPDATE emp SET ename =   (SELECT ename, empno FROM emp WHERE ename = 'SMITH') ...  Action:	Change one of the lists so that they contain the same number of items.

PLS-00407	'*' not allowed here; a list of columns is required

 Cause:	An asterisk (*) was used as an abbreviation for a list of column names. However, in this context the column names must be written out explicitly.

 Action:	Replace the asterisk with a list of column names.

PLS-00408	duplicate column 'name' not permitted in INSERT or UPDATE

 Cause:	An UPDATE or INSERT statement has a column list that contains duplicate column names.

 Action:	Check your spelling of the column names, then eliminate the duplication.

PLS-00409	duplicate variable 'name' in INTO list is not permitted

 Cause:	The same variable appears twice in the INTO list of a SELECT or FETCH statement.

 Action:	Remove one of the variables from the INTO clause.

PLS-00410	duplicate fields in record or table are not allowed

 Cause:	When declaring a user-defined record, you gave the same name to two fields. Like column names in a database table, field names in a user-defined record must be unique.

 Action:	Check your spelling of the field names, then remove the duplicate.

PLS-00411	number of values in aggregate and in subquery don't match

 Cause:	In a statement of the form <aggregate> <= or !=> <subquery>, the numbers of values in the aggregate and subquery are unequal. For example, you might have coded:

 ... WHERE (10,20,30) = (SELECT empno,deptno FROM emp WHERE...);  Action:	Revise the aggregate or subquery so that the numbers of values match.

PLS-00412	list of values not allowed as argument to this function or procedure

 Cause:	A parenthesized list of values separated by commas (that is, an aggregate) was used in the wrong context. For example, the following usage is invalid:

 WHERE (col1, col2) > (SELECT col3, col4 FROM my_table ...) 	However, an equal sign can take a list of values and a subquery as leftside and rightside arguments, respectively, so the following usage is valid:

 WHERE (col1, col2) = (SELECT col3, col4 FROM my_table ...)  Action:	Rewrite the expression. For example, the clause:

 WHERE (col1, col2) > (SELECT col3, col4 FROM my_table ...) 	can be rewritten as:

 WHERE col1 > (SELECT col3 FROM my_table ...) AND   col2 > (SELECT col4 FROM my_table ...) 	PLS-00413	identifier in CURRENT OF clause is not a cursor name

 Cause:	The identifier in a CURRENT OF clause names an object other than a cursor.

 Action:	Check your spelling of the identifier. Check that it names the cursor in the DELETE or UPDATE statement and that it names the cursor itself, not a FOR-loop variable.

PLS-00414	no column 'name' in table

 Cause:	A table name or alias was used to qualify a column reference, but the column was not found in that table. Either the column was never defined, or the column name is misspelled.

 Action:	Check that the column was defined and check your spelling of the column name.

PLS-00415	'name' is an OUT parameter and cannot appear in a function

 Cause:	When declaring the formal arguments of a function, you specified the OUT or IN OUT parameter mode. Procedures can take IN, OUT, and IN OUT parameters, but functions can take only IN arguments.

 Action:	Remove the OUT or IN OUT argument from the formal argument list or redefine the function as a procedure.

PLS-00417	table or view or column does not exist

 Cause:	A database table, view, or column that you specified in a SQL statement does not exist, or you lack the privileges needed to access the table or view.

 Action:	Check your spelling of the table (or view) and column names; check that the table and columns exist. If necessary, ask your DBA to grant the privileges needed to access the table.

PLS-00418	array bind type must match PL/SQL table row type

 Cause:	A host array was passed (by an Oracle Precompiler program, for example) to a PL/SQL subprogram for binding to a PL/SQL table parameter. However, the datatypes of the array elements and PL/SQL table rows are incompatible, so the binding failed.

 Action:	Change the datatype of the array elements or PL/SQL table rows to make the datatypes compatible.

 Cause:	You tried to reference a remote cursor attribute, which is not allowed. For example, you might have coded:

 IF SQL%NOTFOUND@newyork THEN ...  Action:	Do not try to reference a remote cursor attribute.

PLS-00419	reference to remote attribute not permitted

 Cause:	You tried to reference a remote cursor attribute, which is not allowed. For example, you might have coded:

 IF SQL%NOTFOUND@newyork THEN ...  Action:	Do not try to reference a remote cursor attribute.

PLS-00420	can't call built-in routines remotely

 Cause:	You tried to call a built-in PL/SQL function remotely, which is not allowed. For example, you might have coded:

 my_sqlerrm := SQLERRM@newyork; 	or:

 INSERT INTO emp VALUES (my_empno, STANDARD.RTRIM@newyork(my_ename), ...);  Action:	Always call built-in functions locally. Never specify a database link.

PLS-00421	synonym definitions nested too deeply; possible loop in synonyms

 Cause:	Directly or indirectly, you defined a synonym in terms of itself, creating a circular definition, or you defined a chain of synonyms too long for the PL/SQL compiler to handle.

 Action:	Redefine the synonyms to eliminate the circular definition. If necessary, shorten the chain of synonyms.

PLS-00422	no PL/SQL translation for the bind type given for this bind variable

 Cause:	A host variable was passed (by an Oracle Precompiler program, for example) to PL/SQL for binding. However, its datatype is not compatible with any PL/SQL datatype, so the binding failed.

 Action:	Change the datatype of the host variable to make it compatible with a PL/SQL datatype.

PLS-00424	all arguments must be provided in remote procedure call; no defaults

 Cause:	You tried to call a remote subprogram using defaulted parameters, which is not allowed. When calling remote subprograms, you must pass the actual parameters explicitly--even if the corresponding formal parameters have defaults.

 Action:	Call the remote subprogram by passing each actual parameter explicitly.

PLS-00428	an INTO clause is expected in this SELECT statement

 Cause:	You omitted the INTO clause of a SELECT INTO statement. For example, you might have coded:

 SELECT deptno, dname, loc FROM dept WHERE ... 	instead of:

 SELECT deptno, dname, loc INTO dept_rec FROM dept WHERE ... 	In PL/SQL, only a subquery is written without an INTO clause.

 Action:	Add the required INTO clause.

PLS-00450	a variable of this private type cannot be declared here

Not in Release 2.1.

PLS-00451	remote types not allowed

 Cause:	When declaring a constant or variable, you specified a datatype that is defined in a remote library unit. This is not allowed.

 Action:	Do not specify the datatype unless you define it locally first.

PLS-00452	subprogram 'name' violates its associated pragma

 Cause:	You cannot call a packaged function from SQL statements, unless you assert its purity level by coding a RESTRICT_REFERENCES pragma in the package specification. The pragma, which controls side effects, tells the PL/SQL compiler to deny the packaged function read/write access to database tables, public packaged variables, or both. If you code a SQL statement that violates the pragma, you get a compilation error.

 Action:	Raise the purity level of the function or relax the pragma restrictions.

PLS-00483	exception 'name' may appear in at most one exception handler in this block

 Cause:	An exception appears in two different WHEN clauses (that is, two different exception-handlers) in the exception-handling part of a PL/SQL block or subprogram.

 Action:	Remove one of the references to the exception.

PLS-00484	exceptions 'name' and 'name' have same Oracle error number and must appear in same exception handler

 Cause:	Using PRAGMA EXCEPTION_INIT, you initialized different exceptions to the same Oracle error number, then referred to them in different exception handlers within the same EXCEPTION section. Such references conflict.

 Action:	Remove one of the exceptions or initialize it to a different Oracle error number.

PLS-00485	in exception handler, 'name' must be an exception name

 Cause:	An identifier not declared as an exception appears in an exception handler WHEN clause. Only the name of an exception is valid in a WHEN clause.

 Action:	Check your spelling of the exception name and check that the exception was declared properly.

PLS-00486	SELECT list cannot be enclosed in parentheses

 Cause:	In a SELECT statement, the select list was enclosed in parentheses, as in:

 SELECT (deptno, dname, loc) FROM dept INTO ... 	This breaks the rules of SQL syntax. Parentheses are not needed because the keywords SELECT and FROM delimit the select list.

 Action:	Remove the parentheses enclosing the select list.

PLS-00487	invalid reference to variable 'name'

 Cause:	A variable was referenced in a way that is inconsistent with its datatype. For example, you might have mistakenly referenced a scalar variable as a record, as follows:

 DECLARE   CURSOR emp_cur IS SELECT empno, ename, sal FROM emp;   emp_rec  emp_cur%ROWTYPE;   my_sal   NUMBER(7,2);BEGIN    ...    total_sal := total_sal + my_sal.sal;  -- invalid   ...  Action:	Check your spelling of the variable name. Check that the variable was declared properly and that the declaration and reference are consistent with regard to datatype.

PLS-00488	invalid variable declaration:   object 'name' must be a type or subtype

 Cause:	The datatype specifier in a variable declaration does not designate a legal type. For example, you might have neglected to add the %TYPE attribute to a declaration, as in:

 DECLARE   my_sal    emp.sal%TYPE;   my_ename  emp.ename;    -- missing %TYPE   ... 	When declaring a constant or variable, to provide the datatype of a column automatically, you must use the %TYPE attribute. Likewise, you must use the %ROWTYPE attribute when declaring a record to provide the datatypes of a row automatically.

 Action:	Check that the datatype specifier designates a legal type. Remember to use the %TYPE and %ROWTYPE attributes when necessary.

PLS-00489	invalid table reference:   'name' must be a column in this expression

 Cause:	In a query, a select-list item refers to a table in the FROM clause but not to a database column.

 Action:	Check your spelling of the column names, check that each column in the select list refers to a table in the FROM clause, then re-execute the query.

PLS-00491	numeric literal required

 Cause:	You used a constant or variable where a numeric literal is required. For example, you might have coded:

 my_ename  VARCHAR2(max_len); 	instead of:

 my_ename  VARCHAR2(15); 	When specifying the maximum length of a VARCHAR2 variable, you must use an integer literal.

 Action:	Replace the identifier with a numeric literal.

PLS-00503	RETURN <value> statement required for this return from function

 Cause:	In a function body, you used a RETURN statement that contains no expression. In procedures, a RETURN statement contains no expression because the statement simply returns control to the caller. However, in functions, a RETURN statement must contain an expression because its value is assigned to the function identifier.

 Action:	Add an expression to the RETURN statement.

PLS-00504	type 'name'_BASE may not be used outside of package STANDARD

 Cause:	In a declaration, you mistakenly specified (for example) the datatype NUMBER_BASE. The datatypes CHAR_BASE, DATE_BASE, MLSLABEL_BASE, and NUMBER_BASE are for internal use only.

 Action:	Specify (for example) the datatype NUMBER instead of NUMBER_BASE.

PLS-00505	user-defined types may only be defined as PL/SQL tables or records

 Cause:	You tried to define a datatype derived from some base type other than RECORD or TABLE. User-defined types must be derived from the RECORD or TABLE type.

 Action:	Remove the faulty type definition or define a RECORD or TABLE type.

PLS-00506	user-defined constrained subtypes are disallowed

 Cause:	You tried to define a constrained subtype, but only unconstrained subtypes are allowed in this release of PL/SQL. For example, the following type definition is illegal:

 SUBTYPE Acronym IS VARCHAR2(5);  -- illegal 	However, future versions of PL/SQL will allow you to define constrained subtypes as well.

 Action:	Remove the illegal type constraint.

PLS-00507	PL/SQL tables may not be defined in terms of records or other tables

 Cause:	In a TABLE type definition, you mistakenly specified a composite datatype (RECORD or TABLE) for the column. The single, unnamed column must belong to a scalar datatype such as CHAR, DATE, or NUMBER.

 Action:	Remove the TABLE type definition or replace the composite datatype specifier with a scalar datatype specifier.

PLS-00700	PRAGMA EXCEPTION_INIT of 'name' must follow declaration of its exception in same block

 Cause:	A PRAGMA EXCEPTION_INIT was not declared in the same block as its exception. They must be declared in the proper order in the same block, with the PRAGMA EXCEPTION_INIT declaration following the exception declaration.

 Action:	Place the PRAGMA EXCEPTION_INIT declaration directly after the declaration of the exception referenced by the pragma.

PLS-00701	illegal Oracle error number num for PRAGMA EXCEPTION_INIT

 Cause:	The error number passed to a PRAGMA EXCEPTION_INIT was out of range. The error number must be in the range of -9999.. -1 (excluding -100) for Oracle errors or in the range of -20000.. -20999 for user-defined errors.

 Action:	Use a valid error number.

PLS-00702	second argument to PRAGMA EXCEPTION_INIT must be a numeric literal

 Cause:	The second argument passed to a PRAGMA EXCEPTION_INIT was something other than a numeric literal (a variable, for example). The second argument must be a numeric literal in the range of -9999.. -1 (excluding -100) for Oracle errors or in the range of -20000.. -20999 for user-defined errors.

 Action:	Replace the second argument with a valid error number.

PLS-00703	multiple instances of named argument in list

 Cause:	Two or more actual parameters in a subprogram call refer to the same formal parameter.

 Action:	Remove the duplicate actual parameter.

PLS-00704	'name' must be declared as an exception

 Cause:	The exception_name parameter passed to PRAGMA EXCEPTION_INIT does not refer to a legally-declared exception or the pragma itself is misplaced. The pragma must appear later in the same declarative section as the exception declaration.

 Action:	Check your spelling of the exception_name parameter. Then, check the exception declaration, making sure the exception name and the keyword EXCEPTION are spelled correctly. Also check that the pragma appears in the same declarative section somewhere after the exception declaration.

PLS-00705	exceptions not allowed in an expression

 Cause:	You mistakenly referred to an exception within an expression. Exceptions have names but not values and therefore cannot contribute values to an expression. For example, the following RETURN statement is illegal:

 FUNCTION credit_limit (cust_no INTEGER) RETURN NUMBER IS   limit       NUMBER;   over_limit  EXCEPTION;   ...BEGIN   ...   RETURN over_limit;  -- illegalEND;  Action:	Check your spelling of the identifiers in the expression, then rewrite the expression so that it does not refer to an exception.

PLS-00706	exception 'name' cannot be used as prefix of a selected component

 Cause:	You mistakenly used an exception name to quality a reference to a component. For example, when using dot notation to specify fields within a record, you might have coded an exception name instead of the record name.

 Action:	Rewrite the component reference using a valid prefix (for example, the name of a package, record, or schema).

PLS-00900	can't find body of unit 'name'

 Cause:	At runtime, the body of a program unit could not be found. This happens, for example, if you reference a procedure for which a specification but no body exists. (No compile-time errors were generated because the specification exists.)

 Action:	Define a body for the program unit.

PLS-00901	the datatype of column 'name' of table 'name' is not supported

 Cause:	A column in a database table belongs to a datatype that is not supported by the current release of PL/SQL.

 Action:	Remove the offending column from the table or copy the desired columns to another table.

PLS-00902	a read-only bind variable used in OUT or IN OUT context

 Cause:	A host variable that is protected from update was used in a context that allows an update.

 Action:	Check the context and change your use of the host variable, or assign the value of the host variable to a PL/SQL local variable, then use the local variable instead.

PLS-00904	insufficient privilege to access object 'name'

 Cause:	You tried to operate on a database object without the required privilege. This error occurs, for example, if you try to UPDATE a table for which you have only SELECT privileges.

 Action:	Ask your DBA to perform the operation or to grant you the required privilege.

PLS-00905	object 'name' is invalid

 Cause:	You referenced an invalid package specification or stored subprogram. A package specification or stored subprogram is invalid if its source code or any database object it references has been DROPped, REPLACEd, or ALTERed since it was last compiled.

 Action:	Find out what invalidated the package specification or stored subprogram, then check that Oracle can recompile it without errors.

PLS-00995	unhandled exception # 'num'

 Cause:	An exception was raised for which no handler was found. If it cannot find a handler for a raised exception, PL/SQL returns an unhandled exception to the host environment. The number embedded in the message is an Oracle error code listed in Chapter 2, "Oracle7 Server Messages", of this Manual.

 Action:	Fix the condition that raised the exception, write an appropriate exception handler, or use the OTHERS handler. If there is an appropriate handler in the current block, the exception was raised in a declaration or exception handler. An exception raised in a declaration or exception handler propagates immediately to the enclosing block. You can avoid unhandled exceptions by coding an OTHERS handler at the topmost level of every PL/SQL block and subprogram.

PLS-00996	out of memory

 Cause:	A request from PL/SQL for more memory failed.

 Action:	Check that you are not referencing the wrong row in a PL/SQL table and that your program is not recursing too deeply.

 ________________________________________

01400-01799: FIPS Warnings

This section lists the warnings that can be generated when the FIPS flagger is set in an Oracle product and an Oracle extension to the SQL92 standard is used or a SQL92 feature is used in a nonconforming manner. FIPS warnings messages are listed for completeness. The cause and actions are described in the ANSI document ANSI X3.135-1992. The Oracle products that can generate FIPS warning messages are SQL*DBA, Server Manager, SQL*Plus, Oracle precompilers, and so on.

PLS-01400	Use of '||' token

PLS-01401	Identifier over 18 characters long

PLS-01402	Use of quoted identifier

PLS-01403	Comment delimiters /* */

PLS-01404	ANSI Identifiers can only consist of letters, digits, and the underscore character

PLS-01405	Under ANSI's grammar, numeric data represented in exponent notation must use an uppercase E

PLS-01406	An identifier has been found that is considered a keyword in ANSI's grammar but not in PL/SQL's

PLS-01407	One of the identifiers CHAR, CHARACTER, or INTEGER has been redefined by the programmer

PLS-01408	Use of '&' token

PLS-01409	Use of 'PRIOR_' token

PLS-01410	Use of 'MOD' token

PLS-01411	Use of 'REM' token

PLS-01412	Use of 'EXP' token

PLS-01413	Use of NULL an expression

PLS-01414	Use of qualified expression here

PLS-01415	Use of aggregate value here

PLS-01416	Use of <id> (<value>...) here

PLS-01417	Use of %attribute

PLS-01418	Subquery cannot include set operators in ANSI's grammar

PLS-01419	Subquery must have either '*' or exactly one column in its select list

PLS-01420	INTERSECT and MINUS set operators are not ANSI

PLS-01421	FOR UPDATE clause

PLS-01422	Aliases

PLS-01423	Subquery on right-hand-side in set clause

PLS-01424	Non-ANSI order of clauses

PLS-01425	Connect-by clause

PLS-01450	This <value expression> contains a nonconforming data type

PLS-01451	The data types of these <value expressions> must be comparable

PLS-01452	This function is not part of the ANSI standard

PLS-01453	This procedure is not part of the ANSI standard

PLS-01454	No operator may be used with values of data type CHAR

PLS-01455	The predicates IS NULL and IS NOT NULL are defined only for column specifications

PLS-01456	Name length cannot exceed 3.

PLS-01458	The set clause in an UPDATE statement requires a column name of length 1

PLS-01460	Cannot access object on a remote host

PLS-01463	STDDEV is not a standard set function

PLS-01464	VARIANCE is not a standard set function

PLS-01466	Null strings are not allowed

PLS-01467	The value list of the IN predicate, if not a subquery, must contain only value_specifications

PLS-01468	The first argument of the like-predicate must be a column of type character string

PLS-01469	ANSI standard does not permit records

PLS-01470	The escape character in the like-predicate must be a literal or a variable of type CHAR

PLS-01471	The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr)

PLS-01472	In a set_function_specification, if DISTINCT is present, the expression must be a column_specification

PLS-01473	Use <> instead of != or ~=

PLS-01474	Use of ANY is non_ANSI

PLS-01500	Unions are not allowed in the definition of a view

PLS-01501	Options in CREATE TABLE statement is non-ANSI.

PLS-01502	Constraint name and constraint status are non-ANSI.

PLS-01503	The expression in a SET clause must not include a set function

PLS-01504	Use of AS phase in CREATE TABLE statement is non_ANSI

PLS-01505	ALTER is non-ANSI

PLS-01506	CREATE INDEX is non-ANSI

PLS-01507	DROP is non-ANSI

PLS-01701	Illegal syntax in ROLLBACK WORK statement

PLS-01702	Illegal syntax in COMMIT WORK statement

PLS-01703	Cursor name in CLOSE statment must be of length 1

PLS-01704	The expressions in a sort clause must be column specs or unsigned integers, with optional ASC or DESC

PLS-01705	table specified by a cursor not updatable if cursor specification has a UNION or ORDER_BY

PLS-01707	In positioned DELETE or UPDATE statement, table must be identified in specification of cursor

PLS-01708	In searched DELETE, UPDATE or INSERT, table must not appear in FROM clause of subqueries in search condition

PLS-01709	value list of INSERT statement, if specified with value list rather than subquery, must be value specification

PLS-01710	In a positioned DELETE or UPDATE statement, the cursor name must be of length 1

PLS-01711	A SELECT statement may not contain ORDER_BY, HAVING, or GROUP_BY clause

PLS-01712	ANSI does not allow bind variables as INDICATORS

PLS-01713	The constraints on these types do not match

PLS-01714	ANSI expects a column name not a literal value here

PLS-01715	ANSI does not accept SAVEPOINTs


CHAPTER 4. PRECOMPILER MESSAGES

This chapter lists messages you might see when running the Oracle Precompilers. Also listed are messages that the Oracle runtime library might return to the SQLCA. For each message, the probable cause and corrective action are given. The Oracle Precompilers issue various warning and error messages. For example, you might see the following message code and message text:

PCC-U-0036: No input file name specified

The message code consists of a prefix, severity code, and sequence number. The prefix PCC shows that the message was generated by an Oracle Precompiler. There are four severity codes. The following table gives their meanings:

Code	Meaning

W	Warning--despite an error, a compilable output file was

created.

S	Severe error--despite an error, an output file was created.

However, it might not be compilable.

F	Fatal error--no output file was created because of an internal

problem or because a resource (such as memory) was un-

available or ran out.

U	Unrecoverable error--no output file was created because an

input requirement was not met.

 ________________________________________

00001-01600: PCC Messages

PCC-00001	Unable to open file name

 Cause:	The precompiler was unable to open a temporary file for internal use. There might be insufficient disk space, too many open files, or read-only protection on the output directory.

 Action:	Check that there is enough disk space, that the limit for open files is set high enough (check with your system manager) and that protection on the directory allows opening a file for writing.

PCC-00002	Invalid syntax at column name in line num of file name

 Cause:	There is a syntax error in an EXEC statement or the statement is not properly terminated.

 Action:	Correct the syntax of the EXEC statement. If the error occurred at the end of the input file, check that the last EXEC statement is properly terminated.

PCC-00003	Invalid SQL Identifier at column name in line num of file name

 Cause:	The symbol in a conditional precompilation statement (such as EXEC Oracle IFDEF) is invalid, or the name of a SQL descriptor, statement, or cursor is invalid or was not properly declared.

 Action:	Check the statement syntax and your spelling of the identifier and check that you did not use a reserved word. If necessary, define the identifier in a variable declaration or DECLARE statement ahead of the line in error.

PCC-00004	Mismatched IF/ELSE/ENDIF block at line num in file name

 Cause:	There is an EXEC Oracle ELSE or EXEC Oracle ENDIF statement without a matching EXEC Oracle IFDEF statement.

 Action:	Add the missing EXEC Oracle IFDEF statement or delete or move the EXEC Oracle ELSE or EXEC Oracle ENDIF statement.

PCC-00005	Unsupported datatype in line num of file name

 Cause:	A host variable defined in the Declare Section has an unsupported datatype or has a scale or precision outside the supported range.

 Action:	Redefine the host variable using a supported datatype. Check that the scale and precision of a numeric variable are in the accepted range.

PCC-00007	Invalid WHENEVER condition at column name in line num of file name

 Cause:	A condition other than SQLERROR, SQLWARNING, or NOT FOUND was specified in an EXEC SQL WHENEVER statement, or one of these was used but spelled incorrectly.

 Action:	Correct the spelling of the WHENEVER condition or use a host-language IF statement to test the special condition.

PCC-00008	Invalid WHENEVER action at column name in line num of file name

 Cause:	At least one of the following:

•	An action other than CONTINUE, GOTO, or STOP was specified in an EXEC SQL WHENEVER statement.

•	One of the specified actions was spelled incorrectly.

•	The host language does not allow the action (STOP is illegal in Pro*Pascal programs).

•	A GOTO label is invalid.

 Action:	Check that your host language allows the specified WHENEVER action. If necessary, correct the spelling of the WHENEVER action or correct the GOTO label.

PCC-00009	Invalid host variable at column name in line num of file name

 Cause:	A host variable used in an EXEC SQL statement was not declared in the Declare Section or has an unsupported datatype.

 Action:	Declare the host variable in the Declare Section, making sure it has one of the supported datatypes.

PCC-00010	Statement out of place at line num in file name

 Cause:	An EXEC statement was not placed properly in the host program. For example, there might be a data manipulation statement in the Declare Section. In a Pro*COBOL program, the Declare Section might be outside the WORKING-STORAGE SECTION.

 Action:	Remove or relocate the statement.

PCC-00011	Already in a Declare Section at line num in file name

 Cause:	A BEGIN DECLARE SECTION statement was found inside a Declare Section.

 Action:	Remove the extra BEGIN DECLARE SECTION statement.

PCC-00012	Not in a Declare Section at line num in file name

 Cause:	An END DECLARE SECTION statement without a matching BEGIN DECLARE SECTION statement was found. Either the BEGIN DECLARE SECTION statement is missing or misspelled or the END DECLARE SECTION statement is an extra.

 Action:	Add or correct the BEGIN DECLARE SECTION statement or remove the extra END DECLARE SECTION statement.

PCC-00013	Unable to open INCLUDE file name at line num in file name

 Cause:	The precompiler was unable to open the input file specified in the INCLUDE statement. Some possible causes follow:

•	The filename is misspelled.

•	The file does not exist.

•	The search path to the file is incorrect.

•	You have insufficient file access privileges.

•	Another user has locked the file.

•	There is not enough disk space.

•	There are too many open files.

 Action:	Check that the file exists, that the search path to the file is correct, that you have sufficient privileges to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with your system manager).

PCC-00014	Undeclared SQL identifier ident at line num in file name

 Cause:	The name of a descriptor, statement, or cursor was not declared or is misspelled.

 Action:	Add or correct the descriptor, statement, or cursor declaration.

PCC-00015	Unrecognized host language syntax ignored at line num in file name

 Cause:	The host language syntax used to define a host variable in the Declare Section is incorrect.

 Action:	Check the syntax and your spelling, then correct the declaration.

PCC-00016	Unable to open a cursor at line num in file name

 Cause:	The syntax in a SQL statement is faulty. The precompiler was expecting a host variable but found something else.

 Action:	Check the syntax and your spelling, then correct the SQL statement.

PCC-00017	Unable to parse statement at line num in file name

 Cause:	There is a syntax error in an array declaration. The precompiler was expecting a right bracket (]) but found something else.

 Action:	Check the syntax, then correct the array declaration.

PCC-00018	Expected token, but found token at line num in file name

 Cause:	The syntax in a SQL statement is faulty. The precompiler found an unexpected or illegal token.

 Action:	Check the syntax and your spelling, then correct the SQL statement.

PCC-00019	Unable to obtain bind variables at line num in file name

 Cause:	The precompiler was unable to find information about an input host variable (bind variable) used in a SQL statement.

 Action:	Check that the input host variable is declared in the Declare Section and used properly in the SQL statement.

PCC-00020	Unable to obtain define variables at line num in file name

 Cause:	The precompiler was unable to find information about an output host variable (define variable) used in a SQL statement.

 Action:	Check that the output host variable is declared in the Declare Section and used properly in the SQL statement.

PCC-00021	Oracle Error: ora-nnnnn

 Cause:	An Oracle error occurred.

 Action:	Look up the message in Chapter 2, "Oracle7 Server Messages", of this Manual.

PCC-00022	Out of space - unable to allocate num bytes

 Cause:	The precompiler process ran out of memory.

 Action:	Allocate more memory to the process, then retry.

PCC-00023	Unable to log off Oracle

 Cause:	An Oracle connection error occurred while the precompiler was trying to log off, probably because Oracle has been shut down.

 Action:	Check that Oracle is available, then retry.

PCC-00024	Indicator variable var has wrong type or length at line num in file name

 Cause:	An indicator variable was not declared in the Declare Section as a 2-byte integer. Indicator variables must be defined as 2-byte integers.

 Action:	Redefine the indicator variable as a 2-byte integer.

PCC-00025	Undeclared indicator variable var at line num in file name

 Cause:	An indicator variable used in a SQL statement was not declared in the Declare Section or its name is misspelled.

 Action:	Add or correct the indicator variable declaration.

PCC-00026	Invalid host variable vat at line num in file name

 Cause:	A host variable used in a SQL statement was not declared properly. Some possible causes follow:

•	It was not declared in the Declare Section.

•	Its datatype is not supported.

•	Its name is misspelled.

•	It is a COBOL group item; in Pro*COBOL, only elementary items are allowed in a SQL statement.

 Action:	Add or correct the host variable declaration.

PCC-00027	Redeclared SQL identifier ident at line num in file name

 Cause:	The name of a SQL descriptor, statement, or cursor was redeclared (that is, declared twice).

 Action:	Check your spelling of the identifier, then, if necessary, remove the extra declaration.

PCC-00028	Option optnam not legal as EXEC Oracle OPTION

 Cause:	A precompiler option was specified inline in an EXEC Oracle statement, instead of on the command line. Some options can be specified only on the command line. For example, you cannot specify INAME inline.

 Action:	Respecify the precompiler option on the command line, instead of in an EXEC Oracle statement. To see an online display of the precompiler options, enter the precompiler command (with no options) at your operating-system prompt.

PCC-00029	Ambiguous option optnam

 Cause:	The name of a precompiler option was abbreviated ambiguously. For example, MAX= might refer to MAXLITERAL or MAXOPENCURSORS.

 Action:	Respecify the full option name or an unambiguous abbreviation. To see an online display of the precompiler options, enter the precompiler command (with no options) at your operating-system prompt.

PCC-00031	Invalid value given for option optnam

 Cause:	The value specified for a precompiler option is invalid, probably because the value is misspelled (as in LTYPE=HORT) or out of range (as in PAGELEN=-55).

 Action:	Check the value, making sure it is spelled correctly and within the legal range.

PCC-00032	Invalid option optnam

 Cause:	The precompiler found an invalid precompiler option name. Some possible causes follow:

•	The option name is misspelled.

•	The specified option does not exist.

•	The equal sign (=) between the option name and value is missing or has space around it.

•	The name of the input file was not preceded by INAME=.

 Action:	Check that the option exits and that its name is spelled correctly. To see an online display of the precompiler options, enter the precompiler command (with no options) at your operating-system prompt. Also check that there is an equal sign between the option name and value.

PCC-00033	Missing operand for option optnam

 Cause:	No value was specified for a precompiler option. Either the value is missing or there is space around the equal sign (as in LTYPE   =SHORT).

 Action:	Check that you specify a value for each option and that there is no space around the equal sign.

PCC-00035	No host language specified

 Cause:	The precompiler was unable to determine the host language of the input file. If you use a non-standard input file extension when specifying the INAME precompiler option, you must also specify the HOST option. However, most operating systems are set up to prevent this error (by automatically specifying the HOST option when a precompiler is invoked).

 Action:	Either add the standard input file extension or specify the HOST option. If your operating system is supposed to prevent this error, call customer support for assistance.

PCC-00036	No input file name specified

 Cause:	The input file was not specified on the command line.

 Action:	Use the INAME command-line option to specify the input file.

PCC-00037	Unable to log on to Oracle with username. Oracle error number: ora-nnnnn

 Cause:	The precompiler was unable to log on to Oracle with the specified username and password. An Oracle error with given number occurred when the logon was attempted.

 Action:	Look up the message in Chapter 2, "Oracle7 Server Messages", of this Manual.

PCC-00038	Unable to open a cursor

 Cause:	This is an internal error message not usually issued.

 Action:	Call customer support for assistance. If your application does not require syntactic or semantic checking of SQL statements and does not use PL/SQL, specify SQLCHECK=NONE on the command line.

PCC-00039	Unable to open input file name

 Cause:	The precompiler was unable to open the input file specified by the INAME precompiler option. Some possible causes follow:

•	The filename is misspelled.

•	The file does not exist.

•	The search path to the file is incorrect.

•	You have insufficient file access privileges.

•	Another user has locked the file.

•	There is not enough disk space.

•	There are too many open files.

 Action:	Check that the file exists, that the search path to the file is correct, that you have sufficient privileges to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with your system manager).

PCC-00040	Unable to open listing file name

 Cause:	The precompiler was unable to open the listing file specified by the LNAME precompiler option. Some possible causes follow:

•	The filename is misspelled.

•	The file does not exist.

•	The search path to the file is incorrect.

•	You have insufficient file access privileges.

•	Another user has locked the file.

•	There is not enough disk space.

•	There are too many open files.

 Action:	Check that the file exists, that the search path to the file is correct, that you have sufficient privileges to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with your system manager). If you do not need a listing file, specify LTYPE=NONE on the command line.

PCC-00041	Unable to open output file name

 Cause:	The precompiler was unable to open the output file specified by the ONAME precompiler option. Some possible causes follow:

•	The filename is misspelled.

•	The file does not exist.

•	The search path to the file is incorrect.

•	You have insufficient file access privileges.

•	Another user has locked the file.

•	There is not enough disk space.

•	There are too many open files.

 Action:	Check that the file exists, that the search path to the file is correct, that you have sufficient privileges to access the file, and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with your system manager).

PCC-00042	Must include SQLCA file when MODE=ANSI and WHENEVER SQLWARNING used

 Cause:	When MODE={ANSI | ANSI14}, you tried to use the WHENEVER SQLWARNING statement without declaring the SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the WHENEVER SQLWARNING statement, you must declare the SQLCA.

 Action:	Remove all WHENEVER SQLWARNING statements from your program or declare the SQLCA by hardcoding it or copying it into your program with the INCLUDE statement.

PCC-00044	Array size mismatch in INTO/USING. Minimum is: min (num:num)

 Cause:	The size of an array variable in an INTO/USING clause is too small for the number of rows processed.

 Action:	Declare all array variables in the INTO/USING clause to have at least the minimum dimension given.

PCC-00045	clause_name clause inappropriate at line num in file name. Ignored

 Cause:	There is a misplaced clause at the end of an EXEC SQL statement (an AT clause at the end of a SELECT statement, for example), or the action specified in a FOR clause is invalid (for example, FOR:loop INTO...).

 Action:	Check the statement syntax, then relocate or correct the misplaced or invalid clause.

PCC-00047	Unterminated comment/string constant beginning near line num in file name

 Cause:	A string constant is missing an ending quotation mark, or a comment is missing an ending delimiter.

 Action:	Check that all comments are delimited and all string constants are enclosed by quotation marks.

PCC-00048	Pro* configured without Oracle. INLINE=NO ignored

 Cause:	Currently the Oracle Precompilers generate inline code, not access modules. Thus, the INLINE=NO command-line option is ignored. However, future versions of the Oracle Precompilers will be able to generate access modules.

 Action:	Do not specify the INLINE option.

PCC-00050	Unable to generate descriptor in program unit ending line num in file name

 Cause:	Part of a descriptor was generated incorrectly, or the precompiler was unable to generate a descriptor in a program unit terminated by an end-of-file.

 Action:	Call customer support for assistance.

PCC-00051	Size of VARCHAR hostvar at num is larger than 65533 at line num in file name

 Cause:	The declared size of a VARCHAR host variable exceeds the precompiler limit of 65533 bytes.

 Action:	Check the Declare Section, making sure the size of each VARCHAR variable does not exceed 65533 bytes.

PCC-00053	FOR variable var is invalid type at line num in file name

 Cause:	The count variable in a FOR clause has the wrong datatype. The datatype must be NUMBER or LONG (or be compatible with NUMBER or LONG).

 Action:	Check the declaration and check that the count variable has a datatype of NUMBER or LONG (or a compatible Oracle or host-language datatype).

PCC-00054	Expected end-of-statement at column name in line num of file name

 Cause:	The precompiler expected to find a statement terminator at the end of an EXEC statement but found something else. This can happen if you embed tabs in your source code (because the precompiler has no way of knowing how many spaces a tab represents).

 Action:	If you find tabs embedded in the source code, replace them with spaces. Check the statement syntax and check that each EXEC statement has a terminator. For embedded CREATE {FUNCTION | PROCEDURE | PACKAGE} statements and for embedded PL/SQL blocks, check that the statement terminator is END-EXEC.

 Action:	Correct or remove the erroneous CREATE statement.

PCC-00055	Array "name" not allowed as bind variable at line num in file name

 Cause:	A host array was used as a bind (input) variable in the WHERE clause of a SELECT statement. This is not allowed.

 Action:	Remove the host array or replace the it with a simple host variable.

PCC-00056	FOR clause not allowed in SELECT statement at line num in file name

 Cause:	This message warns that the FOR :loop SELECT... construct will eventually be disallowed.

 Action:	Keep in mind that, eventually, code containing this construct will have to be modified.

PCC-00060	Both CURSOR and STATEMENT have AT clauses at line num of file name

 Cause:	Two AT clauses, one in a DECLARE STATEMENT statement, the other in a DECLARE CURSOR statement, pertain to the same SQL statement. You can specify the AT clause with either DECLARE STATEMENT or DECLARE CURSOR but not with both.

 Action:	Remove the AT clause from one of the statements.

PCC-00061	Error at line num, column name. PLS-N: PLS-nnnnn

 Cause:	The precompiler found a syntax error while parsing an embedded SQL statement or PL/SQL block. If the error was found in a PL/SQL block, the PL/SQL error message code and text are given.

 Action:	Correct the syntax and, if necessary, lookup up the PL/SQL message in Chapter 3, "PL/SQL Messages", of this Manual.

PCC-00062	Must use option SQLCHECK=SEMANTICS when there is embedded PL/SQL

 Cause:	The precompiler tried to parse an embedded PL/SQL block when SQLCHECK={SYNTAX | NONE}. PL/SQL blocks can be parsed only when you specify SQLCHECK=SEMANTICS.

 Action:	Remove the PL/SQL block or specify SQLCHECK=SEMANTICS.

PCC-00063	Reached end of file name before end-of-statement at line num

 Action:	The precompiler encountered an end-of-file while parsing a PL/SQL block.

 Action:	Add the appropriate statement terminator (;) or end-of-block statement (END;) to the PL/SQL block.

PCC-00064	All uses of a given host variable must use identical indicator variables

 Cause:	Two or more occurrences of a host variable in an EXEC SQL statement are associated with different indicator variables. This is not allowed.

 Action:	Rename the indicator variables so that each occurrence of the host variable is associated with the same indicator variable.

PCC-00065	USERID required, but not specified

 Cause:	You specified the SQLCHECK=SEMANTICS option, but failed to specify the USERID option on the command line.

 Action:	Specify USERID=username/password or enter a username and password when prompted or specify SQLCHECK={SYNTAX | NONE}.

PCC-00066	USERID only used when SQLCHECK=SEMANTICS, USERID ignored

 Cause:	You specified the USERID option when SQLCHECK={SYNTAX | NONE}. This is unnecessary.

 Action:	Specify the USERID option only when SQLCHECK=SEMANTICS.

PCC-00067	IRECLEN exceeded. Line num in file name truncated

 Cause:	While reading the input file, the precompiler found a line longer than IRECLEN.

 Action:	Either shorten the input line or specify a larger IRECLEN value on the command line.

PCC-00068	Host and indicator variables may not have the same name

 Cause:	In an EXEC SQL statement, an indicator variable has the same name as a host variable. The names of a host variable and its associated indicator variable must be different. Also, an indicator variable cannot be used as a host variable.

 Action:	Rename the host or indicator variable.

PCC-00069	Host variable var has unsupported datatype at line num in file name

 Cause:	A host variable has an unsupported datatype. For a list of supported datatypes, see your language-specific supplement to the Programmer's Guide to the Oracle Precompilers.

 Action:	Redefine the host variable in the Declare Section, giving it a supported datatype.

PCC-00070	Illegal syntax. Exponential value in SQL statement: text

 Cause:	The precompiler found a syntax error while parsing a number coded in scientific notation. The precompiler expected to find a signed integer following the exponentiation indicator (E), but found something else.

 Action:	Reformat the number correctly.

PCC-00072	Input file name length exceeds 14 characters

 Cause:	On some operating systems, the maximum length of a filename is 14 characters. The filename you specified exceeds the maximum length.

 Action:	Use a filename of 14 or fewer characters.

PCC-00073	Cursor is declared but never OPENed at line num in file name

 Cause:	You DECLAREd a cursor but did not code an OPEN statement for it. This is only an informational message.

 Action:	Remove the cursor declaration or code an OPEN statement for the cursor.

PCC-00074	FIPS warning: Multiply defined host variable in line num of file name

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, you reused the name of a global host variable to declare a local host variable. This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not reuse the names of global host variables to declare local host variables.

PCC-00075	":" expected before indicator variable

 Cause:	An indicator variable is not prefixed with a colon as required.

 Action:	Prefix a colon to the indicator variable in question.

PCC-00076	DISPLAY type must be SIGN LEADING SEPARATE

 Cause:	This message is usually issued only by Pro*COBOL. DISPLAY SIGN LEADING SEPARATE is the only DISPLAY type supported by Pro*COBOL.

 Action:	Check your spelling of the variable declaration. If necessary, remove the reference to the unsupported DISPLAY type.

PCC-00077	Colon usage with numeric label in WHENEVER statement is not ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a numeric WHENEVER... GOTO label was prefixed with a colon. For example, you might have coded

 EXEC SQL WHENEVER SQLERROR GOTO :99;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, prefix alphanumeric (but not numeric) WHENEVER... GOTO labels with a colon.

PCC-00078	FIPS warning: Invalid ANSI SQL identifier

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the name you gave to a host variable:

•	is longer than 18 characters,

•	does not begin with a letter, or

•	contains consecutive or trailing underscores

In the following Pro*C example, the host variable name is 19 characters long and therefore non-compliant:

 EXEC SQL BEGIN DECLARE SECTION;     int  department_location;  -- not ANSI/ISO-compliant     ... EXEC SQL END DECLARE SECTION;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, change the host variable name so that it is <18 characters long, begins with a letter, and does not contain consecutive or trailing underscores.

PCC-00079	ANSI requires colon on label in WHENEVER statement

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, an alphanumeric WHENEVER... GOTO label was not prefixed with a colon. For example, you might have coded

 EXEC SQL WHENEVER NOT FOUND GOTO no_more;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, prefix alphanumeric (but not numeric) WHENEVER... GOTO labels with a colon.

PCC-00080	TYPE identifier already TYPEd

 Cause:	The identifier being TYPEd in an EXEC SQL TYPE statement appeared in a previous EXEC SQL TYPE statement. A given identifier can appear in only one EXEC SQL TYPE statement.

 Action:	Check your spelling of the identifiers. Use different identifiers in the EXEC SQL TYPE statements, or remove one of the EXEC SQL TYPE statements.

PCC-00081	Scale specification not allowed for given datatype

 Cause:	The Oracle external datatype referenced in an EXEC SQL VAR or EXEC SQL TYPE statement does not allow a scale specification.

 Action:	Check the precision specification and remove the scale specification.

PCC-00082	Length and scale specifications must be an integer

 Cause:	You used a floating point number or a non-number to specify a length or scale. Only integers can be used.

 Action:	Correct or remove the length and/or scale specification.

PCC-00083	Bind and define variables not allowed in CREATE statement

 Cause:	Host variables cannot appear in a CREATE statement. If the makeup of a CREATE statement cannot be known until run time, you must use dynamic SQL to execute it. That is, your program must accept or build the CREATE statement at run time, store it in a host string, then EXECUTE it.

 Action:	Correct or remove the erroneous CREATE statement.

PCC-00085	Error writing to file name

 Cause:	The precompiler was unable to write to the named output file. Some possible causes follow:

•	You have insufficient file access privileges.

•	Another user has locked the file.

•	There is not enough disk space.

•	There are too many open files.

 Action:	Check that you have sufficient privileges to access the file and that it is not locked by another user. Also check that there is enough disk space and that the limit for open files is set high enough (check with your system manager).

PCC-00086	Source file name has zero length

 Cause:	The source file you specified on the command line contains no code. Consequently, there is nothing for the precompiler to process.

 Action:	Specify a valid source file containing embedded SQL statements.

PCC-00087	EXEC SQL TYPE statement not allowed for this host language

 Cause:	You used the EXEC SQL TYPE statement with a host language that does not support user-defined datatype equivalencing. This feature is available only in Pro*C and Pro*Pascal.

 Action:	Remove the offending EXEC SQL TYPE statement.

PCC-00088	User-defined type identifier expected

 Cause:	The user-defined datatype name in an EXEC SQL TYPE statement is missing or misspelled, is a reserved word, is not a legal identifier in your host language or conflicts with a base datatype in that language.

 Action:	Check your spelling of the user-defined datatype name. If necessary, declare a valid user-defined datatype. User-defined datatype equivalencing is available only in Pro*C and Pro*Pascal.

PCC-00089	Invalid Oracle TYPE specification

 Cause:	The Oracle external datatype name in an EXEC SQL TYPE or EXEC SQL VAR statement is missing or misspelled.

 Action:	Check your spelling of the external datatype name. If necessary, supply the missing datatype name.

PCC-00090	Precision/scale specification must be given for DECIMAL datatype

 Cause:	You omitted a precision and/or scale specification for the Oracle external datatype DECIMAL in an EXEC SQL TYPE or EXEC SQL VAR statement.

 Action:	Add the precision and/or scale specification to the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00091	TYPE statement requires format specification for this Oracle datatype

 Cause:	You omitted a length, precision, and/or scale specification for an Oracle external datatype in an EXEC SQL TYPE or EXEC SQL VAR statement.

 Action:	Add the length, precision, and/or scale specification for the external datatype to the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00092	Length and/or scale incompatible with specified Oracle datatype

 Cause:	You specified an invalid length or scale for an Oracle external datatype in an EXEC SQL TYPE or EXEC SQL VAR statement.

 Action:	Check that you specify a length large enough to accommodate the external datatype. If you specify a scale, check that it lies in the range -84.. 99.

PCC-00093	Invalid or obsolete option, ignored

 Cause:	The precompiler found an option available in a prior version or different host language but not in your version or host language.

 Action:	Remove the option specification.

PCC-00094	Array length for char[n] datatype must be => 2

 Cause:	When MODE={ANSI | ANSI14}, you specified a length of less than 2 characters for a char[n] host variable. When MODE={ANSI | ANSI14}, the length must be at least 2 characters. This message is issued only by the Pro*C Precompiler.

 Action:	Correct the declaration so that it specifies a length of at least 2 characters.

PCC-00095	Missing PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement

 Cause:	FORTRAN source files are expected to have at least one PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement, which the precompiler uses to detect the beginning of a routine or compilation unit.

 Action:	Add one of these statements to the source file.

PCC-00096	Array FETCH not allowed for MODE=ANSI14

 Cause:	When MODE=ANSI14, you attempted an array SELECT or FETCH. However, array operations are not allowed when MODE=ANSI14.

 Action:	If you must specify MODE=ANSI14, place the SELECT or FETCH statement in a host-language loop, instead of using the array interface.

PCC-00097	Use of DECIMAL and DISPLAY types allowed only for COBOL and PLI

 Cause:	You used the DECIMAL or DISPLAY external datatype in an EXEC SQL VAR statement with an Oracle Precompiler other than Pro*COBOL or Pro*PL/I. These external datatypes are available only in Pro*COBOL and Pro*PL/I.

 Action:	Remove the reference to the DECIMAL or DISPLAY external datatype from the EXEC SQL VAR statement.

PCC-00098	Scale specification cannot be used in this context

 Cause:	In a Pro*C, Pro*FORTRAN, or Pro*Pascal program, you cannot specify scale in an EXEC SQL TYPE or EXEC SQL VAR statement in the current context.

 Action:	Remove the scale specification from the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00099	Length cannot be given for types ROWID, DATE, or MLSLABEL

 Cause:	You specified a length for the ROWID, DATE, or MLSLABEL external datatype in an EXEC SQL TYPE or EXEC SQL VAR statement. This is unnecessary because those are fixed-length types.

 Action:	Remove the length specification from the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-00100	Non integer label is not ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a non-integer WHENEVER... GOTO label was in a Pro*Pascal program. For example, you might have coded

 EXEC SQL WHENEVER NOT FOUND GOTO 5.0;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, use only integer WHENEVER... GOTO labels in a Pro*Pascal program.

PCC-00101	Lower case 'e' in floating point number is not ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a lowercase 'e' was used in scientific notation. For example, you might have coded

 maxnum = 10e38;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, use an uppercase 'E' in scientific notation.

PCC-00102	FOR UPDATE is an Oracle extension

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the FOR UPDATE OF clause was used in a cursor declaration. For example, you might have coded

 EXEC SQL DECLARE emp_cursor CURSOR FOR     SELECT ENAME, SAL FROM EMP WHERE DEPTNO = :dept_number         FOR UPDATE OF SAL;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the FOR UPDATE OF clause.

PCC-00103	AT clause is an Oracle extension

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the AT <db_name> clause was used in a SQL statement. For example, you might have coded

 EXEC SQL AT oracle3 COMMIT RELEASE;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the AT <db_name> clause.

PCC-00104	FOR clause is an Oracle extension

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the FOR clause was used in an array-processing SQL statement. For example, you might have coded

 EXEC SQL FOR :limit INSERT INTO EMP (EMPNO, JOB, DEPTNO)     VALUES (:emp_number, :job_title, :dept_number);  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the FOR clause.

PCC-00105	Keyword WORK required here by ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the keyword WORK was used in a COMMIT or ROLLBACK statement. For example, you might have coded

 EXEC SQL COMMIT WORK RELEASE;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the keyword WORK.

PCC-00106	RELEASE is an Oracle extension to the COMMIT and ROLLBACK statements

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the parameter RELEASE was used in a COMMIT or ROLLBACK statement. For example, you might have coded

 EXEC SQL ROLLBACK RELEASE;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the parameter RELEASE.

PCC-00107	The CONNECT statement is Oracle implementation dependent

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, the CONNECT statement was used to log on to Oracle. For example, you might have coded

 EXEC SQL CONNECT :username IDENTIFIED BY :password;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, specify the AUTO_CONNECT command-line option instead of using a CONNECT statement.

PCC-00108	This statement is not supported by ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a nonconforming SQL statement such as PREPARE was used. For example, you might have coded

 EXEC SQL PREPARE sql_statement FROM :sql_string;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the nonconforming SQL statement.

PCC-00109	Dynamic SQL and PL/SQL are an Oracle extensions to ANSI SQL

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, dynamic SQL or embedded PL/SQL was used. For example, you might have coded

 EXEC SQL EXECUTE     BEGIN         SELECT ...         ...     END; END-EXEC;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use dynamic SQL or embedded PL/SQL.

PCC-00110	Oracle extension to the WHENEVER statement

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a nonconforming keyword such as NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER statement. (Note that NOT FOUND is ANSI-compliant.) For example, you might have coded

 EXEC SQL WHENEVER SQLERROR STOP;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use the nonconforming keyword.

PCC-00111	SQLCHECK value in EXEC Oracle statement exceeds command line value

 Cause:	You entered the SQLCHECK option inline specifying a level of checking higher than the level you specified (or accepted by default) on the command line. This is not allowed. For example, if you specify SQLCHECK={SYNTAX | LIMITED} on the command line, you cannot specify SQLCHECK={SEMANTICS | FULL} inline.

This message is only a warning; the precompiler ignores the inline value and continues processing.

 Action:	Revise the EXEC Oracle statement or specify a lower level of checking on the command line.

PCC-00112	Datatype not supported by ANSI

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, a pointer or nonconforming datatype such as VARCHAR was used. For example, you might have coded

 EXEC SQL BEGIN DECLARE SECTION;     VARCHAR  username[20];     ... EXEC SQL END DECLARE SECTION;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not use pointers or nonconforming datatypes.

PCC-00113	Value of DBMS option invalid with given value of MODE option

 Cause:	When MODE={ANSI14 | ANSI13}, you specified DBMS=V7, or when MODE=ANSI, you specified DBMS=V6. These option settings are incompatible. Note that the DBMS option was not available before release 1.5 of the Oracle Precompilers.

 Action:	With DBMS=V7, instead of MODE={ANSI14 | ANSI13}, you can specify MODE={ANSI | Oracle}. With DBMS=V6, instead of MODE={ANSI14 | ANSI13}, you can specify MODE={ANSI14 | ANSI13 | Oracle} but MODE=Oracle is recommended.

PCC-00114	Length spec required in EXEC SQL VAR statements for VARxxx types

 Cause:	In a EXEC SQL VAR statement, a VARCHAR or VARRAW external datatype was specified without a length. Unlike other types, the VARCHAR and VARRAW types have a 2-byte length field followed by a variable-length data field, so you must specify the maximum length of the data field.

 Action:	Add a length specification to the EXEC SQL VAR statement.

PCC-00115	Array required here

 Cause:	In an ARRAYLEN statement, you failed to specify the name of a previously declared host array. The first host variable in an ARRAYLEN statement must be an array. The second host variable, which specifies an array dimension, must be a 4-byte integer. The correct syntax follows:

 EXEC SQL ARRAYLEN host_array (dimension);  	The ARRAYLEN statement must appear in the Declare Section along with, but somewhere after, the declarations of host_array and dimension.

 Action:	Check your spelling of both identifiers in the ARRAYLEN statement. If necessary, supply the missing host array name.

PCC-00116	This array already given in an ARRAYLEN statement

 Cause:	You specified the same host array in two different ARRAYLEN statements. You cannot reference a given host array in more than one ARRAYLEN statement.

 Action:	Check your spelling of the host array names in both ARRAYLEN statements. Change one of the names so that they refer to different host arrays or remove one of the ARRAYLEN statements.

PCC-00117	Invalid ARRAYLEN length variable type

 Cause:	In an ARRAYLEN statement, you failed to specify a valid array dimension. You must specify the array dimension using a previously declared 4-byte, integer host variable, not a literal or expression. For example, the following statement is illegal:

 EXEC SQL ARRAYLEN ename_array (25);  -- illegal dimension   Action:	Supply a valid array dimension. If necessary, declare a 4-byte, integer host variable for use in the ARRAYLEN statement.

PCC-00118	Use of host variable initialization not supported by ANSI SQL

 Cause:	You used an Oracle extension to the ANSI/ISO SQL standard. Specifically, you initialized a host variable in its declaration, as shown in the following Pro*C example:

 EXEC SQL BEGIN DECLARE SECTION;     int  dept_number = 20;  -- not ANSI/ISO-compliant     ... EXEC SQL END DECLARE SECTION;  	This message is only a warning issued by the FIPS Flagger when FIPS=YES.

 Action:	No action required. However, for ANSI/ISO compliance, do not initialize host variables in their declarations.

PCC-00119	Value of const variable in INTO clause will be modified

 Cause:	You used a constant instead of an output host variable in the INTO clause of a SELECT statement. The SELECT INTO statement retrieves a value for each item in the select list, then assigns the values to corresponding variables in the INTO clause. Because the values of constants are fixed, you cannot use them as output host variables.

 Action:	Check your spelling of all identifiers in the INTO clause. If necessary, change the constant declaration to a variable declaration.

PCC-00120	File I/O error during code generation

 Cause:	This is an internal error message not usually issued.

 Action:	Call customer support for assistance.

PCC-00121	Arrays of VARCHAR pointers are not supported

 Cause:	You tried to declare an array of pointers, which is not allowed. However, pointers to scalar types are allowed. With Pro*C, declare pointers to char[n] and VRCHAR[n] variables as pointers to char or VARCHAR (with no length specification).

 Action:	Correct or remove the declaration.

PCC-00122	Input file name and output file name are identical

 Cause:	On the command line, you mistakenly specified the same pathname for INAME and ONAME, which designate the precompiler input and output files, respectively.

 Action:	Change one of the path/filenames.

PCC-00123	Entire VARCHAR declaration must be on same line

 Cause:	In a Pro*C program, a VARCHAR declaration spans more than one line, which is not allowed.

 Action:	Revise the declaration so that it uses only one line.

PCC-00124	COMMON_NAME option must be before PROGRAM or subroutine beginning

 Cause:	In a FORTRAN program, subroutine, or function, you mistakenly specified the precompiler option COMMON_NAME after the PROGRAM, SUBROUTINE, or FUNCTION statement. If you specify COMMON_NAME inline, its EXEC Oracle OPTION statement must precede the PROGRAM, SUBROUTINE, or FUNCTION statement.

 Action:	Relocate the EXEC Oracle OPTION statement or specify COMMON_NAME on the command line.

PCC-00125	Error on command line or in the configuration file

 Cause:	The precompiler found an invalid option on the command line or in a configuration file (a text file containing preset command-line options). Some possible causes follow:

•	An option name is misspelled.

•	A specified option does not exist.

•	The equal sign (=) between an option name and value is missing or has space around it.

•	The name of the input file was not preceded by INAME=.

 Action:	Check that each option exists, that its name is spelled correctly, and that there is an equal sign between the option name and value.

PCC-00126	Could not find or open system configuration file

 Cause:	The precompiler was unable to find or open the system configuration file (a text file containing preset command-line options, which the precompiler uses by default). Some possible causes follow:

•	The file does not exist.

•	The search path to the file is incorrect.

•	You have insufficient file access privileges.

•	There are too many open files.

However, this message is just a warning. Processing continues even if the system configuration file does not exist.

 Action:	Check that the file exists, that the search path to the file is correct, and that you have sufficient privileges to access the file. Also check that the limit for open files is set high enough (check with your system manager).

PCC-00127	text

 Cause:	This is a generic error message from the command-line processor.

 Action:	Correct the indicated error.

PCC-00128	Command line processor severe error

 Cause:	The command line processor encountered a severe error.

 Action:	After making sure you specified all the command-line options correctly, call customer support with a full account of all the options and configuration files used.

PCC-00129	option optnam must be given

 Cause:	A required command-line option is missing. For example, the INAME option, which specifies the name of the input file, might be missing.

 Action:	Supply the missing command-line option.

PCC-00130	Invalid value val for option optnam

 Cause:	The precompiler found an invalid option value. For example, the value might be misspelled (as in DBMS=6V) or illegal (as in DBMS=V5).

 Action:	Check the value, making sure that it is legal and correctly spelled.

PCC-01000	You are not authorized to run Pro*COBOL

 Cause:	Your authorization or license to run the Pro*COBOL Precompiler has expired.

 Action:	Call customer support for assistance.

PCC-01001	Your Pro*COBOL authorization is about to expire

 Cause:	Your authorization or license to run the Pro*COBOL Precompiler is about to expire.

 Action:	Call customer support for assistance.

PCC-01002	Invalid character char in indicator area at line num in file name

 Cause:	In a Pro*COBOL Precompiler program, only a blank, hyphen (-), asterisk (*), slash (/), or letter "D" is allowed in the indicator area, but the precompiler found another character.

 Action:	Remove or replace the invalid character. If you specified the FORMAT=ANSI option, check for an end-of-line in column 7.

PCC-01003	Invalid continuation at line num in file name

 Cause:	In a Pro*COBOL program, a continuation line was completely blank, except for the continuation character.

 Action:	Remove or replace the empty continuation line.

PCC-01004	In an EXEC statement at end-of-file

 Cause:	In a Pro*COBOL input file, the last EXEC statement was not terminated properly.

 Action:	Terminate the last EXEC statement with an END-EXEC.

PCC-01005	PROCEDURE DIVISION not found

 Cause:	The precompiler could not find the PROCEDURE DIVISION header in a Pro*COBOL program. Some possible causes follow:

•	A keyword in the header is missing or misspelled.

•	There is an apostrophe in the REMARKS section (the precompiler mistook the apostrophe for the beginning of a string literal).

•	There is an unterminated literal in the WORKING-STORAGE SECTION.

•	You specified the wrong value for the FORMAT option.

 Action:	Check that the PROCEDURE DIVISION header is in place and spelled correctly, that there is no apostrophe in the REMARKS section, that all literals in the WORKING-STORAGE SECTION are terminated, and that you specify the right value for the FORMAT option.

PCC-01006	EXEC statement cannot begin in Area A at line num in file name

 Cause:	In a Pro*COBOL program, EXEC statements must begin in Area B, but the precompiler found a statement beginning in Area A.

 Action:	Move the statement rightward so that it begins in Area B.

PCC-01007	WORKING-STORAGE SECTION not found

 Cause:	The precompiler could not find the WORKING-STORAGE SECTION header in a Pro*COBOL program, probably because a keyword is missing or misspelled, or you might have specified the wrong value for the FORMAT option.

 Action:	Check that the WORKING-STORAGE SECTION header is in place and spelled correctly and that you specify the right value for the FORMAT option.

PCC-01008	Multiple element records not allowed in Declare Section

 Cause:	A few COBOL compilers do not allow group items to be passed as parameters in a CALL statement. (Check your COBOL compiler user's guide.) If your compiler is one of these, group items within the Declare Section can contain only one elementary item.

 Action:	Assign each host variable its own group item.

PCC-01009	For HOST=COB74, a SQL statement must be followed by ELSE or "."

 Cause:	In a Pro*COBOL program, an EXEC SQL statement is followed by another statement in the same sentence. An EXEC SQL statement must be the last statement in a COBOL-74 sentence and so must be terminated by the keyword ELSE or a period.

 Action:	Change the program logic, making the EXEC SQL statement the last statement in the sentence.

PCC-01010	Invalid use of NULL character in character literal

 Cause:	A null character (binary zero) was found in a string literal. This is not allowed by Pro*COBOL.

 Action:	Remove the null character from the string literal.

PCC-01011	USAGE IS BINARY clause must be terminated by "." on same line

 Cause:	The period terminating the USAGE IS BINARY clause must be on the same line as the USAGE clause. This message only occurs on operating systems that support the COMP5=YES command line option of Pro*COBOL, where COMP-5 is substituted for BINARY.

 Action:	Check that the period terminating the USAGE IS BINARY clause is on the same line as the USAGE clause.

PCC-01100	You are not authorized to run Pro*FORTRAN

 Cause:	Your authorization or license to run the Pro*FORTRAN Precompiler has expired.

 Action:	Call customer support for assistance.

PCC-01101	Your Pro*FORTRAN authorization is about to expire

 Cause:	Your authorization or license to run the Pro*FORTRAN Precompiler is about to expire.

 Action:	Call customer support for assistance.

PCC-01102	Invalid label at line num in file name

 Cause:	The Pro*FORTRAN Precompiler found an invalid FORTRAN statement label in columns 1 through 6.

 Action:	Correct or remove the statement label.

PCC-01200	You are not authorized to run Pro*C

 Cause:	Your authorization or license to run the Pro*C Precompiler has expired.

 Action:	Call customer support for assistance.

PCC-01201	Your Pro*C authorization is about to expire

 Cause:	Your authorization or license to run the Pro*C Precompiler is about to expire.

 Action:	Call customer support for assistance.

PCC-01202	Identifier ident truncated to 31 characters

 Cause:	A host identifier (the name of a host variable, for example) was truncated to the maximum length (31 characters) allowed by the precompiler.

 Action:	No action required. This message is just informational.

PCC-01300	You are not authorized to run Pro*PL/I

 Cause:	Your authorization or license to run the Pro*PL/I Precompiler has expired.

 Action:	Call customer support for assistance.

PCC-01301	Your Pro*PL/I authorization is about to expire

 Cause:	Your authorization or license to run the Pro*PL/I Precompiler is about to expire.

 Action:	Call customer support for assistance.

PCC-01400	You are not authorized to run Pro*Pascal

 Cause:	Your authorization or license to run the Pro*Pascal Precompiler has expired.

 Action:	Call customer support for assistance.

PCC-01401	Your Pro*Pascal authorization is about to expire

 Cause:	Your authorization or license to run the Pro*Pascal Precompiler is about to expire.

 Action:	Call customer support for assistance.

PCC-01500	You are not authorized to run Pro*Ada

 Cause:	Your authorization or license to run the Pro*Ada Precompiler has expired.

 Action:	Call Oracle Customer Support for assistance.

PCC-01501	Your Pro*Ada authorization is about to expire

 Cause:	Your authorization or license to run the Pro*Ada Precompiler is about to expire.

 Action:	Call Oracle Customer Support for assistance.

PCC-01510	No package, procedure, or function statement seen in name

 Cause:	Every Ada source file must have a package, procedure, or function statement. The precompiler did not find one.

 Action:	Add the appropriate statement(s) to the source file and rerun Pro*Ada.

PCC-01511	Identifier on line num in file name was too long for code generated in file name

 Cause:	An identifier used in the host program is of a length that causes precompiler-generated code to exceed the length limitation on source lines.

 Action:	Use a shorter identifier or use the ORECLEN option to increase the allowed line length.

PCC-01512	Invalid EXEC SQL INCLUDE of file name found at line num in file name

 Cause:	The EXEC SQL INCLUDE statement is not allowed in Pro*Ada.

 Action:	Embed required source text directly in the Pro*Ada file. Use the with context clause to include required packages.

PCC-01513	FIPS warning: Unsupported datatype in line num of file name

 Cause:	For Pro*Ada Version 1.5 or higher, the FIPS Flagger is set and a non-ANSI datatype is used.

 Action:	To comply with the standard, use only ANSI datatypes.

PCC-01515	FIPS warning: Undeclared host variable hostvar at line num in file name

 Cause:	For Pro*Ada Version 1.5 or higher, the FIPS Flagger is set and a host variable is not declared within a Declare Section, which is not compliant with the ANSI standard.

 Action:	To comply with the standard, declare the host variable within a Declare Section.

 ________________________________________

02010-02400: PCC Messages Release 2.0

PCC-02010	Found end-of-file while scanning string literal

 Cause:	A string in a SQL statement, which should be delimited by single quotation marks, was not terminated properly.

 Action:	Check that all strings are delimited.

PCC-02011	Found identifier greater than 128 characters (truncated)

 Cause:	The precompiler found an identifier that was too long.

 Action:	Shorten the identifier. SQL identifiers should be limited to 18 characters.

PCC-02012	Did not find a matching quote for char constant

 Cause:	You did not terminate a character constant with a single quotation mark.

 Action:	Terminate the character constant.

PCC-02013	Unknown escape sequence

 Cause:	The precompiler found an escape sequence that it could not process inside a string literal. This error can arise when multibyte character strings that can contain shift-in or shift-out escape sequences are used.

 Action:	Correct the string representation.

PCC-02014	Syntax error at line num, column colnam, file name

 Cause:	The precompiler detected an error in C or embedded SQL syntax. This message is followed by a more specific error message.

 Action:	Correct the syntax error.

PCC-02015	Unable to open include file

 Cause:	The precompiler could not open a header file that you specified using the #include preprocessor directive or the EXEC SQL INCLUDE statement. This can happen if the file specification is inaccurate or if you do not have read permissions or read access rights on the file or on one or more of the directories in the path.

 Action:	Recheck that the file specification is correct, that the file exists, and that you can read the file.

PCC-02016	Include file pathname is too long

 Cause:	The pathname for include files exceeded the maximum length of 80 characters.

 Action:	You might have to move the include file, or you can create an environment variable or logical to shorten the pathname.

PCC-02017	Unable to open output file

 Cause:	The precompiler could not open an output file. This could be a generated code output file (.c file) or a listing file. This message can result from many causes. For example:

•	A pathname for an output file you specified contains a non-existent directory.

•	An operating-system error occurred because the file system or disk is full.

•	You do not have write permission on the specified directory or directories in the path.

 Action:	Track down the cause of the error, as suggested above, and correct it.

PCC-02018	Found end-of-file while scanning comment

 Cause:	A C comment, either in C code or in an embedded SQL statement, was not terminated.

 Action:	Find the unterminated comment and terminate it with */.

PCC-02019	Preprocessor warning at line num, column colnam, file name

 Cause:	This message informs you that a warning condition occurred as the precompiler was doing the preprocessor pass. A more specific warning message will follow this message.

 Action:	Correct the condition according to the action specified for the message that follows.

PCC-02020	Preprocessor error at line num, column colnam, file name

 Cause:	This message informs you that an error condition occurred as the precompiler was in the preprocessing phase. A more specific error message will follow this message.

 Action:	Correct the error according to the action specified for the message that follows.

PCC-02035	CMD-LINE:  CONFIG= option is invalid in a config file

 Cause:	You cannot specify a user configuration file inside a user configuration file. That is, you cannot nest configuration files.

 Action:	If there are nested configuration files, move the options from the nested files to the top-level file.

PCC-02040	CMD-LINE:  Option selected, but no value provided

 Cause:	You specified an option on the command line but did not provide a value for it. For example, the command

proc ina=sample1 oname=

could trigger this error message.

 Action:	Provide a value for the option.

PCC-02041	CMD-LINE:  Option does not exist:

 Cause:	You specified an non-existent option on the command line.

 Action:	See the Programmer's Guide to the Oracle Precompilers for a list of the valid command-line options and their possible values.

PCC-02043	CMD-LINE:  Option syntax is incorrect

 Cause:	You specified a value for a command-line option incorrectly.

 Action:	See the Programmer's Guide to the Oracle Precompilers for the correct syntax for specifying command-line option values.

PCC-02044	CMD-LINE:  Illegal or out of range value for option:

 Cause:	A value that you specified for a command-line option was not within the accepted range. For example, the range for the MAXOPENCURSORS option is 5 to 256. If you specify a value outside this range, this message is triggered.

 Action:	See the Programmer's Guide to the Oracle Precompilers for the ranges that option values can take.

PCC-02066	CMD-LINE:  Could not find or could not open system config file

 Cause:	The system configuration file has a standard name (pmscfg.h) and a location that is operating-system dependent. On UNIX systems, it is located in the Oracle_HOME/proc directory. If a file named pmscfg.h is not found in the standard location, this warning message is issued.

 Action:	Create a system configuration file in the standard location. The file can be empty. See also your operating system-specific Oracle documentation.

PCC-02100	Unable to initialize PL/SQL

 Cause:	The precompiler connected to Oracle but could not invoke the PL/SQL engine. This error can result if you have an earlier release of Oracle7 and do not have the Procedural Option

 Action:	To use PL/SQL, you must upgrade to a more recent release of Oracle7.

PCC-02101	Unable to open input file

 Cause:	The precompiler could not open the input file. This is the .pc file specified in the INAME= option. This means that the file does not exist, that you incorrectly specified a directory in the pathname, or that you (running the precompiler) do not have read permission for the file.

This message could also result from operating-system errors. For example, an unmounted file system or disk I/O errors, could trigger this error.

 Action:	Check that you can read the file and that you specified the full pathname correctly. Check for operating system-specific problems. See also your operating system-specific Oracle documentation.

PCC-02102	Fatal error while doing C preprocessing

 Cause:	The precompiler issues this message after a more specific message.

 Action:	Correct the problem specified in the previous message or messages.

PCC-02104	Unable to connect to Oracle

 Cause:	The precompiler could not connect to Oracle with the username, password, and, if applicable, database link that you supplied. Note that this is a precompiler message, not a run time message. This means that the USERID option value, either on the command line or in a configuration file, was incorrect.

 Action:	Check that the username and password are current and correct. Run SQL*DBA or SQL*Plus and verify that you can connect using that username and password.

PCC-02105	Unable to open list file

 Cause:	The precompiler could not open the listing file. This message can result from many causes. For example:

•	A pathname for a listing file you specified contains a non-existent directory.

•	An operating-system error occurred because the file system or disk is full.

•	You do not have write permission on the specified directory.

 Action:	Track down the cause of the error, as suggested above, and correct it.

PCC-02106	Userid only used when SQLCHECK=FULL, userid ignored

 Cause:	You specified the USERID option on the command line, but SQLCHECK was not equal to FULL or SEMANTICS. The USERID has no effect, unless SQLCHECK=FULL or SQLCHECK=SEMNATICS.

 Action:	This is a warning message only.

PCC-02129	CMD-LINE:  Client supplied static options table is invalid

 Cause:	This is an internal error message not usually issued.

 Action:	Call Oracle customer support.

PCC-02132	CMD-LINE:  Could not allocate memory

 Cause:	This is an internal error message not usually issued.

 Action:	Call Oracle customer support.

PCC-02133	CMD-LINE:  Error processing string function

 Cause:	This is an internal error message not usually issued. It indicates that a C string function, such as strcpy or strlen, returned an error.

 Action:	Call Oracle customer support.

PCC-02135	CMD-LINE:  User asked for help

 Cause:	This is a final message that the precompiler issues when you have asked for information about the command-line options. For example, if you issue the command

proc ?

to get a list of the current default values for the command-line options, you will see this message at the end of the list.

 Action:	No action required.

PCC-02200	Found unrecognized punctuation sequence

 Cause:	This error indicates that the precompiler parser encountered a badly-formed identifier or keyword

 Action:	Correct the syntax.

PCC-02201	Found syntax error

 Cause:	This general message precedes one or more specific messages that detail the nature of the error.

 Action:	No action required. Correct the errors diagnosed in the following message(s).

PCC-02202	No typedef name was given

 Cause:	The precompiler parser encountered a typedef statement that had no name after the type specification. For example

typedef int;

 Action:	Correct the syntax.

PCC-02203	Found end of file when not expected

 Cause:	The parser can emit this message when a general syntax error occurs, for example, an unmatched `{' or `('.

 Action:	Correct the syntax.

PCC-02204	EXEC SQL INCLUDE not permitted from within an included file

 Cause:	You cannot nest EXEC SQL INCLUDE statements. Also, you cannot put an EXEC SQL INCLUDE statement inside a file that is included using the #include preprocessor command.

 Action:	Recode the program so that the nested include statement is not required.

PCC-02205	Parser error at line num, column colnam, file name

 Cause:	The precompiler parser encountered a syntax error, either in C code or in SQL code. A more specific message should follow.

 Action:	No action required for this message. Take the appropriate action for any following messages.

PCC-02206	Host variables are not permitted within a DDL statement

 Cause:	A Data Definition Language statement cannot use host variables. For example, the statement

CREATE TABLE :table_name (c1 char(10));

is illegal, because the name of the table in a CREATE TABLE statement cannot be represented using a host variable.

 Action:	Use dynamic SQL if you need to create the names of database objects (tables, views, columns, etc.) at runtime. See the Programmer's Guide to the Oracle Precompilers for information about dynamic SQL.

PCC-02209	Macro invocation has incorrect number of arguments

 Cause:	A macro invocation in the source does not have the same number of arguments as the macro definition in the #define line.

 Action:	Correct the macro reference or the macro definition.

PCC-02301	Cannot open input file for reading

 Cause:	The semantic analysis phase of the precompiler could not re-open the input file to generate output code.

 Action:	Check that the input file and its directory's protections and privileges do not change in the course of precompilation.

PCC-02302	Cannot open code generation output file

 Cause:	The precompiler was not able to open one or both of the temporary files that are required for code generation. The user executing the precompiler must have write permission (and/or the appropriate privileges) on the current directory.

 Action:	Check that you have permission to create files in the current directory.

PCC-02303	Cannot open include file

 Cause:	The precompiler was not able to open a header file specified using the #include preprocessor directive or the EXEC SQL INCLUDE statement. This can happen if the file specification is inaccurate or if you do not have read permissions or read-access rights on the file or on one or more of the directories in the path.

 Action:	Recheck that the file specification is correct, that the file exists, and that you can read the file

PCC-02304	Invalid declaration of C function

 Cause:	You declared a C function using invalid syntax.

 Action:	Consult a C programming manual and correct the declaration.

PCC-02305	Illegal mixing of new and old style C function declarations

 Cause:	You must declare all C functions using either the traditional style (K&R style) function declarations or the new (ANSI) style. You cannot mix the two.

 Action:	Adopt a consist declaration style for functions.

PCC-02306	Illegal name of C function

 Cause:	A C function was declared with a name that is not a legal C identifier.

 Action:	Use legal C identifiers for all function names.

PCC-02307	Void can only be used when single parameter

 Cause:	You can declare or define a function using the following syntax:

int func1(void)

to indicate that the function has no parameters. void can be used only once in this case.

 Action:	Remove the extra voids in the function definition or declaration.

PCC-02308	Identifier required in this function definition

 Cause:	A function definition written in ANSI C must have both the name and the type for all parameters.

 Action:	Rewrite the function definition so that it contains the name of each parameter.

PCC-02309	Illegal formal parameter declaration

 Cause:	You specified a formal parameter in a function declaration without giving its type.

 Action:	Include the types of all parameters in function declarations.

PCC-02310	Formal parameter VARCHAR's must be declared as pointers

 Cause:	Many C compilers allow structures to be passed to and returned from functions. Although a VARCHAR is implemented as a C struct, you must pass VARCHARs to a function as pointers.

 Action:	Take the address of a VARCHAR when it is passed to a function. See the example in the section "Referencing VARCHAR Variables" in the Programmer's Guide to the Oracle Precompilers.

PCC-02311	Cannot have VARCHAR bit fields

 Cause:	Host variables cannot contain bit fields.

 Action:	Recode your application to remove the bit fields.

PCC-02312	Arrays of VARCHAR greater than two dimensions not allowed

 Cause:	You declared a VARCHAR array with more than two dimensions. Multidimensional arrays are not supported as host variables.

 Action:	Recode your application to remove multidimensional array usage.

PCC-02313	Malformed VARCHAR declaration - missing length

 Cause:	When you declare a VARCHAR, a length specification is mandatory. For example, the following VARCHAR declaration is meaningless, hence illegal:

VARCHAR v1[];

 Action:	Specify the length for each VARCHAR that you declare.

PCC-02314	Cannot evaluate constant sizeof expression

 Cause:	A sizeof operator was used where a precompiler expression was expected.

 Action:	Eliminate the sizeof operator.

PCC-02315	Cannot evaluate expression as a constant.

 Cause:	The specified expression does not evaluate to a constant. Such expressions are required, for example, as the length of a VARCHAR.

 Action:	Replace the expression with one that does evaluate to a constant integer

PCC-02316	Illegal operator in constant expression

 Cause:	A non-arithmetic operator was present in the expression.

 Action:	Rewrite the expression to eliminate the non-arithmetic operator.

PCC-02317	Illegal cast type expression

 Cause:	A illegal cast is present in the expression.

 Action:	Remove the illegal cast.

PCC-02318	Missing type expression

 Cause:	The specified expression is missing the declaration of a type.

 Action:	Specify a type for the expression.

PCC-02319	Expression type does not match usage

 Cause:	The type of a variable does not match its usage. For example, in dynamic SQL, a host variable containing the text of a SQL statement must be declared as a C character type or be equivalenced to the SQL type STRING.

 Action:	Remove the declaration.

PCC-02320	Arithmetic expression does not have correct operand types

 Cause:	The arithmetic expression must be specified with integral types.

 Action:	Rewrite the expression using integral types.

PCC-02321	Only subtraction between two pointers is permitted

 Cause:	You cannot add, multiply, or divide pointer values.

 Action:	Recode to avoid this error message.

PCC-02322	Found undefined identifier

 Cause:	An identifier used in a SQL statement was not defined. For example, you referenced a cursor name that had not been declared, or in a DECLARE CURSOR statement, you used a statement name that had not been PREPAREd.

 Action:	Check that all SQL identifiers, such as cursor names and statement names, have been defined before use.

PCC-02326	Illegal structure reference operation

 Cause:	You referenced a structure component using invalid syntax. For example, a -> operator was used instead of a required `.' operator.

 Action:	Correct the invalid reference.

PCC-02327	Struct or struct pointer required

 Cause:	You used a scalar host variable in a context where a structure (or its pointer) is required.

 Action:	Make the host variable a structure or add more scalar host variables to satisfy the SQL syntax requirements.

PCC-02328	Undefined struct member

 Cause:	You referenced a structure component that was not declared as part of the structure.

 Action:	Redefine the structure.

PCC-02330	Expecting an expression of integer type

 Cause:	The expression does not evaluate to an integer. For example, a SQL FOR expression must evaluate to an integral type.

 Action:	Rewrite the expression.

PCC-02331	Undefined SQL identifier

 Cause:	All SQL identifiers must be defined before they are used. This message can result when a CURSOR or STATEMENT is not declared (defined) before being referenced.

 Action:	Define the identifier.

PCC-02332	Attempted to redefine SQL identifier

 Cause:	A SQL identifier (such as a cursor name) can be defined only once.

 Action:	Do not redefine the identifier. Use a different name.

PCC-02333	SQL identifier was not declared as a statement

 Cause:	You referenced a SQL statement identifier in a DECLARE... CURSOR statement that was not PREPAREd.

 Action:	Check that all SQL statement names have been declared. Remember that SQL statement names are identifiers, not variables, and that they are local to the precompilation unit.

PCC-02334	SQL identifier was not declared as a cursor

 Cause:	You used a cursor name in an OPEN, FETCH, or CLOSE statement that had not been DECLAREd.

 Action:	Check that all SQL cursor names have been declared. Remember that cursors are identifiers, not variables, and that they are local to the precompilation unit.

PCC-02335	Body of cursor must name statement identifier

 Cause:	In a Dynamic SQL Method 4 application, the DECLARE... CURSOR statement must name a statement identifier that has been PREPAREd in a preceding statement. The PREPARE statement must physically (not logically) precede the DECLARE command.

 Action:	This error message is followed by another message that gives the line and column of the reference to the statement. Recode the application.

PCC-02336	Host variable expression has invalid type

 Cause:	The host variable was declared using a C type that is not permitted as a host variable. See the Programmer's Guide to the oracle Precompilers for a list of the permissible C types for host variables.

 Action:	Use a permissible host variable type

PCC-02337	Cannot declare multi-dimensioned array for this type

 Cause:	You cannot declare host variable arrays of scalars with more than 1 dimension.

 Action:	Recode the application because this kind of host variable usage is not possible with database operations.

PCC-02338	Structure contains a nested struct or union

 Cause:	You used a host structure that contained a struct or union. This usage is not legal for Pro*C Release 2.0.

 Action:	This error message is followed by another message that gives the line and column of the reference to the illegal struct. Redefine the structure.

PCC-02339	Host variables cannot be of union types

 Cause:	You cannot use a C union as a host variable.

 Action:	This error message is followed by another message that gives the line and column of the reference to the illegal union. Recode, using a struct or individual scalar host variables.

PCC-02340	Structure contains a bit field

 Cause:	Bit fields are not allowed in host variables because they are meaningless for database DML operations.

 Action:	This error message is followed by another message that gives the line and column of the reference to the offending host variable. Recode the application.

PCC-02341	Host variable has illegal type

 Cause:	A host variable cannot be declared using the void type.

 Action:	Rewrite the declaration, using a permissible host variable type.

PCC-02342	Using WHERE CURRENT OF on cursor defined without FOR UPDATE clause

 Cause:	When MODE=Oracle, a cursor defined with a WHERE CURRENT OF clause must also have a FOR UPDATE clause.

 Action:	Rewrite the cursor definition.

PCC-02343	Body of cursor must be a query expression

 Cause:	A cursor definition must be a SELECT statement.

 Action:	Rewrite the cursor definition.

PCC-02344	Host variable arrays must all be of equal size

 Cause:	This is a warning message. If host arrays are not of equal size, the size of the smallest array is used.

 Action:	No action required.

PCC-02345	SQLCHECK=SEMANTICS must be given when embedded PL/SQL blocks are used

 Cause:	When your Pro*C program contains embedded PL/SQL blocks, you must precompile using the SQLCHECK=SEMANTICS option, specified either on the command line or in a configuration file.

 Action:	Use the SQLCHECK=SEMANTICS option. This also requires that the USERID connect option be given.

PCC-02346	PL/SQL found semantic errors

 Cause:	You referenced a database entity, such as a table or column name, that does not exist. This is a compile time error, not a runtime error.

 Action:	Check that all referenced objects in PL/SQL statements actually exist and that you have access permissions on them.

PCC-02347	PL/SQL found syntax errors

 Cause:	You used a PL/SQL statement illegally.

 Action:	Check the PL/SQL User's Guide and Reference for the correct syntax.

PCC-02348	Indicators are not allowed in EXEC IAF statements

 Cause:	You cannot use indicator variables associated with host variables in EXEC IAF statements such as GET and PUT in a user exit.

 Action:	Eliminate the indicator variables. If feasible (for example with Forms V4), use EXEC TOOLS statements, which do allow indicator variables. See the Programmer's Guide to the Oracle Precompilers for more information of EXEC IAF and EXEC TOOLS statements.

PCC-02349	Precision must be specified for this type

 Cause:	In a VAR or TYPE statement, certain Oracle types require that you specify a precision. For example, VARCHAR2 or CHAR.

 Action:	Indicate the precision.

PCC-02350	Cannot equivalence this SQL type

 Cause:	You cannot use datatype or variable equivalencing to the datatypes NUMBER or DECIMAL. See the "Datatype Equivalencing" section in the Programmer's Guide to the Oracle Precompilers for more information.

 Action:	Use the appropriate datatype for your application.

PCC-02351	Illegal datatype equivalencing operation

 Cause:	The datatype specified could not be equivalenced, or the syntax was incorrect in the VAR or TYPE statement.

 Action:	See the Programmer's Guide to the Oracle Precompilers for a list of the datatypes that can be equivalenced and the correct syntax of the VAR or TYPE statement.

PCC-02352	Out of bounds bind position from PL/SQL

 Cause:	This is an internal error.

 Action:	Call Oracle customer support for assistance.

PCC-02353	Semantic error at line num, column colnam, file name

 Cause:	This error message precedes a more specific error message.

 Action:	No action required. Correct the error(s) reported in the following message(s).

PCC-02354	A file included with #include cannot contain SQL statements

 Cause:	The Pro*C Precompiler reads header files referenced in #include directives and uses the values defined in them. But the precompiler never generates code using statements in header files, so use of SQL statements in these files is illegal.

 Action:	Move the SQL statement(s) into the main body of the application or use EXEC SQL INCLUDE to check that the included file is precompiled.

PCC-02355	Invalid or obsolete option, ignored

 Cause:	You specified a command-line option that is not used in Pro*C Release 2.0. For example, the option AREASIZE is no longer valid with precompilers used with the Oracle7 Server.

 Action:	No action required. This is an informational message.

PCC-02356	Warning at line num, column colnam, file name

 Cause:	This is a generic warning message. It precedes a more specific warning.

 Action:	No action required. Correct the error(s) indicated in the following messages.

PCC-02357	Function calls may not be used as host variable expressions

 Cause:	Only objects that are lvalues (that resolve to an address) can be host variables. Because a function call is not an lvalue, one cannot be used in place of a host variable.

 Action:	Recode the application.

PCC-02358	Identifier following ARRAYLEN must be the name of an array

 Cause:	You must specify a declared array as the argument for an ARRAYLEN statement. Declare the array textually before the ARRAYLEN statement. See the Programmer's Guide to the Oracle Precompilers for the syntax of the ARRAYLEN statement.

 Action:	Correct the statement, specifying a host array as the argument.

PCC-02359	Identifier specifying ARRAYLEN dimension must be an integer

 Cause:	The expression that specifies the ARRAYLEN dimension must evaluate to an integer. For example, the statement

EXEC SQL ARRAYLEN my_array(1.3)

cannot be parsed.

 Action:	Correct the statement, using an integral dimension.

PCC-02360	This array type is invalid for use with ARRAYLEN statement

 Cause:	Arrays of some host variables types are not allowed and hence also cannot be used in ARRAYLEN statements. VARCHAR is an example.

 Action:	Specify an array with a datatype that can be used in host arrays.

PCC-02361	Use of ARRAYLEN with SQL host arrays is ignored

 Cause:	ARRAYLEN is only valid with arrays that can be bound in PL/SQL blocks.

 Action:	Use an appropriate array type.

PCC-02362	Host variable not declared within SQL Declare Section

 Cause:	When you specify MODE=ANSI at precompile time, all host variables must be declared inside Declare Sections. Remember that MODE=ANSI refers to ANSI SQL, not ANSI C.

 Action:	Add the EXEC SQL BEGIN DECLARE SECTION... EXEC SQL END DECLARE SECTION statements around all host variable declarations.

PCC-02363	Indicator variable must be a structure

 Cause:	If the host variable is a structure, the associated indicator variable must also be a structure.

 Action:	Recode the application.

PCC-02364	Host structure and its indicator must have the same number of fields

 Cause:	When you declare a structure containing indicator variables and associate it with a host structure, the indicator structure must contain the same number of fields as the host structure. This is so even when you do not plan to use some of the indicators or even when it would not make sense to do so (for fields constrained as NON NULL, for example).

 Action:	Redeclare the indicator structure.

PCC-02365	Host and its indicator variable must have the same array dimensions

 Cause:	When associating an array of indicators with a host array, it is good practice to make the indicator array the same length as the host array. It should never be shorter.

 Action:	This is a warning message. The smallest array size will determine the number of items fetched, inserted, or updated.

PCC-02366	Command line argument MODE=ANSI may not be used with DBMS=V6

 Cause:	The semantics of certain operations (such as character comparison) in Oracle Version 6 are not 100% compliant with the ANSI/ISO SQL standards. When you request V6 semantics, using the DBMS=V6 or DBMS=V6_CHAR option, you cannot precompile with MODE=ANSI.

 Action:	Do not use ANSI mode with the V6 options.

PCC-02367	Indicator variables must be declared as type short

 Cause:	The only C type allowed for indicator variables is short. An array of indicator variables must be an array of shorts.

 Action:	Redeclare the indicator variables and/or indicator arrays.

PCC-02368	An EXEC TOOLS host variable context name is not type char

 Cause:	If you use a host variable to define a context name in an EXEC TOOLS GET CONTEXT or EXEC TOOLS SET CONTEXT statement, the host variable must be a character type.

 Action:	Redeclare the context name host variable.

PCC-02369	An EXEC TOOLS host pointer variable is not a pointer

 Cause:	The host variable specifying an EXEC TOOLS context must be a pointer type

 Action:	Redeclare the variable, making sure that it is a pointer.

PCC-02370	An EXEC TOOLS message host variable is not type char

 Cause:	If you use a host variable to define a context name in an EXEC TOOLS GET CONTEXT or EXEC TOOLS SET CONTEXT statement, the host variable must be a character type.

 Action:	Redeclare the context name host variable.

PCC-02371	Illegal FOR clause

 Cause:	The argument of a FOR clause must be specified as an integer or as an identifier containing an integer.

 Action:	Rewrite the FOR clause.

PCC-02372	FOR clause not allowed in a SELECT statement

 Cause:	A SQL statement containing a SELECT command cannot contain a FOR clause. The meaning of such a statement would be unclear.

 Action:	Rephrase the SELECT statement, removing the FOR clause.

PCC-02373	Invalid declaration in EXEC SQL DECLARE section

 Cause:	You put an improper declaration in a Declare Section. This message is usually caused by including an EXEC SQL TYPE or EXEC SQL VAR declaration in a Declare Section.

 Action:	Move the declaration outside the Declare Section.

PCC-02374	SQLCHECK value exceeds command line value

 Cause:	The value you assigned to the SQLCHECK option in an EXEC Oracle statement in your program was greater than the value given either on the command line or greater than the default value if no SQLCHECK option was given on the command line.

The order of the option values is SEMANTICS > SYNTAX > NONE.

When this warning message is issued, the original value of SQLCHECK (the default or the command-line value) stays in effect.

 Action:	Remove or recode the EXEC Oracle option(s) in the .pc source file to avoid this warning message.

 ________________________________________

02100-02139: Oracle Runtime Library SQL Messages

The following error messages might be issued at run time by SQLLIB, the Oracle runtime library.

SQL-02100	Out of memory (i.e., could not allocate)

 Cause:	SQLLIB was unable to allocate enough memory to execute your program.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02101	Inconsistent cursor cache (UCE/CUC mismatch)

 Cause:	The precompiler generates a unit cursor entry (UCE) array. An element in this array corresponds to an entry in the cursor cache (CUC). While doing a consistency check on the cursor cache, SQLLIB found that the unit cursor entry or cursor cache entry for an EXEC SQL statement is missing.

 Action:	The unit cursor entry must be regenerated, so rerun the program. If the error persists, call customer support for assistance.

SQL-02102	Inconsistent cursor cache (no CUC entry for this UCE)

 Cause:	The precompiler generates a unit cursor entry (UCE) array. An element in this array corresponds to an entry in the cursor cache (CUC). While doing a consistency check on the cursor cache, SQLLIB was unable to find a cursor cache entry in the UCE array. This happens only if your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02103	Inconsistent cursor cache (out-of-range CUC ref)

 Cause:	The precompiler generates a unit cursor entry (UCE) array. An element in this array corresponds to an entry in the cursor cache (CUC). While doing a consistency check on the cursor cache, SQLLIB found that the UCE array contains an ordinal value that is either too large or less than zero. This happens only if your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02104	Inconsistent cursor cache (no CUC available)

 Cause:	No cursor cache is available. SQLLIB was unable to allocate enough memory to execute your program.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02105	Inconsistent cursor cache (no CUC entry in cache)

 Cause:	While doing a consistency check on the cursor cache, SQLLIB found that an entry in the cursor cache was missing. This happens only if your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02106	Inconsistent cursor cache (invalid Oracle cursor number)

 Cause:	While carrying out a SQL operation, SQLLIB found an invalid Oracle cursor number.

 Action:	This is an internal error message not usually issued. Call customer support for assistance.

SQL-02107	Program too old for runtime library; please re-precompile it

 Cause:	Your program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.

 Action:	Precompile the program with a newer version of the Oracle Precompilers.

SQL-02108	Invalid descriptor passed to runtime library

 Cause:	While carrying out a SQL operation, SQLLIB found an invalid descriptor.

 Action:	This is an internal error message not usually issued. Call customer support for assistance.

SQL-02109	Inconsistent host cache (out-of-range SIT ref)

 Cause:	SQLLIB found an SIT reference that is either too large or less than zero. This usually happens when your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02110	Inconsistent host cache (invalid SQI type)

 Cause:	SQLLIB found a SQI type value that is either too large or less than zero. This usually happens when your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02111	Heap consistency error

 Cause:	After dynamically allocating or freeing memory, SQLLIB found an error while doing a consistency check on the heap. This usually happens when your program runs out of memory.

 Action:	Allocate more memory to your user session, then rerun the program. If the error persists, call customer support for assistance.

SQL-02112	SELECT..INTO returns too many rows

 Cause:	When you tried to SELECT into a host array, the number of rows returned by the query was larger than the dimension of host array.

 Action:	Either specify a larger array dimension or declare a cursor for use with the FETCH statement.

SQL-02114	Invalid SQL Cursor usage: trying to close a closed cursor

 Cause:	You tried to CLOSE a never OPENed or already CLOSEd cursor or you misspelled the cursor name. Only a currently open cursor can be CLOSEd.

 Action:	Check your spelling of the cursor name and check that the cursor is open before you try to CLOSE it.

SQL-02115	Code interpretation problem -- check COMMON_NAME usage

 Cause:	With Pro*FORTRAN, this error occurs if you specify the precompiler option COMMON_NAME incorrectly. With other Oracle Precompilers, this error occurs when the precompiler cannot generate a segment of code.

 Action:	With Pro*FORTRAN, when using COMMON_NAME to precompile two or more source modules, make sure to specify a different common name for each module. With other Oracle Precompilers, if the error persists, call customer support for assistance.

SQL-02116	FATAL ERROR: Reentrant code generator gave invalid context

 Cause:	The code generator assigned an invalid value to a system-specific parameter.

 Action:	This is an internal error message not usually issued. Call customer support for assistance.

SQL-02117	Invalid SQL Cursor usage: trying to open an opened cursor

 Cause:	When MODE={ANSI | ANSI14 | ANSI13}, you tried to OPEN an already open cursor. However, you can re-Open an already open cursor only when MODE=Oracle.

 Action:	When MODE={ANSI | ANSI14 | ANSI13}, check that you CLOSE a cursor before trying to re-Open it. If you want to reOPEN an already open cursor to avoid reparsing, specify MODE=Oracle.

SQL-02118	Invalid row for a WHERE CURRENT OF operation

 Cause:	You tried to reference a nonexistent row using the CURRENT OF clause in an UPDATE or DELETE statement. This happens when no FETCH has been executed or when FETCH returns a "no data found" error that your program fails to trap.

 Action:	Check that the last cursor operation succeeded and that the current row of the cursor is valid. You can check the outcome of a cursor operation in two ways: implicit checking with the WHENEVER statement or explicit checking of SQLCODE in the SQLCA.

SQL-02122	Invalid OPEN or PREPARE for this database connection

 Cause:	You tried to execute an OPEN or PREPARE statement using a cursor that is currently open for another database connection and therefore cannot be used for this connection.

 Action:	Close the cursor to make it available for this connection or use a different cursor for this connection.

SQL-02123	Application context not found

 Cause:	The application name specified in an EXEC TOOLS GET CONTEXT statement was never stored by an EXEC TOOLS SET CONTEXT statement.

 Action:	Use the EXEC TOOLS SET CONTEXT statement to save the application context for later retrieval.

SQL-02124	NULL value returned by EXEC TOOLS statement

 Cause:	An EXEC TOOLS statement returned a null to a host variable that lacks an indicator variable. This error occurs only when MODE=ANSI. When MODE=Oracle, although the value of the host variable is indeterminate, no error is generated.

 Action:	Associate an indicator variable with every host variable to which nulls might be returned.

SQL-02125	Connect error, can't get error text. See Server Messages & Codes Manual

 Cause:	No connection (not even to the default host) is available, so SQLLIB cannot get the message text for the Oracle error that occurred. However, SQLLIB returns the Oracle error number so that you can look up the message.

 Action:	Lookup up the appropriate message in this Manual.

SQL-02126	Count of array elements cannot be negative (i.e. < 0)

 Cause:	The precompiler found a negative count (< 0) of array elements in the N or F variable of the SQLDA (SQL Descriptor Area, which is used with dynamic SQL Method 4). Before executing the DESCRIBE statement, you must set N to the dimension of the descriptor arrays. After executing the DESCRIBE statement, you must reset N to the actual number of variables DESCRIBEd, which is stored in the F variable.

 Action:	Check that the N and F variables hold positive counts.

SQL-02127	PCC / SQLLIB version mismatch

 Cause:	Your program is linked to an older version of SQLLIB, which is incompatible with this release of the Oracle Precompilers.

 Action:	Relink the program with a newer version of SQLLIB.

 ________________________________________

00250-00300: PCF FIPS Messages

This section contains messages that are generated when you specify the precompiler command-line option FIPS=YES and use an Oracle extension to the ANSI/ISO embedded SQL standard. If you wish your code to comply with the standard, do not use the Oracle extension described in the message.

PCF-00251	SQLCODE is a deprecated feature

PCF-00252	use of the C preprocessor within SQL

PCF-00253	use of the AT clause

PCF-00254	use of the FOR clause

PCF-00255	use of the CONNECT statement

PCF-00256	SQLCODE returns non-standard values

PCF-00257	keyword WORK required after COMMIT

PCF-00258	keyword WORK required after ROLLBACK

PCF-00259	use of RELEASE clause

PCF-00260	use of dynamic SQL

PCF-00261	use of PL/SQL

PCF-00262	use of SQLWARN within WHENEVER clause

PCF-00263	use of NOTFOUND within WHENEVER clause

PCF-00264	use of NOT FOUND within WHENEVER clause

PCF-00265	use of STOP within WHENEVER clause

PCF-00266	use of RAISE within WHENEVER clause

PCF-00267	use of DO within WHENEVER clause

PCF-00268	use of DECLARE TABLE statement

PCF-00269	use of DECLARE DATABASE statement

PCF-00270	use of EXEC SQL INCLUDE

PCF-00271	use of EXEC SQL TYPE

PCF-00272	use of SQL FORMS statement

PCF-00273	use of EXEC ORACLE statement

PCF-00274	invalid datatype

PCF-00275	use of DROP TABLE statement

PCF-00276	use of non-ANSI function


CHAPTER 5. SQL*DBA MESSAGES

This chapter lists messages generated by SQL*DBA. With each message is the likely cause of the event generating the message. If the event generating the message is a problem, then an action is given as a remedy.

The messages listed in this chapter are displayed with the prefix DBA, signifying SQL*DBA, or LCC, signifying the command line. Refer to the Oracle7 Server Utilities User's Guide for more information on and syntax for SQL*DBA.

 ________________________________________

00001-00199: DBA Messages

DBA-00072	Warning: objnam created with compilation errors.

 Cause:	The package, package body, procedure or function could not be created because there code errors.

 Action:	Enter the SHOW ERRORS command and correct the listed compilation errors.

DBA-00073	Warning: objnam created with compilation errors.

 Cause:	The package, package body, procedure or function could not be created because there code errors.

 Action:	Enter the SHOW ERRORS command and correct the listed compilation errors.

DBA-00100	invalid SPOOL file name

 Cause:	When using the SPOOL command, you specified the name of a file that already exists.

 Action:	Specify a valid name for a file that does not currently exist.

DBA-00101	extraneous text at end of command

 Cause:	There were unrecognized commands or other text on the command line.

 Action:	Check the syntax of the command and issue the command again.

DBA-00102	missing LOG keyword

 Cause:	The LOG keyword was missing from the ARCHIVE LOG command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00103	illegal ARCHIVE LOG option

 Cause:	An option specified was not LIST, STOP, START, NEXT, ALL, a number, or a filename in the ARCHIVE LOG command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00104	illegal RECOVER option

 Cause:	An option specified was not DATABASE, MANUAL, UNTIL, TABLESPACE, or DATAFILE in the RECOVER command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00105	invalid INSTANCE name

 Cause:	An invalid SQL*Net CONNECT string was specified for the instance name.

 Action:	Refer to your SQL*Net documentation for a complete description of SQL*Net CONNECT strings.

DBA-00106	invalid ECHO switch

 Cause:	An invalid option for the SET ECHO command was specified.

 Action:	Use either ON or OFF as an option for the SET ECHO command.

DBA-00107	invalid TERMOUT switch

 Cause:	An invalid option for the SET TERMOUT command was specified.

 Action:	Use either ON or OFF as an option for the SET TERMOUT command.

DBA-00108	invalid TIMING switch

 Cause:	An invalid option for the SET TIMING command was specified.

 Action:	Use either ON or OFF as an option for the SET TIMING command.

DBA-00109	invalid CYCLE value

 Cause:	An invalid value for the SET CYCLE command was specified.

 Action:	The SET CYCLE command must use an integer between 1 and 3600.

DBA-00110	illegal SET option

 Cause:	An invalid option for the SET command was specified.

 Action:	Check the syntax of the SET command in the Oracle7 Server Utilities User's Guide and issue the command again.

DBA-00111	illegal SHOW option

 Cause:	An invalid option for the SHOW command was specified.

 Action:	Check the syntax of the SHOW command in the Oracle7 Server Utilities User's Guide and issue the command again.

DBA-00113	invalid PFILE name

 Cause:	The specified PFILE name is not recognized.

 Action:	Specify a legal PFILE name.

DBA-00114	invalid database name

 Cause:	The specified database name is not recognized.

 Action:	Specify a legal database name.

DBA-00115	unexpected end of command

 Cause:	An option was specified without any arguments. For example:

SQLDBA> STARTUP OPEN PFILE

 Action:	Check the syntax of the command and enter the command again with the appropriate arguments for options that require values.

DBA-00116	illegal SHUTDOWN option

 Cause:	An option was specified that was not NORMAL, IMMEDIATE, or ABORT for the SHUTDOWN command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00117	invalid tablespace name

 Cause:	The specified tablespace name was not recognized.

 Action:	Specify a legal tablespace name.

DBA-00118	invalid process identifier or invalid statistics class

 Cause:	Something other than a number for a process identifier, or an invalid class was specified after the MONITOR STATISTICS command.

 Action:	Specify only numbers as process identifiers or specify a valid class for the MONITOR STATISTICS command.

DBA-00119	illegal STARTUP option

 Cause:	An option was specified that was not DBA, PFILE, EXCLUSIVE, SHARED, MOUNT, OPEN, RECOVER, or NOMOUNT for the STARTUP command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00120	invalid STOPONERROR switch

 Cause:	An invalid option was specified for the SET STOPONERROR command.

 Action:	Use either ON or OFF as an option for the SET STOPONERROR command.

DBA-00121	illegal MONITOR option

 Cause:	An illegal option was specified for the MONITOR command.

 Action:	Check the syntax of the MONITOR command in the Oracle7 Server Utilities User's Guide and issue the command again.

DBA-00122	invalid SET numeric parameter

 Cause:	A character or an invalid value was specified when a number was expected as a value for a SET command option.

 Action:	Check the syntax of the command, use an appropriate number for the option and enter the command again.

DBA-00123	invalid tablespace name list

 Cause:	An invalid string was specified as one of the values in the list of tablespaces in the ARCHIVE LOG command. For example, '"' is an invalid string.

 Action:	Check the syntax of the command, use valid tablespace names for all names in the list and enter the command again.

DBA-00124	invalid ARCHIVE destination

 Cause:	The specified ARCHIVE destination was not recognized.

 Action:	Specify a legal ARCHIVE destination.

DBA-00125	integer value overflow

 Cause:	A numeric value was specified that was too large.

 Action:	Use a smaller number.

DBA-00126	invalid VERIFY switch

 Cause:	The VERIFY switch was not recognized.

 Action:	Specify a legal VERIFY switch.

DBA-00127	invalid combination of STARTUP options

 Cause:	The specified options of the STARTUP command cannot be used simultaneously. For example, the following command is not valid:

SQLDBA> STARTUP MOUNT OPEN testdb

 Action:	Check the syntax of the STARTUP command in the Oracle7 Server Utilities User's Guide for options that can be used together.

DBA-00128	invalid DEBUG switch

 Cause:	The DEBUG switch was not recognized.

 Action:	Specify a legal DEBUG switch.

DBA-00129	value out of range (1 - num)

 Cause:	The specified value was out of range. The valid range is given by the error message.

 Action:	Use a number within the range specified by this error.

DBA-00131	invalid ARCHIVE TO device

 Cause:	The specified ARCHIVE TO device was not recognized.

 Action:	Specify a legal ARCHIVE TO device.

DBA-00132	null hostname/password specified

 Cause:	"hostname/password" was not specified.

 Action:	Specify the correct "hostname/password".

DBA-00133	invalid datafile list

 Cause:	An invalid string was entered as one of the values in the list of data files in the ARCHIVE LOG command. For example, '"' is an invalid string.

 Action:	Check the syntax of the command, use valid data filenames for all names in the list and enter the command again.

DBA-00134	invalid AUTORECOVERY switch

 Cause:	An invalid option was specified for the SET AUTORECOVERY command.

 Action:	Use either ON or OFF as options for the SET AUTORECOVERY command.

DBA-00136	bad variable specification

 Cause:	A variable was incorrectly specified using the VARIABLE command.

 Action:	Check the syntax of the command and issue the command again.

DBA-00137	Syntax error in PL/SQL Block

 Cause:	The PL/SQL block contains a syntax error.

 Action:	Correct the syntax error.

DBA-00139	invalid ALTER DATABASE option

 Cause:	The specified ALTER DATABASE option was not recognized.

 Action:	Specify a legal option.

DBA-00140	invalid COMPATIBILITY switch

 Cause:	The specified COMPATIBILITY switch was not recognized.

 Action:	Specify a legal COMPATIBILITY switch.

DBA-00141	invalid RETRIES value

 Cause:	The specified RETRIES value was not recognized.

 Action:	Specify a legal RETRIES value.

DBA-00142	cannot recognize object type, owner or name

 Cause:	The specified object type, owner or name was not recognized.

 Action:	Specify a legal object type, owner or name.

DBA-00143	variable has not been defined

 Cause:	The specified variable was not recognized.

 Action:	Specify an existing variable.

DBA-00144	invalid object type for DESCRIBE

 Cause:	The specified object type was not TABLE, VIEW or PROCEDURE.

 Action:	Check that the object is a table, view, or procedure. If so, check that you specified the correct name and try again. If not, you cannot DESCRIBE the object.

DBA-00145	invalid object name for DESCRIBE

 Cause:	The specified table, view, stored procedure or function was not recognized.

 Action:	Check spelling and specify an existing table, view, stored procedure, or function.

DBA-00146	invalid HISTORY value

 Cause:	The specified HISTORY value was not recognized.

 Action:	Specify a legal HISTORY value.

DBA-00147	invalid LINES value

 Cause:	The specified LINES value was not recognized.

 Action:	Specify a legal LINES value.

DBA-00148	invalid TERM switch (use either PAGE or NOPAGE)

 Cause:	The specified value was not recognized.

 Action:	Specify a legal value.

DBA-00149	invalid SERVEROUTPUT switch

 Cause:	The specified value was not recognized.

 Action:	Specify a legal value.

DBA-00150	invalid FLAGGER switch

 Cause:	The specified value was not recognized.

 Action:	Specify a legal value.

 ________________________________________

00300-00359: DBA Execution

DBA-00300	internal error code, arguments: [num], [str]

 Cause:	An internal error was encountered.

 Action:	Contact customer support with the circumstances leading to the error and the complete set of error messages.

DBA-00301	cannot SET INSTANCE while connected to a database

 Cause:	SET INSTANCE was used while currently connected to a database.

 Action:	To change the current instance, DISCONNECT from the database before using SET INSTANCE.

DBA-00302	not connected to a database

 Cause:	The requested operation required being connected to the database.

 Action:	CONNECT to the database using a valid username and password before retrying the operation.

DBA-00304	input file I/O error [num] - input aborted

 Cause:	A command file used as input to SQL*DBA is corrupt or invalid.

 Action:	Check the file before retrying the operation.

DBA-00305	command size exceeds internal buffer size (num)

 Cause:	The size of the SQL statement exceeds SQL*DBA's buffer size.

 Action:	Shorten the SQL statement by removing extra blanks or by using intermediate statements or views, if necessary.

DBA-00306	monitor cycle interval time out of range (1 - num)

 Cause:	An invalid number was specified for the cycle interval.

 Action:	Enter a number between 1 and 3600 for the cycle interval. The number indicates seconds.

DBA-00307	cannot open spool file name

 Cause:	SQL*DBA tried to open a spool file after the SPOOL filename was specified, but could not open the file. Possible causes are not enough disk space or inadequate privileges to create a file.

 Action:	Determine why SQL*DBA could not create a new file and retry.

DBA-00308	no spool file opened

 Cause:	SPOOL OFF was entered when not currently spooling.

 Action:	To capture session output, use the SPOOL command to open a file, enter the required commands, and close the file with SPOOL OFF.

DBA-00309	cannot close spool file name

 Cause:	SPOOL OFF could not close the currently open spool file.

 Action:	Check for an operating-system reason that the spool file could not be closed.

DBA-00310	cannot open parameter file name

 Cause:	SQL*DBA cannot locate or open the file specified by the PFILE option, because either the file does not exist or SQL*DBA has insufficient privileges to open the file.

 Action:	Check that that the file exists in a location expected by SQL*DBA and can be opened.

DBA-00311	data size exceeds internal buffer size

 Cause:	The results returned by a SQL query exceed the internal SQL*DBA buffer.

 Action:	Use the SET command to increase MAXDATA or decrease ARRAYSIZE.

DBA-00314	unable to attach to default host

 Cause:	The default host has not been set up correctly.

 Action:	Use the SET INSTANCE command with a valid host specification to set up a default host.

DBA-00315	cannot open command file name

 Cause:	SQL*DBA cannot locate the specified command file.

 Action:	Check the file's name and SQL*DBA's access to it before retrying.

DBA-00316	cannot startup while connected to a database

 Cause:	An attempt was made to start up an instance while connected to a database.

 Action:	To start up an instance, first DISCONNECT from the current database.

DBA-00318	SQL*DBA command line error [num]

 Cause:	A syntax or typing error was made while entering a SQL*DBA command line.

 Action:	Check the syntax and try again.

DBA-00319	cannot locate sqldba configuration file name

 Cause:	SQL*DBA cannot open the file specified by the ORA_SQLDBAINIT variable, because either the file does not exist or SQL*DBA has insufficient privilege to open the file.

 Action:	Check that that the specified file exists and can be opened.

DBA-00320	cannot open sqldba configuration file name

 Cause:	File mentioned cannot be opened.

 Action:	Check that that the specified file exists and can be opened.

DBA-00321	instance name too long

 Cause:	An instance name was specified that may be valid, but is too long (exceeds 64 characters).

 Action:	Check the name of the desired instance and try again.

DBA-00322	total size of command line parameters exceeds buffer size

 Cause:	Too many command-line arguments were specified to fit in the SQL*DBA buffer.

 Action:	Specify the arguments over several command lines.

DBA-00325	pfile too large

 Cause:	The file specified using PFILE is too large (exceeds 8K).

 Action:	Reduce the size of the parameter file before specifying it again using PFILE.

DBA-00327	command not available in this mode

 Cause:	A command was specified that is not available in this mode.

 Action:	Switch to a mode where the command is allowed.

DBA-00328	insufficient privilege for this display

 Cause:	An attempt was made to display a MONITOR display without sufficient privileges for the underlying V$ tables.

 Action:	Contact the database administrator to obtain the required privileges.

DBA-00329	insufficient privilege for SHOW SGA

 Cause:	An attempt was made to use SHOW SGA without sufficient privileges.

 Action:	Contact the database administrator to obtain the required privileges.

DBA-00330	logsource name too long

 Cause:	The specified name may be valid, but is too long (exceeds 127 characters).

 Action:	Use a shorter name. For example, relocate the file so that its path name is shorter.

DBA-00331	cannot allocate enough memory for SQL Buffer

 Cause:	There is not enough memory for the current SQL buffer.

 Action:	Use the SET command to reduce MAXDATA. Re-invoke MONITOR FILEIO.

DBA-00336	insufficient privilege for SHOW PARAMETERS

 Cause:	An attempt was made to use SHOW PARAMETERS without sufficient privileges.

 Action:	Contact the database administrator to obtain the required privileges.

DBA-00337	missing instance name

 Cause:	The instance name was not specified in the CONNECT statement.

 Action:	Issue the CONNECT statement again, using the proper instance name.

DBA-00341	'name' is an undefined bind variable

 Cause:	The SQL statement refers to an undefined bind variable.

 Action:	Use the VARIABLE statement to define the bind variable and re-execute the query.

DBA-00342	unable to complete internal login

 Cause:	Some database error occurred that prevented a successful CONNECT INTERNAL. For example, a SHUTDOWN ABORT command was issued. This message is usually followed by another message that indicates the problem.

 Action:	Ensure that the instance is started correctly before trying to CONNECT INTERNAL. You may need to use the STARTUP FORCE command.

DBA-00343	no such parameter

 Cause:	SHOW PARAMETER was given a parameter name that does not exist.

 Action:	Use a different argument to SHOW PARAMETER.

DBA-00344	no items for the requested operation currently exist

 Cause:	A mandatory list element in a dialog contained 0 elements.

 Action:	No action required.

DBA-00345	no user sessions exist

 Cause:	An attempt was made to see if users were connected, but no users were connected.

 Action:	No action required.

DBA-00346	no unresolved in-doubt transactions exist

 Cause:	There are no in-doubt transactions to resolve.

 Action:	No action required.

DBA-00347	no offline tablespaces exist

 Cause:	There are no offline tablespaces to bring online.

 Action:	No action required.

DBA-00348	no online tablespaces exist

 Cause:	There are no tablespaces to take offline. (You cannot take the SYSTEM tablespace offline.)

 Action:	No action required.

DBA-00349	no available rollback segments exist

 Cause:	There are no offline rollback segments to drop.

 Action:	No action required.

DBA-00350	no offline rollback segments exist

 Cause:	There are no offline or partly available rollback segments to bring online.

 Action:	No action required.

DBA-00351	no online rollback segments exist

 Cause:	There are no online rollback segments to take offline.

 Action:	No action required.

DBA-00352	no online tablespaces exist for backup

 Cause:	There are no online tablespaces to backup.

 Action:	No action required.

DBA-00353	no online tablespaces being backed up exist

 Cause:	An attempt was made to end an online tablespace backup, but no tables are being backed up.

 Action:	No action required.

DBA-00354	no offline tablespaces exist

 Cause:	There are no offline tablespaces to recover.

 Action:	No action required.

DBA-00355	no offline data files exist

 Cause:	There are no offline data files to recover.

 Action:	No action required.

DBA-00356	no users exist

 Cause:	There are no named users to alter or drop.

 Action:	No action required.

DBA-00357	no roles exist

 Cause:	There are no roles to alter or drop.

 Action:	No action required.

DBA-00358	no users or roles exist

 Cause:	There are no users or roles to grant privileges and roles to or to revoke privileges and roles from.

 Action:	Create some users before granting roles or privileges.

DBA-00359	monitor already active

 Cause:	An instantiation of this monitor is already active.

 Action:	Cycle through the monitor windows until the monitor becomes visible.

 ________________________________________

00360-00369: DBA Describe Execution

DBA-00360	object to be described does not exist

 Cause:	The object in a DESCRIBE FUNCTION / PROCEDURE / PACKAGE statement does not exist.

 Action:	Check that the object name and owner are correct and that the object exists.

DBA-00361	error during describe

 Cause:	An unexpected error occurred during describe.

 Action:	Check the following error and correct the problem.

DBA-00362	object name is a package; use 'DESCRIBE <package>.<procedure>'

 Cause:	The named object is a package. DESCRIBE does not currently describe an entire package specification.

DBA-00363	procedure or function name not found in the package

 Cause:	The named package does not contain the procedure of function specified.

 Action:	Specify a procedure or function within the package.

DBA-00364	object name is a remote object, cannot further describe

 Cause:	The specified object name contains a database link or is a synonym that resolves to a name with a database link. Such objects cannot currently be described.

 Action:	Specify a local object.

DBA-00365	object name is invalid, it may not be described

 Cause:	The object must have been successfully compiled.

 Action:	Fix any errors in the object and recompile.

DBA-00366	name name is malformed, it must be of form [[a.]b.]c@dblink

 Cause:	The name may have at most three parts and a dblink.

 Action:	Use a well-formed object name.

 ________________________________________

00370-00380: DBA Generic Execution

DBA-00370	mandatory field/list needs to be filled in

 Cause:	You tried to execute the dialog before filling in all required items.

 Action:	 Fill in all required items and retry.

DBA-00371	cannot open/locate input help file, filename

 Cause:	You pressed the Help Key or chose an item from the Help Menu, and the help file was not in the expected location.

 Action:	 Put the help file in the location specified.

DBA-00372	cannot open/locate input index file, filename

 Cause:	You pressed the Help Key or chose an item from the Help Menu, and the help file was not in the expected location.

 Action:	 Put the index help file in the location specified.

DBA-00373	cannot allocate memory of size number from toolkit

 Cause:	You pressed the Help Key or chose an item from the Help Menu, and SQL*DBA ran out of memory.

 Action:	 Exit SQL*DBA, restart and try again.

DBA-00374	could not set file position in filename directly

 Cause:	You pressed the Help Key or chose an item from the Help Menu.

 Action:	 Alternate chosen - no action required.

DBA-00375	Unexpected end of file, filename

 Cause:	You pressed the Help Key or chose an item from the Help Menu, but the help file specified was not installed.

 Action:	 Exit SQL*DBA and install the correct help file.

DBA-00376	mandatory field has to be filled in before navigation is possible

 Cause:	An attempt was made to navigate to the next/previous item without filling a required field.

 Action:	Fill in current field before proceeding to another field.

DBA-00377	mandatory list item has to be selected before navigation is possible

 Cause:	An attempt was made to navigate to the next/previous item without filling a required field.

 Action:	Select a list item before proceeding to another field.

DBA-00378	an item has to be selected before help can be sought for it

 Cause:	Attempted to obtain help before selecting an item.

 Action:	Select an item first and re-execute.

DBA-00379	variable(s) not defined

 Cause:	The SHOW VAR[IABLES] [var-name] command could not find any variables. Either no variables are defined, or you specified a non-existent variable.

DBA-00380	procedural option required for this statement

 Cause:	The attempted statement requires the procedural option.

 Action:	Refrain from using this statement or contact an Oracle sales representative to purchase the procedural option.

DBA-00381	error in the SERVER OUTPUT option

 Cause:	Most likely the package DBMS_OUTPUT is not installed. Check the accompanying messages for more information.

DBA-00382	value var is not a recognizable file name for var

 Cause:	The value for the SQL*DBA initialization variable (which points to the initialization file) is not a recognizable filename.

 Action:	Specify a valid filename or do not define the variable so that no initialization file is run.

DBA-00383	file name var pointed to by var could not be opened

 Cause:	The filename pointed to by the SQL*DBA initialization variable could not be opened.

 Action:	Specify an available file or do not define the variable so that no initialization file is run.

DBA-00384	could not open SQL*DBA resource file, var

 Cause:	The file mentioned could not be opened.

 Action:	Make the file mentioned available for use by SQL*DBA.

DBA-00385	could not locate SQL*DBA resource file, var

 Cause:	The file mentioned could not be located.

 Action:	Check that file exists before rerunning SQL*DBA.

DBA-00386	could not open toolkit resource file, var

 Cause:	The file mentioned could not be opened.

 Action:	Make the file mentioned available for use by SQL*DBA.

DBA-00387	could not locate toolkit resource file, var

 Cause:	The file mentioned could not be located.

 Action:	Check that file exists before rerunning SQL*DBA.

DBA-00388	cannot start SQL*DBA in screen mode; check if values are legal

 Cause:	A variable was not properly set.

 Action:	Check the values listed by SQL*DBA to see if they are correct.

DBA-00389	toolkit resource file name is defined to var

 Cause:	File mentioned could not be located.

 Action:	Check that the file specified exists and can be accessed.

DBA-00390	terminal type var is defined by var

 Cause:	Terminal type specified by may not be valid.

 Action:	Check that the terminal specification is correct.

DBA-00391	value var is defined to var; legal values: var or var

 Cause:	SQL*DBA mode has been incorrectly defined.

 Action:	Define the value of the variable to one of the legal values.

 ________________________________________

00100-00299: LCC Messages

The following messages result from errors occurring in the parameter file. These messages occur when attempting to start an instance.

LCC-00100	internal error, argument num

 Cause:	An internal error was encountered.

 Action:	Call customer support with the circumstances leading to the error and the complete set of messages.

LCC-00111	value not in legal range range

 Cause:	The value of the parameter is outside the valid range.

 Action:	Check the valid range and retry using a new value.

LCC-00112	illegal integer radix specification character

 Cause:	An invalid character was specified.

 Action:	Valid characters are 'd', 'h', 'D', and 'H'.

LCC-00113	integer conversion error or negative integer parameter

 Cause:	A non-integer or negative integer was assigned to an integer parameter.

 Action:	Retry using a valid integer value.

LCC-00114	illegal boolean response parameter

 Cause:	A value other than TRUE or FALSE was specified.

 Action:	Enter a boolean value (either TRUE or FALSE).

LCC-00122	unrecognized keyword keyword

 Cause:	An invalid or misspelled keyword was specified.

 Action:	Re-enter the line.

LCC-00128	invalid positional parameter value val

 Cause:	An invalid positional parameter value was specified.

 Action:	Correct the value.

LCC-00161	Oracle error (possible syntax error) parameter param

 Action:	Correct the error as described in the accompanying message.

LCC-00201	could not open specified filename name

 Cause:	The specified file does not exist.

 Action:	Check the name of the file or create a file by that name before retrying.

LCC-00203	missing keyword keyword

 Cause:	A keyword is expected but none was found.

 Action:	Add a parameter keyword followed by an equal sign and a parameter value.

LCC-00204	left parentheses and no parameter specified parameter

 Cause:	A parameter list was started but no parameter was specified.

 Action:	Add an appropriate list of values and close the parameter list.

LCC-00205	unbalanced parentheses command

 Cause:	An odd number of parentheses was found, indicating that one is missing or one is extra.

 Action:	Retry the statement using the correct number of parentheses.

LCC-00206	positional parameter entered after keyword keyword

 Cause:	An equal sign is missing.

 Action:	Retry the parameter specification using an equal sign between the parameter name and the value.

LCC-00207	nested parentheses encountered command

 Cause:	Only one set of parentheses is permitted.

 Action:	Remove the nested parentheses and retry.

LCC-00208	unexpected keyword in value list keyword

 Cause:	A keyword was found instead of a value.

 Action:	Insert an appropriate value for the keyword.

LCC-00209	missing value for keyword at end of string keyword

 Cause:	A keyword is specified with no value.

 Action:	Specify a valid value for the keyword.

LCC-00210	illegal assignment operator symbol

 Cause:	An attempt was made to use a symbol other than an equal sign to assign a value to a parameter.

 Action:	Retry using an equal sign following the parameter name.

LCC-00211	unexpected delimiter symbol

 Cause:	An invalid delimiter was found between values.

 Action:	A comma or a space is a valid delimiter.

LCC-00212	runaway quoted string command

 Cause:	The parameter value was quoted on the left side but not on the right.

 Action:	Balance the quotation marks.

LCC-00215	parameter files nested too deep command

 Cause:	Too many parameter files have been nested. The maximum number of files that may be nested is three.

 Action:	Reduce the number of nested parameter files.

LCC-00217	failure while processing file parameter

 Cause:	An error occurred while processing a file parameter.

 Action:	Other messages will follow with additional information.

LCC-00218	error in file filename

 Cause:	An error occurred in the particular file.

 Action:	Other messages will follow with additional information.


CHAPTER 6. IMPORT/EXPORT MESSAGES

This appendix lists messages generated by Import/Export. For more information on this utility, refer to the Oracle7 Server Utilities User's Guide.

 ________________________________________

00000-00100: Export Messages

EXP-00000	Export terminated unsuccessfully

 Cause:	Export encountered an Oracle error.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

EXP-00001	data field truncation - column length=num, buffer size=num fetched=num

 Cause:	Export could not fit a column in the data buffer.

 Action:	Record the given size parameters and the accompanying messages and report this as an Export internal error to customer support. (Part of the table has been exported. Export will continue with the next table.)

EXP-00002	error in writing to export file

 Cause:	Export could not write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.

 Action:	Take appropriate action to restore the device.

EXP-00003	no storage definition found for segment (name, num)

 Cause:	Export could not find the storage definitions for a cluster, index, or table.

 Action:	Record the accompanying messages and report this as an Export internal error to customer support.

EXP-00004	invalid username or password

 Cause:	You specified an invalid username or password.

 Action:	Retry with a valid username and password.

EXP-00005	all allowable logon attempts failed

 Cause:	You tried repeatedly to log on with an invalid username or password.

 Action:	Shut down the utility, then restart and retry with a valid username and password.

EXP-00006	internal inconsistency error

 Cause:	Export's data structure was corrupted.

 Action:	Record the accompanying messages and report this as an Export internal error to customer support.

EXP-00007	dictionary shows no columns for name.name

 Cause:	Export failed to gather column information from the data dictionary. The table may have been dropped.

 Action:	Retry the export and if this error recurs, report it as an Export internal error to customer support.

EXP-00008	Oracle error num encountered

 Cause:	Export encountered the referenced Oracle error.

 Action:	Look up the Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

EXP-00009	no privilege to export name's table name

 Cause:	You tried to export another user's table. Only a database administrator can export another user's tables.

 Action:	Ask your database administrator to do the export.

EXP-00010	name is not a valid username

 Cause:	You specified an invalid username.

 Action:	Shut down the utility, then restart and retry with a valid username.

EXP-00011	name.name does not exist

 Cause:	Export could not find the specified table.

 Action:	Retry with the correct table name.

EXP-00012	num is not a valid export mode

 Cause:	You specified an invalid export mode.

 Action:	Retry with a valid export mode.

EXP-00013	respond with either 'Y', 'N', RETURN or '.' to quit

 Cause:	You entered an invalid response.

 Action:	Enter any of the responses shown in the message.

EXP-00014	error on row num of table name

 Cause:	Export encountered an Oracle error while fetching rows.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

EXP-00015	error on row num of table name, column name, datatype num

 Cause:	Export encountered an error while fetching or writing the column. An accompanying message gives more information.

 Action:	Correct the error and try again.

EXP-00016	Oracle error encountered while reading default auditing options

 Cause:	Export encountered an Oracle error while reading the default auditing options (those for updates, deletes, and so on).

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

EXP-00018	datatype (num) for column name, table name.name is not supported

 Cause:	Export does not support the referenced datatype.

 Action:	Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG or RAW).

EXP-00019	failed to process parameters, type 'EXP HELP=Y' for help

 Cause:	You specified invalid command-line parameters.

 Action:	Check the online help screen for the set of valid parameters, then retry.

EXP-00020	failed to allocate memory of size num

 Cause:	Export failed to allocate the necessary memory.

 Action:	Decrease the export buffer size so that less memory is required, or increase the runtime memory size for Export.

EXP-00021	can only perform incremental export in Full Database mode

 Cause:	You specified USER or TABLE mode when doing an incremental export.

 Action:	Specify FULL database mode (FULL=Y) and retry.

EXP-00022	must be SYS or SYSTEM to do incremental export

 Cause:	You don't have the privileges needed to do an incremental export. Only users SYS and SYSTEM can do incremental exports.

 Action:	Ask your database administrator to do the incremental export.

EXP-00023	must be a DBA to do Full Database export

 Cause:	You don't have the privileges needed to do a FULL database export. Only a database administrator can do a FULL database export.

 Action:	Ask your database administrator to do the FULL database export.

EXP-00024	Export views not installed, please notify your DBA

 Cause:	The necessary Export views were not installed.

 Action:	Ask your database administrator to install the required Export views.

EXP-00025	dictionary shows no column for constraint name.num

 Cause:	Export failed to gather column information about the referenced constraint from the data dictionary. The constraint may have been altered.

 Action:	Retry the export and if this error recurs, report it as an Export internal error to customer support.

EXP-00026	only one parameter (TABLES, OWNER, or FULL) can be specified

 Cause:	You specified conflicting export modes.

 Action:	Specify only one parameter and retry.

EXP-00027	failed to calculate Oracle block size

 Cause:	Export failed to calculate the Oracle block size.

 Action:	Report this as an Export internal error to customer support.

EXP-00028	failed to open name for write

 Cause:	Export failed to open the export file for writing. This message is usually followed by device messages from the operating system.

 Action:	Take appropriate action to restore the device.

EXP-00029	incremental export mode and consistent mode are not compatible

 Cause:	You specified both consistent and incremental exports.

 Action:	None. Consistent mode is turned off

EXP-00030	unexpected End-Of-File encountered while reading input

 Cause:	Encountered an EOF while reading the user input.

 Action:	If you are redirecting input to export, check file for errors.

EXP-00031	arraysize not in valid range. Using arraysize=num

 Cause:	The arraysize value specified is not in the valid range.

 Action:	None.

EXP-00032	non-DBAs may not export other users

 Cause:	Only database administrators can export to other users. A non-database administrator attempted to specify owner=user where exporter is not the user.

EXP-00033	Could not find environment character set

 Cause:	The environment character set is missing or incorrectly specified.

 Action:	Ensure that the environment character set is correctly specified and is present.

EXP-00034	error on rowid: file# num block# num slot# num

 Cause:	Identifies the rowid on which an error occurred.

EXP-00035	Cannot specify Rows=N and Compress=Y

 Cause:	Compress applies only to rows of data, so to request compress you must also request rows.

 Action:	Remove the compress parameter or specify Rows=Y.

EXP-00037	Export views not compatible with database version

 Cause:	The Export utility is at a higher version than the database version and is thereby incompatible.

 Action:	Use the same version of Export utility as the database.

 ________________________________________

00000-00100: Import Messages

IMP-00000	Import terminated unsuccessfully

 Cause:	Import encountered an Oracle error.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

IMP-00001	respond with either 'Y', 'N', RETURN or '.' to quit

 Cause:	You entered an invalid response.

 Action:	Enter any of the responses shown in the message.

IMP-00002	failed to open name for read

 Cause:	Import failed to open the export file for reading. This message is usually followed by device message from the operating system.

 Action:	Take appropriate action to restore the device.

IMP-00003	Oracle message code num encountered

 Cause:	Import encountered the referenced Oracle error.

 Action:	Look up the Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

IMP-00004	invalid username or password

 Cause:	You specified an invalid username or password.

 Action:	Retry with a valid username and password.

IMP-00005	all allowable logon attempts failed

 Cause:	You tried repeatedly to log on with an invalid username or password.

 Action:	Retry with valid username and password.

IMP-00006	failed to allocate memory of size num

 Cause:	Import failed to allocate the necessary memory.

 Action:	Decrease the import buffer size so that less memory is required, or increase the runtime memory size for Import.

IMP-00007	must be a DBA to import objects to another user's account

 Cause:	You don't have the privileges needed to import into another user's account. Only a database administrator can import into another user's account.

 Action:	Ask your database administrator to do the import.

IMP-00008	unrecognized statement in the export file: str

 Cause:	Import did not recognize a statement in the export file. Either the export file was corrupted, or an Import internal error has occurred.

 Action:	If the export file was corrupted, retry with a new export file. Otherwise, report this as an Import internal error to customer support.

IMP-00009	abnormal end of export file

 Cause:	The export file is probably from an aborted Export session.

 Action:	If so, retry the export and import. Otherwise, report this as an Import bug and submit the export file that caused this error to customer support.

IMP-00010	not a valid export file, header failed verification

 Cause:	Either the file was not generated by Export, or it was corrupted.

 Action:	If the file was indeed generated by Export, report this an Import bug and submit the export file to customer support.

IMP-00011	formatted table data not currently supported

 Cause:	You tried to import an export file that contains formatted table data. Import only supports export files containing binary table data.

 Action:	Retry using an export file that contains only binary table data.

IMP-00012	invalid export mode (num) in header

 Cause:	The Export mode specified in the export file header is invalid.

 Action:	Check the export file to see if it was corrupted. If it was not, report this as an Import bug and submit the export file to customer support.

IMP-00013	only a DBA can import a file exported by another DBA

 Cause:	You don't have the privileges needed to Import an export file generated by a database administrator. Only a database administrator can import such files.

 Action:	Ask your database administrator to do the import.

IMP-00014	insufficient Oracle privileges to do import

 Cause:	You don't have the privileges needed to do an import. You need at least CONNECT privilege to do an import.

 Action:	Ask your database administrator to grant you the necessary privileges.

IMP-00015	following statement failed because the object already exists: str

 Cause:	Import failed to create an object because it already exists.

 Action:	If you want Import to ignore such errors and import rows even when tables are not created because they already exist, specify 'IGNORE=Y'.

IMP-00016	required character set conversion (type num to num) not supported

 Cause:	Import could not convert the character format of the export file into the native character format.

 Action:	Change the user character set, by setting the NLS_LANG environment variable, to match the character set of the export file.

IMP-00017	following statement failed with Oracle message num: str

 Cause:	Import failed to execute the statement from the export file because of an Oracle error.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

IMP-00018	partial import of previous table complete: num rows imported

 Cause:	A table was only partially imported because of an Oracle error.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

IMP-00019	row rejected due to Oracle message code num

 Cause:	Import encountered the referenced Oracle error while trying to import a row.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action.

IMP-00020	long column too large for column buffer size (num)

 Cause:	The column buffer is too small. Usually occurs when importing LONG data.

 Action:	Increase the insert buffer size 10,000 bytes at a time (for example) up to 66,000 or greater. Use this step-by-step approach because a buffer size that is too large may cause a similar problem.

IMP-00021	operating system error - error code (dec num, hex 0xnum)

 Cause:	An operating-system error has occurred.

 Action:	Look up the referenced message in your operating system-specific Oracle documentation and take appropriate action.

IMP-00022	failed to process parameters, type 'IMP HELP=Y' for help

 Cause:	You specified invalid command-line parameters.

 Action:	Check the online help screen for the set of valid parameters, then retry.

IMP-00023	Import views not installed, please notify your DBA

 Cause:	The necessary Import views were not installed.

 Action:	Ask your database administrator to install the required Import views.

IMP-00024	full import mode, cannot specify FROMUSER or TABLES parameter

 Cause:	You specified parameters that conflict with the import specification FULL=Y.

 Action:	Retry, making sure not to specify FULL=Y.

IMP-00025	for DBA export files, FROMUSER must be specified with TOUSER

 Cause:	When importing a database administrator export file, you specified the TOUSER parameter but not the FROMUSER parameter.

 Action:	Specify the FROMUSER parameter so that Import knows which user's objects to import.

IMP-00027	failed to roll back partial import of previous table

 Cause:	Import encountered an Oracle error while trying to roll back a partial import.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server Messages", and take appropriate action. Then, log on to Oracle and check that the partial import was not committed.

IMP-00028	partial import of previous table rolled back: num rows rolled back

 Cause:	Import encountered an Oracle error while trying to import a table.

 Action:	Look up the accompanying Oracle message in Chapter 2, "Oracle7 Server  Messages", and take appropriate action. Then, if necessary, re-import the table.

IMP-00029	cannot qualify table name by owner (name.name), use FROMUSER parameter

 Cause:	You qualified a table name with the name of its owner, as shown in the following example. This is not allowed.

IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP,SCOTT.DEPT)

 Action:	Use the FROMUSER parameter to specify the table's owner, as shown in the following example:

IMP SYSTEM/MANAGER FROM USER=SCOTT TABLES=(EMP,DEPT)

IMP-00030	failed to create file name for write

 Cause:	Import was unable to create the specified file with write enabled.

 Action:	Check the file name and file system for the source of the error.

IMP-00031	Must specify FULL=Y or provide FROMUSER/TOUSER or TABLE arguments

 Cause:	The database administrator did not specify full or partial import.

 Cause:	database administrator must specify fromuser/touser or table arguments if not a full import.

IMP-00032	SQL statement exceeded buffer length

 Cause:	The buffer was too small for the SQL statement being read.

 Action:	Rerun with a larger buffer. This can also be an indication of a corruption in the import data file

IMP-00033	Warning: Table \"name\" not found in export file

 Cause:	A table name was specified that does not exist in export file.

 Action:	Correct the table specification.

IMP-00034	Warning: FromUser \"name\" not found in export file

 Cause:	The user specified a FromUser name that does not exist in export file.

 Action:	Correct the FromUser specification.

IMP-00035	Warning: ToUser \"name\" not found in export file

 Cause:	The user specified a ToUser name that does not exist in export file.

 Action:	Correct the ToUser specification.

IMP-00036	could not find environment character set

IMP-00037	character set marker unknown

 Cause:	The export file is corrupted.

 Action:	Try to obtain an uncorrupted version of the export file.

IMP-00038	could not find environment character set handle

IMP-00039	no space for owner name in create string

 Cause:	The string is corrupted.

 Action:	Try to obtain an uncorrupted version of the export file.

IMP-00040	Warning:  Statement not executed due to invalid session label

 Cause:	An ALTER SESSION SET LABEL statement in the export file failed because it specified an invalid label. This caused all subsequent CREATE statements until the next valid ALTER SESSION SET LABEL statement to fail. These failed CREATE statements also generate this warning.

 Action:	If the invalid label on the ALTER SESSION SET LABEL statement should be valid, define the label within the operating system and re-execute the import. You would typically want an invalid label to be valid if you are importing an export file from a Trusted Oracle7 database on a different operating system (one that supports different labels).

If you do not want to make the invalid label valid, replace it with a valid label in the export file and re-execute the import.

IMP-00041	Warning: object created with compilation warnings

 Cause:	The object in the SQL statement following this error was created with compilation errors.

 Action:	A warning. The object may have to be recompiled before being used.

IMP-00042	CHARSET used, but the export file has specific character set

 Cause:	The user requested that a specific character set be used to process an export file that has a specific embedded character set ID. The ID in the export file is accurate and should be used.

 Action:	Remove the CHARSET keyword from the command line.

IMP-00043	export file character set inconsistent

 Cause:	The character set of the export file and the environment character set (or the character set specified with the CHARSET keyword) are inconsistent. One character set is ASCII-based while the other is EBCDIC based.

 Action:	Specify the correct character set with the CHARSET keyword.

IMP-00044	unable to allocate enough memory for statement

 Cause:	Import was unable to allocate sufficient memory to read in the specified statement and execute it.

IMP-00045	unexpected character found on line num in mapfile

 Cause:	There is a syntax error while processing the mapfile.

 Action:	Examine the specified line and correct the error.

IMP-00046	must specify MLS_MAPFILE with MLS_LISTLABELS

 Cause:	You did not specify a map file for output of the list labels option.

 Action:	Specify a map file using the MLS_MAPFILE option.

IMP-00047	label string larger than 255 characters found at line num in mapfile

 Cause:	You specified a label string in your mapfile that was too large.

 Action:	Shorten label string to less than 255 characters.

IMP-00048	the MLS_LISTLABELS option cannot be used with this export file

 Cause:	You tried to list the labels on an export file earlier than Release 7.1.

 Action:	Only use the MLS_LISTLABELS option for a Release 7.1 or later export file.

IMP-00049	Unknown language specified in CHARSET

 Cause:	You have listed an unknown language in the CHARSET option.

 Action:	Use a known character set.


CHAPTER 7. SQL*LOADER MESSAGES

This chapter lists messages you might see when using SQL*Loader. SQL*Loader messages take the form:

SQL*Loader-code number: message text

Along with its own messages, SQL*Loader sometimes displays related messages issued by the Oracle7 Server. These messages can be found in Chapter 2, "Oracle7 Server Messages", of this book. For more information on SQL*Loader, see the Oracle7 Server Utilities User's Guide.

 ________________________________________

00100-00199: Command Line

SQL*Loader-100	Syntax error on command line

 Cause:	Possible causes for this error include: placing a positional argument after keyword arguments, misspelling a keyword, not balancing parentheses or quotes, or leaving space between the operator, '=', and an argument.

 Action:	Check the command syntax and your spelling, then retry.

SQL*Loader-101	Invalid argument for username/password

 Cause:	The username/password argument specified on the command line was not recognized. Another argument (not identified by a keyword) could be in the position where username/password is expected.

This error could also result from a spelling mistake. The password, if present, must be separated by a slash (/). No spaces can appear between the slash and username or password. Otherwise, SQL*Loader sees them as multiple arguments.

 Action:	Check the format of the username/password argument, which is the first argument on the command line, if arguments are given without keywords.

SQL*Loader-102	Invalid control file name on command line

 Cause:	The control filename specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place. One possible cause is the existence of a space between username and password. See error 101, above.

 Action:	Check the spelling and position of the arguments on the command line.

SQL*Loader-103	Invalid log file name on command line

 Cause:	The log filename specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the spelling and position of the arguments on the command line.

SQL*Loader-104	Invalid bad file name on command line

 Cause:	The bad filename specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the spelling and position of the arguments on the command line.

SQL*Loader-105	Invalid data file name on command line

 Cause:	The datafile name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the spelling and position of the arguments on the command line.

SQL*Loader-106	Invalid discard file name on command line

 Cause:	The discard filename specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the spelling and position of the arguments on the command line.

SQL*Loader-107	Invalid maximum number of discards

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-108	Invalid number of logical records to load

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-109	Invalid number of logical records to skip

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-110	Invalid maximum number of errors

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-111	Invalid number of rows for bind array or data saves

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-112	Invalid maximum bind array size

 Cause:	The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

 Action:	Check the command line and retry.

SQL*Loader-113	Invalid silent mode option

 Cause:	The only valid options for the SILENT command-line argument are ALL, ERROR, FEEDBACK, or HEADER. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the command line and retry.

SQL*Loader-114	Error in OPTIONS statement

 Cause:	Command line options specified in the control file with the OPTIONS clause were found to be incorrect.

 Action:	Check the format of the OPTIONS clause in the control file.

SQL*Loader-115	Invalid direct path option

 Cause:	The only valid options for the DIRECT command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.

 Action:	Check the command line and retry.

SQL*Loader-116	Error prompting for password

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

 ________________________________________

00200-00299: Control File Syntax

SQL*Loader-200	FORMAT clause should not be present - flat data files only

 Cause:	SQL/DS FORMAT clause is not supported.

 Action:	Remove the FORMAT command from the control file or comment it out.

SQL*Loader-250	Work data sets are not used by SQL*Loader

 Cause:	The control file contains a WRKDDN statement. SQL*Loader ignores this clause.

 Action:	No action required. This is an informational message.

SQL*Loader-251	Sort devices are not used by SQL*Loader

 Cause:	The control file contains a SORTDEVT statement. SQL*Loader ignores this clause.

 Action:	No action required. This is an informational message.

SQL*Loader-252	Sort data sets are not used by SQL*Loader

 Cause:	The control file contains a SORTNUM statement. SQL*Loader ignores this clause.

 Action:	No action required. This is an informational message.

SQL*Loader-253	DB2 partition number has no significance -- ignored

 Cause:	The control file contains a PART statement. SQL*Loader ignores this clause.

 Action:	No action required. This is an informational message.

SQL*Loader-254	Cannot have DISCARDFILE specs here when multiple data files

 Cause:	The control file contains multiple datafiles, and a DISCARDFILE statement was found below the RESUME clause.

 Action:	Move the DISCARDFILE statement above the RESUME clause, so it is adjacent to one of the INFILE statements.

SQL*Loader-255	Log file for error recovery not used by SQL*Loader

 Cause:	The control file contains a LOG statement. SQL*Loader ignores this clause.

 Action:	No action required. This is an informational message.

SQL*Loader-256	SORTED INDEXES option allowed only for direct path

 Cause:	The control file contains a SORTED INDEXES statement, but it was not used in a direct load.

 Action:	Specify a direct load with DIRECT=TRUE on the command line, remove the statement from the control file or comment it out.

SQL*Loader-257	Index name specified in SORTED INDEXES does not exist on table name

 Cause:	A non-existent index was specified in the SORTED INDEXES clause. Either the index doesn't exist, or its name was misspelled.

 Action:	Create the index, change the spelling, remove the specification, or comment it out.

SQL*Loader-258	Maximum number of sorted indexes (num) exceeded on table name.

 Cause:	There are too many indexes in the SORTED INDEX clause. The message displays the maximum number that are permitted.

 Action:	Reduce the number of indexes specified in the SORTED INDEX clause or use the conventional path instead of the direct path.

SQL*Loader-259	Could not escalate DDL share lock to exclusive on table name

 Cause:	This error occurs when another user has a parse lock on the table, for example, when another user is doing a select on the table. The parse lock should clear momentarily.

 Action:	Give the parse lock a chance to clear and then retry or else use the conventional path.

SQL*Loader-260	Index num is in an invalid state

 Cause:	The specified index is in an invalid state.

 Action:	Drop and re-create the index.

SQL*Loader-262	PIECED keyword (on column num) allowed only when path is direct

 Cause:	You cannot use the PIECED keyword in a conventional path load.

 Action:	Remove the PIECED keyword or use the direct path.

SQL*Loader-263	PIECED column num must be last specified column in table name

 Cause:	You specified as PIECED a column that is not the last column.

 Action:	Remove the PIECED keyword or place the column last.

SQL*Loader-264	File mode token name parsed but ignored

 Cause:	An obsolete file mode token was used in the control file.As of version 1.1, the file-processing options string is used to control file processing, rather than keywords like STREAM, RECORD, FIXED, and VARIABLE.

 Action:	No action required. This message is informational. Removing the obsolete keywords will eliminate the message without changing the way in which the datafile is processed.

SQL*Loader-265	Unable to get default character set name

 Cause:	SQL*Loader was unable to locate the default character set name for your environment.

 Action:	 Supply a character set name with the CHARACTERSET keyword.

SQL*Loader-266	Unable to locate character set handle for name

 Cause:	SQL*Loader could not find the character set handle for the named character set.

 Action:	Correct the character set name.

SQL*Loader-267	Control file must be first data file

 Cause:	The control file is specified as containing data, but other datafiles were named first.

 Action:	Move the INFILE "*" clause so that it is the first datafile declared in the control file.

SQL*Loader-268	UNRECOVERABLE keyword may be used only in direct path

 Cause:	You can only specify the UNRECOVERABLE keyword in the direct path.

 Action:	Use the direct path or remove the keyword. (Conventional path loads are always recoverable).

SQL*Loader-269	Null string not allowed as clause comparison text

 Cause:	A clause is being compared to a null string.

 Action:	Modify the clause to compare to at least one character.

SQL*Loader-270	Table name has index defined upon it.

 Cause:	Parallel load was specified into a table that has an index defined for it.

 Action:	Drop the index or indexes defined for the table or do not use parallel load.

SQL*Loader-271	Not a parallel load. Table level OPTIONS statement ignored.

 Cause:	A table-level OPTIONS statement was specified for a non-parallel load.

 Action:	Remove the OPTIONS statement from the control file.

SQL*Loader-272	Table level OPTIONS statement ignored.

 Cause:	In the parallel load option, the file specified on the command line overrides the file specified in the control file.

 Action:	Remove the OPTIONS statement from the control file.

 ________________________________________

00300-00399: Control File Parsing

SQL*Loader-303	Non-hex character encountered where hex char expected

 Cause:	A non-hexidecimal character was found in a hexidecimal string.

 Action:	Change it to the intended hexidecimal character.

SQL*Loader-304	Illegal combination of non-alphanumeric characters

 Cause:	The control file contains a combination of non-alphanumeric characters that SQL*Loader does not recognize. For example, the combination != is recognized as "not equal," but the combination =! is not valid.

 Action:	Remove the unrecognized characters from the control file.

SQL*Loader-305	More than one end of file character encountered

 Cause:	The file contains multiple end-of-file marks.

 Action:	Remove the excess end of file characters.

SQL*Loader-306	Token longer than max allowable length of num characters

 Cause:	The control file contains a single word or combination of characters (a token) that is longer than the maximum permissible value. The maximum possible value is shown. This error could result from missing spaces, so that multiple tokens are joined.

 Action:	Check that you are executing the proper control file. Separate tokens, if joined, or shorten the token.

SQL*Loader-307	Warning: conflicting lengths num1 and num2 specified for column name

 Cause:	The control file specifies two different lengths for the named column. There are three ways to specify the length of a field:

•	with the POSITION keyword: POSITION(1:3)

•	with the length specifier: CHAR(6)

•	with the implied length of a datatype, for example, INTEGER

A conflict could occur between any two of these specifications (or among all three, but only two are shown).

A common cause of this error is the specification of some numeric datatype, such as INTEGER, when the numeric external form is intended (INTEGER EXTERNAL). The external form consists of character data, so it is considerably longer than the numeric form, which consists of binary data.

 Action:	No action is required necessarily, because SQL*Loader uses only one of the lengths. Check the log file under the heading "Len" in the table-description section to see which length was used.Adjusting the control file to produce uniform length specifications will remove the warning.

SQL*Loader-308	Optional SQL string of column name must be in double quotes.

 Cause:	A SQL string was found that was not quoted or in single quotes.

 Action:	Use double quotes for the SQL string, rather than single quotes.

SQL*Loader-350	Syntax error at line num

 Cause:	num identifies the line in the control file at which the error occurred. This message is followed by another of the form:

Expecting str1, found str2

where str1 is a description of what SQL*Loader expected in the control file, and str2 is what was found. Then SQL*Loader displays the offending line from the control file, indicating the location of the error in the line by a carat (^) or an asterisk (*). An example follows:

SQL*Loader-350: Syntax error at line 28

 Expecting column name, found keyword CHAR

 col3 ENCLOSED BY '"', CHAR ENCLOSED "'",

 Action:	Compare the control file's syntax against the syntax diagrams in the Oracle7 Server Utilities User's Guide and make any necessary corrections.

 ________________________________________

00400-00499: Columns

SQL*Loader-401	End field position num must be greater than or equal to start num

 Cause:	The named field contains a (start:end) clause in which end is less than start.

 Action:	Modify the clause so that end is greater than or equal to start.

SQL*Loader-402	Unable to determine length of column name.name from specification

 Cause:	The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a POSITION clause.

 Action:	If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form:

POSITION(start:end)

A length can also specified after the datatype, as in:

INTEGER EXTERNAL (6)

Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.

SQL*Loader-403	Referenced column name not present in table name

 Cause:	The named column is not present in the given table.

 Action:	Correct the column name or table name.

SQL*Loader-404	Column name present more than once in table name

 Cause:	The named column is specified more than once in a single INTO TABLE statement.

 Action:	Remove the extraneous column specification.

SQL*Loader-405	Need termination delim with optional enclosure delim: column name.name

 Cause:	The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.

 Action:	Specify a termination delimiter or make the enclosure delimiters non-optional.

SQL*Loader-406	If data is all generated, number to load cannot beALL

 Cause:	When only generated data is loaded, a number to load must be given so SQL*Loader knows when to stop.

 Action:	Specify a number to load.

SQL*Loader-407	If data is all generated, number to skip is meaningless

 Cause:	When all data is generated, no file is read, and there are no records to skip.

 Action:	Remove the number to skip.

SQL*Loader-408	Physical record stack overflow

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-409	Number to skip must be table-level, not load-level on continued loads

 Cause:	The SKIP parameter was specified on the command line or in the OPTIONS statement, but the load was specified as continued with CONTINUE_LOAD.

When a multiple table direct load is interrupted, it is possible that a different number of records were loaded into each table.As a result, the number of records to skip must be specified for each table when continuing the load. In this case, the load is specified as continued with the CONTINUE_LOAD statement, and the number of records to skip is given in each INTO TABLE statement.

See also messages 410 and 411 for more information.

 Action:	Check the log file to determine the appropriate number of records to skip for each table and specify this number in the INTO TABLE statement for each table in a continued load or with the command-line SKIP parameter in a standard load.

SQL*Loader-410	Number to skip must be load-level, not table-level

 Cause:	A SKIP clause was found in the INTO TABLE statement of a standard (non-continued) load.

In a standard load, specified with LOAD DATA, it is not possible to skip a different number of records for each table. The number of records to skip must be specified for the entire load by using the SKIP parameter on the command line or in the OPTIONS clause.

If table-level skip is required, because a different number of records were loaded into each table (only possible for a multiple table direct load), then specify a continued load with the CONTINUE_LOAD statement.

See also messages 409 and 411 for more information.

 Action:	If the load was not a multiple-table, direct path load, then move the SKIP clause from the INTO TABLE statements to the command line or to the OPTIONS clause. Otherwise, specify the load as continued with CONTINUE_LOAD.

SQL*Loader-411	Only a direct path load may be continued

 Cause:	The load is specified with CONTINUE_LOAD, but DIRECT=FALSE. CONTINUE_LOAD is only possible for a direct path load and is only necessary for a multiple-table direct path load when a different number of records have been loaded into each table.

See also messages 409 and 410 for more information.

 Action:	If CONTINUE_LOAD is necessary, specify a direct load and put the number of records to skip in each INTO TABLE statement. Otherwise, use the command line or OPTIONS clause to specify the number of records to skip and use LOAD DATA instead of CONTINUE_LOAD.

SQL*Loader-412	More columns specified for table name than the maximum (num)

 Cause:	More columns were specified for the table than the maximum number allowed by the database.

 Action:	Remove the extraneous columns.

SQL*Loader-413	Maximum number of constraints (num) exceeded on table name

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-414	Maximum number of triggers (num) exceeded on table name

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-415	Unimplemented database column type num on column name

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-417	SQL string (on column name) not allowed in direct path

 Cause:	Because the direct path bypasses SQL processing, the SQL string cannot be used.

 Action:	Remove the SQL string or use the conventional path.

SQL*Loader-457	Comparison text ('str') of CONTINUEIF LAST must have length 1 not num

 Cause:	The comparison text is too long. It can only be one character.

 Action:	Reduce the comparison text to one character.

SQL*Loader-458	Comparison text of CONTINUEIF LAST must be non-whitespace

 Cause:	The comparison text is a whitespace character (blank or tab).

 Action:	Change the comparison text to a non-whitespace character.

 ________________________________________

00500-00599: File I/O and Operating System

SQL*Loader-500	Unable to open file (name)

 Cause:	SQL*Loader could not open the named file.

 Action:	Check the operating system messages below this one in the log file.

SQL*Loader-501	Unable to read file (name)

 Cause:	 SQL*Loader could not read the named file.

 Action:	Check the operating system messages below this one in the log file.

SQL*Loader-502	Unable to open log file for write (name)

 Cause:	 SQL*Loader could not open the named file.

 Action:	Check that the file location is specified correctly and that you have write privileges for the file.

SQL*Loader-503	Error appending extension to file (name)

 Cause:	SQL*Loader could not append the default extension to create the filename. The given name could be too long or contain illegal characters.

 Action:	Check the specified filename.

SQL*Loader-504	Error skipping records in file (name)

 Cause:	SQL*Loader could not open the file or could not read from it.

 Action:	Check that the file is where it is expected and that you have read access.

SQL*Loader-506	Unable to open bad file (name)

 Cause:	SQL*Loader could not open the named file.

 Action:	Check the errors below it in the log file for more information.

SQL*Loader-507	Unable to open discard file (name)

 Cause:	SQL*Loader could not open the named file.

 Action:	Check the errors below it in the log file for more information.

SQL*Loader-510	Physical record in data file (name) is longer than the maximum (num)

 Cause:	The datafile has a physical record that is too long.

 Action:	Use CONCATENATE or CONTINUEIF. Break up the physical records.

SQL*Loader-511	Unable to initialize read functions

 Cause:	SQL*Loader could not initialize the read functions.

 Action:	 See the messages below it in the logfile.

SQL*Loader-512	Unable to free read buffer

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-513	Unable to close file (name)

 Cause:	SQL*Loader could not close the named file.

 Action:	Check the errors below it in the log file for more information.

SQL*Loader-514	Error getting elapsed time

 Cause:	SQL*Loader could not get the elapsed time from the system.

 Action:	No action required.

SQL*Loader-515	Error getting CPU time

 Cause:	SQL*Loader could not get the CPU time from the system.

 Action:	No action required.

SQL*Loader-516	Control file (name) has no contents

 Cause:	The named file was found to be empty.

 Action:	Check that the intended file was referenced and that it is not empty.

SQL*Loader-517	Error decomposing file name (name)

 Cause:	SQL*Loader could not break down the filename into its component parts.

 Action:	Check the filename for illegal characters.

SQL*Loader-518	Error reassembling file name (name)

 Cause:	SQL*Loader could not put the filename back together again from its components.

 Action:	Check the filename for illegal characters.

SQL*Loader-519	Error num writing to file (name)

 Cause:	SQL*Loader could not write to the named file. The error number displayed in the message is the one returned by the C language FWRITE function. You can get more information by accessing a C language reference manual for your system.

 Action:	Check that the file's location is where you expect it to be and that you have write privileges on it. Be sure that you have disk space and that you have not exceeded your disk quota.

 ________________________________________

00600-00619: Errors Occurring During the Load

SQL*Loader-600	Specified max. bind size num bytes must be num bytes to hold 1 row

 Cause:	The space needed to contain a single row is longer than the specified bind size.

 Action:	One solution is to increase the amount of space allowed for the bind array, using the BINDSIZE keyword on the command line or in the OPTIONS statement in the control file.

If the row contains VARCHAR or VARGRAPHIC data, specifying a maximum length for these fields can also reduce the amount of memory needed to buffer a row.

SQL*Loader-601	For INSERT option, table must be empty. Error on name

 Cause:	A non-empty table is being loaded with the INSERT option.

 Action:	If you want to empty the old table and store the new data in its place, use the REPLACE keyword. If you want to leave the table's contents intact and add the new data to it, use the APPEND keyword.

SQL*Loader-602	Maximum converted length num of column name.name is too big for bind array

 Cause:	The named column cannot undergo the specified character set conversion and still be placed in a contiguous piece of memory on your system.

 Action:	Specify a shorter data column or eliminate the conversion.

SQL*Loader-603	Maximum length num of column name.name is too big for bind array

 Cause:	The named column cannot be put in a contiguous piece of memory on your system.

 Action:	Specify a shorter data column.

SQL*Loader-604	Error occurred on an attempt to commit

 Cause:	An error occurred while trying to commit changes to the database.

 Action:	Look at the message listed below this one in the log file for more information.

SQL*Loader-605	Non-data dependent Oracle error occurred load discontinued

 Cause:	An error occurred that is independent of the data. For example, an out-of-space condition. Because all further rows will be rejected, the load is discontinued. (If the error were data-dependent, then other rows might succeed.)

 Action:	See the errors below this one in the log file for more information.

SQL*Loader-606	Synonym name refers to an object on a remote database

 Cause:	The synonym specified in the INTO TABLE clause in the SQL*Loader control file specifies a remote object via a database link. Only a synonym for an existing local table can be specified in the INTO TABLE clause.

 Action:	Ensure that a local table name or a synonym for a local table is fully specified in the INTO TABLE clause. The table must already exist.

 ________________________________________

00620-00649: Formatting

These are errors in data described by free-format (TERMINATED, ENCLOSED) statements in the control file. Format errors occur when the data does not meet format specifications and might cause the loading of incorrect data into the database.A format error causes the record to be written to the bad file because an attempt to insert data failed.

SQL*Loader-620	Initial enclosing character not found

 Cause:	A mandatory initial enclosure delimiter was not present. Either it is missing on the current field, or the previous field is missing an identical closing delimiter.

 Action:	Supply the missing delimiters.

SQL*Loader-621	Field in data file exceeded maximum specified length

 Cause:	Delimited data was specified with a maximum length, and the data value exceeded that length.

 Action:	Check for missing delimiters and/or shorten the field.

SQL*Loader-622	Column not found before end of logical record(use TRAILING NULLCOLS)

 Cause:	The logical record ended before all specified fields were found.

 Action:	If the missing fields should be loaded as null, use the TRAILING NULLCOLS clause. Otherwise, correct the data.

SQL*Loader-623	Logical record ended -- second enclosure character not present

 Cause:	The logical end of record occurred before a second enclosure delimiter was found.

 Action:	Supply the missing delimiter.

SQL*Loader-624	No terminator found after TERMINATED and ENCLOSED field

 Cause:	No termination delimiter was found after the enclosed field ended.

 Action:	Supply the missing termination delimiter.

SQL*Loader-625	Multibyte character error in control file

 Cause:	Incomplete multibyte character strings were found in the control file.

 Action:	Edit the control file to check that all multibyte character data is valid.

SQL*Loader-640	Variable length field was truncated.

 Cause:	The end of the logical record was encountered before the end of a variable length field. The length of each variable-length field is embedded in the field, so SQL*Loader knows that more data should have been present.

 Action:	Check the data for inadvertent truncation and verify the control file specifications against the log file -- the field may be starting in the wrong place.

SQL*Loader-641	Invalid zoned decimal nibble.

 Cause:	Each byte (character) in a zoned decimal field contains two 4-bit nibbles. Each nibble must have a valid value.

 Action:	Check the control file's specifications against the log file to ensure that the field location was specified correctly. Check the contents of the field.

SQL*Loader-642	Relative start position > absolute field end position

 Cause:	A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.

 Action:	Check that you are not missing a delimiter and that the values of n and y are correct.

 ________________________________________

00700-00799: Fatal Errors

SQL*Loader-700	Out of memory while performing essential allocations [num]

 Cause:	SQL*Loader could not allocate the memory it needs.

 Action:	Check your operating system and process memory. Increase memory available to SQL*Loader if possible. Otherwise, wait until more memory becomes available.

SQL*Loader-701	Out of memory while allocating bind array

 Cause:	SQL*Loader could not allocate memory for the bind array.

 Action:	Check your operating system and process memory. Increase memory if possible. Otherwise, wait until more memory becomes available.

SQL*Loader-702	Internal error - str

 Cause:	An internal error has occurred.

 Action:	Make a note of the message and contact customer support.

SQL*Loader-703	Internal error: argument num

 Cause:	An internal error has occurred.

 Action:	Make a note of the number and contact customer support.

SQL*Loader-704	Internal error:  str [num]

 Cause:	An internal error has occurred.

 Action:	Make a note of the message and the number, then contact customer support.

SQL*Loader-705	Internal error

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

SQL*Loader-706	Bad argument to ulerr [num]

 Cause:	An internal error has occurred.

 Action:	Contact customer support.

 ________________________________________

00900-00949: Direct Path Preparation

SQL*Loader-901	Error logging on to Oracle

 Cause:	The direct path mode could not log on to Oracle.

 Action:	Ensure that your instance is up and running. Check the Oracle messages below this one in the log file for more information.

SQL*Loader-902	Error opening cursor:  [num]

 Cause:	An internal error has occurred.

 Action:	Check the Oracle messages below this one in the log file and contact customer support.

SQL*Loader-903	Database must be at least version num for direct path

 Cause:	The direct path mode is being used with an incompatible database.

 Action:	Upgrade your database to the specified version or else use the conventional path.

SQL*Loader-904	You cannot use the direct path when linked with v5 of the database

 Cause:	The direct path mode is being used after SQL*Loader has been linked with a Version 5 database.

 Action:	Use the conventional path.

SQL*Loader-905	Error parsing SQL statement for upi:  [num]

 Cause:	Header message.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-906	Error executing SQL statement for upi: [num]

 Cause:	An internal error has occurred.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-907	Error parsing insert statement on table name

 Cause:	Loader cannot insert into the specified table.

 Action:	Check that the table exists and that you have insert privileges on it.

SQL*Loader-908	Unable to lock table name in exclusive mode due to Oracle error num

 Cause:	SQL*Loader could not get a DML exclusive lock on the table it needed.

 Action:	Check the message below this one in the log file for more information. Find the object number of your table in the catalog view USER_OBJECTS. Use the SQL*DBA MONITOR LOCK command to list all processes with outstanding locks. Identify the process that has the lock on your table. Then use the MONITOR PROCESS command to find out who is connected as the Oracle process holding the lock and get them to relinquish it. Or, simply wait and retry.

SQL*Loader-909	Loader views must be loaded (as SYS) for direct path to be used

 Cause:	Database views required for the direct path mode are not present.

 Action:	The Oracle7 Server Administrator's Guide details how to run the required scripts as user SYS for loading the required views.

SQL*Loader-910	Error binding input variables of upi: [num]

 Cause:	Header message.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-911	Error defining output variables for upi: [num]

 Cause:	Header message.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-912	Tables loaded through the direct path may not be clustered

 Cause:	A direct path mode load is being used to put data into a clustered table.

 Action:	Use the conventional path.

SQL*Loader-913	Error fetching results of select statement (upi): [num]

 Cause:	Header message.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-914	Error locking table name in exclusive mode

 Cause:	The direct path mode could not lock the named table.

 Action:	Check the message below this one in the log file for more information. Check that you have the necessary privileges.

SQL*Loader-915	Error closing cursor:  [num]

 Cause:	Header message.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-916	Error checking path homogeneity

 Cause:	To do a direct load when the front end and back end of the database are on separate hardware systems, the systems must be identical, using the same machine, operating system, and character set. This error occurs when SQL*Loader detects a difference between the systems that will prevent a direct load from operating properly.

 Action:	Use a conventional load for this configuration.

SQL*Loader-917	Error parsing insert statement on table name

 Cause:	For security purposes, SQL*Loader generates a SQL INSERT statement and uses it to verify that the load specifications make sense and that you have the proper access privileges. This message occurs when the INSERT statement cannot be used.

 Action:	Check the Oracle messages below this one in the log file for more information. Check that all the columns to be loaded exist and that you have insert privileges on the table. Finally, check any SQL strings defined for the named table.

SQL*Loader-918	The catalog must be loaded (as SYS) for SQL*Loader to be used.

 Cause:	The catalog is not loaded.

 Action:	Logon as user SYS and load the Oracle7 catalog and the views in the script ULVIEW.SQL.

SQL*Loader-919	Error during upi fetch:  [num]

 Cause:	An internal error has occurred.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-920	Error deleting data from table name (due to REPLACE keyword)

 Cause:	The REPLACE option is specified in the control file but SQL*Loader could not delete the data from the table.

 Action:	Check the message below this one in the log file for more information.

SQL*Loader-921	NOT NULL column name.name has a NULLIF clause

 Cause:	A column that is NOT NULL in the database has a NULLIF clause in the control file.

 Action:	Remove the NULLIF clause.

SQL*Loader-922	NOT NULL column name.name has a default if clause which may evaluate to null

 Cause:	A column that is NOT NULL in the database has a NULLIF clause that may evaluate to null.

 Action:	Remove the NULLIF clause.

SQL*Loader-923	Column name in table name is NOT NULL but is not being loaded

 Cause:	A column that is NOT NULL in the database is not being loaded, so every row will be rejected.

 Action:	Load the column.

SQL*Loader-925	Error while str

 Cause:	An internal error has occurred.

 Action:	Check the message below this one in the log file for more information. The table or column referenced may not be accessible.

SQL*Loader-926	OCI error while executing name for table name

 Cause:	An OCI error has occurred.

 Action:	Check the message below this one in the log file for more information. The table or column referenced may not be accessible.

SQL*Loader-927	Table name does not exist

 Cause:	SQL*Loader could not find the named table. The specified table may not exist. On some systems, you will also get this message if you do not have the necessary privileges.

 Action:	Check that that the table exists, its name is spelled properly, and that you have the necessary privileges on it.

SQL*Loader-928	Column name.name does not exist

 Cause:	SQL*Loader could not find the named table.

 Action:	Check that the column exists, its name is spelled properly, and you have the necessary privileges on it.

SQL*Loader-929	Error parsing insert statement for table name

 Cause:	The table's insert statement caused a parse error.

 Action:	If you used any SQL strings, check them.

SQL*Loader-930	Error parsing insert statement for column name

 Cause:	The named column's INSERT statement caused a parse error.

 Action:	Check the message below this one in the log file for more information. Check the SQL string used for this column.

SQL*Loader-931	OCI error while binding variable for column name

 Cause:	An OCI error has occurred.

 Action:	Check the errors below it for more information. The SQL string for this column may be in error.

SQL*Loader-932	Could not truncate table name

 Cause:	Truncation of the table was attempted and failed.

 Action:	Check the following errors for more information. Truncation due to referential constraints should not occur.

SQL*Loader-933	Specified file name not part of database

 Cause:	The specified filename to load the table is not a database file.

 Action:	Specify a valid datafile.

SQL*Loader-934	Incorrect data file name specified for table tabnam

 Cause:	A datafile name was given to load the table is not part of the tablespace in which the table resides.

 Action:	Specify a valid datafile.

SQL*Loader-935	Error verifying required option for parallel load.

 Cause:	An error was encountered because a required option was not found or was invalid.

 Action:	Correct the problem as described in the accompanying Oracle message.

 ________________________________________

00950-00999: Direct Load Error-Header Messages

These messages are informational. They describe the kind of error that has occurred. Check the messages below them in the log file for more detailed information.

SQL*Loader-950	Error shipping data structures across 2-task

SQL*Loader-951	Error calling once/load initialization

SQL*Loader-952	Error calling once/data file initialization

SQL*Loader-953	Error shipping read buffer across 2-task

SQL*Loader-954	Error shipping index to read buffer across 2-task

SQL*Loader-955	Error calling col array build, block formatter

SQL*Loader-956	Error calling once/data file finishing

SQL*Loader-957	Error shipping text string across 2-task

SQL*Loader-958	Error popping data relocation address stack

SQL*Loader-959	Error shipping buffer across 2-task

SQL*Loader-960	Error escalating DDL share lock to exclusive

SQL*Loader-961	Error calling once/load finishing

SQL*Loader-962	Error setting user-side Ctrl-C handler

SQL*Loader-963	Error clearing user-side Ctrl-C handler

SQL*Loader-964	Error logging off Oracle

SQL*Loader-965	Error num disabling constraint name of table name

SQL*Loader-966	Error num disabling all triggers on table name

SQL*Loader-967	Oracle error: str

SQL*Loader-968	Error disconnecting from Oracle

SQL*Loader-969	Error performing file name translation on kernel side


CHAPTER 8. SQL*MODULE MESSAGES

This chapter lists messages you might see when using SQL*Module. For more information on SQL*Module, see the SQL*Module User's Guide and Reference. SQL*Module issues error messages like the following:

MOD-F-0037: End of SQL statement or PL/SQL block not found

The error code consists of a prefix, severity code, and sequence number. The prefix MOD shows that the error was issued by SQL*Module. There are four severity codes; the following table gives their meanings:

Code	Meaning

------------------------------------------------------------------------

W   	Warning--despite an error, a compilable output file

was created.

S   	Severe error--despite an error, an output file was

created. However, it might not be compilable. (Note:

the file is created only if RPC_GENERATE=NO.)

F      	Fatal error--no output file was created because of an

internal problem or because a resource (such as

memory) was unavailable or ran out.

U   	Unrecoverable error--no output file was created be-

cause an input requirement was not met.

In addition to the errors generated by SQL*Module, you might encounter errors at runtime. These errors have the prefixes SQL- and ORA-. SQL errors are generated by the routines in the SQLLIB library; ORA errors are generated by the server.

 ________________________________________

00000-00100: SQL*Module Messages

MOD-00009	Unable to open input file name

 Cause:	SQL*Module is not able to open the input file that you specified with the INAME option. This error can result from any of the following:

•	The file does not exist.

•	The file exists, but in a directory not on the path specified.

•	You do not have the permissions or access rights required to read the file.

 Action:	Check that you have the appropriate permission to read the file. Check that you have specified the name and directory hierarchy correctly. Rerun the compiler.

MOD-00010	Unable to open listing file name

 Cause:	SQL*Module is not able to create the listing output file. This usually happens when you do not have write permissions on the current directory or on the directory specified for the LNAME option. It can also happen if the name or directory path is not legal or a directory on the path does not exist.

 Action:	Check your permissions on the specified path and file, or on the current directory if you do not use the LNAME option.

MOD-00011	Unable to open output file name

 Cause:	SQL*Module is not able to create an output file, such as the specification file or the output code file. This usually happens when you do not have write permissions on the current directory or on the directory specified for the ONAME or SNAME options. It can also happen if the name or directory path is not legal or a directory on the path does not exist.

 Action:	Check your permissions on the specified path and file, or on the current directory if you do not use the ONAME or SNAME options.

MOD-00012	Encountered the symbol name when expecting one of the following...

 Cause:	This is caused by a syntax error in the Module Language file. For example, if you have the SQL statement

SELECT ename INTO :name FORM emp WHERE ...

in a module procedure, you get the message:

MOD-S-00012, Encountered the symbol "FORM" where expecting one of the following:

, : INDICATOR FROM

This message is not triggered by semantic errors. See MOD-0075 on page 8 - 9.

 Action:	Correct the syntax error, then recompile.

MOD-00015	Oracle Error: ora-nnnnn

 Cause:	This message results from an internal error: an invalid value for the mode of a bind variable.

 Action:	Contact customer support.

MOD-00016	Out of space - unable to allocate num bytes

 Cause:	SQL*Module could not allocate enough memory to run or to perform some required action.

 Action:	Try killing some non-essential processes, then rerunning SQL*Module. On some operating systems, you might have a quota for the amount of memory your processes can allocate. See your system administrator. If necessary, get more memory for your machine.

MOD-00017	Unable to connect to Oracle with conn_str:username/password. Oracle error number ora-nnnnn

 Cause:	The database connection or the username or the password that you specified was not correct. This message can result from an incorrect command-line specification or an incorrect specification of the username and/or password in the module AUTHORIZATION clause.

 Action:	Look up the error number in the Oracle7 Server Messages and Codes manual for more specific information on the failure. Correct the identifiers, then rerun SQL*Module.

MOD-00027	No input file name specified

 Cause:	You entered the STORE_PACKAGE=YES option, but did not specify an input file using the INAME option.

 Action:	Use INAME on the command line.

MOD-00036	Internal programming exception

 Cause:	An internal error occurred.

 Action:	Contact customer support.

MOD-00038	Module name required when output language is Ada

 Cause:	You did not specify a MODULE clause in the.mad source file, or you did not provide a name for the module.

 Action:	Specify the module name in the module file.

MOD-00039	Unable to open specifications file name

 Cause:	SQL*Module is not able to create the specifications (header) output file. This usually happens when you do not have write permissions on the current directory or on the directory specified for the SNAME option. It can also happen if the name or directory path is not legal, a directory on the path does not exist, or the disk or file system is full.

 Action:	Check your permissions on the specified path and file or on the current directory if you do not use the SNAME options. Check that the disk or file system is not full.

MOD-00041	ANSI violation at line num, column colnam: text

 Cause:	You specified FIPS=YES, and part of your module code is not compliant with the ANSI SQL92 Entry Level standard.

 Action:	Specify FIPS=NO (the default) or correct the code.

MOD-00042	Cursor name is multiply declared

 Cause:	You declared the cursor named in the message more than once in the module file.

 Action:	Check that each cursor names(not just in the module file, but in the entire application) is unique.

MOD-00043	Procedure name is multiply declared

 Cause:	You declared a procedure named "X" more than once in the module file.

 Action:	Check that each procedure name (not just in the module file, but in the entire application) is unique.

MOD-00044	Parameter param in procedure name is multiply declared

 Cause:	In the procedure named in the message, you declared a parameter with a name that duplicates another parameter's name.

 Action:	Check that each parameter name in a procedure is unique.

MOD-00046	Cursor name has not been declared

 Cause:	In the module file, you attempted to perform an OPEN, FETCH, or CLOSE on a cursor that had not yet been declared.

 Action:	Insert an appropriate cursor declaration in the module file. Remember that cursors must be declared in the file before they are acted upon.

MOD-00047	An open statement already exists for cursor name

 Cause:	More than one procedure in this module contains an OPEN command on the named cursor.

 Action:	Remove one of the OPEN commands, as there is no need for redundancy.

MOD-00048	Cursor name was never opened.

 Cause:	No OPEN command exists in the module for the cursor named in this message.

 Action:	Add an OPEN command or remove the cursor if it is not needed.

MOD-00049	Unable to initialize PL/SQL

 Cause:	This message usually results when SQL*Module cannot connect to the database, using the username and password mentioned either in the module's AUTHORIZATION clause or on the command line with the USERID option.

 Action:	If you are connecting using SQL*Net, check that a listener process is running, and that the service name specified in the AUTHORIZATION clause or on the command line, is in the tnsnames.ora file. If the connect parameters are correct, and this problem persists, contact customer support.

MOD-00050	Formal parameter param is not used in procedure

 Cause:	You declared a formal parameter in a procedure, but never used it.

 Action:	Remove the parameter declaration or use it in the procedure.

MOD-00054	name is not a valid cursor reference

 Cause:	You attempted to OPEN a cursor that had not been declared.

 Action:	Declare the cursor or remove the erroneous reference to it.

MOD-00059	INTO variable var was not listed as a formal parameter

 Cause:	The target of an INTO clause in a SELECT statement is not a parameter of the procedure

 Action:	Declare the parameter, using the correct datatype, in the procedure's parameter list.

MOD-00060	PL/SQL error in compiling package specification

 Cause:	A semantic error occurred in the PL/SQL parse phase when running SQL*Module.

 Action:	Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a .pks extension). See the PL/SQL User's Guide and Reference for more information.

MOD-00061	PL/SQL error in compiling package body

 Cause:	A semantic error occurred in the PL/SQL parse phase when running SQL*Module.

 Action:	Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a .pkb extension). See the PL/SQL User's Guide and Reference for more information.

MOD-00062	Host variable for indicator is not recognized

 Cause:	You are using a host variable, before an indicator variable, that was not declared.

 Action:	Declare the host variable or remove the offending indicator variable from the SQL statement.

MOD-00063	Procedure name, parameter param: illegal interface type type

 Cause:	When attempting to generate an interface procedures (stubs) file, the WITH INTERFACE PROCEDURE clause in the referenced stored package or stored procedure contained a parameter having an illegal datatype.

 Action:	Correct the datatype. Datatypes in a WITH INTERFACE PROCEDURE clause must be SQL datatypes, not PL/SQL datatypes.

MOD-00064	Procedure name: extra parameter param in interface

 Cause:	You declared an unused parameter in the WITH INTERFACE PROCEDURE clause of a stored package or a stored procedure.

 Action:	Correct the WITH INTERFACE PROCEDURE clause in the package.

MOD-00065	Interface definition missing for procedure name

 Cause:	You attempted to generate stubs for a package that does not contain a WITH INTERFACE PROCEDURES clause for one or more procedures.

 Action:	Add the WITH INTERFACE PROCEDURE clause to the package spec.

MOD-00066	Unable to load package name from database

 Cause:	The package name that you specified using the PNAME option is not correct, or SQL*Module could not access the database schema required.

 Action:	Check that you are specifying a package that exists, and that has a valid status. Check the STATUS column of the USER_OBJECTS table for that schema to check that the package is valid.

MOD-00067	Package name is required but not specified

 Cause:	You specified the options and values RPC_GENERATE=YES and STORE_PACKAGE=YES, but you did not specify a package name using the PNAME option.

 Action:	Add the PNAME option.

MOD-00068	Could not find or open system configuration file

 Cause:	This is a warning message. SQL*Module is not able to find the system configuration file or is not able to open the file. The location of the system configuration file is system specific. See your SQL*Module installation guide for the location on your system.

 Action:	Check that the file exists, and that read permission or the appropriate access rights are set for it. This file must exist to avoid this warning message, however it can be empty.

MOD-00069	Oracle error N while attempting to store package

 Cause:	SQL*Module's attempt to store the package in the database failed.

 Action:	Look up the error number in this manual and correct the problem.

MOD-00070	Procedure name interface is missing declaration for indvar

 Cause:	An indicator variable was specified in the WITH INTERFACE PROCEDURES clause, but the associated main variable was not declared there.

 Action:	Modify the WITH INTERFACE PROCEDURES clause. Either remove the indicator variable or declare a host variable for it.

MOD-00072	PNAME option is specified but not meaningful

 Cause:	You used the PNAME option when there was no need for it. The PNAME option is only required when you specify RPC_GENERATE, STORE_PACKAGE, or both.

 Action:	Correct the command line.

MOD-00073	INAME option is specified but not meaningful

 Cause:	You used the INAME option when it was not required. For example, INAME is not required when you specify RPC_GENERATE=YES and use the PNAME option.

 Action:	Do not use the INAME option.

MOD-00074	ONAME option is specified but not meaningful

 Cause:	You used the ONAME option when it was not required. For example, the ONAME option is not required when RPC_GENERATE=NO, STORE_PACKAGE=YES, or the OUTPUT values list does not contain the CODE value.

 Action:	Do not use the ONAME option.

MOD-00075	Error at line N. PLS-N:  text

Cause:	A semantic error occurred in the PL/SQL parse phase when running SQL*Module.

 Action:	Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a .pkb extension). See the PL/SQL User's Guide and Reference for more information

MOD-00076	ANSI violation at line N. PLS-N: text

 Cause:	You specified FIPS=YES, and part of your module code is not compliant with the ANSI SQL92 Entry Level standard.

 Action:	Specify FIPS=NO (the default) or correct the code.

MOD-00077	Mandatory parameter SQLCODE or SQLSTATE is missing.

 Cause:	You must include a status parameter - SQLCODE, SQLSTATE, or both - in every parameter definition.

 Action:	Include SQLCODE or SQLSTATE.

MOD-00078	Must specify a user if generating stubs from stored package.

 Cause:	Because no USERID was specified, SQL*Module cannot connect to the server to create stubs (an interface procedures file) from the stored package.

 Action:	Specify the service name (if not connecting to the default database), and the username and password. Do this either on the command line or in a configuration file.

MOD-00079	SQLCHECK must be SEMANTICS when RPC_GENERATE=yes.

 Cause:	You cannot specify SQLCHECK=SYNTAX (or SQLCHECK=NONE) when creating a stubs file.

 Action:	Remove the SQLCHECK=SYNTAX or SQLCHECK=NONE specification from the command line or the configuration file.

MOD-00080	Error extracting stored package source.

 Cause:	You requested OUTPUT=PACKAGE on the command line or in a configuration file, and a package of the name you specified does not exist in the schema or is marked as INVALID.

 Action:	Check that the named package exists, and is valid.

MOD-00081	Failed assertion.

 Cause:	Some part of your input to SQL*Module caused an error or warning condition. This message always follows a specific error or warning message.

 Action:	No action required for this message. Correct the previous errors.

MOD-00086	Error: couldn't install username. Aborted...

 Cause:	The server rejected a username.

 Action:	If the username is valid, contact customer support.

MOD-00088	Feature not implemented yet

 Cause:	SQL*Module encountered a SQL statement that it can compile, but that uses a feature not yet implemented.

 Action:	Contact Oracle Languages Product Management.

MOD-00093	SNAME option is specified but not meaningful

 Cause:	You used the SNAME option when it was not required. For example, no SNAME option is required if the values list of the OUTPUT option does not include the value SPECIFICATION.

 Action:	Do not use the SNAME option.

MOD-00094	Extension in PNAME option is specified but not meaningful.

 Cause:	You included a filename extension in the value of a PNAME option. Packages are database objects, not files.

 Action:	Remove the extension.

MOD-00095	Datatype "X" is not valid for the host language.

 Cause:	You used a datatype that is not supported for the host language. For example, NUMERIC is not a supported datatype for Ada and C.

 Action:	Refer to the Programmer's Guide to the Oracle Precompilers for a list of the datatypes supported in each host language.

MOD-00096	LNAME option is specified but not meaningful.

 Cause:	The OUTPUT option list does not contain the value LIST.

 Action:	Add LIST to the list of values of the OUTPUT option.


APPENDIX A. MESSAGES ALPHABETICALLY

This appendix contains an alphabetical list of the messages that appear earlier in this book. You can use this list to find a message number. For example, if you know the message begins with the words "conversion error", you would find the message in this appendix beginning with these words, see that ORA-00404 is the message number you need, and can then refer to Chapter 2, "Oracle7 Server Messages", for more information on this message. See Chapter 1, "Locating Message Documentation", on page 1 - 2 for more general information about interpreting messages, such as message stacks.

Note:	If you cannot find the message you are looking for, it may be listed at the beginning of this appendix. It is possible that the first or second word is variable text.

In this Manual, variable text in a message is denoted by italics; for example : var, name, number, str, string, and so on. For example:

PLS-00365, FOOBAR is an OUT parameter and cannot be read

appears in this appendix as:

PLS-00365, var is an OUT parameter and cannot be read

It appears close to the beginning of the alphabetical list because of the variable text.

 ________________________________________

Messages Beginning With Variable Text

DBA-00341	'name' is an undefined bind variable

EXP-00010	name is not a valid username

EXP-00011	name.name does not exist

EXP-00012	num is not a valid export mode

ORA-00403	str (str) is not the same as other instances (str)

ORA-00955	name is already used by an existing object

ORA-02264	name already used by an existing constraint

ORA-04063	name has errors

ORA-04090	'name' specifies same table, event and trigger time as 'name'

ORA-08002	name.CURRVAL is not yet defined in this session

ORA-08004	name.NEXTVAL str [MIN][MAX]VALUE and cannot be instantiated

ORA-20000	application_specific_message

ORA-23300	application_specific_message

MOD-00054	name is not a valid cursor reference

PCC-00045	clause_name clause inappropriate at line num in file name. Ignored

PCC-00127	text

PLS-00221	'name' is not a procedure or is undefined

PLS-00313	'name' not declared in this scope

PLS-00353	'name' must name a user in the database

PLS-00356	'name' must name a table to which the user has access

PLS-00365	'name' is an OUT parameter and cannot be read

PLS-00415	'name' is an OUT parameter and cannot appear in a function

PLS-00704	'name' must be declared as an exception

 ________________________________________

Messages in Alphabetic Order

ORA-04014	[de][a]scending sequences that CYCLE must specify [NO][MIN][MAX] VALUE

PCC-00075	":" expected before indicator variable

PLS-00206	%TYPE must be applied to a variable or column, not 'name'

PLS-00407	'*' not allowed here; a list of columns is required

ORA-01818	'HH24' precludes use of meridian indicator

ORA-01841	(full) year must be between -4713 and +4713

ORA-02056	2PC: str: bad two-phase command number num from name

ORA-02057	2PC: str: bad two-phase recovery state number num from name

ORA-02033	a cluster index for this cluster already exists

ORA-01701	a cluster is not appropriate here

ORA-01799	a column may not be outer-joined to a subquery

ORA-01530	a database already mounted by the instance

ORA-01531	a database already open by the instance

PCC-02354	A file included with #include cannot contain SQL statements

ORA-01800	a literal in the date format was too large to process

ORA-02082	a loop-back database link must have a connection qualifier

ORA-01859	a non-alphabetic character was found where a letter was expected

ORA-01858	a non-numeric character found where a digit was expected

PLS-00335	a package name conflicts with an existing object

PLS-00312	a positional parameter association may not follow a named association

ORA-01468	a predicate may reference only one outer-joined table

PLS-00367	a RAISE statement with no exception name must be inside an exception handler

PLS-00902	a read-only bind variable used in OUT or IN OUT context

PLS-01711	A SELECT statement may not contain ORDER_BY, HAVING, or GROUP_BY clause

ORA-12000	a snapshot log already exists on table name

ORA-12006	a snapshot with the same user.name already exists

PLS-00328	a subprogram body must be defined for the forward declaration of 'name'

ORA-01726	a table is not appropriate here

ORA-01417	a table may be outer joined to at most one other table

ORA-01754	a table may contain only one column of type LONG

ORA-02185	a token other than WORK follows COMMIT

PLS-00218	a variable declared NOT NULL must have an initialization assignment

PLS-00450	a variable of this private type cannot be declared here

ORA-01702	a view is not appropriate here

IMP-00009	abnormal end of export file

ORA-01708	ACCESS or SESSION expected

ORA-09122	Access to object "obj" denied.

ORA-01548	active rollback segment 'name' found, terminate dropping tablespace

ORA-01200	actual file size of num is smaller than correct size of num blocks

ORA-01117	adding file 'name' with illegal block size num, limit is num

PLS-00205	aggregate not allowed here

PLS-00402	alias required in SELECT list of cursor to avoid duplicate column names

PLS-01422	Aliases

EXP-00005	all allowable logon attempts failed

IMP-00005	all allowable logon attempts failed

PLS-00424	all arguments must be provided in remote procedure call; no defaults

ORA-00352	all logs for thread num need to be archived - can not enable

ORA-02025	all tables in the SQL statement must be at the remote database

ORA-00391	All threads must switch to new log format at the same time

PCC-00064	All uses of a given host variable must use identical indicator variables

ORA-03286	ALLOCATE EXTENT not valid for HASH CLUSTERS

PCC-00011	Already in a Declare Section at line num in file name

ORA-00948	ALTER CLUSTER statement no longer supported

ORA-01404	ALTER COLUMN will make a concatenated index too large

ORA-01094	ALTER DATABASE CLOSE in progress. Connections not permitted

ORA-01093	ALTER DATABASE CLOSE only permitted with no sessions connected

ORA-02204	ALTER, INDEX,  REFERENCE and EXECUTE not allowed for views

PLS-01505	ALTER is non-ANSI

ORA-01447	ALTER TABLE does not operate on clustered columns

ORA-02204	ALTER, INDEX,  REFERENCE and EXECUTE not allowed for views

ORA-01855	AM/A.M. or PM/P.M. required

ORA-01814	AM/PM conflicts with use of A.M./P.M.

ORA-00960	ambiguous column naming in select list

PCC-00029	Ambiguous option optnam

PCC-02369	An EXEC TOOLS host pointer variable is not a pointer

PCC-02368	An EXEC TOOLS host variable context name is not type char

PCC-02370	An EXEC TOOLS message host variable is not type char

PLS-01406	An identifier has been found that is considered a keyword in ANSI's grammar but not in PL/SQL's

ORA-01153	an incompatible media recovery is active

PLS-00428	an INTO clause is expected in this SELECT statement

DBA-00378	an item has to be selected before help can be sought for it

MOD-00047	An open statement already exists for cursor name

PLS-00210	an OTHERS clause is required in this CASE statement

ORA-01705	an outer join cannot be specified on a correlation column

ORA-00061	another instance has a different DML_LOCKS setting

ORA-08008	another instance is mounted with USE_ROW_ENQUEUES = num

ORA-02051	another session in same transaction failed

PLS-01715	ANSI does not accept SAVEPOINTs

PLS-01712	ANSI does not allow bind variables as INDICATORS

PLS-01714	ANSI expects a column name not a literal value here

PLS-01404	ANSI Identifiers can only consist of letters, digits, and the underscore character

PCC-00079	ANSI requires colon on label in WHENEVER statement

PLS-01469	ANSI standard does not permit records

MOD-00076	ANSI violation at line N. PLS-N: text

MOD-00041	ANSI violation at line num, column colnam: text

SQL-02123	Application context not found

ORA-20000	application_specific_message

ORA-23300	application_specific_message

ORA-00473	ARCH process terminated with error

ORA-00329	archived log begins at change num, need change num

ORA-00310	archived log contains sequence num; sequence num required

ORA-00339	archived log does not contain any redo

ORA-00330	archived log ends at change num, need change num

ORA-00328	archived log ends at change num, need later change num

ORA-00325	archived log for thread num, wrong thread # num in header

ORA-00332	archived log is too small - may be incompletely archived

ORA-00342	archived log was created before last RESETLOGS

ORA-00334	archived log: 'name'

ORA-02166	ARCHIVELOG and NOARCHIVELOG specified

ORA-00257	archiver is stuck. Connect internal only, until freed.

ORA-00250	archiver not started

ORA-00251	archiving/media recovery requires OS DBA or OPER privileges

ORA-01428	argument num is out of range

PCC-02320	Arithmetic expression does not have correct operand types

PCC-00055	Array "name" not allowed as bind variable at line num in file name

ORA-01478	array bind may not include any LONG columns

PLS-00418	array bind type must match PL/SQL table row type

PCC-00096	Array FETCH not allowed for MODE=ANSI14

PCC-00094	Array length for char[n] datatype must be => 2

PCC-00115	Array required here

PCC-00044	Array size mismatch in INTO/USING. Minimum is: min (num:num)

ORA-01484	arrays can only be bound to PL/SQL statements

PCC-02312	Arrays of VARCHAR greater than two dimensions not allowed

PCC-00121	Arrays of VARCHAR pointers are not supported

EXP-00031	arraysize not in valid range. Using arraysize=num

PLS-00359	assignment target in 'str' must have components

ORA-03124	async operation interrupted

PCC-00103	AT clause is an Oracle extension

ORA-01600	at most one "str" in clause "str" of GC_FILES_TO_LOCKS

PLS-00371	at most one declaration for 'name' is permitted in the declaration section

PLS-00105	at most one forward declaration of type 'name' is permitted

ORA-06512	at str line num

ORA-02048	attempt to begin distributed transaction without logging on

ORA-03122	attempt to close Oracle-side window on user side

ORA-01594	attempt to wrap into rollback segment name extent num which is being freed

PCC-02332	Attempted to redefine SQL identifier

PLS-00229	attribute expression within SQL expression

ORA-12443	audit option already exists at a different label

ORA-00443	background process 'name' did not start

ORA-00445	background process 'name' did not start after num seconds

ORA-00444	background process 'name' failed while starting

ORA-00449	background process 'name' unexpectedly terminated with error num

ORA-01077	background process initialization failure

ORA-00446	background process started when not expected

ORA-01906	BACKUP keyword expected

SQL*Load-00706	Bad argument to ulerr [num]

ORA-01899	bad precision specifier

DBA-00136	bad variable specification

ORA-01815	BC/AD conflicts with use of B.C./A.D.

ORA-01856	BC/B.C. or AD/A.D. required

ORA-01642	begin backup not needed for for read only tablespace name

PLS-00214	BEGIN...END block nesting is too deep

ORA-12451	binary OS label could not be translated into string label

PCC-00083	Bind and define variables not allowed in CREATE statement

ORA-01049	bind by name is not supported in streamed RPC

ORA-02039	bind by value is not allowed for array type

PLS-00114	bind variable 'name' exceeds implementation length

PLS-00110	bind variable 'name' not allowed in this context

ORA-01006	bind variable does not exist

ORA-01027	bind variables not allowed for data definition operations

ORA-09117	Bind-value cannot be translated into SQL text.

ORA-01498	block Check Failure - see trace file

ORA-00212	block size num below minimum required size of num bytes

ORA-00209	block size num exceeds limit of num bytes

ORA-01162	block size num in file header does not match DB_BLOCK_SIZE (num)

ORA-01188	block size num in header does not match physical block size

PCC-02343	Body of cursor must be a query expression

PCC-02335	Body of cursor must name statement identifier

ORA-00704	bootstrap process failure

ORA-00702	bootstrap version version inconsistent with version version

PCC-00060	Both CURSOR and STATEMENT have AT clauses at line num of file name

ORA-03288	both FREELIST GROUP and INSTANCE parameters may not be specified

ORA-03111	break received on communication channel

ORA-06558	buffer in DBMS_PIPE package is full. No more items allowed

ORA-01718	BY ACCESS | SESSION clause not allowed for NOAUDIT

ORA-01461	can bind a LONG value only for insert into a LONG column

ORA-01180	can not create data file 1

ORA-02476	can not create index due to parallel direct load on table

ORA-02477	can not perform parallel direct load on object objnam

ORA-01187	can not read from file name because it failed verification tests

ORA-00364	can not write header to new log member

EXP-00021	can only perform incremental export in Full Database mode

ORA-02030	can only select from fixed tables/views

PLS-00420	can't call built-in routines remotely

PLS-00900	can't find body of unit 'name'

ORA-00034	cannot <commit or rollback> in current PL/SQL session

PLS-01460	Cannot access object on a remote host

ORA-01046	cannot acquire space to extend context area

ORA-01050	cannot acquire space to open context area

ORA-01118	cannot add any more data files: limit of num exceeded

ORA-02293	cannot add check constraint - found non-complying values

ORA-01537	cannot add data file 'name' - file already part of database

ORA-01577	cannot add logfile 'name' - file already part of database

ORA-02299	cannot add or enable constraint (name.name) -duplicate keys found

ORA-02294	cannot add referential constraint - parent keys not found

DBA-00331	cannot allocate enough memory for SQL Buffer

DBA-00373	cannot allocate memory of size number from toolkit

ORA-01037	cannot allocate sort work area cursor; too many cursors

ORA-02283	cannot alter starting sequence number

ORA-01597	cannot alter system rollback segment online or offline

ORA-01608	cannot bring rollback segment "name" online, its status is (status)

ORA-12491	cannot change MAC mode when mounted in READ_COMPATIBLE mode

ORA-04085	cannot change the value of an OLD reference variable

ORA-04087	cannot change the value of ROWID reference variable

ORA-04084	cannot change trigger NEW values in after row triggers

DBA-00309	cannot close spool file name

ORA-02074	cannot COMMIT or ROLLBACK in a distributed transaction

ORA-04092	cannot COMMIT or ROLLBACK in a trigger

PLS-00304	cannot compile body of 'name' without its specification

ORA-12490	cannot connect at session label below user definition (name)

ORA-08176	cannot continue consistent read for the table/index - no undo records

ORA-01454	cannot convert column into numeric datatype

ORA-01933	cannot create a stored object using privileges from a role

ORA-01471	cannot create a synonym with the same name as object

ORA-00200	cannot create control file 'name'

ORA-01524	cannot create data file as 'name' - file already part of database

ORA-01182	cannot create data file name - file is in use or recovery

ORA-01508	cannot create database; error in file 'name' at line num

ORA-01532	cannot create database; instance being started elsewhere

ORA-12001	cannot create log: table name already has a trigger

ORA-12010	cannot create snapshot log on table owned by SYS

ORA-04089	cannot create triggers on objects owned by SYS

ORA-01452	cannot CREATE UNIQUE INDEX; duplicate keys found

ORA-01985	cannot create user as LICENSE_MAX_USERS parameter exceeded

ORA-12351	cannot create view using a remote object which has a remote object reference

PCC-02337	Cannot declare multi-dimensioned array for this type

ORA-02265	cannot derive the datatype of the referencing column

ORA-02431	cannot disable constraint (name) - no such constraint

ORA-02297	cannot disable constraint (name.name) - dependencies exist

ORA-01125	cannot disable media recovery - file name has online backup set

ORA-01143	cannot disable media recovery - file name is offline

ORA-02433	cannot disable primary key - primary key not defined for table

ORA-02435	cannot disable unique(str) - unique key not defined for table

ORA-01940	cannot DROP a user that is currently logged in

ORA-02443	cannot drop constraint - nonexistent constraint

ORA-02429	cannot drop index used for enforcement of unique/primary key

ORA-02441	cannot drop nonexistent primary key

ORA-02442	cannot drop nonexistent unique key

ORA-02381	cannot drop PUBLIC_DEFAULT profile

ORA-01544	cannot drop system rollback segment

ORA-01550	cannot drop system tablespace

ORA-02430	cannot enable constraint (name) - no such constraint

ORA-02298	cannot enable constraint (name.name) -parent keys not found

ORA-02296	cannot enable constraint (str.name) - found non-complying values

ORA-02437	cannot enable primary key - found duplicates or null values

ORA-02432	cannot enable primary key - primary key not defined for table

ORA-02434	cannot enable unique(str) - unique key not defined for table

ORA-01140	cannot end online backup - all files are offline

ORA-01142	cannot end online backup - none of the files are in backup

PCC-02350	Cannot equivalence this SQL type

PCC-02314	Cannot evaluate constant sizeof expression

PCC-02315	Cannot evaluate expression as a constant.

ORA-06565	cannot execute name from within stored procedure

ORA-02401	cannot EXPLAIN view owned by another user

ORA-12485	cannot find file label for name

ORA-00260	cannot find online log sequence num for thread num

ORA-01712	cannot grant a privilege grantor does not have

ORA-01931	cannot grant UNLIMITED TABLESPACE, REFERENCES, or INDEX to a role

ORA-01926	cannot grant WITH GRANT OPTION to a role

SQL*Load-00254	Cannot have DISCARDFILE specs here when multiple data files

ORA-01437	cannot have join with CONNECT BY

ORA-01474	cannot have START WITH or PRIOR without CONNECT BY

ORA-01473	cannot have subqueries in CONNECT BY clause

PCC-02311	Cannot have VARCHAR bit fields

ORA-01157	cannot identify data file name - file not found

ORA-00122	cannot initialize network configuration

ORA-12478	cannot insert label above DBHIGH (var)

ORA-12407	cannot insert or update the ROWLABEL column of a view

ORA-01462	cannot insert string literals longer than 2000 characters

ORA-02047	cannot join the distributed transaction in progress

ORA-00027	cannot kill current session

DBA-00319	cannot locate sqldba configuration file name

ORA-12476	cannot login above DBHIGH (name)

ORA-12475	cannot login below DBLOW (name)

ORA-01230	cannot make read only  - file name is offline

ORA-01231	cannot make read write - file name is offline

ORA-01640	cannot make tablespace read only with active transactions

ORA-00981	cannot mix table and system auditing options

ORA-01463	cannot modify column datatype with current constraints

ORA-12439	cannot modify ROWLABEL column

ORA-01102	cannot mount database in exclusive mode

ORA-01183	cannot mount database in parallel mode

ORA-01099	cannot mount database in SHARED mode if started in single process mode

ORA-12494	cannot mount secondary database labeled above DBLOW

ORA-01617	cannot mount: num is not a valid thread number

ORA-01150	cannot offline tablespace - file name has online backup set

ORA-00308	cannot open archived log 'name'

PCC-02302	Cannot open code generation output file

DBA-00315	cannot open command file name

ORA-00210	cannot open control file 'name'

PCC-02303	Cannot open include file

PCC-02301	Cannot open input file for reading

DBA-00310	cannot open parameter file name

DBA-00307	cannot open spool file name

DBA-00320	cannot open sqldba configuration file name

DBA-00371	cannot open/locate input help file, filename

DBA-00372	cannot open/locate input index file, filename

ORA-01071	cannot perform operation without starting up Oracle

IMP-00029	cannot qualify table name by owner (name.name), use FROMUSER parameter

ORA-00320	cannot read file header from log name of thread num

ORA-00311	cannot read header from archived log

DBA-00142	cannot recognize object type, owner or name

ORA-01124	cannot recover online file 'name' - file is in use or recovery

ORA-00361	cannot remove last logmember name group num

ORA-01120	cannot remove online data file name; database is open or mounted parallel

ORA-01121	cannot rename data file name - file is in use or recovery

ORA-01523	cannot rename data file to 'name' - file already part of database

ORA-01533	cannot rename file 'name'; file does not belong to tablespace

ORA-01621	cannot rename member of current log if database is open

ORA-02444	cannot resolve referenced object in referential constraints

ORA-00213	cannot reuse control file 'name'; old file size num, num required

ORA-02015	cannot select FOR UPDATE from remote table

ORA-02014	cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.

ORA-01445	cannot select ROWID from view of more than one table

ORA-01446	cannot select ROWID from view with DISTINCT, GROUP BY, etc.

DBA-00301	cannot SET INSTANCE while connected to a database

ORA-01568	cannot set space quota on PUBLIC

ORA-12808	cannot set [CACHE | SCAN]_INSTANCES greater than number of instances num

ORA-12809	cannot set [CACHE | SCAN]_INSTANCES when mounted in exclusive mode

ORA-01088	cannot shut down Oracle while active processes exist

ORA-01074	cannot shut down Oracle; inside a logon session - log off first

ORA-01149	cannot shutdown - file name has online backup set

ORA-01097	cannot shutdown while in a transaction -commit or rollback

ORA-01936	cannot specify owner when creating users or roles

EXP-00035	Cannot specify Rows=N and Compress=Y

ORA-01081	cannot start already-running Oracle - shut it down first

ORA-01146	cannot start online backup - file name is already in backup

ORA-01128	cannot start online backup - file name is offline

ORA-01232	cannot start online backup - file name is read only

ORA-01123	cannot start online backup; media recovery not enabled

DBA-00388	cannot start SQL*DBA in screen mode; check if values are legal

ORA-01087	cannot start up Oracle - currently logged on

DBA-00316	cannot startup while connected to a database

ORA-00106	cannot startup/shutdown database when connected to a dispatcher

ORA-01072	cannot stop Oracle; Oracle not running

ORA-01411	cannot store the length of column in the indicator

ORA-12437	cannot to write down to a database at a lower label

ORA-01407	cannot update mandatory (NOT NULL) column to NULL

ORA-02016	cannot use a subquery in a START WITH on a remote database

ORA-01472	cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.

ORA-01011	Cannot use Oracle7 compatibility mode with an Oracle Version 6 server

ORA-01552	cannot use system rollback segment for non-system tablespace 'name'

ORA-12324	cannot use the ROM: link type on a private database link

ORA-01038	cannot write data file version ver with Oracle Version ver

ORA-01923	CASCADE aborted, objects locked by another user

ORA-01981	CASCADE CONSTRAINTS must be specified to perform this revoke

ORA-01922	CASCADE must be specified to drop 'name'

ORA-01491	CASCADE option not valid

PLS-00211	CASE labels or ranges must not be duplicated in different WHEN clauses

PLS-00379	CASE statements are not included in this release of PL/SQL

ORA-00276	CHANGE keyword specified but no change given

ORA-00280	change num for thread num is in sequence #num

ORA-00279	change num generated at name needed for thread num

ORA-00355	change numbers out of order

IMP-00037	character set marker unknown

IMP-00042	CHARSET used, but the export file has specific character set

ORA-02290	check constraint (str.name) violated

ORA-02252	check constraint condition not properly ended

ORA-01464	circular grant (granting to grant ancestor) of table or view

ORA-01934	circular role grant detected

ORA-01731	circular view definition encountered

PCC-00045	clause_name clause inappropriate at line num in file name. Ignored

ORA-00601	cleanup lock conflict

ORA-02041	client database did not begin a transaction

ORA-01987	client O/S user name is too long

ORA-02464	cluster definition cannot be both HASH and INDEX

ORA-00943	cluster does not exist

ORA-00951	cluster not empty

ORA-01770	CLUSTER option not allowed in CREATE CLUSTER command

ORA-03293	cluster to be truncated is a HASH CLUSTER

ORA-02032	clustered tables cannot be used before the cluster index is built

PCC-02129	CMD-LINE:  Client supplied static options table is invalid

PCC-02035	CMD-LINE:  CONFIG= option is invalid in a config file

PCC-02132	CMD-LINE:  Could not allocate memory

PCC-02066	CMD-LINE:  Could not find or could not open system config file

PCC-02133	CMD-LINE:  Error processing string function

PCC-02044	CMD-LINE:  Illegal or out of range value for option:

PCC-02041	CMD-LINE:  Option does not exist:

PCC-02040	CMD-LINE:  Option selected, but no value provided

PCC-02043	CMD-LINE:  Option syntax is incorrect

PCC-02135	CMD-LINE:  User asked for help

SQL-02115	Code interpretation problem -- check COMMON_NAME usage

PCC-00077	Colon usage with numeric label in WHENEVER statement is not ANSI

PLS-00358	column 'name' exists in more than one table; use qualifier

ORA-00965	column aliases not allowed for '*'

ORA-00918	column ambiguously defined

ORA-01430	column being added already exists in table

ORA-02438	column check constraint cannot reference other columns

ORA-01449	column contains NULL values; cannot alter to NOT NULL

ORA-01753	column definition incompatible with clustered column definition

ORA-01018	column does not have a LONG datatype

ORA-04073	column list not valid for this trigger type

SQL*Load-00923	Column name in table name is NOT NULL but is not being loaded

SQL*Load-00404	Column name present more than once in table name

SQL*Load-00928	Column name.name does not exist

ORA-00984	column not allowed here

ORA-02360	column not found before end of logical record (use TRAILING NULLCOLS)

SQL*Load-00622	Column not found before end of logical record(use TRAILING NULLCOLS)

ORA-01439	column to be modified must be empty to change datatype

ORA-01441	column to be modified must be empty to decrease column length

ORA-01440	column to be modified must be empty to decrease precision or scale

ORA-01442	column to be modified to NOT NULL is already NOT NULL

ORA-01451	column to be modified to NULL cannot be modified to NULL

ORA-02267	column type incompatible with referenced column type

PCC-02366	Command line argument MODE=ANSI may not be used with DBMS=V6

PCC-00128	Command line processor severe error

ORA-01953	command no longer valid, see ALTER USER

DBA-00327	command not available in this mode

DBA-00305	command size exceeds internal buffer size (num)

PLS-01403	Comment delimiters /* */

ORA-01742	comment not terminated properly

ORA-02089	COMMIT is not allowed in a subordinate session

PCC-00124	COMMON_NAME option must be before PROGRAM or subroutine beginning

ORA-03100	communication area cannot be allocated; insufficient memory

SQL*Load-00457	Comparison text ('str') of CONTINUEIF LAST must have length 1 not num

SQL*Load-00458	Comparison text of CONTINUEIF LAST must be non-whitespace

ORA-00406	COMPATIBILITY parameter needs to be value or higher

ORA-00405	compatibility type \name\

ORA-01485	compile bind length different from execute bind length

PLS-00302	component 'name' must be declared

ORA-02147	conflicting SHARED/EXCLUSIVE options

ORA-01788	CONNECT BY clause required in this query block

PLS-01425	Connect-by clause

ORA-01436	CONNECT BY loop in user data

SQL-02125	Connect error, can't get error text. See Server Messages & Codes Manual

ORA-02019	connection description for remote database not found

ORA-00115	connection refused; dispatcher connection table is full

ORA-02272	constrained column cannot be of LONG datatype

PLS-01502	Constraint name and constraint status are non-ANSI.

ORA-02253	constraint specification not allowed here

ORA-01911	CONTENTS keyword expected

ORA-00211	control file 'name' does not match previous control files

ORA-00220	control file 'name' not mounted by first instance

ORA-00217	control file 'name' physical block size num inconsistent with num

ORA-00214	control file 'name' version num inconsistent with file 'name' version num

ORA-00218	control file 'name' was created with physical size num now is num

SQL*Load-00516	Control file (name) has no contents

SQL*Load-00267	Control file must be first data file

ORA-01190	control file or data file name is from before the last RESETLOGS

ORA-00201	control file version num incompatible with Oracle version num

ORA-00202	control file: 'name'

ORA-00207	control files are not for the same database

ORA-00223	conversion data file is invalid or incorrect version

ORA-00404	Conversion data file not found: name

ORA-02355	conversion error occurred on CONSTANT field str

ORA-02354	conversion initialization error occurred on field name

ORA-01457	converting column overflows decimal datatype

ORA-01455	converting column overflows integer datatype

ORA-02191	correct syntax is:  SET TRANSACTION USE ROLLBACK SEGMENT name

ORA-02178	correct syntax is: SET TRANSACTION READ {  ONLY | WRITE }

ORA-00354	corrupt redo log block header

ORA-02428	could not add foreign key reference

SQL*Load-00259	Could not escalate DDL share lock to exclusive on table name

EXP-00033	Could not find environment character set

IMP-00036	could not find environment character set

IMP-00038	could not find environment character set handle

MOD-00068	Could not find or open system configuration file

PCC-00126	Could not find or open system configuration file

ORA-12806	could not get background process to hold enqueue

DBA-00385	could not locate SQL*DBA resource file, var

DBA-00387	could not locate toolkit resource file, var

PLS-00212	could not obtain enough memory to compile CASE statement

LCC-00201	could not open specified filename name

DBA-00384	could not open SQL*DBA resource file, var

DBA-00386	could not open toolkit resource file, var

DBA-00374	could not set file position in filename directly

SQL*Load-00932	Could not truncate table name

ORA-01048	Couldn't find the specified procedure in the given context

SQL-02126	Count of array elements cannot be negative (i.e. < 0)

ORA-02440	create as select with referential constraints not allowed

ORA-01503	CREATE CONTROLFILE failed

ORA-12701	CREATE DATABASE character set is not known

ORA-01501	CREATE DATABASE failed

ORA-01518	CREATE DATABASE must specify more than one logfile

PLS-01506	CREATE INDEX is non-ANSI

ORA-02446	CREATE TABLE ... AS SELECT failed - check constraint violated

ORA-02425	create table failed

ORA-02427	create view failed

ORA-00262	current log name of closed thread num cannot switch

ORA-00369	Current log of thread name not useable and other log being cleared

ORA-00323	current log of thread num not usable and all others need archiving

ORA-00152	current session does not match requested session

ORA-01075	currently logged on

PLS-00404	cursor 'name' must be declared with FOR UPDATE to use with CURRENT OF

PLS-01703	Cursor name in CLOSE statment must be of length 1

PLS-00324	cursor attribute may not be applied to non-cursor 'name'

ORA-01023	cursor context not found (Invalid cursor number)

PLS-00360	cursor declaration without body needs return type

PCC-00073	Cursor is declared but never OPENed at line num in file name

MOD-00046	Cursor name has not been declared

MOD-00042	Cursor name is multiply declared

MOD-00048	Cursor name was never opened.

ORA-01176	data dictionary has more than the num files allowed by the controlfile

ORA-01175	data dictionary has more than the num files allowed by the instance

ORA-01173	data dictionary indicates missing data file from system tablespace

EXP-00001	data field truncation - column length=num, buffer size=num fetched=num

ORA-01177	data file does not match dictionary - probably old incarnation

ORA-01210	data file header is media corrupt

ORA-01208	data file is an old version - not accessing current version

ORA-01209	data file is from before the last RESETLOGS

ORA-01122	data file name - failed verification check

ORA-01229	data file name is inconsistent with logs

ORA-01221	data file name is not the same file to a background process

ORA-01137	data file name is still in the middle of going offline

ORA-01110	data file name: 'str'

ORA-01169	DATA FILE number 1 not found. Must be present

ORA-01171	data file string is going offline due to error advancing checkpoint

ORA-01569	data file too small for system dictionary tables

ORA-01130	data file version num incompatible with Oracle Version num

ORA-09111	Data manipulation operation not legal on this object.

ORA-01732	data manipulation operation not legal on this view

DBA-00311	data size exceeds internal buffer size

ORA-12318	database (link name name) is already mounted

ORA-12319	database (link name name) is already open

ORA-12333	database (link name name) is not mounted

ORA-12335	database (link name name) is not open

ORA-12321	database (link name name) is not open and AUTO_MOUNTING=FALSE

ORA-12334	database (link name name) is still open

ORA-02086	database (link) name is too long

ORA-01100	database already mounted

ORA-01101	database being created currently mounted by some other instance

ORA-01154	database busy. Open, Close, mount, and dismount not allowed now

ORA-01639	database cannot be mounted parallel with no lock processes

ORA-00402	database changes by release rel cannot be used by release rel

ORA-12440	database has not been mounted in read-compatible mode

ORA-12350	database link being dropped is still mounted

ORA-02080	database link is in use

ORA-02081	database link is not open

ORA-02085	database link name connects to name

ORA-04054	database link name does not exist

ORA-01729	database link name expected

ORA-02024	database link not found

ORA-02018	database link of same name has an open connection

ORA-12315	database link type is invalid for the ALTER DATABASE statement

ORA-01134	database mounted exclusive by another instance

SQL*Load-00903	Database must be at least version num for direct path

ORA-01106	database must be closed before dismounting

ORA-01126	database must be mounted exclusive and not open for this operation

ORA-01148	database must be mounted exclusive for this operation

ORA-01107	database must be mounted for media recovery

ORA-01138	database must either be open in this instance or not at all

ORA-01127	database name 'name' exceeds size limit of num characters

ORA-01103	database name 'name' in control file is not 'name'

ORA-01158	database name already mounted

ORA-02070	database name does not support capability in this context

ORA-02083	database name has illegal character 'str'

ORA-12329	database name is closed; no operations are permitted

ORA-12326	database name is closing immediately; no operations are permitted

ORA-02084	database name is missing a component

ORA-01504	database name name does not match parameter DB_NAME str

ORA-01161	database name name in file header does not match given name of name

ORA-01507	database not mounted

ORA-01109	database not open

ORA-01219	database not open: queries allowed on fixed tables/views only

ORA-01022	database operation not supported in this configuration

ORA-02164	DATAFILE clause specified more than once

ORA-01904	DATAFILE keyword expected

ORA-01641	datafiles cannot be added to read only tablespace name

MOD-00095	Datatype "X" is not valid for the host language.

EXP-00018	datatype (num) for column name, table name.name is not supported

PCC-00112	Datatype not supported by ANSI

ORA-01419	datdts: illegal format code

ORA-00975	date + date not allowed

ORA-01801	date format is too long for internal buffer

ORA-01821	date format not recognized

ORA-01830	date format picture ends before converting entire input string

ORA-01839	date not valid for month specified

ORA-02436	date or system variable wrongly specified in CHECK constraint

ORA-01421	datrnd/dattrn: illegal precision specifier

ORA-01420	datstd: illegal format code

ORA-01834	day of month conflicts with Julian date

ORA-01847	day of month must be between 1 and last day of month

ORA-01835	day of week conflicts with Julian date

ORA-01817	day of week may only be specified once

ORA-01832	day of year conflicts with Julian date

ORA-01848	day of year must be between 1 and 365 (366 for leap year)

SQL*Load-00253	DB2 partition number has no significance -- ignored

ORA-12410	DBHIGH cannot be null in DBMS MAC mode

ORA-12411	DBHIGH must dominate DBLOW

ORA-12413	DBHIGH must dominate name

ORA-12409	DBLOW cannot be null in DBMS MAC mode

ORA-12412	DBLOW must be dominated by name

ORA-00471	DBWR process terminated with error

ORA-00058	DB_BLOCK_SIZE must be num to mount this database (not num)

ORA-01131	DB_FILES files initialization parameter value num exceeds limit of num

ORA-01174	DB_FILES is num but needs to be num to be compatible

ORA-00056	DDL lock on object 'str.name' already held in an incompatible mode

ORA-02021	DDL operations are not allowed on a remote database

ORA-04020	deadlock detected while trying to lock object name

ORA-00060	deadlock detected while waiting for resource

ORA-00104	deadlock detected; all public servers blocked waiting for resource

ORA-04014	[de][a]scending sequences that CYCLE must specify [NO][MIN][MAX] VALUE

PLS-00322	declaration of a constant 'name' must contain an initialization assignment

PLS-00341	declaration of cursor 'name' is incomplete or malformed

PLS-00108	declarative units must be a single variable declaration

ORA-02254	DEFAULT <expression> not allowed here

ORA-12823	default degree of parallelism may not be specified here

ORA-01954	DEFAULT ROLE clause not valid for CREATE USER

ORA-01945	DEFAULT ROLE[S] already specified

ORA-01946	DEFAULT TABLESPACE already specified

ORA-01004	default username feature not supported; logon denied

ORA-02276	default value type incompatible with column type

ORA-01051	deferred rpc buffer format invalid

ORA-02038	define is not allowed for array type

ORA-09107	Definition of a target system object may have changed.

ORA-09116	Definition of target system data object is inconsistent.

ORA-01042	detaching a session with open cursors not allowed

ORA-12405	device high (name) must dominate DBHIGH (name)

ORA-12404	device low (name) must be dominated by DBLOW (name)

EXP-00025	dictionary shows no column for constraint name.num

EXP-00007	dictionary shows no columns for name.name

ORA-01766	dictionary table not allowed in this context

PCC-02012	Did not find a matching quote for char constant

PLS-00401	different column types between cursor SELECT statement and return value found at 'name'

PLS-00400	different number of columns between cursor SELECT statement and return value

PLS-00399	different types of columns in UNION, INTERSECT, or MINUS expression

ORA-02352	direct path connection must be homogeneous

ORA-08175	discrete transaction restriction violated (name)

ORA-00105	dispatching mechanism not configured to support network protocol

ORA-00120	dispatching mechanism not enabled or installed

PCC-00076	DISPLAY type must be SIGN LEADING SEPARATE

ORA-02088	distributed database option not installed

ORA-02062	distributed recovery received DBID num, expected num

ORA-02046	distributed transaction already begun

ORA-02055	distributed update operation failed; rollback required

ORA-01476	divisor is equal to zero

ORA-00062	DML full-table lock cannot be acquired; DML_LOCKS is 0

ORA-01761	DML operation does not map to a unique table in the join

ORA-01095	DML statement processed zero rows

PLS-01507	DROP is non-ANSI

ORA-01567	dropping log name would leave less than two logfiles in thread num

ORA-03276	duplicate ALLOCATE EXTENT option specification

ORA-00977	duplicate auditing option

ORA-02214	duplicate BACKUP option specification

ORA-01769	duplicate CLUSTER option specifications

PLS-00408	duplicate column 'name' not permitted in INSERT or UPDATE

ORA-00957	duplicate column name

PLS-00117	duplicate CONNECT BY clause in table expression

ORA-02011	duplicate database link name

PLS-00410	duplicate fields in record or table are not allowed

PLS-00118	duplicate GROUP BY clause in table expression

ORA-02463	duplicate HASH IS option specified

ORA-02453	duplicate HASH IS specification

ORA-02451	duplicate HASHKEYS specification

PLS-00119	duplicate HAVING clause in table expression

ORA-02284	duplicate INCREMENT BY specifications

ORA-02462	duplicate INDEX option specified

ORA-02206	duplicate INITRANS option specification

ORA-02208	duplicate MAXTRANS option specification

ORA-12822	duplicate option in PARALLEL clause

ORA-03278	duplicate option specified for ALLOCATE EXTENT

ORA-02281	duplicate or conflicting CACHE/NOCACHE specifications

ORA-02280	duplicate or conflicting CYCLE/NOCYCLE specifications

ORA-02278	duplicate or conflicting MAXVALUE/NOMAXVALUE specifications

ORA-02279	duplicate or conflicting MINVALUE/NOMINVALUE specifications

ORA-02258	duplicate or conflicting NULL and/or NOT NULL specifications

ORA-02282	duplicate or conflicting ORDER/NOORDER specifications

ORA-02212	duplicate PCTFREE option specification

ORA-02213	duplicate PCTUSED option specification

ORA-01711	duplicate privilege listed

ORA-02274	duplicate referential constraint specifications

ORA-02378	duplicate resource name name

ORA-02228	duplicate SIZE specification

ORA-02285	duplicate START WITH specifications

ORA-02217	duplicate storage option specification

ORA-02215	duplicate tablespace name clause

ORA-00150	duplicate transaction ID

ORA-02259	duplicate UNIQUE/PRIMARY KEY specifications

ORA-01700	duplicate username in list

PLS-00409	duplicate variable 'name' in INTO list is not permitted

PLS-00116	duplicate WHERE clause in table expression

ORA-00483	during shutdown a process abnormally terminated

PCC-00109	Dynamic SQL and PL/SQL are an Oracle extensions to ANSI SQL

PLS-00104	empty argument list in call of procedure 'name' must be omitted

ORA-01215	enabled thread num is missing after CREATE CONTROLFILE

MOD-00012	Encountered the symbol name when expecting one of the following...

SQL*Load-00401	End field position num must be greater than or equal to start num

PLS-00113	END identifier 'name1' must match 'name2' at line num, column num

PLS-00111	end-of-file in comment

ORA-03113	end-of-file on communication channel

PLS-00112	end-of-line in quoted identifier

PCC-00123	Entire VARCHAR declaration must be on same line

ORA-01528	EOF while processing SQL statement

SQL*Load-00503	Error appending extension to file (name)

ORA-00255	error archiving log 'name' of thread num, sequence # num

MOD-00075	Error at line N. PLS-N:  text (null)

PCC-00061	Error at line num, column name. PLS-N: PLS-nnnnn

SQL*Load-00910	Error binding input variables of upi: [num]

SQL*Load-00955	Error calling col array build, block formatter

SQL*Load-00956	Error calling once/data file finishing

SQL*Load-00952	Error calling once/data file initialization

SQL*Load-00961	Error calling once/load finishing

SQL*Load-00951	Error calling once/load initialization

SQL*Load-00916	Error checking path homogeneity

SQL*Load-00963	Error clearing user-side Ctrl-C handler

SQL*Load-00915	Error closing cursor:  [num]

ORA-01529	error closing file 'name'

ORA-01992	error closing password file name

ORA-01592	error converting Version 6 rollback segment 'num' to Oracle7 format

ORA-00270	error creating archive log

ORA-01580	error creating control backup file 'name'

SQL*Load-00517	Error decomposing file name (name)

SQL*Load-00911	Error defining output variables for upi: [num]

SQL*Load-00920	Error deleting data from table name (due to REPLACE keyword)

SQL*Load-00968	Error disconnecting from Oracle

ORA-01515	error dropping log group num: no such log

ORA-01587	error during control file backup file copy

DBA-00361	error during describe

ORA-04088	error during execution of trigger 'str.name'

ORA-01980	error during OS ROLE initialization

SQL*Load-00919	Error during upi fetch:  [num]

ORA-01423	error encountered while checking for extra rows in exact fetch

SQL*Load-00960	Error escalating DDL share lock to exclusive

SQL*Load-00906	Error executing SQL statement for upi: [num]

MOD-00080	Error extracting stored package source.

SQL*Load-00913	Error fetching results of select statement (upi): [num]

ORA-01595	error freeing extent num of rollback segment name

SQL*Load-00515	Error getting CPU time

SQL*Load-00514	Error getting elapsed time

ORA-01585	error identifying backup file 'name'

ORA-01521	error in adding data files

ORA-00301	error in adding logfile 'name' - file cannot be created

ORA-01505	error in adding logfiles

ORA-00254	error in archive control string 'archive_log_location'

ORA-01119	error in creating data file 'name'

ORA-01510	error in deleting logfiles

ORA-01714	error in execution of user function

LCC-00218	error in file filename

ORA-00205	error in identifying control file 'name'

ORA-01565	error in identifying file 'name'

ORA-01514	error in log specification; no such log

ORA-01116	error in opening data file name

ORA-01526	error in opening file 'name'

SQL*Load-00114	Error in OPTIONS statement

ORA-00204	error in reading control file 'name' (block num, # blocks num)

ORA-01525	error in renaming data files

ORA-01511	error in renaming log/data files

ORA-01080	error in shutting down Oracle

ORA-12008	error in snapshot refresh path

DBA-00381	error in the SERVER OUTPUT option

ORA-00206	error in writing control file 'name' (block num, # blocks num)

EXP-00002	error in writing to export file

ORA-02071	error initializing capabilities for remote database name

SQL*Load-00914	Error locking table name in exclusive mode

SQL*Load-00964	Error logging off Oracle

SQL*Load-00901	Error logging on to Oracle

ORA-00816	error message translation failed

SQL*Load-00966	Error num disabling all triggers on table name

SQL*Load-00965	Error num disabling constraint name of table name

SQL*Load-00519	Error num writing to file (name)

ORA-21000	error number argument to RAISE_APPLICATION_ERROR of name is out of range, must be between -20000 and -20999, inclusive

ORA-00604	error occurred at recursive SQL level num

ORA-00256	error occurred in translating archive text string 'str'

SQL*Load-00604	Error occurred on an attempt to commit

ORA-04052	error occurred when looking up remote object name

ORA-04053	error occurred when validating remote object name

ORA-12012	error on auto refresh of snapshot name

PCC-00125	Error on command line or in the configuration file

EXP-00014	error on row num of table name

EXP-00015	error on row num of table name, column name, datatype num

EXP-00034	error on rowid: file# num block# num slot# num

ORA-00221	error on write to control file

SQL*Load-00902	Error opening cursor:  [num]

ORA-01990	error opening password file name

ORA-04029	error ORA-num occurred when querying 'string'

SQL*Load-00930	Error parsing insert statement for column name

SQL*Load-00929	Error parsing insert statement for table name

ORA-02373	Error parsing insert statement for table name.

SQL*Load-00907	Error parsing insert statement on table name

SQL*Load-00917	Error parsing insert statement on table name

SQL*Load-00905	Error parsing SQL statement for upi:  [num]

SQL*Load-00969	Error performing file name translation on kernel side

SQL*Load-00958	Error popping data relocation address stack

SQL*Load-00116	Error prompting for password

ORA-01995	error reading password file name

SQL*Load-00518	Error reassembling file name (name)

ORA-01141	error renaming data file name - new file 'name' not found

ORA-01512	error renaming logfile 'name' - new file 'name' not found

SQL*Load-00962	Error setting user-side Ctrl-C handler

SQL*Load-00959	Error shipping buffer across 2-task

SQL*Load-00950	Error shipping data structures across 2-task

SQL*Load-00954	Error shipping index to read buffer across 2-task

SQL*Load-00953	Error shipping read buffer across 2-task

SQL*Load-00957	Error shipping text string across 2-task

ORA-12801	error signaled in parallel query server name

SQL*Load-00504	Error skipping records in file (name)

SQL*Load-00935	Error verifying required option for parallel load.

ORA-01519	error while processing file 'name' near line num

ORA-01527	error while reading file

SQL*Load-00925	Error while str

ORA-02479	error while translating file name for parallel load

ORA-02002	error while writing to audit trail

ORA-00272	error writing archive log

ORA-01993	error writing password file name

PCC-00085	Error writing to file name

MOD-00086	Error: couldn't install username. Aborted...

ORA-04045	errors during recompilation/revalidation of name.name

ORA-01425	escape character must be character string of length 1

ORA-02194	event specification syntax error num (minor error num) near 'name'

ORA-01903	EVENTS keyword expected

ORA-01422	exact fetch returns more than requested number of rows

ORA-02393	exceeded call limit on CPU usage

ORA-02395	exceeded call limit on I/O usage

ORA-02390	exceeded COMPOSITE_LIMIT, logoff in progress

ORA-02396	exceeded max Idle Time, please connect again

ORA-02399	exceeded maximum connect time, logging off

ORA-02397	exceeded PRIVATE_SGA Limit, logging off

ORA-02398	exceeded procedure space usage

ORA-02392	exceeded session limit on CPU usage, logging off

ORA-02394	exceeded session limit on I/O usage, logging off

ORA-02391	exceeded simultaneous SESSIONS_PER_USER limit, maximum num

PLS-00706	exception 'name' cannot be used as prefix of a selected component

PLS-00483	exception 'name' may appear in at most one exception handler in this block

PLS-00484	exceptions 'name' and 'name' have same Oracle error number and must appear in same exception handler

PLS-00705	exceptions not allowed in an expression

ORA-02445	Exceptions table not found

ORA-01913	EXCLUSIVE keyword expected

ORA-02148	EXCLUSIVE specified multiple times

PCC-02204	EXEC SQL INCLUDE not permitted from within an included file

PCC-00087	EXEC SQL TYPE statement not allowed for this host language

PCC-01006	EXEC statement cannot begin in Area A at line num in file name

ORA-02224	EXECUTE privilege not allowed for tables

ORA-04061	existing state of name has been invalidated

ORA-04068	existing state of packages has been discarded

ORA-01908	EXISTS keyword expected

PLS-00373	EXIT label 'name' must label a LOOP statement

PCC-00054	Expected end-of-statement at column name in line num of file name

PCC-00018	Expected token, but found token at line num in file name

PCC-02330	Expecting an expression of integer type

ORA-12825	explicit degree of parallelism must be specified here

IMP-00043	export file character set inconsistent

EXP-00000	Export terminated unsuccessfully

EXP-00037	Export views not compatible with database version

EXP-00024	Export views not installed, please notify your DBA

PLS-00363	expression 'str' cannot be used as an assignment target

PLS-00321	expression 'str' is inappropriate as the left hand side of an assignment statement

PLS-00382	expression is of wrong type

ORA-01790	expression must have same datatype as corresponding expression

PCC-02319	Expression type does not match usage

ORA-01551	extended rollback segment, pinned blocks released

MOD-00094	Extension in PNAME option is specified but not meaningful.

DBA-00101	extraneous text at end of command

ORA-01596	fail to coalesce extents because sort area size is too small

MOD-00081	Failed assertion.

ORA-01538	failed to acquire any rollback segment

ORA-01599	failed to acquire rollback segment (name), cache space is full (currently has (num) entries)

ORA-09105	Failed to acquire storage space in target system.

EXP-00020	failed to allocate memory of size num

IMP-00006	failed to allocate memory of size num

ORA-00025	failed to allocate num

ORA-12011	failed to auto refresh num snapshots

EXP-00027	failed to calculate Oracle block size

ORA-00107	failed to connect to network listener process

IMP-00030	failed to create file name for write

ORA-01562	failed to extend rollback segment (ID = num)

IMP-00002	failed to open name for read

EXP-00028	failed to open name for write

EXP-00019	failed to process parameters, type 'EXP HELP=Y' for help

IMP-00022	failed to process parameters, type 'IMP HELP=Y' for help

ORA-01561	failed to remove all objects in the tablespace specified

IMP-00027	failed to roll back partial import of previous table

ORA-00108	failed to set up dispatcher to accept connection asynchronously

ORA-01091	failure during startup force

ORA-01500	failure in getting date/time

ORA-01803	failure in getting date/time

ORA-01078	failure in processing initialization parameters

ORA-00349	failure obtaining block size for 'name'

LCC-00217	failure while processing file parameter

ORA-01073	fatal connection error: unrecognized call type

ORA-00447	fatal error in background process

PCC-02102	Fatal error while doing C preprocessing

SQL-02116	FATAL ERROR: Reentrant code generator gave invalid context

ORA-03106	fatal two-task communication protocol error

MOD-00088	Feature not implemented yet

ORA-09121	Fetch exceeds maximum number of records defined for table.

ORA-01002	fetch out of sequence

ORA-01405	fetched column value is NULL

ORA-01406	fetched column value was truncated

ORA-02028	fetching an exact number of rows is not supported by the server

SQL*Load-00621	Field in data file exceeded maximum specified length

ORA-02359	field in data file exceeded maximum specified length

ORA-01522	file 'name' to be renamed does not exist

ORA-01220	file based sort illegal before database is open

ORA-01226	file header of redo log member is inconsistent with other member

PCC-00120	File I/O error during code generation

ORA-01189	file is from a different RESETLOGS than previous files

ORA-01207	file is more recent than control file - old control file

ORA-01206	file is not part of this database - wrong database id

ORA-12403	file label (name) must be equal to DBHIGH (name)

ORA-12446	file label is higher than instance label

ORA-12444	file label is lower than instance label

ORA-02197	file list already specified

SQL*Load-00264	File mode token name parsed but ignored

ORA-01135	file name accessed for DML/query is offline

ORA-00372	file name can not be modified at this time

ORA-00376	file name can not be read at this time

ORA-01178	file name created before last CREATE CONTROLFILE, cannot recreated

ORA-01181	file name created before last RESETLOGS, cannot recreated

ORA-01179	file name does not exist

ORA-01191	file name is already offline - cannot do a normal offline

ORA-01196	file name is inconsistent due to a failed media recovery session

ORA-01160	file name is not a str it is of type str

ORA-01159	file name is not from same database as previous files

ORA-01193	file name is not the same file seen at start of recovery

ORA-01233	file name is read only - cannot recover using backup control file

ORA-02238	file name lists have different numbers of files

ORA-01113	file name needs media recovery

ORA-01194	file name needs more recovery to be consistent

DBA-00383	file name var pointed to by var could not be opened

ORA-01152	file name was not restored from a sufficiently old backup

ORA-01170	file not found 'name'

ORA-01166	file number num is larger than num (num)

ORA-01144	file size (num blocks) exceeds maximum of num blocks

ORA-01163	file size in header num (bytes) does not match SIZE num (bytes)

ORA-01201	file size num in header does not match size num in control file

ORA-01566	file specified more than once in DROP LOGFILE

ORA-00317	file type str in header is not logfile

ORA-12402	file: str

PCC-00078	FIPS warning: Invalid ANSI SQL identifier

PCC-00074	FIPS warning: Multiply defined host variable in line num of file name

PCC-01515	FIPS warning: Undeclared host variable hostvar at line num in file name

PCC-01513	FIPS warning: Unsupported datatype in line num of file name

ORA-01724	floating point precision is out of range (1 to 126)

ORA-02068	following severe error from name

IMP-00015	following statement failed because the object already exists: str

IMP-00017	following statement failed with Oracle message num: str

PCC-00104	FOR clause is an Oracle extension

PCC-02372	FOR clause not allowed in a SELECT statement

PCC-00056	FOR clause not allowed in SELECT statement at line num in file name

IMP-00025	for DBA export files, FROMUSER must be specified with TOUSER

PCC-01009	For HOST=COB74, a SQL statement must be followed by ELSE or "."

SQL*Load-00601	For INSERT option, table must be empty. Error on name

PLS-01421	FOR UPDATE clause

PCC-00102	FOR UPDATE is an Oracle extension

ORA-01786	FOR UPDATE of this query expression is not allowed

PCC-00053	FOR variable var is invalid type at line num in file name

MOD-00050	Formal parameter param is not used in procedure

PCC-02310	Formal parameter VARCHAR's must be declared as pointers

SQL*Load-00200	FORMAT clause should not be present - flat data files only

ORA-01810	format code appears twice

ORA-01820	format code cannot appear in date input format

IMP-00011	formatted table data not currently supported

PLS-00103	found 'str' but expected one of the following: 'str'

PCC-02203	Found end of file when not expected

PCC-02018	Found end-of-file while scanning comment

PCC-02010	Found end-of-file while scanning string literal

PCC-02011	Found identifier greater than 128 characters (truncated)

ORA-02295	found more than one enable/disable clause for constraint

PCC-02201	Found syntax error

PCC-02322	Found undefined identifier

PCC-02200	Found unrecognized punctuation sequence

ORA-02170	FREELIST GROUPS storage option not allowed

ORA-02169	FREELISTS storage option not allowed

ORA-00923	FROM keyword not found where expected

IMP-00024	full import mode, cannot specify FROMUSER or TABLES parameter

ORA-01841	(full) year must be between -4713 and +4713

PLS-00231	function 'name' may not be used in SQL

PCC-02357	Function calls may not be used as host variable expressions

PLS-00203	function DECODE must be called with at least 3 non-Boolean arguments

PLS-00233	function name used as an exception name in WHEN clause

PLS-00204	function or pseudocolumn 'name' may be used inside a SQL statement only

ORA-09120	Gateway has timed out access to target system.

ORA-09102	Gateway internal communication error

ORA-09104	Gateway internal cross-communication error

ORA-09103	Gateway internal protocol error

ORA-01606	GC_FILES_TO_LOCKS not identical to that of another mounted instance

ORA-01607	GC_LCK_PROCS (num) is not the same as other instances (num)

ORA-01560	global hash table size mismatch for GC_name (num != num)

ORA-01572	global hash table size num for rollback segments is too small for rollback segment ID num

ORA-02069	global_names parameter must be set to TRUE for this operation

ORA-12441	grant already exists at a different label

ORA-01994	GRANT failed: cannot add users to public password file

ORA-01996	GRANT failed: password file name is full

ORA-01997	GRANT failed: user name is identified externally

ORA-01720	grant option does not exist for 'str'

ORA-01713	GRANT OPTION does not exist for that privilege

ORA-01928	GRANT option not granted for all privileges

ORA-00935	group function is nested too deeply

ORA-00934	group function is not allowed here

ORA-01224	group number in header name does not match GROUP name

ORA-02459	hashkey value must be a positive integer

ORA-02458	HASHKEYS must be specified for a HASH CLUSTER

SQL-02111	Heap consistency error

ORA-01818	'HH24' precludes use of meridian indicator

PCC-00068	Host and indicator variables may not have the same name

PCC-02365	Host and its indicator variable must have the same array dimensions

ORA-03112	host string syntax error

PCC-02364	Host structure and its indicator must have the same number of fields

PCC-02344	Host variable arrays must all be of equal size

PCC-02336	Host variable expression has invalid type

MOD-00062	Host variable for indicator is not recognized

PCC-02341	Host variable has illegal type

PCC-02362	Host variable not declared within SQL Declare Section

PCC-00069	Host variable var has unsupported datatype at line num in file name

PCC-02206	Host variables are not permitted within a DDL statement

PCC-02339	Host variables cannot be of union types

ORA-01836	hour conflicts with seconds in day

ORA-01813	hour may only be specified once

ORA-01850	hour must be between 0 and 23

ORA-01849	hour must be between 1 and 12

ORA-12826	hung parallel query server was killed

ORA-00340	I/O error processing online log name of thread num

ORA-01943	IDENTIFIED BY already specified

ORA-01942	IDENTIFIED BY and EXTERNALLY cannot both be specified

ORA-01938	IDENTIFIED BY must be specified for CREATE USER

ORA-01944	IDENTIFIED EXTERNALLY already specified

PLS-00208	identifier 'name' is not a legal cursor attribute

PLS-00201	identifier 'name' must be declared

PLS-00207	identifier 'name', applied to implicit cursor SQL, is not a legal cursor attribute

PCC-02358	Identifier following ARRAYLEN must be the name of an array

PCC-01202	Identifier ident truncated to 31 characters

PLS-00413	identifier in CURRENT OF clause is not a cursor name

ORA-00972	identifier is too long

PCC-01511	Identifier on line num in file name was too long for code generated in file name

PLS-01401	Identifier over 18 characters long

PCC-02308	Identifier required in this function definition

PCC-02359	Identifier specifying ARRAYLEN dimension must be an integer

ORA-00100	idle public server terminating

SQL*Load-00406	If data is all generated, number to load cannot be ALL

SQL*Load-00407	If data is all generated, number to skip is meaningless

DBA-00103	illegal ARCHIVE LOG option

ORA-01974	Illegal archive option

ORA-01760	illegal argument for function

LCC-00210	illegal assignment operator symbol

LCC-00114	illegal boolean response parameter

ORA-01601	illegal bucket size in clause "str" of GC_FILES_TO_LOCKS

ORA-02035	illegal bundled operation combination

PCC-02317	Illegal cast type expression

ORA-01975	Illegal character in change number num

SQL*Load-00304	Illegal combination of non-alphanumeric characters

ORA-02383	illegal cost factor

PCC-02351	Illegal datatype equivalencing operation

PLS-00376	illegal EXIT statement; it must appear inside a loop

PLS-00374	illegal EXIT statement; it must appear inside the loop labeled 'name'

ORA-01604	illegal file number range in clause "str" of GC_FILES_TO_LOCKS

PCC-02371	Illegal FOR clause

PCC-02309	Illegal formal parameter declaration

PLS-00375	illegal GOTO statement; this GOTO cannot branch to label 'name'

ORA-01603	illegal grouping in clause "str" of GC_FILES_TO_LOCKS

LCC-00112	illegal integer radix specification character

PCC-02305	Illegal mixing of new and old style C function declarations

DBA-00121	illegal MONITOR option

PCC-02306	Illegal name of C function

PCC-02316	Illegal operator in constant expression

ORA-01771	illegal option for a clustered table

ORA-02065	illegal option for ALTER SYSTEM

ORA-00277	Illegal option to the UNTIL recovery flag str

PLS-00701	illegal Oracle error number num for PRAGMA EXCEPTION_INIT

DBA-00104	illegal RECOVER option

ORA-00274	illegal recovery option str

ORA-00300	illegal redo log block size num specified -exceeds limit of num

ORA-00949	illegal reference to remote database

DBA-00110	illegal SET option

DBA-00111	illegal SHOW option

DBA-00116	illegal SHUTDOWN option

DBA-00119	illegal STARTUP option

PCC-02326	Illegal structure reference operation

PCC-00070	Illegal syntax. Exponential value in SQL statement: text

PLS-01702	Illegal syntax in COMMIT WORK statement

PLS-01701	Illegal syntax in ROLLBACK WORK statement

ORA-00997	illegal use of LONG datatype

ORA-01413	illegal value in packed decimal number buffer

ORA-01036	illegal variable name/number

ORA-01741	illegal zero-length identifier

ORA-01089	immediate shutdown in progress - no operations are permitted

ORA-02005	implicit (-1) length not valid for this bind or define datatype

IMP-00000	Import terminated unsuccessfully

IMP-00023	Import views not installed, please notify your DBA

PLS-01710	In a positioned DELETE or UPDATE statement, the cursor name must be of length 1

PLS-00372	in a procedure, RETURN statement cannot contain an expression

PLS-01472	In a set_function_specification, if DISTINCT is present, the expression must be a column_specification

PCC-01004	In an EXEC statement at end-of-file

PLS-00326	IN clause must contain same number of expressions as subquery

PLS-00485	in exception handler, 'name' must be an exception name

PLS-00227	IN formal parameter 'name' not allowed in this context

ORA-09124	In name argument name: Index out of range

PLS-01707	In positioned DELETE or UPDATE statement, table must be identified in specification of cursor

PLS-00368	in RAISE statement, 'name' must be an exception name

PLS-01708	In searched DELETE, UPDATE or INSERT, table must not appear in FROM clause of subqueries in search condition

MOD-00073	INAME option is specified but not meaningful

PLS-00120	inappropriate argument in OPEN statement

ORA-02460	inappropriate index operation on a hash cluster

ORA-01744	inappropriate INTO

ORA-02465	inappropriate use of the HASH IS option

ORA-02461	inappropriate use of the INDEX option

PCC-02016	Include file pathname is too long

SQL-02106	Inconsistent cursor cache (invalid Oracle cursor number)

SQL-02104	Inconsistent cursor cache (no CUC available)

SQL-02102	Inconsistent cursor cache (no CUC entry for this UCE)

SQL-02105	Inconsistent cursor cache (no CUC entry in cache)

SQL-02103	Inconsistent cursor cache (out-of-range CUC ref)

SQL-02101	Inconsistent cursor cache (UCE/CUC mismatch)

ORA-00932	inconsistent datatypes

SQL-02110	Inconsistent host cache (invalid SQI type)

SQL-02109	Inconsistent host cache (out-of-range SIT ref)

ORA-00356	inconsistent lengths in change description

SQL*Load-00934	Incorrect data file name specified for table tabnam

ORA-04002	INCREMENT must be a non-zero integer

ORA-04005	INCREMENT must be less than MAXVALUE minus MINVALUE

EXP-00029	incremental export mode and consistent mode are not compatible

ORA-01502	index 'str.name' is in direct load state

ORA-08100	index is not valid - see trace file for diagnostics

ORA-08101	index key does not exist root dba num, dba num (num)

ORA-08102	index key not found, obj# num, dba num (num)

ORA-01448	index must be dropped before changing to desired type

SQL*Load-00257	Index name specified in SORTED INDEXES does not exist on table name

ORA-02365	index name was left in Direct Load State due to

ORA-02367	index name was loaded.

SQL*Load-00260	Index num is in an invalid state

ORA-12445	index/row label mismatch - see trace file

PCC-02363	Indicator variable must be a structure

ORA-01746	indicator variable not permitted here

PCC-00024	Indicator variable var has wrong type or length at line num in file name

PCC-02367	Indicator variables must be declared as type short

PCC-02348	Indicators are not allowed in EXEC IAF statements

SQL*Load-00620	Initial enclosing character not found

ORA-02361	initial enclosing character not found

ORA-02203	INITIAL storage options not allowed

ORA-09119	Initialization file contains error.

ORA-00065	initialization of FIXED_DATE failed

DBA-00304	input file I/O error [num] - input aborted

PCC-00122	Input file name and output file name are identical

PCC-00072	Input file name length exceeds 14 characters

ORA-01840	input value not long enough for date format

PLS-00396	INSERT statement's subquery yields wrong number of columns

ORA-01401	inserted value too large for column

ORA-01576	instance locking protocol version num incompatible with Oracle Version num

DBA-00321	instance name too long

ORA-00265	instance recovery required, cannot set ARCHIVELOG mode

ORA-12824	INSTANCES DEFAULT may not be specified here

ORA-12489	insufficient MAC privilege to alter session.

ORA-12428	insufficient MAC privileges

ORA-00944	insufficient number of clustered columns

IMP-00014	insufficient Oracle privileges to do import

DBA-00336	insufficient privilege for SHOW PARAMETERS

DBA-00329	insufficient privilege for SHOW SGA

DBA-00328	insufficient privilege for this display

PLS-00904	insufficient privilege to access object 'name'

ORA-01031	insufficient privileges

ORA-01039	insufficient privileges on underlying objects of the view

ORA-04060	insufficient privileges to execute name

ORA-12487	insufficient privileges to set label to DBHIGH or DBLOW

ORA-12438	insufficient privileges to validate constraint on all rows

LCC-00113	integer conversion error or negative integer parameter

DBA-00125	integer value overflow

ORA-02017	integer value required

ORA-02292	integrity constraint (str.name) violated -child record found

ORA-02291	integrity constraint (str.name) violated -parent key not found

MOD-00065	Interface definition missing for procedure name

SQL*Load-00705	Internal error

SQL*Load-00702	Internal error - str

ORA-00606	internal error code

ORA-00600	internal error code, arguments: [num], [?], [?], [?], [?], [?]

DBA-00300	internal error code, arguments: [num], [str]

LCC-00100	internal error, argument num

ORA-01041	internal error. HOSTDEF extension does not exist

SQL*Load-00704	Internal error:  str [num]

SQL*Load-00703	Internal error: argument num

EXP-00006	internal inconsistency error

ORA-01431	internal inconsistency in GRANT command

ORA-01443	internal inconsistency; illegal datatype in resultant view column

ORA-01743	internal inconsistency; illegal user function index

ORA-01444	internal inconsistency; internal datatype maps to invalid external type

ORA-01058	internal New Upi interface error

MOD-00036	Internal programming exception

ORA-00602	internal programming exception

PLS-00377	internal type PLS_INTEGER is not included in this release of PL/SQL

PLS-01420	INTERSECT and MINUS set operators are not ANSI

PLS-00403	INTO list of FETCH statement contains illegal assignment target

PLS-00387	INTO variable cannot be a database object

MOD-00059	INTO variable var was not listed as a formal parameter

ORA-03281	invalid ALLOCATE EXTENT option

ORA-02230	invalid ALTER CLUSTER option

ORA-00940	invalid ALTER command

DBA-00139	invalid ALTER DATABASE option

ORA-02243	invalid ALTER INDEX or ALTER SNAPSHOT option

ORA-02244	invalid ALTER ROLLBACK SEGMENT option

ORA-01735	invalid ALTER TABLE option

ORA-01490	invalid ANALYZE command

DBA-00124	invalid ARCHIVE destination

DBA-00131	invalid ARCHIVE TO device

SQL*Load-00101	Invalid argument for username/password

ORA-01414	invalid array length when trying to bind array

PCC-00117	Invalid ARRAYLEN length variable type

ORA-01983	invalid auditing option for DEFAULT

ORA-01984	invalid auditing option for procedures/packages/functions

ORA-01914	invalid auditing option for sequence numbers

ORA-01982	invalid auditing option for tables

ORA-01915	invalid auditing option for views

DBA-00134	invalid AUTORECOVERY switch

SQL*Load-00104	Invalid bad file name on command line

ORA-12461	invalid binary label

ORA-00911	invalid character

PCC-01002	Invalid character char in indicator area at line num in file name

ORA-01040	invalid character in password; logon denied

ORA-02233	invalid CLOSE mode

ORA-02227	invalid cluster name

ORA-00904	invalid column name

DBA-00127	invalid combination of STARTUP options

ORA-01956	invalid command when OS_ROLES are being used

DBA-00140	invalid COMPATIBILITY switch

PLS-00378	invalid compilation unit for this release of PL/SQL

ORA-01021	invalid context size specified

PCC-01003	Invalid continuation at line num in file name

SQL*Load-00102	Invalid control file name on command line

ORA-00901	invalid CREATE command

ORA-02158	invalid CREATE INDEX option

ORA-01513	invalid current time returned by operating system

ORA-01001	invalid cursor

DBA-00109	invalid CYCLE value

ORA-03280	invalid DATA FILE file name specified

SQL*Load-00105	Invalid data file name on command line

DBA-00114	invalid database name

DBA-00133	invalid datafile list

ORA-00902	invalid datatype

PCF-00274	invalid datatype

ORA-01024	invalid datatype in OCI call

DBA-00128	invalid DEBUG switch

PCC-02373	Invalid declaration in EXEC SQL DECLARE section

PCC-02304	Invalid declaration of C function

ORA-01948	invalid DEFAULT ROLE specification

ORA-02155	invalid DEFAULT tablespace identifier

SQL-02108	Invalid descriptor passed to runtime library

SQL*Load-00115	Invalid direct path option

SQL*Load-00106	Invalid discard file name on command line

ORA-00950	invalid DROP option

DBA-00106	invalid ECHO switch

PCC-01512	Invalid EXEC SQL INCLUDE of file name found at line num in file name

IMP-00012	invalid export mode (num) in header

ORA-02236	invalid file name

ORA-02237	invalid file size

DBA-00150	invalid FLAGGER switch

ORA-00991	invalid format for GRANT command

ORA-03287	invalid FREELIST GROUP specified

ORA-00919	invalid function

ORA-02450	invalid hash option - missing keyword IS

ORA-02452	invalid HASHKEYS option value

ORA-01465	invalid hex number

DBA-00146	invalid HISTORY value

PCC-00009	Invalid host variable at column name in line num of file name

PCC-00026	Invalid host variable vat at line num in file name

ORA-01745	invalid host/bind variable name

ORA-00953	invalid index name

ORA-02218	invalid INITIAL storage option value

ORA-02207	invalid INITRANS option value

DBA-00105	invalid INSTANCE name

ORA-03279	invalid INSTANCE specified

PCC-01102	Invalid label at line num in file name

ORA-01483	invalid length for DATE or NUMBER bind variable

ORA-12457	invalid length for MLSLABEL bind variable

ORA-01459	invalid length for variable character string

ORA-01458	invalid length inside variable character string

DBA-00147	invalid LINES value

SQL*Load-00103	Invalid log file name on command line

ORA-02221	invalid MAXEXTENTS storage option value

ORA-02226	invalid MAXEXTENTS value (max allowed: num)

SQL*Load-00112	Invalid maximum bind array size

SQL*Load-00107	Invalid maximum number of discards

SQL*Load-00110	Invalid maximum number of errors

ORA-02209	invalid MAXTRANS option value

ORA-02220	invalid MINEXTENTS storage option value

ORA-02232	invalid MOUNT mode

ORA-00103	invalid network protocol; reserved for use by dispatchers

ORA-04076	invalid NEW or OLD specification

ORA-02219	invalid NEXT storage option value

ORA-01488	invalid nibble or byte in the input data

ORA-12702	invalid NLS parameter string used in SQL function

ORA-12700	Invalid NLS parameter value (var)

ORA-01722	invalid number

ORA-01481	invalid number format model

ORA-00909	invalid number of arguments

ORA-01730	invalid number of column names specified

SQL*Load-00108	Invalid number of logical records to load

SQL*Load-00109	Invalid number of logical records to skip

SQL*Load-00111	Invalid number of rows for bind array or data saves

ORA-06566	invalid number of rows specified

ORA-06567	invalid number of values specified

DBA-00145	invalid object name for DESCRIBE

DBA-00144	invalid object type for DESCRIBE

ORA-01010	invalid OCI operation

ORA-02141	invalid OFFLINE option

ORA-02288	invalid OPEN mode

SQL-02122	Invalid OPEN or PREPARE for this database connection

ORA-02223	invalid OPTIMAL storage option value

ORA-02248	invalid option for ALTER SESSION

ORA-01967	invalid option for CREATE CONTROLFILE

ORA-02165	invalid option for CREATE DATABASE

ORA-02176	invalid option for CREATE ROLLBACK SEGMENT

ORA-02180	invalid option for CREATE TABLESPACE

ORA-02173	invalid option for DROP TABLESPACE

ORA-01986	invalid option for OPTIMIZER_GOAL

ORA-12818	invalid option in PARALLEL clause

PCC-00032	Invalid option optnam

ORA-02181	invalid option to ROLLBACK WORK

ORA-01057	invalid or ambiguous block.field reference in user exit

ORA-04050	invalid or missing procedure, function, or package name

PCC-00093	Invalid or obsolete option, ignored

PCC-02355	Invalid or obsolete option, ignored

ORA-02376	invalid or redundant resource

ORA-12705	Invalid or unknown NLS parameter value specified

PCC-00089	Invalid Oracle TYPE specification

ORA-02006	invalid packed decimal format string

ORA-01991	invalid password file name

ORA-00974	invalid PCTFREE value (percentage)

ORA-02222	invalid PCTINCREASE storage option value

DBA-00113	invalid PFILE name

LCC-00128	invalid positional parameter value val

DBA-00118	invalid process identifier or invalid statistics class

ORA-00985	invalid program name

ORA-02187	invalid quota specification

ORA-09108	Invalid record in target system.

PLS-00487	invalid reference to variable 'name'

ORA-04074	invalid REFERENCING name

ORA-00920	invalid relational operator

ORA-00400	invalid release value val for parameter val

ORA-02377	invalid resource limit

DBA-00141	invalid RETRIES value

ORA-01937	invalid role name

ORA-02175	invalid rollback segment name

ORA-02245	invalid ROLLBACK SEGMENT name

SQL-02118	Invalid row for a WHERE CURRENT OF operation

ORA-01410	invalid ROWID

ORA-01493	invalid SAMPLE size specified

ORA-02277	invalid sequence name

DBA-00149	invalid SERVEROUTPUT switch

ORA-00022	invalid session id; access denied

DBA-00122	invalid SET numeric parameter

ORA-02078	invalid setting for ALTER SYSTEM FIXED_DATE

SQL*Load-00113	Invalid silent mode option

ORA-02229	invalid SIZE option value

ORA-03277	invalid SIZE specified

ORA-00101	invalid specification for initialization parameter MTS_DISPATCHERS

ORA-00119	invalid specification for system parameter MTS_LISTENER_ADDRESS

DBA-00100	invalid SPOOL file name

SQL-02114	Invalid SQL Cursor usage: trying to close a closed cursor

SQL-02117	Invalid SQL Cursor usage: trying to open an opened cursor

PCC-00003	Invalid SQL Identifier at column name in line num of file name

ORA-00900	invalid SQL statement

DBA-00120	invalid STOPONERROR switch

ORA-02143	invalid STORAGE option

PCC-00002	Invalid syntax at column name in line num of file name

ORA-00903	invalid table name

PLS-00489	invalid table reference:   'name' must be a column in this expression

DBA-00117	invalid tablespace name

ORA-02140	invalid tablespace name

DBA-00123	invalid tablespace name list

ORA-02156	invalid TEMPORARY tablespace identifier

DBA-00148	invalid TERM switch (use either PAGE or NOPAGE)

DBA-00107	invalid TERMOUT switch

DBA-00108	invalid TIMING switch

ORA-00151	invalid transaction ID

ORA-04075	invalid trigger action

ORA-04070	invalid trigger name

ORA-04079	invalid trigger specification

ORA-04072	invalid trigger type

ORA-04083	invalid trigger variable 'name'

ORA-03290	invalid truncate command - missing CLUSTER or TABLE keyword

ORA-03291	invalid truncate option - missing STORAGE keyword

PCC-01010	Invalid use of NULL character in character literal

PLS-00330	invalid use of type name or subtype name

ORA-01747	invalid user.table.column, table.column or columns specification

ORA-02003	invalid USERENV parameter

EXP-00004	invalid username or password

IMP-00004	invalid username or password

ORA-01017	invalid username/password; logon denied

ORA-12820	invalid value for DEGREE

ORA-02163	invalid value for FREELIST GROUPS

ORA-02168	invalid value for FREELISTS

ORA-12821	invalid value for INSTANCES

ORA-02162	invalid value for MAXDATAFILES

ORA-02161	invalid value for MAXLOGFILES

ORA-02171	invalid value for MAXLOGHISTORY

ORA-02240	invalid value for OBJNO or TABNO

ORA-02211	invalid value for PCTFREE or PCTUSED

PCC-00031	Invalid value given for option optnam

PCC-00130	Invalid value val for option optnam

ORA-00067	invalid value var for parameter var, must be at least var

ORA-00068	invalid value var for parameter var, must be between var and var

PLS-00488	invalid variable declaration:   object 'name' must be a type or subtype

DBA-00126	invalid VERIFY switch

ORA-00999	invalid view name

PCC-00008	Invalid WHENEVER action at column name in line num of file name

PCC-00007	Invalid WHENEVER condition at column name in line num of file name

SQL*Load-00641	Invalid zoned decimal nibble.

ORA-01115	IO error reading block from file name (block # num)

ORA-01114	IO error writing block to file name (block # num)

PCC-00067	IRECLEN exceeded. Line num in file name truncated

ORA-02064	iterated or long remote update with subquery not supported

ORA-01802	Julian date is out of range

ORA-01854	Julian date must be between 1 and 3442447

ORA-01811	Julian date precludes use of day of year

ORA-02269	key column cannot be of LONG datatype

ORA-02190	keyword TABLES expected

PCC-00105	Keyword WORK required here by ANSI

PCF-00257	keyword WORK required after COMMIT

PCF-00258	keyword WORK required after ROLLBACK

PLS-00219	label 'name' reference is out of scope

ORA-12452	label format string could not be parsed; check format codes

ORA-12416	label of audit must dominate user

ORA-12434	label of child record must dominate parent

ORA-12419	label of column must equal table

ORA-12429	label of comment must equal table or view

ORA-12423	label of constraint must equal table

ORA-12432	label of default role name must dominate user

ORA-12433	label of default role name must dominate user

ORA-12422	label of grant must dominate grantee name

ORA-12421	label of grant must dominate object

ORA-12418	label of index must equal table

ORA-12427	label of object must dominate schema

ORA-12424	label of object must dominate tablespace

ORA-12435	label of package body must equal package

ORA-12420	label of stored object must dominate referenced object name

ORA-12425	label of table must dominate cluster

ORA-12430	label of trigger must equal table

ORA-12426	label of user must dominate default or temporary tablespace

ORA-12431	label of user must dominate default profile

ORA-12450	label string could not be translated into binary label

IMP-00047	label string larger than 255 characters found at line num in mapfile

ORA-01479	last character in the buffer is not Null

ORA-00480	LCK* process terminated with error

ORA-12449	least upper bound resulted in an invalid operating system label

LCC-00204	left parentheses and no parameter specified parameter

PCC-00082	Length and scale specifications must be an integer

PCC-00092	Length and/or scale incompatible with specified Oracle datatype

PCC-00099	Length cannot be given for types ROWID, DATE, or MLSLABEL

ORA-01132	length of data file name 'name' exceeds limit of num characters

ORA-01133	length of logfile name 'name' exceeds limit of num characters

PLS-00406	length of SELECT list in subquery must match number of assignment targets

PCC-00114	Length spec required in EXEC SQL VAR statements for VARxxx types

ORA-00976	LEVEL, PRIOR, or ROWNUM not allowed here

ORA-00470	LGWR process terminated with error

ORA-00035	LICENSE_MAX_USERS cannot be less than current number of users

ORA-00253	limit of num exceeded by length num of archive string 'name'

ORA-00306	limit of num log writer instances in this database

ORA-00302	limit of num logs exceeded

ORA-06550	Line num, column num: str

PLS-00412	list of values not allowed as argument to this function or procedure

ORA-01492	LIST option not valid

ORA-01861	literal does not match format string

ORA-12456	literal string supplied does not match specified input format

MOD-00096	LNAME option is specified but not meaningful.

ORA-02371	loader must be at least version num for direct path

SQL*Load-00909	Loader views must be loaded (as SYS) for direct path to be used

ORA-01591	lock held by in-doubt distributed transaction num

ORA-02061	lock table specified list of non-colocated tables

ORA-00252	log 'name' of thread num is empty, cannot archive

ORA-00390	log name of thread name is being cleared, cannot become current log

ORA-00392	log name of thread name is being cleared, operation not allowed

ORA-00393	log name of thread name is needed for recovery of offline datafiles

ORA-01648	log var is the current log of disabled thread var

ORA-00326	log begins at change num, need earlier change num

ORA-00309	log belongs to wrong database

ORA-00353	log corruption near block num time stamp str

SQL*Load-00255	Log file for error recovery not used by SQL*Loader

ORA-00363	log is not the archived version

ORA-00346	log member marked as STALE

ORA-01517	log member: 'str'

ORA-01227	log name is inconsistent with other log

ORA-01609	log name is the current log for thread num - cannot drop members

ORA-01624	log name needed for crash recovery of thread num

ORA-00259	log name of open thread num is the current log, cannot archive

ORA-00347	log name of thread num expected block size num does not match num

ORA-00319	log name of thread num has incorrect log reset status

ORA-00305	log name of thread num inconsistent; belongs to another database

ORA-00261	log name of thread num is being archived or modified

ORA-00338	log name of thread num is more recent than control file

ORA-00322	log name of thread num is not current copy

ORA-00350	log name of thread num needs to be archived

ORA-00321	log name of thread num, cannot update logfile header

ORA-00318	log name of thread num, expected file size num does not match num

ORA-00314	log name of thread num, expected sequence # num does not match num

ORA-00327	log name of thread num, physical size num less than needed num

ORA-00316	log name of thread num, type str in header is not redo log file

ORA-00341	log name of thread num, wrong log # num in header

ORA-00315	log name of thread num, wrong thread # num in header

ORA-01623	log num is current log for thread num -cannot drop

ORA-00331	log version num incompatible with Oracle version num

ORA-00337	logfile 'name' does not exist and no size specified

ORA-00278	logfile 'name' no longer needed for this recovery

ORA-00324	logfile 'name' translated name 'name' too long, num characters exceeds num limit

ORA-02167	LOGFILE clause specified more than once

ORA-01184	logfile group num already exists

ORA-00359	Logfile group num does not exist

ORA-01185	logfile group number num is invalid

ORA-01900	LOGFILE keyword expected

ORA-01217	logfile member belongs to a different redo log file group

ORA-01218	logfile member is not from the same point-in-time

ORA-00336	logfile size num blocks is less than minimum num blocks

ORA-02362	logical record ended - second enclosing character not present

SQL*Load-00623	Logical record ended <#010A> second enclosure character not present

ORA-00024	logins from more than one process not allowed in single-process mode

ORA-01015	logon called recursively

ORA-12317	logon to database (link name name) denied

DBA-00330	logsource name too long

ORA-00063	LOG_FILES initialization parameter exceeded

ORA-00066	LOG_FILES is var but needs to be var to be compatible

IMP-00020	long column too large for column buffer size (num)

PLS-00364	loop index variable 'name' use is invalid

ORA-01775	looping chain of synonyms

PCC-00101	Lower case 'e' in floating point number is not ANSI

PCC-02209	Macro invocation has incorrect number of arguments

PCC-02313	Malformed VARCHAR declaration - missing length

DBA-00376	mandatory field has to be filled in before navigation is possible

DBA-00370	mandatory field/list needs to be filled in

DBA-00377	mandatory list item has to be selected before navigation is possible

MOD-00077	Mandatory parameter SQLCODE or SQLSTATE is missing.

ORA-00258	manual archiving in NOARCHIVELOG mode must identify log

ORA-01628	max # of extents (num) reached for rollback segment num

ORA-01632	max # of extents (num) reached in index name

ORA-01631	max # of extents (num) reached in table name

ORA-01630	max # of extents (num) reached in temp segment in tablespace name

ORA-01629	max # of extents (num) reached saving undo for tablespace name

ORA-01656	max num extents (%num) reached in cluster name.name

ORA-01165	MAXDATAFILES may not exceed num

ORA-01559	MAXEXTENTS for rollback segment must be greater than 1

ORA-01553	MAXEXTENTS must be no smaller than the num extents currently allocated

SQL*Load-00602	Maximum converted length num of column name.name is too big for bind array

ORA-01450	maximum key length len exceeded

SQL*Load-00603	Maximum length num of column name.name is too big for bind array

ORA-01794	maximum number of cluster columns is 16

ORA-02257	maximum number of columns exceeded

ORA-01792	maximum number of columns in a table or view is 254

ORA-12459	maximum number of columns in a Trusted Oracle table is 253

ORA-01574	maximum number of concurrent transactions exceeded

SQL*Load-00413	Maximum number of constraints (num) exceeded on table name

ORA-00059	maximum number of DB_FILES exceeded

ORA-00703	maximum number of dictionary cache instance locks exceeded

ORA-00055	maximum number of DML locks exceeded

ORA-00052	maximum number of enqueue resources (num) exceeded

ORA-00053	maximum number of enqueues exceeded

ORA-01795	maximum number of expressions in a list is 254

ORA-01793	maximum number of index columns is 16

ORA-00568	maximum number of interrupt handlers exceeded

ORA-12341	maximum number of open mounts exceeded

ORA-00020	maximum number of processes (num) exceeded

ORA-09118	Maximum number of savepoints exceeded.

ORA-08001	maximum number of sequences per session exceeded

ORA-00019	maximum number of session licenses exceeded

ORA-08000	maximum number of session sequence lists exceeded

ORA-00018	maximum number of sessions exceeded

SQL*Load-00258	Maximum number of sorted indexes (num) exceeded on table name.

ORA-00057	maximum number of temporary table locks exceeded

SQL*Load-00414	Maximum number of triggers (num) exceeded on table name

ORA-01925	maximum of num enabled roles exceeded

ORA-01000	maximum open cursors exceeded

ORA-01778	maximum subquery nesting level exceeded

ORA-01213	MAXINSTANCES may not exceed num

ORA-01222	MAXINSTANCES of num requires MAXLOGFILES be at least num, not num

ORA-01164	MAXLOGFILES may not exceed num

ORA-01214	MAXLOGHISTORY may not exceed num

ORA-01212	MAXLOGMEMBERS may not exceed num

ORA-04009	MAXVALUE cannot be made to be less than the current value

ORA-01749	may not GRANT/REVOKE privileges to/from self

ORA-01456	may not perform insert/delete/update operation inside a READ ONLY transaction

ORA-12005	may not schedule automatic refresh for times in the past

ORA-01773	may not specify column datatypes in this CREATE TABLE

ORA-01108	media recovery active on file name

ORA-00275	media recovery has already been started

ORA-00281	media recovery may not be performed using dispatcher

ORA-01112	media recovery not started

ORA-00273	media recovery of direct load data that was not logged

ORA-00362	member is required to form a valid logfile in group name

ORA-02478	merge into base segment would overflow MAXEXTENTS limit

ORA-01556	MINEXTENTS for rollback segment must be greater than 1

ORA-01570	MINEXTENTS must be no larger than the num extents currently allocated

ORA-01851	minutes must be between 0 and 59

ORA-01837	minutes of hour conflicts with seconds in day

ORA-04007	MINVALUE cannot be made to exceed the current value

ORA-04004	MINVALUE must be less than MAXVALUE

PCC-00004	Mismatched IF/ELSE/ENDIF block at line num in file name

ORA-00914	missing ADD keyword

ORA-03282	missing ALLOCATE EXTENT option

ORA-00930	missing asterisk

ORA-04071	missing BEFORE or AFTER keyword

ORA-00924	missing BY keyword

ORA-01973	Missing change number

ORA-01976	Missing change number

ORA-00958	missing CHECK keyword

ORA-00941	missing cluster name

ORA-00917	missing comma

ORA-02013	missing CONNECT keyword

ORA-02199	missing DATAFILE clause

ORA-01740	missing double quote in identifier

ORA-00927	missing equal sign

ORA-02246	missing EVENTS text

ORA-01798	missing EXCEPTION keyword

ORA-00936	missing expression

ORA-02029	missing FILE keyword

ORA-01605	missing file numbers in clause "str" of GC_FILES_TO_LOCKS

ORA-00993	missing GRANT keyword

ORA-00952	missing GROUP keyword

ORA-02010	missing host connect string

ORA-00954	missing IDENTIFIED keyword

ORA-00931	missing identifier

ORA-01738	missing IN keyword

ORA-00968	missing INDEX keyword

DBA-00337	missing instance name

ORA-00925	missing INTO keyword

ORA-00905	missing keyword

ORA-02000	missing keyword 'name'

LCC-00203	missing keyword keyword

ORA-00906	missing left parenthesis

ORA-02026	missing LINK keyword

ORA-01707	missing LIST keyword

DBA-00102	missing LOG keyword

ORA-01009	missing mandatory parameter

ORA-01739	missing MODE keyword

ORA-00908	missing NULL keyword

ORA-01710	missing OF keyword

ORA-00969	missing ON keyword

PCC-00033	Missing operand for option optnam

ORA-00994	missing OPTION keyword

ORA-12819	missing options in PARALLEL clause

ORA-01424	missing or illegal character following the escape character

ORA-01506	missing or illegal database name

ORA-02142	missing or invalid ALTER TABLESPACE option

ORA-00956	missing or invalid auditing option

ORA-02250	missing or invalid constraint name

ORA-00986	missing or invalid group names(s)

ORA-02066	missing or invalid MTS_DISPATCHERS text

ORA-00922	missing or invalid option

ORA-02231	missing or invalid option to ALTER DATABASE

ORA-01979	missing or invalid password for role 'name'

ORA-00988	missing or invalid password(s)

ORA-00990	missing or invalid privilege

ORA-02421	missing or invalid schema authorization identifier

ORA-02422	missing or invalid schema element

ORA-00026	missing or invalid session id

ORA-00995	missing or invalid synonym identifier

ORA-00987	missing or invalid username(s)

ORA-02249	missing or invalid value for MAXLOGMEMBERS

ORA-00929	missing period

ORA-00982	missing plus sign

PCC-00095	Missing PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement

ORA-12453	missing quote in literal string

ORA-02177	Missing required group number

ORA-02174	Missing required thread number

ORA-00907	missing right parenthesis

ORA-02420	missing schema authorization clause

ORA-00928	missing SELECT keyword

ORA-01978	Missing sequence number

ORA-00971	missing SET keyword

ORA-02145	missing STORAGE option

ORA-01703	missing SYNONYM keyword

ORA-00966	missing TABLE keyword

ORA-01977	Missing thread number

ORA-00946	missing TO keyword

PCC-02318	Missing type expression

ORA-01935	missing user or role name

ORA-02012	missing USING keyword

ORA-00114	missing value for initialization parameter MTS_SERVICE

LCC-00209	missing value for keyword at end of string keyword

ORA-00926	missing VALUES keyword

ORA-00967	missing WHERE keyword

ORA-00970	missing WITH keyword

MOD-00038	Module name required when output language is Ada

DBA-00359	monitor already active

DBA-00306	monitor cycle interval time out of range (1 - num)

ORA-01833	month conflicts with Julian date

ORA-01816	month may only be specified once

SQL*Load-00412	More columns specified for table name than the maximum (num)

ORA-01602	more locks in GC_FILES_TO_LOCKS than reserved in GC_DB_LOCKS

SQL*Load-00305	More than one end of file character encountered

ORA-01105	mount is incompatible with mounts by other instances

ORA-00121	MTS_SERVERS specified without MTS_DISPATCHERS

ORA-00116	MTS_SERVICE name is too long

ORA-02027	multi-row UPDATE of LONG column is not supported

ORA-02353	multibyte character error

SQL*Load-00625	Multibyte character error in control file

ORA-01026	multiple buffers of size > 2000 in the bind list

PCC-01008	Multiple element records not allowed in Declare Section

PLS-00703	multiple instances of named argument in list

ORA-01076	multiple logons per process not yet supported

EXP-00023	must be a DBA to do Full Database export

IMP-00007	must be a DBA to import objects to another user's account

ORA-12406	must be at DBHIGH (name) in O/S to add files to a tablespace

ORA-00215	must be at least one control file

ORA-12442	must be at same label as user to modify default roles

ORA-12414	must be DBHIGH (var) to startup database

ORA-02241	must be of form EXTENTS (FILE num BLOCK num SIZE num, ...)

EXP-00022	must be SYS or SYSTEM to do incremental export

ORA-02043	must end current transaction before executing command

ORA-01192	must have at least one enabled thread

ORA-01966	must have OS DBA privilege to CREATE CONTROLFILE

PCC-00042	Must include SQLCA file when MODE=ANSI and WHENEVER SQLWARNING used

ORA-00998	must name this expression with a column alias

ORA-01475	must reparse cursor to change bind variable datatype

MOD-00078	Must specify a user if generating stubs from stored package.

IMP-00031	Must specify FULL=Y or provide FROMUSER/TOUSER or TABLE arguments

IMP-00046	must specify MLS_MAPFILE with MLS_LISTLABELS

ORA-01198	must specify size for file 'name' if RESETLOGS

PCC-00062	Must use option SQLCHECK=SEMANTICS when there is embedded PL/SQL

ORA-01588	must use RESETLOGS option for database open

ORA-01589	must use RESETLOGS or NORESETLOGS option for database open

ORA-02264	name already used by an existing constraint

ORA-01111	name for data file name is unknown - rename to correct file

ORA-04063	name has errors

ORA-00955	name is already used by an existing object

MOD-00054	name is not a valid cursor reference

EXP-00010	name is not a valid username

PLS-01456	Name length cannot exceed 3.

DBA-00366	name name is malformed, it must be of form [[a.]b.]c@dblink

ORA-00266	name of archived logfile needed

ORA-00267	name of archived logfile not needed

PLS-00124	name of exception expected for first argument in EXCEPTION_INIT pragma

ORA-08002	name.CURRVAL is not yet defined in this session

EXP-00011	name.name does not exist

ORA-08004	name.NEXTVAL str [MIN][MAX]VALUE and cannot be instantiated

SQL*Load-00405	Need termination delim with optional enclosure delim: column name.name

ORA-02263	need to specify the datatype for this column

ORA-00978	nested group function without GROUP BY

PLS-00232	nested packages not permitted

LCC-00207	nested parentheses encountered command

ORA-00915	network access of dictionary table not currently allowed

ORA-00102	network protocol ('str') cannot be used by the dispatchers

ORA-03123	network read would block

ORA-04082	NEW or OLD references not allowed in table level triggers

ORA-01764	new update value of join is not guaranteed to be unique

DBA-00349	no available rollback segments exist

PLS-00369	no choices may appear with choice OTHERS in an exception handler

PLS-00414	no column 'name' in table

ORA-01403	no data found

ORA-00371	no free buffer handles available

PLS-00222	no function with name 'name' exists in this scope

PCC-00035	No host language specified

MOD-00027	No input file name specified

PCC-00036	No input file name specified

ORA-03121	no interface driver connected - function not performed

DBA-00344	no items for the requested operation currently exist

ORA-02270	no matching unique or primary key for this column-list

ORA-00286	no members available, or no member contains valid data

ORA-02374	No more slots for read buffer queue

ORA-02202	no more tables permitted in this cluster

ORA-02079	no new sessions may join a committing  distributed transaction

DBA-00355	no offline data files exist

DBA-00350	no offline rollback segments exist

DBA-00347	no offline tablespaces exist

DBA-00354	no offline tablespaces exist

DBA-00351	no online rollback segments exist

DBA-00353	no online tablespaces being backed up exist

DBA-00348	no online tablespaces exist

DBA-00352	no online tablespaces exist for backup

PLS-01454	No operator may be used with values of data type CHAR

ORA-02144	no option specified for ALTER CLUSTER

ORA-02247	no option specified for ALTER SESSION

ORA-02242	no options specified for ALTER INDEX

ORA-02286	no options specified for ALTER SEQUENCE

ORA-02210	no options specified for ALTER TABLE

ORA-02157	no options specified for ALTER USER

PCC-01510	No package, procedure, or function statement seen in name

PLS-00422	no PL/SQL translation for the bind type given for this bind variable

ORA-02058	no prepared transaction found with ID num

EXP-00009	no privilege to export name's table name

ORA-01950	no privileges on tablespace 'name'

ORA-01929	no privileges to GRANT

ORA-01930	no privileges to REVOKE

ORA-01620	no public threads are available for mounting

ORA-00264	no recovery required

DBA-00357	no roles exist

ORA-02031	no ROWID for fixed tables

IMP-00039	no space for owner name in create string

DBA-00308	no spool file opened

ORA-01003	no statement parsed

EXP-00003	no storage definition found for segment (name, num)

DBA-00343	no such parameter

ORA-01032	no such userid

SQL*Load-00624	No terminator found after TERMINATED and ENCLOSED field

ORA-02363	no terminator found after TERMINATED and ENCLOSED field

PCC-02202	No typedef name was given

DBA-00346	no unresolved in-doubt transactions exist

DBA-00345	no user sessions exist

DBA-00356	no users exist

DBA-00358	no users or roles exist

PCC-00100	Non integer label is not ANSI

PLS-01424	Non-ANSI order of clauses

SQL*Load-00605	Non-data dependent Oracle error occurred load discontinued

EXP-00032	non-DBAs may not export other users

ORA-04066	non-executable object, name

SQL*Load-00303	Non-hex character encountered where hex char expected

PLS-00325	non-integral numeric literal num is inappropriate in this context

ORA-12447	non-secure protocol used; connection denied

ORA-02439	non-unique index exists on unique/primary key constraint

ORA-02008	non-zero scale specified for non-numeric column

ORA-01516	nonexistent log/data file 'name'

ORA-00448	normal completion of background process

ORA-00000	normal, successful completion

ORA-01716	NOSORT may not be used with a cluster index

ORA-01409	NOSORT option may not be used; rows are not in ascending order

ORA-01205	not a data file - type number in header is num

ORA-00979	not a GROUP BY expression

ORA-00360	not a logfile member:  name

SQL*Load-00271	Not a parallel load. Table level OPTIONS statement ignored.

ORA-01791	not a SELECTed expression

ORA-00937	not a single-group group function

ORA-01846	not a valid day of the week

IMP-00010	not a valid export file, header failed verification

ORA-01843	not a valid month

ORA-01857	not a valid time zone

ORA-01008	not all variables bound

DBA-00302	not connected to a database

ORA-03114	not connected to Oracle

ORA-00938	not enough arguments for function

ORA-00947	not enough values

ORA-04065	not executed, altered or dropped name

ORA-04064	not executed, invalidated name

ORA-04067	not executed, name does not exist

PCC-00012	Not in a Declare Section at line num in file name

ORA-01012	not logged on

PLS-00351	not logged on to database 'name'

SQL*Load-00922	NOT NULL column name.name has a default if clause which may evaluate to null

SQL*Load-00921	NOT NULL column name.name has a NULLIF clause

ORA-02255	NOT NULL not allowed after DEFAULT NULL

DBA-00132	null hostname/password specified

ORA-01005	null password given; logon denied

SQL*Load-00269	Null string not allowed as clause comparison text

PLS-01466	Null strings are not allowed

SQL-02124	NULL value returned by EXEC TOOLS statement

ORA-06557	null values are not allowed for any parameters to pipe ICD's

EXP-00012	num is not a valid export mode

ORA-00208	number of control file names exceeds limit of num

ORA-01104	number of control files (num) does not equal num

ORA-01520	number of data files to add (num) exceeds limit of num

ORA-02454	number of hash keys per block (num) exceeds maximum of num

ORA-01590	number of segment free list (num) exceeds maximum of num

PLS-00411	number of values in aggregate and in subquery don't match

PLS-00216	NUMBER precision constraint must be in range (1 .. 38)

PLS-00217	NUMBER scale constraint must be in range (-84 .. 127)

ORA-01768	number string too long

ORA-04013	number to CACHE must be less than one cycle

SQL*Load-00410	Number to skip must be load-level, not table-level

SQL*Load-00409	Number to skip must be table-level, not load-level on continued loads

ORA-02256	number, type and size of referencing columns must match referenced columns

PLS-00491	numeric literal required

ORA-01426	numeric overflow

ORA-01727	numeric precision specifier is out of range (1 to 38)

ORA-01728	numeric scale specifier is out of range (-84 to 127)

ORA-00291	numeric value required for PARALLEL option

ORA-00050	O/S error occurred while obtain an enqueue. See O/S error.

PLS-00905	object 'name' is invalid

PLS-00224	object 'name' must be of type function or array to be used this way

ORA-04012	object is not a sequence

ORA-00064	object is too large to allocate on this O/S ('num, num')

ORA-02087	object locked by another process in same transaction

ORA-06564	object name does not exist

ORA-04043	object name does not exist

DBA-00362	object name is a package; use 'DESCRIBE <package>.<procedure>'

DBA-00364	object name is a remote object, cannot further describe

ORA-12352	object name is invalid

DBA-00365	object name is invalid, it may not be described

ORA-00701	object necessary for warm starting database cannot be altered

ORA-08103	object no longer exists

DBA-00360	object to be described does not exist

ORA-03007	obsolete feature

ORA-06568	obsolete ICD procedure called

SQL*Load-00931	OCI error while binding variable for column name

SQL*Load-00926	OCI error while executing name for table name

ORA-01145	offline immediate disallowed unless media recovery enabled

ORA-04078	OLD and NEW values cannot be identical

MOD-00074	ONAME option is specified but not meaningful

PLS-01407	One of the identifiers CHAR, CHARACTER, or INTEGER has been redefined by the programmer

ORA-01195	online backup of file name needs more recovery to be consistent

ORA-01916	ONLINE keyword or OFFLINE keyword expected

ORA-00312	online log name thread num: 'str'

ORA-00335	online log name: No log with this number, log does not exist

ORA-00373	online log version ver incompatible with Oracle version ver

ORA-02198	ONLINE/OFFLINE option already specified

IMP-00013	only a DBA can import a file exported by another DBA

SQL*Load-00411	Only a direct path load may be continued

ORA-00112	only created up to num (maximum specified) dispatchers

ORA-02225	only EXECUTE privilege is valid for procedures

ORA-12814	only one CACHE or NOCACHE clause may be specified

ORA-01787	only one clause allowed per query block

ORA-12812	only one PARALLEL or NOPARALLEL clause may be specified

EXP-00026	only one parameter (TABLES, OWNER, or FULL) can be specified

ORA-02205	only SELECT and ALTER privilege is valid for sequences

ORA-01748	only simple column names allowed here

ORA-01968	only specify RESETLOGS or NORESETLOGS once

PCC-02321	Only subtraction between two pointers is permitted

ORA-01939	only the ADMIN OPTION can be specified

PLS-00121	only the set function COUNT may take * as an argument

ORA-00313	open failed for members of log group var of thread var

ORA-12342	open mounts exceeds limit set on the OPEN_MOUNTS parameter

ORA-00290	operating system archiving error occurred. See error below

IMP-00021	operating system error - error code (dec num, hex 0xnum)

ORA-03002	operator not implemented

PCC-00129	option optnam must be given

PCC-00028	Option optnam not legal as EXEC Oracle OPTION

SQL*Load-00308	Optional SQL string of column name must be in double quotes.

PLS-01501	Options in CREATE TABLE statement is non-ANSI.

ORA-02059	ORA-CRASH-TEST-n in commit comment

ORA-02262	ORA-num occurs while type-checking column default value expression

ORA-01578	Oracle data block corrupted (file # num, block # num)

ORA-01079	Oracle database was not properly created, operation aborted

LCC-00161	Oracle error (possible syntax error) parameter param

EXP-00016	Oracle error encountered while reading default auditing options

MOD-00069	Oracle error N while attempting to store package

EXP-00008	Oracle error num encountered

MOD-00015	Oracle Error: ora-nnnnn

PCC-00021	Oracle Error: ora-nnnnn

SQL*Load-00967	Oracle error: str

PCC-00110	Oracle extension to the WHENEVER statement

ORA-00437	Oracle feature is not licensed. Contact Oracle Corporation for assistance

ORA-01092	Oracle instance terminated. Disconnection forced.

ORA-00436	Oracle is not licensed. Contact Oracle Corporation for assistance

IMP-00003	Oracle message code num encountered

ORA-01034	Oracle not available

ORA-01035	Oracle only available to users with RESTRICTED SESSION privilege

ORA-00603	Oracle Server session terminated by fatal error

ORA-01014	Oracle shutdown in progress

ORA-01033	Oracle startup or shutdown in progress

ORA-03109	oranet buffer overflow

ORA-03107	oranet buffer underflow

ORA-03108	oranet: Oracle does not support this interface version

ORA-03110	oranet: Oracle does not support this SQL version

ORA-01785	ORDER BY item must be the number of a SELECT-list expression

ORA-01927	original grantor must REVOKE privileges

ORA-12455	OS format not allowed in this context

PLS-00370	OTHERS handler must be last among the exception handlers of a block

PLS-00230	OUT and IN OUT formal parameters may not have default expressions

PCC-02352	Out of bounds bind position from PL/SQL

PLS-00996	out of memory

SQL-02100	Out of memory (i.e., could not allocate)

SQL*Load-00701	Out of memory while allocating bind array

SQL*Load-00700	Out of memory while performing essential allocations [num]

ORA-04030	out of process memory when trying to allocate num bytes (str,str)

MOD-00016	Out of space - unable to allocate num bytes

PCC-00022	Out of space - unable to allocate num bytes

ORA-01558	out of transaction ID's in rollback segment num

ORA-01554	out of transaction slots in transaction tables

ORA-02092	out of transaction table slots for distributed transaction

ORA-01719	outer join operator (+) not allowed in operand of OR or IN

ORA-01415	outer-join (+) may not be applied to the  label pseudo column

PLS-00226	package 'name' used as variable reference

ORA-06554	Package DBMS_STANDARD must be created before using PL/SQL

MOD-00067	Package name is required but not specified

ORA-04041	package specification must be created first before creating package body

PLS-00213	package STANDARD not accessible

ORA-04055	package STANDARD@name is incompatible to local package STANDARD

ORA-02357	packed decimal conversion error

ORA-01487	packed decimal number too large for supplied buffer

ORA-12817	parallel query option must be enabled

ORA-12804	parallel query server appears to have died

ORA-12805	parallel query server died unexpectedly

ORA-12803	parallel query server lost contact with another server

ORA-12802	parallel query server lost contact with coordinator

ORA-01633	Parallel Server option needed for this operation

ORA-12810	PARALLEL_MAX_SERVERS must be less than or equal to number

ORA-12811	PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, number

ORA-00374	parameter DB_BLOCK_SIZE = num invalid, valid range [num..num]

LCC-00215	parameter files nested too deep command

ORA-01638	parameter init does not allow Oracle Version ver to mount parallel

MOD-00044	Parameter param in procedure name is multiply declared

PLS-00223	parameterless procedure 'name' used as function

PCC-02205	Parser error at line num, column colnam, file name

PLS-00102	parser stack overflow because nesting is too deep

IMP-00018	partial import of previous table complete: num rows imported

IMP-00028	partial import of previous table rolled back: num rows rolled back

ORA-01999	password file mode has changed from mode to mode

SQL-02127	PCC / SQLLIB version mismatch

ORA-02192	PCTINCREASE not allowed for rollback segment storage clauses

DBA-00325	pfile too large

ORA-01168	physical block size num does not match size num of other members

SQL*Load-00510	Physical record in data file (name) is longer than the maximum (num)

SQL*Load-00408	Physical record stack overflow

SQL*Load-00263	PIECED column num must be last specified column in table name

SQL*Load-00262	PIECED keyword (on column num) allowed only when path is direct

MOD-00061	PL/SQL error in compiling package body

MOD-00060	PL/SQL error in compiling package specification

PCC-02346	PL/SQL found semantic errors

PCC-02347	PL/SQL found syntax errors

PLS-00316	PL/SQL TABLE declarations must currently use a single index

PLS-00315	PL/SQL TABLE declarations must currently use BINARY_INTEGER indexes

PLS-00507	PL/SQL tables may not be defined in terms of records or other tables

ORA-06511	PL/SQL:  cursor already open

ORA-06508	PL/SQL: could not find program unit being called

ORA-06503	PL/SQL: Function returned without value

ORA-06509	PL/SQL: ICD vector missing for this package

ORA-06513	PL/SQL: index for PL/SQL table out of range for host language array

ORA-06501	PL/SQL: internal error num, arguments [num], [num], [num], [num], [num], [num]

ORA-06502	PL/SQL: numeric or value error

ORA-06500	PL/SQL: storage error

ORA-06510	PL/SQL: unhandled user-defined exception str

ORA-02403	plan table does not have correct format

ORA-02402	PLAN_TABLE not found

ORA-00472	PMON process terminated with error

MOD-00072	PNAME option is specified but not meaningful

ORA-06560	pos, num, is negative or larger than the buffer size, num

LCC-00206	positional parameter entered after keyword keyword

ORA-02424	potential circular view references or unknown referenced tables

PLS-00700	PRAGMA EXCEPTION_INIT of 'name' must follow declaration of its exception in same block

ORA-02063	preceding str from name

PCC-02349	Precision must be specified for this type

PCC-00090	Precision/scale specification must be given for DECIMAL datatype

PCC-02020	Preprocessor error at line num, column colnam, file name

PCC-02019	Preprocessor warning at line num, column colnam, file name

ORA-01645	previous attempt to make read write is half complete

PLS-00305	previous use of 'name' conflicts with this use

ORA-01400	primary key or mandatory (NOT NULL) column is missing or NULL during insert

ORA-01469	PRIOR can only be followed by a column name

ORA-01434	private synonym to be dropped does not exist

ORA-02426	privilege grant failed

PCC-00048	Pro* configured without Oracle. INLINE=NO ignored

DBA-00380	procedural option required for this statement

PCC-01005	PROCEDURE DIVISION not found

MOD-00070	Procedure name interface is missing declaration for indvar

MOD-00043	Procedure name is multiply declared

MOD-00063	Procedure name, parameter param: illegal interface type type

MOD-00064	Procedure name: extra parameter param in interface

DBA-00363	procedure or function name not found in the package

ORA-04044	procedure, function, or package is not allowed here

ORA-04042	procedure, function, package, or package body does not exist

ORA-12470	process label could not be found

ORA-12807	process queue could not receive parallel query message

ORA-02379	profile name already exists

ORA-02380	profile name does not exist

ORA-02382	profile name has users assigned, cannot drop without CASCADE

ORA-01709	program does not exist

ORA-01098	program interface error during LONG insert

PLS-00123	program too large

SQL-02107	Program too old for runtime library; please re-precompile it

ORA-01096	program version (num) incompatible with instance (num)

ORA-00113	protocol name string is too long

ORA-01432	public synonym to be dropped does not exist

ORA-12454	punctuation supplied does not match specified input format

PLS-00303	qualifier 'name' must be declared

ORA-01842	quarter must be between 1 and 4

ORA-01789	query block has incorrect number of result columns

ORA-01756	quoted string not properly terminated

PCC-00063	Reached end of file name before end-of-statement at line num

ORA-00476	RECO process terminated with error

ORA-02370	record num - Warning on table name, column num

ORA-02368	record num: Discarded - all columns null.

ORA-02364	record num: Discarded - failed all WHEN clauses

ORA-02351	record num: Rejected - Error on table name, column name

ORA-00351	recover-to time invalid

ORA-01156	recovery in progress may need access to files

ORA-01172	recovery of thread num stuck at block num of file name

ORA-00283	recovery session canceled due to errors.

ORA-00284	recovery session still in progress.

ORA-01610	recovery using the BACKUP CONTROLFILE option must be done

PCC-00027	Redeclared SQL indentifier ident at line num in file name

ORA-00333	redo log read error block num count num

ORA-00345	redo log write error block num count num

ORA-01571	redo version ver incompatible with Oracle Version ver

PLS-00419	reference to remote attribute not permitted

SQL*Load-00403	Referenced column name not present in table name

ORA-02268	referenced table does not have a primary key

ORA-04093	references to columns of type LONG are not allowed in triggers

ORA-12004	REFRESH FAST cannot be used

SQL*Load-00642	Relative start position > absolute field end position

ORA-02372	relative start position > absolute field end position

PCC-00106	RELEASE is an Oracle extension to the COMMIT and ROLLBACK statements

ORA-02040	remote database 'name' does not support two-phase commit

ORA-01988	remote O/S logon is not allowed

ORA-02022	remote statement has unoptimized view with remote object

ORA-02052	remote transaction failure at name

PLS-00451	remote types not allowed

ORA-00304	requested INSTANCE_NUMBER is busy

ORA-00307	requested INSTANCE_NUMBER out of range, maximum is num

IMP-00016	required character set conversion (type num to num) not supported

ORA-02189	required clause: ON <tablespace>

ORA-00219	required control file size num larger than maximum num

PLS-00101	reserved for future use

ORA-01139	RESET LOGS option only valid after an incomplete database recovery

ORA-01223	RESETLOGS must be specified to set a new database nam

ORA-00054	resource busy and acquire with NOWAIT specified

ORA-02184	resource quotas are not allowed in REVOKE

EXP-00013	respond with either 'Y', 'N', RETURN or '.' to quit

IMP-00001	respond with either 'Y', 'N', RETURN or '.' to quit

ORA-01489	result of string concatenation is too long

ORA-04046	results of compilation are too large to support

PLS-00503	RETURN <value> statement required for this return from function

ORA-01909	REUSE keyword expected

ORA-01998	REVOKE failed: user SYS always SYSOPER and SYSDBA

ORA-01919	role 'name' does not exist

ORA-01924	role 'name' not granted or does not exist

ORA-01949	ROLE keyword expected

ORA-01921	role name 'name' conflicts with another user or role name

ORA-01989	role name not authorized by operating system

ORA-01951	role not granted for ROLE: name, user: name

ORA-01901	ROLLBACK keyword expected

ORA-01636	rollback segment "name" is already online

ORA-01637	rollback segment "name" is being used by another instance (#name)

ORA-01545	rollback segment #'name' was not available

ORA-01635	rollback segment #num specified not available

ORA-01535	rollback segment 'name' already exists

ORA-01534	rollback segment 'name' doesn't exist

ORA-01598	rollback segment 'name' is not online

ORA-01557	rollback segment extents must be at least 3 blocks

ORA-01564	rollback segment is not PUBLIC

ORA-01563	rollback segment is PUBLIC, need to use the keyword PUBLIC

ORA-01625	rollback segment name does not belong to this instance

ORA-01634	rollback segment number 'string' is about to go offline

ORA-01626	rollback segment number num cannot handle more transactions

ORA-01627	rollback segment number num is not online

ORA-01593	rollback segment optimal size (num blocks) is smaller than the computed initial size (num blocks)

ORA-00407	rolling upgrade from release ver.ver to ver.ver is not allowed

ORA-01912	ROW keyword expected

IMP-00019	row rejected due to Oracle message code num

ORA-09123	ROWID not found in gateway rowid cache.

LCC-00212	runaway quoted string command

ORA-01086	savepoint 'name' never established

ORA-02182	savepoint name expected

PCC-00098	Scale specification cannot be used in this context

PCC-00081	Scale specification not allowed for given datatype

ORA-02423	schema name does not match schema authorization identifier

ORA-01717	seccta: invalid access mode token passed

PLS-00702	second argument to PRAGMA EXCEPTION_INIT must be a numeric literal

ORA-12480	secondary database changing between OS MAC and DBMS MAC modes

ORA-12354	secondary object being dropped

ORA-12353	secondary stored object cannot reference remote object

ORA-01853	seconds in day must be between 0 and 86399

ORA-01852	seconds must be between 0 and 59

ORA-01838	seconds of minute conflicts with seconds in day

ORA-02004	security violation

ORA-01902	SEGMENT keyword expected

ORA-01030	SELECT ... INTO variable does not exist

ORA-02060	SELECT FOR UPDATE specified a join of non-colocated tables

PLS-00486	SELECT list cannot be enclosed in parentheses

SQL-02112	SELECT..INTO returns too many rows

ORA-02077	selects of long columns must be from co-located tables

PCC-02353	Semantic error at line num, column colnam, file name

ORA-02289	sequence does not exist

ORA-01941	SEQUENCE keyword expected

ORA-02201	sequence not allowed here

ORA-02076	sequence not co-located with updated or long column

ORA-02287	sequence number not allowed here

ORA-04003	sequence parameter num exceeds the maximum size allowed (num digits)

ORA-04001	sequence parameter str must be an integer

ORA-00021	session attached to some other process; cannot switch session

ORA-00028	session has been killed

ORA-00029	session is not a user session

ORA-12488	session label must be equal to name

ORA-12415	session label must dominate the creation label of role name

ORA-00031	session marked for kill

ORA-00023	session references process' private memory; cannot detach session

ORA-01228	SET DATABASE option required to install seed database

ORA-01453	SET TRANSACTION must be first statement of transaction

ORA-06570	shared pool object does not exist, cannot be pinned

ORA-02146	SHARED specified multiple times

ORA-01090	shutdown in progress - connection is not permitted

ORA-01573	shutting down instance, no further change allowed

ORA-01819	signed year precludes use of BC/AD

PLS-00220	simple name required in this context

ORA-00348	single-process redo failure. Must abort instance

ORA-01427	single-row query returns more than one row

ORA-01044	size num of buffer bound to variable name exceeds maximum num

ORA-01486	size of array element is too large

PCC-00051	Size of VARCHAR hostvar at num is larger than 65533 at line num in file name

ORA-19999	SKIP_ROW procedure was called

ORA-00474	SMON process terminated with error

MOD-00093	SNAME option is specified but not meaningful

ORA-12003	snapshot name does not exist

ORA-12007	snapshot reuse parameters are inconsistent

ORA-01555	snapshot too old (rollback segment too small)

ORA-12009	snapshots may not contain long columns

ORA-00477	SNP* process terminated with an error

SQL*Load-00252	Sort data sets are not used by SQL*Loader

SQL*Load-00251	Sort devices are not used by SQL*Loader

ORA-01467	sort key too long

SQL*Load-00256	SORTED INDEXES option allowed only for direct path

PCC-00086	Source file name has zero length

ORA-01536	space quota exceeded for tablespace 'name'

ORA-01496	specified chain row table form incorrect

ORA-01495	specified chain row table not found

ORA-00287	specified change number num not found in thread num

ORA-00945	specified clustered column does not exist

ORA-03283	specified data file name does not exist

ORA-03284	specified data file name is not a member of tablespace name

SQL*Load-00933	Specified file name not part of database

ORA-01418	specified index does not exist

ORA-00910	specified length too long for its datatype

ORA-00268	specified logfile does not exist name

ORA-00269	specified logfile is part of thread num not num

SQL*Load-00600	Specified max. bind size num bytes must be num bytes to hold 1 row

ORA-01509	specified name 'name' does not match actual 'name'

ORA-02404	specified plan table not found

ORA-08005	specified row does not exist

ORA-08006	specified row no longer exists

ORA-01136	specified size of file num (num blocks) is less than original size of num blocks

ORA-01765	specifying table's owner name is not allowed

ORA-02034	speed bind not permitted

ORA-00933	SQL command not properly ended

PCC-02334	SQL identifier was not declared as a cursor

PCC-02333	SQL identifier was not declared as a statement

IMP-00032	SQL statement exceeded buffer length

SQL*Load-00417	SQL string (on column name) not allowed in direct path

DBA-00318	SQL*DBA command line error [num]

MOD-00079	SQLCHECK must be SEMANTICS when RPC_GENERATE=yes.

PCC-02374	SQLCHECK value exceeds command line value

PCC-00111	SQLCHECK value in EXEC Oracle statement exceeds command line value

PCC-02345	SQLCHECK=SEMANTICS must be given when embedded PL/SQL blocks are used

PCF-00251	SQLCODE is a deprecated feature

PCF-00256	SQLCODE returns non-standard values

ORA-04006	START WITH cannot be less than MINVALUE

ORA-04008	START WITH cannot be more than MAXVALUE

ORA-02023	START WITH or CONNECT BY predicate cannot be evaluated by remote database

PCC-00010	Statement out of place at line num in file name

PLS-01463	STDDEV is not a standard set function

ORA-01905	STORAGE keyword expected

ORA-00403	str (str) is not the same as other instances (str)

PLS-00215	string length constraints must be in range (1 .. 32767)

ORA-01780	string literal required

ORA-01704	string literal too long

PCC-02327	Struct or struct pointer required

PCC-02340	Structure contains a bit field

PCC-02338	Structure contains a nested struct or union

PLS-00323	subprogram 'name' is declared in a package specification and must be defined in the package body

PLS-00452	subprogram 'name' violates its associated pragma

PLS-00225	subprogram or cursor 'name' reference is out of scope

PLS-01418	Subquery cannot include set operators in ANSI's grammar

PLS-00319	subquery in an IN or NOT IN clause must contain exactly one column

PLS-01419	Subquery must have either '*' or exactly one column in its select list

ORA-02251	subquery not allowed here

PLS-00405	subquery not allowed in this context

PLS-01423	Subquery on right-hand-side in set clause

PLS-00366	subtype of a NOT NULL type must also be NOT NULL

ORA-02275	such a referential constraint already exists in the table

ORA-01408	such column list already indexed

ORA-02261	such unique or primary key already exists in the table

ORA-00289	suggestion: str

PLS-00421	synonym definitions nested too deeply; possible loop in synonyms

SQL*Load-00606	Synonym name refers to an object on a remote database

ORA-01433	synonym to be created is already defined

ORA-00980	synonym translation is no longer valid

SQL*Load-00350	Syntax error at line num

PCC-02014	Syntax error at line num, column colnam, file name

ORA-12316	syntax error in database link's connect string

DBA-00137	Syntax error in PL/SQL Block

SQL*Load-00100	Syntax error on command line

ORA-12800	system appears too busy for parallel query execution

ORA-01952	system privileges not granted to 'name'

ORA-01541	system tablespace cannot be brought offline; shut down if necessary

ORA-01643	system tablespace cannot be made read only

ORA-01147	SYSTEM tablespace file name is offline

PLS-00209	table 'name' is not in FROM clause

ORA-02260	table can have only one primary key

PLS-00314	TABLE declarations are not allowed as PL/SQL local variables

ORA-02271	table does not have such a constraint

ORA-02266	table has some unique/primary keys that are referenced by some foreign keys

SQL*Load-00272	Table level OPTIONS statement ignored.

ORA-01758	table must be empty to add mandatory (NOT NULL) column

SQL*Load-00927	Table name does not exist

SQL*Load-00270	Table name has index defined upon it.

ORA-04094	table name is constraining, trigger may not modify it

ORA-04091	table name is mutating, trigger/function may not see it

ORA-00964	table name not in FROM list

ORA-00942	table or view does not exist

PLS-00417	table or view or column does not exist

PLS-01705	table specified by a cursor not updatable if cursor specification has a UNION or ORDER_BY

ORA-03292	table to be truncated is a member of a cluster

PLS-00357	table, view or sequence reference 'name' not allowed in this context

ORA-01499	table/Index Cross Reference Failure - see trace file

ORA-01910	TABLES keyword expected

SQL*Load-00912	Tables loaded through the direct path may not be clustered

ORA-01543	tablespace 'name' already exists

ORA-00959	tablespace 'name' does not exist

ORA-01540	tablespace 'name' is not offline

ORA-01539	tablespace 'name' is not online

ORA-01542	tablespace 'name' is offline, cannot allocate space in it

ORA-01647	tablespace 'name' is read only, cannot allocate space in it

ORA-01546	tablespace contains active rollback segment 'name'

ORA-01907	TABLESPACE keyword expected

ORA-02216	tablespace name expected

ORA-01644	tablespace name is already read only

ORA-01646	tablespace name is not read only - cannot make read write

ORA-01549	tablespace not empty, use INCLUDING CONTENTS option

ORA-12408	tablespace previously existed at another label (name)

ORA-02186	tablespace resource privilege may not appear with other privileges

ORA-09112	Target system check constraint violated.

ORA-09101	Target system communication error.

ORA-09106	Target system could not obtain IO resource.

ORA-09115	Target system has timed out.

ORA-09113	Target system integrity constraint violated.

ORA-09114	Target system is out of memory.

ORA-09100	Target system returned following message:

ORA-01947	TEMPORARY TABLESPACE already specified

DBA-00390	terminal type var is defined by var

PCC-00127	text

ORA-01047	The above error occurred in schema=name, packange=name, procedure=name

SQL*Load-00918	The catalog must be loaded (as SYS) for SQL*Loader to be used.

PLS-01713	The constraints on these types do not match

ORA-00996	the concatenate operator is ||, not |

PCC-00107	The CONNECT statement is Oracle implementation dependent

PLS-01451	The data types of these <value expressions> must be comparable

ORA-01155	the database is being opened, closed, mounted, or dismounted

ORA-02356	The database is out of space. The load cannot continue

PLS-00901	the datatype of column 'name' of table 'name' is not supported

PLS-01451	The data types of these <value expressions> must be comparable

PLS-00311	the declaration of the type of 'name' is incomplete or malformed

PLS-00320	the declaration of the type of this expression is incomplete or malformed

PLS-01470	The escape character in the like-predicate must be a literal or a variable of type CHAR

PLS-01503	The expression in a SET clause must not include a set function

PLS-01704	The expressions in a sort clause must be column specs or unsigned integers, with optional ASC or DESC

ORA-02009	the file size specified for a file must not be zero

PLS-01468	The first argument of the like-predicate must be a column of type character string

ORA-02366	the following index or indexes on table name were processed:

ORA-02456	the HASH IS column specification must be NUMBER(*,0)

ORA-02457	the HASH IS option must specify a valid column

ORA-12458	the input string could not be translated into a binary label

PLS-01471	The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr)

IMP-00048	the MLS_LISTLABELS option cannot be used with this export file

ORA-02455	the number of cluster key column must be 1

ORA-04010	the number of values to CACHE must be greater than 1

ORA-06556	the pipe is empty, cannot fulfill the UNPACK_MESSAGE request

PLS-01455	The predicates IS NULL and IS NOT NULL are defined only for column specifications

ORA-02172	The PUBLIC keyword is not appropriate for a disable thread

PLS-01458	The set clause in an UPDATE statement requires a column name of length 1

ORA-02466	the SIZE option is not allowed to be altered for HASH CLUSTERS

ORA-00224	the specified file is not a control file

ORA-00365	the specified log is not the correct next log

ORA-04000	the sum of PCTUSED and PCTFREE cannot exceed 100

ORA-12460	the value var for the MLS_LABEL_FORMAT parameter is not valid

ORA-00401	the value for parameter "param" is not supported by this release

PLS-01467	The value list of the IN predicate, if not a subquery, must contain only value_specifications

ORA-00271	there are no logs that need archiving

ORA-00263	there are no logs that need archiving for thread num

ORA-02239	there are objects which reference this sequence

ORA-12002	there is no snapshot log on table name

PLS-01450	This <value expression> contains a nonconforming data type

PCC-00116	This array already given in an ARRAYLEN statement

PCC-02360	This array type is invalid for use with ARRAYLEN statement

ORA-12703	This character set conversion is not supported

PLS-00308	this construct is not allowed as the origin of an assignment

ORA-12706	This CREATE DATABASE character set is not allowed

ORA-01016	This function can be called only after a fetch

PLS-01452	This function is not part of the ANSI standard

ORA-06555	this name is currently reserved for use by use SYS

ORA-01796	this operator cannot be used with lists

ORA-01797	this operator must be followed by ANY or ALL

PLS-00115	this PRAGMA must follow the declaration of 'name'

PLS-01453	This procedure is not part of the ANSI standard

PCC-00108	This statement is not supported by ANSI

ORA-02273	this unique/primary key is referenced by some foreign keys

ORA-01612	thread num is already enabled

ORA-01614	thread num is busy - cannot enable

ORA-01216	thread num is expected to be disabled after CREATE CONTROLFILE

ORA-01615	thread num is mounted - cannot disable

ORA-01619	thread num is mounted by another instance

ORA-01618	thread num is not enabled - cannot mount

ORA-01616	thread num is open - cannot disable

ORA-01197	thread num only contains one log

ORA-01613	thread num only has num logs - at least 2 logs required to enable

ORA-01622	thread number must be specified - default not specific

ORA-01225	thread number num is greater than MAXINSTANCES num

ORA-01611	thread number num is invalid - must be between 1 and num

ORA-00285	TIME not given as a string constant

ORA-00051	time-out occurred while waiting for resource

ORA-04021	time-out occurred while waiting to lock object name

ORA-01575	time-out waiting for space management resource

ORA-02049	time-out: distributed transaction waiting for lock

ORA-04062	time-stamp of name has been changed

ORA-00288	to continue recovery type ALTER DATABASE RECOVER CONTINUE

SQL*Load-00306	Token longer than max allowable length of num characters

ORA-00939	too many arguments for function

ORA-02020	too many database links in use

PLS-00307	too many declarations of 'name' match this call

ORA-02042	too many distributed transactions

ORA-00343	too many errors, log member closed

ORA-00358	Too many file members specified, the maximum is num

ORA-00962	too many group-by or order-by expressions

ORA-02045	too many local sessions participating in global transactions

ORA-00357	too many members specified for logfile, the maximum is num

ORA-00989	too many passwords for usernames given

ORA-01898	too many precision specifiers

ORA-00913	too many values

ORA-02036	too many variables to describe with automatic cursor open

DBA-00389	toolkit resource file name is defined to var

ORA-06563	top level procedure or function specified, cannot have subparts

DBA-00322	total size of command line parameters exceeds buffer size

ORA-01480	trailing null missing from STR bind value

ORA-02044	transaction manager login denied: transaction in progress

ORA-02053	transaction num committed, some remote DBs may be in-doubt

ORA-02054	transaction num in-doubt

ORA-02050	transaction num rolled back, some remote DBs may be in-doubt

ORA-02067	transaction or savepoint rollback required

ORA-02091	transaction rolled back

ORA-02093	TRANSACTIONS_PER_ROLLBACK_SEGMENT(name) more than maximum possible.

ORA-04095	trigger "name" already exists on another table, cannot replace

ORA-04081	trigger name already exists

ORA-04080	trigger name does not exist

ORA-04096	trigger str has a WHEN clause that is larger than 2K

ORA-00475	TRWR process terminated with error.

ORA-03118	ttc coroutine has invalid state

ORA-03117	ttc save area overflow

ORA-03120	ttci2u: integer overflow

ORA-03116	ttcxxx: invalid buffer length

ORA-01167	two files are the same file/group number or the same file

ORA-01416	two tables cannot be outer-joined to each other

PLS-00202	type 'name' must be declared

PLS-00504	type 'name'_BASE may not be used outside of package STANDARD

PCC-00080	TYPE identifier already TYPEd

PLS-00381	type mismatch found at 'name' between column and variable in subquery or INSERT

PLS-00386	type mismatch found at 'name' between FETCH cursor and INTO variables

PLS-00385	type mismatch found at 'name' in SELECT...INTO statement

PLS-00384	type mismatch found at 'name' in UPDATE's SET clause

PLS-00383	type mismatch found at 'name' inside an IN or NOT IN clause

PLS-00392	type mismatch in arguments to BETWEEN

PLS-00397	type mismatch in arguments to IN

PLS-00206	%TYPE must be applied to a variable or column, not 'name'

PLS-00125	type name expected

PCC-00091	TYPE statement requires format specification for this Oracle datatype

PLS-00352	unable to access another database 'name'

IMP-00044	unable to allocate enough memory for statement

ORA-01019	unable to allocate memory in the user side

ORA-04031	unable to allocate num bytes of shared memory (val, val, val)

DBA-00314	unable to attach to default host

SQL*Load-00513	Unable to close file (name)

DBA-00342	unable to complete internal login

PCC-02104	Unable to connect to Oracle

MOD-00017	Unable to connect to Oracle with conn_str:username/password. Oracle error number ora-nnnnn

SQL*Load-00402	Unable to determine length of column name.name from specification

ORA-00216	unable to determine physical block size for control file 'name'

ORA-01655	unable to extend cluster name.name by num for tablespace name

ORA-01654	unable to extend index name.name by num for tablespace name

ORA-01650	unable to extend rollback segment name by num in tablespace name

ORA-01651	unable to extend save undo segment by num in tablespace name.

ORA-01653	unable to extend table name.name by num in tablespace name

ORA-01652	unable to extent temp segment by num in tablespace name

SQL*Load-00512	Unable to free read buffer

PCC-00050	Unable to generate descriptor in program unit ending line num in file name

ORA-01583	unable to get block size of control file to be backed up

SQL*Load-00265	Unable to get default character set name

ORA-00375	unable to get default DB_BLOCK_SIZE

ORA-01584	unable to get file size of control file to be backed up

MOD-00049	Unable to initialize PL/SQL

PCC-02100	Unable to initialize PL/SQL

SQL*Load-00511	Unable to initialize read functions

ORA-01497	unable to initialize statistics scan - see trace file.

MOD-00066	Unable to load package name from database

SQL*Load-00266	Unable to locate character set handle for name

SQL*Load-00908	Unable to lock table name in exclusive mode due to Oracle error num

PCC-00023	Unable to log off Oracle

PCC-00037	Unable to log on to Oracle with username. Oracle error number: ora-nnnnn

ORA-12322	unable to mount database (link name name)

PCC-00019	Unable to obtain bind variables at line num in file name

PCC-00020	Unable to obtain define variables at line num in file name

PCC-00038	Unable to open a cursor

PCC-00016	Unable to open a cursor at line num in file name

SQL*Load-00506	Unable to open bad file (name)

ORA-01582	unable to open control file for backup

ORA-12323	unable to open database (link name name)

ORA-01586	unable to open destination file 'name' for backup

SQL*Load-00507	Unable to open discard file (name)

SQL*Load-00500	Unable to open file (name)

PCC-00001	Unable to open file name

PCC-02015	Unable to open include file

PCC-00013	Unable to open INCLUDE file name at line num in file name

PCC-02101	Unable to open input file

MOD-00009	Unable to open input file name

PCC-00039	Unable to open input file name

PCC-02105	Unable to open list file

PCC-00040	Unable to open listing file name

MOD-00010	Unable to open listing file name

SQL*Load-00502	Unable to open log file for write (name)

PCC-02017	Unable to open output file

MOD-00011	Unable to open output file name

PCC-00041	Unable to open output file name

MOD-00039	Unable to open specifications file name

PCC-00017	Unable to parse statement at line num in file name

ORA-01466	unable to read data -- object definition has changed

SQL*Load-00501	Unable to read file (name)

ORA-00344	unable to recreate online log 'name'

LCC-00205	unbalanced parentheses command

PCC-00025	Undeclared indicator variable var at line num in file name

PCC-00014	Undeclared SQL identifier ident at line num in file name

PLS-00390	undefined column 'name' in INSERT statement

PLS-00389	undefined column 'name' in left-hand-side expression

PLS-00388	undefined column 'name' in subquery

PLS-00391	undefined column 'name' in UPDATE statement

PCC-02331	Undefined SQL identifier

PCC-02328	Undefined struct member

PLS-01405	Under ANSI's grammar, numeric data represented in exponent notation must use an uppercase E

IMP-00045	unexpected character found on line num in mapfile

LCC-00211	unexpected delimiter symbol

DBA-00115	unexpected end of command

DBA-00375	Unexpected end of file, filename

ORA-00921	unexpected end of SQL command

EXP-00030	unexpected End-Of-File encountered while reading input

LCC-00208	unexpected keyword in value list keyword

PLS-00995	unhandled exception # 'num'

SQL*Load-00415	Unimplemented database column type num on column name

ORA-03001	unimplemented feature

ORA-01460	unimplemented or unreasonable conversion requested

ORA-02037	uninitialized speed bind storage

PLS-01500	Unions are not allowed in the definition of a view

ORA-00001	unique constraint (table.column) violated

ORA-01715	UNIQUE may not be used with a cluster index

ORA-01020	unknown context state

PCC-02013	Unknown escape sequence

PLS-00109	unknown exception name 'name' in PRAGMA EXCEPTION_INIT

IMP-00049	Unknown language specified in CHARSET

PCC-00015	Unrecognized host language syntax ignored at line num in file name

LCC-00122	unrecognized keyword keyword

IMP-00008	unrecognized statement in the export file: str

SQL*Load-00268	UNRECOVERABLE keyword may be used only in direct path

ORA-01482	unsupported character set

PCC-00005	Unsupported datatype in line num of file name

ORA-03115	unsupported network datatype or representation

PCC-00047	Unterminated comment/string constant beginning near line num in file name

ORA-12013	updatable snapshots must be simple enough to do fast refresh

ORA-01767	UPDATE ... SET expression must be a subquery

ORA-01763	update or delete involves outer joined table

ORA-01750	UPDATE/REFERENCES may only be revoked from the whole table, not by column

ORA-00282	UPI name call not supported, use ALTER DATABASE RECOVER

ORA-01025	UPI parameter out of range

PCC-01011	USAGE IS BINARY clause must be terminated by "." on same line

PLS-01473	Use <> instead of != or ~=

ORA-01151	use media recovery to recover block, restore backup if needed

PLS-01416	Use of <id> (<value>...) here

PLS-01400	Use of '||' token

PLS-01408	Use of '&' token

PLS-01417	Use of %attribute

PLS-01415	Use of aggregate value here

PLS-01474	Use of ANY is non_ANSI

PLS-01504	Use of AS phase in CREATE TABLE statement is non_ANSI

PCC-02361	Use of ARRAYLEN with SQL host arrays is ignored

PCC-00097	Use of DECIMAL and DISPLAY types allowed only for COBOL and PLI

PCF-00269	use of DECLARE DATABASE statement

PCF-00268	use of DECLARE TABLE statement

PCF-00267	use of DO within WHENEVER clause

PCF-00275	use of DROP TABLE statement

PCF-00260	use of dynamic SQL

PCF-00273	use of EXEC ORACLE statement

PCF-00270	use of EXEC SQL INCLUDE

PCF-00271	use of EXEC SQL TYPE

PLS-01412	Use of 'EXP' token

PCC-00118	Use of host variable initialization not supported by ANSI SQL

PLS-01410	Use of 'MOD' token

PCF-00276	use of non-ANSI function

PCF-00264	use of NOT FOUND within WHENEVER clause

PCF-00263	use of NOTFOUND within WHENEVER clause

PLS-01413	Use of NULL an expression

ORA-00097	use of Oracle SQL feature not in SQL92  compliance level

PLS-01409	Use of 'PRIOR_' token

PCF-00261	use of PL/SQL

PLS-00355	use of PL/SQL table not allowed in this context

PLS-01414	Use of qualified expression here

PLS-01402	Use of quoted identifier

PCF-00266	use of RAISE within WHENEVER clause

PCF-00259	use of RELEASE clause

PLS-01411	Use of 'REM' token

PCF-00272	use of SQL FORMS statement

PCF-00262	use of SQLWARN within WHENEVER clause

PCF-00265	use of STOP within WHENEVER clause

PCF-00253	use of the AT clause

PCF-00252	use of the C preprocessor within SQL

PCF-00255	use of the CONNECT statement

PCF-00254	use of the FOR clause

ORA-01477	user data area descriptor is too large

ORA-01435	user does not exist

ORA-01759	user function is incorrectly defined

ORA-01706	user function result value was too large

ORA-01920	user name 'name' conflicts with another user or role name

ORA-04051	user name cannot use database link name

ORA-01918	user name does not exist

ORA-12345	user name lacks CREATE SESSION privilege in database (link name %s)

ORA-01045	user name lacks CREATE SESSION privilege; logon denied

ORA-01955	user not granted DEFAULT ROLE 'name'

ORA-01917	user or role 'name' does not exist

ORA-01013	user requested cancel of current operation

ORA-00030	user session ID does not exist

ORA-01043	user side memory corruption [num], [num], [num], [num]

ORA-01053	user storage address cannot be read

ORA-01054	user storage address cannot be written

ORA-01129	user's default tablespace does not exist

PLS-00506	user-defined constrained subtypes are disallowed

PCC-00088	User-defined type identifier expected

PLS-00505	user-defined types may only be defined as PL/SQL tables or records

ORA-01721	USERENV (COMMITSCN) invoked more than once in a transaction

ORA-01725	USERENV (COMMITSCN) not allowed here

PCC-02106	Userid only used when SQLCHECK=FULL, userid ignored

PCC-00066	USERID only used when SQLCHECK=SEMANTICS, USERID ignored

PCC-00065	USERID required, but not specified

PLS-00354	username must be a simple identifier

ORA-01070	Using an old version of Oracle for the server

ORA-00203	using the wrong control files

PCC-02342	Using WHERE CURRENT OF on cursor defined without FOR UPDATE clause

ORA-01737	valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE

ORA-12815	value for INSTANCES must be greater than 0

ORA-12813	value for PARALLEL or DEGREE must be greater than 0

ORA-01438	value larger than specified precision allows for this column

PLS-01709	value list of INSERT statement, if specified with value list rather than subquery, must be value specification

LCC-00111	value not in legal range range

PCC-00119	Value of const variable in INTO clause will be modified

PCC-00113	Value of DBMS option invalid with given value of MODE option

ORA-01083	value of parameter var is inconsistent with that of other servers

DBA-00129	value out of range (1 - num)

ORA-00118	value out of range for MTS_DISPATCHERS system parameter

ORA-00117	value out of range for the MTS_SERVERS system parameter

DBA-00391	value var is defined to var; legal values: var or var

DBA-00382	value var is not a recognizable file name for var

DBA-00143	variable has not been defined

SQL*Load-00640	Variable length field was truncated.

ORA-01007	variable not in select list

DBA-00379	variable(s) not defined

PLS-01464	VARIANCE is not a standard set function

ORA-01186	verification tests failed on file name

ORA-01211	Version 6 data file is not from conversion to Oracle7

ORA-09109	View "view_name" cannot be used in a subquery.

ORA-09110	View "view_name" defines operation not supported on the target system.

ORA-01402	view WITH CHECK OPTION where-clause violation

ORA-01733	virtual column not allowed here

PCC-02307	Void can only be used when single parameter

ORA-01762	vopdrv: view query block not in FROM

PCC-02356	Warning at line num, column colnam, file name

IMP-00040	Warning:  Statement not executed due to invalid session label

ORA-02369	warning:  Variable length field was truncated

SQL*Load-00307	Warning: conflicting lengths num1 and num2 specified for column name

IMP-00034	Warning: FromUser \"name\" not found in export file

ORA-00111	Warning: maximum number of servers is only num; adding num servers

IMP-00041	Warning: object created with compilation warnings

IMP-00033	Warning: Table \"name\" not found in export file

IMP-00035	Warning: ToUser \"name\" not found in export file

ORA-01845	week of month must be between 1 and 5

ORA-01844	week of year must be between 1 and 52

ORA-01860	week of year must be between 1 and 53

ORA-04077	WHEN clause cannot be used with table level triggers

PLS-00309	with %LAST attribute, 'name' must be a variable of an enumerated type

PLS-00310	with %ROWTYPE attribute, 'name' must name a cursor or table

ORA-01932	WITH ADMIN option not granted for role 'name'

ORA-02200	WITH GRANT OPTION not allowed for PUBLIC

ORA-01777	WITH GRANT OPTION not allowed in this system

SQL*Load-00250	Work data sets are not used by SQL*Loader

PCC-01007	WORKING-STORAGE SECTION not found

ORA-01579	write error occurred during recovery

ORA-06559	wrong datatype requested, type, actual datatype is type

ORA-01204	wrong file - file number is num rather than num

ORA-01203	wrong incarnation of this file - wrong creation SCN

ORA-01202	wrong incarnation of this file - wrong creation time

PLS-00393	wrong number of columns in SELECT...INTO statement

PLS-00398	wrong number of columns in UNION, INTERSECT, or MINUS expression

ORA-01862	wrong number of digits for this format item

PLS-00394	wrong number of values in the INTO list of a FETCH statement

PLS-00395	wrong number of values in VALUES clause of INSERT statement

PLS-00306	wrong number or types of arguments in call to 'name'

ORA-01831	year conflicts with Julian date

ORA-01812	year may only be specified once

PCC-01500	You are not authorized to run Pro*Ada

PCC-01200	You are not authorized to run Pro*C

PCC-01000	You are not authorized to run Pro*COBOL

PCC-01100	You are not authorized to run Pro*FORTRAN

PCC-01400	You are not authorized to run Pro*Pascal

PCC-01300	You are not authorized to run Pro*PL/I

SQL*Load-00904	You cannot use the direct path when linked with v5 of the database

ORA-01970	You must specify a database name for CREATE CONTROLFILE

ORA-01969	You must specify RESETLOGS or NORESETLOGS

PCC-01501	Your Pro*Ada authorization is about to expire

PCC-01201	Your Pro*C authorization is about to expire

PCC-01001	Your Pro*COBOL authorization is about to expire

PCC-01101	Your Pro*FORTRAN authorization is about to expire

PCC-01401	Your Pro*Pascal authorization is about to expire

PCC-01301	Your Pro*PL/I authorization is about to expire

ORA-01412	zero length not allowed for this datatype

ORA-01723	zero-length columns are not allowed

ORA-02358	zoned decimal conversion error


APPENDIX B. OPERATING SYSTEM- SPECIFIC INFORMATION

This Manual occasionally refers to other Oracle manuals that contain detailed information for using Oracle on a specific operating system. These Oracle manuals are generically referred to as operating-system-specific Oracle documentation, as the exact name varies on different operating systems.

This appendix lists all the references in this Manual to operating-system-specific Oracle documentation. It lists ranges of error messages that are operating-system-specific and also individual error messages within ranges that are not operating-system-specific. If you are using Oracle on multiple operating systems, this appendix can help you ensure that your applications are portable across these operating systems.

 ________________________________________

Ranges of Operating-System-Specific Messages

The following list contains ranges of error messages that pertain to operating-system-specific issues. See also "Related Publications" on page  iii of the "Preface" for a listing the Oracle manuals containing operating-system-specific messages.

00570-00599: SQL*Connect Opening & Reading Files

00640-00699: SQL*Connect

02500-02699: CTOS

02700-02757: UNIX Two Task

02875-02899: IBM RS/6000

03500-03699: Macintosh

03700-03999: AOS/VS

04500-04899: CMS

04900-09429: ICL DRS6000

05000-05899: OEM

06000-06429: SQL*Net generic messages,

06430-06499: NCR System 3000

06700-06899: SQL*Net TLI

06900-06939: CMX

06950-06999: SQL*Net AppleTalk

07000-07099: SQL*Connect/DB2

07100-07199: SQL*Connect/IMS

07200-07499: UNIX

08401-08410: European OEM Systems

08500-08799: SQL*Connect

08800-08899: SQL*Connect Tandem

09000-09099: SQL*Connect TERADATA

09100-09199: Oracle Gateways

09200-09499: OS/2 & MSDOS

09500-09699: MPE/XL

09700-09999: UNIX

10000-10999: Internal

12100-12299: SQL*Net

12500-12699: SQL*Net

21100-21299: Internal

 ________________________________________

Individual Operating-System-Specific Messages

The following list contains operating-system-specific error messages that occur within generic ranges of error messages. See also "Related Publications" on page  iii of the "Preface" for a listing the Oracle manuals containing operating-system-specific messages.

ORA- 02020

ORA-00050

ORA-00204

ORA-00206

ORA-00290

ORA-00306

ORA-00307

ORA-00445

ORA-01034

ORA-01046

ORA-01050

ORA-01157

ORA-01450

ORA-01497

ORA-01498

ORA-01499

ORA-01519

ORA-01526

ORA-01527

ORA-01528

ORA-01529

ORA-01955

ORA-02082

ORA-12449

IMP-00021

PCC-02066

PCC-02101