Database Error Messages Release 1 (9.0.1) - Docs.oracle

To download free release notes, installation documentation, white papers, or othercollateral, please visit the Oracle Technology Network (OTN). You must registeronline before using OTN; registration is free and can be done athttp://technet.oracle.com/membership/index.htmIf you already have a username and password for OTN, then you can go directly tothe documentation section of the OTN Web site onsThis section describes the conventions used in the text and code examples of thisdocumentation set. It describes: Conventions in Text Conventions in Code ExamplesConventions in TextWe 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.ConventionMeaningBoldBold typeface indicates terms that areWhen you specify this clause, you create andefined in the text or terms that appear in index-organized table.a glossary, or both.ItalicsItalic typeface indicates book titles oremphasis.Oracle9i Database ConceptsUppercase monospace typeface indicateselements supplied by the system. Suchelements include parameters, privileges,datatypes, RMAN keywords, SQLkeywords, SQL*Plus or utility commands,packages and methods, as well assystem-supplied column names, databaseobjects and structures, usernames, androles.You can specify this clause only for a ampleEnsure that the recovery catalog and targetdatabase do not reside on the same disk.You can back up the database by using theBACKUP command.Query the TABLE NAME column in the USERTABLES data dictionary view.Use the DBMS STATS.GENERATE STATSprocedure.xvii

idthfont)Lowercase monospace typeface indicatesexecutables, filenames, directory names,and sample user-supplied elements. Suchelements include computer and databasenames, net service names, and connectidentifiers, as well as user-supplieddatabase objects and structures, columnnames, packages and classes, usernamesand roles, program units, and parametervalues.Enter sqlplus to open SQL*Plus.Lowercase monospace italic fontrepresents placeholders or variables.You can specify the parallel clause.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, andlocation id columns are in thehr.departments table.Set the QUERY REWRITE ENABLED initializationparameter to true.Note: Some programmatic elements use amixture of UPPERCASE and lowercase.Connect as oe user.Enter these elements as shown.The JRepUtil class implements these methods.lowercasemonospace(fixed-widthfont) italicRun Uold release.SQL where old releaserefers to the release you installed prior toupgrading.Conventions in Code ExamplesCode examples illustrate SQL, PL/SQL, SQL*Plus, or other command-linestatements. They are displayed in a monospace (fixed-width) font and separatedfrom 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 andprovides examples of their use.ConventionMeaningExample[]Brackets enclose one or more optionalitems. Do not enter the brackets.DECIMAL (digits [ , precision ]){}Braces enclose two or more items, one ofwhich is required. Do not enter thebraces.{ENABLE DISABLE} A vertical bar represents a choice of two{ENABLE DISABLE}or more options within brackets or braces.[COMPRESS NOCOMPRESS]Enter one of the options. Do not enter thevertical bar.xviii

ConventionMeaning.Horizontal ellipsis points indicate either: That we have omitted parts of thecode that are not directly related tothe exampleCREATE TABLE . AS subquery;That you can repeat a portion of thecodeSELECT col1, col2, . , coln FROMemployees;.Vertical ellipsis points indicate that wehave omitted several lines of code notdirectly related to the example.Other notationYou must enter symbols other thanbrackets, braces, vertical bars, and ellipsispoints as shown.ItalicsUPPERCASElowercaseExampleacctbal NUMBER(11,2);acctCONSTANT NUMBER(4) : 3;Italicized text indicates placeholders orvariables for which you must supplyparticular values.CONNECT SYSTEM/system passwordUppercase typeface indicates elementssupplied by the system. We show theseterms in uppercase in order to distinguishthem from terms you define. Unless termsappear in brackets, enter them in theorder and with the spelling shown.However, because these terms are notcase sensitive, you can enter them inlowercase.SELECT last name, employee id FROMemployees;Lowercase typeface indicatesprogrammatic elements that you supply.For example, lowercase indicates namesof tables, columns, or files.SELECT last name, employee id FROMemployees;Note: Some programmatic elements use amixture of UPPERCASE and lowercase.Enter these elements as shown.CREATE USER mjones IDENTIFIED BY ty3MU9;DB NAME database nameSELECT * FROM USER TABLES;DROP TABLE hr.employees;sqlplus hr/hrDocumentation AccessibilityOracle's goal is to make our products, services, and supporting documentationaccessible to the disabled community with good usability. To that end, ourdocumentation includes features that make information available to users ofassistive technology. This documentation is available in HTML format, and containsmarkup to facilitate access by the disabled community. Standards will continue toevolve over time, and Oracle is actively engaged with other market-leadingxix

technology vendors to address technical obstacles so that our documentation can beaccessible to all of our customers. For additional information, visit the OracleAccessibility Program Web site athttp://www.oracle.com/accessibility/JAWS, a Windows screen reader, may not always correctly read the code examplesin this document. The conventions for writing code require that closing bracesshould appear on an otherwise empty line; however, JAWS may not always read aline of text that consists solely of a bracket or brace.xx

Part IIntroductionThis part contains the following chapter: Chapter 1, "Using Messages"

1Using MessagesThis chapter gives you general information and helpful tips about error messages.This chapter covers the following topics: Locating Message Documentation Accuracy of Messages Message Format Recognizing Variable Text in Messages Message Stacks Contacting Oracle Support Services Oracle Exception Messages Trace Files The Alert FileUsing Messages 1-1

Locating Message DocumentationLocating Message DocumentationOracle Database ServerThese messages are generated by the Oracle database server when running anyOracle program. This manual documents messages that are common across Oracleproducts and tools.Product SpecificThese messages are specific to one product and are documented in manuals for thatproduct. For example, if you are working with SQL*Plus on Windows, you wouldneed to refer to the messages contained in SQL*Plus Getting Started for Windows.Operating System-SpecificThese messages are specific to one operating system. A range of message codenumbers are reserved for each operating system. For example, the range ORA-07500to ORA-07999 is reserved for DEC VAX/VMS messages; these messages are listedin 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 youencounter a message without a prefix, first check the manuals for the Oracle Serveryou are using, then check this manual.Accuracy of MessagesThe accuracy of the messages in this manual is our primary concern. Occasionally,an enhancement to a message is not incorporated into the Oracle software. Shouldyou encounter a message generated on your system that differs from the message inthis book, be assured the improved message text is usually incorporated in the nextrelease of the software. If you should encounter a discrepancy, please contact ususing the information contained in the Reader Comment Form at the front of thismanual.1-2 Oracle9i Database Error Messages

Message StacksMessage FormatAll messages displayed are prefixed by text that indicates which program issued themessage. For example, the prefix "ORA" shows that the message was generated bythe Oracle products. The location of messages in this book depends on the prefix ofthe message.All messages are listed in order by the message code number. To look up a message,use the message code number.Recognizing Variable Text in MessagesTo help you find and fix errors, Oracle embeds object names, numbers, andcharacter strings in some messages. These embedded variables are represented bystring, number, or character, as appropriate. For example:ORA-00020: maximum number of processes (number) exceededThe preceding message might actually appear as follows:ORA-00020: maximum number of processes (50) exceededMessage StacksOccasionally, you may see a message stack. This is simply a series of relatedmessages issued at different levels of Oracle.The following message stack is a generic example:ORA-06502: PL/SQL: numeric or value errorORA-06512: at "SCOTT.VALUE ERR", line 1ORA-06512: at line 1The following message stack is a VAX/VMS example:ORA-01034: Oracle not availableORA-07625: smsget: MGBLSC failure%SYSTEM-W-NOSUCHSEC, no such (global) sectionUsing Messages 1-3

Contacting Oracle Support ServicesIn this example, notice that the message at the bottom of the stack is issued by theVMS operating system. Seeing the messages at each level in the system may helpyou trace the originating event. For example, in this case, Oracle may not beavailable simply because it has not been started, and consequently there is nosystem global area (SGA). If you need the help of Oracle Support Services, be sureto report all the messages in the stack.Contacting Oracle Support ServicesSome messages recommend contacting Oracle Support Services to report a problem.When you contact Oracle Support Services, please have the following informationavailable: the hardware, operating system, and release number of the operating system onwhich Oracle is runningthe complete release number of the Oracle Server (for example, release 8.0.5 orrelease 7.1.3)all Oracle programs (with version numbers) in use when the error occurred. Forexample, SQL*Net V2.0 or SQL*Forms V3.0if you encountered one or more error codes or messages, the exact codenumbers and message text, in the order they appearedthe 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.You will also be expected to provide the following: Your name The name of your organization Your Oracle Support ID Number Your telephone number1-4 Oracle9i Database Error Messages

Trace FilesOracle Exception MessagesOracle’s extensive self-checking helps detect internal errors. Oracle uses thefollowing 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], [], [], []The message text can be followed by up to six arguments, which indicate the originand attributes of the error. The first argument is the internal error number. Otherarguments are various numbers, names, and character strings. Empty brackets maybe ignored.In addition to being returned to the user, internal errors are also written to the Alertfile along with additional information about the event causing the message. TheAlert file also lists any trace files that may have been generated because of aninternal error. See the following sections for descriptions of the trace and alert files.If you receive an ORA-00600 message, report it to Oracle Support Services.Trace FilesA trace file is created each time an Oracle instance starts or an unexpected eventoccurs in a user process or background process. The name of the trace file includesthe instance name, the process name, and the Oracle process number. The fileextension or file type is usually TRC, and, if different, is noted in your operatingsystem-specific Oracle documentation. The contents of the trace file may includedumps of the system global area, process global area, supervisor stack, andregisters.Two initialization parameters are used to specify the location of the trace files. The BACKGROUND DUMP DEST initialization parameter specifies the location oftrace files created by the Oracle background processes PMON, DBWR, LGWR,and SMON.The USER DUMP DEST initialization parameter specifies the location of tracefiles created by user processes such as SQL*Loader or Pro*C.The Alert file also describes the location of trace files generated when internal errorsoccur. See the next section for a description of the Alert file.Using Messages 1-5

The Alert FileYou may need to format the trace file before using it to diagnose problems. Toformat a trace file, use the DUMPFMT utility, which is available on most systemsand is described in your operating system-specific Oracle documentation. OracleSupport Services may ask you for a formatted trace file to help solve a problem.See Also: Oracle9i Database Administrator’s Guide for moreinformation about trace filesThe Alert FileThe Alert file is a log file that records information about internal errors andadministrative activities, such as backups. When an internal error occurs, themessage is sent to the terminal screen as well as written to the Alert file. Oracle alsowrites additional information about internal errors to the Alert file, such as thelocation and name of any trace files generated because of the error.The name of the Alert file is operating system-specific. The location of the Alert fileis the same as the location of the background process trace files. This location isspecified by the BACKGROUND DUMP DEST initialization parameter. For moreinformation, see your Oracle operating system-specific documentation.If your system uses an operator’s console, some messages from Oracle may appearon the console. All important messages are written to the Alert file as well as theoperator’s console. Because non-Oracle messages also appear on this console, theAlert file is a better record for tracing all Oracle administrative activity and errorsthan the console log.The Alert file also records information about administrative activities, such asbackups and archiving online redo log files.See Also: Oracle9i Database Administrator’s Guide for moreinformation about the Alert file.1-6 Oracle9i Database Error Messages

Part IIOracle Database Server MessagesThis part contains the following chapters: Chapter 2, "ORA-00000 to ORA-00899" Chapter 3, "ORA-00900 to ORA-01499" Chapter 4, "ORA-01500 to ORA-02099" Chapter 5, "ORA-02100 to ORA-04099" Chapter 6, "ORA-04100 to ORA-07499" Chapter 7, "ORA-07500 to ORA-09857" Chapter 8, "ORA-09858 to ORA-12299" Chapter 9, "ORA-12300 to ORA-12399" Chapter 10, "ORA-12400 to ORA-12699" Chapter 11, "ORA-12700 to ORA-19399" Chapter 12, "ORA-19400 to ORA-24279" Chapter 13, "ORA-24280 to ORA-29249" Chapter 14, "ORA-29250 to ORA-32767"

2ORA-00000 to ORA-00899ORA-00000 normal, successful completionCause: An operation has completed normally, having met no exceptions.Action: No action required.ORA-00001 unique constraint (string.string) violatedCause: An UPDATE or INSERT statement attempted to insert a duplicate key.Action: Either remove the unique restriction or do not insert the key.ORA-00017 session requested to set trace eventCause: The current session was requested to set a trace event by anothersession.Action: This is used internally; no action is required.ORA-00018 maximum number of sessions exceededCause: All session state objects are in use.Action: Increase the value of the SESSIONS initialization parameter.ORA-00019 maximum number of session licenses exceededCause: All licenses are in use.Action: Increase the value of the LICENSE MAX SESSIONS initializationparameter.ORA-00020 maximum number of processes (string) exceededCause: All process state objects are in use.Action: Increase the value of the PROCESSES initialization parameter.ORA-00000 to ORA-00899 2-1

ORA-00021 session attached to some other process; cannot switch sessionCause: The user session is currentl

server Oracle9i Database Migration for the procedures for migrating a previous release of Oracle to Oracle9i Oracle9i SQL Reference for information on Oracle’s SQL commands and functions Oracle9i Database Utilities for information about the utilities bundled with the Oracle