Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Go To Documentation Library
Home		 Go To Product List
Book List		 Go To Table Of Contents
Contents		 Go To Index
Index
Master Index
Feedback

Go to previous page Go to next page


Preface

This manual describes error messages that may appear while using products that are part of Oracle. Each message listing in the manual contains the message statement, an explanation of the probable causes of the message, and a recommended action. If the message is a warning or indicates that an error occurred, the message listing indicates a corrective action.

This preface contains these topics:

Audience

Oracle9i Database Error Messages is intended for all Oracle users.

Organization

This document contains:

Part I, "Introduction"

Chapter 1, "Using Messages"

This chapter gives you general information and helpful tips about error messages.

Part II, "Oracle Database Server Messages"

Chapter 2, "ORA-00000 to ORA-00899"

This chapter lists error messages generated by the Oracle database server in the range ORA-00000 to ORA-00899.

Chapter 3, "ORA-00900 to ORA-01499"

This chapter lists error messages generated by the Oracle database server in the range ORA-00900 to ORA-01499.

Chapter 4, "ORA-01500 to ORA-02099"

This chapter lists error messages generated by the Oracle database server in the range ORA-01500 to ORA-02099.

Chapter 5, "ORA-02100 to ORA-04099"

This chapter lists error messages generated by the Oracle database server in the range ORA-02100 to ORA-04099.

Chapter 6, "ORA-04100 to ORA-07499"

This chapter lists error messages generated by the Oracle database server in the range ORA-04100 to ORA-07499.

Chapter 7, "ORA-07500 to ORA-09857"

This chapter lists error messages generated by the Oracle database server in the range ORA-07500 to ORA-09857.

Chapter 8, "ORA-09858 to ORA-12299"

This chapter lists error messages generated by the Oracle database server in the range ORA-09858 to ORA-12299.

Chapter 9, "ORA-12300 to ORA-12399"

This chapter lists error messages generated by the Oracle database server in the range ORA-12300 to ORA-12399.

Chapter 10, "ORA-12400 to ORA-12699"

This chapter lists error messages generated by the Oracle database server in the range ORA-12400 to ORA-12699.

Chapter 11, "ORA-12700 to ORA-19399"

This chapter lists error messages generated by the Oracle database server in the range ORA-12700 to ORA-19399.

Chapter 12, "ORA-19400 to ORA-24279"

This chapter lists error messages generated by the Oracle database server in the range ORA-19400 to ORA-24279.

Chapter 13, "ORA-24280 to ORA-29249"

This chapter lists error messages generated by the Oracle database server in the range ORA-24280 to ORA-29249.

Chapter 14, "ORA-29250 to ORA-32799"

This chapter lists error messages generated by the Oracle database server in the range ORA-29250 to ORA-32799.

Chapter 15, "ORA-32800 to ORA-32999"

This chapter lists error messages generated by the Oracle database server in the range ORA-32800 to ORA-32999.

Chapter 16, "ORA-33000 to ORA-65535"

This chapter lists error messages generated by the Oracle database server in the range ORA-33000 to ORA-65535.

Part III, "Oracle Database Server Utilities Messages"

Chapter 17, "Export Messages (EXP)"

This chapter lists error messages generated by the Export utility.

Chapter 18, "Import Messages (IMP)"

This chapter lists error messages generated by the Import utility.

Chapter 19, "SQL*Loader Messages (SQL*Loader)"

This chapter lists error messages generated by the SQL*Loader utility.

Chapter 20, "External Tables Messages (KUP)"

This chapter lists error messages generated by the external tables feature.

Chapter 21, "DBVERIFY Messages (DBV)"

This chapter lists error messages generated by the DBVERIFY utility.

Chapter 22, "DBNEWID Messages (NID)"

This chapter lists error messages generated by the DBNEWID utility.

Chapter 23, "Parameter Messages (LCD)"

This chapter lists parameter error messages.

Chapter 24, "Summary Advisor, Explain Rewrite, and Explain Materialized View Messages (QSM)"

This chapter lists Summary Advisor, Explain Rewrite, and Explain Materialized View error messages.

Chapter 25, "Recovery Manager Messages (RMAN)"

This chapter lists Recovery Manager messages.

Part IV, "Core Library Messages"

Chapter 26, "Parameter Messages (LRM)"

This chapter lists parameter error messages.

Chapter 27, "BFILE-Related Messages (LFI)"

Part V, "PL/SQL Messages"

Chapter 28, "PL/SQL and FIPS Messages (PLS)"

This chapter lists error messages generated by PL/SQL.

Part VI, "Oracle OLAP Catalog Metadata Messages"

Chapter 29, "Oracle OLAP Catalog Metadata Messages (AMD)"

This chapter lists Oracle OLAP Catalog Metadata messages.

Part VII, "Network Messages"

Chapter 30, "Oracle Net Messages (TNS)"
Chapter 31, "Oracle Names Client Messages (NNC)"
Chapter 32, "Oracle Names Server Messages (NNO)"
Chapter 33, "Oracle Names Control Utility Messages (NNL)"
Chapter 34, "Oracle Names Server Network Presentation Layer Messages (NPL)"
Chapter 35, "External Naming Messages (NNF)"
Chapter 36, "Simple Network Management Protocol Messages (NMP)"
Chapter 37, "Remote Operation Messages (NCR)"
Chapter 38, "Network Security Messages (NZE)"

Part VIII, "Precompiler Messages"

Chapter 39, "SQL*Module Messages (MOD)"

This chapter lists error messages generated by SQL*Module.

Chapter 40, "Object Type Translator Type File Messages (O2F)"
Chapter 41, "Object Type Translator Initialization Messages (O2I)"
Chapter 42, "Object Type Translator Unparser Messages (O2U)"
Chapter 43, "Pro*COBOL Messages (PCB)"
Chapter 44, "PCF FIPS Messages (PCF)"
Chapter 45, "Pro*C/C++ Messages (PCC)"

This chapter lists error messages generated by the Pro*C/C++ precompilers.

Chapter 46, "SQL Runtime Messages (SQL)"

Part IX, "interMedia Messages"

Chapter 47, "interMedia Audio Messages (AUD)"
Chapter 48, "interMedia Image Messages (IMG)"
Chapter 49, "interMedia Video Messages (VID)"

Part X, "Oracle Text Messages"

Chapter 50, "Oracle Text Messages (DRG)"

This chapter lists Oracle Text messages.

Part XI, "XML Messages"

Chapter 51, "XML Parser Messages (LPX)"

This chapter lists messages generated by the XML Parser.

Chapter 52, "XML Schema Processor Messages (LSX)"

This chapter lists messages generated by the XML Schema Processor.

Part XII, "Oracle Trace Messages"

Chapter 53, "Oracle Trace Collection Services Messages (EPC)"

Related Documentation

For more information, see these Oracle resources:

Many of the examples in this book use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle9i Sample Schemas for information on how these schemas were created and how you can use them yourself.

In North America, printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

http://www.oraclebookshop.com/

Other customers can contact their Oracle representative to purchase printed documentation.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/admin/account/membership.html

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/docs/index.htm

To access the database documentation search engine directly, please visit

http://tahiti.oracle.com

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention Meaning Example

Bold

Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.

When you specify this clause, you create an index-organized table.

Italics

Italic typeface indicates book titles or emphasis.

Oracle9i Database Concepts

Ensure that the recovery catalog and target database do not reside on the same disk.

UPPERCASE monospace (fixed-width) font

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.

You can specify this clause only for a NUMBER column.

You can back up the database by using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.

Use the DBMS_STATS.GENERATE_STATS procedure.

lowercase monospace (fixed-width) font

Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.

Enter sqlplus to open SQL*Plus.

The password is specified in the orapwd file.

Back up the datafiles and control files in the /disk1/oracle/dbs directory.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user.

The JRepUtil class implements these methods.

lowercase italic monospace (fixed-width) font

Lowercase italic monospace font represents placeholders or variables.

You can specify the parallel_clause.

Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention Meaning Example 
[ ]

Brackets enclose one or more optional items. Do not enter the brackets.

 
DECIMAL (digits [ , precision ])

{ }

Braces enclose two or more items, one of which is required. Do not enter the braces.

 
{ENABLE | DISABLE}

|

A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.

 
{ENABLE | DISABLE}
[COMPRESS | NOCOMPRESS]

...

Horizontal ellipsis points indicate either:

  • That we have omitted parts of the code that are not directly related to the example
  • That you can repeat a portion of the code
 

CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM 
employees;

 .
 .
 .

Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.

 
SQL> SELECT NAME FROM V$DATAFILE;
NAME
------------------------------------
/fsl/dbs/tbs_01.dbf
/fs1/dbs/tbs_02.dbf
.
.
.
/fsl/dbs/tbs_09.dbf
9 rows selected.

Other notation

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown.

 
acctbal NUMBER(11,2);
acct    CONSTANT NUMBER(4) := 3;

Italics

Italicized text indicates placeholders or variables for which you must supply particular values.

 
CONNECT SYSTEM/system_password
DB_NAME = database_name


UPPERCASE

Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.

 
SELECT last_name, employee_id FROM 
employees;
SELECT * FROM USER_TABLES;
DROP TABLE hr.employees;

lowercase

Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown.

 
SELECT last_name, employee_id FROM 
employees;
sqlplus hr/hr
CREATE USER mjones IDENTIFIED BY ty3MU9;

Conventions for Microsoft Windows Operating Systems

The following table describes conventions for Microsoft Windows operating systems and provides examples of their use.

Convention Meaning Example

Choose Start >

How to start a program.

To start the Oracle Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant.

File and directory names

File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the file name begins with \\, then Windows assumes it uses the Universal Naming Convention.

c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32

C:\>

Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual.

C:\oracle\oradata>

The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters.

C:\>exp scott/tiger TABLES=emp QUERY=\"WHERE job='SALESMAN' and sal<1600\"

C:\>imp SYSTEM/password FROMUSER=scott TABLES=(emp, dept)

HOME_NAME

Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore.

C:\> net start OracleHOME_NAMETNSListener

ORACLE_HOME and ORACLE_BASE

In releases prior to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level ORACLE_HOME directory that by default used one of the following names:

  • C:\orant for Windows NT
  • C:\orawin98 for Windows 98

This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level ORACLE_HOME directory. There is a top level directory called ORACLE_BASE that by default is C:\oracle. If you install Oracle9i release 1 (9.0.1) on a computer with no other Oracle software installed, then the default setting for the first Oracle home directory is C:\oracle\ora90. The Oracle home directory is located directly under ORACLE_BASE.

All directory path examples in this guide follow OFA conventions.

Refer to Oracle9i Database Getting Started for Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories.

Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Go to previous page Go to next page
Oracle
Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.
Go To Documentation Library
Home		 Go To Product List
Book List		 Go To Table Of Contents
Contents		 Go To Index
Index
Master Index
Feedback