Oracle 8i Error - EBIN.PUB (2023)

Oracle8i

message error

Version 2 (8.1.6)

December 1999 Part No. A76999-01

Error Messages Version 2 (8.1.6) Part No. A76999-01 Copyright © 1996, 1999, Oracle Corporation. All rights reserved. The Programs (including software and documentation) contain proprietary information of Oracle Corporation; are provided under a license agreement that contains 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 is prohibited. The information contained in this document is subject to change without notice. If you find any problems with the documentation, please let us know in writing. Oracle Corporation does not warrant that this document is error free. Except as 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, without the express written permission of Oracle Corporation. If the Programs are provided to the US Government or to anyone who licenses or uses the Programs on behalf of the US Government, the following notice applies: Restricted Rights Notice The Programs provided are subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the license restrictions set forth in the applicable Oracle license agreement. Otherwise, the Programs delivered subject to the Federal Acquisition Regulations are "restricted computer software" and use, duplication, and disclosure of the Programs will be subject to the restrictions of FAR 52.227-19, Commercial Computer Software - Restricted Rights ( June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in nuclear, aviation, mass transit, medical, or other inherently hazardous applications. It shall be Licensee's responsibility to take all appropriate security, backup, redundancy, and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims any liability for any damages caused. for such use of the Programs. . Oracle is a registered trademark and ConText, LogMiner, Net8, Oracle Names, Oracle7, Oracle7 Spatial Data Option, Oracle8, Oracle8i, PL/SQL, Pro*Ada, Pro*C, Pro*C/C++, Pro*COBOL, Pro* FORTRAN, Pro*Pascal, Pro*PL/1, SQL*Connect, SQL*Forms, SQL*Loader, SQL*Module, SQL*Net, SQL*Plus, SQL*Report, and Trusted Oracle are trademarks or registered trademarks of Oracle Corporation. All other company or product names mentioned are used for identification purposes only and may be trademarks of their respective owners.

Content Send us your comments ............................................ . . . . . . . . . . .... ..... ix Preface ................................... ... . ............................................... ................ ... .. ............................. .................. ....... .... ........... xi Target Audience .... .......................... ........... .............. ............................................. .... .... ........................... ....... xiii Structure ....... .... .... .......................... .. ... .... .......................... ................... .... .................................... xiii Related Documents............ ................................................................ ................ . ................................................................ ....... .................. xiv How to contact customer service ............ ...... . ............................................ ... ....................................................... ......... ... XV

Part I 1

Introduction

Using Messaging Locating the Messaging documentation .................................. ....... ............................................ ....... ................... ... Oracle Server . ................. .................................. .................................................. .. ..................... .......... Product Specific . ............................................ ...... ................................................................ .................. ............................ ....... OS Specific ....... ....... ........................ ..... ................ .......... .......... ....... ............ ........ Accuracy of message ............ .......... ...................................................... ................................................................ ....... ..... Message format ..... ............................ ....... ............ ............................ ........................ .......... ... ............. ................... Recognition of variable text in messages .......... ... .......... .. ................................................ ... .......... ........... ............ Piles of men centuries........ ......................................... ......... ............ ..... ........................ ......... ............ ... ................... ...... Calling Customer Service .................................. ...... . ......................................................... .... ..... . .................................... Oracle Exception Messages.. ... ... .. .................................................. ............. .... .................................. ................... ............. . ... Trace Files ............................................ ........ ..... ........................ ............ ....... ............................................ .. ....... The alert file ......................................... .... .......... .......... ......................... .... .............................................. ........ ......................

1-1 1-1 1-1 1-2 1-2 1-2 1-3 1-3 1-4 1-4 1-5 1-6

iii

Part II

Oracle server messages

ORA-00000 to ORA-00899

ORA-00900 to ORA-01499

ORA-01500 to ORA-02099

ORA-02100 to ORA-04099

ORA-04100 to ORA-07499

ORA-07500 to ORA-09857

ORA-09870 to ORA-12299

ORA-12300 to ORA-12399

ORA-12400 to ORA-12699

ORA-12700 to ORA-19399

ORA-19400 to ORA-24279

ORA-24280 to ORA-29249

ORA-29250 to ORA-30999

Part III

Server utility messages

Mensajeros de Oracle Trace Collection Services (EPC)

sixteen

Export messages (EXP)

Import messages (IMP)

Parameter messages (LRM)

Parameter messages (LCD)

BFILE (LFI) Related Messages

PL/SQL and FIPS (PLS) messages

Consultant Message Summary (QSM)

Recovery Manager Messages (RMAN)

Mensajes SQL*Loader (SQL*Loader)

Part IV

network messages

Net8 Messaging (TNS)

Oracle Name Client Messages (NNC)

Oracle Names Server (NNO) Messages

Oracle Name Control (NNL) Utility Messages

Oracle Name Server Network Presentation Layer (NPL) Messages

External Name Messaging (NNF)

Network Management Protocol (NMP) Simple Messaging

Remote Operation Messages (NCR)

Network Security Messages (NZE)

Parte V

Precompiler messages

SQL* Module Messages (MOD)

Object Type Translator File Type Messages (O2F)

Object Type Converter (O2I) Initialization Messages

Object Type Converter (O2U) Unparser Messages

Pro*COBOL Messages (PCBs)

Mensagens PCF FIPS (PCF)

Pro*C/C++ Messaging (PCS)

Preprocesador (PG2)

Command Line Messaging (PGO)

Parser Messages (PPE)

Preprocessor (PR2)

Messaging Pro* (PRO)

SQL runtime messages (SQL)

Part VI 47

Options Messages

Intermediate audio messages (AUD)

intermediate image messages (IMG)

Intermediate Video Messages (VIDs)

intermediate text messaging (DRG)

Time Series (TS) messages

Spatial Data Option (SDO) messages

Visual Information Retrieval (VIR) messages

Index

viii

Send us your feedback Error Messages Version 2 (8.1.6) Part No. A76999-01

Oracle Corporation welcomes your comments and suggestions regarding the quality and usefulness of this publication. Your input is an important part of the information used for the review. 🇧🇷

? Did you find errors? Is the information presented clearly? Do you need more info? If yes 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 other suggestions for improvement, please provide the chapter, section, and page number (if available). You can send us feedback in the following ways: ■ ■ ■

Email -[email protected]FAX - (650) 506-7228. A la atención de: Information Development Service postal: Oracle Corporation Information Development Department 500 Oracle Parkway, M/S 4op12 Redwood Shores, CA 94065 EE. UU.

If you would like an answer, please provide your name, address and phone number below.

If you have problems with the software, please contact your local Oracle support services.

Preface This manual describes error messages that may appear when using products that are part of Oracle. Messages are included in this manual for the following products:

Product/chapter name

Prefix

Intermediate audio messages (AUD)

AUD

intermediate text messaging (DRG)

GRD

Mensajeros de Oracle Trace Collection Services (EPC)

CEP

Export messages (EXP)

Exp

intermediate image messages (IMG)

IMG

Import messages (IMP)

DIABLILLO

Parameter messages (LCD)

LCD

BFILE (LFI) Related Messages

LFI

Parameter messages (LRM)

LRM

SQL* Module Messages (MOD)

MODIFICACIÓN

Remote Operation Messages (NCR)

RNC

Network Management Protocol (NMP) Simple Messaging

NMP

Oracle Name Client Messages (NNC)

NNC

External Name Messaging (NNF)

NNF

Oracle Name Control (NNL) Utility Messages

NNL

Product/chapter name

Prefix

Oracle Names Server (NNO) Messages

NNO

Oracle Name Server Network Presentation Layer (NPL) Messages

NPL

Network Security Messages (NZE)

Object Type Translator File Type Messages (O2F)

O2F

Object Type Converter (O2I) Initialization Messages

O2I

Object Type Converter (O2U) Unparser Messages

O2U

Oracle server messages

TIME-00000 to TIME-00899 TIME-00900 to TIME-01499 TIME-01500 to TIME-02099 TIME-02100 to TIME-04099 TIME-04100 to TIME-07499 TIME-07500 to TIME-09857 TIME-09870 to TIME-12299 TIME -12300 to TIME-12399 TIME-12400 to TIME-12699 TIME-12700 to TIME-19399 TIME-19400 to TIME-24279 TIME-24280 to TIME-29249 TIME-29250 to TIME-30999

Pro*COBOL Messages (PCBs)

printed circuit board

Mensagens PCF FIPS (PCF)

PCF

Pro*C/C++ Messaging (PCS)

Preprocesador (PG2)

PG2

Command Line Messaging (PGO)

OGP

PL/SQL and FIPS (PLS) messages

please

Parser Messages (PPE)

PAI

Preprocessor (PR2)

PR2

Messaging Pro* (PRO)

PRO

Consultant Message Summary (QSM)

QSM

Product/chapter name

Prefix

Recovery Manager Messages (RMAN)

RMAN

Spatial Data Option (SDO) messages

SDO

SQL runtime messages (SQL)

sql

Mensajes SQL*Loader (SQL*Loader)

SQL Loader*

Net8 Messaging (TNS)

TNS

Time Series (TS) messages

Intermediate Video Messages (VIDs)

Visual Information Retrieval (VIR) messages

Each message list in the manual contains the statement of the message, an explanation of the probable cause(s) for the message, and a recommended action. If the message is a warning or indicates that an error has occurred, the message list indicates a corrective action.

Intended Audience This manual is intended for all Oracle users.

Structure Oracle8i error messages are divided into the following parts: ■

Part I, "Introduction"

■

Part II, "Oracle Server Messages"

■

Part III, "Server Utility Messages"

■

Part IV, "Network Messages"

■

Part V, "Precompiler Messages"

■

Part VI, "Option Messages"

XIII

Related Documents You will also find references in this book to important information in related publications. Related books referenced in this manual are listed below: ■

■

For general information about Oracle Server and how it works, see Oracle8i Concepts. For information on administering the Oracle Server, see the Oracle8i Administrator's Guide and the Oracle8i Backup and Recovery Guide. For information about developing database applications on Oracle Server, see the following: ■

Oracle8i Application Developer's Guide - Fundamentals

■

Reference to PL/SQL packages provided by Oracle8i

■

Oracle8i Application Developer's Guide - Large Objects (LOBs)

■

Oracle8i Application Developer Guide - Advanced Queue

For procedures for migrating a previous version of Oracle to Oracle8i, see Migrating from Oracle8i. For information on Oracle SQL commands and functions, see the Oracle8i SQL Reference. For information about the utilities included with Oracle Server, including Export, Import, and SQL*Loader, see Oracle8i Utilities. For specific information about Oracle Server running 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. For information about Net8, see the Net8 Administrator's Guide. For information about data encryption, external authentication services, and Oracle DCE integration, all included in the Oracle Advanced Networking option, see the Oracle Advanced Security Administrator's Guide.

Oracle Corporation also publishes various files, which are available on its distribution media. These files describe differences between minor releases of Oracle software that are not accompanied by new manuals. These files are typically named README.DOC, BUGFIX.DOC, BUGHST.DOC, and RESTRICT.DOC. Read these files for software changes that are not described in the regular manuals.

xiv

Additional Information: The exact names and locations of the files being referenced

above may vary depending on your operating system. See your operating system-specific Oracle documentation for information on these files.

Contacting Customer Service You can contact Oracle Worldwide Support Services (WWS) at the following numbers (hours are specified in your support contract): ■

In the United States, call: 1.650.506.1500.

■

In Europe, call: +44.1344.860160.

■

In Asia, call: +81.3.5717.1850.

Please have the following information ready before you call: ❏

Your CSI number (if applicable) or full contact details, including any special project information.

❏

Release levels of Oracle Server and associated products (for example, Oracle8 Server version 8.0.3.0 and Oracle Forms version 4.5.6.3.2).

❏

OS name and version level, including patches and packages.

❏

Details of error codes, numbers, and descriptions associated with the problem.

❏

A complete description of the problem, including: ■

■

What happened? For example, the command used and the result obtained. When I pass that? For example, the time of day or after a specific command or after an operating system or Oracle update. Where did it happen? For example, about a specific system or about a specific procedure or table. What is the scope of the problem? For example, is your production system down or is the impact less severe? Is the problem getting worse?

Note what didn't happen as well as what did. 🇧🇷

Copies of any trace files, core dumps, or log files recorded near the time of the incident.

For installation-related problems, please have the following information available: ❏

Listings of the contents of the ORACLE_HOME directory and any staging areas, if applicable.

❏

Contents of the installation log files in the $ORACLE_HOME/orainst directory: install.log, sql.log, make.log, and os.log.

For more information, contact http://www.oracle.com/support.

XVI

Part I Introduction This part contains the following chapter: ■

Chapter 1, "Using Messages"

1 Using Messaging This chapter provides general information and useful tips on messaging. The following sections are included: ■

Locating the message documentation

■

Message accuracy

■

message format

■

Recognition of variable text in messages

■

lots of messages

■

Call customer service

■

Oracle exception messages

■

trace files

■

the alert file

Oracle Server Message Documentation Location These messages are generated by the Oracle server when any Oracle program is executed. This manual documents the messages that are common to all Oracle products and tools.

Product Specific These messages are specific to a product and are documented in the manuals for that product. For example, if you are working with SQL*Net on a Macintosh,

Using Messages 1-1

Message accuracy

you should refer to the messages in the SQL*Net documentation, SQL*Net Manual for Macintosh.

Operating System Specific These messages are specific to an operating system. A range of message code numbers is reserved for each operating system. For example, the range ORA-07500 to ORA-07999 is for DEC VAX/VMS messages; these messages are listed in the appropriate operating system-specific documentation. The message prefix indicates where to find information about the message. For example, some messages in this manual are prefixed with "ORA". If you encounter a message with no prefix, first consult the manuals for the Oracle server you are using, and then refer to this manual.

Accuracy of Messages The accuracy of the messages in this manual is our primary concern. Sometimes a message enhancement is not integrated into Oracle software. If you find a message generated on your system that differs from the message in this book, rest assured that the improved message text will be incorporated into the next version of the software. If you find a discrepancy, please contact us using the information contained in the reader comment form at the beginning of this manual.

Message Format All displayed messages are preceded by text indicating which program issued the message. For example, the "ORA" prefix shows that the message was generated by Oracle products. The location of messages in this book depends on the message prefix. The table in the "Preface" of this book lists the message prefixes you can find and the location of the message in this book. All messages are listed in order by message code number. To search for a message, use the code number of the message.

1-2

message error

lots of messages

Variable Text Recognition in Messages To help you find and correct errors, Oracle embeds object names, numbers, and character strings into some messages. These built-in variables are represented by strings, numbers, or characters, as appropriate. For example, message ORA-00020: Maximum number of processes (number) exceeded

it may 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 an example of VAX/VMS: ORA-01034: Oracle not available ORA-07625: smsget: $MGBLSC failed %SYSTEM-W-NOSUCHSEC, (global) section does not exist

In this example, notice that the VMS operating system issues the message at the bottom of the stack. Viewing the messages at each level of the system can help you trace the source event. For example, in this case, Oracle may be unavailable simply because it has not started and therefore there is no System Global Area (SGA). If you need help from Oracle customer support, be sure to report all messages in the stack.

Using Messages 1-3

Call customer service

Call Customer Support Some messages recommend calling Oracle Customer Support to report a problem. When you call Oracle Customer Service, please have the following information available: ■

■

the hardware, operating system, and version number of the operating system on which Oracle is running the full version number of the Oracle server (for example, 8.0.2 or 7.1.3) any Oracle programs (with version numbers) in use when an error occurred. For example, SQL*Net V2.0 or SQL*Forms V3.0 if it encountered one or more error codes or messages, the exact code numbers and texts of the messages, in the order in which they occurred, the severity of the problem , based on the following codes: 1 = Program unusable. Critical impact on operations. 2 = Program usable. Operations severely restricted. 3 = Usable program with limited functions. It is not critical to general operations. 4 = Problem circumvented by the customer. Minimal effect, if any, on operations.

In addition, you are expected to give your ■

Name

■

company name

■

Company's Oracle Support ID number

■

phone number

Oracle Exception Messages Oracle's extensive self-test helps detect internal errors. Oracle uses the following general message for Oracle inner exceptions: ORA-00600: inner error code, arguments: [num], [], [], [], [], []

An actual message might appear as follows: ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[]

1-4

message error

trace files

Note that the message text is followed by up to six arguments, indicating the source and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and strings. Empty square brackets can be ignored. In addition to being returned to the user, internal errors are also written to the alert file along with additional information about the event that caused the message. The alert file also lists any trace files that may have been generated due to an internal error. See the following sections for descriptions of the trace and alert files. If you receive an ORA-00600 message, please report it to Oracle Customer Support.

Trace Files A trace file is created whenever an Oracle instance is started or an unexpected event occurs in a user process or background process. The trace file name includes the instance name, process name, and Oracle process number. The file type or extension is usually TRC and, if different, is noted in the operating system-specific Oracle documentation. The contents of the trace file can include dumps of the system global area, process global area, monitor stack, and logs. Two initialization parameters specify where the trace files are stored: ■

■

BACKGROUND_DUMP_DEST specifies the location of the trace files created by the Oracle PMON, DBWR, LGWR, and SMON background processes. USER_DUMP_DEST 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 the trace files generated when internal errors occur. See the next section for a description of the alert. 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 the Oracle documentation specific to your operating system. Oracle Customer Support may request a formatted trace file to help resolve a problem. For more information about trace files, see the Oracle8i Administrator's Guide.

Using messages 1-5

the alert file

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 and written to the alert. Oracle also writes additional information about internal errors to the alert file, such as the location and name of the trace files generated due to the error, etc. The alert file name is specific to the operating system. 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 the documentation specific to the Oracle operating system. If your system uses an operator console, some Oracle messages may appear on the console. All important messages are written to the alert file as well as to the operator console. Since non-Oracle messages also appear in this console, the alert file is a better log for tracking all Oracle administrative activities and errors than the console log. The alert file also logs information about administrative activities, such as online redo log file backup and archiving. For more information about the alert file, see the Oracle8i Administrator's Guide.

1-6

message error

Part II Oracle Server Messages This part contains the following chapters: ■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

■

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

2 ORA-00000 to ORA-00899 ORA-00000 normal, successful completion Cause: An operation completed normally, with no exceptions. Action: No action is required. Unique constraint ORA-00001 (string.string) violated Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you might see this message if a duplicate entry exists at a different level. Action: Remove the unique constraint or do not enter the key. ORA-00017 session requested to set trace event Cause: Another session requested the current session to set a trace event. 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 initialization parameter PROCESSES.

ORA-00000 to ORA-00899 2-1

Session ORA-00021 attached to some other process; cannot change session Cause: The user's session is being used by others. Action: Do not switch to a session attached to some other process. ORA-00022 Invalid session ID; access denied Cause: The specified session does not exist or the caller does not have privileges to access it. Action: Specify a valid session ID that you have access privileges to, whether you are the owner or have the CHANGE_USER privilege. ORA-00023 session references process private memory; cannot disconnect session Cause: An attempt was made to disconnect the current session when it contains references to process private memory. Action: A session can contain process memory references (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow separation, it may be necessary to close links and/or session database cursors. It is always prohibited to disconnect a session with operating system privileges. ORA-00024 Logins from multiple processes are not allowed in single-process mode Cause: Attempted to log in multiple times from different processes in Oracle started in single-process mode. Action: Log off the other process. ORA-00025 could not allocate string Cause: An application failed because Oracle ran out of memory. Action: Restart Oracle with a larger SGA heap. ORA-00026 Missing or invalid session ID Cause: The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid or no string was specified. User Response: Retry the command with a valid session ID. ORA-00027 Unable to kill current session Cause: An attempt was made to use ALTER SYSTEM KILL SESSION to kill the current session. Action: If you need to end the current session, do so from another session.

2-2

message error

ORA-00028 Your session has ended Cause: A privileged user has terminated the session and the session is no longer connected to the database. Action: Contact the database administrator. The administrator may be trying to perform an operation that requires users to log off. When the database administrator announces that the database is available, log in and resume work. Session ORA-00029 is not a user session Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session can be started recursively. User Response: Retry the command with a valid session ID. ORA-00030 The user session ID does not exist. Explanation: The user's session ID no longer exists, presumably because the session was disconnected. Action: Use a valid session ID. ORA-00031 session marked for deletion Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be terminated immediately because the session is involved in an ongoing operation (for example, rolling back a transaction or being blocked by a network operation) . The session is scheduled to end as soon as possible after the current operation completes. Action: No action is required for the session to end, but subsequent executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to end prematurely. ORA-00032 invalid session migration password Cause: The session migration password specified in a create session call was invalid (probably too long). Action: Try again with a valid password (less than 30 characters). ORA-00033 current session has empty migration password Cause: An attempt was made to disconnect 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-00000 to ORA-00899 2-3

ORA-00034 cannot be a string in the current PL/SQL session Cause: An attempt was made to commit or rollback a PL/SQL object (procedure, function, package) in a session that was disabled by the ALTER SESSION DISABLE COMMIT IN PROCEDURE statement. Action: Enable PL/SQL commits in this session, or try not to use PL/SQL commits or rollbacks when they are disabled in the current session. ORA-00035 LICENSE_MAX_USERS cannot be less than the current number of users Cause: The values specified for LICENSE_MAX_USERS are less than the current number of users. Action: Check the license limit and drop the additional users or buy more licenses. ORA-00036 Exceeded maximum number of recursive SQL levels (string) Cause: An attempt was made to exceed 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 on a different server group. This is not allowed. Action: Make sure the server switches to a session that belongs to your server group. ORA-00038 Cannot create session: pool owned by another user Cause: An attempt was made to create a non-migrable session on a pool owned by another user. Action: A pool is owned by the first user who logs on to a server in the pool in nonmigratory mode. All subsequent logins in non-migratory mode must be done by the user who owns the pool. To have a different user login in non-migratory mode, the ownership of the pool will need to be changed. This can be done by logging out of all current sessions and disconnecting from all existing servers in the pool, then having the new user log in to become the new owner. An ORA-00050 operating system error occurred while getting a queue. Cause: The operating system resources required to cover an Oracle enqueue could not be obtained. This is usually the result of a very low user share of the operating system.

2-4

message error

Action: Look for the operating system error in the system documentation and take the necessary action. ORA-00051 timed out while waiting for a resource. Cause: This message is usually caused by an instance that ended abnormally. Action: Reboot all unrecovered instances. ORA-00052 Maximum number of queued resources (string) exceeded Cause: Queue resource exhaustion. User Response: Increase the value of the ENQUEUE_RESOURCES initialization parameter. ORA-00053 maximum number of queues exceeded Cause: Exhaustion of queue status objects. User Response: Increase the value of the ENQUEUES initialization parameter. ORA-00054 resource busy and acquired with NOWAIT specified Cause: The NOWAIT keyword forced a return to the command prompt because a resource was not available for a LOCK TABLE or SELECT FOR UPDATE command. Action: Try the command after a few minutes, or enter the command without the NOWAIT keyword. ORA-00055 maximum number of DML locks exceeded Cause: Exhaustion of DML lock state objects. Action: Increase the value of the DML_LOCKS initialization parameter and restart Oracle. ORA-00056 DDL lock on object 'string.string' is already in incompatible mode Cause: The lock attempt is incompatible with the DDL lock already held on the object. This happens if you try to drop a table that has parse locks. Action: Before attempting to drop a table, verify that it does not have parse locks. Wait a few minutes before trying the operation again. ORA-00057 Maximum number of temp table locks exceeded Cause: The number of temp tables is equal to or greater than the number of temp table locks. Temporary tables are often created using large sorts.

ORA-00000 to ORA-00899 2-5

Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and restart Oracle. ORA-00058 DB_BLOCK_SIZE must be a string to mount this database (not a string) Cause: The value of the DB_BLOCK_SIZE initialization parameter used to start this database does not match the value used when this database was created. Possible reasons for this mismatch are: ■

mount wrong database

■

using the wrong initialization parameter file

■

The value of the DB_BLOCK_SIZE parameter has changed

Action: For one of the above reasons: ■

mount correct database

■

use the correct initialization parameter file

■

correct the value of the DB_BLOCK_SIZE parameter

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 restart Oracle. ORA-00060 deadlock detected while waiting for resource Cause: Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more instructions were rolled back to keep the other session running. Action: Either: ■

■

Enter a ROLLBACK statement and rerun all statements since the last commit, or wait until the lock is released, possibly several minutes, and then rerun the rolledback statements.

ORA-00061 Another instance has a different DML_LOCKS setting Cause: The starting shared instance uses DML locks and the running instances do not, or vice versa. Action: Either: ■

2-6

message error

Do not use DML_LOCKS by setting DML_LOCKS to zero in all cases or

■

Use DML_LOCKS by setting DML_LOCKS to a positive integer in all instances.

ORA-00062 Cannot acquire DML full table lock; DML_LOCKS is 0 Cause: The instance was started with the DML_LOCKS value set to zero, and the statement being executed requires a full table lock (S, X, or SSX). Action: Restart the instance with non-zero DML_LOCKS and rerun the statement. ORA-00063 maximum number of LOG_FILES exceeded Cause: The value of the initialization parameter LOG_FILES was exceeded. Action: Increase the value of the LOG_FILES initialization parameter and restart Oracle. The parameter value should be as large as the largest number of log files currently in existence, rather than just the existing log count. Object ORA-00064 is too large to allocate on this operating system (string,string) Cause: An initialization parameter was set to a value that required the allocation of more contiguous space than can be allocated on this operating system. Action: Reduce the value of the initialization parameter. FIXED_DATE Initialization ORA-00065 Failed Cause: The FIXED_DATE string was not in the date format yyyy-mm-dd:hh24:mi:ss. User Response: Make sure the initialization parameter has the correct date format. ORA-00066 LOG_FILES is a string, but must be a string to be supported. Cause: The maximum number of log files supported by this instance is not the same as the other instances. All instances must be able to open all files that any instance can open. Action: Change the value of the LOG_FILES initialization parameter to make it compatible. ORA-00067 invalid string value for parameter string; must be at least a string Cause: The initialization parameter value is invalid. Action: Choose a value as indicated by the message.

ORA-00000 to ORA-00899 2-7

ORA-00068 Invalid value string for parameter string, must be between string and string Cause: The initialization parameter value is invalid. Action: Choose a value as indicated by the message. ORA-00069 cannot acquire lock: table locks are disabled for chain 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 try the command again. ORA-00070 script is invalid Cause: An invalid debug command was specified. Action: Type HELP to see the list of available commands. Process number ORA-00071 must be between 1 and a string. Cause: An invalid process number was specified. Action: Specify a valid case number. ORA-00072 Process "chain" is not active Cause: An invalid process was specified. Action: Specify a valid process. ORA-00073 command string occupies between string and string argument(s) Cause: Incorrect number of arguments specified. Action: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax. ORA-00074 no process specified Cause: No debug process was specified. Action: Specify a valid process. ORA-00075 process "string" not found in this instance Cause: The specified process was not attached to the current instance. Action: Specify a valid process.

2-8

message error

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 invalid 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 String variable not found Cause: An attempt was made to dump a variable that does not exist. User Response : 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 PGA, 2 for SGA, and 3 for UGA. Use the extra + level to dump the global area level, as well as the extra bytes for each pointer; extra must be a multiple of 4. Address range ORA-00081 [string, string) cannot be read Cause: An attempt was made to read/write an invalid memory address range. Action: Try another address or length. ORA-00082 String memory length is not in the valid set of [1], [2], [4] string string string string string Cause: An invalid length was specified for the POKE command. Action: Use a valid length (1, 2, 4, or possibly 8). Warning ORA-00083: SGA possibly corrupt assigned Cause: Although there may be corruption in SGA, the SGA has been assigned. 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.

ORA-00000 to ORA-00899 2-9

Action: Specify PGA, SGA, or UGA. ORA-00085 current call does not exist Cause: An invalid attempt was made to evict the current call heap. Action: Wait for the process to initiate a call. User call ORA-00086 does not exist Cause: An invalid attempt was made to dump the user call heap. Action: Wait for the process to initiate a call. ORA-00087 command cannot be executed on the remote instance Cause: An OPS command was issued for a non-OPS ORADEBUG command. Action: Issue the command without the OPS syntax. MTS server cannot execute command ORA-00088 Cause: A debug command was issued on an MTS 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 an OPS ORADEBUG command. Action: Reissue the command with valid instance numbers. ORA-00090 Could not allocate memory for OPS ORADEBUG command Cause: Could not allocate the memory needed to run ORADEBUG in parallel. Action: Reissue the command on each instance with single-instance ORADEBUG. ORA-00091 LARGE_POOL_SIZE must be at least a string Cause: The value of LARGE_POOL_SIZE is below the minimum size. Action: Increase the value of LARGE_POOL_SIZE beyond 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 above the value of LARGE_POOL_MIN_ALLOC.

2-10

message error

ORA-00093 string must be between string and string Cause: The parameter value is not in a valid range. User Response : Modify the parameter value to be within the specified range. The ORA-00094 string requires an integer value. Cause: The parameter value is not an integer. User Response : Modify the parameter value to an integer. ORA-00096 Invalid value string for parameter string, must be enclosed in strings Cause: The initialization parameter value is invalid. Action: Choose a value as indicated by the message. ORA-00097 Oracle SQL feature usage is not at the SQL92 string level Cause: An attempt was made to use an Oracle SQL feature that is not compliant with the SQL92 standard. Action: Do not use the ALTER SESSION SET FLAGGER command or feature to set the appropriate level of SQL92 compliance. ORA-00099 Resource timed out, possible PDML deadlock Cause: The resource required for the transaction was busy. The PDML transaction was unable to acquire the resource within the specified time period. This indicates a potential deadlock involving this PDML transaction and other transactions currently running on the system. Action: Increase the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then repeat the operation. ORA-00100 No data found Cause: An application was referencing unknown or inaccessible data. Action: Handle this condition in the application or make appropriate modifications to the application code. ORA-00101 Invalid specification for MTS_DISPATCHERS system parameter Cause: The syntax of the MTS_DISPATCHERS parameter is incorrect. Action: Enter the MTS_DISPATCHERS parameter in the startup parameters file with the correct syntax, then shut down and restart the instance.

ORA-00000 to ORA-00899

2-11

Dispatchers cannot use network protocol chain ORA-00102 Cause: The network specified in MTS_DISPATCHERS does not have the functionality required by dispatchers. Action: Consult the specific Oracle operating system documentation for the network protocols supported by dispatchers. ORA-00103 invalid network protocol; Reserved for dispatcher use Cause: The network specified in the Net8 connection string is reserved for dispatcher use. Action: Specify other network protocols in the connection string. ORA-00104 block detected; all public servers blocked waiting for resources Cause: All available public servers are servicing requests that require resources that are blocked by a client that cannot obtain a public server to release the resources. Action: Increase the limit for the MTS_MAX_SERVERS system parameter as the system will automatically start new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_SERVERS. ORA-00105 The dispatch engine is not configured for the network protocol chain Cause: An attempt was made to change the dispatcher configuration for a network protocol that was not specified in the INIT.ORA file. Action: Do one of the following: ■

■

Add the network protocol to the definition of the MTS_DISPATCHERS initialization parameter and reboot the system. Use the ALTER SYSTEM SET MTS_DISPATCHERS command with a network protocol that exists in the initialization parameter file.

ORA-00106 Unable to start/shutdown database when connected to a dispatcher Cause: An attempt was made to start or stop an instance while connected to a shared server through a dispatcher. Action: Reconnect as an INTERNAL user without going through the dispatcher. In most cases, this can be done by connecting to INTERNAL without specifying a network connection string. ORA-00107 Could not connect to ORACLE listener Cause: Probably because the network listener process was not started. Action: Check the following:

2-12

message error

■

The network configuration file is not configured correctly.

■

The client-side address was not specified correctly.

■

The listener initialization parameter file is not configured correctly.

ORA-00108 could not configure the dispatcher to accept the connection asynchronously Cause: The network protocol used by the dispatcher does not support asynchronous operations. Action: Contact Oracle Customer Support. ORA-00111 No servers started because the number of servers is limited to a string Cause: An attempt was made to start more servers than the maximum number specified by the MTS_MAX_SERVERS system parameter. Action: Increase the value of the MTS_MAX_SERVERS initialization parameter as needed or reissue the ALTER SYSTEM SET MTS_SERVERS command with an appropriate number of servers. ORA-00112 created only up to chain (maximum specified) dispatchers Cause: An attempt was made to start more dispatchers than the maximum number specified by the MTS_MAX_DISPATCHERS system parameter. Action: Increase the value of the initialization parameter MTS_MAX_DISPATCHERS as needed. ORA-00113 protocol name string too long Cause: A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long. Action: Use a valid protocol name for the MTS_DISPATCHERS value. ORA-00114 Missing value for MTS_SERVICE system parameter Cause: No value was specified for either the MTS_SERVICE initialization parameter or the DB_NAME parameter. User Response : Add an MTS_SERVICE or DB_NAME definition to the initialization file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE is explicitly specified. ORA-00115 connection refused; dispatcher connection table is full Cause: A dispatcher rejected a connection request because it cannot support more connections. Action: Connect to a different dispatcher or use a dedicated server.

ORA-00000 to ORA-00899

2-13

ORA-00116 MTS_SERVICE name is too long Cause: The service name specified in the initialization parameter of MTS_SERVICE is too long. Action: Use a shorter name for the MTS_SERVICE value (less than or equal to 255 characters). ORA-00117 value out of range for MTS_SERVERS system parameter Cause: The value specified for the MTS_SERVERS parameter is incorrect. Action: MTS_SERVERS must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_SERVERS. ORA-00118 value out of range for MTS_DISPATCHERS system parameter Cause: The value of the MTS_DISPATCHERS parameter is incorrect. Action: The sum of all MTS_DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_DISPATCHERS. ORA-00119 Invalid specification for MTS_LISTENER_ADDRESS system parameter Cause: The syntax of the MTS_LISTENER_ADDRESS parameter is incorrect. Action: Consult the Oracle8i reference manual for the correct syntax. ORA-00120 Dispatch engine not enabled or installed Cause: The dispatch engine was not enabled or the Oracle executable image was not installed with the dispatch engine. Action: See the Oracle8i Administrator's Guide and your operating system-specific documentation for procedures to start and configure the dispatcher process. ORA-00121 MTS_SERVERS specified without MTS_DISPATCHERS Cause: A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition was specified for MTS_DISPATCHERS. Without a value for MTS_DISPATCHERS, shared servers will never be used. Action: Add a definition for MTS_DISPATCHERS in the INIT.ORA file (or remove the definition for MTS_SERVERS if MTS is not being used). ORA-00122 Failed to initialize network configuration Cause: Oracle was unable to initialize Net8. Action: View the attached messages.

2-14

message error

ORA-00123 public server down Cause: Too many down servers were waiting in the common queue. Action: This error is used internally, no action is required. ORA-00124 MTS_DISPATCHERS specified without MTS_MAX_SERVERS Cause: A definition for MTS_DISPATCHERS was specified in the INIT.ORA file, but MTS_MAX_SERVERS was specified as zero. Action: Specify MTS_MAX_SERVERS to be greater than zero. ORA-00125 connection refused; invalid presentation Cause: The PRESENTATION in CONNECT_DATA of the DESCRIPTION of the TNS address is not correct or not supported. Action: Correct the PRESENTATION specified in the TNS address. ORA-00126 connection refused; Invalid Duplicate Cause: The DUPLICITY in CONNECT_DATA of the TNS Address DESCRIPTION is not correct or not supported. Action: Correct the DUPLICITY specified in the TNS address. ORA-00127 Dispatcher chain does not exist Cause: There is currently no dispatcher running with the specified name. Action: Try again with a name in the format "D###" indicating an existing dispatcher process. ORA-00128 This command requires a dispatcher name Cause: Incorrect syntax for ALTER SYSTEM SHUTDOWN. Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [IMMEDIATE] 'dispatcher name'

ORA-00150 Duplicate transaction ID Cause: An attempt was made 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 match an existing valid transaction.

ORA-00000 to ORA-00899

2-15

Action: Check your application. ORA-00152 current session does not match requested session Cause: The current session is not the same as the one passed to a UPIXADO() call. Action: Check your application. Internal error ORA-00153 in XA library Cause: The XA library could not access thread-specific pointers. Action: Contact Oracle Customer Support. Transaction monitor protocol error ORA-00154 Cause: The transaction monitor returned TMJOIN on an AX_REG call, but the transaction was suspended locally. Action: Contact transaction monitor customer support. ORA-00155 cannot perform work outside of global transaction Cause: The application attempted to perform some work on an Oracle 7.3 server outside of a global transaction. Action: Verify that the application is connected to an Oracle 7.3 server. The transaction monitor should not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. ORA-00160 Global transaction length string is greater than maximum (string) Cause: An external global transaction ID was passed with a length field that was too long. Action: Report the problem to your third-party transaction coordinator provider. ORA-00161 Transaction branch length string is invalid (maximum string allowed) Cause: An external transaction branch ID was passed with a length that is too long or 0. Action: Report the problem to your external transaction coordinator provider . ORA-00162 External dbid length string is greater than maximum (string) Cause: An external database name was passed with too long a field length. Action: Report the problem to your third-party transaction coordinator provider.

2-16

message error

ORA-00163 Internal database name length string is greater than maximum (string) Cause: An internal database name was passed with too long a field length. Action: Report the problem to your third-party transaction coordinator provider. Cannot create control file ORA-00200 Cause: Cannot create control file. Action: Verify that there is enough disk space and that there are no file name conflicts 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: Reboot with a compatible software version or use CREATE CONTROL FILE to create a new control file that is compatible with this version. ORA-00202 control file: 'string' Cause: This message reports the file name involved in other messages. Action: Check the associated error messages for a description of the problem. ORA-00203 Using 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. An instance is likely to use a backup control file. Action: Verify that the correct control files have been specified. ORA-00204 error reading (block string, # block string) from control file Cause: A disk I/O failure was detected while reading the control file. Action: Check if the disk is online. If not, bring it online, shutdown and restart Oracle. If you are online, look for the operating system reasons why Oracle cannot read the disk or control file. See the Oracle8i Administrator's Guide for information on recovering a lost control file. Also refer to the Oracle documentation specific to your operating system. ORA-00205 error identifying control file, see alert log for more information Cause: The system could not find a control file with the specified name and size. Action: One of the following:

ORA-00000 to ORA-00899

2-17

■

Verify that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again. When using duplicate control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name from the initialization parameter file message and restart the instance . If the message does not appear again, remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file.

Error ORA-00206 writing (block string, # block string) to control file Cause: A disk I/O failure was detected while writing to the control file. Action: Check if the disk is online. If not, bring it online, shutdown and restart Oracle. If you are online, look for the operating system reasons why Oracle cannot write to disk or to the control file. See the Oracle8i Administrator's Guide for information on recovering a lost control file. Also refer to the Oracle documentation specific to your operating system. The control files ORA-00207 are not for the same data bank Cause: The data bank ID in the control file is not the same as the data bank ID in the control file used in the first instance to assemble this bank of dice. Probably one of the assemblies used the wrong control file or there are two databases with the same name. Action: Verify that the control file is for the correct database and is not an older version. When multiplexed control files are used, that is, more than one control file is referenced in the initialization parameter file, remove the control file name that appears in the initialization parameter file message and restart the instance. If the message does not appear again, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file. ORA-00208 The number of control file names exceeds the string limit 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 unused files. ORA-00209 Control file block size mismatch; check the alert log for more information. Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

2-18

message error

Action: Reduce the block size to the value specified in the message and try again. ORA-00210 cannot open specified control file Cause: Cannot open control file. Action: Verify that 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 belonging to another database was specified. Action: Find and install the correct control file. ORA-00212 string block size below minimum required string byte size Cause: The specified block size was too small. Space is needed for system overhead. Action: Specify a larger block size and retry the operation. ORA-00213 cannot reuse control file; old file size string, required string Cause: To reuse a control file, it must be the same size as the one used previously. Action: Do not specify REUSE or specify a matching combination of the MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement. ORA-00214 control file version string 'string' inconsistent with file version string 'string' Cause: An inconsistent set of control files, data files, and redo log files were used. Action: Use a consistent set of control files, data files, and redo log files. That is, all files must be from the same database and from the same period. ORA-00215 must be at least one control file Cause: No control file specified or the specified control file does not exist. Action: Specify at least one valid control file and retry the operation.

ORA-00000 to ORA-00899

2-19

Could not resize control file ORA-00216 for migration from 8.0.2 Cause: Some records were missing from the control files created by version 8.0.2. These logs are automatically added when resizing the control file when trying to run a later version. Failed resize. Action: Look in the alert log for why the resize failed. If it can be fixed by giving the control file more space, do so. Otherwise, use the CREATE CONTROLFILE script dumped in the trace file to create a new control file. ORA-00218 Control file block size string does not match DB_BLOCK_SIZE (string) Cause: The block size stored in the control file header is different from the value of the DB_BLOCK_SIZE initialization parameter. This could be due to an incorrect DB_BLOCK_SIZE setting, or it could indicate that the control file has become corrupted or belongs to a different database. Action: Restore a good copy of the control file. ORA-00219 Required control file size string exceeds maximum allowed length string Action: For CREATE DATABASE or CREATE CONTROLFILE, use a different combination of the MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts. ORA-00220 control file not mounted for first instance, see alert log for more information. Cause: The specified control file has a different mount ID than the other control files 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 writing to control file Cause: An error occurred while writing to one or more control files. Action: View the attached messages.

2-20

message error

The ORA-00222 operation would reuse the name of a currently mounted control file. Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the currently specified mounted control file name. User Response : Repeat the operation with a different file name. The ORA-00223 conversion file is invalid or has the wrong version. Cause: An Oracle7 to Oracle8 conversion file contains invalid data or was created with a different version of the migration utility. This error can also be caused by the incorrect ORACLE_HOME environment variable when the ALTER DATABASE CONVERT command is issued. Action: Use a correct version of the converted file or rebuild 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 set correctly. ORA-00224 Attempted to resize control file with illegal record type (string) Cause: An attempt was made to expand or collapse the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. User Response : 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 Control file expected size string differs from actual size string Cause: The expected size of the control file stored in its header was different from the operating system actual file size. This usually indicates that the control file has become corrupted. Action: Restore a good copy of the control file. ORA-00226 Operation not allowed while alternate control file open Cause: The attempted operation could not be performed at this time because this process had an alternate control file open for fixed table access. User Response : Repeat the operation after calling cfileUseCurrent. ORA-00227 Block corruption detected in control file: (blockstring, #blockstring) Cause: A checksum error or block header corruption was detected while reading the control file. Action: Use the CREATE CONTROL FILE or RECOVER DATABASE USING BACKUP CONTROL FILE command.

ORA-00000 to ORA-00899

2-21

ORA-00228 Control file alternate name length exceeds maximum string Cause: The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system. User Response : Repeat the operation with a shorter file name. ORA-00229 operation not allowed: already holding queued snapshot control file Cause: The attempted operation cannot be performed at this time because this process currently holds the queued snapshot control file. User Response : Repeat the operation after calling cfileUseCurrent to release the snapshot control file queue. ORA-00230 operation not allowed: snapshot control file queue not available Cause: The attempted operation cannot be performed at this time because another process currently has the snapshot control file queue. User Response: Retry the operation after the concurrent operation that maintains the snapshot control file enqueue completes. Snapshot control file not named ORA-00231 Cause: During a call to cfileMakeAndUseSnapshot or cfileUseSnapshot, it was detected that no file name was previously specified for the snapshot control file. User Response : Specify a name for the snapshot control file by calling cfileSetSnapshotName. ORA-00232 Snapshot control file is missing, corrupted, or unreadable Cause: The snapshot control file was found to be missing, corrupted, or unreadable during a call to cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time). ORA-00233 The copy control file is corrupted or unreadable Cause: The specified copy control file was found to be corrupted or unreadable during a call to cfileUseCopy. Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy.

2-22

message error

ORA-00234 error identifying or opening a snapshot or copy control file Cause: A snapshot or copy control file with the name specified during a call to cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy could not be found or opened. Action: Recreate the snapshot or copy the control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively. ORA-00235 Fixed inconsistent control file table due to concurrent update Cause: Concurrent update activity on a control file caused a query against a fixed table in the control file to read inconsistent information. Action: Repeat the operation. ORA-00236 snapshot operation not allowed: mounted control file is a backup Cause: An attempt was made to call 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 not allowed: newly created control file Cause: An attempt was made to call cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE. 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 given as a parameter to the ALTER DATABASE BACKUP CONTROLFILE or cfileSetSnapshotName command matches the name of a file that is currently part of the database data. User Response : Repeat the operation with a different file name. ORA-00250 Archiver did not start Cause: An attempt was made to stop automatic archiving, but the archiver process was not running. Action: No action is required.

ORA-00000 to ORA-00899

2-23

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 destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command. Action: Specify a different destination for the LOG_ARCHIVE_DUPLEX_DEST parameter, or specify a different destination with the ALTER SYSTEM command. ORA-00252 Thread sequence log chain is empty, cannot be archived Cause: A log must be used for regeneration before it can be archived. The specified redo record has not been used since it was entered into the database. However, it is possible that the instance died during a registry change and the registry is empty. Action: Empty records do not need to be archived. Do not attempt to archive the redo log file. ORA-00253 limit string exceeded by archive destination 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 less than the limit specified in the error message. ORA-00254 error in archive control string 'string' Cause: The log file location specified is invalid in the archive command or in the LOG_ARCHIVE_DEST initialization parameter. Action: Check the file string used to make sure it refers to a valid online device. ORA-00255 error archiving thread log string string, sequence # string Cause: An error occurred during archiving. Action: Check the stack of attached messages for more detailed information. If the online log is corrupted, the log can be purged with the NOT ARCHIVED option. This will make existing backups useless for recovery any time after the log is created, but will allow the database to generate redos.

2-24

message error

ORA-00256 cannot translate destination string from archive string Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated. Action: Check the stack of attached messages for more detailed information. Then repeat the ALTER SYSTEM command using a different string. Archiver error ORA-00257. Connect internal only, until it comes loose. Cause: The archiver process received an error while attempting 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 that the target device does not have space to store the redo log file. Action: Check the archiver trace file for a detailed description of the problem. Also, verify that the device specified in the ARCHIVE_LOG_DEST initialization parameter is correctly configured for archiving. ORA-00258 Manual archiving in NOARCHIVELOG mode should identify record Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not explicitly specify the record by sequence number, group number, or file name. Action: Specify the record by file name, by group number, or by thread and sequence number. ORA-00259 open thread string string log string is current record, cannot archive Cause: An attempt was made to archive the current record of an open thread. This is not allowed because the redo log file might still be in use to generate redo entries. Action: Force a registry change on the instance where the thread is open. If there are no open instances, open the database so that instance recovery can recover the thread. ORA-00260 Cannot find online log stream sequence for thread stream Cause: The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations: ■

The record may have been reused for another sequence number.

■

The record may have been discarded.

■

The sequence number can be greater than the current record sequence number.

ORA-00000 to ORA-00899

2-25

■

The thread may not have any records.

User Response : Check the ARCHIVE statement and specify a valid record sequence number. Specify a valid log sequence number. ORA-00261 Thread Sequence The registry sequence is being archived or modified Cause: The registry is being archived by another process or is being modified by an administrative command. Operations that modify the record include delete, add a member, drop a member, rename a member, and drop the record. Action: Wait for the current operation to complete and try again. ORA-00262 Cannot change current log stream from closed threads stream Cause: The log cannot be manually cleaned or archived because it is the current log of a closed thread and it is not possible to change the logs to another log so that be the current record. Current. All other logs for the thread must be archived or purged and cannot be reused. Action: Archive another record to the same segment first, or complete the cleanup. Please refer to the attached errors for the reason why the exchange cannot be completed. ORA-00263 There are no records to be archived for the thread chain Cause: An attempt was made to manually archive unarchived records on this thread, but no records needed to be archived. Action: No action is required. ORA-00264 no recovery required Cause: An attempt was made to perform a media recovery on files that do not require recovery of any kind. Action: Do not attempt to perform media recovery on the selected files. Make sure the file names have been entered correctly. Otherwise, try the command again with the appropriate file names. ORA-00265 instance recovery required, cannot set ARCHIVELOG mode Cause: The database was locked or terminated with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current data files. Action: Open the database and enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.

2-26

message error

ORA-00266 Archived log file name required 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 prompted. ORA-00267 Archived log file name not required Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested. Action: Continue with media recovery, but do not enter a new log name. ORA-00268 The specified log file does not exist 'string' Cause: The provided redo log file does not exist. Action : Check the spelling and case of the file name and try the command again. ORA-00269 The specified log file is part of the given thread and is not part of the given thread Cause: The given redo log file is not part of the given thread. Action: Verify that the thread in the redo log file matches the thread on the command line. Otherwise, use a redo log file for the appropriate thread. Retry the command after correcting the error. ORA-00270 error creating file record string Cause: An error was encountered while creating or opening the target file for archiving. Action: Verify that the destination of the file is valid and that there is enough space on the destination device. ORA-00271 no logs to archive Cause: An attempt was made to manually archive the unarchived redo log files, but there are no files to archive. Action: No action is required. ORA-00272 error writing log file string Cause: An I/O error occurred while archiving a redo log file. Action: Verify that the output device is still available and correct any device errors that may have occurred. Also, make sure there is enough space to archive on the output device.

ORA-00000 to ORA-00899

2-27

ORA-00273 media retrieval of direct load data not being logged Cause: A media retrieval 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 corrupted. Action: The table should be dropped or truncated so that the bad blocks can be reused. If a more recent backup of the file is available, try to recover it to eliminate this error. ORA-00274 invalid recovery option string Cause: An invalid option was specified for a recovery command. Action: Correct the syntax and try the command again. ORA-00275 Media recovery has already 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 The CHANGE keyword was specified but the change number was not provided Cause: The CHANGE keyword was specified on the command line but the change number was not provided. Action: Retry the command using a valid change number after the CHANGE keyword. ORA-00277 invalid option for UNTIL recovery indicator string Cause: Only CANCEL, CHANGE, and TIME can be used with the UNTIL keyword. Action: Correct the syntax. ORA-00278 The log file 'chain' is no longer needed for this recovery Cause: The specified redo log file is no longer needed for the current recovery. Action: No action is required. The archived redo log file can be deleted from its current location to save disk space, if necessary. However, the redo log file might still be needed for another recovery session in the future. ORA-00279 change string generated to string required for thread string Cause: The requested record is required to continue with the recovery.

2-28

message error

Action: Provide the requested log with the file name ALTER DATABASE RECOVER LOGFILE or cancel the recovery with ALTER DATABASE RECOVER CANCEL. ORA-00280 change string to thread string is in sequence #string Cause: This message helps to find the redo log file with the specified change number requested by other messages. Action: Use the information provided in this message to specify the archived redo log files needed for other errors. ORA-00281 Media recovery cannot be performed by dispatcher Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements do not allow this recovery method. Action: Connect to the instance through a dedicated server process to perform media recovery. ORA-00282 Unsupported UPI string call, 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 aborted due to errors Cause: An error during recovery was considered serious enough to terminate the current recovery session. Action: More specific messages will follow this message. See the other messages for the appropriate action. ORA-00284 Recovery session still in progress Cause: An error during recovery was considered small enough to allow the current recovery session to continue. Action: More specific messages will follow this message. See the other messages for the appropriate action. ORA-00285 TIME not provided as constant string Cause: UNTIL TIME was not followed by a constant string for time. Action: Enter the time in single quotes.

ORA-00000 to ORA-00899

2-29

ORA-00286 No members available or no members contain 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, try to make them available. Make sure that the correct file names are used, especially if the redo log file is being accessed from a remote location. ORA-00287 Specified change number string not found in thread chain Cause: The given change number does not appear in any of the online redo logs for the given thread. Action: Check the statement to ensure a valid change number is provided. Maybe try using the NEXT option to archive logs. ORA-00288 To continue recovery, type ALTER DATABASE RECOVER CONTINUE Cause: During recovery from media, re-login is not required, but the resume command is required to take a checkpoint and report errors. Action: Type ALTER DATABASE RECOVER CONTINUE and the recovery will resume. Suggestion ORA-00289: string Cause: This message reports the name of the next required redo log file, 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 file name for the next log required for recovery. An ORA-00290 operating system file error has 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 reported in the messages and retry the operation. See also the Oracle documentation specific to the operating system. Numeric value ORA-00291 is required for the PARALLEL option Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument specifying the degree of parallelism.

2-30

message error

Action: Rewrite the command with a numeric argument that specifies the desired degree of parallelism. ORA-00292 Parallel recovery feature not installed Cause: A parallel recovery was requested when the parallel recovery option is not installed. Action: Remove the PARALLEL clause from the RETRIEVE command. Also, remove the RECOVERY_PARALLELISM parameter in the initialization file. ORA-00293 control file is out of sync with redo log Cause: The redo log file and control file are out of sync because a non-current control file was specified when the instance 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 archive log format specifier 'string' Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters allowed for the string are s, S, t, and T. Action: Correct the initialization file and restart the instance. ORA-00295 Invalid data file number string, must be between 1 and string Cause: Invalid file number specified. Action: Specify a correct data file number and retry the operation. ORA-00296 The maximum number of files (string) to RETRIEVE LIST OF DATA FILES was exceeded Cause: The RETRIEVE LIST OF DATA FILES command specified more data files than allowed by the DB_FILES initialization parameter. This error occurs when recovering with Recovery Manager and the instance was started with a DB_FILES parameter that specifies fewer data files than Recovery Manager needs to recover to satisfy the user's RECOVER command. User Response: Restart 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 command was issued. This only happens when recovering with Recovery Manager and is an internal error in

ORA-00000 to ORA-00899

2-31

Recovery Manager, because Recovery Manager should always issue RECOVER DATA FILE LIST before RECOVER DATA FILE START. Action: Contact Oracle Customer Support. ORA-00298 Missing or invalid TIMEOUT interval Cause: A non-zero integer timeout interval (in minutes) must be specified after the TIMEOUT keyword. Action: Correct the syntax and try the command again. ORA-00300 Illegal redo log block size string specified: exceeds string limit Cause: The specified redo log block size is larger than the maximum block size for the operating system. Action: Create the redo log on a device with a smaller block size. Error ORA-00301 adding log file 'string': Unable to create file Cause: Failed to create redo log file Action: Verify that: 1.

There is enough storage space on the device

The file name is valid.

The device is online

An I/O error has occurred

Also, REUSE may have been specified on the command line and there may be a file of the wrong size. Do not specify REUSE or use a file of the correct size. ORA-00302 chain log limit exceeded Cause: The maximum number of redo log files was exceeded. There is a limit, set at database creation, to the number of redo log files (typically 16). Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES. ORA-00304 requested INSTANCE_NUMBER is busy Cause: An instance attempted to start using an INSTANCE_NUMBER initialization parameter value that is already in use. Action: Either: ■

2-32

message error

Specify another INSTANCE_NUMBER,

■

Terminate the running instance with this number or

■

Wait for the instance recovery to complete on the instance with that number.

ORA-00305 Inconsistent thread string log string; belongs to another database Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database. User Response : Specify the correct redo log file and retry the operation. ORA-00306 string instance limit in this database Cause: Launching this instance would exceed the maximum number of instances allowed for this database. This message only appears with shared HOME and multiple instances. Action: Cannot start more than the lesser of: ■

■

the operating system-specific maximum or the number of instances specified by the MAXINSTANCES option specified in the CREATE DATABASE statement

ORA-00307 requested INSTANCE_NUMBER out of range, maximum is a string Cause: The INSTANCE_NUMBER initialization parameter specified a number that was out of range. User Response : Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1, and the maximum value is the lesser of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also the Oracle documentation specific to the operating system. ORA-00308 cannot open archive log 'string' Cause: The system cannot access a required archive redo log file. Action: Verify that the offline log exists, that the storage device is online, and that the archive file is in the correct location. Then try to continue with the recovery or restart the recovery session. ORA-00309 Log belongs to wrong database Cause: The archived redo log cannot be accessed by the system because it belongs to another database. User Response : Specify the correct redo log file and retry the operation.

ORA-00000 to ORA-00899

2-33

Archived record ORA-00310 contains a sequence string; sequence string required Cause: The archived log is out of sequence, possibly because it is corrupted or because an incorrect redo log file name was specified during recovery. User Response : Specify the correct redo log file and retry the operation. ORA-00311 cannot read archived log header Cause: An I/O error occurred while trying to read the log file header of the specified archived redo log file. Action: Other messages will follow this message. See the associated messages for the appropriate action to take. ORA-00312 online logging thread string: 'string' Cause: This message reports the file name for details in another message. Action: Other messages will follow this message. See the associated messages for the appropriate action to take. ORA-00313 Failed to open for thread chain log group chain members Cause: Unable to open online log. The file may not be in the expected location. Action: Specify the correct redo log file or make the log available if needed. Also, check out the attached messages. ORA-00314 thread string log string, expected string # string does not match string Cause: The online log is corrupted or an old version. Action: Find and install the correct version of the registry or reset the registry. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00315 thread string log string, bad thread # string in header Cause: The online log is corrupted or an old version. Action: Find and install the correct version of the registry or reset the registry. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00316 thread string log string, write string in header is not a log file Cause: The online log is corrupt or an old version. Action: Find and install the correct version of the registry or reset the registry. See the Oracle8i Administrator's Guide for recovery procedures.

2-34

message error

ORA-00317 The file type string in the header is not a log file Cause: This is not an archived log file. Action: Find the correct file and try again. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00318 thread string log string, expected file size string does not match string Cause: The file size indicated in the control file does not match the file size contained in the log file. Action: Restore the correct file or reset the logs. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00319 Thread stream registry chain has incorrect registry reset state Cause: An online redo registry has different registry reset data than the registry reset data in the control file. The registry is probably an incorrectly restored backup. Action: Restore the correct file or reset the logs. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00320 Unable to read thread chain log file header Cause: The file is not available. Action: Restore the log file. ORA-00321 thread string log string, cannot update log file header Cause: Unable to write to the log file. Action: Restore access to the file. ORA-00322 Thread stream log stream is not current copy Cause: An online log appears to be an incorrectly restored backup. Action: Restore the correct file or reset the logs. See the Oracle8i Administrator's Guide for recovery procedures. ORA-00323 The current thread sequence log cannot be used and all others must be archived Cause: An attempt to open the thread failed because redo generation needs to be switched to another online log, but all other logs must be archived before you can make it be used. User Response : Archive the thread logs and try opening them again.

ORA-00000 to ORA-00899

2-35

ORA-00324 log file 'string' translated name 'string' too long, string characters exceed string limit Cause: The translated name for a log file is too long. Action: Choose an untranslated name that produces a shorter translated name. ORA-00325 archived log for thread thread, thread # bad string in header Cause: The archived log is corrupted or is for another thread. It is not possible to use the registry to apply redo. Action: Find the correct archived log. ORA-00326 Log starts at change string, need to change string first Cause: The archived log provided for recovery was generated after the required log. It is not yet possible to use the registry to apply redo. Action: Find the correct archived log. ORA-00327 thread string log string, physical length string smaller than required string Cause: A log file has decreased in size. This is likely due to computer operator error or an operating system error. Action: Restore the log file from the backup. If no backup is available, drop this log and recreate it. If the database was shut down successfully, no further action is required; otherwise, an incomplete recovery may be required. ORA-00328 archived log ends in a change string, you need to change the string later Cause: The archived log provided for recovery was generated before the required log. It is not possible to use the registry to apply redo. Action: Find the correct archived log. ORA-00329 Archived record starts at change string, need to change string Cause: Archived record is not the correct record. Prior registration is required. Action: Restore the correct log file. ORA-00330 archived record ends in change string, change string required Cause: The archived record is not the correct record. Subsequent registration is required. Action: Restore the correct log file. ORA-00331 registry version string incompatible with ORACLE version string Cause: The registry was written by an incompatible version of Oracle.

2-36

message error

Action: Recover the database with the supported software, gracefully shut down and restart Oracle with the current software. Archived record ORA-00332 is too small; it may have been archived incompletely. Cause: The log is smaller than the space allocated on it. It could be the result of a SHUTDOWN ABORT while being written by the archiver. Action: Get a full version of this log and use it for recovery. There must be an online version or a copy that has been successfully archived. ORA-00333 block chain count chain redo log read error Cause: An I/O error occurred while reading the log described in the attached error. Action: Restore accessibility to the file or obtain another copy of the file. Record Archived ORA-00334: 'string' Cause: This message reports the name of the file involved with other errors. Action: Review the associated error messages. ORA-00335 online record string: No record with this number, record does not exist Cause: This message reports the name of the file involved with other errors. Action: Review the associated error messages. ORA-00336 Log file size string blocks are less than string block minimum Cause: The log file size, as specified in the CREATE DATABASE statement, is too small. Action: Increase the size of the log file. ORA-00337 Log file 'string' does not exist and no size was specified Cause: An attempt to add a log could not find an existing file or a size to create the file. User Response : Specify a size for the log file. ORA-00338 Thread stream log sequence is newer than control file Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can stop it from occurring without correcting the actual problem. Each attempt to open the database will advance the control file change sequence number until it is large enough.

ORA-00000 to ORA-00899

2-37

Action: Use the current control file or backup control file recovery to update the control file. Be sure to follow all restrictions when performing a backup control file recovery. Archived log ORA-00339 does not contain redo Cause: The archived log is not the correct log. It is a copy of a log file that was never used for redo generation, or an online log was being prepared to be the current log. Action: Restore the correct log file. ORA-00340 I/O error processing thread string online log string Cause: An I/O error occurred in the mentioned online log. Action: Restore accessibility to the file or restore the file from backup. ORA-00341 log string for thread string, # wrong log string in header Cause: Internal information in an online log file does not match the control file. Action: Restore the correct file or reset the logs. See the Oracle8i Administrator's Guide for recovery procedures. Archived log ORA-00342 was created before the last RESETLOGS Cause: Recovery received a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then containing the correct redo. User Response : Provide the correct log file. ORA-00343 too many errors, log member closed Cause: The maximum number of errors on this log member has been exceeded. Action: Correct the underlying problem by referring to the other error messages encountered with this one. ORA-00344 could not recreate online log 'string' Cause: An I/O failure occurred while trying to recreate an online log as part of an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. Action: Correct the file/device as indicated by the associated errors. ORA-00345 redo log write error string count string Cause: An I/O error occurred while writing the log.

2-38

message error

Action: Correct the cause of the error and restart the system. If the record is lost, apply media/incomplete recovery. ORA-00346 log member marked EMPTY Cause: A log file member is no longer full. Action: Correct the underlying problem by referring to the other error messages encountered with this one. ORA-00347 thread string log string, expected block size string does not match string Cause: During online fetch, the block size specified in the control file did not match the block size contained in the redo log file. Action: Restore the correct redo file from a backup or restore the online redo log files. ORA-00348 error redoing single process. You must stop the instance Cause: A critical part of the registration code failed during the operation of a single process. This error does not occur during normal multithreaded operation. Action: SHUTDOWN ABORT and restart the database. ORA-00349 could not get block size for 'string' Cause: The operating system could not determine the block size for the given file name. Action: View the attached error message and correct the device or specify another file name. ORA-00350 Thread Chain Log string needs to be archived Cause: The command cannot be executed because the log has not been archived and media recovery has been enabled. Action: Archive the log or disable media recovery. If the command supports a NO FILE option, it can be used. However, this can make your backups useless and force deletion of some offline files. ORA-00351 Invalid recovery time Cause: The time specified in a recovery statement must be after January 1, 1988. Action: Specify a time after January 1, 1988.

ORA-00000 to ORA-00899

2-39

ORA-00352 all logs for thread chain should be archived; cannot be enabled Cause: An attempt was made to enable a thread with all logs to be archived and media retrieval was enabled. There is no registration that can re-register the current thread for the thread. Action: File a log for the thread or disable media recovery. ORA-00353 registry corruption near time string change block string Cause: Some type of recovery registry corruption was discovered. This error describes the location of the corruption. The accompanying errors describe the type of corruption. Action: Perform recovery with a good version of the redo log, or perform an incomplete recovery to the indicated change or time. ORA-00354 Corrupt redo log block header Cause: The redo block header indicated by the accompanying error is invalid. The block number and timestamp are provided in an attached message. Action: Perform recovery with a good version of the redo log or perform a rollback-based recovery up to, but not including, the damaged redo log file. If this happens during archiving, archiving of the problem log can be omitted by clearing the log with the NO ARCHIVE option. This must be followed by a backup of each data file to ensure the recoverability of the database. ORA-00355 Change numbers out of order Cause: A change number found in the redo log is less than a change number found previously. The registry is damaged in some way. The corruption can be in the previous change or in this one. Action: Run recovery with a good version of the log or run time-based recovery at the indicated time. ORA-00356 Inconsistent lengths in change description Cause: A change record in the redo log contains lengths that do not sum to a consistent value. The registry is damaged in some way. Action: Run recovery with a good version of the registry or perform a time-based recovery at the indicated time.

2-40

message error

ORA-00357 Too many log file members specified, maximum is string Cause: An ADD LOGFILE or ADD LOGFILE MEMBER command would result in a log with too many members. The number of members is defined when the database is created. User Response: Use fewer log file members. ORA-00358 Too many file members specified, maximum is string Cause: A CREATE or ALTER statement specified too many members in a file list enclosed in parentheses. Action: Specify a number of file members that are within the limit defined by the port. ORA-00359 Log file group string does not exist Cause: An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist. Action: Check the configuration of the log files and issue the command again. ORA-00360 is not a member of the log file: string Cause: The DROP LOGFILE MEMBER command was given a file name that is not part of the database or is a data file. User Response : Provide a valid log file member name. ORA-00361 cannot remove last log member string from group chain Cause: An attempt was made to remove the last member of a group from the log files. Action: If desired, remove the entire log with DROP LOGFILE. The ORA-00362 member is required to form a valid log file in the group chain. Cause: A request to drop a log file member was rejected because it would remove data necessary to form a complete log file. Action: If desired, delete the entire log (after archiving it if necessary) with DROP LOGFILE. Log ORA-00363 is not the archived version Cause: The log provided for recovery is a backup of the online version at the time it was the current log. The archived version of the log would not be marked as the end of the thread. This error can also be caused by not displaying the current record of a thread activated in a CREATE CONTROLFILE command.

ORA-00000 to ORA-00899

2-41

Action: Find the archived version of the log and provide its name. If this is media recovery immediately after CREATE CONTROL FILE, make sure the current record for this segment is included. ORA-00364 Cannot write header to new registry member Cause: An I/O error occurred while trying to write the header to a registry member that is added to an existing group. Action: Check the attached errors. Fix the problem or use another file. ORA-00365 The specified record is not the next good record Cause: The specified record did not pass checks to ensure it matches the newly applied record. This is likely the result of using a log that was generated on a cold backup image of the database. Action: Locate the log generated by this database copy and provide this file name for recovery. ORA-00366 Thread logging stream file header checksum error Cause: The file header for the redo log contains a checksum that does not match the calculated value of the file header as described read from disk. This means that the file header is corrupted. Action: Find and install the correct version of the registry or reset the registry. ORA-00367 Checksum error in log file header Cause: The file header for the redo log contains a checksum that does not match the calculated value of the file header as read from disk. This means that the file header is corrupted. Action: Find the correct file and try again. ORA-00368 checksum error in redo log block Cause: The redo block indicated by the accompanying error is invalid. You have a checksum that does not match the content of the block. Action: Run recovery with a good version of the registry or perform a time-based recovery at the indicated time. If this happens during archiving, archiving of the problem log can be omitted by clearing the log with the NO ARCHIVE option. This must be followed by a backup of each data file to ensure the recoverability of the database. Restore the correct file or reset the logs.

2-42

message error

ORA-00369 The thread flow's current record is unusable and another record is being cleared Cause: An attempt to open the thread failed because it needs to switch redo generation to another online record, but all other records are being cleared o They must be archived before they can be used. Action: If the ALTER DATABASE CLEAR LOGFILE command is still active, wait for it to complete. Otherwise, issue the CLEAR command again. If there are other records online for the thread that are not cleared, archive them. ORA-00371 no free buffer identifier available Cause: There is not enough memory to continue the operation. Action: Increase the value of the SHARED_POOL_SIZE initialization parameter and try again. The string in file ORA-00372 cannot be modified at this time Cause: An attempt was made to modify the content of a file that cannot be modified. The file is likely part of a read-only tablespace, but it might be in the process of going offline, or the database might be in the process of shutting down. Action: Check the status of the file and its tablespace. ORA-00373 online registry version string incompatible with ORACLE version string Cause: The online registry was written by an incompatible version of Oracle. This can happen when the log file was created by a newer or older version of Oracle. Action: Recover the database with the supported software, shut it down gracefully, and restart it with the current software. Parameter ORA-00374 db_block_size = invalid string, valid range [string...string] Cause: An invalid value was specified for the DB_BLOCK_SIZE parameter. Action: Adjust the parameter value and restart the instance. ORA-00375 Could not get default size of db_block_size Cause: The system could not determine the default value for DB_BLOCK_SIZE. Action: See the attached system-specific error. As a workaround, specify the block size in the INIT.ORA file.

ORA-00000 to ORA-00899

2-43

File string ORA-00376 cannot be read at this time Cause: An attempt was made to read a file that cannot be read. The file is probably offline. Action: Check the status of the file. Put it online. ORA-00377 File string backups frequently cause the write operation to stop. Cause: Backups are performed too frequently on this file. Every time a new backup for a file is started, all writes that were previously issued (but did not complete) must be reissued. If active backups are started very, very frequently, some writes may be reissued over and over again and never complete. Action: Increase the interval between start active backup commands for this file. ORA-00378 Buffer groups cannot be created as specified Cause: The number of buffers or the number of LRU locks is too small to satisfy the specified buffer group configuration. Action: Increase the number of buffers and/or the number of LRU locks, or configure smaller buffer pools. ORA-00379 no free buffer available in buffer pool chain Cause: All buffers in the specified buffer pool are in use and no free buffers are available. Action: Increase the number of buffers in the specified pool. ORA-00390 Thread sequence log stream is being cleaned up, cannot be converted to current log Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log was found. This record is being cleaned up and will be usable when the cleanup is complete. The command that started the cleanup may have finished without completing the cleanup. Action: If the delete command is still running, wait for it to complete. If it exits, reissue the clear command or discard the record. ORA-00391 All threads must switch to the new log format at the same time Cause: An attempt to change the current log for a single thread is not allowed because compatibility requirements force a new log format version number. When changing record formats, all threads must switch to the new format at the same time.

2-44

message error

Action: Open the database to perform the coordinated record change. If this is not possible, revert to the same software version and compatibility settings that were last used to open the database. ORA-00392 Thread stream log chain is being cleaned up, operation not allowed Cause: An operation encountered this record online in the middle of cleaning. The command that started the cleanup may have finished without completing the cleanup. Action: If the delete command is still running, wait for it to complete. If it exits, reissue the clear command or discard the record. ORA-00393 Thread Chain A log chain is required to retrieve offline data files Cause: The log cannot be cleared because a redo is required to retrieve offline data files. It has not been archived, so no other copy is available. If the record is deleted, the table spaces containing the files will need to be dropped. Action: Archive the log and retry the clear command. If archiving is not possible and dropping the table spaces is acceptable, add the UNRECOVERABLE DATAFILE clause to the end of the clear command. ORA-00394 Online log reused when trying to archive Cause: An attempt was made to reuse an online log file that is being archived. Action: The online log file has been replaced; cannot be archived. ORA-00395 Online logs for cloned database need to be renamed Cause: An open cloned database forces the log file to be renamed to avoid overwriting the parent log files. User Response : Change the name of the log files manually or by using the LOG_FILE_NAME_CONVERT initialization parameter. ORA-00400 Invalid release value string for parameter string Cause: The release level supplied for the specified initialization parameter is invalid. User Response : Correct the parameter value in the parameter file and try again. Parameter string value ORA-00401 is not supported by this version Cause: The specified value is not supported by this software version. Action: Choose an appropriate value or remove the parameter value to use the default value.

ORA-00000 to ORA-00899

2-45

ORA-00402 Database changes by version string cannot be used by version string Cause: Changes were made to the database that require a newer software version or violate compatibility parameters. Action: Use a software version that can understand the changes or relax the compatibility requirements in the boot file. ORA-00403 string (string) is not the same as other instances (string) Cause: Another instance defined the COMPATIBLE or COMPATIBLE WITHOUT RECOVERY parameters differently than this instance. Action: Change the parameters of the current instance to match other instances that are already running. ORA-00404 Conversion file not found: 'string' Cause: The file used to convert the database from V7 to V8 was not found. Action: Verify that the migration process has started on this database and that the converted file name is accessible. ORA-00405 compatibility type "string" Cause: Report of a type associated with another error. Action: See the attached error. ORA-00406 The COMPATIBLE parameter must be a string or greater. Cause: The value of the COMPATIBLE initialization parameter is not high enough to allow the operation. Enabling the command would make the database incompatible with the version specified by the current COMPATIBLE parameter. Action: Shut down and reboot with a higher compatibility setting. ORA-00407 Rolling version upgrade not allowed string.string to string.string Cause: Another instance running software at a different version point already has the database mounted. Action: Shut down all instances and reboot with fresh software. Parameter string ORA-00408 is set to TRUE Cause: Report parameter that resulted in a compatibility error. Action: Shut down and reboot with a higher compatibility setting.

2-46

message error

ORA-00436 ORACLE is not licensed. Contact Oracle Corp. for assistance. Cause: This installed Oracle software is not licensed to run on this CPU. This can also happen if the Oracle software was installed incorrectly, for example with the wrong license codes. Action: Verify that Oracle is installed correctly. Then contact Oracle Customer Support. ORA-00437 The ORACLE feature is not licensed. Contact Oracle Corp. for assistance. Cause: This installed Oracle feature is not licensed to run on this CPU. This can also happen if the Oracle software was installed incorrectly, for example with the wrong license codes. Action: Verify that Oracle is installed correctly. Then contact Oracle Customer Support. ORA-00438 string Option not installed Cause: The specified option is not installed. Action: Avoid calling the option or purchase and install the option. ORA-00439 function not enabled: string Cause: The specified function is not enabled. Action: Do not attempt to use this function. ORA-00443 Background process "chain" did not start Cause: The specified process did not start. Action: Make sure that the executable image is in the correct location with the correct protections and that there is enough memory. ORA-00444 The background process "chain" failed to start. Cause: Usually due to a bad (or non-existent) background process image. Action: Get a good picture of the background process. ORA-00445 background process "chain" did not start after chain seconds Cause: The specified process did not start after the specified time. Action: Make sure the background hasn't died and leave a trace file. ORA-00446 Background process started when not expected Cause: The specified background process was started after Oracle was already running.

ORA-00000 to ORA-00899

2-47

Action: Check the attached messages, if any, and the background process trace file. Please fix the problem mentioned in other posts. If no user at the site initiated the process, please report the message to Oracle Customer Support. Fatal error ORA-00447 in background process Cause: One of the background processes died unexpectedly. Action: Reboot the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST. ORA-00448 Background process completed successfully Cause: One of the background processes completed normally as requested by the user. Action: If you are troubleshooting a problem, check for other messages and the background process trace file. Please fix the problem mentioned in other posts. Then shut down and restart Oracle. ORA-00449 Background process 'chain' terminated unexpectedly with an error string Cause: A foreground process that needed service from a background process discovered that the process was terminated. Action: Check the message code provided in the message and the trace file for the foreground and background processes. ORA-00470 LGWR process terminated with an error Cause: The log writer process terminated abnormally. Action: Check the attached messages and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00471 DBWR process terminated with error Cause: The database write process terminated abnormally. Action: Check the attached messages and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00472 PMON process terminated with an error Cause: The process monitor process terminated abnormally.

2-48

message error

Action: Check the attached messages and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00473 ARCH process terminated with an error Cause: The archiver process terminated abnormally. Action: Check the attached messages, if any, and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00474 SMON process terminated with an error Cause: The system monitor process terminated abnormally. Action: Check the attached messages, if any, and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00475 TRWR process terminated with error Cause: The system scan process terminated abnormally. Action: Reboot the instance. ORA-00476 RECO process terminated with error Cause: Distributed transaction recovery (two-phase commit) processing terminated abnormally. Action: Reboot the instance. ORA-00477 SNP* process terminated with error Cause: A snapshot update process terminated abnormally. Action: Reboot the instance. ORA-00480 LCK* process terminated with error Cause: A lock process terminated abnormally. Action: Check the attached messages, if any, and the background process trace file. Fix the problem mentioned in the messages. then hang up and

ORA-00000 to ORA-00899

2-49

restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00481 LMON process terminated with an error Cause: The lock manager monitor process terminated abnormally. Action: Reboot the instance. ORA-00482 LMD* process terminated with error Cause: A Lock Manager daemon process terminated abnormally. Action: Reboot the instance. ORA-00483 During shutdown, a process terminated abnormally Cause: One of the background processes did not terminate normally at or near shutdown time. Action: Use the SHUTDOWN ABORT command. Check the attached messages, if any, and the background process trace file. Fix the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found. ORA-00568 Maximum number of interrupt handlers exceeded Cause: The number of interrupt handlers registered when the interrupt switch is inserted exceeds the maximum allowed. Action: Reduce the number of registered interrupt handlers. Internal error code ORA-00600, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: This is the internal error number generic for Oracle Program Exceptions. Indicates that a process encountered a low-level unexpected condition. Causes for this message include:

2-50

message error

■

time limits

■

file corruption

■

memory failed data checks

■

hardware, memory or I/O errors

■

incorrectly restored files

The first argument is the internal message number. Other arguments are various numbers, names, and strings. The numbers may change meaning between different versions of Oracle. Action: Report this error to Oracle Customer Support after collecting the following information: ■

events leading up to the error

■

the operations that were attempted that led to the error

■

the conditions of the operating system and databases at the time of the failure

■

any unusual circumstances that occurred before receiving the ORA-00600 message

■

content of any trace file generated by the error

■

the relevant parts of the Alter files

Note: The cause of this message can manifest as different errors at different times. Please note the history of errors that occurred prior to this internal error. Cleanup lock conflict ORA-00601 Cause: Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message that is usually not issued. Action: Contact Oracle Customer Support. ORA-00602 internal programming exception Cause: An internal programming exception occurred. Action: Report this error as a program error to Oracle Customer Support. ORA-00603 ORACLE server session terminated fatally Cause: An Oracle server session is in an unrecoverable state. Action: Log in to Oracle again and a new server session will be automatically created. Examine the session trace file for more information. ORA-00604 error occurred in recursive SQL level string Cause: An error occurred while processing a recursive SQL statement (a statement that is applied to internal dictionary tables). Action: If the situation described in the following stack error can be corrected, do so; otherwise, contact Oracle Customer Support.

ORA-00000 to ORA-00899

2-51

ORA-00606 Internal Error Code Cause: A call to deferred UPI functions was made in non-deferred mode. Action: Contact Oracle Customer Support. The ORA-00701 object required to warm-initialize the database cannot be changed Cause: An attempt was made to change or drop a database object (table, cluster, or index) defined in the initialization segment of the control file and needed warm start the database. Action: Correct the spelling of the object name or remove it from the ALTER or DROP statement. ORA-00702 Boot version 'string' inconsistent with version 'string' Cause: The boot data version is incompatible with the current software version. Action: Restore a version of the software that is compatible with the data files. ORA-00703 Max Line Cache Instance Locks Exceeded Cause: There are not enough line cache queues. Action: Increase the value of the ROW CACHE ENQUEUE parameter and reboot the system. ORA-00704 Boot process failed Cause: Boot data processing failed. Please refer to the attached messages for more information on the cause of the problem. Action: Correct the problems mentioned in other messages. If the problem persists, contact Oracle Customer Support. ORA-00705 Inconsistent state during boot; shut down the instance and restart it Cause: A previous attempt to start an instance ended. Action: Shut down the instance completely and restart it. ORA-00816 error message translation failed Cause: There was an internal error in which a routine was unable to translate a message code. Action: Contact Oracle Customer Support.

2-52

message error

3 ORA-00900 to ORA-01499 ORA-00900 Invalid SQL statement Cause: The statement is not recognized as a valid SQL statement. This error can occur if the procedure option is not installed and an SQL statement that requires this option is issued (for example, a CREATE PROCEDURE statement). You can determine if the procedure option is installed by starting SQL*Plus. If the PL/SQL banner is not displayed, the option is not installed. Action: Correct the syntax or install the procedural option. ORA-00901 Invalid CREATE command Cause: The CREATE command was not followed by a valid CREATE option. Action: Correct the syntax. ORA-00902 invalid data type Cause: The data type entered in the CREATE or ALTER TABLE statement is invalid. Action: Correct the syntax. ORA-00903 invalid table name Cause: The name of a table or cluster is invalid or does not exist. This message will also be issued if an invalid cluster name or no cluster name is specified in an ALTER CLUSTER or DROP CLUSTER statement. Action: Check spelling. A valid table or cluster name must begin with a letter and can only contain alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word. ORA-00904 invalid column name Cause: The column name entered is missing or invalid.

ORA-00900 to ORA-01499 3-1

Action: Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist only of alphanumeric characters and the special characters $, _, and #. If it contains other characters, it must be enclosed in double quotes. It may not be a reserved word. ORA-00905 Missing keyword Cause: A required keyword is missing. Action: Correct the syntax. ORA-00906 Missing left parenthesis Cause: A required left parenthesis was omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses are also required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements. Action: Correct the syntax, insert a left parenthesis where necessary, and repeat the declaration. ORA-00907 Missing Right Parenthesis Cause: A left parenthesis was entered without a closing right parenthesis, or there was additional information inside the parentheses. All parentheses must be entered in pairs. User Response : Correct the syntax and retry the declaration. ORA-00908 Missing NULL keyword Cause: One of the following: In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that null values are not allowed in this column, but the NULL keyword was omitted. In the logical operator IS [NOT] NULL, the keyword NULL was not found. For example, the following statement generates this message: SELECT * FROM EMP WHERE DEPTNO IS NOT;

The NULL keyword must follow the IS NOT keywords. Action: Correct the syntax. ORA-00909 Invalid number of arguments Cause: An Oracle function was referenced with an incorrect number of arguments. All Oracle functions except SYSDATE require at least one argument.

3-2

message error

Action: Correct the syntax of the function by entering the required number of arguments. ORA-00910 The specified length is too long for its data type Cause: No length was specified for a character field or the length was invalid. A maximum length must be specified for each column of characters. The maximum value of this length varies for each character data type, such as CHAR or VARCHAR2. Action: Enter a maximum length for the field. ORA-00911 invalid character Cause: Special characters are only valid in certain locales. If special characters other than $, _, and # are used in a name and the name is not enclosed in double quotes ("), this message will be returned. An exception to this rule are database names; in this case, the double quotes are removed and ignored Action: Remove the invalid character from the statement or enclose the object name in double quotes ORA-00913 too many values Cause: The SQL statement requires two sets of values that are equal in number. error occurs when the second array contains more elements than the first. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in INSERT. Action: Check the number of elements in each array and change the SQL statement to make them equal ORA-00914 Missing ADD keyword Cause: The ADD keyword does not precede one of the following: ■

Keyword log file in an ALTER DATABASE statement

■

A column element or table constraint in an ALTER TABLE statement

■

The DATAFILE keyword in an ALTER TABLESPACE statement

Action: Specify the ADD keyword on the ALTER statement. ORA-00915 Dictionary table network access is not currently allowed Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support.

ORA-00900 to ORA-01499 3-3

ORA-00917 missing comma Cause: A required comma was omitted from a list of columns or values in an INSERT statement or a list in the format ((C,D),(E,F), ...). Action: Correct the syntax. ORA-00918 column defined ambiguously Cause: A column name used in a join exists in more than one table and is therefore ambiguously referenced. In a join, any column name that appears in more than one of the tables must be prefixed with its table name when referenced. The column must be named TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if the tables EMP and DEPT are joined and both contain the column DEPTNO, all references to DEPTNO must be prefixed with the table name, such as EMP.DEPTNO or E.DEPTNO. User Response: I prefix references to column names that exist in multiple tables with the name of the table or a table alias and a period (.) as in the previous examples. Invalid function ORA-00919 Cause: An input was formatted as a function call, but is not recognized as an Oracle function. Action: Correct the syntax. ORA-00920 Invalid relational operator Cause: A search condition was entered with an invalid or missing relational operator. Action: Add a valid relational operator such as =, !=, ^=, , >, =, 4000 to the link list Cause: More than one long buffer in the link list. User Response : Change the buffer size to less than 4000 for the bind variable bound to a regular column. ORA-01027 Illegal bind variables for dataset operations Cause: An attempt was made to use a bind variable in an SQL dataset operation.

3-22

message error

Action: These binding variables are not allowed. Two task internal error ORA-01028 Cause: Long send message received but no cursor context. Action: Contact Oracle Customer Support. Two task internal error ORA-01029 Cause: Received a request to resend the length when there is no length Action: Contact Oracle customer support. ORA-01030 SELECT ... INTO variable does not exist Cause: The SELECT ... INTO variable specified in the bind call does not correspond to a variable in the SQL statement. Action: If the statement cannot be corrected, call Oracle Customer Support. ORA-01031 Insufficient privileges Cause: An attempt was made to change the current username or password without the proper privilege. This error also occurs when trying to install a database without the necessary operating system privileges. When Trusted Oracle is configured on DBMS MAC, this error can occur if the user has been granted the required privilege on a label higher than the current login. Action: Ask the database administrator to perform the operation or grant the necessary privileges. For Trusted Oracle users who receive this error despite having been granted the proper privilege on a higher tag, ask the database administrator to re-grant the privilege on the proper tag. ORA-01032 Missing User ID Cause: This is an internal error message related to export/import. Action: Contact Oracle Customer Support. ORA-01033 ORACLE startup or shutdown in progress Cause: An attempt was made to login while Oracle was starting up or shutting down. Action: Wait a few minutes. Then repeat the operation. ORA-01034 ORACLE not available Cause: Oracle did not start. Possible causes include the following: ■

The LMS requires more space than it has been allocated.

ORA-00900 to ORA-01499

3-23

■

The operating system variable that points to the instance is set incorrectly.

Action: Please review the attached messages for possible causes and correct the problem mentioned in the other messages. If Oracle has started, on some operating systems, verify that Oracle has successfully linked. Consult the platform-specific Oracle documentation. ORA-01035 ORACLE only available to users with SESSION RESTRICTED privilege Cause: No logins allowed because an instance was started in restricted mode. Only users with the SESSION RESTRICTED system privilege can log in. Action: Request to restart Oracle without the restricted option or get the SESSION RESTRICTED system privilege. ORA-01036 Illegal variable name/number Cause: The binding context could not be found on the user side. User Response : Make sure the variable being bound is in the SQL statement. ORA-01037 Maximum cursor memory exceeded Cause: An attempt was made to process a complex SQL statement that consumed all available cursor memory. Action: Simplify the complex SQL statement. Alternatively, you can use the NO_EXPAND hint which prevents the cost-based optimizer from considering OR expansion for queries with OR or INLIISTS conditions in the WHERE clause. Typically, the optimizer considers using OR expansion and uses this method if it decides that the cost is less than not using it. See Oracle8i Designing and Tuning for Performance for information on using hints. ORA-01038 cannot write database file version string with ORACLE version string Cause: An attempt was made to write the data file headers in an old format. The new format cannot be used until the database has been verified to be compatible with this version of the software. Action: Open the database to switch to the new file formats and try the operation again. If the operation is required before you can open the database, use the older software version to perform the operation. ORA-01039 Insufficient privileges on the underlying objects of the view Cause: An attempt was made to explain the plan in the view to others without the necessary privileges on the underlying objects of the view.

3-24

message error

Action: Obtain the necessary privileges or do not perform the offending operation. ORA-01040 invalid character in password; login denied Cause: There are multi-byte characters in the password or some characters in the password are not in the US7ASCII range. Action: Resubmit the password with valid characters. Internal error ORA-01041. Hostdef extension does not exist Cause: The pointer to the HSTDEF extension in HSTDEF is null. Action: Contact Oracle Customer Support. ORA-01042 not allowed to disconnect a session with open cursors Cause: An attempt was made to disconnect a session that had open cursors. Action: Close all cursors before disconnecting the session. ORA-01043 User Side Memory Corruption [string], [string], [string], [string] Cause: The application code has corrupted part of the user memory used by Oracle. Action: Make sure that the application code is not overwriting memory. ORA-01044 Buffer size string bound to string variable exceeds maximum string Cause: An attempt was made to bind a buffer whose total size would exceed the maximum allowed size. The total array size for arrays is calculated as: (element_size)*(number of elements)

Action: Reduce the buffer size. The user string ORA-01045 lacks the CREATE SESSION privilege; login denied Cause: An attempt was made to connect with a user ID that does not have session creation privileges. Action: Grant the user the CREATE SESSION privilege. ORA-01046 cannot acquire space to expand the context area Cause: Oracle could not expand the current area any further because the operating system did not provide more space. After this message a specific system message should appear. Action: Please close some cursors and try again, or check the operating system quotas to use more virtual memory. Consult the Oracle documentation specific to the operating system.

ORA-00900 to ORA-01499

3-25

ORA-01047 The above error occurred at schema=string, package=string, procedure=string Cause: This message is displayed after a previous message to provide more specific information. Action: See the cause and action of the previous message. ORA-01048 Could not find the procedure specified in the given context Cause: The user of the procedure specified in lazy RPC does not exist. Action: Verify that the procedure exists and is visible to the replication process. ORA-01049 Bind by name is not compatible with past RPC Cause: This error occurs when a newer server version requests an operation from an older server version that is not supported. Action: You may need to update one or more of your Oracle servers or relink your user application with new libraries. ORA-01050 Could not acquire space to open context area Cause: Oracle could not open a new context area because the operating system did not provide more space. After this message a specific system message should appear. Action: Please close some cursors and try again, or check the operating system quotas to use more virtual memory. Consult the Oracle documentation specific to the operating system. ORA-01051 Lazy RPC buffer format invalid Cause: Lazy RPC data in SYS.DEF$_CALL is corrupted. Action: Contact Oracle Customer Support. ORA-01052 LOG_ARCHIVE_DUPLEX_DEST mandatory destination not specified Cause: A valid destination was not specified for the LOG_ARCHIVE_DUPLEX_DEST parameter when the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter was set to 2. Action: Specify a value for the LOG_ARCHIVE_DUPLEX_DEST parameter or reduce the value for the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter to 1. -01052 - 01053 Cannot read user storage address Cause: Oracle could not read a bind variable or other user area.

3-26

message error

Action: Check that the binds succeeded in the valid user buffers and retry the operation. Cannot write user storage address ORA-01054 Cause: Oracle could not write a definition, FETCH... INTO or SELECT... INTO, variable or other user area. Action: Verify that the INTO variables and pointers are specified correctly. Then repeat the operation. ORA-01057 Invalid or ambiguous block field reference in user exit Cause: The reference to a block field identifier in a user exit is incorrect or ambiguous, probably because it is incorrect or incomplete. Action: Check the syntax and spelling of the identifier. Then set the reference. New Upi interface internal error ORA-01058 Cause: Attempt to remove non-existent HSTDEF extension. Action: Contact Oracle Customer Support. ORA-01059 Parsing expected before binding or execution Cause: The client application tried to bind a variable or execute an open cursor in a PL/SQL block before the statement was parsed. Action: Make sure the statement is parsed before binding or execution. ORA-01060 Array bound or executed not allowed Cause: The client application tried to bind an array of cursors or repeatedly tried to execute in a PL/SQL block with a binding variable of type cursor. Action: Bind a single cursor or execute the PL/SQL block once. ORA-01061 unable to start a V8 server using a V7 client application Cause: You are using an Oracle client application linked to version 7 (or lower) libraries and tried to start a V8 (or higher) server. Action: Use a client application that links to V8 (or higher) libraries. ORA-01070 Using an older version of Oracle for the server Cause: An attempt was made to run an old and outdated Oracle server. Action: Update the server.

ORA-00900 to ORA-01499

3-27

ORA-01071 cannot perform operation without initializing ORACLE Cause: An attempt was made to perform an operation before starting Oracle. Action: Start Oracle. Then repeat the operation. ORA-01072 cannot stop ORACLE; ORACLE is not running Cause: An attempt was made to stop Oracle, but Oracle was not running. Action: No action is required. Fatal connection error ORA-01073: unrecognized call type Cause: An illegal internal operation was attempted. Action: Contact Oracle Customer Support. ORA-01074 cannot close ORACLE; within a login session: log off first Cause: An attempt was made to close Oracle within a login session. Action: Log off before closing Oracle. ORA-01075 is currently connected Cause: An attempt was made to log in while already connected. Action: No action is required. ORA-01076 multiple logins per process not yet supported Cause: Oracle does not support multiple logins per process. Action: No action is required. ORA-01077 Background process initialization failed Cause: An error occurred while initializing background processes. Action: Review the diagnostic information in the attached message stack or trace file and take appropriate action. ORA-01078 failed to process system parameters Cause: Could not process initialization parameters during system startup. Action: Other diagnostic information should be in the error stack. ORA-01079 The ORACLE database was not created successfully, the operation was canceled Cause: An error occurred while creating the database or control file.

3-28

message error

Action: Check what error was flagged when the database was first created or when the control file was recreated. Take the appropriate steps to recreate the database or a new control file. ORA-01080 error when shutting down ORACLE Cause: A failure occurred during system shutdown. Action: Review the stack of attached messages for diagnostic information and take appropriate action. ORA-01081 cannot start ORACLE which is already running; shut it down first Cause: An attempt was made to start Oracle while it was already running. Action: Shut down Oracle first if you want to restart it. ORA-01082 'row_locking = always' requires transaction processing option Cause: "row_locking = always" is specified in the INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option. Action: Remove it from the INIT.ORA file or set it to "default" or "intent". ORA-01083 The value of the parameter "string" is not consistent with other servers Cause: The value of the given initialization parameter must be the same for all servers in the parallel configuration. Action: Change the value in the initialization parameter file to match that of the other control files. ORA-01084 Invalid argument in OCI call Cause: The failed OCI call contains an argument with an invalid value. User Response: Use valid argument values. For more information, see the Oracle Call Interface Programmer's Guide and the appropriate programming language supplement. Previous Errors ORA-01085 in lazy rpc to "string.string.string" Cause: Errors were encountered when the named procedure was executed as a lazy remote procedure call. Action: Correct the cause of the above errors. ORA-01086 Savepoint 'string' never set Cause: An attempt was made to revert to a savepoint that was never set. Action: No action is required.

ORA-00900 to ORA-01499

3-29

ORA-01087 cannot start ORACLE - currently logged in Cause: A user who is currently logged in attempted to start Oracle. Action: Log out. Then issue the STARTUP command. ORA-01088 cannot close ORACLE while processes are active Cause: Users are still connected to the instance. Action: Wait until all users log off or use CLOSE IMMEDIATELY. ORA-01089 Immediate shutdown in progress: no operations allowed Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, ending all active operations. Action: Wait until the instance restarts or contact your database administrator. ORA-01090 shutdown in progress: connection not allowed Cause: The SHUTDOWN command was used to shut down a running Oracle instance, preventing any connection to Oracle. Action: Wait for the instance to restart or contact your database administrator. ORA-01091 failed during forced initialization Cause: Could not destroy the old SGA. Action: Manually remove the old LMS. Consult the Oracle documentation specific to your operating system for instructions. Then repeat the START command. ORA-01092 ORACLE instance terminated. Forced disconnection cause: The connected instance was terminated abnormally, most likely due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance. Action: Contact your database administrator to determine when the instance will be restarted. Try to connect again after the instance is running again. ORA-01093 ALTER DATABASE CLOSE only allowed without connected sessions Cause: There is at least one more session, besides the current one, registered in the instance. ALTER DATABASE CLOSE is not allowed when other sessions are active. Action: Find the other sessions and disconnect them. Then repeat the ALTER DATABASE CLOSE command. Also issue IMMEDIATE SHUTDOWN

3-30

message error

to force users to disconnect from the system or issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be disconnected. ORA-01094 CLOSURE OF DATABASE ALTERATION in progress. Connections not allowed Cause: A connection attempt was made while the database was being closed with the ALTER DATABASE CLOSE command. Action: Try to connect again when the database is open. Contact your database administrator to find out when the database will open. ORA-01095 DML statement processed 0 lines Cause: A DML cursor in the OTEX() call processed 0 lines when executed. Action: The caller can back out or ignore the message and execute the rest of the cursors in the cursor array. ORA-01096 program version (string) incompatible with instance (string) Cause: The program was linked to a different server version than the instance it is trying to connect to. Action: Rebind the program to the same Oracle version of the instance or reboot (force start) the database using the SERVER version of the program. ORA-01097 cannot be closed during a transaction; commit or rollback first Cause: An attempt was made to close the database while a transaction was in progress. Action: Commit or roll back the current transaction and try to close the database. PI error ORA-01098 during long insert Cause: The PI failed to insert or update a LONG column due to an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid. Action: Repeat the insert or update. ORA-01099 cannot mount database in SHARED mode if started in single process mode Cause: An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.

ORA-00900 to ORA-01499

3-31

Action: Mount the database in EXCLUSIVE mode or set the SINGLE_PROCESS initialization parameter to FALSE before starting the instance in parallel (shared) mode. ORA-01100 Database already mounted Cause: An attempt was made to mount a database with the name of a currently mounted database. Action: No action is required. Database ORA-01101 is being created mounted by some other instance. Cause: Some other instance has the database of the same name currently mounted and you are trying to create it. Action: Change the database name or shut down the other instance. ORA-01102 cannot mount database in EXCLUSIVE mode Cause: Some other instance has the database mounted exclusively or shared. Action: Shut down the other instance or mount in a compatible mode. ORA-01103 The database name 'string' in the control file is not 'string' Cause: The database name in the control file does not match the database name. Action: Find the correct control file or change the database name. ORA-01104 number of control files (string) does not equal string Cause: The number of control files used by this instance does not match the number of control files in an existing instance. Action: Verify that all control files are listed. ORA-01105 mount is incompatible with mounts of other instances Cause: An attempt to mount the database found that another instance mounted a database with the same name, but the mount is not compatible. Additional bugs are reported explaining why. Action: Check the attached errors. Database ORA-01106 must be closed before unmounting Cause: An attempt was made to unmount a database before it could be closed. Action: Close the database and retry the operation.

3-32

message error

The ORA-01107 database must be mounted for media recovery. Cause: An attempt was made to perform media recovery, but the database is not mounted. Action: Mount the database. ORA-01108 Chain file is in backup or recovery media" Cause: Media recovery is actively being applied to the file or being backed up while the database is in NOARCHIVELOG mode. Cannot use for normal database access data or failover Action: Complete or cancel the backup or recovery media session Database ORA-01109 not open Cause: A command was attempted that requires the database to be open the database Action: Open the database and try the command again ORA-01110 data file string: 'string' Cause: This message reports the name of the file involved with other messages Action: See the messages for a description of the problem ORA-01111 Unknown string data file name, please rename the correct file The BACKUP CONTROLFILE RECOVERY command was performed with a control file that s e saved before the file will be created a howl. Action: Change the name of the MISSING file to the actual file name. ORA-01112 Media Recovery Not Started Cause: An error occurred while trying to continue media recovery, but the media recovery did not start. Action: No action is required. ORA-01113 file stream needs media recovery Cause: An attempt was made to open a data file that needs media recovery. Action: First apply media recovery to the data file identified in the message, then retry the operation. ORA-01114 I/O error writing block to file string (block #string) Cause: The device the file resides on is probably offline.

ORA-00900 to ORA-01499

3-33

Action: Restore access to the device and try the operation again. ORA-01115 I/O error reading block string from file (block # string) Cause: The device the file resides on is probably offline. Action: Restore access to the device and try the operation again. ORA-01116 error opening database file string Cause: The file cannot be accessed normally. Action: Make sure the data file is in the expected location and can be accessed correctly, and try the operation again. ORA-01117 adding file 'string' with illegal block size: string; limit is string Cause: An attempt was made to add a data file with a block size greater than the maximum block size allowed. User Response : Repeat the operation with a smaller block size. ORA-01118 cannot add more database files: string limit exceeded Cause: An attempt to add a data file failed because the limit for these files has already been reached. Action: If more space is needed in the database, export the database and recreate it with a higher limit for data files and perhaps a larger file size. Error ORA-01119 creating database file 'string' Cause: There is not enough space on the device. Action: Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the instructions, specify a file size that is smaller than the available space on the device. ORA-01120 unable to delete file string from online database Cause: An attempt was made to delete a data file while it was online. Action: Take the file offline before dropping it. ORA-01121 unable to rename database file string: file is in use or being retrieved Cause: An attempt was made to use ALTER DATABASE RENAME to rename a data file that is online on an open or recovering instance. Action: Shut down the database on all instances and end all recovery sessions.

3-34

message error

Database file chain check failed ORA-01122 Cause: The information in this file is not consistent with the information in the control file. See the message that accompanies the reason. Action: Make sure that the database files and control files are the correct files for this database. ORA-01123 cannot start online backup; media recovery not enabled Cause: An attempt to start an online tablespace backup failed because media recovery is not enabled. Action: Enable media recovery and try this operation again. ORA-01124 Unable to retrieve data file string: File is in use or being retrieved Cause: An attempt to retrieve from media found the file to be unavailable for recovery. Either you are online and the database is open at some point, or another process is performing a media recovery on the file. Action: Do not perform media recovery. ORA-01125 cannot disable media recovery: file chain has an online backup set Cause: An attempt to disable media recovery found that an online backup is still in progress. Action: End the backup of the offending table space and try this command again. The ORA-01126 database must be mounted EXCLUSIVELY and must not be opened for this operation. Cause: An operation failed because the database was not uniquely mounted. Action: Shut down Oracle and mount the database in exclusive mode. ORA-01127 Database name 'string' exceeds string character length limit Cause: The specified database name is too long. Action: Shorten the database name to eight characters or less and try the operation again. ORA-01128 unable to start online backup: file string is offline Cause: An attempt to start an online backup found one of the files to be offline. Action: Bring the problematic files online and try this command again or do a cold backup.

ORA-00900 to ORA-01499

3-35

ORA-01129 User default or temporary table space does not exist Cause: User default or temporary table space was dropped. User Response: Reassign the default or temporary tablespace. ORA-01130 database file version string incompatible with ORACLE version string Cause: The named data file was created on an incompatible version of Oracle or the file is invalid or does not exist. Action: Shut down and restart the correct version of Oracle or check the references to the data file and verify that it exists. ORA-01131 String value of DB_FILES system parameter exceeds string limit Cause: The specified value of the DB_FILES initialization parameter is too large. Action: Reduce the value of the DB_FILES parameter and retry the operation. ORA-01132 The length of the database file name 'string' exceeds the string character limit. Cause: The specified data file name is too long. Action: Shorten the file name and try the operation again. ORA-01133 Length of log file name 'string' exceeds string character limit Cause: The specified redo log file name is too long. Action: Shorten the file name and try the operation again. ORA-01134 Database mounted exclusively by another instance Cause: An attempt to access a database failed because another instance mounted it exclusively. Action: Shut down the other instance or wait for the other instance to shut down the database or mount it in parallel mode before retrying the operation. ORA-01135 File string accessed for DML/query is offline Cause: An attempt was made to access a data file that is offline. Action: Bring the data file back online. ORA-01136 The size of the file string (string blocks) specified is smaller than the original size of the string blocks Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller than the required size.

3-36

message error

Action: Create the file with a larger size. ORA-01137 data file string is still in the middle of being disconnected Cause: A file that is offline could not be locked while trying to bring it online. The most likely cause is that the lock is still held by the instance that detached it. Action: Wait for the other instance to release the lock on the file. Database ORA-01138 must be open on this instance or not open Cause: The requested operation cannot be performed when the database is mounted but not open on this instance and another instance has the database open. Action: Perform the operation on an open instance, open the database on this instance, or close the database on all other instances. ORA-01139 The RESETLOGS option is only valid after an incomplete recovery of the database. Cause: The RESETLOGS option was provided on ALTER DATABASE OPEN, but there was no incomplete recovery session. Action: Retry ALTER DATABASE OPEN without specifying RESETLOGS. ORA-01140 Unable to end online backup: all files are offline Cause: All files were found offline when trying to end an online backup. Action: No action is required. There is no need to end the online backup for this tablespace. ORA-01141 error renaming data file string: New file 'string' not found Cause: An attempt to rename a data file in the control file failed because no data file was found file with the new name. Action: Make sure the operating system has correctly renamed the data file and try again. ORA-01142 unable to end online backup: none of the files are in the backup Cause: None of the files were found in the online backup when trying to end an online backup. Action: No action is required. There is no need to end the online backup for this tablespace.

ORA-00900 to ORA-01499

3-37

ORA-01143 cannot disable media retrieval: file string needs media retrieval Cause: An attempt to disable media retrieval encountered a file that needs media retrieval, so media retrieval cannot be disabled . Action: Recover the offending file or drop the table space it belongs to and try this command again. ORA-01144 File size (string blocks) exceeds maximum string blocks Cause: The specified file size is larger than the maximum allowed size value. Action: Specify a smaller size. ORA-01145 Immediate disconnect is not allowed unless media recovery is enabled Cause: ALTER TABLESPACE... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE... OFFLINE is only allowed if the database is in ARCHIVELOG mode. Action: Take the tablespace offline as usual or cancel the shutdown before attempting the required operation. It is worth reconsidering the backup strategy for the database. Operation attempts can be made if the ARCHIVEREDO LOG mode is activated. ORA-01146 unable to start online backup: file chain is already in the backup Cause: An attempt was made to start an online backup, but an online backup has already started for one of the the data files. Action: End the first backup before starting another. ORA-01147 SYSTEM table space file string is offline Cause: The database administrator has marked a file belonging to the SYSTEM table space as offline. The database cannot be started until all files in the SYSTEM tablespace are online and can be opened. Action: Put the file online. ORA-01148 Unable to mount PARALLEL database without a lock manager installed. Cause: An attempt was made to mount the PARALLEL database without a lock manager installed. Action: Mount the database in EXCLUSIVE mode. ORA-01149 unable to shutdown: file chain has online backup set Cause: A shutdown attempt typically found that an online backup is still in progress. Action: End the backup of the offending table space and try this command again.

3-38

message error

ORA-01150 cannot prevent writes: file chain has online backup configured Cause: Tablespace cannot be made offline or read-only when online backup is running. Terminating the backup involves writing the file header, which this operation, if allowed, would prevent. Action: End the online backup and then take the tablespace offline or make it read-only. ORA-01151 use media recovery to recover block, restore backup if necessary Cause: Failover or Instance Recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and repaired during recovery. This message is usually accompanied by ORA-01172. Action: There is additional information for ORA-01172. Run a data file RECOVER for the file containing the block. If that doesn't solve the problem, restore the file from a backup and recover it again. File string ORA-01152 was not restored from a sufficiently old backup. Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last applied redo record. The most likely cause of this message is forgetting to restore the file from backup before performing a soft recovery. Action: Apply additional redo log files until the database is consistent, or restore the data files from a previous backup and repeat the recovery. ORA-01153 A mismatched media recovery is active Cause: An attempt was made to start a mismatched media recovery or open reset records during media recovery. Media recovery sessions are incompatible if they try to recover the same data file. Incomplete media recovery or open reset records are incompatible with any media recovery. Action: Complete or cancel another media recovery session. Database ORA-01154 busy. Open, close, mount, and unmount now not allowed Cause: There is some operation in progress that is expecting the instance state to remain open or mounted. Action: Wait for the operation to complete and try again. If you are attempting a clean shutdown of the database, try SHUTDOWN ABORTED.

ORA-00900 to ORA-01499

3-39

ORA-01155 the database is being opened, closed, mounted or unmounted Cause: The attempted operation will fail while the instance is in one of the states mentioned in the message. Action: Wait until the open, close, mount, or unmount is complete, and then try again. If you are attempting a clean shutdown of the database, try SHUTDOWN ABORTED. ORA-01156 recovery in progress may need access to files Cause: Media or instance recovery is in progress. Recovery may need access to the files that the attempted operation tried to use. Action: Wait for the recovery to complete and try again. ORA-01157 cannot identify/lock data file string; check the DBWR trace file Cause: The background process could not find one of the data files or could not lock it because the file was already in use. The database will prohibit access to this file, but other files will not be affected. However, the first instance to open the database will need access to all of the online data files. The attached operating system error describes why the file could not be identified. Action: At the operating system level, make the file available to the database. Then open the database or perform ALTER SYSTEM CHECK DATAFILES. ORA-01158 database string already mounted Cause: Another instance has a database with this name mounted. Action: Find which instance is still running. Maybe you haven't lost the control files after all. ORA-01159 file is not from the same database as the previous files - incorrect database ID Cause: Not all files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match the first file specified. Action: Check the list of files provided to CREATE. ORA-01160 file is not a string Cause: The file mentioned in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be the one indicated. Action: Check the referenced file.

3-40

message error

ORA-01161 The database name string in the file header does not match the supplied string name Cause: The database name supplied on the command line does not match the database name data found in the file header. Action: It is very likely that the database name specified on the command line is incorrect. Resolve the discrepancy and resubmit the command. If you are trying to change the database name, be sure to use the SET DATABASE option. ORA-01162 Block size string in file header does not match DB_BLOCK_SIZE (string) Cause: CREATE CONTROLFILE found that the block size for this file is incompatible with the DB_BLOCK_SIZE initialization parameter used to allocate cache buffers. If it is not the first file, there is a mix of block sizes or the file is corrupted. Action: If this is the first file in the command, correct DB_BLOCK_SIZE to match the file and restart the instance. If it is not the first file, find the correct version of the file. ORA-01163 SIZE clause indicates a string (blocks), but must match the string in the header Cause: The size in bytes specified in the SIZE clause of the CREATE CONTROLFILE statement is not equal to the number of blocks recorded in the header. Action: Specify the correct file name and size (in bytes). ORA-01164 MAXLOGFILES cannot exceed string Cause: MAXLOGFILES specified on the command line is too large. Action: Resubmit the command with a lower value for MAXLOGFILES. ORA-01165 MAXDATAFILES cannot exceed string Cause: MAXDATAFILES specified on the command line is too large. Action: Resubmit the command with a lower value for MAXDATAFILES. ORA-01166 file number string is greater than string (string) Cause: The file referenced in CREATE CONTROLFILE has a file number greater than that specified for MAXDATAFILES or MAXLOGFILES. Action: Increase the maximum specified on the command line.

ORA-00900 to ORA-01499

3-41

ORA-01167 two files have the same file/group number or the same file Cause: There is an overlap of file numbers in the files specified on the command line, or the same file is specified twice. If they are not exactly the same file, it is likely that one is a backup of the other. If they are two members of the same registry, they must be specified together in a group file specification. This message will also appear if the same control file appears more than once in the CONTROL_FILES parameter in the INIT.ORA file. If this happens, check for additional error messages. Action: Confirm that the referenced file is not a repetition of a file already referenced in the command. If they are different files, skip the previous backup. If they are members of the same registry, make sure they are in the same group file specification. If this message appears due to a duplicate control file, check the CONTROL_FILES parameter in the INIT.ORA file and see if a file was specified more than once. If all the file names seem unique, check that the actual control files are unique. For example, on UNIX, check if there is a symbolic or hard link to another control file in the list. ORA-01168 The physical block size string does not match the size string of other members Cause: The file is located on a device with a different physical block size than the other members of the pool. Action: Use a physical device with the same block size. ORA-01169 DATA FILE number 1 not found. Must be present Cause: Data file number 1 was not specified in a CREATE CONTROLFILE command. Action: Locate data file number 1 and run the CREATE CONTROLFILE command again. ORA-01170 file not found 'string' Cause: A file specified in the CREATE CONTROLFILE statement was not found. All data files and all redo log files, if NORESETLOGS was used, must be accessible by the process issuing the CREATE CONTROLFILE statement. Action: Check the file name in the statement for a typo and verify that all files exist. Then issue the statement again after correcting the file names.

3-42

message error

ORA-01171 Data file chain disconnected due to error advancing checkpoint Cause: Failed to advance checkpoint in file header. Please refer to the attached errors for the reason. The data file will be disconnected in the same way as for a data block write error. Action: See the attached errors for more information. Restore access to the file, perform media recovery, and bring it back online. ORA-01172 Thread Stream Recovery Stuck in File Stream Crashing Stream Cause: Failover or Instance Recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and repaired during recovery. Action: Perform a DATA FILE RECOVERY for the file containing the block. If that doesn't solve the problem, restore the file from a backup and recover it. ORA-01173 data dictionary indicates a missing data file in the system table space Cause: One of the following: ■

■

The database is rolled back to a point in time in the future of the control file. A system table space data file is omitted from the issued CREATE CONTROLFILE statement.

Action: One of the following: ■

■

Retrieve the database from a more recent control file. Recreate the control file, making sure all data files are added for the system tablespace on the command line.

ORA-01174 DB_FILES is a string, but must be a string to be supported Cause: The maximum number of database files supported by this instance is not the same as the other instances. All instances must be able to open all files that any instance can open. Action: Change the value of the DB_FILES parameter to make it compatible. ORA-01175 data dictionary has more than the allowed stream files per instance Cause: The data dictionary was found to have more files than this instance can support. Action: Terminate the instance and restart with a larger value for DB_FILES.

ORA-00900 to ORA-01499

3-43

The ORA-01176 data dictionary has more string files than the control file allows. Cause: After CREATE CONTROL FILE, it was discovered that the data dictionary has more data files than the control file supports. Action: Recreate the control file with a larger value for MAXDATAFILES. The ORA-01177 data file does not match the dictionary; probably an old incarnation Cause: When comparing the control file to the data dictionary after CREATE CONTROL FILE or OPEN RESTART RECORDS, it was observed that this data file did not match the dictionary. The file is most likely a backup of a file that was deleted from the database and the same file number was reused for a new file. It could also be that an incomplete recovery stopped at the time this file number was used for another data file. Action: Run CREATE CONTROLFILE with the correct file or none. ORA-01178 file string created before last CREATE CONTROLFILE, cannot be recreated Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a data file that existed in the last CREATE CONTROL file command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database. Action: Find a backup copy of the file and recover it. Perform an incomplete recovery to the time before the original creation of the file. ORA-01179 file string does not exist Cause: During data file retrieval, a file was listed that was not part of the database. Action: Double check the file name. Remember to use single quotes on the SQL*DBA command line. Also remember that the file name is translated in the SQL*DBA operating environment. ORA-01180 unable to create data file 1 Cause: An attempt was made to create data file 1 using ALTER DATABASE CREATE DATAFILE. Action: Recover the file from a backup or recreate the database. ORA-01181 file string created before last RESETLOGS, cannot be recreated Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a data file that existed in the last opened RESETLOGS database.

3-44

message error

Action: Find a backup copy of the file and recover it. Perform an incomplete recovery to the time before the original creation of the file. ORA-01182 unable to create database file chain: file is in use or being retrieved Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to recreate a data file that is online on an open or missing instance he is recovering. Action: Shut down the database on all instances and end all recovery sessions. ORA-01183 cannot mount database in SHARED mode Cause: Some other instance has the database mounted exclusively. Action: Shut down the other instance and then mount the shared one. ORA-01184 Log file group string already exists Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log that is already in use. Action: Specify a different log file number or let the database choose an unused value. ORA-01185 The log file group number string is invalid Cause: An ALTER DATABASE ADD LOGFILE command specified a record number for the new record that is too large. User Response : Specify a correct log file number. File string verification tests failed ORA-01186 Cause: The data file failed the checks to ensure it is part of the database. See the accompanying error messages as to why the verification failed. Action: Make the correct file available to the database. Then open the database or run ALTER SYSTEM CHECK DATAFILES. ORA-01187 cannot read file string because verification tests failed Cause: The data file failed the checks to ensure it is part of the database. No reads allowed until verified. Action: Make the correct file available to the database. Then open the database or run ALTER SYSTEM CHECK DATAFILES. ORA-01188 Block size string in header does not match physical block size string Cause: A log file member supplied to CREATE CONTROLFILE is on a physical device that has a different block size than the device being originally used to create the record.

ORA-00900 to ORA-01499

3-45

Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROL FILE. The ORA-01189 file is from a different RESETLOGS than the above files. Cause: In a CREATE CONTROLFILE command, this file or all previous files were backed up before the last RESETLOGS. This can also happen if it is a file that is offline and has been offline since before the last RESETLOGS. Action: If the file was taken offline normally before the last RESETLOGS and it is still offline, omit it from the CREATE CONTROLFILE command. Rename and bring the file online after opening the database. If not, find the version of the referenced file that is consistent with the rest of the data files and run the command again. ORA-01190 The control file or data file sequence is older than the last RESETLOGS Cause: An attempt was made to use a data file when the log reset information in the file does not match the control file. The data file or control file is a backup made before the most recent ALTER DATABASE OPEN RESETLOGS. Action: Restore the file from a more recent backup. The string in file ORA-01191 is already offline: cannot be taken offline normally Cause: While trying to take a normal tablespace offline, it was discovered that one of the files in the tablespace was already offline. Action: Bring the data file online first or use another offline tablespace option. ORA-01192 must have at least one thread enabled Cause: At least two redo log files from at least one thread must be specified on the CREATE CONTROLFILE command line. Action: Look for the missing redo log files and retry the command with the newly found redo log files added to the command line. ORA-01193 file string is not the same file seen at the start of recovery Cause: A different copy of the file was accessed the last time recovery media examined the file header. A backup copy of the file was restored or the meaning of the file name was changed during recovery. Action: Verify that the correct file is available and try the recovery again.

3-46

message error

ORA-01194 file chain needs more recovery to be consistent Cause: An incomplete recovery session was started, but not enough records were applied to make the file consistent. The reported file was not closed properly when the database last opened it. It must be recovered to a time when it was not updating. The most likely cause of this error is forgetting to restore the file from a backup before performing a soft recovery. Action: Apply more logs until the file is consistent or restore the file from a previous backup and repeat the recovery. ORA-01195 Online backup of file stream needs more recovery to be consistent Cause: An incomplete recovery session was started, but not enough records were applied to make the file consistent. The reported file is an online backup that needs to be recovered before the backup is complete. Action: Apply more logs until the file is consistent or restore the database files from a previous backup and repeat the recovery. ORA-01196 file string is inconsistent due to media recovery session failure Cause: The file was being recovered, but the recovery did not finish normally. This left the file in an inconsistent state. No other recovery completed successfully on this file. Action: Apply more logs until the file is consistent or restore the backup again and repeat the recovery. ORA-01197 Thread chain contains only one record Cause: During CREATE CONTROL FILE, all threads represented in records must be represented by at least two records. A "last record" and a second record. The named thread is missing two of these records. Action: Find more records for the named thread. Or use the RESETLOGS option to CREATE CONTROL FILE. ORA-01198 Must specify log file size if RESETLOGS Cause: File sizes must be provided for all log files when performing CREATE CONTROLFILE with the RESETLOGS option. User Response: Resubmit the command with the appropriate log file size. File stream ORA-01199 is not in online backup mode. Cause: An attempt was made to end an online backup of a file that currently does not have an online backup. Action: Do not enter the command as it is not required.

ORA-00900 to ORA-01499

3-47

ORA-01200 The actual file size of the string is smaller than the correct size of the string blocks Cause: The file size returned by the operating system is smaller than the file size as indicated in the file header and the control file. Somehow the file got truncated. Perhaps it is the result of an incomplete copy. Action: Restore a good copy of the data file and recover it as necessary. Error writing file string header correctly ORA-01201 Cause: An I/O error was reported for the file header. The error has been detected and a second attempt will be made. Action: The file may need to be recovered. Other error messages will indicate what is needed. ORA-01202 Incorrect incarnation of this file: incorrect creation time Cause: The creation time in the file header is not the same as the creation time in the control file. Most likely it is a copy of a file that has been discarded. Action: Restore a current copy of the data file and recover it as necessary. ORA-01203 Incorrect incarnation of this file: Incorrect build SCN Cause: The build SCN in the file header is not the same as the build SCN in the control file. Most likely it is a copy of a file that has been discarded. Action: Restore a current copy of the data file and recover it as necessary. ORA-01204 file number is a string instead of a string: bad file Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but of the same database. Action: Restore a copy of the correct data file and recover as necessary. ORA-01205 not a data file: the type number in the header is a string Cause: The file type in the header is not correct for a data file. Most likely it is a log file or a control file. If the type is not a non-zero small positive number, the header is corrupted. Action: Restore a copy of the correct data file and recover as necessary. File ORA-01206 is not part of this database: Incorrect database ID Cause: The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a database file. If the database was rebuilt, it could be a pre-rebuilt file. Please note that if you see this error when the file should be connected

3-48

message error

from another database via the Transportable Tablespace feature, it means the database ID in the file header doesn't match what you expect. Action: Restore a copy of the correct data file and recover as necessary. ORA-01207 file is newer than control file - old control file Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can stop it from occurring without correcting the actual problem. Each attempt to open the database will advance the control file change sequence number until it is large enough. Action: Use the current control file or do BACKUP CONTROLFILE RECOVERY to update the control file. Be sure to follow all restrictions when performing a CONTROL FILE BACKUP RECOVERY. The ORA-01208 data file is an old version; the current version is not accessed. Cause: The checkpoint in the file header is less recent than the checkpoint in the control file. If you open a database that is already open by another instance, or if another instance has just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup copy of the file was probably restored while the file was in use. Action: Make the correct file available to the database. Then open the database or run ALTER SYSTEM CHECK DATAFILES. ORA-01209 data file is older than the last RESETLOGS Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If you open a database that is already open by another instance, or if another instance has just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup copy of the file was probably restored while the file was in use. Action: Make the correct file available to the database. Then open the database or run ALTER SYSTEM CHECK DATAFILES. ORA-01210 data file header has bad media Cause: The header block of the file is internally inconsistent. The start of the block has a header with a checksum and other data to ensure block consistency. The last disk write may not have worked correctly. The most likely problem is that this is not a data file for any database.

ORA-00900 to ORA-01499

3-49

Action: Have the operating system make the correct file available to the database. If the trace file dump indicates that only the checksum is bad, restore from a backup and recover from the media. ORA-01211 Oracle7 data file is not from Oracle8 migration Cause: The file is not a copy of the LAST file used in Oracle7. This data file is a backup taken before the migration or Oracle7 opened the database after running the migration utility. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database on Oracle7. Oracle8 can only access data files that were current when the migration was performed. Action: Have the operating system send the correct data file to the database or repeat the migration from Oracle7 to Oracle8. Make sure the database is NOT open after running the migration utility. ORA-01212 MAXLOGMEMBERS cannot exceed string Cause: MAXLOGMEMBERS specified on the command line is too large. Action: Resubmit the command with a lower value for MAXLOGMEMBERS. ORA-01213 MAXINSTANCES cannot exceed string Cause: MAXINSTANCES specified on the command line is too large. Action: Resubmit the command with a lower value for MAXINSTANCES. ORA-01214 MAXLOGHISTORY cannot exceed string Cause: MAXLOGHISTORY specified on the command line is too large. Action: Resubmit the command with a lower value for MAXLOGHISTORY. ORA-01215 Missing string of enabled threads after CREATE CONTROLFILE Cause: A CREATE CONTROLFILE statement was supplied that did not list all enabled threads for the database. Action: Reissue the CREATE CONTROLFILE statement, including all activated threads. Thread chain ORA-01216 expected to be disabled after CREATE CONTROLFILE Cause: A thread provided during CREATE CONTROLFILE is enabled, but the data files indicate that it should be disabled. This is probably because the records supplied to CREATE CONTROLFILE are old (before the thread was exited).

3-50

message error

Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the offending thread, and the thread can be re-created after opening the database if desired. ORA-01217 log file member belongs to a different log file group Cause: A member of a multi-member log file group specified in CREATE CONTROLFILE is not part of the same group as the previous members. Action: Group the correct members for the CREATE CONTROLFILE command. ORA-01218 Log file member is not from the same time Cause: A member of a multi-member log file group is from a different time. One of the specified members can be a previous copy (backup) of the registry. Action: Find the correct version of the registry or leave it out of the CREATE CONTROLFILE command. ORA-01219 database not open: queries allowed only on fixed tables/views Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database was opened. Action: Rephrase the query to include only fixed objects or open the database. ORA-01220 Illegal file-based sort before opening database Cause: A query issued against a fixed table or view required a temporary thread to sort before opening the database. Only in-memory sorts are supported before opening the database. Action: Rerun the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to allow the sort to be done in memory. ORA-01221 data file string is not the same file for a background process. Cause: When the database writer opens the data file, it accesses a different physical file than the one in the foreground and performs recovery. The background did not find the timestamp set in the file header by the foreground. The background process may not have been able to read the file. Action: Look in the DBWR trace file for the error received when trying to read the header of the file. Reconfigure the operating system as necessary for the file name to successfully access the same file when opened by a background process.

ORA-00900 to ORA-01499

3-51

ORA-01222 string MAXINSTANCES requires MAXLOGFILES to be at least string, not string Cause: An attempt was made to create a database or control file that does not have room for at least two records per redo thread. A redo thread must have two logs online to be enabled. It doesn't make sense to allow more redo threads than the logs can support. Action: Reduce the MAXINSTANCES argument or increase the value of MAXLOGFILES. ORA-01223 RESETLOGS must be specified to define a new database name. Cause: The SET database name option was specified for CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed by opening the database with RESETLOGS. Action: Add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE. ORA-01224 The group number in the header string does not match the GROUP string Cause: The group number specified in CREATE CONTROL FILE does not match the group number stored in the header. The specification is probably wrong. Action: Skip the GROUP option or provide the correct one. ORA-01225 thread number string is greater than MAXINSTANCES string Cause: The record is for a thread greater than the MAXINSTANCES argument. Action: Increase the value of MAXINSTANCES and resubmit the command. ORA-01226 log member file header is inconsistent with other members Cause: The log file member in the attached error is for the same group as the previous members, but other fields in the header are different. A file header is corrupted or a file is a member of a deleted record. User Response : Find the correct registry member or omit that member from the command. ORA-01227 log string is not consistent with other logs Cause: The attached error log file is not consistent with the content of other logs provided in the CREATE CONTROLFILE command. A file header is corrupted or some file is an old copy instead of the current version. The problem may not be with the listed registry, as all that can be detected is that there is an inconsistency. All log files listed in the command must be current versions of the online logs. Action: Find the correct online logs or use the RESETLOGS option.

3-52

message error

ORA-01228 SET DATABASE option required to install initial database Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing an initial database. The database does not have a database ID because it is designed to be installed on multiple sites and each site must be a different database with its own database ID. The SET DATABASE and RESETLOGS options must be specified to create the control file for this database. Action: Resubmit the command with the SET DATABASE and RESETLOGS options. ORA-01229 data file string is not consistent with records Cause: The attached error data file is not consistent with the content of the records provided in the CREATE CONTROLFILE command. The most likely cause is one or more missing registers in the command line. It is also possible that one or more records are an old copy instead of the current version. All online log files must be listed in the command and must be the current versions of the online logs. Action: Find the correct online logs or use the RESETLOGS option. ORA-01230 cannot be made read-only: file chain is offline Cause: An attempt to make a tablespace read-only found that one of its files is offline. Action: Bring the file online and try this command again. ORA-01231 cannot read/write: file chain is offline Cause: An attempt to read/write a tablespace found one of its files to be offline. Action: Bring the file online and try this command again. ORA-01232 Unable to start online backup: file string is read-only Cause: An attempt to start an online backup found that one of the files is marked read-only. Read-only files do not need to be set to online backup mode. Action: Perform a backup without the start backup command. ORA-01233 file string is read-only: cannot be recovered using backup control file Cause: An attempt to recover media using a backup control file discovered that one of the files is marked as read-only. Read-only files usually do not need to be recovered, but recovery with a backup control file should recover all files online.

ORA-00900 to ORA-01499

3-53

Action: If the file is truly read-only, take it offline before recovery and bring the read-only tablespace online after opening the database. If the file needs recovery, use an archive to keep track of the time the file was read/written. If the correct control file is not available, use CREATE CONTROLFILE to create one. ORA-01234 cannot finish file chain backup: file is in use or recovering Cause: An attempt was made to finish an online file backup when the file was busy. Some operations like recovery or renaming may be active, or there may still be some instance that has the database open with this online file. Action: If there is an instance with the database open, the backup can be terminated with the ALTER TABLESPACE command. Otherwise, wait for the other operation to complete. ORA-01235 END BACKUP failed for string files and succeeded for string Cause: One or more of the files in an end backup command failed. Some other files given in the same command might have succeeded. Action: Check the attached error messages to find out why the backups could not be completed. All files not listed in the error messages were successful. ORA-01236 An error occurred while initializing file header access Cause: The indicated error occurred while processing file header initialization. Action: The indicated error must be corrected. An attempt is made to recover from this error by using a slower access algorithm. ORA-01237 cannot extend data file string Cause: An operating system error occurred during the resize. Action: Correct the cause of the operating system error and try the command again. ORA-01238 cannot shorten data file string Cause: An operating system error occurred during resize. Action: The error is ignored, the operation continues normally. The ORA-01239 database must be in ARCHIVELOG mode to use the external cache. Cause: An online archive uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery, this cannot be allowed. Action: Change the database to ARCHIVELOG mode or do not use an external cache.

3-54

message error

ORA-01240 Too many data files to add in a single command Cause: The command specifies to add more data files than can be done in a single command. It is necessary to include all file names in one log entry, but that would make the entry too large. Action: If this is a CREATE TABLESPACE command, create with fewer files and add the other files later. If it is an ADD DATA FILE command, break it into multiple commands. ORA-01241 an external cache died Cause: The external cache may have been reset. Action: Take the file referenced to the error stack offline, run media recovery, bring the file online, and retry the operation. You can also restart all instances to ensure that they access all data files through consistent external caches. Data file ORA-01242 media failure: database in NOARCHIVELOG mode Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01243 System table space file media error Cause: A system table space file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01244 Nameless data files added to control file by media recovery Cause: Media recovery with a backup control file or a control file that was rebuilt encountered creating a data file which was not in the control file. Added an entry to the control file for new data files, but with the file name UNNAMEDnnnn, where nnnn is the file number. The attached errors describe the filenames that were originally used to create the files. Action: Rename the files to valid file names and resume recovery. If necessary, the ALTER DATABASE CREATE DATAFILE command can be used to create a suitable file for recovery and renaming. If the file is not retrieved, drop it with the FOR DROP option.

ORA-00900 to ORA-01499

3-55

ORA-01245 Offline file string will be lost if RESETLOGS is performed Cause: An attempt was made to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not dropped with the FOR DROP option. Action: Put the file online and retrieve it, or take it offline with the FOR DROP option. ORA-01246 retrieving files via tablespace chain TSPITR Cause: The files named in the attached errors are backups that were taken prior to the tablespace point-in-time recovery of this tablespace. They cannot be recovered to a point in time after recovery to a point in time. Action: Restore the most recent backups and recover. ORA-01247 database recovery via table space chain TSPITR Cause: A full database recovery was found indicating that there was a time when the table space was recovered. The new version of the files in the tablespace was supposed to be included in the recovery, but this was not done. Action: If the tablespace is not going to be recovered, take its file offline to dispose of it. If you need to recover it, restore or rename it as necessary and start the recovery again. File string ORA-01248 was created in the future of incomplete recovery. Cause: An attempt was made to open RESETLOGS with a file entry in the control file that was originally created after the UNTIL incomplete recovery time. Allowing such input may hide the version of the file that is currently needed. The file number may be in use for a different file that would be lost if RESETLOGS were allowed. Action: If more recovery is desired, redo until the file creation time is reached. If the file is not wanted and the same file number is not in use at the time the recovery is stopped, the file can be dropped with the FOR DROP option. Otherwise, a different control file is needed to allow RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE. ORA-01249 Not allowed to archive to a cloned database Cause: An attempt was made to archive an online redo log or enable archiving for a cloned database.

3-56

message error

Action: Do not try to archive from a clone. The destination of the archived log can easily be the same as the destination of the main database that destroys its archived logs. If archiving is necessary, recreate the database, not as a clone. ORA-01250 A string error occurred while completing file header access Cause: The indicated error occurred while completing file header processing. The error was different from a registry error. Action: The indicated error must be corrected. ORA-01251 Unknown file header version read for file number string Cause: Reading the file header returned a record but its version could not be identified. The header is corrupted or the file is not a valid database file. Action: Have the operating system make the correct file available to the database or retrieve the file. ORA-01252 cannot prevent writes: file string in Recovery Manager backup Cause: An attempt to take a normal or read-only tablespace offline found that a Recovery Manager proxy backup is in progress. If the file goes offline or is read-only, the file header cannot be updated when the backup is complete. Action: Wait for the Recovery Manager backup to complete and try this command again. ORA-01253 unable to start online backup: file string in recovery manager backup Cause: Recovery Manager is backing up the specified file. Action: Wait for the Recovery Manager proxy backup to complete before starting another backup. ORA-01254 unable to complete online backup: file string in recovery manager backup Cause: Recovery Manager is backing up the specified file. Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be started or ended manually. ORA-01255 unable to shutdown: file string in Recovery Manager backup Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress. Action: Wait for the Recovery Manager proxy backup to complete and try this command again.

ORA-00900 to ORA-01499

3-57

ORA-01280 LogMiner fatal error. Cause: One of the following: ■

■

One or more input parameters to the DBMS_LOGMNR.START_LOGMNR() procedure may not be valid. The starting or ending SCN may not be available in the selected log files. The specified dictionary file may be from a different database than the one that generated the log files. LogMiner may have encountered an internal error from which it cannot recover.

Action: Verify that the input parameters are valid. The V$LOGMNR_LOG view can be queried to see the valid SCN ranges for the specified set of log files and the DB_ID of the database that generated the log files. ORA-01281 The SCN range specified in dbms_logmnr.start_logmnr() is invalid Cause: StartSCN may be greater than EndSCN or the specified SCN may not be valid. Action: Specify a valid SCN range. The ORA-01282 date range specified in dbms_logmnr.start_logmnr() is invalid Cause: The specified date value is invalid for the log file. Action: Specify a valid date range. ORA-01283 The specified options are not valid Cause: The specified options are not valid for the procedure. Action: Specify valid options. Cannot open file string ORA-01284 Cause: The specified file cannot be opened. Action: Verify that the file or directory exists and is accessible. ORA-01285 error reading string from file Cause: The file or directory may not exist or be accessible. Action: Specify a valid file or directory. Make sure the file and directory are accessible.

3-58

message error

ORA-01286 Cannot add file string due to DB_ID mismatch Cause: The log file is produced by a different database than other log files already added to the list. User Response : Specify a log file produced by the same database. ORA-01287 Reset SCN for file string does not match other log files specified for this LogMiner session ORA-01288 Reset count for file string does not match other log files specified for this LogMiner session ORA-01289 cannot add duplicate log file string Cause: The specified log file has already been added to the log file list. User Response : Specify a different log file. ORA-01290 cannot delete unlisted log file string Cause: The user attempted to delete a unlisted log file. User Response: Specify a valid log file in the DBMS_LOGMNR.ADD_LOGFILE() procedure. ORA-01291 Missing log file ORA-01292 No log file specified for the current LogMiner session Cause: No log file was specified for the LogMiner session. User Response : Specify at least one log file. ORA-01293 SCN or time range is not fully contained in the log files listed Cause: The input SCN/date range is not fully contained in the log files specified for the session. Action: Select out of the V$LOGMNR_LOGS view to verify the date range or SCN covered by the log files specified for the LogMiner session and reissue the START_LOGMNR() procedure with the appropriate date range or SCN. ORA-01294 error occurred while processing information in dictionary file string, possible corruption ORA-01295 DBID mismatch between dictionary string and log files Cause: Dictionary file is produced by a different database to the one generated through the log files. Action: Specify a compatible dictionary file.

ORA-00900 to ORA-01499

3-59

ORA-01296 Charset mismatch between dictionary string and log files Cause: The database charset that generated the dictionary file is different from the database charset that generated the files register. Action: Specify a dictionary file with the same character set. ORA-01297 Redo version mismatch between dictionary chain and log files ORA-01298 LowSCN mismatch between dictionary chain and previous log file ORA-01299 ResetSCN mismatch between dictionary chain and log file previous previous log file ORA-01301 dbms_logmnr.USE_COLMAP can only be used with a valid dictionary Cause: DBMS_LOGMNR.USE_COLMAP can only be used with a valid dictionary. Action: Specify the dictionary file in DBMS_LOGMNR.START_LOGMNR(). ORA-01302 syntax error in logmnr.opt file The ORA-01303 schema string specified in the logmnr.opt file does not exist Cause: The specified schema does not exist. User Response : Please specify a correct schema or compatible dictionary file. ORA-01304 table string, schema string, specified in logmnr.opt file, does not exist ORA-01305 column string, specified in logmnr.opt file, does not exist in table string, schema string ORA-01306 dbms_logmnr.start_logmnr() must be called before selecting v$logmnr_contents Cause: A select was issued from V$LOGMNR_CONTENTS without first calling the DBMS_LOGMNR.START_LOGMNR() procedure. Action: Call the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view. ORA-01307 No LogMiner session is currently active Cause: A select was issued from V$LOGMNR_CONTENTS without first calling the DBMS_LOGMNR.START_LOGMNR() procedure. Otherwise, DBMS_LOGMNR.END_LOGMNR() was called without a prior call to DBMS_LOGMNR.START_LOGMNR() or DBMS_LOGMNR.ADD_LOGFILE() Action: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view.

3-60

message error

ORA-01400 cannot insert NULL into (string) Cause: An attempt was made to insert a NULL into column "USER".."TABLE".."COLUMN". For example, if you type: connect scott/tiger create table a (a1 number not null); insert into a value (null);

Oracle returns: ORA-01400 cannot insert NULL into ("SCOTT"."A"."A1"): which means that it cannot insert NULL into "SCOTT"."A"."A1".

User Response : Repeat the operation with a non-null value. ORA-01401 The value entered is too large for the column Cause: The value entered is greater than the maximum width defined for the column. User Response : Enter a value less than the column width or use the MODIFY option with ALTER TABLE to expand the column width. ORA-01402 view WITH CHECK OPTION where clause violation Cause: An INSERT or UPDATE statement was attempted on a view created with CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the WHERE clause of the view. Action: Examine the WHERE clause of the view in the VIEWS dictionary table. If the current view does not have a CHECK OPTION, its FROM clause must refer to a second view defined using the CHECK OPTION. The WHERE clause of the second view must also be satisfied by any INSERT or UPDATE statement. To insert the row, you may need to insert it directly into the underlying table instead of through the view. ORA-01403 no data found Cause: In a host language program, all records were retrieved. The get return code was +4, indicating that all records were returned from the SQL query. Action: End the processing of the SELECT statement.

ORA-00900 to ORA-01499

3-61

ORA-01404 ALTER COLUMN will make the index too large Cause: Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum length of the index (255). The total length of the index is calculated as the sum of the width of all the indexed columns plus the number of indexed columns. Date fields are calculated with a length of 7, character fields are calculated with their defined width, and numeric fields are calculated with a length of 22. Action: The only way to change the column is to drop the affected index. The index cannot be rebuilt if it exceeds the maximum width of the index. ORA-01405 The value of the retrieved column is NULL Cause: The INTO clause of a FETCH operation contained a NULL value and no pointers were used. The column buffer in the program remained unchanged and the cursor return code was +2. This is an error unless you are running Oracle with DBMS=6, emulating version 6, in which case it is just a warning. Action: You can do any of the following: ■

■

Use the NVL function to convert the retrieved NULL to another value, such as zero or blank. This is the simplest solution. Use a flag to record the presence of NULL. You should probably use this option when you want a specific action to be taken when a NULL occurs. Review the cursor definition so that columns that possibly contain NULLs are not retrieved.

ORA-01406 The value of the retrieved column was truncated Cause: In a host language program, a FETCH operation was forced to truncate a string. The program's buffer area for this column was not large enough to hold the entire string. The search cursor return code was +3. Action: Increase the area of the column buffer to hold the largest column value, or do other appropriate processing. ORA-01407 cannot update (string) to NULL Cause: An attempt was made to update a column in table "USER","TABLE","COLUMN" with a NULL value. For example, if you write: connect scott/tiger's update table to (number a1 is not null);

3-62

message error

insert into a value (null);

Oracle returns: ORA-01407 cannot update ("SCOTT".."A".."A1") to NULL

which means you can't update column "SCOTT", "A", "A1" to NULL. User Response : Repeat the operation with a non-null value. ORA-01408 such column list is already indexed Cause: A CREATE INDEX statement specified a column that is already indexed. A single column can only be indexed once. Additional indexes can be created on the column if it is used as part of a concatenated index, that is, if the index consists of multiple columns. Action: Do not try to reindex the column, as it is not necessary. To create a concatenated key, specify one or more additional columns in the CREATE INDEX statement. The ORA-01409 NOSORT option cannot be used; rows are not in ascending order Cause: Index created with NOSORT option when rows were not in ascending order. The NOSORT option can only be used for indices on rowgroups that are already in ascending order. For non-unique indexes, the ROWID is considered part of the index key. This means that two lines that appear to be stored in ascending order may not be. If you create a NOSORT index and two of the rows in the table have the same index values but are split across two extents, the data block address of the first block in the second extent can be less than the data block address of the second extent. last block in the first stretch. If these addresses are not in ascending order, neither are the ROWIDs. Because these ROWIDs are considered part of the index key, the index key is not in ascending order and the NOSORT index creation fails. Action: Create the index without the NOSORT option or make sure the table is stored in an extent. ORA-01410 Invalid ROWID Cause: A ROWID was entered incorrectly. ROWIDs must be entered as hexadecimal strings formatted using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'. Action: Check the format and enter the ROWID using the correct format. ROWID Format: Block ID, Line in Block, File ID.

ORA-00900 to ORA-01499

3-63

ORA-01411 unable to store column length in pointer Cause: An attempt was made to get a column with a size greater than 64K and the length of the column could not be stored in the given pointer of size 2 bytes. Action: Use the new hook type with callbacks to retrieve the long column. ORA-01412 Zero length not allowed for this data type Cause: The length for type 97 is 0. Action: Specify the correct length. ORA-01413 Illegal value in packed decimal number buffer Cause: The user buffer bound by the user as packed decimal number contained an illegal value. Action: Use a legal value. ORA-01414 Invalid array length when attempting to bind array Cause: An attempt was made to bind an array without a current array length pointer or a maximum array length of zero. Action: Specify a valid length. ORA-01415 Too many distinct aggregate functions Cause: The query contains more distinct aggregates than can be processed. The current limit is 255. Action: Reduce the number of distinct aggregate functions in the query. ORA-01416 two tables cannot be an outer join Cause: Two tables in a join operation specified an outer join with each other. If an outer join is specified on one of the tables in a join condition, it cannot be specified on the other table. User Response : Remove the outer join specification (+) from one of the tables and retry the operation. ORA-01417 A table can be outer joined to a maximum of another table. Cause: a.b (+) = b.b and a.c (+) = c.c are not allowed. Action: Check that this is really what you want, then a b and c first in a single view. ORA-01418 The specified index does not exist Cause: An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that does not exist. Only existing key figures can be included.

3-64

message error

modified, discarded or validated. Existing indices can be enumerated by querying the data dictionary. Action: Specify the name of an existing index in the ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement. ORA-01419 datdts: invalid format code Cause: An attempt was made to use an incorrect format. Action: Inspect the format, correct it if necessary, and try the operation again. ORA-01420 datstd: invalid format code Cause: An attempt was made to use an invalid format. Action: Inspect the format, correct it if necessary, and try the operation again. ORA-01421 datrnd/dattrn: invalid precision specifier Cause: An attempt was made to use an invalid precision specifier. Action: Inspect the precision specifier, correct it if necessary, and retry the operation. ORA-01422 exact search returns more than requested number of rows Cause: The number specified in the exact search is less than the rows returned. Action: Rewrite the query or change the number of rows requested. ORA-01423 error encountered while searching for extra lines in exact search Cause: An error was encountered while performing an exact search. This message will be followed by more descriptive messages. Action: View the attached messages and take appropriate action. ORA-01424 Missing or invalid character after the escape character Cause: Missing character after the escape character in the LIKE pattern or none of the escape characters, '%' or '_'. Action: Remove the escape character or specify the missing character. ORA-01425 escape character must be a string of length 1 Cause: The escape character supplied for LIKE is not a string of length 1. Action: Change it to a string of length 1. Numeric overflow ORA-01426 Cause: Evaluating a value expression causes an overflow/underflow.

ORA-00900 to ORA-01499

3-65

Action: Shorten the operands. ORA-01427 Single row subquery returns more than one row Cause: The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row. Action: Use ANY, ALL, IN, or NOT IN to specify which values to compare, or rephrase the query so that only one row is retrieved. ORA-01428 Argument 'string' is out of range Cause: An invalid value was specified for the argument of a mathematical function. For example, SELECT SQRT(-1) ”Square Root” FROM DUAL;

Action: See the Oracle8i SQL reference manual for valid math function inputs and ranges. ORA-01429 Table organized by index: no data segment to store parts of overflow rows Cause: No overflow segment defined. Action: Add overflow segment. The ORA-01430 column being added already exists in the table Cause: An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table. Action: Specify a unique name for the new column and run the statement again. ORA-01431 GRANT command internal inconsistency Cause: An internal error occurred while attempting to execute a GRANT statement. Action: Contact Oracle Customer Support. ORA-01432 The public synonym to drop does not exist Cause: The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It can be a private synonym. Action: Correct the synonym name or use DROP SYNONYM if the synonym is not public.

3-66

message error

ORA-01433 the synonym to be created is already defined. Cause: A CREATE SYNONYM statement specified a synonym name that is the same as an existing synonym, table, view, or cluster. Synonyms cannot have the same name as any other synonym, table, view, or cluster available to the user creating the synonym. Action: Specify a unique name for the synonym and rerun the statement. ORA-01434 Private synonym to drop does not exist Cause: A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names can be listed by querying the data dictionary. Action: Specify the name of an existing synonym in the DROP SYNONYM statement. User ORA-01435 does not exist Cause: This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that does not exist. Only a GRANT CONNECT statement can specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, the usernames must already exist. Action: Specify only existing usernames in the SELECT, GRANT, or REVOKE statement, or ask the database administrator to define the new username. ORA-01436 CONNECT BY loop in user data Cause: The condition specified in a CONNECT BY clause caused the query to loop where the next record to be selected is a descendant of itself. When that happens, there can be no end to the query. User Response: Check the CONNECT BY clause and remove the circular reference. ORA-01437 cannot join with CONNECT BY Cause: A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause is used in a SELECT statement for a tree-structured query, only one table can be referenced in the query. Action: Remove the CONNECT BY clause or join operation from the SQL statement. ORA-01438 value greater than the specified precision allowed for this column Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.

ORA-00900 to ORA-01499

3-67

Action: Enter a value that matches the precision of the numeric column, or use the MODIFY option with the ALTER TABLE command to expand the precision. ORA-01439 Column to be modified must be empty to change data type Cause: An ALTER TABLE MODIFY statement attempted to change the data type of a column that contains data. A column whose data type is to be changed must only contain NULL values. User Response : To change the data type, first set all values in the column to NULL. ORA-01440 Column to be modified must be empty to decrease precision or scale Cause: An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. To decrement any of these values, the column must only contain NULL values. An attempt to increase the scale without also increasing the precision will also generate this message. User Response: Set all column values to NULL before decreasing the numeric precision or scale. If you try to scale up, either increase the precision by scale or set all values in the column to NULL first. ORA-01441 Column to be modified must be empty to reduce column length Cause: An ALTER TABLE MODIFY statement attempted to reduce the size of a character field containing data. A column whose maximum size is to be reduced must only contain NULL values. User Response: Set all column values to NULL before decreasing the maximum size. Column ORA-01442 to be modified to NOT NULL is already NOT NULL Cause: An ALTER TABLE MODIFY statement unnecessarily attempted to change a column specification from NOT NULL to NOT NULL. Action: No action is required. ORA-01443 internal inconsistency; Invalid data type in resulting view column Cause: An internal error occurred while referencing a view. Action: Contact Oracle Customer Support. ORA-01444 internal inconsistency; internal data type is mapped to an invalid external type Cause: This is an internal error message that is not normally thrown. Action: Contact Oracle Customer Support.

3-68

message error

ORA-01445 cannot select ROWID from a join view without a key-preserved table Cause: A SELECT statement attempted to select ROWID from a view derived from a join operation. Since the selected rows in the view do not match the underlying physical records, ROWID cannot be returned. Action: Remove ROWID from the view select clause and re-execute the statement. ORA-01446 cannot select view ROWID with DISTINCT, GROUP BY, etc. Cause: A SELECT statement attempted to select a ROWID from a view that contained columns derived from functions or expressions. Since the selected rows in the view do not match the underlying physical records, ROWID cannot be returned. Action: Remove ROWID from the view select clause and re-execute the statement. ORA-01447 ALTER TABLE does not work on grouped columns Cause: An ALTER TABLE MODIFY statement specified a column used to group the table. Grouped columns cannot be changed. User Response : To modify the column, first re-create the table in nonclustered format. The column size can be increased at the same time. The ORA-01448 index must be removed before changing to the desired type. Cause: An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the LONG data type cannot be indexed, so the index must be dropped before the modification. Action: Drop all indexes that reference the column before changing its data type to LONG. Column ORA-01449 contains NULL values; cannot be changed to NOT NULL Cause: An ALTER TABLE MODIFY statement attempted to change the definition of a column that contains NULL values to NOT NULL. The column cannot contain any NULL values if it is changed to NOT NULL. User Response: Set all NULL values in the column to non-NULL values before ALTERING the column to NOT NULL. ORA-01450 maximum key (string) length exceeded Cause: The combined length of all columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum length of the index varies by operating system. The total length of the index is calculated as the sum of

ORA-00900 to ORA-01499

3-69

the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have a defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1. Action: Select the columns to be indexed so that the total length of the index does not exceed the maximum index length for the operating system. See also the Oracle documentation specific to the operating system. ORA-01451 column to be modified to NULL cannot be modified to NULL Cause: The column may already allow NULLs, the NOT NULL constraint is part of a primary key or check constraint, or an ALTER TABLE MODIFY statement attempted to change a specification unnecessarily from NULL to NULL. Action: If a primary key or check constraint enforces the NOT NULL constraint, remove that constraint. ORA-01452 cannot CREATE UNIQUE INDEX; duplicate keys found Cause: A CREATE UNIQUE INDEX statement specified one or more columns that currently contain duplicate values. All values in the indexed columns must be unique per row to create a UNIQUE INDEX. Action: If the entries are not required to be unique, remove the UNIQUE keyword from the CREATE INDEX statement, and then run the statement again. If the entries must be unique, such as in a primary key, remove duplicate values before creating the UNIQUE index. ORA-01453 SET TRANSACTION must be the first statement in the transaction Cause: A transaction was not processed successfully because the SET TRANSACTION statement was not the first statement. Action: Commit or roll back the current transaction before using the SET TRANSACTION statement. ORA-01454 Cannot cast column to a numeric data type Cause: A non-numeric value could not be cast to a numeric value. Action: Check the value to make sure it contains only numbers, a sign, a decimal point, and the character "E" or "e", then try the operation again. ORA-01455 integer data type column overflow conversion Cause: The converted format of the specified expression was too large for the specified data type.

3-70

message error

Action: Set a larger data type or correct the data. ORA-01456 might not perform insert/delete/update operation within a READ-ONLY transaction Cause: A non-DDL insert/delete/update operation or select-for-update was attempted. Action: Commit (or roll back) the transaction and run it again. ORA-01457 cast column data type overflow Decimal Cause: The cast form of the specified expression was too large for the specified type. The problem also occurs in COBOL programs when COMP-3 is used in the image clause, which is acceptable to the Pro*COBOL precompiler and to COBOL, but results in this error. Action: Set a larger data type or correct the data. ORA-01458 invalid length within string variable Cause: An attempt was made to bind or set a string variable with a buffer length less than the minimum requirement. Action: Increase the buffer size or use a different type. ORA-01459 invalid length for variable string Cause: The buffer length was less than the required minimum or greater than its length at bind time minus two bytes. Action: Make sure the length of the string is long enough to contain the buffer. ORA-01460 Requested conversion unreasonable or not implemented Cause: The requested format conversion is not supported. Action: Remove the requested cast from the SQL statement. Check the syntax of the TO_CHAR, TO_DATE, and TO_NUMBER functions to see which conversions are supported. ORA-01461 can bind a LONG value only to insert it into a LONG column Cause: An attempt was made to insert a value of a LONG data type into another data type. This is not allowed. Action: Do not try to insert LONG data types into other column types. ORA-01462 cannot insert string literals longer than 2000 characters Cause: The longest literal supported by Oracle is 2000 characters.

ORA-00900 to ORA-01499

3-71

Action: Reduce the number of characters in the literal to 2000 characters or less, or use the VARCHAR2 or LONG data type to input strings that exceed 2000 characters. ORA-01463 cannot modify data type of column with current constraints Cause: An attempt was made to modify the data type of the column that has referential constraints; or you have check constraints that only allow you to change the data type from CHAR to VARCHAR or vice versa. Action: Remove the constraint(s) or do not perform the offending operation. ORA-01464 circular grant (grant to grant ancestor) of table or view Cause: The user in the TO clause of the GRANT statement has already been granted GRANTed privileges on this table. Action: Do not grant privileges on a table to the user who originally granted privileges on that table. The misstatement is probably unnecessary. ORA-01465 invalid hexadecimal number Cause: In an UPDATE statement after a SELECT FOR UPDATE, part of the ROWID contains invalid characters. ROWID must be expressed in the proper format expected for ROWID and enclosed in quotation marks. Action: Insert the ROWID exactly as it was returned in SELECT TO UPDATE. ORA-01466 could not read data: table definition changed Cause: This is a time-based read consistency error for a database object, such as a table or index. Any of the following could have happened: ■

■

The query was parsed and executed with a snapshot before the time the object was changed. The object's creation timestamp is greater than the current system time. This happens, for example, when the system time is set to a time before the object's creation time.

Action: If the cause is: ■

a previous snapshot, commit or roll back the transaction, and resume work.

■

a creation timestamp in the future, make sure the system time is set correctly.

If the object creation timestamp is still greater than system time, export the object data, drop the object, re-create the object so that it has a new creation timestamp, import the object data, and resume work.

3-72

message error

ORA-01467 sort key too long Cause: A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a larger sort key than is supported by Oracle. Too many columns or too many group functions were specified in the SELECT statement. Action: Reduce the number of columns or group functions involved in the operation. ORA-01468 a predicate can refer to only one outer join table Cause: A predicate in the WHERE clause has two columns from different tables with "(+)". User Response: Change the WHERE clause so that each predicate has at most one outer join table. ORA-01469 PRIOR can only be followed by a column name Cause: An invalid column name was specified after the PRIOR keyword. Action: Check the syntax, the spelling, use a valid column name, and try again. ORA-01470 List iteration does not support mixed operators Cause: Constants of different types are specified in a list. Action: Use constants of the same type for lists. ORA-01471 cannot create a synonym with the same name as the object Cause: An attempt was made to create a private synonym with the same name as the object it refers to. This error usually occurs when a user tries to create a private synonym with the same name as one of her objects. Action: Choose a different synonym name or create the synonym with a different username. ORA-01472 cannot CONNECT BY the view with DISTINCT, GROUP BY, etc. Cause: CONNECT BY cannot be used on a view where the output rows do not match the rows in the underlying table. User Response: Remove DISTINCT or GROUP BY from the view or move the CONNECT BY clause to the view. ORA-01473 cannot have subqueries in CONNECT BY clause Cause: Subqueries cannot be used in a CONNECT BY clause. Action: Delete the subquery or move it to the WHERE clause.

ORA-00900 to ORA-01499

3-73

ORA-01474 cannot have BEGIN WITH or PRIOR without CONNECT BY Cause: BEGIN WITH and PRIOR only make sense in relation to CONNECT BY. Action: Check the syntax of the SQL statement and add a CONNECT BY clause if necessary. ORA-01475 must reparse cursor to change data type of bind variable Cause: After executing a statement, an attempt was made to rebind a bind variable with a different data type than the original bind. Action: Reparse the cursor before rebinding it with a different data type. ORA-01476 divisor equals zero Cause: An expression attempted to divide by zero. Action: Correct the expression and repeat the operation. ORA-01477 User data area descriptor is too large Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support. ORA-01478 The bind array might not include any LONG columns Cause: The user is executing a bind array with a bind variable whose maximum length is greater than 2000 bytes. Action: These bind variables cannot participate in array binds. Instead, use a common bind operation. ORA-01479 Last character in buffer is not null Cause: A type 97 binding variable does not contain a null value in the last position. Action: Make the last character null. ORA-01480 trailing null STR bind value missing Cause: A type 5 (null-terminated string) bind variable does not contain the terminating null in its buffer. Action: Terminate the string with a null character. ORA-01481 invalid number format template Cause: An invalid format parameter was used with the TO_CHAR or TO_NUMBER function. Action: Correct the syntax and retry the operation.

3-74

message error

ORA-01482 unsupported character set Cause: The second or third parameter of the CONVERT function is not a supported character set. Action: Use one of the supported character sets. kkORA-01484 Arrays can only be bound to PL/SQL statements Cause: An attempt was made to bind an array to a non-PL/SQL statement. Action: Rewrite the offending code, taking care to only bind arrays to PL/SQL statements. ORA-01485 The length of the compile link is different from the length of the execute link Cause: You bound a buffer of type DTYVCS (VARCHAR with a length of two bytes in front) and, at run time, the length of the first two bytes is greater than the maximum length of the buffer, given in the binding call. The number of elements in the array and the current number of elements in the array cannot be greater than the maximum size of the array. Action: Make sure the buffer size is large enough to hold the array plus two bytes for the buffer size. ORA-01486 array element size is too large Cause: An attempt was made to bind a data value that was too large for the data type, for example, NUMBER, or greater than 2000 bytes, for example, VARCHAR or LONG. Action: Find a way to convert or truncate the data value so that its length is acceptable. ORA-01487 Packed decimal is too large for the given buffer Cause: A conversion request cannot be performed because the buffer is too small to hold the result. Action: Increase the size of the buffer. ORA-01488 Invalid nibble or byte in input data Cause: A conversion request could not be performed because a digit was invalid. Action: Correct the number and try again. ORA-01489 String concatenation result is too long Cause: String concatenation result is longer than the maximum length. Action: Make sure the result is less than the maximum size.

ORA-00900 to ORA-01499

3-75

Invalid ANALYZE command ORA-01490 Cause: The syntax of the ANALYZE command was incorrect. Action: Check the syntax and enter the command using the correct syntax. ORA-01491 Invalid CASCADE option Cause: The CASCADE option should only be used for tables or clusters. Action: Do not use the CASCADE option in this way. Please check the syntax of the declaration and try again. ORA-01492 Invalid LIST option Cause: The LIST option can only be used for tables or clusters. Action: Do not use the LIST option in this way. Please check the syntax of the declaration and try again. ORA-01493 Invalid SAMPLE size specified Cause: Specified SAMPLE size is out of range Action: Specify a value within the appropriate range. ORA-01494 Invalid specified SIZE Cause: The specified histogram SIZE value was out of range. Action: Specify a value within the appropriate range. ORA-01495 No row table found for the specified string Cause: The specified table does not exist or the user does not have the appropriate privileges. Action: Specify the correct table to use. ORA-01496 An incorrect string row table form was specified. Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. ORA-01497 invalid option for ANALYZE CLUSTER Cause: The FOR COLUMNS column_list clause cannot be used with ANALYZE CLUSTER. Action: Try again with a valid syntax. For more information on ANALYZE CLUSTER, see the Oracle8i SQL Reference.

3-76

message error

ORA-01498 Block verification failed; see trace file Cause: An error occurred while verifying a block with the ANALYZE command. Action: Search the trace file for more descriptive messages about the problem. Correct these errors. The trace file name is specific to the operating system, for example, ORAxxxx.TRC. It is located in the directory specified by the USER_DUMP_DEST initialization parameter. If USER_DUMP_DEST is not set, trace files will not be created. It may be necessary to recreate the object. See also the Oracle documentation specific to the operating system. ORA-01499 table/index cross reference error: see trace file Cause: An error occurred while validating an index or table with the ANALYZE command. One or more entries do not point to the proper cross reference. Action: Search the trace file for more descriptive messages about the problem. Correct these errors. The trace file name is specific to the operating system, for example, ORAxxxx.TRC. It is located in the directory specified by the USER_DUMP_DEST initialization parameter. If USER_DUMP_DEST is not set, trace files will not be created. It may be necessary to recreate the object. See also the Oracle documentation specific to the operating system.

ORA-00900 to ORA-01499

3-77

3-78

message error

4 ORA-01500 to ORA-02099 ORA-01500 error getting date/time Cause: During CREATE DATABASE or ALTER TABLESPACE, the date and time could not be obtained. Action: Contact Oracle Customer Support. ORA-01501 CREATE DATABASE failed Cause: An error occurred during CREATE DATABASE. Action: Check the attached errors. ORA-01502 Index 'string.string' or the partition of that index is in an unusable state Cause: An attempt was made to access an index or index partition that was marked unusable by a direct load or DDL operation. Action: DROP the specified index or REBUILD the specified index or REBUILD the unusable index partition. ORA-01503 CREATE CONTROL FILE failed Cause: An error occurred during CREATE CONTROL FILE. Action: Check the attached errors. ORA-01504 Database name 'string' does not match db_name parameter 'string' Cause: The name in a created or mounted database does not match the name given in the DB_NAME initialization parameter. Action: Correct or omit one of the two names. ORA-01505 error adding log files Cause: During CREATE or ALTER DATABASE, errors occurred while adding new log files.

ORA-01500 to ORA-02099 4-1

Action: Check the error stack for detailed information about the errors. ORA-01506 Missing or invalid database name Cause: No database name was specified in the CREATE/ALTER DATABASE statement and no initialization parameter DB_NAME was specified. Action: The database name must be provided in the DB_NAME statement or in the initialization parameter. Note that the SVRMGR or SQL*PLUS STARTUP command issues an ALTER DATABASE statement using the database name specified as part of the START (if applicable). ORA-01507 Database not mounted Cause: An attempt was made to execute a command that requires the database to be mounted. Action: If you are using the ALTER DATABASE statement through the SVRMGR or SQL*PLUS STARTUP command, specify the MOUNT option to restart; otherwise, if you are directly performing ALTER DATABASE DISMONTT, do nothing; otherwise, specify the MOUNT option for ALTER DATABASE. If you are performing a backup or copy, you must first mount the desired database. ORA-01508 cannot create the database; error in file 'string' at line string Cause: CREATE DATABASE could not process the specified file. Action: Check the offending line in the specified file. ORA-01509 The name specified 'string' does not match the actual 'string' Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database. Action: Correct the spelling of the database name or UNMOUNT the mounted database. ORA-01510 error dropping log files Cause: During ALTER DATABASE, an error occurred while dropping log files. Action: Check the error stack for detailed information about the errors. ORA-01511 error renaming log/data files Cause: During ALTER DATABASE, an error occurred while renaming logs or data files. Action: Check the error stack for detailed information about the errors.

4-2

message error

ORA-01512 error renaming log file string: New file string not found Cause: An attempt to rename a log file in the control file failed because no file with the new name. Action: Make sure the operating system has successfully renamed the log file and try again. ORA-01513 Invalid current time returned by the operating system Cause: The operating system returned a time that was not between 1988 and 2121. Action: Correct the time maintained by the operating system. Record specification ORA-01514 error: no record Cause: A record file name or list of member names does not match an existing record. User Response : Specify an existing log file. ORA-01515 error dropping log group string: no log Cause: ALTER DATABASE is trying to delete a log file that is not known to the database control file. Action: Specify the name of an existing log file. ORA-01516 Missing log file, data file, or temporary file 'string' Cause: An attempt was made to use ALTER DATABASE to rename a log file or data file or change the attributes of a data file or a temporary file. The attempt failed because the specified file is not known to the database control file or is not a supported type for the request. Action: Specify the name of an existing file of the correct type. ORA-01517 log member: 'string' Cause: This message indicates the file name related to other messages. Action: View the attached messages and take appropriate action. ORA-01518 CREATE DATABASE must specify more than one log file Cause: Only one log file was specified in the CREATE DATABASE statement. Action: Specify at least two log files. ORA-01519 error processing file 'string' near line string Cause: CREATE DATABASE encountered a problem processing the specified file. The specified file is invalid.

ORA-01500 to ORA-02099 4-3

Action: Repeat the system installation procedure or contact Oracle Customer Support. ORA-01520 The number of data files to add (string) exceeds the string limit Cause: The CREATE TABLESPACE statement specifies more files than are allowed for this database. Action: Use fewer files or rebuild the database with a larger MAXDATAFILES value. ORA-01521 error adding data files Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files. Action: Check the error stack for detailed information about the errors. ORA-01522 Rename file 'string' does not exist Cause: During ALTER TABLESPACE RENAME, a rename file was not found in the database control file. Action: Specify the correct file name. ORA-01523 cannot rename data file to 'string'; the file is already part of the database Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file. Action: Change the name of the file to a name that is not being used as part of the database. ORA-01524 cannot create data file as 'string': file is already part of database Cause: During ALTER DATABASE CREATE DATAFILE, a new file name is already present in the control file. Action: Create the file with a name that is not already in use as part of the database. ORA-01525 error renaming data files Cause: An error occurred while renaming files as part of ALTER TABLESPACE. Action: Check the error stack for detailed information. All files except those mentioned in the error stack are renamed. ORA-01526 error opening file 'string' Cause: CREATE DATABASE could not open the specified file. It is most likely due to a system installation error.

4-4

message error

Action: Repeat the system installation procedure or contact Oracle Customer Support. ORA-01527 error reading file Cause: CREATE DATABASE could not read the specified file. It is most likely due to a system installation error. Action: Repeat the system installation procedure or contact Oracle Customer Support. ORA-01528 EOF while processing SQL statement Cause: CREATE DATABASE hit EOF unexpectedly while reading the specified file. The SQL.BSQ file is invalid. Action: Repeat the system installation procedure or contact Oracle Customer Support. ORA-01529 error closing file 'string' Cause: CREATE DATABASE could not close the specified file. Action: Repeat the system installation procedure or contact Oracle Customer Support. ORA-01530 a database already mounted by the instance Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance where a database is or was previously mounted. Action: If you want to mount the database, shutdown and restart the instance and try the operation again. ORA-01531 a database already opened by the instance Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which a database already exists. Action: If you want to open a new database on the instance, first shutdown and restart the instance and try the operation again. ORA-01532 cannot create the database; instance started elsewhere Cause: During CREATE DATABASE, another user seems to be changing the instance simultaneously. Action: Make sure no one else is changing the instance at the same time. If no one is, contact Oracle Customer Support; otherwise, repeat the operation.

ORA-01500 to ORA-02099 4-5

ORA-01533 cannot rename file 'string'; file does not belong to table space Cause: During ALTER TABLESPACE RENAME, a file to rename was not found in the argument table space. User Response : Specify the correct file name or table space name. ORA-01534 Rollback segment 'string' does not exist Cause: During ALTER or DROP ROLLBACK SEGMENT, the name of the specified rollback segment is unknown. User Response : Use the correct rollback segment name. ORA-01535 Rollback segment 'string' already exists Cause: The specified rollback segment already exists. Action: Use a different name. ORA-01536 Space quota for table space 'string' was exceeded Cause: The space quota for the slice owner in the table space was exhausted and the operation attempted to create a new slice extent in the table space . Action: Drop unnecessary objects into the tablespace to reclaim space, or have a privileged user increase the quota on this tablespace for the segment owner. ORA-01537 cannot add data file 'string': file is already part of the database Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database. Action: Use a different file name. ORA-01538 Failed to acquire any rollback segments Cause: Failed to acquire any rollback segments when starting in shared mode. Action: Reboot in exclusive mode to create one more public segment or specify the available private segments in the initialization parameter. ROLLBACK_ SEGMENTS_REQUIRED, so start in shared mode ORA-01539 table space 'string' is not online Cause: Could not make a table space read-only or offline because it is not online. A tablespace must be online before it can be read-only or normal offline.

4-6

message error

Action: Check the status of the tablespace. Use the IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read-only. ORA-01540 table space 'string' is not offline Cause: A table space could not be brought online because it is not offline. Action: Check the status of the tablespace. System tablespace ORA-01541 cannot be taken offline; shut it down if necessary Cause: An attempt was made to disconnect the tablespace from the system. Action: Power off if necessary to perform recovery. ORA-01542 table space 'string' is offline, space cannot be allocated Cause: An attempt was made to allocate space in an offline table space. Action: Bring the tablespace online or create the object in another tablespace. ORA-01543 tablespace 'string' already exists Cause: An attempt was made to create a tablespace that already exists. Action: Use a different name for the new table space. ORA-01544 unable to drop system rollback thread Cause: An attempt was made to drop the system rollback thread. Action: No action is required. The specified ORA-01545 rollback segment 'string' is not available Cause: One of the following: 1.

An attempt was made to bring a rollback segment online that is not available during initialization; for example, the rollback segment is in an offline tablespace.

An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file, or the rollback segment is already online by another instance.

An attempt was made to drop a rollback thread that is currently online.

An attempt was made to change a rollback thread that is currently online to use unlimited extensions.

Action: One of the following:

ORA-01500 to ORA-02099 4-7

Make the rollback segment available; for example, bring an offline tablespace online.

Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment.

Disconnect the rollback thread first. This might involve waiting for active transactions to complete or, if the rollback thread needs recovery, finding out what errors are preventing transactions from rolling back and taking appropriate action.

Same as 3).

ORA-01546 table space contains active rollback segment 'string' Cause: An attempt was made to make a table space offline or read-only that contains active rollback segments. Action: Terminate the instances that are using the active rollback segments in the tablespace, then make the tablespace offline or read-only. Warning ORA-01547: RECOVERY was successful but OPEN RESETLOGS would get the following error Cause: Media recovery with one of the incomplete recovery options completed without error. However, if the ALTER DATABASE OPEN RESETLOGS command were tried now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more data files from a sufficiently old backup before performing a soft recovery. Action: Rerun the incomplete media recovery using different data file backups, a different control file, or different stop criteria. ORA-01548 Active rollback segment 'chain' found, terminate table space drop Cause: An attempt was made to drop a table space that contains active rollback segments. Action: Terminate the instances that are using the active rollback segments in the table space, and then drop the table space. ORA-01549 non-empty tablespace, use INCLUDE CONTENT option Cause: An attempt was made to drop a non-empty tablespace. Action: To place all objects in the tablespace, use the INCLUDING CONTENT option.

4-8

message error

ORA-01550 unable to drop system table space Cause: An attempt was made to drop the system table space. This is not allowed. Action: No action is required. ORA-01551 Rollback segment extended, pinned blocks released Cause: Rollback segment extending recursively, caught internally by system. Action: No action is required. ORA-01552 cannot use system rollback thread for non-system table space 'string' Cause: An attempt was made to use the system rollback thread for operations involving non-system table spaces. If it is a cloned database, this will happen when attempting any data modification outside of the system table space. Only the system rollback thread can be online in a cloned database. Action: Create one or more private/public segments, shutdown and reboot. It may be necessary to modify the ROLLBACK_SEGMENTS initialization parameter to acquire the private rollback segment. If it is a cloned database that is used for point-in-time recovery of the tablespace, this operation is not allowed. ORA-01553 MAXEXTENTS must not be less than the currently allocated string extensions Cause: The number of allocated extensions is greater than the specified MAXEXTENTS. Action: Specify a larger MAXEXTENTS value. ORA-01554 No transaction slots in transaction tables Cause: Too many concurrent transactions. Action: Shut down the system, modify the TRANSACTIONS, ROLLBACK_SEGMENTS, or ROLLBACK_SEGMENTS_REQUIRED initialization parameters, and reboot. ORA-01555 snapshot too old: rollback segment number string called "string" too short Cause: Rollback records needed by a reader for a consistent read are overwritten by other writers. Action: Use larger rollback segments.

ORA-01500 to ORA-02099 4-9

ORA-01556 MINEXTENTS for rollback segment must be greater than 1 Cause: MINEXTENTS specified less than 2 for the rollback segment. Action: Specify larger MINEXTENTS. ORA-01557 Rollback segment extents must be at least blocks of string Cause: The specified extent is less than the minimum size for the rollback segment. Action: Specify larger extents. ORA-01558 No transaction ID in rollback segment chain Cause: All available transaction IDs were used. Action: Terminate the instance and restart it with another rollback segment(s), then delete the rollback segment that no longer has a transaction ID. ORA-01559 MAXEXTENTS for rollback segment must be greater than 1 Cause: MAXEXTENTS specified less than 2 for rollback segment. Action: Specify larger MAXEXTENTS. ORA-01560 Global hash table size mismatch for string (string != string) Cause: The specified "GC_" initialization parameter was incompatible with another instance that already has the database mounted. Action: Correct the "GC_" parameter and restart. ORA-01561 could not drop all objects in the specified table space Cause: Failed to drop all objects when dropping a table space. Action: Repeat the drop table space until all objects are dropped. ORA-01562 could not extend rollback segment number string Cause: An attempt to extend the rollback segment failed. Action: This is usually followed by another error message that caused the failure. You can take the rollback thread offline to perform maintenance. Use SELECT SEGMENT_NAME FROM DBA_ROLLBACK_SEGS WHERE SEGMENT_ID=string (where string is the segment number of the message) to determine the rollback segment name. Then use the ALTER ROLLBACK SEGMENT OFFLINE command to take the rollback segment offline. ORA-01563 Rollback segment is PUBLIC, you must use keyword PUBLIC Cause: The PUBLIC keyword was not used to identify the public rollback segment. Action: Use the PUBLIC keyword when identifying the public rollback segment.

4-10

message error

ORA-01564 Rollback segment is not PUBLIC Cause: The identified rollback segment is not public. Action: Do not use the PUBLIC keyword when identifying the private rollback segment. ORA-01565 error identifying file 'string' Cause: An error occurred while trying to identify a file. Action: Check the error stack for detailed information. ORA-01566 file specified more than once in DROP LOGFILE Cause: The list of files supplied to DROP LOGFILE contains at least one duplicate. Action: Remove the duplicate file specification and try again. ORA-01567 deleting the log chain would leave less than 2 log files in the thread chain Cause: Deleting all the specified logs would leave less than 2 log files needed per enabled thread. Action: Delete fewer records or disable threads before deleting the records. It may be possible to clear the registry instead of downloading it. ORA-01568 unable to set space quota to PUBLIC Cause: An attempt was made to set the space quota on a table space to PUBLIC. Action: If you are trying to grant system-wide or table space privileges to all users, use GRANT RESOURCE [ON tablespace] TO PUBLIC. ORA-01569 The data file is too small for the system dictionary tables. Cause: The data file specified during database creation is too small to contain the system dictionary tables. Action: Re-create the database by specifying a larger file or files. ORA-01570 MINEXTENTS must not be greater than the currently allocated string extents Cause: The number of allocated extents is less than the specified MINEXTENTS. User Response : Specify a smaller MINEXTENTS value.

ORA-01500 to ORA-02099

4-11

ORA-01571 redo version string incompatible with ORACLE version string Cause: This software version cannot read the current redo logs and a crash recovery is required or there are offline database files that need recovery media. If a file name appears, you need media recovery. Action: Shut down and reboot using supported software. Perform any necessary media recovery and open the database. Shut down and reboot using current software. If the file is dropped, disconnect it with the DROP option to bypass this check. ORA-01572 Rollback segment string cannot be brought online, string lengths exceeded Cause: The number of lengths in the rollback segment exceeds the maximum limit. Cannot put online to write. Action: Drop and recreate the rollback segment. ORA-01573 shutting down instance, no other changes allowed Cause: Some process tried to make changes while the database was shutting down. Action: No action is required. ORA-01574 maximum number of concurrent transactions exceeded Cause: The limit for the number of concurrent transactions was reached. Action: Shut down the system, increase the value of the TRANSACTIONS initialization parameter, and reboot the system. ORA-01575 space management resource timed out Cause: The resource required to perform space management could not be acquired. Action: Repeat the operation. ORA-01576 instance lock protocol version string mismatch with ORACLE version string Cause: The current software uses a mismatch lock protocol. Action: Update the software used to start the instances so that they use the supported lockdown protocol. ORA-01577 cannot add log file 'string': file is already part of database Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database. Action: Use a different file name.

4-12

message error

ORA-01578 Corrupt ORACLE data block (file # string, block # string) Cause: The indicated data block was corrupted, probably due to program errors. Action: Determine which object was corrupted with a command like the following: SELECT SEGMENT_TYPE,OWNER||'.'||SEGMENT_NAME FROM DBA_EXTENTS WHERE file = FILE_ID AND block BETWEEN BLOCK_ID AND BLOCK_ID+BLOCKS -1;

where the values for file and block are from the message. Attempts to restore the segment that contains the indicated block. This might involve deleting the thread and recreating it. If there is a trace file, report the errors it contains to Oracle Customer Support. ORA-01579 write error occurred during recovery Cause: A write error occurred during recovery. Action: Check the trace files for the nature of the write error and correct the error. ORA-01580 error creating a control file backup chain Cause: An operating system error occurred while trying to create a control file backup. Action: Check the error stack for more detailed information. ORA-01581 attempted to use rollback segment (string) new extent (string) allocated Cause: Undo generated to extend a rollback segment exhausted the current space of the undo block and attempted to write to a new extent that was not fully allocated. Action: The system will reverse the extension of the reversal segment, no further extensions can be made until the next extension is released by reversing or confirming other transactions. ORA-01582 unable to open control file for backup Cause: An operating system error occurred while trying to open a control file for backup. Action: Check the error stack for more detailed information.

ORA-01500 to ORA-02099

4-13

ORA-01583 Unable to get backup control file block size Cause: An operating system error occurred while trying to get the block size of a backup control file. Action: Check the error stack for more detailed information. ORA-01584 Unable to get control file size for backup Cause: An operating system error occurred while trying to get the control file size for backup. Action: Check the error stack for more detailed information. ORA-01585 error identifying backup file string Cause: An operating system error occurred while trying to identify the file to use for the control file backup. Action: Check the error stack for more detailed information. ORA-01586 Unable to open destination file string for backup Cause: An operating system error occurred while trying to open a control file for backup. Action: Check the error stack for more detailed information. ORA-01587 error copying control file backup file Cause: An operating system error occurred while trying to copy a control file for backup. Action: Check the stack of attached messages for detailed information, then take the appropriate action. ORA-01588 You must use the RESETLOGS option to open the database Cause: A previous attempt to open the database with the RESETLOGS option failed or recovery was performed using a control file backup. Action: Use the RESETLOGS option when opening the database. ORA-01589 You must use the RESETLOGS or NORESETLOGS option to open the database Cause: An incomplete recovery or control file backup was performed. After these types of recovery, you must specify either the RESETLOGS option or the NORESETLOGS option to open your database. Action: Specify the appropriate option. ORA-01590 segment free list number (string) exceeds maximum string Cause: The value of the FREELIST GROUPS storage parameter is too large.

4-14

message error

Action: Reduce the value of the storage parameter FREELIST GROUPS. ORA-01591 lock held by indoubt distributed transaction sequence Cause: An attempt was made to access the resource that is locked by an idle two-phase commit transaction that is in the prepared state. Action: The database administrator should query PENDING_TRANS$ and related tables and attempt to repair network connections to the coordinator and commit point. If timely repair is not possible, the database administrator should contact the database administrator at the point of compromise, if known, or the end user to get the correct result, or use the pattern heuristic, if provided, to issue a COMMIT or ABORT heuristic command. to end the local part of the distributed transaction. Error ORA-01592 converting Version 7 rollback segment (string) to Oracle 8 format Cause: Note the accompanying internal error; The version 7 database may not have been shut down properly. Action: Investigate the internal error; it may be necessary to reload the version 7 database (from the backup) and shut down the database properly. ORA-01593 The optimal size of the rollback segment (chain blocks) is smaller than the calculated initial size (string blocks) Cause: The specified OPTIMAL size is smaller than the cumulative size of the initial extents when creating the rollback segment. reversion. Action: Specify a larger OPTIMUM size. ORA-01594 Break attempt on rollback segment extent (chain) being freed Cause: Undo generated to free a rollback segment extent is attempting to write to the same extent due to small extents or too many free extents, release. Action: The system will revert the rollback segment collapse; increase the optimal size of the recoil segment. ORA-01595 error freeing rollback segment extent(string)(string)) Cause: An error occurred while freeing idle rollback segment extents. Action: Investigate the associated error.

ORA-01500 to ORA-02099

4-15

ORA-01596 cannot specify system in string parameter Cause: The system rollback segment is specified in the initialization parameter referenced in the error message. User Response : Change the value of the initialization parameter. ORA-01597 cannot change system rollback segment online or offline Cause: An attempt was made to bring the system rollback segment online or offline. Action: No action is required. ORA-01598 Rollback segment 'chain' is not online Cause: It may have been previously taken offline by the database administrator or deleted by SMON. Action: Check the status of the rollback thread in UNDO$ or DBA_ROLLBACK_SEGS to make sure that the rollback thread is actually online. ORA-01599 Failed to acquire rollback segment (string), cache space is full (currently has entries (string)) Cause: The statically allocated amount is not enough based on the value of the MAX_ROLLBACK_SEGMENTS parameter. Action: For now, disconnect another rollback segment or increase the value of the MAX_ROLLBACK_SEGMENTS parameter. ORA-01600 at most one "string" in string "string" clause Cause: The initialization parameter was specified incorrectly. User Response : Correct the initialization parameter and restart the instance. ORA-01601 Invalid bucket size in string "string" clause Cause: The bucket size was invalid for this parameter. User Response : Correct the initialization parameter and restart the instance. ORA-01603 Invalid collation size in string clause "string" Cause: The collation size was invalid for this parameter. User Response : Correct the initialization parameter and restart the instance. ORA-01604 Invalid number range in string clause "string" Cause: The number range was invalid for this parameter. User Response : Correct the initialization parameter and restart the instance.

4-16

message error

ORA-01605 Missing numbers in string "string" clause Cause: Missing numbers for this parameter. User Response : Correct the initialization parameter and restart the instance. ORA-01606 gc_files_to_locks is not identical to another mounted instance Cause: The GC_FILES_TO_LOCKS parameters were different on two instances. Action: Modify the initialization parameter GC_FILES_TO_LOCKS and reboot. ORA-01607 gc_lck_procs (string) is not equal to the other instances (string) Cause: The initialization parameter GC_LCK_PROCS is not equal to the other instances that already have the database open. Action: Modify the GC_LCK_PROCS parameter and restart the instance. ORA-01608 cannot bring rollback thread 'chain' online, its status is (chain) Cause: The database administrator may have brought it online previously or left it as a result of a failure in the process. Action: Check thread rollback status in UNDO$ or DBA_ROLLBACK_SEGS ORA-01609 record string is current record for thread string: cannot drop members Cause: cannot drop a current record member for a thread . Action: If the thread is open, request a registration change from the instance using it. If it's not open, disable the thread, manually archive the log, or delete it. ORA-01610 Recovery must be performed using the BACKUP CONTROLFILE option Cause: A previous database recovery session specified BACKUP CONTROLFILE, or the control file was re-created with the RESETLOGS option, or the control file used is a backup file. backup control. After that, only the recovery of the BACKUP CONTROLFILE is allowed and must be followed by a log reset on the next open database. Action: Perform recovery using the BACKUP CONTROLFILE option. ORA-01611 Invalid thread number string: must be between 1 and string Cause: The thread number in a command is greater than the number of threads supported by the control file. Action: Use a valid thread number or change the size of the thread log and/or checkpoint progress log sections of the control file.

ORA-01500 to ORA-02099

4-17

ORA-01612 Thread chain is already enabled Cause: An attempt was made to enable a thread that is already enabled. Action: Use this thread or enable another thread. Thread chain ORA-01613 has only chain registers: at least 2 registers are required to enable Cause: The thread cannot be enabled because it only has two associated online register files. Action: Add logs to the thread or choose another thread to enable. ORA-01614 Thread stream is busy: cannot be enabled Cause: The mount queue for the thread could not be acquired when trying to enable the thread. This probably means that another process has already started enabling that thread. Action: Wait and try again or find another thread to enable. Thread chain ORA-01615 is mounted; cannot be disabled Cause: Some instance, possibly this one, has allocated the thread for use. Threading cannot be disabled during use. Action: Terminate the instance successfully using the thread. Thread chain ORA-01616 is open; cannot be closed Cause: The thread is not closed. The last instance that used the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for instance failure or recovery. Action: If the database is open, the instance recovery should close the thread shortly; Wait some minutes. If not, open the database; disaster recovery will close the topic. ORA-01617 cannot mount: string is not a valid thread number Cause: The value of the THREAD initialization parameter is not between 1 and the number of threads allowed by the control file. Action: Shut down the instance, change the value of the startup parameter, and restart or resize the thread log and/or checkpoint progress log sections of the control file. ORA-01618 Thread stream not enabled: cannot mount Cause: The value of the THREAD initialization parameter requests a thread that is not enabled. A thread must be activated before it can be mounted.

4-18

message error

Action: Shut down the instance, change the value of the startup parameter, and reboot, mounting a different thread. If the database is open in another instance, threading might be active. ORA-01619 Thread chain is mounted by another instance Cause: The value of the THREAD initialization parameter requests a thread that was mounted by another instance. Only one instance can use a thread. Action: Shut down the instance, change the value of the startup parameter, and reboot, mounting a different thread. ORA-01620 no public threads available to mount Cause: The value of the THREAD initialization parameter is zero, its default value. There are no threads that have been publicly enabled and have not been mounted. Action: Terminate the instance, change the value of the launch parameter to a privately enabled unmounted thread. If the database is open in another instance, a thread can be publicly enabled. ORA-01621 cannot rename current log member if database is open Cause: This is a rename command for a current log member for an open thread. If the database is open anywhere, the record may be in use, so the name cannot be changed. Action: Wait until the registry is out of date or mount the database exclusively. Thread number ORA-01622 must be specified; non-specific default Cause: The thread was not specified when adding a record and the currently mounted thread was chosen by default at mount time. Since the current thread was not explicitly specified, the user cannot know which thread the record will be added to. User Response: Explicitly specify the thread number in the THREAD initialization parameter or in the ADD command. ORA-01623 record chain is current record for thread chain: cannot be discarded Cause: The current record of a thread cannot be discarded even if the thread is closed. A disabled thread usually does not have a current record, but a half-disabled one may need to be disabled again. Action: If the database is not open, disable the thread. If the database is open and an instance is open by threads, the instance can be asked to

ORA-01500 to ORA-02099

4-19

change records. If the database is closed, the log can be archived or purged to force a change. ORA-01624 registry chain is required for thread chain failover. Cause: A record cannot be discarded or cleared until the thread's checkpoint has advanced out of the record. Action: If the database is not open, open it. Crash recovery will advance the checkpoint. If the database is open, force a global checkpoint. If the registry is corrupted and the database cannot be opened, a soft recovery may be required to clear this registry. ORA-01625 Rollback segment 'chain' does not belong to this instance Cause: An attempt was made to shrink or detach a rollback segment that does not belong to this instance. Action: Take offline only the rollback segments that belong to the current instance. To disconnect the rollback segment, connect to the containing instance. ORA-01626 rollback thread number 'chain' cannot handle any more transactions Cause: Too many transactions on this thread. Action: Choose a different reversal segment or reduce the number of concurrent transactions. ORA-01627 rollback segment number 'string' is not online Cause: It may have been previously taken offline by the database administrator or deleted by SMON. Action: Check the status of the rollback thread in UNDO$ or DBA_ROLLBACK_SEGS to make sure that the rollback thread is actually online. ORA-01628 The maximum number of extensions (chain) was reached for the rollback chain segment Cause: An attempt was made to extend a rollback segment that was already at the MAXEXENTS value. Action: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, increase this value. ORA-01629 maximum number of extents (string) reached when saving undo in table space chain Cause: Save undo in offline table space in MAXEXTENTS. User Response : Check the storage parameters for the system tablespace. The tablespace must be brought back online before the undo can be applied.

4-20

message error

ORA-01630 maximum number of extents (string) reached in temporary segment in table space chain Cause: A temporary thread attempted to extend beyond MAXEXTENTS. Action: If the MAXEXTENTS for the tablespace is less than the system maximum, you can increase it. Otherwise, increase PCTINCREASE for the table space. ORA-01631 maximum number of extents (string) reached in table string.string Cause: A table attempted to extend beyond MAXEXTENTS. Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-01632 maximum number of extents (string) reached at index string.string Cause: An index attempted to extend beyond MAXEXTENTS. Action: If the value of MAXEXTENTS in the index store clause is less than the maximum (based on the block size), increase it. Otherwise, rebuild the index with larger extent sizes so that the total number of extents is below the maximum. ORA-01633 Parallel server option required for this operation Cause: The system does not have a parallel server configured. Action: Get the parallel server option. ORA-01634 Rollback segment number 'string' is about to go offline Cause: The specified rollback segment has been marked offline by the database administrator. Action: Put the rollback segment online first. ORA-01635 revert segment # specified string not available Cause: One of the following: ■

Attempted to acquire an offline rollback segment during initialization.

■

You tried to drop a rollback segment that contains active transactions.

Action: For the above, one of the following: ■

■

Bring the tablespace containing the rollback segment online, or do not specify the rollback segment in the initialization parameter file. If the rollback thread is in use, shut down the instance using the rollback thread. Otherwise, if the rollback thread needs recovery, determine what errors are preventing the transactions from rolling back and take appropriate action.

ORA-01500 to ORA-02099

4-21

ORA-01636 Rollback segment 'chain' is already online Cause: A rollback segment can only be used by one instance, and an instance is trying to bring online a rollback segment that is already in use. Action: Verify that the values defined in the initialization parameter file for the ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT parameters are set correctly for the problem instance. Also check that the instance is using the correct initialization parameter file. Make sure you're not confused about the difference between private and public rollback segments. See the Oracle8i Administrator's Guide for more information on using rollback segments in parallel mode. ORA-01637 Rollback segment 'chain' is in use by another instance (#string) Cause: A rollback segment can only be used by one instance and an instance is trying to access an online rollback segment that is already in use. Action: Verify that the values defined in the initialization parameter file for the ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT parameters are set correctly for the problem instance. Also check that the instance is using the correct initialization parameter file. Make sure you're not confused about the difference between private and public rollback segments. See the Oracle8i Administrator's Guide for more information on using rollback segments in parallel mode. ORA-01638 parameter string does not allow ORACLE version string to be mounted in parallel Cause: The value of the RECOVERY_COMPATIBLE parameter is set too low to allow this software version to be mounted in parallel. Action: Use an older software version or advance the RECOVERY_COMATIBLE parameter. If this happens when no RECOVERY_COMPATIBLE parameter is specified, set it to the current software version. ORA-01640 unable to make table space read only with active transactions Cause: An attempt was made to make a table space read only while there are active transactions in the database. All transactions must be committed or rolled back to ensure that there is no rollback of a tablespace before it becomes read-only. This certainly includes distributed transactions. Action: Prevent further transactions from starting. Putting the database in strict mode often helps. If there are questionable transactions, they must also be resolved.

4-22

message error

ORA-01641 tablespace 'string' is not online: cannot add data file Cause: An attempt was made to add a data file to a tablespace that was defined as read-only or offline. Action: Bring the tablespace online and read, write, and add the data file. ORA-01642 Start backup not required for read-only table space 'string' Cause: An attempt was made to start or end a backup for a table space that was defined as read-only. Action: Perform a backup without any BEGIN or END command. The files are not changed, so the backup is consistent. ORA-01643 System table space cannot be made read-only Cause: An attempt was made to set the system table space to read-only. The system tablespace must remain read/write for database operation. Action: Leave the system tablespace read and write. ORA-01644 tablespace 'string' is already read-only Cause: An attempt was made to make a tablespace read-only that is already read-only. Action: Make the table space read-only or make it read-write and then make it read-only again. ORA-01645 Previous read/write attempt is incomplete Cause: An error making the tablespace read/write left it read-only, but the checkpoint moved forward. The tablespace cannot be used after a log reset if its files are offline. User Response : Repeat the command to make the table space read and write. ORA-01646 tablespace 'string' is not readonly: cannot read/write Cause: An attempt was made to make a tablespace read/write that is not readonly. It can be online or offline. Action: Leave the table space read and write. ORA-01647 table space 'string' is read-only, space cannot be allocated Cause: An attempt was made to allocate space in a read-only table space. Action: Create the object in another tablespace.

ORA-01500 to ORA-02099

4-23

The ORA-01648 log string is the current log for the disabled thread string. Cause: An attempt to enable the thread failed after it was half completed. This record has been left as the current record even though the thread is still disabled. Since a registry change cannot be made until the thread is activated, the registry cannot be cleared or archived. Action: Complete enabling the thread by issuing the ENABLE command again. ORA-01649 Operation not allowed with a backup control file Cause: An attempt is being made to execute a command that does not make sense when the control file is a restored backup. Action: Wait until the database has been opened and try again. ORA-01650 cannot extend rollback segment string by string in table space string Cause: Failed to allocate an extension for the rollback segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01651 cannot extend undo save segment by string to table space string Cause: Failed to allocate an extension to save undo entries for the indicated offline table space. User Response : Check the storage parameters for the SYSTEM tablespace. The tablespace must be brought back online before the undo can be applied. ORA-01652 cannot extend temporary segment by string in table space string Cause: Failed to allocate an extension for the temporary segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01653 cannot extend table string.string by string in table space string Cause: Failed to allocate an extension for table segment in table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01654 cannot extend index string.string by string in table space string Cause: Failed to allocate an extension for the index segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace.

4-24

message error

ORA-01655 cannot extend cluster string.string by string in table space string Cause: Failed to allocate an extent for the cluster segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01656 maximum number of extents (string) reached in cluster string.string Cause: A cluster attempted to extend beyond MAXEXTENTS. Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-01657 Invalid SHRINK option value Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-01658 Could not create INITIAL extent for segment in tablespace chain Cause: Could not find enough contiguous space to allocate the INITIAL extent for the segment being created. User Response : Use ALTER TABLESPACE ADD DATAFILE to add more space to the tablespace or try again with a smaller value for INITIAL. ORA-01659 cannot allocate MINEXTENTS beyond string in table space string Cause: Could not find enough contiguous space to allocate MINEXTENTS for the slice being created. Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace, or try again with a smaller value for MINEXTENTS, NEXT, or PCTINCREASE. ORA-01660 tablespace 'string' is already persistent Cause: An attempt was made to convert a tablespace that is already persistent to permanent. Action: Make the tablespace permanent. ORA-01661 tablespace 'string' is already temporary Cause: An attempt was made to convert a tablespace that is already temporary to temporary. Action: Make the tablespace permanent.

ORA-01500 to ORA-02099

4-25

ORA-01662 tablespace 'string' is not empty and cannot be converted to temporary Cause: An attempt was made to convert a non-empty tablespace to a temporary tablespace Action: Delete all objects in the tablespace. ORA-01663 The content of tablespace 'string' is constantly changing Cause: The content of the tablespace is always changing between PERMANENT and TEMPORARY. Action: Decide what the content of the tablespace should be and stick with it. ORA-01664 The transaction that expanded the sort segment was aborted Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-01665 Control file is not a standby control file Cause: An attempt was made to mount, recover, or activate a standby database without a standby control file. Action: Create a standby control file before attempting to use the database as a standby. The ORA-01666 control file is for a standby database. Cause: An attempt was made to mount, recover, or open a standby without the appropriate command option to designate a standby. Action: Use the wait option or appropriate commands or mount with the main control file. ORA-01667 cannot add more tablespaces: string limit exceeded Cause: There is no more space in the control file to add tablespaces. Action: Change the size of the control file or drop other tablespaces. ORA-01668 standby database requires DROP option for offline data file Cause: An attempt was made to take a data file on a standby database offline without specifying the DROP option. Files that are offline in a standby database cannot be recovered and may not be usable if standby is enabled. Note that specifying DROP does not prevent the file from being attached later. Action: Specify the DROP option or leave the file online.

4-26

message error

ORA-01669 standby database control file is inconsistent Cause: An attempt was made to activate a standby database with a control file that was not retrieved to the same point as the data files. Most likely the control file was copied from the main database and not used for recovery. Action: Recover the standby database until all files are consistent. ORA-01670 A new data file chain is required for standby recovery Cause: Standby recovery noticed that a file was added to the primary database but it is not available in the standby database. Action: Copy the main database file or run an ALTER DATABASE CREATE DATAFILE command in standby mode to create a file to recover. ORA-01671 control file is a backup, cannot create a standby control file Cause: The currently mounted control file is a backup control file and you are trying to create a control file for a standby database. Action: Complete any necessary recovery and open the database with the resetlogs option. The ORA-01672 control file may be missing files or may have additional files Cause: An attempt was made to create a standby control file, but the control file was newly created via CREATE CONTROL FILE or a recovery was performed incomplete. Therefore, the data files in the control file and those in the data dictionary may not match. Action: Open the database and retry the operation. Data file string not identified ORA-01673 Cause: This data file was not in the control file after an incomplete recovery or CREATE CONTROL FILE. Since its header information is required for standby database recovery, we cannot create a standby control file. Action: Find the file and put it online. If desired, it can be disconnected again. If you intend to drop this file, unplugging it with the DROP option will prevent this error. The ORA-01674 data file string is an old incarnation instead of the current file. Cause: Recovery found redo, indicating that this file was removed from the database and another file with the same file number was added. East

ORA-01500 to ORA-02099

4-27

implies that a CREATE CONTROLFILE command received the old file that was dropped instead of the newer file. Action: Rebuild the control file using CREATE CONTROLFILE and provide the correct file. ORA-01675 max_commit_propagation_delay inconsistent with other instances Cause: The initialization parameter MAX_COMMIT_PROPAGATION_DELAY is inconsistent with those of other instances. Action: Make sure all instances have the same MAX_COMMIT_PROPAGATION_DELAY. ORA-01676 Conversion of standby filename from 'string' exceeds maximum length of string Cause: When the given filename is converted to the name used for the standby database, the converted name is greater than the maximum file name allowed. Action: Change the value of the initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name. ORA-01677 Standby filename conversion parameters differ from another instance Cause: The initialization parameters DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT are not the same as those of other instances that already have the database mounted. Action: Change the value of the initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match the other instances. The ORA-01678 parameter string must have two strings, one default and one substitute. Cause: The initialization parameter is missing two strings for its value. The first string is a pattern to search the file names. The second string is used to replace the pattern when found in file names. Action: Specify two strings for the parameter or omit the parameter. The ORA-01679 database must be mounted EXCLUSIVELY and not be opened for activation. Cause: An attempt was made to activate a standby database when the database was not EXCLUSIVELY mounted or was already open. Action: Mount the EXCLUSIVE database and repeat the ACTIVATE command.

4-28

message error

ORA-01680 cannot extend LOB segment by string in table space string Cause: Failed to allocate an extension for a LOB segment in table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01681 maximum number of extents (string) reached in LOB segment in table space string Cause: A LOB segment attempted to extend beyond MAXEXTENTS. Action: If the MAXEXTENTS for the tablespace is less than the system maximum, you can increase it. Otherwise, increase PCTINCREASE for the table space. ORA-01682 Read-only database cannot allocate temporary space in tablespace chain Cause: Temporary space (usually for sorting) could not be allocated from main storage or a temporary file. An attempt was made to allocate space from the named tablespace, but the database opens in read-only mode. The open database requires a classification workspace. Action: Allow enough working space on main storage (SORT_AREA_SIZE initialization parameter) or create a temporary table space before making the database read-only. Use the ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace. ORA-01683 cannot extend index string.string partition string by string in table space string Cause: Could not allocate an extension for the index segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01684 Maximum number of extents (string) reached in table string.string partition string Cause: A table attempted to extend beyond MAXEXTENTS. Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-01685 max. # extents (string) reached at index string.string partition string Cause: An index attempted to extend beyond MAXEXTENTS. Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-01686 Maximum number of files (string) for table space string reached Cause: The number of files for a given table space has reached its maximum value.

ORA-01500 to ORA-02099

4-29

Action: Resize existing files in the tablespace, partition objects across multiple tablespaces, or move some objects to a different tablespace. ORA-01687 Log attribute specified for table space 'string' is equal to existing Cause: An attempt was made to change the table space's default log attribute (LOGGING or NOLOGGING) to equal the existing log attribute. User Response : Change the specified registry attribute. ORA-01688 cannot extend table string partition.string string by string in table space string Cause: Failed to allocate an extension for the table segment in the table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01689 syntax error in string clause "string" Cause: There was syntax in the initialization parameter. User Response: Correct the syntax error and restart the instance. ORA-01690 gc_rollback_locks is not identical to another mounted instance Cause: The GC_ROLLBACK_LOCKS parameter was different on different instances. Action: Modify the initialization parameter GC_ROLLBACK_LOCKS and reboot. ORA-01691 cannot extend lob segment string.string by string in table space string Cause: Could not allocate an extension for LOB segment in table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01692 cannot extend lob segment string.string partition string by string in tablespace string Cause: Could not allocate an extension for LOB segment in tablespace. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-01693 maximum number of extents (string) reached in segment lob string.string Cause: A LOB segment attempted to extend beyond MAXEXTENTS.

4-30

message error

Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-01694 max. # extents (string) reached in segment lob string.string partition string Cause: A LOB segment attempted to extend beyond MAXEXTENTS. Action: If MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. Error ORA-01695 converting rollback segment chain to version 8.0.2 Cause: The version 8.0.1 database might not have been shut down correctly. Action: It may be necessary to reload the 8.0.1 database and shut it down gracefully. ORA-01696 control file is not a clone control file Cause: An attempt was made to mount a database as a clone when it was already mounted by a non-clone instance, or an attempt was made to use an existing control file for a clone . Action: Mount without the clone option or use a backup control file and power off other instances before mounting as a clone. The ORA-01697 control file is for a cloned database. Cause: An attempt was made to mount a cloned database without the proper command option to designate a cloned database. Action: Use the clone option or appropriate commands or mount with the main control file. ORA-01698 a cloned database can only have one SYSTEM rollback segment online Cause: An attempt was made to bring a rollback segment online in a cloned database. Action: Do not use this command. ORA-01699 Tablespace 'chain' is being imported for point-in-time recovery Cause: An attempt was made to bring a tablespace online or start another point-in-time import while a point-in-time import was already in progress. grade. Action: Wait for the import to complete.

ORA-01500 to ORA-02099

4-31

ORA-01700 duplicate username in list ORA-01701 cluster not appropriate here ORA-01702 display not appropriate here ORA-01703 missing SYNONYM keyword ORA-01704 string literal too long Cause: string literal has more than 4000 characters. Action: Use a string literal of no more than 4000 characters. Longer values can only be entered using binding variables. ORA-01705 cannot specify an outer join on a mapping column ORA-01706 the user function result value was too large ORA-01707 the LIST keyword is missing ORA-01708 ACCESS or SESSION was expected ORA-01709 the program does not exist ORA-01710 missing OF keyword ORA-01711 enumerated duplicate privilege ORA-01712 cannot grant a privilege that it does not have ORA-01713 GRANT OPTION does not exist for this privilege ORA-01714 user role execution error ORA- 01715 UNIQUE cannot be used with a clustered index Explanation : An attempt was made to create a clustered index with the UNIQUE attribute. Action: Remove UNIQUE from the CREATE INDEX statement. ORA-01716 NOSORT cannot be used with a clustered index Cause: An attempt was made to create a clustered index using the NOSORT option. Action: Remove NOSORT from the CREATE INDEX statement. ORA-01717 seccta: Invalid access mode token passed ORA-01718 PER ACCESS | SESSION clause not allowed for NOAUDIT Cause: Attempting to specify PER ACCESS | SESSION in a NOAUDIT statement. Action: Delete BY ACCESS | SESSION. ORA-01719 Outer join operator (+) not allowed in OR or IN operand Cause: An outer join appears in an OR clause.

4-32

message error

Action: If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) the union of all (select where (B)). ORA-01720 grant option does not exist for 'string.string' Cause: A grant was being performed on a view and the grant option was not present for an underlying object. Action: Get the grant option on all underlying objects in the view. ORA-01721 USERENV(COMMITSCN) called more than once in a transaction Cause: The USERENV('COMMITSCN') function can only be used once in a transaction. Action: Rewrite the transaction to use USERENV('COMMITSCN') only once. ORA-01722 invalid number Cause: The attempt to convert a string to a number failed because the string was not a valid numeric literal. Only numeric fields or character fields that contain numeric data can be used in functions or arithmetic expressions. Only numeric fields can be added or subtracted from dates. Action: Check the strings in the function or expression. Make sure they only contain numbers, a sign, a decimal point, and the character "E" or "e" and repeat the operation. ORA-01723 Zero-length columns not allowed Cause: During CREATE TABLE, a zero-length column was specified, for example CHAR(0). Action: Correct the column declaration so that the length is at least 1 and retry the operation. ORA-01724 Floating point precision is out of range (1 to 126) Cause: Floating point precision is too small or too large. Action: Correct and try again. ORA-01725 USERENV('COMMITSCN') not allowed here Cause: The USERNEV('COMMMITSCN') function is only allowed as a top-level expression in the VALUES clause of INSERT statements and on the right-hand side of an assignment in a statement UPDATE . Action: Correct the use of the function.

ORA-01500 to ORA-02099

4-33

ORA-01726 a table is not appropriate here Cause: A table name was used in a statement where tables are not allowed. Action: Enter a valid table declaration or use the current declaration in the appropriate object. ORA-01727 numeric precision specifier is out of range (1 to 38) Cause: The precision specified for a numeric column in a CREATE/ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If none is specified precision, a default precision of 22 digits is used. Action: Specify a numeric precision between 1 and 38 and retry the statement. ORA-01728 numeric scale specifier is out of range (-84 to 127) Cause: The scale specified for a numeric field in a CREATE/ALTER TABLE or CREATE CLUSTER statement is not in the valid range. It must be between -84 and 127. Action: Specify a numeric scale between -84 and 127. If a number is not specified, the column defaults to 0 decimal places. ORA-01729 Expected database link name Cause: The name of a database link does not follow the at sign (@) in a reference to a table in a remote database. Action: Correct the reference and retry the operation. The correct syntax to point to a table in a remote database is as follows:[email protected]database name

Spaces before and after the at sign (@) are optional. ORA-01730 invalid number of column names specified Cause: The number of column names specified in a CREATE VIEW statement did not match the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause. Action: Specify a display column name for each column in the SELECT clause. ORA-01731 Circular view definition found Cause: Through a series of CREATE and DROP VIEW statements, a view was defined that references itself. For example, VIEW1 can include a column from VIEW2 defined as a column in VIEW1. The display definitions can be seen by querying the data dictionary.

4-34

message error

Action: Check the display definitions, remove all circular references, and repeat the instructions. ORA-01732 Invalid data manipulation operation on this view Cause: An attempt was made to use an UPDATE, INSERT, or DELETE statement on a view that contains expressions or functions, or it was derived from more than one table. If a join operation was used to create the view, or if the view contains virtual columns derived from functions or expressions, the view can only be queried. Action: UPDATE, INSERT, or DELETE rows in the base tables and restrict operations on the view to queries. ORA-01733 virtual column not allowed here Cause: An attempt was made to use an INSERT, UPDATE, or DELETE statement in an expression in a view. Action: INSERT, UPDATE, or DELETE data in the base tables instead of the view. ORA-01734 Illegal parameters: EXTENT MIN greater than EXTENT MAX Cause: An incorrect value was specified for the parameter. User Response : Correct the parameter and resubmit the declaration. ORA-01735 Invalid ALTER TABLE Option Cause: An invalid option was specified in an ALTER TABLE statement. Action: Check the syntax of the declaration, specify a valid option, and retry the declaration. ORA-01736 [NOT] SUCCESSFUL expected cause: A contained AUDIT or NOAUDIT statement is ALWAYS followed by something that is not SUCCESSFUL or NOT SUCCESSFUL. Action: Correct the WHENEVER clause and retry the statement. ORA-01737 Valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE Cause: The lock mode entered was not recognized. Action: Enter one of the following: SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, ROW SHARE EXCLUSIVE, or SHARE UPDATE.

ORA-01500 to ORA-02099

4-35

ORA-01738 Missing IN keyword Cause: In a LOCK TABLE statement, the IN keyword was missing. Action: Put the IN keyword and the lock mode directly after the table name in the LOCK TABLE statement and repeat the statement. ORA-01739 Missing keyword MODE Cause: In a LOCK TABLE statement, the keyword MODE was missing. The MODE keyword must directly follow the specified lock mode. Action: Check the syntax of the statement, insert the MODE keyword where necessary, and retry the statement. ORA-01740 Missing double quote in identifier Cause: Encountered a leading double quote (") without a closing quote. If an identifier contains whitespace or special characters other than $, #, or _, it must be enclosed in quotes Action : Add a closing double quote (") to the end of the identifier. ORA-01741 Illegal zero-length identifier Cause: An attempt was made to use two double quotes ("") as the identifier. An identifier must be at least one character long. Action: Enter at least one character in double quotes in the identifier. If a blank identifier is required, specify a blank space within double quotes (" "). ORA-01742 comment not terminated correctly Cause: The indicated comment or track that started with the /* token did not have the ending */. Action: Properly end the comment or suggestion with a */. ORA-01743 can only index pure functions Cause: The indexed function uses SYSDATE or user environment. Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV() or anything else that depends on session state. Functions dependent on NLS are fine. ORA-01744 INTO inappropriate Cause: The INTO clause cannot be used in a subquery. Action: Check the syntax, put the INTO clause in the top-level query, and try the statement again.

4-36

message error

ORA-01745 invalid host/bind variable name Cause: The colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word. Action: Change the name of the variable and repeat the operation. ORA-01746 Pointer variable not allowed here Cause: A pointer variable is not allowed in this context. Action: Delete the indicator variable and repeat the operation. ORA-01747 Invalid user.table.column, table.column or column specified Cause: A column name was incorrectly specified in the current SQL statement. Action: Check the syntax of the declaration, especially the references to the column names, and try the declaration again. ORA-01748 Only simple column names are allowed here. Cause: This SQL statement does not allow a qualified column name such as username.table.column or table.column. Action: Remove the qualifications from the column and try the operation again. ORA-01749 cannot GRANT/REVOKE privileges to/from yourself. Cause: The grantor cannot grant or revoke object or system privileges for itself. Action: Issue GRANT or REVOKE system privileges from another database administrator account. ORA-01750 UPDATES/REFERENCES can only be REVOKED from the entire table, not per column Cause: While GRAND update privileges are possible on a column-by-column basis, it is only possible to REVOKE them for an entire table. Action: Do not identify specific columns. To revoke update privileges for certain columns, use REVOKE for the entire table and GRANT user privileges for specific columns. ORA-01751 Invalid undo option Cause: An invalid option was specified in the ALTER DUMP UNDO command. Action: Correct and reissue the command.

ORA-01500 to ORA-02099

4-37

ORA-01752 cannot drop from view without exactly one key-keep table Cause: The dropped table had no key-keep tables, had more than one key-keep table, or the key-keep table was a non-merged view or a table with key preserved table a read-only screen. Action: Reset the view or remove it from the underlying base tables. ORA-01753 Column definition incompatible with clustered column definition Cause: When adding a table to a cluster, the column definition in the table was not consistent with the column definition in the cluster. User Response: The table cannot be added to the cluster until all column definitions in the cluster are consistent. ORA-01754 A table can only contain one column of type LONG Cause: An attempt was made to add a LONG column to a table that already has a LONG column. Note that even if the LONG column currently in the table has already been marked as unused, another LONG column cannot be added until the unused columns are dropped. User Response : Remove the LONG column currently in the table using the ALTER TABLE command. ORA-01755 You must specify an extension or block number Cause: An extension or block number was expected, but something else was specified. Action: Correct the error and issue the command again. ORA-01756 quoted string not terminated correctly Cause: A quoted string must end with a single quote ('). Action: Insert the closing quote and repeat the declaration. ORA-01757 You must specify an object number Cause: An object number was expected but something else was specified. Action: Correct the error and issue the command again. ORA-01758 table must be empty to add required column (NOT NULL) Cause: A new column cannot be defined as NOT NULL if rows already exist in the table being modified. User Response: Repeat the statement without the NOT NULL specification. ORA-01759 user role is incorrectly defined Cause: A user role was defined incorrectly.

4-38

message error

Action: Contact Oracle Customer Support. ORA-01760 Invalid argument to function Cause: The arguments specified for the function are invalid in this context. Action: Check the function definition and correct the arguments. ORA-01761 DML operation is not mapped to a unique table in the join Cause: The parent table is the base table on which the update, insert, or delete operation is ultimately performed. To delete, there is no parent table in the join query or there are more than one. For update or insert, the specified columns are mapped to more than one base table. User Response : Change the join specification. ORA-01762 vopdrv: view query block not in FROM Cause: This is an internal error message that is not normally thrown. Action: Contact Oracle Customer Support. ORA-01763 update or drop involves outer join table Cause: For deletes, the table being dropped is outer joined to another table. For updates, the table being updated is externally joined to another table, or some table accessible from the parent table is externally joined to a table that is not accessible from the parent table. User Response : Change the join specification. ORA-01764 New join update value is not guaranteed to be unique Cause: A row in a join query table is updated using a row from a table that is not guaranteed to have exactly one value for the row being updated. User Response : Change the join specification. ORA-01765 not allowed to specify table owner name Cause: A table or view name was specified with a period (.) or was identified with an invalid prefix. Action: Check that the object is correctly identified and, if necessary, remove the dot from the name.

ORA-01500 to ORA-02099

4-39

ORA-01766 Dictionary table not allowed in this context Cause: The name of a data dictionary object was used outside of the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object is a SELECT from it. User Response: Restrict operations on data dictionary objects to queries. ORA-01767 UPDATE... SET expression must be a subquery Cause: An attempt was made to use a single expression without a subquery to update a list of columns. User Response: Check the syntax for using subqueries to update data and add the required subquery. ORA-01768 numeric string too long Cause: A number entered exceeds the 255 character limit, including digits, sign, decimal point, and exponent. Action: Shorten the string of numbers, perhaps expressing them in scientific notation, for example, 1.85E9 instead of 1,850,000,000. ORA-01769 Duplicate CLUSTER option specifications Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option. Action: Remove the extra CLUSTER option. ORA-01770 The CLUSTER option is not allowed in the CREATE CLUSTER command Cause: An attempt was made to use the CLUSTER option in a CREATE CLUSTER statement. Action: Remove the CLUSTER clause and try again. ORA-01771 invalid option for a clustered table Cause: During CREATION or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE, CACHE, NOCACHE. These options can only be specified for the cluster itself. Action: Remove the illegal options. ORA-01772 You must specify a value for LEVEL Cause: The value of LEVEL was expected, but something else was specified. Action: Correct the error and issue the command again.

4-40

message error

ORA-01773 cannot specify column data types in this CREATE TABLE Cause: The column data types were specified in a SELECT statement used to directly create and load a table. User Response : Remove the column data types. The data types of SELECT list expressions are automatically used as column data types. ORA-01774 Undodump option specified more than once Cause: The same option for ALTER DUMP UNDO was specified twice. Action: Remove the redundant options and reissue the command. Chain of synonyms looping ORA-01775 Cause: Through a series of synonym CREATE statements, a synonym was defined that referred to itself. For example, the following definitions are circular: CREATE SYNONYM s1 for s2 CREATE SYNONYM s2 for s3 CREATE SYNONYM s3 for s1

User Response : Change a synonym definition to apply to a base table or view and retry the operation. ORA-01776 Cannot modify more than one base table through a join view Cause: Columns belonging to more than one underlying table were inserted or updated. Action: Formulate the statement as two or more separate statements. ORA-01777 WITH LEAVE OPTION not allowed on this system Cause: This version of Oracle does not support WITH LEAVE OPTION. Action: Remove the WITH LEASE option. ORA-01778 Maximum subquery nesting level exceeded Cause: An attempt was made to use more than 255 levels of nested subqueries. Action: Combine some of the subqueries in the containing queries until there are fewer than 255 levels of nesting. ORA-01779 cannot modify a column that is mapped to a table with no persisted key Cause: An attempt was made to insert or update columns from a join view that is mapped to a table with no persisted key. User Response : Modify the underlying base tables directly.

ORA-01500 to ORA-02099

4-41

ORA-01780 string literal required Cause: In a COMMENT statement, the comment after the IS keyword must be a quoted string literal. Action: Check that the comment is a string literal. ORA-01781 Unable to specify UNRECOVERABLE without AS SELECT Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a fill subquery with an AS clause. Action: Do not specify UNRECOVERABLE. ORA-01782 Unable to specify UNRECOVERABLE for a clustered or clustered table Cause: A clustered CREATE CLUSTER or CREATE TABLE statement specified UNRECOVERABLE. Action: Do not specify UNRECOVERABLE. ORA-01783 only one RECOVERABLE or UNRECOVERABLE clause can be specified Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement. Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement. ORA-01784 Cannot specify RECOVERABLE with database media recovery disabled Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not archived, they will be overwritten and the object that is created cannot be recovered from a backup made before the object was created. Action: Do not specify RECOVERABLE or restart the database with media recovery enabled. ORA-01785 The ORDER BY element must be the number of a SELECT list expression Cause: An ORDER BY element for an array expression is not a column number or the ORDER BY element is not a column number of the SELECT list. Action: The ORDER BY element must be a number between 1 and the number of columns in the SELECT list. Check the column number and repeat the instruction.

4-42

message error

ORA-01786 FOR UPDATE of this query expression is not allowed Cause: An attempt was made to use a FOR UPDATE clause on the result of a set expression involving GROUP BY, DISTINCT, UNION, INTERSECT, or MINUS. Action: Check the syntax, remove the FOR UPDATE clause, and try the statement again. ORA-01787 only one clause allowed per query block Cause: An attempt was made to use more than one WHERE, GROUP BY, CONNECT BY, or HAVING clause in the query. Action: Combine the duplicate clauses into a single clause and repeat the statement. ORA-01788 CONNECT BY clause required in this query block Cause: A START WITH clause was specified without a CONNECT BY clause. User Response : Check the syntax, specify a CONNECT BY clause, and try the statement again. ORA-01789 query block has an incorrect number of result columns. Cause: All queries that participate in a set expression do not contain the same number of columns as the SELECT list. Action: Verify that all queries in the defined expression have the same number of columns in the SELECT list. The ORA-01790 expression must have the same data type as the corresponding expression. Cause: A SELECT list item matches a SELECT list item with a different data type in another query for the same defined expression. Action: Check that all items in the corresponding SELECT list have the same data types. Use the TO_NUMBER, TO_CHAR, and TO_DATE functions to perform explicit data conversions. ORA-01791 is not a SELECT expression Cause: There is an incorrect ORDER BY element. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY elements must be constants, SELECT list expressions, or expressions whose operands are constants, or SELECT list expressions. Action: Remove the inappropriate ORDER BY element from the SELECT list and retry the statement.

ORA-01500 to ORA-02099

4-43

ORA-01792 The maximum number of columns in a table or view is 1000 Cause: An attempt was made to create a table or view with more than 1000 columns or to add more columns to a table or view that exceeds the maximum allowed limit of 1000 . Note that unused columns in the table count toward the 1,000-column limit. Action: If the error is the result of a CREATE command, reduce the number of columns in the command and resubmit. If the error is the result of an ALTER TABLE command, there are two options: ■

■

If the table contains unused columns, drop them by running ALTER TABLE DROP UNUSED COLUMNS before adding new columns. Reduce the number of columns in the command and resubmit.

Cause: When creating a table or view, more than 1000 columns were specified. User Response : Remove some columns from the table or view definition. If all the information is needed, split the columns into two tables or views and join the columns when performing the query. ORA-01793 The maximum number of index columns is 32 Cause: When creating an index, more than 32 columns were specified. User Response : Remove some columns from the index definition. If all the columns are needed to be indexed, split them into two indexes. ORA-01794 The maximum number of cluster columns is 32 Cause: More than 32 columns were specified in the cluster key. User Response : Remove some of the columns from the cluster key definition. Consider concatenating multiple strings in a single column. ORA-01795 The maximum number of expressions in a list is 1000 Cause: More than 254 columns or expressions were specified in a list. Action: Remove some of the expressions from the list. ORA-01796 This operator cannot be used with lists Cause: A relational operator is not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN. User Response: Rephrase the query so that it only compares lists for matches. For example, the following clause is not valid: WHERE (A,B) > ((C,D), (E,F))

4-44

message error

It may be necessary to compare individual columns separately. For example, to see if A and B are respectively greater than C and D, use WHERE A>B AND C>D instead of WHERE (A,B)>(C,D). ORA-01797 This operator must be followed by ANY or ALL Cause: The ANY or ALL keyword was missing. Action: Check the syntax of the declaration and add ANY or ALL where appropriate. ORA-01798 Missing EXCEPTION keyword Cause: The EXCEPTION keyword is missing from the ENABLE clause. Action: Correct the syntax. ORA-01799 A column cannot be externally joined to a subquery Cause: Repeating (+) expression (subquery) is not allowed. Action: Remove the (+) or create a view of the subquery. In V6 and earlier, the (+) was simply ignored in this case. ORA-01800 A literal in date format was too long to process Cause: A literal specified in a date format was too long. If a literal is entered as a date, it must be less than 220 characters. Action: Use only literals less than 220 characters in the date format. ORA-01801 date format is too long for internal buffer Cause: The date format string was too long to process. This should only happen if multiple long literals are specified as part of a date. User Response: Remove the long literals from the date format string. ORA-01802 Julian date is out of range Cause: An invalid Julian date was entered. Valid dates in the Julian period range from 1 to 3,442,447. Action: Please enter a valid Julian date between 1 and 3,442,447. ORA-01803 Failed to get timestamp Cause: This is an internal error message and is unlikely to occur. It is usually caused by a system clock failure. Action: Investigate the system clock and the process that requested the date or time. If necessary, contact customer service.

ORA-01500 to ORA-02099

4-45

ORA-01810 format code appears twice Cause: A format code was listed twice in a date specification. Each format code can be specified only once in the TO_DATE function. Action: Remove the duplicate format code from the date specification and retry the operation. ORA-01811 Julian date prevents use of day of year Cause: A Julian date and day of year were specified in the TO_DATE function. If a Julian date is specified, the day of the year (DDD) may not be specified, as it is contained in the Julian date. Action: Remove the day of the year or Julian date from the specification and retry the operation. The year ORA-01812 can only be specified once. Cause: More than one year format code was included in a date specification. Only one of the following year format codes can be specified in a date: YYYY, YYYY, YY, Y. Action: Remove all but one year format from the date specification. The ORA-01813 time can only be specified once. Cause: More than one time format code was listed in a date specification. Only one of the following time format codes can be specified in a date: HH, HH12, HH24. Action: Remove all time formats except one from the date specification. ORA-01814 AM/PM conflicts with the use of A.M./P.M. Cause: Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified. Action: Use a meridian indicator format, with or without dots, consistently. ORA-01815 BC/AD conflicts with the use of B.C./A.D. Cause: Both types of BC/AD flags were listed in a date specification. If one of the BC/AD flag format masks, such as BC or B.C., is specified in the date, the other may not be specified. Action: Use a BC/AD indicator format, with or without periods, consistently.

4-46

message error

ORA-01816 The month can only be specified once. Cause: More than one month format code was listed in a date specification. Only one of the following month format codes can be specified in a date: MM, MON, MONTH. Action: Remove all but one of the month formats from the date specification. ORA-01817 The day of the week can only be specified once. Cause: More than one weekday format code was listed in a date specification. Only one of the following weekday format codes can be specified in a date: D, DY, DAY. Action: Remove all but one of the weekday formats from the date specification. ORA-01818 'HH24' prevents the use of the meridian indicator Cause: A date specification contained a 24-hour time format code and a meridian indicator code. If times are specified using the 24-hour format (HH24), a meridian, AM, or PM indicator may not be specified. Action: Remove the meridian indicator format code, AM/PM or A.M./P.M., or the 24-hour format code, HH24, from the date specification. ORA-01819 signed year prevents use of BC/AD Cause: A date specification contained a signed year and a B.C./A.D. indicator. If the year is specified with a sign, such as SYYYY, then B.C. or AD it is implicit in the date and should not be entered. Action: Remove the B.C./A.D. date specification indicator. ORA-01820 format code cannot appear in date input format Cause: A date specification contained an invalid format code. Only the following can be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D. User Response: Remove the invalid format code from the date specification. ORA-01821 unrecognized date format Cause: A date specification contained an invalid format code. Action: Check that only valid date format codes are specified. The era format code ORA-01822 is invalid with this calendar Cause: An era format code, E or EE, was specified with a calendar that does not use era information.

ORA-01500 to ORA-02099

4-47

Action: Repeat the operation using a date format mask that does not contain era format codes. ORA-01830 date format image ends before converting entire input string Cause: A valid date format image included extra data. The first part of the format image was converted to a valid date, but the remaining data was not needed. Action: Check the date format image specifications and correct the declaration. The year ORA-01831 conflicts with the Julian date Cause: An incorrect year with a Julian day was specified. If a year with a Julian date is specified, it must be the year in which the Julian date occurs. Action: Remove the year value from the date specification or enter the correct year for the Julian date. ORA-01832 day of year conflicts with Julian date Cause: A Julian date with day of year was specified, but the day does not match the Julian date. If the day of the year is specified with a Julian date, it must be the same day as the Julian date. Action: Remove the day-of-year value from the date specification or enter the correct day for the Julian date. The month ORA-01833 conflicts with the Julian date. Cause: An incorrect month was specified with a Julian date. If a month with a Julian date is specified, it must be the month in which the Julian date occurs. Action: Remove the month value from the date specification or enter the correct month for the Julian date. ORA-01834 Julian day of month conflict Cause: A Julian date with the day of the month was specified, but the day of the month does not match the Julian date. If the day of the month is specified with a Julian date, it must be the same day of the month as the Julian date. Action: Remove the day of month value from the date specification or enter the correct day of month for the Julian date.

4-48

message error

ORA-01835 Weekday Julian date conflict Cause: A Julian date with the day of the week was specified, but the day of the week does not match the Julian date. If the day of the week is specified with a Julian date, it must be the same day of the week as the Julian date. Action: Remove the day of week value from the date specification or enter the correct day of week for the Julian date. ORA-01836 time conflicts with seconds of day Cause: An incorrect time with seconds of day was specified. If a time with seconds after midnight (SSSSS) is specified, it must be the time that the seconds value falls. Action: Remove the time value from the date specification or specify the correct time for seconds after midnight. ORA-01837 Hour minutes with day seconds conflict Cause: A date specification contained hour minutes and day seconds, but the values did not match. If minutes on the hour (MI) and seconds after midnight (SSSSS) are specified, the minutes value must be the minute that the seconds value occurs. User Response : Remove the minutes value from the date specification or enter the correct minutes value for the specified seconds value. ORA-01838 Minute seconds with day seconds conflict Cause: A date specification contained minute seconds and day seconds, but the values did not match. If both types of seconds are specified, the seconds in the minutes value (SS) must be the seconds into which seconds after midnight (SSSSS) will fall. Action: Remove the seconds from the minutes value of the date specification, or enter a value that matches the given seconds in the day. ORA-01839 invalid date for the specified month Cause: The day of the month specified in date is not valid for the specified month. The day of the month (DD) must be between 1 and the number of days in the month. Action: Enter a valid day of the month for the specified month. ORA-01840 input value is not long enough for date format Cause: The data to be converted to date format was incomplete; the date format image was longer than the input data.

ORA-01500 to ORA-02099

4-49

Action: Add more entries or shorten the date image format and repeat the operation. ORA-01841 Year (full) must be between -4713 and +9999 and not 0 Cause: A specified date in a year that is not in the valid date range. A valid date is any date between January 1, 4712 B.C. and December 31, 9999 AD. Action: Please enter a valid date value between 4712 B.C. and 9999 AD ORA-01842 quarter must be between 1 and 4 Cause: An invalid value was specified for the quarter of the year on a date. The quarter (Q) must be between 1 and 4. Action: Enter a value for the quarter between 1 and 4. ORA-01843 is not a valid month Cause: A specified date is an invalid month. Valid months are: January-December for the MONTH format code and January-December for the MON format code. Action: Please enter a valid month value in the correct format. ORA-01844 Week of the year must be between 1 and 52 Cause: An invalid value was specified for the week of the year on a date. The week of the year (WW) must be between 1 and 52. Action: Enter a week of the year value between 1 and 52. ORA-01845 The week of the month must be between 1 and 5 Cause: A specified invalid value for week of month in a date. The week of the month (W) must be between 1 and 5. Action: Enter a week of the month value between 1 and 5. ORA-01846 is not a valid day of the week Cause: A date specified an invalid day of the month . week. Valid days are: ■

Monday to Sunday, for DAY format code

■

Lun-Dom, for DY format code

■

1-7, for format code D

Action: Enter a valid weekday value in the correct format.

4-50

message error

ORA-01847 the day of the month must be between the 1st and the last day of the month Cause: The day of the month indicated in a date is not valid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month. Action: Enter a valid day value for the specified month. ORA-01848 day of year must be between 1 and 365 (366 for leap year) Cause: An invalid day of year was specified on a date. The day of the year (DDD) must be between 1 and 365 for a non-leap year or between 1 and 366 for a leap year. Action: Enter a Day of Year value between 1 and 365 (or 366). ORA-01849 time must be between 1 and 12 Cause: An invalid time was specified for a date that uses the 12-hour format. If a 12-hour format code (HH or HH12) is used, the specified hour must be between 1 and 12. Action: Enter an hour value between 1 and 12. The ORA-01850 hour must be between 0 and 23 Cause : An invalid time The time value was specified for a date using the 24-hour format. If the 24-hour format code (HH24) appears, the specified hour must be between 0 and 23. Action: Enter an hour value between 0 and 23. ORA-01851 minutes must be between 0 and 59 Cause: A invalid minute value the number was specified in a date. Minutes must be between 0 and 59. Action: Enter a minutes value between 0 and 59. ORA-01852 Seconds must be between 0 and 59 Cause: An invalid seconds value was specified in a date. Seconds must be between 0 and 59 if the Seconds (SS) format code is used. Action: Enter a seconds value between 0 and 59. ORA-01853 Seconds in day must be between 0 and 86399 Cause: An invalid value was specified for seconds in day on a date. Seconds must be between 0 and 86399 if the Seconds After Midnight (SSSSS) format code is used. Action: Specify a seconds value between 0 and 86399.

ORA-01500 to ORA-02099

4-51

ORA-01854 Julian date must be between 1 and 5373484 Cause: An invalid Julian date was entered. Action: Please enter a valid Julian period date between 1 and 5373484. ORA-01855 AM/A.M. o PM/PM Required Cause: A date specification contained a meridian flag format code, but no valid meridian flag was specified. If a meridian indicator code, A.M./P.M. o AM/PM, is included in a date format, the date must include a valid meridian indicator. Action: Specify the meridian indicator in the correct format, AM/AM or PM/PM. ORA-01856 A.C./A.C. or AD/A.D. required Cause: A date specification contained a BC/AD format code, but no valid BC/AD flag was specified. If one of the format codes BC/AD, BC/AD, or B.C./A.D. in a date format, the date must include BC/B.C. or AD/A.D. Action: Specify the BC/AD flag on the date using the correct format. ORA-01857 is not a valid time zone Cause: An incorrect time zone code was specified for the NEW_TIME function. Action: Correct the invalid time zone code and retry the operation. ORA-01858 A non-numeric character was found where a numeric character was expected Cause: The input data to be converted using a date format template was incorrect. The input data did not contain a number when the format model required a number. User Response : Correct the input data or date format template to ensure that the elements match in number and type. Then repeat the operation. ORA-01859 Non-alphabetic character found where alpha character expected Cause: The input data to be converted using a date format template was incorrect. The input data did not contain a letter when the format model required a letter. User Response : Correct the input data or date format template to ensure that the elements match in number and type. Then repeat the operation.

4-52

message error

ORA-01860 Week of the year must be between 1 and 53 Cause: A week number outside the range 1 to 53 was specified. Action: Use only a value within the valid range for the week number. Literal ORA-01861 does not match format string Cause: Literals in input must have the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier was activated, the literal must match exactly, with no extra whitespace. User Response: Correct the format string to match the literal. ORA-01862 Numeric value does not match length of format element Cause: When format codes FX and FM are specified for an input date, the number of digits must be exactly the number specified by the format code. For example, 9 will not match the DD format specifier, but 09 will. Action: Correct the input date or disable the FX or FM format specifier in the format string. ORA-01863 The year is not compatible with the current calendar Cause: The year is not compatible with the current calendar. Action: Check the documentation to find out which years are supported by the current calendar. ORA-01864 Date is outside the current calendar range Cause: Your calendar does not extend to the specified date. Action: Specify a legal date for this calendar. ORA-01865 is not a valid era Cause: The era entry does not match a known era. Action: Provide a valid era in the input. ORA-01866 Datetime class is invalid Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-01867 range is invalid Cause: The string you specified is not a valid range. Action: Specify a valid range.

ORA-01500 to ORA-02099

4-53

ORA-01868 Range initial precision is too small Cause: Range initial precision is too small to store the specified range. Action: Increase the initial precision of the range or specify a range with a lower initial precision. ORA-01869 reserved for future use Cause: Not an error. Action: No action is required. ORA-01870 The ranges or the datetime are not comparable to each other Cause: The ranges or the datetime are not comparable to each other. Action: Specify a pair of intervals or dates that are comparable to each other. ORA-01871 number of seconds must be less than 60 Cause: The number of seconds specified was greater than 59. Action: Specify a value for seconds that is 59 or less. ORA-01872 reserved for future use Cause: Not an error. Action: No action is required. ORA-01873 The initial precision of the range is too small Cause: The initial precision of the range is too small to store the specified range. Action: Increase the initial precision of the range or specify a range with a lower initial precision. ORA-01874 time zone hour must be between -12 and 13 Cause: The specified time zone hour was not in the valid range. Action: Specify a time zone hour between -12 and 13. ORA-01875 Time zone minutes must be between -59 and 59 Cause: The specified time zone minutes were not in the valid range. Action: Specify a time zone minute between -59 and 59. The year ORA-01876 must be at least -4713 Cause: The specified year was not in the range.

4-54

message error

Action: Specify a year greater than or equal to -4713. ORA-01877 string is too long for internal buffer Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-01878 specified field not found in datetime or range Cause: The specified field was not found in datetime or range. User Response : Make sure the specified field is in date/time or range. ORA-01879 The hh25 field must be between 0 and 24 Cause: The specified hh25 field was not in the valid range. Action: Specify an hh25 field between 0 and 24. ORA-01880 split seconds must be between 0 and 999999999 Cause: The specified split seconds were not in the valid range. Action: Specify a value for fractional seconds between 0 and 999999999. ORA-01890 NLS Error Detected Cause: An NLS error was detected. Action: Check for additional error messages and take appropriate action. If there are no additional errors, call Oracle Customer Support. ORA-01891 Internal date/time/range error Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-01898 too many precision specifiers Cause: When trying to truncate or round dates, extra data was found in the date format image. Action: Check the syntax of the date format image and try again. Invalid precision specifier ORA-01899 Cause: An invalid precision code was specified for a date. User Response : Enter a valid precision code in date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds.

ORA-01500 to ORA-02099

4-55

Expected Keyword ORA-01900 LOGFILE Cause: Missing keyword. Action: Provide the missing keyword. ORA-01901 ROLLBACK keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01902 SEGMENT keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. Expected Keyword ORA-01903 EVENTS Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01904 DATAFILE keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01905 STORAGE keyword expected Cause: Missing keyword. Action: Provide the missing keyword. ORA-01906 BACKUP keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01907 Expected TABLESPACE keyword Cause: Missing keyword. Action: Provide the missing keyword. Expected Keyword ORA-01908 EXISTS Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01909 REUSE keyword expected Cause: A keyword is missing.

4-56

message error

Action: Provide the missing keyword. ORA-01910 TABLES keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01911 Expected CONTENTS keyword Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01912 ROW keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01913 EXCLUSIVE keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01914 Invalid audit option for sequence numbers Cause: AUDIT or NOAUDIT on a sequence number specifies an audit option that is invalid for sequence numbers. Action: The following options cannot be used for sequence numbers and must be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE. ORA-01915 Invalid audit option for views Cause: AUDIT or NOAUDIT on a view specifies an audit option that is not valid for views. Action: The following options cannot be used for views and must be removed: ALTER, INDEX, REFERENCES, RUN. ORA-01916 ONLINE, OFFLINE, RESIZE, AUTOEXTEND, or END/DROP keyword expected Cause: An expected keyword was not used for the DATAFILE/TEMPFILE clause Action: Use the correct syntax. ORA-01917 User or role 'string' does not exist Cause: A user or role with that name does not exist.

ORA-01500 to ORA-02099

4-57

Action: Re-enter the name. ORA-01918 user 'string' does not exist Cause: The user does not exist in the system. Action: Check that the username is correct. ORA-01919 Function 'string' does not exist Cause: The function with that name does not exist. Action: Verify that you are using the correct role name. ORA-01920 Username 'string' conflicts with another username or role Cause: A user or role with that name already exists. Action: Specify a different username. ORA-01921 role name 'string' conflicts with another user or role name Cause: A user or role with that name already exists. Action: Specify a different role name. ORA-01922 CASCADE must be specified to remove 'string' Cause: Cascade is required to remove this user from the system. The user's own object to be disposed of. Action: Specify the cascade. ORA-01923 CASCADE aborted, objects locked by another user Cause: Cannot drop user objects; someone locked them up. Action: Use the lock monitor to determine who has locked objects. ORA-01924 role "string" not granted or does not exist Cause: The defined role can only be performed with roles granted directly to your account (for example, a subrole cannot be enabled). Action: Do not try to define the function. ORA-01925 String maximum enabled roles exceeded Cause: The MAX_ENABLED_ROLES initialization parameter was exceeded. Action: Increase MAX_ENABLED_ROLES and warm start the database. ORA-01926 role cannot be GRANTED WITH GRANT OPTION Cause: Role cannot have a privilege with grant option.

4-58

message error

Action: Perform the grant without the grant option. ORA-01927 cannot REVOKE privileges that you have not granted Cause: You can only revoke privileges that you have granted. Action: Do not revoke these privileges. ORA-01928 GRANT option not granted for all privileges Cause: To grant a privilege, you must first have the privilege with the grant option. Action: Get the privilege with the grant option and try again. ORA-01929 No privileges for GRANT Cause: "ALL" was specified but the user does not have any privileges with the grant option. Action: Do not grant privileges on this object. ORA-01930 Object auditing is not supported Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited. Action: Do not try to LIFT the object. ORA-01931 A role cannot be granted a string Cause: The UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA, or SYSOPER privilege cannot be granted to a role. Action: Grant the privilege directly to the user. ORA-01932 ADMIN option not granted for role 'string' Cause: The operation requires the ADMIN option on the role. Action: Get the lease option and try again. ORA-01933 unable to create a stored object using the privileges of a role Cause: An attempt was made to create a stored object using the privileges of a role. Stored objects cannot use role privileges. Action: Grant the necessary privileges directly to the user. ORA-01934 circular role grant detected Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself.

ORA-01500 to ORA-02099

4-59

Action: Do not carry out the lease. ORA-01935 Missing username or role Cause: A username or role was expected. Action: Specify a user name or a role. ORA-01936 cannot specify owner when creating users or roles Cause: Users and roles do not have owners. Action: Do not specify an owner. ORA-01937 Invalid or missing role name Cause: A valid role name was expected. Action: Specify a valid role name. ORA-01938 IDENTIFIED BY must be specified for CREATE USER Cause: Cannot create a user without specifying a password or EXTERNALLY IDENTIFIED. Action: Specify one of the password clauses. ORA-01939 only ADMINISTRATOR OPTION can be specified Cause: System roles and privileges can only be granted with the ADMINISTRATOR option. The grant option cannot be used with these privileges. Action: Specify the ADMIN option. ORA-01940 cannot logoff a user who is currently logged in Cause: An attempt was made to logout a user who is currently logged in. Action: Make sure the user is logged out and try the command again. ORA-01941 SEQUENCE keyword expected Cause: A keyword is missing. Action: Provide the missing keyword. ORA-01942 Cannot specify IDENTIFIED BY and EXTERNALLY Cause: Cannot specify that a user has and does not have a password. Action: Specify only one of the options. ORA-01943 IDENTIFIED BY already specified Cause: The IDENTIFIED clause was supplied twice.

4-60

message error

User Response: Use only an IDENTIFIED BY clause. ORA-01944 EXTERNALLY IDENTIFIED already specified Cause: The EXTERNALLY IDENTIFIED clause was supplied twice. Action: Use only an IDENTIFIED clause. ORA-01945 DEFAULT ROLE[S] already specified Cause: The DEFAULT ROLES clause was supplied twice. User Response: Use only a DEFAULT ROLE clause. ORA-01946 DEFAULT TABLESPACE already specified Cause: The DEFAULT TABLESPACE clause was supplied twice. User Response: Use only a DEFAULT TABLESPACE clause. ORA-01947 TEMPORARY TABLESPACE already specified Cause: The TEMPORARY TABLESPACE clause was supplied twice. User Response: Use only a TEMPORARY TABLESPACE clause. ORA-01949 ROLE keyword expected Cause: The ROLE keyword is required here. Action: Specify the ROLE keyword. ORA-01950 No privileges on tablespace 'string' Cause: The user does not have privileges to allocate an extent on the specified tablespace. Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace. ORA-01951 ROLE 'string' not granted to 'string' Cause: The role you tried to revoke was not granted to the user. Action: Do not attempt to revoke a privilege that has not been granted. ORA-01952 System privilege not granted to 'string' Cause: A system privilege that you tried to revoke was not granted to the user. Action: Ensure that the privileges you are trying to revoke are granted.

ORA-01500 to ORA-02099

4-61

The ORA-01953 command is no longer valid, see ALTER USER Cause: The syntax for assigning quotas on table spaces has changed. The ALTER USER command is now used to perform the functionality. Action: Use the ALTER USER command instead. ORA-01954 DEFAULT ROLE clause is invalid for CREATE USER Cause: Default roles cannot be specified for create user. Action: Grant and change the user's default roles after the user is created. ORA-01955 DEFAULT ROLE 'string' not granted to user Cause: The user being changed is not granted the specified role directly to the user. Note that child roles cannot be used in the DEFAULT ROLE clause. Action: Grant the role to the user. ORA-01956 invalid command when using OS_ROLES Cause: This command cannot be used when the initialization parameter OS_ROLES is TRUE. Action: Grant the role to the user in the operating system. ORA-01957 Expected MIN or MAX keyword not found Cause: The MIN or MAX keyword was expected as an argument. Action: Enter the MIN or MAX keyword and retry the operation. ORA-01958 You must provide an integer for the LAYER option Cause: An element that is not an integer was entered for the LAYER option. Action: Enter an integer for the LAYER option and repeat the operation. ORA-01959 You must provide an integer for the OPCODE option Cause: An element that is not an integer was entered for the OPCODE option. The value in ALTER SYSTEM DUMP... OPCODE must be an integer. Action: Enter an integer for the OPCODE option and retry the operation. For more information on the OPCODE option, see the Oracle8i SQL Reference. ORA-01960 Invalid dump log file option Cause: An invalid option was entered for the ALTER SYSTEM DUMP LOGFILE option command. Action: For a list of valid options for DUMP LOGFILE, see the Oracle8i SQL Reference.

(Video) Das Oracle Problem - eine unausweichliche Tatsache (v1.13)

4-62

message error

ORA-01961 Invalid dump option Cause: An invalid option was entered for the ALTER SYSTEM DUMP command. Action: Enter a valid option for ALTER SYSTEM DUMP. Examples of valid options are LOGFILE and UNDO. For more information on the DUMP option, see the Oracle8i SQL Reference. ORA-01962 You must specify a log file number or sequence number Cause: An invalid log file number or sequence number was specified. User Response : Enter a valid file number or log sequence number and retry the operation. For more information on valid file and record sequence numbers, see the Oracle8i SQL Reference. ORA-01963 You must specify a block number Cause: An invalid block number was specified. Action: Enter a valid block number and retry the operation. For more information on valid block numbers, see the Oracle8i SQL Reference. ORA-01964 You must specify a time for the TIME option Cause: A value was entered for the TIME option that could not be interpreted as a date. Action: Enter a valid date. For more information on the TIME option, see the Oracle8i SQL Reference. ORA-01965 You must specify a PERIOD Cause: There is a missing period between the file number and the block number. Action: Insert a period between the file number and the block number and repeat the operation. For more information on file numbers and block numbers, see the Oracle8i SQL Reference. ORA-01967 Invalid option to CREATE CONTROL FILE Cause: There is an invalid CREATE CONTROL FILE option. User Response: Only specify valid CREATE CONTROLFILE options. ORA-01968 Specify RESETLOGS or NORESETLOGS only once Cause: The RESETLOGS or NORESETLOGS keyword appeared more than once. Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.

ORA-01500 to ORA-02099

4-63

ORA-01969 You must specify RESETLOGS or NORESETLOGS Cause: A RESETLOGS or NORESETLOGS is missing. Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. ORA-01970 You must specify a database name for CREATE CONTROLFILE Cause: Missing database name. Action: Retype the CREATE CONTROLFILE command with the DATABASE keyword. ORA-01971 Invalid ALTER TRACING option Cause: There is an invalid ALTER TRACING option. Action: Specify only valid ALTER TRACING options. Examples of valid options are ENABLE and DISABLE. For more information, see the Oracle8i SQL Reference. ORA-01972 You must specify a string for ALTER TRACING ENABLE or DISABLE Cause: Something other than a valid identifier was specified for ALTER TRACING ENABLE or DISABLE. Action: Specify a valid identifier for ALTER TRACING ENABLE or DISABLE and retry the operation. For more information on valid identifiers, see the Oracle8i SQL Reference. ORA-01973 Missing change number Cause: The CHANGE keyword was found, but the change number was not specified. Action: Correct the command line and resubmit. ORA-01974 Invalid Archive Option Cause: An invalid option was specified for the ALTER SYSTEM ARCHIVE command. Action: Check the command syntax and try again. ORA-01975 Invalid character in change number string Cause: An invalid change number was supplied. Action: Resubmit the command with a valid change number. ORA-01976 Missing change number Cause: A change number was required but not provided.

4-64

message error

Action: Check the syntax of the command, provide a change number where necessary, and try the command again. ORA-01977 Missing thread number Cause: The keyword THREAD was found but the thread number was not specified. Action: Correct the command line and resubmit. ORA-01978 Missing sequence number Cause: The SEQUENCE keyword was found, but the sequence number was not specified. Action: Correct the command line and resubmit. ORA-01979 Missing or invalid password for function 'string' Cause: An attempt was made to enable a function without providing the correct password. Action: Use the IDENTIFIED BY clause in SET ROLE to specify the correct password. ORA-01980 error during OS ROLE initialization Cause: An operating system error occurred while loading a user OS ROLE. Action: Check the operating system error. ORA-01981 CASCADE CONSTRAINTS must be specified to perform this revocation. Cause: During this revocation, some foreign key constraints will be removed. To achieve this automatically, CASCADE CONSTRAINTS must be specified. Action: Remove the constraints or specify CASCADING CONSTRAINTS. ORA-01982 invalid audit option for tables Cause: AUDIT or NOAUDIT on a table specifies an audit option that is not legal for tables. Action: The following options cannot be used for tables and must be removed: REFERENCES, RUN. ORA-01983 invalid audit option for DEFAULT Cause: AUDIT or NOAUDIT on DEFAULT specifies an audit option that is not legal for DEFAULT. Action: The following options cannot be used for STANDARD and must be removed: REFERENCES.

ORA-01500 to ORA-02099

4-65

ORA-01984 invalid audit option for procedures/packages/functions Cause: AUDIT or NOAUDIT on DEFAULT specifies an audit option that is not legal for procedures, packages, or functions. Action: The following options cannot be used for procedures, packages, and functions and must be removed: all except EXECUTE. ORA-01985 Cannot create user because LICENSE_MAX_USERS parameter is exceeded Cause: The maximum user limit in the database has been exceeded. Action: Increase the license limit. ORA-01986 Invalid option for OPTIMIZER_GOAL Cause: An invalid OPTIMIZER_GOAL option exists. Action: Check the syntax of OPTIMIZER_GOAL, specify a valid option, and rerun the statement. ORA-01987 Client operating system username is too long Cause: The client operating system username is too long to successfully log on to the operating system. Action: Use a shorter operating system username. ORA-01988 Remote OS login not allowed Cause: An attempt was made to log in to the remote OS when it was not allowed. Action: Use a local client or use the REMOTE_OS_AUTHENT system parameter to enable remote operating system login. ORA-01989 role 'string' not authorized by OS Cause: The OS role does not exist, was not granted, or did not provide the correct password. Action: Retry SET ROLE with a valid operating system role and password, if necessary. ORA-01990 error opening password file 'string' Cause: An attempt to open the specified password file failed due to one of the following errors: ■

An operating system error has occurred.

■

ORAPWD is already running, so the password file is locked.

The environment variables ORA_sid_PWFILE and ORA_PWFILE are not defined.

4-66

message error

Action: Check the causes above and correct as necessary. ORA-01991 invalid password file 'string' Cause: The specified password file name is invalid. Action: Specify a correct password file name. ORA-01992 error closing password file 'string' Cause: The password file could not be closed due to an operating system error or a failed authentication action. Action: Check the causes above and correct as necessary. ORA-01993 error writing password file 'string' Cause: The password file could not be written due to an operating system error or a failed authentication action. Action: Check the causes above and correct as necessary. ORA-01994 GRANT failed: Could not add users to shared password file Cause: A grant failed because a user could not be added to the password file. This is because the value of the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED. Action: To add a user to the password file, close the database, change the initialization parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE, and restart the database. ORA-01995 error reading password file 'string' Cause: An operating system error occurred while trying to read the password file. Action: Correct the operating system error. ORA-01996 GRANT failed: password file 'string' is full Cause: Grant failed when a user could not be added to the password file because all available slots in the password file have already been used. Action: Create a larger password file or free slots in the password file by revoking SYSOPER and SYSDBA privileges from some of the remote users. You can determine which remote users are valid and their privileges by issuing the following SQL*DBA query: SELECT * FROM V$REMOTE_USERS;

ORA-01500 to ORA-02099

4-67

ORA-01997 GRANT failed: user 'string' was identified externally Cause: You cannot grant the SYSOPER or SYSDBA privilege to a user created with the IDENTIFIED EXTERNALLY clause. Action: If you want to give the user SYSOPER or SYSDBA privileges, drop and recreate the user without the IDENTIFIED EXTERNALLY clause. ORA-01998 REVOKE failed: SYS user always has SYSOPER and SYSDBA Cause: You tried to revoke one of the required privileges, SYSOPER or SYSDBA, from the SYS user. These privileges cannot be revoked. Action: Do not attempt this operation. ORA-01999 password file mode changed from 'string' to 'string' Cause: Another instance was started with the FORCE_PASSWORD_FILEMODE startup parameter, which is incompatible with your instance's startup mode. Action: Shut down your instance and restart it later when the password file changes for the other instance are complete. Missing string keyword ORA-02000 Cause: The inserted statement requires the missing keyword. Action: Use the specified keyword. ORA-02001 SYS user does not have permission to create indexes with free list groups Cause: An attempt was made to create an index while running with SYS authority. Action: Cannot create indexes with SYS authority. Do not create the index or change to USER authority. ORA-02002 error writing to audit trail Cause: The audit function cannot write to the AUDIT_TRAIL table. If this error occurs, the SQL statements being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space. User Response: Add space to the SYSTEM tablespace or remove rows from the AUDIT_TRAIL table. If these operations fail or do not fix the problem, shutdown and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE. ORA-02003 Invalid USERENV parameter Cause: An invalid parameter was specified for the USERENV function.

4-68

message error

Action: Specify one of the allowed parameters TERMINAL, SESSIONID, ENTRYID, or NLS_LANG. Security Violation ORA-02004 Cause: A user is attempting to perform an operation without proper permission and this fact is being logged in the AUDIT_TRAIL table. This message only appears in the return code column of the AUDIT_TRAIL table. Action: For audit information only; No action is required. ORA-02005 Invalid implicit length (-1) for this definition or binding data type Cause: A negative length for the definition variable was passed to a define function. Action: An explicit, non-negative length parameter must be passed. ORA-02006 invalid packed decimal format string Cause: A packed decimal data type was passed to a function or binding definition, and the format string parameter was missing or invalid. User Response: A valid format string parameter must be passed to a packed decimal variable. See your programming manual for the definition of a packed decimal format string. ORA-02007 cannot use ALLOCATE or DEALLOCATE options with REBUILD Cause: Storage allocation or deallocation and rebuild index are not supported. Action: Choose one or the other. ORA-02008 A non-zero scale was specified for a non-numeric column Cause: A scale factor was specified for a binding or definition of a non-numeric variable. Action: Set the scale factor to zero and retry the operation. ORA-02009 The size specified for a file must not be zero Cause: A zero value was specified in a SIZE or RESIZE clause of a file specification. User Response : Use the correct syntax or, if allowed, omit the SIZE or RESIZE clause. ORA-02010 missing host connection string Cause: A quoted string does not follow the USING keyword in the USING clause of a CREATE DATABASE LINK statement. Action: Specify the host connection string and retry the operation.

ORA-01500 to ORA-02099

4-69

ORA-02011 duplicate database link name Cause: The database link name specified in a CREATE DATABASE LINK statement already exists. Action: Specify a new name or remove the existing link. ORA-02012 Missing USING keyword Cause: The USING keyword does not follow the CONNECT TO clause in a CREATE DATABASE LINK statement. Action: Specify the USING clause after the CONNECT TO clause. ORA-02013 Missing CONNECT keyword Cause: The CONNECT keyword does not follow the database link name in a CREATE DATABASE LINK statement. User Response: Specify the CONNECT clause after the database link name. ORA-02014 cannot select TO UPDATE to view with DISTINCT, GROUP BY, etc. Cause: An attempt was made to SELECT...TO UPDATE on a view whose SELECT statement definition uses at least one of the following constructs in its outer block: outer join, GROUP BY clause, aggregate functions, SELECT DISTINCT clause, CONNECT BY clause, or set the UNION, INTERSECT, or MINUS operation. Action: Do not use SELECT... TO UPDATE in this view. ORA-02015 cannot select TO UPDATE from a remote table Cause: An attempt was made to SELECT... TO UPDATE from a table in a remote database. Action: It is currently not possible to SELECT... TO UPDATE from a table in a remote database. Instead, log in or connect directly to the remote database before entering SELECT... TO UPDATE on your tables. ORA-02016 cannot use a subquery in a START WITH on a remote database Cause: An attempt was made to use a subquery in a START WITH clause. This subquery is currently not allowed if the table in the FROM clause of the tree query is in a remote database. Action: You must connect directly to the remote database before using a subquery in the START WITH clause.

4-70

message error

ORA-02017: integer value required Cause: The specified value must be an integer. Action: Specify a suitable integer value and retry the operation. ORA-02018 DB link with the same name has an open connection Cause: The user is currently connected to a PUBLIC DB link with the same name as the DB link specified in a CREATE or DROP statement DATABASE LINK. Action: Close the cursors that use the PUBLIC database link. ORA-02019 Connection description for remote database not found Cause: An attempt was made to connect or log in to a remote database using a connection description that could not be found. User Response : Specify an existing database link. Query the data dictionary to see all existing database links. Consult your operating system-specific Net8 documentation for valid connection descriptors. ORA-02020 Too many database links in use Cause: The current session has exceeded the maximum of INIT.ORA OPEN_LINKS. Action: Raise the OPEN_LINKS threshold or release some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases. ORA-02021 DDL operations are not allowed on a remote database Cause: An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE[email protected]". Action: To change the structure of the remote database, you must connect to the remote database with the appropriate privileges. The ORA-02022 remote statement has an unoptimized view with the remote object Cause: The local view is not optimized and contains references to objects in the remote database and the statement should be executed in the remote database Action: Create a similar view in the remote database and modify the offending view in the SQL statement with the new one[email protected]

ORA-01500 to ORA-02099

4-71

ORA-02023 The remote database cannot evaluate the START WITH or CONNECT BY predicate Cause: The statement contains a tree query on a remote database and the START WITH or CONNECT BY predicate of the tree query contains a term that cannot be evaluated on the remote database. These terms include user function calls, USERENV calls, and ROWID references. Action: Remove the disallowed term, connect directly or log in to the remote database. Database link not found ORA-02024 Cause: The database link to be removed was not found in the dictionary. User Response: Correct the name of the database link. ORA-02025 all tables in the SQL statement must be in the remote database Cause: An SQL statement references tables from multiple databases and one or more remote databases are not Oracle servers. Action: Remote updates can only be performed if all the databases in the SQL statement are Oracle servers. Upgrade databases from older versions in a separate statement. ORA-02026 Missing keyword LINK Cause: A keyword is missing. Action: Provide the missing keyword. ORA-02027 Multiple row UPDATE of LONG column is not supported. Cause: A bind variable with a length greater than 4000 bytes is used to update a column, and the update statement updates more than one row. Action: You can only update a single row with this binding variable. The server does not support ORA-02028 getting an exact number of rows. Cause: The server does not support UPIALL, so getting an exact number of rows cannot be emulated on the user side. Action: Connect to a valid server or do not use an exact search. ORA-02029 Missing keyword for FILE Cause: A keyword is missing. Action: Provide the missing keyword.

4-72

message error

ORA-02030 can only select from fixed tables/views Cause: You are trying to perform an operation other than retrieving a fixed table/view. Action: You can only select rows from fixed tables/views. ORA-02031 no ROWID for fixed table or index-organized table Cause: Attempting to access the ROWID of a fixed table or index-organized table. Action: Do not access the ROWID of a fixed table or an index-organized table. ORA-02032 clustered tables cannot be used before creating a clustered index. Cause: The user attempted to execute a DML statement on a clustered table for which a clustered index was not created. User Response : Create the clustered index. ORA-02033 Clustered index already exists for this cluster Cause: A clustered index already exists for this cluster. Action: No action is required. ORA-02034 Speed link not allowed Cause: Speed link not allowed with given link variables. Trapped internally by the system. Action: No action is required. ORA-02035 Illegal bundle operation combination Cause: The user requested the UPI bundle execution call to perform an illegal bundle operation combination. Action: Use a valid combination of operations and try again. ORA-02036 Too many variables to describe with auto open cursor Cause: The UPI package execute call attempted to auto open and close the cursor in a describe operation. There were too many SELECT list items or binding variables to do this. Action: Explicitly opens and closes the cursor. ORA-02037 quickbind store not initialized Cause: An attempt was made to make a quickexecute call on an SQL statement that contained host variables without first executing a quickbind call.

ORA-01500 to ORA-02099

4-73

Action: Execute a quick link call before executing a quick play call. ORA-02038 definition is not allowed for type array Cause: A user attempted to define a selectlist variable of type "array". Arrays can only serve as host binding variables. Action: Correct the incorrect code. ORA-02039 Value binding is not allowed for array type Cause: The user attempted to bind the value of an array host variable. Arrays can only be linked by reference. Action: Correct the incorrect code. ORA-02040 Remote database chain does not support two-phase commit Cause: A distributed update of more than one database was attempted, but the named database does not support the prepare phase of two-phase commit phases, as determined by the characteristics of your login transaction. The transaction has been rolled back. Action: Do not attempt to update the named database unless it is the only database updated in the transaction. Distributed updates to more than one database in a single transaction can only be performed if all databases support the two-phase commit mechanism. ORA-02041 Client database did not start a transaction Cause: An update to a coordinated database occurred without the coordinator starting a distributed transaction. This can happen if a stored procedure commits and then makes updates and the stored procedure is called remotely. It can also happen if an external transaction monitor violates the XA protocol. Action: If the cause is the former, check that no commit is followed by an update. ORA-02042 Too many distributed transactions Cause: The distributed transaction table is full because there are too many active distributed transactions. Action: Increase the DISTRIBUTED_TRANSACTIONS parameter in the initialization parameter file, shutdown and restart Oracle, or run fewer transactions. If it is certain that there are not many concurrent distributed transactions, this could be an internal error. In that case, contact Oracle Customer Support. Shutting down and restarting the instance can be a workaround.

4-74

message error

ORA-02043 must end current transaction before executing chain Cause: A transaction is in progress and one of the following commands was issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. Action: COMMIT or ROLLBACK the current transaction and retry the command. ORA-02044 transaction manager login denied: transaction in progress Cause: A remote transaction manager attempted to log in while a distributed transaction was in progress. A protocol error occurred in the remote transaction manager. Action: Ends the current transaction. ORA-02045 Too many local sessions participating in a global transaction Cause: There are too many sessions at this site to accommodate this transaction. Action: Use an existing database link so that it is not necessary to create another session at the remote site. ORA-02046 distributed transaction already started Cause: This is an internal error that is not normally found. A server session received a BEGIN_TRAN remote procedure call before ending with a previous distributed transaction. Action: Contact Oracle Customer Support. ORA-02047 cannot join an ongoing distributed transaction Cause: This can only occur when trying to upgrade an Oracle version 6 database and an Oracle7 database in the same transaction because ■

■

There is a transaction in progress on a remote database that does not support two-phase commit. Updates are pending and an attempt was made to update a different database that does not support two-phase commit.

Action – Complete the current transaction before attempting the action that caused the error. ORA-02048 attempted to start a distributed transaction without logging Cause: The client program did not issue a distributed transaction login. This is an internal error.

ORA-01500 to ORA-02099

4-75

Action: Contact Oracle Customer Support. ORA-02049 timeout: Distributed transaction waiting for lock Cause: INIT.ORA DISTRIBUTED_LOCK_TIMEOUT seconds exceeded waiting for lock. Action: Treat as deadlock. ORA-02050 transaction chain rolled back, some remote databases may be in doubt Cause: Remote or network failure during a two-phase commit. Action: Notify operations; remote databases will be automatically resynchronized when the failure is fixed. ORA-02051 Another session failed in the same transaction Cause: A session failed in the same site with the same global transaction ID. Action: No action required; the transaction is automatically reversed. ORA-02052 Remote transaction failed on chain Cause: Some error occurred in a remote transaction on the named database link. Action: More descriptive messages will follow. Solve the problem specified in the following messages and try the operation again. ORA-02053 transaction chain compromised, some remote databases may be in doubt Cause: There was a network failure or remote failure during two-phase commit. Action: Notify the database administrator. Remote databases will be automatically resynchronized when the failure is fixed. ORA-02054 indoubt transaction string Cause: There was a network failure or a two-phase remote commit failure. Action: Notify the database administrator. Remote databases will be automatically resynchronized when the failure is fixed. Monitor the DBA_2PC_PENDING table for the result and resubmit the transaction if necessary.

4-76

message error

Distributed update operation failed ORA-02055; Rollback Required Cause: An error during a distributed update operation might not have reversed the full effects of the operation. Because some sites may be inconsistent with others, the transaction must be rolled back to a save point or rolled back completely. Action: Revert to a savepoint or revert the entire transaction and resubmit the reverted statements. ORA-02056 2PC: string: bad two-phase command number string string Cause: There was a two-phase handshake protocol error. Action: The transaction can be automatically reversed. Monitor the DBA_2PC_ PENDING table to determine the resolution. Enter the transaction again, if necessary. Contact Oracle Customer Support if necessary. ORA-02057 2PC: string: bad two-phase recovery state number string-string Cause: An internal error occurred in the two-phase recovery protocol. Action: Contact Oracle Customer Support. ORA-02058 No prepared transaction found with ID string Cause: No transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID was found in table PENDING_TRANS$ in prepared state. Action: Check the PENDING_TRANS$ table. ORA-02059 ORA-2PC-CRASH-TEST-string in commit comment Cause: This is a special comment used to test two-phase commit. Action: Do not use this special comment (enter a number from 1 to 10). ORA-02060 select to update specified a distributed table join Cause: An attempt was made to join tables in different remote databases in a SELECT...FOR UPDATE statement. User Response: Tables joined in a SELECT statement with the FOR UPDATE clause must reside in the same database. Simplify the SELECT...FOR UPDATE statement so that only one table in the same database. ORA-02061 lock table specified distributed table list Cause: The tables in a LOCK TABLE statement must reside in the same database. Action: Issue several LOCK TABLE commands.

ORA-01500 to ORA-02099

4-77

ORA-02062 distributed recovery received DBID string, expected string Cause: A database link on a coordinator no longer points to the expected database. The link may have been reset or a different database may have been mounted. Action: Restore the link definition or the remote database. ORA-02063 string preceding string string Cause: An Oracle error was received from a remote database link. Action: Review previous error messages. ORA-02064 Unsupported Distributed Operation Cause: One of the following unsupported operations was attempted: ■

■

Array performs a remote update with a subquery that references a database link, or An update of a long column with a binding variable and an update of a second column with a subquery that references a database link and a binding variable, or An acknowledgment is issued in a coordinated session of an RPC with OUT parameters.

Action: Simplify the remote update statement. ORA-02065 invalid option for ALTER SYSTEM Cause: The option specified for ALTER SYSTEM is not supported. Action: See the Oracle8i SQL Reference for information on supported options. ORA-02066 Missing or invalid MTS_DISPATCHERS text Cause: A string literal was expected but not found after ALTER SYSTEM SET MTS_DISPATCHERS. User Response: Place the string literal containing the dispatcher specification after ALTER SYSTEM SET MTS_DISPATCHERS. ORA-02067 Transaction or savepoint rollback required Cause: A failure has occurred (usually a trigger or stored procedure with multiple remote updates) such that all-or-nothing execution of a previous Oracle call cannot be guaranteed. Action: Return to a previous save point or reverse the transaction and resubmit.

4-78

message error

ORA-02068 after chain fatal error Cause: A fatal error (disconnection, Oracle fatal error) was received from the indicated database link. See the following error text. Action: Contact the remote system administrator. The global_names parameter ORA-02069 must be set to TRUE for this operation. Cause: A remote assignment of the declaration is required, but cannot be obtained because GLOBAL_NAMES must be set to TRUE to obtain it. Action: Issue ALTER SESSION SET GLOBAL_NAMES = TRUE if possible. ORA-02070 string String database does not support strings in this context Cause: The remote database does not support the named resource in the context in which it is used. Action: Simplify the SQL statement. ORA-02071 error initializing resources for remote database string Cause: A remotely specified capability table could not be loaded. Action: Contact Oracle customer support for the remote SQL*Connect product. ORA-02072 Distributed database network protocol mismatch Cause: This should never happen between different PRODUCTION versions of ORACLE, but can happen between alpha and beta versions, for example. Action: Upgrade to the previous version. ORA-02073 Sequence numbers are not supported in remote updates Cause: Sequence numbers cannot be used in INSERTS, UPDATES, or DELETES on remote tables. Action: Perform the operation without specifying a sequence number. ORA-02074 cannot be a string in a distributed transaction Cause: A commit or rollback attempt was made from a non-master session of a distributed transaction. Action: Only commit or revert from the main session. ORA-02075 Transaction chain state changed by another instance Cause: A forced commit or forced rollback was issued from a session in another instance.

ORA-01500 to ORA-02099

4-79

Action: Check if another Oracle instance is performing a pending transaction recovery. Query DBA_2PC_PENDING to determine the new status of the transaction. ORA-02076 sequence is not located together with the updated table or long column Cause: All referenced sequences must be located on the same node as the updated table or long column. Action: Correct the problem and resubmit the return. ORA-02077 Long column selects must come from collocated tables Cause: All tables returning long column values in a SELECT statement must be located on the same node. Action: Correct the problem and resubmit the return. ORA-02078 invalid configuration for ALTER SYSTEM FIXED_DATE Cause: An invalid value was used. Action: Use a correct value. ORA-02079 no new session can join a distributed commit transaction Cause: A call to UPI2BG was issued in a session for a transaction that started committing on a different branch; that is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager. Action: Contact Oracle Customer Support. ORA-02080 database link in use Cause: A transaction is active or a cursor is open on the database link provided in the ALTER SESSION CLOSE DATABASE LINK command. Action: Commit or revert and close all cursors ORA-02081 Database link not open Cause: An attempt was made to use a database link that is not currently open. Action: Troubleshoot the network or contact the remote database administrator to determine if the remote database problem is fixed. Contact your local database administrator to determine if the network issues have been resolved. Wait for the link to open and try the operation again.

4-80

message error

ORA-02082 a loopback database link must have a connection qualifier Cause: An attempt was made to create a database link with the same name as the current database. Action: This database binding needs a final qualifier to make the name unique. These qualifiers are specific to the operating system. See your operating system-specific Oracle documentation for more information on creating database links. ORA-02083 database name contains invalid character 'string' Cause: The supplied database name contains an invalid character. For example, there cannot be periods, semicolons, single quotes, double quotes, blank spaces, or non-printing characters in the database name. See the Oracle8i Administrator's Guide for naming rules. Action: Specify a valid database name. ORA-02084 Missing component in database name Cause: The full database name was not provided. Action: Specify the full name of the database. ORA-02085 database link string connected to string Cause: The database link tried to connect to a database with a different name. The database link name must be the same as the database name. Action: Create a database link with the same name as the database you are connecting to. ORA-02086 database name (link) too long Cause: The database name or the database link is too long. Database names and database links cannot be longer than 128 characters. User Response : Specify the correct database or database link name, or specify a name with fewer characters. ORA-02087 object locked by another process in the same transaction Cause: A database link is being used in the parallel server environment that goes back to the same instance. A session is trying to convert a lock that was taken by another session. Action: Get the most restrictive lock first. For example, if session 1 gets a shared lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or use the same session to access the object.

ORA-01500 to ORA-02099

4-81

ORA-02088 Distributed database option not installed Cause: The distributed database option is not installed on this site, so the requested operation is not possible. Action: Contact Oracle Customer Support for information on the distributed database option. ORA-02089 COMMIT is not allowed on a slave session Cause: COMMIT was issued on a session that is not the two-phase commit global coordinator. Action: Issue confirmation on the global coordinator only. Network error ORA-02090: callback attempt + passthrough Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02091 Transaction Rolled Back Cause: The distributed transaction is assigned to the system rollback thread and is trying to enter the prepared state, but the required number of non-ORADOED slots are not available, so the transaction is rolled back. If the transaction is canceled on a remote site, only ORA-02091 will be seen. If the transaction is interrupted on the host site, ORA-02091 and ORA-02092 will be seen. Action: Complete the current transaction and perform the required operation. ORA-02092 no slots in the transaction table for distributed transaction Cause: the transaction is attributed to the rollback segment of the system and is trying to enter the READY state, more than the necessary number of non-READY slots are not available, therefore, the transaction is rolled back. User Response : Add a rollback segment and retry the transaction. ORA-02093 TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) greater than maximum possible (string) Cause: The specified parameter value is greater than allowed on this port. Action: Use the default value or reduce it to less than the maximum. ORA-02094 replication option not installed Cause: The replication option was not installed on this site. Therefore, updatable snapshots, lazy RPCs, and other replication features were not available.

4-82

message error

Action: Install the replication option. The replication option is not part of the Oracle7 Server product and must be purchased separately. Please contact an Oracle sales representative if you need to purchase the replication option. The specified initialization parameter ORA-02095 cannot be modified Cause: The specified initialization parameter cannot be modified with this option. Action: See the Oracle8i Administrator's Guide for information on what scope the parameter can be modified. For more information on how to modify an initialization parameter, see the Oracle8i Reference. The specified initialization parameter ORA-02096 cannot be modified with this option Cause: Although the initialization parameter can be modified, it cannot be modified with the specified command. Action: See the Oracle8i Administrator's Guide for information on the scope in which the parameter can be modified. The ORA-02097 parameter cannot be modified because the specified value is invalid. Cause: Although the initialization parameter can be modified, the modified value is not acceptable for the parameter. Action: See the Oracle8i Administrator's Guide for the range of acceptable values for this parameter. Error ORA-02098 parsing index table reference (:I) Cause: Incorrect index table syntax (:I) was found. Action: This syntax is for internal Oracle use only.

ORA-01500 to ORA-02099

4-83

4-84

message error

5 ORA-02100 to ORA-04099 ORA-02100 PCC: out of memory (ie, could not be allocated) Cause: SQLLIB was unable to allocate enough memory to run the program. Action: Allocate more memory for the user session and run the program again. If the error persists, call Oracle Customer Service for assistance. ORA-02101 PCC: cursor cache inconsistent (uce/cuc mismatch) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02102 PCC: cursor cache inconsistent (no cuc entry for this uce) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02103 PCC: cursor cache inconsistent (cuc ref out of range) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02104 PCC: host cache inconsistent (no cuc available) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02105 PCC: cursor cache inconsistent (no cuc entry in cache) Cause: This internal error usually indicates a memory related error.

ORA-02100 to ORA-04099 5-1

Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02106 PCC: Inconsistent cursor cache (OraCursor nr is bad) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02107 PCC: This pgm is too old for the runtime library: redo the PCC Cause: The program was precompiled by an older version of Oracle Precompilers, which is incompatible with this version of SQLLIB. Action: Precompile the program with a newer version of the Oracle precompilers. ORA-02108 PCC: Invalid descriptor passed to runtime library Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02109 PCC: host cache inconsistent (location reference out of range) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02110 PCC: host cache inconsistent (invalid sqi type) Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02111 PCC: heap coherence error Cause: This internal error usually indicates a memory related error. Action: Check the program for memory-related errors, such as invalid pointers or array bounds violations. ORA-02112 PCC: SELECT..INTO returns too many rows Cause: A SELECT...INTO statement returned more rows than can be stored in the given host variable.

5-2

message error

Action: There are three possible solutions: 1.

Use the SELECT_ERROR=NO precompiler option.

Declare a host variable with a larger array dimension.

Declare a cursor or a cursor variable for the select statement.

ORA-02140 invalid table space name Cause: An identifier does not follow ALTER TABLESPACE. User Response : Specify a table space name after ALTER TABLESPACE. ORA-02141 Invalid OFFLINE option Cause: An option other than NORMAL or IMMEDIATE goes OFFLINE. Action: The user should not specify any option after NO CONNECTION or one of the NORMAL or IMMEDIATE options. ORA-02142 The ALTER TABLESPACE option is missing or invalid Cause: No valid option is present. Action: Use one of the valid options: add, rename, default, online, offline, read-only, read-write, start, and end. ORA-02143 Invalid STORAGE option Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause. Action: Specify only valid options. ORA-02144 no option specified for ALTER CLUSTER Cause: No ALTER CLUSTER option specified. Action: Specify one or more of the following options: PCTFREE, PCTUSED, SIZE, STORAGE. ORA-02145 Missing STORAGE option Cause: No STORAGE option was specified after STORAGE(. Action: Specify one or more STORAGE options in parentheses. ORA-02146 SHARED was specified multiple times Cause: SHARED option was specified multiple times times in a CREATE DATABASE statement Action : Specify the SHARED option only once.

ORA-02100 to ORA-04099 5-3

ORA-02147 Conflicting SHARED/EXCLUSIVE options Cause: The SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement. Action: Specify SHARED or EXCLUSIVE, but not both. ORA-02148 EXCLUSIVE specified multiple times Cause: The EXCLUSIVE option was specified multiple times in a CREATE DATABASE statement. Action: Specify the EXCLUSIVE option only once. ORA-02149 The specified partition does not exist Cause: The partition for the object was not found. Action: Try again with the correct partition name. ORA-02153 invalid VALUES password string Cause: An encoded password string does not follow the VALUES clause. User Response: Place a suitable encoded password string after the VALUES clause. ORA-02155 invalid DEFAULT table space identifier Cause: An identifier does not follow DEFAULT TABLESPACE. User Response : Put a table space name after DEFAULT TABLESPACE. ORA-02156 Invalid TEMPORARY tablespace identifier Cause: An identifier does not follow the TEMPORARY TABLESPACE. User Response: Place a table space name after the TEMPORARY TABLESPACE. ORA-02157 no options specified for ALTER USER Cause: No options were specified. Action: Specify at least one ALTER USER option. ORA-02158 Invalid CREATE INDEX option Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified. Action: Choose one of the valid CREATE INDEX options.

5-4

message error

ORA-02159 Installed DLM does not support releasable lock mode Cause: The parameter file specified GC_* parameters that allow the LCK process to release locks when not in use. This mode requires additional DLM support which is not available. Action: Specify the configuration parameters that do not require the additional function. ORA-02160 Index-organized table cannot contain columns of type LONG Cause: A column of type LONG defined for the index-organized table. User Response: Do not use columns of type LONG in tables organized by indexes. ORA-02161 invalid value for MAXLOGFILES Cause: A number does not follow MAXLOGFILES. Action: Specify a number after MAXLOGFILES. ORA-02162 invalid value for MAXDATAFILES Cause: A number does not follow MAXDATAFILES. Action: Specify a number after MAXDATAFILES. ORA-02163 invalid value for FREE LIST GROUPS Cause: A number does not follow FREE LIST GROUPS. Action: Specify a number after FREELIST GROUPS. ORA-02164 DATAFILE clause specified more than once Cause: The CREATE DATABASE command contains more than one DATAFILE clause. Action: Specify at most one DATAFILE clause. ORA-02165 Invalid option to CREATE DATABASE Cause: There is an invalid option to CREATE DATABASE. User Response: Only specify valid options for CREATE DATABASE. ORA-02166 ARCHIVELOG and NOARCHIVELOG specified Cause: ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement. Action: Specify at most one of these two options.

ORA-02100 to ORA-04099 5-5

ORA-02167 LOGFILE clause specified more than once Cause: The CREATE DATABASE command contains more than one LOGFILE clause. Action: Specify at most one LOGFILE clause. ORA-02168 invalid value for FREELISTS Cause: A number does not follow FREELISTS. Action: Specify a number after FREELISTS. ORA-02169 FREELISTS storage option is not allowed Cause: An attempt was made to specify the FREELISTS storage option. This option can only be specified during table creation or index creation. Action: Clear these options and repeat the statement. ORA-02170 FREELIST GROUPS storage option is not allowed Cause: An attempt was made to specify the FREELIST GROUPS storage option. This option can only be specified when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file. User Response : Repeat the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file. ORA-02171 invalid value for MAXLOGHISTORY Cause: A number does not follow MAXLOGHISTORY. Action: Specify a number after MAXLOGHISTORY. ORA-02172 The PUBLIC keyword is not suitable for a deactivation thread Cause: The PUBLIC keyword was specified for a deactivation. Action: Delete the keyword and resubmit. ORA-02173 invalid option for DROP TABLESPACE Cause: A token other than INCLUDE was found after the table space name or some text was found after INCLUDE CONTENT. Action: Do not put anything or just INCLUDE CONTENTS after the table space name. ORA-02174 Missing required thread number Cause: A thread number must be specified after the THREAD keyword.

5-6

message error

Action: Use the correct syntax. ORA-02175 invalid rollback segment name Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier after ROLLBACK SEGMENT was not found. Action: Put the segment name after ROLLBACK SEGMENT. ORA-02176 Invalid option for CREATE ROLLBACK SEGMENT Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. User Response: Specify one of the valid options: TABLESPACE and STORAGE. ORA-02177 Required group number is missing Cause: A group number must be specified after the GROUP keyword. Action : Check the command syntax, specify a group number after GROUP and try again. The correct syntax for ORA-02178 is: SET TRANSACTION READ { ONLY | WRITE } Cause: There is a syntax error in the user declaration. Action: Correct the syntax as indicated. ORA-02179 Valid Options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED } Cause: There is a syntax error in the user declaration. Action: Correct the syntax as indicated. ORA-02180 invalid option for CREATE TABLESPACE Cause: An invalid option is listed. Action: Specify one of the valid options: DATA FILE, DEFAULT STORAGE, ONLINE, OFFLINE. ORA-02181 invalid option for ROLLBACK WORK Cause: A non-TO token follows ROLLBACK [WORK]. Action: Do not put anything including the name A SAVEPOINT after ROLLBACK [WORK]. ORA-02182 expected save point name Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. Action: Place a save point name after TO [SAVEPOINT].

ORA-02100 to ORA-04099 5-7

ORA-02183 Valid Options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED } Cause: There is a syntax error in the user declaration. Action: Correct the syntax as indicated. ORA-02184 Resource quotas are not allowed in REVOKE Cause: In a revoke statement, a resource quota was specified. Action: Specify the privilege of the resource without the quota. ORA-02185 Non-WORK token follows COMMIT Cause: Non-WORK token follows COMMIT. Action: Put nothing or WORK after COMMIT. The ORA-02186 table space resource privilege might not appear with other privileges. Cause: An attempt was made to grant or revoke a resource share in the same statement where other privileges are granted or revoked. Action: Use a separate grant or revoke statement for the resource share privilege. ORA-02187 invalid quota specification Cause: In a grant or revoke statement, an attempt was made to grant a table space quota above the upper limit. Action: Grant a smaller tablespace quota. ORA-02189 ON table space required Cause: In a grant or revoke statement, the user specified a table space quota but did not follow it with the ON table space clause. Action: Specify the tablespace to which the quota will be applied with the ON tablespace clause. ORA-02190 keyword TABLES expected Cause: The keyword TABLES was expected after the name DROP CLUSTER INCLUDING. Action: Put TABLES after INCLUDE. ORA-02191 The correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs Cause: There is a syntax error in the user declaration.

5-8

message error

Action: Correct the syntax as indicated. ORA-02192 PCTINCREASE not allowed for rollback segment storage clauses Cause: The PCTINCREASE storage parameter was specified in a CREATE or ALTER ROLLBACK SEGMENT command. Action: Repeat the command without the PCTINCREASE clause. ORA-02194 event specification syntax error string (minor error string) next to 'string' Cause: There is a syntax error in an event specification. Action: Check the syntax and spelling and try again. ORA-02195 Attempt to create a string object in a string tablespace Cause: The object type is not consistent with the content of the tablespace. Action: Create an object in a different tablespace or change the user defaults. ORA-02196 PERMANENT/TEMPORARY option already specified Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once. Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. For more information on the CREATE TABLESPACE parameters, see the Oracle8i SQL Reference. ORA-02197 file list already specified Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified. User Response: Combine the DATAFILE/TEMPFILE clauses into a single clause. ORA-02198 ONLINE/OFFLINE option already specified Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once. Action: Specify at most one ONLINE or OFFLINE. ORA-02199 Missing DATAFILE/TEMPFILE clause Cause: A CREATE TABLESPACE statement is missing a DATAFILE/TEMPFILE clause. User Response: Specify a DATAFILE/TEMPFILE clause.

ORA-02100 to ORA-04099 5-9

ORA-02200 WITH GRANT OPTION not allowed for PUBLIC Cause: GRANT was attempted for PUBLIC WITH GRANT OPTION. User Response: Remove the WITH GRANT OPTION clause. The sequence ORA-02201 is not allowed here. Cause: An attempt was made to reference a stream in a source list. Action: Only one sequence can be referenced in a select list. ORA-02202 No more tables are allowed in this cluster Cause: An attempt was made to create a table in a cluster that already contains 32 tables. Action: Up to 32 tables can be stored per cluster. ORA-02203 INITIAL storage options not allowed Cause: An attempt was made to change the INITIAL storage option of a table, cluster, index, or rollback segment. These options can only be specified when the object is created. Action: Clear these options and repeat the statement. ORA-02204 ALTER, INDEX, REFERENCE, and EXECUTE are not allowed for views Cause: An attempt was made to grant or revoke an invalid privilege on a view. Action: Do not attempt to grant or revoke any of the ALTER, INDEX, or REFERENCES privileges on views. ORA-02205 only SELECT and ALTER privileges are valid for streams Cause: An attempt was made to grant or revoke an invalid privilege on a stream. Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES, or EXECUTE privileges on streams. ORA-02206 duplicate INITRANS option specification Cause: INITRANS is specified more than once. Action: Specify INITRANS at most once. ORA-02207 Invalid INITRANS option value Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value. Action: Choose a valid INITRANS value.

5-10

message error

ORA-02208 Duplicate MAXTRANS option specification Cause: MAXTRANS is specified more than once. Action: Specify MAXTRANS at most once. ORA-02209 Invalid MAXTRANS option value Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value. Action: Choose a valid MAXTRANS value. ORA-02210 no option specified for ALTER TABLE Cause: No ALTER TABLE option specified. Action: Specify at least one table modification option. ORA-02211 invalid value for PCTFREE or PCTUSED Cause: The value specified for PCTFREE or PCTUSED is not an integer between 0 and 100. Action: Choose an appropriate value for the option. ORA-02212 Duplicate PCTFREE option specification Cause: The PCTFREE option was specified more than once. Action: Specify PCTFREE at most once. ORA-02213 Duplicate PCTUSED option specification Cause: The PCTUSED option was specified more than once. Action: Specify PCTUSED at most once. ORA-02214 Duplicate BACKUP option specification Cause: The BACKUP option for ALTER TABLE was specified more than once. Action: Specify the option at most once. ORA-02215 Duplicate table space name clause Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement. User Response: Specify at most one TABLESPACE clause.

ORA-02100 to ORA-04099

5-11

ORA-02216 expected table space name Cause: A table space name is not present when required by the syntax of one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT. User Response : Specify a table space name when the syntax requires it. ORA-02217 duplicate storage option specification Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once. Action: Specify all storage options at most once. ORA-02218 Invalid INITIAL storage option value Cause: The value specified must be an integer. Action: Choose an appropriate integer value. ORA-02219 Invalid NEXT storage option value Cause: The value specified must be an integer. Action: Choose an appropriate integer value. ORA-02220 MINEXTENTS storage option invalid value Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS. Action: Specify an appropriate value. ORA-02221 invalid value for storage option MAXEXTENTS Cause: The value specified must be a positive integer greater than or equal to MINEXTENTS. Action: Specify an appropriate value. ORA-02222 Invalid value of storage option PCTINCREASE Cause: The value specified must be a positive integer. Action: Specify an appropriate value. ORA-02223 Invalid storage option OPTIMAL value Cause: The value specified must be an integer. Action: Choose an appropriate integer value.

5-12

message error

ORA-02224 EXECUTE privilege not allowed for tables Cause: An attempt was made to grant or revoke an invalid privilege on a table. Action: Do not attempt to grant or revoke the EXECUTE privilege on the tables. ORA-02225 only EXECUTE privilege is valid for procedures Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function, or package. Action: Do not attempt to grant or revoke any non-EXECUTE privileges on procedures, functions, or packages. ORA-02226 Invalid MAXEXTENTS value (maximum allowed: string) Cause: The specified MAXEXTENTS is too large for the database block size. This only applies to the SYSTEM rollback segment. Action: Specify a smaller value. ORA-02227 Invalid cluster name Cause: A cluster name was not formed correctly. Action: Check the rules for forming object names and enter an appropriate cluster name. ORA-02228 Duplicate SIZE specification Cause: The SIZE option was specified more than once. Action: Specify the SIZE option at most once. ORA-02229 Invalid SIZE option value Cause: The value specified must be an integer number of bytes. Action: Specify an appropriate value. ORA-02230 Invalid ALTER CLUSTER option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE was specified on an ALTER CLUSTER statement. Action: Specify only the legal options. ORA-02231 Missing or invalid option for ALTER DATABASE Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE was specified in the statement. Action: Specify only the legal options.

ORA-02100 to ORA-04099

5-13

ORA-02232 invalid MOUNT mode Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement. Action: Specify SHARED, EXCLUSIVE, or nothing after MOUNT. ORA-02233 Invalid CLOSE mode Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement. Action: Specify NORMAL, IMMEDIATE, or nothing after CLOSE. ORA-02234 Changes to this table are already logged Cause: The logging table to be added is a duplicate of another. Action: Do not add this changelog to the system; verify that the replication product system tables are consistent. ORA-02235 This table already logs changes to another table Cause: The table to be changed is already a change log for another table. User Response: Do not log changes to the specified base table in this table; verify that the replication product system tables are consistent. ORA-02236 Invalid filename Cause: A string literal was not used in the filename list of a LOGFILE, DATAFILE, or RENAME clause. Action: Use the correct syntax. ORA-02237 Invalid file size Cause: A non-integer value was specified in the SIZE or RESIZE clause. Action: Use the correct syntax. ORA-02238 file name lists have different numbers of files Cause: In a RENAME clause on ALTER DATABASE or TABLESPACE, the number of existing file names is not equal to the number of new file names. Action: Make sure there is a new filename to match each existing filename. ORA-02239 there are objects referencing this string Cause: The string to be discarded is still referenced by other objects.

5-14

message error

User Response : Make sure the sequence name is correct, or remove the constraint or object that references the sequence. ORA-02240 invalid value for OBJNO or TABNO Cause: A number does not follow OBJNO or TABNO. Action: Specify a number after OBJNO or TABNO. ORA-02241 must be in the format EXTENTS (FILE n BLOCK n SIZE n, ...) Cause: An error occurred in the extensions storage clause. User Response : Re-specify the store clause using the correct syntax and retry the command. ORA-02242 no option specified for ALTER INDEX Cause: No option specified. Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. ORA-02243 Invalid ALTER INDEX or ALTER SNAPSHOT option Cause: An option other than INITRANS, MAXTRANS, or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER SNAPSHOT statement. Action: Specify only the legal options. ORA-02244 invalid ALTER ROLLBACK SEGMENT option Cause: The STORAGE option was expected but not found. Action: Specify the STORAGE option. ORA-02245 Invalid ROLLBACK SEGMENT name Cause: An identifier was expected but not found after ALTER [PUBLIC] ROLLBACK SEGMENT. Action: Put a rollback segment name after SEGMENT. ORA-02246 Missing text from EVENTS Cause: A string literal was expected but not found after ALTER SESSION SET EVENTS. User Response: Place the string literal containing the event text after EVENTS.

ORA-02100 to ORA-04099

5-15

ORA-02247 No option specified for ALTER SESSION Cause: The SET EVENTS option was expected but was not found after ALTER SESSION. Action: Put the SET EVENTS option after ALTER SESSION. ORA-02248 invalid option for ALTER SESSION Cause: An option other than SET EVENTS was found after the ALTER SESSION command. Action: Specify the SET EVENTS option after the ALTER SESSION command and try again. ORA-02249 Missing or invalid value for MAXLOGMEMBERS Cause: A valid number does not follow MAXLOGMEMBERS. The specified value must be between 1 and the maximum number of members of the port-specific log file. Action: Specify a valid number after MAXLOGMEMBERS. ORA-02250 Constraint name is missing or invalid Cause: Constraint name is missing or invalid. User Response : Specify a valid identifier name for the constraint name. ORA-02251 subquery is not allowed here Cause: The subquery is not allowed here in the statement. User Response : Remove the subquery from the statement. ORA-02252 The check constraint condition did not complete successfully Cause: The search condition specified for the check constraint did not complete successfully. Action: Terminate the condition successfully. ORA-02253 constraint specification not allowed here Cause: The constraint specification is not allowed here in the declaration. User Response : Remove the constraint specification from the declaration. ORA-02254 DEFAULT expression not allowed here Cause: The default value expression is not allowed for the column here in the statement. User Response: Remove the default value expression from the declaration.

5-16

message error

ORA-02255: NOT NULL not allowed after DEFAULT NULL Cause: A NOT NULL specification conflicts with the default NULL. Action: Remove the NOT NULL or DEFAULT NULL specification and try again. ORA-02256 the number of reference columns must match the referenced columns Cause: The number of columns in the foreign key reference list is not equal to the number of columns in the referenced list . Action: Make sure that the reference columns match the reference columns. ORA-02257 maximum number of columns exceeded Cause: The number of columns in the keylist exceeds the maximum number. Action: Reduce the number of columns in the list. ORA-02258 Duplicate or conflicting NULL or NOT NULL specifications Cause: A duplicate or conflicting NULL or NOT NULL value was specified. Action: Delete one of the conflicting specifications and try again. ORA-02259 Duplicate UNIQUE KEY/PRIMARY KEY specifications Cause: A duplicate unique or primary key was specified. Action: Remove the duplicate specification and try again. Table ORA-02260 can only have one primary key Cause: Two or more primary keys were specified for the same table. Action: Delete the extra primary keys and try again. ORA-02261 This unique or primary key already exists in the table Cause: An already existing unique or primary key was specified for the table. Action: Remove the extra key and try again. ORA-02262 ORA-nnnnn occurs during type check of column default value expression Cause: The new column data type causes a type check error for the existing column default value expression. User Response : Remove the default value expression or do not change the data type of the column.

ORA-02100 to ORA-04099

5-17

ORA-02263 you need to specify the data type for this column Cause: The required data type for the column is missing. Action: Specify the required data type. ORA-02264 name already used by an existing constraint Cause: The specified constraint name must be unique. Action: Specify a unique constraint name for the constraint. ORA-02265 Unable to derive data type of referenced column Cause: The data type of the referenced column is not yet defined. User Response : Make sure the data type of the referenced column is defined before referencing it. ORA-02266 unique/primary keys on table referenced by foreign keys enabled Cause: An attempt was made to drop or truncate a table with unique/primary keys referenced by foreign keys enabled on another table. User Response : Before dropping or truncating the table, disable foreign key constraints on other tables. You can see which constraints refer to a table by issuing the following command: select constraint_name, table_name, state from user_constraints where r_constraint_name in ( select constraint_name from user_constraints where table_name ='tabnam');

ORA-02267 Column type does not match reference column type Cause: The data type of the reference column is not compatible with the data type of the reference column. User Response : Select a supported data type for the reference column. Referenced table ORA-02268 has no primary key Cause: The referenced table has no primary key. User Response : Explicitly specify the unique key of the referenced table. ORA-02269 key column cannot be of data type LONG Cause: An attempt was made to define a key column of data type LONG. This is not allowed.

5-18

message error

Action: Change the data type of the column or remove the LONG column from the key and try again. ORA-02270 No matching primary or unique key for this list of columns Cause: An attempt was made to reference a primary or unique key in a table with a CREATE or ALTER TABLE statement when that key does not exist in the referenced table . Action: Add the primary or unique key to the table or find the correct column names with the unique or primary key and try again. Table ORA-02271 does not have this constraint Cause: An attempt was made to reference a table using a constraint that does not exist. Action: Check the spelling of the constraint name or add the constraint to the table and try again. ORA-02272 Constrained column cannot be of data type LONG Cause: A constrained column cannot be defined as data type LONG. This is not allowed. User Response : Change the data type of the column or remove the constraint on the column and try again. ORA-02273 this unique/primary key is referenced by some foreign keys Cause: A unique/primary key referenced by foreign keys cannot be dropped. Action: Remove all references to the key before discarding it. ORA-02274 duplicate referential constraint specifications Cause: A referential constraint was specified more than once. This is not allowed. Action: Remove the duplicate specification. ORA-02275 such a referential constraint already exists in the table Cause: An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and is therefore not allowed. Action: Make sure to specify a constraint only once. ORA-02276 Default value type does not match column type Cause: The type of the evaluated default expression is not compatible with the data type of the column.

ORA-02100 to ORA-04099

5-19

User Response : Change the column type or modify the default expression. ORA-02277 invalid sequence name Cause: The specified sequence name is not a valid identifier name. User Response : Specify a valid identifier name for the string name. ORA-02278 Duplicate or conflicting MAXVALUE/NOMAXVALUE specifications Cause: Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications. Action: Delete one of the conflicting specifications and try again. ORA-02279 Duplicate or conflicting MINVALUE/NOMINVALUE specifications Cause: Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified. Action: Delete one of the conflicting specifications and try again. ORA-02280 Duplicate or conflicting CYCLE/NOCYCLE specifications Cause: Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified. Action: Delete one of the conflicting specifications and try again. ORA-02281 Duplicate or conflicting CACHE/NOCACHE specifications Cause: Duplicate or conflicting CACHE and/or NOCACHE clauses were specified. Action: Delete one of the conflicting specifications and try again. ORA-02282 Duplicate or conflicting ORDER/NOORDER specifications Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified. Action: Delete one of the conflicting specifications and try again. ORA-02283 cannot change starting sequence number Cause: An attempt was made to change a starting sequence number. This is not allowed. Action: Do not try to change a starting sequence number. ORA-02284 Duplicate INCREMENT BY specifications Cause: A duplicate INCREMENT BY clause was specified. Action: Remove the duplicate specification and try again.

5-20

message error

ORA-02285 Duplicate START WITH specifications Cause: A duplicate START WITH clause was specified. Action: Remove the duplicate specification and try again. ORA-02286 no option specified for ALTER SEQUENCE Cause: No ALTER SEQUENCE option specified. Action: Check the syntax. Then specify at least one ALTER SEQUENCE option. The sequence number ORA-02287 is not allowed here. Cause: The specified sequence number reference, CURRVAL or NEXTVAL, is not appropriate at this point in the statement. Action: Check the syntax. Then delete or reassign the sequence number. ORA-02288 Invalid OPEN mode Cause: A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode. Action: Remove the invalid mode from the declaration or replace it with the RESETLOGS keyword and try again. String ORA-02289 does not exist Cause: The specified string does not exist or the user does not have the necessary privilege to perform this operation. Action: Make sure the stream name is correct and that you have the right to perform the desired operation on this stream. ORA-02290 (string.string) check constraint violated Cause: The value or values attempted to be entered into a field or fields violate a defined check constraint. Action: Enter values that satisfy the constraint. ORA-02291 (string.string) integrity constraint violated - primary key not found Cause: A foreign key value does not have a corresponding primary key value. Action: Delete the foreign key or add a corresponding primary key. Integrity constraint ORA-02292 (string.string) violated: child record found Cause: An attempt was made to delete a row referenced by a foreign key.

ORA-02100 to ORA-04099

5-21

Action: You must DELETE or UPDATE the foreign key before changing this line. ORA-02293 cannot validate (string.string) - check constraint violated Cause: An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that did not have compatible values. User Response : Repeat the ALTER TABLE statement, specifying a check constraint on a table containing compatible values. For more information about ALTER TABLE, see the Oracle8i SQL Reference. ORA-02294 cannot activate (string.string): Constraint changed during validation Cause: While one DDL statement was trying to activate this constraint, another DDL changed the same constraint. Action: Try again, this time with just a DDL changing the constraint. ORA-02295 found more than one enable/disable clause for constraint Cause: An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint. Action: Only one ENABLE or DISABLE clause can be specified for a given constraint. ORA-02296 cannot enable (string.string): null values found Cause: An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not meet the constraint. User Response : Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle8i SQL Reference. ORA-02297 cannot disable constraint (string.string): dependencies exist Cause: A table switch disable constraint failed because the table has foreign keys that depend on the constraint. Action: Disable foreign key constraints or use a DISABLE CASCADE command. ORA-02298 cannot validate (string.string) - primary keys not found Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records.

5-22

message error

User Response : Make sure the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle8i SQL Reference. ORA-02299 cannot validate (string.string): duplicate keys found Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values. User Response : Make sure the table does not have duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle8i SQL Reference. ORA-02300 Invalid value for OIDGENERATORS Cause: A number was not specified for the value of OIDGENERATORS. Action: Specify a number for OIDGENERATORS. ORA-02301 the maximum number of OIDGENERATORS is 255 Cause: A number greater than 255 was specified for the value of OIDGENERATORS. Action: Make sure that the number specified for OIDGENERATORS does not exceed 255. ORA-02302 Invalid or missing type name Cause: An invalid or missing type name was entered in a declaration. User Response : Enter a valid type name in the declaration and retry the operation. ORA-02303 cannot drop or replace a type with table or type dependents Cause: An attempt was made to drop or replace a type that has dependents. Action: Drop all types and tables, depending on the type, and retry the operation or use the FORCE option. ORA-02304 invalid object identifier literal Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is: ■

Not a 32 character hexadecimal string

■

An object identifier that already identifies an existing object

■

An object identifier other than the original object identifier already assigned to the type

ORA-02100 to ORA-04099

5-23

User Response: Do not specify the object identifier clause, or specify a 32 hex character object identifier literal that is unique or identical to the originally assigned object identifier. Then repeat the operation. ORA-02305 only EXECUTE privilege is valid for types Cause: An attempt was made to GRANT or REVOKE an invalid (non-EXECUTE) privilege on a type. Action: GRANT or REVOKE EXECUTE privilege only on types. ORA-02306 cannot create a type that already has valid dependents Cause: An attempt was made to create a type that already has valid dependents (these dependents depend on the fact that the type does not exist). Action: Drop the dependents before creating the type, or don't create the type. ORA-02307 cannot be modified with the REPLACE option for an invalid type Cause: An attempt was made to ALTER with the REPLACE option for an invalid type. Action: Use the CREATE OR REPLACE TYPE command to modify the type. ORA-02308 invalid option string for object type column Cause: An attempt was made to specify an invalid option such as PACKED or UNPACKED for the object type column. User Response : Remove the invalid option from the column specification and try again. Atomic NULL Violation ORA-02309 Cause: An attempt was made to access the attributes of a NULL object instance. Action: Make sure the object instance is not NULL before accessing. ORA-02310 The maximum number of columns allowed in the table was exceeded Cause: The object type column attributes exceeded the maximum number of columns allowed in a table. Action: Specify fewer attributes for the object type and retry the operation.

5-24

message error

ORA-02311 unable to alter with COMPILE option a valid type with type or table dependents Cause: An attempt was made to ALTER with the COMPILE option a valid type and with type or table dependents. Action: It is not necessary to perform this operation. ORA-02312 unable to create extension table for VALUE ADT Cause: An attempt was made to create an extension table for VALUE object type. User Response : Specify the object type when creating the extension table. ORA-02313 object type contains a string attribute of non-queryable type Cause: The specified object type contains a nested attribute whose type cannot be queried. User Response : Use an object type with queryable attribute types. ORA-02314 unable to create index on object type column or attribute Cause: An attempt was made to create an index on an object type column. Action: Index can only be created on columns or simple scalar attributes. ORA-02315 Incorrect number of arguments to default constructor Cause: The number of arguments specified for the default constructor does not match the number of attributes for the object type. User Response : Specify the correct number of arguments to the default constructor and retry the operation. ORA-02316 Incorrect number of attributes in object type column Cause: The number of attributes in the object type operand does not match the number of attributes in the object type column to be updated. Action: Make sure that both object type attributes match. ORA-02317 invalid operation for object type operands Cause: An invalid operation was specified on object type operands. Action: Ensure that the correct operation is requested on operands of type object. ORA-02318 Invalid REF function on non-object table Cause: An invalid REF operator was specified for a non-object table. The REF operator can only be specified on an object table.

ORA-02100 to ORA-04099

5-25

User Response: Do not specify a REF operator on a non-object table. ORA-02319 Invalid column argument for REF operator Cause: An invalid REF column argument was specified. The argument of a REF operator can only be the object type column of the object table. Action: Specify a valid REF column argument. ORA-02320 Could not create storage table for nested table column string Cause: An error occurred while creating the storage table for the specified nested table column. Action: See the messages below for more details. If the situation they describe can be fixed, do it; otherwise, contact Oracle Customer Support. ORA-02321 a default constructor of object type was expected Cause: The expected constructor was not found. Action: Specify a default ADT constructor. ORA-02322 Could not access nested table column storage table Cause: An error occurred while executing DML on nested table column storage table. Action: If the situation described in the following messages can be corrected, do so; otherwise, contact Oracle Customer Support. ORA-02323 string inner table failed for column string Cause: An error occurred while executing DML on the nested table column. Action: If the situation described in the following stack error can be corrected, do so; otherwise, contact Oracle Customer Support. ORA-02324 More than one column in SELECT list of subquery Cause: More than one column was selected in the subquery. Action: Specify only one column in the SELECT list of the THE subquery and repeat the operation. ORA-02325 zero rows returned by subquery Cause: The evaluation of the subquery returns no rows while it should return only one row. User Response: Modify the subquery in the THE operator to return exactly one row.

5-26

message error

ORA-02326 Missing THE keyword Cause: The THE operator includes the subquery used to return an inner nested table. Action: Wrap the operator around the subquery; for example, THE(subquery). ORA-02327 cannot create an index on an expression with a string of data type Cause: An attempt was made to create an index on a non-indexable expression. User Response : Change the data type of the column or do not create the index on an expression whose data type is VARRAY, nested table, object, LOB, or REF. ORA-02328 Cannot specify REF column in VALUE ADT Cause: An attempt was made to create a REF column of VALUE ADT. User Response: Remove the REF specifier from the column specification. Column ORA-02329 of data type string cannot be unique or a primary key Cause: An attempt was made to place a UNIQUE or PRIMARY KEY constraint on a column of data type VARRAY, nested table, object, LOB, FILE, or REF. User Response : Change the data type of the column or remove the constraint. Then repeat the operation. ORA-02330 data type specification not allowed Cause: An attempt was made to specify the data type in the column constraint specification of an object table. User Response : Unspecify the data type and retry the operation. ORA-02331 unable to create constraint on column of string data type Cause: An attempt was made to create a constraint on a column that has an unrestricted data type: VARRAY, nested table, object, LOB, FILE, or REF. User Response : Change the data type of the column or remove the constraint. ORA-02332 unable to create an index on the attributes of this column Cause: An attempt was made to create an index on the attributes of an object type column. User Response: Do not specify the index on the attribute. ORA-02333 Cannot create constraints on attributes of this column Cause: An attempt was made to create a constraint on an attribute of a column of type object.

ORA-02100 to ORA-04099

5-27

Action: Remove the constraint or change the object type. ORA-02334 cannot infer column type Cause: A data type was not declared for this column (in CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column. User Response : Declare a data type for the column. ORA-02335 Invalid data type for cluster column Cause: An attempt was made to declare a CLUSTER column of data type object, REF, nested table, VARRAY, LOB, or FILE. User Response: Drop the CLUSTER column or change the data type of the column. Cannot access column attribute ORA-02336 Cause: An attempt was made to extract an attribute from a column of type object. User Response : Change the object type of the column and try again. ORA-02337 is not an object type column Cause: An attempt was made to use dotted notation on a non-ADT column; i.e. "a.b.c" where "a" is not an object type. Action: Change the column type to an object type or do not perform this operation. ORA-02338 Missing or invalid column constraint specification Cause: A column constraint was not specified. User Response : Unspecify the column or specify a column constraint. Then repeat the operation. Invalid column specification ORA-02339 Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a column of type non-object. User Response : Remove the PACKED or UNPACKED keyword in the column specification and retry the operation. ORA-02340 invalid column specification Cause: An attempt was made to specify an UNPACKED column in a compressed table. User Response: Remove the UNPACKED keyword in the column specification.

5-28

message error

ORA-02341 cannot reference a string of non-SQL queryable type Cause: An attempt to reference an object type attribute that is of a non-SQL queryable type. Action: Change the attribute type to a type that can be queried in SQL or reference the attribute through a 3GL. ORA-02342 replacement type has compile errors Cause: Using the ALTER...REPLACE statement on a valid type caused a compile error. User Response: Use the ALTER...REPLACE statement to replace the type with a valid type that does not cause compile errors. ORA-02344 unable to revoke execution on a type with dependent tables Cause: An attempt was made to revoke execution on a type that has dependents. Action: Drop all tables based on type and retry the operation or use the FORCE option. ORA-02345 unable to create column view based on CURSOR operator Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. Action: Remove the CURSOR operator and replace it with the CAST operator. ORA-02347 cannot grant privileges on the columns of an object table Cause: An attempt was made to grant privileges on the columns of an object table. Action: Choose another table. Privileges cannot be granted on the columns of an object table. ORA-02348 Invalid attribute type Cause: Object type columns cannot have LOB or nested table type attributes. User Response: Remove the invalid attribute from the type. ORA-02349 invalid user-defined type: type is incomplete Cause: An attempt was made to use an incomplete type definition as a table or column data type. User Response : Complete the type definition and retry the operation. ORA-02350 cannot insert into attributes of a compressed typed table Cause: A list of columns was specified in an INSERT statement.

ORA-02100 to ORA-04099

5-29

User Response: Remove the specification declaration from the column list. ORA-02351 Record String: rejected: table string, column string error Cause: The indicated record caused an Oracle error on insert. Action: Determine the Oracle error and correct the log. ORA-02352 Direct path connection must be homogeneous Cause: The connection from the user side to the kernel side is heterogeneous. Action: Make the connection between identical hardware and operating systems. ORA-02353 Multibyte character error Cause: Text specified by POSITION or terminated by newlines is invalid. Action: Edit the control file or the data file to correct the alignment of the column. ORA-02354 Field string conversion initialization failed Cause: An error occurred during field string conversion initialization. This is an internal error. Action: Contact customer service. ORA-02355 String conversion error occurred in CONSTANT field Cause: A CONSTANT field caused an Oracle error; all rows will be rejected. Action: Determine the Oracle error and correct the log. ORA-02356 The database is out of space. Upload cannot continue Cause: The upload was interrupted due to running out of space in the database. User Response : Add space to the specified table. ORA-02357 Packed decimal conversion error Cause: The column could not be converted from packed decimal to character. Action: Check the column and make it compatible with packed decimal format. ORA-02358 Decimal zone conversion error Cause: The column could not be converted from packed decimal to character. Action: Check the column and make it compatible with packed decimal format. ORA-02359 The field in the data file exceeded the specified maximum length Cause: The field is too long for the specified column.

5-30

message error

Action: Shorten the field so that its length is less than or equal to the length of the column. ORA-02360 Column not found before end of logical record (use TRAILING NULLCOLS) Cause: A column was started after reaching the end of logical record. User Response : Use the TRAILING NULLCOLS option or provide data for the column. ORA-02361 Initial delimiter character not found Cause: The initial delimiter character of a delimited field was not found. Action: Provide the character before the beginning of the field. ORA-02362 Logical record closed: second delimiter character not present Cause: The second delimiter character of a delimited field was not found. Action: Provide the character after the end of the field. ORA-02363 No terminator found after a DONE and CLOSED field Cause: No terminator found after a finished and closed field. Action: Provide the character after the end of the field. ORA-02364 Record String: dropped: all WHEN clauses failed Cause: The record was not loaded because the WHEN clauses of all tables failed. Action: No action is required. ORA-02365 Index string became Index unusable due to Cause: Index was not loaded. The cause of the error is indicated after the message. Action: Fix the cause of the error and reload. ORA-02366 The following indexes on the table chain were processed: Cause: The listed indexes for the named table were loaded. Action: No action is required. ORA-02367 Index string was loaded. Explanation: The index specified in the message was loaded. Action: No action is required.

ORA-02100 to ORA-04099

5-31

ORA-02368 Record string: dropped: all columns are null. Explanation: The record was not loaded because all the columns in the table were null for this record. Action: No action is required. ORA-02369 Warning: variable length field has been truncated. Explanation: A variable length field was truncated at the end of the logical record. Action: This is just a warning, but since a variable length field has the length embedded in the data for each line, you may want to check your data. ORA-02370 Record string: warning on table string, column string Cause: The indicated record generated a warning. Action: Determine the warning and correct the registry if necessary. ORA-02371 Loader must have at least version string.string.string.string.string for direct path. Cause: The loader being used is not compatible with this kernel version. Action: Update your loader to at least the specified version or use the conventional path. ORA-02372 Relative start position > absolute end position of the field. Explanation: A field specified as POSITION(*+n:y) had its relative start after the absolute position y. Action: Checks that there is no missing delimiter and that the values of n and y are correct. ORA-02373 Error parsing insert statement for table string. Cause: A parse error occurred. Action: Check the message after this parse error message. ORA-02374 There are no more read buffer queue slots. Cause: There are no free read buffers. Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers. ORA-02375 Record String: Rejected - Table String Error Cause: The indicated record caused an Oracle error on the insert.

5-32

message error

Action: Determine the Oracle error and correct the log. The offending column(s) is(are) unknown. ORA-02376 Invalid or redundant resource Cause: An undefined or specified resource appears twice in the CREATE or ALTER PROFILE statement. User Response : Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the declaration to see if each function only appears once. ORA-02377 Invalid resource limit Cause: An invalid resource limit of 0 was specified. Action: Specify a resource limit greater than 0. ORA-02378 Duplicate resource name string Cause: The same resource was specified twice in a CREATE or ALTER PROFILE statement. Action: Reissue the statement, carefully checking that each resource is used only once. Profile string ORA-02379 already exists Cause: An attempt was made to create a profile that already exists. Action: Create the profile with a name that has not been used by another profile. ORA-02380 profile string does not exist Cause: An attempt was made to assign a user to a non-existent profile. Action: Assign the user to an existing profile. ORA-02381 unable to delete profile PUBLIC_DEFAULT Cause: An attempt was made to delete profile PUBLIC_DEFAULT. Action: The PUBLIC_DEFAULT profile cannot be dropped. Profile string ORA-02382 has assigned users, cannot be dropped without CASCADE Cause: An attempt was made to drop a profile that had assigned users without using the CASCADE option of the DROP PROFILE statement. A profile that has assigned users cannot be dropped unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile. Action: To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option.

ORA-02100 to ORA-04099

5-33

ORA-02383 illegal cost factor Cause: A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement. User Response: Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Reissue the statement, using a positive integer value for each specified feature. ORA-02390 exceeded COMPOSITE_LIMIT, being disconnected Cause: The COMPOSITE_LIMIT for the profile was exceeded. That is, the weighted sum of connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit defined by the COMPOSITE_LIMIT clause defined in the user profile. Action: If this happens frequently, ask the database administrator to increase the COMPOSITE_LIMIT of the user profile or determine which role is used the most and increase the limit for that role. ORA-02391 concurrent session limit exceeded for SESSIONS_PER_USER Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile. Action: End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile. For more information about SESSIONS_PER_USER and specific database administrator tasks for tuning concurrent sessions, see the Oracle8i SQL Reference and Oracle8i Administrator's Guide ORA-02392 CPU Usage Exceeded Session Limit , you are being disconnected Cause: An attempt was made to exceed the Maximum CPU Usage allowed by the CPU_PER_SESSION clause of the user profile. Action: If this happens frequently, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile. ORA-02393 Call limit on CPU usage exceeded Cause: An attempt was made to exceed the maximum CPU time for a call, parse, execute, or retrieve allowed by the CPU_PER_CALL clause of the user profile. Action: If this happens frequently, ask the database administrator to increase the CPU_PER_CALL limit of the user profile.

5-34

message error

ORA-02394 Exceeded session limit on I/O usage, being disconnected Cause: An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile. Action: If this happens frequently, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile. ORA-02395 I/O usage call limit exceeded Cause: An attempt was made to exceed the maximum I/O for a call, parse, execute, or retrieve allowed by the LOGICAL_READS_PER_CALL clause of the user profile. Action: If this happens frequently, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit for the user profile. ORA-02396 Maximum idle time exceeded, please connect again Cause: A user has exceeded the maximum time allowed to remain idle. Action: The user must reconnect to the database. ORA-02397 PRIVATE_SGA limit exceeded, being disconnected Cause: This error only occurs when using a multithreaded server. Action: Contact your database administrator to extend the PRIVATE_SGA limit. ORA-02398 Procedure space usage exceeded Cause: Stored procedures took up too much space in the SYSTEM table space. User Response: Use fewer stored procedures or add an additional file to the system tablespace. ORA-02399 Maximum connection time exceeded, you are being disconnected Cause: A user has exceeded the maximum time allowed to connect to the database. Action: The user must reconnect to the database. ORA-02401 cannot EXPLAIN view owned by another user Cause: The view specified in the SQL statement belongs to another user and cannot be explained. Action: Create a view with the same definition that belongs to the current user. ORA-02402 PLAN_TABLE not found Cause: The table used by EXPLAIN to store row source information does not exist in the current schema.

ORA-02100 to ORA-04099

5-35

Action: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command into an existing plan table. The ORA-02403 plan table is not in the correct format. Cause: The explicit plan table does not have the proper field definitions. Action: Reset the schedule table to have the proper field definitions. ORA-02404 The table for the specified plan was not found Cause: The table for the specified plan could not be found. Action: Create the specified plan table or use an existing plan table. ORA-02420 Missing schema authorization clause Cause: The AUTHORIZATION clause is missing from a create schema statement. User Response: Continue with the schema authorization identifier with the AUTHORIZATION keyword. Missing or invalid schema authorization identifier ORA-02421 Cause: One of the following: ■

■

The schema authorization identifier is not recognized. An attempt was made to use a schema authorization identifier for a user while not logged in as that user.

Action: If the cause is ■

■

an unrecognized identifier and use an existing identifier. logged in with a different username, then log out and log in with the correct username.

ORA-02422 Missing or invalid schema element Cause: A statement other than CREATE TABLE, CREATE VIEW, or GRANT appears in a CREATE SCHEMA statement. Action: Check the Oracle8i SQL reference or the valid elements of the CREATE SCHEMA statement. ORA-02423 schema name does not match schema authorization identifier Cause: A table definition with a schema name attached to the table name does not match the schema name provided in the AUTHORIZATION clause of the CREATE SCHEMA STATEMENT.

5-36

message error

Action: Check that the schema names match those provided in the CREATE SCHEMA statement. ORA-02424 possible unknown circular view or referenced table references Cause: The CREATE SCHEMA statement contains a view that depends on other views contained in the CREATE SCHEMA statement or contains references to non-existent tables. Action: Create the dependent views in a separate CREATE SCHEMA statement and ensure that all referenced tables are defined in the CREATE SCHEMA statement or exist outside of the statement. ORA-02425 table creation failed Cause: The CREATE TABLE statement in the CREATE SCHEMA statement failed. Action: The cause of the failure will be displayed below this message. Follow the appropriate actions suggested by the subsequent messages. Privilege grant failed ORA-02426 Cause: A GRANT statement failed in the CREATE SCHEMA statement. Action: The cause of the failure will be displayed below this message. Follow the appropriate actions suggested by the subsequent messages. ORA-02427 view create error Cause: A CREATE VIEW statement failed on the CREATE SCHEMA statement. Action: The cause of the failure will be displayed below this message. Follow the appropriate actions suggested by the subsequent messages. ORA-02428 unable to add a foreign key reference Cause: Oracle was unable to add a foreign key reference due to an assertion error. The referenced table does not exist or the table does not have a unique key. Action: Verify that the referenced table exists and/or has a unique key. ORA-02429 Unable to drop index used for primary/unique key application. Cause: An attempt was made to drop an index that is used as an enforcement mechanism for a primary or unique key. User Response : Drop the integrity constraint instead of dropping the index.

ORA-02100 to ORA-04099

5-37

ORA-02430 cannot activate constraint (string) - this constraint does not exist Cause: The named constraint does not exist for this table. Action: Check if a restriction exists before trying to enable it. ORA-02431 cannot disable constraint (string): This constraint does not exist Cause: The named constraint does not exist for this table. Action: Check if a restriction exists before attempting to disable it. ORA-02432 unable to enable primary key: primary key is not defined for table Cause: An attempt was made to enable a primary key that is not defined for the table. User Response : Add a primary key definition for the table. ORA-02433 unable to disable primary key: primary key is not defined for table Cause: An attempt was made to disable a primary key that is not defined for the table. Action: Verify that a primary key exists before attempting to deactivate it. ORA-02434 cannot activate unique (string): unique key not defined for table Cause: An attempt was made to activate a unique key that is not defined for the table. Action: Verify that a unique key exists before attempting to enable it. ORA-02435 cannot disable unique (string): unique key not defined for table Cause: An attempt was made to disable a unique key that is not defined for the table. Action: Verify that a unique key exists before attempting to disable it. ORA-02436 Incorrectly specified date or system variable in CHECK constraint Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not fully specified in a CREATE TABLE or ALTER TABLE statement . For example, a date was specified without the century. Action: Fully specify the date constant or system variable. ORA-02437 unable to validate (string.string) - primary key violated Cause: An attempt was made to validate a primary key with duplicate values or null values.

5-38

message error

Action: Remove duplicates and null values before enabling a primary key. ORA-02438 Column check constraint cannot reference other columns Cause: An attempt was made to define a column check constraint that references another column. Action: Set it as a table scan constraint. ORA-02439 Unique index not allowed on a deferrable constraint Cause: An attempt was made to activate a deferrable primary key/unique constraint that has an existing unique index on the constraint columns. Action: Drop the index on the constraint columns or make the constraint non-deferrable. ORA-02440 Create as selection with referential constraints not allowed Cause: Unable to create integrity constraints on a table when the table is created using the CREATE TABLE... AS SELECT.... form Action: First, create the table and then modify the table to add the desired integrity constraints. ORA-02441 Cannot drop non-existent primary key Cause: An attempt was made to drop the primary key constraint on a table, but there is no primary key constraint on this table. User Response : Be sure to enter the correct table name in the declaration. Otherwise, no action is required. ORA-02442 Cannot drop a unique key that does not exist Cause: An attempt was made to drop a unique key constraint for a column that does not have a unique key constraint. Action: Make sure you enter the correct column name. Otherwise, no action is required. ORA-02443 Cannot remove constraint: non-existent constraint Cause: An attempt was made to remove a constraint that does not exist. User Response : Make sure the table name and constraint are correct and try the procedure again. ORA-02444 Cannot resolve object referenced in referential constraints Cause: An attempt was made to define a foreign key with a reference to a schema object that cannot be resolved to a base table reference.

ORA-02100 to ORA-04099

5-39

User Response: Define referential constraints only with schema objects resolved to a base table. ORA-02445 Exception table not found Cause: The explicitly or implicitly declared exception table does not exist. User Response : If the correct exception table name was used, create the table and try the enable command again. ORA-02446 CREATE TABLE ... AS SELECT failed: check constraint violated Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints. Action: Do not select rows that violate the constraints. ORA-02447 cannot defer a constraint that cannot be deferred Cause: An attempt was made to defer a constraint that cannot be deferred. Action: Remove the constraint and create a new one that is deferrable. ORA-02448 constraint does not exist Cause: The named constraint does not exist. Action: Choose an existing constraint or do not perform this operation. ORA-02449 unique/primary keys in table referenced by foreign keys Cause: An attempt was made to drop a table with unique/primary keys referenced by foreign keys in another table. Action: Before performing the above operations on the table, drop the foreign key constraints on other tables. You can see which constraints refer to a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";

ORA-02450 Invalid Hash Option: Missing IS keyword Cause: Missing IS keyword. Action: Specify the HASH IS option. ORA-02451 duplicate HASHKEYS specification Cause: The HASHKEYS option was specified more than once. Action: Specify the HASHKEYS option only once.

5-40

message error

ORA-02452 Invalid HASHKEYS option value Cause: The HASHKEYS option specified must be an integer value. Action: Specify an appropriate value. ORA-02453 Duplicate HASH IS specification Cause: The HASH IS option was specified more than once. Action: Specify the HASH IS option only once. ORA-02454 The number of hash keys per block (string) exceeds the maximum string Cause: The SIZE argument is too small. Action: Increase the SIZE argument. ORA-02455 Cluster key column number must be 1 Cause: When specifying the HASH IS option, the number of key columns must be 1. Action: Do not specify the HASH IS option or reduce the number of key columns. ORA-02456 HASH IS column specification must be NUMBER(*,0) Explanation: The column specification must specify an integer. User Response : Specify the column definition as type NUMBER (precision, 0). ORA-02457 The HASH IS option must specify a valid column. Cause: The HASH IS column name is not specified in the cluster definition. Action: Specify a valid column name. ORA-02458 HASHKEYS must be specified for a HASH CLUSTER Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER. Action: Specify the HASHKEYS option. ORA-02459 The hash key value must be a positive integer Cause: The hash key value was not a positive number. Action: Specify a positive integer. ORA-02460 Bad index operation on a hash cluster Cause: An attempt to create a cluster index on a hash cluster was issued. Action: Do not try to create this index.

ORA-02100 to ORA-04099

5-41

ORA-02461 Misuse of the INDEX option Cause: This option is only valid for hashless clusters. Action: Do not specify this option. ORA-02462 Duplicate INDEX option specified Cause: The INDEX option was specified more than once. Action: Specify the INDEX option only once. ORA-02463 Duplicate HASH IS option specified Cause: The HASH IS option was specified more than once. Action: Specify the HASH IS option only once. ORA-02464 Cluster definition cannot be both HASH and INDEX Cause: The cluster can be either an indexed cluster or a hash, but not both. Action: Remove the HASH IS or INDEX options. ORA-02465 Misuse of the HASH IS option Cause: This option is only valid for clusters. Action: Do not specify this option. ORA-02466 SIZE option cannot be changed for HASH CLUSTERS Cause: The SIZE cannot be changed after the hash cluster is created. Action: Do not specify this option. ORA-02467 Column referenced in expression not found in cluster definition Cause: A column in the hash is expression was not present in the cluster definition. User Response: Re-create the cluster and correct the hash expression error. ORA-02468 System variable or constant specified incorrectly in expression Cause: A system variable or constant was specified in the hash expression. User Response: Re-create the cluster and correct the hash expression error. ORA-02469 The hash expression does not return an Oracle number. Cause: The result of evaluating the hash expression is not an Oracle number. User Response: Re-create the cluster and correct the hash expression error.

5-42

message error

ORA-02470 TO_DATE, USERENV, or SYSDATE used incorrectly in hash expression. Cause: TO_DATE, USERENV, and SYSDATE are not allowed in hash expressions. User Response: Re-create the cluster and correct the hash expression error. ORA-02471 SYSDATE, UID, USER, ROWNUM, or LEVEL used incorrectly in hash expression. Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions. Action: Rebuild the cluster and remove the offending keywords. ORA-02472 PL/SQL functions not allowed in hash expressions Cause: A PL/SQL function was used in the hash expression. Action: Re-create the cluster and remove the PL/SQL role. ORA-02473 Error evaluating cluster hash expression. Explanation: An error occurred while evaluating the hash expression of the clusters. Action: Correct the query and try again. ORA-02474 Used fixed hash area extents (string) exceeds maximum allowed (string) Cause: The number of extents required to create the fixed hash area exceeds the maximum number allowed. Action: Reduce the number of required extents by increasing the extent allocation sizes in the STORAGE clause. ORA-02475 The maximum number of blocks in the cluster chain has been exceeded. Cause: The number of blocks in a cluster chain exceeds the maximum number allowed. Action: Increase the SIZE parameter in the CREATE CLUSTER statement or reconsider the appropriateness of the cluster key. ORA-02476 Unable to create index due to parallel direct load on table Cause: A parallel direct load is occurring on the specified table. Action: Repeat the instruction after the upload is complete.

ORA-02100 to ORA-04099

5-43

ORA-02477 cannot perform parallel direct load on object string Cause: Parallel direct load is not possible because an index is being created on the table. Action: Try uploading again after the index creation is complete. ORA-02478 merge into base segment would exceed MAXEXTENTS threshold Cause: Merge from time segment into base segment failed because MAXEXTENTS was greater than total across both time and base segments. Action: Use a larger value for MAXEXTENTS in the base segment, or increase the extents in temporary segments. ORA-02479 error translating filename for parallel upload Cause: An invalid filename was specified to upload data. User Response : Specify a valid database file. ORA-02480 Too many event classes were specified for events. Cause: Invalid trace enable string. User Response : Enter a legal trace enable control string. ORA-02481 Too many ID ranges were specified for events. Cause: Illegal trace enable string. User Response : Enter a legal trace enable control string. ORA-02482 An event class was specified, but no event was provided. Cause: Illegal trace enable string. User Response : Enter a legal trace enable control string. ORA-02483 An invalid ID value was specified for events. Cause: Invalid trace enable string. User Response : Enter a legal trace enable control string. ORA-02485 Low ID value is greater than High ID value Cause: Incorrect file name supplied in TRACE_DEST initialization parameter. Action: Specify a valid name in the TRACE_DEST initialization parameter. ORA-02486 File string error. Check trace_dest INIT.ORA parm Cause: Incorrect filename supplied in the TRACE_DEST initialization parameter. Action: Specify a valid name in the TRACE_DEST initialization parameter.

5-44

message error

ORA-02487 Error writing file name string. Check trace_dest INIT.ORA parm Cause: Incorrect filename supplied in the TRACE_DEST initialization parameter. Action: Specify a valid name in the TRACE_DEST initialization parameter. ORA-02489 trace_block_size(string) must be divisible by string Cause: The initialization parameter TRACE_BLOCK_SIZE was set incorrectly. Action: Change the startup parameter and reboot. ORA-02490 Missing required file size in RESIZE clause Cause: No value was specified for the RESIZE clause. User Response: Use the correct syntax. ORA-02491 Missing required ON or OFF keyword in AUTOEXTEND clause Cause: The ON or OFF keyword was not specified for the AUTOEXTEND clause. User Response: Use the correct syntax. ORA-02492 missing required file block increment size in NEXT clause Cause: No value was specified for the NEXT clause. User Response: Use the correct syntax. ORA-02493 Invalid file increment size in NEXT clause Cause: A non-integer value was used for the NEXT clause of the DATAFILE list. User Response: Use the correct syntax. ORA-02494 Invalid or missing maximum file size in MAXSIZE clause Cause: UNLIMITED was not specified or an invalid integer value was specified for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be less than the SIZE value. User Response: Use the correct syntax. ORA-02495 unable to resize file string, tablespace string is read-only Cause: An attempt was made to resize a data file in a tablespace that is read-only. User Response : Change the tablespace to read/write and retry the resize operation.

ORA-02100 to ORA-04099

5-45

ORA-02700 osnoraenv: ORACLE_SID translation failed Cause: The dual task driver could not find the ORACLE_SID value in the environment. Action: Make sure the ORACLE_SID environment variable is set and exported correctly. ORA-02701 osnoraenv: error translating Oracle image name Cause: The ORACLE_HOME environment variable is not set. Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. ORA-02702 osnoraenv: error translating orapop image name Cause: The ORACLE_HOME environment variable is not set. Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. ORA-02703 osnpopipe: channel creation failed Cause: The channel driver was unable to create channels for communications with the ORAPOP process. Action: You have probably exceeded the maximum number of open file descriptors per user, or the system file table is full. Make a note of the operating system error code and contact your system administrator. ORA-02704 osndopop: branch failed Cause: The dual task driver was unable to branch ORAPOP. Action: Check if there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02705 osnpol: polling communication channel failed Cause: The pipeline driver failed to poll the communication channel. Action: Contact Oracle Customer Support. ORA-02706 osnshs: hostname too long Cause: The length of the host string specified by the TWO_TASK environment variable exceeds the limit imposed by the Oracle system. Action: Contact Oracle Customer Support.

5-46

message error

ORA-02707 osnacx: could not allocate context area Cause: The UNIX two-task driver called could not allocate heap space for the context area. Action: Contact Oracle Customer Support. ORA-02708 osnrntab: connection to host failed, unknown ORACLE_SID Cause: The invoked UNIX two-task driver could not find an entry in ORATAB for the given SID. Action: First, verify that you have read access to ORATAB and see that the desired sid is there. Add an entry to ORATAB for the desired SID, if necessary. ORA-02709 osnpop: channel creation failed Cause: The channel driver was unable to create channels for two-task communications with the parallel Oracle process. Action: You have probably exceeded the maximum number of open file descriptors per user, or the system file table is full. Make a note of the operating system error code and contact your system administrator. ORA-02710 osnpop: branch failed Cause: The pipeline driver was unable to branch the Oracle shadow process. Action: Check if there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02711 osnpvalid: error writing to validation channel Cause: The pipeline driver was unable to write to the ORAPOP process. Action: Contact Oracle Customer Support. ORA-02712 osnpop: malloc failed Cause: The channel driver was unable to allocate enough heap space for its context area buffers. Action: Contact Oracle Customer Support. ORA-02713 osnprd: could not receive message Cause: The pipe driver was unable to read a message from the communication channel. Action: Contact Oracle Customer Support.

ORA-02100 to ORA-04099

5-47

ORA-02714 osnpwr: error sending message Cause: The pipeline driver was unable to write a message to the communication channel. Action: Contact Oracle Customer Support. ORA-02715 osnpgetbrkmsg: message from host had wrong message type Cause: The pipeline controller received a message with an unrecognizable message type. Action: Contact Oracle Customer Support. ORA-02716 osnpgetdatmsg: message from host had wrong message type Cause: The Pipe controller received a message with an unrecognizable message type. Action: Contact Oracle Customer Support. ORA-02717 osnpfs: incorrect number of bytes written Cause: The Pipe driver sent an apparently successful message, but the number of bytes transmitted did not match the number of bytes allocated to the driver. Action: Contact Oracle Customer Support. ORA-02718 osnprs: reset protocol error Cause: The two-task handler was unable to reset the connection. Action: Contact Oracle Customer Support. ORA-02719 osnfop: fork failed Cause: The fast driver was unable to fork the Oracle shadow process. Action: Check if there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02720 osnfop: shmat failed Cause: When the fast driver was called, processes were unable to connect to the shared memory buffer. You probably provided an illegal shared memory add address, or the system ran out of data space to accommodate the buffer. Action: Try calling the fast handler later or use the default attached address. ORA-02721 osnseminit: unable to create semaphore set Cause: The fast driver was unable to obtain a semaphore set.

5-48

message error

Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and consult your system administrator. ORA-02722 osnpui: failed to send interrupt message to orapop Cause: The pipeline driver was unable to send the interrupt message to ORAPOP. Action: Contact Oracle Customer Support. ORA-02723 osnpui: failed to send interrupt signal Cause: The Pipe driver was unable to send an interrupt message to the Oracle shadow process. Action: Contact Oracle Customer Support. ORA-02724 osnpbr: Could not send interrupt message to orapop Cause: The Pipe driver could not send an interrupt message to ORAPOP. Action: Contact Oracle Customer Support. ORA-02725 osnpbr: Could not send interrupt signal Cause: The Pipe driver was unable to send an interrupt message to the Oracle shadow process. Action: The Kill system call fails. Check the error code (errno) and contact Oracle Customer Support. ORA-02726 osnpop: access error in Oracle executable Cause: The Pipe driver could not access the Oracle executable. Action: Check the permissions on the Oracle executable and each component in the ORACLE_HOME/bin path. ORA-02727 osnpop: access error in orapop executable Cause: The Pipe driver could not access the ORAPOP executable. Action: Check the permissions on the ORAPOP executable and each component in the ORACLE_HOME/bin path. ORA-02728 osnfop: access error in oracle executable Cause: The fast driver could not access the oracle executable. Action: Check the permissions on the Oracle executable and each component in the ORACLE_HOME/bin path.

ORA-02100 to ORA-04099

5-49

ORA-02729 osncon: driver not in osntab Cause: The specified driver is not supported. Action: Check with your database administrator which drivers are supported. ORA-02730 osnrnf: could not find user login directory Cause: The specified driver could not find the login directory when looking for the local .SQLNET file. Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure your UID and home directory are correct in the /etc/passwd file. ORA-02731 osnrnf: buffer malloc error Cause: The specified driver could not find enough heap space for MALLOC in a buffer. Action: Contact Oracle Customer Support. ORA-02732 osnrnf: Could not find matching database alias Cause: The specified database alias was not identified in $HOME/.sqlnet or /etc/sqlnet. Action: Create the alias in a file called .sqlnet in your home directory for personal use, or have your system administrator create the alias in /etc/sqlnet for system-wide use. ORA-02733 osnsnf: database string too long Cause: When converting a database alias to a database ID, the resulting database ID string exceeded the limit imposed by the Oracle system. Action: Contact Oracle Customer Support. ORA-02734 osnftt: Could not reset shared memory permission Cause: The fast driver could not reset shared memory permissions. Action: Contact Oracle Customer Support. ORA-02735 osnfpm: unable to create shared memory segment Cause: The fast driver was unable to create a shared memory segment for two-task communication. Action: Check if the system-imposed limit on shared memory identifiers has already been reached for your system.

5-50

message error

ORA-02736 osnfpm: illegal default shared memory address Cause: The fast driver was unable to set a default shared memory address. Action: Contact Oracle Customer Support. ORA-02737 osnpcl: cannot tell orapop to quit Cause: The Pipe driver could not send ORAPOP the command to quit. Action: Contact Oracle Customer Support. ORA-02738 osnpwrtbrkmsg: incorrect number of bytes written Cause: The pipeline driver apparently sent an incomplete interrupt message. Action: Contact Oracle Customer Support. ORA-02739 osncon: host alias too long Cause: The alias used for a SQLNET host is longer than 161 characters. Action: Use a shorter alias. ORA-02750 osnfsmmap: cannot open shared memory file?/dbs/ftt_pid.dbf Cause: The fast driver could not create a shared memory file for two task communication. Action: Check the permissions on the ?/dbs directory. ORA-02751 osnfsmmap: unable to allocate shared memory file Cause: The fast driver was unable to allocate a shared memory file for two-task communication. Action: Contact Oracle Customer Support. ORA-02752 osnfsmmap: invalid shared memory address Cause: The fast driver was unable to attach shared memory at the expected location. Action: Contact Oracle Customer Support. ORA-02753 osnfsmmap: cannot close shared memory file Cause: The fast driver cannot close the shared memory file. Action: Contact Oracle Customer Support. ORA-02754 osnfsmmap: unable to change shared memory inheritance Cause: The fast driver was unable to change the shared memory inheritance attributes. Action: Contact Oracle Customer Support.

ORA-02100 to ORA-04099

5-51

ORA-02755 osnfsmcre: unable to create file for shared memory?/dbs/ftt_pid.dbf Cause: The fast driver could not create a file for shared memory. Action: Check the permissions on the ?/dbs directory. ORA-02756 osnfsmnam: name translation failed Cause: The fast driver encountered an error translating the name of the shared memory file ?/dbs/ftt_pid.dbf. Action: Contact Oracle Customer Support. ORA-02757 osnfop: fork_and_bind failed Cause: The fast driver was unable to fork a process on the desired cluster and node number. Action: Check the desired node number in sercose[0] and the cluster ID in sercose[1]. If they appear valid, contact Oracle Customer Support. ORA-02758 Internal array allocation failed Cause: The package could not allocate memory for an array because the system ran out of memory. Action: Reclaim memory by killing other processes or reboot the machine with more memory. ORA-02759 Not enough request descriptors available Cause: All request descriptors in the package are in use by executing other requests. Action: Wait until enough requests are made, or close the package and restart it with more request descriptors. ORA-02760 The file could not be closed by the client. Cause: The client was unable to close a file after forking the servers. Action: This is a system problem; contact your system administrator. ORA-02761 The file number to be dropped is negative. Explanation: The file number contained in the SFIOV structure is less than zero. Action: This could be a programming error. Otherwise, contact Oracle Customer Support. ORA-02762 the file number to be canceled is greater than the maximum. Cause: The file number contained in the SFIOV structure is greater than the maximum.

5-52

message error

Action: This could be a programming error. Otherwise, contact Oracle Customer Support. ORA-02763 Could not cancel at least one request Cause: No cancelable requests found. Action: This error can occur if all requests to this file number have already been fulfilled. ORA-02764 Invalid packet mode Cause: The packet mode can only be parallel or duplex. Action: See SFA.H for the correct values. ORA-02765 Invalid maximum number of servers Cause: The number of servers provided was less than or equal to zero. Action: Use a number greater than zero. ORA-02766 Invalid maximum number of request descriptors Cause: The number of request descriptors was less than or equal to zero. Action: Use a number greater than zero. ORA-02767 Less than one request descriptor allocated per server Cause: The package requires the number of request descriptors to be greater than or equal to the number of servers used. Action: Use a larger number ORA-02768 The maximum number of files is invalid Cause: The maximum number of files to be used by the package was less than or equal to zero. Action: Use a positive number. ORA-02769 Failed to configure handler for SIGTERM Cause: Package failed to configure server handling for shutdown signal. This is an internal error. Action: Contact Oracle Customer Support. ORA-02770 Invalid total number of blocks Cause: The total number of blocks to allocate for use by the package was not greater than zero.

ORA-02100 to ORA-04099

5-53

Action: Use a positive number. ORA-02771 Invalid request timeout value Cause: The number was not a positive number. Action: Use a positive number. ORA-02772 Invalid Maximum Server Idle Time Cause: The time entered was not a positive number. Action: Use a positive number. ORA-02773 Invalid Client Max Timeout Cause: The time entered was not a positive number. Action: Use a positive number. ORA-02774 Invalid request list lock timeout value Cause: The time provided was not a positive number. Action: Use a positive number. ORA-02775 Invalid request completed token Cause: The token number was not a positive number. Action: Use a positive number. ORA-02776 Request complete signal value exceeds maximum Cause: The value sent to the package for use as a "request complete" signal exceeds the maximum allowed by the operating system. Action: Contact your system administrator. ORA-02777 Log directory statistics error Cause: The package was unable to get information about the directory where the log files should reside. Action: Check the permissions on the directory or use a different directory name. ORA-02778 The name provided for the logs directory is invalid. Cause: The name provided for the directory where the logs will be saved does not correspond to a directory. Action: Use a different name.

5-54

message error

ORA-02779 Statistics error in core dump directory Cause: The package could not get information about the directory where servers should dump core in case of an exception. Action: Check the permissions on the directory or use a different directory name. ORA-02780 Invalid name provided for core dump directory Cause: The name given for the directory where server processes should dump core on exception does not match a directory. Action: Use a different name. ORA-02781 An invalid value was supplied for the desired time flag. Cause: The supplied value was neither TRUE nor FALSE. Action: Specify TRUE or FALSE for the desired time flag. ORA-02782 Unspecified read and write functions Cause: To ensure that the functions act symmetrically, pointers to the read and write functions must be provided. Action: Specify both roles or specify neither. The package will provide its own functions. ORA-02783 The publish and wait functions were not specified. Cause: To ensure that the functions act symmetrically, pointers to the publish and wait functions must be provided. Action: Specify both roles or specify neither. The package will provide its own functions. ORA-02784 An invalid shared memory ID was specified. Cause: The segment ID specified to use as the shared buffer region was invalid. Action: Use a different ID or let the package specify its own. ORA-02785 Invalid shared memory buffer size Cause: The size provided for the shared memory segment to be used as the shared buffer region was less than or equal to zero. Action: Use a positive number.

ORA-02100 to ORA-04099

5-55

ORA-02786 Required shared region size is greater than segment size Cause: The shared segment size specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the required size. The second is the size of the segment. Action: Use a larger slice or let the package allocate its own. ORA-02787 Cannot allocate memory for thread list Cause: The package cannot allocate memory for an internal thread list because the system ran out of memory. The "additional information" field is the amount of memory the package tried to allocate. Action: Close some processes or contact your system administrator. ORA-02788 Cannot find kernel process pointer in asynchronous process array Cause: This is an internal error. Action: Contact Oracle Support. ORA-02789 Maximum number of files reached Cause: The maximum number of files that can be used for asynchronous I/O has been reached. Action: Shut down the servers and restart the package with a higher number. ORA-02790 File name is too long Cause: The name length of a file that is opened for asynchronous I/O is greater than the maximum. The "additional information" field is the maximum length. Action: Use a shorter name. ORA-02791 Cannot open file for use with asynchronous I/O Cause: The package could not open the file for some reason. Action: Check the file name. ORA-02792 Cannot use fstat() on a file that is used for asynchronous I/O. Cause: The fstat(2) call failed on a file that is used for asynchronous I/O. Action: Check the file name. ORA-02793 Async I/O close failed. Explanation: The client was unable to close a file that is used for asynchronous I/O.

5-56

message error

Action: Contact Oracle Customer Support. ORA-02794 Client could not get key for shared memory Cause: The client could not get a key to get shared memory for use with shared memory. This is an internal error. Action: Contact Oracle Customer Support. ORA-02795 Request list is empty Cause: A server told the client that a request was completed, but the "completed" list was empty. This is an internal error. Action: Contact Oracle Customer Support. ORA-02796 Completed request is not in the correct state Cause: A request is not in the correct state. This is an internal error. Action: Contact Oracle Customer Support. ORA-02797 No requests available Cause: No free request descriptors available. Action: Wait for a few requests to be served and retry the request, or shut down the servers and initialize the package with a larger number of requests. ORA-02798 Invalid number of requests Cause: The number of operations sent to SFARD() or SFAWRITE() is less than zero. This is a user programming error. Action: Check the calling program. ORA-02799 Cannot set signal handler Cause: Failed to set a signal handler for the "done" signal. This is an internal error. Action: Contact Oracle Customer Support. ORA-02800 Requests timed out Cause: Some of the asynchronous input or output requests were not serviced in the required time. Action: If the load on the system is high, the timeout threshold might be too low. Reset with SFAINIT(). If server processes are dying due to unexpected signals, it is an internal error and Oracle Customer Support should be contacted.

ORA-02100 to ORA-04099

5-57

ORA-02801 Operations timed out Cause: Some asynchronous operations timed out in kernel mode. This is an internal error. Action: Contact Oracle Customer Support. ORA-02802 No idle server available in parallel mode Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02803 Failed to retrieve current time Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02804 Failed to allocate memory for log file name Cause: The client was unable to allocate a buffer for the log file name. Action: Contact your system administrator. ORA-02805 Cannot set handler for SIGTPA Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02806 Cannot set driver for SIGALRM Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02807 Memory allocation for I/O arrays failed. Explanation: The client was unable to allocate memory for the array of I/O arrays to be used by the servers. Action: Contact your system administrator. ORA-02808 Open files array memory allocation failed. Explanation: The client was unable to allocate memory for an array of flags that should be used by the servers. Action: Contact your system administrator. ORA-02809 Invalid jump buffer Cause: This is an internal error. Action: Contact Oracle Customer Support.

5-58

message error

ORA-02810 Cannot create temporary file name for memory mapped file Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02811 Cannot attach shared memory segment Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02812 Incorrect attached address Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02813 Cannot create a temporary filename to get the key Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02814 Cannot get shared memory Cause: SHMGET(2) failed. Action: Check the UNIX number. If you are not sure what this means, contact Oracle Customer Support. ORA-02815 Cannot connect shared memory Cause: SHMAT(2) failed. Action: Check the UNIX number. If you are not sure what this means, contact Oracle Customer Support. ORA-02816 Failed to shut down a process Cause: A server failed to shut down after receiving a shutdown signal. Action: The process may be out of control; contact Oracle Customer Support. ORA-02817 Read Error Cause: A server was unable to read the requested amount of data. Action: Check the call to SFARD(). An incorrect file descriptor may have been sent to SFARD(). The number in the "additional information" field is the starting block number of the data segment being read.

ORA-02100 to ORA-04099

5-59

ORA-02818 Read fewer blocks than requested Cause: A server was unable to read the requested amount of data. The first number in the "additional information" field is the number of the block being read. The second is the actual number of bytes that were read. This is a programming error. Action: Check the calling program. ORA-02819 Write Error Cause: A server failed to perform a write. The number in the "additional information" field is the starting block number of the data segment being written. The first number in the "additional information" field is the number of the block being written. The second is the actual number of bytes that were written. The disk may be full. Action: Check the UNIX error number. ORA-02820 Unable to write requested number of blocks Cause: A server was unable to write the requested amount of data to disk. The disk may have run out of space. Action: Check the UNIX error number. ORA-02821 The requested number of blocks cannot be read. Explanation: A server was unable to read the requested number of blocks. The end of the file may have been read. Action: Check the file on disk. ORA-02822 Invalid block offset Cause: A server was unable to retrieve the designated block. Action: Check the UNIX error number. ORA-02823 The buffer is not aligned. Cause: The buffer being I/Oed to is not at the correct boundary. Action: Check the calling program. ORA-02824 Free request list is empty Cause: The list from which the package allocates request descriptors is empty because all descriptors are in use. Action: Wait until some are published, or initialize the package with a larger number of request descriptors.

5-60

message error

ORA-02825 The request in the free list was not free Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02826 Invalid block size Cause: A negative number was supplied for the I/O block size to be used by the asynchronous I/O packet. This is a programming error. Action: Use a positive number or zero to get the default value. ORA-02827 Invalid file number Cause: The file number to perform an operation on is less than zero or greater than the maximum number of files that can be opened. Action: Since the calling program should not touch this number, this is a programming error. ORA-02828 Free segment list is empty Cause: No segment available for allocation. Action: Free some threads or end the package and restart with a larger number of threads. ORA-02829 No segments of the right size available Cause: There are no segments of the right size ready for the caller to use. Action: Release some threads and try again. ORA-02830 Could not split segment: no free segments available Cause: Could not split a segment larger than desired because there were no free segments available. Action: Release some threads and try again. ORA-02831 Segment deallocation failed: segment list empty Cause: The caller tried to deallocate a segment, but the "in use" list was empty. This is a programming error. Action: Check the calling program. ORA-02832 Segment deallocation failed: Segment not in list Cause: The caller tried to deallocate a segment that was not in the "in use" list. This is a programming error. Action: Check the calling program.

ORA-02100 to ORA-04099

5-61

ORA-02833 Server could not close file Cause: A server could not close a file that is used for asynchronous I/O. Action: See the UNIX error number for more information. ORA-02834 The server could not open the file Cause: The server could not open a file for use with asynchronous I/O. Action: Check the UNIX error number for more information. ORA-02835 Server cannot send signal to client Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02836 Cannot create temporary key file Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02837 Cannot unlink temporary file Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02838 Cannot arm signal handler for alarm signal Cause: Failed to arm a signal handler for alarm signal. This is an internal error. Action: Contact Oracle Customer Support. ORA-02839 Failed to sync blocks to disk. Cause: The server was unable to flush its writes to disk. Action: Check the UNIX error number. ORA-02840 Client could not open log file Cause: The client process could not open its log file. Action: Check the UNIX error number for more information. ORA-02841 Server died on startup Cause: A server shut down during the startup process. Action: Check the server logs for more information.

5-62

message error

ORA-02842 Client was unable to fork a server Cause: The client was unable to spawn a server. One possible reason is that the operating system has reached its limit on the number of processes it can spawn. Action: Reduce the number of servers to be used or reconfigure the operating system so that it can handle more processes. ORA-02843 Invalid value for kernel flag Cause: An invalid value for the kernel flag was provided in the information structure. Only TRUE and FALSE are allowed. This is a programming error. Action: Check the calling routine. ORA-02844 Invalid value for leave open flag Cause: A value was provided for the flag that determines whether a file should be left open after the client has checked to see if servers can use it. Only TRUE and FALSE are accepted. This is a programming error. Action: Check the calling routine. ORA-02845 Invalid value for desired timeout flag Cause: A value was supplied for the flag that indicates that operations should time out. Only TRUE and FALSE are accepted. This is a programming error. Action: Check the calling routine. ORA-02846 Server indestructible Cause: A server was unable to respond to the shutdown signal. The first number is the server number. The second is the UNIX process number. This is an internal problem. Action: Contact Oracle Customer Support. ORA-02847 Server did not shutdown when published Cause: A server did not respond to a published shutdown request. The first number is the server number. The second is the UNIX process number. This is an internal problem. Action: Contact Oracle Customer Support. ORA-02848 Asynchronous I/O package is not executing Cause: An operation was attempted on the asynchronous I/O package without first initializing the package with SFAINIT(). Action: Call SFAINIT() before using the package.

ORA-02100 to ORA-04099

5-63

ORA-02849 Read failed due to error Cause: A server was unable to read the requested amount of data from disk. Action: Check the UNIX error number. ORA-02850 File is closed Cause: The package has already closed a file on which an asynchronous I/O operation is to be performed. This is a programming error. Action: Check the calling program. ORA-02851 Request list is empty when it shouldn't Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-02852 Invalid critical section timeout value Cause: The time provided was not a positive number. Action: Use a positive number. ORA-02853 Invalid server list lock timeout value Cause: The time provided was not a positive number. Action: Use a positive number. ORA-02854 Invalid number of request buffers Cause: The value provided for DB_SLAVE_BUFFERS in your INIT.ORA file is less than 0. Action: Use a number greater than or equal to 0. ORA-02855 The number of requests is less than the number number of slaves Cause: The value supplied for DB_SLAVE_BUFFERS in your INIT.ORA file is less than the number specified for the number of slaves, DB_SLAVES. Action: Specify a number greater than the given for DB_SLAVES Alternatively, specify 0. The kernel will provide the appropriate number. ORA-02875 smpini: Unable to get shared memory for PGA Cause: Indicated by error code (errno). Action: Solve the problem. ORA-02876 smpini: cannot connect to shared memory for PGA Cause: Indicated by error code (errno).

5-64

message error

Action: Solve the problem. ORA-02877 smpini: Unable to initialize memory protection Cause: The ADSPCINIT program did not run. Action: Run the ADSCPINIT program as shown in the Installation and User's Guide. If the problem persists, try restarting your computer. ORA-02878 sou2o: smpdidini variable overwritten Cause: The SMPDIDINI variable was overwritten, probably by client code. Action: Check the client code (for example, in Pro*C, check for illegal memory access). If the problem occurs outside of a single task operation, contact Oracle Customer Support. ORA-02879 sou2o: Cannot access protected memory Cause: This is an internal error, note the error code in errno. Action: Restarting the application or the computer may resolve the issue. If not, please report the error to Oracle Customer Support. ORA-02880 smpini: Cannot register PGA for protection Cause: This is an internal error, note the error code in errno. Action: Restarting the application or the computer may resolve the issue. If not, please report the error to Oracle Customer Support. ORA-02881 sou2o: Cannot revoke access to protected memory Cause: This is an internal error, note the error code in errno. Action: Restarting the application or the computer may resolve the issue. If not, please report the error to Oracle Customer Support. ORA-02882 sou2o: Cannot register SGA for protection Cause: This is an internal error, note the error code in errno. Action: Restarting the application or the computer may resolve the issue. If not, please report the error to Oracle Customer Support. ORA-02899 smscre: Cannot create SGA with extended shared memory feature Cause: The EXTSHM environment variable was set before starting Oracle. Action: Clear the EXTSHM environment variable and restart Oracle. ORA-03001 function not implemented Cause: An attempt was made to use a function that is not currently implemented.

ORA-02100 to ORA-04099

5-65

Action: Do not attempt to use this function at this time. ORA-03002 Operator not implemented Cause: An attempt was made to use an operator that is not currently implemented. Action: Do not attempt to use this operator at this time. Deprecated Function ORA-03007 Cause: An attempt was made to use a function that is no longer supported. Action: No action is required. Parameter ORA-03008 COMPATIBLE >= string required for string Cause: An attempt was made to use a function for a version of Oracle after setting the initialization parameter, COMPATIBLE. Action: Set COMPATIBLE to the value of the message (or higher) and try the command again, but remember that this will limit your downgrade options. Cannot assign communication area ORA-03100; out of memory Cause: An attempt to allocate stack space for communication purposes failed. This is an internal error message that is usually not issued. Action: Contact Oracle Customer Support. Internal protocol error ORA-03105 ORA-03106 Fatal two-task communication protocol error Cause: The communication path between Oracle and the user task has been interrupted. This is an internal error message that is usually not issued. Action: Contact Oracle Customer Support. ORA-03107 oranet buffer overflow Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support. ORA-03108 oranet: ORACLE does not support this interface version Cause: The version of Oracle connected via Net8 does not support this version of the Net8 protocol. Action: Please upgrade to a previous version of Oracle and try again.

5-66

message error

ORA-03109 oranet buffer overflow Cause: The data being transferred between the user program and Oracle has exceeded the available buffer space. This is an internal error message that is usually not issued. Action: Contact Oracle Customer Support. ORA-03110 oranet: ORACLE is not compatible with this version of SQL Cause: The version of Oracle connected via Net8 is not compatible with the version of the Net8 protocol. Action: Please upgrade to a previous version of Oracle and try again. ORA-03111 Interrupt received on communication channel Cause: An interrupt was processed on the communication channel, but was not handled correctly by the Net8 software. This is an internal error message that is usually not issued. Action: Contact Oracle Customer Support. ORA-03112 Single task linked server cannot use SQL*Net Cause: A statement containing a Net8t connection string was issued to the single task server. For example, a database link was used in an SQL statement. Action: Do not use Net8t connection strings in a single task environment. ORA-03113 End of file on communication channel Cause: An unexpected end of file was processed on the communication channel. The problem could not be resolved with the two-task Net8 software. This message may appear if the two-task shadow process associated with a Net8 connection terminated abnormally or if there is a physical failure of the inter-process communication vehicle, ie the network or server machine has gone down. Also, this message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM DISCONNECT SESSION is issued with the IMMEDIATE qualifier because, in these cases, the client's connection to the database is terminated without waiting for the client to issue a request. Action: If this message appears during a connection attempt, check the appropriate Net8 driver configuration files and confirm that the Net8 software is correctly installed on the server. If the message appears after a successful connection and the failure is not due to a physical failure, verify that a trace file was generated on the server at the time of failure. The existence of a trace file may suggest an internal Oracle error that requires customer service assistance.

ORA-02100 to ORA-04099

5-67

ORA-03114 not connected to ORACLE Cause: A call to Oracle was attempted when no connection was established. This usually happens because a user-written program is not connected. It can occur if the communication problem causes a disconnection. Also, this message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM DISCONNECT SESSION is issued with the IMMEDIATE qualifier because, in these cases, the client's connection to the database is terminated without waiting for the client to issue a request. Action: Try again. If the message appears again and the program is user-written, check the program. ORA-03115 Unsupported network representation or data type Cause: This heterogeneous Net8 connection does not support a binding or user definition, or an Oracle function. Action: Please upgrade to a previous version of Oracle and try again. ORA-03116 Invalid buffer length passed to conversion routine Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support. Two Job Save Area Overflow ORA-03117 Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support. The ORA-03118 two-task routine has an invalid state. Cause: This is an internal error message that is not normally issued. Action: Contact Oracle Customer Support. ORA-03120 two-task conversion routine: integer overflow Cause: An integer value in an internal Oracle structure overflowed when it was sent or received over a heterogeneous connection. This can occur when an invalid buffer size or too large a line count is specified. It usually indicates an error in the user agent. Action: Check the parameters for the Oracle calls. If the problem persists, reduce all integer parameters, excluding column values, to less than 32767. ORA-03121 no interface driver attached - function not performed Cause: This message usually occurs because the Net8 driver is not loaded on the memory or not is a driver version mismatch. a user program

5-68

message error

linked to an outdated library can also cause this message. Only programs provided by Oracle Corporation should use this interface. Action: If the message appeared while you were using a program provided by Oracle Corporation, contact customer support. If a user program caused the message, relink the program with the current versions of the Oracle libraries. ORA-03122 attempt to close ORACLE window on user side Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-03123 operation would block Cause: The attempted operation cannot be completed now. Action: Repeat the operation later. Internal error of two tasks ORA-03124 Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-03125 Client-server protocol violation Cause: The application received an invalid escape sequence from the server and could indicate a problem with the user code of the client application. Action: Contact Oracle Customer Support. ORA-03126 The network driver does not support non-blocking operations Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations. Action: Use standard blocking operations or use a driver that supports non-blocking operations. ORA-03127 a new operation is not allowed until the active operation completes Cause: A new operation was attempted before the active non-blocking operation completed, or a new operation was attempted before all the operations were inserted or retrieved. parts of a column Action: Run the new operation after the non-blocking operation completes. If making part bindings/definitions, perform the new operation after all parts have been inserted or obtained.

ORA-02100 to ORA-04099

5-69

ORA-03128 connection is in blocking mode Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode. Action: If non-blocking mode is required, use the appropriate OCI calls to change the mode. ORA-03129 The next part to be inserted is required. Cause: The application performed a piecewise join on a column. Action: Provide the next part of this binding variable. The ORA-03130 buffer is required to get the next part. Cause: The application performed a piecewise definition on the column. Action: Provide the next buffer to retrieve the next part. ORA-03131 Invalid buffer provided for next part Cause: The application passed the buffer length for the next part as zero or provided a null pointer. Action: Check if the buffer pointer to the next part is null or if the length is zero. ORA-03200 Invalid segment type specification Cause: The segment type is not TABLE, INDEX, or CLUSTER. Action: Use a correct segment type. ORA-03201 Invalid group number specification Cause: The free list group number is negative or greater than the number of free list groups in the segment. Action: Use a correct group number. ORA-03202 Invalid scan limit specification Cause: The scan limit does not have a positive integer value greater than the number of free list groups in the segment. Action: Use a correct analysis threshold. ORA-03203 Concurrent update activity makes space analysis impossible Cause: High volume of user updates interferes with space analysis. Action: Retry the command or lock the underlying objects.

5-70

message error

ORA-03204 Segment type specification must indicate partition Cause: A partition name was specified for space analysis, but the object type does not indicate partition. Action: Specify PARTITION in the segment type if the object is to be partitioned. Otherwise, omit the partition name. ORA-03205 partition name is required when partition type is specified Cause: A partition name was not specified for space analysis, but the object type indicates partition. Action: Specify a partition name if the object is to be partitioned. Otherwise, specify a non-partitioned type. ORA-03206 Maximum file size of blocks (string) in AUTOEXTEND clause is out of range Cause: The maximum file size for an autoextend file exceeded the maximum number of blocks allowed. Action: Reduce the size and try again. ORA-03207 The subpartition type must be specified for the composite object. Cause: A partition type is specified for space analysis, but the object type indicates a composite partition. Action: Specify a subpartition name and a subpartition type. ORA-03208 partition type must be specified for a non-composite object. Cause: A subpartition type is specified for space analysis, but the object type indicates a noncomposite partition. Action: Specify a partition name and a partition type. Invalid file/block specification DBMS_ADMIN_PACKAGE ORA-03209 Cause: The file number or block number value is out of bounds or inconsistent. Action: Correct the value of the file number/block number. ORA-03210 DBMS_ADMIN_PACKAGE invalid option specification Cause: The value of one of the option parameters is incorrect. Action: Correct the value of the option.

ORA-02100 to ORA-04099

5-71

ORA-03211 Segment does not exist or is not in a valid state Cause: The segment specified in the DBMS_SPACE_ADMIN operation does not have or is not in a state appropriate for this operation. Action: Correct the segment specification or put the segment in the proper state. ORA-03212 Cannot create a temporary slice in a locally managed tablespace. Cause: An attempt was made to create a temporary segment for SORT/HASH/LOBS in a locally managed permanent tablespace. Action: Change the user's temporary tablespace to a temporary tablespace or dictionary-managed permanent tablespace. ORA-03213 Invalid LOB segment name for package DBMS_SPACE Cause: The LOB segment specified in the DBMS_SPACE operation does not exist. User Response: Correct the segment specification. ORA-03214 The specified file size is less than the minimum required Cause: The file size specified for adding/resizing the data file/temp file does not allow for the required minimum of an allocation unit. Action: Increase the file size specification. ORA-03215 The file size specified to resize is too small Cause: The file size specified to resize the data file/temp file causes bitmap control structures to overlap. Action: Increase the file size specification. ORA-03216 Segment/tablespace check cannot continue Cause: Corruption detected during check that cannot be handled Action: Perform manual check. ORA-03217 Invalid option to change temporary tablespace Cause: An invalid option was specified to change temporary tablespace. Action: Specify one of the valid options: ADD TEMPFILE. ORA-03218 invalid option to CREATE/ALTER TABLESPACE Cause: Invalid option to create/alter tablespace of type locally managed. Action: Specify one of the valid options.

5-72

message error

ORA-03219 Applies only to locally managed tablespaces. Tablespace 'string' is not locally managed Cause: The operation that is only applicable to locally managed tablespaces is specified for a dictionary-managed tablespace. Action: Reissue the operation for a different table space or do not issue it because it does not apply to the specified table space. ORA-03220 Mandatory parameter DBMS_ADMIN_PACKAGE is NULL or missing Cause: Some of the procedures were called with missing or NULL parameters. Action: Specify the missing parameter. Segment ORA-03230 contains only unused space string blocks above the high watermark Cause: An attempt was made to preserve too many blocks. Action: Reduce the amount of KEEP. ORA-03231 Unable to deallocate extension INITIAL Cause: An attempt was made to deallocate space from the slice that was truncated prior to version 7.3. Action: Increase the HOLD amount or truncate the segment and issue the command again. ORA-03232 cannot allocate a chain block extent from table space chain Cause: An attempt was made to specify a HASH_MULTIBLOCK_IO_COUNT value greater than the table space NEXT value. Action: Increase the value of NEXT for the tablespace using ALTER TABLESPACE DEFAULT STORAGE or decrease the value of HASH_MULTIBLOCK_IO_COUNT. ORA-03233 cannot extend subpartition string.string of table string by string in table space string Cause: Failed to allocate an extension for subpartition segment of table in table space. User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-03234 cannot extend index string.string subpartition string by string in tablespace string Cause: Could not allocate an extension for index subpartition segment in tablespace.

ORA-02100 to ORA-04099

5-73

User Response : Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-03235 maximum number of extents (string) reached in table string.string subpartition string Cause: A table subpartition attempted to extend beyond MAXEXTENTS. Action: If the value of MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-03236 maximum number of extents (string) reached in the index string. string subpartition string Cause: An index subpartition attempted to extend beyond MAXEXTENTS. Action: If the value of MAXEXTENTS is less than the system maximum, increase it. Otherwise, you must rebuild with larger boot, next, or PCTINCREASE parameters. ORA-03237 Cannot allocate initial extent of specified size Cause: The size is too large for the initial extent due to the free list group specification. Action: Reduce the number of free list groups specified for the segment. ORA-03238 could not extend LOB segment string.string subpartition string by string in tablespace string Cause: An attempt was made to allocate an extension for the LOB subpartition segment in tablespace, but the extension could not be allocated because there is not enough space in the indicated tablespace. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the indicated tablespace. ORA-03239 maxextents(string) reached in LOB segment string.string subpartition string Cause: A LOB subpartition segment attempted to extend beyond MAXEXTENTS. Action: If the value of MAXEXTENTS is less than the system maximum, increase it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters. ORA-03274 ALLOCATE EXTENT and DEALLOCATE UNUSED options specified Cause: The DEALLOCATE and ALLOCATE options were specified in the same command.

5-74

message error

Action: Choose one of the options or issue two separate commands. ORA-03275 Duplicate DEALLOCATE option specification Cause: The DEALLOCATE UNUSED option for ALTER TABLE or ALTER INDEX was specified more than once. Action: Specify the option at most once. ORA-03276 Duplicate ALLOCATE EXTENT option specification Cause: The ALLOCATE EXTENT option for ALTER TABLE or ALTER INDEX was specified more than once. Action: Specify the option at most once. ORA-03277 Invalid SIZE specified Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-03278 Duplicate ALLOCATE EXTENT option specification Cause: An option (DATA FILE, SIZE, or INSTANCE) was specified more than once. Action: Specify each option at most once. ORA-03279 Invalid INSTANCE specified Cause: The specified value is not recognized as a valid instance name. Action: Use a valid name. ORA-03280 An invalid DATAFILE file name was specified. Cause: A string literal was expected, but was not found. User Response : Specify the file names using string literals. ORA-03281 Invalid ASSIGN EXTENT option Cause: An option other than DATA FILE, SIZE, or INSTANCE was specified. Action: Remove the invalid option and retry the command. ORA-03282 Missing ALLOCATE EXTENT option Cause: No ALLOCATE EXTENT option specified. Action: Specify one or more of the following options: DATA FILE, SIZE, or INSTANCE.

ORA-02100 to ORA-04099

5-75

ORA-03283 The specified data file string does not exist Cause: The data file does not exist. Action: Retry the option with the correct data file. ORA-03284 The data file string is not a member of the table space string Cause: The specified data file does not belong to the table space in which the object resides. Action: Retry the option with the correct data file. ORA-03286 ALLOCATE EXTENT is invalid for HASH CLUSTERS Cause: The cluster cannot use the extension allocation option because it is a hash cluster. Action: Do not use this command on a hash cluster. ORA-03287 FREE LIST GROUP specified invalid Cause: The specified FREE LIST GROUP number is invalid. Action: Choose a number between 1 and the number of free list groups for this object. ORA-03288 Cannot specify FREELIST GROUP and INSTANCE parameters Cause: Both FREELIST GROUP and INSTANCE were specified in the clause. Action: Delete one of the two parameters. ORA-03290 Invalid truncation command: Missing CLUSTER or TABLE keyword Cause: An invalid object specification was supplied. User Response: Specify TRUNCATE CLUSTER or TRUNCATE TABLE. ORA-03291 Invalid truncation option: STORAGE keyword missing Cause: The STORAGE keyword was expected. Action: Specify LEAVE STORAGE or REUSE STORAGE. ORA-03292 The table to be truncated is part of a cluster Cause: The table to be truncated is a member of a cluster. Action: Use TRUNCATE CLUSTER or DROP TABLE. ORA-03293 The cluster to be truncated is a HASH CLUSTER Cause: Only INDEX CLUSTERS can be truncated.

5-76

message error

Action: Drop and recreate the HASH CLUSTER instead of using truncation. ORA-03296 cannot resize data file: file string not found Cause: The specified data file is not available for resizing. Action: Make sure the data file name is valid, and if so, make sure the file is accessible. File ORA-03297 contains data used beyond the requested RESIZE value Cause: Part of the file in the region to be clipped is currently in use by a database object. Action: Drop or move segments containing extents in this region before resizing the file, or choose a resize value so that only free space is clipped. ORA-03298 cannot shrink data file: file chain has an active backup Cause: Attempt to shrink a data file while an active backup is in progress. This is not allowed. Action: Try shrinking the file again after the active backup is complete. ORA-03299 Cannot create dictionary table string Cause: A dictionary table is created on the first execution of the ALTER DATABASE DATAFILE AUTOEXTEND ON command for a database. This operation was unsuccessful. The most likely cause of this is insufficient space in the system tablespace. Action: View the action for the next error message in the error stack. ORA-04000 The sum of PCTUSED and PCTFREE cannot exceed 100 Cause: The sum of PCTUSED and PCTFREE for a cluster or table exceeds 100. Action: Create the table/cluster by specifying values whose sum is less than or equal to 100. ORA-04001 string parameter string must be an integer Cause: The specified string (a string parameter) was not an integer. Action: Create the sequence, assigning the specified parameter an integer value. ORA-04002 INCREMENT must be a non-zero integer Cause: A sequence increment was specified as zero. Action: Specify the increment as a non-zero value.

ORA-02100 to ORA-04099

5-77

ORA-04003 Sequence parameter string exceeds maximum allowed length (string digits) Cause: The string (a sequencer parameter) had too many digits. Action: Specify the parameter with the allowed number of digits. ORA-04004 MINVALUE must be less than MAXVALUE Cause: MINVALUE was specified to be greater than or equal to MAXVALUE. Action: Specify a MINVALUE less than MAXVALUE. ORA-04005 INCREMENT must be less than MAXVALUE minus MINVALUE Cause: The specified INCREMENT is greater than or equal to MAXVALUE-MINVALUE. Action: Specify an INCREMENT less than MAXVALUE-MINVALUE. ORA-04006 START WITH cannot be less than MINVALUE Cause: The supplied start value is less than MINVALUE. Action: Make sure that the initial value is greater than or equal to MINVALUE. ORA-04007 MINVALUE cannot exceed current value Cause: The supplied MINVALUE would be greater than the current value. Action: Always ensure that MINVALUE is less than or equal to the current value. ORA-04008 START WITH cannot be greater than MAXVALUE Cause: The start value would be greater than MAXVALUE. Action: Make sure that the initial value is less than MAXVALUE. ORA-04009 MAXVALUE cannot be less than the current value Cause: The current value exceeds the given MAXVALUE. Action: Make sure that the new MAXVALUE is greater than the current value. ORA-04010 number of values for CACHE must be greater than 1 Cause: The value in the CACHE clause was one. Action: Specify NOCACHE or a value greater than one. ORA-04011 string string must vary between string and string Cause: The value specified for one of the string parameters exceeds limits.

5-78

message error

Action: Specify a parameter within these limits. The ORA-04012 object is not a sequence. Cause: The specified object cannot execute stream DDL. Action: Rewrite the declaration, being careful about the spelling of the name. ORA-04013 CACHE number must be less than one loop Cause: The CACHE number specified in a CREATE SEQUENCE statement exceeds the number of values in one loop. Action: Increase the loop or cache fewer values and try again. ORA-04014 Descendant CYCLE sequences must specify MINVALUE Cause: A value was not specified in the CREATE SEQUENCE statement. Sequences in this loop must specify a value at which to start over. Action: Recreate the sequence, specifying the value at which it should start. ORA-04015 Ascending CYCLE sequences must specify MAXVALUE Cause: A value was not specified on the CREATE SEQUENCE statement. Sequences in this loop must specify a value at which to start over. Action: Recreate the sequence, specifying the value at which it should start. ORA-04016 sequence string no longer exists Cause: The sequence was discarded while its next value was being processed. Action: Re-create the sequence. ORA-04017 Invalid string value (length = string) for parameter max_dump_file_size Cause: The string supplied for the MAX_DUMP_FILE_SIZE parameter did not match the string value "UNLIMITED" or represented a base 10 integer. Action: Reassign an appropriate value to this parameter. ORA-04018 Invalid value string for _scn_scheme parameter Cause: The value specified for the _SCN_SCHEME initialization parameter is not recognized as one of the defined schemes. Action: Reassign an appropriate value.

ORA-02100 to ORA-04099

5-79

ORA-04019 SCN Scheme incompatible with other instances Cause: Different instances are running incompatible versions of Oracle or different values were assigned to the _SCN_SCHEME initialization parameter on different instances. User Response: Make sure that the initialization parameter _SCN_SCHEME has the same value in all instances. ORA-04020 crash detected while trying to lock object stringstringstringstringstring Cause: While trying to lock a library object, a lock was detected. Action: Repeat the operation later. ORA-04021 Timed out waiting to lock object stringstringstringstringstring Cause: Timed out while waiting to lock a library object. Action: Repeat the operation later. ORA-04022 Nowait requested but had to wait to lock dictionary object Cause: Had to wait to lock a library object during a nowait request. Action: Repeat the operation later. ORA-04028 unable to generate target for object stringstringstringstringstring Cause: Unable to generate target for an object due to a lock conflict. Action: Report this error to your support representative. ORA-04029 ORA-string error occurred while querying stringstringstring Cause: The table or view being queried might be missing. The error number indicates the error. Action: Correct the error. ORA-04030 Insufficient process memory when trying to allocate string bytes (string,string) Cause: The operating system's private process memory was exhausted. Action: Consult your database or operating system administrator to increase the memory quota of the process. There may be a bug in the application that causes excessive allocations of process memory space.

5-80

message error

ORA-04031 cannot allocate shared memory string bytes ("string","string","string","string") Cause: More shared memory is needed than allocated in the shared pool. Action: If the shared pool is out of memory, use the DBMS_SHARED_POOL package to clamp large packages, reduce shared memory usage, or increase the amount of available shared memory by increasing the value of the SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE initialization parameters. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE. The ORA-04041 package specification must be created before creating the package body. Cause: Attempting to create a package body before creating its package specification. User Response : Create the package specification before creating the package body. ORA-04042 Procedure, function, package, or package body does not exist Cause: An attempt was made to access a procedure, function, package, or package body that does not exist. Action: Make sure the name is correct. The object string ORA-04043 does not exist. Cause: An object name was specified that the system did not recognize. The following are possible causes: ■

■

An invalid name was entered for a table, view, sequence, procedure, function, package, or package body. Since the system did not recognize the invalid name, it responded with the message that the named object does not exist. An attempt was made to rename an index or cluster or some other object that cannot be renamed.

Action: Check the spelling of the named object and run the code again. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.) Procedure, function, package, or type ORA-04044 is not allowed here. Cause: A procedure, function, or package was specified in an inappropriate place in a declaration.

ORA-02100 to ORA-04099

5-81

Action: Verify that the name is correct or remove it. ORA-04045 errors during rebuild/revalidation of string.string Cause: This message indicates the object to which the following errors apply. The errors occurred during the implicit recompile/revalidation of the object. Action: Check the errors below for more information and make any necessary corrections to the object. ORA-04046 Build results too large to handle Cause: An attempt was made to compile and store a large stored procedure that results in build data that is too large for the system to handle or store. User Response: Reduce the size of the stored procedure by breaking it into smaller stored procedures. ORA-04047 The specified object is not compatible with the specified flag. Cause: The implicit object type in the prompt does not match the specified object type. Action: Specify the correct object or use the appropriate flag. ORA-04050 Invalid or missing package, function or procedure name Cause: The required package, function or procedure name is invalid or missing. Action: Specify a valid name. ORA-04051 user string cannot use database link string.string Cause: When forwarding access to a remote object, an attempt was made to use a database link that did not exist or was owned by a user other than login user or PUBLIC. Action: Change your database link structure so that all indirect remote access is from the same user ID that originated the request. ORA-04052 error occurred while searching for a remote object stringstringstringstringstring Cause: An error occurred while trying to search for a remote object. Action: Correct the error. Make sure the remote database system has run KGLR.SQL to create the necessary views that are used to query/lookup objects stored in the database.

5-82

message error

ORA-04053 error occurred while validating remote object stringstringstringstringstring Cause: An error occurred while trying to validate a remote object. Action: Correct the error. Make sure the remote database system has run KGLR.SQL to create the necessary views that are used to query/lookup objects stored in the database. ORA-04054 Database link string does not exist Cause: When compiling a PL/SQL block, an attempt was made to use a non-existent database link. Action: Use a different database link or create the database link. ORA-04055 Aborted: "string" has formed a mutually dependent non-REF loop with "string". Cause: This build was aborted because the library unit that was compiled would have formed a mutually dependent non-REF loop with some other library units. This happens when trying to compile types that have attributes of other types that might toggle with that type. Example: create type t1; create type t2 (to t1); create type t1 (one t2);

Action: Stop the loop (possibly by adding a REF or using another type). ORA-04060 Insufficient privileges to execute string Cause: An attempt was made to execute a stored procedure without sufficient privileges. Action: Obtain the necessary privileges. ORA-04061 The existing state of the chain was invalidated Cause: An attempt was made to resume execution of a stored procedure using the existing state that became invalid or inconsistent with the stored procedure because the procedure was changed or deleted. Action: try again; this error should have caused all packages to be reset to the existing state. ORA-04062 string string changed Cause: An attempt is made to execute a stored procedure to service an RPC stub that specifies a different timestamp/signature than the procedure's current timestamp/signature. Action: Recompile the caller to get the new timestamp.

ORA-02100 to ORA-04099

5-83

String ORA-04063 contains errors Cause: An attempt to execute a stored procedure or use of a view failed. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view definition query to a non-existent table. It could also be a table that has references to non-existent or inaccessible types. Action: Correct the errors and/or create referenced objects as necessary. ORA-04064 not executed, string invalidated Cause: An attempt was made to execute a stored procedure that was invalidated. User Response: Recompile the stored procedure. ORA-04065 String not executed, changed, or dropped Cause: Attempting to execute a stored procedure that has been altered or dropped, so it cannot be called from the calling procedure. Action: Rebuild your dependents. ORA-04066 non-executable object, string Cause: An attempt was made to execute a non-executable procedure. Action: Make sure you provide a correct name. ORA-04067 not executed, string missing Cause: An attempt was made to execute a non-existent stored procedure. Action: Make sure you provide a correct name. ORA-04068 Discarded existing state of packagesstringstringstring Cause: An error occurred while trying to execute a stored procedure. Action: Check the attached messages and correct the mentioned error. Retry the procedure after you restore the proper state of any application. ORA-04070 invalid trigger name Cause: An invalid trigger name was specified. Action: Verify that the trigger name is not a reserved keyword. ORA-04071 Missing keyword BEFORE, AFTER, or INSTEAD OF Cause: The trigger declaration does not contain the BEFORE/AFTER/INSTEAD OF clause. Action: Specify BEFORE, AFTER, or INSTEAD OF.

5-84

message error

ORA-04072 invalid trigger type Cause: An invalid trigger type was supplied. Action: Specify INSERT, UPDATE, or DELETE. ORA-04073 Invalid column list for this trigger type Cause: A column list was specified for an out-of-date trigger type. Action: Delete the column list. ORA-04074 invalid REFERENCE name Cause: An invalid name was supplied in the reference clause. User Response: Check that the reference name is not a reserved word. ORA-04075 Invalid activation action Cause: An instruction for the activation action was provided. Action: Re-specify the action of the trigger. ORA-04076 Invalid NEW or OLD specification Cause: An invalid NEW or OLD specification was provided for a column. Action: Respecify the column using the correct NEW or OLD specification. ORA-04077 WHEN clause cannot be used with table level triggers Cause: The when clause can only be specified for row level triggers. User Response : Remove the when clause or specify for each row. ORA-04078 Values OLD and NEW cannot be identical Cause: The reference clause specifies identical values for NEW and OLD. Action: Re-enter the OLD or NEW reference value. ORA-04079 Invalid trigger specification Cause: The TRIGGER create statement is invalid. User Response: Verify that the statement has the correct syntax. ORA-04080 Trigger 'string' does not exist Cause: The trigger name is invalid. Action: Check the name of the trigger. ORA-04081 trigger 'string' already exists Cause: TRIGGER name or type already exists.

ORA-02100 to ORA-04099

5-85

Action: Use a different trigger name or remove the trigger with the same name. ORA-04082 NEW or OLD references not allowed in table level triggers Cause: The trigger is accessing "new" or "old" values in a table trigger. Action: Remove all new or old references. ORA-04083 invalid trigger variable 'string' Cause: The variable referenced in the trigger body is invalid. Action: See the Oracle8i SQL Reference for valid activation variable types. ORA-04084 cannot change NEW values for this type of trigger Cause: New trigger variables can only be changed before inserting a row or updating triggers. Action: Change the trigger type or remove the reference of the variable. ORA-04085 cannot change the value of an OLD reference variable Cause: Old values can only be read and not changed. Action: Do not try to change an old variable. ORA-04086 Trigger description too long, move comments to trigger code Cause: Trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the PL/SQL code executed for the trigger. Action: If the trigger description contains a long comment, move that comment to the trigger's PL/SQL code. ORA-04087 cannot change value of ROWID reference variable Cause: ROWIDs can only be read and not changed. Action: Do not try to change a ROWID value. ORA-04088 error executing trigger 'string.string' Cause: A runtime error occurred while executing a trigger. Action: Check the triggers that were involved in the operation. ORA-04089 cannot create triggers on objects owned by SYS Cause: An attempt was made to create a trigger on an object owned by SYS. Action: Do not create triggers on objects owned by SYS.

5-86

message error

ORA-04090 'string' specifies the same table, event, and trigger time as 'string' Cause: trigger is a duplicate trigger event and time. Action: Combine the trigger information into a trigger that fires at the given time. ORA-04091 table string.string is mutating, trigger/function might not see it Cause: A trigger (or a PL/SQL user-defined function referenced in this statement) attempted to examine (or modify) a table that was in the middle of being modified by the statement that triggered it. Action: Rewrite the trigger (or function) so that it does not read this table. ORA-04092 cannot be a string in a trigger Cause: A trigger tried to commit or roll back. Action: Rewrite the trigger so that it is not committed or rolled back. ORA-04093 References to columns of type LONG are not allowed in triggers. Cause: A trigger tried to reference a long column in the triggers table. User Response: Do not reference the long column. ORA-04094 Table string.string is constrained, trigger cannot modify it Cause: A trigger tried to modify a table that was constraining some referential constraint of a main SQL statement. Action: Rewrite the trigger so that it does not modify this table. ORA-04095 Trigger 'string' already exists on another table, cannot be replaced Cause: A trigger that already exists on a different table than the one being replaced cannot be replaced. Action: Drop the trigger with the same name and recreate it. ORA-04096 Trigger 'string' has WHEN clause too large, 2K limit Cause: The WHEN clause of a trigger is limited to 2K for dictionary storage reasons. The trigger being created has exceeded this size. Action: Use a shorter WHEN clause. Note that the body of the trigger can be used to perform the same constraint action as the WHEN clause. ORA-04097 DDL conflict when trying to remove or change a trigger Cause: An attempt was made to simultaneously perform two DDL operations on a trigger or on a trigger table.

ORA-02100 to ORA-04099

5-87

Action: Investigate the new activation status and retry the DDL operation if it is still appropriate. ORA-04098 Trigger 'string.string' is invalid and revalidation failed Cause: An attempt was made to retrieve a trigger for execution and was found to be invalid. It also means that build/authorization failed for the trigger. Action: The options are to resolve compile/authorization errors, disable the trigger, or dismiss the trigger. The ORA-04099 trigger 'string' is valid but is not stored in compiled format. Cause: An attempt was made to retrieve a trigger for execution and was found to be valid, but it was not stored. This could mean that an incorrect update was made from a non-stored activation version. Action: Change the build of the trigger to build the trigger in stored format. Also, you may want to verify that a proper update has been done.

5-88

message error

6 ORA-04100 to ORA-07499 ORA-04930 open sequence number failed or initial state is valid Cause: OS component Shared Sequence Number was not installed correctly or MC hardware failure or previous instance failed closed successfully. Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the operating system command ps -ef|grep instance_name. Verify that there are no shared memory segments owned by the user who owns the Oracle installation by issuing the ipcs -b operating system command. If there are still shared memory threads or processes in the system, use SVRMGRL to terminate the instance with the abort option. If the instance is not active, verify that the cluster hardware and/or software is up and running. Log in as super user and run the CNXSHOW command. Are all cluster nodes listed? Are they members of the cluster? Are the communications between the nodes ok? If the answer to any of these questions is false, please contact Digital's customer support organization. ORA-04931 cannot set initial sequence number value Cause: A call to the SSN failed to set the sequence number to its initial value, possibly due to an MC hardware problem. Action: Verify that the MC hardware is working properly. Otherwise, contact Digital's customer support organization. If so, contact Oracle Customer Support. ORA-04932 Failed to increment or adjust sequence number Cause: A call to the SSN failed to increment the sequence number.

ORA-04100 to ORA-07499 6-1

Action: Verify that the MC hardware is working properly. Otherwise, contact Digital's customer support organization. If so, contact Oracle Customer Support. ORA-04933 initial service identifier is not zero Cause: A valid service identifier existed before the sequence number service was opened. User Response: Verify that the instance is completely powered off. ORA-04934 Could not get current sequence number Cause: A call to the SSN could not return its current value. There are too many MC hardware errors occurring or the sequence number has become invalid and cannot be validated. Action: Verify that the MC hardware is working properly. If so, contact Oracle Customer Support. ORA-04935 failed to get/cast SCN fetch lock Cause: A process timed out while trying to get or cast the SCN fetch lock. Probably another process has the lock in EX or SHR mode, but is not releasing. Action: Contact Oracle Customer Support. ORA-06000 NETASY: failed to open port Cause: Autologin cannot open the port. Action: Check the log file for the operating system specific error code. ORA-06001 NETASY: port configuration failure Cause: Autologin cannot change port attributes. Action: Check the log file for the operating system specific error code. ORA-06002 NETASY: read port error Cause: Autologin cannot read from port. Action: Check the log file for the operating system specific error code. ORA-06003 NETASY: port write error Cause: Autologin cannot write to the port. Action: Check the log file for the operating system specific error code.

6-2

message error

ORA-06004 NETASY: error opening dialog file Cause: Autologin cannot open dialog file. Action: Check the connection string for any typos or precision errors. ORA-06005 NETASY: Could not read dialog file Cause: Autologin could not read the dialog file. Action: Check the log file for the operating system specific error code. ORA-06006 NETASY: Dialog execution failed Cause: The expected response was never received. Action: Check the log file for the operating system specific error code. ORA-06007 NETASY: incorrect dialog format Cause: The dialog file contains a syntax error. Action: Correct the dialog file. ORA-06009 NETASY: dialog file name too long Cause: The full specification of the dialog file exceeds 64 bytes. Action: Correct the connection string accordingly. ORA-06010 NETASY: dialog file too long Cause: The dialog file exceeds 768 bytes in length. Action: Simplify the dialog (eg remove comments, redundant white space) or split it in two and link it with the MORE command. ORA-06011 NETASY: dialog too long Cause: One of the following: ■

Dialog contains more than 24 swap blocks

■

Dialog send string exceeds 84 bytes in length

Action: Simplify the dialog or split it in two and link it with the MORE command. ORA-06017 NETASY: Error receiving message Cause: The asynchronous driver got an I/O error during the network read operation. Action: Check the log file for the operating system specific error code and contact Oracle Customer Support.

ORA-04100 to ORA-07499 6-3

ORA-06018 NETASY: error sending message Cause: Async driver got an I/O error during network write operation. Action: Check the log file for the operating system specific error code and contact Oracle Customer Support. ORA-06019 NETASY: Invalid login (connection) string Cause: Syntax error in the login string. Action: Resubmit with the correct string. ORA-06020 NETASY: initialization failed Cause: The async driver cannot complete initialization. Action: Check the log file for the operating system specific error code. ORA-06021 NETASY: connection error Cause: The async driver cannot connect to the partner. Action: Check the log file for the operating system specific error code. ORA-06022 NETASY: channel opening failed Cause: There is no free channel. Action: Contact Oracle Customer Support. ORA-06023 NETASY: failed to open port Cause: The asynchronous driver cannot open the port. Action: Check the log file for the operating system specific error code. ORA-06024 NETASY: VTM error Cause: Virtual Terminal Manager cannot read/write the port. Action: Check the log file for the operating system specific error code. ORA-06025 NETASY: Configuration Error Cause: An async handler was generated for the server only, but the client service was requested. Action: Contact Oracle Customer Support. ORA-06026 NETASY: failed to close port Cause: The asynchronous driver cannot close the port. Action: Check the log file for the operating system specific error code.

6-4

message error

ORA-06027 NETASY: failed to close channel Cause: The asynchronous driver cannot close the channel. Action: Check the log file for the operating system specific error code. ORA-06028 NETASY: cannot be initialized to register Cause: The async driver cannot be initialized to register I/O. Action: Contact Oracle Customer Support. ORA-06029 NETASY: port assignment error Cause: The asynchronous driver cannot assign the port to the channel. Action: Contact Oracle Customer Support. ORA-06030 NETDNT: connection failed, unrecognized node name Cause: The node name specified in the host string is unknown (probably misspelled). Action: Try again with the correct node name. ORA-06031 NETDNT: connection failed, unrecognized object name Cause: The host string contains a reference to the object (which does not exist): @d:node-obj => object is ORDNobj; 🇧🇷

■

when the node is VMS, the object is ORDNobj.COM when the node is UNIX, the object is ORDNobj @d:node::"task=obj" => the object is obj;

■

when the node is VMS, the object is obj.COM

■

when the node is UNIX, the object is obj

Action: Try again with the correct object name or create the required object on the host node. ORA-06032 NETDNT: connection failed, access control data refused Cause: The host string contains an invalid username/password. Action: Try again with the correct username/password. ORA-06033 NETDNT: connection failed, connection refused by partner Cause: The connection to the partner was made but was refused. Action: Contact your network administrator.

ORA-04100 to ORA-07499 6-5

ORA-06034 NETDNT: connection error, partner terminated unexpectedly Cause: The connection to the host node was made, but the partner stopped. Action: Make sure the object (see 06031, above) is running (for VMS, run the script and make sure the Oracle server process is started); sometimes it happens when the network/node is under stress; in this case, a retry usually works. ORA-06035 NETDNT: connection failed, insufficient resources Cause: There are not enough system resources available to complete the connection; for example, all DECnet channels are in use. Action: Contact your network administrator. ORA-06037 NETDNT: connection failed, cannot reach node Cause: The host node is down. Action: Contact your network administrator. ORA-06039 NETDNT: connection failed Cause: The connection failed due to an unexpected reason (see OSD error). Action: Contact Oracle Customer Support. ORA-06040 NETDNT: Invalid login (connection) string Cause: Syntax error in the login string. Action: Resubmit with the correct string. ORA-06041 NETDNT: disconnect error Cause: The driver has an error performing the network shutdown operation. Action: Contact Oracle Customer Support. ORA-06042 NETDNT: Error receiving message Cause: The driver got an I/O error while performing the network read operation. Action: Contact Oracle Customer Support. ORA-06043 NETDNT: error sending message Cause: The controller received an I/O error during a network write operation. Action: Contact Oracle Customer Support. ORA-06044 NETDNT: connection failed, byte count quota exceeded Cause: Connection failed due to insufficient byte count quota.

6-6

message error

Action: Increase the byte count quota. ORA-06102 NETTCP: unable to allocate context area Cause: Insufficient dynamic memory available for connection context area. Action: Contact Oracle Customer Support. ORA-06105 NETTCP: remote host is unknown Cause: The host name specified in the login (connection) string is unknown. Action: Check spelling; make sure the name is in the TCP/IP HOST file. ORA-06106 NETTCP: socket creation failed Cause: The open file quota for the process has probably been exceeded. Action: Contact Oracle Customer Support. ORA-06107 NETTCP: ORACLE network server not found Cause: There is no entry in the SERVICES file for the Oracle server. Action: Add the (ORASRV) entry to the TCP/IP SERVICES file. ORA-06108 NETTCP: connection to host failed Cause: An attempt to connect to the remote host failed. It probably means that the SQL*Net TCP/IP server on the remote host is not up, or that the host itself is down (check the latter by Telneting it). Action: Start the SQL*Net TCP/IP server process on the remote host. ORA-06109 NETTCP: Could not receive message Cause: An I/O error occurred while attempting a network read operation. Action: Contact Oracle Customer Support. ORA-06110 NETTCP: error sending message Cause: An I/O error occurred while attempting a network write operation. Action: Contact Oracle Customer Support. ORA-06111 NETTCP: disconnect error Cause: An error occurred while closing a socket. Action: Contact Oracle Customer Support.

ORA-04100 to ORA-07499 6-7

ORA-06112 NETTCP: invalid buffer size Cause: The buffer size specified in the login string exceeds the maximum allowed (of 4096). Action: Forward with a valid buffer size. ORA-06113 NETTCP: Too many connections Cause: The maximum number. of connections open at the same time has been reached. Action: Exit an application with an open connection that is no longer needed. ORA-06114 NETTCP: SID lookup failed Cause: From remote host's SQL*Net TCP/IP server: The SID of the database, specified in the login (connection) string, was not recognized. Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server). ORA-06115 NETTCP: cannot create ORACLE logicals Cause: The SQL*Net TCP/IP host server was unable to create the necessary logical names required by the Oracle server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact your system administrator. ORA-06116 NETTCP: Failed to create ORASRV process Cause: The SQL*Net TCP/IP host server could not create the Oracle server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact your system administrator. ORA-06117 NETTCP: failed to create ORASRV: quota exceeded Cause: The SQL*Net TCP/IP host server was unable to create the Oracle server process due to quota exhaustion. Action: Increase the quota allocations for the SQL*Net TCP/IP server process. ORA-06118 NETTCP: Failed to complete handshake with ORASRV Cause: The Oracle server process started but was unable to complete its initialization. Action: Contact Oracle Customer Support.

6-8

message error

ORA-06119 NETTCP: bogus client request Cause: The SQL*Net TCP/IP host server could not recognize this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06120 NETTCP: network driver not loaded Cause: The TCP/IP network driver was not loaded. Action: Verify that the TCP/IP driver has been loaded correctly. ORA-06121 NETTCP: access error Cause: The host's SQL*Net TCP/IP server was unable to test the reachability of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06122 NETTCP: configuration error Cause: The host's SQL*Net TCP/IP server could not set up the proper environment to service this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06123 NETTCP: KEEPALIVE could not be set Cause: The SQL*Net TCP/IP host server could not set the KEEPLIVE socket option. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06124 NETTCP: ORASRV timeout Cause: Oracle server process started but did not respond after N seconds. Action: For heavily loaded systems, this is not an uncommon occurrence. Increase the value of N (default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = no_of_secs, which will take effect the next time the SQL*Net TCP/IP server is started. ORA-06125 NETTCP: ORASRV terminated unexpectedly Cause: The Oracle server process was started but terminated unexpectedly. Possible causes: 1.

Insufficient quotas to run ORASRV

ORA-04100 to ORA-07499 6-9

Oracle is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name in the format: ORA_SRVTnn_sid.OUT

Action – If the appropriate action is not obvious in the ORASRV output file, contact Oracle Customer Support. ORA-06126 NETTCP: ORASRV could not open network connection Cause: The Oracle server process started but could not open the socket passed to it by TCPSRV. Action: Contact Oracle Customer Support. ORA-06127 NETTCP: unable to change username Cause: The host's SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client's username is unknown (to the host's operating system). Action: Create a new user account on the host. ORA-06128 NETTCP: failed to create mailbox Cause: The host's SQL*Net TCP/IP server was unable to create a mailbox (required for IPC communication with the Oracle server process). See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06129 NETTCP: failed to transfer socket ownership to ORASRV Cause: The SQL*Net TCP/IP host server was unable to transfer the network communication identifier to the Oracle server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06130 NETTCP: host access denied Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have access privileges, as determined by the contents of the valid nodes table ( VNT), a component of the host CONFIG.ORA. Action: To grant access, add the appropriate entry to the host's VNT. ORA-06131 NETTCP: user access denied Cause: The host SQL*Net TCP/IP server rejected this connection request because the client user (name) does not have access privileges as determined by

6-10

message error

the contents of the username mapping table (UMT), a component of the host's CONFIG.ORA. Action: To grant access, add the corresponding entry to the UMT of the host. ORA-06132 NETTCP: access denied, bad password Cause: The SQL*Net TCP/IP host server rejected this connection request because the client's password did not match the host's password. Action: To grant access, synchronize the passwords. ORA-06133 NETTCP: file not found Cause: The SQL*Net TCP/IP host server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request. Action: Check the spelling of CONFIG.ORA; make the correct entry. ORA-06134 NETTCP: file access privilege violation Cause: The host SQL*Net TCP/IP server did not have READ/EXECUTION permission for the SID mapping file (specified in CONFIG.ORA) associated with this request Connection. Action: Change the protection in the SID mapping file. ORA-06135 NETTCP: connection refused; server is stopping Cause: The host's SQL*Net TCP/IP server rejected this connection request because it is stopping. Action: Restart the SQL*Net TCP/IP server. ORA-06136 NETTCP: error during connection handshake Cause: Network I/O error during communication with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06137 NETTCP: error during connection handshake Cause: Network I/O error during communication with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support.

ORA-04100 to ORA-07499

6-11

ORA-06138 NETTCP: error during connection handshake Cause: Network I/O error when communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06140 NETTCP: no such user Cause: A proxy login connection attempt failed because the client username has no host equivalent. Action: Try again with a user who has a host counterpart. ORA-06141 NETTCP: No privileges for user Cause: A proxy login connection attempt failed because the SQL*Net TCP/IP server did not have sufficient privileges to access the proxy account. Action: change account protection; change server privileges. ORA-06142 NETTCP: error getting user information Cause: A proxy login connection attempt failed because the SQL*Net TCP/IP server could not access the proxy account. See the SQL*Net TCP/IP server log file for more details. Action: Contact Oracle Customer Support. ORA-06143 NETTCP: maximum connections exceeded Cause: The connection failed because the maximum concurrent connections supported by the SQL*Net TCP/IP server on the host has already been reached. Action: Wait a moment and try again. ORA-06144 NETTCP: SID (database) not available Cause: The database administrator on the host changed the SID offline. Action: Wait until you are back online. ORA-06145 NETTCP: cannot start ORASRV: images not installed Cause: The SQL*Net TCP/IP host server could not start the Oracle server process because the Oracle protected images were not installed. Action: Install the images.

6-12

message error

ORA-06200 TWOTASK: connection failed, failed to create mailbox ORA-06201 TWOTASK: connection failed, failed to attach to mailbox ORA-06202 TWOTASK: connection failed, failed to spawn process ORASRV ORA-06203 TWOTASK: connection failed , handshake failed ORA-06204 TWOTASK: connection failed, cannot reach ORASRV2.COM ORA-06205 TWOTASK: connection failed, cannot create logical name ORA-06206 TWOTASK: failed to receive message ORA-06207 TWOTASK : message sending failed ORA-06208 TWOTASK: invalid login (connection) string ORA-06209 TWOTASK: connection failed, mailbox already exists ORA-06210 TWOTASK: connection failed, ORASRV closed unexpectedly ORA-06211 TWOTASK: connection failed , standby timeout ORASRV ORA-06212 TWOTASK: connection failed, logical name table full ORA-06213 TWOTASK: connection failed ORA-06214 TWOTASK: connection failed, insufficient quotas to create ORASRV ORA-06215 TWOTASK: connection failed ão , image p Protected ORASRV not installed ORA-06216 TWOTASK: connection failed, unable to find ORASRV image file ORA-06250 NETNTT: unable to allocate as send and receive buffers Cause: dual-task driver cannot allocate data buffers. Action: There is not enough memory to run your program. Kill other processes to free up memory. ORA-06251 NETNTT: cannot translate address file name Cause: The ORACLE_HOME environment variable is not set. Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. ORA-06252 NETNTT: Unable to open address file Cause: The NTT dual task driver was unable to open a file containing address information. Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. Make sure that the instance you are trying to connect to actually works. ORA-06253 NETNTT: Unable to read address file arguments Cause: The NTT dual-task driver was unable to read routing information from its routing file.

ORA-04100 to ORA-07499

6-13

Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. Make sure that the instance you are trying to connect to actually works. ORA-06254 NETNTT: Unable to share connection to hub Cause: The NTT dual task driver was unable to share a connection to the hub. Action: Make sure the ORACLE_HOME environment variable is set and exported correctly. Make sure that the instance you are trying to connect to actually works. ORA-06255 NETNTT: cannot read pid from remote process Cause: An error occurred while reading the NTT communication link. Action: Contact Oracle Customer Support. ORA-06256 NETNTT: remote fork failed Cause: The Oracle listener process in the cube was unable to fork a shadow process. Action: The instance you are trying to connect to probably does not have enough memory to run another shadow process. Have someone else sign out or connect to a different instance. ORA-06257 NETNTT: unable to send command line to shadow process Cause: An error occurred while writing the NTT communication link. Action: Contact Oracle Customer Support. ORA-06258 NETNTT: Failed to allocate context area Cause: The dual task driver was unable to allocate data buffers. Action: There is not enough memory to run your program. Kill other processes to free up memory. ORA-06259 NETNTT: cannot read from remote process Cause: An error occurred while reading the NTT communication link. Action: Contact Oracle Customer Support. ORA-06260 NETNTT: cannot write to remote process Cause: An error occurred while writing the NTT communication link. Action: Contact Oracle Customer Support.

6-14

message error

ORA-06261 NETNTT: nrange() failed Cause: The call to NRANGE() failed while trying to establish a connection. Action: Contact Oracle Customer Support. ORA-06262 NETNTT: nfconn() failed Cause: The call to NFCONN() failed while trying to establish a connection. Action: Contact Oracle Customer Support. ORA-06263 NETNTT: out of memory on pi_connect Cause: The two-task driver could not allocate data buffers. Action: There is not enough memory to run your program. Kill other processes to free up memory. ORA-06264 NETNTT: data protocol error Cause: The NTT two-task handler received an unexpected message type. Action: Contact Oracle Customer Support. ORA-06265 NETNTT: interrupt protocol error Cause: The NTT dual task driver received an unexpected message type. Action: Contact Oracle Customer Support. ORA-06266 NETNTT: incorrect write length Cause: The NTT two-task driver failed an internal consistency check. Action: Contact Oracle Customer Support. ORA-06267 NETNTT: unhealthy Cause: The NTT two-task driver failed an internal consistency check. Action: Contact Oracle Customer Support. ORA-06268 NETNTT: Could not read /etc/oratab Cause: The dual-task NTT driver could not read the configuration information from /etc/oratab. Action: Make sure /etc/oratab exists and is readable. This error can occur if the file is in the wrong format. It can also happen if the controller runs out of memory.

ORA-04100 to ORA-07499

6-15

ORA-06300 IPA: disconnect error Cause: A fatal error occurred while disconnecting from the server. This is most likely due to inaccessible message queues. Action: If there is no message queue, restart the SQL*Net IPA servers using IPACTL. Otherwise, contact Oracle Customer Support. ORA-06301 IPA: Unable to assign controller context. Cause: The memory pool is exhausted. Action: Check the circumstances and try to allocate less memory in your program or adjust the parameters in your INIT.ORA file and try again. ORA-06302 IPA: Unable to connect to remote host Cause: One of the following: ■

There is no ADI server defined to mirror a connection to the specified host.

■

The remote host is not known to the local system.

■

Oracle kernel on remote host is not built with IPA driver

Action: Check the above causes sequentially and eliminate the actual cause found. ORA-06303 IPA: send message error Cause: The SQL*Net IPA driver could not write the message to the message queue. Action: Make sure the message queue exists and is accessible. If necessary, run IPACTL again. ORA-06304 IPA: receive message error Cause: The SQL*Net IPA driver was unable to read a message from the message queue. Action: Make sure the message queue exists and is accessible. If necessary, run IPACTL again. ORA-06305 IPA: Illegal Message Type Cause: Communication between the user and Oracle is out of sync. This message should not normally be issued. Action: Contact Oracle Customer Support.

6-16

message error

ORA-06306 IPA: write message size error Cause: The IPA driver attempted to write a message to the queue that was too large for the queue. Action: Contact Oracle Customer Support. ORA-06307 IPA: Unable to reestablish connection Cause: A fatal error occurred while reestablishing the connection. Action: Contact Oracle Customer Support. ORA-06308 IPA: No more connections available Cause: You have exhausted all your connections. Action: Try again when some of the current users have logged out. ORA-06309 IPA: No message queues available Cause: SQL*Net IPA servers failed to start. Action: Run IPACTL. ORA-06310 IPA: Environment variables not set Cause: Environment variables not set correctly. Action: Check and correct. ORA-06311 IPA: Maximum number of servers reached Cause: Maximum number of servers reached. Action: Shut down and reboot with a higher maximum number of servers. Note that database links consume one server per link. Be sure to start enough servers to support database links. ORA-06312 IPA: Wrong output service name provided. Cause: An incorrect output service name was provided. Action: Check and correct the service name. ORA-06313 IPA: Shared memory initialization failed Cause: Shared memory was not configured correctly. Action: Contact your system administrator. ORA-06314 IPA: Error configuring event Cause: Fatal interprocess communication error. Action: Contact your system administrator.

ORA-04100 to ORA-07499

6-17

ORA-06315 IPA: invalid connection string Cause: The connection string is in the wrong format. Action: Check and correct. ORA-06316 IPA: Invalid Database SID Cause: The SID is unknown on the remote side. Action: The database does not exist, is not running, or there are no servers reserved for this SID. ORA-06317 IPA: Local maximum number of users exceeded Cause: The maximum number of concurrent SQL*Net IPA users on the local side was exceeded. Action: Wait until free connections are available. If the problem persists, contact your system administrator. ORA-06318 IPA: Local maximum number of connections exceeded Cause: The maximum number of concurrent connections that SQL*Net IPA can handle to different hosts on the local side has been exceeded. Action: Wait until free connections are available. If the problem persists, contact your system administrator. ORA-06319 IPA: Maximum number of remote users exceeded Cause: The maximum number of concurrent SQL*Net IPA users on the remote side was exceeded. Action: Wait until free connections are available. If the problem persists, contact your system administrator. ORA-06320 IPA: Maximum number of remote connections exceeded Cause: The maximum number of concurrent connections that SQL*Net IPA can handle from different hosts on the remote side has been exceeded. Action: Wait until free connections are available. If the problem persists, contact your system administrator. ORA-06321 IPA: Unable to reach remote side Cause: A timeout occurred while trying to connect to a remote server; the most likely reason is that the remote SQL*Net IPA software is not running. An alternative reason could be that the remote launcher service name is incorrect.

6-18

message error

Action: Check and start the remote SQL*Net software. Verify that you started with the correct service names provided. ORA-06322 IPA: shared memory fatal error Cause: An internal error occurred in the handling of shared memory. Action: Contact Oracle Customer Support. ORA-06323 IPA: Cause Event Error Cause: Fatal interprocess communication error. Action: Contact your system administrator. ORA-06400 NETCMN: No default host string specified Cause: No default host string was specified in the configuration and no explicit connection string was specified by the user. Action: Reconfigure the system by specifying a default connection string or use an explicit connection string. ORA-06401 NETCMN: invalid handler designator Cause: The login (connection) string contains an invalid handler designator. Action: Correct the string and resubmit. ORA-06402 NETCMN: error receiving interrupt message Cause: An error occurred while trying to read an interrupt message. Action: Contact Oracle Customer Support. ORA-06403 Cannot allocate memory. Cause: The system cannot allocate the required virtual memory. Action: Configure more memory, reduce the load, or try again. ORA-06404 NETCMN: Invalid login (connection) string Cause: Syntax error in the login string. Action: Correct the string and resubmit. ORA-06405 NETCMN: reset protocol error Cause: Unable to reset interrupt state. Action: Contact Oracle Customer Support.

ORA-04100 to ORA-07499

6-19

ORA-06406 NETCMN: Failed to send interrupt message Cause: An error occurred while trying to send an interrupt message. Action: Contact Oracle Customer Support. ORA-06407 NETCMN: Unable to configure interrupt handling environment Cause: An error occurred while trying to configure asynchronous handlers for incoming and out-of-band interrupt messages. Action: Contact Oracle Customer Support. ORA-06408 NETCMN: Incorrect message format Cause: The partner message contains an invalid header. Action: Contact Oracle Customer Support. ORA-06413 Connection not open. Cause: The connection could not be established. Action: Use diagnostic procedures to determine the exact problem. ORA-06416 NETCMN: test failed Cause: An error occurred while testing the I/O status of the network connection. Action: Contact Oracle Customer Support. ORA-06419 NETCMN: Server cannot start Oracle Cause: The remote server could not start an Oracle process on behalf of the client. Action: Make sure the permissions on the remote Oracle program are set correctly. Contact your system administrator. ORA-06420 NETCMN: SID lookup failed Cause: From remote host server: The SID of the database, specified in the login (connection) string, was not recognized. Action: Add the appropriate SID entry to the CONFIG.ORA or ORATAB file on the remote host (remote server might need to be rebooted). ORA-06421 NETCMN: An error was detected reading data. Cause: An error was encountered during the CRC or checksum recalculation. Action: Possible hardware failure of the communication nodes. Contact your system administrator immediately.

6-20

message error

ORA-06422 NETCMN: Failed to send data Cause: Cannot transmit data to the remote host. Action: Try to reconnect to the remote host and contact your system administrator. ORA-06423 NETCMN: Error receiving data Cause: Cannot receive data from the remote host. Action: Try to reconnect to the remote host and contact your system administrator. ORA-06430 Message: Stamps do not match Cause: A function was called with an invalid argument. Action: Contact Oracle Customer Support. ORA-06431 Message: invalid block number Cause: The file block number is outside the file range. The additional information returns the block number. Action: Check that the block number is correct. Run DBFSIZE and check if the block number is in this range. Contact Oracle Customer Support. ORA-06432 Message: Buffer Misaligned Cause: The I/O buffer was misaligned at a 2K boundary. Action: Contact Oracle Customer Support. ORA-06433 message: LSEEK error, could not get requested block. Explanation: The additional information returns the block number. Action: Look for the additional information returned in the operating system reference manual. Check that the block number is correct. ORA-06434 ssaio: read error, could not read requested block from database file. Explanation: The read system call returned an error. Action: The additional information indicates the block number. Look for the additional information returned in the operating system manual. ORA-06435 ssaio: write error, could not write the requested block to the database file. Explanation: The recording system call returned an error. Action: The additional information indicates the block number. Look for the additional information returned in the operating system manual.

ORA-04100 to ORA-07499

6-21

ORA-06436 Message: Asynchronous I/O failed due to incorrect parameters. Explanation: The asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look for the additional information returned in the operating system manual. ORA-06437 Message: asynchronous write could not write to the database file. Explanation: The asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look for the additional information returned in the operating system manual. ORA-06438 ssaio: asynchronous read could not read from database file. Explanation: The asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look for the additional information returned in the operating system manual. ORA-06439 ssaio: asynchronous write returned incorrect number of bytes Cause: This write call may have been truncated. The additional information returns the block number and the number of bytes. Action: Verify that the block number and the number of bytes written are correct. ORA-06440 Message: asynchronous read returned incorrect number of bytes Cause: This read call may have been truncated. The additional information returns the block number and the number of bytes. Action: Verify that the block number and the number of bytes read are correct. ORA-06441 ssvwatev: wrong parameter passed to function call Cause: Invalid Oracle process ID, timeout, or event ID. Action – Additional information indicates the process ID, time, and event ID. ORA-06442 ssvwatev: Error with unexpected error number. Cause: There may be some system problems on your system; check the error logs. Action: The additional information indicates the error number. Look for the additional information returned in the operating system manual. ORA-06443 ssvpstev: An incorrect parameter was passed to the function call. Cause: An invalid event ID was passed to this routine.

6-22

message error

Action: The additional information indicates the ID of the event. ORA-06444 ssvpstev: Error with unexpected error number. Cause: There may be some system problems on your system; check the error logs. Action: The additional information indicates the error number. Look for the additional information returned in the operating system manual. ORA-06445 ssvpstevrg: Incorrect parameters passed to function call. Cause: There is no invalid event ID or low and high event ID. Action: The additional information indicates the error number. It also contains the event ID, lower bound, and upper bound. ORA-06446 ssvpstevrg: Error with unexpected error number. Cause: There may be some system problems on your system; check the error logs. Action: The additional information indicates the error number. Look for the additional information returned in the operating system manual. ORA-06447 ssvpstp: An incorrect parameter was passed to the function call. Cause: An invalid Oracle process ID was passed to this routine. Action: The additional information indicates the ID of the process. ORA-06448 ssvpstp: failed with unexpected error number. Cause: There may be some system problems on your system; check the error logs. Action: The additional information indicates the error number. Look for the additional information returned in the operating system manual. ORA-06449 List IO or sysvendor is not installed. Cause: Oracle tries to use the SYSVENDOR interface (INIT.ORA parameter USE_SYSVENDOR=TRUE), but the UNIX kernel does not have the Oracle SYSVENDOR interface bound. Action: Set USE_SYSVENDOR=FALSE in INIT.ORA if you do not want to use this interface, or bind the UNIX kernel to this interface so that Oracle can use it. ORA-06500 PL/SQL: storage error Cause: This is a rare internal error message. The memory has been exhausted or damaged. Action: Contact Oracle Customer Support.

ORA-04100 to ORA-07499

6-23

ORA-06501 PL/SQL: program error Cause: This is an internal error message. An error was detected in a PL/SQL program. Action: Contact Oracle Customer Support. ORA-06502 PL/SQL: string numeric or value error Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if you try to assign the value NULL to a variable declared NOT NULL or if you try to assign an integer greater than 99 to a variable declared NUMBER(2). Action: Change the data, how it is handled, or how it is declared so that the values do not violate the constraints. ORA-06503 PL/SQL: function returned with no value Cause: A PL/SQL function call completed, but no RETURN statement was executed. Action: Rewrite the PL/SQL function, making sure that it always returns a value of the proper type. ORA-06504 PL/SQL: Return types of query or result set variables do not match Cause: The number and/or types of columns in a query do not match the declared return type of a result set variable results or the declared types of two result set variables do not match. Action: Change the statement or statement of the program. Check which query the variable actually refers to at runtime. ORA-06505 PL/SQL: Variable requires more than 32767 bytes of contiguous memory Cause: A PL/SQL variable was declared with a constraint that required more than 32767 bytes of memory. PL/SQL currently does not support contiguous memory allocations greater than 32,767 bytes. User Response: Relax the constraint on the declaration of variables. If this is not possible, try changing the national database or character set to one that requires less memory for the same constraint. Note: Changing the character set will affect the execution of all PL/SQL code.

6-24

message error

ORA-06508 PL/SQL: Cannot find called program unit Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or modified in an incompatible way or compiled with errors. Action: Check that all referenced programs, including their package bodies, exist and are supported. ORA-06509 PL/SQL: ICD vector is missing for this package Cause: This indicates a version conflict between some package distributed with an Oracle product and the product executable. Action: Contact Oracle Customer Support. ORA-06510 PL/SQL: Unhandled User Defined Exception Cause: The PL/SQL code generated a User Defined Exception, but it was not handled. Action: Fix the problem that is causing the exception or write an exception handler for this condition. Or you may need to contact the application administrator or the database administrator. ORA-06511 PL/SQL: Cursor is already open Cause: An attempt was made to open a cursor that was already open. Action: First close the cursor before reopening. ORA-06512 at stringline string Cause: Trace message because the stack unrolled due to unhandled exceptions. Action: Fix the problem that is causing the exception or write an exception handler for this condition. Or you may need to contact the application administrator or the database administrator. ORA-06513 PL/SQL: PL/SQL table index is out of range of host language array Cause: An attempt is being made to copy a PL/SQL table into a host language array. But an index on the table is less than one or greater than the maximum size of the host language array. When copying PL/SQL tables into host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, and so on. assigned, the corresponding element in the host language array is set to null. Action: Increase the size of the host language array or reduce the size of the PL/SQL table. Also make sure you don't use index values less than 1.

ORA-04100 to ORA-07499

6-25

ORA-06514 PL/SQL: Server cannot handle remote call. Cause: The remote call has parameters that are cursor variables. This cannot be handled by stored procedures on your server. Action: Avoid using cursor variables as parameters to stored procedures on this server, or upgrade your server to a version that supports this. ORA-06515 PL/SQL: Unhandled exception string Cause: The PL/SQL code raised an exception, but it was not handled. The exception number is outside of Oracle's legal error range. Action: Fix the problem that is causing the exception or write an exception handler for this condition. Or you may need to contact the application administrator or the database administrator. ORA-06516 PL/SQL: Probe packages do not exist or are invalid Cause: A probe operation, most likely an attempt to initialize the Oracle server for debugging PL/SQL, failed to complete because the probe packages were not loaded or are no longer valid. Action: The DBA should load the probe packages. This can be done by running the PBLOAD.SQL script provided with the RDBMS. ORA-06517 PL/SQL: poll error - string Cause: An error occurred while passing a poll operation to the server for execution. Action: Check the embedded error message entry. ORA-06518 PL/SQL: Probe version string does not match version string Cause: The current version of the probe does not match the version on the Oracle server. Action: Check the documentation to ensure that this degree of compatibility is supported. ORA-06519 Active unattended transaction detected and rolled back Cause: Before returning from a stand-alone PL/SQL block, all unattended transactions started within the block must complete (commit or roll back). Otherwise, the active stand-alone transaction is implicitly rolled back and this error is generated. Action: Ensure that before returning from an independent PL/SQL block, all active independent transactions are explicitly committed or rolled back.

6-26

message error

ORA-06520 PL/SQL: Error loading external library Cause: PL/SQL encountered an error while trying to dynamically load the external library. Action: Check the stacked error (if any) for more details. ORA-06521 PL/SQL: assignment function error Cause: PL/SQL encountered an error while trying to dynamically allocate the named function. Action: Check the stacked error (if any) for more details. String ORA-06522 Cause: ORA-06520 or ORA-06521 can accumulate this error with a system-specific error string. Action: This error string should provide the cause of the ORA-06520 or ORA-06521 errors ORA-06523 Maximum number of arguments exceeded Cause: There is an upper limit on the number of arguments that can be passed to the outer function. Action: See the port-specific documentation on how to calculate the upper limit. ORA-06524 Unsupported Option: string Cause: The specified option is an unsupported function for external procedures. User Response: Correct the syntax in the external specification. ORA-06525 Length mismatch for CHAR or RAW data Cause: The length specified in the length variable has an invalid value. This can happen if you requested that a raw PL/SQL INOUT, OUT, or RETURN variable be passed as RAW without the corresponding length variable. This error can also occur if there is a mismatch between the length value defined in the length variable and the length in ORLVSTR or ORLRAW. User Response: Correct the external procedure code and set the length variable correctly. ORA-06526 Cannot load PL/SQL library Cause: PL/SQL could not create an instance of the library referenced in the EXTERNAL syntax. This is a serious error and should not normally occur.

ORA-04100 to ORA-07499

6-27

Action: Report this issue to Oracle Customer Support. ORA-06527 External Procedure SQLLIB Error: string Cause: An SQLLIB error occurred while executing a Pro* external procedure. Action: The message text indicates the actual SQLLIB error that occurred. ORA-06528 Error executing PL/SQL Profiler Cause: An error occurred while executing a PL/SQL Profiler procedure. Action: Check the stacked errors for more details. ORA-06529 Version mismatch: PL/SQL Profiler Cause: The PL/SQL Profiler package (DBMSPB.SQL, PRVTPBP.PLB) does not match the version of the code on the server that implements the Profiler. Action: Run the PROFLOAD.SQL package in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages. ORA-06530 Uninitialized Composite Reference Cause: An object, LOB, or other composite was referenced as uninitialized lefthand. User Response: Initialize the composite with a suitable constructor or integer object assignment. ORA-06531 Collection reference not initialized Cause: An element or member function of a nested table or VARRAY (where an initialized collection is required) was referenced without initializing the collection. User Response : Initialize the collection with a suitable constructor or a full object mapping. ORA-06532 Subscript out of bounds Cause: A subscript was greater than the bound of a VARRAY or was not positive for a VARRAY or nested table. Action: Check the logic of the program and increase the VARRAY limit if necessary. ORA-06533 Subscript beyond count Cause: A subscript at the boundary was greater than the VARRAY count or too large for a nested table.

6-28

message error

Action: Check the logic of the program and explicitly extend if necessary. ORA-06534 cannot access serial scratch bundle string in the context of a trigger Cause: The program tried to access a serial scratch bundle in the context of a trigger. This access is currently not supported. Action: Check the logic of the program and remove any references to serialized reusable packages (references to procedures, functions, or variables) that might occur in the context of a trigger. ORA-06535 statement string in string is NULL or of length 0 Cause: The program attempted to use a dynamic statement string that was NULL or of length 0. Action: Check the logic of the program and ensure that the statement string dynamics has been initialized correctly. ORA-06536 IN binding variable bound to an OUT position Cause: The program attempted to bind an IN binding variable to an instruction that expected an OUT binding variable at that position. Action: Make sure that an OUT or IN OUT bind mode is specified for the bind argument. ORA-06537 OUT binding variable bound to an IN position Cause: The program attempted to bind an OUT binding variable to an instruction that expected an IN binding variable at that position. Action: Make sure that an IN or IN OUT bind mode is specified for the bind argument. The ORA-06538 statement violates the RESTRICT_REFERENCES pragma string Cause: The program attempted to execute a dynamic statement that does not meet the purity level specified (in the RESTRICT_REFERENCES pragma directive) for the module executing the statement. Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement. ORA-06539 Target of OPEN must be a query Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.

ORA-04100 to ORA-07499

6-29

Action: Ensure that the OPEN cursor operation is performed in a dynamic query statement. ORA-06540 PL/SQL: compile error Cause: A PL/SQL compile error occurred. However, the user will usually not see this error message. Instead, there will be PLS-nnnnn error messages attached. Action: Check the attached PLS-nnnnn error messages. ORA-06541 PL/SQL: Compile Error: Compilation stopped Cause: A PL/SQL compile error occurred and compilation stopped; but the compilation unit was written to the backing storage. However, unlike ORA-06545, the user will generally not see this error message. Instead, there will be PLS-nnnnn error messages attached. Action: Check the attached PLS-nnnnn error messages. ORA-06542 DDL statement is executed in illegal context Cause: DDL statement is executed dynamically in illegal PL/SQL context: ■

Dynamic OPEN cursor for a PL/SQL DDL

■

Bind the variables used in the USING clause for EXECUTE IMMEDIATE to DDL

■

Define the variables used in the INTO clause to IMMEDIATELY EXECUTE a DDL

Action: Use EXECUTE IMMEDIATE without the USING and INTO clauses to execute the DDL statement. ORA-06543 RETURNING clause must be used with INSERT, UPDATE, or DELETE statements Cause: EXECUTE IMMEDIATE with a RETURNING clause is used only to execute dynamic UPDATE, INSERT, or DELETE statements. Action: Use the RETURNING clause in EXECUTE IMMEDIATE only for INSERT, UPDATE, or DELETE statements. For other declarations, use the USING clause. ORA-06544 PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: Um PL/SQL internal an error occurred. Action: Report as error; the first argument is the internal error number.

6-30

message error

ORA-06545 PL/SQL: Compile Error: Compilation Aborted Cause: A PL/SQL compile error occurred and the compilation stopped completely without the compilation unit being written to the backing store. Unlike ORA-06541, the user will always see this error along with the accompanying PLS-nnnnn error messages. Action: Check the attached PLS-nnnnn error messages. ORA-06550 linestring, columnstring: string Cause: A PL/SQL compiler error occurred. The numbers given for row and column are the location in the PL/SQL block where the error occurred. Action: See the following PL/SQL messages for more information about the error. ORA-06551 PL/SQL: unhandled exception ORA-06552 PL/SQL: string ORA-06553 PLS-string: string ORA-06554 Package DBMS_STANDARD must be created before using PL/SQL Cause: DBMS-specific extensions to PL/SQL STANDARD are in the DBMS_STANDARD package. This package must be created before using PL/SQL. Action: Create the DBMS_STANDARD package. The source of this package stored in PL/SQL is provided with the distribution. ORA-06555 This name is currently reserved for use by the SYS user Cause: An attempt was made to create a package named STANDARD, DBMS_STANDARD, or DEBUG_IO. These are currently reserved for use by the SYS user. Action: Choose another name for your package. ORA-06556 Pipe is empty, unpack_message request cannot be serviced Cause: There are no more items in the pipeline. Action: Verify that the sender and recipient agree on the number and types of items placed in the pipeline. ORA-06557 Null values are not allowed for any parameter to pipe icds. Cause: Internal error in the DBMS_PIPE package. Action: Contact Oracle Customer Support.

ORA-04100 to ORA-07499

6-31

The ORA-06558 buffer in the dbms_pipe package is full. No more items are allowed. Cause: Pipe buffer size exceeded. Action: Inspect the program to analyze the rate of entry and exit of the pipe. You may need to remove items from the pipeline by running RECEIVE_MESSAGE or flush the entire pipeline by running PURGE on the pipeline. ORA-06559 Incorrect requested data type, string, actual data type is string Cause: The sender placed a different data type in the pipe than the one requested (DBMS_PIPE packet). The numbers are: ■

6 - number

■

9 - characters

■

12 - data

Action: Verify that the sender and recipient agree on the number and types of items placed in the pipeline. ORA-06560 pos, string, is negative or greater than buffer size, string Cause: Internal error in DBMS_PIPE package. Action: Contact Oracle Customer Support. ORA-06561 The supplied statement is not supported by the DBMS_SQL package Cause: An attempt was made to parse an unsupported statement using the PARSE procedure provided by the DBMS_SQL package. Action: Only statements beginning with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE, or =0). Unsupported GeoTIFF geometry definition ORA-13463 Cause: The key/label combination used to define the GeoImage geometry fingerprint is not supported. Action: Verify that the version of the GeoTIFF format is supported and that the format is valid. ORA-13464 conversion not supported Cause: The format specified for the conversion is not supported. In GeoTIFF, only a limited number of tag/key combinations are supported for conversion. Action: Verify that the version of the GeoTIFF format is supported and that conversion to the desired format is available. ORA-13499 string Cause: This is an internal error in the Spatial Cartridge. Action: Contact Oracle Customer Support.

ORA-12700 to ORA-19399

11-41

ORA-14000 Only one LOCAL clause can be specified Cause: The CREATE INDEX statement contained more than one LOCAL clause. Action: Specify the LOCAL option at most once. ORA-14001 LOCAL clause contradicts previously specified GLOBAL clause Cause: The CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause. Action: Specify either the LOCAL or the GLOBAL clause, but not both. ORA-14002 Only one GLOBAL clause can be specified Cause: The CREATE INDEX statement contained more than one GLOBAL clause. Action: Specify the GLOBAL option at most once. ORA-14003 GLOBAL clause contradicts previously specified LOCAL clause Cause: The CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause. Action: Specify either the GLOBAL or the LOCAL clause, but not both. ORA-14004 Missing PARTITION keyword Cause: The PARTITION keyword is missing. Action: Provide the missing keyword. ORA-14005 The RANGE keyword is missing Cause: The RANGE keyword is missing. Action: Provide the missing keyword. ORA-14006 Invalid partition name Cause: A form identifier partition name was expected, but is not present. Action: Enter an appropriate partition name. ORA-14007 Missing keyword LESS Cause: Missing keyword LESS. Action: Provide the missing keyword. ORA-14008 Missing keyword THAN Cause: Missing keyword THAN. Action: Provide the missing keyword.

11-42 Error messages

Cannot specify ORA-14009 partition boundary for a LOCAL index partition Cause: While parsing a CREATE INDEX statement to create a LOCAL partitioned index, the partition description of one of the partitions was found to contain the VALUES LESS THAN clause , which is illegal as LOCAL index inherits the partition boundaries of its base table. Action: Remove all VALUES LESS THAN clauses from the LOCAL index partition descriptions. ORA-14010 Cannot specify this physical attribute for an index partition Cause: An unexpected option was encountered while parsing the physical attributes of an index partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; TABLESPACE can only be specified for hash partitions. Action: Remove invalid options from the list of physical attributes of an index partition. ORA-14011 names assigned to resulting partitions must be different Cause: The partition names resulting from splitting an existing table or index partition are not different. Action: Rename the resulting partitions to ensure that their names are distinct and different from those of any other partitions in the table or index. ORA-14012 Resulting partition name conflicts with an existing partition Cause: The name of a partition resulting from splitting an existing table or index partition is identical to some other existing partition of that table or index. Action: Rename the resulting partitions to ensure that their names are distinct and different from those of any other partitions in the table or index. ORA-14013 duplicate partition name Cause: The name of a partition of a table or index being created is not unique. Action: Rename the partitions to ensure that their names are unique across all partitions of the table or index being created. ORA-14014 The maximum number of partition columns is 16 Cause: The number of columns in a partition column list has exceeded the legal limit of 16. Action: Modify the partition column list to consist of a maximum of 16 columns .

ORA-12700 to ORA-19399

11-43

ORA-14015 too many partition descriptions Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; the maximum number of partitions is 65535. Action: Reduce the number of partitions so that it does not exceed 65535. The ORA-14016 underlying table of a LOCAL partitioned index must be partitioned Cause: An attempt was made to create a LOCAL partitioned index on a nonpartitioned index that is illegal. You can only create GLOBAL indexes (partitioned or not) on a non-partitioned table. Action: Correct the declaration and enter it again. ORA-14017 Partition linked list contains too many elements Cause: The partition linked list contained more elements than the number of partition columns. User Response : Make sure that the number of items in the partitioned linked list is equal to the number of partition columns in the table or index. ORA-14018 Partition linked list contains too few elements Cause: The partition linked list contained fewer elements than the number of partition columns. User Response : Make sure that the number of items in the partitioned linked list is equal to the number of partition columns in the table or index. ORA-14019 The element bound to the partition must be one of the following: string, datetime, or range literal, number, or MAXVALUE Cause: The list bound to the partition contained an element of invalid type (that is, it is not a number, non-empty string, datetime or literal range, or MAXVALUE). Action: Make sure that all the elements of the list linked to the partition are of valid type. ORA-14020 Cannot specify this physical attribute for a table partition Cause: An unexpected option was encountered while parsing the physical attributes of a table partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; TABLESPACE can only be specified for hash partitions. Action: Remove the invalid options from the physical attribute list for a table partition.

11-44 Error messages

ORA-14021 MAXVALUE must be specified for all columns Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns. Action: Make sure that the VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns. ORA-14022 Creating LOCAL partitioned cluster indexes is not supported Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal. Action: Remove LOCAL along with the partition_descriptions, if any, from the CREATE INDEX statement. ORA-14023 The creation of GLOBAL partitioned cluster indexes is not supported. Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal. Action: Remove the PARTITION BY RANGE clause along with the partition_descriptions from the CREATE INDEX statement. ORA-14024 The number of partitions in the LOCAL index must be the same as the number of the underlying table. Cause: An attempt was made to create a LOCAL partitioned index with a different number of partitions than the underlying table. User Response: Correct the CREATE INDEX statement to specify a correct number of partitions. ORA-14025 Cannot specify PARTITION for a snapshot or snapshot record Cause: The PARTITION option was found while parsing a snapshot definition or snapshot record. Action: Make sure that the definition of a SNAPSHOT does not include invalid options. ORA-14026 PARTITION and CLUSTER clauses are mutually exclusive Cause: A table definition contained PARTITION and CLUSTER clauses, which is illegal. Action: Remove one of the conflicting clauses. ORA-14027 Only one PARTITION clause can be specified Cause: The CREATE TABLE statement contained more than one PARTITION clause.

ORA-12700 to ORA-19399

11-45

Action: Specify the PARTITION option at most once. ORA-14028 Missing AT keyword Cause: The AT keyword is missing. Action: Provide the missing keyword. ORA-14029 GLOBAL partitioned index must have a prefix Cause: The partition columns of a global partitioned index did not contain a prefix of the key columns of the index. Action: Make sure that the GLOBAL partitioned index being created has the prefix and retry the operation. ORA-14030 Missing partition column in CREATE TABLE statement Cause: The partition column specified in the CREATE TABLE statement is not one of the columns of the table being created. Action: Make sure that all the columns in the partition column list are columns of the table being created. ORA-14031 partition column cannot be of type LONG or LONG RAW Cause: The user-specified partition column was of type LONG or LONG RAW, which is illegal. Action: Make sure that no partition columns are of type LONG or LONG RAW. ORA-14032 The partition limit of the partition number string is too high Cause: The upper limit of the partition whose number (partitions are numbered starting with 1) shown in this message has not been grouped below that of the next partition, which is illegal. Action: Make sure that the upper limit of all partitions (except the last one) is lower than the next partition. ORA-14036 The partition limit value is too long for the column Cause: The length of the partition limit value is longer than the corresponding partition column. Action: Make sure that the lengths of the upper bound values do not exceed those of the corresponding partition columns.

11-46 Error messages

ORA-14037 The partition limit of partition "string" is too high Cause: The upper limit of the partition whose name (explicitly specified by the user) is shown in this message was not lower than the upper limit of the next partition, which is illegal. Action: Make sure that the upper limit of all partitions (except the last one) is lower than the next partition. ORA-14038 GLOBAL partitioned index must have a prefix Cause: An attempt was made to create a GLOBAL partitioned index without a prefix, which is illegal. Action: If you want an index without a prefix, it must be created as LOCAL; otherwise, correct the list of key columns and/or the partition to ensure that the index is prefixed. Then repeat the operation. ORA-14039 Partition columns must form a subset of key columns of a UNIQUE index Cause: An attempt was made to create a UNIQUE partitioned index whose partition columns do not form a subset of its key columns, which is illegal. Action: If you want to create an index whose partition columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key columns and/or the partition to ensure that the partition columns of the index form a subset of its key columns. Cannot specify partition limit ORA-14041 for the resulting partitions. Cause: While parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, it was discovered that the partition description of a resulting partition contains the VALUES LESS THAN clause, which is illegal. Action: Remove the VALUES LESS THAN clause from the descriptions of partitions that result from splitting an existing table or index partition. The ORA-14042 partition limit cannot be specified for a partition that is being moved, modified, or rebuilt. The partition being moved, modified, or rebuilt was found to contain the VALUES LESS THAN clause, which is illegal. Action: Remove the VALUES LESS THAN clause from the new attribute description of the partition that is being moved, modified, or rebuilt.

ORA-12700 to ORA-19399

11-47

ORA-14043 only one partition can be added Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to add. User Response : Make sure that the statement contains exactly one partition definition and does not contain commas. ORA-14044 only one partition can be moved Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to move. Action: Make sure that the statement exactly describes a partition to be moved and does not contain commas. ORA-14045 only one partition can be modified Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to modify. Action: Make sure that the declaration exactly describes a partition to be modified and that it does not contain commas. ORA-14046 a partition could be split into exactly two new partitions Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition should be split. User Response : Make sure that the statement describes exactly two partitions into which an existing partition will be divided. ORA-14047 ALTER TABLE|INDEX RENAME cannot be combined with other operations Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with another invalid operation. Action: Make sure that the RENAME operation is the only operation specified on the ALTER TABLE or ALTER INDEX statement. ORA-14048 Partition maintenance operation cannot be combined with other operations Cause: The ALTER TABLE or ALTER INDEX statement tried to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal. Action: Make sure that a partition maintenance operation is the only operation specified in an ALTER TABLE or ALTER INDEX statement; other operations

11-48 Error messages

Than those dealing with partitions, you can combine the standard attributes of partitioned tables/indexes or that specify that a table should be renamed (ALTER TABLE RENAME). ORA-14049 Invalid ALTER TABLE MODIFY PARTITION option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a range or partition of composite range. Action: Specify only the legal options. ORA-14050 Invalid ALTER INDEX MODIFY PARTITION option Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement. Action: Specify only the legal options. ORA-14051 Invalid ALTER SNAPSHOT option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER SNAPSHOT statement. Action: Specify only the legal options. ORA-14052 The partition extended table name syntax is not allowed in this context Cause: An attempt was made to use the partition extended table name syntax in an illegal context (that is, not in the FROM clause or INSERT statement, DELETE or UPDATE). Action: Avoid using the name of the partition extended table in contexts other than those mentioned above. ORA-14053 Illegal attempt to modify a string in a string statement Cause: Certain attributes of objects (eg tables) can be specified at creation time, but cannot be modified using the ALTER statement. Unfortunately, the user has specified one of these attributes. Action: Make sure that the ALTER statement specifies new values only for attributes that can be changed after an object is created. ORA-14054 invalid ALTER TABLE TRUNCATE PARTITION option Cause: The name of the partition to be truncated can be followed by DROP STORAGE or REUSE STORAGE.

ORA-12700 to ORA-19399

11-49

Action: Make sure that no options other than DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION. ORA-14055 REBUILD keyword in ALTER INDEX REBUILD must immediately follow index_name Cause: The ALTER INDEX statement contained the REBUILD keyword after some index attributes (for example, INITRANS). Action: Make sure the REBUILD keyword immediately follows the name of the index being changed. ORA-14056 Partition number string: sum of PCTUSED and PCTFREE cannot exceed 100 Cause: The sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) shown in this message exceeds 100. Be aware Note that if the PCTUSED and/or PCTFREE values for this partition were not explicitly specified, the default values for the partitioned table or index would be used. If the default values of PCTUSED and/or PCTFREE are not specified for the partitioned table or index, the system defaults are used. Action: Ensure that the sum of PCTUSED and PCTFREE for the partition does not exceed 100. ORA-14057 partition "string": The sum of PCTUSED and PCTFREE cannot exceed 100 Cause: The sum of PCTUSED and PCTFREE for a partition whose name ( explicitly specified by the user) displayed in this message exceeds 100. Note that if the PCTUSED and/or PCTFREE values for this partition are not explicitly specified, the default values for the partitioned table or index will be used. If the default values of PCTUSED and/or PCTFREE are not specified for the partitioned table or index, the system defaults are used. Action: Ensure that the sum of PCTUSED and PCTFREE for the partition does not exceed 100. ORA-14058 partition number string: INITRANS value must be less than MAXTRANS value Cause: INITRANS value found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is shown in this message. Note that if the INITRANS and/or MAXTRANS values for this partition are not explicitly specified, the default values for the partitioned table or index will be used. If, in turn, standard INITRANS and/or

11-50 Error messages

No MAXTRANS values were specified for the partitioned table or index, system defaults would be used. Action: Ensure that the INITRANS value (specified either explicitly or derived from the default value for the partitioned table or index) is not greater than MAXTRANS. ORA-14059 "String" partition: INITRANS value must be less than MAXTRANS value Cause: The INITRANS value was found to be greater than the MAXTRANS value for a partition whose name (explicitly specified by the user) is shows in this message. Note that if the INITRANS and/or MAXTRANS values for this partition are not explicitly specified, the default values for the partitioned table or index will be used. If the default INITRANS and/or MAXTRANS values are not specified for the partitioned table or index, the system defaults are used. Action: Ensure that the INITRANS value (specified either explicitly or derived from the default value for the partitioned table or index) is not greater than MAXTRANS. ORA-14060 Cannot change the data type or length of a table partitioning column Cause: The user issued an ALTER TABLE statement attempting to modify the data type and/or length of a column used to partition the named table in the ALTER TABLE statement, which is illegal. Action: Avoid changing the data type and/or length of the partition columns in the table. ORA-14061 Cannot change the data type or length of an index partitioning column Cause: The user issued an ALTER TABLE statement attempting to modify the data type and/or length of a column used to partition some defined index on the table named in the ALTER TABLE statement, which is illegal. Action: Avoid changing the data type or length of the partition columns of the index. ORA-14062 one or more table partitions reside in a read-only table space Cause: The user issued an ALTER TABLE statement trying to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase the length of an existing CHAR (or CHARACTER) or adds a

ORA-12700 to ORA-19399

11-51

user-specified patterned column for a table where one or more partitions reside in read-only table spaces, which is illegal. Action: Avoid performing the above operations on a partitioned table where one or more partitions reside in read-only table spaces. ORA-14063 Unusable index exists on primary/unique constraint key Cause: An attempt was made to add or enable a primary key/unique constraint on columns of a table where an index marked as unusable index exists. Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD. ORA-14064 Unusable partitioned index exists on primary/unique constraint key Cause: An attempt was made to add or enable a primary key/unique constraint on columns of a table where an index exists where one or more partitions are marked as Index unusable. Action: Drop the existing index or rebuild the unusable partitions using ALTER INDEX REBUILD PARTITION. ORA-14065 ALLOCATE STORAGE cannot be specified for a partitioned table Cause: The user-specified ALLOCATE STORAGE clause in the ALTER TABLE statement issued on a partitioned table is invalid. Action: Delete the illegal option. If you want to add storage to individual partitions, the ALLOCATE STORAGE clause can be specified with the ALTER TABLE MODIFY PARTITION statement. ORA-14066 Invalid option for a non-partitioned table Cause: An attempt was made to issue a CREATE TABLE or ALTER TABLE command on a non-partitioned table, but the command contains an option that is only valid for partitioned tables. These options are: ENABLE LINE MOTION and DISABLE LINE MOTION. Action: Remove illegal command options. ORA-14067 Duplicate specification of TABLESPACE_NUMBER Cause: The TABLESPACE_NUMBER clause was specified more than once for a table, index, or index partition. Action: Correct the code generator text of the CREATE INDEX statement sent to the slaves.

11-52 Error messages

ORA-14068 TABLESPACE and TABLESPACE_NUMBER cannot be specified at the same time Cause: The TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, index, or index partition. Action: Correct the code generator text of the CREATE INDEX statement sent to the slaves. ORA-14069 Invalid TABLESPACE_NUMBER value Cause: The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF. Action: Correct the code generator text of the CREATE INDEX statement sent to the slaves. ORA-14070 option can only be specified for partitioned indexes or with REBUILD Cause: The user issued an ALTER INDEX statement containing an option that is legal only for partitioned indexes or in conjunction with REBUILD against a non-partitioned index. These options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS and FREELIST GROUPS within the STORAGE clause. Action: Remove illegal options. ORA-14071 invalid option for an index used to apply a constraint Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL was selected or GLOBAL. specified for an index used to apply a constraint. Action: Choose one of the valid index options. Fixed table ORA-14072 cannot be truncated Cause: An attempt was made to truncate a fixed table that is illegal. Action: Make sure that the table being truncated is not a fixed table. ORA-14073 Cannot truncate Bootstrap table or cluster Cause: An attempt was made to truncate an invalid Bootstrap table or cluster. User Response : Make sure that the table (or cluster) to be truncated is not a bootable table (or cluster).

ORA-12700 to ORA-19399

11-53

ORA-14074 Partition boundary must be greater than last partition Cause: The partition boundary specified in the ALTER TABLE ADD PARTITION statement does not cluster larger than the last partition in the table, which is illegal. Action: Make sure that the limit of the partition to be added is greater than the limit of the last partition in the table. ORA-14075 Partition maintenance operations can only be performed on partitioned indexes. Cause: The index mentioned in the ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation pointless at best. Action: Make sure that the index mentioned in the ALTER INDEX statement that specifies a partition maintenance operation is actually partitioned. ORA-14076 DROP/SPLIT PARTITION cannot be applied to a LOCAL index partition Cause: An attempt was made to drop or split a partition from a LOCAL index that is illegal. Action: Make sure that the index mentioned in that statement is a GLOBAL partitioned index. ORA-14078 cannot drop the highest partition of a GLOBAL index Cause: An attempt was made to drop the highest partition of a GLOBAL index, which is illegal. User Response: Make sure that the partition specified in the ALTER INDEX DROP PARTITION statement is not the highest partition in the index. ORA-14079 invalid option for partition marked index unusable Cause: The ALTER INDEX MODIFY PARTITION statement on an index partition marked index unusable contained STORAGE and/or DEALLOCATE SPACE clauses that are illegal. Action: Make sure that only valid options are specified. The ORA-14080 partition cannot be partitioned along the specified upper bound. Cause: An attempt was made to split a partition along a boundary that clusters above the partition to be split or below the partition immediately before the partition to be split.

11-54 Error messages

Action: Ensure that the boundary along which a partition will be split is less than the partition to be split and larger than the partition immediately before the partition to be split. ORA-14081 New partition name must be different from old partition name Cause: The user entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of the partition being renamed. Action: Make sure the name of the new partition is different from the name of any existing partition (including the one being renamed) for a given table or index. ORA-14082 new partition name must be different from any other partition in the object Cause: The user entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of some existing partition in the object. Action: Make sure the name of the new partition is different from the name of any existing partition (including the one being renamed) for a given table or index. ORA-14083 cannot drop the only partition of a partitioned table Cause: A drop partition command is executed when there is only one partition in the table. Action: Make sure there is at least one partition. Drop the table to remove all partitions. ORA-14084 can specify TABLESPACE DEFAULT for only a LOCAL index Cause: An attempt was made to specify TABLESPACE DEFAULT for an object that is not a LOCAL index, which is illegal. User Response: Rewrite the statement without the TABLESPACE DEFAULT clause. ORA-14085 partitioned table cannot have a column with data type LONG Cause: An attempt was made to create a partitioned table with a data type LONG or an attempt was made to add a column of data type LONG to a partitioned table. Action: LONG data types are not supported with partitioned tables. Create a table without a LONG column or change the table to non-partitioned. If you add a column, don't use the LONG data type. If you are modifying the attributes of a column to change the data type to LONG, it must be a non-partitioned table.

ORA-12700 to ORA-19399

11-55

ORA-14086 A partitioned index cannot be rebuilt as a whole Cause: An attempt was made to rebuild a partitioned index using the ALTER INDEX REBUILD statement, which is illegal. Action: Rebuild the index one partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and rebuild the entire index. ORA-14094 invalid ALTER TABLE EXCHANGE PARTITION option Cause: The name of the table to be EXCHANGED must be followed by [{INCLUDING|EXCLUDING} INDICES][{NO} VALIDATION]. User Response: Make sure that no option other than INCLUDED INDEXES or EXCLUDED INDEXES is specified with ALTER TABLE EXCHANGE PARTITION. ORA-14095 ALTER TABLE EXCHANGE requires a non-partitioned and non-clustered table. Cause: The table in the EXCHANGE operation is clustered or split. Action: Make sure that the table with which the partition is swapped is not split or clustered. ORA-14096 Tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns. Cause: Two tables specified in EXCHANGE have a different number of columns. Action: Make sure that the two tables have the same number of columns with the same type and size. ORA-14097 Column size or type mismatch in ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in ALTER TABLE EXCHANGE PARTITION are of different type or size. Action: Make sure that the two tables have the same number of columns with the same type and size. ORA-14098 index mismatch for tables in ALTER TABLE EXCHANGE PARTITION Cause: The two tables specified in EXCHANGE have indexes that are not equivalent.

11-56 Error messages

Action: Make sure that the indexes on both tables have indexes that follow this rule. For every nonpartitioned index on the nonpartitioned table, there must be an identical LOCAL index on the partitioned table, and vice versa. For identical, the position, type, and size of the column must be the same. ORA-14099 all rows in the table do not qualify for the specified partition Cause: There is at least one row in the non-partitioned table that does not qualify for the partition specified in ALTER TABLE EXCHANGE PARTITION. Action: Make sure that all rows in the segment qualify for partitioning. Perform the alter table operation with the DO NOT CHECK option. Run ANALYZE table VALIDATE on that partition to find the invalid rows and remove them. ORA-14100 extended partition table name cannot reference a remote object Cause: An attempt was made to use the partition extended table name syntax together with the remote object name, which is illegal. Action: Correct the declaration and enter it again. ORA-14101 partition extended table name cannot reference a synonym Cause: An attempt was made to use the partition extended table name syntax together with the synonym name, which is illegal. Action: Correct the declaration and enter it again. ORA-14102 only one LOGGING or NOLOGGING clause can be specified Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified. Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement. ORA-14103 LOGGING/NOLOGGING cannot be combined with RECOVERABLE/IRRECOVERABLE Cause: A statement contained [NO]LOGGING and [UN]RECOVERABLE clauses which are not allowed. Action: remove one of the offending clauses. [UN]RECOVERABLE is deprecated in V8 and will be deprecated in V9. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the RECORD option.

ORA-12700 to ORA-19399

11-57

ORA-14104 Cannot specify RECOVERABLE/IRRECOVERABLE for partitioned tables/indexes Cause: The CREATE TABLE/INDEX statement used to create a partitioned table/index contained a RECOVERABLE or UNRECOVERABLE clause which is illegal. Action: remove the offending clause. [UN]RECOVERABLE is deprecated in V8 and will be deprecated in V9. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the RECORD option. ORA-14105 RECOVERABLE/IRRECOVERABLE cannot be specified in this context Cause: The RECOVERABLE/IRRECOVERABLE clause is not allowed in this context. Action: remove the offending clause. RECOVERABLE/UNRECOVERABLE can only be specified in the CREATE TABLE/INDEX statement that describes a non-partitioned table or index and in the ALTER INDEX REBUILD statement. [UN]RECOVERABLE is deprecated in V8 and will be deprecated in V9. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the RECORD option. ORA-14106 Cannot specify LOGGING/NOLOGGING for a clustered table. Cause: An attempt was made to specify the LOGGING or NOLOGGING clause in the CREATE TABLE or ALTER TABLE statement related to a clustered table. Action: remove the offending clause. The ORA-14107 partition specification is required for a partitioned object Cause: The parameter providing the name of the partition is missing. This parameter is optional for non-partitioned objects, but required for partitioned objects. Action: Provide the missing parameter. ORA-14108 Invalid partition extended table name syntax Cause: The partition being accessed can only be specified by its name. An attempt was made to use a partition number or bind variable. User Response : Modify the statement to refer to a partition using its name.

11-58 Error messages

ORA-14109 Partition-extended object names can only be used with tables. Cause: An attempt was made to use a partition-extended object name with an object that is not a table. Action: Avoid using the extended partition name syntax with objects other than tables. ORA-14110 partition column cannot be of type ROWID Cause: The user-specified partition column was of type ROWID, which is illegal. User Response: Make sure that no partition columns are of type ROWID. ORA-14111 Creating GLOBAL partitioned indexes on clustered tables is not supported Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal. Action: Remove the PARTITION BY RANGE() clause together with (partition_list) to create a non-partitioned GLOBAL index on a clustered table. ORA-14112 Unable to specify RECOVERABLE/IRRECOVERABLE for a partition or subpartition Cause: The description of a partition or subpartition found in the CREATE TABLE/INDEX statement contained either the RECOVERABLE or UNRECOVERABLE clause which is illegal. Action: remove the offending clause. Use LOG or NOLOGGING instead. ORA-14113 partitioned table cannot have a column with LOB data type Cause: An attempt was made to create a partitioned table with a LOB data type or an attempt was made to add a column of LOB data type to a partitioned table. User Response: LOB data types are not supported with partitioned tables. Create a table with no LOB column or change the table to non-partitioned. If you add a column, don't use the LOB data type. If you are modifying the attributes of a column to change the data type to LOB, it must be a non-partitioned table. ORA-14114 partitioned table cannot have a column with object, REF, nested table, array data type Cause: An attempt was made to create a partitioned table with an object data type (object, REF, nested table, array) or An attempt was made to add a column object data type to a partitioned table.

ORA-12700 to ORA-19399

11-59

Action: Object data types are not supported with partitioned tables. Create a table with no object column or change the table to non-partitioned. If you add a column, don't use object data types. If you modify the attributes of a column to change the data type to object, it must be a non-partitioned table. ORA-14115 Partition number partition string partition boundary is too long Cause: The length of the linear key representation of an upper boundary of the partition whose number (partitions are numbered starting with 1) is displayed in This message has exceeded the legal limit (4K). Action: Change the representation of an upper partition boundary to bring its length within the legal limit. ORA-14116 partition partition boundary "string" is too long Cause: The length of the linear key representation of an upper boundary of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K ). Action: Change the representation of an upper partition boundary to bring its length within the legal limit. The ORA-14117 partition resides in an offline tablespace. Cause: The user attempted an operation that requires access to data on a partition that resides in a tablespace that went offline. Such operations include trying to drop a tablespace from a table that has indexes defined or is referenced by a constraint. Action: Bring the tablespace online before attempting the operation. ORA-14118 CHECK constraint mismatch on ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have the CHECK constraint defined. User Response : Make sure that neither table has the CHECK constraint defined on any column. ORA-14119 The specified partition boundary is too long Cause: The length of a linear key representation of an upper boundary of a table partition that is added to or along which an existing table or index partition is split exceeded the legal limit (4K). Action: Change the representation of an upper partition boundary to bring its length within the legal limit.

11-60 Error messages

ORA-14120 incompletely specified partition bound to a DATE column Cause: An attempt was made to use a date expression whose format does not fully specify (that is, day, month, and year (including century)) a date as a bound partition for a column of data. The format may have been specified explicitly (using the TO_DATE() function) or implicitly (NLS_DATE_FORMAT). Action: Ensure that the date format used in a partition linked to a DATE column supports the full specification of a date (that is, day, month, and year (including century)). If NLS_DATE_FORMAT does not support the full specification (i.e. including century) of the year, use TO_DATE() (eg TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the date ORA -14121 MODIFY DEFAULT ATTRIBUTES cannot be combined with other operations Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) that is illegal the only operation specified in the statement ALTER TABLE or ALTER INDEX; operations other than those dealing with partitions, default attributes of partitioned tables/indexes, or specifying that a table should be renamed (ALTER TABLE RENAME) can be combined with will ORA - 14122 only one REVERSE or NOREVERSE clause can be specified Cause: Both REVERSE and NOREVERSE were specified in the CREATE INDEX statement Action: Remove all REVERSE or NOREVERSE clauses except u ma, and return to em itir statement. ORA-1412 3 Duplicate NOREVERSE clause Cause: NOREVERSE was specified more than once in the ALTER INDEX statement. Action: Remove all but one of the NOREVERSE clauses and resubmit the statement. ORA-14124 Duplicate REVERSE clause Cause: REVERSE was specified more than once in the ALTER INDEX or CREATE INDEX statements. Action: Remove all but one of the REVERSE clauses and resubmit the statement.

ORA-12700 to ORA-19399

11-61

ORA-14125 Cannot specify REVERSE/NOREVERSE in this context Cause: The REVERSE/NOREVERSE clause is not allowed in this context. Action: remove the offending clause. REVERSE can be specified as an attribute of an index (not an individual partition if a partitioned index is created) in the CREATE INDEX and ALTER INDEX REBUILD statements. NOREVERSE can only be specified on the ALTER INDEX REBUILD statement. ORA-14126 only a parallel_clause can follow the resulting partition description(s) Cause: Descriptions of the partition(s) that result from splitting a table or index partition can be followed by a parallel_clause optional that applies to the entire declaration and that, in turn, cannot be followed by any other clause. User Response: Make sure that all partition attributes appear in the list in parentheses of the resulting partition descriptions in the ALTER TABLE/INDEX SPLIT PARTITION statement. ORA-14128 FOREIGN KEY constraint mismatch on ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints. Action: Make sure that both tables do not have FOREIGN KEY constraints defined on any column, or disable all FOREIGN KEY constraints on both tables. Then repeat the operation. ORA-14129 INCLUDING INDEXES must be specified because the tables have UNIQUE constraints enabled. Cause: The corresponding UNIQUE constraints on both tables are enabled and validated, but INCLUDING INDEXES is not specified in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command. Action: Disable matching of currently enabled UNIQUE constraints on both tables or ensure that the INCLUDING INDICES option is used. ORA-14130 UNIQUE constraint mismatch on ALTER TABLE EXCHANGE PARTITION Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no corresponding constraint (with respect to key columns) is defined on the other table, or a constraint mapping is defined in the other table, but differs from the one defined in the first table in being enabled and/or validated.

11-62 Error messages

Action: Make sure that, for each UNIQUE constraint defined in one of the tables named in the ALTER TABLE EXCHANGE PARTITION instruction, there is a corresponding UNIQUE constraint (vis-a-vis key-columns and being enabled and/or validated) defined elsewhere table. If UNIQUE constraints are enabled, UNIQUE constraints on the partitioned table must be enforced using local indexes. There is a UNIQUE constraint enabled by ORA-14131 on one of the tables. Cause: One of the tables mentioned in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled the UNIQUE constraints defined on it, preventing EXCHANGE from continuing. User Response: Disable the constraints defined on the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement. Table ORA-14132 cannot be used in EXCHANGE Cause: Attempted to issue ALTER TABLE EXCHANGE PARTITION | SUBPARTITION, but the non-partitioned table cannot be used in EXCHANGE because one or more of the following apply: ■

is a written table

■

contains ADT columns

■

contains columns of nested tables

■

contains REF columns

■

contains matrix columns

■

is a table organized by index

■

contains LOB columns

■

is a nested table

Action: Make sure that the non-partitioned table does not violate any of the above restrictions for ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command. ORA-14133 ALTER TABLE MOVE cannot be combined with other operations Cause: An attempt was made to combine an ALTER TABLE MOVE statement with another operation such as MODIFY. Action: Make sure that MOVE is the only operation specified in the ALTER TABLE statement.

ORA-12700 to ORA-19399

11-63

ORA-14134 indexes cannot use DESC and REVERSE Cause: An attempt was made to do a reverse index on some index columns marked with DESC. Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan backward indexes, allowing a normal reverse index to simulate a reverse index with columns marked DESC. ORA-14135 a LOB column cannot serve as a partition column Cause: An attempt was made to specify a column of type BLOB or CLOB as a partition or subpartition column. Action: Make sure that no partitioning or subpartitioning columns are of type BLOB or CLOB. ORA-14150 Missing SUBPARTITION keyword Cause: The SUBPARTITION keyword is missing. Action: Provide the missing parameter. ORA-14151 invalid table partitioning method Cause: An invalid partitioning method was specified in the CREATE TABLE statement. A table can be partitioned by RANGE, HASH, or range/composite hash (R+H). Action: Specify one of the valid partition methods. ORA-14152 Invalid number of partitions specified in PARTITIONS clause Cause: The number of partitions clause contained in the CREATE TABLE or CREATE INDEX statement specified a number of partitions outside the legal range (1-65535). Action: Specify a number between 1 and 65535 in the number of partitions clause. ORA-14153 Only one of the STORE IN or partition_description clauses can be specified Cause: The STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command. Action: remove one of the offending clauses.

11-64 Error messages

ORA-14154 only one of the STORE IN or subpartition_description clauses can be specified Cause: Both the STORE IN and subpartition_description clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION, or ALTER TABLE MERGE PARTITIONS command for a partition per composite range object. Action: remove one of the offending clauses. ORA-14155 The PARTITION or SUBPARTITION keyword is missing Cause: The PARTITION or SUBPARTITION keyword was expected, but none was supplied. Action: Provide the missing keyword. ORA-14156 invalid number of subpartitions specified in SUBPARTITIONS clause Cause: The Number of Subpartitions clause contained in the CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside the legal range (1-65535). Action: Specify a number between 1 and 65535 in the number of subpartitions clause. ORA-14157 invalid subpartition name Cause: A form identifier subpartition name was expected, but is not present. Action: Enter an appropriate subpartition name. ORA-14158 too many subpartition descriptions Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; the maximum number of subpartitions is 65535. Action: Reduce the number of subpartitions so that it does not exceed 65535. ORA-14159 duplicate subpartition name Cause: The name of a subpartition of a table or index being created is not unique. Action: Rename the subpartitions to ensure that their names are unique across all subpartitions of the table or index being created. ORA-14160 This physical attribute cannot be specified for a table subpartition Cause: An unexpected option was encountered while parsing the physical attributes of a table subpartition; TABLESPACE is the only valid option. Action: Remove invalid options.

ORA-12700 to ORA-19399

11-65

ORA-14161 subpartition number string: sum of PCTUSED and PCTFREE cannot exceed 100 Cause: The sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) shown in this message exceeds 100. Be aware Note that if the PCTUSED and/or PCTFREE values for this subpartition were not explicitly specified, the partition-level default values would be used. If, in turn, the default values of PCTUSED and/or PCTFREE are not specified at the partition level, the default values of the partitioned table or index will be used. If these values were not also explicitly specified, the system default values would be used. Action: Ensure that the sum of PCTUSED and PCTFREE for the subpartition does not exceed 100. ORA-14162 subpartition "string": The sum of PCTUSED and PCTFREE cannot exceed 100 Cause: The sum of PCTUSED and PCTFREE for a subpartition whose name ( explicitly specified by the user) displayed in this message exceeds 100. Note that if the PCTUSED and/or PCTFREE values for this subpartition are not explicitly specified, the partition-level default values will be used. If, in turn, the default values of PCTUSED and/or PCTFREE are not specified at the partition level, the default values of the partitioned table or index will be used. If these values were not also explicitly specified, the system default values would be used. Action: Ensure that the sum of PCTUSED and PCTFREE for the subpartition does not exceed 100. ORA-14163 subpartition number string: INITRANS value must be less than MAXTRANS value Cause: INITRANS value found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is shown in this message. Note that if the INITRANS and/or MAXTRANS values for this subpartition are not explicitly specified, the partition-level default values will be used. If, in turn, the default values for INITRANS and/or MAXTRANS are not specified at the partition level, the default values for the partitioned table or index will be used. If these values were not also explicitly specified, the system default values would be used. Action: Ensure that the INITRANS value (either explicitly specified or derived from the default value at the partition, table, or index level) is not greater than MAXTRANS.

11-66 Error messages

ORA-14164 subpartition "string": INITRANS value must be less than MAXTRANS value Cause: The INITRANS value was found to be greater than the MAXTRANS value for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if the INITRANS and/or MAXTRANS values for this subpartition are not explicitly specified, the partition-level default values will be used. If, in turn, the default values for INITRANS and/or MAXTRANS are not specified at the partition level, the default values for the partitioned table or index will be used. If these values were not also explicitly specified, the system default values would be used. Action: Ensure that the INITRANS value (either explicitly specified or derived from the default value at the partition, table, or index level) is not greater than MAXTRANS. ORA-14165 MODIFY DEFAULT ATTRIBUTES FOR PARTITION cannot be combined with other operations Cause: An ALTER TABLE or ALTER INDEX statement tried to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (for example, ADD PARTITION or PCTFREE) that is illegal. Action: Make sure that MODIFY DEFAULT ATTRIBUTES is the only operation specified on the ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, standard attributes of partitioned tables/indexes, or specifying that a table should be renamed (ALTER TABLE RENAME) can be combined at will. ORA-14166 Missing INTO keyword Cause: The INTO keyword is missing. Action: Provide the missing keyword. ORA-14167 Only one subpartition can be moved Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to move. Action: Make sure that the statement exactly describes a subpartition to be moved and does not contain commas. ORA-14168 only one subpartition can be modified Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to modify.

ORA-12700 to ORA-19399

11-67

Action: Make sure that the declaration exactly describes a subpartition to be modified and that it does not contain commas. ORA-14169 Invalid ALTER TABLE MODIFY SUBPARTITION Option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE was specified in an ALTER TABLE MODIFY SUBPARTITION statement. Action: Specify only the legal options. ORA-14170 cannot specify partition description clause in CREATE TABLE|INDEX Cause: The user requested the generation of default partition descriptions (possibly via PARTITIONS number_of_partitions) while specifying the partition description clause which is illegal. Action: remove one of the offending clauses. ORA-14171 cannot specify subpartition_description clause in CREATE|ALTER TABLE Cause: The user requested the generation of default subpartition descriptions (possibly via SUBPARTITIONS) while at the same time specifying the subpartition_description clause which is illegal. Action: remove one of the offending clauses. ORA-14172 invalid option ALTER TABLE EXCHANGE SUBPARTITION Cause: The name of the table to be EXCHANGED must be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]. Action: Make sure that no options other than INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION. ORA-14173 Invalid subpartition extended table name syntax Cause: The accessed subpartition can only be specified by name. An attempt was made to use a subpartition number or a binding variable. Action: Modify the declaration to refer to a subpartition using its name. ORA-14174 only a parallel_clause can follow COALESCE PARTITION|SUBPARTITION Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION can be followed by an optional parallel_clause. Cannot specify partition/subpartition attributes.

11-68 Error messages

Action: Make sure that partition/subpartition attributes are not specified. ORA-14175 a subpartition maintenance operation cannot be combined with other operations Cause: An ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (for example, MOVE SUBPARTITION) with some other operation (for example, MODIFY PARTITION ADD SUBPARTITION or PCTFREE ) which is illegal. Action: Make sure that a subpartition maintenance operation is the only operation specified in the ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indexes, or specifying that a table should be renamed (ALTER TABLE RENAME) can be combined at will. ORA-14176 This attribute cannot be specified for a partition hash Cause: An invalid option was encountered while parsing the physical attributes of a partition of a partitioned table using the HASH method. The TABLESPACE option is the only valid option for such partitions. Action: Remove invalid options. ORA-14183 TABLESPACE DEFAULT can only be specified for composite LOCAL index Cause: An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash partitioned LOCAL index object, which is illegal. Action: Replace TABLESPACE DEFAULT with TABLESPACE ts_name or remove it. ORA-14185 Incorrect physical attribute specified for this index partition Cause: An unexpected option was encountered while parsing the physical attributes of a local index partition; valid options for range-composite-range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING, and TABLESPACE; but TABLESPACE can only be specified for hash partitions. STORE IN() is also not allowed for all partitions except composite range partitions. Action: Remove the invalid options from the physical attribute list for an index partition.

ORA-12700 to ORA-19399

11-69

ORA-14186 The number of subpartitions in the LOCAL index must be the same as the number of the underlying table. Cause: An attempt was made to create a LOCAL partitioned index with a different number of subpartitions than the underlying table. User Response: Correct the CREATE INDEX statement to specify a correct number of subpartitions. The ORA-14187 partitioning method for the LOCAL index is not consistent with the underlying table. Cause: An attempt was made to create a LOCAL partitioned index that is not partitioned with the underlying table. The partition types are incompatible. User Response: Correct the CREATE INDEX statement to ensure that the partition method of the index is consistent with that of the base table. ORA-14188 Subpartition columns must form a subset of key columns of a UNIQUE index Cause: An attempt was made to create a UNIQUE partitioned index whose subpartition columns do not form a subset of its key columns, which is illegal. Action: If you want to create an index whose subpartition columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioned columns to ensure that the subpartitioned columns of the index form a subset of its key columns. ORA-14189 This physical attribute cannot be specified for an index subpartition Cause: An unexpected option was encountered while parsing the physical attributes of an index subpartition; TABLESPACE is the only valid option. Action: Remove invalid options. ORA-14190 only one ENABLE/DISABLE ROW MOVE clause can be specified Cause: One of the following: ■

ENABLE ROW MOVE was specified more than once.

■

ROW MOVE DISABLE was specified more than once.

■

11-70 Error messages

Both ENABLE ROW MOVE and DISABLE ROW MOVE to specify.

Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and issue the command again. ORA-14191 ALLOCATE STORAGE cannot be specified for composite range partitioned object Cause: The user specified the ALLOCATE STORAGE clause in the ALTER TABLE/ALTER INDEX statement issued against a range partitioned index that is not valid. Action: Delete the illegal option. If it is desired to add storage to individual partitions, the ALLOCATE STORAGE clause can be specified with the ALTER TABLE/INDEX MODIFY PARTITION statement. ORA-14192 cannot modify the physical index attributes of a hash index partition Cause: An attempt was made to modify one of the INITRANS/MAXTRANS/LOGGING/STORAGE clauses for an index partition of a hash partitioned index. Action: Remove the physical attributes that you are trying to modify. ORA-14193 Invalid ALTER INDEX MODIFY SUBPARTITION option Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement. Action: Specify only the legal options. ORA-14194 Only one subpartition can be rebuilt Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to rebuild. Action: Make sure that the declaration exactly describes a subpartition to be rebuilt and that it does not contain commas. ORA-14195 ALLOCATE STORAGE cannot be specified for partitioned object RANGE Cause: The user specified the ALLOCATE STORAGE clause in the ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index that is not valid. Action: Delete the illegal option. If it is desired to add storage to individual partitions, the ALLOCATE STORAGE clause can be specified with the ALTER TABLE/INDEX MODIFY PARTITION statement. ORA-14251 The specified subpartition does not exist Cause: The subpartition for the object was not found.

ORA-12700 to ORA-19399

11-71

Action: Try again with the correct subpartition name. ORA-14252 Invalid ALTER TABLE MODIFY PARTITION option for a hash partition Cause: ALLOCATE EXTENT and DEALLOCATE UNUSED can only be specified on ALTER TABLE MODIFY PARTITION for a hash partition. Action: Specify only the legal options. ORA-14253 table is not partitioned by composite range method Cause: Table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned using composite range method) composite range Action: Make sure the table is partitioned by the composite range method ORA-14254 cannot specify ALLOCATE STORAGE for a range-partitioned (composite) table Cause: User-specified ALLOCATE STORAGE clause in The ALTER TABLE statement issued on a range or composite range partitioned table that is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, the ALLOCATE STORAGE clause can be specified with the ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If you want to add storage to all subpartitions of a composite partition, the ALLOCATE STORAGE clause can be specified with ALTER TABLE MODIFY PARTITION. Table ORA-14255 is not partitioned by the range or composite range method. Cause: The ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for the table partitioned by the range or composite range method. User Response : Make sure the table is split by range or composite range method. ORA-14256 Invalid resulting partition descriptions Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description in partition descriptions in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement, but table in maintenance La operation is not a composite range-splittable, which is illegal.

11-72 Error messages

User Response : Remove the invalid clauses or make sure the table is partitioned using the composite range method. ORA-14257 cannot move a partition that is not a range or hash partition Cause: An attempt was made to move a partition that is not a range or hash partition, which is illegal. Action: Specify MOVE PARTITION only for a hash range or partition. ORA-14258 Invalid partition description Cause: User-specified STORE-IN clause, SUBPARTITIONS, and/or subpartition_description in the ALTER TABLE ADD PARTITION statement, but the table in the maintain operation is not a composite range/hash partitioned table , which is illegal. User Response : Either remove the invalid clauses or ensure that the table is partitioned using the range/composite hash method. Table ORA-14259 is not partitioned by Hash Cause: ALTER TABLE COALESCE PARTITION is only valid for tables partitioned by Hash. User Response : Specify a valid ALTER TABLE option for the table or ensure that the table is partitioned using the Hash method. ORA-14260 Incorrect physical attribute specified for this partition Cause: The user specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED and/or the [NO]LOGGING option for a hashed partition via the ALTER TABLE ADD/MOVE PARTITION command which is illegal . Only TABLESPACE can be specified. Action: Remove invalid options. Cannot specify ORA-14261 partition limit when adding this partition Hash Cause: The user specified the VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a hash partitioned table which is illegal. Action: Remove the VALUES LESS THAN clause from the description of the partition being added.

ORA-12700 to ORA-19399

11-73

ORA-14262 El nuevo nombre de la subpartición debe ser diferente del nombre de la subpartición anterior Causa: el usuario ingresó ALTER TABLE/INDEX RENAME SUBPARTITION especificando new_subpartition_name que es idéntico al nombre de la subpartición cuyo nombre se está cambiando. Acción: asegúrese de que el nombre de la nueva subpartición sea diferente del nombre de cualquier subpartición existente (incluida la que se está renombrando) de una tabla o índice determinado. ORA-14263 El nombre de la nueva subpartición debe ser diferente de cualquier otra subpartición del objeto Causa: el usuario ingresó ALTER TABLE/INDEX RENAME SUBPARTITION especificando new_subpartition_name que es idéntico al nombre de alguna subpartición existente del objeto. Acción: asegúrese de que el nombre de la nueva subpartición sea diferente del nombre de cualquier subpartición existente (incluida la que se está renombrando) de una tabla o índice determinado. La tabla ORA-14264 no está particionada por el método de rango compuesto. Causa: la tabla en la operación MODIFY DEFAULT ATTRIBUTES FOR PARTITION está particionada por un método que no es el método compuesto. Respuesta del usuario: asegúrese de que la tabla esté particionada mediante el método compuesto. ORA-14265 No se puede cambiar el tipo de datos o la longitud de una columna de subpartición de tabla Causa: El usuario emitió una declaración ALTER TABLE intentando modificar el tipo de datos y/o la longitud de una columna utilizada para subparticionar la tabla nombrada en la declaración ALTER TABLE, lo cual es ilegal . Acción: evite modificar el tipo de datos y/o la longitud de las columnas de subpartición de la tabla. ORA-14266 No se puede cambiar el tipo de datos o la longitud de una columna de subpartición de índice Causa: El usuario emitió una declaración ALTER TABLE intentando modificar el tipo de datos y/o la longitud de una columna utilizada para subparticionar algún índice definido en la tabla nombrada en la declaración ALTER TABLE, que es ilegal. Acción: Evite modificar el tipo de datos y/o la longitud de las columnas de subpartición del índice.

11-74 Error messages

ORA-14267 cannot specify PARALLEL clause when adding range partition (composite) Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for range partition or composite range which is illegal. User Response: Remove the PARALLEL clause. ORA-14268 subpartition 'string' of partition resides in an offline tablespace Cause: The user attempted an operation that requires access to data on a subpartition that resides in a tablespace that went offline. Such operations include trying to drop a tablespace from a table that has indexes defined or is referenced by a constraint. Action: Bring the tablespace online before attempting the operation. ORA-14269 cannot swap a partition that is not a range or hash partition Cause: The user tries to swap a partition with a non-partitioned table, but the specified partition is not a range or hash partition, which is illegal. Action: Specify the SWAP PARTITION only for a hash range or a partition. ORA-14270 table is not partitioned by Range or Hash method Cause: Table at ALTER TABLE MODIFY PARTITION {UNUSABLE LOCAL INDEXES | The REBUILD UNUSABLE LOCAL INDEXES} statement does not partition by range or hash method, which is illegal. User Response : Make sure the table is partitioned by range or hash method. Table ORA-14271 is not partitioned by Hash/Composite Range method Cause: Table in ALTER TABLE MODIFY SUBPARTITION {UNUSABLE LOCAL INDEXES | The REBUILD UNUSABLE LOCAL INDEXES} statement is not split by the range/hash composite method, which is illegal. User Response : Make sure the table is partitioned using the hash/composite range method. ORA-14272 only upper bound partition can be reused Cause: The user attempts to reuse a lower bound partition in the ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal. Action: Use the upper bound partition to be the resulting partition, or specify a new partition name. ORA-14273 Lower bound partition must be specified first Cause: The user specified the upper bound partition before the lower bound partition in the ALTER TABLE MERGE PARTITIONS statement, which is illegal.

ORA-12700 to ORA-19399

11-75

Action: Specify the lower bound partition and then the upper bound partition. ORA-14274 Merged partitions are not adjacent Cause: The user attempts to merge two partitions that are not adjacent to each other, which is illegal. Action: Specify two adjacent partitions. ORA-14275 cannot reuse lower bound partition as result partition Cause: The user attempts to reuse the lower bound partition of the partitions being merged, which is illegal. Action: Specify the resulting new partition name or reuse only the upper bound partition. ORA-14276 EXCHANGE SUBPARTITION requires a partitioned and non-clustered table. Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is clustered or partitioned. Action: Make sure that the table that the subpartition is swapped with is not partitioned or clustered. ORA-14277 Tables in EXCHANGE SUBPARTITION must have the same number of columns Cause: The two tables specified in ALTER TABLE EXCHANGE SUBPARTITION have different numbers of columns. Action: Make sure that the two tables have the same number of columns with the same type and size. ORA-14278 column size or type mismatch in EXCHANGE SUBPARTITION Cause: The corresponding columns in the tables specified in ALTER TABLE EXCHANGE SUBPARTITION are of different type or size. Action: Make sure that the two tables have the same number of columns with the same type and size. ORA-14279 index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION Cause: The two tables specified in ALTER TABLE EXCHANGE SUBPARTITION have indexes that are not equivalent. Action: Make sure that the indexes on both tables have indexes that follow this rule.

11-76 Error messages

be an identical LOCAL index on the partitioned table and vice versa. For identical, the position, type, and size of the column must be the same. ORA-14280 all rows in the table do not qualify for the specified subpartition Cause: There is at least one row in the non-partitioned table that does not qualify for the subpartition specified in ALTER TABLE EXCHANGE SUBPARTITION. Action: Make sure that all rows in the segment qualify for the subpartition. Perform the alter table operation with the DO NOT CHECK option. Run the ANALYZE VALIDATE table on that subpartition to find the invalid rows and remove them. ORA-14281 ALTER TABLE EXCHANGE SUBPARTITION CHECK constraint mismatch Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have the CHECK constraint defined on them. User Response : Make sure that neither table has the CHECK constraint defined on any column. ORA-14282 FOREIGN KEY constraint mismatch on ALTER TABLE EXCHANGE SUBPARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints. Action: Make sure that both tables do not have FOREIGN KEY constraints defined on any column, or disable all FOREIGN KEY constraints on both tables. Then repeat the operation. ORA-14283 UNIQUE constraints do not match on ALTER TABLE EXCHANGE SUBPARTITION Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no corresponding constraint (with respect to key columns) is defined on the another table, or a constraint mapping is defined in the other table, but differs from the one defined in the first table in terms of being enabled and/or validated. Action: Make sure that, for each UNIQUE constraint defined in one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION instruction, there is a corresponding UNIQUE constraint (vis-a-vis column-keys and being enabled and/or validated) defined elsewhere table. If UNIQUE constraints are enabled,

ORA-12700 to ORA-19399

11-77

UNIQUE constraints on the partitioned table must be enforced using local indexes. ORA-14284 One or more subpartitions of the table reside in a read-only tablespace Cause: The user issued the ALTER TABLE statement trying to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase the length of an existing CHAR (or CHAR) or adding a column with a user-specified pattern to a table where one or more subpartitions reside in read-only table spaces, which is illegal. Action: Avoid performing the above operations on a partitioned table, one or more subpartitions of which reside in read-only table spaces. ORA-14285 Unable to COALESCE a single partition from this partitioned table Cause: A COALESCE PARTITION command was issued when there is only one partition in the table that is invalid. Action: Make sure there is at least one partition. Drop the table to remove all partitions. ORA-14286 cannot COALESCE the only subpartition of this table partition Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition that is illegal. Action: Make sure there is at least one subpartition. Delete Partition to delete all subpartitions. ORA-14287 unable to REBUILD a partition of a composite range partitioned index Cause: An attempt was made to rebuild a partition of a composite range partitioned index that is illegal. Action: REBUILD the index partition, one subpartition at a time. ORA-14288 index is not partitioned by the composite range method Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or the ALTER INDEX REBUILD SUBPARTITION command must be partitioned by the composite method range Action: No action required ORA-14289 cannot unuse local index partition of composite range partitioned table Cause: An attempt was made to rebuild a partition of a composite range partitioned index that is illegal.

11-78 Error messages

Action: No action is required. ORA-14290 PRIMARY KEY constraint mismatch on ALTER TABLE EXCHANGE [SUB]PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints. Action: Make sure that both tables do not have PRIMARY KEY constraints defined on any column, or turn off all PRIMARY KEY constraints on both tables. Then repeat the operation. ORA-14291 cannot swap a composite partition with a non-partitioned table Cause: A composite partition can only be swapped with a partitioned table. Action: Make sure that the table being swapped is partitioned or that the partition being swapped is not composite. ORA-14292 The partitioning type of the table must match the subpartitioning type of the composite partition Cause: When exchanging a partitioned table with a composite partition, the partitioning type of the table must match the subpartitioning type of the partition composed. User Response : Make sure that the partitioning type of the partitioned table is the same as the subpartitioning type of the composite partition. ORA-14293 The number of partition columns does not match the number of subpartition columns Cause: When replacing a partitioned table with a composite partition, the number of partition columns in the table must match the number of subpartition columns in the table. composite partition. User Response : Make sure that the number of partitioning columns in the partitioned table is equal to the number of subpartitioning columns in the composite partition. ORA-14294 The number of partitions does not match the number of subpartitions Cause: When replacing a partitioned table with a composite partition, the number of partitions in the table must match the number of subpartitions in the composite partition.

ORA-12700 to ORA-19399

11-79

Action: Make sure that the number of partitions in the partitioned table is equal to the number of subpartitions in the composite partition. ORA-14295 Column type or size does not match between partition columns and subpartition columns Cause: When exchanging a partitioned table with a composite partition, the type and size of the partition columns in the table must match the type and size of the partition columns. the composite partition. User Response : Make sure that the type and size of the partition columns in the partitioned partition are the same as the type and size of the subpartition columns in the composite partition. ORA-14301 Table level attributes must be specified before partition level attributes Cause: While processing an ALTER TABLE ADD COLUMN statement, table level attributes of LOB columns were found after processing partition level attributes of columns LOB or during CREATE TABLE statement processing, table level attributes of LOB columns were found after processing partition descriptions. User Response : Modify the SQL statement to specify table level attributes before partition level attributes or partition descriptions; then repeat the instruction. ORA-14302 Only one list of aggregate LOB store clauses can be specified in one statement Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of aggregate LOB store clauses was parsed when another list of store clauses was found of LOBs added . There can be no more than one list of LOB store clauses added in a declaration; all added LOB store clauses must be combined into one list. Action: Combine all the aggregated LOB store clause lists into one list and repeat the statement. ORA-14303 Partitions or subpartitions are not in the correct order Cause: The descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently than the DDL order of partitions or subpartitions. Action: Reorder the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order and repeat the statement.

11-80 Error messages

The partition key entered ORA-14400 is beyond the highest legal partition key Cause: An attempt was made to insert a record with a concatenated partition key that is beyond the list linked to the last partition's concatenated partition. Action: Do not enter the key. Or add a partition capable of accepting the key. ORA-14401 The inserted partition key is outside the specified partition Cause: The concatenated partition key of an inserted record is outside the ranges of the two linked lists of concatenated partitions that delimit the partition named in the INSERT statement. Action: Do not enter the key or enter it in another partition. ORA-14402 partition key column update would cause partition change Cause: An UPDATE statement attempted to change the value of a partition key column, causing the row to be migrated to another partition. Action: Do not try to update a partition key column or make sure that the new partition key is within the range that contains the old partition key. ORA-14403 Cursor invalidation detected after getting partition lock DML Cause: Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. Action: No action is required. ORA-14404 partitioned table contains partitions in a different tablespace. Cause: An attempt was made to drop a tablespace that contains tables whose partitions are not fully contained in this tablespace. Action: Locate tables with partitions that span the table space being dropped and some other table spaces. Drop those tables or move the partitions to a different tablespace. ORA-14405 partitioned index contains partitions in a different table space Cause: An attempt was made to drop a table space that contains indexes whose partitions are not fully contained in this table space and are defined on tables that are fully contained in this space of tablespace table. Action: Look for partitioned indexes that span the table space being dropped and some other table spaces. Drop these indexes or move the index partitions to a different tablespace or find the tables on which the indexes are defined and drop (or move) them.

ORA-12700 to ORA-19399

11-81

ORA-14406 updated partition key is beyond the highest legal partition key Cause: An attempt was made to update a record with a concatenated partition key that is beyond the list linked to the last partition's concatenated partition. Action: Do not update the key. Or add a partition capable of accepting the key. ORA-14407 partitioned table contains subpartitions in a different table space Cause: An attempt was made to drop a table space that contains tables whose subpartitions are not entirely contained in this table space. Action: Locate tables with subpartitions that span the table space being dropped and some other table spaces. Drop these tables or move the subpartitions to a different tablespace. ORA-14408 partitioned index contains subpartitions in a different tablespace Cause: An attempt was made to drop a tablespace that contains indexes whose subpartitions are not fully contained in this tablespace and are defined on tables that are fully contained in this space of tablespace table. Action: Locate subpartitioned indexes that span the table space being dropped and some other table spaces. Drop these indexes or move the index partitions to a different tablespace or find the tables on which the indexes are defined and drop (or move) them. ORA-14409 Inserted partition key is outside specified subpartition Cause: The concatenated partition key of an inserted record is outside the ranges of the two linked lists of concatenated subpartitions that delimit the subpartition named in the INSERT statement. Action: Do not enter the key or enter it in another subpartition. ORA-14450 An attempt was made to access a transactional temporary table that was already in use Cause: An attempt was made to access a transactional temporary table that was already populated by a concurrent transaction in the same session. Action: Do not attempt to access the temporary table until the concurrent transaction has committed or aborted. ORA-14451 Unsupported function with temporary table Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause. Action: No action is required.

11-82 Error messages

ORA-14452 An attempt was made to create, modify, or drop an index on a temporary table that is already in use Cause: An attempt was made to create, modify, or drop an index on a temporary table that is already in use. Action: All sessions that use the session-specific temporary table should truncate the table, and all transactions that use the transaction-specific temporary table should end their transactions. ORA-14453 Attempt to use a LOB from a temporary table whose data has already been flushed Cause: An attempt was made to use a LOB from a temporary table whose data was flushed because the table was transaction-specific and the transaction was committed or aborted. the table was truncated or the session that created this LOB ended. Action: This LOB locator is invalid and cannot be used. ORA-14454 Attempt to reference temporary table in a referential integrity constraint Cause: An attempt was made to reference the temporary table in a referential integrity constraint. This is not supported. Action: Use triggers. ORA-14455 Attempt to create a referential integrity constraint on a temporary table Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported. Action: Use triggers. ORA-14456 unable to rebuild index on a temporary table Cause: An attempt was made to rebuild an index on a temporary table. Action: Either way, the index data is lost at the end of the session/transaction. ORA-14457 did not allow VARRAY column or nested table in a temporary table. Cause: An attempt was made to create a VARRAY column or a nested table in a temporary table. This is not supported. User Response: Do not specify these data types for temporary tables.

ORA-12700 to ORA-19399

11-83

ORA-14458 An attempt was made to create a temporary table with organization INDEX. Cause: An attempt was made to create a temporary table organized by index. This is not supported. Action: Create the table with the HEAP organization and primary key. ORA-14459 Missing GLOBAL keyword Cause: The GLOBAL keyword is missing during temporary table creation. Action: Provide the missing keyword. ORA-14500 LOCAL option is invalid without partition name Cause: Incorrect syntax specified. Action: Repeat the command. Object ORA-14501 is not partitioned. Cause: The table or index is not partitioned. invalid syntax. Action: Repeat the command with the correct syntax. ORA-14503 Only one partition name can be specified Cause: More than one partition name was specified for the scan. Action: Specify a partition name. ORA-14504 syntax is not supported for parsing. Cause: A partition/subpartition number or bind variable was used. Action: Specify a valid partition/subpartition name. ORA-14505 LOCAL option valid only for partitioned indexes Cause: Incorrect syntax specified. Action: Repeat the command. ORA-14506 LOCAL option required for partitioned indexes Cause: Incorrect syntax specified. Action: Repeat the command. Corrupted ORA-14507 partition. all rows are not within partition boundaries Cause: The partition contains rows that should be in some other partition. Possibly due to a non-validating swap partition. Action: Remove the non-qualifying partition rows.

11-84 Error messages

ORA-14508 The specified VALIDATE INTO table was not found Cause: The specified table does not exist or the user does not have the appropriate privileges. Action: Specify the correct table to use. ORA-14509 Incorrect VALIDATE INTO table shape specified Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. See UTLVALID.SQL for more information. ORA-14510 may specify VALIDATE INTO clause only for partitioned tables Cause: VALIDATE INTO was specified for a non-partitioned table, cluster, or index. Action: Use the syntax correctly. ORA-14511 cannot perform operation on partitioned object Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes. Action: Repeat the command with the correct syntax. ORA-14512 cannot perform operation on a clustered object Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes. Action: Repeat the command with the correct syntax. ORA-14513 partitioning column might not be of object data type Cause: The user-specified partitioning column was an object data type (object, REF, nested table, array) which is illegal. User Response: Make sure none of the partition columns are an object data type. ORA-14514 LOCAL option is invalid without subpartition name Cause: Incorrect syntax specified. Action: Repeat the command. ORA-14515 Only one subpartition name can be specified Cause: More than one subpartition name was specified for analysis. Action: Specify a subpartition name.

ORA-12700 to ORA-19399

11-85

Corrupted ORA-14516 subpartition. all rows are not within subpartition boundaries Cause: The subpartition contains rows that should be in some other subpartition. Possibly due to a non-validating swap subpartition. Action: Remove the rows from the subpartition that do not qualify. ORA-14517 Index subpartition 'string.string' is in an unusable state Cause: An attempt was made to access an index subpartition that was marked unusable by a direct load or DDL operation. Action: REBUILD the unusable index subpartition. ORA-14551 cannot perform a DML operation within a query Cause: DML operations such as insert, update, delete, or select-to-update cannot be performed within a query or on a PDML slave. Action: Ensure that the offending DML operation is not performed, or use a stand-alone transaction to perform the DML operation within the PDML slave or query. ORA-14552 cannot DDL, commit or rollback within a query or DML Cause: DDL operations like creating tables, views, etc. and transaction control statements, such as commit/rollback, cannot be executed within a DML statement or query. Action: Make sure that the wrong operation is not performed or use stand-alone transactions to perform the operation within the query/DML operation. ORA-14553 cannot perform LOB write operation within a query Cause: Unable to perform a LOB write operation within a PDML query or slave. Action: Ensure that the incorrect LOB write operation is not performed, or use a stand-alone transaction to perform the operation on the PDML slave or query. ORA-16000 database open for read-only access Cause: The database was opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error. Action: To modify the database, it must first be closed and reopened for read/write access.

11-86 Error messages

Database ORA-16001 already opened for read-only access by another instance Cause: The database was opened for read-only access by another instance and cannot be opened for read/write access by this instance. Action: This instance must be opened for read/write access or all other instances must first be closed and reopened for read-only access. Database ORA-16002 already opened for read/write access by another instance Cause: The database was opened for read/write access by another instance and cannot be opened for read-only access by this instance. Action: This instance must be opened for read-only access or all other instances must first be closed and reopened for read/write access. ORA-16003 standby database is restricted to read-only access Cause: To ensure its integrity, a standby database can only be opened for read-only access. Action: Reissue ALTER DATABASE OPEN specifying READ ONLY. ORA-16004 backup database requires recovery Cause: The control file is for a backup database that requires recovery and cannot be opened by this instance for read-only access. Action: Perform the required recovery and reopen for read-only access. ORA-16005 database requires recovery Cause: The database requires recovery and therefore cannot be opened by this instance for read-only access. Action: Perform the required recovery and reopen for read-only access. ORA-16006 target audit_trail incompatible with database open mode Cause: The AUDIT_TRAIL initialization parameter was set to "DB" (or TRUE), which is incompatible with a database open for read-only access. Action: When the database is opened for read-only access, the AUDIT_TRAIL initialization parameter can only be set to "SO" or "NONE" (FALSE). ORA-16007 Invalid backup control file checkpoint Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore, the database cannot be opened for read-only access. Action: First, open the database for read/write access, which will result in a valid control file checkpoint. Then reopen the database for read-only access.

ORA-12700 to ORA-19399

11-87

Indeterminate control file checkpoint ORA-16008 Cause: The database control file being opened for read-only access was created via CREATE CONTROLFILE. Therefore, a control file checkpoint could not be computed and the database could not be opened for read-only access. Action: First, open the database for read/write access, which will result in a valid control file checkpoint. Then reopen the database for read-only access. ORA-16009 The remote file log destination must be a STANDBY database. Cause: The database associated with the file log destination service name is different from the required STANDBY type database. Remote archiving of redo log files is not allowed for non-STANDBY DB instances. Action: Perform the necessary steps to create the required compatible STANDBY database before retrying to process the FILE LOG. ORA-16010 Remote file log target database is open for update Cause: The database associated with the file log target service name is open for update access. Remote archiving of redo log files to open standby databases for update access is not allowed. Action: Shut down the target standby instance and reopen it for read-only access, or simply leave the standby instance mounted and closed. ORA-16011 Archivelog remote file server process in error state Cause: The archive log remote file server (RFS) process at the specified standby database site experienced an unrecoverable error and cannot receive any more files data file record. Action: Correct the problem on the standby database site. ORA-16012 Archivelog standby identifier mismatch Cause: The main and standby identifiers do not match. Remote archiving of redo log files is not allowed for unsupported STANDBY DB instances. Action: Perform the necessary steps to create the required compatible STANDBY database before retrying to process the FILE LOG. ORA-16013 log string sequence # string does not need archiving Cause: An attempt was made to archive the manually named file, but the file did not require archiving. The file was previously archived successfully. Action: No action is required.

11-88 Error messages

ORA-16014 log string sequence # string not archived, no destinations available Cause: An attempt was made to archive the named log, but the archive was unsuccessful. Archive failed because no archive log destinations were specified or all destinations had debilitating errors. Action: Verify that the archive log destinations are specified and/or take the necessary steps to correct any errors that may have occurred. ORA-16015 log string sequence # string not archived, media recovery disabled Cause: An attempt was made to archive named log, but the archive was unsuccessful. A standby file log destination was specified and the database was not enabled for media recovery. This is not allowed. Action: Disable the standby destination or enable media recovery and try again. ORA-16016 archive log for thread string sequence # string not available Cause: The standby database sustained recovery operation timed out while waiting for the requested archive log file. Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command. ORA-16017 cannot use LOG_ARCHIVE_DUPLEX_DEST without a central archive destination Cause: The LOG_ARCHIVE_DUPLEX_DEST parameter was set to a non-null value when the central archive destination was explicitly set to NULL. User Response : Set the destination of the main file to a valid non-null value. ORA-16018 cannot use a string with LOG_ARCHIVE_DEST_n Cause: One of the following events caused a mismatch: ■

■

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter was in use when a LOG_ARCHIVE_DEST_n (n = 1...5) parameter was encountered while getting the initialization parameters. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while searching for start parameters. A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to set a value for the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter.

ORA-12700 to ORA-19399

11-89

Action: Remove all incompatible parameter definitions. ORA-16019 cannot use a string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST Cause: One of the following events caused a mismatch: ■

■

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter was encountered when getting the initialization parameters. The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to set a value for the specified LOG_ARCHIVE_DEST_n parameter. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered when getting the start parameters. An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to set a value for the specified LOG_ARCHIVE_DEST_n parameter.

Action: Remove all incompatible parameter definitions. ORA-16020 Fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the value of the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter. Action: Adjust the configuration of the log file destination parameter or reduce the value of LOG_ARCHIVE_MIN_SUCCEED_DEST. ORA-16021 session string target cannot be the same as session string target Cause: An attempt was made to change the first file registry parameter specified using ALTER SESSION to have a target value that duplicates the value of session level target of the second log file specified parameter. User Response : Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.

11-90 Error messages

ORA-16022 LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is not NULL Cause: An attempt was made to change the LOG_ARCHIVE_DEST parameter to NULL when the LOG_ARCHIVE_DUPLEX_DEST parameter is not NULL. User Response : Set the LOG_ARCHIVE_DEST parameter to a non-NULL value or set the LOG_ARCHIVE_DUPLEX_DEST parameter to a NULL value. ORA-16023 system string destination cannot be the same as session string destination Cause: An attempt to change the first parameter LOG_ARCHIVE_DEST_n (n = 1...5) specified resulted in a destination that duplicates the value The session destination of the second LOG_ARCHIVE_DEST_n specified parameter. This error can occur when setting a non-null value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with the ALTER SESSION command, because the associated system target value can appear as a duplicate. Action: Specify a different destination value for the first LOG_ARCHIVE_DEST_n parameter specified. Cannot parse parameter string ORA-16024 Cause: The specified parameter value LOG_ARCHIVE_DEST_n (n = 1...5) could not be parsed. Common causes of this error are a misplaced equals sign, an unrecognized option, or an option that does not have a required value. Action: Correct the value of the LOG_ARCHIVE_DEST_n parameter. ORA-16025 parameter string contains repeated or conflicting options Cause: The specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter value contained repeated or conflicting options. Action: Correct the value of the LOG_ARCHIVE_DEST_n parameter. ORA-16026 parameter string contains invalid reopen time Cause: The specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter value contained a REOPEN option with an invalid numeric value. The valid range is 0-65535. Action: Correct the value of the LOG_ARCHIVE_DEST_n parameter.

ORA-12700 to ORA-19399

11-91

ORA-16027 parameter string is missing a destination option Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...5) parameter could not add a destination option. Valid destination options are LOCATION or SERVICE. Action: Correct the value of the LOG_ARCHIVE_DEST_n parameter. ORA-16028 New chain results in fewer destinations than required LOG_ARCHIVE_MIN_SUCCEED_DEST Cause: With automatic archiving enabled, an attempt was made to change the specified LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...5) to a value that reduces the number of archives log destinations less than the LOG_ARCHIVE_MIN_SUCCEED_DEST value. Action: Select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters or reduce the value of the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter. ORA-16029 cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations. Action: Define one or more log file destinations using the LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...5) parameters. Then change the value of the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter. ORA-16030 session-specific change requires a LOG_ARCHIVE_DEST_n destination Cause: The following event caused a mismatch: The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command. Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with the LOG_ARCHIVE_DEST_n (n = 1...5) parameters. ORA-16031 Parameter string target string exceeds string character limit Cause: The specified parameter value contained a target string that was too long.

11-92 Error messages

User Response : Replace the target value of the specified parameter with a string less than the length specified in the error message. ORA-16032 parameter string target string cannot be translated Cause: The specified parameter value contained a target string that could not be translated. User Response : Use a valid target string in the specified parameter. The target string for the ORA-16033 parameter cannot be the same as the target string for the parameter Cause: An attempt was made to change the first specified log file parameter to have a target value that duplicates the target value in the system of the second file record parameter specified. User Response : Specify a different value for one of the file's registry parameters. ORA-16034 FROM parameter is not supported for MANAGED recovery Cause: The use of the FROM parameter 'location' is not allowed when MANAGED recovery was specified. Action: Correct the syntax and try the command again. ORA-16035 missing required keyword string Cause: The STANDBY DATABASE keywords are required when MANAGED recovery was specified. Action: Correct the syntax and try the command again. ORA-16036 Invalid recovery MANAGED CANCEL option Cause: A mode other than IMMEDIATE follows the CANCEL keyword in the RECOVER MANAGED STANDBY DATABASE statement. Action: Specify nothing or IMMEDIATELY after CANCEL. ORA-16037 User requested to cancel the standby recovery operation Cause: The standby database recovery operation was canceled at the user's request. Action: No action is required. ORA-16038 Unable to archive log string # Cause: An attempt was made to archive the indicated file, but the archive failed. Examine the minor error messages to determine the cause of the error.

ORA-12700 to ORA-19399

11-93

Action: No action is required. ORA-16039 RFS request version mismatch Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the remote file server (RFS) on the standby site. Action: Verify that the supported versions of Oracle are running on the primary site and all standby sites. ORA-16040 destination standby log file is locked. Cause: The log file for the destination standby file is currently locked. This indicates that the file is being archived by another RFS (Remote File Server) process. Action: Verify and remove any duplicate standby destination file logging service names defined for the primary database. ORA-16041 Remote File Server Fatal Error Cause: The Remote File Server (RFS) process on the standby target file registry site encountered a shutdown error and is no longer available. Additional archiving may not be possible on the storage site. Action: Check the appropriate RFS trace file located on the standby site for details on the error encountered and, if possible, take corrective action. ORA-16042 The user requested that the standby recovery operation be canceled immediately Cause: The standby database recovery operation was canceled immediately at the user's request. Log file processing of the current file has stopped and therefore the database is in an inconsistent state. Action: No action is required. ORA-18000 invalid schema name Cause: The parser detected an invalid or missing schema name. Action: Reissue the command, specifying a valid schema name. ORA-18001 No option specified for ALTER CONTOUR Cause: The parser detected that no clause was specified in the command. Action: Reissue the command, specifying a valid ALTER OUTLINE clause. ORA-18002, specified contour does not exist Cause: The contour did not exist to begin with, or a time window allowed another thread to drop or change the contour midway.

11-94 Error Messages

Action: Check the outline and try again. ORA-18003 A schema with this signature already exists Cause: The signature generation algorithm generates signatures that are 16 bytes long, so it is highly unlikely that two signatures are identical. This message is generated in such a rare case. Action: Reissue the statement that led to the creation of the sketch with some white space added, or force the creation of the sketch in a different category. ORA-18004 Stub already exists Cause: A stub already exists, either with the specified name or for the specified SQL text. Action: Try again with another name. ORA-18005 Create any schema privilege is required for this operation Cause: Create any schema privilege is required to attempt the operation. Action: Make sure that you have created all schema privileges and try the operation again. ORA-18006 remove schema privileges required for this operation Cause: Removing schema privileges required for the attempted operation. Action: Make sure that you have dropped all schema privileges and try the operation again. ORA-18007 The schema privileges need to be changed for this operation Cause: The schema privileges need to be changed for the attempted operation. Action: Make sure to change the schema privileges and try the operation again. ORA-18008 Cannot find OUTLN schema Cause: The database creation script that creates this schema must not have been executed. Action: Review the log files to see what happened when the database was created. ORA-18009 One or more schema system tables do not exist. Cause: The database creation script that creates these tables did not run or a user accidentally dropped the table. Action: Review the log files to see what happened when the database was created.

ORA-12700 to ORA-19399

11-95

Command ORA-18010 is missing CATEGORY keyword required Cause: The user could not specify the CATEGORY keyword. Action: Reissue the command with the CATEGORY keyword included.

11-96 Error messages

12 ORA-19400 to ORA-24279 ORA-19400 System type conflict with SYS.string object Cause: The user had an object with the same name as one of the system types. The system types were not initialized correctly. Action: Delete the conflicting object and rerun the migration. ORA-19500 device block size string is invalid Cause: The device block size returned by the sequential I/O OSD is invalid. Action: If the block size was configured with the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, the specified block size must be changed. If the PARMS option was not specified in the ALLOCATE CHANNEL command, this is an internal error that should be reported to Oracle. ORA-19501 read error in file "string", block no string (blocksize=string) Cause: read error in input file. Action: Check the file. Write error ORA-19502 to file "string", blockno string (blocksize=string) Cause: Write error to output file. Action: Check the file. ORA-19503 cannot get device info, name="string", type="string", parms="string" Cause: The get device info call returned an error. Action: Check the name, type, and parameters of the device. ORA-19504 could not create file "string" Cause: The call to create the file returned an error.

ORA-19400 to ORA-24279

12-1

Action: Check additional messages and check access permissions. ORA-19505 could not identify file "string" Cause: The call to identify file returned an error. Action: Review any additional messages and verify that the file exists. ORA-19506 could not create sequential file, name="string", parms="string" Cause: The call to create sequential file returned an error. Action: Check additional messages, check access permissions. ORA-19507 could not retrieve sequential file, handle="string", parms="string" Cause: The call to retrieve sequential file returned an error. Action: Review any additional messages and verify that the file exists. ORA-19508 could not delete file "string" Cause: The call to delete the file returned an error. Action: Check for additional messages. ORA-19509 could not remove sequential file, handle="string", parms="string" Cause: The call to remove sequential file returned an error. Action: Check for additional messages. ORA-19510 could not set string block size for file "string" (blocksize=string) Cause: The call to change file size returned an error. Action: Check for additional messages. ORA-19511 string Cause: An error occurred in the media management software that is linked to the Oracle server to perform backup and restore in cooperation with Recovery Manager. Action: If the text of message 19511 does not provide enough information to resolve the problem, contact your media management software vendor. ORA-19550 cannot use backup/restore functions when using dispatcher Cause: An attempt was made to use backup/restore functions while connected to dispatcher on a multi-threaded server. This is not allowed because the device used for backup and restore must remain assigned to a single process.

12-2

message error

Action: Connect directly to the instance and run the backup or restore function again. Device ORA-19551 is busy, device type: string, device name: string Cause: The indicated device could not be allocated because it is assigned to another session, no device is named, or all devices of the requested type are busy. Action: Try to assign another device or wait until the required device is no longer busy. ORA-19552 device type string is invalid Cause: The indicated device type is invalid. Action: Provide a correct device type and retry the mapping. ORA-19553 device name string is invalid Cause: The supplied device name is invalid. Action: Provide a correct device name and retry the assignment. ORA-19554 error allocating device, device type: string, device name: string Cause: Failed to allocate the specified device. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error and retry the assignment. ORA-19555 Invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value Cause: The LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value was not set within the valid range. Action: Specify a correct value for the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter. If the log file parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter to 1 or 2. ORA-19556 The required destination LOG_ARCHIVE_DUPLEX_DEST is currently deferred Cause: The destination of the LOG_ARCHIVE_DUPLEX_DEST parameter was deferred when it needed to be enabled. The destination was automatically deferred when an ALTER SYSTEM command for the LOG_ARCHIVE_DEST parameter set a destination that duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.

ORA-19400 to ORA-24279

12-3

Action: Change the destination value of the LOG_ARCHIVE_DUPLEX_DEST parameter. ORA-19557 Device Error, Device Type: String, Device Name: String Cause: An error occurred in platform-specific device code. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error and retry the assignment. ORA-19558 error when deallocating device Cause: The specified device could not be deallocated. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error and retry the assignment. ORA-19559 error sending device command: string Cause: An error occurred while sending the indicated command to the session device. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error and retry the assignment. The string ORA-19560 is not a valid device limit. Cause: An invalid device limit type was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT. Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL. ORA-19561 string requires a DISK channel Cause: The command intent required a DISK device channel to be assigned for the session, but a non-DISK device was found. Action: Unmap the current device and assign a DISK channel, then try the command again. ORA-19562 file string is empty Cause: The indicated file, which is a file record, control file, or data file, was found empty during a copy, backup, or scan operation]. Action: Make sure that the correct files are specified for the copy or backup operation.

12-4

message error

ORA-19563 String header validation for file string failed Cause: When opening the file for placement in a Backup or Copy Set, inspecting it, or using it as a destination for an incremental restore, the header was not recognized as a file string. A valid file header for a file of the indicated type (data file, archive log, or control file) belonging to the current database. Action: Make sure that the correct files are specified for the copy or backup operation. ORA-19564 error occurred while writing string bytes to block number string Cause: An error occurred while writing to a file. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error, if possible, and try the copy, backup, or restore operation again. ORA-19565 BACKUP_TAPE_IO_SLAVES not enabled during mirroring for sequential devices Cause: An attempt was made to specify mirroring for sequential devices, but the initialization parameter BACKUP_TAPE_IO_SLAVES was not enabled. Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file or do not specify duplex for sequential devices. ORA-19566 Bad block limit from chain to chain from file exceeded Cause: User-specified limit of allowed bad blocks was exceeded when reading the specified data file for a copy or backup of the data file . Action: No action is required. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupted. ORA-19567 cannot reduce the file chain because it is being copied or backed up. Cause: An ALTER statement tried to reduce the size of the indicated file while copying or copying the same file. Action: Try to resize again after the backup or copy is complete. ORA-19568 a device is already assigned to this session Cause: A device cannot be assigned to a session if another device is already assigned. Action: Unmap the current device.

ORA-19400 to ORA-24279

12-5

ORA-19569 No device is allocated for this session Cause: An operation that requires a device to be allocated for the current session was attempted and no device was allocated. Action: Assign a device and retry the operation. ORA-19570 file number string is outside the valid range of 1 to string Cause: A file number used in a copy, backup, or restore operation is invalid for the current database. Action: Specify a valid file number. ORA-19571 string recid string stamp string not found in control file Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file was not found in the control file . Action: Specify a correct RECID/stamp and try the copy or backup again. ORA-19572 cannot process file string, file size is being changed Cause: The input file specified for a copy or backup operation could not be opened because the file size is being changed. Action: Wait for the resize to complete and try the copy or backup again. ORA-19573 cannot enqueue string for data file string Cause: Failed to get file access enqueue for a specific file in a backup, copy, or restore operation. If the displayed queue type is SHARED, the file is the input file for a backup or copy. If the type is EXCLUSIVE, the file is the output file for a copy or restore of a data file that attempts to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed. If the type is read-only, you are trying to back up or copy this file while the database is in NOARCHIVELOG mode. Action: Wait until the conflicting operation is complete and try the copy or backup again. If the database is in NOARCHIVELOG mode, all backup files should be closed gracefully. Output file name must be specified ORA-19574 Cause: This type of backup or restore requires an output file name. Action: Specify an output file name and repeat the copy.

12-6

message error

ORA-19575 String blocks expected in file string, string found Cause: During a backup, restore, copy, or browse operation, the indicated file did not contain as many blocks as indicated in the file header. Action: The input copy or the backup part is probably corrupted. If another backup or copy of the file being restored exists, the damaged file can be removed from the recovery catalog and the operation can be restarted. ORA-19576 Data file string not defined in control file Cause: The specified file number was not found in the control file. Action: Specify a correct file number and retry the operation. ORA-19577 file string is MISSING Cause: A copyDataFileCopy, restoreDataFileTo, or proxyRestoreDataFile function specified a file number but not an output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but was not named during the last CREATE CONTROLFILE statement, so the name in the control file does not can be used for restoration. Action: Specify an output file name or issue a RENAME SQL command to insert a valid name for this file into the control file. ORA-19578 End of volume during duplex for sequential files, part of incomplete backup Cause: An end of volume (EOV) condition was detected during duplex for sequential files and this condition cannot currently be handled. Action: Before retrying the backup, verify that the backup parts fit on the volume, or disable duplexing. ORA-19580 thread conversation idle Cause: A backup or restore operation was attempted before a conversation was started. Action: start a conversation and repeat the operation. ORA-19581 no file named Cause: An attempt was made to move from the file naming phase to the processing phase of part of a backup or restore conversation before any files were specified for backup or restore. Action: Specify some files and try the operation again.

ORA-19400 to ORA-24279

12-7

ORA-19583 conversation ended due to error Cause: An error occurred that forced the current backup or restore conversation to end. Action: There should be other error messages to help identify the cause of the problem. Fix the mistake and start another conversation. ORA-19584 file string already in use Cause: The indicated file, which was specified as the destination of a copy, restore, or delete operation, is already in use in the database. Action: Specify a different name and try the operation again. ORA-19585 Premature end of partial sequenced volume Cause: While creating the indicated backup shard, an end-of-volume condition was encountered before all backup set control data was written to the backup shard. backup. This is most likely a media error because the amount of control data in the Backup Set is very small relative to the total amount of data in a Backup Set. Action: Retry the part with a larger piece of output material. ORA-19586 String k-byte limit is too small to contain part directory Cause: The user-specified limit of k-bytes per backup part is not enough to contain part control data. backup set. User Response : Use the setLimit procedure to increase the limit by k bytes and retry the operation. ORA-19587 error occurred while reading string bytes in block number string Cause: An error occurred while reading a file. Action: One or more messages should be displayed to help identify the cause of the error. Correct the error and try the copy, backup, or restore operation again. ORA-19588 string recid string stamp string is no longer valid Cause: The indicated record was marked as deleted. This indicates that the corresponding file has been replaced by another copy or restore, or that the copy has been 'consumed' by a switchToCopy operation. Action: If you know the name of the file you want to copy, inspect it and retry the copy by specifying the new RECID.

12-8

message error

ORA-19589 String is not a backup or snapshot control file Cause: The control file that is the source of a copy or backup operation is not a backup or snapshot control file . Action: Specify the name of a snapshot or a backup control file. ORA-19590 chat already active Cause: An attempt was made to start a backup or restore chat, but another chat is already active in this session. Action: Continue the current conversation or call backupCancel or restoreCancel to end the current conversation before starting a new one. ORA-19592 bad string conversation type Cause: An attempt was made to specify a file type to back up or restore, but the current conversation cannot process that file type. For example, you specified that an archived log be included in a data archive backup set. The specified file will not be included in the backup or restore operation. Action: No action is required. The conversation is still active and more files can be specified. ORA-19593 data file number string already included as string Cause: This data file is already specified to be included in this backup or restore conversation. A backup or restore conversation can process only a single instance of a data file. Action: No action is required. The conversation is still active and more files can be specified. ORA-19594 control file already included as string Cause: The control file is already specified to be included in this backup or restore conversation. A backup or restore conversation can only process a single instance of the control file. Action: No action is required. The conversation is still active and more files can be specified. ORA-19595 file log thread string string already included as string Cause: The indicated file log has already been specified for inclusion in this backup conversation. A backup conversation can process only one copy of any log file. Action: No action is required. The conversation is still active and more files can be specified.

ORA-19400 to ORA-24279

12-9

ORA-19596 Snapshot control file not created Cause: You requested that the snapshot control file be included in the backup set, but no snapshot control file was created for this instance. Action: Specify a different control file name or call cfileMakeAndUseSnapshot to create the snapshot control file. ORA-19597 file string block size string does not match the defined block size of the string Cause: A file was specified for inclusion in a backup set, but it has a different logical block size than the rest of the files in the backup set. All files in a Backup Set must have the same logical block size. Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified. ORA-19598 Initial SCN must be specified for incremental backup Cause: No initial SCN was specified for backupDataFile or backupDataFileCopy, but the current backup conversation is for an incremental backup, which requires an SCN other than SCN to be specified. zero for all backup files. . Action: The conversation is still active. Re-specify the data file with a non-zero SCN. ORA-19599 block number string is corrupted in string string Cause: A bad block was found in a control file, log file, or backup part that was being read for backup or copy. Corruption in control files, archive logs or backup parts must not be tolerated. Action: No action is required. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the replay can be played. ORA-19600 input file is a string string Cause: This message identifies the input file for a failed copy operation. The file number and name (if the name has been determined) are displayed. 🇧🇷

■

12-10 Error messages

For a data file, the file number refers to the absolute number of the data file as displayed in the DBA_DATA_FILES view. For a data file copy, the file number refers to the copy control file record number, as shown on the V$DATAFILE_COPY screen. For a data file copy, the file number refers to the copy control file record number, as displayed in the RECID column of the V$DATAFILE_COPY view.

■

For an archived log, the file number refers to the record number of the log's control file, as displayed in the RECID column of the V$ARCHIVED_LOG view.

Action: Other messages should be displayed to help identify the cause and solution. ORA-19601 output file is a string string Cause: This message identifies the output file for a failed copy operation. The fields are described in message 19600. When creating a new copy of the data file, its control file record number may not have been determined at the time the message was printed. In this case, the record number displayed is zero. Action: View another error message. ORA-19602 Unable to back up or copy an active file in NOARCHIVELOG mode Cause: An attempt was made to back up or back up a file that was not closed properly and the database was in NOARCHIVELOG mode. This is not allowed because when the file is restored it will need to be redoed by the application before it can be used and the redo is not currently saved beyond the contents of the online redo logs. Action: Drop the offline tablespace or shut down the database and retry the copy or backup. ORA-19604 Conversation file naming phase ended Cause: A call was made to specify a file to back up or restore after processing the first part of the backup. Action: You cannot specify more files to be processed during a backup or restore conversation after the first part of the backup has been processed. If more files need to be specified, you must start a new conversation. Input file name must be specified ORA-19605 Cause: The input file name was not specified for a control file copy operation. Action: Specify an input file name and retry the operation. ORA-19606 Cannot copy or restore to snapshot control file Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. Overwriting the snapshot control file in this way is not allowed. Other methods are available to create the snapshot control file. Action : Specify a different file name and try the operation again. If it is a restore, the restore conversation will remain active and more files can be specified.

ORA-19400 to ORA-24279

12-11

The ORA-19607 string is an active control file. Cause: A copy, restore, or backup of a control file specified the name of a named control file in the INIT.ORA file as the input or output file. Action : Specify a different file name and try the operation again. If it is a backup or restore conversation, the conversation will remain active and more files can be specified. ORA-19608 String is not a backup chunk Cause: The specified file is not a backup chunk produced by the DBMS_BACKUP_RESTORE package. The first block of the backup part is corrupted or this file is not a backup part. Action : Specify a different file name and try the operation again. String ORA-19609 is from a different Backup Set: stamp string count string Cause: The file specified is not from the Backup Set that is currently being processed. It is part of a different backup set. The identification of the assembly that contains this part is displayed. Action : Specify the correct backup part and retry the operation. ORA-19610 directory block chain is corrupted Cause: The indicated directory block failed checksum validation. This backup piece is unusable. Action: Provide another copy of the same part of the backup or end the restore conversation. Backup part ORA-19611 out of order. String expected but string found Cause: This part of the backup is out of sequence. Action: Provide the correct backing piece. ORA-19612 data file string was not restored due to string Cause: The indicated file could not be restored because all of its data blocks were not found in the backup part. Action: The restore conversation remains active and the current part must be reprocessed. If the fault cannot be resolved by reprocessing the current part, the restore conversation must be cancelled. ORA-19613 data string not found in backup set Cause: The indicated file could not be restored because it is not in this backup set. If the file number is zero, it refers to the control file.

12-12 Error messages

Action: This message is issued when the directory of the first part of the backup is read and one or more files named for restore are not found. The restore conversation is still active, but no data has been read and you must provide the first backup part of a backup set that contains all the requested files. ORA-19614 file log thread string string not found in backup set Cause: The indicated archived log file was explicitly named for restore, but is not included in this backup set. Action: This message is issued when the directory of the first part of the backup is read and one or more files named for restore are not found. The restore conversation is still active, but no data has been read and you must provide the first backup part of a backup set that contains all the requested files. ORA-19615 Some files were not found in the backup set Cause: Some files specified to restore were not found in the backup set directory. Message 19613 or 19614 is issued for each file not found. Action: See the instructions for message 19613. The output file name ORA-19616 must be specified if the database is not mounted. Cause: Restoring a data file did not specify a destination file name, but the data in the database is not mounted. The database must be mounted when no destination filename is specified, so that the destination filename can be taken from the control file. Action: The restore conversation remains active. If you want to restore data files without their destination file names, mount the database before proceeding. Otherwise, a destination file name must be specified on all data file restore calls. The ORA-19617 file string contains data from different resetlogs. Cause: The named file contains resetlogs data that is different from the archived log files that are already included in the backup set. All archived log files in a backup set must have the same log restore data. Action: The restore conversation remains active and you can continue to specify the archived log files to include in the backup set. ORA-19618 cannot name files after restoreValidate was called Cause: A call was made to specify a file to restore from a backup set, but a previous restoreValidate call was already made. Action: You must cancel and restart the conversation if you want to specify the files to be restored.

ORA-19400 to ORA-24279

12-13

ORA-19619 cannot call restoreValidate after files have been named Cause: restoreValidate was called after some files were already specified to restore. Action: You must cancel and restart the conversation if you want to call restoreValidate. ORA-19621 File log range already specified Cause: A log range has already been specified. Only one SCN range can be specified per conversation. Action: The restore conversation remains active and more records per thread and sequence number can be specified if desired. ORA-19622 File log thread string sequence string not restored due to string Cause: The named file could not be restored because all of its data blocks were not found in the backup part. Action: The restore conversation remains active and the current part must be reprocessed. If the fault cannot be resolved by reprocessing the current part, the restore conversation must be cancelled. ORA-19623 file chain is open Cause: A SwitchToCopy operation specified a copy of the data file whose parent data file is open. Action: Take the owning tablespace offline or shut down the database and retry the operation. Operation ORA-19624 failed, can you try again? Cause: A backup, restore, or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, the operation can be retried. Action: Recovery Manager uses this message to decide whether or not to retry the operation. ORA-19625 error identifying file string Cause: A file specified as an input for a copy or backup operation, or as a destination for an incremental restore, could not be identified as an Oracle file. An operating system specific error accompanies this error to help identify the problem. Action: Specify a different file and try the operation again.

12-14 Error messages

The ORA-19626 backup set type is a string; this conversation can't process it. Cause: The data in the backup set is not compatible with the current conversation. Action: Provide the first part of a backup set that matches the current conversation, or start a new restore conversation that can process this backup set. ORA-19627 cannot read backup parts while control file is applied Cause: This is a control file restore conversation, which uses offline range information from one or more control files to update the checkpoint data from the data file. Backup sets are not used during this type of conversation. Action: The conversation is still active and more control files can be applied. ORA-19628 invalid SCN range Cause: Starting SCN to restoreRedoLogRange is greater than ending SCN. Action: Specify a starting SCN that is less than or equal to the ending SCN. ORA-19629 no files in specified file record SCN range Cause: This backup set does not contain files in the specified range. Action: Provide a backup set that contains files in the correct range, or start a new conversation and specify a range that will select some files from that backup set. End of volume ORA-19630 encountered when copying part of backup Cause: When copying a part of the operating system's native file system backup to an output device, the output device encountered the end of the volume. Action: The copy fails. This can happen if you use a tape that is not large enough to hold the entire backup. Archive record ORA-19631 contains no file name Cause: This archive record represents a change to an active record that occurred without archiving its previous content. The previous content of the log file is lost. User Response : Specify the RECID of a file record that contains a file name. The V$ARCHIVED_LOG fixed view can be used to examine archived logs. ORA-19632 filename not found in control file Cause: The name passed to getFno was not found in the control file.

ORA-19400 to ORA-24279

12-15

User Response : Provide a valid file name. ORA-19633 The control file log string is out of sync with the recovery catalog Cause: The control file record that describes the file to be deleted in a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete, or deleteArchivedLog does not match the data validation files provided by Recovery Manager. Action: Contact Oracle Customer Support. ORA-19634 filename required for this function Cause: The FNAME parameter or identifier was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog, or proxyDelete. Action: Specify the FNAME or the identifier parameter when calling these functions. ORA-19635 input and output file names are identical Cause: Identical input and output file names were specified for a data file copy operation. User Response : Specify an output file name that is different from the input file name. ORA-19636 file record thread string already included string Cause: The indicated file record is already specified for inclusion in this restore conversation. A restore conversation can process only one copy of any log file. Action: No action is required. The conversation is still active and more files can be specified. ORA-19637 backupPieceCreate requires a filename when using a DISK device Cause: The session device is currently mapped to disk and therefore a filename is required. Action: Provide a file name and try the operation again. The string in the ORA-19638 file is not current enough to apply this incremental backup Cause: The target checkpoint for this incremental backup is less than the start of the incremental backup. If this backup were applied, any changes made between the data file checkpoint and the start of the incremental backup could be lost. Action: Provide a backup set that can be applied and retry the operation.

12-16 Error messages

The ORA-19639 file stream is more current than this incremental backup. Cause: The target checkpoint for this incremental backup is greater than or equal to the file checkpoint in the incremental backup set. This backup cannot advance the checkpoint of the destination file, so there is no point in applying it. Action: Provide a backup set that can be applied and retry the operation. ORA-19640 data file checkpoint is SCN string time string Cause: This message identifies the data file checkpoint for a data file that was too old to perform an incremental backup or the destination of an incremental backup. incremental restore failed to apply. Action: View another error message. ORA-19641 Backup data file checkpoint is SCN string time string Cause: This message identifies a data file checkpoint in an incremental backup set that could not be applied. Action: View another error message. ORA-19642 SCN incremental-start is string Cause: This message identifies the SCN start of an incremental backup that could not be applied. Action: View another error message. ORA-19643 datafile string: Incremental start SCN too recent Cause: The incremental start SCN specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which can cause some blocks to be lost. Action: Specify a smaller incremental start SCN. ORA-19644 Data File Sequence: Incremental Start SCN is earlier than Resetlogs SCN sequence Cause: The Incremental Start SCN that was specified when starting an Incremental Data File backup is less than the Resetlogs SCN. resetlogs. Action: Specify a larger incremental start SCN. ORA-19645 Data File String: Incremental Start SCN is older than SCN creation string Cause: The Incremental Start SCN that was specified when starting an Incremental Data File backup is less than the SCN of creation of the data file die. Action: Specify a larger incremental start SCN.

ORA-19400 to ORA-24279

12-17

ORA-19646 unable to change data file string size from one string to another Cause: The named file was resized before this incremental backup was taken, but the incremental backup could not set the file in the new size. Action: Examine the other messages that should be present to indicate the cause of the failure. ORA-19647 Cannot specify a non-zero LEVEL when INCREMENTAL is FALSE Cause: BackupSetDataFile was called with a non-zero BACKUP_LEVEL and an incremental indication of FALSE. Action: Set incremental to TRUE or change BACKUP_LEVEL to zero. ORA-19648 Data File String: Incremental Startup SCN is equal to the Checkpoint SCN Cause: The Incremental Startup SCN that was specified to start an Incremental Datafile Backup is equal to the File Checkpoint SCN of dice. Because an incremental backup can only be applied to a data file whose checkpoint SCN is between the backup set's incremental (inclusive) start SCN and the backup set's checkpoint (exclusive) SCN, backup set, there are no data files to which this backup set can be applied. . Action: Specify a smaller incremental start SCN. ORA-19649 Offline range record string stamp string not found in file string Cause: applyOfflineRange was called with a RECID/stamp that was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is. Action: Specify the RECID/Stamp of an existing record in the control file copy. ORA-19650 Offline Trace Log Record Sequence Stamp string in file string contains string SCN Cause: This message identifies the offline deleted SCN of the indicated offline trace log in the indicated file. Action: View another error message. ORA-19651 cannot apply offline range record to data file string: mismatched SCN Cause: applyOfflineRange cannot apply offline range record to a target data file unless the SCN of the point of control of the data in the data file exactly matches the offline cleared SCN in the specified offline interval record. Action: Specify an offline interval record whose offline-cleared SCN matches the checkpoint of the target data file.

12-18 Error messages

ORA-19652 cannot apply offline range registration to datafile chain: file is out of order Cause: The target data file for an applyOfflineRange call is out of order. Action: Specify a destination data file that is closed gracefully. ORA-19653 cannot switch to an older file incarnation Cause: SwitchToCopy was called with a data file copy to a data file that was deleted before this control file was backed up. Action: Restore and mount a previous control file. It is acceptable to use a control file that was backed up before creating the specified data file. ORA-19654 must use backup control file to switch file incarnations Cause: This switchToCopy operation attempts to change the incarnations of a data file, but the currently mounted control file is not a backup control file security. Action: Restore and mount a backup control file. ORA-19655 cannot switch to incarnation with data from different resetlogs Cause: This switchToCopy operation attempts to switch to a data file that comes from a different version of database resetlogs. Action: Restore a backup control file that was taken from the same version of the database as the destination data file copy, or switch to a different data file copy. ORA-19656 unable to back up, copy, or delete log string online Cause: The indicated log file is an active log. You can only back up, copy, or delete archived records. Action: The indicated log file cannot be processed. Select another file. ORA-19657 cannot inspect current data file chain Cause: The file being inspected is already part of the currently mounted database. Action: No action is required. The file is already part of the database. ORA-19658 cannot inspect chain: file comes from different reset logs Cause: The data in the reset logs in the log file being inspected does not match the currently mounted control file. Action: The indicated file cannot be processed; inspect another file.

ORA-19400 to ORA-24279

12-19

ORA-19659 incremental restore would advance the file string past the restore records. Cause: This incremental backup cannot be applied to the specified data file because the data file is from a previous incarnation of the database and its checkpoint would be too early to be recoverable in the current one. database incarnation. Action: This incremental cannot be applied to this data file. If you want to recover the file for the SCN reset logs so that the database can be opened with the RESETLOGS option, then you must use redo log recovery, not incremental restore, to continue recovering this file. ORA-19660 Some files in the backup set could not be verified Cause: A restore conversation was performed to verify all files in a backup set, and the files that were printed in messages 19661 or 19662 could not be verified because blocks damaged files for those files were found in the backup set. Action: Unless the corruption to the Backup Set can be repaired, the indicated files cannot be restored from this Backup Set. Could not verify data file string ORA-19661 Cause: Some data blocks for the indicated data file were corrupted in the backup set. Action: Unless the corruption to the Backup Set can be repaired, the indicated data file cannot be restored from this Backup Set. ORA-19662 Unable to verify archive log thread sequence Cause: Some data blocks for the indicated archive log were corrupted in the backup set. Action: Unless the corruption to the Backup Set can be repaired, the indicated log archive cannot be restored from this Backup Set. ORA-19663 cannot apply current offline range to data file string Cause: An attempt was made to apply current offline range to the specified data file, but the data file is not current enough or is not in the Correct SCN to apply offline range. Action: The data file remains unchanged. ORA-19664 file type: string, file name: string Cause: This message is issued to identify the file that is subject to an error.

12-20 Error messages

Action: No action is required. This is an informative message. There should be other messages from Oracle explaining the cause of the error. The ORA-19665 size string in the file header does not match the actual file size of the string. Cause: The file size indicated in the file header does not match the actual file size. The two different sizes are shown in logical block units. Action: This file cannot be used; it was probably truncated. ORA-19666 cannot perform incremental restore of control file Cause: The control file was included in an incremental restore conversation Action: If you want to restore the control file, you must perform a full restore of the control file. ORA-19667 cannot perform incremental restore of data file chain Cause: The data file backup is a full backup. Action: If you want to restore the data file, you must perform a full restore of the data file. ORA-19668 cannot fully restore data file chain Cause: The data file backup is an incremental backup. Action: If you want to restore the data file, you must perform an incremental restore of the data file. ORA-19669 Copy proxy functions cannot be performed on the DISK channel. Cause: A copy proxy procedure was called, but the device allocated for the current session is of type DISK. Action: Assign a channel other than DISK and try the operation again. Please note that proxy copy requires a third-party media management software product that supports this backup/restore feature. The ORA-19670 file chain is already being restored. Cause: A proxy restore function has already named this file as the restore destination. Action: Use a different file name. If this message appears during a Recovery Manager job, it is an internal Recovery Manager error and you should contact Oracle Customer Support.

ORA-19400 to ORA-24279

12-21

ORA-19671 The media management software returned an invalid proxy handle Cause: During a proxy backup or restore, the media management software returned an invalid file handle. This is an internal error in the media management software that is linked to Oracle to provide backup/restore services. Action: Contact your media management software vendor. ORA-19672 The media management software returned an invalid file status Cause: During a proxy backup or restore, the media management software returned an invalid file status. This is an internal error in the media management software that is linked to Oracle to provide backup/restore services. Action: Contact your media management software provider. ORA-19673 error during file chain proxy copy Cause: During a proxy backup or restore, there was an error copying this file, but other files might have been copied successfully. Action: There should be other errors in the error stack that explain why the file could not be copied successfully. File string ORA-19674 is already being backed up with a proxy copy Cause: Recovery Manager attempted to back up the specified file with a proxy copy, but another Recovery Manager job is already backing up file backup. Action: Wait until the other Recovery Manager backup of this file is complete, then try the backup again. The string in the ORA-19675 file was modified during the proxy copy. Cause: A proxy backup of the specified file failed because the file was brought online or otherwise modified while the proxy backup was in progress. This file was offline or read-only when the backup was started, so the file was not placed in hot backup mode, so modifications are not allowed while the backup is in progress. grade. Action: Make another backup of this file. ORA-19676 One or more files failed during proxy backup or restore Cause: During a proxy backup or restore, errors were encountered while processing some files. Files for which no error message is displayed were processed successfully.

12-22 Error messages

Action: Examine the messages related to specific files to determine the cause of the problems. ORA-19700 device type exceeds maximum string length Cause: The indicated device type is invalid. Action: Provide a correct device type and retry the mapping. ORA-19701 device name exceeds maximum string length Cause: The supplied device name is invalid. Action: Provide a correct device name and retry the assignment. ORA-19702 device parameter exceeds maximum string length Cause: The device parameter exceeds the port-specific maximum length. Action: Correct the parameter and repeat the operation. ORA-19703 device command string exceeds maximum string length Cause: Device command string exceeds maximum length. Action: Correct the command and retry the operation. ORA-19704 filename exceeds maximum string length Cause: The specified filename, which was a parameter to a copy, backup, or restore operation, exceeds the maximum filename length for this operating system. User Response : Repeat the operation with a shorter file name. ORA-19705 Tag value exceeds maximum string character length Cause: During a copy or backup operation, the user supplied a tag value that was too long to fit in the file header. Action: Provide a shorter label and retry the operation. ORA-19706 Invalid SCN Cause: The input SCN is not a positive integer or is too large. Action: Check the incoming SCN and make sure it is a valid SCN. ORA-19707 invalid record block number - string Cause: The input number is negative or too large. Action: Check the input record block number and make sure it is a valid number of clauses in the CREATE DATABASE statement.

ORA-19400 to ORA-24279

12-23

ORA-19708 Log destination exceeds maximum string character length Cause: When starting a restore conversation, the user specified a log restore destination greater than the port-specific maximum. Action: Provide a shorter destination and retry the operation. The numeric parameter ORA-19709 must be a non-negative integer. Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional part. User Response : Provide a valid numeric parameter. ORA-19720 An error occurred while converting an OCI number to an SCN Cause: This is most likely due to an invalid SCN coming from an external file, such as an export file. Action: View other errors in the error stack to find the source of the problem. ORA-19721 Cannot find data file with absolute file number string in tablespace string Cause: Cannot find one of the data files that should be in the pluggable group. Action: Make sure that all data files are specified through the import command line option or parameter files. ORA-19722 data file string is wrong version Cause: The data file is the wrong version. Contains fewer or more changes than the desired version. Action: Make sure the correct data files are transported. Make sure the data file is copied while your tablespace is read-only. ORA-19723 Cannot re-create string of connected read-only data file Cause: The data file is connected as read-only. It cannot be recreated. Action: Use the ALTER DATABASE RENAME FILE command instead. ORA-19724 snapshot too old: snapshot time is older than file chain complement time Cause: snapshot's SCN is older than the SCN where the referenced data file is connected to the database. Action: Retry the query.

12-24 Error messages

ORA-19725 cannot acquire plugin enqueue Cause: Another ALTER DATABASE RESET COMPATIBILITY command might have been issued at the same time, preventing this process from acquiring plugin enqueue. Action: Repeat the operation. ORA-19726 cannot connect to data [string] at string level in database running at string compatibility level Cause: Some of the data in the pluggable array requires a higher compatibility level than what currently supported by the database. The string in brackets is the name of the compatibility type associated with the data. Action: Increase the value of the COMPATIBLE initialization parameter and retry the operation. ORA-19727 cannot connect the data from [string] to the string level in the database using Oracle string execution Cause: Some of the data in the pluggable array requires a higher compatibility level than the string level. Oracle executable version. The string in brackets is the name of the compatibility type associated with the data. Action: Update Oracle and retry the operation. ORA-19728 Data object number conflict between table string and partition string in table string Cause: The non-partitioned table has the same data object number as one of the partitions of the partitioned table . In this case, you cannot swap the table with the partition. Action: Use the ALTER TABLE MOVE PARTITION command to move the offending partition so that the partition gets a new data object number. Then repeat the operation. ORA-19729 The file string is not the initial version of the connected data file Cause: The file is not the initial version of the connected data file. Action: Use the correct initial version of the connected data file. ORA-19730 cannot convert connected data file string to offline Cause: As part of creating a read/write tablespace, we need to convert the data files that are connected to read-only. The file must be online. Action: Bring the data file online and try the operation again.

ORA-19400 to ORA-24279

12-25

ORA-19731 cannot apply change to chain of unverified connected data files Cause: Recovery was unable to verify the referenced data file based on information in the control file. Before finding this change vector for this file, recovery somehow missed the file conversion redo that was supposed to check the file. This can happen due to a corrupt or incorrect control file used for media recovery. Action: Use the correct control file and continue with the recovery. ORA-19732 Incorrect number of data files for table space chain Cause: The number of data files in the export file for the referenced table space is not the same as expected. This is most likely caused by a user editing the export file. Action: Use the correct export file and retry the operation. ORA-19733 The COMPATIBLE parameter must be a string or greater. Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Enabling the command would make the database incompatible with the version specified by the current COMPATIBLE parameter. Action: Shut down and reboot with a higher compatibility setting. ORA-19734 Bad SCN creation: control file expects converted connected data file Cause: When a table space is connected to a database, the table space is initially read-only. Oracle converts the header of connected data files (assigns them a newly created SCN) when the tablespace is first read/written. This error occurs when the build SCN in the file header is different from the build SCN in the control file, possibly because this is the initial version of the attached data file. Action: Restore the converted data file or continue to recover the data file. ORA-19735 Bad Create SCN - Control File Expected Initial Data File Connected Cause: When a tablespace is connected to a database, the tablespace is initially read-only. Oracle converts the header of connected data files (assigns them a newly created SCN) when the tablespace is first read/written. This error occurs when the SCN created in the file header is different from the SCN created in the control file, possibly because this is the converted data file. Action: Restore the initial version of the attached data file or continue with database recovery, which will recover the control file.

12-26 Error messages

ORA-19736 cannot connect a table space to a database using a different national character set Cause: Oracle does not support connecting a table space to a database using a different national character set. Action: Use import/export or download/upload to move the data. The skip_row procedure was called ORA-19999 Cause: The SKIP_ROW procedure was called, resulting in this error. Action: SKIP_ROW should only be called within a trigger or a procedure called by a trigger. ORA-20000 string Cause: The RAISE_APPLICATION_ERROR stored procedure was called, causing this error to be generated. Action: Correct the problem as described in the error message or contact your application or database administrator for more information. ORA-21000 error number argument to stringstring raise_application_error is out of range Cause: An attempt was made to specify a number outside the allowed range. Action: Use an error number in the range -20000 to -20999, inclusive. ORA-21001 The error number argument to stringstring raise_system_error is out of range Cause: An attempt was made to specify a number outside the allowed range. Action: Use an error number in the range -23300 to -24299 or -29300 to -29399, inclusive. ORA-21300 object option not installed Cause: The object option is not installed on this site. therefore, object types and other object characteristics are not available. Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact Oracle Customer Support if the object option needs to be purchased. ORA-21301 not initialized in object mode Cause: This function requires the OCI process to be initialized in object mode. Action: Specify the OCI_OBJECT mode when calling OCIInitialize().

ORA-19400 to ORA-24279

12-27

ORA-21500 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: This is the generic error number for OCI internal environment errors (client side). This indicates that the OCI environment has encountered an exceptional condition. Action: Report to Oracle Customer Support. The first argument is the internal error number. Program ORA-21501 could not allocate memory Cause: The operating system ran out of memory. Action: Take an action to make more memory available to the program. ORA-21503 Program Terminated Fatal Error Cause: A program is in an unrecoverable error state. Action: Report to Oracle Customer Support. ORA-21520 database server driver not installed Cause: The user attempted to access a database server through an OCI object-mode environment, but the driver required to support such access to the database server it was not installed or linked. Action: Verify that the appropriate driver for the database server has been installed/linked and entered into the server's driver table. ORA-21521 Maximum number of connections in OCI exceeded (object mode only) Cause: The user has exceeded the maximum number of connections (255) that an object mode OCI environment can support. Action: Close some of the existing unused connections before opening more connections. ORA-21522 Attempted to use an invalid connection in OCI (Object mode only) Cause: The user attempted to use an invalid connection or a connection terminated in an OCI (Object mode) environment, or the user attempted to dereference a REF obtained from a connection that was terminated. Action: Make sure the connection exists and is still valid. ORA-21523 Functionality not supported by the server (object mode only) Cause: The user tried to use a functionality that the server does not support. Action: Update the server.

12-28 Error messages

Object type mismatch ORA-21524 Cause: The object type of the object is different from the one specified. Action: Check the object type and correct it. ORA-21525 The attribute number or string (collection element in index) violated its constraint Cause: The attribute value or the collection element value violated its constraint. Action: Change the value of the attribute or collection element so that it meets your constraints. Constraints are specified as part of the schema information for the attribute or collection element. Boot Error ORA-21526 Cause: The boot sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value. Action: Verify that all NLS environment variables are well-formed. ORA-21560 argument string is null, invalid, or out of range Cause: The argument expects a valid non-null value, but the passed argument value is null, invalid, or out of range. Examples include when the positional or size argument LOB/FILE has a value outside the range 1 to (4 GB - 1), or when an invalid open mode is used to open a file, etc. Action: Check your program and correct the calling routine so that it does not pass a null, invalid, or out-of-range argument value. ORA-21600 Path expression too long Cause: The user-supplied path expression is too long. The path expression is used to specify the position of an attribute on an object. This error occurs when one of the intermediate elements in the route expression references an attribute of inner type. Therefore, the OCI function cannot proceed to process the rest of the elements in the path expression. User Response: Pass the correct path expression to find the attribute. ORA-21601 attribute is not an object Cause: The user attempts to perform an operation (only valid on an object) on an attribute of built-in type. An example of this illegal operation is dynamically setting a null structure on an attribute of inner type. Action: Avoid performing this operation on a built-in type attribute.

ORA-19400 to ORA-24279

12-29

The ORA-21602 operation does not support the specified type code. Cause: The user attempts to perform an operation that is not supported by the specified type code. User Response : Use the range of valid type codes supported by this operation. ORA-21603 Property ID [string] is invalid Cause: The specified property ID is invalid. Action: Specify a valid property ID. Valid property IDs are listed using OCIObjectPropId. The ORA-21604 [string] property is not a value or transient instance property. Cause: An attempt was made to get a property that only applies to persistent objects. Action: Check the lifetime and get this property for persistent objects only. ORA-21605 property [string] is not a property of value instances Cause: An attempt was made to get a property that only applies to persistent and transient objects. Action: Check the lifetime and get this property only for persistent and transient objects. ORA-21606 cannot free this object Cause: An attempt was made to free a persistent dirty object and the OCI_OBJECTFREE_FORCE flag was not specified. Action: Delete the lingering object or set the flag to OCI_OBJECTFREE_FORCE ORA-21607 memory cartridge service identifier not initialized Cause: Attempt to use the identifier without initializing it. Action: Initialize the memory cartridge service identifier. ORA-21608 Invalid duration for this function Cause: An attempt was made to use an invalid duration for this function. Action: Use a valid duration: a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For the duration of the call or the duration of the external procedure, use OCIExtProcAllocCallMemory. ORA-21609 Memory size is changed without first allocating Cause: An attempt was made to change the memory size without first allocating it.

12-30 Error messages

Action: Allocate memory before resizing it. ORA-21610 size [string] is invalid Cause: An attempt was made to resize memory with an invalid size. Action: Pass a valid size (must be a positive integer). ORA-21611 Invalid key length [string] Cause: An attempt was made to use an invalid key length. Action: The key length is invalid and the valid range is 0 to 64. ORA-21612 key is already in use Cause: Attempting to use a key that has already been used. Action: Use a new key that is not already in use. ORA-21613 key does not exist Cause: An attempt was made to use a key that does not exist. Action: Use a key that already exists. ORA-21614 Constraint violation for attribute number string Cause: Constraints were violated on the attribute. Action: Correct the value (of the attribute) to satisfy the constraints. Failed to copy ORA-21615 from an OTS instance (named or raw) Cause: See the following message. Action: Verify that no attribute values violate the constraints. Object ORA-21700 does not exist or is marked for tombstone Cause: The user attempted to perform an incorrect operation on a non-existent or tombstone object. Operations such as set, delete, and update cannot be applied to a non-existent or dropped object. Action: Reinitialize the reference to refer to an existing object or delete the object. ORA-21701 An attempt was made to release objects to different servers Cause: The user attempted to release objects to different servers in one function call. These objects are obtained by calling the callback functions provided by the program.

ORA-19400 to ORA-24279

12-31

Action: Avoid performing this operation. Object ORA-21702 was not instantiated or the instance was deleted in the cache. Cause: The user attempted to perform an incorrect operation on a transient object that is not instantiated in the object cache. Operations that cannot be applied to an uninstantiated transient object include removing or attaching that object. Action: Check the code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the object's allocation lifetime has expired. ORA-21703 cannot free an object that has not been modified Cause: See error message. Action: The object should not be washed. ORA-21704 cannot terminate cache or connection without flushing first Cause: See error message. Action: The transaction must be aborted or committed before ending the cache or the connection. ORA-21705 service context is invalid Cause: The service context provided by the user is invalid. Action: Set the service context. ORA-21706 duration does not exist or is invalid Cause: The duration number provided by the user is invalid. Action: Set the duration or use a correct preset duration. ORA-21707 pin lifetime is longer than allocation lifetime Cause: The user-supplied pin lifetime is longer than the allocation lifetime. This affects operations like fix and set default parameters. Action: Use a shorter pin duration or use a null duration. ORA-21708 Incorrect operation on a temporary object Cause: An attempt was made to perform an incorrect operation on a temporary object. Operations that cannot be applied to a transient object include release and lock. Action: Avoid performing this type of operation on a transient object.

12-32 Error messages

ORA-21709 cannot update an object that has been modified Cause: An attempt was made to update an object that was marked for delete, update, or insert (new). Action: Deselect the object before updating it. Argument ORA-21710 expects a valid memory address of an object Cause: The user-supplied memory address of the object is invalid. The user may have passed an invalid memory address to a function that expects a valid memory address of an object. Action: Pass a valid memory address of an object to the function. ORA-21779 Duration inactive Cause: An attempt was made to use a duration that has expired. Action: Avoid performing such an operation. ORA-22053 Overflow Error Cause: The result of this operation is above the Oracle number range. Action: Decrement the input values so that the result is in the Oracle number range. ORA-22054 Overflow Error Cause: The result of this operation is below the Oracle number range. Action: Increment the input values so that the result is in the Oracle number range. ORA-22055 unknown sign flag value [string] Cause: The signed flag used is neither OCI_NUMBER_SIGNED nor OCI_NUMBER_UNSIGNED. Action: Use OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as the signal flag. ORA-22056 Value [string] is divided by zero Cause: The supplied value is divided by zero. Action: Modify the value of the divisor to be non-zero. ORA-22057 invalid integer length [string] Cause: The integer length (that is, the number of bytes) to be converted to or from an Oracle number is invalid.

ORA-19400 to ORA-24279

12-33

Action: Use only an integer length of 1, 2, 4, or 8 bytes. ORA-22059 Buffer size [string] is too small: [string] is required Cause: The buffer to hold the resulting text string is too small. Action: Provide a buffer of the required size. Argument [string] ORA-22060 is an invalid or uninitialized number Cause: An invalid or uninitialized number was passed. Action: Use a valid number. To initialize the number, call OCINumberInit(). ORA-22061 invalid format text [string] Cause: The numeric format string to convert characters to or from an Oracle number is invalid. Action: Use a valid format string as documented in the Oracle Call Interface Programmer's Guide. ORA-22062 Invalid input string [string] Cause: The text string to convert to numbers is invalid. Action: Use a valid input string as documented in the Oracle Call Interface Programmer's Guide. ORA-22063 read negative value [string] as unsigned Cause: An attempt was made to convert a negative number to an unsigned integer. Action: Use the ORLTSB sign flag to convert a signed number. ORA-22064 Invalid NLS parameter string [string] Cause: The NLS parameter string to convert characters to or from an Oracle number is invalid. Action: Use a valid format string as documented in the Oracle Call Interface Programmer's Guide. Translation of number ORA-22065 to text with the given format causes an overflow Cause: Rounding done due to the given string format causes an overflow. Action: Change the format of the string so that an overflow does not occur. ORA-22130 Buffer size [string] is less than required size [string] Cause: The size of the buffer into which the REF hexadecimal string should be written is too small.

12-34 Error messages

Action: Provide a buffer of the required size. ORA-22131 Length of hexadecimal string is zero Cause: The length of the supplied hexadecimal string must be greater than zero. Action: Specify a length greater than zero. ORA-22132 Hexadecimal string does not match a valid REF Cause: The supplied hexadecimal string is invalid. Action: Provide a valid hexadecimal string that was previously returned by calling OCIRefToHex(). ORA-22140 The specified length [string] must be in the range 0 to [string] Cause: The provided resize size is invalid. Action: Make sure that the size provided is within the required range. ORA-22150 variable length array is not initialized Cause: An uninitialized variable length array is being operated on. User Response : Initialize the variable length array before calling this function. ORA-22151 cannot resize a non-zero variable length array to 0 elements Cause: An attempt was made to resize a non-zero variable length array to 0 elements. Action: Specify a non-zero size. ORA-22152 destination variable length array is not initialized Cause: The variable length array on the right side of an assignment or the destination array of an attachment is not initialized. User Response : Initialize the target variable length array before calling this function. ORA-22153 Source variable length array is not initialized Cause: The variable length array on the left side of an assignment or the source array of an attachment is not initialized. User Response : Initialize the target variable length array before calling this function. ORA-22160 element at index [string] does not exist Cause: The collection element at the given index does not exist.

ORA-19400 to ORA-24279

12-35

Action: Specify the index of an existing element. ORA-22161 typecode [string] is invalid Cause: The supplied typecode is invalid. User Response : Use one of the type codes listed in OCITypeCode. Element ORA-22162 at index [string] was previously deleted Cause: An attempt was made to delete a non-existent collection element. Action: Check for the existence of the element before calling this function. ORA-22163 The collections on the left and right sides are not of the same type Cause: The collections on the left and right sides are not of the same type. Action: Make sure the same collection type is passed to the left and right sides of this function. ORA-22164 Item delete operation not allowed for variable length array Cause: An attempt was made to delete an element from a variable length array. User Response : Make sure the collection is not a variable length array before calling this function. ORA-22165 The supplied index [string] must be in the range 0 to [string] Cause: The supplied index is not in the required range. Action: Make sure the given index is in the required range. ORA-22166 collection is empty Cause: The given collection is empty. Action: Test that the collection is empty before calling this function. ORA-22167 Slice size provided [string] must be less than or equal to [string] Cause: Slice size provided is greater than current collection size. User Response : Make sure that the supplied size is less than or equal to the size of the collection before calling this function. Invalid LOB locator specified ORA-22275 Cause: One of the following:

12-36 Error messages

The LOB locator was never initialized.

The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator.

The locator is for BLOB/CLOB/NCLOB and the routine expects a BFILE locator.

An attempt was made to update the LOB in a trigger body: LOBs in trigger bodies are read-only.

The locator was never enabled for the buffer.

It is not an updated locator, but is used for a write/flush operation.

Action: To (1) enable the browser for buffering; (2) ensure that only an updated locator is used for a LOB update operation. ORA-22277 cannot use two different locators to modify the same LOB Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators. Action: When using the LOB buffer, modify the LOB only through a LOB locator. ORA-22278 should update the LOB via LOB buffers only. Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Therefore, updating the LOB by means other than LOB buffers is not allowed. Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, the buffers associated with this LOB must be freed as needed or the buffer must be disabled. Once this is done, issue the command again. ORA-22279 cannot perform operation with LOB buffering enabled Cause: Operation attempt is not allowed when LOB buffering is enabled. Action: If the operation is required, the LOB buffer should not be used. In this case, flush the buffers associated with the input LOB locator as needed, disable buffering on the input LOB locator, and reissue the command.

ORA-19400 to ORA-24279

12-37

ORA-22280 No more buffers available for operation Cause: One of the following: 1.

All buffers in the buffer pool have been used by previous operations.

An attempt was made to free a LOB without a previous buffered update operation.

Action: For (1), release the LOBs through the locator that is being used to update the LOB. For (2), write to the LOB through a buffering-enabled pager before attempting to flush the buffers. ORA-22281 cannot perform the operation with an updated locator Cause: The input locator has buffering enabled and was used to update the LOB value via the LOB buffering subsystem. The modified buffer has not been freed since the write by the input locator; therefore, the incoming locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB can be used to modify the LOB value through the LOB buffer subsystem. Action: Depending on whether modifications made through the input locator to the LOB buffering subsystem are to be written to the server, either clear the buffer to write the modifications or disable buffering in the locator to discard the modifications. Then reissue the command. ORA-22282 Non-contiguous append enabled LOB to an illegal buffer Cause: The buffer write operation has an input offset value of more than one byte or character after the end of the LOB. Action: Specify an input offset value that is exactly one character or one byte greater than the length of the LOB you are trying to update via a buffer write operation. ORA-22285 Missing directory or file for string operation Cause: An attempt was made to access a directory that does not exist, or an attempt was made to access a file in a directory that does not exist. Action: Make sure that a system object corresponding to the specified directory exists in the database dictionary or make sure the name is correct. ORA-22286 Insufficient privileges on the file or directory to perform the string operation Cause: The user does not have the required access privileges on the file and/or directory alias for the operation.

12-38 Error messages

Action: Ask the database or system administrator to grant the necessary privileges on the directory and/or file alias. ORA-22287 directory invalid or modified during chain operation Cause: The directory alias used for the current operation is invalid if it is accessed for the first time or has been modified since last by the database administrator access. Action: If you are accessing this directory for the first time, provide a valid directory name. If you were able to open a file in that directory before this error occurred, close the file and retry the operation with a valid directory alias modified by the database administrator. Oracle recommends that directories only be changed during idle time. ORA-22288 File or LOB operation string failed Cause: The attempted operation on the file or LOB failed. Action: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are defined for the specified operation. If the error persists, report the error to the database administrator. ORA-22289 cannot perform a string operation on an unopened file or LOB Cause: The file or LOB is not open to perform the required operation. Action – Precede the current operation with a successful open operation on the file or LOB. The ORA-22290 operation would exceed the maximum number of open files or LOBs. Cause: The number of open files or LOBs has reached the maximum limit. Action: Close some of the open files or LOBs and try the operation again. ORA-22291 There are open LOBs at the time of transaction commit Cause: An attempt was made to commit a transaction with the LOBs open at the time of transaction commit. Action: Close the LOBs before committing the transaction. ORA-22292 Cannot open a LOB in read/write mode without a transaction Cause: An attempt was made to open a LOB in read/write mode before a transaction was started.

ORA-19400 to ORA-24279

12-39

Action: Start a transaction before opening the LOB in read/write mode. Ways to start a transaction include issuing a SQL DML or SELECT FOR UPDATE command. Opening the LOB in read-only mode does not require a transaction. ORA-22293 LOB already open in the same transaction Cause: An attempt was made to open a LOB that is already open in this transaction. Action: Close the LOB before trying to reopen it. ORA-22294 cannot update a LOB opened in read-only mode Cause: An attempt was made to write or update a LOB opened in read-only mode. Action: Close the LOB and reopen it in read/write mode before attempting to write or update the LOB. ORA-22303 type "string".."string" not found Cause: An attempt was made to get information for a type that could not be found. Action: Check that the schema is correct and that the type was created correctly. ORA-22304 input type is not an object type Cause: An attempt was made to get the supertype information for a non-object type. Action: Pass only one type of object. ORA-22305 "string" attribute/method/parameter not found Cause: The type element with the given name was not found in the type. Action: Check if the type element exists. ORA-22306 type "string".."string" already exists Cause: An attempt was made to create a type that already exists. Action: Check that the type was not created before this. The ORA-22307 operation must be on a user-defined type. Cause: An attempt was made to perform an operation that is only allowed on a user-defined type, and the type is not a user-defined type. Action: Verify that only user-defined types are being operated.

12-40 Error messages

ORA-22309 attribute with name "string" already exists. Cause: An attempt was made to create an object type where more than one attribute has the same name. Action: Verify that all attribute names are unique. Write ORA-22311 for attribute "string" does not exist Cause: The attribute type does not exist. Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the attribute type creation in the DDL transaction. ORA-22313 cannot use two versions of the same type of "string" Cause: The version of this type conflicts with the version of this type used by another library linked to the application. An application can only use one version of a type. Action: Check that the libraries linked to this application use the same type versions. ORA-22314 Method information does not match in ALTER TYPE Cause: The method number or method signature does not match the original type declaration. This is not supported. Action: Make sure that the method signature remains identical to the previously declared method. Do not discard existing methods. ORA-22315 type "string" does not contain a map or command function Cause: The input type does not contain a map or command function, so return is not possible. Action: Add an order or map function to the type or catch this error. ORA-22316 input type is not a collection type Cause: An attempt was made to get information for collection types on an unnamed collection type. User Response : Use a named collection type for the function. Number type code ORA-22317 is not legal as a number type Cause: An attempt was made to use a number type code that is not valid. Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE,

ORA-19400 to ORA-24279

12-41

OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL. ORA-22318 input type is not an array type Cause: An attempt was made to get the number of elements for a non-array type. Action: Pass only one named collection type that is an array. ORA-22319 type attribute information changed in ALTER TYPE Cause: The type attribute information does not match the original type declaration when the type was changed. Attributes cannot be changed during ALTER TYPE. Only new methods can be added. Action: Verify that all type changes are legal. ORA-22321 method does not return any results Cause: OCITypeResult() was called on a method that does not return any results. Action: Check that you are passing the correct method descriptor or that the method creation was successful. ORA-22369 Invalid parameter found in method string Cause: An invalid parameter is being passed to this method from SYS.RowType or SYS.RowSet. User Response : Check the parameters that are passed to this method and make sure that they are allowed. ORA-22370 Method string Incorrect use Cause: This method of SYS.RowType or SYS.RowSet is being used incorrectly. Action: Check the documentation for correct usage. ORA-22600 encountered VARRAY 8.0.2 (Beta) data that cannot be processed. Cause: Production Oracle8 (8.0.3 and later) encountered some VARRAY data created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process this VARRAY data. Action: Remove the VARRAY data from the table by dropping the table, dropping the rows or dropping the VARRAY columns, then reinsert the VARRAY data. No script or tool is provided to help automate this conversion.

12-42 Error messages

ORA-22601 TDS selector context [string] not initialized Cause: An attempt was made to use the TDS selector context without initializing it. Action: Use OCIPicklerTdsCtxInit to initialize the context. ORA-22602 TDS pickler identifier [string] is malformed Cause: An attempt was made to use the TDS pickler identifier without initializing or building it. Action: Use OCIPicklerTdsInit to initialize the handle before building it. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed. ORA-22603 unable to add attribute to already built TDS identifier Cause: An attempt was made to add an attribute to the already built TDS. Action: Use a TDS handle initialized but not yet built. ORA-22604 TDS identifier already generated Cause: An attempt was made to generate the TDS that was already generated. Action: Use a TDS identifier that has been initialized but not yet generated. ORA-22605 FDO identifier [string] is not initialized Cause: An attempt was made to use an uninitialized FDO identifier. Action: Use OCIPicklerFdoInit to initialize the FDO handler. ORA-22606 Pickler image identifier [string] is malformed Cause: An attempt was made to use the image identifier without initializing/building it. Action: Use OCIPickleImageInit to initialize the handle before it is built. Use OCIPickleImageGenerate to generate the image before its attributes can be accessed. Image identifier ORA-22607 already generated Cause: An attempt was made to generate the image that was already generated. Action: Use an image handle initialized but not yet generated. ORA-22608 cannot add attribute to already generated image id Cause: An attempt was made to add an attribute to already created image.

ORA-19400 to ORA-24279

12-43

Action: Use an image handle initialized but not yet created. ORA-22609 error string during FDO initialization Cause: An error occurred during FDO initialization. Action – Performs an action based on the specified error. ORA-22610 error adding scalar to image identifier Cause: An error occurred while adding a scalar attribute to the image identifier. Action: Make sure the image handle is initialized before adding the scalar. ORA-22611 TDS version not recognized Cause: The wrong TDS identifier was passed. Action: Make sure that the image identifier is initialized with the correct TDS. ORA-22612 TDS does not describe a collection TDS Cause: The compilation/collection access routines are in an image, but the TDS does not describe this collection TDS. Action: Ensure that a collection TDS is used before calling the collection routines on the image handle. ORA-22613 buflen does not match scalar size Cause: BUFLEN is incorrect. Action: Make sure that BUFLEN is correct and matches the size of the scalar. ORA-22614 error creating collection on image Cause: An error occurred while creating the collection. Action: Ensure that the image handler is initialized and that OCIPicklerImageCollBegin is called to start the collection. The ORA-22615 attribute is not a collection. Cause: The collection routine is called on an attribute that is not a collection. Action: Make sure the attribute is a collection. Image ORA-22616 is not in Oracle 8.1 format Cause: The function being called only applies to 8.1 images. Action: Make sure the image is in 8.1 format. ORA-22617 error accessing image id collection Cause: An error occurred while accessing the collection on image id.

12-44 Error messages

Action: Make sure that the image was initialized correctly and that the collection was created correctly. The ORA-22618 attribute is a BAD NULL on the image identifier. Cause: The attribute in question is likely the attribute of an embedded null image. Action: Make sure that the attribute number is valid or is NULL or NOT NULL. ORA-22619 All collection items already accessed Cause: An attempt was made to access a collection item after all the collection items had already been accessed. Action: This function should no longer be called. ORA-22620 The buffer size is too small to hold the value Cause: The buffer size is not large enough to hold the value. Probably, when doing character set conversion, a larger buffer is needed. Action: Move to a larger buffer. If the client's character set format differs from the server's, the conversion may result in 4X expansion. ORA-22621 error while transferring an agent object. Cause: An error was returned from the pickler routines on the agent side. Action: Contact Oracle Customer Support. ORA-22800 invalid user-defined type Cause: An attempt was made to use an incomplete type as a constructor. User Response: Complete the type definition before using it in a query. Invalid object line variable ORA-22801 Cause: The specified object line variable is not available in the name resolution scope. User Response: Verify that the specified object row variable is correct or use a scoped visible object row variable. ORA-22802 cannot update attributes of compressed ADTs in SQL Cause: An attempt was made to update an attribute of a compressed ADT column in an UPDATE statement. Action: Use an unpacked ADT column OR update the entire ADT.

ORA-19400 to ORA-24279

12-45

The ORA-22803 object type contains zero attributes. Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context. Action: Specify a valid object type. ORA-22804 Remote operations are not allowed on object tables or columns of user-defined type Cause: An attempt was made to perform queries or DML operations on remote object tables or columns of remote tables whose type is object, REF, nested table, or VARRAY . User Response: Remove the reference to remote tables in the statement. ORA-22805 cannot insert a NULL object into object tables or nested tables Cause: An attempt was made to insert a NULL object into an object table or nested table. User Response : Make sure that a non-null object is inserted into the table, or insert an object with attributes whose values are NULL. ORA-22806 is neither an object nor a REF Cause: An attempt was made to extract an attribute from an element that is neither an object nor a REF. Action: Use an object or element type of type REF and retry the operation. ORA-22807 cannot resolve to a scalar type or a collection type. Cause: Invalid use of a non-scalar element (eg object type). Action: Change the data type of the element and retry the operation. ORA-22808 REF dereferencing not allowed Cause: An attempt was made to access the attributes of an object type by dereferencing a REF element. Action: Make the element an object type instead of a REF for an object type. ORA-22809 Missing attribute Cause: An attempt was made to access a missing attribute of an object type. Action: Check the attribute reference to see if it is valid. Then repeat the operation.

12-46 Error messages

ORA-22810 cannot modify object attributes with REF dereferencing Cause: An attempt was made to modify an object's attributes by dereferencing a REF column in an UPDATE statement. User Response : Update the table containing the object that REF points to, or change the REF column to an object type column. ORA-22811 cannot access compressed ad attributes in SQL Cause: Attempt to access an attribute of a compressed ADT table/column. Action: Use an unzipped ADT or retrieve the full ADT. ORA-22812 cannot reference nested table column store table Cause: An attempt to access nested table column store table is not allowed in the given context. User Response : Issue the statement on the parent table that contains the nested table column. The value of operand ORA-22813 exceeds the system limits. Cause: The value of the object or collection was too large. The size of the value may have exceeded 30k in a SORT context, or the size may be too large for available memory. Action: Choose another value and repeat the operation. ORA-22814 The value of the attribute or element is greater than that specified in the type. Cause: The value supplied for the type attribute of the object or collection element exceeded the size specified in the type declaration. Action: Choose another value and repeat the operation. ORA-22816 Function not supported in RETURNING clause Cause: The RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and dereferencing within the return clause. Action: Use separate SELECT statements to get the values. ORA-22817 subquery not allowed in default clause Cause: An attempt was made to use a subquery in the column's default clause expression. User Response : Remove the subquery from the default clause.

ORA-19400 to ORA-24279

12-47

ORA-22818 Subquery expressions not allowed here Cause: An attempt was made to use a subquery expression where it is not supported. User Response: Rewrite the statement without the subquery expression. ORA-22819 Input value scope does not match target scope Cause: An attempt was made to operate on a REF value scoped to a different table than expected. Action: Use a scoped REF to the expected table and retry the operation. ORA-22850 Duplicate LOB storage option specification Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once. Action: Specify all LOB storage options only once. ORA-22851 Invalid CHUNK LOB storage option value Cause: The specified CHUNK LOB storage option value must be an integer. Action: Choose an appropriate integer value and repeat the operation. ORA-22852 Invalid PCTVERSION LOB storage option value Cause: The PCTVERSION LOB storage option value specified must be an integer. Action: Choose an appropriate integer value and repeat the operation. ORA-22853 Invalid LOB storage option specification Cause: A LOB storage option was not specified. Action: Specify CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause. ORA-22854 Invalid option for LOB storage index Cause: A valid LOB storage index option was not specified. Action: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index. ORA-22855 Optional name for LOB storage segment incorrectly specified Cause: The optional name for the LOB storage segment was specified with multiple columns in the column list.

12-48 Error messages

Action: Specify the LOB storage for each column with optional names only. ORA-22856 unable to add columns to object tables Cause: An attempt was made to add columns to an object table. Object tables cannot be modified to add columns, since their definition is based on an object type. Action: Create a new type with additional attributes and use the new type to create a table of objects. The new object table will have the desired columns. ORA-22857 cannot modify object table columns Cause: An attempt was made to alter the object table by modifying existing columns. An object table cannot be modified to modify existing columns, since it is based on an object type. The table definition must be synchronized with the corresponding type. Action: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns. ORA-22858 invalid data type change Cause: An attempt was made to change the column type to object, REF, nested table, VARRAY, or LOB type. Action: Create a new column of the desired type and copy the data from the current column to the new type using the appropriate type constructor. ORA-22859 invalid column modification Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type. Action: Create a new column of the desired type and copy the data from the current column to the new type using the appropriate type constructor. Expected ORA-22860 Object Type Cause: An attempt was made to create an object table using a non-object type or to create a column that is a REF to a non-object type. User Response : Use a valid object type in the table or column definition. ORA-22861 invalid user-defined type Cause: An attempt was made to create an object column or table of a non-existent type. User Response : Specify a valid type in the table or column definition.

ORA-19400 to ORA-24279

12-49

ORA-22862 specified object identifier does not match existing object identifier Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type with the same name. Action: Specify the correct object identifier or leave it out of the declaration. ORA-22863 synonym for data type string.string not allowed Cause: A synonym specification for a data type is not supported. User Response: Do not use the synonym for the data type. ORA-22864 cannot ALTER or DROP LOB indices Cause: An attempt was made to ALTER or DROP a LOB index. Action: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column. ORA-22865 More than one column specified Cause: An attempt was made to specify multiple columns where only one is allowed. Action: Specify a single column and retry the operation. ORA-22866 default character set is variable width Cause: A character LOB was defined, but the default character set does not have a fixed width. Action: Make sure the character set has a fixed width before defining character LOBs. ORA-22868 Table with LOB contains segments in different table spaces Cause: An attempt was made to drop a table space that contains the segments for the LOB columns of a table, but does not contain the table segment. Action: Find tables with LOB columns that have non-table segments in this table space. Drop these tables and reissue the drop table space. ORA-22869 Type dependency hierarchy depth exceeds maximum Cause: The type dependency hierarchy was designed to have a depth greater than 1024. Action: Restructure the type dependency hierarchy to a shallower depth.

12-50 error messages

ORA-22870 ALTER TYPE with REPLACE option of a non-object type Cause: An attempt was made to perform ALTER TYPE with the REPLACE option of a non-object type. Action: First drop the non-object type and then recreate it as an object type. ORA-22871 ALTER TYPE with REPLACE not allowed for pure incomplete types Cause: An attempt was made to perform ALTER TYPE with the REPLACE option for a pure incomplete type. Action: Fully define the original type before using the ALTER TYPE option with REPLACE. ORA-22872 OID INDEX clause not allowed on tables with primary key based object ids Cause: An attempt was made to create an OID INDEX on a table with primary key based object ids. Action: Remove the OID INDEX clause. ORA-22873 Primary key not specified for primary key based object table Cause: An attempt was made to create a primary key based object table without specifying a primary key. Action: Specify a primary key and retry the operation. ORA-22874 Attribute "string" is not part of type "string" Cause: The attribute specified in the USER_DEFINED clause is not an attribute of type REF. Action: Make sure that the name specified in the USER_DEFINED clause is the name of a valid attribute of type REF. ORA-22875 cannot remove the primary key from an object table whose object identifier is based on the primary key Cause: An attempt was made to remove the primary key from an object table that has an object identifier based on the primary key. User Response : Remove the remove primary key clause.

ORA-19400 to ORA-24279

12-51

ORA-22876 This user-defined type is not allowed or cannot be used in this context Cause: An attempt was made to create a type of user-defined type that is not allowed or an attempt was made to create table columns or use the default constructor with a type in which they are not compatible. Action: Make sure the type is allowed in this context. ORA-22877 Invalid option specified for a HASH partition or subpartition of a LOB column Cause: One or more invalid options were found while parsing the physical attributes of a LOB partition or subpartition. The LOB partition is in a HASH partitioned table or the LOB subpartition is in a HASH subpartitioned table. TABLESPACE is the only valid option for a HASH partition or subpartition. Action: Remove invalid options. ORA-22878 Duplicate LOB partition or subpartition specified Cause: An attempt was made to specify a partition or subpartition that was already specified for the LOB column. Action: Remove the duplicate specification. ORA-22879 cannot use LOB INDEX clause for partitioned tables Cause: An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table. Action: Remove the LOB INDEX clause. ORA-22880 Bad REF Cause: An invalid REF was accessed. Action: Modify the REF and retry the operation. ORA-22881 REF pending Cause: The object corresponding to the REF accessed does not exist. Action: Make sure the REF value points to an existing object. Error creating object ORA-22882 Cause: Could not create object in database. Action: Verify that the object table exists and that the size of the object is not too large. Then repeat the operation.

12-52 Error messages

Could not delete object ORA-22883 Cause: The object could not be deleted from the database. Action: Check if the object table exists. Then repeat the operation. Object Modification Failed ORA-22884 Cause: Could not modify object in database. Action: Verify that the object table exists and that the size of the object is not too large. Then repeat the operation. ORA-22885 cannot get REF for a non-persistent object Cause: An attempt was made to get a REF for something that is not an object in an object table. REFs can only be obtained for objects in object tables. User Response: Rewrite the query to get REF values from the object tables. ORA-22886 Scoped table "string" in schema "string" is not an object table Cause: The scoped table specified for a REF column is not an object table. User Response : Check that the scoped table is an object table. Then repeat the operation. The ORA-22887 type of the REF column is not the same as the type of the scope table Cause: The type specified for the REF column and the type specified for the scope table are different. Action: Make sure that the types of a REF column and its scope table are the same. ORA-22888 Duplicate SCOPE clauses for a REF column Cause: Multiple SCOPE clauses were specified for a single REF column. User Response : Remove the duplicate SCOPE clauses and retry the operation. ORA-22889 REF value does not point to scope table Cause: An attempt was made to insert a REF value that does not point to the scope table. Action: Make sure the REF values point to the scope table. ORA-22890 cannot specify name for constraint REF column Cause: An attempt was made to specify a constraint name for a constraint on a REF column. User Response : Remove the name from the constraint and retry the operation.

ORA-19400 to ORA-24279

12-53

ORA-22891 cannot have multiple columns in REF constraint Cause: An attempt was made to specify multiple columns in a single REF constraint. User Response : Specify separate constraints for each column and try again. ORA-22892 Scoped table "string" does not exist in schema "string" Cause: The scoped table specified for a REF column does not exist. User Response : Check that the scoped table exists and retry the operation. The ORA-22893 constraint can only be specified for REF columns. Cause: The specified constraint does not apply to non-REF columns. User Response : Remove the constraint and retry the operation. ORA-22894 cannot add a constraint to existing unscoped REF columns of non-empty tables Cause: An attempt was made to add a constraint to existing unscoped REF columns of a table that contains one or more rows. User Response : Drop the constraint specification or add the constraint after emptying the table. ORA-22895 Referenced table "string" in schema "string" is not an object table Cause: The referenced table specified for a REF column is not an object table. User Response : Make sure the referenced table is an object table. Then repeat the operation. ORA-22896 cannot have a referential constraint and a scope on column REF "string" Cause: The REF column has a referential constraint and a scope. A referential constraint implies a scope constraint. User Response : Remove the referential or scope constraint and retry the operation. ORA-22897 No scope clause specified for user-defined REF column "string" Cause: The user-defined REF column does not have a scope constraint. User Response : Specify a scope constraint for the user-defined REF column and retry the operation.

12-54 Error messages

ORA-22898 existing scope clause in "chain" points to a different table than the one named in the referential constraint Cause: The table named in the referential integrity constraint is different from the scope table of the REF column. User Response : Specify the REF column scope table in the referential integrity constraint and retry the operation. ORA-22899 unable to specify scope and row id constraint on reference column Cause: An attempt was made to specify a scope and row id constraint on a REF column. User Response : Remove the ROWID or scope constraint and retry the operation. ORA-22900 The item in the SELECT list of the subquery is not a collection type Cause: The subquery must select a nested table or VARRAY element. User Response: Change the subquery to SELECT a nested table or VARRAY element. ORA-22901 cannot compare nested table or VARRAY or LOB attributes of an object type Cause: An attempt was made to compare nested table or VARRAY or LOB attributes of an object type in the absence of a MAP or ORDER method. Action: Define a MAP or ORDER method for the object type. ORA-22902 CURSOR expression not allowed Cause: The CURSOR in a subquery is only allowed in the top-level SELECT list of a query. Action: Remove the CURSOR expression and retry the operation. ORA-22903 MULTISET expression not allowed Cause: MULTISET expressions are only allowed within a CAST for a nested table or VARRAY type. Action: Place the MULTISET expression (subquery) inside a CAST for a nested table or VARRAY type. ORA-22904 Invalid reference to a nested table column Cause: An invalid reference was made to a nested table column. User Response : Remove the invalid reference to the column from the nested table and try again.

ORA-19400 to ORA-24279

12-55

ORA-22905 unable to access rows of non-nested table element Cause: An attempt was made to access rows of an element whose type is not known at parse time or is not of a nested table type. User Response : Use CAST to cast the element to a nested table type. ORA-22906 cannot perform DML on a nested table view column or expression Cause: An attempt was made to perform DML on a nested table view column or expression where a nested table column of a base table was expected. User Response: Only the nested table column of a base table is allowed in the DML. ORA-22907 Invalid CAST for a type that is not a nested table or VARRAY Cause: A CAST was attempted for a type that is not a nested table or VARRAY. User Response: Specify CAST again for a nested table or type VARRAY. ORA-22908 NULL table value reference Cause: The evaluation of the nested table column or subquery resulted in a NULL value, indicating a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance. User Response : Ensure that the evaluation of the THE subquery or the nested table column results in a single non-null table instance. If it occurs in the context of an INSERT statement where the THE subquery is the target of an insert, be sure to create an empty nested table instance by updating the nested table column of the parent table row by specifying an empty nested table constructor . ORA-22909 VARRAY maximum limit exceeded Cause: The total number of elements used in the VARRAY construction exceeds the specified VARRAY limit. Action: Do not use more than the specified limit of elements for the VARRAY construction. ORA-22910 cannot specify schema name for nested tables Cause: The table name was qualified with the schema name in the column (or attribute) store clause of the nested table. User Response: Re-specify the nested table item storage clause without schema name qualification. By default, the storage table for the nested table element is created in the same schema as the containing table.

12-56 Error messages

ORA-22911 duplicate storage specification for nested table element Cause: The storage clause is specified more than once for the NESTED TABLE column. User Response : Remove the duplicate storage specification. ORA-22912 The specified column or attribute is not a nested table type Cause: The store clause is specified for a column or attribute that is not a column or attribute of a nested table. User Response : Specify a valid nested table column or attribute. ORA-22913 must specify the table name for the nested table column or attribute. Cause: The Store clause is not specified for a column or attribute of the nested table. User Response : Specify the nested table store clause for the nested table column or attribute. ORA-22914 DROP of nested tables is not supported Cause: An attempt was made to DROP a nested table. User Response: Nested tables cannot be dropped explicitly. Nested tables can only be dropped by dropping the parent containing table. ORA-22915 cannot ALTER nested tables to add/modify columns Cause: An attempt was made to add or modify columns from a nested table. Columns cannot be added or modified for a nested table. Action: Instead, change the nested table column of the parent table to cause that change. ORA-22916 cannot perform an exact FETCH on a query with nested cursors Cause: Exact FETCH was specified in a query which is not allowed if the query returns cursors. Action: Do not use an exact FETCH. ORA-22917 use VARRAY to define the store clause for this column or attribute Cause: VARRAY is not used to define the store clause for the VARRAY column or attribute. Action: Specify VARRAY before the column store clause and resubmit the statement.

ORA-19400 to ORA-24279

12-57

ORA-22918 The specified column or attribute is not of type VARRAY Cause: An attempt was made to define a VARRAY storage clause for a column or attribute that is not of type VARRAY. Action: Specify the VARRAY storage clause for a VARRAY column or attribute. ORA-22919 Hanging REF error or failed lock object for request without waiting Cause: The error can be one of the following: the object corresponding to the REF does not exist, or the object was locked by another user and the lock with the request without wait failed. Action: Make sure the REF value points to an existing object, or issue a lock request without the nowait option. ORA-22920 row containing LOB value is not locked Cause: The row containing LOB value must be locked before updating the LOB value. User Response: Lock the row that contains the LOB value before updating the LOB value. ORA-22921 The input buffer size is less than the requested amount Cause: The buffer size is not large enough to hold the requested amount of data. Action: Verify that the number of bytes/characters specified in the input amount parameter is not greater than the number of bytes specified in the input buffer size parameter. Allocate more space for the input buffer if necessary. ORA-22922 LOB value does not exist Cause: The LOB value associated with the input locator does not exist. The locator information does not refer to an existing LOB. Action: Repopulate the locator by issuing a SELECT statement and retry the operation. ORA-22923 The amount of data specified in the stream LOB write is 0 Cause: An attempt was made to write the LOB value through the stream engine (i.e. unlimited write), but the amount of input data for the stream was specified as 0. Therefore, the user is attempting to write 0 bytes to the LOB value. Action: Write more than 0 bytes to the LOB value. ORA-22924 snapshot too old Cause: The version of the LOB value required for a consistent read has already been superseded by another writer.

12-58 Error messages

Action: Use a larger version group. ORA-22925 operation would exceed the maximum size allowed for a LOB value Cause: An attempt was made to write too much data to the LOB value. LOB size is limited to 4 gigabytes. Action: Start writing at a smaller LOB offset or write less data to the LOB value. ORA-22926 The specified cut length is greater than the length of the current LOB value Cause: The input length for cutting the LOB value is greater than the length of the current LOB value. Action: It may not be necessary to trim the LOB value because it is already smaller than the specified trim length. Or, if you really need to trim the LOB value, use a shorter trim length. ORA-22927 Bad LOB locator specified Cause: One of the following: 1.

The LOB locator was never initialized.

The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator.

The locator is for BLOB/CLOB/NCLOB and the routine expects a BFILE locator.

An attempt was made to update the LOB in a trigger body: LOBs in trigger bodies are read-only.

Action: For (1), initialize the LOB locator by selecting on the locator variable or by setting the LOB locator to be empty. For (2) and (3), pass the correct locator type to the routine. For (4), remove the code from the trigger body that updates the LOB value. ORA-22928 Invalid privilege on directories Cause: An attempt was made to grant or revoke an invalid privilege on a directory. Action: Only CREATE, DELETE, READ, and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges. ORA-22929 Invalid or missing directory name Cause: The required directory name is invalid or missing.

ORA-19400 to ORA-24279

12-59

Action: Specify a valid name. ORA-22930 directory does not exist Cause: An attempt was made to access a directory that does not exist. Action: Make sure the name is correct. ORA-22950 cannot SORT objects without MAP or ORDER method Cause: An object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons. Action: Define a MAP or ORDER method for the object type. ORA-22951 NULL returned by ORDER method Cause: The ORDER method used to compare two object values returned NULL, which is not allowed. User Response: Redefine the ORDER method so that it does not return NULL. ORA-22970 Name does not match an object view Cause: The expression is not a view name or the specified name does not match an object view. Action: Replace the expression with the name of an object view. ORA-22971 Invalid data type for PRIMARY KEY based object identifier Cause: When creating an object view, the data type of an expression in the WITH OBJECT OID clause is not allowed for the PRIMARY KEY based OID. User Response: Replace the expression with one of the appropriate scalar data type. ORA-22972 NULL value not allowed in object identifier based on PRIMARY KEY Cause: A value constituting the object identifier based on PRIMARY KEY is NULL. Action: Ensure that expressions in the MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL. ORA-22973 object identifier size exceeds maximum allowed size Cause: The size of the PRIMARY KEY based object identifier of an object view exceeded the maximum size of 65535 bytes. Action: Specify PRIMARY KEY minor or minority attributes in the OID clause of the WITH object when creating the object view.

12-60 error messages

ORA-22974 Missing WITH OBJECT OID clause Cause: The WITH OBJECT OID clause was not specified when creating an object view. User Response: Specify the WITH OBJECT OID clause. ORA-22975 cannot create a PRIMARY KEY based REF for this object view Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY based object identifier. A REF based on PRIMARY KEY cannot be created for such a view. User Response: Specify an object view that has a PRIMARY KEY based object identifier in the MAKE_REF function. ORA-22976 Incorrect number of arguments to MAKE_REF Cause: The number of arguments to MAKE_REF is different from the number of PRIMARY KEY attributes of the object view. Action: Specify all the necessary arguments for MAKE_REF. ORA-22977 missing or invalid attribute Cause: The attribute name is missing from the WITH OBJECT OID clause or invalid. Action: Specify a valid attribute of the object type of the object view. ORA-22978 only simple attribute name allowed in WITH OBJECT OID clause Cause: An attempt was made to specify a nested attribute in the WITH OBJECT OID clause. Action: Specify a top-level attribute of the object type of the object view. ORA-22979 cannot INSERT REF or REF user-defined object view Cause: An attempt was made to insert a REF or REF user-defined object view into a REF column created to store system-generated REF values. Action: Ensure that the REF to be inserted is not from an object view or user-defined REF column ORA-22980 must specify an attribute set for the WITH OBJECT OID clause Cause: WITH clause was used OBJECT OID DEFAULT, but the underlying view or table has no OID. User Response : Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view.

ORA-19400 to ORA-24279

12-61

ORA-22990 LOB locators cannot span transactions Cause: A LOB locator selected in one transaction cannot be used in a different transaction. Action: Reselect the LOB locator and repeat the operation. ORA-22991 Insufficient space allocated for argument string Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument. Action: Allocate more space for the argument. ORA-22992 cannot use selected LOB locators from remote tables Cause: A remote LOB column cannot be referenced. Action: Remove references to LOBs in remote tables. ORA-22993 The specified input amount is greater than the actual source amount Cause: 1.

For LOB writing, the amount of data received is different from the amount that was indicated to be sent.

For LOB copy and load from file, the end of the source LOB/FILE value was reached before the specified amount of input was copied/loaded.

Action: (1) Will happen when using the OCI chunked mechanism with polling or with a callback function. Modify the code to either send the specified value or to pass 0 as the input value so that any amount of data can be sent. (2) Will fail if the amount of input specified is too large for the source LOB/FILE, given the source's initial offset. Decrease the initial font offset or decrease the amount to copy/load. ORA-22994 Source offset is beyond the end of the source LOB Cause: The source offset for a COPY LOB or LOB LOADFROMFILE is beyond the end of the source LOB. Action: Check the length of the LOB, then adjust the font offset. ORA-22995 The TABLESPACE DEFAULT option is invalid in this context Cause: The TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts:

12-62 Error messages

■

at the table level for a partitioned table

■

at the partition level for a composite partition

An attempt was made to use the TABLESPACE DEFAULT option in a different context. User Response : Remove the TABLESPACE DEFAULT option. ORA-22996 The size of the NEXT extent is less than the size of the LOB block Cause: An attempt was made to create or modify a LOB segment so that the size of the NEXT extent was less than the size of the LOB block. User Response : Specify a NEXT extent size that is greater than or equal to the size of the LOB part. ORA-22997 VARRAY stored as LOB is not specified at table level Cause: An attempt was made to specify a VARRAY column to be stored as LOB at the partition/subpartition level in a table move or partition maintain statement. However, the VARRAY column was not specified to be stored as a LOB at the table level when the table was created. Action: Specify the VARRAY column to be stored as a LOB at the table level when the table is created. Alternatively, do not specify that the VARRAY column be stored as a LOB at the partition/subpartition level if it is not specified at the table level when the table is created. ORA-23300 string Cause: The RAISE_SYSTEM_ERROR stored procedure was called, causing this error to be generated. Action: Correct the problem as described in the error message or contact your application or database administrator for more information. ORA-23301 Mixed use of deferred RPC destination modes Cause: The replication catalog determined that the deferred RPC destinations were mixed with the destination determined by other engines in the same transaction. Action: Do not mix target types in the same transaction. Application ORA-23302 was unable to communicate during lazy RPC. Cause: An application declared a communication failure during a deferred RPC. Action: Retry the application when communication is restored. ORA-23303 application threw a generic exception during a lazy RPC Cause: An application declared a generic fault during a lazy RPC. Action: Determined by the application.

ORA-19400 to ORA-24279

12-63

ORA-23304 Malformed deferred RPC at string arg from string in call string, at string tid Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to DBMS_DEFER. CALL. Action: Make sure the number of arguments matches the count. Lazy RPC internal error ORA-23305: string Cause: An internal error occurred in Lazy RPC. Action: Report the bug and other information to support. ORA-23306 schema string does not exist Cause: The schema name was null or misspelled, or the schema does not exist locally. Action: Specify the schema correctly or create it with CREATE USER. ORA-23307 replicated schema chain already exists Cause: The supplied database already replicates the specified schema. User Response : Choose a different schema or a different database. ORA-23308 The string.string object does not exist or is invalid Cause: The supplied name was null or misspelled, the supplied type was incorrect, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate state. Action: Make sure the object is valid in the database, visible to the user, and if applicable, a valid object in ALL_REPOBJECT. ORA-23309 object string.string of type string exists Cause: An object exists in the same namespace, perhaps with a different type or form, or the same object is already registered as a REPOBJECT in another object group. Action: Drop the offending object with the SQL DROP command, unregister the offending object with DBMS_REPCAT.DROP_MASTER_REPOBJECT() or recover the request by using TRUE for a boolean parameter such as repeat or USE_EXISTING_OBJECT. ORA-23310 The object group string.string is not disabled Cause: The requested operation requires the object group to be suspended.

12-64 Error messages

Action: Call SUSPEND_MASTER_ACTIVITY on the MASTERDEF of the REPGROUP, wait until the state changes to inactive, and then retry the original request. ORA-23312 is not masterdef based on string Cause: The group name is null, the group name is incorrect, the given invocation or database is not MASTERDEF, or one of the masters does not believe that the invocation data of the database are the MASTER DEF. Action: If the given group name and the MASTERDEF are correct, connect to the MASTERDEF and retry the request or relocate the MASTERDEF in the databases (roam) using RELOCATE_MASTERDEF. ORA-23313 object group string.string is not mastered to string Cause: group name is null, group name is misspelled, calling database is not master, or calling database does not create that the given database is master. Action: If the supplied pool name is correct, connect to a current master and retry the request, make the invoking database master with ADD_MASTER_DATABASE, or use SWITCH_SNAPSHOT_MASTER if the invoking database is a snapshot site. ORA-23314 database is not a snapshot site for string.string Cause: The invoking database is not a snapshot database for the specified object group. Action: Connect to the desired snapshot database and retry the request, or convert the calling database to a snapshot site with CREATE_SNAPSHOT_REPSCHEMA or CREATE_SNAPSHOT_REPGROUP. ORA-23315 Repcatlog version or request string is not compatible. Version string Cause: Incompatible REPCAT versions are used or a REPCATLOG record has been corrupted. Action: Convert the master to a REPCAT-compliant version or retry the request. ORA-23316 masterdef is a string Cause: The requested operation is not allowed on a MASTERDEF site. Action: Reassign the MASTERDEF to another master and retry the operation.

ORA-19400 to ORA-24279

12-65

ORA-23317 A communication error occurred Cause: The remote database cannot be accessed. Action: Make sure the remote database is running, the communication network is working, and the proper database links are present. ORA-23318 A ddl failure occurred Cause: The user-supplied or system-generated DDL did not execute correctly. Action: Examine DDL, database status, REPCATLOG, and ALL_ERRORS to determine why the failure occurred. ORA-23319 parameter value string is not appropriate Cause: The supplied value of a parameter is null, misspelled, or not supported. Action: Consult the documentation and use the appropriate parameter values for the situation at hand. ORA-23320 request failed due to strings and string values Cause: Missing DDL record for a REPCATLOG record or inconsistency in REPCAT views. Action: Retry the request or make the views consistent. ORA-23321 Pipe name cannot be null Cause: You called DBMS_PIPE with a null pipe name. Action: Find out the name of the pipe and call the function with the non-null pipe name. ORA-23322 Privilege error when accessing channel Cause: You tried to create a channel that already existed and belonged to someone else, you deleted a channel you were not authorized to use, or you posted a message on a channel you were not authorized to use. , or receive a message from a pipeline for which you are not authorized. Action: You may need to use a different pipe name. ORA-23323 Parameter length exceeds lazy RPC limits Cause: A lazy RPC parameter exceeded the lazy RPC limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters. Action: Use smaller parameters.

12-66 Error messages

ORA-23324 error string, creating deferred input on "string" with error string Cause: The given error was encountered while trying to create a DEFERROR input for the given error code and database. Action: Correct the cause of the given error. ORA-23325 parameter type is not a string Cause: A conflict resolution priority function received a different type than the type assigned to the priority group; o The priority group is not assigned a type or role; or DBMS_DEFER_SYS_QUERY was called to retrieve a deferred RPC parameter from the deferred RPC queue, but the type of the parameter does not match the return type of the function. Action: Use the function corresponding to the parameter type. ORA-23326 The object group string.string is disabled Cause: SUSPEND_MASTER_ACTIVITY was called before the object group resumed normal operation or an RPC (deferred) operation was attempted while the object group was disabled. Action: If SUSPEND_MASTER_ACTIVITY was called and there is a pending RESUME_MASTER_ACTIVITY request, wait until it completes and then call SUSPEND_MASTER_ACTIVITY again. Otherwise, resume the database activity with the RESUME_MASTER_ACTIVITY call. ORA-23327 Imported lazy RPC data does not match the import database string Cause: Lazy RPC queues were imported from a database with a different global name or operating system than the lazy RPC database. import. Action: Lazy RPC data should only be imported into a database with the same global name, hardware, and operating system. ORA-23328 snapshot base table "chain".."chain" differs from master table "chain".."chain" Cause: When creating a snapshot via REPCAT, the snapshot base table name did not match a replicated table name on master . User Response : Change the DDL of the snapshot to use the same base table as the replicated table name on the master. ORA-23329 User supplied ddl was successful but there is no snapshot "chain". "string" Cause: The user-supplied DDL to create a snapshot ran without errors, but the snapshot does not exist.

ORA-19400 to ORA-24279

12-67

Action: Manually retrieve the DDL and re-register it with the matching DDL and snapshot. ORA-23330 Column group string already exists Cause: The column group was already registered in the object group. User Response : Use a column group name that is not already registered in the replicated object group. ORA-23331 column group string does not exist Cause: The supplied column group is null, misspelled, or not registered. User Response : Use a registered column group. ORA-23332 group string is in use; cannot be dropped Cause: The provided column group or priority group is being used to resolve conflicts. Action: Call the DBMS_REPCAT DROP_UPDATE_RESOLUTION, DROP_DELETE_RESOLUTION, DROP_UNIQUE_RESOLUTION procedures to make the column group or priority group no longer in use before it is dropped. ORA-23333 Column "string" is already part of a column group Cause: An attempt was made to add a column to a column group when the column was already a member of a column group. Action: Drop the column from your existing column group before trying to add it to another. ORA-23334 Column "string" does not exist in the table or column group Cause: The specified column is null, misspelled, or not part of the specified table or column group. User Response : Use a column that is a member of the table or column group. ORA-23335 priority group string already exists Cause: The priority group is already registered in the object group. User Response : Use a column group name that is not already registered in the object group. ORA-23336 Priority group string does not exist Cause: The priority group is already registered in the object group. Action: Use a priority group name that is not already registered in the object group.

12-68 Error messages

ORA-23337 Priority or value not in priority group string Cause: The specified priority or value was not registered as part of the priority group. Action: Specify a different value or priority that is already part of the priority group, or add the value to the priority group. ORA-23338 Priority or value already in priority group string Cause: The specified value or priority was already registered as part of the priority group. Action: Specify a different value or priority that is not part of the priority group, or drop the value in the priority group. ORA-23339 duplicate conflict resolution information Cause: The specified combination of column group, sequence, conflict type, and/or parameter table name, parameter column name, and parameter sequence number has already been registered. Action: Check if additional conflict resolution information needs to be added and provide a new sequence number. If you modify existing information, the existing information must be deleted first. ORA-23340 incorrect resolution method string Cause: The user role was specified when the conflict resolution method was not "USER ROLE" or the specified resolution method is not one of the predefined methods. Action: If the user role is specified when the conflict resolution method is not "USER ROLE", re-register the role with the method as "USER ROLE" or specify a NULL user role. Otherwise, specify one of the documented supported conflict resolution methods. ORA-23341 user role required Cause: A NULL user role was specified for the "USER ROLE" method. Action: Provide the name of the user role (for example, "schema".."package".."function") that conforms to the documented user role specifications, or specify one of the conflict resolution methods Documented admissions.

ORA-19400 to ORA-24279

12-69

ORA-23342 invalid parameter column "string" Cause: The parameter column name is null or misspelled, the invoking database is not master, or it is of the wrong type for the specified conflict resolution method. User Response : Specify a parameter column from the specified column group that has a correct type for the conflict resolution method. ORA-23343 No match for specified conflict resolution information Cause: The specified combination of column group, string, and conflict type was not registered (for example, to add a comment). Action: Specify a combination of column group, sequence, and logged conflict type. ORA-23344 (string.string) constraint does not exist Cause: A null, incorrect, or non-existent constraint was specified when registering a uniqueness conflict. User Response : Register a named constraint for the specified table. ORA-23345 table "string".."string" not registered for statistics collection Cause: A procedure that handles the collection of conflict resolution statistics was called for a table that was not registered for statistics collection. Action: Call DBMS_REPCAT.REGISTER_STATISTICS to register the table. ORA-23346 primary key is not defined for snapshot table or sequence Cause: An attempt was made to generate replication support for a table or snapshot without a primary key defined by a constraint or DBMS_REPCAT.SET_COLUMNS. User Response : For a table, add a primary key constraint or define a primary key using DBMS_REPCAT.SET_COLUMNS. For a ROWID snapshot, set MIN_COMMUNICATION to false or use a primary key snapshot. ORA-23347 data type string for column "string" table string not supported Cause: The table has a column whose data type is not supported by REPCAT. Action: Drop the column from the table or change the column to be one of the supported data types. ORA-23348 cannot replicate procedure chain; only IN parameters are supported Cause: An attempt was made to generate replication support for a package that has a procedure with OUT or IN OUT parameters.

12-70 Error messages

Action: Remove the procedure from the package, or remove the OUT or IN OUT parameters of the procedure. ORA-23349 cannot generate replication support for roles Cause: An attempt was made to generate replication support for a package that has a public role or an independent role. Action: Remove the public function from the package or change the function to be a procedure. ORA-23350 Maximum number of recursive calls exceeded Cause: This often occurs when trying to resolve conflicts on a table while concurrent updates on the same row create more conflicts. Action: Re-execute DefError deferred transaction using DBMS_DEFER_SYS.EXECUTE_ERROR. ORA-23351 parameter data type string for procedure string not supported Cause: The procedure has a parameter whose data type is not supported by REPCAT. User Response : Remove the parameter from the procedure or change the parameter to be one of the supported data types. ORA-23352 Duplicate destination for deferred transaction Cause: A duplicate destination for a deferred transaction was specified in a previous DBMS_DEFER.CALL call or in a previous DBMS_DEFER.TRANSACTION call or in a dbms_defer_sys.add_default_dest call. Action: Remove the duplicate entry. Lazy RPC queue ORA-23353 has entries for object group string.string Cause: The requested action cannot be performed until the queue is empty for the specified object group. Action: Use DBMS_DEFER_SYS.EXECUTE or DBMS_DEFER_SYS.DELETE_TRAN to flush the queue. ORA-23354 Lazy RPC execution disabled for "chain" Cause: Lazy RPC cannot be performed on the target because Lazy RPC propagation has been disabled. Action: Enable deferred RPC execution with the DBMS_DEFER_SYS.ENABLE call.

ORA-19400 to ORA-24279

12-71

ORA-23355 The object string.string does not exist or is invalid on the master site Cause: The supplied name was null or misspelled, the supplied type was incorrect, the object does not exist as a valid database object on the master site. master site or the object does not exist as a replicated object with the appropriate state. Action: Make sure that the object is valid in the main database and is visible to the user and, if applicable, is a valid object in ALL_REPOBJECT. ORA-23356 masterdef recognizes a master that masterdef does not Cause: DROP_MASTER_REPGROUP was possibly executed on a master site, but REMOVE_MASTER_DATABASES was not executed on the master definition site for that master. Action: Run REMOVE_MASTER_DATABASES from the master definition site to remove the appropriate master (see associated error messages). ORA-23357 seed does not exist Cause: The seed does not exist. Action: Register a new seed. ORA-23358 invalid remote user Cause: The local user does not match the remote user connected via a database link. Action: Drop and recreate the database link identified with the login user identical to the database link owner. ORA-23359 error creating a ddl record for a repcatlog record Cause: The USERID in the REPCATLOG record does not match the USERID of the logged in user. Action: Repeat the operation with another user. ORA-23360 Can only create one snapshot for master table "chain" Cause: An attempt was made to create more than one snapshot on a given master table in the same representative group. Action: Create these other snapshots in a different representative group at another site. ORA-23361 Snapshot "chain" does not exist on parent site Cause: Snapshot does not exist on parent site for offline snapshot instantiation.

12-72 Error messages

Action: The correct procedure is to create the snapshot in a different schema on the primary site and follow the instructions for offline snapshot instantiation. ORA-23362 invalid user Cause: The supplied user does not exist. Action: Enter a valid username and try the operation again. ORA-23363 "Chain" snapshot base table mismatch on master site and snapshot site Cause: The name of the snapshot base table on the master site is different from the base table on the "chain" site. the snapshot. This error can occur when creating offline snapshot instances. Action: Retry offline instantiation with a snapshot name less than 24 bytes ORA-23364 Feature not enabled: advanced replication Cause: The advanced replication feature is not enabled on this site. Therefore, updatable snapshots, lazy RPCs, and other replication features are not available. Action: Do not attempt to use this function. Contact Oracle Customer Support if the Advanced Replication feature was purchased but not activated. ORA-23365 site string does not exist Cause: The site specified in the REFERENCE_SITE or COMPARISON_SITE argument in the DIFFERENCES() or RECTIFY() routine call does not name an existing site. Action: Make sure that the specified database sites actually exist and run the routine again. ORA-23366 Integer value string is less than 1 Cause: The value of the MAX_MISSING argument to the DIFFERENCES() routine cannot be less than 1. The value of the COMMIT_ROWS argument to the DIFFERENCES() and RECTIFY() routines cannot be less than 1. Action: Choose an integer value to make these arguments 1 or more. ORA-23367 table string is missing primary key Cause: The table specified in the "oname1" or "oname2" argument in the "differences()" routine call does not contain a primary key or virtual primary key (defined using the DBMS_REPCAT package in symmetric replication).

ORA-19400 to ORA-24279

12-73

User Response : Make sure that the specified tables have a primary key defined. ORA-23368 name string cannot be null or empty string Cause: The argument SNAME1, SNAME2, ONAME1, ONAME2, MISSING_ROWS_SNAME, MISSING_ROWS_ONAME1, MISSING_ROWS_ONAME2 to DIFFERENCES() or RECTIFY() cannot be NULL or '' (empty string). Action: Change the argument to a non-null or non-empty string. ORA-23369 argument value "string" cannot be null Cause: The MAX_MISSING argument of the DIFFERENCES() routine cannot be NULL. Action: Valid values for MAX_MISSING are integers of 1 or more. ORA-23370 tablestring and tablestring are not equivalent in form (string) Cause: The specified tables are not equivalent in form, which intuitively means that the number of columns, names, data types, and lengths are not equal. Specifically, the problem is in the parentheses and is one of the following: the number of columns is not the same, the data types of columns with the same name in different tables are different, the lengths of the varchar2 and char columns are not the same, the precision and scale of the numeric data types are not the same. User Response : Make sure that the two tables being compared have the same number of columns, column names, and data types. ORA-23371 unknown column string in table string Cause: Some column in the ARRAY_COLUMNS argument (or COLUMN_LIST argument) to the DIFFERENCES() routine does not match a column in the specified table. User Response : Make sure that all columns in ARRAY_COLUMNS or COLUMN_LIST are present in the specified table. ORA-23372 Type string is not supported in table string Cause: Certain types in the table comparison utility are not supported. Action: Make sure that the column types of the tables to be compared are compatible with symmetric replication. ORA-23373 Object group string.string does not exist Cause: The group name was null or misspelled, or the group does not exist locally.

12-74 Error messages

Action: Specify the group correctly or create it with DBMS_REPCAT.CREATE_MASTER_REPGROUP(). ORA-23374 Object group string.string already exists Cause: The given database already replicates the specified object group. You cannot create a snapshot proxy group on a given site where a master proxy group with the same name already exists. Action: Choose a different group or a different database. ORA-23375 function is incompatible with database version in chain Cause: A function incompatible with the specified database was used. Action: Set or increase the value of the COMPATIBLE initialization parameter to match the required compatibility level. ORA-23376 node chain is not compatible with replication version "chain" Cause: An incompatible feature was used on the remote database. Action: Update the remote database and retry the operation. ORA-23377 Incorrect name string for missing_rows_oname1 argument Cause: An attempt was made to use the referring site table name as the name of the missing_rows_oname1 argument. Action: Provide a separately created table with a different name for the MISSING_ROWS_ONAME1 argument. The separately created table will contain the differences between the tables being compared. ORA-23378 connection qualifier "string" is invalid for object group string.string Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in CREATE_MASTER_REPGROUP. User Response : Use or create a database link that contains the correct connection qualifier. ORA-23379 connection qualifier "string" is too long Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes. Action: Use a shorter connection qualifier or shorten the database link name

ORA-19400 to ORA-24279

12-75

ORA-23380 The propagation mode "string" is invalid Cause: The propagation specified is incorrect or not supported. For snapshot sites, all snapshot object groups in the same snapshot site with the same parent object group must have the same propagation method. Action: See Oracle8i Replication for valid propagation modes. For snapshot sites, also ensure that the propagation modes of all snapshot object groups with the same master object group are the same. ORA-23381 object generated for base object[email protected]does not exist Cause: The system-generated objects for the specified base object do not exist at the specified site. The current operation requires that the base object has generated replication support. Action: Make sure that the replication objects generated for the base object exist and are valid at the specified site. If the generated objects do not exist, then the DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() procedure must be called from the master definition site for the base object. argument missing_rows_oname1. The separately created table will contain the differences between the tables being compared. ORA-23382 snapshot repgroup string.string is not registered in the site string Cause: Snapshot REPGROUP is not currently registered on master and therefore cannot be cancelled. Action: No action is required. ORA-23383 record for snapshot repgroup string.string failed on site string Cause: Insert failed into local REPSCHEMA table. Action: No action is required. ORA-23384 Replication parallel insert string argument out of range Cause: The numeric argument specified for DBMS_DEFER_SYS.PUSH is invalid. Action: Correct the value of the argument and try again. ORA-23385 The replication parallel insert string argument is invalid Cause: The string argument specified for DBMS_DEFER_SYS.PUSH is invalid. Action: Correct the value of the argument and try again. ORA-23386 Replication parallel push cannot create slave processes Cause: An error occurred while creating slave processes for parallel push.

12-76 Error messages

Action: If the initialization parameter PARALLEL_MAX_SERVERS is zero, reset the parameter to be greater than zero. Otherwise, contact Oracle Customer Support. ORA-23387 Replication parallel insert queue dequeue error Cause: An attempt to dequeue a dequeued deferred transaction while attempting to assign a new queue batch number failed. Action: Contact Oracle Customer Support. Replication Parallel Push Watermark Error ORA-23388 Cause: An error occurred during parallel push while trying to update the maximum watermark information in SYSTEM.DEF$_DESTINATION. Action: Contact Oracle Customer Support. deprecated procedure ORA-23389; drop objects and recreate using new master Cause: DBMS_REPCAT.SWITCH_SNAPSHOT_MASTER is no longer supported. Action: Drop the objects into the object pool and recreate them using the new master. ORA-23392 could not find snapshot to associate with "string".."string" Cause: Could not find the snapshot associated with a trigger or index pulled from the master site. Action: Make sure that the snapshot, master, and master index or trigger are registered as replicated objects. ORA-23393 user is already a seeder Cause: The given user is already the current seeder. Action: No action is required. ORA-23394 duplicate seed Cause: There is more than one valid seed. Action: Unregister duplicate planters. ORA-23395 object "string".."string" of type "string" does not exist or is invalid Cause: The supplied name was null or misspelled, the supplied type was incorrect, the object does not exist as a string object. Valid database or object does not exist does not exist as a replicated object with the appropriate state.

ORA-19400 to ORA-24279

12-77

Action: Make sure the object is valid in the database, visible to the user, and if applicable, a valid object in ALL_REPOBJECT. ORA-23396 Database link "chain" does not exist or has not been scheduled Cause: The database link does not exist in the replication propagator schema or has not been scheduled. Action: Make sure the database link exists in the database, is accessible, and is scheduled to run. ORA-23397 Global name "string" does not match the database link name "string" Cause: The database link name on the local node does not match the global database name to which the link accesses. Action: Make sure global names are set to true and the link name matches the global name. ORA-23398 Username "string" in database link "string" does not match local username "string" Cause: The username of the replication administrator user on the local node and the name user names in the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same. Action: Make sure that the replication administration user ID on the local node and the user ID on the node corresponding to the database link are the same. ORA-23399 Replication support generation for "string".."string" is not complete Cause: Replication support has not been generated for the specified object or the generation process has not yet completed. Action: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object. ORA-23400 invalid snapshot name "string" Cause: A null, misspelled, or malformed snapshot name was supplied for DBMS_SNAPSHOT.REFRESH. User Response : Provide a valid snapshot name for DBMS_SNAPSHOT.REFRESH. ORA-23401 snapshot "string".."string" does not exist Cause: A snapshot name was supplied for DBMS_SNAPSHOT.REFRESH that is not in SYS.SNAP$ or its associated views.

12-78 Error messages

Action: Provide a snapshot name that is in SYS.SNAP$, ALL_SNAPSHOTS, or USER_SNAPSHOTS. ORA-23402 update stopped due to conflicts caused by deferred txns. Cause: There are pending conflicts logged in the DefError table on the snapshot master. Action: Resolve the conflicts in the DefError master table and refresh again after the table is empty. Alternatively, update with REFRESH_AFTER_ERRORS set to TRUE, which will continue the update even if there are conflicts in the master's DefError table. Continuing despite conflicts can cause changes to an updateable snapshot to appear to be temporarily lost (until an update succeeds after the conflicts are resolved). ORA-23403 Update group "string".."string" already exists Cause: A new update group is created when a group with the same name already exists in SYS.RGROUP$. Action: Choose a different update group name. ORA-23404 Update group "string".."string" does not exist Cause: An update group name was supplied that is not in SYS.RGROUP$. Action: Provide an update group name that is in SYS.RGROUP$ or DBS_RGROUP. ORA-23405 Update group number string does not exist Cause: An update group number was supplied that is not in SYS.RGROUP$. Action: Provide an update group number that is in SYS.RGROUP$ or DBS_RGROUP. ORA-23406 Insufficient privileges on user "string" Cause: The caller is not the owner of the snapshot and does not have ALTER ANY SNAPSHOT privileges. Action: Perform the operation as the owner of the snapshot or as a user with ALTER ANY SNAPSHOT privileges. The ORA-23407 object name string must be in the format "schema". Action: Repeat the operation with the correctly specified object name (such as "schema", "object", or "object").

ORA-19400 to ORA-24279

12-79

ORA-23408 This replication operation is not supported in a mixed configuration. Cause: The operation is not supported if the object group is replicated to a pre-V8 node. Action: Make sure that all nodes in the replicated object group are V8. ORA-23409 could not find an unused update group number Cause: 1000 consecutive update group numbers defined by the RGROUPSEQ number have already been used by lines in SYS.RGROUP$. Action: Change the sequence number to be within an unused legal range and destroy any unnecessary update groups. ORA-23410 snapshot "string". "string" is already in an update group Cause: A snapshot with the same name is already in an update group. Action: Subtract the snapshot from the current update group and add it to the new update group, or combine the two update groups into a single update group. ORA-23411 The snapshot "string". "string" is not in update group "string". "string" Cause: The specified snapshot is not in the specified update group. Action: Try again with the appropriate snapshot and update the group names. ORA-23412 Master table primary key columns changed Cause: The master table primary key constraint was changed after the primary key snapshot was created. Action: Drop and recreate the snapshot of the primary key. ORA-23413 the table "string". "string" does not have a snapshot record Cause: A fast update cannot be performed because the master table does not contain a snapshot record. Action: Use the CREATE SNAPSHOT LOG command to create a snapshot log on the master table. ORA-23414 Snapshot record for "string". Action: Use the CREATE SNAPSHOT LOG...ADD ROWID command to start logging ROWID information to the snapshot log.

12-80 Error messages

ORA-23415 Snapshot registry for "string".."string" does not record primary key Cause: A primary key snapshot updates quickly, but the snapshot registry does not record primary key information. Action: Use the CREATE SNAPSHOT LOG...ADD PRIMARY KEY command to begin logging primary key information to the snapshot log. ORA-23416 Table "string".."string" does not contain a primary key constraint Cause: The master table does not contain a primary key constraint or the primary key constraint has been disabled. Action: Create a primary key constraint on the parent table or activate the existing constraint. ORA-23417 Unknown snapshot type: string Cause: A fast update is being performed on a snapshot of an unknown or unsupported type. Action: Check ALL_SNAPSHOTS and make sure that the snapshot being updated is a valid snapshot. ORA-23418 cannot unregister the seeder that is currently in use. Cause: The seeder is currently being used to seed replication RPCs. Action: Try again later when there are no active transactions in the propagation replication RPCs. ORA-23419 rebuilds replication media before resuming master activity Cause: There are tables in the object pool that require replication media rebuild. Action: Check the GENERATION_STATUS column in the ALL_REPOBJECTS view. Rebuild replication support for any table in the object group with a status of 'NEEDSGEN'. Resume main activity. The ORA-23420 interval must be evaluated at a time in the future Cause: The INTERVAL parameter is evaluated at a time before SYSDATE. Action: Choose an expression that is evaluated at a time after SYSDATE. ORA-23421 The task number string is not a task in the task queue Cause: There is no task visible to the caller with the given task number. Action: Choose a work number visible to the caller.

ORA-19400 to ORA-24279

12-81

ORA-23422 Oracle Server could not generate an unused job number Cause: The Oracle Server could not generate a job number that was not used to identify another job. Action: Repeat the operation. ORA-23423 task number string is not positive Cause: The given task number is less than 1. Action: Choose a positive integer. ORA-23424 snapshot "string". "string" in unregistered string Cause: The specified snapshot was not successfully registered with this site. Action: Manually register the snapshot on the primary site or on the snapshot site. ORA-23425 invalid snapshot identifier string Cause: The argument supplied to DBMS_SNAPSHOT.PURGE_SNAPSHOT_FROM_LOG is an invalid snapshot identifier or does not identify an Oracle 8 fast update snapshot or the snapshot has already been purged. Action: If the snapshot is an Oracle 8 Flash Snapshot, provide the PURGE_SNAPSHOT_FROM_LOG with your valid snapshot identifier. ORA-23426 lazy RPC queue has entries for string Cause: The requested action cannot be performed until the queue is empty for the given website/database link. Action: Use DBMS_DEFER_SYS.PUSH, DBMS_DEFER_SYS.PURGE_QUEUE, or DBMS_DEFER_SYS.DELETE_TRAN to flush the queue. ORA-23427 Deferred purge queue argument string out of range Cause: The numeric argument specified for DBMS_DEFER_SYS.PURGE_QUEUE is invalid. Action: Correct the value of the argument and try again. ORA-23428 The instance number string associated with the job is invalid Cause: A job is associated with an instance that is not running. Action: Choose a running instance for the worker affinity or set the force parameter to TRUE.

12-82 Error messages

Argument "string" ORA-23430 cannot be NULL or an empty string Cause: The caller supplied an argument whose value cannot be NULL or an empty string. Action: Verify that the supplied varchar2 value is not null or the empty string and retry the call. ORA-23431 bad state: string Cause: The routine was executed on a replicated object group that was in an bad state. Action: Make sure that the replicated object group is in the state indicated in the error message. ORA-23432 Master site chain already exists Cause: An attempt was made to instantiate a replicated object group on a master site that was already part of the object group. Action: If you were trying to add this site, do nothing because it already exists; otherwise, choose another site name and run the routine again. ORA-23433 running on incorrect master site string Cause: An attempt was made to run the routine on a site other than the site specified in the routine argument. Action: Provide an argument to the routine that correctly indicates the site where the routine should be executed. ORA-23434 The object group does not know the master site string. Cause: The replicated object group did not yet know the site name supplied as an argument to a routine. Action: Run the DBMS_OFFLINE_OG.BEGIN_INSTANTIATION() routine to add a new site to the group of replicated objects. ORA-23435 cannot create an updateable ROWID snapshot with LOB columns Cause: Propagating LOB data from snapshot sites to the master site requires a primary key in the replicated table. Therefore, updateable ROWID snapshots that contain LOB columns are not supported. Action: Create a primary key snapshot instead of a ROWID snapshot. If the snapshot already exists, it can be converted to a primary key snapshot using the ALTER SNAPSHOT DDL command.

ORA-19400 to ORA-24279

12-83

ORA-23436 Missing model authorization for user Cause: The specified model authorization does not exist. Action: Check the values for username, update template name, or AUTH_TEMPLATE_ID to ensure that a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view. ORA-23437 template authorization already exists for user Cause: The specified user was already authorized to use the specified update group template. Action: Check the values for the username and update the model name or check the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters. ORA-23438 missing update group template Cause: The specified update group template does not exist. User Response : Verify that the update group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view. ORA-23439 update group template already exists Cause: The specified update group template already exists. User Response : Verify that the update group template exists by querying the DBA_REPCAT_REFRESH_TEMPLATES view. ORA-23440 incorrect public template value Cause: The public template parameter is not 'Y', 'N' or NULL. User Response: Correct the value of the public template parameter. Must be 'Y', 'N', or NULL. ORA-23441 object does not exist for update group template Cause: The specified object does not exist in the update group template. User Response: Correct the object name and type parameters. Check the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct object name and type. ORA-23442 object already exists for update group template Cause: The specified object already exists in the update group template. User Response : Change the object name and object type parameters. Query the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct object name and type.

12-84 Error messages

Missing template parameter ORA-23443 Cause: The specified template parameter does not exist. Action: Correct the model parameter value and rerun the procedure. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the update group template name and parameter name. ORA-23444 duplicate template parameter Cause: The template parameter already exists for the specified update group template. Action: Correct the model parameter value and rerun the procedure. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the update group template name and parameter name. ORA-23445 Missing model site Cause: The model site specified by site name, username, and update group model name does not exist. Action: Correct the invalid parameter and rerun the procedure. Use the DBA_REPCAT_TEMPLATE_SITES view to query for existing template sites. ORA-23446 duplicate template site Cause: The template site specified by site name, username, and update group template name already exists. Action: Correct the invalid parameter and rerun the procedure. Use the DBA_REPCAT_TEMPLATE_SITES view to query for existing template sites. ORA-23447 Missing user parameter value Cause: The user parameter value specified by username, parameter name, and update group template name does not exist. Action: Correct the invalid parameter and rerun the procedure. Use the DBA_REPCAT_USER_PARM_VALUES view to query for existing user parameters. ORA-23448 duplicate user parameter value Cause: The user parameter value specified by username, parameter name, and update group template name already exists.

ORA-19400 to ORA-24279

12-85

Action: Correct the invalid parameter and rerun the procedure. Use the DBA_REPCAT_USER_PARM_VALUES view to query for existing user parameters. ORA-23449 Missing username Cause: The user specified by the username parameter does not exist in the database. Action: Correct an invalid username or create the user in the master database. Use the DBA_USERS view to select valid database users. ORA-23450 type already contains object "string".."string" Cause: The type already contains the specified object. Action: Check that the specified object is correct. To add all the columns of a table object, delete the type object and add it again. ORA-23451 type string already defined for object group string.string Cause: The given object group already contains a (possibly unpublished) definition of the specified type. Action: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name. ORA-23452 object group type string string.string is already published Cause: The given object group already contains a (published) definition of the specified type. Action: Check the spelling of the flavor name. The requested operation ORA-23453 is not supported on the superior type. Cause: The UPPER type has a NULL name and cannot be set or removed directly. Action: Provide the name of a type other than the TOP type, or use the DBMS_REPCAT routines to implicitly change the TOP type. ORA-23454 type string not defined for object group string.string Cause: The given object group does not contain a (published) definition of the specified type. Action: Check the spelling of the flavor name. Make sure the type has been defined (and published) for the object group.

12-86 Error messages

String type ORA-23455 contains object "string" Cause: The supplied type contains the object to be discarded. Action: Purge the flavor or choose another item to drop. ORA-23456 string type does not contain "string" Cause: The type does not contain the specified object, column, or attribute. Action: Drop the type or choose a different object, column, or attribute. ORA-23457 Invalid Variation ID String Cause: The supplied variation ID is invalid. Action: Make sure that an instance of this type has been created. If the Variation ID is out of range (-2147483647, 2147483647), contact Oracle Customer Support. ORA-23458 improperly typed string in string Cause: The given type in the given database prevents the operation from succeeding. Action: Change the database type or choose a different operation. ORA-23459 Type string must contain "string" Cause: The type must contain the specified object, column, or attribute. Action: Choose a different database type or make sure the object, column, or attribute is available. ORA-23460 Missing value for column string in resolver method "string" for "string".. "string".. "string" Cause: Before resolving conflicts, some values required to resolve conflicts are not available; or, after resolving the conflicts, some values required for SQL retry are not available. Action: Define the appropriate flavors, provide the required values via the availability vector in USER FLAVOR FUNCTION for conflict resolution. ORA-23461 could not resolve conflict for "string".."string".."string" ORA-23462 string of type in use on site string Cause: The supplied type cannot be removed because it is in use on the site specified. Action: Change the version of the site or unregister it if it is an instant site.

ORA-19400 to ORA-24279

12-87

ORA-23463 variant incompatible with object "string"."string" Cause: An existing variant includes the specified object with an incompatible type. Action: Change the type of the object or remove the type if it is not in use. Missing type ORA-23464 column string of "string".."string" Cause: The type includes some columns from a group of objects, but not all required columns. Action: Change the type definition to include all required columns. The ORA-23465 type already includes the column string of "string".."string" Cause: The type includes the specified column being added. User Response : Check that the specified column is correct. ORA-23466 type requires object "string" to be missing."string" Cause: The type includes the specified object that does not exist. Action: Verify that the specified object name is correct and create the object if applicable. ORA-23467 type is missing object "string".."string" Cause: The type does not include the specified object that is being discarded. Action: Check that the specified object is correct. ORA-23468 string missing string Cause: The model does not contain the object with the specified key. Action: Add the object to the model. ORA-23469 string is different between models Cause: The specified column values are different in each model for the same key values. Action: Correct the column values so that the models are the same. ORA-23470 invalid status Cause: Status must be REMOVED, INSTALLING, or INSTALLED. Any other status is invalid. Action: Verify that the specified status value is correct.

12-88 Error messages

ORA-23471 model not authorized for user Cause: The update model is private and the user has not been authorized to create an instance of the model. Action: Authorize the user to use the template. ORA-23472 Snapshot "string".."string" must be updated atomically Cause: Non-atomic update is not supported for the specified snapshot. Action: Set the value of the ATOMIC parameter to FALSE in the update procedure being used, or remove the specified snapshot from the set of snapshots being updated. ORA-23473 Replication RPC processing for "string".."string" is disabled Cause: Replication RPC processing for the object group containing this object is disabled. This includes RPC in the error queue. Action: Replication RPC processing is disabled when the object group is created offline. Wait for the offline instantiation to complete. The ORA-23474 definition of "string" was altered since the generation of replication support Cause: the current columns in the specified table and their column types do not correspond to the columns and column types when the replication support was generated for the last time. Action: Rebuild replication media for the affected table. All flavors including the specified table should also be checked for validity. ORA-23475 Key column "string" must be sent and compared Cause: The specified column is a key column and must be sent and compared during seed replication. Action: Make sure all key columns are submitted and compared. ORA-23476 cannot import from one string to another Cause: This object was imported from a database with a different global name than the import database. User Response : Only import this object into a database with the same global name. ORA-23477 cannot change seed mode for object group string.string Cause: The seed method of a snapshot object group can only be changed when no other object group with the same master object group shares the location of the snapshot.

ORA-19400 to ORA-24279

12-89

Action: Make sure there are no other snapshot object groups in the local site with the same master object group. ORA-23478 object group chain is already mastered in chain Cause: There is at least one other snapshot proxy group at the local site with the same group name but a different parent site. Action: Make sure that all snapshot proxy groups on the local site with the same group name have the same master. ORA-24000 invalid value string, string must be in the format [SCHEMA.] NAME Explanation: An invalid value was specified for the parameter. Action: Specify a string in the format [SCHEMA.]NAME. ORA-24001 cannot create QUEUE_TABLE, string already exists Cause: The queue table already exists in the queuing system. Action: Drop the table first using the DROP_QUEUE_TABLE() command or specify another table. ORA-24002 The string QUEUE_TABLE does not exist Cause: QUEUE_TABLE does not exist. Action: Query the user view USER_QUEUE_TABLES to discover the existing queue tables. ORA-24003 Queue table index string does not match queue table string Cause: The queue table index has not yet been imported correctly. User Response: Import the queue table index before attempting to use the queue table. If the import fails, correct the problem and try importing the queue table index again. ORA-24004 invalid column name string in SORT_LIST, must be ENQ_TIME or PRIORITY Cause: An invalid column name was specified in SORT_LIST. Action: Valid column names are ENQ_TIME and PRIORITY. ORA-24005 should use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables. Cause: An attempt was made to use the SQL DROP TABLE command for queue tables, but DROP TABLE is not supported for queue tables.

12-90 Error Messages

Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the DROP TABLE command. ORA-24006 cannot create QUEUE, chain already exists Cause: The requested queue to create already exists. Action: Specify another queue name. Query USER_QUEUES for all existing queues in the user schema. ORA-24007 invalid value string, MAX_RETRIES must be a non-negative integer Cause: An invalid value was specified for MAX_RETRIES. Action: Specify a non-negative integer. ORA-24008 The queue table string.string must be dropped first. Cause: An error was detected while dropping a queue table on a cluster, table space, or schema. Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to first drop the specified queue table; then repeat the operation. ORA-24009 invalid value string, QUEUE_TYPE must be NORMAL_QUEUE or EXCEPTION_QUEUE Cause: Invalid queue type parameter. Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE for exception queue. ORA-24010 QUEUE string does not exist Cause: The specified queue does not exist. Action: Specify a valid queue. Query USER_QUEUES for all valid queues. ORA-24011 cannot remove QUEUE, chain must be stopped first Cause: Queue was not stopped. That is, queuing or dequeuing is still enabled. Action: First stop the queue with the STOP_QUEUE command and disable the queue and dequeue. ORA-24012 cannot drop QUEUE_TABLE, some rows in chain were not dropped Cause: There is a queue in the queue table that was not dropped. All queues must be cleared first.

ORA-19400 to ORA-24279

12-91

Action: Drop all the queues that belong to this queue table using the DROP_QUEUE() command. Be sure to stop the queues correctly before deleting them. Alternatively, use the force option on DROP_QUEUETABLE. ORA-24013 invalid string value, RETRY_DELAY must be non-negative Cause: A negative value was specified for RETRY_DELAY. Action: Specify a non-negative value for RETRY_DELAY. ORA-24014 invalid string value, RETENTION_TIME must be FOREVER or non-negative Cause: Queue retention was specified, but the retention time was specified to be less than zero. Action: Specify the retention time as non-negative or FOREVER. Alternatively, do not specify retention. ORA-24015 cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist Cause: An invalid QUEUE_PAYLOAD_TYPE was specified during CREATE_QUEUE_TABLE. Action: QUEUE_PAYLOAD_TYPE must be RAW or an object type that already exists in the database. ORA-24016 cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string Cause: An invalid object type was specified for QUEUE_PAYLOAD_TYPE during CREATE_QUEUE_TABLE. Action: Make sure you have execute privileges on the object type specified for the queue. ORA-24017 cannot enable queue on QUEUE, chain is exception queue Cause: An attempt was made to enable queue for an exception queue. Action: No action is required. ORA-24018 STOP_QUEUE in chain failed, pending transactions found Cause: There were pending transactions in the queue and WAIT was set to false, so STOP_QUEUE could not stop the queue. Action: Set WAIT to TRUE and try STOP_QUEUE again. It will be suspended until all pending transactions are completed.

12-92 Error Messages

The ORA-24019 identifier for the string is too long, it should not have more than 1,000 characters in the string. Cause: The specified identifier is too long. Action: Try again with a shorter identifier. ORA-24020 Internal error in DBMS_AQ_IMPORT_INTERNAL, string Cause: An internal error occurred in the package. DBMS_AQ_IMPORT_INTERNAL. Action: Contact Oracle Customer Support. ORA-24021 Queue table definition was not imported to string.string Cause: The queue definition was not updated because the queue table was not imported correctly. Action: Re-import the queue table. The specified ORA-24022 parameters have no effect on the queue. Cause: The combination of parameters will not cause the queue to start or stop. Action: No action is required. This is a warning. ORA-24023 Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string] Cause: An internal error occurred in the DBMS_AQ_EXP_INTERNAL package. Action: Contact Oracle Customer Support. ORA-24024 Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string] Cause: An internal error occurred in the DBMS_AQ_IMP_INTERNAL package. Action: Contact Oracle Customer Support. ORA-24025 Invalid value string, QUEUE_PAYLOAD_TYPE must be RAW or an object type Cause: The QUEUE_PAYLOAD_TYPE parameter has an invalid value. Action: Specify a valid object type or RAW. ORA-24031 invalid value, string must not be NULL Cause: Parameter is NULL. User Response : Specify a non-null value for the parameter.

ORA-19400 to ORA-24279

12-93

Object string ORA-24032 exists, could not create index for queue table string Cause: Oracle AQ attempted to create an index with the name specified in the error message. The index for the specified queue table could not be created because an object with the same name exists. Action: Drop the object specified in the error message and try the command again. You can also choose a different name for the queue table. ORA-24033 No recipient for message Cause: A queue was performed on a queue that was configured for multiple queue removers, but no explicit recipients were specified in the call, and no queue subscribers were determined to be recipients of the call message. Action: Pass a list of recipients in the queued call or add subscribers to the queue to receive this message. ORA-24034 application chain is already a subscriber of the queue chain Cause: An application name that was already a subscriber of the queue was specified in the DBMS_AQ.SUBSCRIBE call. Action: Choose another application name and repeat the call. ORA-24035 AQ agent chain is not a queue chain subscriber Cause: An AQ agent was specified that was not a queue subscriber. Action: Verify the agent's name and/or address and call back. ORA-24036 An invalid SORT_ORDER column string was specified for the queue table. Cause: The CREATE QUEUE TABLE command was issued with MESSAGE_GROUPING set to TRANSACTIONAL and a sort order column other than Priority. Only the priority column can be specified in the sort order for queue tables with transactional pooling. Action: Change the sort order list in the CREATE QUEUE TABLE command and retry the call. ORA-24037 The schema string in QUEUE_NAME is not the same as the schema string in QUEUE_TABLE Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter. User Response : Use the same schema name for the QUEUE_NAME and QUEUE_TABLE parameters and repeat the command.

12-94 Error Messages

ORA-24038 RETRY_DELAY and MAX_RETRIES cannot be used for an 8.0 compliant multi-consumer queue Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created multi-consumer and with the COMPATIBLE parameter set to '8.0'. Action: Set RETRY_DELAY to zero or update the queue table to be compatible with 8.1 using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. ORA-24039 Queue chain not created in multi-consumer queue table Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER or ENQUEUE procedure was issued with a non-empty recipient list on a queue that was not created multi-consumer. Action: Create the queue in a queue table that was created for multiple consumers and try the call again. ORA-24041 propagation schedule exists for sequence QUEUE and sequence DESTINATION Cause: SCHEDULE_PROPAGATION was issued for a queue and destination pair that has an existing propagation schedule. Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule, then issue the SCHEDULE_PROPAGATION call again. ORA-24042 No propagation schedule exists for QUEUE chain and DESTINATION string Cause: An UNSCHEDULE_PROPAGATION was issued for a queue and destination pair that does not have an existing propagation schedule. Action: Check the spelling of the specified QUEUE and DESTINATION and retrieve with the correct spelling. ORA-24043 destination string uses a reserved name, names prefixed with AQ$_ are invalid Cause: An attempt was made to specify a reserved name for a destination. Action: Enter a different value or NULL for the local destination. Then repeat the operation. ORA-24044 Source string and destination string object types do not match Cause: The recipient queue of a message has a different object structure than the sender queue. The message cannot be propagated.

ORA-19400 to ORA-24279

12-95

Action: Remove the recipient from the sender's queue subscriber list or create the destination queue with an object type that matches the object type of the source queue. ORA-24045 Invalid agent address string, agent address must be in the format [SCHEMA.]NAME[@DATABASE LINK] Cause: An invalid value was specified for the agent address parameter. Action: Specify a string in the format [SCHEMA.]NAME[@DATABASE LINK]. ORA-24046 Protocol attribute reserved for future use Cause: The AQ agent object type protocol attribute is reserved for future use. Action: Do not specify the protocol attribute in the agent object type. ORA-24047 Invalid agent name string, agent name must be in NAME format Cause: An invalid value was specified for the agent name parameter. Action: Specify a string in NAME format. Then repeat the operation. ORA-24048 cannot create QUEUE_TABLE, user does not have access to AQ object types Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to the internal AQ object types. Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user access to AQ object types. ORA-24049 Invalid agent name string, names prefixed with AQ$_ are invalid Cause: An attempt was made to use a reserved prefix in the agent name. Action: Enter a different value for the agent name. Then repeat the operation. ORA-24050 subscribers do not support exception queue chain Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE. Action: Specify a NORMAL_QUEUE in the procedure.

12-96 Error messages

ORA-24051 cannot propagate payloads of type object that have a REF or BFILE attribute Cause: An ADD_SUBSCRIBER or ENQUEUE procedure was issued with a non-NULL address field on the agent type on a queue whose payload has an attribute REF or BFILE. Propagation of payloads of type object that have a REF or BFILE attribute is currently not supported. Action: Specify an agent with a NULL address field so that the agent can leave the same queue. Or change the object type definition to one that does not use the REF or BFILE attributes. ORA-24052 cannot propagate object type payloads with LOB attributes to a version 8.0 Cause: The recipient of a message with LOB attributes was using an Oracle version 8.0. LOB attribute propagation is only supported in Oracle 8.1 and later. Action: Upgrade the target version to Oracle 8.1 and try again. Or, change the object type definition to one that does not use LOB. ORA-24053 PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative Cause: PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative. Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE. ORA-24054 cannot propagate to Oracle version 8.0.3 or earlier Cause: The recipient of a message was using Oracle version 8.0.3 or earlier. Initialization is only supported in Oracle 8.0.4 and later. Action: Upgrade the target version to Oracle 8.0.4 or higher and try again. ORA-24055 unable to delete propagation status rows that are in a prepared state Cause: An attempt was made to use the built-in administration procedure to delete the status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in a prepared state. Action: Wait until the propagation completes successfully before retrying the operation.

ORA-19400 to ORA-24279

12-97

ORA-24056 Internal inconsistency for QUEUE string and destination string Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were not consistent for the specified queue and destination. Action: Contact Oracle Customer Support. ORA-24057 unable to set subscriber with rule in queue sequence Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure was issued with a rule in a queue for which rule-based subscribers are not supported. Rule-based Subscribers are currently only supported for NORMAL (persistent) multi-consumer queues created with a queue table supported by Oracle version 8.1.0 or higher. Action: Create a multi-consumer NORMAL queue in a queue table supported by Oracle version 8.1.0 or higher and retry the call. Or, if the queue is a regular multi-consumer (persistent) queue, convert the queue table to compatibility with Oracle 8.1.0 or higher and try again. ORA-24058 cannot downgrade a QUEUE_TABLE that has initialization in a ready state Cause: An attempt was made to downgrade the queue table when initializing messages that were in a ready state. Action: Wait for the propagation to complete before retrying the operation. ORA-24059 Invalid COMPATIBLE parameter configuration string specified in DBMS_AQADM.string Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting should be in the format '8.x.y', where x is the version number and y is the update number. Action: Specify a valid COMPATIBLE parameter setting and retry the operation. ORA-24060 cannot convert QUEUE_TABLE, string is already compatible with release string Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting. Action: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility.

12-98 Error messages

ORA-24061 cannot specify a non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE is zero Cause: A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero. User Response : Specify a non-zero parent instance before specifying a non-zero child instance. ORA-24062 Subscriber table string does not match queue table string Cause: The subscriber table has not yet been imported correctly. Action: Import the subscriber table before trying to use the queue table. If the import failed, correct the problem and try to import the subscriber table again. ORA-24063 cannot downgrade QUEUE_TABLE having queues with rule-based subscribers Cause: An attempt was made to downgrade the queue table when there were queues where rule-based subscribers were defined. Action: Remove rule-based subscribers from all queues in this queue table and try again. ORA-24064 Propagation for QUEUE chain and DESTINATION chain already enabled Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose scheduled propagation was already enabled. Action: Make sure that the QUEUE and DESTINATION are correct when you issue the ENABLE_SCHEDULE_PROPAGATION command. ORA-24065 Propagation for QUEUE chain and DESTINATION chain already disabled Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation scheduling has already been disabled. Action: Make sure that the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command. ORA-24066 Invalid privilege specified Cause: An invalid privilege was specified to grant or revoke the privilege. Action: Specify a valid privilege.

ORA-19400 to ORA-24279

12-99

ORA-24067 Maximum number of subscribers for queue chain exceeded Cause: An attempt was made to add new subscribers to the specified one, but the number of subscribers for this queue exceeded the maximum number (1024) of subscribers allowed per queue. Action: Remove existing subscribers before trying to add new subscribers. ORA-24068 cannot start queue chain, queue table chain is being migrated Cause: An attempt was made to start a queue on a queue table being migrated. User Response : Complete the queue table migration and retry the operation. ORA-24069 cannot downgrade queue table chain while updating Cause: An attempt was made to downgrade a queue table, but a previous command to update the queue table still did not complete successfully. Action: Complete the queue table update by re-running the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then downgrade the queue table. ORA-24070 unable to update queue table chain while demoting Cause: An attempt was made to update a queue table, but a previous command to demote the queue table still did not complete successfully. Action: Complete the degradation of the queue table by re-running the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then update the queue table. ORA-24071 cannot perform operation chain, queue table chain is being migrated Cause: An attempt was made to perform an operation on a queue on a queue table being migrated. User Response : Complete the queue table migration and retry the operation. ORA-24072 cannot execute procedure MIGRATE_QUEUE_TABLE; must be queue table owner Cause: An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who performed the procedure is not the queue owner. Action: Reconnect as the owner of the queue table, and then run the procedure DBMS_AQADM.MIGRATE_QUEUE_TABLE.

12-100

message error

ORA-24073 cannot specify RETENTION_TIME on exception queue string.string Cause: An attempt was made to create or modify an exception queue by specifying non-zero RETENTION_TIME. User Response : Use the default RETENTION_TIME parameter value for exception queues. ORA-24074 RETRY_DELAY and MAX_RETRIES cannot be used for exception queue chain Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and exception queue. Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues. ORA-24075 cannot specify an agent with a NULL address and a non-null protocol Cause: An ADD_SUBSCRIBER or queue attempt with an agent that had a NULL address and a non-null protocol. Action: Specify a non-null address or set the protocol to NULL. ORA-24076 cannot perform string operation for NON_PERSISTENT queue string.string Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue. User Response: Do not specify a NON_PERSISTENT queue for these operations. ORA-24077 cannot create a propagation schedule for EXCEPTION queue string.string Cause: SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Initialization programs can only be created for NORMAL queues. User Response: To propagate messages from a queue, specify the queue type as NORMAL. ORA-24078 cannot specify a non-NULL CHILD_INSTANCE if PARENT_INSTANCE is NULL Cause: A non-NULL value was specified for CHILD_INSTANCE when CHILD_INSTANCE was NULL. User Response : Specify a non-null parent instance before specifying a non-null child instance.

ORA-19400 to ORA-24279 12-101

ORA-24079 invalid name string, names prefixed with AQ$_ are invalid for string Cause: An attempt was made to use a reserved prefix for the object name. Action: Enter a different name for this object. Then repeat the operation. ORA-24080 pending abort_propagation for QUEUE chain and DESTINATION chain Cause: A propagation management command was issued for a queue and destination pair whose propagation is not scheduled. Action: Do not issue initialization admin commands for an initial program for which a program cancel request is pending. The ORA-24081 compliant parameter must be a string or greater. Cause: The value of the COMPATIBLE parameter was not high enough to allow the operation. Action: Shut down and reboot with a higher compatibility setting. ORA-24082 Propagation may still be occurring for both the tail chain scheduling and the DESTINATION chain scheduling Cause: The snapshot process performing the propagation scheduling did not respond to the disable propagation command . Action: Make sure the job for the propagation program is done. ORA-24083 cannot specify remote subscribers for string QUEUE string Cause: An ADD_SUBSCRIBER call with a non-null address field was issued on a queue that does not support remote subscribers. Remote subscribers do not support NON_PERSISTENT QUEUES. Action: Specify a null address field and retry the call. ORA-24084 The DBLINK name in the agent string address field is not unique within the first 24 bytes" Cause: Advanced queuing requires the agent DBLINK name to be unique within the first 24 bytes (for queue tables 8.0 compatible) Action: Specify a DBLINK name that is unique within the first 24 bytes or migrate to 8.1 compatible queue tables where this restriction does not exist ORA-24100 error in ktz test layer Cause: There is an error in the ICDs transaction layer test.

12-102

message error

ORA-24120 An invalid string parameter was passed to the procedure DBMS_REPAIR.string Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure. User Response : Specify a valid parameter value or use the default value of the parameter. ORA-24121 Cascade and range of blocks passed to DBMS_REPAIR.CHECK_OBJECT procedure Cause: Both the cascade and range of blocks were specified in a call to DBMS_REPAIR.CHECK_OBJECT. Action: Use a cascade or range of blocks, or use neither. ORA-24122 invalid block range specification Cause: An incorrect block range was specified. Action: Specify the correct values for the BLOCK_START and BLOCK_END parameters. Function chain ORA-24123 not yet implemented Cause: An attempt was made to use the specified function, but it has not been implemented yet. Action: Do not attempt to use the function. ORA-24124 An invalid ACTION parameter was passed to the procedure DBMS_REPAIR.string Cause: An invalid ACTION parameter was specified. Action – Specify CREATE_ACTION, PURGE_ACTION, or DROP_ACTION for the ACTION parameter. ORA-24125 Object string.string has changed Cause: An attempt was made to repair bad blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was executed. Action: Use DBMS_REPAIR.ADMIN_TABLES to clear the repair table and run DBMS_REPAIR.CHECK_OBJECT to determine if there are any bad blocks to repair. ORA-24126 Invalid CASCADE_FLAG passed to procedure DBMS_REPAIR.string Cause: CASCADE_FLAG was specified for a non-table object. User Response: Use CASCADE_FLAG for tables only.

ORA-19400 to ORA-24279 12-103

ORA-24127 TABLESPACE parameter specified with an ACTION other than CREATE_ACTION Cause: The TABLESPACE parameter can only be used with CREATE_ACTION. Action: Do not specify TABLESPACE when performing actions other than CREATE_ACTION. ORA-24128 Partition name specified for non-partitioned object Cause: A partition name was specified for a non-partitioned object. Action: Specify a partition name only if the object is partitioned. ORA-24129 Table name string does not start with string prefix Cause: An attempt was made to pass a table name parameter without the specified prefix. User Response : Pass a valid table name parameter. ORA-24130 table string does not exist Cause: An attempt was made to specify an allocation, repair, or synchronization table that does not exist. User Response : Specify a valid table name parameter. Table string ORA-24131 has bad columns. Cause: An attempt was made to specify an allocation, repair, or synchronization table that does not have a correct definition. Action: Specify a table name that references a successfully created table. ORA-24132 Table name string is too long Cause: An attempt was made to specify that the table name is longer than 30 characters. User Response : Specify a valid table name parameter. The specified ORA-24141 ruleset does not exist Cause: An attempt was made to access or modify a ruleset, but failed because the ruleset does not exist. Action: Access or modify existing rule sets only. ORA-24142 Invalid rule set name Cause: An attempt was made to create a rule set with an invalid name. The rule set name cannot be NULL and cannot be longer than 26 characters unless

12-104

message error

RULES_TABLE_NAME is also specified, in which case the rule set name can be up to 30 characters. Action: Try creating again with a valid ruleset name. ORA-24143 invalid table name Cause: An attempt was made to create a rule set on an invalid table name. The DATA_TABLE name cannot be NULL and cannot be longer than 30 characters. The table with the specified name must exist. User Response : Repeat the build with a valid table name. Rule engine internal error ORA-24144, arguments: [string], [string] Cause: An internal rule engine error occurred. This indicates that the rule engine encountered an exception condition. Action: Contact Oracle Customer Support. The first argument is the error and the second argument is the package. ORA-24270 row already exists in string table for these parameters Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values. Action: Delete the existing row using the appropriate API or check the parameters used to create the row. ORA-24271 translation type must be T, S, or M Cause: The translation type parameter is not T, S, or M. A value other than T, S, or M was specified. Action: Correct the translation type and re-execute the API call. ORA-24272 The seed value must be F or T Cause: The seed value must be F or T. A value other than F or T was specified. Action: Correct the seed value and rerun the API call . ORA-24273 translation text required if translation type is T or S Cause: If a translation type of T or S is specified, the translation text must be provided. Action: Provide the translation text and re-execute the API call.

ORA-19400 to ORA-24279 12-105

ORA-24274 No row exists in the string table for these parameters Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist. Action: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all the specified values exist. ORA-24275 Parameter 'string' of function 'string' is missing or invalid Cause: The function pkgname.funcname was called with a parmname parameter that was null, of length 0, or had an invalid value. User Response : Correct the parameter to provide values that conform to its data type and bounds as specified in the documentation. ORA-24276 Maximum output value 'string' of function 'string' was exceeded Cause: The pkgname.funcname function computed a value for the output parameter name that exceeded the maximum allowed. This can occur when multiple input parameters, each separately valid, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter produces a total length that exceeds the maximum for the output data type. Action: Correct the input values to produce a result that conforms to the limits specified in the documentation. ORA-24277 Insufficient privileges to execute chain Cause: Access to the named procedure is limited to users with certain privileges that the caller does not have. Action: Check your documentation to verify the privileges required to run the mentioned procedure. Privilege type mismatch ORA-24278 Cause: A user can be granted privileges on an object as execute rights or just a user as library creation rights. These are different types of privileges. It is not possible to insert an object privilege into the user privilege table and vice versa. Action: Make sure the privilege type is correct. ORA-24279 Insufficient privileges to create library Cause: The user attempted to create a remote library without having the create remote library privilege.

12-106

message error

Action: A local database administrator should grant the remote user the create library privilege by calling DBMS_HS_EXTPROC.GRANT_CREATE_LIBRARY().

ORA-19400 to ORA-24279 12-107

12-108

message error

13 ORA-24280 to ORA-29249 ORA-24280 Invalid input value for parameter string Cause: The parameter received a negative, out-of-range, or NULL input value. Action: Correct the input value so that it is valid and is within the range specified in the documentation. ORA-24281 invalid access beyond maximum LOB parameter string size Cause: The value of the positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes. User Response : Correct the input values for the amount and offset so that their sum is less than or equal to 4 Gigabytes. If an error occurs in a read or write cycle, check the cycle conditions and/or offset increments. ORA-24300 Invalid value for mode Cause: An undefined mode value was specified. Action: Verify that the correct mode has been selected and that an allowed value has been specified for that mode. ORA-24301 null host specified in thread-safe login Cause: An HDA was not specified in the login call when running in a thread-safe environment. Action: Make sure that HDA is not NULL when calling the login routine. ORA-24302 Host connection in use by another thread Cause: An attempt was made to use the host connection while it was in use by another thread. Action: Wait for another thread to complete before using this connection.

ORA-24280 to ORA-29249

13-1

ORA-24303 call not supported on non-deferred bind Cause: One of the calls supported only on deferred bind was invoked when the client was non-deferred bind. Action: Use this call in lazy bind mode. ORA-24304 data type not allowed for this call Cause: Data of this data type cannot be sent or retrieved in chunks. User Response : Use other define or bind calls for this data type. ORA-24305 Invalid definition context or binding Cause: The call was made to a cursor for which it is invalid. Action: Check if this call is valid for this cursor. For example, get part information and set part information are valid on a cursor if the appropriate definitions and bindings have been made on that cursor. ORA-24306 Incorrect buffer for part Cause: A zero length buffer or a null buffer pointer was supplied. Action: Check that the buffer pointing to this part or its length is not zero. The buffer's pointer to the next piece or its length can be zero if it is the last piece to be inserted and there is no more data for the column. ORA-24307 Invalid length for part Cause: The length of the part exceeded the maximum possible size. Action: Verify that the length of this part and the cumulative length of all previous parts is not greater than the desired value provided by the application. ORA-24308 Invalid position set Cause: The call to modify attributes was made for a non-existent position. Action: Check whether a definition has been made for this position. ORA-24309 is already connected to a server Cause: This server identifier is already connected to a server. Action: Disconnect from the server and try the call again to establish a connection. ORA-24310 length specified for null connection string Cause: The connection string is null but a length was specified for it. User Response: Set the length to zero if the connection string is null.

13-2

message error

Memory initialization error ORA-24311 Cause: Cannot initialize user memory. Action: Contact Oracle Customer Support. ORA-24312 Illegal parameters specified to allocate user memory Cause: An illegal size or null pointer was specified in user memory. Action: Specify a legal size and a valid pointer to user memory. ORA-24313 user already authenticated Cause: A user was already authenticated under this service identifier. Action: Terminate the service context before using it for another user. ORA-24314 service identifier not initialized Cause: The server context does not exist. Action: Set the server context to the service context. ORA-24315 invalid attribute type Cause: An invalid attribute type was specified for the identifier. Action: See the Oracle Call Interface Programmer's Guide. to specify a valid attribute for this identifier. ORA-24316 Illegal identifier type Cause: An illegal identifier type was specified. Action: See the Oracle Call Interface Programmer's Guide. to specify a valid identifier type. ORA-24317 Set identifier used in a different position Cause: A definition was made with an existing identifier in a different position. Action: Specify the same position as before on a reset. ORA-24318 call not allowed for scalar data types Cause: This call is only valid for object types. User Response: Verify that the data type of this variable is an object type. ORA-24319 Could not allocate memory Cause: The process was unable to allocate memory to store diagnostics. Action: End other processes to reclaim the required memory.

ORA-24280 to ORA-29249

13-3

ORA-24320 unable to initialize a mutex Cause: An attempt to initialize a MUTEX failed. Action: Contact Oracle Customer Support. ORA-24321 inconsistent parameters passed Cause: One of the three memory function pointers is null or not null. User Response: Verify that all memory functions are null or not null. ORA-24322 cannot remove an initialized mutex Cause: An attempt to remove an initialized mutex failed. Action: Contact Oracle Customer Support. ORA-24323 Illegal value Cause: A null or invalid value was passed for a required parameter. Action: Verify that all required parameters are correctly initialized. ORA-24324 service identifier not initialized Cause: An attempt was made to use an inappropriate service context identifier. User Response: Check that the service context identifier has all the parameters initialized before this call. ORA-24325 This OCI operation is currently not allowed. Cause: An attempt was made to use a context identifier outside of its scope. User Response: Verify that the context identifier is set to a service context identifier that has been converted to a login data area for other OCI calls. The login data area must be converted back to a service context before it can be used. ORA-24326 Passed identifier is already initialized Cause: An attempt was made to pass an initialized identifier. User Response: Check that the parameter passed to retrieve an identifier does not already point to an identifier. ORA-24327 requires an explicit connection before authenticating a user Cause: A server context must be initialized before creating a session. Action: Create and initialize a server identifier. ORA-24328 invalid attribute value Cause: The passed attribute value is invalid.

13-4

message error

Action: See the Oracle Call Interface Programmer's Guide. and specify a legal attribute value for the identifier. ORA-24329 Invalid charset identifier Cause: The specified charset identifier is invalid. Action: Specify a valid charset identifier in the OCI call. Internal OCI Error ORA-24330 Cause: An internal OCI error occurred. Action: Contact Oracle Customer Support. ORA-24331 User buffer too small Cause: The user buffer to store the output data is too small. Action: Specify a larger buffer. ORA-24332 Invalid object type Cause: An invalid object type is requested for the describe call. User Response: Specify a valid object type for the describe call. ORA-24333 zero iteration count Cause: An iteration count of zero was specified for the declaration. Action: Specify the number of times this statement will be executed. ORA-24334 There is no descriptor for this position Cause: The application tries to get a description of an identifier for an illegal position. Action: Check the position number. ORA-24335 does not support more than 1000 columns Cause: The number of columns exceeds the maximum number supported. Action: Specify a number of columns less than 1000. ORA-24336 invalid result set descriptor Cause: The result set descriptor must have valid data fetched before it can be converted to a declaration identifier. Action: Get valid data from the descriptor before trying to convert it to a declaration identifier.

ORA-24280 to ORA-29249

13-5

Statement identifier ORA-24337 not prepared Cause: A statement cannot be executed before preparing a request. Action: Prepare a statement before attempting to execute it. ORA-24338 statement identifier not executed Cause: An attempt was made to get or describe before executing a statement identifier. Action: Execute a statement and then get or describe the data. ORA-24339 unable to set server group name after connecting to server Cause: An attempt was made to set the server group to a server identifier after connecting to the server. However, once the connection to a server is established, the server group name can no longer be configured. Action: Connect to the server after defining the server group name in the server identifier. ORA-24340 does not support more than 255 columns Cause: The number of columns exceeds the maximum supported by the server. Action: Limit your operation to 255 columns. ORA-24341 Invalid mode specified Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client. Action: OCI_ENV_NO_MUTEX can be specified when OCI_THREADED was specified at the start of the process. ORA-24342 unable to destroy a mutex Cause: An attempt to destroy a MUTEX failed. Action: Contact Oracle Customer Support. ORA-24343 User Defined Callback Error Cause: The only valid return value for a user defined callback function is OCI_CONTINUE. Any other value will cause this error. Action: Ensure that OCI_CONTINUE is returned from the user-defined callback function. Success ORA-24344 with compile error Cause: An SQL or PL/SQL compile error occurred. Action: Return OCI_SUCCESS_WITH_INFO along with the error code.

13-6

message error

ORA-24345 A null truncation or fetch error occurred. Cause: A null truncation or fetch error occurred. Action: Make sure that the buffer size is large enough to store the returned data. ORA-24346 cannot execute without bind variables Cause: None of the bind variables in the SQL statement are bound. Action: Bind all variables before execution completes. ORA-24347 Warning for a NULL column in an aggregate function Cause: An aggregate function processed a null column. Action: An OCI_SUCCESS_WITH_INFO is returned. ORA-24348 Update or Delete without Where Cause: An UPDATE or DELETE was performed without a WHERE clause. Action: An OCI_SUCCESS_WITH_INFO is returned. OCI ORA-24350 call not allowed Cause: The use of OCI from external procedures is not allowed. Action: See the Oracle Call Interface Programmer's Guide. for usage restrictions. ORA-24351 An invalid date was passed to the OCI call Cause: An invalid date was passed to one of the OCI calls. Action: Check your date binding values and correct them. ORA-24352 An invalid COBOL view type was passed to the OCI call Cause: An invalid COBOL view type was passed to one of the OCI calls. Action: Check the binding values of the COBOL view type and correct them. ORA-24353 User buffer too small to accommodate COBOL display type Cause: The user-supplied buffer for a COBOL display type was too small to accommodate the returned number. Action: Increase the allocation for the COBOL display type buffer. The number ORA-24354 returned is too large to fit in the COBOL display type buffer. Cause: The number returned was beyond the range that can be displayed. Action: Check the number in the database.

ORA-24280 to ORA-29249

13-7

ORA-24355 attempts to store a negative number in an unsigned display type. Cause: An attempt was made to convert a negative number to an unsigned display type. Action: Check the number in the database or change the defined data type. Internal error ORA-24356 during COBOL view type conversion. Cause: An internal error was encountered while converting to the COBOL display type. Action: Contact Oracle Customer Support. Internal error ORA-24357 when converting from to OCIDate. Cause: An internal error was encountered while casting to the OCIDate type. Action: Contact Oracle Customer Support. ORA-24358 OCIBindObject was not called for a reference type or object Cause: OCIBindObject was not called, resulting in an incomplete binding specification for a reference type or object. Action: Invoke the OCIBindObject call for all object types and references. ORA-24359 OCIDefineObject was not called for a reference type or object Cause: OCIDefineObject was not called, resulting in an incomplete binding specification for a reference type or object. User Response : Invoke the OCIDefineObject call for all object types and references. ORA-24360 The object type descriptor for object binding/defining was not specified. Cause: The object type descriptor is a required parameter for bindings and defines types of objects. User Response: Invoke the OCIBindObject() or OCIDefineObject() call with a valid type descriptor object. ORA-24361 The basic bind call was not called before the advanced bind call was called Cause: One of the basic bind calls was not called on this bind identifier before executing an advanced bind call. Action: Call the advanced call on this caller ID only after making a basic call. ORA-24362 Incorrect use of character count flag Cause: When setting the character count flag, the maximum buffer size on the server must be specified as a non-zero value.

13-8

message error

User Response : Use a non-zero value for the maximum buffer size on the server. ORA-24363 invalid character measurements here Cause: Character measurements instead of bytes are illegal if the server or client character set has a variable width. Action: If the client or server character set has a variable width, do not use the OCI_ATTR_CHAR_COUNT attribute for the binding identifier. Use OCI_ATTR_MAXDATA_SIZE instead. ORA-24364 internal error padding blanks Cause: An internal error occurred while trying to fill blank string data. This error should not normally occur. Action: Contact Oracle Customer Support. ORA-24365 Character Conversion Error Cause: This typically occurs when converting multi-byte character data when the source data abends in the middle of a multi-byte character. Action: Make sure that all multibyte character data is properly terminated. ORA-24366 Migratable User Identifier is defined in the Service Identifier Cause: This occurs during user authentication, a Migratable User Identifier has been defined in the Service Identifier. Action: The service identifier should not be configured as a migrable user identifier when it is used to authenticate another user. ORA-24367 user id not defined in service id Cause: This occurs when authenticating a migrated user. undefined service id with non-migrable user id. Action: The service identifier should be set to a nonmigratory user identifier when it is used to authenticate a migrated user. ORA-24368 Non-zero OCI mutex counter when dropping an identifier Cause: This is an internal OCI error. Action: Contact Oracle Customer Support. ORA-24369 Required callbacks were not registered for one or more binding identifiers Cause: No callbacks were registered for one or more binding identifiers that are part of the RETURNING clause.

ORA-24280 to ORA-29249

13-9

Action: Bind handlers that are to receive data in a DML statement with a RETURNING clause must have their mode set to DATA_AT_EXEC, and callback functions must be registered for these bind handlers using OCIBindDynamic. ORA-24370 Illegal chunked operation attempt Cause: Data of a certain data type that does not support chunked operation is sent or retrieved in chunks. Action: Always set the part value to OCI_ONE_PIECE for data types that do not support piecewise operation. ORA-24371 data did not fit in the current prefetch buffer Cause: An internal OCI error occurred. Action: Contact Oracle Customer Support. ORA-24372 Invalid object to describe Cause: The object to describe is invalid. You have compile or authorization errors. Action: The object to describe must be valid. ORA-24373 Invalid length specified for declaration Cause: The length specified for the declaration is 0 or too long. Action: Specify a valid length for the declaration. ORA-24374 not set before find or execute and find Cause: The application did not set the output variables for the data being searched before issuing a search call or invoking a search specifying a non-zero row count in a execution call. Action: Issue OCI define calls to get the columns. ORA-24375 Cannot use V6 syntax when communicating with a V8 server Cause: V6 syntax is no longer supported by the V8 server. Action: Change the syntax to V7 or higher syntax. ORA-24376 cannot register/get user callback for non-environment handle Cause: An attempt to register or get user callback on a non-environment handle. Action: Pass the environment identifier to register/get the user callback.

13-10 Error messages

ORA-24377 invalid OCI function code Cause: An invalid function code was used to register or obtain a callback from the user. Action: Use a valid OCI function code. ORA-24378 User callbacks are not allowed for this call Cause: An attempt was made to register a user callback for an OCI call for which user callbacks are not allowed to be registered. Action: Do not register the user callback for this OCI call. ORA-24379 Invalid user callback type Cause: An invalid user callback type was specified. User Response: Specify a valid user callback type. Invalid mode specification ORA-24380 Cause: The mode parameter on an OCIU* call is invalid. Action: Use only a valid mode parameter. ORA-24381 error(s) in DML array Cause: One or more lines failed in the DML. Action: Query the error stack in the error handler. ORA-24382 handled statement already executed or described Cause: The handled statement was successfully executed or described above. Action: Rerun OCIstmtPrepare before OCI_PARSE_ONLY. ORA-24383 Unable to describe an IOT overflow segment Cause: The name specified in the OCIDescribeAny call refers to an IOT overflow segment. Action: Use OCIDescribeAny to describe only documented objects. ORA-24750 Incorrect attribute length Cause: The transaction ID attribute length is incorrect. User Response : Check that the size parameter is correct. ORA-24752 The OCI_TRANS_NEW flag must be specified for local transactions. Cause: The application tried to start a local transaction without using OCI_TRANS_NEW. Action: Use OCI_TRANS_NEW when starting local transactions.

ORA-24280 to ORA-29249

13-11

ORA-24753 Local transactions cannot be detached Cause: An attempt was made to detach a local transaction. Action: Local transactions can only be committed or rolled back. ORA-24754 unable to start a new transaction with an active transaction Cause: An attempt was made to start a new transaction when there was an active transaction. Action: Commit, roll back, or disconnect the existing transaction before starting a new transaction. ORA-24755 OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported Cause: These flags are not currently supported. Action: No action is required. Transaction ORA-24756 does not exist Cause: An invalid transaction identifier or context was used or the transaction was completed. Action: Provide a valid identifier if the transaction did not complete and retry the call. Duplicate transaction identifier ORA-24757 Cause: An attempt was made to start a new transaction with an identifier that was already in use by an existing transaction. User Response : Check that the identifier is not in use. ORA-24758 not attached to requested transaction Cause: An attempt was made to disconnect or complete a transaction that is not the current transaction. User Response: Verify that the transaction context refers to the current transaction. ORA-24759 Invalid transaction start flags Cause: An invalid transaction start flag was passed. Action: Check if any of the values OCI_TRANS_NEW, OCI_TRANS_JOIN, or OCI_TRANS_RESUME were specified. ORA-24760 invalid isolation level flags Cause: An invalid isolation level flag was passed.

13-12 Error messages

Action: Check that only one of the following values is used: OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE. ORA-24761 transaction rolled back Cause: The application tried to commit a transaction and the server rolled it back. Action: No action is required. ORA-24762 server failed due to unspecified error Cause: An internal error occurred in the server commit protocol. Action: Contact Oracle Customer Support. Transaction operation ORA-24763 cannot be completed now. Cause: Cannot commit or rollback now because the session cannot switch to the specified transaction. Action: Repeat the operation later. Transaction branch ORA-24764 was heuristically committed. Cause: This is an informational message. Action: No action is required. Transaction branch ORA-24765 was heuristically rolled back. Cause: This is an informational message. Action: No action is required. Transaction branch ORA-24766 was partially committed and stopped. Cause: This is an informational message. Action: No action is required. Transaction ORA-24767 was read-only and committed Cause: This is an informational message. Action: No action is required. An ORA-24768 handshake error occurred on the server. Cause: This is an internal error. Action: Contact Oracle Customer Support.

ORA-24280 to ORA-29249

13-13

ORA-24769 cannot forget an active transaction Cause: The transaction identifier refers to an active transaction. User Response: Check that an active transaction identifier is not passed as an argument. ORA-24770 cannot forget a prepared transaction Cause: The transaction identifier refers to a prepared transaction. User Response : Check that a prepared transaction identifier is not passed as an argument. ORA-24771 cannot disconnect, prepare, or forget a local transaction Cause: The service identifier contains a local transaction context. User Response: Check that the transaction context does not refer to a local transaction. ORA-24772 Cannot merge tightly coupled and loosely coupled branches Cause: The application tried to start a transaction with a global transaction identifier and an incorrect option. Action: Check that all branches of a global transaction are started with the OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact Oracle Customer Support. ORA-24773 Invalid transaction type flags Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified. Action: Verify that the correct parameters are being used. ORA-24774 cannot change to specified transaction Cause: The transaction specified in the call refers to a transaction created by a different user. Action: Create transactions with the same authentication so they can be exchanged. ORA-24775 cannot prepare or commit transaction with non-zero lock value Cause: An attempt was made to disconnect the transaction with a non-zero lock value. Action: Detach the transaction with the lock value set to zero and try to prepare or commit the transaction.

13-14 Error messages

ORA-24776 unable to start a new transaction Cause: An attempt was made to start a new transaction when the session was already attached to an existing transaction. Action: End the current transaction before creating a new transaction. ORA-24777 The use of a non-migrable database link is not allowed. Cause: The transaction, which should be portable between sessions, tried to access a remote database from a non-threaded server process. Action: Run the job on the local database or open a connection to the remote client database. If the multithreaded server option is installed, connect to the Oracle instance through the dispatcher. ORA-24778 cannot open connections Cause: The migrateable transaction attempted to access a remote database when the session itself opened connections to remote databases. Action: Close the connections in the session and try to access the remote database from the migratable transaction. If the error persists, contact Oracle Customer Support. ORA-24779 Detach not allowed with remote cursor open Cause: The migrateable transaction attempted to detach from the current session while a remote cursor is open. Action: Close all open remote cursors before detaching them. ORA-24780 Unable to roll back a transaction while in an existing transaction Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is inactive for a long time). Action: Detach from the current transaction and retry the operation. ORA-24781 branches do not belong to the same global transaction Cause: The list of xids passed to kpotxmp() does not have the same gtrid ORA-24801 illegal parameter value in the OCI lob function Cause: One of the values of parameter in the OCI LOB function is illegal. Action: Check all the parameters in the OCI Lob function call to make sure they are correct. Offsets must be greater than or equal to one.

ORA-24280 to ORA-29249

13-15

ORA-24802 User-defined LOB read callback error Cause: The only valid return value for a user-defined LOB read callback function is OCI_CONTINUE. Any other value will cause this error. Action: Verify that OCI_CONTINUE is returned from the user-defined read LOB callback function. ORA-24803 invalid parameter value in read lob function Cause: This is an internal error. Action: This error should not normally occur. If it persists, contact Oracle Customer Support. ORA-24804 Illegal parameter value in lob write function Cause: This is an internal error. Action: This error should not normally occur. If it persists, contact Oracle Customer Support. ORA-24805 LOB type mismatch Cause: When copying or adding LOB locators, the source and destination LOB locators must be of the same type. Action: Pass the same type of LOB locators to copy or add. ORA-24806 LOB form mismatch Cause: When reading or writing to LOBs, the charset format of the user buffer must be the same as the LOB. Action: Make sure that the buffer you are using to read or write has the same format as the LOB. ORA-24807 LOB form mismatch Cause: When copying or adding LOBs, the source and destination LOB locators must have the same charset format. Action: Pass locators of the same charset form to copy or add LOBs. ORA-24808 LOB data streaming is not allowed when LOB buffering is used. Cause: An attempt was made to transmit LOB data via polling mode or a callback when LOB buffering was enabled for the locator input LOB. Action: Lob buffering is useful when reading or writing small amounts of LOB data, so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. if you are transmitting

13-16 Error messages

of data, the LOB buffer should not be used. In this case, flush the buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator, and reissue the OCILobRead/OCILobWrite call. The specified ORA-24809 quantity does not fit in the LOB buffers. Cause: LOB buffering is enabled for the incoming LOB locator, so the buffer will be used. However, the amount of LOB data to read or write is larger than the LOB buffers can hold. Action: Turn off buffering on the input LOB locator and either reissue the command or pass a smaller amount. ORA-24810 attempting to write more data than indicated Cause: When writing to a LOB, more data than indicated was provided. Action: If the data is written in chunks, ensure that you do not provide more chunked (cumulative) data than indicated. ORA-24811 Less data was provided for writing than indicated Cause: While writing to a LOB, less data was provided than indicated. Action: If you write data to individual chunks, ensure that the specified buffer size is large enough to accommodate the supplied data. If the data is written in chunks, be sure to provide all the data before specifying OCI_LAST_PIECE. ORA-24812 charset conversion to or from UCS2 failed Cause: If the database charset has a variable width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed. Action: Contact Oracle Customer Support. ORA-24813 cannot send or receive an unsupported LOB Cause: An attempt was made to send a LOB over the network, but the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and the server are running different versions of Oracle. Action: Use a version of Oracle that supports LOBs on both the client and the server. ORA-24850 failed to initialize shared subsystem Cause: While trying to initialize OCI in shared mode, a problem was encountered starting the shared subsystem.

ORA-24280 to ORA-29249

13-17

Action: Contact Oracle Customer Support. ORA-24851 Failed to connect to shared subsystem Cause: When trying to start OCI in shared mode, a problem was encountered connecting the process to the shared subsystem. Action: Contact Oracle Customer Support. ORA-24852 protocol error during statement execution Cause: An internal protocol error occurred while receiving descriptive data from the server during statement execution. Action: Contact Oracle Customer Support. ORA-24853 could not connect thread to shared subsystem Cause: When trying to start OCI in shared mode, a problem was encountered connecting the thread to the shared subsystem. Action: Contact Oracle Customer Support. ORA-24900 Invalid or unsupported mode parameter passed in call Cause: The mode parameter passed to the OCI client notification call is incorrect. Action: Correct the mode parameter passed to OCI. ORA-24901 Identifiers belonging to different environments passed to an OCI call Cause: All identifiers passed to an OCI call must belong to the same environment. In the call that returned this error, identifiers belonging to different environments were passed. Action: Make sure that the identifier parameters in the call come from the same OCI environment. ORA-24902 Invalid signature name or name length in signature identifier Cause: The signature identifier passed to the OCI call does not have a proper name or name length attribute. User Response : Set the name and name length attributes using the OCIAttrSet() call. ORA-24903 Invalid namespace attribute passed to OCI call Cause: The subscription identifier passed to the OCI call does not have a proper NAMESPACE attribute. User Response : Set the NAMESPACE attribute using the OCIAttrSet() call.

13-18 Error messages

ORA-24904 Invalid callback attribute passed to OCI call Cause: Signature identifier passed to OCI call does not have a proper callback attribute. Action: Set the callback attribute using the OCIAttrSet() call. ORA-25000 Invalid use of bind variable in trigger WHEN clause Cause: A bind variable was used in the when clause of a trigger. Action: Delete the binding variable. To access the columns of the table, use (new/old).column_name . ORA-25001 cannot create this type of trigger on views Cause: INSTEAD OF triggers can only be created on a view. Action: Change the trigger type to INSTEAD OF. ORA-25002 cannot create INSTEAD OF triggers on tables Cause: You can only create triggers BEFORE or AFTER a table. Action – Change the trigger type to BEFORE or AFTER. ORA-25003 cannot change the NEW values for this type of column in the trigger Cause: Attempting to change the NEW trigger variables of the object of data type, REF, nested table, VARRAY or LOB data type that is not supported. Action: Do not change the NEW trigger variables in the body of the trigger. ORA-25004 WHEN clause is not allowed in INSTEAD OF triggers Cause: The WHEN clause is specified in an INSTEAD OF trigger. Action: Remove the WHEN clause when creating an INSTEAD OF trigger. ORA-25005 cannot trigger CREATE INSTEAD on a read-only view Cause: An attempt was made to create a trigger INSTEAD OF on a view created with the read-only option. View cannot be updated with INSTEAD OF triggers. Action: Do not create the trigger. ORA-25006 cannot specify this column in the UPDATE OF clause Cause: Attempt to create a trigger on update of a column whose data type is not allowed in the clause, such as LOB and nested table. Action: Remove the UPDATE OF clause.

ORA-24280 to ORA-29249

13-19

ORA-25007 Functions or methods not allowed in WHEN clause Cause: PL/SQL function or method call is not allowed in WHEN clause when creating a trigger. User Response: Remove the function call or method invocation from the WHEN clause. ORA-25008 no implicit conversion to LOB data type in trigger instead of Cause: When inserting or updating a view using the trigger instead, the new value for a LOB view column is of a different data type. User Response : You specified a LOB value as the new value for the LOB view column. ORA-25009 Nested table clause is only allowed for INSTEAD OF triggers Cause: Triggers on nested tables can only be created on view columns using INSTEAD OF triggers. User Response : Use nested view table columns to define nested table triggers. ORA-25010 Invalid nested table column name in nested table clause Cause: The column name specified in the nested table clause of an INSTEAD OF trigger does not match a nested table column. Action: Specify a nested table column on which the trigger will be defined. ORA-25012 PARENT and NEW values cannot be identical Cause: The reference clause specifies identical values for PARENT and OLD. Action: Re-enter the PRIMARY or NEW reference value. ORA-25013 OLD and PARENT values cannot be identical Cause: The reference clause specifies identical values for OLD and PARENT. User Response: Re-specify the OLD or PARENT reference value. ORA-25014 cannot change the value of a PRINCIPAL reference variable Cause: Primary values can only be read and not changed. Action: Do not try to change a primary variable. ORA-25015 cannot execute DML on this nested table view column Cause: DML cannot be executed on a nested table view column except through an INSTEAD OF trigger. Action: Create an INSTEAD OF trigger on the nested table view column, and then run the DML.

13-20 Error messages

ORA-25016 cannot specify column list to insert into nested table view column Cause: Unable to specify column list to insert into nested table view column. User Response : Specify all the columns to insert into the nested table. ORA-25017 cannot reference NEW ROWID to move rows in previous triggers Cause: NEW ROWID was referenced in a previous row trigger that is defined on an index-organized table or a partitioned table with row movement enabled. The ROWID cannot be calculated in a previous row update trigger because it depends on the actual row values. User Response: Remove references to NEW ROWID from the trigger definition. ORA-25100 TABLESPACE option can only be used with ALTER INDEX REBUILD Cause: The TABLESPACE option for ALTER INDEX was used without the REBUILD option. User Response: Use the table space name ALTER INDEX REBUILD TABLESPACE. ORA-25101 Duplicate REBUILD option specification Cause: The REBUILD option for ALTER INDEX was specified more than once. Action: Specify the option at most once. ORA-25102 PARALLEL option can only be used with ALTER INDEX REBUILD Cause: The PARALLEL option for ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25103 The NOPARALLEL option can only be used with ALTER INDEX REBUILD Cause: The NOPARALLEL option for ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25104 UNRECOVERABLE option can only be used with ALTER INDEX REBUILD Cause: The UNRECOVERABLE option for ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD.

ORA-24280 to ORA-29249

13-21

ORA-25105 RECOVERABLE option can only be used with ALTER INDEX REBUILD Cause: The RECOVERABLE option for ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25106 only PARALLEL or NOPARALLEL clause can be specified Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement. Action: Remove all but one of the PARALLEL or NOPARALLEL clauses. ORA-25107 Duplicate TABLESPACE option specification Cause: TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement. User Response: Remove all but one of the TABLESPACE clauses. ORA-25108 Standby lock namespace exceeds string length limit Cause: The lock namespace for the standby database exceeded the maximum string length. Action: Change the initialization parameter _STANDBY_LOCK_NAME_SPACE to a string shorter than the specified characters. ORA-25109 standby lock namespace has invalid character 'string' Cause: An invalid lock namespace was specified for the standby database. The lock namespace for the standby database can only contain A-Z, 0-9, '_', '#', '$', '.' and the '@' characters. Action: Change the initialization parameter _STANDBY_LOCK_NAME_SPACE to a valid string. ORA-25110 NOSORT cannot be used with a bitmap index Cause: An attempt was made to create a bitmap index using the NOSORT option. Action: Remove NOSORT from the CREATE BITMAP INDEX statement. ORA-25111 BITMAP cluster index creation is not supported Cause: An attempt was made to create a cluster index with the BITMAP attribute. Action: Remove BITMAP from the CREATE INDEX statement.

13-22 Error messages

ORA-25112 The maximum number of columns in the BITMAP index is 30 Cause: Too many columns were specified for the index. Action: Create an index on fewer columns. ORA-25113 GLOBAL cannot be used with a bitmap index Cause: An attempt was made to create a bitmap index using the GLOBAL option. Action: Remove GLOBAL from the CREATE BITMAP INDEX statement and/or add a LOCAL partition descriptor if the table is partitioned. ORA-25114 Invalid file number specified in DUMP DATAFILE/TEMPFILE command Cause: An invalid file number was used when dumping a data file or temporary file. Action: Specify a valid file number. ORA-25115 Duplicate BLOCK option specification Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command. Action: Specify only one BLOCK option. ORA-25116 Invalid block number specified in DUMP DATAFILE/TEMPFILE command Cause: An invalid block number was used when dumping a data file or temporary file. Action: Specify a valid block number. ORA-25117 MIN/MAX/Expected block number Cause: A value other than MIN/MAX or block number was entered in the DUMP DATAFILE/TEMPFILE command. Action: Correct the syntax. ORA-25118 Invalid DUMP DATAFILE/TEMPFILE option Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command. Action: Correct the syntax.

ORA-24280 to ORA-29249

13-23

ORA-25119 LOGGING/NOLOGGING option already specified Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once. Action: Delete all but one of the registry specifications. ORA-25120 MINIMUM EXTENT option already specified Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once. Action: Remove all but one of the MIN EXTENT specifications. ORA-25121 MIN EXTENT value greater than maximum extent length Cause: In CREATE/ALTER TABLESPACE, the value specified for the MIN EXTENT option was greater than the maximum extent length. Action: Choose a smaller value for the MIN EXTENT option. ORA-25122 Only LOCAL bitmap indexes are allowed on partitioned tables Cause: An attempt was made to create a global bitmap index on a partitioned table. User Response: Create a local bitmap index instead. ORA-25123 Too many components specified in the name. Cause: More components were specified by name than allowed. Action: Check the name specified for the operation. ORA-25124 Illegal database link name. Explanation: A database link name was specified when it is not allowed. Action: Check the name specified for the operation. ORA-25125 The BUFFER_POOL storage option is not allowed Cause: An attempt was made to specify the BUFFER_POOL storage option. This option can only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX. Action: Clear this option and repeat the statement. ORA-25126 Invalid name specified for BUFFER_POOL Cause: The user-specified buffer pool name is invalid. The only valid names are KEEP, RECYCLE, and DEFAULT. Action: Use a valid name or remove the BUFFER_POOL clause.

13-24 Error messages

ORA-25127 TRUST not allowed on NOT NULL constraint Cause: An attempt was made to enable TRUST for the NOT NULL constraint. Action: NORELY can only be specified for a NOT NULL constraint. ORA-25128 No insert/update/delete on table with constraint (string.string) disabled and validated Cause: An attempt was made to insert/update/delete on table with constraint DISABLE VALIDATE. Action: Change the restriction states. ORA-25129 cannot modify constraint (string): This constraint does not exist Cause: The named constraint does not exist for this table. User Response: Try again with an existing constraint for this table. ORA-25130 unable to modify primary key: primary key is not defined for table Cause: An attempt was made to modify a primary key that is not defined for the table. Action: No action is required. ORA-25131 cannot modify unique (string): unique key not defined for table Cause: An attempt was made to modify a unique key that is not defined for the table. Action: No action is required. ORA-25132 UNIQUE (string.string) constraint disabled and validated on ALTER TABLE EXCHANGE PARTITION Cause: Unable to ALTER TABLE EXCHANGE PARTITION when partition and table have unique constraints disabled and validated AND the unique keys in the partition are not mutually exclusive from the rest of the table. Action: Change the state of the constraint. ORA-25133 Duplicate SINGLE TABLE option specified Cause: The SINGLE TABLE option was specified more than once. User Response : Specify the SINGLE TABLE option only once. ORA-25134 TABLE keyword expected Cause: The TABLE keyword is missing from the SINGLE TABLE option. Action: Place the TABLE keyword after the SINGLE keyword in the command.

ORA-24280 to ORA-29249

13-25

ORA-25135 cannot use the SINGLE TABLE option Cause: The SINGLE TABLE option is only valid for hash clusters. User Response: Do not specify the SINGLE TABLE option. ORA-25136 This cluster can only contain one table Cause: An attempt was made to store more than one table in a cluster created with the SINGLE TABLE option. User Response: Do not try to store more than one table in the cluster. ORA-25137 Data value out of range Cause: The value of the cast operand is greater than the size of the cast target. Action: Increases the size of the thrown target. String initialization parameter ORA-25138 has become obsolete Cause: An obsolete initialization parameter was specified. Action: The system will be activated, but the parameters must be examined. ORA-25139 Invalid option to CREATE TEMPORARY TABLE SPACE Cause: An invalid option appears. Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM. String space policy ORA-25140 cannot be specified for handling string extensions. Cause: An invalid option appears. Action: Ensure that UNIFORM or AUTOALLOCATE is specified for LOCAL extension management and that UNIFORM or AUTOALLOCATE is not specified for extension management DICTIONARY ORA-25141 Invalid EXTENT MANAGEMENT clause Cause: An invalid option appears for the EXTENT MANAGEMENT clause . Action: Specify one of the valid options: UNIFORM SIZE, AUTO ALLOCATION. ORA-25142 Default store clause specified twice Cause: The default store clause was specified twice to create a table space. Action: Specify it once.

13-26 Error messages

ORA-25143 default store clause is not compatible with allocation policy Cause: A default store clause was specified for a table space with the AUTOALLOCATE or UNIFORM policy. Action: Skip the store clause. ORA-25144 Invalid option to CREATE TABLE SPACE with TEMPORARY content Cause: An invalid option appears. Action: Specify one of the valid options: EXTENSION MANAGEMENT DICTIONARY, USER. ORA-25145 Allocation policy already specified Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example AUTOALLOCATE and UNIFORM. Action: Remove all but one of the allocation policy specifications. ORA-25146 EXTENSION MANAGEMENT option already specified Cause: In CREATE TABLESPACE, the EXTENSION MANAGEMENT option was specified more than once. Action: Remove all but one EXTENSION MANAGEMENT specification. ORA-25147 The value of UNIFORM SIZE is greater than the maximum extent size Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size. Action: Choose a smaller value for the UNIFORM SIZE option. ORA-25148 ONLINE option not allowed Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not organized by indexes. Currently, the ONLINE option is only supported for index-organized tables. Action: Remove the ONLINE option from the command. ORA-25149 Columns of type UROWID cannot be indexed Cause: An attempt was made to create an index on a column of type UROWID. User Response : Remove the column from the list of indexed columns. ORA-25150 CHANGE of extension parameters not allowed Cause: An attempt was made to change the extension parameters for a segment in a tablespace with automatic allocation or uniform extension allocation policy.

ORA-24280 to ORA-29249

13-27

User Response : Remove the appropriate extension parameters from the command. ORA-25151 Cannot create a rollback segment in this tablespace Cause: An attempt was made to create a rollback segment in a tablespace with autoallocate extension allocation policy. User Response : Specify a different tablespace for the rollback segment. ORA-25152 TEMPFILE cannot be dropped at this time Cause: An attempt was made to drop a TEMPFILE that was being used by online users. Action: The TEMPFILE was disconnected. Try later. ORA-25153 Temporary table space is empty Cause: An attempt was made to use space in a temporary table space with no files. User Response : Add files to the table space using the ADD TEMPFILE command. ORA-25175 No PRIMARY KEY constraint found Cause: A PRIMARY KEY constraint must be defined for a table with this organization. Action: Define a PRIMARY KEY. ORA-25176 storage specification not allowed for primary key Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization. User Response : Remove the storage specification for the primary key. ORA-25177 UNRECOVERABLE option not allowed Cause: The UNRECOVERABLE option cannot be specified for a primary key for a table with this organization. Action: Remove the UNRECOVERABLE option from the primary key. ORA-25178 duplicate PCTTHRESHOLD storage option specification Cause: The PCTTHRESHOLD storage option was specified more than once. Action: Specify storage options at most once. ORA-25179 Invalid value of storage option PCTTHRESHOLD Cause: The value specified must be a positive integer. Action: Specify an appropriate value.

13-28 Error messages

ORA-25180 PCTTHRESHOLD is only valid for certain table organizations. Cause: PCTTHRESHOLD can only be specified for tables with certain organizations. Action: Remove the PCTTHRESHOLD option. ORA-25181 Missing ON keyword for NESTED INDEX Cause: The ON keyword is required to specify nesting of nested index columns. Action: Add the ON keyword. The ORA-25182 feature is currently not available for index-organized tables Cause: An attempt was made to use one or more of the following currently unsupported features for index-organized tables: ■

CREATE TABLE with LOB/BFILE/VARRAY columns

■

partition options/PARALLEL/CREATE TABLE AS SELECT

■

ALTER TABLE with ADD/MODIFY column options

■

(Video) Oracle Autonomous Database Technical Overview

CREATE INDEX

Action: Do not use features not supported in this version. ORA-25183 The index segment at the top of the index-organized table is in a different table space Cause: An attempt was made to drop a table space that contains only an index table overflow segment, but not the index table overflow segment. top index. Action: Locate the index-organized tables that span the table space being dropped and some other table spaces. Leave those tables. ORA-25184 column name expected Cause: No column name is present when CREATE TABLE requires it to specify the last column to include in the index segment of the index-organized table. User Response : Specify a column name when the syntax requires it. ORA-25185 Cannot specify non-last index column for INCLUDE clause Cause: Non-last index column name was specified as include column. Action: Specify a column name that is not part of the index-organized table's primary key index or the last key column of the primary key for the INCLUDING clause.

ORA-24280 to ORA-29249

13-29

ORA-25186 INCLUDING clause specified for index-organized table without OVERFLOW Cause: The INCLUDING clause of CREATE TABLE is a valid option only for index-organized tables with an OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER moment). Action: Specify the OVERFLOW clause for the index-organized table: For ALTER, first execute ADD OVERFLOW. ORA-25187 An incorrect exception table form was specified. Cause: The specified table does not have proper field definitions. Action: Specify the correct table to use. ORA-25188 cannot drop/disable/defer primary key constraint for index-organized tables Cause: An attempt was made to DROP, DISABLE, or DEFER the primary key constraint for an index-only table. This is not allowed. Action: Do not DROP, DISABLE, or DEFER the primary key constraint to an index-only table. ORA-25189 Invalid ALTER TABLE option for an index-organized table Cause: During ALTER of an index-organized table, the user attempted to enter one or more of the following options: TABLESPACE, ALLOCATE/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment Action: Remove the illegal option(s). ORA-25190 an index-organized table maintenance operation cannot be combined with other operations Cause: The ALTER TABLE statement attempted to combine an index-organized table maintenance operation (for example, changing physical attributes) with some other operation (for example example, ADD constraint) that is illegal Action: Ensure that an index-organized table maintenance operation is the only operation specified on the ALTER TABLE statement. ORA-25191 cannot reference the overflow table of an index-organized table Cause: An attempt was made to directly access the overflow table of an index-organized table. User Response : Issue the statement for the main index-organized table that contains the specified overflow table.

13-30 Error messages

ORA-25192 invalid option for an index-organized table Cause: An attempt was made to specify one or more of the following options for an index-organized table: [NO] CACHE, NO LOGGING, CLUSTER. Action: Remove the illegal options. ORA-25193 cannot use the COMPRESS option for a single column key Cause: An attempt was made to use the COMPRESS option on a single column key. Action: Remove the COMPRESS option. ORA-25194 Invalid COMPRESS prefix length value Cause: The specified value must be a positive integer less than the number of key columns. Action: Specify an appropriate value. ORA-25195 invalid option for index on an index-organized table Cause: An attempt was made to specify one or more of the following options for the index on an IOT: BITMAP, REVERSE, PCTUSED. Action: Specify an appropriate option. ORA-25196 MOVE keyword in ALTER TABLE MOVE must immediately follow table_name Cause: MOVE specified after one or more ALTER options. Action: Change the order of the options, MOVE must be first, or remove the illegal option(s). ORA-25197 Segment overflow already exists for index-organized table Cause: An attempt was made to ADD an OVERFLOWed segment to an index-organized table that already has a segment overflow. Action: No action is required. ORA-25198 Only range partitioning is supported for index organized table. Cause: Composite, system, or hash partitioning schemes are not supported. Action: Select a different partition scheme. ORA-25199 The partition key of an index-organized table must be a subset of the primary key Cause: An attempt was made to specify a partition key that is not a prefix of the primary key of the index-organized table.

ORA-24280 to ORA-29249

13-31

Action: Select a different partition key. ORA-25200 invalid string value, QUEUE_NAME must be [SCHEMA.]NAME Explanation : A NULL parameter was specified for QUEUE_NAME. User Response: Specify a non-NULL queue name. ORA-25201 invalid value, VISIBILITY must be ON_COMMIT or IMMEDIATE Cause: An invalid value was specified for the VISIBILITY parameter. Action: Specify ON_COMMIT or IMMEDIATE. ORA-25202 invalid value NULL, string must not be NULL Cause: A NULL value was specified for the parameter. Action: Specify a non-null value. ORA-25203 Invalid value string, DELAY must be non-negative Cause: A negative or NULL value was specified for DELAY. Action: Specify a non-negative integer for DELAY. ORA-25204 invalid value, SEQUENCE_DEVIATION must be BEFORE or ABOVE Cause: An invalid SEQUENCE_DEVIATION was specified. Action: Specify the 'BEFORE' or 'ABOVE' option. ORA-25205 QUEUE string.string does not exist Cause: The specified queue does not exist. Action: Create the queue before specifying it to enqueue or delete. Enqueue failed ORA-25206, enqueue to exception queue string.string not allowed Cause: An attempt was made to enqueue to an exception queue. Action: Try queuing in another queue. Queue failed ORA-25207, queue string.string is disabled for queuing Cause: Queue was stopped to prevent further queuing. Action: Activate the queue first through an administrative operation. ORA-25208 RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE Cause: A relative message identifier must be specified if sequence deviation is specified as BEFORE.

13-32 Error messages

Action: Specify an existing relative message identifier or do not specify the sequence offset as BEFORE. ORA-25209 invalid string value, EXPIRATION must be non-negative or NEVER Cause: Expiration is less than zero or NULL. Action: Specify a valid value for EXPIRE_AFTER that must be greater than or equal to zero or NEVER. ORA-25210 Invalid value for RELATIVE_MSGID, no queued message with this msgid Cause: There is no queued message with MSGID equal to the specified RELATIVE_MSGID. Action: Try again with a valid RELATIVE_MSGID. ORA-25211 An invalid LAG was specified when using sequence offset. Cause: The DELAY specified in the queue is greater than the delay of the message with the given relative message ID. Action: Set the LAG to be less than or equal to the delay of the message with the given relative message ID. If the TOP option is used, the delay must be less than or equal to the delay of all messages in the queue. ORA-25212 Invalid PRIORITY specified when using resequence. Cause: The PRIORITY specified in the queue is lower than the priority of the message with the given relative message ID. Action: Set the PRIORITY to be less than the message delay with the given relative message ID. If the TOP option is used, the priority must be greater than or equal to the priority of all messages in the queue. Message ORA-25213 with the specified RELATIVE_MSGID has been removed from the queue. Cause: The message specified by the RELATIVE_MSGID field in the stream branch option BEFORE was removed from the queue. Action: No action is required. this is an informational message only. ORA-25215 User data type and queue type do not match Cause: A user attempts to enqueue an object to a queue that was created for objects of different types. Action: Try to enqueue again with an object of the correct type.

ORA-24280 to ORA-29249

13-33

ORA-25216 Invalid recipient, NAME, or ADDRESS must be specified Cause: The NAME and ADDRESS attributes were specified null for one of the recipients in the recipient list. Action: Specify a non-null NAME or ADDRESS for the recipient. Error enqueue ORA-25217, visibility must be IMMEDIATE for queue string.string Cause: An attempt was made to enqueue a non-persistent queue without setting the visibility to IMMEDIATE. Action: Set the visibility to IMMEDIATELY. Queue failed ORA-25218, delay must be zero for queue string.string Cause: An attempt was made to enqueue a non-persistent queue with a delay greater than zero seconds. Action: Set the delay to zero. Enqueue error ORA-25219, stream offset not allowed for queue string.string Cause: An attempt was made to enqueue a non-persistent queue with the specified stream offset. Action: Do not specify the sequence offset. ORA-25225 invalid value string, DEQUEUE_MODE must be REMOVE or BROWSE or LOCKED Cause: An invalid parameter was specified for DEQUEUE_MODE. Action: Specify DELETE, BROWSE, or BLOCKED. ORA-25226 dequeue failed, queue string.string is not enabled for dequeue Cause: The queue was not enabled for dequeue. Action: Activate the queue using START_QUEUE. ORA-25228 Timeout or expiration on dequeuing messages from string.string Cause: The user-specified dequeue timeout has passed or the end of the queue has been reached, but has not been reached. retrieved no message. Action: Try to remove the queue again with the appropriate WAIT_TIME or FIRST_MESSAGE option. ORA-25230 invalid string value, WAIT must be non-negative Cause: A negative value was specified for WAIT.

13-34 Error messages

Action: Specify a non-negative value or FOREVER. ORA-25231 Unable to delete from queue because CONSUMER_NAME was not specified Cause: A user tried to delete from a queue that was created for multiple consumers, but CONSUMER_NAME was not specified in the delete options. Action: Specify CONSUMER_NAME in the dequeue options. ORA-25232 Duplicate recipients were specified for message Cause: A queue with duplicate queue agents was made in the recipients parameter. Action: Delete the duplicate queue agent and retry the call. ORA-25233 An invalid parameter was specified for NAVIGATION Cause: An invalid parameter was specified for NAVIGATION. Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE, or NEXT_TRANSACTION. Use FIRST_MESSAGE to dequeue the first message that meets the criteria, NEXT_MESSAGE to dequeue the next message that meets the criteria, and NEXT_TRANSACTION to move to a set of messages queued by another transaction. ORA-25234 Invalid NEXT_TRANSACTION scan option for queue table string.string Cause: The NEXT_TRANSACTION scan option was used on a queue in a queue table that was not created for transactional pooling. Action: Specify FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional pooling, create the queue in a queue table that has transactional pooling enabled. ORA-25235 got all messages for the current transaction. Cause: The NEXT_TRANSACTION scan option was used on a queue when there were no other messages belonging to the same transaction. Action: Use the NEXT_TRANSACTION navigation option to go to the next one, and also use the FIRST_MESSAGE option to start again from the beginning of the queue. ORA-25236 Buffer too small for user data Cause: The variable or buffer used to load the output parameter is too small for the stripped user data.

ORA-24280 to ORA-29249

13-35

Action: Increase the size of the buffer or the size of the variable. The maximum size allowed is 32K. ORA-25237 navigation option used out of sequence Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after all messages were dequeued. Action: Reset the dequeue position with the FIRST_MESSAGE navigation option and specify the NEXT_MESSAGE or NEXT_TRANSACTION option. ORA-25238 Too many recipients specified for message destination string Cause: An ENQUEUE was performed with more than 32 recipients for the provided destination (address). Action: Reduce the number of recipients to 32 or less and try the call again. Message ID ORA-25239 was not supplied when dequeuing exception queue string.string Cause: An attempt was made to dequeue a version 8.0 compliant exception queue without including a message ID in the options exit queue. Action: Check the application to make sure the queue name was specified correctly. If the queue name is correct, provide a message ID when removing a version 8.0-compliant exception queue. Otherwise, update the QUEUE_TABLE that contains the queue to be compatible with version 8.1 using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. ORA-25240 Message ID and Correlation ID specified in dequeue options Cause: An attempt was made to delete the queue by including a message ID and correlation ID in the dequeue options. In the dequeue options, you can specify a message ID or a correlation ID or no ID. User Response : To remove a message from the queue, specify either a message ID or a correlation ID in the dequeue options, but do not specify both. If you want to delete the queue in queue sort order, do not specify the message ID or correlation ID in the dequeue options. ORA-25241 cannot change correlation ID from one chain to another without FIRST_MESSAGE option Cause: An attempt was made to change the correlation ID when using the NEXT_MESSAGE or NEXT_TRANSACTION option to remove the queue. Action: To use a different correlation ID from the previous dequeue call, reset the dequeue position with the FIRST_MESSAGE navigation option.

13-36 Error messages

ORA-25242 cannot change subscriber name from one chain to another without FIRST_MESSAGE option Cause: An attempt was made to change the subscriber name when using the NEXT_MESSAGE or NEXT_TRANSACTION option to remove the queue. Action: To use a different subscriber name than the previous dequeue call, reset the dequeue position with the FIRST_MESSAGE navigation option. ORA-25243 CONSUMER_NAME cannot be specified when dequeuing exception queue string.string Cause: An attempt was made to dequeue an exception queue by specifying CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when queuing a regular queue created for multiple consumers. Action: Specify only the message ID in the delete queue options to delete a message from an exception queue. ORA-25244 Dequeue index key not found, string QUEUE, row ID string Cause: An internal error was encountered. There may be an inconsistency in the queue table index. Action: Contact Oracle Customer Support. You may need to provide the trace file and information on how to reproduce the error. ORA-25245 Agent name cannot be specified if address is single consumer queue or exception queue. Cause: The agent name for the agent on the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue. Action: Do not specify the name of the agent. Listen failed ORA-25246, address string is 8.0-style exception queue Cause: An 8.0-style exception queue was specified in the agent list for the LISTEN call. Action: Specify a regular 8.0-style queue or an 8.1-style queue in the agent list. The string ORA-25247 is not the recipient of the specified message. Cause: The consumer name specified in the dequeue options is not the recipient of the message specified by the message ID. Action: Make sure that the agent specified by the consumer name is a recipient of the message specified by the message ID.

ORA-24280 to ORA-29249

13-37

ORA-25248 Duplicate agent specified in agent list Cause: An agent was specified more than once in the agent list for the LISTEN call. Action: Remove the duplicate agent specifications and retry the call. ORA-25249 queue deletion failed, queue deletion is not allowed for queue string.string Cause: An attempt was made to delete a non-persistent queue. Action: Dequeue a different queue. ORA-25250 Cannot specify remote recipient for message Cause: A message recipient on a non-persistent queue had a non-local address. Action: Do not specify the address field or specify the queue that is the destination of the enqueue ORA-25251 The maximum number of recipients of the message was exceeded Cause: An attempt was made to issue an ENQUEUE call that exceeded the maximum number (1024) of recipients per message Action: Reduce the number of recipients to 1024 or less and try the call again. ORA-25252 listener error, address string is a non-persistent queue Cause: A non-persistent queue was specified as the address for an agent on the LISTEN call. Action: Specify a normal queue as the address for the agent and repeat the LISTEN call. Listener failed ORA-25253, queue string.string not enabled for dequeue Cause: An attempt was made to specify a queue that is not enabled for dequeueing on a LISTEN call. Action: Enable the queue to remove the queue using START_QUEUE and repeat the LISTEN call. ORA-25254 LISTEN timed out while waiting for a message Cause: The specified timeout expired and there were no messages for any of the agents in the agent list. Action: Test the LISTEN call with a suitable timeout. ORA-25255 bad signature string string Cause: Bad signature string was specified with OCIRegister.

13-38 Error messages

Action: Specify a signature string using the form [CONSUMER:]SCHEMA.QUEUE. ORA-25256 Consumer cannot be specified with a single consumer queue or exception queue Cause: An attempt was made to specify a consumer in the subscription chain when registering to receive notifications on a single consumer queue or an exception. Action: Do not specify the consumer in the signature string. The ORA-25257 consumer must be specified with a multi-consumer queue. Cause: An attempt was made to register with a multi-consumer queue without specifying a consumer in the subscription string. Action: Specify a consumer in the signature string. ORA-25258 cannot register for notifications on an 8.0-style exception queue Cause: An attempt was made to specify an 8.0-style exception queue in the OCIRegister signature string. Action: Specify a normal queue or a non-persistent queue. ORA-25259 unable to specify protocol for agent Cause: User-specified protocol attribute for an agent in the agent list. Action: Do not specify the agent object type protocol attribute. ORA-25261 JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation Cause: AQ Propagator found a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation. Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation. ORA-25262 Agent name cannot be NULL if address is multi-consumer queue Cause: Agent name in the LISTEN call was not specified when agent address was multi-consumer queue. Action: Specify a non-null name for the agent. ORA-25263 no message in queue string.string with id string. Message ID Cause: An attempt was made to dequeue a message with a message id. specific message name, but that message does not exist on the queue. Action: Try to dequeue again with a valid message ID.

ORA-24280 to ORA-29249

13-39

ORA-25276 The specified table is not a queue table Cause: An invalid queue table name was specified. Action: Check the dictionary views to see if the table is a queue table. ORA-25277 cannot grant or revoke object privilege on 8.0-compliant queues Cause: An attempt was made to grant or revoke object privilege on version 8.0-style queues. Action: Convert the version 8.0 compatible queue table to a version 8.1 compatible queue table using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking the object privilege. ORA-25278 Payee name cannot be NULL Cause: An attempt was made to specify NULL for the payee parameter. Action: Specify a valid payee parameter. ORA-25350 Maximum number of concurrent transaction branches exceeded Cause: The limit on the number of concurrent transaction branches was reached. Action: Increase the TRANSACTIONS initialization parameter and reboot the system. Transaction ORA-25351 is currently in use Cause: The transaction is currently in use by another session. Action: Do not switch to a transaction attached to some other session. ORA-25352 no current transaction Cause: The user session is not attached to any transaction. Action: Do not attempt to disconnect when there is no current transaction. ORA-25353 branch marked for deletion Cause: The specified branch cannot be dropped immediately because another session is using the branch, but it has been marked for deletion. This means that it will be removed as soon as possible after the current uninterrupted operation completes. Action: No action is required for the branch to be deleted.

13-40 Error messages

ORA-25400 must fetch Cause: An error occurred since the last fetch on this statement. Failover was able to return the statement to its original state to allow for continued recoveries. Action: This is an internal use error message and should not be seen by the user. ORA-25401 cannot continue fetches Cause: A failure has occurred since the last fetches on this statement. Failover was unable to return the statement to its original state to allow for continuation of recoveries. Action: Rerun the statement and start searching from the beginning. Transaction ORA-25402 needs to be rolled back Cause: An error occurred while a transaction was active on this connection. Action: The client should revert. ORA-25403 failed to reconnect Cause: The connection to the database was lost and reconnection attempts failed. Action: Reconnect manually. ORA-25404 instance lost Cause: The primary instance was terminated. Action: This is an internal use error message and should not be seen by the user. ORA-25405 Transaction Status Unknown Cause: An error occurred while trying to commit a transaction. Failover could not automatically determine the state of the instance. Action: The user must determine the status of the transaction manually. ORA-25406 Failed to generate a connection address Cause: Failover was unable to generate an address for a backup instance. Action: Contact Oracle Customer Support. ORA-25407 connection closed Cause: The connection was lost during a recovery. Action: This is an internal use error message and should not be seen by the user.

ORA-24280 to ORA-29249

13-41

ORA-25408 cannot play the call safely Cause: The connection was lost during this call. It may not be safe to reproduce after failover. Action: Verify that the results of the call have been produced and play the call if desired. ORA-25425 Lost connection during rollback Cause: The connection was lost while issuing a rollback. Action: If the transaction is not externally coordinated, Oracle will implicitly roll back, so no action is required. If not, examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required. ORA-25426 remote instance does not support shared dblinks Cause: A shared database link is being used to connect to a remote instance that does not support this feature because it is an older version. Action: Use a normal database binding if you need to connect to this instance. The specified rule set ORA-25436 does not exist Cause: An attempt was made to access a rule set, but the referenced rule set does not exist. Action: Look for the correct rule set name in USER_RULESETS. ORA-25437 rule chain does not exist Cause: An attempt was made to access a rule, but failed because the rule does not exist. Action: Look up the rule in the rule storage table, which can be found in USER_RULESETS. ORA-25438 The specified table does not exist Cause: An attempt was made to define a set of rules on a table, but failed because the rule does not exist. User Response : Define rule sets only on existing tables. ORA-25440 duplicate ruleset Cause: An attempt was made to define a ruleset, but it failed because a ruleset with the same name exists in the same schema. Action: Define a rule set with a different name.

13-42 Error messages

ORA-25441 duplicate rule chain Cause: An attempt was made to define a rule, but it failed because a rule with the same name already exists in the same rule set. Action: Define a rule with a different name. ORA-26000 partition load specified but table chain is not partitioned Cause: The loader control file contains a PARTITION clause, but the table being loaded is not partitioned. Action: Remove the partition specification from the SQL*Loader control file and retry the load. ORA-26001 The index string specified in SORTED INDEXES does not exist in table string Cause: A non-existent index was specified in the SORTED INDEXES clause. Action: Do not specify as SORTED INDEX. ORA-26002 The table string has a defined index. Cause: Parallel load was specified on a table that has an index defined. Action: Drop the indexes defined on the table, or do not use parallel loading, or use the SKIP_INDEX_MAINTENANCE option. ORA-26003 Parallel load is not supported for index-organized table chain Cause: Parallel load is not supported for index-organized tables. User Response: Load the index-organized table without the PARALLEL option. ORA-26004 Tables loaded via direct path cannot be clustered Cause: An attempt was made to load a clustered table via direct path. Action: Use the conventional path. ORA-26007 For the INSERT option, the table must be empty. Table string error Cause: The user attempted to use the INSERT option on a table that was not empty. Action: Empty the SQL*Plus table or use the REPLACE option. ORA-26008 NOT NULL column string has a nullif clause Cause: A NOT NULL column in the database has a NULLIF clause of SQL*Loader. User Response: Remove the NULLIF clause from the SQL*Loader control file.

ORA-24280 to ORA-29249

13-43

ORA-26009 NOT NULL column string has a defaultif clause that can evaluate to null Cause: A column that is NOT NULL in the database has a SQL*Loader DEFAULTIF clause that can evaluate to null. User Response: Remove the DEFAULTIF clause from the SQL*Loader control file. ORA-26010 Column string in table string IS NOT NULL and will not load Cause: A column that is NOT NULL in the database will not load and will cause all rows to be rejected. User Response: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file. ORA-26011 Tables loaded via direct path might not be object tables Cause: An attempt was made to load an object table via direct path. Action: Use the conventional path. ORA-26012 Tables loaded via direct path might not have object columns Cause: An attempt was made to load a table with an object column via direct path. Action: Use the conventional path. ORA-26013 Tables loaded via direct path cannot be nested. Cause: An attempt was made to load a nested table via the direct path. Action: Use the conventional path. ORA-26014 Tables loaded via direct path might not have REF columns Cause: An attempt was made to load a table with a REF column via direct path. Action: Use the conventional path. ORA-26015 Tables loaded via direct path might not have array columns Cause: An attempt was made to load a table with an array column via direct path. Action: Use the conventional path. ORA-26016 Record String: Rejected: table string error, partition string Cause: The indicated record caused an Oracle error when inserting it.

13-44 Error messages

Action: Determine the Oracle error and correct the log. The offending column(s) is(are) unknown. ORA-26017 Global indexes not allowed on direct path partition load, table chain Cause: Global indexes are defined on a table when the direct path loads a single partition of the table. User Response : Drop the global index on the indicated table and retry the operation. ORA-26018 Column string in table string does not exist Cause: The column specified in the loader control file does not exist. Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is incorrect. ORA-26019 Column string in table string of type string not supported by direct path Cause: The specified column of string of SQL column type is not supported by the direct path loader. Action: If the column is nullable, remove it from the control file description. So it will be loaded as NULL. ORA-26020 index string.string successfully loaded with string keys Cause: Unpartitioned index information placed in loader log file. Action: No action is required. This is an informative message. ORA-26021 index string.string partition string successfully loaded with string keys Cause: Partitioned index information placed in loader log file. Action: No action is required. This is an informative message. ORA-26022 index string.string became unusable due to: Cause: A non-partitioned index became unusable due to the error listed below this error. Action: Depending on the error, either rebuild the index or drop it and build it again. ORA-26023 index string.string The partition string became unusable due to: Cause: A partition of a partitioned index became unusable due to the error listed below this error.

ORA-24280 to ORA-29249

13-45

Action: Depending on the error, rebuild the index partition or drop and rebuild the entire index. ORA-26024 SKIP_UNUSABLE_INDEXES requested and index segment initially unusable Cause: The user requested the SKIP_UNUSABLE_INDEXES option and the index segment was in an unusable state before the load began. Action: informational only. The user will need to rebuild the index or index partition or rebuild the index. ORA-26025 SKIP_INDEX_MAINTENANCE Option Requested Cause: A request was made to skip index maintenance on a direct route load. Action: The listed index was placed in the Unusable Index state because the user requested that index maintenance be bypassed. Rebuild the index or index partitions, or drop and rebuild the index. ORA-26026 unique index string.string initially in unusable state Cause: A unique index is in UI state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES). Action: Rebuild the index or index partition or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. ORA-26027 unique index string. string partition string initially in unusable state Cause: A single index partition is in UI state (a single index cannot bypass index maintenance via SKIP_UNUSABLE_INDEXES). Action: Rebuild the index or index partition or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. ORA-26028 index string.string initially in unusable state Cause: An index is in the UI state before the start of a direct path load, the loader cannot maintain it. Action: Rebuild the index, re-create it, or use SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only). ORA-26029 index string.string partition string initially in unusable state Cause: A partition of an index is in the UI state before the start of a direct path load, the loader cannot maintain it.

13-46 Error messages

Action: Rebuild the index partition, rebuild the index, or use SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only). ORA-26030 index string.string had unused string partitions due to: Cause: A logical index error occurred on a partitioned index that affected one or more index partitions, listed below this message. Action: The affected index partitions will need to be rebuilt or the entire index will be dropped and rebuilt. Index maintenance error ORA-26031, load cannot continue Cause: An index error occurred during the index maintenance phase of a direct path load. The upload cannot continue. See the error message below this message. Action: See the action for the error message that follows this one. ORA-26032 index string.string loading stopped after string braces Cause: An index error occurred while directly loading an index-organized table. The upload had to be aborted. No lines loaded. Action: Verify the key by simply following the number of keys mentioned above. This key caused the index problem mentioned in a previous post. ORA-26033 error evaluating string from index.string,rowstring due to: Cause: An index error occurred while trying to evaluate an expression at a functional index. User Response: Verify that the input data is valid for the functional index. ORA-26034 Encountered logical end of record while reading length of variable-length field Cause: An attempt to read the length part of a variable-length field reached the logical end of the record. Action: Verify that the control file describes the data correctly and that the data in the data file matches the description in the control file ORA-26035 Log String: Rejected: table string error, subpartition string Cause : The indicated record caused an Oracle error on insert. Action: Determine the Oracle error and correct the log. The offending column(s) is(are) unknown.

ORA-24280 to ORA-29249

13-47

ORA-26036 Subpartition load specified but table chain is not subpartitioned Cause: The loader control file contains a PARTITION clause, but the table being loaded is not subpartitioned. Action: Remove the subpartition specification from the SQL*Loader control file and retry the load. ORA-26037 Record string: rejected: table string error, subpartition string Cause: The indicated record caused an Oracle error on insert. Action: Determine the Oracle error and correct the log. The offending column(s) is(are) unknown. ORA-26038 error converting character length field to a number Cause: An error occurred while trying to convert characters that contained the count part of a VARCHARC or VARRAWC field. User Response: Verify that the count portion of the field has the correct value. ORA-26039 Table chain has a domain index defined Cause: Direct path load was specified for a table that has a domain index defined. Action: Drop the domain indices defined on the table or use the conventional route. ORA-26040 Data block was loaded using the NOLOGGING option Cause: An attempt was made to access data in a block that was loaded without generating a redo using the NOLOGGING/UNRECOVERABLE option. Action: Drop the object that contains the block. ORA-26041 DATETIME/INTERVAL data type conversion error Cause: The column could not be converted from the DATETIME data type to the internal DATETIME/CHARACTER data type. Action: Contact Oracle Customer Support. ORA-26042 cannot convert format string to internal format Cause: An attempt to convert a DATETIME format string to internal format in preparation for processing the DATETIME data type failed. Action: Contact Oracle Customer Support.

13-48 Error messages

ORA-26043 cannot convert time zone for DATETIME/INTERVAL processing Cause: An attempt to convert the time zone specified by the ORA_STDZ environment variable to internal format failed. Action: Verify that the ORA_STDZ setting is valid. ORA-26044 Unable to get DATETIME/INTERVAL date reference Cause: An attempt to retrieve the system date reference for DATETIME/INTERVAL data types failed. Action: Contact Oracle Customer Support. The file string ORA-26078 is not part of the database being loaded. Cause: A parallel load file was specified that is not part of the database. Action: Verify that the file name and path name are correct. The string in the ORA-26079 file is not part of the table string.string Cause: A parallel load file was specified that is not in the tablespace of the table being loaded. Action: Verify that the specified parallel load file is in the table space of the table being loaded. ORA-26080 file string is not part of table string.string partition string Cause: A parallel load file was specified that is not in the table space of the table (partition, subpartition) being loaded. When loading a partitioned table, the file must be in the tablespace of each partition or subpartition (ie, each (sub)partition must be in the same tablespace). Action: Specify a different parallel load file or no file. ORA-26081 Payload Stream Synchronization Error Cause: The row header flag byte contains an unexpected value, this indicates that there was an error generating or sending the payload stream from the client to the server. Action: Typically due to a programming error in the application that handles error handling or does not reset the state of the flow. ORA-26082 Loading of overlapping segments into table string.string is not allowed Cause: The client application tries to perform multiple direct path load operations on the same table, but the segments overlap. Action: Check the partition names (direct path context subname attribute) being loaded. Make sure you are not loading a table and partition from

ORA-24280 to ORA-29249

13-49

same table Make sure not to load a partition and a subpartition within the same partition. ORA-26084 direct path context already completed Cause: An OCIDirPathLoadStream operation was attempted after calling OCIDirPathFinish. Once a direct route operation is complete, no more data can be loaded. Action: Check the logic of the program to ensure that OCIDirPathLoadStream is not called after OCIDirPathFinish. ORA-26085 Direct path operation must start its own transaction Cause: A direct path operation is being attempted within a transaction that has already started. Action: Commit the transaction and redo the direct route operation. ORA-26086 direct path does not support triggers Cause: A direct path operation is being attempted on a table that has triggers enabled. Action: Disable the triggers on the table and try again. ORA-26087 Direct path does not support referential or check constraints. Cause: A direct path operation is being attempted on a table that has enabled referential integrity or check constraints. Action: Disable referential integrity and/or check the constraints on the table and try again. ORA-26088 The scalar column 'string' must be specified before the LOB columns. Cause: All scalar columns (that is, non-LOB and non-LONG columns) must be specified using the direct path API client before specifying any LOB columns. User Response : Specify all scalar columns before specifying any LOB columns. ORA-26089 The LONG column 'string' must be specified last. Cause: A direct route API client specified a LONG column to be loaded, but the LONG column was not the last column specified. Action: Specify the last LONG column.

13-50 Error messages

ORA-26090 row is in partial state Cause: A direct path operation is completing or a save data request was made, but the table for which the request is made has a row in partial state. The line must be completed before the segment's high watermarks can be moved. Action: Complete the line or stop the direct route operation. ORA-26091 The requested direct path operation is not supported Cause: An unsupported direct path operation was requested Action: Do not use this operation. UNLOAD is currently not supported. ORA-26092 only types LONG or LOB can be partial Cause: A column that is not LONG or LOB had the OCI_DIRPATH_COL_PARTIAL flag associated with it. Only columns of type LONG or LOB can be loaded in chunks. Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column. ORA-26093 stream offset is not mapped to a column array Cause: The ROW_COUNT attribute was being read from a direct route stream identifier and discovered that the stream offset for the last row processed was not mapped to a column matrix displacement. Action: Make sure the stream comes from a column array. ORA-26094 Stream Format Error: Input Column Overflow Cause: An input stream contained data for more input columns than specified by the direct route API client. Action: Make sure the stream being loaded is for the correct table. Check the boot sequence. ORA-26095 There is raw stream data Cause: A call was made to OCIDirPathLoadStream that provided more stream data before the server could fully process the stream data it already has, or a call was made to OCIDirPathFinish when the server had raw streaming data. Action: Probably misuse of the Direct Path API by the application. Ensure that the stream is not inadvertently reset before the data from the previous stream is processed, or that OCIDirPathFinish is not called prematurely (that is, the stream was sent, an error was encountered, and LoadStream was not called to process the stream). rest of the sequence before the end is called). ).

ORA-24280 to ORA-29249

13-51

ORA-26096 The transfer size is too small for the line data (number of bytes required) Cause: The specified transfer buffer size or the default transfer buffer size (if you did not specify a size) is too small to hold a single row of the converted row data. User Response : Set the direct path context transfer buffer size attribute to be larger. ORA-26097 Conversion is not supported for column string (type number to type number) Cause: The direct path API does not support the required conversion. Action: Make sure the types are correct. ORA-26098 Direct path context not ready Cause: A direct path API function was called with a direct path context that was not ready. Action: Ensure that all required attributes have been set on the direct path context and that the context is prepared via OCIDirPathPrepare. ORA-26099 Direct path context already prepared Cause: OCIDirPathPrepare was called with a context that was already prepared. Action: Release the direct path context, set the required attributes, and call OCIDirPathPrepare. ORA-26100: unused error Cause: This error is not used. Action: No action is required. ORA-26101 tablespace # in file header is a string instead of string for string file Cause: The tablespace number in the file header is not consistent with the one in the control file. Action: Verify that the control file was successfully migrated. Try again with the correct control file and data file. ORA-26102 relative file number in file header is a string instead of string for file string Cause: The relative file number in the file header is inconsistent with that in the control file. Action: Verify that the control file was successfully migrated. Try again with the correct control file and data file.

13-52 Error messages

ORA-26103 V6 or V7 data file used to create a control file Cause: The referenced file header is in V6 or V7 format. Action: Remove the file from the create control file command or somehow migrate the file header to V8 format. Error ORA-26500 caching "string"."string" Cause: An attempt was made to cache replication information that is not available in the object catalog. Action: Use DBMS_REPUTIL.SYNC_UP_REP to validate the replication catalog or use DBMS_REPUTIL.MAKE_INTERNAL_PKG to validate the internal package. ORA-26501 RepAPI operation failed Cause: An external RepAPI operation failed. Action: See the error message for more details. ORA-26502 resignation error Cause: An internal service failed and reported an error. Action: See the error message for more details. ORA-26503 RepAPI internal operation failed on object string.string Cause: An unexpected RepAPI internal failure was detected. Action: Contact Oracle Customer Support. ORA-26504 operation not implemented Cause: The caller requested a RepAPI operation that was not implemented. Action: Do not issue this call. ORA-26505 unexpected internal null Cause: An internal buffer control structure was NULL. User Response : Make sure there are enough memory resources available for RepAPI. Null Global Context ORA-26506 Cause: An internal buffer control structure was NULL. User Response : Make sure there are enough memory resources available for RepAPI. ORA-26507 null master connection Cause: The master connection identifier was invalid or no longer valid.

ORA-24280 to ORA-29249

13-53

Action: Verify that the primary connection is valid. ORA-26508 null snapshot connection Cause: The client connection identifier was invalid or no longer valid. Action: Verify that the client connection is valid. ORA-26509 Null snapshot control structure Cause: Unable to get an internal snapshot control structure. Action: Verify that the owner and users provided are correct. Snapshot name ORA-26510: 'string' is greater than max. allowed string byte length Cause: The snapshot name specified was too long. Action: Shorten the snapshot name. ORA-26511 master table 'string.string' not found Cause: A RepAPI operation was attempted on a non-existent or invalid master table. User Response : Check if the master table object exists. ORA-26512 error sending transaction to def$error Cause: An unexpected error occurred while sending a DEF$ERROR RPC to the master site. Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact your local administrator or site master if necessary. ORA-26513 insert error: master process. string$RP.string failed for trans:string seq:string Cause: A conflict/error occurred on the master site while executing a $RP.rep_insert(), rep_update() or rep_delete() function that was not handled by the logic of conflict resolution in the master. Action: Notify the master site system administrator or database administrator. ORA-26514 object 'string.string' not found Cause: The specified object was expected, but was not found. User Response : Check that the specified object exists and is valid.

13-54 Error messages

ORA-26515 No master record available for 'string.string' Cause: The specified master record was not found or available for the named table. Action: Create the master record at the master site or correct any problems that might exist with the record. ORA-26516 no push transaction acknowledgment Cause: RepAPI was unable to confirm that the master site successfully committed the last push transaction. Action: Verify that the communication link between the local site and the master site is still valid. If the transaction has not been committed on the master, repeat the transaction. ORA-26517 Snapshot control entry not found for 'string.string' Cause: The specified snapshot catalog control record was not found. User Response : Check that the local snapshot catalog is valid and that the local snapshot is configured correctly. ORA-26518 Push queue synchronization error detected Cause: The client attempted to resubmit a transaction that was already committed on the master site. A common cause of this problem is a site-local error initializing or updating the site-local transaction sequencing engine. Action: Verify that the transaction data that RepAPI was trying to send to the master site exists in the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then removed from the local updatable snapshot records. Verify that the local site is correctly assigning new transaction IDs and not accidentally generating non-unique values. ORA-26519 No memory available to allocate Cause: There was not enough memory left for the RepAPI process. This error can occur when RepAPI tries to allocate a new table buffer area. Action: Exit one or more local applications to try to free heap memory and retry the RepAPI operation. Internal memory failure ORA-26520 Cause: An internal memory error was detected. Action: Check for other errors or determine if a local application might have corrupted the memory subsystem.

ORA-24280 to ORA-29249

13-55

ORA-26521 rpc initialization error Cause: An error occurred while initializing a PL/SQL RPC. Action: Verify that the procedure to be called exists and is valid on the master site and that it is executable by the RepAPI user. ORA-26522 rpc execution error Cause: An error occurred while executing a PL/SQL RPC. Action: Check the error messages from the remote procedure and correct any problems at the remote site that might be preventing the invoked RPC from executing. ORA-26523 rpc Termination Error Cause: An error occurred while terminating a PL/SQL RPC. This is usually because the master site can't close an open cursor or RepAPI can't deallocate internal memory. Action: Troubleshoot any server-side issues first, determine if the RepAPI memory subsystem has been corrupted. ORA-26524 nls subsystem initialization error for product=string, installation=string Cause: The NLS product/install error message file could not be located or initialized correctly. Action: Check that the error messages directory and files have been installed correctly. Session connection attempt failed ORA-26525 for string (@string) Cause: A connection to the specified database could not be established using the provided connection string. Action: Verify that the user, password, connection string, name services, network, and any processes listening to the remote site are installed and working correctly. ORA-26526 Snapshot SQL ddl parsing/expanding to string.string failed Cause: The Oracle master site was unable to parse the SQL snapshot definition query from the client correctly. Action: Verify that the DDL SQL snapshot is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions. ORA-26527 Local storage callback initialization phase failed for 'string.string' Cause: The client callback failed during its INIT phase for the named object.

13-56 Error messages

User Response : Check that the objects referenced by the client callback exist and are valid. Consult the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. ORA-26528 Local store callback procedure phase failed for 'string.string' Cause: The client callback failed during its PROC phase for the named object. Action: Consult the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. ORA-26529 Local storage callback timeout phase failed for 'string.string' Cause: The client callback failed during its TERM phase for the named object. Action: Consult the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Customer Support. ORA-26530 Unable to create snapshot update watchlist Cause: The snapshot watchlist could not be created. This is usually the result of an error accessing the local snapshot catalog. Action: Verify that the named snapshots are defined correctly and are valid. ORA-26532 Replication Parallel Push Simulated Site Error Cause: A parallel push performed with event 26531 enabled generates this error for the target site or network simulation failure. Action: Do not enable the event for normal operation. ORA-26534 collision: tranID number ignored and discarded Cause: A transaction that was sent had a transaction ID that collided with a transaction that was previously sent and committed at the master site. Action: See the action section for E_QUEUESYNC (26518). ORA-26535 Insufficient cache byte row number for table with row size = number Cause: A transaction that was sent had a transaction ID that collided with a transaction that was previously sent and committed on the master site. Action: Increase the size of the RepAPI row buffer or reduce the width of the replicated tables. ORA-26536 update stopped due to deadlocks caused by deferred transactions. Cause: There are pending deadlocks logged in the DEFERROR table at the snapshot master site.

ORA-24280 to ORA-29249

13-57

Action: Resolve the conflicts in the DEFERROR master table and refresh again after the table is empty. Alternatively, update with REFRESH_AFTER_ERRORS even if there are conflicts in the master's DEFERROR table. Continuing despite conflicts can cause changes to an updateable snapshot to appear to be temporarily lost, until an update is performed after the conflicts are resolved. ORA-26563 Not allowed to rename this table Cause: An attempt is made to rename a replicated table, an updatable snapshot table, or the master table of a snapshot for which a snapshot record was created. Action: If desired, unregister the replicated table with DBMS_REPCAT.DROP_MASTER_REPOBJECT or use the best practice to rename the master table of a snapshot. ORA-26564 string argument is not of specified type Cause: The user-passed type of the supplied argument number does not match the argument type in the stored arguments. Action: Call the procedure of the correct type (ie get_XXX_arg). ORA-26565 Type_arg called before calling dbms_defer.call Cause: The user called the type_arg procedure before starting a deferred call. Action: Invoke multiple procedures in the correct order. ORA-26566 Cannot open connection with string Cause: The connection could not be opened using the provided database link. Action: Make sure the database link is valid and the remote m/c is up. ORA-26571 string.string.string: number of arguments (string) does not match replication catalog Cause: Number of arguments does not match replication catalog. User Response : Examine the total number of arguments to the RPC call. ORA-26572 string.string.string: argument string does not match replication catalog Cause: Call (RPC) is corrupted. Action: Examine the total number of arguments and each argument of the RPC call.

13-58 Error messages

ORA-26575 remote database does not support parallel replication initialization Cause: The remote database is older than Oracle 8.0 and therefore does not understand parallel replication initialization. Action: Use serial initialization or upgrade the remote database to Oracle 8.0 or higher. ORA-27000 skgfqsbi: failed to initialize storage subsystem layer (SBT) Cause: SBTINIT returned an error, additional information indicates an error. Action: Verify that the vendor's storage subsystem product is working properly. Unsupported Device Type ORA-27001 Cause: The specified device type is supported on this platform. Action: Check V$BACKUP_DEVICE for supported device types. ORA-27002 function called with invalid device structure Cause: An internal error occurred. The additional information indicates which function encountered the error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27003 cannot open file on device assigned with NOIO option Cause: An internal error occurred. A file is being created/retrieved on a device assigned with the NOIO option, the additional information indicates which function encountered the error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27004 Invalid block size specified Cause: An internal error occurred. The specified block size is incorrect for the device on which the file is being created, additional information indicates the specified block size and the function that encountered the error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27005 cannot open file for asynchronous I/O on a device that does not support asynchronous Cause: An internal error occurred. A file is being opened for asynchronous I/O on a device that does not support asynchronous I/O; the additional information indicates which function encountered the error. Action: Check for a trace file and contact Oracle Customer Support.

ORA-24280 to ORA-29249

13-59

ORA-27006 sbtremove returned an error Cause: Additional information indicates the error returned by SBTREMOVE and the function that encountered the error. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27007 Could not open file Cause: SBTOPEN returned an error, additional information indicates the error returned by SBTOPEN and the function that encountered the error. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27008 function called with invalid file structure Cause: An internal error occurred. The additional information indicates which function encountered the error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27009 skgfwrt: cannot write to file open for reading Cause: An internal error occurred. Action: Check for a trace file and contact Oracle Customer Support. ORA-27010 skgfwrt: Error writing file Cause: SBTWRITE returned an error, additional information indicates that SBTWRITE returned an error. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27011 skgfrd: cannot read file open for writing Cause: An internal error occurred. Action: Check for a trace file and contact Oracle Customer Support. ORA-27012 skgfrd: error reading file Cause: SBTREAD returned an error, additional information indicates that SBTREAD returned an error. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27013 skgfqdel: cannot delete an open file Cause: An internal error occurred.

13-60 Error messages

Action: Check for a trace file and contact Oracle Customer Support. ORA-27014 skgfqpini: translation error expanding SS_UDMPDIR Cause: SLTLN error in SKGFQPINI. Action: Check the additional return error for more information. ORA-27015 skgfcls: could not close file Cause: SBTCLOSE returned an error. The additional information indicates an error returned by SBTCLOSE. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27016 skgfcls: sbtinfo returned an error Cause: Additional information indicates that SBTINFO returned an error. Action: Verify that the vendor's storage subsystem product is working properly. ORA-27017 skgfcls: media identifier returned by sbtinfo exceeds maximum length (SSTMXQMH) Cause: The length of the media identifier string exceeds SSTMXQMH. Action: Verify that the vendor's storage subsystem product is working correctly and that the platform threshold (SSTMXQMH) is at least 64 (the threshold specified for SBTINFO). the additional information indicates the length of the media identification string returned by SBTINFO and the threshold (SSTMXQMH). ORA-27018 BLKSIZE is not a multiple of the minimum physical block size Cause: The user-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size allowed on this platform. Action: Two ADDITIONAL INFORMATION messages are displayed showing the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integer multiple of the minimum block size. ORA-27019 Tape file name length exceeds limit (SBTOPMXF) Cause: The tape file name length supplied to the OSD sequential I/O functions is too long. Action: Additional information indicates in which function this error was encountered, the length of the given file name, and the file name limit.

ORA-24280 to ORA-29249

13-61

ORA-27020 Named devices not supported Cause: The specified device type or platform does not support named devices. Action: Do not specify the device name or use a device type that supports named devices. Use the V$BACKUP_DEVICE view to see what device types and names (if any) are available. ORA-27021 sequential file handle must be specified Cause: The file name to be passed to SBTOPEN was not specified. Action: Specify a file name and continue. If this is a Backup Set created with Recovery Manager, use the "format" option to specify the name of the backup part identifier. ORA-27022 skgfqsbi: failed to allocate memory for media manager Cause: Oracle was unable to allocate the memory required by Oracle-linked media management software to provide backup/restore services. Action: Increase the amount of memory available to the Oracle process and try the backup/restore again. ORA-27023 skgfqsbi: media manager protocol error Cause: Media management software linked to Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. This is an internal bug in the media management product. Action: Contact your media management provider. ORA-27024 skgfqsbi: sbtinit2 returned an error Cause: SBTINIT2 returned an error. This happens during a backup or restore operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27025 skgfqsbi: invalid media manager context area size Cause: The media management software requested a context area size larger than the maximum size allowed. This is an internal bug in the media management product. Action: Contact your media management provider.

13-62 Error messages

ORA-27026 skgfrls: sbtend returned an error Cause: SBTEND returned an error. This happens during a backup or restore operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27027 sbtremove2 returned an error Cause: SBTREMOVE2 returned an error. This happens when a backup file is deleted. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27028 skgfqcre: sbtbackup returned an error Cause: SBTBACKUP returned an error. This happens when a backup file is created during a backup operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27029 skgfrtrv: sbtrestore returned an error Cause: SBTRESTORE returned an error. This happens when a backup file is recovered during a restore operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27030 skgfwrt: sbtwrite2 returned an error Cause: SBTWRITE2 returned an error. This happens when a backup file is written during a backup operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider.

ORA-24280 to ORA-29249

13-63

ORA-27031 Mirror mirror functions are not supported Cause: An internal error occurred. Action: Check for a trace file and contact Oracle Customer Support. ORA-27032 skgfrpini: failed to get file size limit Cause: The GETRLIMIT system call returned an error. Action: Check errno. ORA-27033 skgfrpini: failed to get file size limit Cause: The ULIMIT system call returned an error. Action: Check errno. ORA-27034 skgfrcre: ORACLE_SID maximum length exceeded Cause: Too many characters in the ORACLE_SID string. Action: Change the name of ORACLE_SID to a string of up to the maximum number of characters specified for your system. ORA-27035 logical block size is invalid Cause: The logical block size for Oracle files must be a multiple of the physical block size and less than the maximum. Action: The specified block size is returned as additional information, check the initialization parameters, the additional information also indicates which function encountered the error. Translation error ORA-27036, cannot expand file name Cause: The additional information indicates an SLTLN/SLNRM error and also indicates which function encountered the error. Action: Verify the additional information. ORA-27037 unable to get file status Cause: The STAT system call returned an error; the additional information indicates which function encountered the error. Action: Check errno. ORA-27038 skgfrcre: file exists Cause: An attempt was made to create a database file, but the file with that name already exists. Action: Verify that the name is correct, specify to reuse if necessary.

13-64 Error messages

ORA-27039 Could not create file, file size limit reached Cause: An attempt was made to create a file that exceeds the process file size limit; the additional information indicates which function encountered the error. Action: Increase the file size limit. ORA-27040 skgfrcre: create error, cannot create file Cause: The Create system call returned an error, cannot create file. Action: Check the file name and permissions. ORA-27041 Unable to open file Cause: Open system call returned an error, additional information indicates which function encountered the error. Action: Check errno. ORA-27042 there is not enough space in the raw partition for the service request Cause: This is an internal error. The file is too large for the raw partition. The additional information indicates which function encountered the error. Action: Check the trace file and contact Oracle Customer Support. ORA-27043 could not get start of file Cause: Get system call failed, additional information indicates which function encountered the error. Action: Check errno. ORA-27044 Unable to write file header block Cause: Write system call failed, additional information indicates which function encountered the error. Action: Check errno. ORA-27045 cannot close file Cause: Close system call failed, additional information indicates which function encountered the error. Action: Check errno. ORA-27046 file size is not a multiple of logical block size Cause: The file size indicated by STAT is not correct, the additional information indicates which function encountered the error. Action: Check that the file has not been overwritten or truncated.

ORA-24280 to ORA-29249

13-65

ORA-27047 cannot read file header block Cause: Read system call failed, additional information indicates which function encountered the error. Action: Check errno. ORA-27048 skgfifi: Invalid file header information Cause: Possibly attempting to use a non-database file as the database file. User Response: Verify that the file is a database file. ORA-27049 cannot retrieve and read last block Cause: An attempt was made to retrieve and read the last block of the file; the additional information indicates which function encountered the error. Action: Check errno. ORA-27050 function called with invalid FIB/IOV structure Cause: This is an internal error. The additional information indicates which function encountered the error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27052 could not free file data Cause: An error was returned on the FSYNC system call, additional information indicates which function encountered the error. Action: Check errno. ORA-27053 skgfifi: Block size in file header is not a multiple of logical block size Cause: Invalid logical block size, additional information indicates logical block size and block size in file header file header. Action: Use a different logical block size or do not reuse the file. ORA-27056 skgfrdel: unable to delete file Cause: Failed to unbind system call. Action: Check errno. ORA-27057 skgfask: cannot perform asynchronous I/O on file Cause: This is an internal error. The query is done via asynchronous vector I/O when the file does not support asynchronous I/O. Action: Check for a trace file and contact Oracle Customer Support.

13-66 Error messages

ORA-27058 skgfask: Invalid question parameter Cause: This is an internal error. An invalid query is being performed. Action: Check for a trace file and contact Oracle Customer Support. ORA-27059 skgfrsz: unable to reduce file size Cause: An error was returned on the FTRUNCATE system call. Action: Check errno. ORA-27060 skgfofi: cannot set kill bit when executing on file Cause: The FCNTL system call returned an error. Action: Check errno. ORA-27061 skgfospo: asynchronous I/O wait failed Cause: The AIOWAIT function returned an error. Action: Check errno. ORA-27062 skgfospo: cannot find pending asynchronous I/O Cause: This is an internal error. There should be some asynchronous I/O in the system, but an AIOWAIT block indicates that there is no more I/O. Action: Check for a trace file and contact Oracle Customer Support. ORA-27063 skgfospo: number of bytes read/written is incorrect Cause: The number of bytes read/written returned by AIOWAIT does not match the original number; the additional information indicates these two numbers. Action: Check errno. ORA-27064 skgfdisp: cannot perform asynchronous I/O on file Cause: This is an internal error. A request was made to perform asynchronous I/O when IOV indicates that it cannot be performed on the file. Action: Check for a trace file and contact Oracle Customer Support. ORA-27065 skgfdisp: cannot perform asynchronous vector I/O to file Cause: This is an internal error. A request was made to perform asynchronous vector I/O when it cannot be performed on the file. Action: Check for a trace file and contact Oracle Customer Support.

ORA-24280 to ORA-29249

13-67

ORA-27066 skgfdisp: number of buffers in I/O array exceeds maximum Cause: This is an internal error. The number of buffers in the I/O vector exceeds the maximum allowed by the OSD, the additional information indicates these two numbers. Action: Check for a trace file and contact Oracle Customer Support. ORA-27067 skgfdisp: invalid buffer size Cause: This is an internal error. If the buffer size is 0 or greater than SSTIOMAX or is not a multiple of the logical block size, the additional information indicates where in the function the error was encountered and the buffer size. Action: Check for a trace file and contact Oracle Customer Support. ORA-27068 skgfdisp: buffer misaligned Cause: This is an internal error. The buffer is not aligned with the SSIOALIGN boundary, the additional information indicates where in the function the error was encountered and the buffer pointer. Action: Check for a trace file and contact Oracle Customer Support. ORA-27069 skgfdisp: attempt to do I/O beyond file range Cause: This is an internal error. The range of blocks being read or written is outside the range of the file, the additional information indicates the starting block number, the number of blocks in I/O, and the last valid block in the file. Action: Check for a trace file and contact Oracle Customer Support. ORA-27070 skgfdisp: asynchronous read/write error Cause: An error was returned on the AIOREAD/AIOWRITE system call, additional information indicates the starting I/O block number. Action: Check errno. ORA-27071 skgfdisp: Could not get desired position in file Cause: An error was returned from the LSEEK system call, the additional information indicates the block number in the file where the seek was attempted. Action: Check errno. ORA-27072 skgfdisp: I/O error Cause: An error was returned on the READ/WRITE/READV/WRITEV system call; the additional information indicates the starting I/O block number. Action: Check errno.

13-68 Error messages

ORA-27073 skgfcfi: Remaining asynchronous I/O will be dequeued for this file Cause: This is an internal error. The file is being closed, but not all asynchronous I/O to the file has been dequeued; the additional information indicates the number of pending I/Os on the file. Action: Check for a trace file and contact Oracle Customer Support. ORA-27074 skgfrofl: Could not determine limit for open files Cause: An error was returned on the GETRLIMIT system call. Action: Check errno. ORA-27075 skgfrofl: SSTMOFRC constant is too large Cause: This is an internal error. Action: Check for a trace file and contact Oracle Customer Support. ORA-27076 skgfrofl: cannot set limit for open files Cause: The SETRLIMIT system call returned an error. Action: Check errno. ORA-27077 skgfofi: too many open files Cause: This is an internal error. The number of files opened via SKGFOFI has reached the limit. Action: Check for a trace file and contact Oracle Customer Support. ORA-27084 skgfqio: unable to get/set file status flags Cause: The FCNTL system call with the F_GETFL/F_SETFL flag returned an error. Action: Check errno. ORA-27086 skfglk: cannot lock file; already in use Cause: The file is locked by another process, indicating that it is currently in use by a database instance. User Response : Determine which database instance is the rightful owner of this file. ORA-27087 skfglk: failed to get share lock: file cannot be read Cause: A share lock request was made on a file that was not opened for read access. Action: The file must be open in read-only or read/write mode to get a shared lock. ORA-27088 skfglk: unable to get file status Cause: The file is not open or the file descriptor is invalid.

ORA-24280 to ORA-29249

13-69

Action: Make sure the file is open and the descriptor is valid. ORA-27089 skgfrlk: could not release warning lock Cause: Could not release lock on file. Cause: See errno. ORA-27091 skgfqio: unable to enqueue I/O Cause: A read/write/read/write system call returned an error. The additional information indicates the starting I/O block number. Action: Check the errno. Shared memory domain ORA-27100 already exists Cause: An attempt was made to start duplicate instances or restart an instance that was not shut down correctly. Action: Use a different instance name or clear the SGA for the failed instance. Shared memory domain ORA-27101 does not exist Cause: The shared memory domain could not be found. Action: Verify that the domain is accessible. ORA-27102 out of memory Cause: out of memory. Action: Check the trace file for more information. Internal error ORA-27103 Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-27120 unable to remove shared memory segment Cause: The SHMCTL() call failed. Action: Check the permissions on the segment, contact Oracle Customer Support. ORA-27121 unable to determine shared memory segment size Cause: The SHMCTL() call failed. Action: Check the permissions on the segment, contact Oracle Customer Support. ORA-27122 unable to protect memory Cause: The call to MPROTECT() failed. Action: Contact Oracle Customer Support.

13-70 Error messages

ORA-27123 cannot connect to shared memory segment Cause: The SHMAT() call failed. Action: Check the permissions on the segment, contact Oracle Customer Support. ORA-27124 cannot detach from shared memory segment Cause: The SHMDT() call failed. Action: Contact Oracle Customer Support. ORA-27125 unable to create shared memory segment Cause: The SHMGET() call failed. Action: Contact Oracle Customer Support. ORA-27126 unable to lock shared memory segment in kernel Cause: Insufficient privileges to lock shared memory segment in kernel. Action: Make sure the process is running with the necessary privileges. ORA-27127 unable to unlock shared memory segment Cause: Insufficient privileges to unlock shared memory segment. Action: Make sure the process is running with the necessary privileges. ORA-27128 could not determine page size Cause: The call to SYSCONF() failed. Action: Contact Oracle Customer Support. ORA-27141 Invalid process ID Cause: The process operation was attempted using an invalid process ID. Action: Contact Oracle Customer Support. ORA-27142 failed to create a new process Cause: OS call failed. Action: Check the errno and if possible increase the number of processes. ORA-27143 OS call failed Cause: OS call failed. Action: Check the errno and contact Oracle customer support. ORA-27144 Failed to attempt to terminate process Cause: OS call error.

ORA-24280 to ORA-29249

13-71

Action: Check the errno and contact Oracle customer support. ORA-27145 Insufficient resources for the requested number of processes Cause: OS call error. Action: Check the errno and contact Oracle customer support. Post/wait initialization error ORA-27146 Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. ORA-27147 Post/wait reset error Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. ORA-27148 Build Wait Error Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. ORA-27149 assignment out of range Cause: This is an internal error. A mold too large for the type was requested. Action: Contact Oracle Customer Support. ORA-27150's attempt to notify process of pending oradebug call failed Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. ORA-27151 buffer is not large enough to hold the process ID string Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-27152 postprocessing attempt failed Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. Wait operation failed ORA-27153 Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support.

13-72 Error messages

ORA-27154 post/await creation error Cause: This is an internal error. An attempt was made to create multiple posts/waits simultaneously. Action: Check the errno and contact Oracle customer support. ORA-27155 could not execute file Cause: The call to the operating system failed. Action: Check the errno and contact Oracle customer support. ORA-27156 process info request failed Cause: This is an internal error. Action: Contact Oracle Customer Support. ORA-27190 skgfrd: sbtread2 returned an error Cause: SBTREAD returned an error. This happens when a backup file is read during a restore operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27191 sbtinfo2 returned an error Cause: SBTINFO2 returned an error. This happens when retrieving information from the media manager catalog backup file. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27192 skgfcls: sbtclose2 returned error: could not close file Cause: SBTCLOSE2 returned an error. This happens when a backup file is closed during a backup or restore operation. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider.

ORA-24280 to ORA-29249

13-73

ORA-27193 sbtinfo2 did not return volume label Cause: SBTINFO2 did not return volume label information for the newly created backup file. This is an internal bug in the media management product. Action: Contact your media management provider. ORA-27194 skgfdvcmd: sbtcommand returned an error Cause: SBTCOMMAND returned an error. This happens when an RMAN SEND command is issued. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27195 Proxy Copy Not Supported Cause: A proxy backup or restore was attempted, but the media management software installed with Oracle does not support proxy copy. Action: Run the backup in non-proxy mode again or contact your media management provider if their software supports proxy copy. ORA-27196 skgfpbk: sbtpcbackup returned an error Cause: SBTPCBACKUP returned an error. This happens when a proxy backup is started. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27197 skgfprs: sbtpcrestore returned an error Cause: SBTPCRESTORE returned an error. This happens when a proxy restore is started. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27198 skgfpvl: sbtpcvalidate returned an error Cause: SBTPCVALIDATE returned an error. This happens during a proxy backup or restore.

13-74 Error messages

Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27199 skgfpst: sbtpcstatus returned an error Cause: SBTPCSTATUS returned an error. This happens during a proxy backup or restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27200 skgfpgo: sbtpcsstart returned an error Cause: SBTPCSTART returned an error. This happens during a proxy backup or restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27201 skgfpcm: sbtpccommit returned an error Cause: SBTPCCOMMIT returned an error. This happens during a proxy backup or restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27202 skgfpen: sbtpcend returned an error Cause: SBTPCEND returned an error. This happens during a proxy backup or restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27203 skgfpqb: sbtpcquerybackup returned an error Cause: SBTPCQUERYBACKUP returned an error. This happens during a proxy backup.

ORA-24280 to ORA-29249

13-75

Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27204 skgfpqr: sbtpcqueryrestore returned an error Cause: SBTPCQUERYRESTORE returned an error. This happens during a proxy restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. ORA-27205 skgfpcn: sbtpccancel returned an error Cause: SBTPCCANCEL returned an error. This happens during a proxy restore. Action: This error is returned from Oracle-linked media management software. There should be additional messages explaining the cause of the error. This error usually requires contact with the media management provider. File requested ORA-27206 not found in media management catalog Cause: A backup file used in a Recovery Manager catalog maintenance command could not be found in the media management catalog. Action: Repeat the command with a different file. ORA-27207 Syntax error in device PARMS: missing or mismatched parentheses Cause: The user-supplied PARMS value has incorrect syntax. Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn ORA-27208 syntax error on device PARMS: environment variable value missing Cause: User-supplied PARMS value has incorrect syntax. Action: Retry the command with the correct syntax: ENV=(var1=val1,var2=val2,..) ORA-27209 syntax error on device PARMS: unknown or missing keyword = Cause: The PARMS value provided by the user has incorrect syntax. The server expected to find ENV or BLKSIZE but found an unknown keyword. Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn

13-76 Error messages

ORA-27210 syntax error on PARMS device Cause: The user-supplied PARMS value has incorrect syntax. Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn ORA-27300 OS dependent operation: string failed with status: string Cause: OS call failed. Action: Contact Oracle Customer Support. ORA-27301 OS Failure Message: string Cause: OS call failed. Action: Contact Oracle Customer Support. ORA-27302 error occurred in: string Cause: OS call failed. Action: Contact Oracle Customer Support. ORA-27303 additional information: string Cause: OS call failed. Action: Contact Oracle Customer Support. Inter-instance IPC error ORA-27500 Cause: Most likely an operating system call error. Action: Check the additional information and contact Oracle Customer Support. ORA-27501 IPC error creating port Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27502 IPC error configuring signal handler Cause: OS call failed. Action: Check the errno and contact Oracle customer support. ORA-27504 IPC error when querying the network address of a port Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27505 IPC failed to destroy a port Cause: OS call error.

ORA-24280 to ORA-29249

13-77

Action: Check the errno and contact Oracle customer support. ORA-27506 IPC failed to connect to a port Cause: OS call failed. Action: Check the errno and contact Oracle customer support. ORA-27507 IPC failed when disconnecting from a port Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27508 IPC error sending message Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27509 IPC error receiving message Cause: OS call failed. Action: Check the errno and contact Oracle customer support. ORA-27510 IPC error while waiting for a request to complete Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27512 IPC Error Publishing Process Cause: OS call error. Action: Check the errno and contact Oracle customer support. ORA-27528 cannot allocate zero-length communication buffers Cause: The client is trying to allocate a zero-length message. Action: See KGXP.H for the use of KGXPVALO(). ORA-27529 cannot allocate zero-length communication buffers Cause: The client is trying to allocate a zero-length message. Action: See KGXP.H for the use of KGXPVALO(). ORA-27530 cannot deallocate NULL memory pointer Cause: The client is passing a NULL pointer for deallocation. Action: See KGXP.H for the use of KGXPVFRE().

13-78 Error messages

ORA-27531 cannot destroy invalid port Cause: The port is invalid. Action: Re-create the port. ORA-27532 IPC global name service is not supported Cause: The global name service used by KGXP is not supported. Action: Use a service with a different name or stop the current process/thread. ORA-27533 attempting to destroy invalid connection identifier Cause: The connection identifier passed is invalid. Action: Check the connection identifier or stop the process/thread. ORA-27534 cannot send misaligned message Cause: The message being sent is not aligned within the required bounds. Action: Use the KGXPALSZ() macro to get the message align size and align all messages on this limit. ORA-27