Oracle® Database Error Messages pot

If it is online, then you need to recover the disk.ORA-00205: error in identifying control file, check alert log for more info Cause: The system could not find a control file of the spec

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.

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

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: infodev_us@oracle.com

■ FAX: (650) 506-7227 Attn: Server Technologies Documentation Manager

■ Postal service:

Oracle Corporation

Server Technologies Documentation

400 Oracle Parkway, Mailstop 4op11

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:

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

http://www.oracle.com/accessibility/

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

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

http://oraclestore.oracle.com/

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

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

■ 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

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 errorORA-06512: at "SCOTT.VALUE_ERR", line 1ORA-06512: at line 1

The following message stack is a VAX/VMS example:

ORA-01034: Oracle not availableORA-07625: smsget: $MGBLSC failure

Oracle Exception Messages

%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

■ 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

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

See Also: Oracle Database Administrator's Guide for more

information about the Alert file

The Alert File

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

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

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

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

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

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

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

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

ORA-00096: invalid value string for parameter string, must be from among string

Cause: The value for the initialization parameter is invalid

Action: Choose a value as indicated by the message

ORA-00097: use of Oracle SQL feature not in SQL92 string Level

Cause: Usage of Oracle"s SQL extensions

ORA-00100

ORA-00101: invalid specification for system parameter DISPATCHERS Cause: The syntax for the DISPATCHERS parameter is incorrect

Action: Refer to the manual for correct syntax

ORA-00102: network protocol string cannot be used by dispatchers

Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers

Action: Refer to the manual on network protocols supported by the dispatchers

ORA-00103: invalid network protocol; reserved for use by dispatchers Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers

Action: Specify other network protocols in the connection string

ORA-00104: deadlock detected; all public servers blocked waiting for resources Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources

Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS

ORA-00105: too many dispatcher configurations Cause: Too many dispatcher configurations have been specified No more can be added

Action: Consolidate the dispatcher configurations if possible

ORA-00106: cannot startup/shutdown database when connected to a dispatcher Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher

Action: Re-connect as user INTERNAL without going through the dispatcher For most cases, this can be done by connect to INTERNAL without specifying a network connect string

ORA-00107: failed to connect to ORACLE listener process Cause: Most likely due to the fact that ORACLE listener has not been started

Action: Start ORACLE listener if it has not been started Or else contact your ORACLE representative

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

Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations

Action: Contact your ORACLE representative

ORA-00109: invalid value for attribute string: string

Cause: The value specified for the attribute was incorrect

Action: Refer to the manual for the proper values

ORA-00110: invalid value string for attribute string, must be between string and string

Cause: The value specified for the attribute was incorrect

Action: Specify a value within the range allowed

ORA-00111: invalid attribute string

Cause: The specified attribute was not recognized

Action: Refer to the manual for the proper keyword to use to specify a dispatcher attribute

ORA-00112: value of string is null

Cause: The attribute was specified with no value

Action: Specify a non-null value

ORA-00113: protocol name string is too long

Cause: A protocol name specified in the DISPATCHERS system parameter is too long

Action: Use a valid protocol name for the DISPATCHERS value

ORA-00114: missing value for system parameter SERVICE_NAMES

Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter

Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file

By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_

NAMES 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: SERVICE_NAMES name is too long

Cause: A service name specified in the SERVICE_NAMES system parameter is too long

Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars)

ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified

Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified

Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers

ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified

Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.

Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION

to specify the listening address for dispatchers

ORA-00119: invalid specification for system parameter string

Cause: The syntax for the specified parameter is incorrect

Action: Refer to the Oracle Reference Manual for the correct syntax

ORA-00122: cannot initialize network configuration Cause: ORACLE could not initialize SQL*Net version 2

Action: Check the error stack for detailed information

ORA-00123: idle public server terminating Cause: Too many idle servers were waiting on the common queue

Action: This error is used internally, no action is required

ORA-00125: connection refused; invalid presentation Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported

Action: Correct the PRESENTATION specified in the TNS address

ORA-00126: connection refused; invalid duplicity Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported

Action: Correct the DUPLICITY specified in the TNS address

ORA-00127: dispatcher string does not exist

Cause: There is currently no dispatcher running with the specified name

Action: Retry with a name of the form "D###" denoting an existing dispatcher process

ORA-00128: this command requires a dispatcher name Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN

Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ]

"dispatcher name"

ORA-00129: listener address validation failed "string"

Cause: An error was encountered while validating the listener address

Action: Resolve error or contact your ORACLE representative

ORA-00130: invalid listener address "string"

Cause: The listener address specification is not valid

Action: Make sure that all fields in the listener address (protocol, port, host, key, ) are correct

ORA-00131: network protocol does not support registration "string"

Cause: The specified protocol does not support async notification

Action: Refer to the manual for information on supported network protocols

ORA-00132: syntax error or unresolved network name "string"

Cause: Listener address has syntax error or cannot be resolved

Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system Make sure that the entry is syntactically correct.

ORA-00133: value of string is too long

Cause: The value specified for the attribute was too long

Action: Use shorter names and keywords or remove unneeded blanks

ORA-00134: invalid DISPATCHERS specification #string

Cause: The syntax for the n-th DISPATCHERS specification was incorrect

Action: Refer to the Oracle Reference Manual for the correct syntax

ORA-00150: duplicate transaction ID

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

Action: Check your application

ORA-00151: invalid transaction ID

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

Action: Check your application

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 your application

ORA-00153: internal error in XA library

Cause: The XA library could not access thread-specific pointers

Action: Contact customer support

ORA-00154: protocol error in transaction monitor

Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended

Action: Contact the transaction monitor customer support

ORA-00155: cannot perform work outside of global transaction

Cause: The application tried to perform some work on either an Oracle 7.3 server

or an Oracle8 server with local transactions disabled while outside of a global transaction

Action: Check if the application is connected to an Oracle 7.3 server The

Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3 If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work

ORA-00160: global transaction length string is greater than maximum (string)

Cause: An external global transaction ID with a too large length field was passed in

Action: Report the problem to your external transaction coordinator vendor

ORA-00161: transaction branch length string is illegal (maximum allowed string)

Cause: An external transaction branch ID with a length either too large or 0 was passed in.

Action: Report the problem to your external transaction coordinator vendor

ORA-00162: external dbid length string is greater than maximum (string)

Cause: An external database name with too large a length field was passed in

Action: Report the problem to your external transaction coordinator vendor

ORA-00163: internal database name length string is greater than maximum (string)

Cause: An internal database name with a too large length field was passed in

Action: Report the problem to your external transaction coordinator vendor

ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction

Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction

Action: Roll back or commit the current distributed transaction first

ORA-00165: migratable distributed autonomous transaction with remote operation

is not allowed Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation

Action: none

ORA-00166: remote/local nesting level is too deep Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table

Action: Rearrange the query or co-locate the functions with the tables

ORA-00200: control file could not be created Cause: It was not possible to create the control file

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

ORA-00201: control file version string incompatible with ORACLE version string

Cause: The control file was created by incompatible software

Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release

ORA-00202: control file: "string"

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

Action: See associated error 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 they are not the same files Most likely one instance is using a backup control file

Action: Check that the correct control files were specified

ORA-00204: error in reading (block string, # blocks string) of control file

Cause: A disk I/O failure was detected on reading the control file

Action: Check if the disk is online, if it is not, bring it online and try a warm start again If it is online, then you need to recover the disk.

ORA-00205: error in identifying control file, check alert log for more info

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

Action: Check that ALL control files are online and that they are the same files that the system created at cold start time

ORA-00206: error in writing (block string, # blocks string) of control file

Cause: A disk I/O failure was detected on writing the control file

Action: Check if the disk is online, if it is not, bring it online and try a warm start again If it is online, then you need to recover the disk

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 Most likely 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 is not an old version

ORA-00208: number of control file names exceeds limit of string

Cause: An attempt was made to use more control files than Oracle supports

Action: Shut down Oracle Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle Delete usused files

ORA-00209: control file blocksize mismatch, check alert log for more info

Cause: The block size in the control file header does not match the size specified

in the DB_BLOCK_SIZE parameter

Action: Look at the alert log for more information

ORA-00210: cannot open the specified control file

Cause: Cannot open the control file

Action: Check to make sure the control file exists and is not locked by some other program

ORA-00211: control file does not match previous control files

Cause: A control file was specified that belongs to another database

Action: Find and install the correct control file

ORA-00212: block size string below minimum required size of string bytes

Cause: The block size specified was too small Space for the system overhead is required

Action: Specify a larger block size and retry the operation

ORA-00213: cannot reuse control file; old file size string, string required

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

Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE

CONTROLFILE statement

ORA-00214: control file "string" version string inconsistent with file "string" version string

Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used

Action: Use a consistant set of control files, datafiles/logfiles, 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 is specified or the control file specified does not exist

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

ORA-00216: control file could not be resized for migration from 8.0.2 Cause: The control file created by release 8.0.2 was missing some record types These record types are automatically added by resizing the control file during mount The resize has failed

Action: Look in the alert log for the reason that the resize has failed If indicated

in the alert log, give the control file more space Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file

ORA-00217: control file could not be resized for new record types Cause: The control file was missing some new record types supported by this release These record types are automatically added by resizing the contol file during mount The resize has failed

Action: Look in the alert log for the reason that the resize has failed If indicated

in the alert log, give the control file more space Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file

ORA-00218: block size string of control file "string" does not match DB_BLOCK_ SIZE (string)

Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database

Action: Restore a good copy of the control file If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value

ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)

Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value

Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES,

MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses

ORA-00220: control file not mounted by first instance, check alert log for more info 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 install 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: See accompanying messages.

ORA-00222: operation would reuse name of a currently mounted control file

Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file

Action: Retry the operation with a different filename

ORA-00223: convert file is invalid or incorrect version

Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued

Action: Use a correct version of the convert file or regenerate it with the migration utility Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is

properly set

ORA-00224: control file resize attempted with illegal record type (string)

Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter

Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16)

ORA-00225: expected size string of control file differs from actual size string

Cause: The expected size of the control file as stored in its header was different than the actual operating system file size This usually indicates that the control file was corrupted

Action: Restore a good copy of the control file

ORA-00226: operation disallowed while alternate control file open

Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access

Action: Retry the operation after calling cfileUseCurrent

ORA-00227: corrupt block detected in control file: (block string, # blocks string)

Cause: A block header corruption or checksum error was detected on reading the control file

Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command

ORA-00228: length of alternate control file name exceeds maximum of string

Cause: The specified filename, which was supplied as a parameter to

cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system

Action: Retry the operation with a shorter filename

ORA-00229: operation disallowed: already hold snapshot control file enqueue Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue

Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue

ORA-00230: operation disallowed: snapshot control file enqueue unavailable Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.

Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates

ORA-00231: snapshot control file has not been named Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified

Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName

ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot

Action: Call cfileMakeAndUseSnapshot again (or for the first time)

ORA-00233: copy control file is corrupt or unreadable Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy

Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy

ORA-00234: error in identifying or opening snapshot or copy control file Cause: A snapshot or copy control file of the specified name could not be found

or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot,

or cfileUseCopy

Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively

ORA-00235: control file fixed table inconsistent due to concurrent update Cause: Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information

Action: Retry the operation

ORA-00236: snapshot operation disallowed: mounted control file is a backup Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot,

or cfileUseSnapshot when the currently mounted control file is a backup control file

Action: Mount a current control file and retry the operation

ORA-00237: snapshot operation disallowed: control file newly created Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made

Action: Mount a current control file and retry the operation

ORA-00238: operation would reuse a filename that is part of the database

Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.

Action: Retry the operation with a different filename

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: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as

string string

Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST

parameter is the same as the destination specified by an ALTER SYSTEM

ARCHIVE LOG START TO command

Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command

ORA-00252: log string of thread string is empty, cannot archive

Cause: A log must be used for redo generation before it can be archived The specified redo log was not been used since it was introduced to the database However it is possible that instance death during a log switch left the log empty

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

ORA-00253: character limit string exceeded by archive destination string string

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START

TO command was too long

Action: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message

ORA-00254: error in archive control string "string"

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

Action: Check the archive string used to make sure it refers to a valid online device

ORA-00255: error archiving log string of thread string, sequence # string

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 will allow the database to generate redo

ORA-00256: cannot translate archive destination string string

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START

TO command could not be translated

Action: Check the accompanying message stack for more detailed information Then, retry the ALTER SYSTEM command using a different string

ORA-00257: archiver error Connect internal only, until freed.

Cause: The archiver process received an error while trying to archive a redo log If the problem is not resolved soon, the database will stop executing transactions

The most likely cause of this message is the destination device is out of space to store the redo log file.

Action: Check 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: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number

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

ORA-00260: cannot find online log sequence string for thread string

Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs

Action: Check the ARCHIVE statement, then specify a valid log sequence number Specify a valid log sequence number

ORA-00261: log string of thread string is being archived or modified

Cause: The log is either being archived by another process or an administrative command is modifying the log Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log

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

ORA-00262: current log string of closed thread string 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 string

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

Action: No action required

ORA-00264: no recovery required Cause: An attempt was made to perform media recovery on files that 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 shutdown with the ABORT option Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles

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

ORA-00266: name of archived log file 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 log file 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 log file does not exist "string"

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 log file is part of thread string not string

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 string

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 archive the unarchived redo log files manually, but there are no files that need to be archived

Action: No action required

ORA-00272: error writing archive log string

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 string

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 number 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 string

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

Action: Correct the syntax

ORA-00278: log file "string" 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 string generated at string needed for thread string

Cause: The requested log is required to proceed with recovery

Action: Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL"

ORA-00280: change string for thread string is in sequence #string

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 string 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 the 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 offline, attempt to make it available Make sure 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 string not found in thread string

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, 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 : string

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 archival error occurred See error below

Cause: While attempting to archive to a redo log file, the server encountered an 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.

ORA-00292: parallel recovery feature not installed Cause: A parallel recovery was requested when the parallel recovery option is not installed

Action: Delete the PARALLEL clause from the RECOVER command Also, delete the RECOVERY_PARALLELISM parameter in the initialization file

ORA-00293: control file out of sync with redo log Cause: The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started

Action: Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause

ORA-00294: invalid archivelog format specifier "string"

Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter The only characters permitted following the % symbol are

s, S, t, and T

Action: Correct the initialization file and re-start the instance

ORA-00295: datafile/tempfile number string is invalid, must be between 1 and string

Cause: An invalid file number was specified

Action: Specify a valid datafile or tempfile number and retry the operation

ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE

LIST Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user"s RECOVER command

Action: Re-start the instance with a higher value for DB_FILES

ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START

Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START

Action: Contact customer support

ORA-00298: Missing or invalid attribute value Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT

Action: Correct the syntax and retry the command

ORA-00299: must use file-level media recovery on data file string

Cause: The control file does not contain an entry for this file, so block media recovery cannot be done

Action: Restore the data file and perform file-level media recovery