Oracle® Database Error Messages pot

Oracle® Database
Error Messages
10g Release 2 (10.2)
B14219-01
June 2006
Oracle Database Error Messages, 10g Release 2 (10.2)
B 14219-01
Copyright © 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation
and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license
agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such

purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
iii
Contents
Send Us Your Comments vii
Preface ix
Audience ix
Documentation Accessibility ix
Related Documents x
Conventions xi
1 Using Messages
Locating Message Documentation 1-1
Oracle Database Messages 1-1
Product Specific Messages 1-1
Operating System-Specific Messages 1-2
Accuracy of Messages 1-2
Message Format 1-2
Recognizing Variable Text in Messages 1-2
Message Stacks 1-2
Contacting Oracle Support Services 1-3
Oracle Exception Messages 1-3

Trace Files 1-4
The Alert File 1-4
iv
2 ORA-00000 to ORA-00832
3 ORA-00910 to ORA-01497
4 ORA-01500 to ORA-02098
5 ORA-02140 to ORA-04099
6 ORA-04930 to ORA-07499
7 ORA-09870 to ORA-12100
8 ORA-07500 to ORA-09859
9 ORA-12150 to ORA-12236
10 ORA-12315 to ORA-12354
11 ORA-12400 to ORA-12497
12 ORA-12500 to ORA-12699
13 ORA-12700 to ORA-19380
14 ORA-19400 to ORA-24276
15 ORA-24280 to ORA-28674
16 ORA-29250 to ORA-32775
17 ORA-32800 to ORA-32848
18 ORA-33000 to ORA-37999
19 ORA-38029 to ORA-39962
20 ORA-40001 to ORA-40322
21 EXP-00000 to EXP-00107
22 IMP-00000 to IMP-00401
23 SQL*Loader-00100 to SQL*Loader-03120
v
24 KUP-00550 to KUP-11012
25 UDE-00001 to UDE-00053
26 UDI-00001 to UDI-00053
27 DBV-00200 to DBV-00200

28 NID-00001 to NID-00604
29 DGM-16900 to DGM-17007
30 LCD-00100 to LCD-00219
31 QSM-00501 to QSM-03120
32 OCI-00601 to OCI-31199
33 RMAN-00550 to RMAN-20507
34 LRM-00100 to LRM-00123
35 LFI-00002 to LFI-01523
36 PLS-00049 to PLS-01913
37 PLW-05000 to PLW-07204
38 AMD-00100 to AMD-00160
39 CLSR-00001 to CLSR-06507
40 CLSS-00001 to CLSS-03202
41 PROC-00001 to PROC-00106
42 PROT-00001 to PROT-00807
43 TNS-00000 to TNS-12699
44 NNC-00001 to NNC-00501
45 NNO-00050 to NNO-00854
vi
46 NNL-00001 to NNL-01078
47 NPL-00100 to NPL-00420
48 NNF-00001 to NNF-04009
49 NMP-00001 to NMP-00011
50 NCR-00001 to NCR-04028
51 NZE-28750 to NZE-29249
52 O2F-00301 to O2F-00341
53 O2I-00101 to O2I-00133
54 O2U-00200 to O2U-00212
55 PCB-00001 to PCB-00903
56 PCC-00001 to PCC-01515

57 PCC-02010 to PCC-02451
58 SQL-01075 to SQL-02157
59 AUD-00611 to AUD-00809
60 IMG-00001 to IMG-02014
61 VID-00611 to VID-00721
62 DRG-10000 to DRG-52210
63 LPX-00000 to LPX-00773
64 LSX-00001 to LSX-00344
vii
Send Us Your Comments
Oracle Database Error Messages, 10g Release 2 (10.2)
B14219-01
Oracle welcomes your comments and suggestions on the quality and usefulness of this
publication. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate
the title and part number of the documentation and the chapter, section, and page
number (if available). You can send comments to us in the following ways:
■ Electronic mail:
■ FAX: (650) 506-7227 Attn: Server Technologies Documentation Manager
■ Postal service:
Oracle Corporation
Server Technologies Documentation
400 Oracle Parkway, Mailstop 4op11
Redwood Shores, CA 94065
USA

If you would like a reply, please give your name, address, telephone number, and
electronic mail address (optional).
If you have problems with the software, please contact your local Oracle Support
Services.
viii
ix
Preface
This manual describes error messages that may appear while using products that are
part of the Oracle Database. 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
■ Documentation Accessibility
■ Related Documents
■ Conventions
Audience
Oracle Database Error Messages is intended for all Oracle users.
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. Accessibility standards will continue to
evolve over time, and Oracle 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 more information, visit the Oracle Accessibility
Program Web site at
/>Accessibility of Code Examples in Documentation

Screen readers 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, some screen readers may not always read a line of text
that consists solely of a bracket or brace.
x
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or
organizations that Oracle does not own or control. Oracle neither evaluates nor makes
any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services
within the United States of America 24 hours a day, seven days a week. For TTY
support, call 800.446.2398.
Related Documents
For more information, see these Oracle resources:
■ Oracle Database Concepts for general information about the Oracle Database and
how it works
■ Oracle Database Administrator's Guide and Oracle Database Backup and Recovery Basics
for information about administering the Oracle Database
■ Oracle Database Application Developer's Guide - Fundamentals, Oracle Database
PL/SQL Packages and Types Reference, Oracle Database Application Developer's Guide -
Large Objects, and Oracle Streams Advanced Queuing User's Guide and Reference for
information about developing database applications within the Oracle Database
■ Oracle Database Upgrade Guide for the procedures for upgrading the Oracle
Database
■ Oracle Database SQL Reference for information on Oracle’s SQL commands and
functions
■ Oracle Database Utilities for information about the utilities bundled with the Oracle
Database, including Export, Import, and SQL*Loader
■ Oracle Database Net Services Administrator's Guide for information about Oracle Net

Services
■ Oracle Database Advanced Security Administrator's Guide for information about data
encryption, external authentication services, and Oracle DCE integration, all
included in the Oracle Advanced Networking Option
■ For information specific to the Oracle Database working on your host operating
system, see your operating system-specific Oracle documentation (specific book
titles vary by operating system) and system release bulletins, if available.
Many of the examples in this book use the sample schemas, which are installed by
default when you select the Basic Installation option with an Oracle Database
installation. Refer to Oracle Database Sample Schemas for information on how these
schemas were created and how you can use them yourself.
Oracle error message documentation is only available in HTML. If you only have
access to the Oracle Documentation CD, you can browse the error messages by range.
Once you find the specific range, use your browser's "find in page" feature to locate the
specific message. When connected to the Internet, you can search for a specific error
message using the error message search feature of the Oracle online documentation.
Printed documentation is available for sale in the Oracle Store at
/>xi
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
/>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
/>Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type
indicates graphical
user interface
elements associated

with an action, or
terms defined in text
or the glossary.
italic Italic type indicates
book titles, emphasis,
or placeholder
variables for which
you supply particular
values.
monospace Monospace type
indicates commands
within a paragraph,
URLs, code in
examples, text that
appears on the
screen, or text that
you enter.
xii
Using Messages 1-1
1
Using Messages
This 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 File
Locating Message Documentation
This section describes how to locate message documentation when given an error
message.
Oracle error message documentation is only available in HTML. If you only have
access to the Oracle Documentation CD, you can browse the error messages by range.
Once you find the specific range, use your browser's "find in page" feature to locate the
specific message. When connected to the Internet, you can search for a specific error
message using the error message search feature of the Oracle online documentation.
Oracle Database Messages
These messages are generated by the Oracle Database when running any Oracle
program. This manual documents messages that are common across Oracle products
and tools.
Product Specific Messages
These messages are specific to one product and are documented in manuals for that
product. For example, if you are working with Oracle Enterprise Manager, you would
need to refer to the messages contained in the Oracle Enterprise Manager Messages
Manual.
Accuracy of Messages
1-2 Oracle Database Error Messages
Operating System-Specific Messages
These messages are specific to one operating system. A range of message code
numbers are reserved for each operating system. For example, the range ORA-07500 to
ORA-07999 is reserved 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 release of Oracle 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, then please contact us using
the information contained in the Reader Comment Form at the front of this manual.
Message Format
All messages 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 products. The location of messages in this book depends on the prefix of the
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 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 string, number,
or character, as appropriate. For example:
ORA-00020: maximum number of processes (number) exceeded
The preceding message might actually appear as follows:
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
Oracle Exception Messages
Using Messages 1-3
%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 Oracle Support Services, then be sure to report all the
messages in the stack.
Contacting Oracle Support Services
Some messages recommend contacting Oracle Support Services to report a problem.
When you contact Oracle Support Services, please have the following information
available:
■ The hardware, operating system, and release number of the operating system on
which Oracle is running
■ The complete release number of the Oracle Database (for example, release 9.2.0.1.0
or release 9.0.1.1.2)
■ 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, then the exact code
numbers and message text, 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.
You will also be expected to provide the following:
■ Your name
■ The name of your organization

■ Your Oracle Support ID Number
■ Your telephone number
Oracle Exception Messages
Oracle’s extensive self-checking helps detect internal errors. Oracle uses the following
catchall message for Oracle internal exceptions:
ORA-00600: internal error code, arguments: [number], [number], [], [], [], []
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 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.
Trace Files
1-4 Oracle Database Error Messages
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 to Oracle Support Services.
Trace Files
A trace file is created each time an Oracle instance starts or an unexpected event occurs
in a user process or background process. 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 in 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 are used to specify the location of the trace files.
■ The BACKGROUND_DUMP_DEST initialization parameter specifies the location of
trace files created by the Oracle background processes PMON, DBWR, LGWR, and
SMON.

■ The USER_DUMP_DEST initialization parameter specifies the location of trace files
created by user processes such as SQL*Loader 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. Oracle Support
Services may ask you for a formatted trace file to help solve a problem.
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.
The name of the Alert file is operating system-specific. 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 Oracle 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.
See Also: Oracle Database Administrator's Guide for more
information about trace files
The Alert File
Using Messages 1-5
See Also: Oracle Database Administrator's Guide for more

information about the Alert file
The Alert File
1-6 Oracle Database Error Messages
ORA-00000 to ORA-00832 2-1
2
ORA-00000 to ORA-00832
ORA-00000: normal, successful completion
Cause: Normal exit.
Action: None.
ORA-00001: unique constraint (string.string) violated
Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For
Trusted Oracle configured in DBMS MAC mode, you may see this message if a
duplicate entry exists at a different level.
Action: Either remove the unique restriction or do not insert the key.
ORA-00017: session requested to set trace event
Cause: The current session was requested to set a trace event by another session.
Action: This is used internally; no action is required.
ORA-00018: maximum number of sessions exceeded
Cause: All session state objects are in use.
Action: Increase the value of the SESSIONS initialization parameter.
ORA-00019: maximum number of session licenses exceeded
Cause: All licenses are in use.
Action: Increase the value of the LICENSE MAX SESSIONS initialization
parameter.
ORA-00020: maximum number of processes (string) exceeded
Cause: All process state objects are in use.
Action: Increase the value of the PROCESSES initialization parameter.
ORA-00021: session attached to some other process; cannot switch session
Cause: The user session is currently used by others.
Action: Do not switch to a session attached to some other process.

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 that you have privilege to access, that is either
you own it or you have the CHANGE_USER privilege.
ORA-00023: session references process private memory; cannot detach session
2-2 Oracle Database Error Messages
Cause: An attempt was made to detach the current session when it contains
references to 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 and/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: Trying to login more than once from different processes for ORACLE
started in single-process mode.
Action: Logoff from the other process.
ORA-00025: failed to allocate string
Cause: Out of memory.
Action: Restart with larger sga heap.
ORA-00026: missing or invalid session ID
Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION.
Action: Retry with a valid session ID.
ORA-00027: cannot kill current session
Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current
session.
Action: None.
ORA-00028: your session has been killed
Cause: A privileged user has killed your session and you are no longer logged on

to the database.
Action: Login again if you wish to continue working.
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, recursive, etc.).
Action: Retry with a user 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 an ALTER SYSTEM KILL SESSION command
cannot be killed immediately (because it is rolling back or blocked on a network
operation), but it has been marked for kill. This means it will be killed as soon as
possible after its current uninterruptable operation is done.
Action: No action is required for the session to be killed, but further executions of
the ALTER SYSTEM KILL SESSION command on this session may cause the
session to be killed sooner.
ORA-00032: invalid session migration password
ORA-00000 to ORA-00832 2-3
Cause: The session migration password specified in a session creation call was
invalid (probably too long).
Action: Retry with a valid password (less than 30 chars).
ORA-00033: current session has empty migration password
Cause: An attempt was made to detach or clone the current session and it has an
empty migration password. This is not allowed.
Action: Create the session with a non-empty migration password.
ORA-00034: cannot string in current PL/SQL session
Cause: An attempt was made to issue a commit or rollback from a PL/SQL object
(procedure, function, package) in a session that has this disabled (by "alter session

disable commit in procedure")
Action: Enable commits from PL/SQL in this session, or do not attempt to use
commit or rollback in PL/SQL when they are disabled in the current session.
ORA-00036: maximum number of recursive SQL levels (string) exceeded
Cause: An attempt was made to go more than the specified number of recursive
SQL levels.
Action: Remove the recursive SQL, possibly a recursive trigger.
ORA-00037: cannot switch to a session belonging to a different server group
Cause: An attempt was made to switch to a session in a different server group.
This is not allowed.
Action: Make sure the server switches to a session that belongs to its server
group.
ORA-00038: Cannot create session: server group belongs to another user
Cause: An attempt was made to create a non-migratable session in a server group
that is owned by a different user.
Action: A server group is owned by the first user who logs into a server in the
server group in non-migratable mode. All subsequent non-migratable mode logins
must be made by the user who owns the server group. To have a different user
login in non-migratable mode, the ownership of the server group will have to be
changed. This can be done by logging off all current sessions and detaching from
all existing servers in the server group and then having the new user login to
become the new owner.
ORA-00040: active time limit exceeded - call aborted
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database
administrator for more information.
ORA-00041: active time limit exceeded - session terminated
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database
administrator for more information.

ORA-00042: Unknown Service name string
Cause: An attempt was made to use an invalid application service.
Action: Use a valid service name from SERVICE$ or add a new service using the
DBMS_SERVICE package.
2-4 Oracle Database Error Messages
ORA-00050: operating system error occurred while obtaining an enqueue
Cause: Could not obtain the operating system resources necessary to cover an
oracle enqueue. This is normally the result of an operating system user quota that
is too low.
Action: Look up the operating system error in your system documentation and
perform the needed action.
ORA-00051: timeout occurred while waiting for a resource
Cause: Usually due to a dead instance.
Action: Check for any dead, unrecovered instances and recover them.
ORA-00052: maximum number of enqueue resources (string) exceeded
Cause: Ran out of enqueue resources.
Action: Increase the value of the ENQUEUE_RESOURCES initialization
parameter.
ORA-00053: maximum number of enqueues exceeded
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.
ORA-00054: resource busy and acquire with NOWAIT specified
Cause: Resource interested is busy.
Action: Retry if necessary.
ORA-00055: maximum number of DML locks exceeded
Cause: Ran out of DML lock state objects.
Action: Increase the value of the DML_LOCKS initialization parameter and warm
start.
ORA-00056: DDL lock on object "string.string" is already held in an incompatible
mode

Cause: An attempt was made to acquire a DDL lock that is already locked.
Action: This happens if you attempt to drop a table that has parse locks on it.
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 the value of the TEMPORARY_TABLE_LOCKS initialization
parameter and warm start.
ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being
mounted. It does not match the value used to create the database.
Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that
matches the value.
ORA-00059: maximum number of DB_FILES exceeded
Cause: The value of the DB_FILES initialization parameter was exceeded.
Action: Increase the value of the DB_FILES parameter and warm start.
ORA-00060: deadlock detected while waiting for resource
Cause: Transactions deadlocked one another while waiting for resources.
ORA-00000 to ORA-00832 2-5
Action: Look at the trace file to see the transactions and resources involved. Retry
if necessary.
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: Ensure that all instances" INIT.ORA files specify the DML_LOCKS
parameter as 0 or all as non-zero.
ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause: The instance was started with DML_LOCKS = 0, and the statement being
executed needs a full-table lock (S, X, or SSX).
Action: Restart the instance with DML_LOCKS not equal to zero, and reexecute
the statement.

ORA-00063: maximum number of log files exceeded string
Cause: The number of log files specificied exceeded the maximum number of log
files supported in this release.
Action: Re-create the control file with the highest number of log files no greater
than the maximum supported in this release.
ORA-00064: object is too large to allocate on this O/S (string,string)
Cause: An initialization parameter was set to a value that required allocating
more contiguous space than can be allocated on this operating system.
Action: Reduce the value of the initialization parameter.
ORA-00065: initialization of FIXED_DATE failed
Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
Action: Make sure the initialization parameter is in the correct date format.
ORA-00067: invalid value string for parameter string; must be at least string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.
ORA-00068: invalid value string for parameter string, must be between string and
string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.
ORA-00069: cannot acquire lock table locks disabled for string
Cause: A command was issued that tried to lock the table indicated in the
message. Examples of commands that can lock tables are: LOCK TABLE, ALTER
TABLE ADD ( ), and so on.
Action: Use the ALTER TABLE ENABLE TABLE LOCK command, and retry
the command.
ORA-00070: command string is not valid
Cause: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.
ORA-00071: process number must be between 1 and string
Cause: An invalid process number was specified.

2-6 Oracle Database Error Messages
Action: Specify a valid process number.
ORA-00072: process "string" is not active
Cause: An invalid process was specified.
Action: Specify a valid process.
ORA-00073: command string takes between string and string argument(s)
Cause: An incorrect number of arguments was specified.
Action: Specify the correct number of arguments. Type HELP to see the list of
commands and their syntax.
ORA-00074: no process has been specified
Cause: No debug process has been specified.
Action: Specify a valid process.
ORA-00075: process "string" not found in this instance
Cause: The specified process was not logged on to the current instance.
Action: Specify a valid process.
ORA-00076: dump string not found
Cause: An attempt was made to invoke a dump that does not exist.
Action: Type DUMPLIST to see the list of available dumps.
ORA-00077: dump string is not valid
Cause: An attempt was made to invoke an invalid dump.
Action: Try another dump.
ORA-00078: cannot dump variables by name
Cause: An attempt was made to dump a variable by name on a system that does
not support this feature.
Action: Try the PEEK command.
ORA-00079: variable string not found
Cause: An attempt was made to dump a variable that does not exist.
Action: Use a valid variable name.
ORA-00080: invalid global area specified by level string
Cause: An attempt was made to dump an invalid global area.

Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra +
level> to dump global area <level> as well as <extra> bytes for every pointer;
<extra> must be a multiple of 4.
ORA-00081: address range [string, string) is not readable
Cause: An attempt was made to read/write an invalid memory address range.
Action: Try another address or length.
ORA-00082: memory size of string is not in valid set of [1], [2],
[4]stringstringstringstringstring
Cause: An invalid length was specified for the POKE command.
Action: Use a valid length (either 1, 2, 4, or possibly 8).
ORA-00083: warning: possibly corrupt SGA mapped
ORA-00000 to ORA-00832 2-7
Cause: Even though there may be SGA corruptions, the SGA was mapped.
Action: Use the DUMPSGA command to dump the SGA.
ORA-00084: global area must be PGA, SGA, or UGA
Cause: An attempt was made to dump an invalid global area.
Action: Specify either PGA, SGA, or UGA.
ORA-00085: current call does not exist
Cause: An invalid attempt was made to dump the current call heap.
Action: Wait until the process starts a call.
ORA-00086: user call does not exist
Cause: An invalid attempt was made to dump the user call heap.
Action: Wait until the process starts a call.
ORA-00087: command cannot be executed on remote instance
Cause: Cluster database command issued for non cluster database ORADEBUG
command.
Action: Issue the command without the cluster database syntax.
ORA-00088: command cannot be executed by shared server
Cause: Debug command issued on shared server.
Action: Reissue the command using a dedicated server.

ORA-00089: invalid instance number in ORADEBUG command
Cause: An invalid instance number was specified in a cluster database
ORADEBUG command.
Action: Reissue the command with valid instance numbers.
ORA-00090: failed to allocate memory for cluster database ORADEBUG command
Cause: Could not allocate memory needed to execute cluster database oradebug.
Action: Reissue the command on each instance with single-instance oradebug.
ORA-00091: LARGE_POOL_SIZE must be at least string
Cause: The value of LARGE_POOL_SIZE is below the minimum size.
Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_
ALLOC
Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_
POOL_MIN_ALLOC.
Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_
POOL_MIN_ALLOC.
ORA-00093: %s must be between string and string
Cause: The parameter value is not in a valid range.
Action: Modify the parameter value to be within the specified range.
ORA-00094: %s requires an integer value
Cause: The parameter value is not an integer.
Action: Modify the parameter value to be an integer.